Technology for downlink and uplink data DCI triggering for full-duplex UE in wireless communication system

Abstract

In one aspect, the present disclosure includes methods, apparatus, and computer-readable media for wireless communications, for: transmitting, by a UE, a radio resource control (RRC) configuration message indicating the UE's full-duplex capability to a network entity; receiving, by the UE, a downlink control information (DCI) message from the network entity, wherein the DCI message enables concurrent transmission on an uplink channel and reception on a downlink channel by the UE; and communicating between the UE and the network entity based on the DCI message.

Description

[0001] Cross-reference to related application(s)

[0002] This patent application claims the benefit of Greek application No. 20190100591, filed on December 27, 2019, entitled “TECHNIQUES FOR DOWNLINK AND UPLINK DATA DCI TRIGGERING FOR FULL DUPLEX UES IN A WIRELESS COMMUNICATION SYSTEM,” which is assigned to the assignee of this application and is hereby expressly incorporated herein by reference.

[0003] background

[0004] The present disclosure relates generally to communication systems, and more particularly to downlink control information (DCI) triggering for downlink and uplink data for full-duplex user equipment (UE) in Fifth Generation New Radio (5G NR).

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), and time division synchronous code division multiple access (TD-SCDMA).

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies.

[0007] As the demand for wireless communications continues to grow, it is desirable to improve the efficiency of wireless communication network technologies.

[0008] Overview

[0009] The following is a brief summary of one or more aspects to provide a basic understanding of such aspects. This summary is not an exhaustive overview of all conceivable aspects and is neither intended to identify key or critical elements of all aspects nor to define the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0010] An example implementation includes a method of wireless communication, the method comprising: transmitting, by a user equipment (UE), a radio resource control (RRC) configuration message to a network entity indicating the full-duplex capability of the UE; receiving, by the UE, a downlink control information (DCI) format message from the network entity, wherein the DCI format message enables concurrent transmission of an uplink channel and reception of a downlink channel by the UE on the same component carrier, wherein the concurrent transmission and reception include 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.

[0011] An example implementation includes a wireless communication method, the method comprising: transmitting, by a UE, an RRC configuration message to a network entity indicating at least one of half-duplex capability or full-duplex capability of the UE; receiving, by the UE from the network entity, a first DCI format message for scheduling reception 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.

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

[0013] To accomplish the foregoing and related ends, one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and accompanying drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are indicative of but a few of the various ways in which the principles of the various aspects may be employed, and this description is intended to encompass all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0016] Figure 2A 、 2B , 2C, and 2D are diagrams illustrating examples of a first 5G / NR frame, a DL channel within a 5G / NR subframe, a second 5G / NR frame, and a UL channel within a 5G / NR subframe, respectively.

[0017] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0018] Figure 4 This is a diagram explaining the full-duplex communication mode.

[0019] Figure 5 is a diagram illustrating the half-duplex communication mode.

[0020] Figure 6 This is a diagram explaining the full-duplex communication mode.

[0021] Figure 7 is a flow chart of a wireless communication method, and more particularly, a flow chart utilizing a DCI format configured for joint triggering of both uplink and downlink channels.

[0022] Figure 8 is a flow chart of a wireless communication method, and more particularly, a flow chart of independent DCI for overlapping downlink and uplink channel allocations.

[0023] Figure 9 is a flowchart of a wireless communication method according to another embodiment.

[0024] Figure 10 is a block diagram illustrating an example of a UE according to various aspects of the present disclosure.

[0025] Figure 11 is a block diagram illustrating an example of a base station in accordance with various aspects of the present disclosure.

[0026] Detailed description

[0027] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid overstating such concepts.

[0028] Several aspects of telecommunications systems will now be presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0029] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system" comprising one or more processors. Examples of processors include: a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gating logic, a discrete hardware circuit, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system can execute software. Software can be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether it is described in software, firmware, middleware, microcode, hardware description language, or other terms.

[0030] Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, each function may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of the aforementioned types of computer-readable media, or any other medium that can be used to store instructions or data structures in the form of computer-executable code that can be accessed by a computer.

[0031] Figure 1 1 is a diagram illustrating an example of a wireless communication system and access network 100 configured for downlink and uplink data downlink control information (DCI) triggering for full-duplex user equipment (UE) in fifth generation new radio (5G NR). The wireless communication system (also known as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)).

[0032] In certain aspects, the UE 104 may be configured to operate the communication component 198 and / or the configuration component 240 to transmit a radio resource control (RRC) configuration message to a network entity indicating the full-duplex capability of the UE; receive a DCI format message from the network entity, wherein the DCI format message enables concurrent transmission of an uplink channel and reception of a downlink channel by the UE on the same component carrier, wherein the concurrent transmission and reception include 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.

[0033] In another aspect, the UE 104 can be configured to operate the communication component 198 and / or the configuration component 240 to transmit an RRC configuration message indicating at least one of half-duplex capability or full-duplex capability of the UE to a network entity; receive a first DCI format message from the network entity for scheduling reception on a downlink channel; receive a second DCI format message from the network entity 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.

[0034] Accordingly, in certain aspects, a network entity (e.g., base station 102) and / or another UE (such as UE 104) may be configured to operate communicating component 199 and / or configuring component 241 to transmit DCI format messages to UE 104. For example, communicating component 199 and / or configuring component 241 may transmit one or more DCI format messages to UE 104 and communicate with UE 104 based on the DCI format messages.

[0035] Base stations 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femto cells, pico cells, and micro cells.

[0036] Base stations 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a backhaul link 132 (e.g., an S1 interface). Base stations 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG-RAN)) can interface with core network 190 via a backhaul link 184. Among other functions, base stations 102 can perform one or more of the following: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of alert messages. Base stations 102 may communicate with each other via backhaul links 134 (eg, an X2 interface), directly or indirectly (eg, through EPC 160 or core network 190). Backhaul links 132, 134, and 184 may be wired or wireless.

[0037] Base stations 102 can communicate wirelessly with UEs 104. Each base station 102 can provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102′ can have a coverage area 110′ that overlaps with the coverage area 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network can also include a home evolved Node B (eNB) (HeNB), which can provide service to a restricted group known as a closed subscriber group (CSG). The communication link 120 between the base station 102 and the UE 104 can include uplink (UL) (also known as reverse link) transmissions from the UE 104 to the base station 102 and / or downlink (DL) (also known as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 can utilize multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. These communication links may be over one or more carriers. For each carrier allocated in the carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use spectrum with a bandwidth of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.). These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carriers may be referred to as secondary cells (SCells).

[0038] Some UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use DL / UL WWAN spectrum. The D2D communication links 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be accomplished through various wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0039] The wireless communication system may further include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 in the 5 GHz unlicensed spectrum via a communication link 154. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available before communicating.

[0040] Small cell 102′ may operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102′ may employ NR and use the same 5 GHz unlicensed spectrum as used by Wi-Fi AP 150. Small cell 102′ employing NR in the unlicensed spectrum may improve access network coverage and / or increase access network capacity.

