Subband full duplex (SBFD) aware user equipment (UE) for subband full duplex

Abstract

A method in a user equipment (UE 22) for communicating with a network node (16) via a cell supporting a subband full duplex (SBFD) operation includes: determining an indication that indicates one or both of the UE (22) being an SBFD aware UE (22); and the UE (22) having a preference to one or both of enable and disable SBFD operation; and transmitting the indication to the network node (16) while performing a random access channel (RACH) procedure.

Description

[0001] SUBBAND FULL DUPLEX (SBFD) AWARE USER EQUIPMENT (UE) FOR

[0002] SUBBAND FULL DUPLEX

[0003] TECHNICAL FIELD

[0004] The present disclosure relates to wireless communications, and in particular, to indications associated with subband full duplex (SBFD) aware user equipment.

[0005] BACKGROUND

[0006] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipments (UE), as well as communication between network nodes and between UEs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0007] FDD and TDD systems

[0008] Transmission and reception from a node, e.g., a terminal in a cellular wireless communication 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 FIG. 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 FIG. 1, implies that downlink and uplink transmission take place in different, nonoverlapping 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. In more detail, the following two information elements (IES) are defined in current specifications. The TDD pattern is typically configured with at least the first IE and optionally the second IE:

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

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

[0012] The first IE is cell specific (common to all UEs) and is provided by broadcast signaling. The first IE 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: • A number of full downlink slots at the beginning of the pattern configured by the parameter nDownlinkSlots.

[0013] • A number of full uplink slots at the end of the pattern configured by the parameter nUplinkSlots.

[0014] • A number of downlink ('D') symbols following the full downlink slots configured by the parameter nDownlinkSymbols.

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

[0016] • 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'

[0017] • Optionally, a 2ndpattern that is concatenated to the first pattern can be configured as above. If a 2ndpattern is configured, the constraint is that the sum of the periodicities of the two patterns must evenly divide 20 ms.

[0018] FIG. 2 shows an example TDD DL / UL pattern configured by TDD-DL-UL- ConfigCommon. The exemplary TDD DL / UL pattern includes S = 5 slots, i.e., 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.' TDD-DL-UL-ConfigCommon configures the cell-specific pattern, and TDD-DL-UL- ConfigDedicated (if provided) UE-specifically configures the direction for some or all of the 'F' symbols in the cell-specific pattern.

[0019] If a UE is not configured with TDD-DL-UL-ConfigDedicated, then the pattern at the top of the diagram is what the UE 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 in advance; rather, the direction becomes known once the UE detects a DCI scheduling / triggering a particular DL or UL signal / channel.

[0020] 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 DD-DL-UL-ConfigDedicated. The lower part of FIG. 2 shows three example 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 7 and the last 5 are indicated as 'D' and 'U', which converts some of the 'F' symbols (but not all in this example) to 'D' and 'U.'

[0021] A 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 cellspecific IE TDD-DL-UL-ConfigCommon. In other words, a UE does not expect to have a 'D' symbol converted to 'U' or vice versa.

[0022] Subband full duplex

[0023] As described in the prior section, in a conventional TDD system, entire carrier 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 FIG. 3.

[0024] For the 3GPP Release 18 (Rel-18) evolution of the NR system, 3GPP has decided to study the technical feasibilities and potential benefits of subband full duplex (SBFD) systems.

[0025] • 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 FIG. 4. That is, unlike a conventional TDD system as shown on the left-hand side of FIG. 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 lefthand side of FIG. 4.

[0026] • Similarly, instead of utilizing all carriers for the same DL or UL directions in a conventional TDD system as shown in the right-hand side of FIG. 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 FIG. 4.

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

[0028] Rel-18 PRACH Configuration

[0029] An exemplary physical random access channel (PRACH) configuration according to existing (3GPP Release 17 (Rel-17)) specifications is described. The example is for frequency range 1 (FR1) for unpaired spectrum, and uses PRACH configuration index 118 from the existing (Rel-17) 3GPP Technical Specification (TS) 38.211 as follows:

[0030] Table 1. - Example PRACH configuration index

[0031] FIG. 5 illustrates the example PRACH configuration assuming the PRACH subcarrier spacing (SCS) is 30 kHz. The value x = 1 in Table 1 above means that the PRACH configuration period is 2 radio frames (20 ms), and the value y = 1 means that the random access channel (RACH) occasions (ROs) occur in the 2ndframe of this period. Within this frame, the ROs occur in subframes 2, 3, 4, 7, 8, and 9. With 30 kHz SCS, there are two slots per subframe. Since the number of PRACH slots within a subframe is equal to 1 for this example, the 2ndslot of the subframe contains the ROs according to current specifications. This means that the ROs are contained in slots 5,6,9, 14, 17, and 19. In this example PRACH format A3 (6 symbol duration) is used, hence there are two back-to-back ROs per slot starting at symbol 0 of the slot. For this example, the cell-specific (common) TDD UL / DL pattern may be assumed to be D-D-D-D-U, which is also shown in FIG. 5. In the existing 3GPP TS 38.213, the UE assumes that a RACH occasion is valid if it is within UL symbols according to the following:

[0032] For unpaired spectrum, if a UE is not provided tdd-UL-DL-ConfigurationCommon, a PRACH occasion in a PRACH slot is valid if it does not precede a synchronization signal (SS) / physical broadcast channel (PBCH) block (SSB) in the PRACH slot and starts at least Agapsymbols after a last SS / PBCH block reception symbol, where Agapis provided in 3GPP TS 38.213, Table 8.1-2 and, if channelAccessMode = "semiStatic" is provided, does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where the UE does not transmit [3GPP TS 37.213], the candidate SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurst in system information block 1 (SIB1) or in ServingCellConfigCommon , as described in clause 4.1.

[0033] If a UE is provided tdd-UL-DL-ConfigurationCommon, a PRACH occasion in a PRACH slot is valid if it is within UL symbols, or it does not precede a SS / PBCH block in the PRACH slot and starts at least Agap symbols after a last downlink symbol and at least Agapsymbols after a last SS / PBCH block symbol, where Agapis provided in Table 8.1-2, and if channelAccessMode = "semiStatic" is provided, does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where there shall not be any transmissions, as described in [3GPP TS 37.213] the candidate SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon, as described in clause 4.1.

[0034] With the D-D-D-D-U pattern, it turns out that only slots 9 and 19 contain valid ROs. The ROs in slots in 5, 7, 15, and 17 are invalidated, as indicated by the Xs in FIG. 5.

[0035] In the current 3GPP TS 38.331, ROs are configured in the frequency domain via two parameters: msgl -FDM which indicates the number of ROs in the frequency domain (1, 2, 4, or 8) within an orthogonal frequency-division multiplexing (OFDM) symbol, and msgl -FrequencyStart which indicates the lowest indexed resource block (RB) in the active bandwidth part (BWP) of the first RO in the frequency domain. RACH-ConfigGeneric information element

[0036] RACH-ConfigGeneric ::= SEQUENCE { prach-Configurationlndex INTEGER (0..255), msgl-FDM ENUMERATED {one, two, four, eight}, msgl-FrequencyStart INTEGER

[0037] (0.,maxNrofPhysicalResourceBlocks-l), zeroCorrelationZoneConfig INTEGERfO..15), preambleReceivedTargetPower INTEGER (-202..-60),

[0038] }

[0039] Table 2. - RACH-ConfigGeneric field descriptions

[0040] Random Access failure

[0041] In the NR RACH procedure, the MAC entity counts the number of RACH transmissions, e.g., PRACH preamble transmissions in case of 4-step RACH procedure, or MsgA transmissions in case of 2-step RACH procedure. When the number of RACH transmissions in a RACH procedure has exceeded a given maximum number, the MAC entity may declare one of the below events:

[0042] 1> if the Random Access Preamble is transmitted on the SpCell:

[0043] 2> indicate a Random Access problem to upper layers;

[0044] 2> if this Random Access procedure was triggered for SI request:

[0045] 3> consider the Random Access procedure unsuccessfully completed.

[0046] 1> else if the Random Access Preamble is transmitted on an SCell:

[0047] 2> consider the Random Access procedure unsuccessfully completed.

[0048] The medium access control (MAC) entity may further trigger radio link failure (RLF) and RRC connection reestablishment if the event is declared on the special cell (SpCell). In addition, the MAC entity may also report the events to the network node (e.g., gNB).

[0049] SUMMARY

[0050] Some embodiments advantageously provide methods, systems, and apparatuses for determining and / or providing indications associated with subband full duplex (SBFD) aware user equipment.

[0051] A SBFD aware UE may operate in a cell supporting SBFD operation. The cell may serve both legacy UEs (i.e., which are not SBFD aware), and SBFD aware UEs. In such scenario, it would be beneficial for the cell / the network node (e.g., gNB) to be able to identify SBFD aware UEs as early as possible. This way, the cell / the network node (e.g., gNB) can assign / schedule SBFD aware UEs with resources in UL subbands during SBFD slots / symbols, so that these UEs can initiate UL transmission using resources in UL subband while there are parallel DL transmissions towards other UEs on the same slot and / or symbols using DL subbands, thereby exploiting the benefits of SBFD operation, e.g., reduce latency for their accesses / transmissions.

[0052] One solution to indicate whether a UE is SBFD aware to the network node (e.g., gNB) is to transmit PRACH preamble (and potentially data) by the UE using a SBFD RO. However, this solution would not work if a SBFD aware UE can use both legacy ROs (i.e., non SBFD ROs) and SBFD ROs to transmit PRACH preamble.

[0053] In some embodiments, a UE (e.g., an SBFD aware UE) may be configured to indicate its capability. One or more embodiments, one or more of the following may be performed:

[0054] 1) An SBFD aware UE indicates its capability to the network node (e.g., gNB) during RACH, especially when the UE initiates a RACH from RRC IDLE. a. Indication may be infeasible via RO, since the UE may use legacy ROs. b. This may be also applicable to the UE when the UE in RRC INACTIVE or RRC CONNECTED, e.g., the UE has moved from a cell where the cell does not support SBFD operation to a neighbor cell where the cell supports SBFD operation. That is, the UE may not report its capability on SBFD operation in the last serving cell when the UE was in RRC CONNECTED. So, the UE can report its capability via RACH signaling to the new serving cell / camped cell. 2) An SBFD aware UE indicates its preference on whether the UE prefers to enable / disable SBFD operation to the gNB during RACH. a. This gives the possibility to the SBFD aware UE to dynamically enable or disable SBFD operation. b. This may be applicable to the UE in all RRC states.

[0055] One or more embodiments may be beneficial at least because:

[0056] • More efficient SBFD operation in terms of resource utilization and RA performance in SBFD symbols may be obtained.

[0057] • Latency for a random access (RA) procedure is reduced.

[0058] • The UE can assist the network to refine SBFD configuration.

[0059] • Increased UL capacity may be obtained since: o SBFD aware UEs may use SBFD symbols earlier in their communication, leaving UL symbols for legacy UEs to use.

[0060] SBFD symbols and UL symbols may be better utilized from a signal interference plus noise ratio (SINR) perspective, such that UL symbols are used for worse SINR communications and SBFD symbols are used for better SINR communications. According to one aspect of the present disclosure, a method in a UE is provided. The method includes determining an indication that indicates one or both of: the UE being an SBFD aware UE; and the UE having a preference to one or both of enable and disable SBFD operation. The method includes transmitting the indication to the network node while performing a RACH procedure.

[0061] According to one or more embodiments of this aspect, the indication is transmitted when the UE initiates the RACH procedure from a radio resource control idle state.

[0062] According to one or more embodiments of this aspect, the transmitted indication is included in a MAC CE.

[0063] According to one or more embodiments of this aspect, the transmitted indication is included in one or more of: a Msg3 of four-step random access procedure, a MsgA of a two-step random access procedure, and an RRCSetupRequest message.

[0064] According to one or more embodiments of this aspect, the method includes enabling the SBFD operation per one or more of: a service, an application, an LCH, and an LCH group.

[0065] According to one or more embodiments of this aspect, the method includes receiving an indication indicating whether the UE is allowed to perform the SBFD operation. According to one or more embodiments of this aspect, being an SBFD aware UE includes a capability of the UE to operate according to an SBFD configuration of the cell.

[0066] According to another aspect of the present disclosure, a UE is provided. UE is configured to determine an indication that indicates one or both of: the UE being an SBFD aware UE; and the UE having a preference to one or both of enable and disable SBFD operation; and transmitting the indication to the network node while performing a RACH procedure.

[0067] According to one or more embodiments of this aspect, the indication is transmitted when the UE initiates the RACH procedure from a radio resource control idle state.

[0068] According to one or more embodiments of this aspect, the transmitted indication is included in a MAC CE.

[0069] According to one or more embodiments of this aspect, the transmitted indication is included in one or more of: a Msg3 of four-step random access procedure, a Msg A of a two-step random access procedure, and an RRCSetupRequest message.

[0070] According to one or more embodiments of this aspect, UE is configured to enable the SBFD operation per one or more of: a service, an application, an LCH, and an LCH group.

[0071] According to one or more embodiments of this aspect, UE is configured to receive an indication indicating whether the UE is allowed to perform the SBFD operation.

[0072] According to one or more embodiments of this aspect, being an SBFD aware UE includes a capability of the UE to operate according to an SBFD configuration of the cell.

[0073] According to another aspect of the present disclosure, a method in a network node is provided. The method includes receiving an indication while performing a RACH process, the indication indicating one or both of: the UE being an SBFD aware UE; and the UE having a preference to one or both of enable and disable SBFD operation. The method includes performing one or more actions based on the indication.

[0074] According to one or more embodiments of this aspect, the method includes transmitting another indication indicating whether the UE is allowed to perform the SBFD operation.

[0075] According to one or more embodiments of this aspect, the method includes: determining whether the UE is allowed to perform the SBFD operation based on whether one or more of: legacy resources are congested; SBFD resources are available; and one or both of a UE-measured channel parameter and a SINR at the network node exceeds a predetermined threshold. According to one or more embodiments of this aspect, the received indication is included in a MAC CE.

[0076] According to one or more embodiments of this aspect, the received indication is included in one or more of: a Msg3 of four-step random access procedure, a Msg A of a two-step random access procedure, and an RRCSetupRequest message.

[0077] According to one or more embodiments of this aspect, an SBFD aware UE includes a capability of the UE to operate according to an SBFD configuration of the cell.

[0078] According to another aspect of the present disclosure, a network node is provided. Network node is configured to receive an indication while performing a RACH process, the indication indicating one or both of: the UE being an SBFD aware UE ; and the UE having a preference to one or both of enable and disable SBFD operation. Network node is configured to perform one or more actions based on the indication.

[0079] According to one or more embodiments of this aspect, network node is further configured to: transmit another indication indicating whether the UE is allowed to perform the SBFD operation.

[0080] According to one or more embodiments of this aspect, the network node is further configured to: determine whether the UE is allowed to perform the SBFD operation based on whether one or more of: legacy resources are congested; SBFD resources are available; and one or both of a UE-measured channel parameter and a SINR at the network node exceeds a predetermined threshold.

[0081] According to one or more embodiments of this aspect, the received indication is included in a MAC CE.

