Scheduling single downlink control information (DCI) message for both downlink and uplink communications in full duplex network

Abstract

A method for wireless communication by a user equipment (UE) includes receiving downlink control information (DCI) including an uplink grant and a downlink grant. The DCI indicates a time domain resource allocation (TDRA) and a frequency domain resource allocation (FDRA). The method also includes determining whether the DCI is a unidirectional DCI or a bidirectional DCI based on whether the FDRA is directed to an uplink subband and / or a downlink subband. The method also includes communicating according to the DCI.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Patent Application No. 18 / 073,315, filed on December 1, 2022, entitled “SINGLE DOWNLINK CONTROLINFORMATION (DCI) MESSAGE SCHEDULING BOTH DOWNLINK AND UPLINK COMMUNICATIONS IN FULL-DUPLEX NETWORKS,” which claims priority to U.S. Patent Application No. 18 / 073,315, filed on July 15, 2022, entitled “SINGLE DOWNLINK CONTROL INFORMATION (DCI) SCHEDULING BOTH DOWNLINK AND UPLINK COMMUNICATIONS IN FULL-DUPLEX NETWORKS,” which claims priority to U.S. Patent Application No. 18 / 073,315, filed on December 1, 2022, entitled “SINGLE DOWNLINK CONTROL INFORMATION (DCI) SCHEDULING BOTH DOWNLINK AND UPLINK COMMUNICATIONS IN FULL-DUPLEX NETWORKS (SINGLE DOWNLINK CONTROL INFORMATION (DCI) SCHEDULING BOTH DOWNLINK AND UPLINK COMMUNICATIONS IN FULL-DUPLEX NETWORKS)), the disclosures of which are expressly incorporated herein by reference in their entirety. Technical Field

[0003] The present disclosure relates generally to wireless communications, and more particularly to a single downlink control information (DCI) message that schedules both downlink and uplink communications in a full-duplex network. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may 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) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at city, national, regional, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continued 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). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies.

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

[0007] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects, and is neither intended to identify key or important elements of all aspects, nor to describe 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 a more detailed description presented later.

[0008] An example implementation includes a wireless communication method, the method comprising: sending, by a user equipment (UE) a radio resource control (RRC) configuration message indicating the full-duplex capability of the UE to a network entity; receiving, by the UE, a downlink control information (DCI) format message from the network entity, wherein the DCI format message enables the UE to concurrently send uplink channels and receive downlink channels 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.

[0009] In various aspects of the present disclosure, a method for wireless communication by a user equipment (UE) includes: receiving downlink control information (DCI) including an uplink grant and a downlink grant. The DCI indicates a time domain resource allocation (TDRA) and a frequency domain resource allocation (FDRA). The method also includes determining whether the DCI is a unidirectional DCI or a bidirectional DCI based on whether the FDRA points to an uplink subband and / or a downlink subband. The method also includes communicating according to the DCI.

[0010] In other aspects of the present disclosure, a method for wireless communication by a network component includes: sending downlink control information (DCI) including an uplink grant and a downlink grant. The DCI indicates a time domain resource allocation (TDRA) and a frequency domain resource allocation (FDRA). The DCI indicates whether the DCI is a unidirectional DCI or a bidirectional DCI based on whether the FDRA points to an uplink subband and / or a downlink subband. The method also includes communicating according to the DCI.

[0011] Other aspects of the present disclosure relate to a device. The device has a memory and one or more processors coupled to the memory. The processor is configured to receive downlink control information (DCI) including uplink grant and downlink grant. The DCI indicates time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA). The processor is also configured to determine whether the DCI is unidirectional DCI or bidirectional DCI based on whether the FDRA points to an uplink subband and / or a downlink subband. The processor is also configured to communicate according to the DCI.

[0012] Other aspects of the present disclosure relate to a device having a memory and one or more processors coupled to the memory. The processor is configured to send downlink control information (DCI) including uplink grants and downlink grants. The DCI indicates time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA). The DCI indicates whether the DCI is unidirectional DCI or bidirectional DCI based on whether the FDRA points to an uplink subband and / or a downlink subband. The processor is also configured to communicate according to the DCI.

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

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

[0015] Figure 2A , Figure 2B , Figure 2C and Figure 2D Schematic diagrams illustrating examples of a first 5G / NR frame, a downlink (DL) channel within a fifth generation / new radio (5G / NR) subframe, a second 5G / NR frame, and an uplink (UL) channel within a 5G / NR subframe, respectively.

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

[0017] Figure 4 is a diagram illustrating a full-duplex communication mode.

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

[0019] Figure 6 is a diagram illustrating a full-duplex communication mode.

[0020] Fig. 7A is a block diagram illustrating a type zero frequency domain resource allocation (FDRA) in accordance with various aspects of the present disclosure.

[0021] Figure 7B is a block diagram illustrating a type one frequency domain resource allocation (FDRA) according to various aspects of the present disclosure.

[0022] FIG. 8A to FIG. 8C is a block diagram illustrating intra-slot time domain resource allocation (TDRA) according to various aspects of the present disclosure.

[0023] FIG. 9A to FIG. 9B is a block diagram illustrating inter-slot time domain resource allocation (TDRA) according to various aspects of the present disclosure.

[0024] Fig.10 is a flow chart illustrating an example process performed, for example, by a user equipment (UE) according to various aspects of the present disclosure.

[0025] Fig.11 is a flow chart illustrating an example process, for example, performed by a network device, according to various aspects of the present disclosure. DETAILED DESCRIPTION

[0026] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, it is apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid blurring these concepts.

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

[0028] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic components, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present 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, executable files, threads of execution, procedures, functions, etc., whether it is expressed in software, firmware, middleware, microcode, hardware description languages, or other terms.

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

[0030] In conventional systems, a base station can schedule user equipment (UE) for downlink (DL) communication and uplink (UL) communication using a separate downlink control information (DCI) message. Combining two DCI messages into one DCI message in a half-duplex network may cause problems due to independent parameters for each direction (e.g., DL direction and UL direction). However, in a full-duplex network, DL grants and UL grants can share many parameters, which makes the merging of two DCI messages more reasonable. Therefore, one DCI can schedule both DL communication and UL communication in overlapping resources. However, for a half-duplex UE, a DCI can schedule DL grants and UL grants with fields that can be interpreted based on sub-bands. Various aspects of the present disclosure introduce DCI messages for scheduling DL communication and UL communication for full-duplex UEs in a full-duplex network.

[0031] In some aspects of the present disclosure, a base station may transmit a DCI message that schedules both a DL grant and an UL grant for the same UE. When using an existing DL scheduling DCI or UL scheduling DCI, the UE may determine from the frequency domain resource assignment (FDRA) field whether it is unidirectional scheduling or bidirectional scheduling. For example, if the FDRA points to a frequency allocation contained in a DL subband or a UL subband, the UE determines that the DCI is used for unidirectional scheduling. If the FDRA points to a frequency allocation contained in both a DL subband and a UL subband, the UE determines that the DCI is a DL and UL scheduling DCI. Alternatively or additionally, different radio network temporary identifiers (RNTIs) may be dedicated to scheduling DCI for both DL and UL. That is, the DCI for scheduling DL or UL may have a cell RNTI (C-RNTI), and the DCI for scheduling both DL and UL may have a separate RNTI. In other aspects, a new DCI may be introduced for scheduling both DL transmissions and UL transmissions.