[0041] Whether a small cell 102′ or a large cell (e.g., a macro base station), base station 102 may include an eNB, a gNode B (gNB), or another type of base station. Some base stations, such as gNB 180, may operate in the traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near-mmW frequencies to communicate with UE 104. When gNB 180 operates in mmW or near-mmW frequencies, gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is a portion of the RF spectrum in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near-mmW extends down to 3 GHz frequencies with a wavelength of 100 mm. Super high frequency (SHF) bands extend between 3 GHz and 30 GHz and are also referred to as centimeter waves. Communications using mmW / near-mmW radio frequency bands (e.g., 3 GHz–300 GHz) have extremely high path loss and short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range.

[0042] Base station 180 may transmit beamformed signals in one or more transmit directions 182′ to UE 104. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182″. UE 104 may also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of base station 180 / UE 104. The transmit direction and receive direction of base station 180 may be the same or different. The transmit direction and receive direction of UE 104 may be the same or different.

[0043] EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. MME 162 may be in communication with a Home Subscriber Server (HSS) 174. MME 162 is a control node that handles signaling between UE 104 and EPC 160. Generally speaking, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through Serving Gateway 166, which itself is connected to PDN Gateway 172. PDN Gateway 172 provides UE Internet Protocol (IP) address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Services 176. IP services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), packet-switched (PS) streaming (PSS) services, and / or other IP services. BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may schedule MBMS transmissions. MBMS gateway 168 may distribute MBMS traffic to base stations 102 within a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and collecting eMBMS-related charging information.

[0044] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may be in communication with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Generally speaking, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are passed through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to the IP services 197. The IP services 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), PS streaming services, and / or other IP services.

[0045] A base station may also be referred to as a gNB, a NodeB, an evolved NodeB (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit reception point (TRP), or some other suitable terminology. Base station 102 provides an access point for UE 104 to EPC 160 or core network 190. Examples of UE 104 include a cellular phone, a smartphone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet device, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some UEs 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, an oven, a vehicle, a heart monitor, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0046] Figures 2A-2D Included are diagrams of example frame structures and resources that may be utilized in communications between base station 102, UE 104, and / or secondary UE (or sidelink UE) 110 as described in the present disclosure. Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G / NR frame structure. Figure 2B is a diagram 230 illustrating an example of DL channels within a 5G / NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G / NR frame structure. Figure 2D 280 is a diagram illustrating an example of UL channels within a 5G / NR subframe. The 5G / NR frame structure can be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL; or it can be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A and 2CIn the example provided, the 5G / NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL) and subframe 3 is configured with slot format 34 (mostly UL), where D is DL, U is UL, and X is for flexible use between DL / UL. Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible codewords. The UE is configured with the slot format (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling) via the received slot format indicator (SFI). Note that the following description also applies to the 5G / NR frame structure for TDD.

[0047] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, while for time slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter design. For slot configuration 0, different parameter designs μ of 0 to 5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter designs 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and parameter design μ, there are 14 symbols per slot and 2 per subframe. μ The subcarrier spacing and symbol length / duration vary depending on the parameter design. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter design 0 to 5. Thus, parameter design μ=0 has a subcarrier spacing of 15kHz, while parameter design μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D An example is provided for slot configuration 0 with 14 symbols per slot and parameter design μ = 0 with 1 slot per subframe. The subcarrier spacing is 15 kHz and the symbol duration is approximately 66.7 μs.

[0048] A resource grid can be used to represent the frame structure. Each slot includes a resource block (RB) (also called a physical RB (PRB)) that extends over 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0049] like Figure 2A As illustrated in

[15] , some REs carry reference (pilot) signals (RS) for the UE. The RSs may include a demodulation RS (DM-RS) (indicated as Rx for one specific configuration, where 100x is the port number, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RSs may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0050] Figure 2B An example of various DL channels within a subframe of a frame is illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE includes 9 RE groups (REGs), and each REG includes 4 consecutive REs in an OFDM symbol. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identity. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0051] As in Figure 2CAs illustrated in FIG, some REs carry DM-RSs for channel estimation at the base station (indicated as R for one specific configuration, but other DM-RS configurations are possible). The UE may transmit DM-RSs for the physical uplink control channel (PUCCH) and DM-RSs for the physical uplink shared channel (PUSCH). The PUSCH DM-RSs may be transmitted in the first one or the first two symbols of the PUSCH. The PUCCH DM-RSs may be transmitted in different configurations depending on whether a short PUCCH or a long PUCCH is transmitted and on the specific PUCCH format used. Although not shown, the UE may transmit a sounding reference signal (SRS). The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0052] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at the position indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and hybrid automatic repeat request (HARQ) ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0053] Figure 33 is a block diagram of a base station 310 and a UE 350 in communication in an access network, where base station 310 may be an example implementation of base station 102, and where UE 350 may be an example implementation of UE 104. In the DL, IP packets from EPC 160 may be provided to controller / processor 375. Controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0054] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes and for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0055] At the UE 350, each receiver 354RX receives a signal via its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the signal constellation point most likely transmitted by the base station 310. These soft decisions may be based on channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by the base station 310. These data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0056] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, cipher decoding, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0057] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto TBs, demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0058] Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by a TX processor 368 to select the appropriate coding and modulation scheme, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0059] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to an RX processor 370.

[0060] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, cipher decoding, header decompression, and control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0061] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The communication component 198 combines various aspects.

[0062] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The communication component 199 combines various aspects.

[0063] refer to Figure 4-10 The described features generally relate to downlink control information (DCI) triggering for downlink and uplink data for full-duplex UEs in fifth generation new radio (5G NR). For example, two separate DCI format messages are currently utilized when scheduling information for uplink and downlink channels.

[0064] Currently, DCI format 1_1 schedules information for downlink channels. In one example, DCI format 1_1 includes fields for the following: frequency domain resource assignment (FDRA), frequency domain assignment type (type 0 / 1), time domain resource allocation (TDRA), precoding resource block group (PRG) bundling indicator, VRB-2-PRB mapping indicator, carrier indicator, rate matching indicator, ZPCSI-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, and DMRS sequence initialization.

[0065] Currently, DCI format 0_1 schedules information for uplink channels. In one example, DCI format 0_1 includes fields for the following: carrier indicator, bandwidth fraction 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 port, SRS request, CSI request, CBG transmission information (CBGTI), PTRS-DMRS association, β_offset indicator, DMRS sequence initialization, and UL-SCH indicator.

[0066] Therefore, DCI format 1_1 and DCI format 0_1 share several fields, such as but not limited to antenna port and SRS request fields.

[0067] The present disclosure generally relates to the current problem of downlink and uplink data DCI triggering for full-duplex UEs. For example, in one aspect, the present disclosure includes methods, apparatus, and non-transitory computer-readable media for wireless communications, which are used to: transmit, by a UE, a radio resource control (RRC) configuration message indicating the full-duplex capability of the UE to a network entity; receive, by the UE, a DCI format message from the network entity, wherein the DCI format message enables concurrent transmission of an uplink channel and reception of a downlink channel by the UE on the same component carrier, wherein the concurrent transmission and reception include transmission and reception in at least one overlapping orthogonal frequency division multiplexing (OFDM) symbol; and communicate between the UE and the network entity based on the DCI format message. In another aspect, for example, the present disclosure includes methods, apparatus, and non-transitory computer-readable media for wireless communications, configured to: transmit, by a UE, an RRC configuration message indicating at least one of half-duplex capability or full-duplex capability of the UE to a network entity; receive, by the UE, from the network entity, a first DCI format message for scheduling reception on a downlink channel; receive, by the UE, from the network entity, a second DCI format message for scheduling transmission on an uplink channel; and communicate 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.

