Patent Description:
Due to the increasing demand for wireless communications, there is a desire to improve the efficiency of wireless communication network techniques.

Reference is made to <CIT> which discloses a carrier indication method, user equipment, and base station, and to XP055792288 RRC IE - UE Capability Info https://web. org/web/<NUM>/https://www. sharetechnote. com/html/Hand book_LTE_RRC_IE_UE_Capability.

An example implementation includes a method of wireless communication, including transmitting, by a user equipment (UE) to a network entity, a radio resource control (RRC) configuration message indicating a full-duplex capability of the UE; receiving, by the UE from the network entity, a downlink control information (DCI) format message, wherein the DCI format message enables concurrent transmission of an uplink channel and reception of a downlink channel by the UE on a same component carrier, wherein the concurrent transmission and reception comprises a transmission and reception in at least one overlapping orthogonal frequency division multiplexing (OFDM) symbol; and communicating, between the UE and the network entity, based on the DCI format message.

An example implementation includes a method of wireless communication, including transmitting, by a UE to a network entity, a RRC configuration message indicating at least one of a half-duplex capability or a full-duplex capability of the UE; receiving, by the UE from the network entity, a first DCI format message for scheduling receptions on a downlink channel; receiving, by the UE from the network entity, a second DCI format message for scheduling transmission on an uplink channel; and communicating, between the UE and the network entity, based on the first DCI format message and the second DCI format message. In an example, the first DCI format message is received separately from the second DCI format message.

In a further example, an apparatus for wireless communication is provided that includes a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled with the transceiver and the memory. The one or more processors are configured to execute the instructions to perform the operations of methods described herein. In another aspect, an apparatus for wireless communication is provided that includes means for performing the operations of methods described herein. In yet another aspect, a non-transitory computer-readable medium is provided including code executable by one or more processors to perform the operations of methods described herein.

Software may be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

<FIG> is a diagram illustrating an example of a wireless communications system and an access network <NUM> configured for downlink and uplink data downlink control information (DCI) triggering for full-duplex user equipments (UEs) in fifth generation new radio (<NUM> NR).

In certain aspects, the UE <NUM> may be configured to operate a communication component <NUM> and/or a configuration component <NUM> to transmit to a network entity, a radio resource control (RRC) configuration message indicating a full-duplex capability of the UE; receive, from the network entity, a DCI format message, wherein the DCI format message enables concurrent transmission of an uplink channel and reception of a downlink channel by the UE on a same component carrier, wherein the concurrent transmission and reception comprises a transmission and reception in at least one overlapping orthogonal frequency division multiplexing (OFDM) symbol; and communicate, with the network entity, based on the DCI format message.

In another aspect, the UE <NUM> may be configured to operate the communication component <NUM> and/or a configuration component <NUM> to transmit to a network entity, a RRC configuration message indicating at least one of a half-duplex capability or a full-duplex capability of the UE; receive, from the network entity, a first DCI format message for scheduling receptions on a downlink channel; receive, from the network entity, a second DCI format message for scheduling transmission on an uplink channel; and communicate, with the network entity, based on the first DCI format message and the second DCI format message. In one example, the first DCI format message is received separately from the second DCI format message.

Correspondingly, in certain aspects, the network entity (e.g., base station <NUM>) and/or another UE, such as UE <NUM>, may be configured to operate a communication component <NUM> and/or a configuration component <NUM> to transmit DCI format messages to UE <NUM>. For example, communication component <NUM> and/or a configuration component <NUM> may transmit one or more DCI format messages to the UE <NUM> and communicate with the UE <NUM> based on the DCI format messages.

The base stations <NUM> configured for <NUM> LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC <NUM> through backhaul links <NUM> (e.g., S1 interface). The base stations <NUM> configured for <NUM> NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network <NUM> through backhaul links <NUM>. The base stations <NUM> may communicate directly or indirectly (e.g., through the EPC <NUM> or core network <NUM>) with each other over backhaul links <NUM> (e.g., X2 interface). The backhaul links <NUM>, <NUM>, and <NUM> may be wired or wireless.

D2D communication may be through a variety of wireless D2D communications systems, such as for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) <NUM> standard, LTE, or NR.

The PDN Gateway <NUM> provides UE internet protocol (IP) address allocation as well as other functions. The IP Services <NUM> may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a packet-switched (PS) Streaming Service, and/or other IP services.