[0032] In various aspects of the present disclosure, the FDRA field in the scheduling DCI can indicate DL, UL, or both based on the coverage in the DL subband and the UL subband. For example, a type zero FDRA includes a bitmap with nine or 18 bits (which can be configured by the radio resource control (RRC)). Each bit in the bitmap with a value of '1' is allocated. If the allocation corresponds to a resource block group (RBG) in the DL subband, the bit is for the allocation of the physical downlink shared channel (PDSCH), and if the bit corresponds to an RBG in the UL subband, the bit is for the allocation of the physical uplink shared channel (PUSCH). For type one FDRA, a resource indicator value (RIV) indication can be used in a similar manner so that the indicated bandwidth is divided between PDSCH and PUSCH based on the subband to which the RIV belongs.

[0033] For time domain resource allocation (TDRA), the UE may be configured with a single DCI in a time slot for scheduling DL transmission and UL transmission. In some aspects, the TDRA field may point to a row in an RRC configuration table that lists possible time domain resource allocations for both DL and UL. In other aspects, a single start and length indicator value (SLIV) indicates both DL allocation and UL allocation. More specifically, the UE may be configured by the RRC with a mapping between SLIVs that specifies which portion is allocated for DL ​​and which portion is allocated for UL. In each of these aspects, the UE may apply a guard time between the reception of DL and the transmission of UL. In yet other aspects, the bits describing the SLIV indication are divided into two fields for two SLIV values. The first field is used for DL, and the second field is used for UL.

[0034] The UE may be configured with a single DCI between time slots that schedules DL transmissions and UL transmissions. In the case of inter-time slot scheduling (e.g., multiple time slots), in some aspects, the TDRA for DL ​​and for UL are the same. In these aspects, TDRA is provided by the scheduling DCI. In other aspects, the TDRA field in the scheduling DCI indicates the TDRA for DL ​​and UL via the RRC configuration mapping between the bit in the TDRA field and the TDRA for DL ​​and the TDRA for UL. In other words, there are two separate fields: the uplink field and the downlink field.

[0035] Aspects of the present disclosure also address other fields in the DCI. For example, the UE may be configured by RRC with a mapping from a DCI field and corresponding DL parameters and UL parameters. In one example, a modulation and coding scheme (MCS) parameter is indicated by five bits. The indicated MCS may be a DL MCS, where the UL MCS is obtained via an offset from the DL MCS configured by RRC. The reference parameters may be defined, for example, by an RRC configuration. In other specific implementations, the five-bit indication points to a pair of DL MCS and UL MCS, which may be configured by RRC. In some further specific implementations, the pair of MCS parameters may be a function of TDRA, FDRA, and possibly other parameters.

[0036] 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 and half-duplex user equipment (UE) in fifth generation new radio (5G NR). The wireless communication system (which is also referred to 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)).

[0037] In certain aspects, the UE 104 may be configured to operate the communication component 198 and / or the configuration component 240 to receive downlink control information (DCI) including an uplink grant and a downlink grant. The DCI indicates a time domain resource allocation (TDRA) and a frequency domain resource allocation (FDRA). The UE 104 may also be configured to determine whether the DCI is a unidirectional DCI or a bidirectional DCI based on whether the FDRA points to an uplink subband and / or a downlink subband. The UE 104 communicates according to the DCI.

[0038] Accordingly, in certain aspects, a network entity (e.g., base station 102) and / or another UE (such as UE 104) can be configured to operate communication component 199 and / or configuration component 241 to send downlink control information (DCI) including uplink grant and downlink grant, the DCI indicating time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA), the DCI indicating whether the DCI is unidirectional DCI or bidirectional DCI based on whether the FDRA points to an uplink subband and / or a downlink subband. The network entity communicates according to the DCI.

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

[0040] The base station 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 the EPC 160 via a backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5GNR (collectively referred to as the Next Generation RAN (NG-RAN)) can interface with the core network 190 via a backhaul link 184. Among other functions, the base station 102 can perform one or more of the following functions: 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 setup 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 warning messages. Base stations 102 may communicate with each other directly or indirectly (eg, through EPC 160 or core network 190) via backhaul links 134 (eg, X2 interfaces). Backhaul links 132, 134, and 184 may be wired or wireless.

[0041] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). A communication link 120 between base station 102 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through 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 can use a spectrum of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) bandwidth. The 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 for DL ​​compared to UL). The component carrier 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 carrier may be referred to as a secondary cell (SCell).

[0042] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 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 performed 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.

[0043] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. 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 prior to communication.

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

[0045] The base station 102, whether a small cell 102' or a large cell (e.g., a macro base station), may include an eNB, a gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near mmW frequencies to communicate with the UE 104. When the gNB 180 operates at mmW or near mmW frequencies, the gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is part of the radio frequency (RF) of the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz with a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW can extend down to a frequency of 3 GHz with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands (e.g., 3 GHz to 300 GHz) have extremely high path loss and a shorter 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.

[0046] 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 may be different. The transmit direction and receive direction of UE 104 may be the same or may be different.

[0047] The 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. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are passed through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 may provide UE Internet Protocol (IP) address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a packet switched (PS) streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service configuration and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services in a public land mobile network (PLMN), and may be used to schedule MBMS delivery. The MBMS Gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area broadcasting a specific service, and may be responsible for session management (start / stop) and collecting eMBMS related billing information.

[0048] 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 communicate 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. In general, the AMF 192 provides quality of service (QoS) flows 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 an IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services.

[0049] A base station may also be referred to as a gNB, a Node B, an evolved Node B (eNB), an access point, a transceiver base station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other suitable term. Base station 102 provides an access point to EPC 160 or core network 190 for UE 104. Examples of UE 104 include a cellular phone, a smart phone, 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, 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 of UE 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, 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.

[0050] FIG. 2A to FIG. 2D Included are diagrams of example frame structures and resources that may be utilized in communications between base stations 102, UEs 104, and / or secondary UEs (or sidelink UEs) 110 as described in the present disclosure. Figure 2A 200 is a diagram illustrating an example of a first subframe within a 5G / NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G / NR subframe. Figure 2C 250 is a diagram illustrating an example of a second subframe within a 5G / NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of an UL channel within a 5G / NR subframe. The 5G / NR frame structure can be frequency division duplex (FDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), a subframe within the subcarrier set is dedicated to either DL or UL), or can be time division duplex (TDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), a subframe within the subcarrier set is dedicated to both DL and UL). Figure 2A and Figure 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 may be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The slot format is configured for the UE by a received slot format indicator (SFI) (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling). Note that the following description also applies to the 5G / NR frame structure for TDD.