[0068] Figure 4FIG4 is a diagram illustrating a full-duplex communication mode. For example, scenario 410 depicts a full-duplex base station and half-duplex UEs 1 and 2. In scenario 410, a full-duplex first gNB can transmit to UE 1 on a downlink channel and receive from UE 2 on an uplink channel. However, UE 2 may cause interference on UE 1 due to its uplink transmission to the first gNB. Furthermore, a second gNB may cause interference on the first gNB due to its communications with both UE 1 and UE 2. Additionally, the first gNB may cause self-interference from both downlink and uplink communications.

[0069] In one aspect, scenario 420 depicts a full-duplex gNB and a full-duplex UE 1. In scenario 420, UE 1 experiences self-interference from full-duplex uplink and downlink communications with the first gNB, from UE 2 receiving downlink communications from a second gNB, and from downlink communications from the second gNB.

[0070] In one aspect, scenario 430 depicts a full-duplex UE 1 communicating simultaneously with a first gNB in uplink and a second gNB in downlink using multiple TRPs. For example, because UE 1 is the only entity configured in full-duplex mode, UE 1 experiences self-interference due to both uplink and downlink communications with the first gNB and the second gNB.

[0071] Figure 5 5 is a diagram illustrating a half-duplex communication mode. For example, scenario 510 depicts a transmit receive point 1 (TRP1) configured in full-duplex mode with a half-duplexed UE. Accordingly, diagram 520 depicts a subframe / timeslot decomposition for a full-duplex TRP1 and a half-duplex UE. In this example, entities can participate in time-flexible downlink and uplink operations across time slots and across UEs. That is, simultaneous PDSCH and PUSCH grants for the same subframe / time slot for different UEs can be configured. The UE can change the uplink transmit and / or downlink receive bandwidth portion between time slots with zero latency. The UE can transmit a sounding reference signal (SRS) using full reciprocity (e.g., full duplex) to cover the entire downlink bandwidth portion and partial reciprocity (e.g., half duplex) to cover a portion of the downlink bandwidth. In this example, the dotted lines of diagram 520 depict a subframe / timeslot decomposition for a full-duplex TRP1 and a half-duplex UE.

[0072] Figure 66 is a diagram illustrating a full-duplex communication mode. For example, scenario 610 depicts TRP1 configured in full-duplex mode with a full-duplexed UE and a half-duplexed UE. Accordingly, diagram 620 depicts a subframe / time slot decomposition of a full-duplex TRP1 and a full-duplex UE. In this example, entities can participate in downlink and uplink operations that are flexible in time across time slots and across UEs. That is, simultaneous PDSCH and PUSCH grants for the same subframe / time slot for different UEs can be configured. A full-duplex UE can be configured for uplink and downlink grants. The UE can change the uplink transmission and / or downlink reception bandwidth portion between each time slot with zero waiting time. The UE can transmit SRS using full reciprocity (e.g., full duplex) for covering the entire downlink bandwidth portion and partial reciprocity (e.g., half duplex) for covering a portion of the downlink bandwidth. In this example, the dotted line of diagram 620 depicts the subframe / timeslot breakdown for a full-duplex TRP1 and a half-duplex UE.

[0073] Figure 7 700 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104; apparatus 350; controller / processor 359 (which may include memory 360), processor(s) 1012 (which may include memory 1016, modem 1040), which may be the entire UE 104 or components of the UE 104 (such as TX processor 368, RX processor 356, and / or transceiver 1002)) in conjunction with communication component 198 / configuration component 240.

[0074] At 702, method 700 includes transmitting, by the UE, an RRC configuration message indicating full-duplex capability of the UE to a network entity. In one aspect, the UE 104 and / or the communication component 198 / configuration component 240 may be configured to transmit, to the network entity, an RRC configuration message indicating full-duplex capability of the UE. As such, the UE 104 and / or the communication component 198 / configuration component 240 (e.g., in conjunction with the controller / processor 359 (which may include memory 360), the processor(s) 1012 (which may include memory 1016, the modem 1040, the TX processor 368, and the transceiver 1002)) may define means for transmitting, by the UE, an RRC configuration message indicating full-duplex capability of the UE to the network entity.

[0075] At 704, method 700 includes receiving, by the UE from a network entity, a DCI format message, wherein the DCI format message enables a format for concurrent transmission of an uplink channel and reception of a downlink channel by the UE on the same component carrier, wherein the concurrent transmission and reception include transmission and reception in at least one overlapping OFDM symbol. In an aspect, UE 104 and / or communication component 198 / configuration component 240 may be configured to receive, from the network entity, a DCI format message, wherein the DCI format message enables a format for concurrent transmission of an uplink channel and reception of a downlink channel by the UE on the same component carrier, wherein the concurrent transmission and reception include transmission and reception in at least one overlapping OFDM symbol. As such, the UE 104 and / or the communication component 198 / configuration component 240 (e.g., in conjunction with the controller / processor 359 (which may include the memory 360), the processor(s) 1012 (which may include the memory 1016, the modem 1040, the RX processor 356, and the transceiver 1002)) may define means for receiving, by the UE, a DCI format message from a network entity, wherein the DCI format message is formatted to enable concurrent transmission of an uplink channel and reception of a downlink channel by the UE on the same component carrier, wherein the concurrent transmission and reception include transmission and reception in at least one overlapping OFDM symbol. For example, the transmission and reception may correspond to a partial overlap of the OFDM symbols.

[0076] In the example of method 700, the DCI format message implements a joint triggering of concurrent transmission on an uplink channel and reception on a downlink channel by the UE. For example, the uplink channel corresponds to a physical uplink shared channel (PUSCH) SRS or a channel for transmission of SRS. In addition, the downlink channel corresponds to a CSI-RS, a physical downlink shared channel (PDSCH), a positioning reference signal (PRS), and a tracking reference signal (TRS). In addition, the DCI format message is configured to schedule at least one of a downlink channel and an uplink channel that overlap in at least one OFDM symbol, the downlink channel including a group of OFDM symbols, and the uplink channel including a group of OFDM symbols.

[0077] In an example of method 700, the DCI format message includes one or more merged fields that are common to both transmission on the uplink channel and reception on the downlink channel. For example, the uplink channel and the downlink channel overlap on the same number of OFDM symbols of the shared carrier. The one or more merged fields include time domain resource allocation (TDRA) for both the downlink channel and the uplink channel. In one example, the TDRA includes a time domain resource allocation starting at a symbol offset after the reception of the DCI format message. In addition, the one or more merged fields include 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.

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

[0079] In an example of method 700, one or more merged fields include a mapping of virtual resource blocks (VRBs) to physical resource blocks (PRBs) associated with downlink and uplink channels.

