Network indication of full duplex capability

Abstract

Methods, systems, and devices for wireless communication are described. Some wireless communication systems may support network indication of full duplex capability. For example, a user equipment (UE) may receive a capability message from a network entity indicating that the network entity supports one or more modes of a full duplex communication scheme. The capability message may be associated with an access procedure between the UE and the network entity, and the UE may perform the access procedure with the network entity. The UE may communicate with the network entity based on the access procedure and the one or more modes associated with the full duplex communication scheme supported by the network entity.

Description

[0001] Cross-references

[0002] This patent application claims the benefit of U.S. patent application No. 17 / 744,435, entitled “NETWORK INDICATION OF FULL-DUPLEX CAPABILITY,” filed by Abotabl et al. on May 13, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including network indication of full-duplex capability. Background Art

[0004] 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).

[0005] 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). In some wireless communication systems, the one or more network entities may support a full-duplex communication scheme. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices and apparatuses for supporting network indication of full-duplex capability. Generally speaking, the technology described herein allows a user equipment (UE) to receive an indication of the full-duplex capability of a network entity. For example, the UE may receive a capability message from the network entity indicating that the network entity supports one or more modes of a full-duplex communication scheme. The one or more modes may include a non-overlapping sub-band full-duplex mode, a partially overlapping sub-band full-duplex mode, a completely overlapping sub-band full-duplex mode, or any combination thereof. In some aspects, the capability message may be associated with an access procedure between the UE and the network entity, so that the UE may perform the access procedure with the network entity and may establish communication based on one or more full-duplex modes supported by the network entity. For example, the UE may communicate with the network entity based on the access procedure and the network entity supporting the one or more modes associated with the full-duplex communication scheme.

[0007] In some cases, the capability message may include a system information message, wherein the system information message indicates that the network entity supports the one or more modes of the full-duplex communication scheme. In some other cases, the capability message may include a downlink message or a control message associated with a random access procedure, wherein the downlink message or the control message indicates that the network entity supports the one or more modes of the full-duplex communication scheme. In some other cases, the capability message may include a control message associated with a handover procedure, wherein the control message indicates that the network entity supports the one or more modes of the full-duplex communication scheme.

[0008] A method for wireless communication at a UE is described. The method may include: receiving a capability message from a network entity indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the UE and the network entity; performing the access procedure with the network entity; and communicating with the network entity based on the access procedure and the network entity supporting the one or more modes associated with the full-duplex communication scheme.

[0009] 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 may be executable by the processor to cause the apparatus to: receive a capability message from a network entity indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the UE and the network entity; perform the access procedure with the network entity; and communicate with the network entity based on the access procedure and the network entity supporting the one or more modes associated with the full-duplex communication scheme.

[0010] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for receiving a capability message from a network entity indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the UE and the network entity; a component for performing the access procedure with the network entity; and a component for communicating with the network entity based on the access procedure and the network entity supporting the one or more modes associated with the full-duplex communication scheme.

[0011] 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 perform the following actions: receiving a capability message from a network entity indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the UE and the network entity; performing the access procedure with the network entity; and communicating with the network entity based on the access procedure and the network entity supporting the one or more modes associated with the full-duplex communication scheme.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the capability message may include operations, features, components, or instructions for the following actions: receiving a system information message indicating that the network entity supports the one or more modes of the full-duplex communication scheme, the capability message including the system information message.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the system information message includes one or more bits indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for decoding the system information message, wherein one or more portions of the system information may be encoded with an indication of the one or more modes that the network entity supports the full-duplex communication scheme.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the system information message indicates one or more parameters associated with a public service cell configuration, the one or more parameters indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the system information message includes one or more fields of a common uplink / downlink configuration indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the system information message includes an indication of an initial bandwidth portion, the indication of the initial bandwidth portion indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the system information message includes one or more bits indicating that the network entity supports the one or more modes of the full-duplex communication scheme, and the system information message is associated with a system information block (SIB) for cell reselection.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the system information message includes a master information block (MIB) or a SIB.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the capability message may include operations, features, components, or instructions for the following actions: as part of a random access procedure, receiving a downlink message indicating that the network entity supports the one or more modes of the full-duplex communication scheme, wherein the capability message includes the downlink message and the access procedure includes the random access procedure.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the downlink message includes one or more reserved bits indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the downlink message may include operations, features, components, or instructions for: sending a first message including a random access request as part of the random access process; and receiving the downlink message including a random access preamble identifier (RAPID) in response to the random access request, wherein the value of the RAPID indicates that the network entity supports the one or more modes of the full-duplex communication scheme.

[0023] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, each of the one or more modes may be associated with one or more RAPIDs.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the capability message may include operations, features, components, or instructions for the following actions: as part of a random access procedure, receiving a control message that schedules a downlink message associated with the random access procedure, wherein one or more bits of the control message indicate that the network entity supports the one or more modes of the full-duplex communication scheme, and the control message includes the capability message.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the capability message may include operations, features, components, or instructions for the following actions: receiving a control message associated with a handover process, wherein the control message indicates that one or more other network entities support the one or more modes of the full-duplex communication scheme.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more modes include a non-overlapping sub-band full-duplex mode, a partially overlapping sub-band full-duplex mode, a fully overlapping sub-band full-duplex mode, or any combination thereof.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the capability message indicates that the network entity supports the partially overlapping sub-band full-duplex mode, and the methods, apparatus, and non-transitory computer-readable media may include additional operations, features, components, or instructions for the following actions: based on the network entity supporting the partially overlapping sub-band full-duplex mode, determining that the network entity supports the non-overlapping sub-band full-duplex mode and the partially overlapping sub-band full-duplex mode.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the capability message indicates that the network entity supports the fully overlapping sub-band full-duplex mode, and the methods, apparatus, and non-transitory computer-readable media may include additional operations, features, components, or instructions for the following actions: based on the network entity supporting the fully overlapping sub-band full-duplex mode, determining that the network entity supports the non-overlapping sub-band full-duplex mode, the partially overlapping sub-band full-duplex mode, and the fully overlapping sub-band full-duplex mode.

[0029] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a message indicating the UE's ability to support the one or more modes associated with the full-duplex communication scheme, wherein the message may be sent in response to the capability message.

[0030] A method of wireless communication at a network entity is described. The method may include: sending a capability message indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the network entity and a UE; performing the access procedure with the UE; and communicating with the UE based on the access procedure and the network entity supporting the one or more modes associated with the full-duplex communication scheme.

[0031] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: send a capability message indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the network entity and a UE; perform the access procedure with the UE; and communicate with the UE based on the access procedure and the network entity supporting the one or more modes associated with the full-duplex communication scheme.

[0032] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for sending a capability message indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the network entity and a UE; means for performing the access procedure with the UE; and means for communicating with the UE based on the access procedure and the network entity supporting the one or more modes associated with the full-duplex communication scheme.

[0033] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to perform the following actions: sending a capability message indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the network entity and a UE; performing the access procedure with the UE; and communicating with the UE based on the access procedure and the network entity supporting the one or more modes associated with the full-duplex communication scheme.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the capability message may include operations, features, components, or instructions for the following actions: broadcasting a system information message indicating that the network entity supports the one or more modes of the full-duplex communication scheme to one or more UEs including the UE, the capability message including the system information message.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the system information message includes one or more bits indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

[0036] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for encoding one or more portions of system information with an indication that the network entity supports the one or more modes of the full-duplex communication scheme, wherein the system information message includes the one or more portions of the system information encoded with the indication.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the system information message indicates one or more parameters associated with a public service cell configuration, the one or more parameters indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the system information message includes one or more fields of a common uplink / downlink configuration indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the system information message includes an indication of an initial bandwidth portion, the indication of the initial bandwidth portion indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the system information message includes one or more bits indicating that the network entity supports the one or more modes of the full-duplex communication scheme, and the system information message is associated with a SIB for cell reselection.

[0041] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the capability message may include operations, features, components, or instructions for the following actions: as part of a random access procedure, sending a downlink message indicating that the network entity supports the one or more modes of the full-duplex communication scheme, wherein the capability message includes the downlink message and the access procedure includes the random access procedure.

[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the downlink message includes one or more reserved bits indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

[0043] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the downlink message may include operations, features, components, or instructions for: receiving a first message including a random access request as part of the random access process; and sending the downlink message including a RAPID in response to the random access request, wherein the value of the RAPID indicates that the network entity supports the one or more modes of the full-duplex communication scheme.

[0044] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, each of the one or more modes may be associated with one or more RAPIDs.

[0045] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the capability message may include operations, features, components, or instructions for the following actions: as part of a random access procedure, sending a control message that schedules a downlink message associated with the random access procedure, wherein one or more bits of the control message indicate that the network entity supports the one or more modes of the full-duplex communication scheme.

[0046] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the capability message may include operations, features, components, or instructions for the following actions: sending a control message associated with the handover process, wherein the control message indicates that one or more other network entities support the one or more modes of the full-duplex communication scheme.

[0047] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more modes include a non-overlapping sub-band full-duplex mode, a partially overlapping sub-band full-duplex mode, a fully overlapping sub-band full-duplex mode, or any combination thereof.

[0048] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving a message indicating the ability of the UE to support the one or more modes associated with the full-duplex communication scheme, the one or more modes including a non-overlapping sub-band full-duplex mode, a partially overlapping sub-band full-duplex mode, a fully overlapping sub-band full-duplex mode, or any combination thereof, wherein the message may be received in response to the capability message.

[0049] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message indicates that the UE supports the partially overlapping sub-band full-duplex mode, and the methods, apparatus, and non-transitory computer-readable media may include additional operations, features, components, or instructions for the following actions: based on the UE supporting the partially overlapping sub-band full-duplex mode, determining that the UE supports the non-overlapping sub-band full-duplex mode and the partially overlapping sub-band full-duplex mode.

[0050] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the capability message indicates that the UE supports the fully overlapping sub-band full-duplex mode, and the methods, apparatus, and non-transitory computer-readable media may include additional operations, features, components, or instructions for the following actions: based on the UE supporting the fully overlapping sub-band full-duplex mode, determining that the UE supports the non-overlapping sub-band full-duplex mode, the partially overlapping sub-band full-duplex mode, and the fully overlapping sub-band full-duplex mode. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Figure 1 , Figure 2A , Figure 2B and Figure 2C Each illustrates an example of a wireless communication system supporting network indication of full-duplex capability according to one or more aspects of the present disclosure.

[0052] Figure 3A and Figure 3B Each illustrates an example of a network-indicated full-duplex communication scheme supporting full-duplex capability according to one or more aspects of the present disclosure.

[0053] Figure 4 and Figure 5 Each illustrates an example of a process flow in a system supporting network indication of full-duplex capability according to one or more aspects of the present disclosure.

[0054] Figure 6 and Figure 7 A block diagram of a device supporting network indication of full-duplex capability according to one or more aspects of the present disclosure is shown.

[0055] Figure 8 A block diagram of a communications manager supporting network indication of full-duplex capability in accordance with one or more aspects of the present disclosure is shown.

[0056] Fig. 9 A diagram of a system including a device supporting network indication of full-duplex capability is shown in accordance with one or more aspects of the present disclosure.

[0057] Fig.10 and Fig.11A block diagram of a device supporting network indication of full-duplex capability according to one or more aspects of the present disclosure is shown.

[0058] Fig.12 A block diagram of a communications manager supporting network indication of full-duplex capability in accordance with one or more aspects of the present disclosure is shown.

[0059] Fig.13 A diagram of a system including a device supporting network indication of full-duplex capability is shown in accordance with one or more aspects of the present disclosure.

[0060] Fig.14 and Fig.15 A flow chart illustrating a method for supporting full-duplex capable network indication according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0061] In some wireless communication systems, communication devices such as user equipment (UE) or network entities may support wireless communication through one or more radio access technologies. Examples of radio access technologies may include fourth generation (4G) systems (such as long term evolution (LTE) systems) and fifth generation (5G) systems (which may be referred to as NR systems). In such cases, the communication device may operate in half-duplex mode or full-duplex mode or a combination thereof. In full-duplex mode, the communication device may simultaneously send and receive communications during the time period. That is, the communication received by the communication device may overlap with the communication sent by the communication device in the time domain. For example, the symbol occupied by the received signal may overlap with the symbol occupied by the transmitted signal.

