UL failure handling for SBFD operation

Abstract

Systems and methods are disclosed that relate to uplink failure handling for SubBand Full Duplex (SBFD) operation. In one embodiment, a method performed by a User Equipment (UE) comprises receiving, from a network node, information that configures the UE for Physical Uplink Control Channel (PUCCH) Scheduling Request (SR) transmission on SBFD slots or symbols and non-SBFD slots or symbols and separately monitoring PUCCH SR transmissions for SBFD slots or symbols and non-SBFD slots or symbols. In this manner, efficient uplink failure monitoring and recovery is enabled. Further, triggering of radio link failure and Radio Resource Control (RRC) connection reestablishment if the UE only detects uplink failures for one specific resource type (SBFD or non-SBFD) can be avoided.

Description

[0001] UL FAILURE HANDLING FOR SBFD OPERATION

[0002] RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 683,935, filed August 16, 2024, the disclosure of which is hereby incorporated herein by reference in its entirety.

[0004] TECHNICAL FIELD

[0005] The present disclosure relates to a cellular communications system and, more specifically, to failure handling in a cellular communications system.

[0006] BACKGROUND

[0007] FDD and TDD Systems

[0008] Transmission and reception from a node, e.g. a User Equipment (UE) (also referred to herein as a “terminal”) in a cellular system, can be multiplexed in the frequency domain or in the time domain (or combinations thereof). Frequency Division Duplex (FDD) as illustrated to the left in Figure 1 implies that downlink and uplink transmission take place in different, sufficiently separated, frequency bands. Time Division Duplex (TDD), as illustrated to the right in Figure 1, implies that downlink and uplink transmission take place in different, non-overlapping time slots. Thus, TDD can operate in unpaired spectrum, whereas FDD requires paired spectrum.

[0009] Typically, the structure of the transmitted signal in a communication system is organized in the form of a frame structure.

[0010] In more detail, the following two information elements (IES) are defined in current 3rdGeneration Partnership (3GPP) New Radio (NR) specifications. The TDD pattern is typically configured with at least the first IE and optionally the second IE:

[0011] • TDD-DL-UL-ConfigCommon (cell-specific)

[0012] • TDD-DL-UL-ConfigDedicated (UE-specific)

[0013] The first IE is cell specific (common to all UEs) and is provided by broadcast signaling. It provides the number of slots in the TDD pattern via a reference subcarrier spacing and a periodicity such that the S-slot pattern repeats every S slots. This IE allows for very flexible configuration of the pattern characterized as follows:

[0014] • A number of full downlink slots at the beginning of the pattern configured by the parameter nDownlinkSlots

[0015] • A number of full uplink slots at the end of the pattern configured by the parameter nUplinkSlots • A number of downlink ('D') symbols following the full downlink slots configured by the parameter nDownlinkSymbols

[0016] • A number of uplink ('U') symbols preceding the full downlink slots configured by the parameter nUplinkSlots

[0017] • If there is a gap between the last downlink symbol and the first uplink symbol, then all symbols in the gap are characterized as flexible ('F'). A symbol classified as 'F' can be used for downlink or uplink. A UE determines the direction in one of the following two ways: o Detecting a Downlink Control Information (DCI) that schedules / triggers a downlink (DL) signal / channel, e.g., Physical Downlink Shared Channel (PDSCH), Channel State Information Reference Signal (CSI-RS) or schedules / triggers an uplink (UL) signal / channel, e.g. Physical Uplink Shared Channel (PUSCH), Sounding Reference Signal (SRS), etc. o By dedicated (UE-specific) signaling of the IE TDD-DL-UL-ConfigDedicated. This parameter overrides some or all of the 'F' symbols in the pattern, thus providing a semi-static indication of whether a symbol is classified as 'D' or U'

[0018] • Optionally, a 2ndpattern that is concatenated to the first pattern can be configured as above.

[0019] If a 2ndpattern is configured, the constraint is that the sum of the periodicities of the two patterns must evenly divide 20 milliseconds (ms).

[0020] Figure 2 shows an exemplary TDD DL / UL pattern configured by TDD-DL-UL- ConfigCommon. It consists of three full 'D' slots, one full U' slot, with a mixed slot in between consisting of four 'D' symbols and three U' symbols. The remaining seven symbols in the mixed slot are classified as 'F.'

[0021] If a UE is not configured with TDD-DL-UL-ConfigDedicated, then the pattern at the top of the diagram is what it assumes. As stated above, the network can make use of the 'F' symbols flexibly, by scheduling / triggering either an uplink or a downlink signal / channel in a UE specific manner. This allows for very dynamic behavior: the direction is not known to the UE a priori; rather, the direction becomes known once the UE detects a DCI scheduling / triggering a particular DL or UL signal / channel.

[0022] In contrast, the DL / UL direction for some or all of the 'F' symbols in a particular slot can be provided to the UE in a semi-static manner by Radio Resource Control (RRC) configuring the UE with TDD-DL-UL-ConfigDedicated. The lower part of Figure 2 shows three exemplary configurations for overriding 'F' symbols in Slot 3. If the IE indicates 'allDownlink' or 'allUplink' for a particular slot (or slots), then all 'F' symbols in the slot are converted to either 'D' or U,' respectively. If the IE indicates 'explicit,' then a number of symbols at the beginning of the slot and / or a number of symbols at the end of the slot are indicated as 'D' and 'U,' respectively. In the example below, the first seven slots and the last slots are indicated as 'D' and 'U', which converts some of the 'F' symbols (but not all in this example) to 'D' and 'U.'

[0023] The key behavior in the above is that the UE-specific IE TDD-DL-UL-ConfigDedicated can only override (i.e., specify 'D' or 'U') for symbols that are configured as 'F' by the cell-specific IE TDD-DL-UL-ConfigCommon. In other words, a UE does not expect to have a 'D' symbol converted to 'U' or vice versa.

[0024] Subband Full Duplex

[0025] As described in the last section, in a conventional TDD system, the entire carrier bandwidth (BW) or all carriers in the same frequency band need to be utilizing the same DL transmission or UL reception directions. This is further illustrated in Figure 3.

[0026] For the Rel-18 evolution of the New Radio (NR) system, 3rdGeneration Partnership Project (3 GPP) has decided to study the technical feasibilities and potential benefits of SubBand Full Duplex (SBFD) systems. In such a system, a portion of a wide bandwidth carrier may be used for a different direction than that of the rest of the carrier. This is illustrated in the left-hand side of Figure 4. That is, unlike a conventional TDD system as shown on the left-hand side of Figure 3 where the entire bandwidth is used for DL transmission in the first three slots, the center portion of the SBFD carrier is used for UL reception while the rest of the carrier continues to be used for DL transmission as shown in the left-hand side of Figure 4. Similarly, instead of utilizing all carriers for the same DL or UL directions in a conventional TDD system as shown in the righthand side of Figure 3, some carriers in the SBFD system can be used for a different direction than that of the other carriers as shown in the right-hand side of Figure 4.

[0027] In the 3 GPP Rel-18 study, the scope has been limited such that in SBFD operation, only NR base stations (i.e., next generation NodeBs, gNBs) transmit DL and receive UL simultaneously. An individual UE is scheduled in only one direction (DL or UL) at a time.

[0028] Scheduling Request

[0029] The Scheduling Request (SR) is described in clause 5.4.4 of 3GPP Technical Specification (TS) 38.321 V18.2.0. Some relevant details of the SR are shown in the following excerpt from clause 5.4.4 of 3GPP TS 38.312 V18.2.0 (emphasis added via bold font).

[0030] ***** START EXCERPT FROM 3GPP TS 38.321 *****

[0031] The Scheduling Request (SR) is used for requesting UL-SCH resources for new transmission. The MAC entity may be configured with zero, one, or more SR configurations. An SR configuration consists of a set of PUCCH resources for SR across different BWPs and cells. For a logical channel or for SCell beam failure recovery (see clause 5.17) and for consistent LBT failure recovery (see clause 5.21), at most one PUCCH resource for SR is configured per BWP. For a logical channel serving a radio bearer configured with SDT, PUCCH resource for SR is not configured for SDT. For beam failure recovery of BFD-RS set(s) of Serving Cell, up to two PUCCH resources for SR is configured per BWP. For positioning measurement gap activation / deactivation request, a dedicated SR configuration is configured.

[0032] Each SR configuration corresponds to one or more logical channels and / or to SCell beam failure recovery and / or to consistent LBT failure recovery and / or to beam failure recovery of a BFD-RS set and / or to positioning measurement gap activation / deactivation request. Each logical channel, SCell beam failure recovery, beam failure recovery of a BFD-RS set and consistent LBT failure recovery, may be mapped to zero or one SR configuration, which is configured by RRC. The SR configuration of the logical channel that triggered a BSR (clause 5.4.5) or a DSR (clause 5.4.9) or the SCell beam failure recovery or the beam failure recovery of a BFD-RS set or the consistent LBT failure recovery (clause 5.21) (if such a configuration exists) or positioning measurement gap activation / deactivation request (clause 5.25) is considered as corresponding SR configuration for the triggered SR. Any SR configuration may be used for an SR triggered by Pre-emptive BSR (clause 5.4.7) or Timing Advance reporting (clause 5.4.8).

[0033] [part omitted]

[0034] As long as at least one SR is pending, the MAC entity shall for each pending SR:

[0035] 1> if the MAC entity has no valid PUCCH resource configured for the pending SR; and

[0036] 1> if there is no ongoing RACH-less LTM cell switch; and

[0037] 1> if rach-LessHO is not configured:

[0038] 2> initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel the pending SR.

[0039] 1> else, for the SR configuration corresponding to the pending SR:

[0040] 2> when the MAC entity has an SR transmission occasion on the valid PUCCH resource for SR configured; and

[0041] 2> if sr-ProhibitTimer is not running at the time of the SR transmission occasion; and

[0042] 2> if the PUCCH resource for the SR transmission occasion does not overlap with a measurement gap:

[0043] [part omitted]

[0044] 3> if an SL-PRS resource overlaps with the PUCCH resource for the SR transmission occasion for the pending SR triggered as specified in clause 5.22.1.5, and the MAC entity is not able to perform this SR transmission simultaneously with the transmission of the SL-PRS resource, and the priority of the triggered SR determined as specified in clause 5.22.1.5 is higher than the priority of the MAC PDU and SL-PRS, if available, determined as specified in clause 5.22.1.3. la for the SL-PRS resource:

[0045] 4> consider the SR transmission as a prioritized SR transmission.

[0046] 4> consider the other overlapping uplink grant(s), if any, as a de-prioritized uplink grant(s), except for the overlapping uplink grant(s) whose simultaneous transmission is allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCH group or simultaneousSR-PUSCH-diffPUCCH-Groups or simultaneousPUCCH-PUSCH-SamePriority or simultaneousP U CCH -P USCH -SamePriority-SecondaryP U ( '( '[[group'.

[0047] 4> if the de-prioritized uplink grant(s) is a configured uplink grant configured with autonomousTx whose PUSCH has already started: 5> stop the configuredGrantTimer for the corresponding HARQ process of the de-prioritized uplink grant(s);

[0048] 5> stop the cg-RetransmissionTimer for the corresponding HARQ process of the de-prioritized uplink grant(s).

[0049] 4> if SR COUNTER < sr-TransMax:

[0050] 5> instruct the physical layer to signal the SR on one valid PUCCH resource for SR;

[0051] 5> if LBT failure indication is not received from lower layers:

[0052] 6> increment SR CO UNTER by 1;

[0053] 6> start the sr-ProhibitTimer.

[0054] 5> else if Ibt-FailureRecoveryConfig is not configured:

[0055] 6> increment SR CO UNTER by 1.

[0056] 4> else:

[0057] 5> notify RRC to release PUCCH for all Serving Cells;

[0058] 5> notify RRC to release SRS for all Serving Cells;

[0059] 5> clear any configured downlink assignments and uplink grants;

[0060] 5> clear any PUSCH resources for semi-persistent CSI reporting;

[0061] 5> if rach-LessHO is not configured and if there is no ongoing RACH-less LTM cell switch:

[0062] 6> initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel all pending SRs.

[0063] 3> else:

[0064] 4> consider the SR transmission as a de-prioritized SR transmission.

[0065] ***** END EXCERPT FROM 3GPP TS 38.321 *****

[0066] SUMMARY

[0067] Systems and methods are disclosed that relate to uplink failure handling for SubBand Full Duplex (SBFD) operation. In one embodiment, a method performed by a User Equipment (UE) comprises receiving, from a network node, information that configures the UE for Physical Uplink Control Channel (PUCCH) Scheduling Request (SR) transmission on SBFD slots or symbols and non-SBFD slots or symbols and separately monitoring PUCCH SR transmissions for SBFD slots or symbols and non-SBFD slots or symbols. In this manner, efficient uplink failure monitoring and recovery is enabled. Further, triggering of radio link failure and Radio Resource Control (RRC) connection reestablishment if the UE only detects uplink failures for one specific resource type (SBFD or non-SBFD) can be avoided. In one embodiment, receiving the information that configures the UE for PUCCH SR transmission on SBFD slots or symbols and non-SBFD slots or symbols comprises receiving a first PUCCH SR configuration that indicates one or more first PUCCH SR resources and is applicable for SBFD slots or symbols and receiving a second PUCCH SR configuration that indicates one or more second PUCCH SR resources and is applicable for non-SBFD slots or symbols, the second PUCCH SR configuration being separate from the first PUCCH SR configuration. In one embodiment, the method further comprises transmitting one or more first PUCCH SR transmissions on the one or more first PUCCH SR resources in SBFD slots or symbols, in accordance with the first PUCCH SR configuration and transmitting one or more second PUCCH SR transmissions on the one or more second PUCCH SR resources in non-SBFD slots or symbols, in accordance with the second PUCCH SR configuration, wherein separately monitoring PUCCH SR transmissions for SBFD slots or symbols and non-SBFD slots or symbols comprises separately monitoring the first PUCCH SR transmissions transmitted in SFBD slots or symbols and the second PUCCH SR transmissions transmitted in non-SBFD slots or symbols.

[0068] In one embodiment, receiving the information that configures the UE for PUCCH SR transmission on SBFD slots or symbols and non-SBFD slots or symbols comprises receiving a common PUCCH SR configuration that indicates one or more PUCCH SR resources applicable for both SBFD slots or symbols and non-SBFD slots or symbols. In one embodiment, the method further comprises transmitting one or more first PUCCH SR transmissions in SBFD slots or symbols, in accordance with the common PUCCH SR configuration and transmitting one or more second PUCCH SR transmissions in non-SBFD slots or symbols, in accordance with the common PUCCH SR configuration, wherein separately monitoring PUCCH SR transmissions for SBFD slots or symbols and non-SBFD slots or symbols comprises separately monitoring the first PUCCH SR transmissions transmitted in SBFD slots or symbols and the second PUCCH SR transmissions transmitted in non-SBFD slots or symbols.

[0069] In one embodiment, the UE maps the PUCCH SR configuration or the PUCCH SR resources applicable to SBFD slots or symbols to one or more logical channels associated with a first latency requirement and maps the PUCCH SR configuration or the PUCCH SR resources applicable to non-SBFD slots or symbols to one or more logical channel associated with a second latency requirement, the second latency requirement being more relaxed than the first latency requirement.

[0070] In one embodiment, separately monitoring PUCCH SR transmissions for SBFD slots or symbols and non-SBFD slots or symbols comprises maintaining a first counter for PUCCH SR transmissions transmitted during SBFD slots or symbols and maintaining a second counter for PUCCH SR transmissions transmitted during non-SBFD slots or symbols.

[0071] In one embodiment, the method further comprises determining that the first counter for PUCCH SR transmissions transmitted during SBFD slots or symbols has reached a configured maximum threshold number of PUCCH SR transmissions and, in response thereto, triggering one or more failure recovery actions. In one embodiment, the one or more failure recovery actions comprises any one or more of the following: notifying an upper layer to release PUCCH and SR resources assigned for SBFD symbols, clearing uplink grants or PUSCH resources assigned for SBFD symbols, and initiating a random access procedure on a special cell (SpCell) using Random Access Channel (RACH) resources which are allowed or assigned to be used for random access operation in SBFD symbols. In another embodiment, the one or more failure recovery actions comprises initiating a random access procedure, wherein the UE includes an indicator in the random access procedure that indicates that the maximum number of PUCCH SR transmissions for SBFD symbols has been reached.

[0072] In another embodiment, the method further comprises determining that the second counter for PUCCH SR transmissions transmitted during non-SBFD slots or symbols has reached a configured maximum threshold number of PUCCH SR transmissions and, in response thereto, triggering one or more failure recovery actions. In one embodiment, the one or more failure recovery actions comprises any one or more of the following: notifying an upper layer to release PUCCH and SR resources assigned for non-SBFD symbols, clearing uplink grants or PUSCH resources assigned for non-SBFD symbols, and initiating a random access procedure on a SpCell using RACH resources which are allowed / assigned to be used for random access operation in non- SBFD symbols. In another embodiment, the one or more failure recovery actions comprises initiating a random access procedure, wherein the UE includes an indicator in the random access procedure that indicates that the maximum number of PUCCH SR transmissions for non-SBFD symbols has been reached.

[0073] In another embodiment, the method further comprises determining that the first counter for PUCCH SR transmissions transmitted during SBFD slots or symbols has reached a configured maximum threshold number of PUCCH SR transmissions and, in response thereto, using PUCCH SR resources configured for non-SBFD slots or symbols for one or more additional PUCCH SR transmissions.

[0074] In another embodiment, the method further comprises determining that the second counter for PUCCH SR transmissions transmitted during non-SBFD slots or symbols has reached a configured maximum threshold number of PUCCH SR transmissions and, in response thereto, using PUCCH SR resources configured for SBFD slots or symbols for one or more additional PUCCH SR transmissions.

[0075] Corresponding embodiments of a UE are also disclosed. In one embodiment, a UE comprises a communication interface comprising a transmitter and a receiver, and processing circuitry associated with the communication interface. The processing circuitry is configured to cause the UE to receive, from a network node, information that configures the UE for PUCCH SR transmission on SBFD slots or symbols and non-SBFD slots or symbols and separately monitor PUCCH SR transmissions for SBFD slots or symbols and non-SBFD slots or symbols.

[0076] In another embodiment, a method performed by a UE comprises separately monitoring uplink failure instances for SBFD slots or symbols and non-SBFD slots or symbols and performing one or more actions based on results of separately monitoring uplink failure instances for SBFD slots or symbols and non-SBFD slots or symbols.

[0077] In one embodiment, performing the one or more actions comprises, based on the separate monitoring, detecting a random access problem caused by SBFD slots or symbols or associated SBFD operation and, in response thereto, either: declaring a SBFD specific radio link failure and refraining from triggering Radio Resource Control (RRC) connection reestablishment or refraining from declaring a radio link failure.

[0078] In another embodiment, performing the one or more actions comprises, based on the separate monitoring, detecting a random access problem caused by non-SBFD slots or symbols or associated non-SBFD operation and, in response thereto, either: declaring a non-SBFD specific radio link failure and refraining from triggering RRC connection reestablishment or refraining from declaring a radio link failure.

[0079] In another embodiment, performing the one or more actions comprises, based on the separate monitoring, detecting a random problem caused by both SBFD slots or symbols or associated SBFD operation and non-SBFD slots or symbols or associated non-SBFD operation and, in response thereto, declaring a radio link failure.

[0080] In one embodiment, the uplink failure instances are failed random access transmissions.

[0081] Corresponding embodiments of a UE are also disclosed. In one embodiment, a UE comprises a communication interface comprising a transmitter and a receiver, and processing circuitry associated with the communication interface. The processing circuitry is configured to cause the UE to separately monitor uplink failure instances for SBFD slots or symbols and non- SBFD slots or symbols and perform one or more actions based on results of separately monitoring uplink failure instances for SBFD slots or symbols and non-SBFD slots or symbols. Embodiments of a method performed by a network node are also disclosed. In one embodiment, a method performed by a network node comprises transmitting, to a UE, information that configures the UE for PUCCH SR transmission on SBFD slots or symbols and non-SBFD slots or symbols.

[0082] In one embodiment, transmitting the information that configures the UE for PUCCH SR transmission on SBFD slots or symbols and non-SBFD slots or symbols comprises transmitting, to the UE, a first PUCCH SR configuration that indicates one or more first PUCCH SR resources and is applicable for SBFD slots or symbols and transmitting, to the UE, a second PUCCH SR configuration that indicates one or more second PUCCH SR resources and is applicable for non- SBFD slots or symbols, the second PUCCH SR configuration being separate from the first PUCCH SR configuration.

[0083] In one embodiment, transmitting the information that configures the UE for PUCCH SR transmission on SBFD slots or symbols and non-SBFD slots or symbols comprises transmitting, to the UE, a common PUCCH SR configuration that indicates one or more PUCCH SR resources applicable for both SBFD slots or symbols and non-SBFD slots or symbols.

[0084] Corresponding embodiments of a network node are also disclosed. In one embodiment, a network node comprises processing circuitry configured to cause the network node to transmit, to a UE, information that configures the UE for PUCCH SR transmission on SBFD slots or symbols and non-SBFD slots or symbols.

[0085] In another embodiment, a method performed by a network node comprises receiving, from a UE during a random access procedure, an indication that indicates that an associated failure is detected for SBFD resources, non-SBFD resources, or both SBFD resources and non-SBFD resources and performing one or more actions based on the received indication.

[0086] In one embodiment, the indication indicates that the failure is detected for SBFD resources, and performing the one or more actions comprises allocating one or more Physical Uplink Shared Channel (PUSCH) resources or one or more PUSCH grants within one or more uplink subbands of one or more SBFD symbols.

[0087] In one embodiment, the indication indicates that the failure is detected for non-SBFD resources, and performing the one or more actions comprises allocating one or more PUSCH resources or one or more PUSCH grants on one or more non-SBFD uplink or flexible symbols within a full carrier bandwidth of an associated carrier.

[0088] In one embodiment, the indication indicates that the failure is detected for SBFD resources, and performing the one or more actions comprises assigning one or more PUCCH resources for SBFD operation or SBFD symbols. In one embodiment, the indication indicates that the failure is detected for non-SBFD resources, and performing the one or more actions comprises assigning one or more PUCCH resources for non-SBFD operation or non-SBFD symbols.

[0089] Corresponding embodiments of a network node are also disclosed. In one embodiment, a network node comprises processing circuitry configured to cause the network node to receive, from a UE during a random access procedure, an indication that indicates that an associated failure is detected for SBFD resources, non-SBFD resources, or both SBFD resources and non-SBFD resources and perform one or more actions based on the received indication.

[0090] BRIEF DESCRIPTION OF THE DRAWINGS

[0091] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0092] Figure 1 illustrates Frequency Division Duplexing (FDD), Half-Duplex FDD, and Time Division Duplexing (TDD) in a cellular system.

[0093] Figure 2 shows an exemplary TDD downlink (DL) / uplink (UL) pattern configured by TDD-DL-UL-ConfigCommon in current 3rdGeneration Partnership (3GPP) New Radio (NR) specifications.

[0094] Figure 3 illustrates conventional TDD carrier and TDD carrier system.

[0095] Figure 4 illustrates a SubBand Full Duplex (SBFD) carrier and SBFD carrier system.

[0096] Figure 5 illustrates a process performed by a User Equipment (UE) and a network node related to Physical Uplink Control Channel (PUCCH) configuration and failure handling in a system having both SBFD slots / symbols and non-SBFD slots / symbols, in accordance with embodiments of the present disclosure.

[0097] Figure 6 is a flow chart that illustrates the operation of a network node, in accordance with an exemplary embodiment of the present disclosure.

[0098] Figure 7 is a flow chart that illustrates the operation of a UE for Radio Link Failure (RLF) handling triggered by a Random Access Channel (RACH) problem, in accordance with some other embodiments of the present disclosure.

[0099] Figure 8 is a flow chart that illustrates the operation of a UE related to detection and handling of physical layer problems, in accordance with some other embodiments of the present disclosure.

[0100] Figure 9 shows an example of a communication system in accordance with some embodiments. Figure 10 shows a UE in accordance with some embodiments.

[0101] Figure 11 shows a network node in accordance with some embodiments.

[0102] Figure 12 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

[0103] DETAILED DESCRIPTION

[0104] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0105] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0106] There currently exist certain challenge(s). For the SubBand Full Duplex (SBFD) Work Item (WI) in 3rdGeneration Partnership Project (3GPP) Release (Rel)-19, an SBFD aware User Equipment (UE) in a cell capable of SBFD operation would be able to perform uplink (UL) transmissions in both non-SBFD symbols (e.g., configured as UL or flexible by TDD-DL-UL common) and SBFD slots / symbols (i.e., configured as downlink (DL) by TDD-DL-UL common). The UE performing UL transmissions using UL subbands during SBFD symbols may cause Cross Link Interference (CLI) to other UEs which perform DL reception at the same time. It is expected that the UE may experience different interference level between SBFD symbols and non-SBFD symbols.