<FIG> include diagrams of example frame structures and resources that may be utilized in communications between the base stations <NUM>, the UEs <NUM>, and/or the secondary UEs (or sidelink UEs) <NUM> described in this disclosure. The <NUM>/NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for both DL and UL.

<FIG> is a block diagram of a base station <NUM> in communication with a UE <NUM> in an access network, where the base station <NUM> may be an example implementation of base station <NUM> and where UE <NUM> may be an example implementation of UE <NUM>.

At least one of the TX processor <NUM>, the RX processor <NUM>, and the controller/processor <NUM> may be configured to perform aspects in connection with communication component <NUM> of <FIG>.

Referring to <FIG>, the described features generally relate to downlink and uplink data downlink control information (DCI) triggering for full-duplex UEs in fifth generation new radio (<NUM> NR). For example, currently two separate DCI format messages are utilized when scheduling information for the uplink channel and the downlink channel.

Currently, DCI format 1_1 schedules information for the downlink channel. In an example, DCI format 1_1 includes fields for Frequency domain Resource assignment (FDRA), Frequency domain assignment Type (Type <NUM>/<NUM>), Time domain Resource Allocation (TDRA), precoding resource block group (PRG) bundling Indicator, VRB-<NUM>-PRB mapping Indicator, Carrier Indicator, Rate matching indicator, ZP CSI-RS trigger, TCI-state Indication, bandwidth part (BWP) Indicator, MCS, NDI, redundancy version (RV) per TB, HARQ Process Number, Antenna port, PUCCH resource indicator, transmit power control (TPC) command for scheduled PUCCH, SRS request, code block group (CBG) transmission information, DMRS sequence initialization.

Currently, DCI format 0_1 schedules information for the uplink channel. In an example, DCI format 0_1 includes fields for Carrier indicator, Bandwidth part indicator, Frequency domain resource assignment, Time domain resource assignment, Frequency hopping flag, Modulation and coding scheme, New data indicator, Redundancy version, HARQ process number, TPC command for scheduled PUSCH, UL/SUL indicator, SRS resource indicator, Precoding information and number of layers, Antenna ports, SRS request, CSI request, CBG transmission information (CBGTI), PTRS-DMRS association, beta_offset indicator, DMRS sequence initialization, and UL-SCH indicator.

Accordingly, DCI format 1_1 and DCI format 0_1 share a number of fields, such as but not limited to, antenna port and SRS request fields.

The present disclosure relates generally to current issues of downlink and uplink data DCI triggering for full-duplex UEs. In an example not claimed by the invention, the present disclosure includes a method, apparatus, and non-statutory computer readable medium for wireless communications for transmitting, by a UE to a network entity, a RRC configuration message indicating at least one of a half-duplex capability or a full-duplex capability of the UE; receiving, by the UE from the network entity, a first DCI format message for scheduling receptions on a downlink channel; receiving, by the UE from the network entity, a second DCI format message for scheduling transmission on an uplink channel; and communicating, between the UE and the network entity, based on the first DCI format message and the second DCI format message. In one example, the first DCI format message is received separately from the second DCI format message.

<FIG> is a diagram <NUM> illustrating full duplex communication modes. For example, scenario <NUM> depicts full-duplex base stations with half-duplex UEs <NUM> and <NUM>. In scenario <NUM>, a full-duplex first gNB may transmit on the downlink channel to UE1 and receive on the uplink channel from UE2. However, UE2 may cause interference on UE1 due to the uplink transmissions to the first gNB. Further, the second gNB may cause interference on the first gNB due to communication with both UE1 and UE2. Additionally, the first gNB may cause self-interference from the downlink and uplink communications.

In an aspect, scenario <NUM> depicts a full-duplex gNB and a full-duplex UE1. In scenario <NUM>, UE1 experiences self-interference from the full-duplex uplink and downlink communications with the first gNB, from UE2, which receives downlink communications from the second gNB, and from downlink communications from the second gNB.

In an aspect, scenario <NUM> depicts a full-duplex UE1 using multi-TRP to communicate simultaneously in the uplink with a first gNB and in the downlink with a second gNB. For example, since UE1 is the only entity configured in full-duplex mode, UE1 experiences self-interference due to uplink and downlink communications with both the first gNB and second gNB.

