WO2025166531A1

WO2025166531A1 - Reporting capability information for communicating with ambient internet of things devices

Info

Publication number: WO2025166531A1
Application number: PCT/CN2024/076240
Authority: WO
Inventors: Kazuki Takeda; Le LIU; Yuchul Kim; Zhikun WU
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2024-02-06
Filing date: 2024-02-06
Publication date: 2025-08-14
Anticipated expiration: 2026-08-06

Abstract

Methods, systems, and devices for wireless communications are described. The described techniques may enable a user equipment (UE) to transmit a capability report indicating a capability to transmit forward link (FL) messages and continuous-wave (CW) signals and to receive backward link (BL) messages via a same carrier, and a capability to simultaneously transmit or receive FL messages, BL messages, CW signals, uplink messages, and/or downlink messages via paired or unpaired carriers. In some examples, based on the UE capability, a network entity may schedule the UE to transmit or receive FL messages, BL messages, CW signals, uplink messages, and/or downlink messages simultaneously or at different times via paired or unpaired carriers. In some examples, based on the UE capability, the UE may drop transmission or reception of one or more FL messages, BL messages, CW signals, uplink messages, and/or downlink messages.

Description

REPORTING CAPABILITY INFORMATION FOR COMMUNICATING WITH AMBIENT INTERNET OF THINGS DEVICES

INTRODUCTION

The following relates to wireless communications, including reporting capability information for communicating with ambient internet of things (A-IoT) devices. Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the 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, LTE-Advanced (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 technologies 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) . A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE) .

SUMMARY

The described techniques relate to improved methods, systems, devices, and apparatuses that support reporting capability information for communicating with ambient internet of things (A-IoT) devices. For example, the described techniques provide for a user equipment (UE) to transmit a capability report indicating a capability to transmit forward link (FL) communications and continuous-wave (CW) signals and to receive backwards link (BL) communications via a same carrier, and/or to simultaneously transmit or receive FL communications, BL communications, CW signals, uplink communications, and/or downlink communications via paired or unpaired carriers. In some examples, based on the UE capability, a network entity may schedule the UE to transmit or receive FL communications, BL communications, CW signals, uplink communications, and/or downlink communications simultaneously or at different times via paired or unpaired carriers. In some examples, based on the UE capability, the UE may drop transmission or reception of one or more FL communications, BL communications, CW signals, uplink communications, and/or downlink communications (e.g., if one or more of the messages are scheduled simultaneously and if the UE may not transmit and/or receive the one or more of the messages simultaneously) .

A method for wireless communication by a first network entity is described. The method may include transmitting a capability report that indicates a capability of the first network entity to communicate, via a first carrier of a frequency band, with a second network entity, receiving a grant that schedules a communication that includes one or more FL transmissions, one or more BL transmissions, one or more CW signals, or a combination thereof between the first network entity and the second network entity, where the communication is scheduled to occur via the first carrier, and communicating with the second network entity via the first carrier in accordance with the grant and with the capability.

A first network entity for wireless communication is described. The first network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the first network entity to transmit a capability report that indicates a capability of the first network entity to communicate, via a first carrier of a frequency band, with a second network entity, receive a grant that schedules a communication that includes one or more FL transmissions, one or more BL transmissions, one or more CW signals, or a combination thereof between the first network entity and the second network entity, where the communication is scheduled to occur via the first carrier, and communicate with the second network entity via the first carrier in accordance with the grant and with the capability.

Another first network entity for wireless communication is described. The first network entity may include means for transmitting a capability report that indicates a capability of the first network entity to communicate, via a first carrier of a frequency band, with a second network entity, means for receiving a grant that schedules a communication that includes one or more FL transmissions, one or more BL transmissions, one or more CW signals, or a combination thereof between the first network entity and the second network entity, where the communication is scheduled to occur via the first carrier, and means for communicating with the second network entity via the first carrier in accordance with the grant and with the capability.

A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to transmit a capability report that indicates a capability of the first network entity to communicate, via a first carrier of a frequency band, with a second network entity, receive a grant that schedules a communication that includes one or more FL transmissions, one or more BL transmissions, one or more CW signals, or a combination thereof between the first network entity and the second network entity, where the communication is scheduled to occur via the first carrier, and communicate with the second network entity via the first carrier in accordance with the grant and with the capability.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, the capability report includes a capability of the first network entity to simultaneously transmit the one or more CW signals via the first carrier and receive a BL transmission of the communication via the first carrier, to simultaneously perform the communication via the first carrier and receive a downlink transmission via a downlink carrier of the frequency band, to simultaneously perform the communication via the first carrier and transmit an uplink transmission via an uplink carrier of the frequency band, or some combination thereof.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, the capability report includes a capability of the first network entity to perform the communication via the first carrier and to communicate with a third network entity via a downlink carrier of the frequency band, via an uplink carrier of the frequency band, or both, the downlink carrier may be paired with the first carrier or unpaired with the first carrier, and the uplink carrier may be unpaired with the first carrier.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, the capability report indicates a limitation associated with simultaneous communications at the first network entity and the first carrier may be a first uplink carrier of the frequency band.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, the grant indicates for the first network entity to perform the communication in accordance with the capability.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, the grant indicates a time gap between the communication and one or more uplink transmissions based on the capability and the time gap may be associated with a switching time for the first network entity to switch from performance of the communication via the first uplink carrier and transmission of one or more uplink messages via a second uplink carrier of the frequency band.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, the limitation may be an inability to simultaneously transmit the one or more CW signals and receive the one or more BL transmissions, to simultaneously receive the one or more BL transmissions and receive one or more downlink communications via a downlink carrier of the frequency band, to simultaneously transmit the one or more FL transmissions and receive one or more downlink transmissions via the downlink carrier, to simultaneously transmit the one or more FL transmissions and transmit one or more uplink transmissions via a second uplink carrier of the frequency band, or to simultaneously receive the one or more BL transmissions and transmit one or more uplink transmissions via the second uplink carrier.

Some examples of the method, first network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for dropping one or more communications based on the grant being indicative of performance of the communication in violation of the limitation, where the one or more communications may be dropped in accordance with the capability.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, the one or more dropped communications include the one or more FL transmissions, the one or more BL transmissions, the one or more CW signals, one or more uplink transmissions, one or more downlink transmissions, or some combination thereof.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, the one or more communications may be dropped in accordance with one or more prioritization rules associated with a type of transmission of the one or more uplink transmissions or of the one or more downlink transmissions.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, when the limitation indicates that the first network entity does not support simultaneous reception of the one or more BL transmissions via the first uplink carrier and reception of one or more downlink transmissions via a downlink carrier of the frequency band that may be paired with the first uplink carrier, the type of transmission that may be associated with the one or more prioritization rules includes a synchronization signal block (SSB) , a physical downlink control channel (PDCCH) common search space (CSS) , a PDCCH UE specific search space (USS) , a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) message, or a dynamically scheduled PDSCH message.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, when the limitation indicates that the first network entity does not support simultaneous transmission of the one or more FL transmissions via the first uplink carrier and reception of one or more downlink transmissions via a downlink carrier of the frequency band that may be paired with the first uplink carrier, the type of transmission that may be associated with the one or more prioritization rules includes a SSB, a dedicated radio resource control (RRC) message, a physical uplink control channel (PUCCH) CSS, a PUCCH CSS, or a SPS physical uplink shared channel (PUSCH) message.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, when the limitation indicates that the first network entity does not support simultaneous reception of the one or more BL transmissions via the first uplink carrier and reception of one or more downlink transmissions via a downlink carrier of the frequency band that may be unpaired with the first uplink carrier, the type of transmission that may be associated with the one or more prioritization rules includes a SSB, a PDCCH CSS, a PDCCH CSS, a dedicated RRC message, or a dynamically scheduled PDSCH message.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, when the limitation indicates that the first network entity does not support simultaneous reception of the one or more BL transmissions via the first uplink carrier and transmission of one or more uplink transmissions via an second uplink carrier of the frequency band that may be unpaired with the first uplink carrier, the type of transmission that may be associated with the one or more prioritization rules includes a physical random access channel message, a semi-static PUCCH message, a dynamic PUCCH message, a semi-static PUSCH message, a dynamic PUSCH message, a semi-static sounding reference signal (SRS) , or a dynamic SRS.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, the second network entity may be capable of reception or transmission via at least one of amplitude-shift keying modulation or frequency-shift keying modulation.

A method for wireless communication by a first network entity is described. The method may include obtaining a capability report that indicates a capability of a second network entity to communicate, via a first carrier of a frequency band, with a third network entity and outputting a grant that schedules a communication that includes one or more FL communications, one or more BL communications, one or more CW signals, or a combination thereof between the second network entity and the third network entity, where the communication is scheduled to occur via the first carrier.

A first network entity for wireless communication is described. The first network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the first network entity to obtain a capability report that indicates a capability of a second network entity to communicate, via a first carrier of a frequency band, with a third network entity and output a grant that schedules a communication that includes one or more FL communications, one or more BL communications, one or more CW signals, or a combination thereof between the second network entity and the third network entity, where the communication is scheduled to occur via the first carrier.

Another first network entity for wireless communication is described. The first network entity may include means for obtaining a capability report that indicates a capability of a second network entity to communicate, via a first carrier of a frequency band, with a third network entity and means for outputting a grant that schedules a communication that includes one or more FL communications, one or more BL communications, one or more CW signals, or a combination thereof between the second network entity and the third network entity, where the communication is scheduled to occur via the first carrier.

A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to obtain a capability report that indicates a capability of a second network entity to communicate, via a first carrier of a frequency band, with a third network entity and output a grant that schedules a communication that includes one or more FL communications, one or more BL communications, one or more CW signals, or a combination thereof between the second network entity and the third network entity, where the communication is scheduled to occur via the first carrier.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, the capability report includes a capability of the second network entity to simultaneously transmit the one or more CW signals via the first carrier and receive a BL transmission of the communication via the first carrier, to simultaneously perform the communication via the first carrier and receive a downlink transmission via a downlink carrier of the frequency band, to simultaneously perform the communication via the first carrier and transmit an uplink transmission via an uplink carrier of the frequency band, or some combination thereof.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, the capability report includes a capability of the second network entity to perform the communication via the first carrier and to communicate with a third network entity via a downlink carrier of the frequency band, via an uplink carrier of the frequency band, or both, the downlink carrier may be paired with the first carrier or unpaired with the first carrier, and the uplink carrier may be unpaired with the first carrier.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, the capability report indicates a limitation associated with simultaneous communications at the second network entity and the first carrier may be a first uplink carrier of the frequency band.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, the grant indicates for the second network entity to perform the communication in accordance with the capability.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, the limitation may be an inability to simultaneously transmit the one or more CW signals and receive the one or more BL communications, to simultaneously receive the one or more BL communications and receive one or more downlink communications via a downlink carrier of the frequency band, to simultaneously transmit the one or more FL communications and receive one or more downlink transmissions via the downlink carrier, to simultaneously transmit the one or more FL communications and transmit one or more uplink communications via a second uplink carrier of the frequency band, or to simultaneously receive the one or more BL communications and transmit one or more uplink transmissions via the second uplink carrier.

In some examples of the method, first network entities, and non-transitory computer-readable medium described herein, the third network entity may be capable of reception or transmission via at least one of amplitude-shift keying (ASK) modulation or frequency-shift keying (FSK) modulation.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example of a wireless communications system that supports reporting capability information for communicating with ambient internet of things (A-IoT) devices in accordance with one or more aspects of the present disclosure.

FIG. 2 shows an example of a wireless communications system that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure.

FIG. 3 shows an example of a signaling diagram that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure.

FIG. 4 shows an example of a signaling diagram that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure.

FIG. 5 shows an example of a signaling diagram that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure.

FIGs. 6A and 6B show examples of signaling diagrams that support reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure.

FIG. 7 shows an example of a signaling diagram that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure.

FIG. 8 shows an example of a signaling diagram that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure.

FIG. 9 shows an example of a process flow that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure.

FIGs. 10 and 11 show block diagrams of devices that support reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure.

FIG. 12 shows a block diagram of a communications manager that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure.

FIG. 13 shows a diagram of a system including a device that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure.

FIGs. 14 and 15 show block diagrams of devices that support reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure.

FIG. 16 shows a block diagram of a communications manager that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure.

FIG. 17 shows a diagram of a system including a device that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure.

FIGs. 18 through 20 show flowcharts illustrating methods that support reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure.

DETAILED DESCRIPTION

In some wireless communications systems, a user equipment (UE) may function as a reader device for an ambient internet-of-things (A-IoT) device. The A-IoT device may be an energy-harvesting device that may have relatively less energy storage capabilities than the UE. Accordingly, the A-IoT device may communicate with the UE by receiving forward link (FL) messages via an uplink frequency band and transmitting backward link (BL) messages via the uplink frequency band by backscattering a continuous-wave (CW) signal from the UE. In some examples, however, the UE may not be capable of simultaneously transmitting CW signals and receive BL messages via the same carrier (e.g., the uplink frequency band) . In some examples, the UE may not be capable of simultaneously transmitting or receiving FL or BL messages (e.g., or CW signals) via the uplink frequency band and receiving or transmitting downlink or uplink messages from or to a network entity via a different frequency band.