[0062] In some examples, adjacent communication devices (e.g., UE, network entity, etc.) may concurrently perform full-duplex communication or half-duplex time division duplex (TDD), which may cause cross-link interference (CLI) due to the overlap of communications from adjacent devices in time. Additionally or alternatively, the communication device may experience self-interference due to the overlap of multiple communications from the communication device in time. In some cases, in order to reduce interference, the communication device (such as UE) may adopt one or more interference suppression techniques to communicate with the network entity, wherein the one or more suppression techniques may be based on the ability of the network entity to communicate using a full-duplex communication scheme. However, in some cases, the UE may not know the ability of the network entity to support the full-duplex communication scheme, and may not be able to adopt the one or more interference suppression techniques (e.g., unable to set the appropriate hardware configuration), and may therefore experience interference when communicating with the network entity. Additionally or alternatively, such as when entering a connected state, the UE may not know the ability of the network entity to support the full-duplex communication scheme, and may not know how or whether to indicate to the network entity the ability of the UE to support the full-duplex communication scheme.

[0063] Thus, the techniques described herein may allow a UE to receive an indication of the full-duplex capability of a network entity (e.g., via a capability message). For example, a UE may receive a message (e.g., a capability message) from a network entity indicating that the network entity supports one or more modes of a full-duplex communication scheme. The one or more modes may include a non-overlapping sub-band full-duplex mode, a partially overlapping sub-band full-duplex mode, a completely overlapping sub-band full-duplex mode, or any combination thereof. Additionally, a capability message indicating that the network entity supports one or more modes of a full-duplex communication scheme may be associated with an access procedure. Thus, a UE may perform an access procedure with a network entity and may communicate with the network entity based on the access procedure and the network entity supporting one or more modes associated with the full-duplex communication scheme.

[0064] In some cases, the network entity may indicate one or more modes supported by the network entity via a system information message, which may include one or more system information blocks (SIBs) or master information blocks (MIBs), or any combination thereof. For example, the network entity may indicate one or more modes via one or more bits of a system information message, via one or more parameters associated with a public service cell configuration included in a system information message, via one or more fields of a common uplink / downlink configuration included in a system information message, via an indication of an initial bandwidth portion included in a system information message, via one or more bits associated with a SIB for cell reselection, or any combination thereof. In some other cases, the network entity may indicate one or more modes supported by the network entity via a message associated with an access procedure (e.g., a random access procedure). For example, the network entity may indicate one or more modes via a downlink message associated with a random access procedure or via a control message that schedules a downlink message associated with a random access procedure. In some other cases, the network entity may indicate one or more modes supported by other network entities via a control message associated with a handover procedure.

[0065] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are then described in the context of a full-duplex communication scheme and process flow. Aspects of the present disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow diagrams related to network indication of full-duplex capability.

[0066] Figure 1An example of a wireless communication system 100 supporting network indication of full-duplex capability 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).

[0067] 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 different 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).

[0068] 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. 1 . The UEs 115 described herein may be capable of communicating with various types of devices, such as Figure 1 Other UEs 115 or network entities 105 are shown.

[0069] 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 yet 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.

[0070] In some examples, the network entities 105 may communicate with the core network 130, or communicate with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication 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 over the backhaul communication links 120 (e.g., according to X2, Xn or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). 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), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0071] 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, stand-alone) 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).

[0072] 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 sponsored 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)).

[0073] The functional split between CU 160, DU 165, and RU 175 is flexible and can 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, and RU 175. For example, a functional split of a protocol stack can be employed between CU 160 and DU 165, such that CU 160 can support one or more layers of a protocol stack and DU 165 can support one or more different layers of a protocol stack. In some examples, CU 160 can 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 a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) 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.

[0074] In some wireless communication systems (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 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 termination (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a collection of independent antennas for relaying communications with the UE 115, or may share the same antenna 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.

[0075] 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 network indication of full-duplex capability 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).

[0076] 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 electrical appliances or vehicles, meters, etc.

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

[0078] The UE 115 and the 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 the communication link 125. For example, a carrier for the 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-A Pro, 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 the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the 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) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between a device and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0079] The signal waveform transmitted over 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 employing MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The amount 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), such 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, beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0080] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, 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., ranging from 0 to 1023).

[0081] 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, the 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, the time slot may be further divided into multiple micro-time slots including one or more symbols. Excluding 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.

[0082] 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., a certain amount 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 a burst of a shortened TTI (sTTI)).

[0083] 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 amount 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 a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0084] 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.

[0085] 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 may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency may be used interchangeably herein.

[0086] In some examples, a UE 115 may be able to communicate directly with other UEs 115 via 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 may be unable or not configured to receive transmissions from the network entity 105 for other reasons. 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 of the other UEs 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 .

[0087] 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 for managing access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity for routing packets or interconnecting to an external network (e.g., a serving gateway (S-GW)), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access layer (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 transported by user plane entities, 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.

[0088] 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). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is about 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 lower frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

[0089] The wireless communication system 100 can utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can adopt 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 can use carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed bands can be based on a carrier aggregation configuration (e.g., LAA) combined with component carriers operating in licensed bands. Operations in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0090] 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 may 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 communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0091] 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 communicated 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 communicated 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).

[0092] UE 115 and network entity 105 may support retransmission of data to increase the possibility of successfully receiving data. Hybrid automatic repeat request (HARQ) feedback is a technology for increasing the possibility of correctly receiving data through a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0093] A UE 115 attempting to access a wireless network may perform an initial cell search by detecting a primary synchronization signal (PSS) from the network entity 105. The PSS may enable synchronization of time slot timing and may indicate a physical layer identification value. The UE 115 may then receive a secondary synchronization signal (SSS). The SSS may enable radio frame synchronization and may provide a cell identification value, which may be combined with a physical layer identification value to identify a cell. The SSS may also enable detection of duplex mode and cyclic prefix length. Some systems (such as TDD systems) may send SSS but not PSS. In some examples, the PSS and SSS may be located in the center 62 and 72 subcarriers of the carrier, respectively. In some cases, the network entity 105 may use multiple beams to send synchronization signals (e.g., PSS SSS, etc.) through a cell coverage area in a beam sweeping manner. In some cases, PSS, SSS, and / or broadcast information (e.g., physical broadcast channel (PBCH)) may be sent in different synchronization signals (SSBs) on corresponding directional beams, wherein one or more SSBs may be included in a burst.

[0094] After receiving the PSS and SSS, the UE 115 may receive the MIB, which may be sent in the PBCH. The MIB may include system bandwidth information, SFN, and physical HARQ indicator channel (PHICH) configuration. After decoding the MIB, the UE 115 may receive one or more SIBs. For example, SIB1 may include cell access parameters and scheduling information for other SIBs. Decoding SIB1 may enable the UE 115 to receive SIB2. SIB2 may include RRC configuration information related to RACH procedures, paging, PUCCH, physical uplink shared channel (PUSCH), power control, SRS, and cell barring.

[0095] After completing the initial cell synchronization, the UE 115 may decode the MIB, SIB1, and SIB2 before accessing the network. The MIB may be sent on the PBCH and may utilize the first 4 OFDMA symbols of the second slot of the first subframe of each radio frame, and the MIB may use the middle 6 RBs (72 subcarriers) in the frequency domain. The MIB carries some important pieces of information about the initial access of the UE, including the downlink channel bandwidth in RBs, the PHICH configuration (duration and resource assignment), and the SFN. A new MIB may be broadcast every fourth radio frame (SFN mod 4=0) and rebroadcast every frame (10ms). Each repetition is scrambled with a different scrambling code. After reading the MIB (new version or copy), the UE 115 may try different phases of the scrambling code until it obtains a successful CRC check. The phase of the scrambling code (0, 1, 2, or 3) may enable the UE 115 to identify which of the four repetitions has been received. Thus, the UE 115 can determine the current SFN by reading the SFN in the decoded transmission and adding the scrambling code phase. After receiving the MIB, the UE 115 can receive one or more SIBs. Different SIBs can be defined according to the type of system information conveyed. The new SIB1 can be transmitted in the fifth subframe in every eighth frame (i.e., SFN mod 8=0) and rebroadcast every other frame (20ms). SIB1 includes access information (including cellular cell identification information), and it can indicate whether the UE is allowed to camp on the cellular cell. SIB1 can also include cell selection information (or cell selection parameters). Additionally, SIB1 can include scheduling information for other SIBs. SIB2 can be dynamically scheduled according to the information in SIB1, and includes access information and parameters related to common and shared channels. The periodicity of SIB2 can be set to, for example, 8, 16, 32, 64, 128, 256 or 512 radio frames.

[0096] After the UE 115 decodes SIB2, it may send a RACH preamble to the network entity 105. For example, the RACH preamble may be randomly selected from a set of 64 predetermined sequences. This may enable the network entity 105 to distinguish between multiple UEs 115 attempting to access the system at the same time. The network entity 105 may respond with a random access response that provides an uplink resource grant, a timing advance, and a temporary C-RNTI. The UE 115 may then transmit an RRC connection request together with a temporary mobile subscriber identity (TMSI) (e.g., in the case where the UE 115 has previously been connected to the same wireless network) or a random identifier. The RRC connection request may also indicate the reason why the UE 115 is connected to the network (e.g., emergency, signaling, data exchange, etc.). The network entity 105 may respond to the connection request with a contention resolution message addressed to the UE 115, which may provide a new C-RNTI. If the UE 115 receives a contention resolution message with the correct identity, the process may proceed to RRC establishment. If the UE 115 does not receive a contention resolution message (eg, if there is a collision with another UE 115), it may repeat the RACH procedure by transmitting a new RACH preamble.

[0097] In the wireless communication system 100, the UE 115 and the network entity 105 may support a network indication of full-duplex capability. For example, the network entity 105 may send an indication to the UE 115 (e.g., in a capability message) that the network entity 105 supports one or more modes of a full-duplex communication scheme. The one or more modes may include a first full-duplex mode associated with an uplink / downlink non-overlapping subband configuration (e.g., mode), a second full-duplex mode associated with an uplink / downlink non-overlapping subband configuration, and a third full-duplex mode associated with an uplink / downlink fully overlapping subband configuration. In some cases, the network entity 105 may indicate the one or more modes supported by the network entity 105 via system information (such as one or more SIBs or MIBs). In some other cases, the network entity 105 may indicate the one or more modes supported by the network entity via one or more messages associated with an access procedure (such as a random access channel (RACH) procedure). In some other cases, the network entity 105 may indicate the one or more modes supported by the network entity via a message associated with the handover procedure (e.g., a handover command). The UE 115 may receive a capability message including an indication that the network entity 105 supports one or more modes of the full-duplex communication scheme, and may perform an access procedure with the network entity 105. Additionally, the UE 115 may communicate with the network entity 105 based on the access procedure and the one or more modes supported by the network entity 105.