<FIG> is a diagram <NUM> illustrating a half duplex communication mode. For example, scenario <NUM> depicts a transmission reception point <NUM> (TRP1) configured in full-duplex mode with half-duplexed UEs. Correspondingly, diagram <NUM> depicts a subframe/slot breakdown of the full-duplex TRP1 and half-duplex UEs. In this example, the entities may engage in flexible downlink and uplink operation in time across slots and across UEs. That is, simultaneous PDSCH and PUSCH grant for the same subframe/slot for different UEs may be configured. The UEs may change the uplink transmission and/or the downlink reception bandwidth portion between slots in zero latency. The UEs may transmit sounding reference signals (SRS) with full reciprocity (e.g., full-duplex) to cover the whole downlink bandwidth portion and partial reciprocity (e.g., half-duplex) to cover part of the downlink bandwidth. In this example, the dotted lines of diagram <NUM> depict the subframe/slot breakdown of the full-duplex TRP1 and half-duplex UEs.

<FIG> is a diagram <NUM> illustrating a full duplex communication mode. For example, scenario <NUM> depicts a TRP1 is configured in full-duplex mode with a full-duplexed UE and a half-duplexed UE. Correspondingly, diagram <NUM> depicts a subframe/slot breakdown of the full-duplex TRP1 and full-duplex UEs. In this example, the entities may engage in flexible downlink and uplink operation in time across slots and across UEs. That is, simultaneous PDSCH and PUSCH grant for the same subframe/slot for different UEs may be configured. The full-duplex UEs may be configured for an uplink and downlink grant. The UEs may change the uplink transmission and/or the downlink reception bandwidth portion between slots in zero latency. The UEs may transmit SRS with full reciprocity (e.g., full-duplex) to cover the whole downlink bandwidth portion and partial reciprocity (e.g., half-duplex) to cover part of the downlink bandwidth. In this example, the dotted lines of diagram <NUM> depict the subframe/slot breakdown of the full-duplex TRP1 and half-duplex UEs.

<FIG> is a flowchart <NUM> of a method of wireless communication. The method may be performed by a UE (e.g., the UE <NUM>; the apparatus <NUM>; the controller/processor <NUM>, which may include the memory <NUM>, processor(s) <NUM>, which may include the memory <NUM>, modem <NUM> and which may be the entire UE <NUM> or a component of the UE <NUM>, such as the TX processor <NUM>, the RX processor <NUM>, and/or the transceiver <NUM>) in combination with the communication component <NUM>/configuration component <NUM>.

At <NUM>, method <NUM> includes transmitting, by a UE to a network entity, a RRC configuration message indicating a full-duplex capability of the UE. In an aspect, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM> may be configured to transmit, to a network entity, a RRC configuration message indicating a full-duplex capability of the UE. As such, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM>, e.g., in conjunction with controller/processor <NUM>, which may include the memory <NUM>, processor(s) <NUM>, which may include the memory <NUM>, modem <NUM>, TX processor <NUM>, and transceiver <NUM> may define a means for transmitting, by a UE to a network entity, a RRC configuration message indicating a full-duplex capability of the UE.

At <NUM>, method <NUM> includes receiving, by the UE from the network entity, a DCI format message, wherein the DCI format message enables a format of the concurrent transmission of an uplink channel and reception of a downlink channel by the UE on a same component carrier, wherein the concurrent transmission and reception comprises a transmission and reception in at least one overlapping OFDM symbol. According to the claimed invention, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM> is configured to receive, from the network entity, a DCI format message, wherein the DCI format message enables a format of the concurrent transmission of an uplink channel and reception of a downlink channel by the UE on a same component carrier, wherein the concurrent transmission and reception comprises a transmission and reception in at least one overlapping OFDM symbol. As such, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM>, e.g., in conjunction with controller/processor <NUM>, which may include the memory <NUM>, processor(s) <NUM>, which may include the memory <NUM>, modem <NUM>, RX processor <NUM>, and transceiver <NUM> may define a means for receiving, by the UE from the network entity, a DCI format message, wherein the DCI format message enables a format of the concurrent transmission of an uplink channel and reception of a downlink channel by the UE on a same component carrier, wherein the concurrent transmission and reception comprises a transmission and reception in at least one overlapping OFDM symbol. For example, transmission and reception may correspond to a partial overlap of the OFDM symbol.