[0080] In an example of method 700, the one or more combined fields include a DMRS sequence initialization associated with a first demodulation reference signal (DMRS) for a downlink channel and a second DMRS for an uplink channel.

[0081] In an example of method 700, the one or more merged fields include a joint DMRS port indication table identifying a port for each of the downlink channel and the uplink channel.

[0082] In an example of method 700, the one or more combined fields include a joint field that triggers both SRS resources and CSI RS resources on the same one or more OFDM symbols.

[0083] In an example of method 700, receiving, by the UE, a DCI format message from a network entity further includes receiving, by the UE, a first part of the DCI format message from the network entity, the first part including information indicating a location of a second part of the DCI format message, wherein the second part of the DCI format message includes remaining information not included in the first part of the DCI format message; and receiving, by the UE, the second part of the DCI format message from the network entity based on the first part of the DCI format message.

[0084] For example, the first part of the DCI format message includes one or more common fields for downlink channel and uplink channel allocation. In addition, the one or more common fields include at least one of the following: time domain resource allocation (TDRA), frequency domain resource assignment (FDRA), SRS request and CSI request.

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

[0086] At 706, method 700 includes communicating between the UE and a network entity based on the DCI format message. In one aspect, UE 104 and / or communication component 198 / configuration component 240 can be configured to transmit data to one or more second UEs using the one or more reserved transmission resources. As such, UE 104 and / or communication component 198 / configuration component 240 (e.g., in conjunction with controller / processor 359 (which may include memory 360), processor(s) 1012 (which may include memory 1016, modem 1040, RX processor 356, and transceiver 1002)) can define means for transmitting data by a first UE to one or more second UEs using the one or more reserved transmission resources.

[0087] Figure 8 800 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104; apparatus 350; controller / processor 359 (which may include memory 360), processor(s) 1012 (which may include memory 1016, modem 1040), which may be the entire UE 104 or components of the UE 104 (such as TX processor 368, RX processor 356, and / or transceiver 1002)) in conjunction with communication component 198 / configuration component 240.

[0088] At 802, method 800 includes transmitting, by the UE, an RRC configuration message indicating full-duplex capability of the UE to a network entity. In one aspect, the UE 104 and / or the communication component 198 / configuration component 240 may be configured to transmit, by the UE, an RRC configuration message indicating full-duplex capability of the UE to the network entity. As such, the UE 104 and / or the communication component 198 / configuration component 240 (e.g., in conjunction with the controller / processor 359 (which may include memory 360), the processor(s) 1012 (which may include memory 1016, the modem 1040, the TX processor 368, and the transceiver 1002)) may define means for transmitting, by the UE, an RRC configuration message indicating full-duplex capability of the UE to the network entity.

[0089] At 804, method 800 includes receiving, by the UE, a self-contained DCI format message from a network entity, the self-contained DCI format message including information associated with a first portion of the self-contained DCI. In one aspect, UE 104 and / or communication component 198 / configuration component 240 may be configured to receive, by the UE, a self-contained DCI format message from the network entity, the self-contained DCI format message including information associated with the first portion of the self-contained DCI. As such, UE 104 and / or communication component 198 / configuration component 240 (e.g., in conjunction with controller / processor 359 (which may include memory 360), processor(s) 1012 (which may include memory 1016, modem 1040, TX processor 368, and transceiver 1002)) may define means for receiving, by the UE, a self-contained DCI format message from the network entity, the self-contained DCI format message including information associated with the first portion of the self-contained DCI. In one aspect, the self-contained DCI format message will be able to trigger downlink PDSCH and PUSCH for a full-duplex UE, such as UE 104. For example, the first portion of the self-contained DCI format message further includes one or more downlink-related parameters for scheduling downlink transmissions, and a pointer to scheduling information that points to the remaining information in the second portion of the self-contained DCI.

[0090] At 806, method 800 includes communicating between the UE and the network entity based on the DCI format message. In one aspect, the UE 104 and / or the communication component 198 / configuration component 240 can be configured to communicate between the UE and the network entity based on the DCI format message. As such, the UE 104 and / or the communication component 198 / configuration component 240 (e.g., in conjunction with the controller / processor 359 (which can include memory 360), the processor(s) 1012 (which can include memory 1016, the modem 1040, the TX processor 368, and the transceiver 1002)) can define means for communicating between the UE and the network entity based on the DCI format message.

[0091] In an example of method 800, UE 104 and / or communication component 198 / configuration component 240 may be configured to determine that scheduling information is within the scheduled PDSCH; and schedule the PUSCH after the offset number of symbols based on the determination that the scheduling information is within the scheduled PDSCH.

[0092] In the example of method 800, the offset number of symbols corresponds to a number of symbols after the last symbol carrying control information for the PUSCH.

[0093] In the example of method 800 , the first portion of the self-contained DCI format message includes one or more downlink-related parameters but does not include uplink-related parameters.

[0094] Figure 9 Flowchart 900 of a method of wireless communication. The method may be performed by a UE (e.g., UE 104; apparatus 350; controller / processor 359 (which may include memory 360), processor(s) 1012 (which may include memory 1016, modem 1040), which may be the entire UE 104 or components of the UE 104 (such as TX processor 368, RX processor 356, and / or transceiver 1002)) in conjunction with communication component 198 / configuration component 240.

[0095] At 902, method 900 includes transmitting, by the UE, an RRC configuration message to a network entity indicating at least one of half-duplex capability or full-duplex capability of the UE. In one aspect, the UE 104 and / or the communication component 198 / configuration component 240 may be configured to transmit, to the network entity, an RRC configuration message indicating at least one of half-duplex capability or full-duplex capability of the UE. As such, the UE 104 and / or the communication component 198 / configuration component 240 (e.g., in conjunction with the controller / processor 359 (which may include memory 360), the processor(s) 1012 (which may include memory 1016, the modem 1040, the TX processor 368, and the transceiver 1002)) may define means for transmitting, by the UE, an RRC configuration message to the network entity indicating at least one of half-duplex capability or full-duplex capability of the UE.

[0096] At 904, method 900 includes receiving, by the UE, a first DCI format message for scheduling reception on a downlink channel from a network entity. In one aspect, the UE 104 and / or the communication component 198 / configuration component 240 may be configured to receive, from the network entity, a first DCI format message for scheduling reception on a downlink channel. As such, the UE 104 and / or the communication component 198 / configuration component 240 (e.g., in conjunction with the controller / processor 359 (which may include memory 360), the processor(s) 1012 (which may include memory 1016, the modem 1040, the TX processor 368, and the transceiver 1002)) may define means for receiving, by the UE, from the network entity, a first DCI format message for scheduling reception on a downlink channel.

[0097] At 906, method 900 includes receiving, by the UE, a second DCI format message for scheduling transmissions on an uplink channel from a network entity. In one example, the first DCI format message is received separately from the second DCI format message. In one aspect, the UE 104 and / or the communication component 198 / configuration component 240 may be configured to receive, from the network entity, a second DCI format message for scheduling transmissions 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 104 and / or the communication component 198 / configuration component 240 (e.g., in conjunction with the controller / processor 359 (which may include memory 360), the processor(s) 1012 (which may include memory 1016, the modem 1040, the TX processor 368, and the transceiver 1002)) may define means for receiving, by the UE, a second DCI format message for scheduling transmissions on an uplink channel from the network entity. In one example, the first DCI format message is received separately from the second DCI format message.