[0098] Figure 2A , Figure 2B and Figure 2C Each illustrates an example of a wireless communication system 200 that supports network indication of full-duplex capability according to one or more aspects of the present disclosure. In some examples, the wireless communication system 200 (e.g., wireless communication system 200-a, wireless communication system 200-b, and wireless communication system 200-c) can implement aspects of the wireless communication system 100. For example, the wireless communication systems 200 can each include one or more network entities 205 (e.g., network entity 205-a, network entity 205-b, network entity 205-c, network entity 205-d, network entity 205-e, and network entity 205-f) and one or more UEs 215 (e.g., UE 215-a, UE 215-b, UE 215-c, UE 215-d, UE 215-e, and UE 215-f), which can be referenced. Figure 1 Examples of corresponding devices described. Figure 2A , Figure 2B and Figure 2C In the example of FIG. 1 , the network entity 205 may be as shown in FIG. Figure 1 Examples of CU 160, DU 165, RU 170, base station 140, IAB node 104, or one or more other network nodes are described. Wireless communication system 200 can include techniques for network entity 205 to provide one or more UEs 215 with an indication of full-duplex capability.

[0099] exist Figure 2A , Figure 2B and Figure 2C In the example of , UE 215 and network entity 205 can communicate via one or more communication links 210 (e.g., communication link 210-a, communication link 210-b, communication link 210-c, and communication link 210-d) and via one or more communication links 220 (e.g., communication link 220-a, communication link 220-b, communication link 220-c, communication link 220-d, and communication link 220-e). Communication link 210 can be an example of an uplink, and communication link 220 can be an example of a downlink. Additionally or alternatively, communication link 210 and communication link 220 can each be a communication link as described in detail in detail in FIG. Figure 1Examples of communication links 125 described. Each wireless communication system 200 may illustrate communication devices (e.g., one or more UEs 215, one or more network entities 205) operating in full-duplex mode (e.g., performing full-duplex wireless communication) or half-duplex TDD mode (e.g., performing half-duplex TDD wireless communication). That is, full-duplex (or half-duplex TDD) capabilities may exist at one or more network entities 205, one or more UEs 215 (or both). For example, the wireless communication system 200 may support TDD radio frequency bands (e.g., radio frequency spectrum bands configured for TDD communication), FDD radio frequency bands (e.g., radio frequency spectrum bands configured for FDD communication), full-duplex communication at one or more network entities 205 (and / or one or more UEs 215), half-duplex communication at one or more UEs 215, or any combination thereof.

[0100] Each wireless communication system 200 can support multiple types of full-duplex operation. For example, a communication device (e.g., network entity 205, UE 215) operating within the wireless communication system 200 can support in-band full-duplex (IBFD) operation, sub-band FDD (SBFD) operation (e.g., frequency duplex operation), or both. In some examples of IBFD operation, the communication device can send and receive wireless communications on the same time and frequency resources (e.g., the same time slot and component carrier bandwidth). For example, downlink communication and uplink communication can share time and frequency resources (e.g., IBFD time and frequency resources). In some examples, time and frequency resources can partially overlap or completely overlap (e.g., partially overlapping sub-band full-duplex mode or completely overlapping sub-band full-duplex mode). Additionally or alternatively, for SBFD operation, the communication device can send and receive communications on the same time resources and one or more different frequency resources. That is, downlink resources can be separated from uplink resources in the frequency domain (e.g., non-overlapping sub-band full-duplex mode).

[0101] exist Figure 2AIn some examples, the network entity 205-a may support SBFD operation (e.g., non-overlapping sub-band full-duplex mode) such that downlink communications sent by the network entity 205-a (e.g., to the UE 215-b) may overlap in time with uplink communications received by the network entity 205-a (e.g., from the UE 215-a). In some examples, the network entity 205-a may configure communications for the UE 215-a and the UE 215-b according to the resource structure 240. The resource structure 240 may include time domain resources (e.g., time slots, symbols) allocated for downlink data 250 (e.g., time domain resources 245-a), time domain resources allocated for uplink data 251 (e.g., time domain resources 245-d), and one or more time domain resources allocated for both the downlink data 250 and the uplink data 251 (e.g., time domain resources 245-b and time domain resources 245-c).

[0102] In some examples, the time domain resources (e.g., time domain resources 245-b and time domain resources 245-c) allocated for both downlink data 250 and uplink data 251 can be referred to as D+U time slots (or D+U symbols). In some examples, the D+U time slots can include half-duplex symbols (e.g., downlink symbols or uplink symbols) or full-duplex symbols (e.g., both downlink symbols and uplink symbols). For example, time domain resources 245-b and time domain resources 245-c (e.g., D+U time slots) can be examples of time slots where the radio frequency band is used to send both uplink communications (e.g., uplink transmissions) and downlink communications (e.g., downlink transmissions). In some examples, uplink transmissions and downlink transmissions can occur in overlapping frequency bands (e.g., for IBFD operations) or adjacent frequency bands (e.g., for SBFD operations).

[0103] For SBFD operation in which uplink transmission and downlink transmission occur in adjacent frequency bands, a half-duplex communication device may transmit in an uplink RF band or receive in a downlink RF band. That is, for a given time domain resource such as time domain resource 245-b (e.g., for a given D+U time slot or a given D+U symbol), a half-duplex device (e.g., UE 215-a, UE 215-b) may transmit uplink data 251 in an uplink RF band 271 (e.g., perform PUSCH transmission), or receive downlink data 250 in a downlink RF band 270. For example, UE 215-a may transmit uplink data 251 in an uplink RF band 271, while UE 215-b may receive downlink data 250 in a downlink RF band 270.

[0104] Additionally or alternatively, for SBFD operations in which uplink and downlink transmissions occur in adjacent frequency bands, a full-duplex device may transmit in an uplink RF band and receive in a downlink RF band. That is, for a given time domain resource such as time domain resource 245-b (e.g., for a given D+U time slot or a given D+U symbol), a full-duplex device may transmit uplink data 251 in an uplink RF band 271 (e.g., perform a PUSCH transmission) and receive downlink data 250 in a downlink RF band 270. Figure 2B In the example, UE 215 - c (eg, a full-duplex device) may send communications in an uplink RF band and receive communications in a downlink RF band (eg, in the same D+U time slot or the same D+U symbol).

[0105] In some examples, full-duplex communication can provide latency reduction. For example, latency savings can be achieved by receiving downlink signals in uplink time slots. In addition, full-duplex communication can provide spectrum efficiency enhancement (e.g., per cell or per UE 215), efficient resource utilization and coverage extension, and other benefits. However, in some examples, full-duplex communication may cause one or more types of interference, such as inter-cell interference (e.g., from adjacent communication devices), self-interference (e.g., for full-duplex communication devices) and CLI (e.g., inter-cell CLI or intra-cell CLI). For example, a communication device (e.g., one or more network entities 205, one or more UEs 215) may experience self-interference 230 (e.g., self-interference 230-a, self-interference 230-b, self-interference 230-c, and self-interference 230-d) between a pair of beams (such as a beam for sending communication and a beam for receiving communication). In some examples, self-interference may be caused by signal leakage between an antenna panel for sending communication and an antenna panel for receiving communication.

[0106] Additionally or alternatively, neighboring communication devices (e.g., neighboring UE 215, neighboring network entity 205) may concurrently perform full-duplex communication (or half-duplex TDD) such that communications received by a first communication device may overlap in time with communications sent by a second communication device (e.g., neighboring communication device). In such an example, communications sent by the second communication device may interfere with communications received at the first communication device. For example, communications sent by the second communication device may result in a CLI at the first communication device. In some examples, a CLI (e.g., CLI 225-a, CLI 225-b, CLI 225-c, CLI 225-d, CLI 225-e, or CLI 225-f) may be caused by energy leakage due to timing and frequency misalignment (e.g., misalignment) between neighboring communication devices.

[0107] Additionally or alternatively, CLI may be caused by an automatic gain control (AGC) mismatch (eg, misalignment). Figure 2A As illustrated in the example of , the AGC of UE 215-b can be driven (e.g., controlled) by downlink communications from a serving cell (e.g., network entity 205-a). In such an example, uplink communications sent from UE 215-a may saturate the AGC of UE 215-b, resulting in a misalignment (e.g., loss of orthogonality) of downlink communications received by UE 215-b and uplink communications sent by UE 215-a. In some examples, the misalignment of downlink communications and uplink communications may result in CLI 225-a at UE 215-b.

[0108] In some examples, network entity 205-a may operate in full-duplex mode (e.g., SBFD or IBFD) and UE 215 (e.g., UE 215-a and UE 215-b) may operate in half-duplex mode. For example, network entity 205-a may receive uplink communications from UE 215-a (e.g., via communication link 210-a) while sending downlink communications to UE 215-b (e.g., via communication link 220-a). In such an example, full-duplex communications at network entity 205-a may cause self-interference 230-a. Additionally or alternatively, network entity 205-a and network entity 205-b (e.g., adjacent network entities) may perform full-duplex communications concurrently such that a downlink signal sent by network entity 205-b may overlap an uplink signal received by network entity 205-a, thereby causing CLI 225-b.

[0109] Additionally or alternatively, UE 215-a and UE 215-b (e.g., adjacent UEs) may concurrently perform half-duplex TDD communications such that an uplink signal transmitted by UE 215-b may overlap a downlink signal received by UE 215-a, which may result in CLI 225-a. In some examples, UE 215-a may operate in a cell different from a cell in which UE 215-b may operate. For example, UE 215-a and UE 215-b may operate in adjacent cells. In an example, CLI 225 may be an example of an inter-cell CLI. Additionally or alternatively, network entity 205-b may concurrently perform full-duplex communications with network entity 205-a. In such an example, downlink communications transmitted by network entity 205-b may result in inter-cell interference at UE 215-b. For example, downlink communications sent by network entity 205-b (eg, to another UE (not shown)) may interfere with downlink communications received by UE 215-b (eg, from network entity 205-a).

[0110] In some other examples, UE 215-a and UE 215-b may operate in the same cell. In such an example, CLI 225 may be an example of an intra-cell CLI. For example, network entity 205-a may operate in full-duplex mode (e.g., in SBFD) such that network entity 205-a may configure downlink communications for UE 215-a in frequency domain resources adjacent to frequency domain resources allocated for uplink communications from UE 215-b. For example, network entity 205-a may configure UE 215-b to receive downlink data 250 in time domain resources 245-b and in downlink radio frequency band 270 (e.g., from network entity 205-a), and UE 215-a may be configured to send uplink data 251 in time domain resources 245-b (e.g., adjacent frequency resources) in uplink radio frequency band 271. In such an example, uplink communications sent by UE 215-a may interfere with downlink communications received at UE 215-b.

[0111] exist Figure 2BIn an example of a wireless communication system 200-b, the network entity 205-c and the UE 215-c can each operate in a full-duplex mode (e.g., IBDF) such that the UE 215-c can receive downlink communications from the network entity 205-c via the communication link 220-b while simultaneously sending uplink communications to the network entity 205-c via the communication link 210-c. In such an example, the full-duplex communications at the network entity 205-c and the full-duplex communications at the UE 215-c can result in self-interference 230-b and self-interference 230-c, respectively. In some examples of the wireless communication system 200-b, the UE 215-c and the UE 215-d can each operate in a multiple transmit and receive mode. In such an example, the downlink communications and uplink communications performed by the network entity 205-c can occur at two different antenna panels located at the two transmit and receive points. For example, reception of uplink communications from UE 215-c may occur at an antenna panel at a first transmit and receive point, and transmission of downlink communications to UE 215-c may occur at an antenna panel at a second transmit and receive point. In some other examples, reception of uplink communications and transmission of downlink communications may occur at two co-located antenna panels of a network entity 205-c (e.g., a single base station).

[0112] exist Figure 2C In an example of a wireless communication system 200-c, UE 215-e may operate in a full-duplex mode (e.g., SBFD) such that UE 215-e may receive downlink communications from network entity 205-f via communication link 220-d while simultaneously sending uplink communications to network entity 205-e via communication link 210-d. In such an example, full-duplex communications at UE 215-e may result in self-interference 230-d. In some examples of wireless communication system 200-c, network entity 205-e and network entity 205-f may be examples of transmit and receive points, and UE 215-e (e.g., and UE 215-f) may operate in a multiple transmit and receive mode. In such an example, uplink communications sent from UE 215-e may result in CLI 225-e (e.g., intra-cell CLI) at UE 215-f.