According to the claimed invention and with method <NUM>, the DCI format message enables joint triggering of the concurrent transmission on the uplink channel and reception on the downlink channel by the UE. For example, the uplink channel corresponds to a physical uplink shared channel (PUSCH) SRS or a channel for the transmission of SRS. Further, the downlink channel corresponds to a CSI-RS, a physical downlink shared channel (PDSCH), a Positioning Reference Signal (PRS), a Tracking Reference Signal (TRS). Further, the DCI format message is configured to schedule at least one of the downlink channel and the uplink channel that are overlapping in at least one OFDM symbol, the downlink channel comprises a set of OFDM symbols, and the uplink channel comprises a set of OFDM symbols.

According to the claimed invention and with method <NUM>, the DCI format message includes one or more merged fields common to both the transmission on the uplink channel and the reception on the downlink channel. The uplink channel and the downlink channel overlap on a same number of OFDM symbols of a common carrier. The one or more merged fields includes a time domain resource allocation (TDRA) for both the downlink channel and the uplink channel. In an example, the TDRA comprises a time domain resource allocation that starts at an offset of symbols after reception of the DCI format message. Further, the one or more merged fields includes a first frequency domain resource assignment (FDRA) for the downlink channel and a second FDRA for the uplink channel, wherein the first FDRA occupies a greater number of bits than the second FDRA.

In an example of method <NUM>, the one or more merged fields include a joint transmission configuration indication (TCI) indication. For example, each of one or more TCI states have a quasi co-location (QCL) for the downlink channel and a QCL for the uplink channel. Each of one or more TCI states have a QCL for the downlink channel and a SRS resource indicator (SRI) for the uplink channel.

In an example of method <NUM>, the one or more merged fields include a virtual resource block (VRB) to physical resource block (PRB) mapping associated with the downlink channel and the uplink channel.

In an example of method <NUM>, the one or more merged field includes a demodulated reference signal (DMRS) sequence initialization that is associated with a first DMRS of the downlink channel and a second DMRS of the uplink channel.

In an example of method <NUM>, the one or more merged fields include a joint DMRS port indication table that identifies ports for each of the downlink channel and the uplink channel.

In an example of method <NUM>, the one or more merged fields include a joint field that triggers both SRS resources and a CSI RS resources on a same one or more OFDM symbol.

In an example of method <NUM>, receiving, by the UE from the network entity, the DCI format message further comprises receiving, by the UE from the network entity, a first portion of the DCI format message including information indicating a location of a second portion of the DCI format message, wherein the second portion of the DCI format message includes remaining information not included in the first portion of the DCI format message; and receiving, by the UE from the network entity, the second portion of the DCI format message based on the first portion of the DCI format message.

For example, the first portion of the DCI format message includes one or more common fields of the downlink channel and the uplink channel allocations. Further, the one or more common fields include at least one of a time domain resource allocation (TDRA), a frequency domain resource assignment (FDRA), a SRS request, and a CSI request.

For example, the first portion of the DCI format message further includes one or more downlink-related parameters for scheduling the downlink transmission and a pointer to scheduling information of the remaining information in the second portion of the DCI format. Further, method <NUM> may include determining that the scheduling information is within a scheduled PDSCH; and scheduling a PUSCH after an offset number of symbols based on the determination that the scheduling information is within the scheduled PDSCH.

At <NUM>, method <NUM> includes communicating, between the UE and the network entity, based on the DCI format message. In an aspect, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM> may be configured to transmit, to the one or more second UEs, data using the one or more reserved transmission resources. As such, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM>, e.g., in conjunction with controller/processor <NUM>, which may include the memory <NUM>, processor(s) <NUM>, which may include the memory <NUM>, modem <NUM>, RX processor <NUM>, and transceiver <NUM> may define a means for transmitting, by the first UE to the one or more second UEs, data using the one or more reserved transmission resources.

At <NUM>, method <NUM> includes transmitting, by a UE to a network entity, a RRC configuration message indicating a full-duplex capability of the UE. In an aspect, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM> may be configured to transmit, by a UE to a network entity, a RRC configuration message indicating a full-duplex capability of the UE. As such, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM>, e.g., in conjunction with controller/processor <NUM>, which may include the memory <NUM>, processor(s) <NUM>, which may include the memory <NUM>, modem <NUM>, TX processor <NUM>, and transceiver <NUM> may define a means for transmitting, by a UE to a network entity, a RRC configuration message indicating a full-duplex capability of the UE.