[0098] At 908, method 900 includes communicating between the UE and the network entity based on the first DCI format message and the second DCI format message. In one aspect, the UE 104 and / or the communication component 198 / configuration component 240 can 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 104 and / or the communication component 198 / configuration component 240 (e.g., in conjunction with the controller / processor 359 (which may include the memory 360), the processor(s) 1012 (which may include the memory 1016, the modem 1040, the TX processor 368, and the transceiver 1002)) can define means for communicating between the UE and the network entity based on the first DCI format message and the second DCI format message.

[0099] In the example of method 900, 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 includes an indicator for identifying full duplex mode or half duplex mode.

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

[0101] Reference Figure 10 , one example of an implementation of the UE 104 may include various components, some of which have been described above and are further described herein, including components such as one or more processors 1012 and memory 1016 in communication via one or more buses 1044 and a transceiver 1002, which may operate in conjunction with a modem 1040 and / or a configuration component 198 for improved downlink and uplink data DCI triggering for full-duplex UEs.

[0102] In one aspect, the one or more processors 1012 may include the modem 1040 and / or may be part of the modem 1040 using one or more modem processors. Thus, various functions associated with the communication component 198 may be included in the modem 1040 and / or the processor 1012 and, in one aspect, may be performed by a single processor, while in other aspects, different ones of these functions may be performed by a combination of two or more different processors. For example, in one aspect, the one or more processors 1012 may include any one or any combination of the following: a modem processor, a baseband processor, a digital signal processor, a transmit processor, a receiver processor, or a transceiver processor associated with the transceiver 1002. In other aspects, some of the features of the one or more processors 1012 and / or the modem 1040 associated with the communication component 198 may be performed by the transceiver 1002.

[0103] In addition, the memory 1016 can be configured to store data used herein and / or local versions of the applications 1075 or the communication component 198 and / or one or more subcomponents executed by the at least one processor 1012. The memory 1016 may include any type of computer-readable medium usable by a computer or the at least one processor 1012, such as random access memory (RAM), read-only memory (ROM), tape, magnetic disk, optical disk, volatile memory, non-volatile memory, and any combination thereof. In one aspect, for example, when the UE 104 is operating the at least one processor 1012 to execute the communication component 198 and / or one or more subcomponents thereof, the memory 1016 may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining the communication component 198 and / or one or more subcomponents thereof and / or data associated therewith.

[0104] Transceiver 1002 may include at least one receiver 1006 and at least one transmitter 1008. Receiver 1006 may include hardware for receiving data and / or software code executable by a processor, the code comprising instructions and stored in memory (e.g., a computer-readable medium). Receiver 1006 may be, for example, a radio frequency (RF) receiver. In one aspect, receiver 1006 may receive signals transmitted by at least one base station 102. Receiver 1006 may also process such received signals and obtain signal measurements such as, but not limited to, Ec / Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), and the like. Transmitter 1008 may include hardware and / or software executable by a processor for transmitting data, the code comprising instructions and stored in memory (e.g., a computer-readable medium). Suitable examples of transmitter 1008 may include, but are not limited to, an RF transmitter.

[0105] Moreover, in an aspect, the UE 104 may include an RF front end 1088 that may operate in communication with the one or more antennas 1065 and the transceiver 1002 for receiving and transmitting radio transmissions, such as wireless communications transmitted by at least one base station 102 or wireless transmissions transmitted by the UE 104. The RF front end 1088 may be connected to the one or more antennas 1065 and may include one or more low noise amplifiers (LNAs) 1090, one or more switches 1092, one or more power amplifiers (PAs) 1098, and one or more filters 1096 for transmitting and receiving RF signals.

[0106] In one aspect, the LNA 1090 can amplify the received signal to a desired output level. In one aspect, each LNA 1090 can have specified minimum and maximum gain values. In one aspect, the RF front end 1088 can use one or more switches 1092 to select a particular LNA 1090 and its specified gain value based on the desired gain value for a particular application.

[0107] Furthermore, for example, one or more PAs 1098 can be used by the RF front end 1088 to amplify the signal to obtain an RF output at a desired output power level. In one aspect, each PA 1098 can have a specified minimum and maximum gain value. In one aspect, the RF front end 1088 can use one or more switches 1092 to select a specific PA 1098 and its specified gain value based on the desired gain value for a particular application.

[0108] Additionally, for example, one or more filters 1096 can be used by the RF front end 1088 to filter a received signal to obtain an input RF signal. Similarly, in one aspect, for example, a corresponding filter 1096 can be used to filter the output from a corresponding PA 1098 to produce an output signal for transmission. In one aspect, each filter 1096 can be connected to a corresponding LNA 1090 and / or PA 1098. In one aspect, the RF front end 1088 can use one or more switches 1092 to select a transmit or receive path using a specified filter 1096, LNA 1090, and / or PA 1098 based on a configuration as specified by the transceiver 1002 and / or the processor 1012.

[0109] As such, the transceiver 1002 can be configured to transmit and receive wireless signals via the RF front end 1088 through one or more antennas 1065. In an aspect, the transceiver can be tuned to operate at a specified frequency so that the UE 104 can communicate, for example, with one or more base stations 102 or one or more cells associated with the one or more base stations 102. In an aspect, the modem 1040 can configure the transceiver 1002 to operate at a specified frequency and power level based on, for example, the UE configuration of the UE 104 and the communication protocol used by the modem 1040.

[0110] In one aspect, the modem 1040 may be a multi-band, multi-mode modem that can process digital data and communicate with the transceiver 1002 so that the digital data is sent and received using the transceiver 1002. In one aspect, the modem 1040 may be multi-band and configured to support multiple frequency bands for a specific communication protocol. In one aspect, the modem 1040 may be multi-mode and configured to support multiple operating networks and communication protocols. In one aspect, the modem 1040 may control one or more components of the UE 104 (e.g., the RF front end 1088, the transceiver 1002) to enable transmission and / or reception of signals from the network based on a specified modem configuration. In one aspect, the modem configuration may be based on the mode of the modem and the frequency band used. In another aspect, the modem configuration may be based on UE configuration information associated with the UE 104, such as provided by the network during cell selection and / or cell reselection.

[0111] In one aspect, processor(s) 1012 may correspond to a processor that is coupled to Figure 3 Similarly, the memory 1016 may correspond to one or more of the processors described in conjunction with the UE. Figure 3 Furthermore, the transceiver 1002 and / or the RF front end 1088 may correspond to and / or be included in the reference Figure 3 The transceiver 354 of FIG. 1 and the antenna(s) 1065 may correspond to the reference Figure 3 Antenna(s) 352.

[0112] Reference Figure 11 , one example of an implementation of a base station 102 (e.g., base station 102, as described above) may include various components, some of which have been described above, but also include components such as one or more processors 1112 and memory 1116 in communication via one or more buses 1144 and a transceiver 1102, which may operate in conjunction with a modem 1140 and a communication component 199 for communicating reference signals.