[0107] In the Medium Access Control (MAC) layer, multiple failure handling mechanisms have been supported, including Physical Uplink Control Channel (PUCCH) Scheduling Request (SR) failure handling and Random Access Channel (RACH) problem handling.

[0108] In regard to PUCCH SR failure handling, as described in the section of the Background above entitled “Scheduling Request”, when the MAC layer has pending SRs and the number of SR transmission attempts, i.e., SR COUNTER, has reached sr -TransMax, the MAC layer declares SR failure, and performs the following actions as specified in Section 5.4.4 of 3GPP Technical Specification (TS) 38.321 V18.2.0:

[0109] 5> notify RRC to release PUCCH for all Serving Cells;

[0110] 5> notify RRC to release SRS for all Serving Cells; 5> clear any configured downlink assignments and uplink grants;

[0111] 5> clear any PUSCH resources for semi-persistent CSI reporting;

[0112] 5> if rach-LessHO is not configured and if there is no ongoing RACH-less LTM cell switch:

[0113] 6> initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel all pending SRs.

[0114] In regarding to RACH problem handling, when the MAC layer has transmitted Physical Random Access Channel (PRACH) preambles up to a maximum number, i.e., PREAMBLE TRANSMISSION COUNTER = preambleTransMax + 1, the MAC layer indicates a random access problem to upper layers (i.e., the Radio Resource Control (RRC) layer). The upper layer may further declare Radio Link Failure (RLF) and triggers RRC connection reestablishment.

[0115] For any one of the above failure handling mechanisms, it is unclear on whether the MAC entity needs to treat SBFD failure instances and non-SBFD failure instances separately. Therefore, there is a need to study the above issues and develop corresponding solutions.

[0116] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Embodiments of the solution(s) disclosed herein may include any one or more of the following aspects:

[0117] • UL failures (e.g., PUCCH SR, RACH) are monitored for SBFD operation (i.e., for SBFD symbols) and non-SBFD operation (i.e., for non-SBFD symbols) separately.

[0118] • The UE may indicate UL failures to a network node (e.g., the gNB) for SBFD operation and non-SBFD operation separately.

[0119] • The UE may fallback between SBFD resources and non-SBFD resources, if the UE has detected failures or congestion for one chosen resource type.

[0120] • The UE may switch between different fallback options based on a configuration (e.g., the network configures the wanted UE behavior).

[0121] • Upon reception of failure events on a specific resource type / operation (e.g., SBFD operation or SBFD resources), the network node (e.g., gNB) assigns or reconfigures new resources as indicated to the UE (e.g., the gNB assigns new SBFD resources to the UE if the UE has indicated UL failures for SBFD resources, vice versa, the gNB assigns new non-SBFD resources to the UE if the UE has indicated UL failures for non-SBFD resources).

[0122] • The UE may skip triggering of a RLF (and RRC connection reestablishment) if the UE has only detected UL failures for either SBFD resources or non-SBFD resources. Certain embodiments may provide one or more of the following technical advantage(s). Embodiments of the proposed solutions may provide either or both of the following advantages:

[0123] • More efficient UL failure monitoring and recovery.

[0124] • Avoid triggering of RLF and RRC connection reestablishment if the UE only detects UL failures for one specific resource type (SBFD resources or non-SBFD resources) rather than both resource types (SBFD resources and non-SBFD resources).

[0125] Note that, as used herein, the term “SBFD aware UE” means a UE which is capable of operating in a cell configured with SBFD feature, i.e., the cell / the network node (e.g., gNB) controlling the cell transmits DL and receives UL simultaneously in SBFD slots and symbols. The UE can be aware of SBFD configurations so that the UE knows which slots and / or symbols are SBFD capable, which are also referred to as SBFD slots / symbols. This does not mean that the UE needs to support full duplex operation. The UE may or may not support full duplex operation.