[0051] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10ms) can be divided into 10 subframes of the same size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, 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, and for time slot configuration 1, each time slot may include 7 symbols. The symbol on the DL may be a cyclic prefix (CP) OFDM (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots in a subframe is based on the time slot configuration and parameter set (numerology). For slot configuration 0, different parameter sets μ0 to 5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and parameter set μ, there are 14 symbols per slot and 2 per subframe. μ time slots. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 5. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=5 is 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2DAn example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ=0 with 1 slot per subframe. The subcarrier spacing is 15 kHz and the symbol duration is about 66.7 μs.

[0052] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0053] like Figure 2A As illustrated in FIG. 1 , some REs carry reference (pilot) signals (RS) for UEs. RSs may include demodulation RSs (DM-RSs) for channel estimation at the UE (indicated as R for a particular configuration). x , where 100x is the port number, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS). RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0054] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol. The primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of the frame. The PSS is used by UE 104 to determine the subframe / symbol timing and the physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identification group number and the radio frame timing. Based on the physical layer identification and the physical layer cell identification 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 system frame number (SFN) and the number of RBs in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information such as System Information Blocks (SIBs) not sent through the PBCH, and paging messages.

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

[0056] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as 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) acknowledgement / negative acknowledgement (ACK / NACK) feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0057] Figure 33 is a block diagram of a base station 310 and a UE 350 in communication in an access network, where the base station 310 may be an example implementation of the base station 102, and where the UE 350 may be an example implementation of the UE 104. In the DL, IP packets from the EPC 160 may be provided to the controller / processor 375. The 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 (encryption, decryption, 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), re-segmentation 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.

[0058] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to 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-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Subsequently, each stream can be mapped to an OFDM subcarrier, each stream can be multiplexed with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and each stream can then be combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel state feedback sent 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.

[0059] At the UE 350, each receiver 354RX receives a signal through 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 can 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 can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then transforms 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 and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0060] 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, decryption, 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 an ACK and / or NACK protocol to support HARQ operations.

[0061] Similar to the functions 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 (encryption, decryption, 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 of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0062] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 to select appropriate coding and modulation schemes 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.

[0063] 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 a RX processor 370.

[0064] 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 channels and logical channels, packet reassembly, decryption, header decompression, 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.

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

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