Accordingly, techniques described herein may enable the UE to transmit a capability report indicating a capability to transmit FL messages and CW signals and to receive BL messages via a same carrier, and/or to simultaneously transmit or receive FL messages, BL messages, CW signals, uplink messages, and/or downlink messages via paired or unpaired carriers. In some examples, based on the UE capability, a network entity may schedule the UE to transmit or receive FL messages, BL messages, CW signals, uplink messages, and/or downlink messages simultaneously or at different times (e.g., with a time gap) via paired or unpaired carriers. In some examples, based on the UE capability, the UE may drop transmission or reception of one or more FL messages, BL messages, CW signals, uplink messages, and/or downlink messages (e.g., if one or more of the messages are scheduled simultaneously and if the UE may not transmit and/or receive the one or more of the messages simultaneously) .

Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to signaling diagrams, process flows, apparatus diagrams, system diagrams, and flowcharts that relate to reporting capability information for communicating with A-IoT devices.

FIG. 1 shows an example of a wireless communications system 100 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more devices, such as one or more network devices (e.g., network entities 105) , one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

As described herein, a network entity (which may alternatively be referred to as an entity, a node, a network node, or a wireless entity) may be, be similar to, include, or be included in (e.g., be a component of) a base station (e.g., any base station described herein, including a disaggregated base station) , a UE (e.g., any UE described herein) , a reduced capability (RedCap) device, an enhanced reduced capability (eRedCap) device, an ambient internet-of-things (IoT) device, an energy harvesting (EH) -capable device, a network controller, an apparatus, a device, a computing system, an integrated access and backhauling (IAB) node, a distributed unit (DU) , a central unit (CU) , a remote/radio unit (RU) (which may also be referred to as a remote radio unit (RRU) ) , and/or another processing entity configured to perform any of the techniques described herein. For example, a network entity may be a UE. As another example, a network entity may be a base station. As used herein, “network entity” may refer to an entity that is configured to operate in a network, such as the network 105. For example, a “network entity” is not limited to an entity that is currently located in and/or currently operating in the network. Rather, a network entity may be any entity that is capable of communicating and/or operating in the network.

The adjectives “first, ” “second, ” “third, ” and so on are used for contextual distinction between two or more of the modified noun in connection with a discussion and are not meant to be absolute modifiers that apply only to a certain respective entity throughout the entire document. For example, a network entity may be referred to as a “first network entity” in connection with one discussion and may be referred to as a “second network entity” in connection with another discussion, or vice versa. As an example, a first network entity may be configured to communicate with a second network entity or a third network entity. In one aspect of this example, the first network entity may be a UE, the second network entity may be a base station, and the third network entity may be a UE. In another aspect of this example, the first network entity may be a UE, the second network entity may be a base station, and the third network entity may be a base station. In yet other aspects of this example, the first, second, and third network entities may be different relative to these examples.

Similarly, reference to a UE, base station, apparatus, device, computing system, or the like may include disclosure of the UE, base station, apparatus, device, computing system, or the like being a network entity. For example, disclosure that a UE is configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity. Consistent with this disclosure, once a specific example is broadened in accordance with this disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity) , the broader example of the narrower example may be interpreted in the reverse, but in a broad open-ended way. In the example above where a UE is configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity, the first network entity may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first set of one or more one or more components, a first processing entity, or the like configured to receive the information; and the second network entity may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second set of one or more components, a second processing entity, or the like.

As described herein, communication of information (e.g., any information, signal, or the like) may be described in various aspects using different terminology. Disclosure of one communication term includes disclosure of other communication terms. For example, a first network entity may be described as being configured to transmit information to a second network entity. In this example and consistent with this disclosure, disclosure that the first network entity is configured to transmit information to the second network entity includes disclosure that the first network entity is configured to provide, send, output, communicate, or transmit information to the second network entity. Similarly, in this example and consistent with this disclosure, disclosure that the first network entity is configured to transmit information to the second network entity includes disclosure that the second network entity is configured to receive, obtain, or decode the information that is provided, sent, output, communicated, or transmitted by the first network entity.

As shown, the network entity (e.g., network entity 105) may include a processing system 106. Similarly, the network entity (e.g., UE 115) may include a processing system 112. A processing system may include one or more components (or subcomponents) , such as one or more components described herein. For example, a respective component of the one or more components may be, be similar to, include, or be included in at least one memory, at least one communication interface, or at least one processor. For example, a processing system may include one or more components. In such an example, the one or more components may include a first component, a second component, and a third component. In this example, the first component may be coupled to a second component and a third component. In this example, the first component may be at least one processor, the second component may be a communication interface, and the third component may be at least one memory. A processing system may generally be a system one or more components that may perform one or more functions, such as any function or combination of functions described herein. For example, one or more components may receive input information (e.g., any information that is an input, such as a signal, any digital information, or any other information) , one or more components may process the input information to generate output information (e.g., any information that is an output, such as a signal or any other information) , one or more components may perform any function as described herein, or any combination thereof. As described herein, an “input” and “input information” may be used interchangeably. Similarly, as described herein, an “output” and “output information” may be used interchangeably. Any information generated by any component may be provided to one or more other systems or components of, for example, a network entity described herein) . For example, a processing system may include a first component configured to receive or obtain information, a second component configured to process the information to generate output information, and/or a third component configured to provide the output information to other systems or components. In this example, the first component may be a communication interface (e.g., a first communication interface) , the second component may be at least one processor (e.g., that is coupled to the communication interface and/or at least one memory) , and the third component may be a communication interface (e.g., the first communication interface or a second communication interface) . For example, a processing system may include at least one memory, at least one communication interface, and/or at least one processor, where the at least one processor may, for example, be coupled to the at least one memory and the at least one communication interface.

A processing system of a network entity described herein may interface with one or more other components of the network entity, may process information received from one or more other components (such as input information) , or may output information to one or more other components. For example, a processing system may include a first component configured to interface with one or more other components of the network entity to receive or obtain information, a second component configured to process the information to generate one or more outputs, and/or a third component configured to output the one or more outputs to one or more other components. In this example, the first component may be a communication interface (e.g., a first communication interface) , the second component may be at least one processor (e.g., that is coupled to the communication interface and/or at least one memory) , and the third component may be a communication interface (e.g., the first communication interface or a second communication interface) . For example, a chip or modem of the network entity may include a processing system. The processing system may include a first communication interface to receive or obtain information, and a second communication interface to output, transmit, or provide information. In some examples, the first communication interface may be an interface configured to receive input information, and the information may be provided to the processing system. In some examples, the second system interface may be configured to transmit information output from the chip or modem. The second communication interface may also obtain or receive input information, and the first communication interface may also output, transmit, or provide information.

The network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 115 may wirelessly communicate via communication link (s) 125 (e.g., a radio frequency (RF) access link) . For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish the communication link (s) 125. The coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .

The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices in the wireless communications system 100 (e.g., other wireless communication devices, including UEs 115 or network entities 105) , as shown in FIG. 1.

As described herein, a node of the wireless communications 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, a node may be a UE 115. As another example, a 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, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.

In some examples, network entities 105 may communicate with a core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via backhaul communication link (s) 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol) . In some examples, network entities 105 may communicate with one another via backhaul communication link (s) 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via the core network 130) . In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof. The backhaul communication link (s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) or one or more wireless links (e.g., a radio link, a wireless optical link) , among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.

One or more of the network entities 105 or network equipment described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) . In some examples, a network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within one network entity (e.g., a network entity 105 or a single RAN node, such as a base station 140) .

In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105) , such as an integrated access and 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, a network entity 105 may include one or more of a central unit (CU) , such as a CU 160, a distributed unit (DU) , such as a DU 165, a radio unit (RU) , such as an RU 170, a RAN Intelligent Controller (RIC) , such as an 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) system, such as an SMO system 180, or any combination thereof. An 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 transmission reception point (TRP) . One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations) . In some examples, one or more of the network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .

The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3) , layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) . The CU 160 (e.g., one or more CUs) may be connected to a DU 165 (e.g., one or more DUs) or an RU 170 (e.g., one or more RUs) , or some combination thereof, and the DUs 165, RUs 170, or both 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 a DU 165 and an 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 multiple different cells (e.g., via one or multiple different RUs, such as an RU 170) . In some cases, a functional split between a CU 160 and a DU 165 or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170) . A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to a DU 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to an RU 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface) . In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities (e.g., one or more of the network entities 105) that are in communication via such communication links.

In some wireless communications systems (e.g., the wireless communications system 100) , infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130) . In some cases, in an IAB network, one or more of the network entities 105 (e.g., network entities 105 or IAB node (s) 104) may be partially controlled by each other. The IAB node (s) 104 may be referred to as a donor entity or an IAB donor. A DU 165 or an RU 170 may be partially controlled by a CU 160 associated with a network entity 105 or base station 140 (such as a donor network entity or a donor base station) . The one or more donor entities (e.g., IAB donors) may be in communication with one or more additional devices (e.g., IAB node (s) 104) via supported access and backhaul links (e.g., backhaul communication link (s) 120) . IAB node (s) 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DUs 165) of a coupled IAB donor. An IAB-MT may be equipped with an independent set of antennas for relay of communications with UEs 115 or may share the same antennas (e.g., of an RU 170) of IAB node (s) 104 used for access via the DU 165 of the IAB node (s) 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) . In some examples, the IAB node (s) 104 may include one or more DUs (e.g., DUs 165) that support communication links with additional entities (e.g., IAB node (s) 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream) . In such cases, one or more components of the disaggregated RAN architecture (e.g., the IAB node (s) 104 or components of the IAB node (s) 104) may be configured to operate according to the techniques described herein.

In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support test 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 disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180) .

A 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 terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A 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, a UE 115 may include or 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 communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, vehicles, or meters, among other examples.

The UEs 115 described herein may be able to communicate with various types of devices, such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.

The UEs 115 and the network entities 105 may wirelessly communicate with one another via the communication link (s) 125 (e.g., one or more access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link (s) 125. For example, a carrier used for the communication link (s) 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR) . Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information) , control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105. For example, the terms “transmitting, ” “receiving, ” or “communicating, ” when referring to a network entity 105, may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities, such as one or more of the network entities 105) .

In some examples, such as in a carrier aggregation configuration, a carrier may have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN) ) and may be identified according to a channel raster for discovery by the UEs 115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different RAT) .

The communication link (s) 125 of the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode) .

A carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular RAT (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) . Devices of the wireless communications system 100 (e.g., the network entities 105, the UEs 115, or both) may have hardware configurations that support communications using a particular carrier bandwidth or may be configurable to support communications using one of a set of carrier bandwidths. In some examples, the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.

Signal waveforms transmitted via a carrier may be made up of 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 resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity 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 a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.

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

The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of T_s=1/ (Δf_max·N_f) seconds, for which Δf_max may represent a supported subcarrier spacing, and N_f may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource 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) .

Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) . In some wireless communications systems, such as the wireless communications system 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N_f) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

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

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

In some examples, a network entity 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110. In some examples, coverage areas 110 (e.g., different coverage areas) associated with different technologies may overlap, but the coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., a network entity 105) . In some other examples, overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (e.g., the network entities 105) . The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.

The wireless communications system 100 may support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base stations 140) may have similar frame timings, and transmissions from different network entities (e.g., different ones of the network entities 105) may be approximately aligned in time. For asynchronous operation, network entities 105 may have different frame timings, and transmissions from different network entities (e.g., different ones of network entities 105) may, in some examples, not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.

Some UEs 115, such as MTC or IoT devices, may be relatively low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication) . M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) . The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications 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.

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

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 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (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 stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.

The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) . Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) RAT, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA) . Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115 may be located within 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, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.

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 steer 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 the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .

In some examples, the wireless communications system 100 may support full-duplex communications, in which a UE 115 or a network entity 105 may perform simultaneous communication of downlink signaling and communication of uplink signaling on a frequency subband basis (e.g., across a set of frequencies) . For example, for SBFD communications, the network entity 105 may partition a particular frequency band or carrier (e.g., 100 MHz) into subbands which the network entity 105 may use exclusively for uplink or downlink communications. For example, the network entity 105 or the UE 115 may use the 40 MHz of a 100 MHz band for downlink communications, 20 MHz for uplink communications, and another 40 MHz again for downlink communications. That is, the uplink and downlink subbands may have relatively similar frequencies, however, may be non-overlapping in frequency. Full-duplex communications may be suitable for macro cells with a large transmit power, and may be relatively simpler to enable than other full-duplex techniques. In some examples, such SBFD communication techniques may also support a dedicated frequency band for supplementary uplink communications, as described with reference to FDD and TDD communications.

To further enhance flexibility of some operations, the wireless communications system 100 may support UEs 115 and network entities 105 which may both perform simultaneous transmission and reception of downlink and uplink communications via partially or fully overlapping frequency bands. For example, the wireless communications system 100 may support a network entity 105 that operates using full-duplex communications via partially overlapping frequency bands, or a network entity 105 that operates using half-duplex communications (e.g., in a multi-transmission reception point (mTRP) ) scenario) and a UE 115 that operates using full-duplex communications.