[0113] The transceiver 1102, receiver 1106, transmitter 1108, one or more processors 1112, memory 1116, applications 1175, bus 1144, RF front end 1188, LNA 1190, switch 1192, filter 1196, PA 1198, and one or more antennas 1165 may be the same as or similar to the corresponding components of the UE 104 as described above, but are configured or otherwise programmed for base station operation rather than UE operation.

[0114] In one aspect, processor(s) 1112 may correspond to a processor that is coupled to Figure 3Similarly, the memory 1116 may correspond to one or more of the processors described in conjunction with the base station. Figure 3 Furthermore, the transceiver 1102 and / or the RF front end 1188 may correspond to and / or be included in reference Figure 3 and the antenna(s) 1165 may correspond to the reference Figure 3 Antenna(s) 320.

[0115] Some further example clauses

[0116] Implementation examples are described in the following numbered clauses:

[0117] 1. A wireless communication method, comprising:

[0118] Transmitting, by the UE to the network entity, a radio resource control (RRC) configuration message indicating the full-duplex capability of the UE;

[0119] receiving, by the UE, a downlink control information (DCI) message from a network entity, wherein the DCI message enables concurrent transmission of an uplink channel and reception of a downlink channel by the UE on the same component carrier,

[0120] wherein the DCI message comprises one or more fields that are common to both transmission on an uplink channel and reception on a downlink channel on the same component carrier, and

[0121] wherein the concurrent transmitting and receiving comprises transmitting and receiving in at least one overlapping orthogonal frequency division multiplexing (OFDM) symbol; and

[0122] Communication is performed between the UE and a network entity based on the DCI message.

[0123] 2. The method of any of the preceding clauses, wherein the DCI message enables joint triggering of concurrent transmission on an uplink channel and reception on a downlink channel by the UE.

[0124] 3. The method of any of the preceding clauses, wherein the uplink channel corresponds to a physical uplink shared channel (PUSCH), a sounding reference signal (SRS).

[0125] 4. A method as in any of the preceding clauses, wherein the downlink channel corresponds to a channel state information reference signal (CSI-RS), a physical downlink shared channel (PDSCH), a positioning reference signal (PRS), or a tracking reference signal (TRS).

[0126] 5. A method as in any of the preceding clauses, wherein the DCI message is configured to schedule at least one of a downlink channel and an uplink channel that overlap in at least one orthogonal frequency division multiplexing (OFDM) symbol, the downlink channel comprising a set of OFDM symbols, and the uplink channel comprising a set of OFDM symbols.

[0127] 6. The method of any of the preceding clauses, wherein the uplink channel and the downlink channel overlap over the same number of OFDM symbols of the common carrier.

[0128] 7. The method of any of the preceding clauses, wherein the one or more common fields include a time domain resource allocation (TDRA) for both downlink and uplink channels.

[0129] 8. The method of any of the preceding clauses, wherein the TDRA comprises a time domain resource allocation starting at a symbol offset after reception of the DCI message.

[0130] 9. The method of any of the preceding clauses, wherein the one or more common fields include a first frequency domain resource assignment (FDRA) for a downlink channel and a second FDRA for an uplink channel, wherein the first FDRA occupies a greater number of bits than the second FDRA.

[0131] 10. The method of any of the preceding clauses, wherein the one or more common fields include a joint transmission configuration indication (TCI) indication.

[0132] 11. The method of any of the preceding clauses, wherein each of the one or more TCI states has a quasi-co-location (QCL) for a downlink channel and a QCL for an uplink channel.

[0133] 12. The method of any of the preceding clauses, wherein each of the one or more TCI states has a quasi-co-location (QCL) for a downlink channel and a sounding reference signal (SRS) resource indicator (SRI) for an uplink channel.

[0134] 13. The method of any of the preceding clauses, wherein the one or more common fields include a mapping of virtual resource blocks (VRBs) to physical resource blocks (PRBs) associated with downlink channels and uplink channels.

[0135] 14. The method of any of the preceding clauses, wherein the one or more common fields include a DMRS sequence initialization associated with a first demodulation reference signal (DMRS) for a downlink channel and a second DMRS for an uplink channel.

[0136] 15. The method of any preceding clause, wherein the one or more common fields include a joint demodulation reference signal (DMRS) port indication table identifying a port for each of a downlink channel and an uplink channel.

[0137] 16. The method of any of the preceding clauses, wherein the one or more common fields include a joint field that triggers both a sounding reference signal (SRS) resource and a channel station information (CSI) reference signal (RS) resource on the same one or more OFDM symbols.

[0138] 17. The method of any preceding clause, wherein receiving, by the UE, a DCI message from a network entity further comprises:

[0139] receiving, by the UE from a network entity, a first part of a DCI message, the first part including information indicating a location of a second part of the DCI message, wherein the second part of the DCI message includes remaining information not included in the first DCI message; and

[0140] A second part of the DCI message is received by the UE from the network entity based on the first part of the DCI message.

[0141] 18. The method of any of the preceding clauses, wherein the first part of the DCI message comprises one or more common fields for downlink channel and uplink channel allocations.

[0142] 19. The method of any of the preceding clauses, wherein the one or more common fields include at least one of: a time domain resource allocation (TDRA), a frequency domain resource assignment (FDRA), a sounding reference signal (SRS) request, and a channel station information (CSI) request.

[0143] 20. A wireless communication method, comprising:

[0144] Transmitting, by the UE to the network entity, a radio resource control (RRC) configuration message indicating the full-duplex capability of the UE;

[0145] receiving, by the UE from a network entity, a self-contained downlink control information (DCI) message including information associated with a first portion of the self-contained DCI message; and

[0146] Communication between the UE and a network entity is based on the self-contained DCI message.

[0147] 21. A method as in any of the preceding clauses, wherein the first part of the self-contained DCI message further comprises one or more downlink-related parameters for scheduling downlink transmissions, and a pointer to scheduling information of the remaining information in the second part of the self-contained DCI message.

[0148] 22. The method of any of the preceding clauses, further comprising

[0149] determining that the scheduling information is within a scheduled physical downlink shared channel (PDSCH); and

[0150] Based on the determination that scheduling information is within the scheduled PDSCH, a physical uplink shared channel (PUSCH) is scheduled after an offset number of symbols.

[0151] 23. The method of any of the preceding clauses, wherein the offset number of symbols corresponds to a number of symbols after the last symbol carrying control information for the PUSCH.

[0152] 24. The method of any of the preceding clauses, wherein the first part of the self-contained DCI message comprises one or more downlink-related parameters but no uplink-related parameters.

[0153] 25. A user equipment (UE) for wireless communication, comprising:

[0154] transceiver;

[0155] a memory configured to store instructions; and

[0156] one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to cause the UE to:

[0157] transmitting, via the transceiver, a radio resource control (RRC) configuration message to a network entity indicating full-duplex capability of the UE;

[0158] receiving, via the transceiver, a downlink control information (DCI) message from a network entity, wherein the DCI message enables concurrent transmission of an uplink channel and reception of a downlink channel by the UE on the same component carrier,

[0159] wherein the DCI message comprises one or more fields that are common to both transmission on an uplink channel and reception on a downlink channel on the same component carrier, and

