Uplink and downlink multiplexing for half-duplex devices

Abstract

Methods, systems, and devices for wireless communication are described. In one aspect, a network entity operating in a full duplex mode may configure a user equipment (UE) operating in a half duplex mode for uplink and downlink communications on the same time resource. The UE may then determine whether to receive a downlink message or to transmit an uplink message on the time resource. In some examples, if the UE determines to ignore the downlink message, the UE may transmit the uplink message. Otherwise, the UE may receive the downlink message. In another aspect, a network entity may send a group common downlink control information (GC-DCI) message to one or more UEs, thereby triggering a BWP handover at the UE. Since the network entity may avoid sending UE-specific signaling to trigger the BWP handover, the overhead associated with triggering the BWP handover may be reduced.

Description

Technical Field

[0001] The following relates to wireless communications, including uplink and downlink multiplexing for half-duplex devices. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems), and fifth generation (5G) systems, which may be referred to as new radio (NR) systems. These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM).

[0003] A wireless multiple access communication system may include one or more network entities, each of which supports wireless communication of communication devices, which may be referred to as user equipment (UE). Some wireless communication systems may include UEs and network entities capable of operating in half-duplex mode, full-duplex mode, or both. Improved techniques for coordinating communications between UEs and network entities supporting half-duplex mode, full-duplex mode, or both may be desirable. Summary of the invention

[0004] The described technology relates to improved methods, systems, devices and apparatuses for supporting uplink and downlink multiplexing for half-duplex devices and group common bandwidth part (BWP) switching. In one aspect, a network entity operating in full-duplex mode can configure a user equipment (UE) operating in half-duplex mode for uplink and downlink communications on the same time resource. The UE can then determine whether to receive a downlink message or send an uplink message on the time resource. In some examples, if the UE determines to ignore the downlink message, the UE can send the uplink message. Otherwise, the UE can receive the downlink message. On the other hand, the network entity can send a group common downlink control information (DCI) message to one or more UEs, thereby triggering a BWP switch at the UE. Since the network entity can avoid sending UE-specific signaling to trigger the BWP switch, the overhead associated with triggering the BWP switch can be reduced.

[0005] A method for wireless communication at a UE is described. The method may include: receiving an indication of a first configuration for utilizing at least one time resource for downlink communication from a network entity; receiving an indication of a second configuration for utilizing the same at least one time resource for uplink communication from the network entity; determining whether to receive a downlink message or send an uplink message on the at least one time resource based on the first configuration, the second configuration, the UE operating in half-duplex mode, and the network entity operating in full-duplex mode; and communicating with the network entity based on the determination.

[0006] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to receive an indication of a first configuration for downlink communication using at least one time resource from a network entity, receive an indication of a second configuration for uplink communication using the same at least one time resource from the network entity, determine whether to receive a downlink message or send an uplink message on the at least one time resource based on the first configuration, the second configuration, the UE operating in half-duplex mode, and the network entity operating in full-duplex mode, and communicate with the network entity based on the determination.

[0007] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving an indication of a first configuration for utilizing at least one time resource for downlink communication from a network entity; means for receiving an indication of a second configuration for utilizing the same at least one time resource for uplink communication from the network entity; means for determining whether to receive a downlink message or send an uplink message on the at least one time resource based on the first configuration, the second configuration, the UE operating in half-duplex mode, and the network entity operating in full-duplex mode; and means for communicating with the network entity based on the determination.

[0008] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive an indication of a first configuration for utilizing at least one time resource for downlink communication from a network entity, receive an indication of a second configuration for utilizing the same at least one time resource for uplink communication from the network entity, determine whether to receive a downlink message or send an uplink message on the at least one time resource based on the first configuration, the second configuration, the UE operating in half-duplex mode, and the network entity operating in full-duplex mode, and communicate with the network entity based on the determination.

[0009] In some examples of the methods, devices, and non-transitory computer-readable media described herein, determining whether to receive a downlink message or send an uplink message on at least one time resource may include operations, features, components, or instructions for determining whether to receive a downlink message or send an uplink message based on a first priority associated with the downlink message and a second priority associated with the uplink message. In some examples of the methods, devices, and non-transitory computer-readable media described herein, the first priority associated with the downlink message may be based on an active transmission configuration indication state at the UE and whether the UE can perform a beam management process at the UE. In some examples of the methods, devices, and non-transitory computer-readable media described herein, the second priority associated with the uplink message may be based on a latency requirement associated with the uplink message.

[0010] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: identifying that the UE may not have initiated a random access procedure, wherein at least one time resource includes a valid random access opportunity; and receiving a downlink message on at least one time resource based on identifying that the UE may not have initiated a random access procedure. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: identifying that the UE may have initiated a random access procedure, wherein at least one time resource includes a valid random access opportunity; and sending an uplink message on at least one time resource based on identifying that the UE may have initiated a random access procedure, wherein the uplink message includes a random access message.

[0011] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the downlink message includes a synchronization signal block, and the uplink message includes a data message, a control information message, a random access message, or a sounding reference signal. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the downlink message includes a data message, a control information message, or a channel state information reference signal, the uplink message includes a random access message, and the at least one time resource includes a valid random access opportunity.

[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving radio resource control signaling that configures at least one time resource for an uplink, wherein the downlink message scheduled on the at least one time resource includes a data message, a control information message, or a channel state information reference signal. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving radio resource control signaling that configures at least one time resource for a downlink, wherein the uplink message scheduled on the at least one time resource includes a data message, a control information message, a random access message, or a sounding reference signal. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, at least one time resource includes a flexible time resource configured for an uplink or a downlink.

[0013] A method for wireless communication at a network entity is described. The method may include: sending an indication of a first configuration for downlink communication using at least one time resource to a first set of UEs operating in half-duplex mode; sending an indication of a second configuration for uplink communication using at least one time resource to a second set of UEs, wherein the first set of UEs and the second set of UEs are at least partially overlapping sets; based on the network entity operating in full-duplex mode, monitoring at least one uplink message from at least one UE in the second set of UEs on at least one time resource; and based on the network entity operating in full-duplex mode, sending one or more downlink messages to one or more UEs in the first set of UEs on at least one time resource.

[0014] A device for wireless communication at a network entity is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor so that the device sends an indication of a first configuration for downlink communication using at least one time resource to a first set of UEs operating in half-duplex mode; sends an indication of a second configuration for uplink communication using at least one time resource to a second set of UEs, wherein the first set of UEs and the second set of UEs are at least partially overlapping sets; based on the network entity operating in full-duplex mode, monitors at least one uplink message from at least one UE in the second set of UEs on at least one time resource; and based on the network entity operating in full-duplex mode, sends one or more downlink messages to one or more UEs in the first set of UEs on at least one time resource.

[0015] Another apparatus for wireless communication at a network entity is described. The apparatus may include means for sending an indication of a first configuration for downlink communication utilizing at least one time resource to a first set of UEs operating in half-duplex mode; means for sending an indication of a second configuration for uplink communication utilizing at least one time resource to a second set of UEs, wherein the first set of UEs and the second set of UEs are at least partially overlapping sets; means for monitoring at least one uplink message from at least one UE in the second set of UEs on at least one time resource based on the network entity operating in full-duplex mode; and means for sending one or more downlink messages to one or more UEs in the first set of UEs on at least one time resource based on the network entity operating in full-duplex mode.

[0016] A non-transitory computer-readable medium is described that stores code for wireless communication at a network entity. The code may include instructions that can be executed by a processor to perform the following operations: send an indication of a first configuration for downlink communication using at least one time resource to a first set of UEs operating in half-duplex mode; send an indication of a second configuration for uplink communication using at least one time resource to a second set of UEs, wherein the first set of UEs and the second set of UEs are at least partially overlapping sets; based on the network entity operating in full-duplex mode, monitor at least one uplink message from at least one UE in the second set of UEs on at least one time resource; and based on the network entity operating in full-duplex mode, send one or more downlink messages to one or more UEs in the first set of UEs on at least one time resource.

[0017] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, one or more downlink messages include a synchronization signal block, and at least one uplink message includes a data message, a control information message, a random access message, or a sounding reference signal. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, one or more downlink messages include a data message, a control information message, or a channel state information reference signal, or a combination thereof, at least one uplink message includes a random access message, and at least one time resource includes a valid random access opportunity.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending radio resource control signaling to configure at least one time resource for an uplink, wherein one or more downlink messages scheduled on the at least one time resource include data messages, control information messages, channel state information reference signals, or a combination thereof.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending radio resource control signaling to configure at least one time resource for downlink, wherein the uplink message scheduled on the at least one time resource includes a data message, a control information message, a random access message, or a sounding reference signal. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, at least one time resource includes a flexible time resource configured for uplink or downlink. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 An example of a wireless communication system supporting uplink and downlink multiplexing for half-duplex devices according to one or more aspects of the present disclosure is illustrated.

[0021] Figure 2 An example of full-duplex communication according to one or more aspects of the present disclosure is illustrated.

[0022] Figure 3 An example of full-duplex operation at a first network entity and half-duplex operation at a first user equipment (UE) and a second UE according to one or more aspects of the present disclosure is illustrated.

[0023] Figure 4 An example of full-duplex operation at a first network entity and a first UE according to one or more aspects of the present disclosure is illustrated.

[0024] Figure 5 An example of full-duplex operation at a first UE and half-duplex operation at a first network entity and a second network entity according to one or more aspects of the present disclosure is illustrated.

[0025] Figure 6 An example of full-duplex operation at a first integrated access backhaul (IAB) node and a second IAB node according to one or more aspects of the present disclosure is illustrated.

[0026] Figure 7 An example of a wireless communication system supporting uplink and downlink multiplexing for half-duplex devices according to one or more aspects of the present disclosure is illustrated.

[0027] Figure 8 An example of communication based on multiplexing restriction rules according to one or more aspects of the present disclosure is illustrated.

[0028] Fig. 9 An example of communication based on relaxed or lifted multiplexing restriction rules according to one or more aspects of the present disclosure is illustrated.

[0029] Fig.10An example of a process flow supporting uplink and downlink multiplexing for half-duplex devices in accordance with one or more aspects of the present disclosure is illustrated.

[0030] Fig.11 An example of a wireless communication system supporting uplink and downlink multiplexing for half-duplex devices according to one or more aspects of the present disclosure is illustrated.

[0031] Fig.12 An example of bandwidth part (BWP) switching according to one or more aspects of the present disclosure is illustrated.

[0032] Fig.13 An example of group common BWP switching according to one or more aspects of the present disclosure is illustrated.

[0033] Fig.14 An example of a process flow supporting uplink and downlink multiplexing for half-duplex devices in accordance with one or more aspects of the present disclosure is illustrated.

[0034] Fig.15 and Fig.16 A block diagram of a device supporting uplink and downlink multiplexing for half-duplex devices is shown in accordance with one or more aspects of the present disclosure.

[0035] Fig.17 A block diagram of a communications manager supporting uplink and downlink multiplexing for half-duplex devices is shown in accordance with one or more aspects of the present disclosure.

[0036] Fig.18 A diagram of a system including a device supporting uplink and downlink multiplexing for half-duplex devices is shown in accordance with one or more aspects of the present disclosure.

[0037] Fig.19 and Fig. 20 A block diagram of a device supporting uplink and downlink multiplexing for half-duplex devices is shown in accordance with one or more aspects of the present disclosure.

[0038] Fig.21 A block diagram of a communications manager supporting uplink and downlink multiplexing for half-duplex devices is shown in accordance with one or more aspects of the present disclosure.

[0039] Fig. 22 A diagram of a system including a device supporting uplink and downlink multiplexing for half-duplex devices is shown in accordance with one or more aspects of the present disclosure.

[0040] Fig.23 and Fig.24A flow chart illustrating a method of supporting uplink and downlink multiplexing for half-duplex devices according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0041] Some wireless communication systems may include user equipment (UE) and network entities capable of operating in half-duplex mode, full-duplex mode, or both. In such systems, coordinating communications between the UE and the network entities may be challenging.