In some scenarios, network entities 105 in the wireless communications system 100 may support full-duplex operations (e.g., where a network entity 105 may communicate simultaneously on uplink and downlink sub-bands that are non-overlapping in frequency) , while UEs 115 may support half-duplex communications. For example, the network entity 105 may use a particular sub-band for transmitting downlink communications to a first UE 115, and a particular sub-band for receiving simultaneous uplink communications from a second UE 115. As such, a UE 115 capable of half-duplex communications may be paired with any network entity 105 capable of full-duplex operations in the wireless communications system 100.

In some examples, the network entity 105 may use IBFD communications, in which the network entity 105 may transmit and receive communications with a UE 115 via a same time resource and a same frequency resource. That is, the downlink and uplink may share same IBFD time and frequency resources, which may partially or fully overlap. Alternatively, the network entity 105 may use SBFD (e.g., flexible duplex) communications, in which the network entity 105 may transmit and receive communications with the UE 115 via a same time resource but via different frequency resources. That is, a frequency resource used for downlink communications may be separated from a frequency resource used for uplink communications (e.g., by a guard band) . In some examples, the network entity 105 may use SBHD, in which the network entity 105 may transmit and receive communications with the UE 115 via frequency subbands that do not overlap in time or frequency. Such techniques may allow for the network entity 105 to transition between a half-duplex mode (e.g., TDD or FDD) and a full-duplex mode (e.g., SBFD, IBFD) .

In some examples, a A-IoT device (e.g., a tag, an EH-capable device) , which may be an example of a UE 115, may be a passive, semi-passive, or active A-IoT device. For example, if the A-IoT device is a passive device, the A-IoT device may communicate using backscattering techniques. If the A-IoT device is a semi-passive device, the A-IoT device may communicate using backscattering techniques and using additional energy in energy storage (e.g., powering integrated circuit (IC) , amplifying reflected signal) with LO turn off and amplifier turn on. If the A-IoT device is an active device, the A-IoT device may communicate with active signal generation method using energy stored in energy storage (e.g., amplifying signals, using active RF components, better filtering, more complex baseband (BB) processing, and using clocks with higher accuracy) with LO turn on and amplifier turn on. In some examples, A-IoT devices may be devices with a fixed length of a unique identifier (ID) , such as an A-IoT ID or a Tag ID. A-IoT devices may be devices that are able to receive FL communications using on-off keying (OOK) modulation, amplitude shift keying (ASK) modulation, and/or frequency shift keying (FSK) modulation. A-IoT devices may be devices that are able to transmit BL (or reverse-link) communications using OOK modulation, ASK modulation, FSK modulation, and/or phase-shift keying (PSK) modulation. A-IoT devices may transmit BL messages with backscattering externally received or internally generated carrier wave (e.g., CW signals) or carrier frequency generated internally (e.g., in the case of semi-passive or active A-IoT devices) . As described herein, full-duplex communications with an A-IoT device may refer to simultaneous transmission (e.g., of CW signals) and reception (e.g., of BL messages) via a same carrier in non-overlapping frequency resources.

Techniques described herein may enable a UE 115 to transmit a capability report to a network entity 105 indicating a capability to transmit FL messages and CW signals and to receive BL messages to an A-IoT device via a same carrier. The capability report may, additionally, or alternatively, indicate a capability of the UE 115 to simultaneously transmit or receive FL messages, BL messages, CW signals, uplink messages, and/or downlink messages via paired or unpaired carriers. In some examples, based on the UE capability, a network entity may schedule the UE to transmit or receive FL messages, BL messages, CW signals, uplink messages, and/or downlink messages simultaneously or at different times (e.g., with a time gap) via paired or unpaired carriers. In some examples, based on the UE capability, the UE may drop transmission or reception of one or more FL messages, BL messages, CW signals, uplink messages, and/or downlink messages (e.g., if one or more of the messages are scheduled simultaneously and if the UE may not transmit and/or receive the one or more of the messages simultaneously) .

FIG. 2 shows an example of a wireless communications system 200 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The wireless communications system 200 may implement or may be implemented by aspects of the wireless communications system 100. For example, the wireless communications system 200 may include a UE 115 (e.g., a UE 115-a) and a network entity 105 (e.g., a network entity 105-a) , which may be examples of the corresponding devices as described with reference to FIG. 1.

In some examples of the wireless communications system 200, an A-IoT device 205 may operate in one or more topologies. For example, in a first topology, the A-IoT device 205 may receive one or more FL messages 215 from a network entity 105 (e.g., FL control or data messages, including a FL preamble 225) via a FDD downlink carrier. The A-IoT device 205 may transmit one or more BL messages 220 to the network entity 105 via a FDD uplink carrier (e.g., paired or unpaired with the FDD downlink carrier) by backscattering one or more CW signals 210 from the network entity 105. The A-IoT device may receive the backscattered CW signals via a central frequency and may transmit the BL messages 220 via frequency bands on either side of the central frequency. The A-IoT device 205 and the network entity 105 may therefore support FL, CW, and BL via the FDD uplink carrier. The network entity 105 may support full-duplex operations to enable simultaneous CW transmission and BL reception.

In some examples of a second topology, as illustrated with reference to FIG. 2, the A-IoT device may receive the one or more FL messages 215 including the FL preamble 225 from a reader device (e.g., a UE 115-a) via a FDD uplink carrier 230. The UE 115-a may transmit the CW signal 210 and may receive the BL messages 220 from the A-IoT device via the FDD uplink carrier 230. The UE 115-a may receive a scheduling grant 245 (e.g., a L1 control grant, a medium access control-control element (MAC-CE) , an RRC message) from a network entity 105-a (e.g., via an FDD downlink carrier 235) scheduling the one or more FL messages 215 and the one or more BL messages 220. The UE 115-a may therefore support receiving downlink via the FDD downlink carrier 235 and transmitting uplink via an FDD uplink carrier 240, and the UE 115-a and the A-IoT device 205 may support FL, CW, and BL via the FDD uplink carrier 230. The UE 105-a may support full-duplex operations to enable simultaneous CW transmission and BL reception via the FDD uplink carrier 230. In some examples, a reader device may be an extra RF antenna equipped on the network entity 105-a that may imitate a virtual UE 115 to enable transmission via the FDD uplink carrier 230.

In some examples, a reader device for the second topology (e.g., the UE 115-a) may be a special device equipped with specific hardware or software enabling reader functions (e.g., in addition to or instead of other UE functionalities) . In some examples, the reader device may be a first UE 115 such as a smartphone supporting communication via the FDD uplink carrier 230 (e.g., with extra capability enabling UE reader functionalities) , a RedCap or eRedCap UE 115 supporting communication via the FDD uplink carrier 230, or an advanced UE 115 supporting carrier aggregation (CA) and/or dual connectivity (DC) via the uplink carrier 230, one or more additional uplink carriers 240, and one or more downlink carriers 235 (e.g., unpaired with the uplink carrier 230) . For example, the advanced UE 115 may support connectivity via multiple carriers (e.g., unpaired carriers) . The advanced UE 115 may switch between the multiple carriers to communicate with one or more network entities 105.

In the example of the first UE 115, the UE 115-a may have capabilities or limitations related to transmitting FL messages 215 and CW signals 210 via the uplink carrier 230 (e.g., due to timing or transmission power differences) . Additionally, or alternatively, the UE 115-a may have capabilities or limitations related to receiving BL messages 220 via the uplink carrier 230 (e.g., due to timing or transmission power differences) . The UE 115-a may have capabilities or limitations related to simultaneous transmission and/or reception within the uplink carrier 230. Additionally, or alternatively, the UE 115-a may have one or more full-duplex capabilities or limitations related to simultaneous CW signal 210 transmission and BL message 220 reception.

In the example of the RedCap or eRedCap UE 115, the UE 115-a may be a special device designated as the UE reader, and may not support gigabits per second (Gbps) -class data rates, 100 MHz bandwidth, multiple frequency bands, CA/DC, and non-standalone (NSA) deployment. The UE 115-a may have capabilities or limitations related to transmitting FL messages 215 and CW signals 210 via the uplink carrier 230 (e.g., due to timing or transmission power differences) . Additionally, or alternatively, the UE 115-a may have capabilities or limitations related to receiving BL messages 220 via the uplink carrier 230 (e.g., due to timing or transmission power differences) . The UE 115-a may have capabilities or limitations related to simultaneous transmission and/or reception within the uplink carrier 230. Additionally, or alternatively, the UE 115-a may have one or more full-duplex capabilities or limitations related to simultaneous CW signal 210 transmission and BL message 220 reception, and/or related to simultaneous FL transmission via the uplink carrier 230 and downlink reception via the downlink carrier 235.

In the example of the advanced UE 115 supporting CA/DC, the UE 115-a may support communications via various frequency bands (e.g., paired or unpaired carriers, such as the uplink carrier 230, the uplink carrier 240, and the downlink carrier 235) . The UE 115-a may support UE reader functionalities in addition to other features supported by the UE 115-a, such as CA/DC. The UE 115-a may have capabilities or limitations related to transmitting FL messages 215 and CW signals 210 via the uplink carrier 230 (e.g., due to timing or transmission power differences) . Additionally, or alternatively, the UE 115-a may have capabilities or limitations related to receiving BL messages 220 via the uplink carrier 230 (e.g., due to timing or transmission power differences) . The UE 115-a may have capabilities or limitations related to simultaneous transmission and/or reception within the uplink carrier 230. Additionally, or alternatively, the UE 115-a may have one or more full-duplex capabilities or limitations related to simultaneous CW signal 210 transmission and BL message 220 reception.

If the UE 115-a supports CA/DC, the UE 115-a may have one or more capabilities or limitations related to communicating with the A-IoT device 205 and communicating via one or more carriers that are unpaired with the uplink carrier 230 (e.g., the downlink carrier 235, the uplink carrier 240) . For example, the one or more capabilities or limitations may include simultaneously transmitting CW signals 210 or FL messages 215 via the uplink carrier 230 and transmitting uplink messages via the uplink carrier 240, simultaneously receiving BL messages 220 and receiving downlink messages via the downlink carrier 235, and/or simultaneously receiving BL messages 220 and transmitting uplink messages via the uplink carrier 240.