[0126] The embodiments described below are applicable to SBFD aware UEs.

[0127] First, a number of embodiments related to PUCCH configuration and failure handling will be described. These embodiments are described with respect to Figure 5, which illustrates a process performed by a UE 500 and a network node 502 (e.g., a RAN node such as, e.g., a gNB), in accordance with some embodiments of the present disclosure. Optional steps are represented by dashed boxes.

[0128] As illustrated in Figure 5, the UE 500 receives, from the network node 502, information that configures the UE 500 for PUCCH SR transmission (with PUCCH SR resources) on SBFD slots and / or symbols (“SBFD slots / symbols”) and non-SBFD slots and / or symbols (“non-SBFD slots / symbols”) (step 504).

[0129] In a first embodiment, the UE 500 is configured in step 504 with at least one PUCCH SR configuration for SBFD symbols / slots, and at least one different PUCCH SR configuration for non-SBFD symbols / slots, where each PUCCH SR configuration indicates configurations (i.e., settings) for one or multiple PUCCH SR resources. The UE then uses different PUCCH SR configurations (and the corresponding resources) to transmit SR in SBFD symbols and non-SBFD symbols (steps 506 and 508).

[0130] In a second embodiment, the UE is configured in step 504 with at least one common PUCCH SR configuration which is applicable for both SBFD symbols and non-SBFD symbols. In this common PUCCH SR configuration, at least one PUCCH SR resource is configured for operation in SBFD symbols, and one separate PUCCH SR resource is configured for operation in non SBFD symbols. As an additional embodiment, the UE maps PUCCH SR configurations (and / or the corresponding resources) associated with SBFD symbols (or SBFD operation) to Logical Channels (LCHs) associated with strict latency requirements.

[0131] As an additional embodiment, the UE maps PUCCH SR configurations (and / or the corresponding resources) associated with non-SBFD symbols (or SBFD operation) to LCHs associated with relaxed latency requirements.

[0132] In this case, upon arrival of new data for a LCH, the UE may trigger an SR, after that, the UE transmits the SR using PUCCH SR resources / configurations associated with the LCH.

[0133] In a third embodiment, the UE monitors PUCCH SR transmission instances separately for SBFD operation and non-SBFD operation (step 510) and optionally performs one or more actions based on results of this monitoring (step 512).

[0134] In one example of the third embodiment, the UE maintains separate counters for PUCCH SR transmission instances during SBFD symbols and non-SBFD symbols and compares these separate counters to the same or different counter thresholds (maximum number of PUCHH SR transmission threshold(s)) (steps 510A and 51 OB). When either of the counters reaches a configured maximum number, e.g., configured by RRC parameter sr-TransMax, the UE considers the corresponding PUCCH resources / configurations invalid, and triggers at least one of the below failure recovery actions (step 512A):

[0135] • notify RRC to release the corresponding PUCCH for all Serving Cells;

[0136] • notify RRC to release the corresponding Sounding Reference Signal (SRS) for all Serving Cells;

[0137] • clear any configured downlink assignments and corresponding uplink grants;

[0138] • clear any corresponding PUSCH resources for semi-persistent Channel State Information (CSI) reporting;

[0139] • initiate a Random Access procedure on the Special Cell (SpCell) using corresponding RACH resources and cancel all corresponding pending SRs.

[0140] In one embodiment, when the maximum PUCCH transmission attempts are reached for SBFD symbols, in step 512, the UE notifies RRC to release PUCCH and SR resources assigned for SBFD symbols. In addition, the UE may clear uplink grants or PUSCH resources assigned for SBFD symbols. In addition, the UE may initiate a random access procedure on the SpCell using RACH resources which are allowed / assigned to be used for RA operation in SBFD symbols. In one embodiment, when the maximum PUCCH transmission attempts are reached for non SBFD symbols, in step 512, the UE notifies RRC to release PUCCH and SR resources assigned for non SBFD symbols. In addition, the UE may clear uplink grants or PUSCH resources assigned for non SBFD symbols, in addition, the UE may initiate a random access procedure on the SpCell using RACH resources which are allowed / assigned to be used for RA operation in non SBFD symbols.

[0141] As an additional embodiment, an indicator may be included in the RACH procedure indicating that the failure (i.e., the maximum PUCCH SR transmission attempts has been reached) is detected for SBFD symbols, for non-SBFD symbols, or for both SBFD and non-SBFD symbols. The indicator may be included in, for example, a MAC subheader or a MAC Control Element (CE). The MAC CE may be a new MAC CE named as, for example, “PUCCH SR failure indicator MAC CE”.

[0142] As an additional embodiment, upon reception of the RACH transmission, the network node (e.g., gNB) may further trigger one of the below actions:

[0143] 1) allocate PUSCH resources / grants for the operation as indicated. a. If the indication is associated with SBFD operation, the gNB assigns PUSCH resources / grants within UL subbands of SBFD symbols (i.e., which is configured for UL transmissions during SBFD symbols) b. If the indication is associated with non-SBFD operation, the gNB assigns PUSCH resources / grants on non-SBFD UL / F symbols within the full carrier.

[0144] 2) Allocate PUCCH resources for the operation as indicated. a. If the indication is associated with SBFD operation, the gNB assigns PUCCH resources for SBFD operation / symbols b. If the indication is associated with non SBFD operation, the gNB assigns PUCCH resources for non SBFD operation / symbols.

[0145] This is illustrated in the flowchart of Figure 6, which illustrates the operation of a network node in accordance with one example embodiment. As illustrated, the network node (e.g., gNB) receives, from the UE during a random access procedure (e.g., in a RACH transmission), an indication (e.g., explicit indication or implicit indication) that an associated failure was detected on SBFD resource(s), a non-SBFD resource(s), or both SBFD resource(s) and non-SBFD resource(s) (step 600). The network node then performs one or more actions based on the received indication (step 602). Examples of such actions are described above in regard to allocating PUSCH resources / grants and allocation of PUCCH resources, based on the received indication. Returning to Figure 5, in a fourth embodiment, a fallback mechanism is introduced for the UE when performing PUCCH SR resource selection.

[0146] In an example, when the UE has reached the maximum number of SR transmissions for SBFD symbols, instead of triggering any failure recovery action as described in the third embodiment, the UE falls back to PUCCH SR resources configured for non-SBFD symbols (step 512B). In other words, the UE continues to transmit the SR using PUCCH SR resources configured for non-SBFD symbols instead. In this case, if the SR transmission during SBFD symbols cannot get through, the UE still has the possibility to transmit the SR in non-SBFD symbols.

[0147] In an example, when the UE has reached the maximum number of SR transmissions for non-SBFD symbols, instead of triggering any failure recovery action as described in the third embodiment, the UE falls back to PUCCH SR resources configured for SBFD symbols (step 512B). In other words, the UE continues to transmit the SR using PUCCH SR resources configured for SBFD symbols instead. In this case, if the SR transmission during non-SBFD symbols cannot get through, the UE still has possibility to transmit the SR in SBFD symbols.

[0148] In both of these examples, the UE only perform failure recovery actions (as described in the third embodiment) when the UE has reached the maximum number of SR transmissions for both SBFD operation / symbols and non SBFD operation / symbols.

[0149] Now, embodiments related to RLF handling triggering by a RACH problem will be described. These embodiments are illustrated by Figure 7, which is a flow chart that illustrates the operation of a UE, in accordance with some embodiments of the present disclosure. Optional steps are represented by dashed lines.

[0150] In one embodiment, the UE monitors UL failure instances (e.g., RACH transmissions) separately (e.g., separately for SBFD symbols and non-SBFD symbols) for RLF handling (step 702). The UE performs one or more actions based on results of the separate monitoring (step 704).

[0151] In one example, when the UE detects a RACH problem caused by SBFD symbols / operations via the monitoring of step 702 (step 705, YES), the UE may then, in step 704, apply one of the below options:

[0152] • Option 1 : declare SBFD specific RLF, and not further trigger RRC connection reestablishment (step 706), or

[0153] • Option 2: not declare RLF (step 706).

[0154] In one example, when the UE detects a RACH problem caused by non-SBFD symbols / operations via the monitoring of step 702 (step 708, YES), the UE may then, in step 704, apply one of the below options • Option 1 : declare non-SBFD operation specific RLF, and not further trigger RRC connection reestablishment (step 710), or

[0155] • Option 2: not declare RLF (step 710).

[0156] In one example, the UE declares RLF only when the UE has detected both RA problem for SBFD operation and RA problem for non SBFD operation (steps 712, YES and step 714).

[0157] Now, embodiments related to physical layer problems and handling will be described. Figure 8 is a flow chart that illustrates the operation of a UE in accordance with at least some of these embodiments. Optional steps are represented by dashed boxes. As illustrated, the UE optionally selects either SBFD slots / symbols, non-SBFD slots / symbols, or both SBFD slots / symbols and non-SBFD slots / symbols, for monitoring (step 801). The UE monitors for physical layer problems on either SBFD slots / symbols, non-SBFD slots / symbols, or both SBFD slots / symbols and non-SBFD slots / symbols (step 802). In step 802, in one embodiment, the monitored slots / symbols are those selected in step 801. The UE then performs one or more actions based on results of the monitoring (step 804).