[0113] In some examples, to reduce interference within the wireless communication system 200, the network (e.g., one or more network entities 205) may employ one or more interference mitigation techniques (e.g., sub-band filtering, strict transmission requirements, or use of timing / power control modes). However, the UE 215 may employ one or more mitigation techniques to communicate with the network entity 205 based on the ability of the network entity 205 to communicate using a full-duplex communication scheme. In some cases, the UE 215 may not be aware of the ability of the network entity 205 to support a full-duplex communication scheme, and may not be able to employ the one or more interference mitigation techniques (e.g., may not be able to set an appropriate hardware configuration), and may therefore experience interference when communicating with the network entity 205. Additionally or alternatively, such as when entering a connected state, UE 215 may not be aware of the network entity 205's ability to support a full-duplex communication scheme, and may not know how or whether to indicate to the network entity 205 the UE 215's ability to support a full-duplex communication scheme (for example, if the network entity 205 does not support a full-duplex communication scheme, particularly SBFD or Flexible FD, the UE 215 may avoid reporting the UE 215's ability to support a full-duplex communication scheme).

[0114] The technology described herein can support the network entity 205 to send a capability message 255, such as a capability message 255-a, to the UE 215 indicating that the network entity 205 supports one or more modes of a full-duplex communication scheme. For example, the network entity 205 can support a first full-duplex communication mode, a second full-duplex communication mode, a third full-duplex communication mode, or any combination thereof. The first full-duplex communication mode can be associated with a non-overlapping subband configuration of the uplink / downlink. That is, the first full-duplex communication performed can be associated with SBFD operation. The second full-duplex communication mode can be associated with a configuration in which the uplink / downlink partially overlaps. That is, the second full-duplex mode can be associated with an IBFD operation, wherein the IBFD operation is associated with partially overlapping time and frequency resources. The third full-duplex communication mode can be associated with a configuration in which the uplink / downlink completely overlaps. That is, the third full-duplex mode can be associated with an IBFD operation, wherein the IBFD operation is associated with completely overlapping time and frequency resources.

[0115] In some cases, the network entity 205 may indicate via a system information message (e.g., the capability message 255-a may include a system information message) such as via one or more SIBs (e.g., carried by a physical downlink shared channel (PDSCH)) or MIBs (e.g., carried by a physical broadcast channel (PBCH)) one or more modes of a full-duplex communication scheme supported by the network entity 205. In some embodiments (e.g., when indicated via a MIB), the network entity 205 may indicate the one or more modes via one or more bits in the system information message (e.g., via explicit). In some other embodiments, the network entity 205 may jointly encode the indication of the one or more modes with one or more system information fragments (e.g., a physical resource block (PRB) grid offset or a broadcast channel subcarrier spacing (SCS) flag) included in the system information message. In some other embodiments (e.g., when indicated via one or more SIBs), the network entity 205 may indicate one or more modes via one or more parameters associated with a common service cell configuration (e.g., servingCellConfigCommon) included in a system information message, via one or more fields of a common uplink / downlink configuration (e.g., tddUL-DLConfigurationCommon) included in a system information message, via an indication of an initial bandwidth part (BWP) included in a system information message, or via one or more bits associated with system information for cell reselection (e.g., an explicit bit indication in other SIBs for cell reselection).

[0116] Additionally or alternatively, the network entity 205 may indicate one or more modes of the full-duplex communication scheme supported by the network entity 205 via a message associated with an access procedure, such as a random access procedure (e.g., a RACH procedure) (e.g., the capability message 255-a may include a message associated with an access procedure). In some cases, the network entity 205 may send an indication of one or more modes via a downlink message of the random access procedure. For example, the network entity 205 may send an indication via the PDSCH of the second message (e.g., MSG2) or the fourth message (e.g., MSG4) of a four-step random access procedure (e.g., a 4-step RACH procedure). In another example, the network entity 205 may send an indication via a second message (e.g., MSGB) of a two-step random access procedure (e.g., a 2-step RACH procedure). In some cases, the network entity 205 may send an indication via one or more reserved bits of a downlink message (e.g., in a MAC subheader or in a MAC payload). In some other cases, the network entity 205 may send the indication using a random access preamble identifier (RAPID) in a downlink message. That is, each of the one or more modes may be associated with one or more values ​​of RAPID (e.g., each mode may be associated with a range of RAPIDs). Thus, the network entity 205 may receive a random access request from the UE 215 (e.g., as part of a random access procedure), and may send a downlink message including a RAPID in response to the random access request, wherein the value of the RAPID is associated with a mode in the one or more modes supported by the network entity 205.

[0117] In another embodiment, the network entity 205 may send an indication of one or more modes via a control message of a random access procedure (e.g., downlink control information (DCI)). For example, the network entity 205 may send an indication via a control message (e.g., a payload of DCI format 1_0) that schedules a downlink message (e.g., MSG2 or MSGB) associated with a random access procedure (e.g., a 2-step RACH procedure or a 4-step RACH procedure). In some cases, the network entity 205 may send an indication (e.g., explicitly) via one or more reserved bits in the control message. Additionally, the control message may be scrambled with a radio network temporary identifier (RNTI) (scrambled with a random access RNTI in a 4-step RACH procedure, or scrambled with a MsgB RNTI in a 2-step RACH procedure).

[0118] Additionally or alternatively, the network entity 205 may indicate one or more modes of the full-duplex communication scheme supported by the network entity 205 via a control message (e.g., a handover command) associated with the handover process (e.g., the capability message 255-a may include a control message associated with the handover process). For example, the UE 215 may be handed over to the target network entity 205 (e.g., in a connected state). In such a case, the source network entity 205 may indicate in a control message (e.g., sent during the handover process) whether one or more modes of the full-duplex communication scheme are supported by a set of one or more target cells that can be used for handover. In other examples, the network node 205 associated with the target cell may indicate its ability to support one or more modes of the full-duplex communication scheme (e.g., in a message associated with the handover process). In some examples, the network entity 205 may provide an indication of whether one or more target cells support one or more modes of the full-duplex communication scheme before the handover process. For example, the indication of whether the neighboring network entity 205 supports one or more modes of the full-duplex communication scheme may be provided with one or more measurement configurations for measurements to be performed as part of the handover process. In such cases, the UE 215 may determine which cells or network nodes support full-duplex communications when performing measurements.

[0119] In some cases, the network entity 205 may refrain from sending the capabilities message 255-a, and the UE 215 may determine that the network entity 205 does not support one or more modes of the full-duplex communication scheme (e.g., does not support the full-duplex communication scheme) based on the network entity 205 refraining from sending the indication (e.g., based on not receiving the capabilities message 255-a). That is, if the network entity does not signal an indication that it supports the capability for one or more full-duplex modes, the UE 215 may assume that the network entity (or the call) does not support the one or more full-duplex modes.

[0120] In some cases (e.g., based on receiving an indication of the network entity 205's ability to support one or more modes), the UE 215 may send an indication of the UE 215's ability to support one or more modes associated with a full-duplex communication scheme to the network entity (e.g., via a capability message 255-b). For example, the UE 215 may send the indication via a message associated with a random access procedure (e.g., via a specific RACH sequence / preamble associated with MSG1 of a 4-step RACH procedure, via a payload of MSG3 of a 4-step RACH procedure, or via a payload of MSG A of a 2-step RACH procedure).

[0121] Figure 3A and Figure 3BExamples of network-indicated full-duplex communication schemes 300-a and 300-b supporting full-duplex capability according to one or more aspects of the present disclosure are illustrated. In some examples, the full-duplex communication schemes 300 (full-duplex communication schemes 300-a and full-duplex communication schemes 300-b) can implement aspects of or be implemented by aspects of the following items: wireless communication system 100 and wireless communication system 200. For example, the full-duplex communication schemes 300 can be implemented by network entity 105 or UE 115, respectively, which can be as described in reference to Figure 1 Examples of corresponding devices described. Figure 3A and Figure 3B In some examples, the network entity 105 may be as shown in FIG. Figure 1 Examples of CU 160, DU 165, RU 170, base station 140, IAB node 104, or one or more other network nodes are described. Full-duplex communication scheme 300 may include techniques for network entity 105 to provide UE 115 with an indication of full-duplex capability.

[0122] In some examples, a wireless communication device (e.g., network entity 105 or UE 115) can support full-duplex communication, where the communication device can send and receive communications simultaneously, thereby facilitating latency savings achieved by receiving downlink signals in uplink time slots (or symbols). In some examples, the communication device can support multiple (e.g., two) types of full-duplex operation. For example, the communication device can support SBFD operation, where the communication device can send and receive communications on the same time resources and on different frequency resources. That is, downlink resources can be separated from uplink resources in the frequency domain.

[0123] For example, Figure 3A As illustrated in the example of , the network entity 105 may configure one or more UEs 115 (e.g., for SBFD operation) according to configuration 305-a. In such an example, the network entity 105 may configure a downlink transmission (e.g., transmission of downlink data 310) for UE 115 in a frequency domain resource (e.g., resource 315-a) that may be adjacent to a frequency domain resource (e.g., resource 315-b) configured for an uplink transmission (e.g., transmission of uplink data 320) of another UE 115. In some examples, in order to reduce interference between uplink transmissions (e.g., scheduled for resource 315-a) and downlink transmissions (e.g., scheduled for resource 315-b), the network entity 105 may configure resource 315-a and resource 315-b to be separated by a guard band 316.

[0124] Additionally or alternatively, such as Figure 3BAs illustrated by the example of , the network entity 105 can support IBFD operation so that the network entity 105 can send and receive communications on the same time resources and the same frequency resources (e.g., the same time slot and carrier bandwidth). For example, the network entity 105 can configure one or more UEs 115 according to configuration 305-b, configuration 305-c, or both. In such examples, the network entity 105 can configure downlink transmissions (e.g., transmission of downlink data 310) and uplink transmissions (e.g., transmission of uplink data 320) so that the downlink transmissions and uplink transmissions can share the same one or more time and frequency resources (e.g., IBFD time and frequency resources). In some examples, the network entity 105 can configure one or more UEs 115 according to configuration 305-b so that one or more time and frequency resources (e.g., resources 315-c) allocated for transmission of uplink data 320 can overlap (e.g., completely overlap) with one or more time and frequency resources (e.g., resources 315-d) allocated for transmission of downlink data 310. Additionally or alternatively, the network entity 105 may configure one or more UEs 115 according to the configuration 305-c such that a portion of one or more time and frequency resources (e.g., resources 315-e) allocated for transmission of uplink data 320 may overlap with a portion of one or more time and frequency resources (e.g., resources 315-f) allocated for transmission of downlink data 310. That is, the resources 315-e may partially overlap with the resources 315-f.

[0125] In some examples, although full-duplex communication can provide one or more spectrum efficiency enhancements (e.g., per cell or per UE), efficient resource utilization, and coverage area extension, concurrent full-duplex communication may cause CLI. For example, adjacent communication devices may perform full-duplex communication concurrently, so that the communication received by the first communication device may overlap in time with the communication sent by the second communication device (e.g., adjacent communication device). In such an example, the communication sent by the second communication device may cause CLI at the first communication device. In addition, concurrent full-duplex communication at UE 115 may cause self-interference. For example, the uplink communication sent by UE 115 may overlap in time with the downlink communication received by UE 115, so that the uplink communication and the downlink communication interfere with each other. In such cases, UE 115 may attempt to communicate with network entity 105 using one or more suppression techniques. However, the one or more suppression techniques may be based on the ability of network entity 105 to support the full-duplex communication scheme, and UE 115 may not know the ability of network entity 105. As a result, the UE 115 may be unable to employ the one or more interference mitigation techniques (e.g., unable to set an appropriate hardware configuration), and may therefore experience interference when communicating with the network entity 105. Additionally or alternatively, such as when entering a connected state, the UE 115 may not know how or whether to indicate to the network entity 105 the ability of the UE 115 to support a full-duplex communication scheme.

[0126] Thus, according to the techniques described herein, the network entity 105 may send a capability message to the UE 115 indicating that the network entity 105 supports one or more modes of the full-duplex communication scheme. In some cases, a communication device (such as the network entity 105 or the UE 115) may support one or more modes of the full-duplex communication scheme. For example, Figure 3AAs illustrated in , the network entity 105 may support a first full-duplex mode (e.g., Mode 1) associated with configuration 305-a, such that the network entity 105 may configure downlink transmissions for the UE 115 in frequency domain resources that are adjacent to frequency domain resources configured for uplink transmissions (e.g., uplink / downlink non-overlapping subband mode, SBFD). In another example, the network entity 105 may support a second full-duplex mode (e.g., Mode 2) associated with configuration 305-c. The network entity 105 supporting the second full-duplex mode may configure uplink transmissions and downlink transmissions such that a portion of one or more time and frequency resources allocated for transmission of uplink data may overlap with a portion of one or more time and frequency resources allocated for transmission of downlink data (e.g., uplink / downlink partially overlapping subband mode). In another example, the network entity 105 may support a third full-duplex mode (e.g., Mode 3) associated with configuration 305-b. The network entity 105 supporting the third full-duplex mode can configure uplink transmission and downlink transmission so that one or more time and frequency resources allocated for transmission of uplink data can overlap (e.g., completely overlap) with one or more time and frequency resources allocated for transmission of downlink data (e.g., uplink / downlink completely overlapping subband mode).

[0127] In some cases, the network entity 105 may send a capability message indicating that the network entity 105 supports the first full-duplex mode, the second full-duplex mode, the third full-duplex mode, or any combination thereof. If the network entity 105 sends an indication that the network entity 105 supports the third full-duplex mode, the network entity 105 may also support the first full-duplex mode and the second full-duplex mode. For example, if the network entity 105 indicates (e.g., via a capability message) that it supports fully overlapping uplink / downlink subbands for full-duplex communication, the UE 115 may assume that the network entity 105 also supports both non-overlapping uplink / downlink subbands (e.g., SBFD) and partially overlapping uplink / downlink subbands (e.g., flexible duplex) for full-duplex communication. Additionally, if the network entity 105 sends an indication that the network entity 105 supports the second full-duplex mode, the network entity 105 may also support the first full-duplex mode. As an example, if the network entity 105 indicates (e.g., via a capability message) that it supports partially overlapping uplink / downlink subbands for full-duplex communication (e.g., flexible duplex), the UE 115 may assume that the network entity 105 also supports non-overlapping uplink / downlink subbands for full-duplex communication (e.g., SBFD).

[0128] The capability message sent by UE 115 may also indicate one or more modes supported by UE 115. For example, UE 115 may send a capability message indicating that UE 115 supports a first full-duplex mode, a second full-duplex mode, a third full-duplex mode, or any combination thereof. In some examples, if UE 115 sends an indication that UE 115 supports the third full-duplex mode, UE 115 may also support the first full-duplex mode and the second full-duplex mode. For example, if UE 115 (e.g., via a capability message) indicates that it supports fully overlapping uplink / downlink subbands for full-duplex communication, network entity 105 may assume that UE 115 also supports both non-overlapping uplink / downlink subbands (e.g., SBFD) and partially overlapping uplink / downlink subbands (e.g., flexible full-duplex communication) for full-duplex communication. In some aspects, if UE 115 sends an indication that UE 115 supports the second full-duplex mode, UE 115 may also support the first full-duplex mode. As an example, if UE 115 indicates (e.g., via a capability message) that it supports partially overlapping uplink / downlink subbands for full-duplex communication (e.g., flexible full-duplex communication), the network entity 105 may assume that UE 115 also supports non-overlapping uplink / downlink subbands for full-duplex communication (e.g., SBFD).

[0129] In some cases, the network entity 105 may switch between one or more of the full-duplex modes based on frequency domain resource allocations for uplink data and downlink data in frequency domain time slots. In such cases, the switching may be based on the full-duplex capability sent by the UE 115. As an example, when the UE 115 supports both SBFD and flexible full-duplex communication (e.g., subband overlap), the switching between SBFD and flexible full-duplex communication may be performed through frequency domain resource allocation.

[0130] Figure 4 An example of a process flow 400 in a system supporting network indication of full-duplex capability according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 400 can implement or be implemented by aspects of the following items: wireless communication system 100, wireless communication system 200, and full-duplex communication scheme 300. For example, the process flow 400 can be implemented by a network entity 405 or a UE 415, which can be as described in reference Figure 1 Examples of corresponding devices described. Figure 4 In the example of FIG. 1 , the network entity 405 may be as shown in FIG. Figure 1Examples of CU 160, DU 165, RU 170, base station 140, IAB node 104, or one or more other network nodes are described. Process flow 400 may include techniques for network entity 405 to provide UE 415 with an indication of full-duplex capability.

[0131] In some cases, at 410, the network entity 405 may broadcast one or more MIBs (e.g., a system information message). In some cases, the MIB may indicate that the network entity 405 supports one or more modes of a full-duplex communication scheme. For example, the network entity 405 may indicate, via one or more bits in the MIB, the one or more modes of a full-duplex communication scheme supported by the network entity 405. In another example, the network entity 405 may (e.g., jointly) encode one or more portions of system information included in the MIB with an indication that the network entity 405 supports one or more modes of a full-duplex communication scheme (e.g., the UE 415 may decode the system information message to identify the indication).

[0132] In some cases, the network entity may send one or more SIBs (e.g., system information messages) at 420. In some cases, the one or more SIBs may indicate that the network entity 405 supports one or more modes of the full-duplex communication scheme. For example, the network entity 405 may indicate the one or more modes of the full-duplex communication scheme supported by the network entity 405 via one or more parameters associated with a common service cell configuration, via one or more fields of a common uplink / downlink configuration, via an indication of an initial BWP, or via one or more bits of one or more SIBs associated with cell reselection.

[0133] In some cases, at 425 , UE 415 may perform downlink synchronization, which may be based on system information received from network entity 405 .

[0134] In some cases, at 430, the UE 115 may send a first message (e.g., MSGA) of a two-step random access procedure (e.g., a 2-step RACH procedure) that includes a random access request. In some cases, the first message may include an indication of one or more modes of a full-duplex communication scheme supported by the UE 115.

[0135] In some cases, at 435, network entity 435 may process the first message.

[0136] In some cases, at 440, the network entity 405 may (e.g., in response to the first message) send a second message (e.g., MSGB) of the two-step random access procedure. In some cases, the second message may include an indication of one or more modes of the full-duplex communication scheme supported by the network entity 405. For example, the network entity 405 may indicate the one or more modes of the full-duplex communication scheme supported by the network entity 405 via one or more reserved bits in the second message. In another example, the second message may include a RAPID, and the network entity 405 may indicate the one or more modes of the full-duplex communication scheme supported by the network entity 405 via the value of the RAPID. That is, each of the one or more modes may be associated with one or more RAPIDs (e.g., the value of the RAPID). In another example, the network entity may send a control message (e.g., DCI) scheduling the second message, and the indication of the one or more modes of the full-duplex communication scheme supported by the network entity 405 may be included in one or more bits of the control message.

[0137] In some cases, UE 415 may send a feedback message including an acknowledgement message or a negative acknowledgement message at 445. Additionally, UE 415 may communicate with network entity 405 based on the random access procedure and network entity 405 supporting one or more modes associated with a full-duplex communication scheme.

[0138] In some cases, the one or more modes may include a non-overlapping sub-band full-duplex mode, a partially overlapping sub-band full-duplex mode, a completely overlapping sub-band full-duplex mode, or any combination thereof. For example, the network entity 405 may indicate to the UE 415 that the network entity 405 supports the partially overlapping sub-band full-duplex mode, and the UE 415 may determine that the network entity 405 supports the non-overlapping sub-band full-duplex mode and the partially overlapping sub-band full-duplex mode based on the network entity 405 supporting the partially overlapping sub-band full-duplex mode. In another example, the network entity 405 may indicate to the UE 415 that the network entity 405 supports the completely overlapping sub-band full-duplex mode, and the UE 415 may determine that the network entity 405 supports the non-overlapping sub-band full-duplex mode, the partially overlapping sub-band full-duplex mode, and the completely overlapping sub-band full-duplex mode based on the UE supporting the completely overlapping sub-band full-duplex mode.

[0139] Figure 5An example of a process flow 500 in a system supporting network indication of full-duplex capability according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 500 can implement or be implemented by aspects of the following items: wireless communication system 100, wireless communication system 200, full-duplex communication scheme 300, and process flow 500. For example, the process flow 500 can be implemented by a network entity 505 or a UE 515, which can be as described in reference Figure 1 Examples of corresponding devices described. Figure 5 In the example of FIG. 1 , the network entity 505 may be as shown in FIG. Figure 1 Examples of CU 160, DU 165, RU 170, base station 140, IAB node 104, or one or more other network nodes are described. Process flow 500 may include techniques for network entity 505 to provide an indication of full-duplex capability to UE 515.

[0140] In some cases, at 510, UE 515 may send a first message (e.g., MSG1) of a four-step random access procedure (e.g., a 4-step RACH procedure) that includes a random access request. In some cases, the first message may include an indication of one or more modes of a full-duplex communication scheme supported by UE 115.

[0141] In some cases, at 520, the network entity 505 may send a second message (e.g., MSG2) of the four-step random access procedure. In some cases, the second message may include an indication of one or more modes of the full-duplex communication scheme supported by the network entity 505. For example, the network entity 505 may indicate one or more modes of the full-duplex communication scheme supported by the network entity 505 via one or more reserved bits in the second message. In another example, the second message may include a RAPID, and the network entity 505 may indicate one or more modes of the full-duplex communication scheme supported by the network entity 505 via the value of the RAPID. That is, each of the one or more modes may be associated with one or more RAPIDs (e.g., the value of the RAPID). In another example, the network entity may send a control message (e.g., DCI) scheduling the second message, and the indication of one or more modes of the full-duplex communication scheme supported by the network entity 505 may be included in one or more bits of the control message.

[0142] In some cases, the UE 515 may send a third message (eg, MSG3) of the four-step random access procedure at 525. In some cases, the third message may include an indication of one or more modes of a full-duplex communication scheme supported by the UE 115.

[0143] In some cases, at 530, the network entity 505 may send a fourth message (e.g., MSG4) of the four-step random access procedure. In some cases, the fourth message may include an indication of one or more modes of the full-duplex communication scheme supported by the network entity 505. For example, the network entity 505 may indicate the one or more modes of the full-duplex communication scheme supported by the network entity 505 via one or more reserved bits in the fourth message. In another example, the fourth message may include a RAPID, and the network entity 505 may indicate the one or more modes of the full-duplex communication scheme supported by the network entity 505 via the value of the RAPID.

[0144] In some cases, at 535, the network entity 505 may send a handover command to the UE 515. For example, after the UE 515 and the network entity (e.g., using a two-step random access procedure, using a four-step random access procedure) establish a connection, some communication link conditions may change (e.g., due to the mobility of the UE 515, due to interference, etc.). In such cases, the UE 515 and the network entity 505 may complete the handover process based on a set of measurements so that the UE 515 can connect to another cell (e.g., one or more target cells, one or more target network nodes). In some cases, the handover command may indicate that one or more other network entities support one or more modes of a full-duplex communication scheme, which may inform the UE 515 which network entities can support one or more modes of a full-duplex communication scheme.

[0145] Figure 6 A block diagram 600 of a device 605 supporting network indication of full-duplex capability according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0146] The receiver 610 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to network indications of full-duplex capability), user data, control information, or any combination thereof. The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0147] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to network indications of full-duplex capability), user data, control information, or any combination thereof. In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0148] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or various components thereof may be examples of means for performing various aspects of network indication of full-duplex capability as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0149] In some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof can 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, a processor and a memory coupled to the processor can be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0150] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, 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 620, the receiver 610, the transmitter 615, 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.