Accordingly, techniques described herein may enable the UE 115-a to transmit a capability report 250 to the network entity 105-a indicting the capabilities of the UE 115-a to communicate with the A-IoT device 205. For example, the UE 115-a may report capability signaling including one or more frequency bands via which the UE 115-a supports reader functionalities (e.g., FL, BL and CW transmission and reception) . The UE 115-a may report a capability or limitation of the UE 115-a to perform simultaneous transmission of CW signals 210 and reception of BL messages 220 (e.g., a full-duplex capability) , simultaneous BL reception via the uplink carrier 230 and downlink reception via the downlink carrier 235 (e.g., paired with the uplink carrier 230) , and/or simultaneous FL transmission via the uplink carrier 230 and downlink reception via the downlink carrier 235 (e.g., paired with the uplink carrier 230. In some examples, a RedCap UE or an eRedCap UE may not support simultaneous forward link transmission and downlink reception.

In some examples, if the UE 115-a supports CA/DC, the UE 115-a may additionally or alternatively report a capability of the UE 115-a to simultaneously transmit CW signals 210 and receive BL messages 220 via a same carrier (e.g., the uplink carrier 230) or via different carriers (e.g., a full-duplex capability) , to simultaneously transmit FL messages 215 and/or CW signals 210 via the uplink carrier 230 and transmit uplink messages via the uplink carrier 240 (e.g., a carrier unpaired with the uplink carrier 230) , to switch between transmitting via the uplink carrier 230 and the uplink carrier 240, to simultaneously receive BL messages 220 via the uplink carrier 230 and receive downlink messages via the downlink carrier 235 (e.g., unpaired with the uplink carrier 230) , or to simultaneously receive BL messages 220 via the uplink carrier 230 and transmit uplink messages via the uplink carrier 240 (e.g., unpaired with the uplink carrier 230) .

In some examples, the network entity 105-a may schedule the UE 115-a with communications in accordance with the capability. That is, if the UE 115-a reports a limitation to perform communications simultaneously or via some carriers, the network entity 105-a may not schedule the communications to be simultaneous. In some examples, the UE 115-a may drop one or more simultaneous transmissions in accordance with the capability (e.g., according to one or more dropping rules) . Such techniques are described in further detail with reference to FIGs. 3–8.

FIG. 3 shows an example of a signaling diagram 300 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The signaling diagram 300 may implement or may be implemented by aspects of the wireless communications system 100 or the wireless communications system 200. For example, the signaling diagram 300 may be implemented by a UE 115 and a network entity 105, which may be examples of the corresponding devices as described with reference to FIG. 1.

In some examples, a UE 115 may transmit a capability report indicating that the UE 115 does not support full-duplex for transmitting CW signals 310 and receiving BL messages 315 simultaneously via an uplink carrier 325 (e.g., via non-overlapping frequency resources) . In such examples, the UE 115 may receive one or more scheduling grants 305 from a network entity 105 (e.g., a L1 scheduling grant, a MAC-CE message, an RRC message) via a downlink carrier 320 that indicates for the UE 115 to either transmit CW signals 310 or receive BL messages 315. That is, the UE 115 may treat CW signals 310 and BL messages 315 that are scheduled to occur simultaneously as an error case.

Additionally, or alternatively, if the UE 115 receives one or more scheduling grants 305 that schedules the CW signals 310 and the BL messages 315 to occur simultaneously, the UE 115 may drop one or both of the CW signals 310 and the BL messages 315 (e.g., according to one or more rules) . For example, the one or more rules may state for the UE 115 to drop the CW signals 310 or to drop the BL messages 315. In some examples, the UE 115 may receive a configuration of the one or more rules from the network entity 105 (e.g., via RRC, MAC-CE, downlink control information (DCI) , or the like) .

In some examples, the UE 115-a may report a capability to transmit the CW signals 310 via a first carrier and to receive the BL messages 315 via a second carrier (e.g., unpaired or paired with the first carrier) . In such examples, the one or more scheduling grant 305 may indicate for the UE 115 to transmit the CW signals 310 via the uplink carrier 325 and to receive the BL messages 315 via one or more other carriers (e.g., other uplink or downlink carriers that are paired or unpaired with the uplink carrier 325, such as the downlink carrier 320) .

FIG. 4 shows an example of a signaling diagram 400 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The signaling diagram 400 may implement or may be implemented by aspects of the wireless communications system 100, the wireless communications system 200, or the signaling diagram 300. For example, the signaling diagram 400 may be implemented by a UE 115 and a network entity 105, which may be examples of the corresponding devices as described with reference to FIG. 1.

In some examples, a UE 115 may transmit a capability report indicating that the UE 115 does not support simultaneously receiving BL messages 415 via an uplink carrier 425 and receiving downlink messages 410 via a downlink carrier 420 (e.g., paired with the uplink carrier 425) . In such examples, the UE 115 may receive one or more scheduling grants 405 from a network entity 105 (e.g., a L1 scheduling grant, a MAC-CE message, an RRC message) via the downlink carrier 420 that indicates for the UE 115 to either receive downlink messages 410 or receive BL messages 415 at a given time. That is, the UE 115 may treat downlink messages 410 and BL messages 415 that are scheduled to occur simultaneously as an error case.

Additionally, or alternatively, if the UE 115 receives one or more scheduling grants 405 that schedules the downlink messages 410 and the BL messages 415 to occur simultaneously, the UE 115 may drop one or both of the downlink messages 410 and the BL messages 415 (e.g., according to one or more rules) . For example, the one or more rules may state for the UE 115 to drop the downlink messages 410 or to drop the BL messages 415 depending on a type of downlink message 410 (e.g., synchronization signal block (SSB) , physical downlink control channel (PDCCH) common search space (CSS) , a PDCCH UE-specific search space (USS) , a semi-persistent scheduled (SPS) physical downlink shared channel (PDSCH) , or a dynamically scheduled PDSCH) .

Table 1 provides an illustrative example of the one or more rules.

Table 1

Although the one or more rules illustrated by Table 1 provide illustrative examples of handling rules for various types of downlink transmissions, in some examples, the one or more rules may be different than the rules illustrated by Table 1. For example, the one or more rules may state for the UE 115 to prioritize SPS PDSCH reception over BL reception. Additionally, the one or more rules may instruct for the UE 115 to prioritize or drop one or more other types of downlink transmissions over BL transmissions. In some examples, the UE 115 may receive a configuration of the one or more rules (e.g., a configuration of the table) from the network entity 105 (e.g., via RRC, MAC-CE, DCI, or the like) .

FIG. 5 shows an example of a signaling diagram 500 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The signaling diagram 500 may implement or may be implemented by aspects of the wireless communications system 100, the wireless communications system 200, the signaling diagram 300, or the signaling diagram 400. For example, the signaling diagram 500 may be implemented by a UE 115 and a network entity 105, which may be examples of the corresponding devices as described with reference to FIG. 1.

In some examples, a UE 115 may transmit a capability report indicating that the UE 115 does not support simultaneously transmitting FL messages 515 (e.g., or CW signals) via an uplink carrier 525 and receiving downlink messages 510 via a downlink carrier 520 (e.g., unpaired with the uplink carrier 525) . In such examples, the UE 115 may receive one or more scheduling grants 505 from a network entity 105 (e.g., a L1 scheduling grant, a MAC-CE message, an RRC message) via the downlink carrier 520 that indicates for the UE 115 to either receive downlink messages 510 or transmit FL messages 515 or CW signals at a given time. That is, the UE 115 may treat downlink messages 510 and FL messages 515 or CW signals that are scheduled to occur simultaneously as an error case.

Additionally, or alternatively, if the UE 115 receives one or more scheduling grants 505 that schedules the downlink messages 510 and the FL messages 515 (e.g., or CW signals) to occur simultaneously, the UE 115 may drop one or both of the downlink messages 510 and the FL messages 515 or CW signals (e.g., according to one or more rules) . For example, the one or more rules may state for the UE 115 to drop the downlink messages 510 or to drop the FL messages 515 or CW signals depending on a type of downlink message 510 (e.g., SSB, PDCCH CSS, a PDCCH USS, a dedicated RRC, or a dynamically scheduled PDSCH) . Table 2 provides an illustrative example of the one or more rules.

Table 2

Although the one or more rules illustrated by Table 2 provide illustrative examples of handling rules for various types of downlink transmissions, in some examples, the one or more rules may be different than the rules illustrated by Table 2. For example, the one or more rules may state for the UE 115 to prioritize dedicated RRC reception over FL transmission. Additionally, the one or more rules may instruct for the UE 115 to prioritize or drop one or more other types of downlink transmissions over FL or CW transmissions. In some examples, the UE 115 may receive a configuration of the one or more rules (e.g., a configuration of the table) from the network entity 105 (e.g., via RRC, MAC-CE, DCI, or the like) .

FIGs. 6A and 6B show examples of a signaling diagram 600-a and a signaling diagram 600-b that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The signaling diagrams 600-a and 600-b may implement or may be implemented by aspects of the wireless communications system 100, the wireless communications system 200, the signaling diagram 300, the signaling diagram 400, or the signaling diagram 500. For example, the signaling diagrams 600 may be implemented by a UE 115 and a network entity 105, which may be examples of the corresponding devices as described with reference to FIG. 1.

In some examples, a UE 115 may transmit a capability report indicating that the UE 115 does not support simultaneously transmitting FL messages 615 (e.g., or CW signals) via an uplink carrier 625 and transmitting uplink messages 610 via an uplink carrier 630 (e.g., unpaired with the uplink carrier 625) . In such examples, the UE 115 may receive one or more scheduling grants 605 from a network entity 105 (e.g., a L1 scheduling grant, a MAC-CE message, an RRC message) via a downlink carrier 620 (e.g., paired with the uplink carrier 625) that indicates for the UE 115 to either transmit uplink messages 610 via the uplink carrier 630 or transmit FL messages 615 or CW signals via the uplink carrier 625 at a given time. That is, the UE 115 may treat uplink messages 610 and FL messages 615 or CW signals that are scheduled to occur simultaneously as an error case.

In some aspects, a UE 115 may indicate (e.g., via the capability report) a time gap 635 (e.g., T_offset) supported by the UE 115 for switching between transmitting via the uplink carrier 625 and transmitting via the uplink carrier 630. The time gap 635 may be based on a time for the UE 115 to switch and/or tune one or more transmitting antenna chains. In such examples, the network entity 105 may schedule the UE 115 to transmit FL messages 615 (e.g., or CW signals) via the uplink carrier 625 during a first transmission duration and to transmit uplink messages 610 via the uplink carrier 630 during a second transmission duration that is at least T_offset after the first transmission duration, as illustrated with reference to FIG. 6A.

Additionally, or alternatively, if the UE 115 receives one or more scheduling grants 605 that schedules the uplink messages 610 and the FL messages 615 (e.g., or CW signals) to occur simultaneously (e.g., or within a time duration smaller than the time gap 635) , as illustrated with reference to FIG. 6B, the UE 115 may drop one or both of the uplink messages 610 and the FL messages 615 or CW signals (e.g., according to one or more rules) . For example, the one or more rules may state for the UE 115 to drop the uplink messages 610 or to drop the FL messages 615 or CW signals. In some examples, the UE 115 may receive a configuration of the one or more rules from the network entity 105 (e.g., via RRC, MAC-CE, DCI, or the like) .

FIG. 7 shows an example of a signaling diagram 700 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The signaling diagram 700 may implement or may be implemented by aspects of the wireless communications system 100, the wireless communications system 200, the signaling diagram 300, the signaling diagram 400, the signaling diagram 500, or the signaling diagrams 600. For example, the signaling diagram 700 may be implemented by a UE 115 and a network entity 105, which may be examples of the corresponding devices as described with reference to FIG. 1.

In some examples, a UE 115 may transmit a capability report indicating that the UE 115 does not support simultaneously receiving BL messages 715 via an uplink carrier 725 and receiving downlink messages 710 via a downlink carrier 730 (e.g., unpaired with the uplink carrier 725) . In such examples, the UE 115 may receive one or more scheduling grants 705 from a network entity 105 (e.g., a L1 scheduling grant, a MAC-CE message, an RRC message) via a downlink carrier 720 (e.g., paired with the uplink carrier 725) that indicates for the UE 115 to either receive downlink messages 710 via the downlink carrier 730 or receive BL messages 715 via the uplink carrier 725 at a given time. That is, the UE 115 may treat downlink messages 710 and BL messages 715 that are scheduled to occur simultaneously as an error case.

Additionally, or alternatively, if the UE 115 receives one or more scheduling grants 705 that schedules the downlink messages 710 and the BL messages 715 to occur simultaneously, the UE 115 may drop one or both of the downlink messages 710 and the BL messages 715 (e.g., according to one or more rules) . For example, the one or more rules may state for the UE 115 to drop the downlink messages 710 or to drop the BL messages 715 depending on a type of downlink message 710 (e.g., SSB, PDCCH CSS, a PDCCH USS, a dedicated RRC, or a dynamically scheduled PDSCH) . Table 3 provides an illustrative example of the one or more rules.

Table 3

Although the one or more rules illustrated by Table 3 provide illustrative examples of handling rules for various types of downlink transmissions, in some examples, the one or more rules may be different than the rules illustrated by Table 3. For example, the one or more rules may state for the UE 115 to prioritize PDSCH reception over BL reception. Additionally, the one or more rules may instruct for the UE 115 to prioritize or drop one or more other types of downlink transmissions over BL transmissions. In some examples, the UE 115 may receive a configuration of the one or more rules (e.g., a configuration of the table) from the network entity 105 (e.g., via RRC, MAC-CE, DCI, or the like) .

FIG. 8 shows an example of a signaling diagram 800 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The signaling diagram 800 may implement or may be implemented by aspects of the wireless communications system 100, the wireless communications system 200, the signaling diagram 300, the signaling diagram 400, the signaling diagram 500, the signaling diagrams 600, or the signaling diagram 700. For example, the signaling diagram 800 may be implemented by a UE 115 and a network entity 105, which may be examples of the corresponding devices as described with reference to FIG. 1.

In some examples, a UE 115 may transmit a capability report indicating that the UE 115 does not support simultaneously receiving BL messages 815 via an uplink carrier 825 and transmitting uplink messages 810 via an uplink carrier 830 (e.g., unpaired with the uplink carrier 825) . In such examples, the UE 115 may receive one or more scheduling grants 805 from a network entity 105 (e.g., a L1 scheduling grant, a MAC-CE message, an RRC message) via a downlink carrier 820 (e.g., paired with the uplink carrier 825) that indicates for the UE 115 to either transmit uplink messages 810 via the uplink carrier 830 or receive BL messages 815 via the uplink carrier 825 at a given time. That is, the UE 115 may treat uplink messages 810 and BL messages 815 that are scheduled to occur simultaneously as an error case.

Additionally, or alternatively, if the UE 115 receives one or more scheduling grants 805 that schedules the uplink messages 810 and the BL messages 815 to occur simultaneously, the UE 115 may drop one or both of the uplink messages 810 and the BL messages 815 (e.g., according to one or more rules) . For example, the one or more rules may state for the UE 115 to drop the uplink messages 810 or to drop the BL messages 815 depending on a type of uplink message 810 (e.g., physical random access channel (PRACH) , semi-static physical uplink control channel (PUCCH) , dynamic PUCCH, semi-static physical uplink shared channel (PUSCH) , dynamic PUSCH, semi-static sounding reference signals (SRS) , dynamic SRS) . Table 4 provides an illustrative example of the one or more rules.

Table 4

Although the one or more rules illustrated by Table 4 provide illustrative examples of handling rules for various types of uplink transmissions, in some examples, the one or more rules may be different than the rules illustrated by Table 4. For example, the one or more rules may state for the UE 115 to prioritize semi-static SRS transmission over BL reception. Additionally, the one or more rules may instruct for the UE 115 to prioritize or drop one or more other types of uplink transmissions over BL transmissions. In some examples, the UE 115 may receive a configuration of the one or more rules (e.g., a configuration of the table) from the network entity 105 (e.g., via RRC, MAC-CE, DCI, or the like) .

FIG. 9 shows an example of a process flow 900 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The process flow 900 may implement or may be implemented by aspects of the wireless communications system 100, the wireless communications system 200, the signaling diagram 300, the signaling diagram 400, the signaling diagram 500, the signaling diagrams 600, the signaling diagram 700, or the signaling diagram 800. For example, the process flow 900 may include a UE 115 (e.g., a UE 115-b) and a network entity 105 (e.g., a network entity 105-b) , which may be examples of the corresponding devices as described with reference to FIG. 1.

In the following description of the process flow 900, the operations between the UE 115-b and the network entity 105-b may be transmitted in a different order than the example order shown. Some operations may also be omitted from the process flow 900, and other operations may be added to the process flow 900. Further, although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time.

At 905, the UE 115-b (e.g., a network entity) may transmit, to the network entity 105-b, a capability report that indicates a capability or a limitation of the UE 115--b to communicate with an A-IoT device 903 (e.g., a device or network entity that is capable of ASK modulation or FSK modulation) via a first carrier of a frequency band (e.g., an uplink carrier) . For example, the capability report may indicate a capability or a limitation of the UE 115-b to simultaneously transmit or receive one or more communications (e.g., CW signals, BL transmissions, FL transmissions, uplink transmissions, and/or downlink transmissions) via the first carrier and/or one or more additional carriers of the frequency band as described herein. In some examples, the one or more additional carriers of the frequency band may be a downlink carrier paired or unpaired with the first carrier, or a second uplink carrier unpaired with the first carrier.

The limitation may be a limitation of the UE 115-b to perform simultaneous communications. For example, the limitation may be an inability to simultaneously transmit the CW signals and receive the BL transmissions via the first carrier, an inability to simultaneously receive the BL transmissions via the first carrier and receive the downlink transmissions (e.g., via the downlink carrier paired or unpaired with the first carrier) , an inability to simultaneously transmit the FL transmissions via the first carrier and receive the downlink transmissions (e.g., via the downlink carrier paired or unpaired with the first carrier) , an inability to simultaneously receive the BL transmissions via the first carrier and transmit the uplink transmissions (e.g., via the uplink carrier unpaired with the first carrier) , and/or an inability to simultaneously transmit the FL transmissions via the first carrier and transmit the uplink transmissions (e.g., via the uplink carrier unpaired with the first carrier) . In some examples, the limitation may be a time duration (e.g., a time gap) for the UE 115-b to switch from transmitting via the first carrier and transmitting via the uplink carrier unpaired with the first carrier.

At 910, the UE 115-b may receive one or more scheduling grants from the network entity 105-b. The scheduling grants may schedule a communication between the UE 115-b and the A-IoT device 903, including one or more CW signals, FL transmissions, and/or BL transmissions via the first carrier. In some examples, the one or more scheduling grants may schedule for the UE 115-b to perform the communication in accordance with the capability. That is, the one or more scheduling grants may not schedule one or more simultaneous communications if the UE 115-b indicates an inability to simultaneously perform the one or more simultaneous communications. For example, if the UE 115-b indicates a time duration to switch from transmitting via the first carrier and transmitting via the uplink carrier unpaired with the first carrier, the one or more grants may indicate a time gap between FL transmissions via the first carrier and uplink transmissions via the uplink carrier unpaired with the first carrier.

In some examples, at 615, the UE 115-b may drop one or more communications (e.g., in accordance with a rule) . For example, if the UE 115-b reports an inability to simultaneously perform one or more communications, and the one or more scheduling grants indicate for the UE 115-b to perform the one or more communications simultaneously (e.g., or within the time durations) in violation of the limitation, the UE 115-b may drop one or more of the scheduled communications.

In some examples, the one or more dropped communications may be the one or more FL transmissions, the one or more BL transmissions, the CW signals, the downlink transmissions (e.g., SSBs, PDCCHs, PDSCHs, RRC messages) , or the one or more uplink transmissions (e.g., PRACHs, PUSCHs, PUCCHs, SRSs) . For example, the rule may indicate for the UE 115-b to prioritize the one or more FL transmissions, the one or more BL transmissions, the CW signals, the downlink transmissions (e.g., SSBs, PDCCHs, PDSCHs, RRC messages) , or the one or more uplink transmissions (e.g., PRACHs, PUSCHs, PUCCHs, SRSs) and to drop one or more other communications that are scheduled simultaneously.

At 920, the UE 115-b may perform the communication in accordance with the capability (e.g., or based on dropping one or more transmissions) . That is, the UE 115-b may communicate the CW signals, the FL transmissions, and/or the BL transmissions with the A-IoT device 903 via the first carrier. At 925, the UE 115-b may transmit an uplink transmission to the network entity 105-b via the uplink carrier unpaired with the first carrier (e.g., in accordance with the capability or in accordance with dropping one or more other transmissions) . At 930, the UE 115-b may receive a downlink transmission from the network entity 105-b via the downlink carrier paired or unpaired with the first carrier (e.g., in accordance with the capability or in accordance with dropping one or more other transmissions) .

FIG. 10 shows a block diagram 1000 of a device 1005 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The device 1005 may be an example of aspects of a UE 115 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020. The device 1005, or one or more components of the device 1005 (e.g., the receiver 1010, the transmitter 1015, the communications manager 1020) , may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .

The receiver 1010 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to reporting capability information for communicating with A-IoT devices) . Information may be passed on to other components of the device 1005. The receiver 1010 may utilize a single antenna or a set of multiple antennas.