[0082] According to one or more embodiments of this aspect, the received indication is included in one or more of: a Msg3 of four-step random access procedure, a Msg A of a two-step random access procedure, and an RRCSetupRequest message.

[0083] According to one or more embodiments of this aspect, an SBFD aware UE includes a capability of the UE to operate according to an SBFD configuration of the cell.

[0084] BRIEF DESCRIPTION OF THE DRAWINGS

[0085] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0086] FIG. 1 shows examples of FDD, half-duplex FDD, and TDD; FIG. 2 shows examples of TDD DL / UL patterns;

[0087] FIG. 3 shows examples of conventional TDD carrier or carrier systems;

[0088] FIG. 4 shows examples of subband full duplex systems;

[0089] FIG. 5 shows an example PRACH configuration;

[0090] FIG. 6 is a schematic diagram of an example network architecture illustrating a communication system according to principles disclosed herein;

[0091] FIG. 7 is a block diagram of a network node in communication with a user equipment over a wireless connection according to some embodiments of the present disclosure;

[0092] FIG. 8 is a flowchart of an example process in a user equipment according to some embodiments of the present disclosure;

[0093] FIG. 9 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0094] FIG. 10 is a flowchart of another example process in a user equipment according to some embodiments of the present disclosure; and

[0095] FIG. 11 is a flowchart of another example process in a network node according to some embodiments of the present disclosure.

[0096] DETAILED DESCRIPTION

[0097] Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to determining and / or providing indications associated with subband full duplex (SBFD) aware user equipment.

[0098] Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0099] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0100] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0101] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0102] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0103] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multistandard radio (MSR) radio node such as MSR BS, multi -cell / multicast coordination entity (MCE), relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node.

[0104] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein can be any type of user equipment capable of communicating with a network node or another UE over radio signals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device etc.

[0105] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0106] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0107] Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and / or network nodes. In other words, it is contemplated that the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0108] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0109] Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 6 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP -type cellular network that may support standards such as LTE and / or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). In some embodiments, coverage area 18 corresponds to a cell, which may serve or be used for communication with other devices of system 10. In some embodiments, a cell may be referred to as cell 18 (which may provide one or more coverage areas as described herein). Further, a cell may be of one or more types, such as a serving cell, target cell, neighbor cell, etc. Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first user equipment (UE) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as user equipments 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16.

[0110] Also, it is contemplated that a UE 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 can be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0111] A network node 16 (eNB or gNB) is configured to include a node management unit 24 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., network node functions. A user equipment 22 is configured to include a UE management unit 26 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., UE functions.

[0112] Example implementations, in accordance with an embodiment, of the UE 22 and network node 16 discussed in the preceding paragraphs will now be described with reference to FIG. 7.

[0113] The communication system 10 includes a network node 16 provided in a communication system 10 and including hardware 28 enabling it to communicate with the UE 22. The hardware 28 may include a radio interface 30 for setting up and maintaining at least a wireless connection 32 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 30 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 30 includes an array of antennas 34 to radiate and receive signal(s) carrying electromagnetic waves.

[0114] In the embodiment shown, the hardware 28 of the network node 16 further includes processing circuitry 36. The processing circuitry 36 may include a processor 38 and a memory 40. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 36 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 38 may be configured to access (e.g., write to and / or read from) the memory 40, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0115] Thus, the network node 16 further has software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16. Processor 38 corresponds to one or more processors 38 for performing network node 16 functions described herein. The memory 40 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 42 may include instructions that, when executed by the processor 38 and / or processing circuitry 36, causes the processor 38 and / or processing circuitry 36 to perform the processes described herein with respect to network node 16. For example, processing circuitry 36 of the network node 16 may include node management unit 24 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., network node functions.

[0116] The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 44 that may include a radio interface 46 configured to set up and maintain a wireless connection 32 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located. The radio interface 46 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 46 includes an array of antennas 48 to radiate and receive signal(s) carrying electromagnetic waves.

[0117] The hardware 44 of the UE 22 further includes processing circuitry 50. The processing circuitry 50 may include a processor 52 and memory 54. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 50 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 52 may be configured to access (e.g., write to and / or read from) memory 54, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0118] Thus, the UE 22 may further comprise software 56, which is stored in, for example, memory 54 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 56 may be executable by the processing circuitry 50. The software 56 may include a client application 58. The client application 58 may be operable to provide a service to a human or non-human user via the UE 22.

[0119] The processing circuitry 50 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by UE 22. The processor 52 corresponds to one or more processors 52 for performing UE 22 functions described herein. The UE 22 includes memory 54 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 56 and / or the client application 58 may include instructions that, when executed by the processor 52 and / or processing circuitry 50, causes the processor 52 and / or processing circuitry 50 to perform the processes described herein with respect to UE 22. For example, the processing circuitry 50 of the user equipment 22 may include UE management unit 26 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., UE functions.

[0120] In some embodiments, the inner workings of the network node 16 and UE 22 may be as shown in FIG. 7 and independently, the surrounding network topology may be that of FIG. 6.

[0121] The wireless connection 32 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.

[0122] Although FIGS. 6 and 7 show various “units” such as node management unit 24 and UE management unit 26 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0123] FIG. 8 is a flowchart of an example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 50 (including the UE management unit 26), processor 52, and / or radio interface 46. User equipment 22 such as via processing circuitry 50 and / or processor 52 and / or radio interface 46 is configured to determine (Block SI 00) an indication indicating a UE capability and / or UE preference to enable and / or disable the SBFD operation and transmit (Block SI 02) the indication to the network node while performing a random access channel (RACH) process.

[0124] In some embodiments, UE 22 is a an SBFD aware UE. In some other embodiments, the indication is transmitted when the UE 22 initiates the RACH process from a radio resource control idle state.

[0125] In some embodiments, the transmitted indication is included in a medium access control (MAC) control element (CE).

[0126] In some other embodiments, the transmitted indication is included in a message (Msg3) of four-step random access procedure and / or another message (MsgA) of a two- step random access procedure and / or an RRCSetupRequest message.

[0127] In some embodiments, the UE is configured to enable the SBFD operation per one or more of service, application, logical channel (LCH), and LCH group.

[0128] FIG. 9 is a flowchart of an example process in a network node 16. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the node management unit 24), processor 38, and / or radio interface 30. Network node 16 such as via processing circuitry 36 and / or processor 38 and / or radio interface 30 is configured to receive (Block SI 04) an indication indicating a UE capability and / or UE preference to enable and / or disable the SBFD operation, where the indication is received while performing a random access channel (RACH) process, and perform (Block SI 06) one or more actions based on the indication.

[0129] In some embodiments, the method further includes transmitting another indication indicating whether the UE 22 is allowed to perform the SBFD operation.

[0130] In some other embodiments, the method further includes determining whether the UE is allowed to perform the SBFD operation based on whether one or more of: legacy resources are congested, SBFD resources are available, and a UE measured channel parameter and / or signal interference plus noise ratio (SINR) in the cell exceeds a predetermined threshold.

[0131] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for determining and / or providing indications associated with subband full duplex (SBFD) aware user equipment.

[0132] In some embodiments, the term “SBFD aware UE” is used and may refer to a UE 22 which is capable of operating in a cell configured with the SBFD feature, i.e., the cell / the network node 16 transmits DL and receive UL simultaneously using different subbands in SBFD slots and symbols. The UE 22 may be aware of SBFD configurations so that the UE 22 knows or determines time and frequency locations for SBFD operation. That is, UE 22 may know or determine which slots / symbols are SBFD capable, which are also referred to as SBFD slots / symbols and also knows the frequency range / PRB ranges for UL subbands. In some embodiments, the UE 22 does not need to support a predetermined operation (e.g., full duplex operation) while being SBFD aware. That is, UE 22 may or may not support the predetermined operation.