[0158] In one embodiment, in step 802, the UE considers a subset of the resources available to the UE when determining if physical layer problems occur. For example, the UE may consider only non-SBFD resources but not SBFD resources. The UE may in this case declared RLF (in step 804) in response to detecting physical layer problems on the non-SBFD resources but not declare RLF even if there are physical layer problems on the SBFD resource (and it may be the case with this embodiment that the UE does not even monitor for physical layer problems on the SBFD resources). In another example, the UE may consider only SBFD resources, but not non SBFD resources.

[0159] As an additional embodiment, the UE determines, in step 801, to monitor a subset of the resources for detecting RLF purpose, depending on whether the UE mainly uses the subset of the resources (for UL transmissions) in the recent transmissions. If the UE mainly uses SBFD resources recently, the UE therefore, considers only SBFD resources for RLF detection purpose. If the UE mainly uses non SBFD resources recently, the UE may consider only non SBFD resources for RLF detection purpose. If the UE uses both SBFD resources and non SBFD resources recently, the UE may consider both SBFD resources and non SBFD resources for RLF detection purpose. Here, the UE may consider that it mainly uses SBFD resources recently using any suitable criteria such as the following: if, for a predefined or configured amount of time (defined in terms of, e.g., milliseconds, slots, symbols, or the like) prior to the current time, the UE has used more SBFD resources than non-SBFD resources (otherwise the UE may determine that it mainly uses non-SBFD resources recently). In a version of this embodiment, in step 802, the UE monitors for physical layer problems on both resources but the UE declares RLF (in step 804) only in response to problems with one of these resources. If physical layer problems are detected on the other set of resources, the UE may instead send an indication to the network saying that the UE has detected physical layer problems on the problematic resources.

[0160] In one embodiment, the UE considers both SBFD and non-SBFD resources for the monitoring of step 802, but the UE will independently monitor for physical layer problems on these resources, i.e. the UE will consider the SBFD resources and monitor for physical layer problems on those resources and independently the UE monitors for physical layer problems on the non-SBFD resources. In one version of this embodiment, the UE declares RLF (in step 804) in response to that physical layer problems are detected on any of these resources, in another version of this embodiment the UE declares RLF in response to that physical layer problems are detected on both these resources.

[0161] The UE may consider different parameters for detecting physical layer problems on different resources, e.g. the UE may consider a first set of parameters for detecting physical layer problems on the SBFD resources and a second set of parameters detecting physical layer problems on the non-SBFD resources.

[0162] In the above embodiments, for RLF monitoring purpose, the UE may monitor DL resources (e.g., Channel State Information Reference Signal (CSLRS), or Synchronization Signal (SS) / Physical Broadcast Channel (PBCH)) and / or UL resources (e.g., SRS, PUCCH). DL SBFD resources refer to the DL resources allocated confined to the DL subbands during SBFD symbols. DL non-SBFD resources refer to the DL resources during non SBFD symbols, which may be located in any region of DL carrier. Similarly, UL SBFD resources refer to the UL resources allocated confined to the UL subbands during SBFD symbols. UL non SBFD resources refer to the UL resources during non SBFD symbols, which may be located in any region of UL carrier.

[0163] Figure 9 shows an example of a communication system 900 in accordance with some embodiments.

[0164] In the example, the communication system 900 includes a telecommunication network 902 that includes an access network 904, such as a Radio Access Network (RAN), and a core network 906, which includes one or more core network nodes 908. The access network 904 includes one or more access network nodes, such as network nodes 910A and 910B (one or more of which may be generally referred to as network nodes 910), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP Access Points (APs). Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 902 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 902 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 902, including one or more network nodes 910 and / or core network nodes 908.

[0165] Examples of an ORAN network node include an Open Radio Unit (O-RU), an Open Distributed Unit (O-DU), an Open Central Unit (O-CU), including an O-CU Control Plane (O- CU-CP) or an O-CU User Plane (O-CU-UP), a RAN intelligent controller (near-real time or non- real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 910 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 912A, 912B, 912C, and 912D (one or more of which may be generally referred to as UEs 912) to the core network 906 over one or more wireless connections.

[0166] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 900 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 900 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system. The UEs 912 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 910 and other communication devices. Similarly, the network nodes 910 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 912 and / or with other network nodes or equipment in the telecommunication network 902 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 902.

[0167] In the depicted example, the core network 906 connects the network nodes 910 to one or more hosts, such as host 916. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 906 includes one more core network nodes (e.g., core network node 908) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 908. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-Concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0168] The host 916 may be under the ownership or control of a service provider other than an operator or provider of the access network 904 and / or the telecommunication network 902, and may be operated by the service provider or on behalf of the service provider. The host 916 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0169] As a whole, the communication system 900 of Figure 9 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 900 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.

[0170] In some examples, the telecommunication network 902 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunication network 902 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 902. For example, the telecommunication network 902 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs, and / or massive Machine Type Communication (mMTC) / massive Internet of Things (loT) services to yet further UEs.

[0171] In some examples, the UEs 912 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 904 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 904. Additionally, a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi -standard mode. For example, a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. being configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).

[0172] In the example, a hub 914 communicates with the access network 904 to facilitate indirect communication between one or more UEs (e.g., UE 912C and / or 912D) and network nodes (e.g., network node 910B). In some examples, the hub 914 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 914 may be a broadband router enabling access to the core network 906 for the UEs. As another example, the hub 914 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 910, or by executable code, script, process, or other instructions in the hub 914. As another example, the hub 914 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 914 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 914 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 914 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 914 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0173] The hub 914 may have a constant / persistent or intermittent connection to the network node 910B. The hub 914 may also allow for a different communication scheme and / or schedule between the hub 914 and UEs (e.g., UE 912C and / or 912D), and between the hub 914 and the core network 906. In other examples, the hub 914 is connected to the core network 906 and / or one or more UEs via a wired connection. Moreover, the hub 914 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 904 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 910 while still connected via the hub 914 via a wired or wireless connection. In some embodiments, the hub 914 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 910B. In other embodiments, the hub 914 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and the network node 910B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0174] Figure 10 shows a UE 1000 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged, and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, Voice over Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), smart device, wireless Customer Premise Equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3 GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0175] A UE may support Device-to-Device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle-to-Everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0176] The UE 1000 includes processing circuitry 1002 that is operatively coupled via a bus 1004 to an input / output interface 1006, a power source 1008, memory 1010, a communication interface 1012, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 10. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0177] The processing circuitry 1002 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1010. The processing circuitry 1002 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1002 may include multiple Central Processing Units (CPUs).

[0178] In the example, the input / output interface 1006 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1000. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0179] In some embodiments, the power source 1008 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 1008 may further include power circuitry for delivering power from the power source 1008 itself, and / or an external power source, to the various parts of the UE 1000 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1008. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1008 to make the power suitable for the respective components of the UE 1000 to which power is supplied.

[0180] The memory 1010 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1010 includes one or more application programs 1014, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1016. The memory 1010 may store, for use by the UE 1000, any of a variety of various operating systems or combinations of operating systems.

[0181] The memory 1010 may be configured to include a number of physical drive units, such as Redundant Array of Independent Disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High Density Digital Versatile Disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, Holographic Digital Data Storage (HDDS) optical disc drive, external mini Dual In-line Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and / or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’ The memory 1010 may allow the UE 1000 to access instructions, application programs, and the like stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system, may be tangibly embodied as or in the memory 1010, which may be or comprise a device-readable storage medium.

[0182] The processing circuitry 1002 may be configured to communicate with an access network or other network using the communication interface 1012. The communication interface 1012 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1022. The communication interface 1012 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1018 and / or a receiver 1020 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1018 and receiver 1020 may be coupled to one or more antennas (e.g., the antenna 1022) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0183] In the illustrated embodiment, communication functions of the communication interface 1012 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, NFC, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.

[0184] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1012, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected, an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0185] As another example, a UE comprises an actuator, a motor, or a switch related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0186] A UE, when in the form of an loT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application, and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1000 shown in Figure 10.

[0187] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3 GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0188] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator and handle communication of data for both the speed sensor and the actuators.

[0189] Figure 11 shows a network node 1100 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged, and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment in a telecommunication network. Examples of network nodes include, but are not limited to, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), NR Node Bs (gNBs)), and 0-RAN nodes or components of an 0-RAN node (e.g., 0-RU, 0-DU, O-CU).

[0190] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an 0-RAN access node), and / or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a Distributed Antenna System (DAS).

[0191] Other examples of network nodes include multiple Transmission Point (multi-TRP) 5G access nodes, Multi -Standard Radio (MSR) equipment such as MSR BSs, network controllers such as Radio Network Controllers (RNCs) or BS Controllers (BSCs), Base Transceiver Stations (BTSs), transmission points, transmission nodes, Multi-Cell / Multicast Coordination Entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0192] The network node 1100 includes processing circuitry 1102, memory 1104, a communication interface 1106, and a power source 1108. The network node 1100 may be composed of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1100 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may in some instances be considered a single separate network node. In some embodiments, the network node 1100 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 1104 for different RATs) and some components may be reused (e.g., a same antenna 1110 may be shared by different RATs). The network node 1100 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1100, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within the network node 1100.

[0193] The processing circuitry 1102 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic operable to provide, either alone or in conjunction with other network node 1100 components, such as the memory 1104, to provide network node 1100 functionality.

[0194] In some embodiments, the processing circuitry 1102 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 1102 includes one or more of Radio Frequency (RF) transceiver circuitry 1112 and baseband processing circuitry 1114. In some embodiments, the RF transceiver circuitry 1112 and the baseband processing circuitry 1114 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of the RF transceiver circuitry 1112 and the baseband processing circuitry 1114 may be on the same chip or set of chips, boards, or units.