The transmitter 1015 may provide a means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to reporting capability information for communicating with A-IoT devices) . In some examples, the transmitter 1015 may be co-located with a receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a set of multiple antennas.

The communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be examples of means for performing various aspects of reporting capability information for communicating with A-IoT devices as described herein. For example, the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

In some examples, the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include at least one of 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 configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .

Additionally, or alternatively, the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code) . If implemented in code executed by at least one processor, the functions of the communications 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, individually or collectively, a means for performing the functions described in the present disclosure) .

In some examples, the communications manager 1020 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager 1020 may support wireless communication in accordance with examples as disclosed herein. For example, the communications manager 1020 is capable of, configured to, or operable to support a means for transmitting a capability report that indicates a capability of the first network entity to communicate, via a first carrier of a frequency band, with a second network entity. The communications manager 1020 is capable of, configured to, or operable to support a means for receiving a grant that schedules a communication that includes one or more FL transmissions, one or more BL transmissions, one or more CW signals, or a combination thereof between the first network entity and the second network entity, where the communication is scheduled to occur via the first carrier. The communications manager 1020 is capable of, configured to, or operable to support a means for communicating with the second network entity via the first carrier in accordance with the grant and with the capability.

By including or configuring the communications manager 1020 in accordance with examples as described herein, the device 1005 (e.g., at least one processor controlling or otherwise coupled with the receiver 1010, the transmitter 1015, the communications manager 1020, or a combination thereof) may support techniques for reporting capability for communicating with an A-IoT device, which may allow for more efficient utilization of communication resources.

FIG. 11 shows a block diagram 1100 of a device 1105 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The device 1105 may be an example of aspects of a device 1005 or a UE 115 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communications manager 1120. The device 1105, or one or more components of the device 1105 (e.g., the receiver 1110, the transmitter 1115, the communications manager 1120) , may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .

The receiver 1110 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to reporting capability information for communicating with A-IoT devices) . Information may be passed on to other components of the device 1105. The receiver 1110 may utilize a single antenna or a set of multiple antennas.

The transmitter 1115 may provide a means for transmitting signals generated by other components of the device 1105. For example, the transmitter 1115 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to reporting capability information for communicating with A-IoT devices) . In some examples, the transmitter 1115 may be co-located with a receiver 1110 in a transceiver module. The transmitter 1115 may utilize a single antenna or a set of multiple antennas.

The device 1105, or various components thereof, may be an example of means for performing various aspects of reporting capability information for communicating with A-IoT devices as described herein. For example, the communications manager 1120 may include a capability report manager 1125, a scheduling manager 1130, an A-IoT communication manager 1135, or any combination thereof. The communications manager 1120 may be an example of aspects of a communications manager 1020 as described herein. In some examples, the communications manager 1120, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1110, the transmitter 1115, or both. For example, the communications manager 1120 may receive information from the receiver 1110, send information to the transmitter 1115, or be integrated in combination with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager 1120 may support wireless communication in accordance with examples as disclosed herein. The capability report manager 1125 is capable of, configured to, or operable to support a means for transmitting a capability report that indicates a capability of the first network entity to communicate, via a first carrier of a frequency band, with a second network entity. The scheduling manager 1130 is capable of, configured to, or operable to support a means for receiving a grant that schedules a communication that includes one or more FL transmissions, one or more BL transmissions, one or more CW signals, or a combination thereof between the first network entity and the second network entity, where the communication is scheduled to occur via the first carrier. The A-IoT communication manager 1135 is capable of, configured to, or operable to support a means for communicating with the second network entity via the first carrier in accordance with the grant and with the capability.

FIG. 12 shows a block diagram 1200 of a communications manager 1220 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The communications manager 1220 may be an example of aspects of a communications manager 1020, a communications manager 1120, or both, as described herein. The communications manager 1220, or various components thereof, may be an example of means for performing various aspects of reporting capability information for communicating with A-IoT devices as described herein. For example, the communications manager 1220 may include a capability report manager 1225, a scheduling manager 1230, an A-IoT communication manager 1235, a communication dropping manager 1240, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories) , may communicate, directly or indirectly, with one another (e.g., via one or more buses) .

The communications manager 1220 may support wireless communication in accordance with examples as disclosed herein. The capability report manager 1225 is capable of, configured to, or operable to support a means for transmitting a capability report that indicates a capability of the first network entity to communicate, via a first carrier of a frequency band, with a second network entity. The scheduling manager 1230 is capable of, configured to, or operable to support a means for receiving a grant that schedules a communication that includes one or more FL transmissions, one or more BL transmissions, one or more CW signals, or a combination thereof between the first network entity and the second network entity, where the communication is scheduled to occur via the first carrier. The A-IoT communication manager 1235 is capable of, configured to, or operable to support a means for communicating with the second network entity via the first carrier in accordance with the grant and with the capability.

In some examples, the capability report includes a capability of the first network entity to simultaneously transmit the one or more CW signals via the first carrier and receive a BL transmission of the communication via the first carrier, to simultaneously perform the communication via the first carrier and receive a downlink transmission via a downlink carrier of the frequency band, to simultaneously perform the communication via the first carrier and transmit an uplink transmission via an uplink carrier of the frequency band, or some combination thereof.

In some examples, the capability report includes a capability of the first network entity to perform the communication via the first carrier and to communicate with a third network entity via a downlink carrier of the frequency band, via an uplink carrier of the frequency band, or both. In some examples, the downlink carrier is paired with the first carrier or unpaired with the first carrier. In some examples, the uplink carrier is unpaired with the first carrier.

In some examples, the capability report indicates a limitation associated with simultaneous communications at the first network entity. In some examples, the first carrier is a first uplink carrier of the frequency band.

In some examples, the grant indicates for the first network entity to perform the communication in accordance with the capability.

In some examples, the grant indicates a time gap between the communication and one or more uplink transmissions based on the capability. In some examples, the time gap is associated with a switching time for the first network entity to switch from performance of the communication via the first uplink carrier and transmission of one or more uplink messages via a second uplink carrier of the frequency band.

In some examples, the limitation is an inability to simultaneously transmit the one or more CW signals and receive the one or more BL transmissions, to simultaneously receive the one or more BL transmissions and receive one or more downlink communications via a downlink carrier of the frequency band, to simultaneously transmit the one or more FL transmissions and receive one or more downlink transmissions via the downlink carrier, to simultaneously transmit the one or more FL transmissions and transmit one or more uplink transmissions via a second uplink carrier of the frequency band, or to simultaneously receive the one or more BL transmissions and transmit one or more uplink transmissions via the second uplink carrier.

In some examples, the communication dropping manager 1240 is capable of, configured to, or operable to support a means for dropping one or more communications based on the grant being indicative of performance of the communication in violation of the limitation, where the one or more communications are dropped in accordance with the capability.

In some examples, the one or more dropped communications include the one or more FL transmissions, the one or more BL transmissions, the one or more CW signals, one or more uplink transmissions, one or more downlink transmissions, or some combination thereof.

In some examples, the one or more communications are dropped in accordance with one or more prioritization rules associated with a type of transmission of the one or more uplink transmissions or of the one or more downlink transmissions.

In some examples, when the limitation indicates that the first network entity does not support simultaneous reception of the one or more BL transmissions via the first uplink carrier and reception of one or more downlink transmissions via a downlink carrier of the frequency band that is paired with the first uplink carrier, the type of transmission that is associated with the one or more prioritization rules includes a SSB, a PDCCH CSS, a PDCCH USS, a SPS PDCCH message, or a dynamically scheduled PDCCH message.