[0151] In some examples, communication manager 620 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 610, transmitter 615, or both. For example, communication manager 620 can receive information from receiver 610, transmit information to transmitter 615, or be integrated with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0152] According to an example as disclosed herein, the communication manager 620 may support wireless communication at the UE. For example, the communication manager 620 may be configured to or otherwise support a component for the following actions: receiving a capability message from a network entity indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the UE and the network entity. The communication manager 620 may be configured to or otherwise support a component for the following actions: performing an access procedure with the network entity. The communication manager 620 may be configured to or otherwise support a component for the following actions: communicating with the network entity based on the access procedure and the network entity supporting one or more modes associated with the full-duplex communication scheme.

[0153] By including or configuring the communication manager 620 according to the examples described herein, the device 605 (e.g., a processor controlling or otherwise coupled with the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof) can support techniques for network indication of full-duplex capability, which can result in reduced processing, reduced power consumption, and more efficient utilization of communication resources, among other advantages.

[0154] Figure 7 A block diagram 700 of a device 705 supporting network indication of full-duplex capability according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0155] The receiver 710 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to network indications of full-duplex capability), user data, control information, or any combination thereof. The information may be communicated to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0156] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to network indications of full-duplex capability), user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0157] Device 705 or its various components may be examples of components for performing various aspects of network indication of full-duplex capability as described herein. For example, communication manager 720 may include capability component 725, access process component 730, full-duplex component 735, or any combination thereof. Communication manager 720 may be an example of various aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 710, transmitter 715, or both. For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated with receiver 710, transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0158] According to examples as disclosed herein, the communication manager 720 may support wireless communications at the UE. The capability component 725 may be configured to or otherwise support components for receiving a capability message from a network entity indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the UE and the network entity. The access procedure component 730 may be configured to or otherwise support components for performing an access procedure with the network entity. The full-duplex component 735 may be configured to or otherwise support components for communicating with the network entity based on the access procedure and the network entity supporting one or more modes associated with the full-duplex communication scheme.