[0195] The memory 1104 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable, and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1102. The memory 1104 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1102 and utilized by the network node 1100. The memory 1104 may be used to store any calculations made by the processing circuitry 1102 and / or any data received via the communication interface 1106. In some embodiments, the processing circuitry 1102 and the memory 1104 are integrated.

[0196] The communication interface 1106 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 1106 comprises port(s) / terminal(s) 1116 to send and receive data, for example to and from a network over a wired connection. The communication interface 1106 also includes radio front-end circuitry 1118 that may be coupled to, or in certain embodiments a part of, the antenna 1110. The radio front-end circuitry 1118 comprises filters 1120 and amplifiers 1122. The radio front-end circuitry 1118 may be connected to the antenna 1110 and the processing circuitry 1102. The radio front-end circuitry 1118 may be configured to condition signals communicated between the antenna 1110 and the processing circuitry 1102. The radio front-end circuitry 1118 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1118 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 1120 and / or the amplifiers 1122. The radio signal may then be transmitted via the antenna 1110. Similarly, when receiving data, the antenna 1110 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1118. The digital data may be passed to the processing circuitry 1102. In other embodiments, the communication interface 1106 may comprise different components and / or different combinations of components.

[0197] In certain alternative embodiments, the network node 1100 does not include separate radio front-end circuitry 1118; instead, the processing circuitry 1102 includes radio front-end circuitry and is connected to the antenna 1110. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1112 is part of the communication interface 1106. In still other embodiments, the communication interface 1106 includes the one or more ports or terminals 1116, the radio front-end circuitry 1118, and the RF transceiver circuitry 1112 as part of a radio unit (not shown), and the communication interface 1106 communicates with the baseband processing circuitry 1114, which is part of a digital unit (not shown).

[0198] The antenna 1110 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1110 may be coupled to the radio front-end circuitry 1118 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1110 is separate from the network node 1100 and connectable to the network node 1100 through an interface or port.

[0199] The antenna 1110, the communication interface 1106, and / or the processing circuitry 1102 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node 1100. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 1110, the communication interface 1106, and / or the processing circuitry 1102 may be configured to perform any transmitting operations described herein as being performed by the network node 1100. Any information, data, and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0200] The power source 1108 provides power to the various components of the network node 1100 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1108 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1100 with power for performing the functionality described herein. For example, the network node 1100 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1108. As a further example, the power source 1108 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0201] Embodiments of the network node 1100 may include additional components beyond those shown in Figure 11 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1100 may include user interface equipment to allow input of information into the network node 1100 and to allow output of information from the network node 1100. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1100. In some embodiments providing a core network node, such as core network node 108 of FIG. 9, some components, such as the radio front-end circuitry 1118 and the RF transceiver circuitry 1112 may be omitted.

[0202] Figure 12 is a block diagram illustrating a virtualization environment 1200 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices, and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more Virtual Machines (VMs) implemented in one or more virtualization environments 1200 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, a UE, a core network node, or a host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1200 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. Virtualization may facilitate distributed implementations of a network node, a UE, a core network node, or a host. Applications 1202 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1200 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0203] Hardware 1204 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, an input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1206 (also referred to as hypervisors or Virtual Machine Monitors (VMMs)), provide VMs 1208A and 1208B (one or more of which may be generally referred to as VMs 1208), and / or perform any of the functions, features, and / or benefits described in relation with some embodiments described herein. The virtualization layer 1206 may present a virtual operating platform that appears like networking hardware to the VMs 1208.

[0204] The VMs 1208 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 1206. Different embodiments of the instance of a virtual appliance 1202 may be implemented on one or more of VMs 1208, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premise equipment.

[0205] In the context of NFV, a VM 1208 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1208, and that part of the hardware 1204 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1208 on top of the hardware 1204 and corresponds to the application 1202.

[0206] The hardware 1204 may be implemented in a standalone network node with generic or specific components. The hardware 1204 may implement some functions via virtualization. Alternatively, the hardware 1204 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1210, which, among others, oversees lifecycle management of the applications 1202. In some embodiments, the hardware 1204 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1212 which may alternatively be used for communication between hardware nodes and radio units.

[0207] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non- computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0208] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0209] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

[0210] Some exemplary embodiments of the present disclosure are as follows:

[0211] Group A Embodiments

[0212] Embodiment 1 : A method performed by a User Equipment, UE, (500), the method comprising: receiving (504), from a network node (502), information that configures the UE for Physical Uplink Control Channel, PUCCH, Scheduling Request, SR, transmission on SBFD slots or symbols and non-SBFD slots or symbols; and separately monitoring (510) Physical Uplink Control Channel, PUCCH, Scheduling Request, SR, transmissions for SBFD slots or symbols and non-SBFD slots or symbols.

[0213] Embodiment 2: The method of embodiment 1, further comprising performing (512) one or more actions based on results of separately monitoring PUCCH SR transmissions for SBFD slots or symbols and non-SBFD slots or symbols.

[0214] Embodiment 3: The method of embodiment 1, wherein receiving (504) the information that configures the UE for PUCCH SR transmission on SBFD slots or symbols and non-SBFD slots or symbols comprises: receiving (504) a first PUCCH SR configuration that indicates one or more first PUCCH SR resources that is applicable for SBFD slots or symbols; and receiving (504) a second PUCCH SR configuration that indicates one or more second PUCCH SR resources that is applicable for non-SBFD slots or symbols, the second PUCCH SR configuration being separate from the first PUCCH SR configuration.

[0215] Embodiment 4: The method of embodiment 3, further comprising: transmitting (506) one or more first PUCCH SR transmissions on the one or more first PUCCH SR resources in SBFD slots or symbols, in accordance with the first PUCCH SR configuration or SR resource; and transmitting (508) one or more second PUCCH SR transmissions on the one or more second PUCCH SR resources in non-SBFD slots or symbols, in accordance with the second PUCCH SR configuration or SR resource.

[0216] Embodiment 5: The method of embodiment 4, wherein separately monitoring (510) PUCCH SR transmissions for SBFD slots or symbols and non-SBFD slots or symbols comprises separately monitoring (510) the first PUCCH SR transmissions transmitted in SFBF slots or symbols and the second PUCCH SR transmissions transmitted in non-SBFD slots or symbols. Embodiment 6: The method of embodiment 1, wherein receiving (504) the information that configures the UE for PUCCH SR transmission on SBFD slots or symbols and non-SBFD slots or symbols comprises receiving (504) a common PUCCH SR configuration that indicates one or more PUCCH SR resources applicable for both SBFD slots or symbols and non-SBFD slots or symbols.

[0217] Embodiment 7: The method of embodiment 6, further comprising: transmitting (506) one or more first PUCCH SR transmissions in SBFD slots or symbols , in accordance with the common PUCCH SR configuration; and transmitting (506) one or more second PUCCH SR transmissions in non-SBFD slots or symbols , in accordance with the common PUCCH SR configuration.

[0218] Embodiment 8: The method of embodiment 7, wherein separately monitoring (510) PUCCH SR transmissions for SBFD slots or symbols and non-SBFD slots or symbols comprises separately monitoring (510) the first PUCCH SR transmissions transmitted in SBFD slots or symbols and the second PUCCH SR transmissions transmitted in non-SBFD slots or symbols.

[0219] Embodiment 9: The method of any of embodiments 1 to 8, wherein the UE maps the PUCCH SR configuration or the PUCCH SR resources applicable to SBFD slots or symbols to one or more logical channels associated with a first latency requirement and maps the PUCCH SR configuration or the PUCCH SR resources applicable to non-SBFD slots or symbols to one or more logical channel associated with a second latency requirement, the second latency requirement being more relaxed than the first latency requirement.

[0220] Embodiment 10: The method of any of embodiments 1 to 9, wherein separately monitoring (510) PUCCH SR transmissions for SBFD slots or symbols and non-SBFD slots or symbols comprises maintaining (510A) a first counter for PUCCH SR transmissions transmitted during SBFD slots or symbols and maintaining (510B) a second counter for PUCCH SR transmissions transmitted during non-SBFD slots or symbols.

[0221] Embodiment 11 : The method of embodiment 10, further comprising: determining (510A) that the first counter for PUCCH SR transmissions transmitted during SBFD slots or symbols has reached a configured maximum threshold number of PUCCH SR transmissions; and, in response thereto, triggering (512A) one or more failure recovery actions.

[0222] Embodiment 12: The method of embodiment 11, wherein the one or more failure recovery actions comprises any one or more of the following: notifying an upper layer (e.g., RRC layer) to release PUCCH and SR resources assigned for SBFD symbols; clearing uplink grants or PUSCH resources assigned for SBFD symbols; initiating a random access procedure on a special cell, SpCell, using RACH resources which are allowed / assigned to be used for random access operation in SBFD symbols. Embodiment 13: The method of embodiment 11, wherein the one or more failure recovery actions comprises initiating a random access procedure (e.g., on a special cell, SpCell, using RACH resources which are allowed / assigned to be used for random access operation in SBFD symbols), wherein the UE includes an indicator in the random access procedure that indicates that the maximum number of PUCCH SR transmissions for SBFD symbols has been reached.

[0223] Embodiment 14: The method of embodiment 10, further comprising: determining (510B) that the second counter for PUCCH SR transmissions transmitted during non-SBFD slots or symbols has reached a configured maximum threshold number of PUCCH SR transmissions; and, in response thereto, triggering (512A) one or more failure recovery actions.

[0224] Embodiment 15: The method of embodiment 14, wherein the one or more failure recovery actions comprises any one or more of the following: notifying an upper layer (e.g., RRC layer) to release PUCCH and SR resources assigned for non-SBFD symbols; clearing uplink grants or PUSCH resources assigned for non-SBFD symbols; initiating a random access procedure on a special cell, SpCell, using RACH resources which are allowed / assigned to be used for random access operation in non-SBFD symbols.