In some examples, when the limitation indicates that the first network entity does not support simultaneous transmission of the one or more FL transmissions via the first uplink carrier and reception of one or more downlink transmissions via a downlink carrier of the frequency band that is paired with the first uplink carrier, the type of transmission that is associated with the one or more prioritization rules includes a SSB, a dedicated RRC message, a PDCCH CSS, a PDCCH USS, or a SPS PDCCH message.

In some examples, when the limitation indicates that the first network entity does not support simultaneous reception of the one or more BL transmissions via the first uplink carrier and reception of one or more downlink transmissions via a downlink carrier of the frequency band that is unpaired with the first uplink carrier, the type of transmission that is associated with the one or more prioritization rules includes a SSB, a PDCCH CSS, a PDCCH USS, a dedicated RRC message, or a dynamically scheduled PDCCH message.

In some examples, when the limitation indicates that the first network entity does not support simultaneous reception of the one or more BL transmissions via the first uplink carrier and transmission of one or more uplink transmissions via an second uplink carrier of the frequency band that is unpaired with the first uplink carrier, the type of transmission that is associated with the one or more prioritization rules includes a physical random access channel message, a semi-static PDCCH message, a dynamic PDCCH message, a semi-static PDCCH message, a dynamic PDCCH message, a semi-static SRS, or a dynamic SRS.

In some examples, the second network entity is capable of reception or transmission via at least one of amplitude-shift keying modulation or frequency-shift keying modulation.

FIG. 13 shows a diagram of a system 1300 including a device 1305 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The device 1305 may be an example of or include components of a device 1005, a device 1105, or a UE 115 as described herein. The device 1305 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entities 105, UEs 115, or a combination thereof) . The device 1305 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1320, an input/output (I/O) controller, such as an I/O controller 1310, a transceiver 1315, one or more antennas 1325, at least one memory 1330, code 1335, and at least one processor 1340. 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 1345) .

The I/O controller 1310 may manage input and output signals for the device 1305. The I/O controller 1310 may also manage peripherals not integrated into the device 1305. In some cases, the I/O controller 1310 may represent a physical connection or port to an external peripheral. In some cases, the I/O controller 1310 may utilize an operating system such as or another known operating system. Additionally, or alternatively, the I/O controller 1310 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller 1310 may be implemented as part of one or more processors, such as the at least one processor 1340. In some cases, a user may interact with the device 1305 via the I/O controller 1310 or via hardware components controlled by the I/O controller 1310.

In some cases, the device 1305 may include a single antenna. However, in some other cases, the device 1305 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1315 may communicate bi-directionally via the one or more antennas 1325 using wired or wireless links as described herein. For example, the transceiver 1315 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1315 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1325 for transmission, and to demodulate packets received from the one or more antennas 1325. The transceiver 1315, or the transceiver 1315 and one or more antennas 1325, may be an example of a transmitter 1015, a transmitter 1115, a receiver 1010, a receiver 1110, or any combination thereof or component thereof, as described herein.

The at least one memory 1330 may include random access memory (RAM) and read-only memory (ROM) . The at least one memory 1330 may store computer-readable, computer-executable, or processor-executable code, such as the code 1335. The code 1335 may include instructions that, when executed by the at least one processor 1340, cause the device 1305 to perform various functions described herein. The code 1335 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1335 may not be directly executable by the at least one processor 1340 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1330 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The at least one processor 1340 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs) , one or more graphics processing units (GPUs) , one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof) . In some cases, the at least one processor 1340 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 1340. The at least one processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 1330) to cause the device 1305 to perform various functions (e.g., functions or tasks supporting reporting capability information for communicating with A-IoT devices) . For example, the device 1305 or a component of the device 1305 may include at least one processor 1340 and at least one memory 1330 coupled with or to the at least one processor 1340, the at least one processor 1340 and the at least one memory 1330 configured to perform various functions described herein. In some examples, the at least one processor 1340 may include multiple processors and the at least one memory 1330 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions described herein. In some examples, the at least one processor 1340 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1340) and memory circuitry (which may include the at least one memory 1330) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1340 or a processing system including the at least one processor 1340 may be configured to, configurable to, or operable to cause the device 1305 to perform one or more of the functions described herein. Further, as described herein, being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 1335 (e.g., processor-executable code) stored in the at least one memory 1330 or otherwise, to perform one or more of the functions described herein.

The communications manager 1320 may support wireless communication in accordance with examples as disclosed herein. For example, the communications manager 1320 is capable of, configured to, or operable to support a means for transmitting a capability report that indicates a capability of the first network entity to communicate, via a first carrier of a frequency band, with a second network entity. The communications manager 1320 is capable of, configured to, or operable to support a means for receiving a grant that schedules a communication that includes one or more FL transmissions, one or more BL transmissions, one or more CW signals, or a combination thereof between the first network entity and the second network entity, where the communication is scheduled to occur via the first carrier. The communications manager 1320 is capable of, configured to, or operable to support a means for communicating with the second network entity via the first carrier in accordance with the grant and with the capability.

By including or configuring the communications manager 1320 in accordance with examples as described herein, the device 1305 may support techniques for reporting capability for communicating with an A-IoT device, which may allow for improved communication reliability, reduced latency, more efficient utilization of communication resources, and improved coordination between devices.

In some examples, the communications manager 1320 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1315, the one or more antennas 1325, or any combination thereof. Although the communications manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1320 may be supported by or performed by the at least one processor 1340, the at least one memory 1330, the code 1335, or any combination thereof. For example, the code 1335 may include instructions executable by the at least one processor 1340 to cause the device 1305 to perform various aspects of reporting capability information for communicating with A-IoT devices as described herein, or the at least one processor 1340 and the at least one memory 1330 may be otherwise configured to, individually or collectively, perform or support such operations.

FIG. 14 shows a block diagram 1400 of a device 1405 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The device 1405 may be an example of aspects of a network entity 105 as described herein. The device 1405 may include a receiver 1410, a transmitter 1415, and a communications manager 1420. The device 1405, or one or more components of the device 1405 (e.g., the receiver 1410, the transmitter 1415, the communications manager 1420) , may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .

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

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

The communications manager 1420, the receiver 1410, the transmitter 1415, or various combinations or components thereof may be examples of means for performing various aspects of reporting capability information for communicating with A-IoT devices as described herein. For example, the communications manager 1420, the receiver 1410, the transmitter 1415, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

In some examples, the communications manager 1420, the receiver 1410, the transmitter 1415, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include at least one of 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, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .

Additionally, or alternatively, the communications manager 1420, the receiver 1410, the transmitter 1415, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code) . If implemented in code executed by at least one processor, the functions of the communications manager 1420, the receiver 1410, the transmitter 1415, 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, individually or collectively, a means for performing the functions described in the present disclosure) .

In some examples, the communications manager 1420 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1410, the transmitter 1415, or both. For example, the communications manager 1420 may receive information from the receiver 1410, send information to the transmitter 1415, or be integrated in combination with the receiver 1410, the transmitter 1415, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager 1420 may support wireless communication in accordance with examples as disclosed herein. For example, the communications manager 1420 is capable of, configured to, or operable to support a means for obtaining a capability report that indicates a capability of a second network entity to communicate, via a first carrier of a frequency band, with a third network entity. The communications manager 1420 is capable of, configured to, or operable to support a means for outputting a grant that schedules a communication that includes one or more FL communications, one or more BL communications, one or more CW signals, or a combination thereof between the second network entity and the third network entity, where the communication is scheduled to occur via the first carrier.

By including or configuring the communications manager 1420 in accordance with examples as described herein, the device 1405 (e.g., at least one processor controlling or otherwise coupled with the receiver 1410, the transmitter 1415, the communications manager 1420, or a combination thereof) may support techniques for reporting capability for communicating with an A-IoT device, which may allow for more efficient utilization of communication resources.

FIG. 15 shows a block diagram 1500 of a device 1505 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The device 1505 may be an example of aspects of a device 1405 or a network entity 105 as described herein. The device 1505 may include a receiver 1510, a transmitter 1515, and a communications manager 1520. The device 1505, or one or more components of the device 1505 (e.g., the receiver 1510, the transmitter 1515, the communications manager 1520) , may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .

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

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

The device 1505, or various components thereof, may be an example of means for performing various aspects of reporting capability information for communicating with A-IoT devices as described herein. For example, the communications manager 1520 may include a capability report component 1525 a scheduling component 1530, or any combination thereof. The communications manager 1520 may be an example of aspects of a communications manager 1420 as described herein. In some examples, the communications manager 1520, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1510, the transmitter 1515, or both. For example, the communications manager 1520 may receive information from the receiver 1510, send information to the transmitter 1515, or be integrated in combination with the receiver 1510, the transmitter 1515, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager 1520 may support wireless communication in accordance with examples as disclosed herein. The capability report component 1525 is capable of, configured to, or operable to support a means for obtaining a capability report that indicates a capability of a second network entity to communicate, via a first carrier of a frequency band, with a third network entity. The scheduling component 1530 is capable of, configured to, or operable to support a means for outputting a grant that schedules a communication that includes one or more FL communications, one or more BL communications, one or more CW signals, or a combination thereof between the second network entity and the third network entity, where the communication is scheduled to occur via the first carrier.

FIG. 16 shows a block diagram 1600 of a communications manager 1620 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The communications manager 1620 may be an example of aspects of a communications manager 1420, a communications manager 1520, or both, as described herein. The communications manager 1620, or various components thereof, may be an example of means for performing various aspects of reporting capability information for communicating with A-IoT devices as described herein. For example, the communications manager 1620 may include a capability report component 1625 a scheduling component 1630, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories) , may communicate, directly or indirectly, with one another (e.g., via one or more buses) . The communications may include communications within a protocol layer of a protocol stack, communications 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.

The communications manager 1620 may support wireless communication in accordance with examples as disclosed herein. The capability report component 1625 is capable of, configured to, or operable to support a means for obtaining a capability report that indicates a capability of a second network entity to communicate, via a first carrier of a frequency band, with a third network entity. The scheduling component 1630 is capable of, configured to, or operable to support a means for outputting a grant that schedules a communication that includes one or more FL communications, one or more BL communications, one or more CW signals, or a combination thereof between the second network entity and the third network entity, where the communication is scheduled to occur via the first carrier.

In some examples, the capability report includes a capability of the second network entity to simultaneously transmit the one or more CW signals via the first carrier and receive a BL transmission of the communication via the first carrier, to simultaneously perform the communication via the first carrier and receive a downlink transmission via a downlink carrier of the frequency band, to simultaneously perform the communication via the first carrier and transmit an uplink transmission via an uplink carrier of the frequency band, or some combination thereof.

In some examples, the capability report includes a capability of the second network entity to perform the communication via the first carrier and to communicate with a third network entity via a downlink carrier of the frequency band, via an uplink carrier of the frequency band, or both. In some examples, the downlink carrier is paired with the first carrier or unpaired with the first carrier. In some examples, the uplink carrier is unpaired with the first carrier.

In some examples, the capability report indicates a limitation associated with simultaneous communications at the second network entity. In some examples, the first carrier is a first uplink carrier of the frequency band.

In some examples, the grant indicates for the second network entity to perform the communication in accordance with the capability.

In some examples, the limitation is an inability to simultaneously transmit the one or more CW signals and receive the one or more BL communications, to simultaneously receive the one or more BL communications and receive one or more downlink communications via a downlink carrier of the frequency band, to simultaneously transmit the one or more FL communications and receive one or more downlink transmissions via the downlink carrier, to simultaneously transmit the one or more FL communications and transmit one or more uplink communications via a second uplink carrier of the frequency band, or to simultaneously receive the one or more BL communications and transmit one or more uplink transmissions via the second uplink carrier.

In some examples, the third network entity is capable of reception or transmission via at least one of amplitude-shift keying modulation or frequency-shift keying modulation.

FIG. 17 shows a diagram of a system 1700 including a device 1705 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The device 1705 may be an example of or include components of a device 1405, a device 1505, or a network entity 105 as described herein. The device 1705 may communicate with other network devices or network equipment such as one or more of the network entities 105, UEs 115, or any combination thereof. The communications may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof. The device 1705 may include components that support outputting and obtaining communications, such as a communications manager 1720, a transceiver 1710, one or more antennas 1715, at least one memory 1725, code 1730, and at least one processor 1735. 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 1740) .

The transceiver 1710 may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver 1710 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1710 may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver. In some examples, the device 1705 may include one or more antennas 1715, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently) . The transceiver 1710 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1715, by a wired transmitter) , to receive modulated signals (e.g., from one or more antennas 1715, from a wired receiver) , and to demodulate signals. In some implementations, the transceiver 1710 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1715 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1715 that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1710 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver 1710, or the transceiver 1710 and the one or more antennas 1715, or the transceiver 1710 and the one or more antennas 1715 and one or more processors or one or more memory components (e.g., the at least one processor 1735, the at least one memory 1725, or both) , may be included in a chip or chip assembly that is installed in the device 1705. In some examples, the transceiver 1710 may be operable to support communications via one or more communications links (e.g., communication link (s) 125, backhaul communication link (s) 120, a midhaul communication link 162, a fronthaul communication link 168) .