At <NUM>, method <NUM> includes receiving, by the UE from the network entity, a self-contained DCI format message including information associated with a first portion of the self-contained DCI. In an aspect, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM> may be configured to receive, by the UE from the network entity, a self-contained DCI format message including information associated with a first portion of the self-contained DCI. As such, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM>, e.g., in conjunction with controller/processor <NUM>, which may include the memory <NUM>, processor(s) <NUM>, which may include the memory <NUM>, modem <NUM>, TX processor <NUM>, and transceiver <NUM> may define a means for receiving, by the UE from the network entity, a self-contained DCI format message including information associated with a first portion of the self-contained DCI. In an aspect, the self-contained DCI format message would be capable of triggering downlink PDSCH and PUSCH for a full-duplex UE, such as UE <NUM>. For example, the first portion of the self-contained DCI format message further includes one or more downlink-related parameters for scheduling the downlink transmission and a pointer to scheduling information of remaining information in a second portion of the self-contained DCI.

At <NUM>, method <NUM> includes communicating, between the UE and the network entity, based on the DCI format message. In an aspect, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM> may be configured to communicate, between the UE and the network entity, based on the DCI format message. As such, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM>, e.g., in conjunction with controller/processor <NUM>, which may include the memory <NUM>, processor(s) <NUM>, which may include the memory <NUM>, modem <NUM>, TX processor <NUM>, and transceiver <NUM> may define a means for communicating, between the UE and the network entity, based on the DCI format message.

In an example of method <NUM>, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM> may be configured for determining that the scheduling information is within a scheduled PDSCH; and scheduling a PUSCH after an offset number of symbols based on the determination that the scheduling information is within the scheduled PDSCH.

In an example of method <NUM>, the offset number of symbols corresponds to a plurality of symbols subsequent to a last symbol carrying control information for the PUSCH.

In an example of method <NUM>, the first portion of the self-contained DCI format message includes one or more downlink-related parameters and no uplink-related parameters.

<FIG> is a flowchart <NUM> of a method of wireless communication not claimed by the present invention. The method may be performed by a UE (e.g., the UE <NUM>; the apparatus <NUM>; the controller/processor <NUM>, which may include the memory <NUM>, processor(s) <NUM>, which may include the memory <NUM>, modem <NUM> and which may be the entire UE <NUM> or a component of the UE <NUM>, such as the TX processor <NUM>, the RX processor <NUM>, and/or the transceiver <NUM>) in combination with the communication component <NUM>/configuration component <NUM>.

At <NUM>, method <NUM> includes transmitting, by a UE to a network entity, a RRC configuration message indicating at least one of a half-duplex capability or a full-duplex capability of the UE. In an aspect, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM> may be configured to transmit to a network entity, a RRC configuration message indicating at least one of a half-duplex capability or a full-duplex capability of the UE. As such, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM>, e.g., in conjunction with controller/processor <NUM>, which may include the memory <NUM>, processor(s) <NUM>, which may include the memory <NUM>, modem <NUM>, TX processor <NUM>, and transceiver <NUM> may define a means for transmitting, by a UE to a network entity, a RRC configuration message indicating at least one of a half-duplex capability or a full-duplex capability of the UE.

At <NUM>, method <NUM> includes receiving, by the UE from the network entity, a first DCI format message for scheduling receptions on a downlink channel. In an aspect, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM> may be configured to receive, from the network entity, a first DCI format message for scheduling receptions on a downlink channel. As such, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM>, e.g., in conjunction with controller/processor <NUM>, which may include the memory <NUM>, processor(s) <NUM>, which may include the memory <NUM>, modem <NUM>, TX processor <NUM>, and transceiver <NUM> may define a means for receiving, by the UE from the network entity, a first DCI format message for scheduling receptions on a downlink channel.

At <NUM>, method <NUM> includes receiving, by the UE from the network entity, a second DCI format message for scheduling transmission on an uplink channel. In one example, the first DCI format message is received separately from the second DCI format message. In an aspect, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM> may be configured to receive, from the network entity, a second DCI format message for scheduling transmission on an uplink channel. In one example, the first DCI format message is received separately from the second DCI format message. As such, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM>, e.g., in conjunction with controller/processor <NUM>, which may include the memory <NUM>, processor(s) <NUM>, which may include the memory <NUM>, modem <NUM>, TX processor <NUM>, and transceiver <NUM> may define a means for receiving, by the UE from the network entity, a second DCI format message for scheduling transmission on an uplink channel. In one example, the first DCI format message is received separately from the second DCI format message.