[0159] Figure 8A block diagram 800 of a communication manager 820 supporting network indication of full-duplex capability according to one or more aspects of the present disclosure is shown. The communication manager 820 can be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components can be examples of means for performing various aspects of network indication of full-duplex capability as described herein. For example, the communication manager 820 can include a capability component 825, an access procedure component 830, a full-duplex component 835, a system information 840, a random access procedure component 845, a handover component 850, a decoding component 855, or any combination thereof. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses).

[0160] According to examples as disclosed herein, the communication manager 820 may support wireless communications at the UE. The capability component 825 may be configured to or otherwise support components for receiving a capability message from a network entity indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the UE and the network entity. The access procedure component 830 may be configured to or otherwise support components for performing an access procedure with the network entity. The full-duplex component 835 may be configured to or otherwise support components for communicating with the network entity based on the access procedure and the network entity supporting one or more modes associated with the full-duplex communication scheme.

[0161] In some examples, to support receiving a capability message, system information 840 may be configured or otherwise support means for receiving a system information message indicating that the network entity supports one or more modes of a full-duplex communication scheme, the capability message including the system information message.

[0162] In some examples, the system information message includes one or more bits indicating that the network entity supports one or more modes of a full-duplex communication scheme.

[0163] In some examples, decoding component 855 may be configured or otherwise support means for decoding a system information message in which one or more portions of the system information are encoded with an indication that the network entity supports one or more modes of a full-duplex communication scheme.

[0164] In some examples, the system information message indicates one or more parameters associated with a public service cell configuration, the one or more parameters indicating that the network entity supports one or more modes of a full-duplex communication scheme.

[0165] In some examples, the system information message includes one or more fields of a common uplink / downlink configuration that indicate that the network entity supports one or more modes of a full-duplex communication scheme.

[0166] In some examples, the system information message includes an indication of an initial bandwidth portion, the indication of the initial bandwidth portion indicating that the network entity supports one or more modes of a full-duplex communication scheme.

[0167] In some examples, the system information message includes one or more bits indicating that the network entity supports one or more modes of a full-duplex communication scheme, and the system information message is associated with a SIB for cell reselection.

[0168] In some examples, the system information message includes a MIB or a SIB.

[0169] In some examples, to support receiving a capability message, the random access process component 845 can be configured as or otherwise support components for: receiving, as part of a random access process, a downlink message indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message includes a downlink message and the access process includes a random access process.

[0170] In some examples, the downlink message includes one or more reserved bits indicating that the network entity supports one or more modes of a full-duplex communication scheme.

[0171] In some examples, to support receiving a downlink message, the random access procedure component 845 may be configured to or otherwise support means for: sending, as part of a random access procedure, a first message including a random access request. In some examples, to support receiving a downlink message, the random access procedure component 845 may be configured to or otherwise support means for: receiving, in response to the random access request, a downlink message including a RAPID, wherein a value of the RAPID indicates that the network entity supports one or more modes of a full-duplex communication scheme.

[0172] In some examples, each of the one or more modes is associated with one or more RAPIDs.

[0173] In some examples, to support receiving a capability message, the random access process component 845 may be configured to or otherwise support components for: receiving, as part of a random access procedure, a control message that schedules a downlink message associated with the random access process, wherein one or more bits of the control message indicate that the network entity supports one or more modes of a full-duplex communication scheme, the control message including a capability message.

[0174] In some examples, to support receiving a capabilities message, handover component 850 may be configured or otherwise support means for receiving a control message associated with a handover process, wherein the control message indicates that one or more other network entities support one or more modes of a full-duplex communication scheme.

[0175] In some examples, the one or more modes include a non-overlapping sub-band full-duplex mode, a partially overlapping sub-band full-duplex mode, a fully overlapping sub-band full-duplex mode, or any combination thereof.

[0176] In some examples, the capability message indicates that the network entity supports a partially overlapping sub-band full-duplex mode, and the capability component 825 can be configured to or otherwise support components for the following actions: based on the network entity supporting the partially overlapping sub-band full-duplex mode, determining that the network entity supports a non-overlapping sub-band full-duplex mode and a partially overlapping sub-band full-duplex mode.

[0177] In some examples, the capability message indicates that the network entity supports a fully overlapping sub-band full-duplex mode, and the capability component 825 can be configured to or otherwise support components for the following actions: based on the network entity supporting the fully overlapping sub-band full-duplex mode, determining that the network entity supports a non-overlapping sub-band full-duplex mode, a partially overlapping sub-band full-duplex mode, and a fully overlapping sub-band full-duplex mode.

[0178] In some examples, capability component 825 may be configured to or otherwise support means for sending a message indicating the UE's ability to support one or more modes associated with a full-duplex communication scheme, wherein the message is sent in response to a capability message.

[0179] Fig. 9 A diagram of a system 900 including a device 905 that supports network indications of full-duplex capability according to one or more aspects of the present disclosure is shown. The device 905 may be an example of a device 605, a device 705, or a UE 115 as described herein or include a component of the device 605, the device 705, or a UE 115. The device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 905 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, a code 935, and a processor 940. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 945).

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

[0181] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which can send or receive multiple wireless transmissions concurrently. The transceiver 915 can communicate bidirectionally via one or more antennas 925, wired or wireless links, as described herein. For example, the transceiver 915 may represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem that modulates packets, provides the modulated packets to one or more antennas 925 for transmission, and demodulates packets received from one or more antennas 925. The transceiver 915 or the transceiver 915 and one or more antennas 925 can be examples of transmitters 615, transmitters 715, receivers 610, receivers 710, or any combination or components thereof as described herein.

[0182] The memory 930 may include random access memory (RAM) and read-only memory (ROM). The memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed by the processor 940, cause the device 905 to perform various functions described herein. The code 935 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 935 may not be directly executed by the processor 940, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 930 may include a basic I / O system (BIOS), etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0183] The processor 940 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, the processor 940 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 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 930) to enable the device 905 to perform various functions (e.g., various functions or tasks indicated by a network supporting full-duplex capability). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to or coupled to the processor 940, and the processor 940 and the memory 930 are configured to perform the various functions described herein.

[0184] According to an example as disclosed herein, the communication manager 920 may support wireless communication at the UE. For example, the communication manager 920 may be configured to or otherwise support a component for the following actions: receiving a capability message from a network entity indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the UE and the network entity. The communication manager 920 may be configured to or otherwise support a component for the following actions: performing an access procedure with the network entity. The communication manager 920 may be configured to or otherwise support a component for the following actions: communicating with the network entity based on the access procedure and the network entity supporting one or more modes associated with the full-duplex communication scheme.

[0185] By including or configuring the communications manager 920 according to examples as described herein, the device 905 can support techniques for network indication of full-duplex capability, which can result in improved communications reliability, reduced latency, an improved user experience associated with reduced processing, reduced power consumption, more efficient use of communications resources, improved coordination between devices, longer battery life, and improved use of processing power, among other advantages.

[0186] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions that are executable by the processor 940 to cause the device 905 to perform various aspects of the network indication of full-duplex capability as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0187] Fig.10 A block diagram 1000 of a device 1005 supporting network indication of full-duplex capability according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0188] The receiver 1010 may provide a 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 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0189] The transmitter 1015 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1005. For example, the transmitter 1015 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 1015 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1015 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 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0190] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or various components thereof may be examples of means for performing various aspects of network indication of full-duplex capability as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0191] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, 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 in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0192] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, 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 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure).

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

[0194] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. For example, the communication manager 1020 may be configured to or otherwise support components for the following actions: sending a capability message indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the network entity and the UE. The communication manager 1020 may be configured to or otherwise support components for the following actions: performing an access procedure with the UE. The communication manager 1020 may be configured to or otherwise support components for the following actions: communicating with the UE based on the access procedure and the network entity supporting one or more modes associated with the full-duplex communication scheme.

[0195] By including or configuring the communications manager 1020 according to examples as described herein, the device 1005 (e.g., a processor controlling or otherwise coupled to the receiver 1010, the transmitter 1015, the communications manager 1020, or a combination thereof) can support techniques for network indication of full-duplex capability, which can result in reduced processing, reduced power consumption, and more efficient utilization of communications resources, among other advantages.

[0196] Fig.11 A block diagram 1100 of a device 1105 supporting network indication of full-duplex capability according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0197] The receiver 1110 may provide a 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 delivered to other components of the device 1105. In some examples, the receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0198] The transmitter 1115 may provide means for outputting (e.g., sending, providing, communicating, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 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 1115 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0199] Device 1105 or its various components may be examples of components for performing various aspects of network indication of full-duplex capability as described herein. For example, communication manager 1120 may include capability component 1125, access process component 1130, full-duplex component 1135, or any combination thereof. Communication manager 1120 may be an example of various aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0200] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. The capability component 1125 may be configured to or otherwise support components for sending a capability message indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the network entity and the UE. The access procedure component 1130 may be configured to or otherwise support components for performing an access procedure with the UE. The full-duplex component 1135 may be configured to or otherwise support components for communicating with the UE based on the access procedure and the network entity supporting one or more modes associated with the full-duplex communication scheme.