[0042] In one aspect, a UE operating in half-duplex mode may communicate with a network entity operating in full-duplex mode. To ensure that the UE is not scheduled to transmit and receive simultaneously, the UE may be configured to operate according to a plurality of multiplexing restriction rules. These multiplexing restriction rules may prevent the UE from simultaneously sending uplink transmissions to the network entity and receiving downlink transmissions from the network entity. However, in some cases, these multiplexing restriction rules may affect throughput if resources are not fully utilized (e.g., when the UE ignores downlink messages and still avoids sending uplink messages).

[0043] On the other hand, when communicating with one or more UEs, the network entity can operate in half-duplex mode or full-duplex mode. In some examples, the network entity can operate in full-duplex mode, and in the presence of strong self-interference, the network entity can fall back to half-duplex mode. In some cases, the size of the bandwidth part (BWP) used by the network entity for communication when in full-duplex mode may be different from the size of the BWP used by the network entity for communication when in half-duplex mode. Therefore, if the network entity determines to switch from communication in full-duplex mode to communication in half-duplex mode, the network entity may trigger BWP switching at one or more UEs communicating with the network entity. However, in some cases, the overhead associated with triggering BWP switching using existing UE-specific signaling may be high.

[0044] The technology described herein provides for effectively coordinating the communication between UE and network entity supporting half-duplex mode, full-duplex mode or both. In one aspect, the network entity operating in full-duplex mode can configure the UE operating in half-duplex mode to perform uplink and downlink communication on the same time resource. Then, the UE can determine whether to receive a downlink message or send an uplink message on the time resource. In some examples, if the UE determines to ignore the downlink message, the UE can send the uplink message. Otherwise, the UE can receive the downlink message. On the other hand, the network entity can send a group common downlink control information (GC-DCI) message to one or more UEs, thereby triggering a BWP switch at the UE. Since the network entity can avoid sending UE-specific signaling to trigger the BWP switch, the overhead associated with triggering the BWP switch can be reduced.

[0045] Various aspects of the present disclosure are first described in the context of a wireless communication system. Examples of processes and signaling exchanges that support uplink and downlink multiplexing and group-common BWP switching for half-duplex devices are then described. Various aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow charts related to uplink and downlink multiplexing and group-common BWP switching for half-duplex devices.

[0046] Figure 1 An example of a wireless communication system 100 supporting uplink and downlink multiplexing for half-duplex devices according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0047] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, etc. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area), and the UE 115 and the network entity 105 may establish one or more communication links 125 over the coverage area. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0048] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. Figure 1 As shown, the UE 115 described herein is capable of communicating with various types of devices, such as other UEs 115 or network entities 105 .

[0049] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.

[0050] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), and other examples or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0051] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0052] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration initiated by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0053] The functional split between CU 160, DU 165, and RU 175 is flexible and may support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 175. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by the other of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating over those communication links.

[0054] In a wireless communication system (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0055] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support uplink and downlink multiplexing for half-duplex devices as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0056] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0057] The UE 115 described herein is capable of communicating with various types of devices, such as other UEs 115 that may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0058] UE 115 and network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a defined physical layer structure to support a communication link 125. For example, a carrier for a communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-APro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any part (e.g., entity, sub-entity) of the network entity 105. For example, the terms "sending", "receiving" or "communicating" when referring to the network entity 105 may refer to any part of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0059] In some examples (such as in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be located according to a channel raster for discovery by a UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be performed by a UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

[0060] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115 (e.g., physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH), or channel state information reference signal (CSI-RS) transmissions), uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105 (e.g., physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), physical random access channel (PRACH), or sounding reference signal (SRS) transmissions), or both, as well as other transmission configurations. A carrier may carry downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry downlink communications and uplink communications (e.g., in TDD mode).

[0061] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers for a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communication on a particular carrier bandwidth or may be configurable to support communication on one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0062] The signal waveform sent on the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a subcarrier resource, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0063] One or more parameter sets for a carrier may be supported, where the parameter set may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of the UE 115 may be restricted to one or more active BWPs.

[0064] The time interval of the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, T s =1 / (Δf max ·N f ) seconds sampling period, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., in the range of 0 to 1023).

[0065] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, a time slot may also be divided into multiple mini-time slots including one or more symbols. In addition to the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0066] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0067] Physical channels may be multiplexed on a carrier according to various techniques. For example, physical control channels and physical data channels may be multiplexed on a downlink carrier using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a group of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0068] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0069] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, wildlife monitoring, weather and geological event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0070] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). UE 115 can be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication can include private communication or group communication, and can be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable, low-latency functions can include prioritization of services, and such services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency can be used interchangeably in this article.

[0071] In some examples, a UE 115 may be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or otherwise unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each other UE 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0072] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0073] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0074] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region of 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is approximately one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0075] The wireless communication system 100 may also operate in a super high frequency (SHF) region (also known as a centimeter band) using a frequency band of 3 GHz to 30 GHz or in an extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as a millimeter band) of the spectrum. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and network entity 105 (e.g., base station 140, RU170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater atmospheric attenuation and shorter distances than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0076] The wireless communication system 100 may utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as network entities 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed bands may be based on a carrier aggregation configuration (e.g., LAA) combined with component carriers operating in licensed bands. Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0077] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may have an antenna array having a set of rows and columns of antenna ports that the network entity 105 can use to support beamforming for communication with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0078] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0079] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different beamforming weight sets associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as network entity 105, or by a receiving device, such as UE 115) beam directions for later transmission or reception by the network entity 105.

[0080] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, the beam direction associated with the transmission along the single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0081] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a set of configured beams across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may or may not be precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-faceted codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0082] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0083] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer layer or the PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate on a logical channel. The MAC layer may perform priority processing and multiplexing of logical channels to transport channels. The MAC layer may also use error detection technology, error correction technology, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between a UE 115 and a network entity 105 or a core network 130. At the PHY layer, a transport channel may be mapped to a physical channel.

[0084] Some UEs 115 or network entities 105 in the wireless communication system 100 may be configured to adopt an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for the network entity 105 or UE 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating with limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some network entities 105 or UE 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

[0085] As a supplement or alternative to half-duplex mode, some network entities 105 or UE 115 may support full-duplex mode. Full-duplex mode may refer to a mode that supports bidirectional communication via simultaneous transmission and reception. This bidirectional communication may be referred to as full-duplex communication. Full-duplex communication is a technology that can theoretically double the link capacity by enabling a radio network node to simultaneously transmit and receive on the same frequency and time resources. Full-duplex breaks the half-duplex operation constraint in which transmission and reception are different in time or frequency. A full-duplex network node (such as a network entity 105, UE 115, or both in a cellular network) may communicate simultaneously with two half-duplex panels using the same radio resources in the uplink and downlink. For example, UE 115 may send an uplink transmission from one panel at UE 115, and UE 115 may receive a downlink transmission at another panel at UE 115. Similarly, network entity 105 may receive an uplink transmission at one panel at network entity 105, and network entity 105 may send a downlink transmission from another panel at network entity 105.

[0086] Thus, a device equipped with multiple TRPs that are capable of supporting simultaneous transmission and reception using the same time-frequency radio resources (e.g., uplink or downlink transmissions in frequency range 2 (FR2) and different related aspects of the process) may be referred to as a full-duplex capable device (e.g., a full-duplex UE 115 or a full-duplex network entity 105). The device is also capable of operating both in full-duplex mode and falling back to half-duplex mode. In some cases, full-duplex capability may depend on beam separation and other factors (e.g., self-interference between downlink and uplink and clutter echoes at the device). However, full-duplex communications may provide latency reduction (e.g., because it is possible to receive downlink signals in uplink-only time slots, which may achieve latency savings), spectral efficiency enhancement (e.g., per cell or per UE 115), more efficient resource utilization, and coverage enhancement utilizing continuous uplink or downlink transmissions or repetitions.

[0087] Figure 2 Examples of full-duplex communication 200 according to one or more aspects of the present disclosure are illustrated. In a first example 200-a, a UE 210-a may support full-duplex communication (e.g., operate in full-duplex mode), and the UE 210-a may receive a downlink signal from a first network entity 205-a (e.g., a cell or a transmit receive point (TRP)) and send an uplink signal to a second network entity 205-b. The first example 200-a may be an example of multi-TRP communication. In a second example 200-b, a network entity 205-c may support full-duplex communication (e.g., operate in full-duplex mode), and the network entity 205-c may send a downlink signal to a first UE 210-b and receive an uplink signal from a second UE 210-c. In a third example 200-c, the network entity 205-d and the UE 210-d may each support full-duplex communication (e.g., operate in full-duplex mode). The network entity 205 - d may send downlink signals to the UE 210 - d and receive uplink signals from the UE 210 - d , and the UE 210 - d may receive downlink signals from the network entity 205 - d and send uplink signals to the network entity 205 - d .