At <NUM>, method <NUM> includes communicating, between the UE and the network entity, based on the first DCI format message and the second DCI format message. In an aspect, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM> may be configured to communicate, with the network entity, based on the first DCI format message and the second DCI format message. As such, the UE <NUM> and/or the communication component <NUM>/configuration component <NUM>, e.g., in conjunction with controller/processor <NUM>, which may include the memory <NUM>, processor(s) <NUM>, which may include the memory <NUM>, modem <NUM>, TX processor <NUM>, and transceiver <NUM> may define a means for communicating, between the UE and the network entity, based on the first DCI format message and the second DCI format message.

In an example of method <NUM>, the scheduling of reception on the downlink channel and the scheduling of transmission on the uplink channel overlap in at least one OFDM symbol. For example, each of the first DCI format message and the second DCI format message include an indicator for identifying a full-duplex mode or a half-duplex mode.

In an example of method <NUM>, the second DCI format message is configured to be received within a threshold period of time from the reception of the first DCI format message. For example, the first DCI format message and the second DCI format message indicate a full-duplex mode and are associated with a same search space, appear in a same slot, appear on a same PDCCH monitoring span, and appear on a same common carrier.

Referring to <FIG>, one example of an implementation of UE <NUM> may include a variety of components, some of which have already been described above and are described further herein, including components such as one or more processors <NUM> and memory <NUM> and transceiver <NUM> in communication via one or more buses <NUM>, which may operate in conjunction with modem <NUM> and/or communication component <NUM> for improved downlink and uplink data DCI triggering for full-duplex UEs.

In an aspect, the one or more processors <NUM> can include a modem <NUM> and/or can be part of the modem <NUM> that uses one or more modem processors. Thus, the various functions related to communication component <NUM> may be included in modem <NUM> and/or processors <NUM> and, in an aspect, can be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors. For example, in an aspect, the one or more processors <NUM> may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with transceiver <NUM>. In other aspects, some of the features of the one or more processors <NUM> and/or modem <NUM> associated with communication component <NUM> may be performed by transceiver <NUM>.

Also, memory <NUM> may be configured to store data used herein and/or local versions of applications <NUM> or communicating component <NUM> and/or one or more of the subcomponents being executed by at least one processor <NUM>. Memory <NUM> can include any type of computer-readable medium usable by a computer or at least one processor <NUM>, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof. In an aspect, for example, memory <NUM> may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining communication component <NUM> and/or one or more of its subcomponents, and/or data associated therewith, when UE <NUM> is operating at least one processor <NUM> to execute communication component <NUM> and/or one or more of its subcomponents.

In an aspect, each filter <NUM> can be connected to a corresponding LNA <NUM> and/or PA <NUM>.

Furthermore, transceiver <NUM> and/or RF front end <NUM> may correspond to and/or be included in transceiver <NUM> with reference to <FIG> and antenna(s) <NUM> may correspond to antenna(s) <NUM> with reference to <FIG>.

Referring to <FIG>, one example of an implementation of base station <NUM> (e.g., a base station <NUM>, as described above) may include a variety of components, some of which have already been described above, but including components such as one or more processors <NUM> and memory <NUM> and transceiver <NUM> in communication via one or more buses <NUM>, which may operate in conjunction with modem <NUM> and communication component <NUM> for communicating reference signals.

Furthermore, transceiver <NUM> and/or RF front end <NUM> may correspond to and/or be included in transceiver <NUM> with reference to <FIG> and antenna(s) <NUM> may correspond to antenna(s) <NUM> with reference to <FIG>.

Claim 1:
A method of wireless communication, comprising:
transmitting (<NUM>), by a UE, to a network entity, a radio resource control, RRC, configuration message indicating a full-duplex capability of the UE;
receiving (<NUM>), by the UE from the network entity, a downlink control information, DCI, message, wherein the DCI message enables concurrent transmission of an uplink channel and reception of a downlink channel by the UE on a same component carrier,
wherein the DCI message includes one or more fields common to both the transmission on the uplink channel and the reception on the downlink channel on the same component carrier, and wherein the DCI message enables joint triggering of the concurrent transmission on the uplink channel and reception on the downlink channel by the UE; and
wherein the concurrent transmission and reception comprises a transmission and reception in at least one overlapping orthogonal frequency division multiplexing, OFDM, symbol; and
communicating (<NUM>), between the UE and the network entity, based on the DCI message.