[0133] In some other embodiments, the term “SFFD aware UE” is used and may refer to same frequency full duplex aware UE which is capable of operating in a cell configured with the SFFD feature. The UE 22 may be aware of SFFD configurations so that the UE 22 knows or determines time and frequency locations for SFFD operation. That is, UE 22 may know or determine which slots / symbols are SFFD capable, which are also referred to as SFFD slots / symbols and also knows the frequency range / PRB ranges for UL subbands. In some embodiments, the UE 22 does not need to support a predetermined operation (e.g., full duplex operation) while being SFFD aware.

[0134] FIG. 10 is a flowchart of an example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 50 (including the UE management unit 26), processor 52, and / or radio interface 46. UE 22 is configured to determine (Block SI 08) an indication that indicates one or both of: the UE 22 being an SBFD aware UE; and the UE 22 having a preference to one or both of enable and disable SBFD operation. UE 22 is configured to transmit (Block SI 10) the indication to the network node 16 while performing a RACH procedure.

[0135] In some embodiments, the indication is transmitted when the UE 22 initiates the RACH procedure from a radio resource control idle state.

[0136] In some embodiments, the transmitted indication is included in a MAC CE.

[0137] In some embodiments, the transmitted indication is included in one or more of: a Msg3 of four-step random access procedure, a MsgA of a two-step random access procedure, and an RRCSetupRequest message.

[0138] In some embodiments, UE 22 is configured to enable the SBFD operation per one or more of: a service, an application, an LCH, and an LCH group.

[0139] In some embodiments, UE 22 is configured to receive an indication indicating whether the UE 22 is allowed to perform the SBFD operation.

[0140] In some embodiments, being an SBFD aware UE comprises a capability of the UE 22 to operate according to an SBFD configuration of the cell. FIG. 11 is a flowchart of an example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the node management unit 24), processor 38, and / or radio interface 30. Network node 16 is configured to receive (Block SI 12) an indication while performing a random access channel, RACH, process, where the indication indicates one or both of: the UE 22 being an SBFD aware UE 22; and the UE 22 having a preference to one or both of enable and disable SBFD operation. Network node 16 is configured to perform (Block SI 14) one or more actions based on the indication.

[0141] In some embodiments, network node 16 is further configured to: transmit another indication indicating whether the UE is allowed to perform the SBFD operation.

[0142] In some embodiments, the network node 16 is further configured to: determine whether the UE 22 is allowed to perform the SBFD operation based on whether one or more of: legacy resources are congested; SBFD resources are available; and one or both of a UE-measured channel parameter and a SINR at the network node exceeds a predetermined threshold.

[0143] In some embodiments, the received indication is included in a MAC CE.

[0144] In some embodiments, the received indication is included in one or more of: a Msg3 of four-step random access procedure, a MsgA of a two-step random access procedure, and an RRCSetupRequest message.

[0145] In some embodiments, an SBFD aware UE comprises a capability of the UE 22 to operate according to an SBFD configuration of the cell. Although embodiments describe the UE 22 as an SBFD aware UE, the present disclosure is not limited as such, and the UE 22 may be an SFFD aware UE, any other UE 22 that is aware of another predetermined operation, or any other UE 22.

[0146] In one embodiment, a UE 22 informs the network node 16 of at least one of the below indicators concerning SBFD operation

[0147] 1) Whether the UE 22 is SBFD aware UE or not a. It may be applicable for the UE 22 to indicate the UE’ s capability concerning SBFD operation awareness to the network node 16.

[0148] 2) Whether the UE 22 prefers to enable or disable SBFD operation (given UE 22 is a SBFD aware UE) a. it is applicable for the SBFD aware UE 22 to indicate its willingness / preference on enabling / disabling SBFD operation to the network node 16.

[0149] In an example, as soon as an SFBD aware UE 22 indicates its capability to the network node 16, it is assumed (from the network and / or the UE perspective) that the UE 22 would always be supporting / willing to perform SBFD operation.

[0150] In an example, upon reception of an indication of UE capability on SBFD awareness, the network node 16 would just assume that the UE 22 is capable of supporting SBFD operation. However, whether or not the UE 22 wants to use SBFD operation, may be pending on the UE’s second indicator.

[0151] The above indicator(s) may be signaled to the network node 16 by the UE 22 via PUSCH based signaling during a RACH procedure.

[0152] As an additional embodiment, the indicator(s) are signaled by a RRC signaling in Msg3 in a 4-step based RA procedure.

[0153] In an example, the RRC signaling may be included in messages including RRCSetupRequest or RRCResumeRequest. RRCSetupRequest may be applicable to the UE 22 when the UE 22 initiates the RA procedure in RRC IDLE. RRCResumeRequest may be applicable to the UE 22 when the UE 22 initiates the RA procedure in RRC INACTIVE. For the RRCResumeRequest, the UE 22 may be already indicate its capability on SBFD awareness to the last serving network node 16 when the UE 22 is in RRC CONNECTED and the last serving network node 16 has stored the UE capability in the UE context. In this case, the network node 16 (i.e., the camped gNB or the visiting gNB) can fetch the UE’s capability info from the last serving network node 16. The UE 22 then only needs to indicate its preference on SBFD operation to the network node 16. In some embodiments, the last serving network node 16 does not support SBFD operation and therefore, the UE 22 is not requested / enquired by the last serving network node 16 on its capability on SBFD awareness. In this case, the UE 22 can indicate both its capability and its preference on SBFD operation to the network node 16.

[0154] In another example, the RRC signaling is included in RRC message UEAssistancelnformation. In this case, the UE 22 initiates the RA procedure in RRC CONNECTED.

[0155] In yet another example, the RRC signaling is a newly defined RRC message for indicating SBFD capability / preference on SBFD operation purpose. As an additional embodiment, the network node 16 decides whether a SBFD aware UE 22 to enable or disable SBFD operation. In this case, the UE 22 may only use UL subbands to perform UL transmissions in SBFD slots and / or symbols if the network node 16 has allowed the UE 22 to do so. Alternatively, the UE 22 may use UL subbands in SBFD slots and / or symbols in addition to resources in UL slots, to perform UL transmissions, if the network node 16 allows the UE 22 to do so. The network node 16 may determine for the UE 22 whether the UE 22 is allowed to perform SBFD operation based on one or more of

[0156] 1) Whether the legacy resources (i.e., resources in frequency and / or time for non SBFD operation) are congested. a. SBFD operation is preferred if legacy ROs are congested. b. SBFD operation is preferred if PUSCH resources in UL slots are congested. c. The UE’s RACH access or any UL transmission using legacy resources (e.g., legacy RACH resource or PUSCH resource) is delayed due to congestion or transmission failure. d. SBFD operation is preferred if measured UL radio channel quality by the network node 16 during UL slots and / or symbols indicate that the channel is congested. i. E.g., the measured RSRP like metric is below a configured threshold ii. E.g., the measured BLER like metric is higher than a configured threshold.

[0157] 2) Whether the SBFD resources (i.e., resources in frequency and / or time for SBFD operation) are available. a. SBFD operation is preferred if the expected load of SBFD ROs is lower than that of legacy ROs (e.g., the network node 16 can, based on statistics, determine the expected use or load of an RO).. b. SBFD operation is preferred if there are free PUSCH resources in SBFD slots and / or symbols. c. SBFD operation is preferred if measured UL radio channel quality by the network node 16 during SBFD slots and / or symbols indicate that the channel is in good condition (i.e., not congested). In an example, the network node measured UL radio channel quality during SBFD slots and / or SBFD symbols are higher than a reference signal received power (RSRP) like threshold, or below a block error rate (BLER) like threshold.