[0201] Fig.12 A block diagram 1200 of a communication manager 1220 supporting network indication of full-duplex capability according to one or more aspects of the present disclosure is shown. The communication manager 1220 may be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be examples of means for performing various aspects of network indication of full-duplex capability as described herein. For example, the communication manager 1220 may include a capability component 1225, an access procedure component 1230, a full-duplex component 1235, a system information component 1240, a random access procedure component 1245, a handover component 1250, or any combination thereof. Each of these components may communicate with each other directly or indirectly (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.

[0202] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. The capability component 1225 may be configured to or otherwise support components for sending a capability message indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the network entity and the UE. The access procedure component 1230 may be configured to or otherwise support components for performing an access procedure with the UE. The full-duplex component 1235 may be configured to or otherwise support components for communicating with the UE based on the access procedure and the network entity supporting one or more modes associated with the full-duplex communication scheme.

[0203] In some examples, to support sending a capability message, the system information component 1240 may be configured as or otherwise support components for broadcasting a system information message indicating that the network entity supports one or more modes of a full-duplex communication scheme to one or more UEs including the UE, the capability message including the system information message.

[0204] In some examples, the system information message includes one or more bits indicating that the network entity supports one or more modes of a full-duplex communication scheme.

[0205] In some examples, system information component 1240 can be configured to or otherwise support components for encoding one or more portions of system information with an indication that a network entity supports one or more modes of a full-duplex communication scheme, wherein the system information message includes one or more portions of system information encoded with the indication.

[0206] In some examples, the system information message indicates one or more parameters associated with a public service cell configuration, the one or more parameters indicating that the network entity supports one or more modes of a full-duplex communication scheme.

[0207] In some examples, the system information message includes one or more fields of a common uplink / downlink configuration that indicate that the network entity supports one or more modes of a full-duplex communication scheme.

[0208] In some examples, the system information message includes an indication of an initial bandwidth portion, the indication of the initial bandwidth portion indicating that the network entity supports one or more modes of a full-duplex communication scheme.

[0209] In some examples, the system information message includes one or more bits indicating that the network entity supports one or more modes of a full-duplex communication scheme, and the system information message is associated with a SIB for cell reselection.

[0210] In some examples, to support sending a capability message, the random access process component 1245 can be configured as or otherwise support components for the following actions: as part of a random access process, sending a downlink message indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message includes the downlink message and the access process includes a random access process.

[0211] In some examples, the downlink message includes one or more reserved bits indicating that the network entity supports one or more modes of a full-duplex communication scheme.

[0212] In some examples, to support sending a downlink message, the random access process component 1245 may be configured to or otherwise support means for: receiving, as part of a random access process, a first message including a random access request. In some examples, to support sending a downlink message, the random access process component 1245 may be configured to or otherwise support means for: sending, in response to the random access request, a downlink message including a RAPID, wherein a value of the RAPID indicates that the network entity supports one or more modes of a full-duplex communication scheme.

[0213] In some examples, each of the one or more modes is associated with one or more RAPIDs.

[0214] In some examples, to support sending a capability message, the random access process component 1245 can be configured as or otherwise support components for the following actions: as part of the random access process, sending a control message scheduling a downlink message associated with the random access process, wherein one or more bits of the control message indicate that the network entity supports one or more modes of a full-duplex communication scheme.

[0215] In some examples, to support sending a capability message, handover component 1250 may be configured or otherwise support means for sending a control message associated with a handover process, wherein the control message indicates that one or more other network entities support one or more modes of a full-duplex communication scheme.

[0216] In some examples, the one or more modes include a non-overlapping sub-band full-duplex mode, a partially overlapping sub-band full-duplex mode, a fully overlapping sub-band full-duplex mode, or any combination thereof.

[0217] In some examples, capability component 1225 can be configured to or otherwise support components for receiving a message indicating the UE's ability to support one or more modes associated with a full-duplex communication scheme, the one or more modes comprising a non-overlapping sub-band full-duplex mode, a partially overlapping sub-band full-duplex mode, a fully overlapping sub-band full-duplex mode, or any combination thereof, wherein the message is received in response to a capability message.

[0218] In some examples, the message indicates that the UE supports partially overlapping sub-band full-duplex mode, and the capability component 1225 can be configured as or otherwise support components for the following actions: based on the UE supporting the partially overlapping sub-band full-duplex mode, determining that the UE supports non-overlapping sub-band full-duplex mode and partially overlapping sub-band full-duplex mode.

[0219] In some examples, the capability message indicates that the UE supports a fully overlapping sub-band full-duplex mode, and the capability component 1225 can be configured as or otherwise support components for the following actions: based on the UE supporting the fully overlapping sub-band full-duplex mode, determining that the UE supports a non-overlapping sub-band full-duplex mode, a partially overlapping sub-band full-duplex mode, and a fully overlapping sub-band full-duplex mode.

[0220] Fig.13 A diagram of a system 1300 of a device 1305 including a network indication supporting full-duplex capability according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a network entity 105 as described herein, or include components thereof. The device 1305 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 1305 may include components that support output and acquisition of communications, such as a communication manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, a code 1330, and a processor 1335. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

[0221] The transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315 that may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1310 may also include a modem for modulating a signal, providing a modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter), receiving a modulated signal (e.g., from one or more antennas 1315, from a wired receiver), and demodulating a signal. The transceiver 1310 or transceiver 1310 and one or more antennas 1315 or wired interfaces (where applicable) may be examples of transmitter 1015, transmitter 1115, receiver 1010, receiver 1110, or any combination thereof or any components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0222] Memory 1325 may include RAM and ROM. Memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by processor 1335, cause device 1305 to perform various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by processor 1335, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1325 may also include, among other things, BIOS, which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0223] The processor 1335 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 1335 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 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1325) to enable the device 1305 to perform various functions (e.g., various functions or tasks indicated by a network supporting full-duplex capability). For example, the device 1305 or a component of the device 1305 may include a processor 1335 and a memory 1325 coupled to the processor 1335, and the processor 1335 and the memory 1325 are configured to perform the various functions described herein. Processor 1335 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 (e.g., by executing code 1330) to perform the functions of device 1305.

[0224] In some examples, bus 1340 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1340 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1305, or communications performed between different components of device 1305 that may be co-located or located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one of the different components or divided between the different components).

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

[0226] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at a network entity. For example, the communication manager 1320 may be configured to or otherwise support components for the following actions: sending a capability message indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the network entity and the UE. The communication manager 1320 may be configured to or otherwise support components for the following actions: performing an access procedure with the UE. The communication manager 1320 may be configured to or otherwise support components for the following actions: communicating with the UE based on the access procedure and the network entity supporting one or more modes associated with the full-duplex communication scheme.

[0227] By including or configuring the communications manager 1320 according to examples as described herein, the device 1305 can support techniques for network indication of full-duplex capability, which can result in improved communications reliability, reduced latency, an improved user experience associated with reduced processing, reduced power consumption, more efficient use of communications resources, improved coordination between devices, longer battery life, and improved use of processing power, among other advantages.

[0228] In some examples, the communication manager 1320 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the processor 1335, the memory 1325, the code 1330, the transceiver 1310, or any combination thereof. For example, the code 1330 may include instructions that are executable by the processor 1335 to cause the device 1305 to perform various aspects of the network indication of full-duplex capability as described herein, or the processor 1335 and the memory 1325 may be otherwise configured to perform or support such operations.

[0229] Fig.14 A flowchart illustrating a method 1400 for network indication of supporting full-duplex capability according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The described UE 115 may be performed. 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.

[0230] At 1405, the method may include: receiving a capability message from a network entity indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the UE and the network entity. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 8 The described capability component 825 is executed.

[0231] At 1410, the method may include: performing an access procedure with a network entity. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 8 The described access process component 830 is performed.

[0232] At 1415, the method may include: communicating with a network entity based on the access procedure and the network entity supporting one or more modes associated with a full-duplex communication scheme. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 8 The described full-duplex component 835 is implemented.

[0233] Fig.15 A flowchart illustrating a method 1500 for indicating a network supporting full-duplex capability according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 5 and Figures 10 to 13 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.

[0234] At 1505, the method may include sending a capability message indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the network entity and the UE. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig.12 The described capability component 1225 is executed.

[0235] At 1510, the method may include: performing an access procedure with the UE. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig.12 The described access process component 1230 is performed.

[0236] At 1515, the method may include: communicating with the UE based on the access procedure and the network entity supporting one or more modes associated with the full-duplex communication scheme. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference Fig.12 The described full-duplex component 1235 is implemented.

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

[0238] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a capability message from a network entity indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the UE and the network entity; performing the access procedure with the network entity; and communicating with the network entity based at least in part on the access procedure and the network entity supporting the one or more modes associated with the full-duplex communication scheme.

[0239] Aspect 2: The method according to aspect 1, wherein receiving the capability message comprises: receiving a system information message indicating that the network entity supports the one or more modes of the full-duplex communication scheme, and the capability message comprises the system information message.

[0240] Aspect 3: The method according to aspect 2, wherein the system information message includes one or more bits indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

[0241] Aspect 4: The method according to aspect 2, the method further comprising: decoding the system information message, wherein one or more parts of the system information are encoded with an indication that the network entity supports the one or more modes of the full-duplex communication scheme.

[0242] Aspect 5: The method according to aspect 2, wherein the system information message indicates one or more parameters associated with a public service cell configuration, and the one or more parameters indicate that the network entity supports the one or more modes of the full-duplex communication scheme.

[0243] Aspect 6: The method according to aspect 2, wherein the system information message includes one or more fields of common uplink / downlink configuration, and the one or more fields indicate that the network entity supports the one or more modes of the full-duplex communication scheme.

[0244] Aspect 7: The method according to aspect 2, wherein the system information message includes an indication of an initial bandwidth portion, and the indication of the initial bandwidth portion indicates that the network entity supports the one or more modes of the full-duplex communication scheme.

[0245] Aspect 8: The method according to aspect 2, wherein the system information message includes one or more bits indicating that the network entity supports the one or more modes of the full-duplex communication scheme, and the system information message is associated with a SIB for cell reselection.

[0246] Aspect 9: The method according to any one of aspects 2 to 8, wherein the system information message includes a MIB or a SIB.

[0247] Aspect 10: A method according to Aspect 1, wherein receiving the capability message includes: as part of a random access process, receiving a downlink message indicating that the network entity supports the one or more modes of the full-duplex communication scheme, wherein the capability message includes the downlink message, and the access process includes the random access process.

[0248] Aspect 11: The method according to aspect 10, wherein the downlink message includes one or more reserved bits indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

[0249] Aspect 12: A method according to any one of Aspects 10 to 11, wherein receiving the downlink message comprises: sending a first message including a random access request as part of the random access process; and receiving the downlink message including a RAPID in response to the random access request, wherein the value of the RAPID indicates that the network entity supports the one or more modes of the full-duplex communication scheme.

[0250] Aspect 13: The method according to aspect 12, wherein each of the one or more modes is associated with one or more RAPIDs.

[0251] Aspect 14: A method according to Aspect 1, wherein receiving the capability message includes: as part of a random access process, receiving a control message that schedules a downlink message associated with the random access process, wherein one or more bits of the control message indicate that the network entity supports the one or more modes of the full-duplex communication scheme, and the control message includes the capability message.

[0252] Aspect 15: The method according to any one of Aspect 1, wherein receiving the capability message comprises: receiving a control message associated with a handover process, wherein the control message indicates that one or more other network entities support the one or more modes of the full-duplex communication scheme.

[0253] Aspect 16: The method according to any one of aspects 1 to 15, wherein the one or more modes include a non-overlapping sub-band full-duplex mode, a partially overlapping sub-band full-duplex mode, a fully overlapping sub-band full-duplex mode, or any combination thereof.

[0254] Aspect 17: A method according to Aspect 16, wherein the capability message indicates that the network entity supports the partially overlapping sub-band full-duplex mode, and the method further includes: determining that the network entity supports the non-overlapping sub-band full-duplex mode and the partially overlapping sub-band full-duplex mode based at least in part on the network entity supporting the partially overlapping sub-band full-duplex mode.