[0160] wherein the concurrent transmitting and receiving comprises transmitting and receiving in at least one overlapping orthogonal frequency division multiplexing (OFDM) symbol; and

[0161] Communication is performed between the UE and a network entity based on the DCI message.

[0162] 26. The UE of any of the preceding clauses, wherein the DCI message enables joint triggering of concurrent transmission on an uplink channel and reception on a downlink channel by the UE.

[0163] 27. The UE of any of the preceding clauses, wherein the uplink channel corresponds to a Physical Uplink Shared Channel (PUSCH), a Sounding Reference Signal (SRS).

[0164] 28. A UE as described in any of the preceding clauses, wherein the downlink channel corresponds to a channel state information reference signal (CSI-RS), a physical downlink shared channel (PDSCH), a positioning reference signal (PRS), and a tracking reference signal (TRS).

[0165] 29. A UE as described in any of the preceding clauses, wherein the DCI message is configured to schedule at least one of a downlink channel and an uplink channel that overlap in at least one orthogonal frequency division multiplexing (OFDM) codeword, the downlink channel comprising a set of OFDM codewords, and the uplink channel comprising a set of OFDM codewords.

[0166] 30. The UE of any of the preceding clauses, wherein the uplink channel and the downlink channel overlap over the same number of OFDM symbols of the common carrier.

[0167] 31. The UE of any of the preceding clauses, wherein the one or more common fields include a time domain resource allocation (TDRA) for both downlink and uplink channels.

[0168] 32. The UE of any of the preceding clauses, wherein the TDRA comprises a time domain resource allocation starting at a symbol offset after reception of the DCI message.

[0169] 33. The UE of any of the preceding clauses, wherein the one or more common fields include a first frequency domain resource assignment (FDRA) for a downlink channel and a second FDRA for an uplink channel, wherein the first FDRA occupies a greater number of bits than the second FDRA.

[0170] 34. The UE of any preceding clause, wherein the one or more common fields comprise a joint transmission configuration indication (TCI) indication.

[0171] 35. The UE of any of the preceding clauses, wherein each of the one or more TCI states has quasi co-location (QCL) for a downlink channel and QCL for an uplink channel.

[0172] 36. The UE of any of the preceding clauses, wherein each of the one or more TCI states has a quasi-co-location (QCL) for a downlink channel and a sounding reference signal (SRS) resource indicator (SRI) for an uplink channel.

[0173] 37. The UE of any of the preceding clauses, wherein the one or more common fields include a mapping of virtual resource blocks (VRBs) to physical resource blocks (PRBs) associated with downlink channels and uplink channels.

[0174] 38. The UE of any of the preceding clauses, wherein the one or more fields include a demodulation reference signal (DMRS) sequence initialization associated with a first DMRS for a downlink channel and a second DMRS for an uplink channel.

[0175] 39. The UE of any of the preceding clauses, wherein the one or more common fields include a joint demodulation reference signal (DMRS) port indication table identifying a port for each of a downlink channel and an uplink channel.

[0176] 40. The UE of any of the preceding clauses, wherein the one or more common fields include a joint field that triggers both a sounding reference signal (SRS) resource and a channel station information (CSI) reference signal (RS) resource on the same one or more OFDM symbols.

[0177] 41. The UE of any preceding clause, wherein receiving a DCI message from a network entity further comprises:

[0178] receiving, via a transceiver, a first portion of a DCI message from a network entity, the first portion including information indicating a location of a second portion of the DCI message, wherein the second portion of the DCI message includes remaining information not included in the first DCI message; and

[0179] A second portion of the DCI message is received from a network entity via the transceiver based on the first portion of the DCI message.

[0180] 42. The UE of any of the preceding clauses, wherein the first part of the DCI message comprises one or more common fields for downlink channel and uplink channel allocations.

[0181] 43. The UE of any of the preceding clauses, wherein the one or more common fields include at least one of: a time domain resource allocation (TDRA), a frequency domain resource assignment (FDRA), a sounding reference signal (SRS) request, and a channel station information (CSI) request.

[0182] 44. A user equipment (UE) for wireless communication, comprising:

[0183] transceiver;

[0184] a memory configured to store instructions; and

[0185] one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to cause the UE to:

[0186] transmitting, via the transceiver, a radio resource control (RRC) configuration message to a network entity indicating full-duplex capability of the UE;

[0187] receiving, via a transceiver, a self-contained downlink control information (DCI) message from a network entity, the self-contained downlink control information (DCI) message including information associated with a first portion of the self-contained DCI message; and

[0188] Communicate with a network entity based on the self-contained DCI message.

[0189] 45. A UE as claimed in any of the preceding clauses, wherein the first part of the self-contained DCI message further comprises one or more downlink-related parameters for scheduling downlink transmissions, and a pointer to scheduling information of the remaining information in the second part of the self-contained DCI message.

[0190] 46. The UE of any preceding clause, wherein the one or more processors are further configured to cause the UE to:

[0191] determining that the scheduling information is within a scheduled physical downlink shared channel (PDSCH); and

[0192] Based on the determination that scheduling information is within the scheduled PDSCH, a physical uplink shared channel (PUSCH) is scheduled after an offset number of symbols.

[0193] 47. A UE as in any of the preceding clauses, wherein the offset number of symbols corresponds to a number of symbols after the last symbol carrying control information for the PUSCH.

[0194] 48. A UE as claimed in any of the preceding clauses, wherein the first part of the self-contained DCI message comprises one or more downlink-related parameters but not uplink-related parameters.

[0195] 49. A user equipment (UE) for wireless communication, comprising:

[0196] means for transmitting a radio resource control (RRC) configuration message indicating the full-duplex capability of the UE to a network entity;

[0197] means for receiving a downlink control information (DCI) message from a network entity, wherein the DCI message enables concurrent transmission of an uplink channel and reception of a downlink channel by a UE on the same component carrier,

[0198] wherein the DCI message comprises one or more fields that are common to both transmission on an uplink channel and reception on a downlink channel on the same component carrier, and

[0199] wherein the concurrent transmitting and receiving comprises transmitting and receiving in at least one overlapping orthogonal frequency division multiplexing (OFDM) symbol; and

[0200] Means for communicating between the UE and a network entity based on the DCI message.

[0201] 50. A user equipment (UE) for wireless communication, comprising:

[0202] means for transmitting a radio resource control (RRC) configuration message indicating the full-duplex capability of the UE to a network entity;

[0203] means for receiving a self-contained downlink control information (DCI) message from a network entity, the self-contained downlink control information (DCI) message including information associated with a first portion of the self-contained DCI message; and

[0204] Means for communicating between the UE and a network entity based on the DCI message.

[0205] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowcharts is an illustration of an example approach. It should be understood that the specific order or hierarchy of the blocks in these process / flowcharts can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The accompanying method claims present the elements of the various blocks in an example order and are not meant to be limited to the specific order or hierarchy presented.