[0158] 3) Whether the UE’s measured channel / SINR (RSRP / RSRQ) in the cell is sufficiently good, i.e., exceeds, equals to, or is less than a predetermined threshold. a. SBFD operation is preferred if the channel is good indicating that the cell is less congested. b. SBFD operation is preferred if the cell or network node traffic load is sufficiently low (implying low cell / gNB self-interference).

[0159] The network node 16 may determine whether a SBFD aware UE 22 to enable or disable SBFD operation via signaling alternatives including RRC signaling, MAC CE or LI signaling (e.g., on PDCCH channel).

[0160] The network node 16 may obtain radio channel quality measurements via at least one of the below alternatives.

[0161] 1) The network node 16 measures reception of Msgl / MsgA transmission from the UE 22.

[0162] 2) The UE 22 includes its measurements on radio channel quality in Msg3 or MsgA.

[0163] As an additional embodiment, the indicator(s) are included in a MAC control element (CE), which may be newly defined MAC CE (e.g., named as SBFD indication MAC CE) or an existing MAC CE wherein certain existing fields are repurposed to carry the indicators. For the former, the MAC CE payload may contain zero bits. The indicator is carried via specific LCID values (which are used to represent the MAC CE). A MAC PDU contains the LCID value indicating that the UE 22 is SBFD aware / capable, or the UE 22 prefers to enable / disable SBFD operation.

[0164] As an additional embodiment, the indicator(s) are included in Msg3 in case of 4- step RA procedure, or MsgA in case of 2-step RA procedure.

[0165] As an additional embodiment, for a SBFD aware UE 22, SBFD operation may be enabled per service, application, LCH or LCH group. For a service, application, LCH or LCH group, associated with critical QoS requirements, e.g., delay sensitive requirement, SBFD operation can be applied / enabled, while for a service, application, LCH or LCH group associated with non-critical QoS requirements, e.g., delay insensitive requirement, SBFD operation can be disabled. As an additional embodiment, for a SBFD aware UE 22, SBFD operation may be enabled when the UE’s services, applications, LCHs or LCH groups are experiencing long delay (e.g., due to congestion or transmission failure in legacy resource region). SBFD operation may be disabled when the UE’s services, applications, LCHs or LCH groups are not experiencing long delay (e.g., no congestion or transmission failure in the legacy resource region)

[0166] In one implementation example, the above methods impacting the ASN1 of the RRC specification may be represented in 3GPP TS 38.331 vl8.1.0 (as described below) in the RRCSetupRequest message conveying the proposed indicators. The implementation has only covered part of the proposed information elements / changes.

[0167] Example Embodiments:

[0168] Example Al . A method in a UE 22 for communicating with a network node 16 via a cell supporting a SBFD operation, the method comprising: determining an indication indicating a UE capability and / or UE preference to enable and / or disable the SBFD operation; and transmitting the indication to the network node 16 while performing a random access channel (RACH) process.

[0169] Example A2. The method of Example Al, wherein the UE 22 is a an SBFD aware UE.

[0170] Example A3. The method of any one of Examples Al and A2, wherein the indication is transmitted when the UE 22 initiates the RACH process from a radio resource control idle state.

[0171] Example A4. The method of any one of Examples A1-A3, wherein the transmitted indication is included in a MAC CE.

[0172] Example A5. The method of any one of Examples A1-A4, wherein the transmitted indication is included in a message (Msg3) of four-step random access procedure and / or another message (MsgA) of a two-step random access procedure and / or an RRCSetupRequest message.

[0173] Example A6. The method of any one of Examples A1-A5, wherein the UE 22 is configured to enable the SBFD operation per one or more of service, application, LCH, and LCH group.

[0174] Example BL A UE 22 for communicating with a network node via a cell supporting a SBFD operation, the UE 22 configured to, and / or including a radio interface 46 and / or including processing circuitry 50 configured to: determine an indication indicating a UE capability and / or UE preference to enable and / or disable the SBFD operation; and transmit the indication to the network node 16 while performing a RACH process.

[0175] Example B2. The UE 22 of Example Bl, wherein the UE 22 is a an SBFD aware UE.

[0176] Example B3. The UE 22 of any one of Examples Bl and B2, wherein the indication is transmitted when the UE initiates the RACH process from a radio resource control idle state.

[0177] Example B4. The UE 22 of any one of Examples B1-B3, wherein the transmitted indication is included in a MAC CE.

[0178] Example B5. The UE 22 of any one of Examples B1-B4, wherein the transmitted indication is included in a message (Msg3) of four-step random access procedure and / or another message (MsgA) of a two-step random access procedure and / or an RRCSetupRequest message.

[0179] Example B6. The UE 22 of any one of Examples B1-B5, wherein the UE 22 is configured to enable the SBFD operation per one or more of service, application, LCH, and LCH group.

[0180] Example Cl . A method in a network node 16 for communicating with a UE 22 via a cell supporting a SBFD operation, the method comprising: receiving an indication indicating a UE capability and / or UE preference to enable and / or disable the SBFD operation, the indication being received while performing a random access channel (RACH) process; and performing one or more actions based on the indication.

[0181] Example C2. The method of Example Cl, wherein the method further includes: transmitting another indication indicating whether the UE 22 is allowed to perform the SBFD operation.

[0182] Example C3. The method of Examples Cl and C2, wherein the method further includes: determining whether the UE 22 is allowed to perform the SBFD operation based on whether one or more of: legacy resources are congested; SBFD resources are available; and a UE measured channel parameter and / or signal interference plus noise ratio (SINR) in the cell exceeds a predetermined threshold.

[0183] Example DI . A network node 16 for communicating with a UE 22 via a cell supporting a SBFD operation, the network node 16 configured to, and / or including a radio interface and / or including processing circuitry configured to: receive an indication indicating a UE capability and / or UE preference to enable and / or disable the SBFD operation, the indication being received while performing a RACH process; and perform one or more actions based on the indication.

[0184] Example D2. The network node of Example DI, wherein the network node 16 is further configured to: transmit another indication indicating whether the UE 22 is allowed to perform the SBFD operation.

[0185] Example D3. The network node of Examples DI and D2, wherein the network node 16 is further configured to: determine whether the UE 22 is allowed to perform the SBFD operation based on whether one or more of: legacy resources are congested; SBFD resources are available; and a UE measured channel parameter and / or SINR in the cell exceeds a predetermined threshold.

[0186] The following provides non-limiting examples of how certain aspects of the proposed solutions could be implemented within the framework of a specific communication standard. In particular, the following provides non-limiting examples of how the proposed solutions could be implemented within the framework of a 3 GPP TSG RAN standard. The changes described below are merely intended to illustrate how certain aspects of the proposed solutions could be implemented in a particular standard. However, the proposed solutions could also be implemented in other suitable manners, both in the 3GPP Specification and in other specifications or standards.

[0187] SBFD RO enabling and configuration

[0188] .2.2 Message definitions

[0189] = = === = = = Irrelevant texts are skipped. =

[0190] - RRCSetupRequest

[0191] The RRCSetupRequest message is used to request the establishment of an RRC connection.

[0192] Signalling radio bearer: SRBO

[0193] REC-SAP: TM

[0194] Logical channel: CCCH

[0195] Direction: UE to Network

[0196] RRCSetupRequest message

[0197] - ASN1 START

[0198] - TAG-RRC SETUPREQUEST- START