[0255] Aspect 18: A method according to any one of Aspects 16 to 17, wherein the capability message indicates that the network entity supports the completely overlapping sub-band full-duplex mode, and the method further comprises: determining that the network entity supports the non-overlapping sub-band full-duplex mode, the partially overlapping sub-band full-duplex mode and the completely overlapping sub-band full-duplex mode based at least in part on the network entity supporting the completely overlapping sub-band full-duplex mode.

[0256] Aspect 19: According to any one of Aspects 1 to 18, the method further includes: sending a message indicating the ability of the UE to support the one or more modes associated with the full-duplex communication scheme, wherein the message is sent in response to the capability message.

[0257] Aspect 20: A method for performing wireless communications at a network entity, the method comprising: sending a capability message indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the network entity and a UE; performing the access procedure with the UE; and communicating with the UE based at least in part on the access procedure and the network entity supporting the one or more modes associated with the full-duplex communication scheme.

[0258] Aspect 21: A method according to Aspect 20, wherein sending the capability message comprises: broadcasting a system information message indicating that the network entity supports the one or more modes of the full-duplex communication scheme to one or more UEs including the UE, and the capability message comprises the system information message.

[0259] Aspect 22: The method according to aspect 21, wherein the system information message includes one or more bits indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

[0260] Aspect 23: According to the method according to Aspect 21, the method also includes: encoding one or more parts of system information with an indication of the one or more modes that the network entity supports the full-duplex communication scheme, wherein the system information message includes the one or more parts of the system information encoded with the indication.

[0261] Aspect 24: The method according to aspect 21, wherein the system information message indicates one or more parameters associated with a public service cell configuration, and the one or more parameters indicate that the network entity supports the one or more modes of the full-duplex communication scheme.

[0262] Aspect 25: The method according to aspect 21, wherein the system information message includes one or more fields of common uplink / downlink configuration, and the one or more fields indicate that the network entity supports the one or more modes of the full-duplex communication scheme.

[0263] Aspect 26: The method according to aspect 21, wherein the system information message includes an indication of an initial bandwidth portion, the indication of the initial bandwidth portion indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

[0264] Aspect 27: The method according to aspect 21, wherein the system information message includes one or more bits indicating that the network entity supports the one or more modes of the full-duplex communication scheme, and the system information message is associated with a SIB for cell reselection.

[0265] Aspect 28: A method according to Aspect 20, wherein sending the capability message includes: as part of a random access procedure, sending a downlink message indicating that the network entity supports the one or more modes of the full-duplex communication scheme, wherein the capability message includes the downlink message, and the access procedure includes the random access procedure.

[0266] Aspect 29: The method according to aspect 28, wherein the downlink message includes one or more reserved bits indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

[0267] Aspect 30: A method according to Aspect 28, wherein sending the downlink message comprises: receiving a first message including a random access request as part of the random access process; and sending the downlink message including a RAPID in response to the random access request, wherein the value of the RAPID indicates that the network entity supports the one or more modes of the full-duplex communication scheme.

[0268] Aspect 31: The method according to aspect 30, wherein each of the one or more modes is associated with one or more RAPIDs.

[0269] Aspect 32: A method according to Aspect 20, wherein sending the capability message includes: as part of a random access process, sending a control message scheduling a downlink message associated with the random access process, wherein one or more bits of the control message indicate that the network entity supports the one or more modes of the full-duplex communication scheme.

[0270] Aspect 33: A method according to any one of Aspect 20, wherein sending the capability message comprises: sending a control message associated with a handover process, wherein the control message indicates that one or more other network entities support the one or more modes of the full-duplex communication scheme.

[0271] Aspect 34: The method according to any one of aspects 20 to 33, wherein the one or more modes include a non-overlapping sub-band full-duplex mode, a partially overlapping sub-band full-duplex mode, a fully overlapping sub-band full-duplex mode, or any combination thereof.

[0272] Aspect 35: According to the method described in any one of Aspects 20 to 34, the method further includes: receiving a message indicating the ability of the UE to support the one or more modes associated with the full-duplex communication scheme, the one or more modes including a non-overlapping sub-band full-duplex mode, a partially overlapping sub-band full-duplex mode, a fully overlapping sub-band full-duplex mode, or any combination thereof, wherein the message is received in response to the capability message.

[0273] Aspect 36: A method according to Aspect 35, wherein the message indicates that the UE supports the partially overlapping sub-band full-duplex mode, and the method further includes: determining that the UE supports the non-overlapping sub-band full-duplex mode and the partially overlapping sub-band full-duplex mode based at least in part on the UE supporting the partially overlapping sub-band full-duplex mode.

[0274] Aspect 37: A method according to any one of Aspects 35 to 36, wherein the capability message indicates that the UE supports the completely overlapping sub-band full-duplex mode, and the method further includes: determining that the UE supports the non-overlapping sub-band full-duplex mode, the partially overlapping sub-band full-duplex mode and the completely overlapping sub-band full-duplex mode based at least in part on the UE supporting the completely overlapping sub-band full-duplex mode.

[0275] Aspect 38: 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 19.

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

[0277] Aspect 40: 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 a method according to any one of aspects 1 to 19.

[0278] Aspect 41: An apparatus for wireless communication 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 20 to 37.

[0279] Aspect 42: An apparatus for wireless communication at a network entity, the apparatus comprising at least one means for performing a method according to any one of aspects 20 to 37.

[0280] Aspect 43: 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 a method according to any one of aspects 20 to 37.

[0281] 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.

[0282] 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.

[0283] 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 that may be mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0284] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, an 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, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0285] 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 this 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.

[0286] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to be transported 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.

[0287] 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."

[0288] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up 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.

[0289] 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.

[0290] 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," rather than "preferred" or "having advantages over other examples." The specific implementation includes specific details to provide an understanding of the technology. However, the technologies may 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.

[0291] 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. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: receiving a capability message from a network entity indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the UE and the network entity; performing the access procedure with the network entity; as well as Communicating with the network entity is performed based at least in part on the access procedure and the network entity supporting the one or more modes associated with the full-duplex communication scheme.

2. The method of claim 1 , wherein receiving the capability message comprises: A system information message is received indicating that the network entity supports the one or more modes of the full-duplex communication scheme, the capability message comprising the system information message. 3 . The method of claim 2 , wherein the system information message comprises one or more bits indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

4. The method according to claim 2, further comprising: The system information message is decoded, wherein one or more portions of the system information are encoded with an indication that the network entity supports the one or more modes of the full-duplex communication scheme.

5. The method of claim 2, wherein the system information message indicates one or more parameters associated with a public service cell configuration, the one or more parameters indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

6. The method of claim 2, wherein the system information message comprises one or more fields of a common uplink / downlink configuration, the one or more fields indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

7. The method of claim 2, wherein the system information message includes an indication of an initial bandwidth portion, the indication of the initial bandwidth portion indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

8. The method of claim 2, wherein the system information message comprises one or more bits indicating that the network entity supports the one or more modes of the full-duplex communication scheme, the system information message being associated with a system information block for cell reselection.

9. The method of claim 2, wherein the system information message comprises a master information block or a system information block.

10. The method of claim 1 , wherein receiving the capability message comprises: As part of a random access procedure, a downlink message is received indicating that the network entity supports the one or more modes of the full-duplex communication scheme, wherein the capability message includes the downlink message and the access procedure includes the random access procedure.

11. The method of claim 10, wherein the downlink message includes one or more reserved bits indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

12. The method of claim 10, wherein receiving the downlink message comprises: sending, as part of the random access procedure, a first message comprising a random access request; as well as In response to the random access request, the downlink message including a random access preamble identifier is received, wherein a value of the random access preamble identifier indicates that the network entity supports the one or more modes of the full-duplex communication scheme.

13. The method of claim 12, wherein each of the one or more patterns is associated with one or more random access preamble identifiers.

14. The method of claim 1 , wherein receiving the capability message comprises: As part of a random access procedure, a control message is received that schedules a downlink message associated with the random access procedure, wherein one or more bits of the control message indicate that the network entity supports the one or more modes of the full-duplex communication scheme, the control message including the capability message.

15. The method of claim 1 , wherein receiving the capability message comprises: A control message associated with a handover procedure is received, wherein the control message indicates that one or more other network entities support the one or more modes of the full-duplex communication scheme.

16. The method of claim 1, wherein the one or more modes include a non-overlapping sub-band full-duplex mode, a partially overlapping sub-band full-duplex mode, a fully overlapping sub-band full-duplex mode, or any combination thereof.

17. The method according to claim 16, wherein the capability message indicates that the network entity supports the partially overlapping sub-band full-duplex mode, the method further comprising: Based at least in part on the network entity supporting the partially overlapping sub-band full-duplex mode, it is determined that the network entity supports the non-overlapping sub-band full-duplex mode and the partially overlapping sub-band full-duplex mode.

18. The method of claim 16, wherein the capability message indicates that the network entity supports the fully overlapping sub-band full-duplex mode, the method further comprising: Based at least in part on the network entity supporting the fully overlapping sub-band full-duplex mode, it is determined that the network entity supports the non-overlapping sub-band full-duplex mode, the partially overlapping sub-band full-duplex mode, and the fully overlapping sub-band full-duplex mode.

19. The method according to claim 1, further comprising: A message is sent indicating an ability of the UE to support the one or more modes associated with the full-duplex communication scheme, wherein the message is sent in response to the capability message.

20. A method for wireless communication at a network entity, the method comprising: sending a capability message indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the network entity and a user equipment (UE); performing the access procedure with the UE; as well as Communicating with the UE is performed based at least in part on the access procedure and the network entity supporting the one or more modes associated with the full-duplex communication scheme.

21. The method of claim 20, wherein sending the capability message comprises: A system information message indicating that the network entity supports the one or more modes of the full-duplex communication scheme is broadcasted to one or more UEs including the UE, the capability message including the system information message.

22. The method of claim 21, wherein the system information message indicates one or more parameters associated with a public service cell configuration, the one or more parameters indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

23. The method of claim 21, wherein the system information message includes one or more fields of a common uplink / downlink configuration, the one or more fields indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

24. The method of claim 21, wherein the system information message includes an indication of an initial bandwidth portion, the indication of the initial bandwidth portion indicating that the network entity supports the one or more modes of the full-duplex communication scheme.

25. The method of claim 21, wherein the system information message comprises one or more bits indicating that the network entity supports the one or more modes of the full-duplex communication scheme, the system information message being associated with a system information block for cell reselection.

26. The method of claim 20, wherein sending the capability message comprises: As part of a random access procedure, a downlink message is sent indicating that the network entity supports the one or more modes of the full-duplex communication scheme, wherein the capability message includes the downlink message and the access procedure includes the random access procedure.

27. The method of claim 20, wherein sending the capability message comprises: As part of a random access procedure, a control message is sent that schedules a downlink message associated with the random access procedure, wherein one or more bits of the control message indicate that the network entity supports the one or more modes of the full-duplex communication scheme.

28. The method of claim 20, wherein sending the capability message comprises: A control message associated with a handover procedure is sent, wherein the control message indicates that one or more other network entities support the one or more modes of the full-duplex communication scheme.

29. 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 a capability message from a network entity indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the UE and the network entity; performing the access procedure with the network entity; as well as Communicating with the network entity is performed based at least in part on the access procedure and the network entity supporting the one or more modes associated with the full-duplex communication scheme.

30. 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 a capability message indicating that the network entity supports one or more modes of a full-duplex communication scheme, wherein the capability message is associated with an access procedure between the network entity and a user equipment (UE); performing the access procedure with the UE; as well as Communicating with the UE is performed based at least in part on the access procedure and the network entity supporting the one or more modes associated with the full-duplex communication scheme.

Images