[0088] Figure 3An example of full-duplex operation 300 at a first network entity 305-a and half-duplex operation at a first UE 310-a and a second UE 310-b according to one or more aspects of the present disclosure is illustrated. The first network entity 305-a may receive uplink transmissions from the first UE 310-a and send downlink transmissions to the second UE 310-b. The second UE 310-b may experience CLI from the uplink transmissions of the first UE 310-a, and the first network entity 305-a may experience CLI from the second network entity 305-b. The first network entity 305-a may also experience self-interference from full-duplex operation because the first network entity 305-a may simultaneously receive uplink transmissions from the first UE 310-a and send downlink transmissions to the second UE 310-b.

[0089] Figure 4 An example of full-duplex operation 400 at a first network entity 405-a and a first UE 410-a (e.g., customer premises equipment (CPE)) in accordance with one or more aspects of the present disclosure is illustrated. The first network entity 405-a can communicate with the first UE 410-a and the second UE 410-b with partially overlapping uplink and downlink transmissions. The second UE 410-b can experience CLI from the uplink transmissions of the first UE 410-a, and the first network entity 405-a can experience CLI from the second network entity 405-b. The first network entity 405-a can also experience self-interference from full-duplex operation because the first network entity 405-a can simultaneously receive uplink transmissions from the first UE 410-a and send downlink transmissions to the first UE 410-a and the second UE 410-b. The first UE 410-a may also experience self-interference from full-duplex operation because the first UE 410-a may simultaneously receive downlink transmissions from the first network entity 405-a and send uplink transmissions to the first network entity 405-a.

[0090] Figure 5An example of full-duplex operation 500 at a first UE 510-a and half-duplex operation at a first network entity 505-a and a second network entity 505-b according to one or more aspects of the present disclosure is illustrated. The first network entity 505-a and the second network entity 505-b can support multiple transmit receive points (multiple TRPs) transmissions to the first UE 510-a (e.g., utilizing fully overlapping uplink and downlink transmissions). The second UE 510-b may experience CLI from uplink transmissions of the first UE 510-a, and the first network entity 505-a may experience CLI from downlink transmissions of the second network entity 505-b. The first UE 510-a may experience self-interference from full-duplex operation because the first UE 510-a may simultaneously receive downlink transmissions from the first network entity 505-a and the second network entity 505-b and send uplink transmissions to the first network entity 505-a.

[0091] Figure 6 An example of full-duplex operation 600 at a first IAB node 610-a and a second IAB node 610-b according to one or more aspects of the present disclosure (e.g., enhanced duplex capability) is illustrated. The first IAB node 610-a and the second IAB node 610-b may share a parent node 605. The first IAB node 610-a may send a downlink transmission to a first UE 615-a and receive an uplink transmission from a second UE 615-b. The second IAB node 610-b may send a downlink transmission to a third UE 615-c and receive an uplink transmission from a fourth UE 615-d. The first IAB node 610-a may experience a CLI from a downlink transmission of the second IAB node 610-b. The first IAB node 610-a may also experience self-interference from full-duplex operation because the first IAB node 610-a may simultaneously send a downlink transmission to the first UE 615-a and receive an uplink transmission from the second UE 615-b. Similarly, the second IAB node 610-b may experience self-interference from full-duplex operation because the second IAB node 610-b may simultaneously send downlink transmissions to the third UE 615-c and receive uplink transmissions from the fourth UE 615-d. In some cases, the first IAB node 610-a and the second IAB node 610-b may both support single frequency full duplex (SFFD) and FDM or spatial division multiplexing (SDM) with resource block group (RBG) granularity.

[0092] refer to Figures 3 to 6The described examples may be implemented in a wireless communication system 100. Thus, the wireless communication system 100 may include a UE 115 and a network entity 105 that can operate in half-duplex mode, full-duplex mode, or both. In some cases, coordinating communications between the UE 115 and the network entity 105 may be challenging. The wireless communication system 100 may support efficient techniques for coordinating communications between the UE 115 and the network entity 105 that support half-duplex mode, full-duplex mode, or both.

[0093] Figure 7 An example of a wireless communication system 700 that supports uplink and downlink multiplexing for half-duplex devices according to one or more aspects of the present disclosure is illustrated. The wireless communication system 700 includes a UE 115-a, which may be a reference Figures 1 to 6 The wireless communication system 700 also includes a network entity 105-a, which may be a reference Figures 1 to 6 The wireless communication system 700 may implement aspects of the wireless communication system 100. For example, the wireless communication system 700 may support efficient techniques for coordinating communications between a UE 115-a operating in half-duplex mode and a network entity 105-a operating in full-duplex mode.

[0094] Although the network entity 105-a may operate in full-duplex mode, the UE 115-a may operate in half-duplex mode and may not support full-duplex communication with the network entity 105-a. For example, in some wireless communication systems, in order to ensure that the UE 115-a is not scheduled to transmit and receive simultaneously, the UE 115-a may be configured to operate according to a plurality of multiplexing restriction rules. That is, downlink or uplink channel or reference signal multiplexing restriction rules in the time domain may be introduced. The multiplexing restriction rules may be applicable.

[0095] In one example, the multiplexing restriction rule may specify that the half-duplex UE 115 does not send PUSCH, PUCCH, PRACH or SRS transmissions on synchronization signal block (SSB) symbols. In another example, the multiplexing restriction rule may specify that the half-duplex UE 115 does not receive PDCCH, PDSCH or CSI-RS transmissions on valid random access opportunities (RO) and corresponding gap symbols. In another example, the multiplexing restriction rule may specify that the half-duplex UE 115 does not receive PDCCH, PDSCH or CSI-RS transmissions on RRC uplink symbols (e.g., both public and dedicated). In another example, the multiplexing restriction rule may specify that the half-duplex UE 115 does not send PUCCH, PUSCH, PRACH or SRS transmissions on RRC downlink symbols (e.g., both public and dedicated). In another example, the multiplexing restriction rule may specify that the half-duplex UE 115 does not expect to have both reception and transmission of dedicated configurations on the same RRC flexible symbol. Each of the above examples may be applicable to communications on different component carriers (eg, across component carriers) or at least on the same frequency band.

[0096] Figure 8 An example of multiplexing restriction rule based communication 800 in accordance with one or more aspects of the present disclosure is illustrated. As shown, a half-duplex UE 115 may avoid receiving downlink transmissions and sending uplink transmissions in valid random access opportunities.

[0097] These multiplexing restriction rules may prevent a half-duplex UE 115 from simultaneously sending uplink transmissions to the network entity 105 and receiving downlink transmissions from the network entity 105. However, in some cases, these multiplexing restriction rules may affect throughput if resources are not fully utilized (e.g., when the UE ignores downlink messages and still avoids sending uplink messages). Multiplexing restriction rules may also affect overhead if the bandwidth is not fully used for SSB transmissions, random access opportunities, etc. (e.g., because some downlink transmissions can be ignored and uplink transmissions can be avoided). In one example, the PRACH preamble duration may be in the range of 142 μs (e.g., format C0) to 3.5 ms (e.g., format 2) at a bandwidth of several MHz, and the UE 115 may use additional resources to send the PRACH preamble even if downlink transmissions during valid random access opportunities are ignored by the UE 115.

[0098] To improve throughput and minimize overhead, reduce downlink to uplink switching delays, and reduce latency, downlink or uplink channel or reference signal multiplexing restriction rules may be relaxed or lifted in the wireless communication system 700 for a half-duplex UE 115-a communicating with a full-duplex network entity 105-a. For example, the full-duplex network entity 105-a may configure or schedule the half-duplex UE 115-a to receive downlink transmissions 705 and send uplink transmissions 710 on the same time resources.

[0099] In one example, a half-duplex UE 115-b may be scheduled with PUSCH, PUCCH, PRACH, or SRS on an SSB symbol. In another example, a half-duplex UE 115-b may be scheduled with PDCCH, PDSCH, or CSI-RS on a valid random access opportunity and a corresponding gap symbol. In another example, a half-duplex UE 115-b may be scheduled with PDCCH, PDSCH, or CSI-RS on an RRC uplink symbol (e.g., both public and dedicated). In another example, a half-duplex UE 115-b may be scheduled with PUCCH, PUSCH, PRACH, or SRS on an RRC downlink symbol (e.g., both public and dedicated). In another example, a half-duplex UE 115-b may be configured to have both reception and transmission with a dedicated configuration on the same RRC flexible symbol.

[0100] Fig. 9 An example of communication 900 based on relaxed or lifted multiplexing restriction rules in accordance with one or more aspects of the present disclosure is illustrated. As shown, a half-duplex UE 115 may be configured or scheduled to receive downlink transmissions and transmit uplink transmissions in valid random access opportunities.

[0101] Since the half-duplex UE 115-a can be configured or scheduled for downlink communication and uplink communication on a time resource (e.g., the same time resource), the half-duplex UE 115-a can ignore the downlink transmission from the network entity 105-a on the time resource and send an uplink transmission to the network entity 105-a on the time resource. The half-duplex UE 115-a can also be configured to determine whether to receive a downlink message from the network entity 105-a on a certain time resource or to send an uplink message to the network entity 105-a on the same time resource. That is, the wireless communication system 700 can define priority rules for downlink or uplink channels or reference signals on the same symbol. In one example, when PDSCH is multiplexed with a random access opportunity, if UE 115-a does not initiate a random access channel (RACH) process (e.g., RACH for BFR) at the random access opportunity, PDSCH can be prioritized. Otherwise, UE 115-a can prioritize the RACH process at the random access opportunity and ignore PDSCH.

[0102] Fig.10 An example of a process flow 1000 for supporting uplink and downlink multiplexing for half-duplex devices in accordance with one or more aspects of the present disclosure is illustrated. The process flow 1000 includes a UE 115-a, which may be a reference Figures 1 to 9 The process flow 1000 also includes a network entity 105-a, which may be a reference Figures 1 to 9 The process flow 1000 may implement aspects of the wireless communication system 700. For example, the process flow 1000 may support efficient techniques for coordinating communications between a UE 115-a operating in half-duplex mode and a network entity 105-a operating in full-duplex mode.

[0103] In the following description of process flow 1000, signaling exchanged between UE 115-a and network entity 105-a may be exchanged in a different order than the example order shown, or operations performed by UE 115-a and network entity 105-a may be performed in a different order or at a different time. Some operations may also be omitted from process flow 1000, and other operations may be added to process flow 1000.