[0199] RRCSetupRequest ::= SEQUENCE { rrc S etupRequest RRC S etupRequest-IEs

[0200] } RRCSetupRequest-IEs ::= SEQUENCE { ue-Identity InitialUE-Identity, establishmentcause Establishmentcause, spare BIT STRING (SIZE (1))

[0201] } RRCSetupRequest-r 19-IEs : := SEQUENCE { ue-Identity InitialUE-Identity, establishmentcause Establishmentcause, spare BIT STRING (SIZE (1)) ueSBFDIndicator BIT STRING (SIZE (1))

[0202] InitialUE-Identity ::= CHOICE { ng-5G-S-TMSI-Partl BIT STRING (SIZE (39)), random Value BIT STRING (SIZE (39))

[0203] }

[0204] Establishmentcause ::= ENUMERATED { emergency, highPriority Access, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo- VideoCall, mo-SMS, mps- Priority Access, mcs-Priority Access, spared, spared, spared, spare3, spare2, sparel }

[0205] - TAG-RRC SETUPREQUEST- STOP

[0206] - ASN1STOP

[0207] = = === = ===Irrelevant texts are skipped. ======================

[0208] In another implementation example, the above methods impacting the MAC specification may be represented in 3GPP Technical Standard (TS) 38.321 v 18.1.0 as follows. A new LCID value is defined in the LCID table representing a new MAC CE “SBFD indication MAC CE”. The implementation has only covered part of the proposed information elements / changes. In this example, a MAC PDU including the new MAC CE is transmitted to the gNB indicating the UE is a SBFD aware UE. Otherwise, none of the MAC PDU including the new MAC CE is transmitted to the gNB indicating that the UE is a legacy UE, i.e., non SBFD aware UE.

[0209] 5.1.4 Random Access Response reception

[0210] Once the Random Access Preamble is transmitted and regardless of the possible occurrence of a measurement gap, the MAC entity shall: 1> if the contention-free Random Access Preamble for beam failure recovery request was transmitted by the MAC entity:

[0211] 2> if the contention-free Random Access Preamble for beam failure recovery request was transmitted on a non-terrestrial network:

[0212] 3 > start the ra-ResponseWindow configured in BeamFailureRecoveryConfig at the PDCCH occasion as specified in TS 38.213 [6],

[0213] 2> else:

[0214] 3 > start the ra-ResponseWindow configured in BeamFailureRecoveryConfig at the first PDCCH occasion as specified in TS 38.213 [6] from the end of the Random Access Preamble transmission.

[0215] 2> monitor for a PDCCH transmission on the search space indicated by recoverySearchSpaceld of the SpCell identified by the C-RNTI while ra- ResponseWindow is running. l>else:

[0216] 2> if the Random Access Preamble was transmitted on a non-terrestrial network:

[0217] 3> if the Random Access Preamble is transmitted with repetitions:

[0218] 4> start the ra-ResponseWindow configured in RACH-ConfigCommon at the PDCCH occasion from the end of all repetitions of the Random Access Preamble transmission as specified in TS 38.213 [6],

[0219] 3>else:

[0220] 4> start the ra-ResponseWindow configured in RACH-ConfigCommon at the PDCCH occasion as specified in TS 38.213 [6],

[0221] 2>else if the Random Access Preamble is transmitted with repetitions:

[0222] 3 > start the ra-ResponseWindow configured in RACH-ConfigCommon at the first PDCCH occasion from the end of all repetitions of the Random Access Preamble transmission as specified in TS 38.213 [6],

[0223] 2> else:

[0224] 3 > start the ra-ResponseWindow configured in RACH-ConfigCommon at the first PDCCH occasion as specified in TS 38.213 [6] from the end of the Random Access Preamble transmission.

[0225] 2> monitor the PDCCH of the SpCell for Random Access Response(s) identified by the RA-RNTI while the ra-ResponseWindow is running. 1> if notification of a reception of a PDCCH transmission on the search space indicated by recoverySearchSpaceldis received from lower layers on the Serving Cell where the preamble was transmitted; and

[0226] 1> if PDCCH transmission is addressed to the C-RNTI; and

[0227] 1> if the contention-free Random Access Preamble for beam failure recovery request was transmitted by the MAC entity:

[0228] 2> consider the Random Access procedure successfully completed. l>else if a valid (as specified in TS 38.213 [6]) downlink assignment has been received on the PDCCH for the RA-RNTI and the received TB is successfully decoded:

[0229] 2> if the Random Access Response contains a MAC subPDU with Backoff Indicator:

[0230] 3> set the PREAMBLE BACKOFF to value of the BI field of the MAC subPDU using Table 7.2-1, multiplied with SCALING FACTOR BI.

[0231] 2> else:

[0232] 3> set the PREAMBLE BACKOFF to 0 ms.

[0233] 2> if the Random Access Response contains a MAC subPDU with Random Access Preamble identifier corresponding to the transmitted PREAMBLE INDEX (see clause 5.1.3):

[0234] 3> consider this Random Access Response reception successful.

[0235] 2> if the Random Access Response reception is considered successful:

[0236] 3> if the Random Access Response includes a MAC subPDU with RAPID only:

[0237] 4> consider this Random Access procedure successfully completed;

[0238] 4> indicate the reception of an acknowledgement for SI request to upper layers.

[0239] 3>else:

[0240] 4> apply the following actions for the Serving Cell where the Random Access Preamble was transmitted:

[0241] 5> process the received Timing Advance Command (see clause 5.2);

[0242] 5> indicate the preambleReceivedTargetPower and the amount of power ramping applied to the latest Random Access Preamble transmission to lower layers (i.e. (PREAMBLE POWER RAMPING COUNTER - I) x PREAMBLE POWER RAMPING STEP},

[0243] 5>if the Random Access procedure for an SCell is performed on uplink carrier where pusch-Config is not configured: 6> ignore the received UL grant.

[0244] 5>else:

[0245] 6> process the received UL grant value and indicate it to the lower layers.

[0246] 4> if the Random Access Preamble was not selected by the MAC entity among the contention-based Random Access Preamble(s):

[0247] 5> consider the Random Access procedure successfully completed.

[0248] 4> else:

[0249] 5> set the TEMPORARY C-RNTI to the value received in the Random Access Response;

[0250] 5> if this is the first successfully received Random Access Response within this Random Access procedure:

[0251] 6> if the transmission is not being made for the CCCH logical channel: 7> indicate to the Multiplexing and assembly entity to include a C- RNTI MAC CE in the subsequent uplink transmission.

[0252] 6> if the Random Access procedure was initiated for SpCell beam failure recovery and spCell-BFR-CBRA with value true is configured:

[0253] 7>if there is at least one Serving Cell of this MAC entity configured with two BFD-RS sets:

[0254] 8> indicate to the Multiplexing and assembly entity to include an Enhanced BFR MAC CE or a Truncated Enhanced BFR MAC CE in the subsequent uplink transmission.

[0255] 7> else:

[0256] 8> indicate to the Multiplexing and assembly entity to include a BFR MAC CE or a Truncated BFR MAC CE in the subsequent uplink transmission.

[0257] 6>else if the Random Access procedure was initiated for beam failure recovery of both BFD-RS sets of SpCell:

[0258] 7> indicate to the Multiplexing and assembly entity to include an Enhanced BFR MAC CE or a Truncated Enhanced BFR MAC CE in the subsequent uplink transmission.

[0259] 6> if the UE is SBFD operation aware:

[0260] 7> indicate to the Multiplexing and assembly entity to include a SBFD indication MAC CE in the subsequent uplink transmission. 6> obtain the MAC PDU to transmit from the Multiplexing and assembly entity and store it in the Msg3 buffer.

[0261] NOTE 1 : If within a Random Access procedure, an uplink grant provided in the Random Access Response for the same group of contention-based Random Access Preambles has a different size than the first uplink grant allocated during that Random Access procedure, the UE behavior is not defined.

[0262] 1> if ra-ResponseWindow configured in BeamFailureRecoveryConfig expires and if a PDCCH transmission on the search space indicated by recoverySearchSpaceld addressed to the C-RNTI has not been received on the Serving Cell where the preamble was transmitted; or

[0263] 1> if ra-ResponseWindow configured in RACH-ConfigCommon expires, and if the Random Access Response containing Random Access Preamble identifiers that matches the transmitted PREAMBLE INDEX as not been received:

[0264] 2> consider the Random Access Response reception not successful;

[0265] 2> increment PREAMBLE TRANSMISSION COUNTER by 1 ;

[0266] 2> PREAMBLE TRANSMISSION COUNTER = preambleTransMax + 1 :

[0267] 3>if the Random Access Preamble is transmitted on the SpCell:

[0268] 4> indicate a Random Access problem to upper layers;

[0269] 4> if this Random Access procedure was triggered for SI request:

[0270] 5> consider the Random Access procedure unsuccessfully completed.

[0271] 3>else if the Random Access Preamble is transmitted on an SCell:

[0272] 4> consider the Random Access procedure unsuccessfully completed.

[0273] 2> if the Random Access procedure is not completed:

[0274] 3> if the Random Access Preamble is transmitted with repetitions and neither contention-free Random Access Resources nor Random Access resources for SI request have been provided for this Random Access procedure: TRANSMISSION COUNTER = \preambleTransMax-Msgl- Repetitiori\ + 1; or

[0275] 4>if PREAMBLE TRANSMISSION COUNTER = 2 x \preambleTransMax- Msgl -Repetition + 1 :

[0276] 5> if set of Random Access resources configured with the same prach- Configurationlndex and associated with a higher Msgl repetition number with the same feature or feature combination as the current set of Random Access resources is available: 6> select the set of Random Access resources associated with the next higher Msgl repetition number with the same feature or feature combination for this Random Access procedure;

[0277] 6> initialize startPreambleForThisPartition, numberOfPreamblesPerSSB-ForThisPartition, ssb-SharedRO- Masklndex and numberOfRA-PreamblesGroupA parameters for the Random Access procedure according to the values configured by RRC for the selected set of Random Access resources.

[0278] 3> select a random backoff time according to a uniform distribution between 0 and the PREAMBLE BACKOFF,

[0279] 3>if the criteria (as defined in clause 5.1.2) to select contention-free Random Access Resources is met during the backoff time:

[0280] 4> perform the Random Access Resource selection procedure (see clause

[0281] 5.1.2).

[0282] 3>else if the Random Access procedure for an SCell is performed on uplink carrier where pusch-Config is not configured:

[0283] 4> delay the subsequent Random Access transmission until the Random Access Procedure is triggered by a PDCCH order with the same ra- Preamblelndex, ra-ssb-OccasionMasklndex, and UL / SUL indicator TS 38.212 [9],

[0284] 3>else:

[0285] 4> perform the Random Access Resource selection procedure (see clause

[0286] 5.1.2) after the backoff time.

[0287] The MAC entity may stop ra-ResponseWindow (and hence monitoring for Random Access Response(s)) after successful reception of a Random Access Response containing Random Access Preamble identifiers that matches the transmitted PREAMBLE INDEX. HARQ operation is not applicable to the Random Access Response reception.

[0288] NOTE 2: For the case that RAR PDSCH bandwidth is larger than the bandwidth the eRedCap UE can receive or process per slot, and the UL grant in RAR indicates that the time is not enough for Msg3 transmission, as specified in TS 38.213 [6], it is up to UE implementation, e.g. either to consider the Random Access Response reception not successful, or transmit Msg3.

[0289] 5.1.3a MSGA transmission

[0290] The MAC entity shall, for each MSGA: l>tf PREAMBLE TRANSMISSION COUNTER is greater than one; and

[0291] 1> if the notification of suspending power ramping counter has not been received from lower layers; and

[0292] 1> if LBT failure indication was not received from lower layers for the last MSGA Random Access Preamble transmission; and

[0293] 1> if SSB selected is not changed from the selection in the last Random Access Preamble transmission:

[0294] 2> increment PREAMBLE POWER RAMPING COUNTER by 1.

[0295] 1> select the value of DELTA PREAMBLE according to clause 7.3;

[0296] 1> set PREAMBLE RECEIVED TARGET POWER to msgA- PreambleReceivedTargetPower + DELTA PREAMBLE + (PREAMBLE POWER RAMPING COUNTER - 1) x PREAMBLE POWER RAMPING STEP,

[0297] 1> if this is the first MSGA transmission within this Random Access procedure:

[0298] 2> if the transmission is not being made for the CCCH logical channel:

[0299] 3> indicate to the Multiplexing and assembly entity to include a C-RNTI MAC CE in the subsequent uplink transmission.

[0300] 2> if the Random Access procedure was initiated for SpCell beam failure recovery and spCell-BFR-CBRA with value true is configured:

[0301] 3> if there is at least one Serving Cell of this MAC entity configured with two BFD-RS sets:

[0302] 4> indicate to the Multiplexing and assembly entity to include an Enhanced BFR MAC CE or a Truncated Enhanced BFR MAC CE in the subsequent uplink transmission.

[0303] 3>else:

[0304] 4> indicate to the Multiplexing and assembly entity to include a BFR MAC CE or a Truncated BFR MAC CE in the subsequent uplink transmission.

[0305] 2>else if the Random Access procedure was initiated for beam failure recovery of both BFD-RS sets of SpCell:

[0306] 3> indicate to the Multiplexing and assembly entity to include an Enhanced BFR MAC CE or a Truncated Enhanced BFR MAC CE in the subsequent uplink transmission.

[0307] 2> if the UE is SBFD operation aware: 3> indicate to the Multiplexing and assembly entity to include a SBFD indication MAC CE in the subsequent uplink transmission.

[0308] 2> obtain the MAC PDU to transmit from the Multiplexing and assembly entity according to the HARQ information determined for the MSGA payload (see clause 5.1 ,2a) and store it in the MSGA buffer. > compute the MSGB-RNTI associated with the PRACH occasion in which the Random Access Preamble is transmitted; > instruct the physical layer to transmit the MSGA using the selected PRACH occasion and the associated PUSCH resource of MSGA (if the selected preamble and PRACH occasion is mapped to a valid PUSCH occasion), using the corresponding RA-RNTI, MSGB-RNTI, PREAMBLE INDEX, PREAMBLE RECEIVED TARGET POWER, msgA- PreambleReceivedTargetPower , and the amount of power ramping applied to the latest MSGA preamble transmission (i.e.

[0309] (PREAMBLE POWER RAMPING COUNTER - 1) x PREAMBLE POWER RAMPING STEP ,- > if LBT failure indication is received from lower layers for the transmission of this MSGA Random Access Preamble:

[0310] 2> instruct the physical layer to cancel the transmission of the MSGA payload on the associated PUSCH resource;

[0311] 2>if Ibt-FailureRecoveryConfig is configured:

[0312] 3> perform the Random Access Resource selection procedure for 2-step RA type (see clause 5.1.2a).

[0313] 2> else: TRANSMISSION COUNTER by 1; >W PREAMBLE TRANSMISSION COUNTER. = preambleTransMax + 1 :

[0314] 4> indicate a Random Access problem to upper layers;

[0315] 4> if this Random Access procedure was triggered for SI request:

[0316] 5> consider this Random Access procedure unsuccessfully completed.

[0317] 3>if the Random Access procedure is not completed:

[0318] 4> if msgA-TransMax is applied (see clause 5.1.1a) and PREAMBLE TRANSMISSION COUNTER = msgA-TransMax + 1 : 5> set the RA TYPE to 4-stepRA,' 5> perform initialization of variables specific to Random Access type as specified in clause 5.1.1a;

[0319] 5> if the Msg3 buffer is empty:

[0320] 6> obtain the MAC PDU to transmit from the MSGA buffer and store it in the Msg3 buffer;

[0321] 5> flush HARQ buffer used for the transmission of MAC PDU in the MSGA buffer;

[0322] 5> discard explicitly signalled contention-free 2-step RA type Random Access Resources, if any;

[0323] 5> perform the Random Access Resource selection procedure as specified in clause 5.1.2.

[0324] 4> else:

[0325] 5> perform the Random Access Resource selection procedure for 2-step RA type (see clause 5.1.2a).

[0326] NOTE: The MSGA transmission includes the transmission of the PRACH Preamble as well as the contents of the MSGA buffer in the PUSCH resource corresponding to the selected PRACH occasion and PREAMBLE INDEX (see TS 38.213 [6])

[0327] The MSGB-RNTI associated with the PRACH occasion in which the Random Access Preamble is transmitted, is computed as:

[0328] MSGB-RNTI = 1 + s_id + 14 * t_id + 14 * 80 * f id + 14 x 80 x 8 x ul_carrier_id + 14 * 80 x 8 x 2 where s_id is the index of the first OFDM symbol of the PRACH occasion (0 s_id < 14), t_id is the index of the first slot of the PRACH occasion in a system frame (0 t_id < 80), where the subcarrier spacing to determine t_id is based on the value of p specified in clause 5.3.2 in TS 38.211 [8] for p = {0, 1, 2, 3}, and for p = {5, 6}, t_id is the index of the 120 kHz slot in a system frame that contains the PRACH occasion (0 t_id < 80), f id is the index of the PRACH occasion in the frequency domain (0 f id < 8), and ul carrier id is the UL carrier used for Random Access Preamble transmission (0 for NUL carrier, and 1 for SUL carrier). The RA-RNTI is calculated as specified in clause 5.1.3.

[0329] 6.2.1 MAC subheader for DL-SCH and UL-SCH

[0330] = = === = ===Irrelevant texts are skipped. ====================== Table 6.2.1-2: Values of LCID for UL-SCH when the LX field is not present or is set to 0 Table 6.2.1-2a: Values of two-octet eLCID for UL-SCH

[0331] Table 6.2.1-2b: Values of one-octet eLCID for UL-SCH

[0332]

[0333] 6.1.3.X SBFD Indication MAC CE

[0334] The SBFD Indication MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-2b. It has a fixed size of zero bits.

[0335] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices. Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0336] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0337] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0338] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0339] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0340] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0341] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