[0225] Embodiment 16: The method of embodiment 14, wherein the one or more failure recovery actions comprises initiating a random access procedure (e.g., on a special cell, SpCell, using RACH resources which are allowed / assigned to be used for random access operation in non-SBFD symbols), wherein the UE includes an indicator in the random access procedure that indicates that the maximum number of PUCCH SR transmissions for non-SBFD symbols has been reached.

[0226] Embodiment 17: The method of embodiment 10, further comprising: determining (510A) that the first counter for PUCCH SR transmissions transmitted during SBFD slots or symbols has reached a configured maximum threshold number of PUCCH SR transmissions; and, in response thereto, using (514B) PUCCH SR resources configured for non-SBFD slots or symbols for one or more additional PUCCH SR transmissions (e.g., instead of triggering any failure recovery action).

[0227] Embodiment 18: The method of embodiment 10, further comprising: determining (51 OB) that the second counter for PUCCH SR transmissions transmitted during non-SBFD slots or symbols has reached a configured maximum threshold number of PUCCH SR transmissions; and, in response thereto, using (514B) PUCCH SR resources configured for SBFD slots or symbols for one or more additional PUCCH SR transmissions (e.g., instead of triggering any failure recovery action).

[0228] Embodiment 19: A method performed by a User Equipment, UE, the method comprising: separately monitoring (702) uplink failure instances (e.g., failed random access transmissions) for SBFD slots / symbols and non-SBFD slots / symbols; and performing (704) one or more actions based on results of separately monitoring (702) uplink failure instances for SBFD slots / symbols and non- SBFD slots / symbols.

[0229] Embodiment 20: The method of embodiment 19, further comprising: based on the separate monitoring, detecting (705, YES) a problem (e.g., a random access problem) caused by SBFD slots / symbols (or associated SBFD operation); and, in response thereto, either: declaring (706) a SBFD specific radio link failure and refraining from triggering RRC connection reestablishment or refraining (706) from declaring a radio link failure.

[0230] Embodiment 21 : The method of embodiment 19, further comprising: based on the separate monitoring, detecting (708, YES) a problem (e.g., a random access problem) caused by non-SBFD slots / symbols (or associated non-SBFD operation); and, in response thereto, either: declaring (710) a non-SBFD specific radio link failure and refraining from triggering RRC connection reestablishment or refraining (710) from declaring a radio link failure.

[0231] Embodiment 22: The method of embodiment 19, further comprising: based on the separate monitoring, detecting (712, YES) a problem (e.g., a random access problem) caused by both SBFD slots / symbols (or associated SBFD operation) and non-SBFD slots / symbols (or associated non- SBFD operation); and, in response thereto, declaring (714) a radio link failure.

[0232] Embodiment 23: A method performed by a User Equipment, UE, the method comprising: monitoring (802) either SBFD slots / symbols, non-SBFD slots / symbols, or both SBFD slots / symbols and non-SBFD slots / symbols, for physical layer problems; and performing (804) one or more actions based on results of the monitoring (802).

[0233] Embodiment 24: The method of embodiment 23, wherein the monitoring (802) comprises monitoring SBFD slots / symbols, but not non-SBFD slots / symbols, for physical layer problems.

[0234] Embodiment 25: The method of embodiment 23, wherein the monitoring (802) comprises monitoring non-SBFD slots / symbols, but not SBFD slots / symbols, for physical layer problems.

[0235] Embodiment 26: The method of embodiment 23, further comprising: selecting (801) either SBFD slots / symbols or non-SBFD slots / symbols, for monitoring for physical layer problems; wherein the monitoring (802) comprises monitoring the selected SBFD or non-SBFD slots / symbols, for physical layer problems.

[0236] Embodiment 27: The method of embodiment 23, wherein the monitoring (802) comprises monitoring both SBFD slots / symbols and non-SBFD slots / symbols, for physical layer problems.

[0237] Embodiment 28: The method of embodiment 27, further comprising declaring (804) a radio link failure in response to detection of physical layer problems on either SBFD slots / symbols or non-SBFD slots / symbols. Embodiment 29: The method of embodiment 23, wherein the monitoring (802) comprises separately (or independently) monitoring both SBFD slots / symbols and non-SBFD slots / symbols, for physical layer problems.

[0238] Group B Embodiments

[0239] Embodiment 30: A method performed by a network node (e.g., a RAN node such as, e.g., a gNB), the method comprising: transmitting (504), to a UE (500), information that configures the UE for Physical Uplink Control Channel, PUCCH, Scheduling Request, SR, transmission on SBFD slots or symbols and non-SBFD slots or symbols.

[0240] Embodiment 31 : The method of embodiment 30, wherein transmitting (504) the information that configures the UE for PUCCH SR transmission on SBFD slots or symbols and non-SBFD slots or symbols comprises: transmitting (504), to the UE, a first PUCCH SR configuration that indicates one or more first PUCCH SR resources that is applicable for SBFD slots or symbols; and transmitting (504), to the UE, a second PUCCH SR configuration that indicates one or more second PUCCH SR resources that is applicable for non-SBFD slots or symbols, the second PUCCH SR configuration being separate from the first PUCCH SR configuration.

[0241] Embodiment 32: The method of embodiment 30, wherein transmitting (504) the information that configures the UE for PUCCH SR transmission on SBFD slots or symbols and non-SBFD slots or symbols comprises transmitting (504), to the UE, a common PUCCH SR configuration that indicates one or more PUCCH SR resources applicable for both SBFD slots or symbols and non-SBFD slots or symbols.

[0242] Embodiment 33: A method performed by a network node (e.g., a RAN node such as, e.g., a gNB), the method comprising: receiving (600), from a UE during a random access procedure, an indication that indicates that an associated failure is detected for SBFD resources, non-SBFD resources, or both SBFD resources and non-SBFD resources; and performing (602) one or more actions based on the received indication.

[0243] Embodiment 34: The method of embodiment 33, wherein the indication indicates that the failure is detected for SBFD resources, and performing the one or more actions comprises allocating one or more PUSCH resources or one or more PUSCH grants within one or more uplink subbands of one or more SBFD symbols.

[0244] Embodiment 35: The method of embodiment 33, wherein the indication indicates that the failure is detected for non-SBFD resources, and performing the one or more actions comprises allocating one or more PUSCH resources or one or more PUSCH grants on one or more non-SBFD uplink or flexible symbols within a full carrier bandwidth of an associated carrier.

[0245] Embodiment 36: The method of embodiment 33, wherein the indication indicates that the failure is detected for SBFD resources, and performing the one or more actions comprises assigning one or more PUCCH resources for SBFD operation or SBFD symbols.

[0246] Embodiment 37: The method of embodiment 33, wherein the indication indicates that the failure is detected for non-SBFD resources, and performing the one or more actions comprises assigning one or more PUCCH resources for non-SBFD operation or non-SBFD symbols.

[0247] Group C Embodiments

[0248] Embodiment 38: A user equipment comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0249] Embodiment 39: A network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0250] Embodiment 40: A user equipment (UE) comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

Claims

CLAIMS1. A method performed by a User Equipment, UE, (500), the method comprising: receiving (504), from a network node (502), information that configures the UE for Physical Uplink Control Channel, PUCCH, Scheduling Request, SR, transmission on SubBand Full Duplex, SBFD, slots or symbols and non-SBFD slots or symbols; and separately monitoring (510) Physical Uplink Control Channel, PUCCH, Scheduling Request, SR, transmissions for SBFD slots or symbols and non-SBFD slots or symbols.

2. The method of claim 1, wherein receiving (504) the information that configures the UE for PUCCH SR transmission on SBFD slots or symbols and non-SBFD slots or symbols comprises: receiving (504) a first PUCCH SR configuration that indicates one or more first PUCCH SR resources and is applicable for SBFD slots or symbols; and receiving (504) a second PUCCH SR configuration that indicates one or more second PUCCH SR resources and is applicable for non-SBFD slots or symbols, the second PUCCH SR configuration being separate from the first PUCCH SR configuration.

3. The method of claim 2, further comprising: transmitting (506) one or more first PUCCH SR transmissions on the one or more first PUCCH SR resources in SBFD slots or symbols, in accordance with the first PUCCH SR configuration; transmitting (508) one or more second PUCCH SR transmissions on the one or more second PUCCH SR resources in non-SBFD slots or symbols, in accordance with the second PUCCH SR configuration; wherein separately monitoring (510) PUCCH SR transmissions for SBFD slots or symbols and non-SBFD slots or symbols comprises separately monitoring (510) the first PUCCH SR transmissions transmitted in SFBD slots or symbols and the second PUCCH SR transmissions transmitted in non-SBFD slots or symbols.

4. The method of claim 1, wherein receiving (504) the information that configures the UE for PUCCH SR transmission on SBFD slots or symbols and non-SBFD slots or symbols comprises receiving (504) a common PUCCH SR configuration that indicates one or more PUCCH SR resources applicable for both SBFD slots or symbols and non-SBFD slots or symbols.

5. The method of claim 4, further comprising:transmitting (506) one or more first PUCCH SR transmissions in SBFD slots or symbols, in accordance with the common PUCCH SR configuration; transmitting (506) one or more second PUCCH SR transmissions in non-SBFD slots or symbols, in accordance with the common PUCCH SR configuration; wherein separately monitoring (510) PUCCH SR transmissions for SBFD slots or symbols and non-SBFD slots or symbols comprises separately monitoring (510) the first PUCCH SR transmissions transmitted in SBFD slots or symbols and the second PUCCH SR transmissions transmitted in non-SBFD slots or symbols.