[0104] At 1005, the network entity 105-a may send and the UE 115-a may receive an indication of a first configuration for downlink communication utilizing at least one time resource. At 1010, the network entity 105-a may send and the UE 115-a may receive an indication of a second configuration for uplink communication utilizing the same at least one time resource. At 1015, the UE 115-a may determine whether to receive a downlink message or send an uplink message on at least one time resource based on the first configuration, the second configuration, and the UE 115-a operating in half-duplex mode. In some cases, the determination may be based on a network entity operating in full-duplex mode. The UE 115-a may then communicate with the network entity 105-a based on the determination.

[0105] At 1020, the network entity 105-a may send a downlink message to the UE 115-a. The UE 115-a may then determine whether to receive the downlink message. If the UE 115-a determines to receive the downlink message, the UE 115-a may receive the downlink message and avoid sending an uplink message on the at least one time resource. If the UE 115-a determines to ignore the downlink message, the UE 115-a may send an uplink message at 1025. In some cases, the network entity 105-a may send a downlink message and monitor for uplink messages because the network entity 105-a is operating in full-duplex mode. Therefore, the UE 115-a may monitor for downlink messages or send uplink messages, and the network entity 105-a may send a downlink message and monitor for uplink messages.

[0106] In some cases, UE 115-a may determine whether to receive a downlink message or send an uplink message based on a first priority associated with a downlink message and a second priority associated with an uplink message. The first priority associated with a downlink message may be based on an active transmit configuration indication (TCI) state at UE 115-a and whether UE 115-a is to perform a beam management process at UE 115-a. For example, if a downlink message includes an SSB that is not associated with the active TCI state at UE 115-a, UE 115-a may determine to ignore the downlink message. Alternatively, if UE 115-a does not intend to perform a beam management process, UE 115-a may determine to ignore a downlink message (e.g., SSB). The second priority associated with an uplink message may be based on a delay requirement associated with the uplink message. For example, if an uplink message is part of a URLLC service, UE 115-a may give priority to sending an uplink message over receiving a downlink message.

[0107] In some cases, if UE 115-a has not yet initiated a random access procedure (e.g., when at least one time resource allocated for downlink and uplink communications includes a valid random access opportunity), UE 115-a may receive a downlink message on the at least one time resource. Alternatively, if UE 115-a has initiated a random access procedure (e.g., when at least one time resource allocated for downlink and uplink communications includes a valid random access opportunity), UE 115-a may send an uplink message on the at least one time resource. In some examples, the downlink message may include an SSB, and the uplink message may include a data message (e.g., a PUSCH message), a control information message (e.g., a PUCCH message), a random access message (e.g., a PRACH message), or an SRS. In some examples, the downlink message may include a data message (e.g., a PDSCH message), a control information message (e.g., a PDCCH message), or a CSI-RS, and the uplink message may include a random access message (e.g., a PRACH message), wherein at least one time resource is a valid random access opportunity.

[0108] In some cases, the network entity 105-a may send and the UE 115-a may receive RRC signaling that configures at least one time resource for an uplink, wherein the downlink message scheduled on the at least one time resource includes a data message (e.g., a PDSCH message), a control information message (e.g., a PDCCH message), or a CSI-RS. In some cases, the network entity 105-a may send and the UE 115-a may receive RRC signaling that configures at least one time resource for a downlink, wherein the uplink message scheduled on the at least one time resource includes a data message (e.g., a PUSCH message), a control information message (e.g., a PUCCH message), a random access message (e.g., a PRACH message), or an SRS. In some examples, the at least one time resource may include a flexible time resource configured for an uplink or a downlink.

[0109] Fig.11 An example of a wireless communication system 1100 supporting group common BWP switching according to one or more aspects of the present disclosure is illustrated. The wireless communication system 1100 includes a group of UEs 1105, and each UE 115 in the group may be a reference Figures 1 to 10 The wireless communication system 1100 also includes a network entity 105-b, which may be a reference Figures 1 to 10The wireless communication system 1100 may implement aspects of the wireless communication system 100. For example, the wireless communication system 1100 may support efficient techniques for coordinating communications between a network entity 105-b supporting half-duplex mode and a group of UEs 1105 that support full-duplex mode.

[0110] Although the network entity 105-b is capable of operating in full-duplex mode and can support full-duplex communications, in some cases it may be appropriate for the network entity 105-b to operate in half-duplex mode. For example, in the presence of strong self-interference at the network entity 105-b, the network entity 105-b may preferably switch from full-duplex scheduling to half-duplex scheduling, which may involve a change in the active BWP of each UE 115. When the network entity 105-b operates in full-duplex mode and communicates using FDM, the uplink and downlink BWPs used by the network entity 105-b to communicate with each UE 115 in the group of UEs 1105 may be narrower than the full bandwidth to save power. However, when the network entity 105-b operates in half-duplex mode, the uplink and downlink BWPs used by the network entity 105-b to communicate with each UE 115 in the group of UEs 1105 may span the full bandwidth to fully utilize the spectrum.

[0111] Fig.12 An example of BWP switching 1200 in accordance with one or more aspects of the present disclosure is illustrated. The network entity 105-b may experience strong self-interference and may switch from communicating using network FDM-based full-duplex time slots 1205 and may communicate using network half-duplex time slots 1210. That is, the network entity 105-b may prefer half-duplex communications when experiencing strong self-interference. The network entity 105-b may also switch the BWP used for communications when switching from communicating using full-duplex to communicating using half-duplex. For downlink communications, the network entity 105-b may switch from communicating on BWP 1215 to communicating using BWP 1225. For uplink communications, the network entity 105-b may switch from communicating on BWP 1220 to communicating using BWP 1225.

[0112] Thus, if the network entity 105-b determines to switch from communicating in full-duplex mode to communicating in half-duplex mode, the network entity may determine to trigger a BWP switch at the group of UEs 1105 communicating with the network entity 105-b. However, in some cases, active BWP switching may be UE-specific via the BWP indicator field of the non-fallback DCI format, and the overhead associated with triggering the BWP switch using existing UE-specific signaling may be high. That is, if the network entity 105-b prefers to change the BWP used to communicate with a group of UEs 1105 (e.g., which may be subject to strong self-interference at the network entity 105-b), active BWP switching using UE-specific signaling may not be cost-effective.

[0113] When the network entity 105 - b switches from communicating using full-duplex to communicating using half-duplex, the wireless communication system 1100 may support efficient techniques for facilitating BWP switching from a first BWP to a second BWP.

[0114] According to various aspects described herein, a GC-DCI 1110 may be introduced for BWP switching of a group of UEs 1105 (e.g., UEs 115 with which a network entity 105-b communicates using the same SSB beam). The GC-DCI 1110 may carry a downlink or uplink active BWP field for each UE 115 in the group of UEs 1105, or the GC-DCI 1110 may carry a common downlink or uplink active BWP field for all UEs 115 in the group of UEs 1105. In some examples, the GC-DCI 1110 may implicitly activate or reactivate semi-persistent downlink or uplink transmission of a second BWP (e.g., a new BWP) for each UE 115 (e.g., similar to a semi-persistent scheduling (SPS) or type 2 configuration grant). If any UE 115 in the group of UEs 1105 lacks support for BWP switching using GC-DCI 1110, the network entity 105-b may use BWP signaling to trigger BWP switching or reuse the half-duplex BWP for full-duplex. In some examples, a predetermined half-duplex or full-duplex BWP switching pattern may also be configured for the group of UEs 1105, which may implicitly activate or reactivate semi-persistent downlink or uplink transmissions of a second BWP configured for each UE 115 (e.g., similar to an SPS or Type 2 configuration grant).

[0115] Fig.13An example of a group common BWP switch 1300 according to one or more aspects of the present disclosure is illustrated. The network entity 105-b may communicate with the group of UEs 1105 using network FDM-based full-duplex time slots 1305-a and may experience strong self-interference. Therefore, the network entity 105-b may determine to switch to communicating with the group of UEs 1105 using network half-duplex time slots 1310. The network entity 105-b may send a GC-DCI on a GC-PDCCH 1315-a to trigger a BWP switch from communication using full-duplex to communication using half-duplex. For downlink communications, the GC-DCI may trigger a BWP switch from BWP 1320 to BWP 1330, and for uplink communications, the GC-DCI may trigger a BWP switch from BWP 1325 to BWP 1330.

[0116] After a period of time, the network entity 105-b may determine to switch from communications using the network half-duplex time slots 1310 to communications using the network FDM-based full-duplex time slots 1305-b. The network entity 105-b may then send a GC-DCI on the GC-PDCCH 1315-b to trigger a BWP switch from communications using half-duplex to communications using full-duplex. For downlink communications, the GC-DCI may trigger a BWP switch from BWP 1330 to BWP 1320, and for uplink communications, the GC-DCI may trigger a BWP switch from BWP 1330 to BWP 1320.

[0117] Fig.14 An example of a process flow 1400 for supporting group common BWP switching according to one or more aspects of the present disclosure is illustrated. The process flow 1400 includes a UE 115-b, which may be a reference Figures 1 to 13 The process flow 1400 also includes a network entity 105-b, which may be a reference Figures 1 to 13 The process flow 1400 may implement aspects of the wireless communication system 1100. For example, the process flow 1400 may support efficient techniques for coordinating communications between a UE 115-a operating in half-duplex mode and a network entity 105-a operating in full-duplex mode.

[0118] In the following description of process flow 1400, signaling exchanged between UE 115-b and network entity 105-b may be exchanged in a different order than the example order shown, or operations performed by UE 115-b and network entity 105-b may be performed in a different order or at a different time. Some operations may also be omitted from process flow 1400, and other operations may be added to process flow 1400.

[0119] At 1405, UE 115-b may communicate with network entity 105-b on a first BWP. At 1410, network entity 105-b may send and UE 115-b may receive a GC-DCI message indicating that UE 115-b is to communicate with network entity 105-b on a second BWP. The GC-DCI may be for multiple UEs 115 including UE 115-b. In some cases, based on UE 115-b being restricted to communicate on the first BWP, UE 115-b may receive a GC-DCI indicating that UE 115-b is to communicate with network entity 105-b on a second BWP. At 1415, UE 115-b may identify a second BWP on which to communicate with network entity 105-b based on the GC-DCI. At 1420, UE 115-b may then communicate with network entity 105-b on the second BWP based on receiving the GC-DCI message.