What is Claimed is:

1. A method in a user equipment, UE, (22) for communicating with a network node (16) via a cell supporting a subband full duplex, SBFD, operation, the method comprising: determining (SI 12) an indication that indicates one or both of: the UE (22) being an SBFD aware UE (22); and the UE (22) having a preference to one or both of enable and disable SBFD operation; and transmitting (SI 14) the indication to the network node (16) while performing a random access channel, RACH, procedure.

2. The method of Claim 1, wherein the indication is transmitted when the UE (22) initiates the RACH procedure from a radio resource control idle state.

3. The method of any one of Claims 1-2, wherein the transmitted indication is included in a medium access control, MAC, control element, CE.

4. The method of any one of Claims 1-3, wherein the transmitted indication is included in one or more of: a Msg3 of four-step random access procedure, a MsgA of a two-step random access procedure, and an RRCSetupRequest message.

5. The method of any one of Claims 1-4, further comprising enabling the SBFD operation per one or more of: a service, an application, a logical channel, LCH, and an LCH group.

6. The method of any one of Claims 1-5, further comprising receiving an indication indicating whether the UE (22) is allowed to perform the SBFD operation.

7. The method of any one of Claims 1-6, wherein being an SBFD aware UE comprises a capability of the UE (22) to operate according to an SBFD configuration of the cell.