The at least one memory 1725 may include RAM, ROM, or any combination thereof. The at least one memory 1725 may store computer-readable, computer-executable, or processor-executable code, such as the code 1730. The code 1730 may include instructions that, when executed by one or more of the at least one processor 1735, cause the device 1705 to perform various functions described herein. The code 1730 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1730 may not be directly executable by a processor of the at least one processor 1735 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1725 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some examples, the at least one processor 1735 may include multiple processors and the at least one memory 1725 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions herein (for example, as part of a processing system) .

The at least one processor 1735 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs) , one or more graphics processing units (GPUs) , one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof) . In some cases, the at least one processor 1735 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into one or more of the at least one processor 1735. The at least one processor 1735 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1725) to cause the device 1705 to perform various functions (e.g., functions or tasks supporting reporting capability information for communicating with A-IoT devices) . For example, the device 1705 or a component of the device 1705 may include at least one processor 1735 and at least one memory 1725 coupled with one or more of the at least one processor 1735, the at least one processor 1735 and the at least one memory 1725 configured to perform various functions described herein. The at least one processor 1735 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1730) to perform the functions of the device 1705. The at least one processor 1735 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1705 (such as within one or more of the at least one memory 1725) . In some examples, the at least one processor 1735 may include multiple processors and the at least one memory 1725 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 1735 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1735) and memory circuitry (which may include the at least one memory 1725) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1735 or a processing system including the at least one processor 1735 may be configured to, configurable to, or operable to cause the device 1705 to perform one or more of the functions described herein. Further, as described herein, being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1725 or otherwise, to perform one or more of the functions described herein.

In some examples, a bus 1740 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1740 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 the device 1705, or between different components of the device 1705 that may be co-located or located in different locations (e.g., where the device 1705 may refer to a system in which one or more of the communications manager 1720, the transceiver 1710, the at least one memory 1725, the code 1730, and the at least one processor 1735 may be located in one of the different components or divided between different components) .

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

The communications manager 1720 may support wireless communication in accordance with examples as disclosed herein. For example, the communications manager 1720 is capable of, configured to, or operable to support a means for obtaining a capability report that indicates a capability of a second network entity to communicate, via a first carrier of a frequency band, with a third network entity. The communications manager 1720 is capable of, configured to, or operable to support a means for outputting a grant that schedules a communication that includes one or more FL communications, one or more BL communications, one or more CW signals, or a combination thereof between the second network entity and the third network entity, where the communication is scheduled to occur via the first carrier.

By including or configuring the communications manager 1720 in accordance with examples as described herein, the device 1705 may support techniques for reporting capability for communicating with an A-IoT device, which may allow for improved communication reliability, reduced latency, more efficient utilization of communication resources, and improved coordination between devices.

In some examples, the communications manager 1720 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1710, the one or more antennas 1715 (e.g., where applicable) , or any combination thereof. Although the communications manager 1720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1720 may be supported by or performed by the transceiver 1710, one or more of the at least one processor 1735, one or more of the at least one memory 1725, the code 1730, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1735, the at least one memory 1725, the code 1730, or any combination thereof) . For example, the code 1730 may include instructions executable by one or more of the at least one processor 1735 to cause the device 1705 to perform various aspects of reporting capability information for communicating with A-IoT devices as described herein, or the at least one processor 1735 and the at least one memory 1725 may be otherwise configured to, individually or collectively, perform or support such operations.

FIG. 18 shows a flowchart illustrating a method 1800 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The operations of the method 1800 may be implemented by a UE or its components as described herein. For example, the operations of the method 1800 may be performed by a UE 115 as described with reference to FIGs. 1 through 13. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At 1805, the method may include transmitting a capability report that indicates a capability of the first network entity to communicate, via a first carrier of a frequency band, with a second network entity. The operations of 1805 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed by a capability report manager 1225 as described with reference to FIG. 12.

At 1810, the method may include receiving a grant that schedules a communication that includes one or more FL transmissions, one or more BL transmissions, one or more CW signals, or a combination thereof between the first network entity and the second network entity, where the communication is scheduled to occur via the first carrier. The operations of 1810 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed by a scheduling manager 1230 as described with reference to FIG. 12.

At 1815, the method may include communicating with the second network entity via the first carrier in accordance with the grant and with the capability. The operations of 1815 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed by an A-IoT communication manager 1235 as described with reference to FIG. 12.

FIG. 19 shows a flowchart illustrating a method 1900 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The operations of the method 1900 may be implemented by a UE or its components as described herein. For example, the operations of the method 1900 may be performed by a UE 115 as described with reference to FIGs. 1 through 13. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At 1905, the method may include transmitting a capability report that indicates a capability of the first network entity to communicate, via a first carrier of a frequency band, with a second network entity. The operations of 1905 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed by a capability report manager 1225 as described with reference to FIG. 12.

At 1910, the method may include receiving a grant that schedules a communication that includes one or more FL transmissions, one or more BL transmissions, one or more CW signals, or a combination thereof between the first network entity and the second network entity, where the communication is scheduled to occur via the first carrier. The operations of 1910 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed by a scheduling manager 1230 as described with reference to FIG. 12.

At 1915, the method may include communicating with the second network entity via the first carrier in accordance with the grant and with the capability. The operations of 1915 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed by an A-IoT communication manager 1235 as described with reference to FIG. 12.

At 1920, the method may include dropping one or more communications based on the grant being indicative of performance of the communication in violation of the limitation, where the one or more communications are dropped in accordance with the capability. The operations of 1920 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed by a communication dropping manager 1240 as described with reference to FIG. 12.

FIG. 20 shows a flowchart illustrating a method 2000 that supports reporting capability information for communicating with A-IoT devices in accordance with one or more aspects of the present disclosure. The operations of the method 2000 may be implemented by a network entity or its components as described herein. For example, the operations of the method 2000 may be performed by a network entity as described with reference to FIGs. 1 through 9 and 14 through 17. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

At 2005, the method may include obtaining a capability report that indicates a capability of a second network entity to communicate, via a first carrier of a frequency band, with a third network entity. The operations of 2005 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed by a capability report component 1625 as described with reference to FIG. 16.

At 2010, the method may include outputting a grant that schedules a communication that includes one or more FL communications, one or more BL communications, one or more CW signals, or a combination thereof between the second network entity and the third network entity, where the communication is scheduled to occur via the first carrier. The operations of 2010 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed by a scheduling component 1630 as described with reference to FIG. 16.

The following provides an overview of aspects of the present disclosure:

Aspect 1: A method for wireless communication at first network entity, comprising: transmitting a capability report that indicates a capability of the first network entity to communicate, via a first carrier of a frequency band, with a second network entity; receiving a grant that schedules a communication that includes one or more FL transmissions, one or more BL transmissions, one or more CW signals, or a combination thereof between the first network entity and the second network entity, wherein the communication is scheduled to occur via the first carrier; and communicating with the second network entity via the first carrier in accordance with the grant and with the capability.

Aspect 2: The method of aspect 1, wherein the capability report comprises a capability of the first network entity to simultaneously transmit the one or more CW signals via the first carrier and receive a BL transmission of the communication via the first carrier, to simultaneously perform the communication via the first carrier and receive a downlink transmission via a downlink carrier of the frequency band, to simultaneously perform the communication via the first carrier and transmit an uplink transmission via an uplink carrier of the frequency band, or some combination thereof.

Aspect 3: The method of any of aspects 1 through 2, wherein the capability report comprises a capability of the first network entity to perform the communication via the first carrier and to communicate with a third network entity via a downlink carrier of the frequency band, via an uplink carrier of the frequency band, or both, the downlink carrier is paired with the first carrier or unpaired with the first carrier, and the uplink carrier is unpaired with the first carrier.

Aspect 4: The method of any of aspects 1 through 3, wherein the capability report indicates a limitation associated with simultaneous communications at the first network entity, and the first carrier is a first uplink carrier of the frequency band.

Aspect 5: The method of aspect 4, wherein the grant indicates for the first network entity to perform the communication in accordance with the capability.

Aspect 6: The method of aspect 5, wherein the grant indicates a time gap between the communication and one or more uplink transmissions based at least in part on the capability, the time gap is associated with a switching time for the first network entity to switch from performance of the communication via the first uplink carrier and transmission of one or more uplink messages via a second uplink carrier of the frequency band.

Aspect 7: The method of any of aspects 5 through 6, wherein the limitation is an inability to simultaneously transmit the one or more CW signals and receive the one or more BL transmissions, to simultaneously receive the one or more BL transmissions and receive one or more downlink communications via a downlink carrier of the frequency band, to simultaneously transmit the one or more FL transmissions and receive one or more downlink transmissions via the downlink carrier, to simultaneously transmit the one or more FL transmissions and transmit one or more uplink transmissions via a second uplink carrier of the frequency band, or to simultaneously receive the one or more BL transmissions and transmit one or more uplink transmissions via the second uplink carrier.

Aspect 8: The method of any of aspects 5 through 7, further comprising: dropping one or more communications based on the grant being indicative of performance of the communication in violation of the limitation, wherein the one or more communications are dropped in accordance with the capability.

Aspect 9: The method of aspect 8, wherein the one or more dropped communications comprise the one or more FL transmissions, the one or more BL transmissions, the one or more CW signals, one or more uplink transmissions, one or more downlink transmissions, or some combination thereof.

Aspect 10: The method of aspect 9, wherein the one or more communications are dropped in accordance with one or more prioritization rules associated with a type of transmission of the one or more uplink transmissions or of the one or more downlink transmissions.

Aspect 11: The method of aspect 10, wherein when the limitation indicates that the first network entity does not support simultaneous reception of the one or more BL transmissions via the first uplink carrier and reception of one or more downlink transmissions via a downlink carrier of the frequency band that is paired with the first uplink carrier, the type of transmission that is associated with the one or more prioritization rules includes a SSB, a PDCCH CSS, a PDCCH USS, a SPS PDSCH message, or a dynamically scheduled PDSCH message.

Aspect 12: The method of any of aspects 10 through 11, wherein when the limitation indicates that the first network entity does not support simultaneous transmission of the one or more FL transmissions via the first uplink carrier and reception of one or more downlink transmissions via a downlink carrier of the frequency band that is paired with the first uplink carrier, the type of transmission that is associated with the one or more prioritization rules includes a SSB, a dedicated RRC message, a PUCCH CSS, a PUCCH USS, or a SPS PUSCH message.

Aspect 13: The method of any of aspects 10 through 12, wherein when the limitation indicates that the first network entity does not support simultaneous reception of the one or more BL transmissions via the first uplink carrier and reception of one or more downlink transmissions via a downlink carrier of the frequency band that is unpaired with the first uplink carrier, the type of transmission that is associated with the one or more prioritization rules includes a SSB, a PDCCH CSS, a PDCCH USS, a dedicated RRC message, or a dynamically scheduled PDSCH message.

Aspect 14: The method of any of aspects 10 through 13, wherein when the limitation indicates that the first network entity does not support simultaneous reception of the one or more BL transmissions via the first uplink carrier and transmission of one or more uplink transmissions via an second uplink carrier of the frequency band that is unpaired with the first uplink carrier, the type of transmission that is associated with the one or more prioritization rules includes a physical random access channel message, a semi-static PUCCH message, a dynamic PUCCH message, a semi-static PUSCH message, a dynamic PUSCH message, a semi-static SRS, or a dynamic SRS.

Aspect 15: The method of any of aspects 1 through 14, wherein the second network entity is capable of reception or transmission via at least one of ASK modulation or FSK modulation.

Aspect 16: A method for wireless communication at a first network entity, comprising: obtaining a capability report that indicates a capability of a second network entity to communicate, via a first carrier of a frequency band, with a third network entity; and outputting a grant that schedules a communication that includes one or more FL communications, one or more BL communications, one or more CW signals, or a combination thereof between the second network entity and the third network entity, wherein the communication is scheduled to occur via the first carrier.

Aspect 17: The method of aspect 16, wherein the capability report comprises a capability of the second network entity to simultaneously transmit the one or more CW signals via the first carrier and receive a BL transmission of the communication via the first carrier, to simultaneously perform the communication via the first carrier and receive a downlink transmission via a downlink carrier of the frequency band, to simultaneously perform the communication via the first carrier and transmit an uplink transmission via an uplink carrier of the frequency band, or some combination thereof.

Aspect 18: The method of any of aspects 16 through 17, wherein the capability report comprises a capability of the second network entity to perform the communication via the first carrier and to communicate with a third network entity via a downlink carrier of the frequency band, via an uplink carrier of the frequency band, or both, the downlink carrier is paired with the first carrier or unpaired with the first carrier, and the uplink carrier is unpaired with the first carrier.

Aspect 19: The method of any of aspects 16 through 18, wherein the capability report indicates a limitation associated with simultaneous communications at the second network entity, and the first carrier is a first uplink carrier of the frequency band.

Aspect 20: The method of aspect 19, wherein the grant indicates for the second network entity to perform the communication in accordance with the capability.

Aspect 21: The method of any of aspects 19 through 20, wherein the grant indicates a time gap between the communication and one or more uplink transmissions based at least in part on the capability, the time gap is associated with a switching time for the first network entity to switch from performance of the communication via the first uplink carrier and transmission of one or more uplink messages via a second uplink carrier of the frequency band.