[0206] The preceding description is provided to enable anyone skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the universal principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but rather to be granted the full scope consistent with the language of the claims, wherein singular references to elements are not intended to mean "one and only one," but rather "one or more," unless otherwise specified. The term "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as superior to or surpassing other aspects. Unless otherwise specifically stated, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple As, multiple Bs, or multiple Cs. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the various aspects described throughout this disclosure to those of ordinary skill in the art now or hereafter known are expressly incorporated herein by reference and are intended to be encompassed by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is expressly recited in the claims. The terms "module," "mechanism," "element," "device," etc. are not intended to be a substitute for the term "means." As such, no claim element should be construed as means-plus-function unless the element is expressly recited using the phrase "means for."

Claims

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

2. The method according to claim 1, wherein The DCI message enables joint triggering of concurrent transmission on the uplink channel and reception on the downlink channel by the UE.

3. The method according to claim 2, wherein: The uplink channel corresponds to at least one of the following: a physical uplink shared channel (PUSCH) or a channel for transmission of a sounding reference signal (SRS), and wherein the downlink channel corresponds to at least one of the following: a channel for transmission of a channel state information reference signal (CSI-RS), a physical downlink shared channel (PDSCH), a channel for transmission of a positioning reference signal (PRS), or a channel for transmission of a tracking reference signal (TRS).

4. The method according to claim 2, wherein: The DCI message is configured to schedule at least one of the downlink channel and the uplink channel overlapping in at least one Orthogonal Frequency Division Multiplexing (OFDM) symbol, wherein the downlink channel and the uplink channel each include a group of OFDM symbols.

5. The method according to claim 1, wherein The uplink channel and the downlink channel overlap over the same number of OFDM symbols of a common carrier.

6. The method of claim 1, wherein: The one or more common fields include a time domain resource allocation (TDRA) for both the downlink channel and the uplink channel.

7. The method according to claim 6, wherein: The TDRA starts at a symbol offset after reception of the DCI message.

8. The method of claim 1, wherein: The one or more common fields include 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.

9. The method of claim 1, wherein: The one or more common fields include a joint transmission configuration indication (TCI) indication.

10. The method of claim 9, wherein: Each of the one or more TCI states has a first quasi-co-location (QCL) for the downlink channel and a second QCL for the uplink channel or a sounding reference signal (SRS) resource indicator (SRI) for the uplink channel.

11. The method of claim 1, wherein: The one or more common fields include at least one of the following: mapping of virtual resource blocks (VRBs) associated with the downlink channel and the uplink channel to physical resource blocks (PRBs); Initializing a DMRS sequence associated with a first demodulation reference signal (DMRS) of the downlink channel and a second DMRS of the uplink channel; a joint demodulation reference signal (DMRS) port indication table identifying a port for each of the downlink channel and the uplink channel; or A joint field of both sounding reference signal (SRS) resources and channel station information (CSI) reference signal (RS) resources is triggered on the same OFDM symbol or symbols.

12. The method of claim 1, wherein: Receiving, by the UE, the DCI message from the network entity further includes: receiving, by the UE from the network entity, a first part of the DCI message, the first part including information indicating a location of a second part of the DCI message, wherein the second part of the DCI message includes remaining information not included in the first part of the DCI message; and The second part of the DCI message is received by the UE from the network entity based on the first part of the DCI message.

13. The method of claim 12, wherein: The first portion of the DCI message includes one or more common fields for downlink channel allocation and uplink channel allocation.

14. The method of claim 13, wherein: The one or more common fields include at least one of: a time domain resource allocation (TDRA), a frequency domain resource assignment (FDRA), a sounding reference signal (SRS) request, and a channel station information (CSI) request.

15. A user equipment (UE) for wireless communication, comprising: transceiver; a memory configured to store instructions; as well as one or more processors coupled to the transceiver and the memory, wherein the one or more processors are configured to cause the UE to: transmitting, via the transceiver, a radio resource control (RRC) configuration message indicating full-duplex capability of the UE to a network entity; receiving, via the transceiver, a downlink control information (DCI) message from the network entity, wherein the DCI message enables concurrent transmission of an uplink channel and reception of a downlink channel by the UE on the same component carrier, wherein the DCI message comprises one or more fields that are common to both the transmission on the uplink channel and the reception on the downlink channel on the same component carrier, wherein the concurrent transmission of the uplink channel and reception of the downlink channel comprises respective transmission and reception in at least one overlapping orthogonal frequency division multiplexing (OFDM) symbol; and Communication is performed between the UE and the network entity based on the DCI message.

16. The UE according to claim 15, wherein: The DCI message enables joint triggering of concurrent transmission on the uplink channel and reception on the downlink channel by the UE.

17. The UE according to claim 16, wherein: The uplink channel corresponds to at least one of the following: a physical uplink shared channel (PUSCH) or a channel for transmission of a sounding reference signal (SRS), and wherein the downlink channel corresponds to at least one of the following: a channel for transmission of a channel state information reference signal (CSI-RS), a physical downlink shared channel (PDSCH), a channel for transmission of a positioning reference signal (PRS), or a channel for transmission of a tracking reference signal (TRS).

18. The UE according to claim 16, wherein: The DCI message is configured to schedule at least one of the downlink channel and the uplink channel overlapping in at least one Orthogonal Frequency Division Multiplexing (OFDM) symbol, wherein the downlink channel and the uplink channel each include a group of OFDM symbols.

19. The UE according to claim 15, wherein: The uplink channel and the downlink channel overlap over the same number of OFDM symbols of a common carrier.

20. The UE according to claim 15, wherein: The one or more common fields include a time domain resource allocation (TDRA) for both the downlink channel and the uplink channel.

21. The UE according to claim 20, wherein: The TDRA starts at a symbol offset after reception of the DCI message.

22. The UE according to claim 15, wherein: The one or more common fields include 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.

23. The UE according to claim 15, wherein: The one or more common fields include a joint transmission configuration indication (TCI) indication.

24. The UE according to claim 23, wherein: Each of the one or more TCI states has a quasi co-location (QCL) for the downlink channel, and a QCL for the uplink channel or a sounding reference signal (SRS) resource indicator (SRI) for the uplink channel.

25. The UE according to claim 15, wherein: The one or more common fields include at least one of the following: mapping of virtual resource blocks (VRBs) associated with the downlink channel and the uplink channel to physical resource blocks (PRBs); Initializing a DMRS sequence associated with a first demodulation reference signal (DMRS) of the downlink channel and a second DMRS of the uplink channel; a joint demodulation reference signal (DMRS) port indication table identifying a port for each of the downlink channel and the uplink channel; or A joint field of both sounding reference signal (SRS) resources and channel station information (CSI) reference signal (RS) resources is triggered on the same OFDM symbol or symbols.

26. The UE according to claim 15, wherein: Receiving the DCI message from the network entity via the transceiver further comprises: receiving, via the transceiver, a first part of the DCI message from the network entity, the first part including information indicating a location of a second part of the DCI message, wherein the second part of the DCI message includes remaining information not included in the first part of the DCI message; and The second part of the DCI message is received from the network entity via the transceiver based on the first part of the DCI message.

27. The UE according to claim 26, wherein: The first part of the DCI message includes one or more common fields for downlink channel allocation and uplink channel allocation, wherein the one or more common fields include at least one of the following: time domain resource allocation (TDRA), frequency domain resource assignment (FDRA), sounding reference signal (SRS) request and channel station information (CSI) request.

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

Images