8. A user equipment, UE, (22) in communication with a network node (16) via a cell supporting a subband full duplex, SBFD, operation, the UE (22) comprising processing circuitry (50) configured to: determine an indication that indicates one or both of: the UE (22) being an SBFD aware UE (22); and the UE (22) having a preference to one or both of enable and disable SBFD operation; and transmit the indication to the network node (16) while performing a random access channel, RACH, procedure.

9. The UE (22) of Claim 8, wherein the indication is transmitted when the UE (22) initiates the RACH procedure from a radio resource control idle state.

10. The UE (22) of any one of Claims 8-9, wherein the transmitted indication is included in a medium access control, MAC, control element, CE.

11. The UE (22) of any one of Claims 8-10, wherein the transmitted indication is included in one or more of: a Msg3 of four-step random access procedure, a MsgA of a two-step random access procedure, and an RRCSetupRequest message.

12. The UE (22) of any one of Claims 8-11, wherein the processing circuitry (50) is configured to enable the SBFD operation per one or more of: a service, an application, a logical channel, LCH, and an LCH group.

13. The UE (22) of any one of Claims 8-12, wherein the processing circuitry (50) is configured to receive an indication indicating whether the UE (22) is allowed to perform the SBFD operation.

14. The UE of any one of Claims 8-13, wherein being an SBFD aware UE comprises a capability of the UE (22) to operate according to an SBFD configuration of the cell.

15. A method in a network node (16) for communicating with a user equipment, UE, (22) via a cell supporting a subband full duplex, SBFD, operation, the method comprising: receiving (SI 08) an indication while performing a random access channel, RACH, process, the indication indicating one or both of: the UE (22) being an SBFD aware UE (22); and the UE (22) having a preference to one or both of enable and disable SBFD operation; and performing (SI 10) one or more actions based on the indication.

16. The method of Claim 15, further comprising: transmitting another indication indicating whether the UE (22) is allowed to perform the SBFD operation.

17. The method of any one of Claims 15-16, further comprising: determining whether the UE (22) is allowed to perform the SBFD operation based on whether one or more of: legacy resources are congested;SBFD resources are available; and one or both of a UE-measured channel parameter and a signal interference plus noise ratio, SINR, at the network node exceeds a predetermined threshold.

18. The method of any one of Claims 15-17, wherein the received indication is included in a medium access control, MAC, control element, CE.

19. The method of any one of Claims 15-18, wherein the received indication is included in one or more of: a Msg3 of four-step random access procedure, a Msg A of a two-step random access procedure, and an RRCSetupRequest message.

20. The method of any one of Claims 15-19, wherein an SBFD aware UE (22) comprises a capability of the UE (22) to operate according to an SBFD configuration of the cell.

21. A network node (16) for communicating with a user equipment, UE, (22) via a cell supporting a subband full duplex, SBFD, operation, the network node (16) comprising processing circuitry (36) configured to: receive an indication while performing a random access channel, RACH, process, the indication indicating one or both of: the UE (22) being an SBFD aware UE (22); and the UE (22) having a preference to one or both of enable and disable SBFD operation; and perform one or more actions based on the indication.

22. The network node (16) of Claim 21, wherein the processing circuitry (36) is further configured to: transmit another indication indicating whether the UE (22) is allowed to perform the SBFD operation.

23. The network node (16) of any one of Claims 21-22, wherein the processing circuitry (36) is further configured to: determine whether the UE (22) is allowed to perform the SBFD operation based on whether one or more of: legacy resources are congested;SBFD resources are available; and one or both of a UE-measured channel parameter and a signal interference plus noise ratio, SINR, at the network node exceeds a predetermined threshold.

24. The network node (16) of any one of Claims 21-23, wherein the received indication is included in a medium access control, MAC, control element, CE.

25. The network node (16) of any one of Claims 21-24, wherein the received indication is included in one or more of: a Msg3 of four-step random access procedure, a MsgA of a two-step random access procedure, and an RRCSetupRequest message.

26. The network node (16) of any one of Claims 21-25, wherein an SBFD aware UE comprises a capability of the UE (22) to operate according to an SBFD configuration of the cell.

Images