6. The method of any of claims 1 to 5, wherein the UE maps the PUCCH SR configuration or the PUCCH SR resources applicable to SBFD slots or symbols to one or more logical channels associated with a first latency requirement and maps the PUCCH SR configuration or the PUCCH SR resources applicable to non-SBFD slots or symbols to one or more logical channel associated with a second latency requirement, the second latency requirement being more relaxed than the first latency requirement.

7. The method of any of claims 1 to 6, wherein separately monitoring (510) PUCCH SR transmissions for SBFD slots or symbols and non-SBFD slots or symbols comprises maintaining (510A) a first counter for PUCCH SR transmissions transmitted during SBFD slots or symbols and maintaining (510B) a second counter for PUCCH SR transmissions transmitted during non- SBFD slots or symbols.

8. The method of claim 7, further comprising: determining (510A) that the first counter for PUCCH SR transmissions transmitted during SBFD slots or symbols has reached a configured maximum threshold number of PUCCH SR transmissions; and in response thereto, triggering (512A) one or more failure recovery actions.

9. The method of claim 8, wherein the one or more failure recovery actions comprises any one or more of the following: notifying an upper layer to release PUCCH and SR resources assigned for SBFD symbols; clearing uplink grants or PUSCH resources assigned for SBFD symbols; initiating a random access procedure on a special cell, SpCell, using RACH resources which are allowed or assigned to be used for random access operation in SBFD symbols.

10. The method of claim 8, wherein the one or more failure recovery actions comprises initiating a random access procedure, wherein the UE includes an indicator in the random access procedure that indicates that the maximum number of PUCCH SR transmissions for SBFD symbols has been reached.

11. The method of claim 7, further comprising: determining (51 OB) that the second counter for PUCCH SR transmissions transmitted during non-SBFD slots or symbols has reached a configured maximum threshold number of PUCCH SR transmissions; and in response thereto, triggering (512A) one or more failure recovery actions.

12. The method of claim 11, wherein the one or more failure recovery actions comprises any one or more of the following: notifying an upper layer to release PUCCH and SR resources assigned for non-SBFD symbols; clearing uplink grants or PUSCH resources assigned for non-SBFD symbols; initiating a random access procedure on a special cell, SpCell, using RACH resources which are allowed / assigned to be used for random access operation in non-SBFD symbols.

13. The method of claim 11, wherein the one or more failure recovery actions comprises initiating a random access procedure, wherein the UE includes an indicator in the random access procedure that indicates that the maximum number of PUCCH SR transmissions for non-SBFD symbols has been reached.

14. The method of claim 7, further comprising: determining (510A) that the first counter for PUCCH SR transmissions transmitted during SBFD slots or symbols has reached a configured maximum threshold number of PUCCH SR transmissions; and in response thereto, using (514B) PUCCH SR resources configured for non-SBFD slots or symbols for one or more additional PUCCH SR transmissions.

15. The method of claim 7, further comprising: determining (51 OB) that the second counter for PUCCH SR transmissions transmittedduring non-SBFD slots or symbols has reached a configured maximum threshold number of PUCCH SR transmissions; and in response thereto, using (514B) PUCCH SR resources configured for SBFD slots or symbols for one or more additional PUCCH SR transmissions.

16. A User Equipment, UE, (500; 1000) comprising: a communication interface (1012) comprising a transmitter (1018) and a receiver (1020); and processing circuitry (1002) associated with the communication interface (1012), the processing circuitry (1002) configured to cause the UE (500; 1000) to: receive (504), from a network node (502), information that configures the UE for Physical Uplink Control Channel, PUCCH, Scheduling Request, SR, transmission on SubBand Full Duplex, SBFD, slots or symbols and non-SBFD slots or symbols; and separately monitor (510) Physical Uplink Control Channel, PUCCH, Scheduling Request, SR, transmissions for SBFD slots or symbols and non-SBFD slots or symbols.

17. The UE (500; 1000) of claim 16, wherein the processing circuitry (1002) is further configured to cause the UE (500; 1000) to perform the method of any of claims 2 to 15.

18. A method performed by a User Equipment, UE, the method comprising: separately monitoring (702) uplink failure instances for SubBand Full Duplex, SBFD, slots or symbols and non-SBFD slots or symbols; and performing (704) one or more actions based on results of separately monitoring (702) uplink failure instances for SBFD slots or symbols and non-SBFD slots or symbols.

19. The method of claim 18, wherein performing (704) the one or more actions comprises: based on the separate monitoring, detecting (705, YES) a random access problem caused by SBFD slots or symbols or associated SBFD operation; and in response thereto, either: declaring (706) a SBFD specific radio link failure and refraining from triggering Radio Resource Control, RRC, connection reestablishment; or refraining (706) from declaring a radio link failure.

20. The method of claim 18, wherein performing (704) the one or more actions comprises:based on the separate monitoring, detecting (708, YES) a random access problem caused by non-SBFD slots or symbols or associated non-SBFD operation; and in response thereto, either: declaring (710) a non-SBFD specific radio link failure and refraining from triggering Radio Resource Control, RRC, connection reestablishment; or refraining (710) from declaring a radio link failure.

21. The method of claim 18, wherein performing (704) the one or more actions comprises: based on the separate monitoring, detecting (712, YES) a random problem caused by both SBFD slots or symbols or associated SBFD operation and non-SBFD slots or symbols or associated non-SBFD operation; and in response thereto, declaring (714) a radio link failure.

22. The method of any of claims 18 to 21, wherein the uplink failure instances are failed random access transmissions.

23. A User Equipment, UE, (1000) comprising: a communication interface (1012) comprising a transmitter (1018) and a receiver (1020); and processing circuitry (1002) associated with the communication interface (1012), the processing circuitry (1002) configured to cause the UE (1000) to: separately monitor (702) uplink failure instances for SubBand Full Duplex, SBFD, slots or symbols and non-SBFD slots or symbols; and perform (704) one or more actions based on results of separately monitoring (702) uplink failure instances for SBFD slots or symbols and non-SBFD slots or symbols.

24. The UE (1000) of claim 23, wherein the processing circuitry (1002) is further configured to cause the UE (1000) to perform the method of any of claims 19 to 22.

25. A method performed by a network node, the method comprising: transmitting (504), to a User Equipment, UE, (500), information that configures the UE for Physical Uplink Control Channel, PUCCH, Scheduling Request, SR, transmission on SubBand Full Duplex, SBFD, slots or symbols and non-SBFD slots or symbols.

26. The method of claim 25, wherein transmitting (504) the information that configures the UE for PUCCH SR transmission on SBFD slots or symbols and non-SBFD slots or symbols comprises: transmitting (504), to the UE, a first PUCCH SR configuration that indicates one or more first PUCCH SR resources and is applicable for SBFD slots or symbols; and transmitting (504), to the UE, a second PUCCH SR configuration that indicates one or more second PUCCH SR resources and is applicable for non-SBFD slots or symbols, the second PUCCH SR configuration being separate from the first PUCCH SR configuration.

27. The method of claim 25, wherein transmitting (504) the information that configures the UE for PUCCH SR transmission on SBFD slots or symbols and non-SBFD slots or symbols comprises transmitting (504), to the UE, a common PUCCH SR configuration that indicates one or more PUCCH SR resources applicable for both SBFD slots or symbols and non-SBFD slots or symbols.

28. A network node (1100) comprising processing circuitry (1102) configured to cause the network node (1100) to: transmit (504), to a User Equipment, UE, (500), information that configures the UE for Physical Uplink Control Channel, PUCCH, Scheduling Request, SR, transmission on SubBand Full Duplex, SBFD, slots or symbols and non-SBFD slots or symbols.

29. The network node (1100) of claim 28, wherein the processing circuitry (1102) is further configured to cause the network node (1100) to perform the method of any of claims 26 to 27.

30. A method performed by a network node, the method comprising: receiving (600), from a User Equipment, UE, during a random access procedure, an indication that indicates that an associated failure is detected for SubBand Full Duplex, SBFD, resources, non-SBFD resources, or both SBFD resources and non-SBFD resources; and performing (602) one or more actions based on the received indication.

31. The method of claim 30, wherein the indication indicates that the failure is detected for SBFD resources, and performing the one or more actions comprises allocating one or more Physical Uplink Shared Channel, PUSCH, resources or one or more PUSCH grants within one or more uplink subbands of one or more SBFD symbols.

32. The method of claim 30, wherein the indication indicates that the failure is detected for non-SBFD resources, and performing the one or more actions comprises allocating one or more PUSCH resources or one or more PUSCH grants on one or more non-SBFD uplink or flexible symbols within a full carrier bandwidth of an associated carrier.

33. The method of claim 30, wherein the indication indicates that the failure is detected for SBFD resources, and performing the one or more actions comprises assigning one or more Physical Uplink Control Channel, PUCCH, resources for SBFD operation or SBFD symbols.

34. The method of claim 30, wherein the indication indicates that the failure is detected for non-SBFD resources, and performing the one or more actions comprises assigning one or more Physical Uplink Control Channel, PUCCH, resources for non-SBFD operation or non-SBFD symbols.

35. A network node (1100) comprising processing circuitry (1102) configured to cause the network node (1100) to: receive (600), from a User Equipment, UE, during a random access procedure, an indication that indicates that an associated failure is detected for SubBand Full Duplex, SBFD, resources, non-SBFD resources, or both SBFD resources and non-SBFD resources; and perform (602) one or more actions based on the received indication.

36. The network node (1100) of claim 35, wherein the processing circuitry (1102) is further configured to cause the network node (1100) to perform the method of any of claims 31 to 34.

Images