[0120] In some examples, the network entity may be triggered to perform a BWP switch based on switching from communication in full-duplex mode to half-duplex mode or vice versa. For example, UE 115-b may communicate with network entity 105-b on a first BWP using FDD in full-duplex mode, and UE 115-b may communicate with network entity 105-b on a second BWP using TDD in half-duplex mode. Alternatively, UE 115-b may communicate with network entity 105-b on a first BWP using TDD in half-duplex mode, and UE 115-b may communicate with network entity 105-b on a second BWP using FDD in full-duplex mode.

[0121] In some examples, UE 115-b may identify a UE-specific field for UE 115-b in a GC-DCI message that indicates a second BWP over which to communicate with network entity 105-b. In some examples, UE 115-b may identify a common field for multiple UEs in a GC-DCI message that indicates a second BWP over which to communicate with network entity 105-b. In some examples, UE 115-b may identify a second BWP over which to communicate with network entity 105-b based on an implicit indication of the second BWP in the GC-DCI message. For example, the GC-DCI may not explicitly indicate the second BWP, but UE 115-b may identify the second BWP based on receiving the GC-DCI. In some examples, UE 115-b may identify a second BWP over which to communicate with network entity 105-b based on a BWP switching pattern. For example, if UE 115-b is communicating with network entity 105-b on a first BWP, the BWP switching pattern may indicate that UE 115-b is to communicate with the network entity on a second BWP after receiving the GC-DCI.

[0122] Fig.15 A block diagram 1500 of a device 1505 supporting uplink and downlink multiplexing for half-duplex devices according to one or more aspects of the present disclosure is shown. The device 1505 may be an example of aspects of the UE 115 as described herein. The device 1505 may include a receiver 1510, a transmitter 1515, and a communication manager 1520. The device 1505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0123] Receiver 1510 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to uplink and downlink multiplexing for half-duplex devices), user data, control information, or any combination thereof. The information may be passed to other components of device 1505. Receiver 1510 may utilize a single antenna or a collection of multiple antennas.

[0124] The transmitter 1515 may provide means for transmitting signals generated by other components of the device 1505. For example, the transmitter 1515 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to uplink and downlink multiplexing for half-duplex devices), user data, control information, or any combination thereof. In some examples, the transmitter 1515 may be co-located with the receiver 1510 in a transceiver module. The transmitter 1515 may utilize a single antenna or a collection of multiple antennas.

[0125] The communication manager 1520, the receiver 1510, the transmitter 1515, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of uplink and downlink multiplexing for half-duplex devices as described herein. For example, the communication manager 1520, the receiver 1510, the transmitter 1515, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0126] In some examples, the communication manager 1520, the receiver 1510, the transmitter 1515, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which is configured to or otherwise supports means for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0127] Additionally or alternatively, in some examples, the communication manager 1520, the receiver 1510, the transmitter 1515, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1520, the receiver 1510, the transmitter 1515, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0128] In some examples, communication manager 1520 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1510, transmitter 1515, or both. For example, communication manager 1520 may receive information from receiver 1510, transmit information to transmitter 1515, or be integrated in conjunction with receiver 1510, transmitter 1515, or both to obtain information, output information, or perform various other operations as described herein.

[0129] According to the examples disclosed herein, the communication manager 1520 may support wireless communication at the UE. For example, the communication manager 1520 may be configured to or otherwise support a component for receiving an indication of a first configuration for downlink communication using at least one time resource from a network entity. The communication manager 1520 may be configured to or otherwise support a component for receiving an indication of a second configuration for uplink communication using the same at least one time resource from a network entity. The communication manager 1520 may be configured to or otherwise support a component for determining whether to receive a downlink message or send an uplink message on at least one time resource based on the first configuration, the second configuration, the UE operating in half-duplex mode, and the network entity operating in full-duplex mode. The communication manager 1520 may be configured to or otherwise support a component for communicating with the network entity based on the determination.

[0130] By including or configuring the communication manager 1520 according to the example described herein, the device 1505 (e.g., a processor that controls the receiver 1510, the transmitter 1515, the communication manager 1520, or a combination thereof or otherwise coupled thereto) can support techniques for reducing power consumption and more efficiently utilizing communication resources. Specifically, since the network entity can configure or schedule the device 1505 to receive downlink messages and send uplink messages on the same time resources, the device 1505 can avoid wasting time resources. For example, if the device 1505 determines to ignore the downlink message, the device 1505 can send an uplink message, and if the device 1505 determines to avoid sending an uplink message, the device 1505 can receive a downlink message. Thus, the communication delay at the device 1505 can be reduced, resulting in reduced power consumption at the device 1505, and the device 1505 can utilize communication resources more efficiently.

[0131] Fig.16 A block diagram 1600 of a device 1605 supporting uplink and downlink multiplexing for half-duplex devices according to one or more aspects of the present disclosure is shown. The device 1605 may be an example of aspects of the device 1505 or UE 115 as described herein. The device 1605 may include a receiver 1610, a transmitter 1615, and a communication manager 1620. The device 1605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0132] Receiver 1610 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to uplink and downlink multiplexing for half-duplex devices), user data, control information, or any combination thereof. The information may be passed to other components of device 1605. Receiver 1610 may utilize a single antenna or a collection of multiple antennas.

[0133] The transmitter 1615 may provide means for transmitting signals generated by other components of the device 1605. For example, the transmitter 1615 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to uplink and downlink multiplexing for half-duplex devices), user data, control information, or any combination thereof. In some examples, the transmitter 1615 may be co-located with the receiver 1610 in a transceiver module. The transmitter 1615 may utilize a single antenna or a collection of multiple antennas.

[0134] Device 1605 or its various components may be examples of components for performing various aspects of uplink and downlink multiplexing for half-duplex devices as described herein. For example, communication manager 1620 may include downlink configuration manager 1625, uplink configuration manager 1630, prioritization manager 1635, half-duplex manager 1640, or any combination thereof. Communication manager 1620 may be an example of various aspects of communication manager 1520 as described herein. In some examples, communication manager 1620 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1610, transmitter 1615, or both. For example, communication manager 1620 may receive information from receiver 1610, transmit information to transmitter 1615, or integrate with receiver 1610, transmitter 1615, or both to obtain information, output information, or perform various other operations as described herein.

[0135] According to the examples disclosed herein, the communication manager 1620 may support wireless communication at the UE. The downlink configuration manager 1625 may be configured to or otherwise support a component for receiving an indication of a first configuration for downlink communication using at least one time resource from a network entity. The uplink configuration manager 1630 may be configured to or otherwise support a component for receiving an indication of a second configuration for uplink communication using the same at least one time resource from a network entity. The prioritization manager 1635 may be configured to or otherwise support a component for determining whether to receive a downlink message or send an uplink message on at least one time resource based on the first configuration, the second configuration, the UE operating in half-duplex mode, and the network entity operating in full-duplex mode. The half-duplex manager 1640 may be configured to or otherwise support a component for communicating with the network entity based on the determination.

[0136] Fig.17 A block diagram 1700 of a communication manager 1720 supporting uplink and downlink multiplexing for half-duplex devices in accordance with one or more aspects of the present disclosure is shown. The communication manager 1720 may be an example of aspects of the communication manager 1520, the communication manager 1620, or both as described herein. The communication manager 1720 or its various components may be examples of components for performing various aspects of uplink and downlink multiplexing for half-duplex devices as described herein. For example, the communication manager 1720 may include a downlink configuration manager 1725, an uplink configuration manager 1730, a prioritization manager 1735, a half-duplex manager 1740, a RACH manager 1745, an RRC manager 1750, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0137] According to the examples disclosed herein, the communication manager 1720 may support wireless communication at the UE. The downlink configuration manager 1725 may be configured to or otherwise support a component for receiving an indication of a first configuration for downlink communication using at least one time resource from a network entity. The uplink configuration manager 1730 may be configured to or otherwise support a component for receiving an indication of a second configuration for uplink communication using the same at least one time resource from a network entity. The prioritization manager 1735 may be configured to or otherwise support a component for determining whether to receive a downlink message or send an uplink message on at least one time resource based on the first configuration, the second configuration, the UE operating in half-duplex mode, and the network entity operating in full-duplex mode. The half-duplex manager 1740 may be configured to or otherwise support a component for communicating with the network entity based on the determination.

[0138] In some examples, to support determining whether to receive a downlink message or send an uplink message on at least one time resource, the prioritization manager 1735 may be configured as or otherwise support a component for determining whether to receive a downlink message or send an uplink message based on a first priority associated with the downlink message and a second priority associated with the uplink message.

[0139] In some examples, a first priority level associated with a downlink message is based on an active transmit configuration indication state at the UE and whether the UE is to perform a beam management process at the UE.

[0140] In some examples, the second priority associated with the uplink message is based on a latency requirement associated with the uplink message.

[0141] In some examples, the RACH manager 1745 may be configured to or otherwise support a component for identifying that the UE has not initiated a random access procedure, wherein at least one time resource includes a valid random access opportunity. In some examples, the half-duplex manager 1740 may be configured to or otherwise support a component for receiving a downlink message on at least one time resource based on identifying that the UE has not initiated a random access procedure.

[0142] In some examples, the RACH manager 1745 may be configured to or otherwise support means for identifying that the UE has initiated a random access procedure, wherein the at least one time resource comprises a valid random access opportunity. In some examples, the half-duplex manager 1740 may be configured to or otherwise support means for sending an uplink message on the at least one time resource based on identifying that the UE has initiated a random access procedure, wherein the uplink message comprises a random access message.

[0143] In some examples, the downlink message includes a synchronization signal block, and the uplink message includes a data message, a control information message, a random access message, or a sounding reference signal.

[0144] In some examples, the downlink message includes a data message, a control information message, or a channel state information reference signal, the uplink message includes a random access message, and at least one time resource includes a valid random access opportunity.

[0145] In some examples, RRC manager 1750 may be configured to or otherwise support components for receiving radio resource control signaling that configures at least one time resource for an uplink, wherein a downlink message scheduled on the at least one time resource comprises a data message, a control information message, or a channel state information reference signal.

[0146] In some examples, RRC manager 1750 may be configured to or otherwise support components for receiving radio resource control signaling that configures at least one time resource for a downlink, wherein an uplink message scheduled on the at least one time resource comprises a data message, a control information message, a random access message, or a sounding reference signal.