Aspect 22: The method of any of aspects 19 through 21, wherein the limitation is an inability to simultaneously transmit the one or more CW signals and receive the one or more BL communications, to simultaneously receive the one or more BL communications and receive one or more downlink communications via a downlink carrier of the frequency band, to simultaneously transmit the one or more FL communications and receive one or more downlink transmissions via the downlink carrier, to simultaneously transmit the one or more FL communications and transmit one or more uplink communications via a second uplink carrier of the frequency band, or to simultaneously receive the one or more BL communications and transmit one or more uplink transmissions via the second uplink carrier.

Aspect 23: The method of any of aspects 16 through 22, wherein the third network entity is capable of reception or transmission via at least one of ASK modulation or FSK modulation.

Aspect 24: A first network entity for wireless communication, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the first network entity to perform a method of any of aspects 1 through 15.

Aspect 25: A first network entity for wireless communication, comprising a processing system configured to perform a method of any of aspects 1 through 15.

Aspect 26: A first network entity for wireless communication, comprising at least one means for performing a method of any of aspects 1 through 15.

Aspect 27: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 15.

Aspect 28: A first network entity for wireless communication, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the first network entity to perform a method of any of aspects 16 through 23.

Aspect 29: A first network entity for wireless communication, comprising processing system configured to perform a method of any of aspects 16 through 23.

Aspect 30: A first network entity for wireless communication, comprising at least one means for performing a method of any of aspects 16 through 23.

Aspect 31: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform a method of any of aspects 16 through 23.

The methods described herein describe possible implementations, and the operations and the steps may be rearranged or otherwise modified and other implementations are possible. Further, aspects from two or more of the methods may be combined.

Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications 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, as well as other systems and radio technologies not explicitly mentioned herein.

Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, a graphics processing unit (GPU) , a neural processing unit (NPU) , 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 the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration) . Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.

The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.

As used herein, the term “or” is an inclusive “or” unless limiting language is used relative to the alternatives listed. For example, reference to “X being based on A or B” shall be construed as including within its scope X being based on A, X being based on B, and X being based on A and B. In this regard, reference to “X being based on A or B” refers to “at least one of A or B” or “one or more of A or B” due to “or” being inclusive. Similarly, reference to “X being based on A, B, or C” shall be construed as including within its scope X being based on A, X being based on B, X being based on C, X being based on A and B, X being based on A and C, X being based on B and C, and X being based on A, B, and C. In this regard, reference to “X being based on A, B, or C” refers to “at least one of A, B, or C” or “one or more of A, B, or C” due to “or” being inclusive. As an example of limiting language, reference to “X being based on only one of A or B” shall be construed as including within its scope X being based on A as well as X being based on B, but not X being based on A and B. Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently. Also, as used herein, the phrase “a set” shall be construed as including the possibility of a set with one member. That is, the phrase “a set” shall be construed in the same manner as “one or more” or “at least one of. ”

As used herein, including in the claims, the article “a” before a noun is open-ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components, ” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ”

The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database, or another data structure) , ascertaining, and the like. Also, “determining” can include receiving (e.g., receiving information) , accessing (e.g., accessing data stored in memory) , and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label or other subsequent reference label.

The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “aspect” or “example” used herein means “serving as an aspect, example, instance, or illustration” and not “preferred” or “advantageous over other aspects. ” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some figures, structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

A first network entity for wireless communication, comprising:

a processing system configured to:

transmit a capability report that indicates a capability of the first network entity to communicate, via a first carrier of a frequency band, with a second network entity;

receive a grant that schedules a communication that includes one or more forward link transmissions, one or more backward link transmissions, one or more continuous-wave signals, or a combination thereof between the first network entity and the second network entity, wherein the communication is scheduled to occur via the first carrier; and

communicate with the second network entity via the first carrier in accordance with the grant and with the capability.
The first network entity of claim 1, wherein the capability report comprises a capability of the first network entity to simultaneously transmit the one or more continuous-wave signals via the first carrier and receive a backward link transmission of the communication via the first carrier, to simultaneously perform the communication via the first carrier and receive a downlink transmission via a downlink carrier of the frequency band, to simultaneously perform the communication via the first carrier and transmit an uplink transmission via an uplink carrier of the frequency band, or some combination thereof.
The first network entity of claim 1, wherein the capability report comprises a capability of the first network entity to perform the communication via the first carrier and to communicate with a third network entity via a downlink carrier of the frequency band, via an uplink carrier of the frequency band, or both, wherein the downlink carrier is paired with the first carrier or unpaired with the first carrier, and wherein the uplink carrier is unpaired with the first carrier.
The first network entity of claim 1, wherein the capability report indicates a limitation associated with simultaneous communications at the first network entity, and wherein the first carrier is a first uplink carrier of the frequency band.
The first network entity of claim 4, wherein the grant indicates for the first network entity to perform the communication in accordance with the capability.
The first network entity of claim 5, wherein the grant indicates a time gap between the communication and one or more uplink transmissions based at least in part on the capability, wherein the time gap is associated with a switching time for the first network entity to switch from performance of the communication via the first uplink carrier and transmission of one or more uplink messages via a second uplink carrier of the frequency band.
The first network entity of claim 5, wherein the limitation is an inability to simultaneously transmit the one or more continuous-wave signals and receive the one or more backward link transmissions, to simultaneously receive the one or more backward link transmissions and receive one or more downlink communications via a downlink carrier of the frequency band, to simultaneously transmit the one or more forward link transmissions and receive one or more downlink transmissions via the downlink carrier, to simultaneously transmit the one or more forward link transmissions and transmit one or more uplink transmissions via a second uplink carrier of the frequency band, or to simultaneously receive the one or more backward link transmissions and transmit one or more uplink transmissions via the second uplink carrier.
The first network entity of claim 5, wherein, to communicate with the second network entity, the processing system is configured to:

drop one or more communications based on the grant being indicative of performance of the communication in violation of the limitation, wherein the one or more communications are dropped in accordance with the capability.
The first network entity of claim 8, wherein the one or more dropped communications comprise the one or more forward link transmissions, the one or more backward link transmissions, the one or more continuous-wave signals, one or more uplink transmissions, one or more downlink transmissions, or some combination thereof.
The first network entity of claim 9, wherein the one or more communications are dropped in accordance with one or more prioritization rules associated with a type of transmission of the one or more uplink transmissions or of the one or more downlink transmissions.
The first network entity of claim 10, wherein, when the limitation indicates that the first network entity does not support simultaneous reception of the one or more backward link transmissions via the first uplink carrier and reception of one or more downlink transmissions via a downlink carrier of the frequency band that is paired with the first uplink carrier, the type of transmission that is associated with the one or more prioritization rules includes a synchronization signal block, a physical downlink control channel common search space, a physical downlink control channel user equipment specific search space, a semi-persistent scheduling physical downlink shared channel message, or a dynamically scheduled physical downlink shared channel message.
The first network entity of claim 10, wherein, when the limitation indicates that the first network entity does not support simultaneous transmission of the one or more forward link transmissions via the first uplink carrier and reception of one or more downlink transmissions via a downlink carrier of the frequency band that is paired with the first uplink carrier, the type of transmission that is associated with the one or more prioritization rules includes a synchronization signal block, a dedicated radio resource control message, a physical uplink control channel common search space, a physical uplink control channel user equipment specific search space, or a semi-persistent scheduling physical uplink shared channel message.
The first network entity of claim 10, wherein, when the limitation indicates that the first network entity does not support simultaneous reception of the one or more backward link transmissions via the first uplink carrier and reception of one or more downlink transmissions via a downlink carrier of the frequency band that is unpaired with the first uplink carrier, the type of transmission that is associated with the one or more prioritization rules includes a synchronization signal block, a physical downlink control channel common search space, a physical downlink control channel user equipment specific search space, a dedicated radio resource control message, or a dynamically scheduled physical downlink shared channel message.
The first network entity of claim 10, wherein, when the limitation indicates that the first network entity does not support simultaneous reception of the one or more backward link transmissions via the first uplink carrier and transmission of one or more uplink transmissions via an second uplink carrier of the frequency band that is unpaired with the first uplink carrier, the type of transmission that is associated with the one or more prioritization rules includes a physical random access channel message, a semi-static physical uplink control channel message, a dynamic physical uplink control channel message, a semi-static physical uplink shared channel message, a dynamic physical uplink shared channel message, a semi-static sounding reference signal, or a dynamic sounding reference signal.
The first network entity of claim 1, wherein the second network entity is capable of reception or transmission via at least one of amplitude-shift keying modulation or frequency-shift keying modulation.
A first network entity for wireless communication, comprising:

a processing system configured to:

obtain a capability report that indicates a capability of a second network entity to communicate, via a first carrier of a frequency band, with a third network entity; and

output a grant that schedules a communication that includes one or more forward link communications, one or more backward link communications, one or more continuous-wave signals, or a combination thereof between the second network entity and the third network entity, wherein the communication is scheduled to occur via the first carrier.
The first network entity of claim 16, wherein the capability report comprises a capability of the second network entity to simultaneously transmit the one or more continuous-wave signals via the first carrier and receive a backward link transmission of the communication via the first carrier, to simultaneously perform the communication via the first carrier and receive a downlink transmission via a downlink carrier of the frequency band, to simultaneously perform the communication via the first carrier and transmit an uplink transmission via an uplink carrier of the frequency band, or some combination thereof.
The first network entity of claim 16, wherein the capability report comprises a capability of the second network entity to perform the communication via the first carrier and to communicate with a third network entity via a downlink carrier of the frequency band, via an uplink carrier of the frequency band, or both, wherein the downlink carrier is paired with the first carrier or unpaired with the first carrier, and wherein the uplink carrier is unpaired with the first carrier.
The first network entity of claim 16, wherein the capability report indicates a limitation associated with simultaneous communications at the second network entity, and wherein the first carrier is a first uplink carrier of the frequency band.
The first network entity of claim 19, wherein the grant indicates for the second network entity to perform the communication in accordance with the capability.
The first network entity of claim 19, wherein the grant indicates a time gap between the communication and one or more uplink transmissions based at least in part on the capability, wherein the time gap is associated with a switching time for the first network entity to switch from performance of the communication via the first uplink carrier and transmission of one or more uplink messages via a second uplink carrier of the frequency band.
The first network entity of claim 19, wherein the limitation is an inability to simultaneously transmit the one or more continuous-wave signals and receive the one or more backward link communications, to simultaneously receive the one or more backward link communications and receive one or more downlink communications via a downlink carrier of the frequency band, to simultaneously transmit the one or more forward link communications and receive one or more downlink transmissions via the downlink carrier, to simultaneously transmit the one or more forward link communications and transmit one or more uplink communications via a second uplink carrier of the frequency band, or to simultaneously receive the one or more backward link communications and transmit one or more uplink transmissions via the second uplink carrier.
The first network entity of claim 16, wherein the third network entity is capable of reception or transmission via at least one of amplitude-shift keying modulation or frequency-shift keying modulation.
A method for wireless communication performed by a first network entity, comprising:

transmitting a capability report that indicates a capability of the first network entity to communicate, via a first carrier of a frequency band, with a second network entity;

receiving a grant that schedules a communication that includes one or more forward link transmissions, one or more backward link transmissions, one or more continuous-wave signals, or a combination thereof between the first network entity and the second network entity, wherein the communication is scheduled to occur via the first carrier; and

communicating with the second network entity via the first carrier in accordance with the grant and with the capability.
The method of claim 24, wherein the capability report comprises a capability of the first network entity to simultaneously transmit the one or more continuous-wave signals via the first carrier and receive a backward link transmission of the communication via the first carrier, to simultaneously perform the communication via the first carrier and receive a downlink transmission via a downlink carrier of the frequency band, to simultaneously perform the communication via the first carrier and transmit an uplink transmission via an uplink carrier of the frequency band, or some combination thereof.
The method of claim 24, wherein the capability report comprises a capability of the first network entity to perform the communication via the first carrier and to communicate with a third network entity via a downlink carrier of the frequency band, via an uplink carrier of the frequency band, or both, wherein the downlink carrier is paired with the first carrier or unpaired with the first carrier, and wherein the uplink carrier is unpaired with the first carrier.
The method of claim 24, wherein the capability report indicates a limitation associated with simultaneous communications at the first network entity, and wherein the first carrier is a first uplink carrier of the frequency band.
The method of claim 27, wherein the grant indicates for the first network entity to perform the communication in accordance with the capability.
The method of claim 28, wherein the grant indicates a time gap between the communication and one or more uplink transmissions based at least in part on the capability, and wherein the time gap is associated with a switching time for the first network entity to switch from performance of the communication via the first uplink carrier and transmission of one or more uplink messages via a second uplink carrier of the frequency band.
A method for wireless communication performed by a first network entity, comprising:

obtaining a capability report that indicates a capability of a second network entity to communicate, via a first carrier of a frequency band, with a third network entity; and

outputting a grant that schedules a communication that includes one or more forward link communications, one or more backward link communications, one or more continuous-wave signals, or a combination thereof between the second network entity and the third network entity, wherein the communication is scheduled to occur via the first carrier.