[0067] Currently, when scheduling information for uplink channels and downlink channels, two separate DCI format messages are used. DCI format 1_1 schedules information for downlink channels. In an example, DCI format 1_1 includes fields for the following: frequency domain resource assignment (FDRA), frequency domain assignment type (type zero / one), time domain resource allocation (TDRA), pre-decoded resource block group (PRG) bundling indicator, VRB-2-PRB mapping indicator, carrier indicator, rate matching indicator, zero power (ZP) CSI-RS trigger, TCI-state indication, bandwidth part (BWP) indicator, MCS, new data indicator (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, demodulated reference signal (DMRS) sequence initialization.

[0068] DCI format 0_1 ​​schedules information for uplink channels. In an example, DCI format 0_1 ​​includes fields for: carrier indicator, bandwidth part indicator, frequency domain resource assignment, time domain resource assignment, frequency hopping flag, modulation and coding scheme, new data indicator, redundancy version, HARQ process number, TPC command for scheduled PUSCH, UL / supplementary uplink (SUL) indicator, SRS resource indicator, precoding information and number of layers, antenna port, SRS request, CSI request, CBG transmission information (CBGTI), phase tracking reference signal (PTRS_-DMRS association, beta_offset indicator, DMRS sequence initialization, and UL shared channel (SCH) indicator.

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

[0070] refer to Figures 4 to 6 , the described features generally relate to downlink and uplink data downlink control information (DCI) triggering for full-duplex and half-duplex UEs in fifth generation new radio (5G NR). Figure 4 is a diagram 400 illustrating a full-duplex communication mode. For example, scenario 410 depicts a full-duplex base station and half-duplex UEs 1 and UE 2. In scenario 410, a full-duplex first gNB may transmit to UE1 on a downlink channel and receive from UE2 on an uplink channel. However, UE2 may cause interference to UE1 due to uplink transmissions to the first gNB. Furthermore, the second gNB may cause interference to the first gNB due to communications with both UE1 and UE2. Additionally, the first gNB may cause self-interference from both downlink communications and uplink communications.

[0071] 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 a first gNB, from UE 2 receiving downlink communications from a second gNB, and from downlink communications from the second gNB.

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

[0073] Figure 55 is a diagram illustrating a half-duplex communication mode. For example, scenario 510 depicts a transmit receive point 1 (TRP1) configured in a full-duplex mode with a half-duplexed UE. Accordingly, diagram 520 depicts a subframe / slot decomposition of 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 / slot for different UEs can be configured. The UE can change the uplink transmission and / or downlink reception bandwidth portion between time slots with zero latency. The UE can use full reciprocity (e.g., full duplex) to send a sounding reference signal (SRS) to cover the entire downlink bandwidth portion, and use partial reciprocity (e.g., half-duplex) to send a sounding reference signal (SRS) to cover a portion of the downlink bandwidth. In this example, the dotted line of diagram 520 depicts the subframe / time slot breakdown for a full-duplex TRP1 and a half-duplex UE.

[0074] Figure 6 600 is an illustration of a full-duplex communication mode. For example, scenario 610 depicts configuring TRP1 in a full-duplex mode with a full-duplex UE and a half-duplex 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 grants and downlink grants. The UE can change the uplink transmission and / or downlink reception bandwidth portion between each time slot with zero delay. The UE can use full reciprocity (e.g., full duplex) to send SRS to cover the entire downlink bandwidth portion, and use partial reciprocity (e.g., half-duplex) to send SRS to cover a portion of the downlink bandwidth. In this example, the dotted line of diagram 620 depicts the subframe / time slot breakdown for a full-duplex TRP1 and a half-duplex UE.

[0075] In conventional systems, a base station can schedule user equipment (UE) for downlink (DL) communication and uplink (UL) communication using a separate downlink control information (DCI) message. Combining two DCI messages into one DCI message in a half-duplex network may cause problems due to independent parameters for each direction (e.g., DL direction and UL direction). However, in a full-duplex network, DL grants and UL grants can share many parameters, which makes the merging of two DCI messages more reasonable. Therefore, one DCI can schedule both DL communication and UL communication in overlapping resources. However, for half-duplex UEs, DCI can schedule DL grants and UL grants with fields that can be interpreted based on sub-bands. Various aspects of the present disclosure introduce DCI messages for scheduling DL and UL communications for full-duplex and half-duplex UEs in a full-duplex network.

[0076] In some aspects of the present disclosure, a base station may transmit a DCI message that schedules both a DL grant and an UL grant for the same UE. When using an existing DL scheduling DCI or UL scheduling DCI, the UE may determine from the frequency domain resource assignment (FDRA) field whether it is unidirectional scheduling or bidirectional scheduling. For example, if the FDRA points to a frequency allocation contained in a DL subband or a UL subband, the UE determines that the DCI is for unidirectional scheduling. If the FDRA points to a frequency allocation contained in both a DL subband and a UL subband, the UE determines that the DCI is a DL and UL scheduling DCI. Alternatively or additionally, different radio network temporary identifiers (RNTIs) may be dedicated to scheduling DCI for both DL and UL. In other aspects, a new DCI may be introduced for scheduling both DL transmissions and UL transmissions.

[0077] In other aspects of the present disclosure, the FDRA field in the scheduling DCI can indicate DL, UL, or both based on the coverage in the DL subband and the UL subband. For example, a type zero FDRA includes a bitmap with nine or 18 bits (which can be configured by the radio resource control (RRC)). Each bit in the bitmap with a value of '1' is allocated. If the allocation corresponds to a resource block group (RBG) in the DL subband, the bit is an allocation for the physical downlink shared channel (PDSCH), and if the bit corresponds to an RBG in the UL subband, the bit is an allocation for the physical uplink shared channel (PUSCH).

[0078] Fig. 7A is a block diagram illustrating a type zero frequency domain resource allocation (FDRA) 700 in accordance with various aspects of the present disclosure. Fig. 7A In the example of , the type-zero FDRA 700 includes nine bits corresponding to the RBGs in the active BWP: four bits for PUSCH, and five bits for PDSCH. Fig. 7AThe type-zero FDRA 700 in the example of corresponds to scheduling in both the uplink (UL) sub-band 702 and the downlink (DL) sub-band 704.

[0079] For type one FDRA, a resource indicator value (RIV) indication may be used in a similar manner so that the indicated bandwidth is split between PDSCH and PUSCH based on the subband to which the RIV belongs. The RIV indicates the start position and length of the allocation.

[0080] Figure 7B is a block diagram illustrating a type one frequency domain resource allocation (FDRA) 750 according to various aspects of the present disclosure. Figure 7B In the example of FIG. 7 , type one FDRA 750 includes RIVs corresponding to PUSCH and PDSCH in the active BWP. Figure 7B Type one FDRA 750 in the example of FIG. 7 corresponds to scheduling in both uplink (UL) subband 752 and downlink (DL) subband 754 .

[0081] For time domain resource allocation (TDRA), the UE may be configured with a single DCI in a time slot for scheduling DL transmission and UL transmission. In some aspects, the TDRA field may point to a row in an RRC configuration table that lists possible time domain resource allocations for both DL and UL. In other aspects, a single start and length indicator value (SLIV) indicates both DL allocation and UL allocation. More specifically, the UE may be configured by the RRC with a mapping between SLIVs that specifies which portion is allocated for DL ​​and which portion is allocated for UL. In each of these aspects, the UE may apply a guard time between the reception of DL and the transmission of UL. In yet other aspects, the bits describing the SLIV indication are divided into two fields for two SLIV values. The first field is used for DL, and the second field is used for UL.

[0082] FIG. 8A to FIG. 8C is a block diagram illustrating time domain resource allocation (TDRA) within a time slot according to various aspects of the present disclosure. Fig. 8A In FIG. 8 , the first TDRA 800 for uplink subband 802 and downlink subband 804 allocates more symbols for PDSCH than PUSCH. Note that there is a gap after PDSCH is completed before PUSCH starts. Figure 8B In , the second TDRA 850 for uplink subband 852 and downlink subband 854 allocates more symbols for PUSCH than PDSCH. Note that there is a gap after PDSCH is finished before PUSCH starts. Figure 8CIn , the third TDRA 880 for uplink subband 882 and downlink subband 884 allocates symbols for PDSCH and PUSCH. Figure 8C In this example, PDSCH and PUSCH allocations overlap in time.

[0083] The UE may be configured with a single DCI between time slots that schedules DL transmissions and UL transmissions. In the case of inter-time slot scheduling (e.g., multiple time slots), in some aspects, the TDRA for DL ​​and for UL are the same. In these aspects, TDRA is provided by the scheduling DCI. In other aspects, the TDRA field in the scheduling DCI indicates the TDRA for DL ​​and UL via the RRC configuration mapping between the bit in the TDRA field and the TDRA for DL ​​and the TDRA for UL. In other words, there are two separate fields: the uplink field and the downlink field.

[0084] FIG. 9A to FIG. 9B is a block diagram illustrating inter-slot time domain resource allocation (TDRA) according to various aspects of the present disclosure. Fig. 9A In the example of FIG. 1 , a first TDRA 900 for a first downlink subband 902, a first uplink subband 904, and a second downlink subband 906 allocates the same number of symbols for uplink and downlink communications. The first TDRA 900 allocates a PDSCH in a first time slot 910 and a PUSCH in a second time slot 920. Fig. 9B In the example of FIG. 1 , a second TDRA 950 for a first downlink subband 952, a first uplink subband 954, and a second downlink subband 956 allocates symbols for a PDSCH in a first time slot 970. The second TDRA 950 allocates symbols for a PUSCH in a second time slot 980. The second time slot 980 includes a second uplink subband 958 of a different size than the first uplink subband 954. Fig. 9B In the example of 950, the TDRA for DL ​​and UL is indicated via a bit in the TDRA field and an RRC configuration mapping between the TDRA for DL ​​and the TDRA for UL. In other words, there are two separate fields: an uplink field and a downlink field.

[0085] Aspects of the present disclosure also address other fields in the DCI. For example, the UE may be configured by RRC with a mapping from a DCI field and corresponding DL parameters and UL parameters. In one example, a modulation and coding scheme (MCS) parameter is indicated by five bits. The indicated MCS may be a DL MCS, where the UL MCS is obtained via an offset from the DL MCS configured by RRC. The reference parameter may be defined, for example, by an RRC configuration. In other specific implementations, the five-bit indication points to a pair of DL MCS and UL MCS, which may be configured by RRC. In some further specific implementations, the pair of MCS parameters may be a function of TDRA, FDRA, and possibly other parameters.

[0086] Fig.10 1 is a flow chart illustrating an example process 1000 performed, for example, by a user equipment (UE) in accordance with various aspects of the present disclosure. Example process 1000 is an example of a single downlink control information (DCI) message that schedules both downlink and uplink communications in a full-duplex network. The operations of process 1000 may be implemented by a UE 350.

[0087] At block 1002, a user equipment (UE) receives downlink control information (DCI) including an uplink grant and a downlink grant. The DCI indicates a time domain resource allocation (TDRA) and a frequency domain resource allocation (FDRA). For example, a UE (e.g., using an antenna 352, a receiver 354, a receive processor 356, a controller / processor 359, a communication component 198, a memory 360, etc.) may receive the DCI. The UE may decode the DCI based on a radio network temporary identifier (RNTI) dedicated to both uplink scheduling and downlink scheduling. In some aspects, the FDRA includes a type zero FDRA having a bitmap, and determining further includes: when the value of any bit in the bitmap corresponds to any resource block group (RBG) in a downlink subband, determining that the FDRA is used for a physical downlink shared channel (PDSCH), and when the value of any bit in the bitmap corresponds to any RBG in an uplink subband, determining that the FDRA is used for a physical uplink shared channel (PUSCH). In other aspects, the FDRA includes a type-one FDRA having a resource indicator value (RIV), and the determination further includes: when the RIV corresponds to any resource block group (RBG) in the downlink subband, determining that the FDRA is used for a physical downlink shared channel (PDSCH), and when the RIV corresponds to any RBG in the uplink subband, determining that the FDRA is used for a physical uplink shared channel (PUSCH). The DCI can be used to schedule uplink and downlink in the same time slot. In some specific implementations, the TDRA points to a row in a radio resource control (RRC) configuration table, which includes a potential first TDRA for the uplink and a potential second TDRA for the downlink. In other specific implementations, the TDRA includes a start and length indication value (SLIV) for the uplink and for the downlink, and the method also includes receiving a mapping between the SLIV, the downlink allocation, and the uplink allocation.

[0088] A guard time may be applied between receiving a physical downlink shared channel (PDSCH) and transmitting a physical uplink shared channel (PUSCH). TDRA may include a start and length indicator value (SLIV) having an uplink bit in a first field and a downlink bit in a second field. DCI may also be used to schedule uplink and downlink in multiple time slots. In these specific implementations, TDRA may include a first TDRA for a downlink, which is identical to a second TDRA for an uplink. TDRA may include a bit mapped to an uplink TDRA and a bit mapped to a downlink TDRA.

[0089] At block 1004, the user equipment (UE) determines whether the DCI is a unidirectional DCI or a bidirectional DCI based on whether the FDRA points to an uplink subband and / or a downlink subband. For example, the UE (e.g., using a controller / processor 359, a memory 360, etc.) can determine whether the DCI is a unidirectional DCI or a bidirectional DCI. In some specific implementations, the UE may receive a first mapping between an uplink parameter and a field of the DCI, and a second mapping between a downlink parameter and a field of the DCI. The UE may also receive an offset for a configuration of one of the uplink parameters relative to a reference parameter, the offset and the reference parameter indicating one of the downlink parameters and one of the uplink parameters. The UE may receive a configuration for a pair of uplink parameters and downlink parameters, to which the DCI points. The uplink parameters and downlink parameters may be functions of the FDRA and TDRA.

[0090] At block 1006, the user equipment (UE) communicates in accordance with the DCI. For example, the UE (e.g., using antenna 352, receiver 354, receive processor 356, transmitter 354, transmit processor 368, controller / processor 359, communication component 198, memory 360, etc.) may communicate in accordance with the DCI.

[0091] Fig.11 1 is a flow chart illustrating an example process 1100 performed, for example, by a network device, in accordance with various aspects of the present disclosure. The example process 1100 is an example of a single downlink control information (DCI) that schedules both downlink and uplink in a full-duplex network. The operations of process 1100 may be implemented by a network component, such as a base station 310 or a component of a base station.

[0092] At block 1102, the network component sends downlink control information (DCI) including an uplink grant and a downlink grant. The DCI indicates a time domain resource allocation (TDRA) and a frequency domain resource allocation (FDRA). The DCI indicates whether the DCI is a unidirectional DCI or a bidirectional DCI based on whether the FDRA points to an uplink subband and / or a downlink subband. For example, a base station (e.g., using an antenna 320, a transmitter 318, a transmit processor 316, a controller / processor 375, a communication component 199, a memory 376, etc.) can send the DCI. The network component can encode the DCI based on a radio network temporary identifier (RNTI) dedicated to both uplink scheduling and downlink scheduling. In some aspects, the FDRA includes a type zero FDRA with a bitmap, and the DCI indicates that when the value of any bit in the bitmap corresponds to any resource block group (RBG) in the downlink subband, the FDRA is used for a physical downlink shared channel (PDSCH), and when the value of any bit in the bitmap corresponds to any RBG in the uplink subband, the FDRA is used for a physical uplink shared channel (PUSCH). In other aspects, the FDRA includes a type one FDRA with a resource indicator value (RIV), and the DCI indicates that when the RIV corresponds to any resource block group (RBG) in the downlink subband, the FDRA is used for a physical downlink shared channel (PDSCH), and when the RIV corresponds to any RBG in the uplink subband, the FDRA is used for a physical uplink shared channel (PUSCH). The DCI can be used to schedule uplink and downlink in the same time slot. In some specific implementations, the TDRA points to a row in a radio resource control (RRC) configuration table, which includes a potential first TDRA for an uplink and a potential second TDRA for a downlink. In other specific implementations, the TDRA includes a start and length indicator value (SLIV) for the uplink and for the downlink, and the method further includes sending a mapping between the SLIV, the downlink allocation, and the uplink allocation.

[0093] The network component can configure the guard time between receiving the physical downlink shared channel (PDSCH) and sending the physical uplink shared channel (PUSCH). The TDRA includes a start and length indicator value (SLIV) having an uplink bit in a first field and a downlink bit in a second field. In some aspects, the DCI is used to schedule uplink and downlink in multiple time slots. In these aspects, the TDRA may include a first TDRA for the downlink, which is the same as the second TDRA for the uplink. The TDRA may also include a bit mapped to the uplink TDRA and a bit mapped to the downlink TDRA. The network component may send a first mapping between the uplink parameter and the field of the DCI, and a second mapping between the downlink parameter and the field of the DCI. The network component may also send an offset for the configuration of one of the uplink parameters relative to the reference parameter, and the offset and the reference parameter indicate one of the downlink parameters and one of the uplink parameters. The network component may also send a configuration for a pair of uplink parameters and downlink parameters, and the DCI points to the configuration. The uplink parameters and downlink parameters may be a function of FDRA and TDRA.

[0094] At block 1104, the network components communicate in accordance with the DCI. For example, a base station (e.g., using antenna 320, receiver 318, receive processor 370, transmitter 318, transmit processor 316, controller / processor 375, communication component 199, memory 376, etc.) may communicate in accordance with the DCI.

[0095] Example aspects

[0096] Aspect 1: A method for wireless communication by a user equipment (UE), the method comprising: receiving downlink control information (DCI) including an uplink grant and a downlink grant, the DCI indicating a time domain resource allocation (TDRA) and a frequency domain resource allocation (FDRA); determining whether the DCI is a unidirectional DCI or a bidirectional DCI based on whether the FDRA points to an uplink subband and / or a downlink subband; and communicating according to the DCI.

[0097] Aspect 2: The method according to aspect 1, further comprising: when both uplink communication and downlink communication are scheduled, decoding the DCI based on a first radio network temporary identifier (RNTI) dedicated to the DCI.

[0098] Aspect 3: A method according to Aspect 1 or 2, wherein the FDRA includes a type zero FDRA having a bitmap, and the determination further includes: when the value of any bit in the bitmap corresponds to any resource block group (RBG) in the downlink subband, determining that the FDRA is used for the physical downlink shared channel (PDSCH), and when the value of any bit in the bitmap corresponds to any RBG in the uplink subband, determining that the FDRA is used for the physical uplink shared channel (PUSCH).

[0099] Aspect 4: A method according to Aspect 1 or 2, wherein the FDRA includes a type 1 FDRA having a resource indicator value (RIV), and the determination further includes: when the RIV corresponds to any resource block group (RBG) in the downlink subband, determining that the FDRA is used for a physical downlink shared channel (PDSCH), and when the RIV corresponds to any RBG in the uplink subband, determining that the FDRA is used for a physical uplink shared channel (PUSCH).

[0100] Aspect 5: The method according to any one of the preceding aspects, wherein the DCI is used to schedule uplink and downlink in the same time slot.

[0101] Aspect 6: A method according to any of the preceding aspects, wherein the TDRA points to a row in a radio resource control (RRC) configuration table, the radio resource control (RRC) configuration table including a potential first TDRA for uplink and a potential second TDRA for downlink.

[0102] Aspect 7: A method according to any one of the preceding aspects, wherein the TDRA includes a start and length indication value (SLIV) for uplink and for downlink, and the method further includes receiving a mapping between the SLIV, downlink allocation and uplink allocation.

[0103] Aspect 8: The method according to any one of the preceding aspects, further comprising: applying a guard time between receiving a physical downlink shared channel (PDSCH) and sending a physical uplink shared channel (PUSCH).

[0104] Aspect 9: A method according to any of the preceding aspects, wherein the TDRA includes a start and length indication value (SLIV), the start and length indication value (SLIV) having an uplink bit in a first field and a downlink bit in a second field.

[0105] Aspect 10: The method according to any one of the preceding aspects, wherein the DCI is used to schedule uplink and downlink in multiple time slots.

[0106] Aspect 11: The method according to any one of the preceding aspects, wherein the TDRA comprises a first TDRA for a downlink, the first TDRA being the same as a second TDRA for an uplink.

[0107] Aspect 12: The method according to any one of aspects 1 to 10, wherein the TDRA includes a bit mapped to an uplink TDRA and a bit mapped to a downlink TDRA.

[0108] Aspect 13: The method according to any one of the preceding aspects, further comprising: receiving a first mapping between uplink parameters and fields of the DCI, and a second mapping between downlink parameters and fields of the DCI.

[0109] Aspect 14: The method according to any one of the preceding aspects further comprises: receiving an offset for the configuration of one of the uplink parameters relative to a reference parameter, the offset and the reference parameter indicating one of the downlink parameters and one of the uplink parameters.

[0110] Aspect 15: The method according to any one of the preceding aspects, further comprising: receiving a configuration for a pair of uplink parameters and downlink parameters, the DCI pointing to the configuration.

[0111] Aspect 16: The method according to any of the preceding aspects, wherein uplink parameters and downlink parameters are functions of the FDRA and the TDRA.

[0112] Aspect 17: A method for wireless communication by a network component, the method comprising: sending downlink control information (DCI) including an uplink grant and a downlink grant, the DCI indicating a time domain resource allocation (TDRA) and a frequency domain resource allocation (FDRA), the DCI indicating whether the DCI is a unidirectional DCI or a bidirectional DCI based on whether the FDRA points to an uplink subband and / or a downlink subband; and communicating according to the DCI.

[0113] Aspect 18: The method according to aspect 17, the method further comprising: when scheduling both uplink communication and downlink communication, encoding the DCI based on a first radio network temporary identifier (RNTI) dedicated to the DCI.

[0114] Aspect 19: A method according to Aspect 17 or 18, wherein the FDRA includes a type zero FDRA having a bitmap, and the DCI indicates: when the value of any bit in the bitmap corresponds to any resource block group (RBG) in the downlink subband, the FDRA is used for the physical downlink shared channel (PDSCH), and when the value of any bit in the bitmap corresponds to any RBG in the uplink subband, the FDRA is used for the physical uplink shared channel (PUSCH).

[0115] Aspect 20: A method according to Aspect 17 or 18, wherein the FDRA includes a type-one FDRA having a resource indicator value (RIV), and the DCI indicates that when the RIV corresponds to any resource block group (RBG) in the downlink subband, the FDRA is used for a physical downlink shared channel (PDSCH), and when the RIV corresponds to any RBG in the uplink subband, the FDRA is used for a physical uplink shared channel (PUSCH).

[0116] Aspect 21: The method according to any one of aspects 17 to 20, wherein the DCI is used to schedule uplink and downlink in the same time slot.

[0117] Aspect 22: A method according to any one of aspects 17 to 21, wherein the TDRA points to a row in a radio resource control (RRC) configuration table, the radio resource control (RRC) configuration table including a potential first TDRA for an uplink and a potential second TDRA for a downlink.

[0118] Aspect 23: A method according to any one of Aspects 17 to 21, wherein the TDRA includes a start and length indication value (SLIV) for uplink and for downlink, and the method further includes: sending a mapping between the SLIV, downlink allocation and uplink allocation.

[0119] Aspect 24: According to the method according to any one of aspects 17 to 23, the method further comprises: configuring a guard time between receiving a physical downlink shared channel (PDSCH) and sending a physical uplink shared channel (PUSCH).

[0120] Aspect 25: A method according to any one of Aspects 17 to 24, wherein the TDRA includes a start and length indication value (SLIV), the start and length indication value (SLIV) having an uplink bit in a first field and a downlink bit in a second field.

[0121] Aspect 26: The method according to any one of aspects 17 to 25, wherein the DCI is used to schedule uplink and downlink in multiple time slots.

[0122] Aspect 27: The method according to any one of aspects 17 to 26, wherein the TDRA comprises a first TDRA for a downlink, the first TDRA being the same as a second TDRA for an uplink.

[0123] Aspect 28: The method according to any one of aspects 17 to 26, wherein the TDRA includes a bit mapped to an uplink TDRA and a bit mapped to a downlink TDRA.

[0124] Aspect 29: The method according to any one of Aspects 17 to 28, further comprising: sending a first mapping between uplink parameters and fields of the DCI, and a second mapping between downlink parameters and fields of the DCI.

[0125] Aspect 30: According to the method described in any one of Aspects 17 to 29, the method also includes: sending an offset for the configuration of one of the uplink parameters relative to a reference parameter, the offset and the reference parameter indicating one of the downlink parameters and one of the uplink parameters.

[0126] Aspect 31: According to the method according to any one of aspects 17 to 28, the method further includes: sending a configuration for a pair of uplink parameters and downlink parameters, and the DCI points to the configuration.

[0127] Aspect 32: A method according to any one of aspects 17 to 31, wherein uplink parameters and downlink parameters are functions of the FDRA and the TDRA.

[0128] Aspect 33: A device for wireless communication, the device comprising: a memory; and at least one processor coupled to the memory, the at least one processor being configured to: receive downlink control information (DCI) including an uplink grant and a downlink grant, the DCI indicating a time domain resource allocation (TDRA) and a frequency domain resource allocation (FDRA); determine whether the DCI is a unidirectional DCI or a bidirectional DCI based on whether the FDRA points to an uplink subband and / or a downlink subband; and communicate according to the DCI.

[0129] Aspect 34: The apparatus according to aspect 33, wherein the at least one processor is further configured to: when both uplink communication and downlink communication are scheduled, decode the DCI based on a first radio network temporary identifier (RNTI) dedicated to the DCI.

[0130] Aspect 35: An apparatus according to Aspect 33 or 34, wherein the FDRA includes a type zero FDRA having a bitmap, and the at least one processor is further configured to determine by: when the value of any bit in the bitmap corresponds to any resource block group (RBG) in the downlink subband, determining that the FDRA is used for a physical downlink shared channel (PDSCH), and when the value of any bit in the bitmap corresponds to any RBG in the uplink subband, determining that the FDRA is used for a physical uplink shared channel (PUSCH).

[0131] Aspect 36: An apparatus according to Aspect 33 or 34, wherein the FDRA includes a type 1 FDRA having a resource indicator value (RIV), and the at least one processor is further configured to determine by: when the RIV corresponds to any resource block group (RBG) in the downlink subband, determining that the FDRA is used for a physical downlink shared channel (PDSCH), and when the RIV corresponds to any RBG in the uplink subband, determining that the FDRA is used for a physical uplink shared channel (PUSCH).

[0132] Aspect 37: An apparatus according to any one of aspects 33 to 36, wherein the DCI is used to schedule uplink and downlink in the same time slot.

[0133] Aspect 38: An apparatus according to any one of Aspects 33 to 37, wherein the TDRA points to a row in a radio resource control (RRC) configuration table, the radio resource control (RRC) configuration table including a potential first TDRA for uplink communication and a potential second TDRA for downlink communication.

[0134] Aspect 39: An apparatus according to any one of Aspects 33 to 37, wherein the TDRA includes a start and length indication value (SLIV) for an uplink and for a downlink, and the at least one processor is further configured to: receive a mapping between the SLIV, a downlink allocation, and an uplink allocation.

[0135] Aspect 40: An apparatus according to any one of aspects 33 to 39, wherein the at least one processor is further configured to: apply a guard time between receiving a physical downlink shared channel (PDSCH) and sending a physical uplink shared channel (PUSCH).

[0136] Aspect 41: An apparatus according to any one of Aspects 33 to 40, wherein the TDRA includes a start and length indication value (SLIV), the start and length indication value (SLIV) having an uplink bit in a first field and a downlink bit in a second field.

[0137] Aspect 42: An apparatus according to any one of aspects 33 to 41, wherein the DCI is used to schedule uplink and downlink in multiple time slots.

[0138] Aspect 43: The apparatus according to any one of aspects 33 to 42, wherein the TDRA comprises a first TDRA for a downlink, the first TDRA being the same as a second TDRA for an uplink.

[0139] Aspect 44: The apparatus according to any one of aspects 33 to 42, wherein the TDRA includes a bit mapped to an uplink TDRA and a bit mapped to a downlink TDRA.

[0140] Aspect 45: An apparatus according to any one of Aspects 33 to 44, wherein the at least one processor is further configured to: receive a first mapping between uplink parameters and fields of the DCI, and a second mapping between downlink parameters and fields of the DCI.

[0141] Aspect 46: An apparatus according to any one of Aspects 33 to 45, wherein the at least one processor is further configured to: receive an offset for a configuration of one of the uplink parameters relative to a reference parameter, the offset and the reference parameter indicating one of the downlink parameters and one of the uplink parameters.

[0142] Aspect 47: The apparatus according to any one of aspects 33 to 45, wherein the at least one processor is further configured to: receive a configuration for a pair of uplink parameters and downlink parameters, the DCI pointing to the configuration.

[0143] Aspect 48: The apparatus according to any one of aspects 33 to 47, wherein uplink parameters and downlink parameters are functions of the FDRA and the TDRA.

[0144] Aspect 49: A device for wireless communication, the device comprising: a memory; and at least one processor coupled to the memory, the at least one processor being configured to: send downlink control information (DCI) including an uplink grant and a downlink grant, the DCI indicating a time domain resource allocation (TDRA) and a frequency domain resource allocation (FDRA), the DCI indicating whether the DCI is a unidirectional DCI or a bidirectional DCI based on whether the FDRA points to an uplink subband and / or a downlink subband; and communicate according to the DCI.

[0145] Aspect 50: The apparatus according to aspect 49, wherein the at least one processor is further configured to: when scheduling both uplink communication and downlink communication, encode the DCI based on a first radio network temporary identifier (RNTI) dedicated to the DCI.

[0146] Aspect 51: An apparatus according to Aspect 49 or 50, wherein the FDRA includes a type zero FDRA having a bitmap, and the DCI indicates that when the value of any bit in the bitmap corresponds to any resource block group (RBG) in the downlink subband, the FDRA is used for the physical downlink shared channel (PDSCH), and when the value of any bit in the bitmap corresponds to any RBG in the uplink subband, the FDRA is used for the physical uplink shared channel (PUSCH).

[0147] Aspect 52: An apparatus according to Aspect 49 or 50, wherein the FDRA includes a type-one FDRA having a resource indicator value (RIV), and the DCI indicates that when the RIV corresponds to any resource block group (RBG) in the downlink subband, the FDRA is used for a physical downlink shared channel (PDSCH), and when the RIV corresponds to any RBG in the uplink subband, the FDRA is used for a physical uplink shared channel (PUSCH).

[0148] Aspect 53: An apparatus according to any one of aspects 49 to 52, wherein the DCI is used to schedule uplink and downlink in the same time slot.

[0149] Aspect 54: An apparatus according to any one of Aspects 49 to 53, wherein the TDRA points to a row in a radio resource control (RRC) configuration table, the radio resource control (RRC) configuration table including a potential first TDRA for an uplink and a potential second TDRA for a downlink.

[0150] Aspect 55: An apparatus according to any one of Aspects 49 to 53, wherein the TDRA includes a start and length indication value (SLIV) for uplink and for downlink, and the method further includes: sending a mapping between the SLIV, downlink allocation and uplink allocation.

[0151] Aspect 56: An apparatus according to any one of Aspects 49 to 55, wherein the at least one processor is further configured to: configure a protection time between receiving a physical downlink shared channel (PDSCH) and sending a physical uplink shared channel (PUSCH).

[0152] Aspect 57: An apparatus according to any one of Aspects 49 to 56, wherein the TDRA includes a start and length indication value (SLIV), the start and length indication value (SLIV) having an uplink bit in a first field and a downlink bit in a second field.

[0153] Aspect 58: An apparatus according to any one of aspects 49 to 57, wherein the DCI is used to schedule uplink and downlink in multiple time slots.

[0154] Aspect 59: The apparatus according to any one of aspects 49 to 58, wherein the TDRA includes a first TDRA for a downlink, the first TDRA being the same as a second TDRA for an uplink.

[0155] Aspect 60: The apparatus according to any one of aspects 49 to 58, wherein the TDRA includes a bit mapped to an uplink TDRA and a bit mapped to a downlink TDRA.

[0156] Aspect 61: An apparatus according to any one of Aspects 49 to 60, wherein the at least one processor is further configured to: send a first mapping between uplink parameters and fields of the DCI, and a second mapping between downlink parameters and fields of the DCI.

[0157] Aspect 62: An apparatus according to any one of Aspects 49 to 61, wherein the at least one processor is further configured to: send an offset for the configuration of one of the uplink parameters relative to a reference parameter, the offset and the reference parameter indicating one of the downlink parameters and one of the uplink parameters.

[0158] Aspect 63: The apparatus according to any one of aspects 49 to 61, wherein the at least one processor is further configured to: send a configuration for a pair of uplink parameters and downlink parameters, the DCI pointing to the configuration.

[0159] Aspect 64: An apparatus according to any one of aspects 49 to 63, wherein uplink parameters and downlink parameters are functions of the FDRA and the TDRA.

[0160] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not meant to be limited to the specific order or hierarchy provided.

[0161] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to conform to the full scope consistent with the language claims, wherein the elements mentioned in the singular are not intended to represent "one and only one", unless specifically so stated, but "one or more". The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having an advantage over other aspects. Unless 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 A, multiple B, or multiple C. 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 elements of the various aspects described throughout the present disclosure that are or will later become known to a person of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module," "mechanism," "element," "device," etc. cannot replace the word "component." Therefore, no claim element will be understood to be a component plus function unless the element is explicitly stated using the phrase "component for..."

Claims

1. A method for wireless communication by a user equipment (UE), the method comprising: receiving downlink control information (DCI) including an uplink grant and a downlink grant, the DCI indicating a time domain resource allocation (TDRA) and a frequency domain resource allocation (FDRA); Determining whether the DCI is a unidirectional DCI or a bidirectional DCI based on whether the FDRA points to an uplink subband and / or a downlink subband; as well as Communicate according to the DCI.

2. The method according to claim 1, further comprising: When both uplink and downlink communications are scheduled, the DCI is decoded based on a Radio Network Temporary Identifier (RNTI) dedicated to the DCI.

3. The method of claim 1 , wherein the FDRA comprises a type zero FDRA having a bitmap, and the determining further comprises: When the value of any bit in the bitmap corresponds to any resource block group (RBG) in the downlink subband, the FDRA is determined to be used for a physical downlink shared channel (PDSCH), and when the value of any bit in the bitmap corresponds to any RBG in the uplink subband, the FDRA is determined to be used for a physical uplink shared channel (PUSCH).

4. The method of claim 1 , wherein the FDRA comprises a type-one FDRA having a resource indicator value (RIV), and the determining further comprises: When the RIV corresponds to any resource block group (RBG) in the downlink subband, the FDRA is determined to be used for a physical downlink shared channel (PDSCH), and when the RIV corresponds to any RBG in the uplink subband, the FDRA is determined to be used for a physical uplink shared channel (PUSCH). The method according to claim 1 , wherein the DCI is used to schedule uplink communication and downlink communication in the same time slot.

6. The method of claim 5, wherein the TDRA points to a row in a radio resource control (RRC) configuration table, the radio resource control (RRC) configuration table comprising a potential first TDRA for uplink communication and a potential second TDRA for downlink communication.

7. The method of claim 5, wherein the TDRA includes a start and length indication value (SLIV) for uplink communication and for downlink communication, the method further comprising: A mapping between the SLIV, downlink allocations, and uplink allocations is received.

8. The method according to claim 5, further comprising: A guard time is applied between receiving a Physical Downlink Shared Channel (PDSCH) and transmitting a Physical Uplink Shared Channel (PUSCH).

9. The method of claim 5, wherein the TDRA includes a start and length indication value (SLIV) having an uplink bit in a first field and a downlink bit in a second field.

10. The method of claim 1, wherein the DCI is used to schedule uplink communications and downlink communications in a plurality of time slots. 11 . The method of claim 10 , wherein the TDRA comprises a first TDRA for downlink communication, the first TDRA being the same as a second TDRA for uplink communication.

12. The method of claim 10, wherein the TDRA comprises a bit mapped to an uplink TDRA and a bit mapped to a downlink TDRA.

13. The method according to claim 1, further comprising: A first mapping between uplink parameters and fields of the DCI and a second mapping between downlink parameters and fields of the DCI are received.

14. The method according to claim 13, further comprising: An offset for configuration of one of the uplink parameters relative to a reference parameter is received, the offset and the reference parameter indicating one of the downlink parameters and one of the uplink parameters.

15. The method according to claim 1, further comprising: A configuration for a pair of uplink parameters and downlink parameters is received, the DCI pointing to the configuration.

16. The method of claim 1, wherein uplink parameters and downlink parameters are functions of the FDRA and the TDRA.

17. An apparatus for wireless communication by a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory, the at least one processor configured to: receiving downlink control information (DCI) including an uplink grant and a downlink grant, the DCI indicating a time domain resource allocation (TDRA) and a frequency domain resource allocation (FDRA); Determining whether the DCI is a unidirectional DCI or a bidirectional DCI based on whether the FDRA points to an uplink subband and / or a downlink subband; as well as Communicate according to the DCI.

18. The apparatus of claim 17, wherein the at least one processor is further configured to decode the DCI based on a radio network temporary identifier (RNTI) specific to the DCI when both uplink and downlink communications are scheduled.

19. The apparatus of claim 17, wherein the FDRA comprises a type zero FDRA having a bitmap, and the determining further comprises: When the value of any bit in the bitmap corresponds to any resource block group (RBG) in the downlink subband, the FDRA is determined to be used for a physical downlink shared channel (PDSCH), and when the value of any bit in the bitmap corresponds to any RBG in the uplink subband, the FDRA is determined to be used for a physical uplink shared channel (PUSCH).

20. The apparatus of claim 17, wherein the FDRA comprises a type-one FDRA having a resource indicator value (RIV), and the determining further comprises: When the RIV corresponds to any resource block group (RBG) in the downlink subband, the FDRA is determined to be used for a physical downlink shared channel (PDSCH), and when the RIV corresponds to any RBG in the uplink subband, the FDRA is determined to be used for a physical uplink shared channel (PUSCH).

21. The apparatus of claim 17, wherein the DCI is used to schedule uplink communications and downlink communications in the same time slot.

22. The apparatus of claim 21, wherein the TDRA points to a row in a radio resource control (RRC) configuration table, the radio resource control (RRC) configuration table comprising a potential first TDRA for uplink communications and a potential second TDRA for downlink communications.

23. The apparatus of claim 21, wherein the TDRA comprises a start and length indicator value (SLIV) for uplink communications and for downlink communications, the method further comprising: A mapping between the SLIV, downlink allocations, and uplink allocations is received.

24. The apparatus of claim 21, wherein the at least one processor is further configured to apply a guard time between receiving a physical downlink shared channel (PDSCH) and transmitting a physical uplink shared channel (PUSCH).

25. The apparatus of claim 21, wherein the TDRA comprises a start and length indication value (SLIV) having an uplink bit in a first field and a downlink bit in a second field.

26. The apparatus of claim 17, wherein the DCI is used to schedule uplink communications and downlink communications in a plurality of time slots.

27. The apparatus of claim 26, wherein the TDRA comprises a first TDRA for downlink communications, the first TDRA being the same as a second TDRA for uplink communications.

28. The apparatus of claim 26, wherein the TDRA comprises a bit mapped to an uplink TDRA and a bit mapped to a downlink TDRA.

29. The apparatus of claim 17, wherein the at least one processor is further configured to receive a first mapping between uplink parameters and fields of the DCI and a second mapping between downlink parameters and fields of the DCI.

30. The apparatus of claim 29, wherein the at least one processor is further configured to receive an offset for a configuration of one of the uplink parameters relative to a reference parameter, the offset and the reference parameter indicating one of the downlink parameters and one of the uplink parameters.

Images