[0147] In some examples, the at least one time resource includes a flexible time resource configured for an uplink or a downlink.

[0148] Fig.18 A diagram of a system 1800 including a device 1805 supporting uplink and downlink multiplexing for half-duplex devices according to one or more aspects of the present disclosure is shown. The device 1805 may be an example of a device 1505, a device 1605, or a UE 115 as described herein, or include components thereof. The device 1805 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1805 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1820, an input / output (I / O) controller 1810, a transceiver 1815, an antenna 1825, a memory 1830, a code 1835, and a processor 1840. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1845).

[0149] I / O controller 1810 can manage input and output signals for device 1805. I / O controller 1810 can also manage peripheral devices that are not integrated into device 1805. In some cases, I / O controller 1810 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1810 can utilize an operating system such as or another known operating system. Additionally or alternatively, I / O controller 1810 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1810 may be implemented as part of a processor such as processor 1840. In some cases, a user may interact with device 1805 via I / O controller 1810 or via hardware components controlled by I / O controller 1810.

[0150] In some cases, the device 1805 may include a single antenna 1825. However, in some other cases, the device 1805 may have more than one antenna 1825, which can send or receive multiple wireless transmissions concurrently. The transceiver 1815 can communicate bidirectionally via one or more antennas 1825, wired or wireless links, as described herein. For example, the transceiver 1815 may represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 1815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1825 for transmission; and demodulating packets received from one or more antennas 1825. The transceiver 1815 or the transceiver 1815 and one or more antennas 1825 can be examples of transmitters 1515, transmitters 1615, receivers 1510, receivers 1610, or any combination thereof or components thereof as described herein.

[0151] The memory 1830 may include random access memory (RAM) and read-only memory (ROM). The memory 1830 may store computer-readable, computer-executable code 1835 including instructions that, when executed by the processor 1840, cause the device 1805 to perform various functions described herein. The code 1835 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 1835 may not be directly executable by the processor 1840, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 1830 may also include a basic I / O system (BIOS), etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0152] Processor 1840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1840. Processor 1840 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1830) so that device 1805 performs various functions (e.g., functions or tasks that support uplink and downlink multiplexing for half-duplex devices). For example, device 1805 or a component of device 1805 may include processor 1840 and memory 1830 coupled to or coupled to processor 1840, and processor 1840 and memory 1830 are configured to perform various functions described herein.

[0153] According to the examples disclosed herein, the communication manager 1820 may support wireless communication at the UE. For example, the communication manager 1820 may be configured to or otherwise support a component for receiving an indication of a first configuration for downlink communication using at least one time resource from a network entity. The communication manager 1820 may be configured to or otherwise support a component for receiving an indication of a second configuration for uplink communication using the same at least one time resource from a network entity. The communication manager 1820 may be configured to or otherwise support a component for determining whether to receive a downlink message or send an uplink message on at least one time resource based on the first configuration, the second configuration, the UE operating in half-duplex mode, and the network entity operating in full-duplex mode. The communication manager 1820 may be configured to or otherwise support a component for communicating with the network entity based on the determination.

[0154] By including or configuring a communication manager 1820 according to an example as described herein, the device 1805 can support techniques for reducing power consumption and utilizing communication resources more efficiently. Specifically, since the network entity can configure or schedule the device 1805 to receive a downlink message and send an uplink message on the same time resource, the device 1805 can avoid wasting time resources. For example, if the device 1805 determines to ignore the downlink message, the device 1805 can send an uplink message, and if the device 1805 determines to avoid sending an uplink message, the device 1805 can receive a downlink message. Thus, the communication delay at the device 1805 can be reduced, resulting in reduced power consumption at the device 1805, and the device 1805 can utilize communication resources more efficiently.

[0155] In some examples, the communication manager 1820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1815, one or more antennas 1825, or any combination thereof. Although the communication manager 1820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1820 may be supported or performed by the processor 1840, the memory 1830, the code 1835, or any combination thereof. For example, the code 1835 may include instructions executable by the processor 1840 to cause the device 1805 to perform various aspects of uplink and downlink multiplexing for half-duplex devices as described herein, or the processor 1840 and the memory 1830 may be otherwise configured to perform or support such operations.

[0156] Fig.19A block diagram 1900 of a device 1905 supporting uplink and downlink multiplexing for half-duplex devices according to one or more aspects of the present disclosure is shown. The device 1905 may be an example of aspects of the network entity 105 as described herein. The device 1905 may include a receiver 1910, a transmitter 1915, and a communication manager 1920. The device 1905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0157] Receiver 1910 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1905. In some examples, receiver 1910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0158] The transmitter 1915 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1905. For example, the transmitter 1915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)). In some examples, the transmitter 1915 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1915 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1915 and the receiver 1910 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0159] The communication manager 1920, the receiver 1910, the transmitter 1915, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of uplink and downlink multiplexing for half-duplex devices as described herein. For example, the communication manager 1920, the receiver 1910, the transmitter 1915, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0160] In some examples, the communication manager 1920, the receiver 1910, the transmitter 1915, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described herein. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0161] Additionally or alternatively, in some examples, the communication manager 1920, the receiver 1910, the transmitter 1915, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functions of the communication manager 1920, the receiver 1910, the transmitter 1915, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0162] In some examples, communication manager 1920 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1910, transmitter 1915, or both. For example, communication manager 1920 may receive information from receiver 1910, transmit information to transmitter 1915, or be integrated in conjunction with receiver 1910, transmitter 1915, or both to obtain information, output information, or perform various other operations as described herein.

[0163] The communication manager 1920 may support wireless communications at a network entity according to the examples disclosed herein. For example, the communication manager 1920 may be configured to or otherwise support a component for sending an indication of a first configuration for downlink communication using at least one time resource to a first set of UEs operating in half-duplex mode. The communication manager 1920 may be configured to or otherwise support a component for sending an indication of a second configuration for uplink communication using at least one time resource to a second set of UEs, wherein the first set of UEs and the second set of UEs are at least partially overlapping sets. The communication manager 1920 may be configured to or otherwise support a component for monitoring at least one uplink message from at least one UE in the second set of UEs on at least one time resource based on a network entity operating in full-duplex mode. The communication manager 1920 may be configured to or otherwise support a component for sending one or more downlink messages to one or more UEs in the first set of UEs on at least one time resource based on a network entity operating in full-duplex mode.

[0164] By including or configuring the communication manager 1920 according to the example as described herein, the device 1905 (e.g., a processor that controls the receiver 1910, the transmitter 1915, the communication manager 1920, or a combination thereof or otherwise coupled thereto) can support techniques for reducing power consumption and more efficiently utilizing communication resources. Specifically, since the device 1905 can be configured or scheduled to receive downlink messages and send uplink messages on the same time resources, the device 1905 can avoid wasting time resources. For example, if the UE determines to ignore the downlink message, the UE can send an uplink message, and if the UE determines to avoid sending an uplink message, the UE can receive a downlink message. Thus, the communication delay at the device 1905 and the UE can be reduced, thereby resulting in reduced power consumption at the device 1905, and the device 1905 can utilize communication resources more efficiently.

[0165] Fig. 20 A block diagram 2000 of a device 2005 supporting uplink and downlink multiplexing for half-duplex devices according to one or more aspects of the present disclosure is shown. The device 2005 may be an example of aspects of the device 1905 or the network entity 105 as described herein. The device 2005 may include a receiver 2010, a transmitter 2015, and a communication manager 2020. The device 2005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0166] The receiver 2010 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 2005. In some examples, the receiver 2010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 2010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0167] The transmitter 2015 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 2005. For example, the transmitter 2015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)). In some examples, the transmitter 2015 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 2015 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 2015 and the receiver 2010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0168] Device 2005 or its various components may be examples of components for performing various aspects of uplink and downlink multiplexing for half-duplex devices as described herein. For example, communication manager 2020 may include downlink configuration manager 2025, uplink configuration manager 2030, full-duplex manager 2035, or any combination thereof. Communication manager 2020 may be an example of various aspects of communication manager 1920 as described herein. In some examples, communication manager 2020 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise in conjunction with receiver 2010, transmitter 2015, or both. For example, communication manager 2020 may receive information from receiver 2010, transmit information to transmitter 2015, or integrate with receiver 2010, transmitter 2015, or both to obtain information, output information, or perform various other operations as described herein.

[0169] The communication manager 2020 may support wireless communication at a network entity according to an example as disclosed herein. The downlink configuration manager 2025 may be configured to or otherwise support a component for sending an indication of a first configuration for downlink communication using at least one time resource to a first set of UEs operating in half-duplex mode. The uplink configuration manager 2030 may be configured to or otherwise support a component for sending an indication of a second configuration for uplink communication using at least one time resource to a second set of UEs, wherein the first set of UEs and the second set of UEs are at least partially overlapping sets. The full-duplex manager 2035 may be configured to or otherwise support a component for monitoring at least one uplink message from at least one UE in the second set of UEs on at least one time resource based on a network entity operating in full-duplex mode. The full-duplex manager 2035 may be configured to or otherwise support a component for sending one or more downlink messages to one or more UEs in the first set of UEs on at least one time resource based on a network entity operating in full-duplex mode.

[0170] Fig.21 A block diagram 2100 of a communication manager 2120 supporting uplink and downlink multiplexing for half-duplex devices according to one or more aspects of the present disclosure is shown. The communication manager 2120 may be an example of aspects of the communication manager 1920, the communication manager 2020, or both as described herein. The communication manager 2120 or its various components may be examples of components for performing various aspects of uplink and downlink multiplexing for half-duplex devices as described herein. For example, the communication manager 2120 may include a downlink configuration manager 2125, an uplink configuration manager 2130, a full-duplex manager 2135, an RRC manager 2140, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0171] The communication manager 2120 may support wireless communications at a network entity according to an example as disclosed herein. The downlink configuration manager 2125 may be configured to or otherwise support a component for sending an indication of a first configuration for downlink communication using at least one time resource to a first set of UEs operating in half-duplex mode. The uplink configuration manager 2130 may be configured to or otherwise support a component for sending an indication of a second configuration for uplink communication using at least one time resource to a second set of UEs, wherein the first set of UEs and the second set of UEs are at least partially overlapping sets. The full-duplex manager 2135 may be configured to or otherwise support a component for monitoring at least one uplink message from at least one UE in the second set of UEs on at least one time resource based on a network entity operating in full-duplex mode. In some examples, the full-duplex manager 2135 may be configured to or otherwise support a component for sending one or more downlink messages to one or more UEs in the first set of UEs on at least one time resource based on a network entity operating in full-duplex mode.

[0172] In some examples, one or more downlink messages include a synchronization signal block, and at least one uplink message includes a data message, a control information message, a random access message, or a sounding reference signal.

[0173] In some examples, one or more downlink messages include a data message, a control information message, or a channel state information reference signal, or a combination thereof, at least one uplink message includes a random access message, and at least one time resource includes a valid random access opportunity.

[0174] In some examples, the RRC manager 2140 may be configured to or otherwise support components for sending radio resource control signaling that configures at least one time resource for an uplink, wherein one or more downlink messages scheduled on the at least one time resource include a data message, a control information message, a channel state information reference signal, or a combination thereof.

[0175] In some examples, the RRC manager 2140 may be configured to or otherwise support components for sending radio resource control signaling that configures at least one time resource for a downlink, wherein at least one uplink message scheduled on the at least one time resource comprises a data message, a control information message, a random access message, or a sounding reference signal.

[0176] In some examples, the at least one time resource includes a flexible time resource configured for an uplink or a downlink.

[0177] Fig. 22A diagram of a system 2200 including a device 2205 supporting uplink and downlink multiplexing for half-duplex devices according to one or more aspects of the present disclosure is shown. The device 2205 may be an example of a device 1905, a device 2005, or a network entity 105 as described herein, or include components thereof. The device 2205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 2205 may include components that support output and acquisition of communications, such as a communication manager 2220, a transceiver 2210, an antenna 2215, a memory 2225, a code 2230, and a processor 2235. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 2240).

[0178] The transceiver 2210 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 2210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 2210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 2205 may include one or more antennas 2215 capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 2210 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., through one or more antennas 2215, through a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 2215, from a wired receiver); and demodulating the signal. The transceiver 2210 or transceiver 2210 and one or more antennas 2215 or wired interfaces (where applicable) may be examples of transmitter 1915, transmitter 2015, receiver 1910, receiver 2010, or any combination thereof or any components thereof as described herein. In some examples, the transceiver may be operable to support communications via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0179] The memory 2225 may include RAM and ROM. The memory 2225 may store computer-readable, computer-executable code 2230 including instructions that, when executed by the processor 2235, cause the device 2205 to perform various functions described herein. The code 2230 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 2230 may not be directly executable by the processor 2235, but may (for example, when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 2225 may include a BIOS, etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0180] The processor 2235 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 2235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 2235. The processor 2235 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 2225) so that the device 2205 performs various functions (e.g., functions or tasks that support uplink and downlink multiplexing for half-duplex devices). For example, the device 2205 or a component of the device 2205 may include a processor 2235 and a memory 2225 coupled to the processor 2235, and the processor 2235 and the memory 2225 are configured to perform the various functions described herein. Processor 2235 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality for performing functions of device 2205 (e.g., by executing code 2230).

[0181] In some examples, bus 2240 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 2240 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 2205, or communications performed between different components of device 2205 that may be co-located or located in different locations (e.g., where device 2205 may refer to a system in which one or more of communication manager 2220, transceiver 2210, memory 2225, code 2230, and processor 2235 may be located in one of these different components or divided between different components).

[0182] In some examples, the communication manager 2220 may manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 2220 may manage the delivery of data communications for client devices, such as one or more UEs 115. In some examples, the communication manager 2220 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with the UEs 115 in coordination with the other network entities 105. In some examples, the communication manager 2220 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0183] The communication manager 2220 may support wireless communications at a network entity according to an example as disclosed herein. For example, the communication manager 2220 may be configured to or otherwise support a component for sending an indication of a first configuration for downlink communication using at least one time resource to a first set of user equipment (UE) operating in half-duplex mode. The communication manager 2220 may be configured to or otherwise support a component for sending an indication of a second configuration for uplink communication using at least one time resource to a second set of UEs, wherein the first set of UEs and the second set of UEs are at least partially overlapping sets. The communication manager 2220 may be configured to or otherwise support a component for monitoring at least one uplink message from at least one UE in the second set of UEs on at least one time resource based on a network entity operating in full-duplex mode. The communication manager 2220 may be configured to or otherwise support a component for sending one or more downlink messages to one or more UEs in the first set of UEs on at least one time resource based on a network entity operating in full-duplex mode.

[0184] By including or configuring the communication manager 2220 according to the example as described herein, the device 2205 can support the technology for reducing power consumption and utilizing communication resources more efficiently. Specifically, since the device 2205 can be configured or scheduled to receive downlink messages and send uplink messages on the same time resources, the device 2205 can avoid wasting time resources. For example, if the UE determines to ignore the downlink message, the UE can send an uplink message, and if the UE determines to avoid sending an uplink message, the UE can receive a downlink message. Thus, the communication delay at the device 2205 and the UE can be reduced, thereby causing the reduced power consumption at the device 2205, and the device 2205 can utilize communication resources more efficiently.

[0185] In some examples, the communication manager 2220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 2210, one or more antennas 2215 (e.g., where applicable), or any combination thereof. Although the communication manager 2220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 2220 may be supported or performed by the processor 2235, the memory 2225, the code 2230, the transceiver 2210, or any combination thereof. For example, the code 2230 may include instructions executable by the processor 2235 to cause the device 2205 to perform various aspects of uplink and downlink multiplexing for half-duplex devices as described herein, or the processor 2235 and the memory 2225 may be otherwise configured to perform or support such operations.

[0186] Fig.23 A flowchart illustrating a method 2300 for supporting uplink and downlink multiplexing for half-duplex devices according to one or more aspects of the present disclosure is shown. The operations of the method 2300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 2300 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 18 The UE 115 described herein performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0187] At 2305, the method may include receiving an indication of a first configuration for utilizing at least one time resource for downlink communication from a network entity. The operations of 2305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2305 may be performed as described in reference to Fig.17 The downlink configuration manager 1725 executes.

[0188] At 2310, the method may include receiving an indication of a second configuration for utilizing the same at least one time resource for uplink communication from a network entity. The operations of 2310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2310 may be performed as described in reference to Fig.17 The uplink configuration manager 1730 executes.

[0189] At 2315, the method may include determining whether to receive a downlink message or send an uplink message on at least one time resource based on the first configuration, the second configuration, the UE operating in half-duplex mode, and the network entity operating in full-duplex mode. The operations of 2315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2315 may be performed as described in reference to Fig.17The prioritization manager 1735 executes.

[0190] At 2320, the method may include communicating with a network entity based on the determination. The operations of 2320 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2320 may be performed as described in reference to Fig.17 The half-duplex manager 1740 executes.

[0191] Fig.24 A flow chart illustrating a method 2400 for supporting uplink and downlink multiplexing for half-duplex devices according to one or more aspects of the present disclosure is shown. The operations of the method 2400 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2400 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 14 and Figures 19 to 22 The network entity performs. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0192] At 2405, the method may include sending an indication of a first configuration for utilizing at least one time resource for downlink communication to a first set of UEs operating in half-duplex mode. The operations of 2405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2405 may be performed as described in reference to Fig.21 The downlink configuration manager 2125 executes.

[0193] At 2410, the method may include sending an indication of a second configuration for uplink communication utilizing at least one time resource to a second set of UEs, wherein the first set of UEs and the second set of UEs are at least partially overlapping sets. The operations of 2410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2410 may be performed as described in reference to Fig.21 The uplink configuration manager 2130 executes.

[0194] At 2415, the method may include monitoring at least one uplink message from at least one UE in the second set of UEs on at least one time resource based on the network entity operating in full-duplex mode. The operations of 2415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2415 may be performed as described in reference to Fig.21 The half-duplex manager 2135 executes.

[0195] At 2420, the method may include sending one or more downlink messages to one or more UEs in the first set of UEs on at least one time resource based on the network entity operating in full-duplex mode. The operations of 2420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2420 may be performed as described in reference to Fig.21 The half-duplex manager 2135 executes.

[0196] The following provides an overview of various aspects of the disclosure:

[0197] Aspect 1: A method for performing wireless communications at a UE, the method comprising: receiving an indication of a first configuration for performing downlink communications using at least one time resource from a network entity; receiving an indication of a second configuration for performing uplink communications using the same at least one time resource from the network entity; determining whether to receive a downlink message or send an uplink message on the at least one time resource based at least in part on the first configuration, the second configuration, the UE operating in half-duplex mode, and the network entity operating in full-duplex mode; and communicating with the network entity based on the determination.

[0198] Aspect 2: A method according to Aspect 1, wherein determining whether to receive the downlink message or send the uplink message on the at least one time resource includes: determining whether to receive the downlink message or send the uplink message based at least in part on a first priority associated with the downlink message and a second priority associated with the uplink message.

[0199] Aspect 3: A method according to aspect 2, wherein the first priority associated with the downlink message is at least partially based on an active transmission configuration indication state at the UE and whether the UE is to perform a beam management process at the UE.

[0200] Aspect 4: The method according to any one of aspects 2 to 3, wherein the second priority associated with the uplink message is based at least in part on a latency requirement associated with the uplink message.

[0201] Aspect 5: According to the method described in any one of Aspects 1 to 4, the method further includes: identifying that the UE has not yet initiated a random access process, wherein the at least one time resource includes a valid random access opportunity; and receiving the downlink message on the at least one time resource based at least in part on identifying that the UE has not yet initiated the random access process.

[0202] Aspect 6: According to the method described in any one of Aspects 1 to 5, the method further includes: identifying that the UE has initiated a random access process, wherein the at least one time resource includes a valid random access opportunity; and sending the uplink message on the at least one time resource at least partially based on identifying that the UE has initiated the random access process, wherein the uplink message includes a random access message.

[0203] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the downlink message includes a synchronization signal block, and the uplink message includes a data message, a control information message, a random access message or a sounding reference signal.

[0204] Aspect 8: A method according to any one of Aspects 1 to 7, wherein the downlink message includes a data message, a control information message or a channel state information reference signal, the uplink message includes a random access message, and the at least one time resource includes a valid random access opportunity.

[0205] Aspect 9: According to the method described in any one of Aspects 1 to 8, the method further includes: receiving radio resource control signaling that configures the at least one time resource for an uplink, wherein the downlink message scheduled on the at least one time resource includes a data message, a control information message, or a channel state information reference signal.

[0206] Aspect 10: According to the method described in any one of Aspects 1 to 9, the method further includes: receiving radio resource control signaling that configures the at least one time resource for a downlink, wherein the uplink message scheduled on the at least one time resource includes a data message, a control information message, a random access message, or a sounding reference signal.

[0207] Aspect 11: The method according to any one of aspects 1 to 10, wherein the at least one time resource comprises a flexible time resource configured for uplink or downlink.

[0208] Aspect 12: A method for performing wireless communications at a network entity, the method comprising: sending an indication of a first configuration for performing downlink communications utilizing at least one time resource to a first set of user equipment (UE) operating in half-duplex mode; sending an indication of a second configuration for performing uplink communications utilizing the at least one time resource to a second set of UEs, wherein the first set of UEs and the second set of UEs are at least partially overlapping sets; monitoring at least one uplink message from at least one UE in the second set of UEs on the at least one time resource based at least in part on the network entity operating in full-duplex mode; and sending one or more downlink messages to one or more UEs in the first set of UEs on the at least one time resource based at least in part on the network entity operating in full-duplex mode.

[0209] Aspect 13: The method according to aspect 12, wherein the one or more downlink messages include a synchronization signal block, and the at least one uplink message includes a data message, a control information message, a random access message or a sounding reference signal.

[0210] Aspect 14: A method according to any one of Aspects 12 to 13, wherein the one or more downlink messages include a data message, a control information message, or a channel state information reference signal, or a combination thereof, the at least one uplink message includes a random access message, and the at least one time resource includes a valid random access opportunity.

[0211] Aspect 15: According to the method described in any one of Aspects 12 to 14, the method further includes: sending radio resource control signaling to configure the at least one time resource for uplink, wherein the one or more downlink messages scheduled on the at least one time resource include data messages, control information messages, channel state information reference signals, or a combination thereof.

[0212] Aspect 16: According to the method described in any one of Aspects 12 to 15, the method further includes: sending radio resource control signaling to configure the at least one time resource for a downlink, wherein the at least one uplink message scheduled on the at least one time resource includes a data message, a control information message, a random access message, or a sounding reference signal.

[0213] Aspect 17: The method according to any one of aspects 12 to 16, wherein the at least one time resource comprises a flexible time resource configured for uplink or downlink.

[0214] Aspect 18: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 11.

[0215] Aspect 19: An apparatus for wireless communication at a UE, the apparatus comprising at least one means for performing the method according to any one of aspects 1 to 11.

[0216] Aspect 20: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 11.

[0217] Aspect 21: An apparatus for performing wireless communications at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 12 to 17.

[0218] Aspect 22: An apparatus for wireless communication at a network entity, the apparatus comprising at least one means for performing the method according to any one of aspects 12 to 17.

[0219] Aspect 23: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 12 to 17.

[0220] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0221] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0222] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0223] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0224] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent on a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0225] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that promotes computer program to be transmitted from one place to another.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code member and can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure Any other non-transient medium.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0226] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on".

[0227] The term "determining" encompasses a wide variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, searching (such as via searching in a table, database, or other data structure), ascertaining, and similar actions. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), and similar actions. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0228] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label regardless of the second reference label or other subsequent reference labels.

[0229] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration" and does not mean "preferred" or "having advantages over other examples". The specific implementation includes specific details to provide an understanding of the technology. However, these technologies can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples.

[0230] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving, from a network entity, an indication of a first configuration for utilizing at least one time resource for downlink communications; receiving, from the network entity, an indication of a second configuration for utilizing the same at least one time resource for uplink communications; determining whether to receive a downlink message or send an uplink message on the at least one time resource based at least in part on the first configuration, the second configuration, the UE operating in half-duplex mode, and the network entity operating in full-duplex mode; as well as Communicating with the network entity based on the determination.

2. The apparatus of claim 1 , wherein the instructions for determining whether to receive the downlink message or send the uplink message on the at least one time resource are executable by the processor so that the apparatus: A determination is made whether to receive the downlink message or to send the uplink message based at least in part on a first priority level associated with the downlink message and a second priority level associated with the uplink message.

3. An apparatus according to claim 2, wherein the first priority associated with the downlink message is based at least in part on an active transmission configuration indication state at the UE and whether the UE is to perform a beam management process at the UE.

4. The apparatus of claim 2, wherein the second priority associated with the uplink message is based at least in part on a latency requirement associated with the uplink message.

5. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: identifying that the UE has not initiated a random access procedure, wherein the at least one time resource includes a valid random access opportunity; and The downlink message is received on the at least one time resource based at least in part on identifying that the UE has not initiated the random access procedure.

6. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: identifying that the UE has initiated a random access procedure, wherein the at least one time resource includes a valid random access opportunity; and Based at least in part on identifying that the UE has initiated the random access procedure, sending the uplink message on the at least one time resource, wherein the uplink message comprises a random access message.

7. The apparatus of claim 1, wherein the downlink message comprises a synchronization signal block, and the uplink message comprises a data message, a control information message, a random access message, or a sounding reference signal.

8. The apparatus of claim 1, wherein the downlink message comprises a data message, a control information message, or a channel state information reference signal, the uplink message comprises a random access message, and the at least one time resource comprises a valid random access opportunity.

9. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: Radio resource control signaling is received to configure the at least one time resource for uplink, wherein the downlink message scheduled on the at least one time resource comprises a data message, a control information message, or a channel state information reference signal.

10. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: A radio resource control signaling is received to configure the at least one time resource for downlink, wherein the uplink message scheduled on the at least one time resource comprises a data message, a control information message, a random access message, or a sounding reference signal.

11. The apparatus of claim 1, wherein the at least one time resource comprises a flexible time resource configured for uplink or downlink.

12. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending an indication of a first configuration for downlink communication utilizing at least one time resource to a first set of user equipment (UE) operating in half-duplex mode; sending an indication of a second configuration for utilizing the at least one time resource for uplink communication to a second set of UEs, wherein the first set of UEs and the second set of UEs are at least partially overlapping sets; monitoring, based at least in part on the network entity operating in full-duplex mode, at least one uplink message from at least one UE in the second set of UEs on the at least one time resource; as well as Based at least in part on the network entity operating in full-duplex mode, one or more downlink messages are sent to one or more UEs in the first set of UEs on the at least one time resource.

13. The apparatus of claim 12, wherein the one or more downlink messages comprise a synchronization signal block, and the at least one uplink message comprises a data message, a control information message, a random access message, or a sounding reference signal.

14. The apparatus of claim 12, wherein the one or more downlink messages comprise a data message, a control information message, or a channel state information reference signal, or a combination thereof, the at least one uplink message comprises a random access message, and the at least one time resource comprises a valid random access opportunity.

15. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: Radio resource control signaling is sent to configure the at least one time resource for uplink, wherein the one or more downlink messages scheduled on the at least one time resource include data messages, control information messages, channel state information reference signals, or a combination thereof.

16. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: Radio resource control signaling is sent to configure the at least one time resource for downlink, wherein the at least one uplink message scheduled on the at least one time resource comprises a data message, a control information message, a random access message, or a sounding reference signal.

17. The apparatus of claim 12, wherein the at least one time resource comprises a flexible time resource configured for uplink or downlink.

18. A method for wireless communication at a user equipment (UE), the method comprising: receiving, from a network entity, an indication of a first configuration for utilizing at least one time resource for downlink communications; receiving, from the network entity, an indication of a second configuration for utilizing the same at least one time resource for uplink communications; determining whether to receive a downlink message or send an uplink message on the at least one time resource based at least in part on the first configuration, the second configuration, the UE operating in half-duplex mode, and the network entity operating in full-duplex mode; as well as Communicating with the network entity based on the determination.

19. The method of claim 18, wherein determining whether to receive the downlink message or send the uplink message on the at least one time resource comprises: A determination is made whether to receive the downlink message or to send the uplink message based at least in part on a first priority level associated with the downlink message and a second priority level associated with the uplink message.

20. The method of claim 19, wherein the first priority associated with the downlink message is based at least in part on an active transmission configuration indication state at the UE and whether the UE is to perform a beam management procedure at the UE.

21. The method of claim 19, wherein the second priority associated with the uplink message is based at least in part on a latency requirement associated with the uplink message.

22. The method according to claim 18, further comprising: identifying that the UE has not initiated a random access procedure, wherein the at least one time resource includes a valid random access opportunity; as well as The downlink message is received on the at least one time resource based at least in part on identifying that the UE has not initiated the random access procedure.

23. The method according to claim 18, further comprising: identifying that the UE has initiated a random access procedure, wherein the at least one time resource includes a valid random access opportunity; as well as Based at least in part on identifying that the UE has initiated the random access procedure, sending the uplink message on the at least one time resource, wherein the uplink message comprises a random access message.

24. The method of claim 18, wherein the downlink message comprises a synchronization signal block, and the uplink message comprises a data message, a control information message, a random access message, or a sounding reference signal.

25. The method of claim 18, wherein the downlink message comprises a data message, a control information message, or a channel state information reference signal, the uplink message comprises a random access message, and the at least one time resource comprises a valid random access opportunity.

26. The method of claim 18, further comprising: Radio resource control signaling is received to configure the at least one time resource for uplink, wherein the downlink message scheduled on the at least one time resource comprises a data message, a control information message, or a channel state information reference signal.

27. The method according to claim 18, further comprising: A radio resource control signaling is received to configure the at least one time resource for downlink, wherein the uplink message scheduled on the at least one time resource comprises a data message, a control information message, a random access message, or a sounding reference signal.

28. The method of claim 18, wherein the at least one time resource comprises a flexible time resource configured for uplink or downlink.

29. A method for wireless communication at a network entity, the method comprising: sending an indication of a first configuration for downlink communication utilizing at least one time resource to a first set of user equipment (UE) operating in half-duplex mode; sending an indication of a second configuration for utilizing the at least one time resource for uplink communication to a second set of UEs, wherein the first set of UEs and the second set of UEs are at least partially overlapping sets; monitoring, based at least in part on the network entity operating in full-duplex mode, at least one uplink message from at least one UE in the second set of UEs on the at least one time resource; as well as Based at least in part on the network entity operating in full-duplex mode, one or more downlink messages are sent to one or more UEs in the first set of UEs on the at least one time resource.

30. The method of claim 29, wherein the one or more downlink messages comprise a synchronization signal block, and the at least one uplink message comprises a data message, a control information message, a random access message, or a sounding reference signal.

Images