Downlink control information piggybacking in physical downlink shared channel, downlink control information coding

Abstract

The base station transmits a first downlink control information (DCI) part in a physical downlink control channel (PDCCH), wherein the first DCI part indicates a second DCI part. The base station jointly encodes a plurality of component DCIs, each of which provides a resource allocation in conjunction with the first DCI part. The apparatus transmits a second DCI part including the jointly encoded plurality of component DCIs in a physical downlink shared channel (PDSCH).

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Patent Application No. 16 / 868,330, filed on May 6, 2020, entitled “DOWNLINK CONTROL INFORMATION PIGGYBACK IN PHYSICAL DOWNLINK SHARED CHANNEL, DOWNLINK CONTROL INFORMATION ENCODING,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems and, more particularly, to wireless communications including downlink control information. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support 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 a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., utilizing the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. 5G NR technology needs to be further improved. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] A simplified overview of one or more aspects is presented below to provide a basic understanding of these aspects. This overview is not an extensive overview of all contemplated aspects, and is neither intended to identify key or important elements of all aspects, nor to delineate 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 that is presented later.

[0007] In one aspect of the present disclosure, a method, computer readable medium, and apparatus for wireless communication at a base station are provided. The apparatus transmits a first downlink control information (DCI) portion in a physical downlink control channel (PDCCH), wherein the first DCI portion indicates a second DCI portion. The apparatus jointly encodes a plurality of component DCIs, each of which provides a resource allocation in conjunction with the first DCI portion. The apparatus transmits a second DCI portion including the jointly encoded plurality of component DCIs in a physical downlink shared channel (PDSCH).

[0008] In one aspect of the present disclosure, a method, computer readable medium, and apparatus for wireless communication at a user equipment (UE) are provided. The apparatus receives a first DCI part in a PDCCH. The apparatus receives a second DCI part in a PDSCH including a plurality of component DCIs jointly coded, each of which provides a resource allocation in conjunction with the first DCI part.

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

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

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

[0012] Figure 3 is a diagram illustrating an example of a base station and a UE in an access network.

[0013] Figure 4 is a diagram illustrating an example of transmitting DCI in multiple parts.

[0014] Figure 5 is a diagram illustrating an example of multiple component DCIs.

[0015] Figure 6 is a diagram illustrating an example of multiple component DCIs.

[0016] Figure 7 is a diagram illustrating an example of multiple component DCIs.

[0017] Figure 8 is a diagram illustrating an example of transmitting DCI in multiple parts.

[0018] Fig.9A and 9B is a diagram illustrating an example of transmitting DCI in multiple parts.

[0019] Fig.10 is a flow chart of a method of wireless communication.

[0020] Fig.11 is a conceptual data flow diagram illustrating the flow of data between different parts / components in an example apparatus.

[0021] Fig.12 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

[0022] Fig.13 is a flow chart of a method of wireless communication.

[0023] Fig.14 is a conceptual data flow diagram illustrating the flow of data between different parts / components in an example apparatus.

[0024] Fig.15 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system. DETAILED DESCRIPTION

[0025] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it is apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid blurring these concepts.

[0026] 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 such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0027] For example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system" including 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, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. One or more processors in a processing system can execute software. Whether it is software, firmware, middleware, microcode, hardware description language, or other, software should be broadly interpreted as representing instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc.

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

[0029] The grant may be indicated to the UE in multiple parts. The first part of the grant may be sent in the physical downlink control channel (PDCCH) region, and the second part of the grant may be sent in the physical downlink shared channel (PDSCH) region. The inclusion of the second part of the grant may be referred to as piggybacking downlink control information (DCI) using PDSCH. The DCI piggyback design may reduce the need for the UE to perform PDCCH blind decoding, so the UE can process the PDCCH faster. For example, when using the DCI piggyback design, there may be fewer DCIs in the PDCCH region because other DCIs may be sent in the PDSCH region. Therefore, the UE may have fewer PDCCHs to decode. In addition, the DCI piggyback may share the same beam used to send the PDSCH, such as having a QCL relationship with the PDSCH. This can improve transmission efficiency because the beam used for the PDSCH may be narrower than the beam used for the PDCCH. The various aspects proposed in this article may further improve the efficiency of DCI piggybacking in the PDSCH. In one example, multiple component DCIs may be piggybacked in the PDSCH region, and the DCI in the PDCCH region may be used to provide information related to the DCI piggybacking and the multiple component DCIs.Each component DCI may carry resource allocation information in conjunction with the DCI in the PDCCH region.

[0030] Figure 1 1 is a diagram illustrating an example of a wireless communication system and access network 100. In some aspects, a base station 102 or 180 may include a DCI and DCI piggyback configuration component 198 configured to split the DCI into multiple parts. A first DCI part may be sent within a PDCCH region, and a second DCI part (which may be referred to as a DCI piggyback) may be sent within a PDSCH. The first DCI part may include initial control information, and may also include piggyback control information about the second DCI part. The second DCI part may include multiple component DCIs, and each component DCI may include remaining control information about a downlink allocation. For example, a base station may be configured to send a first DCI part in a PDCCH, jointly encode multiple component DCIs, and send a second DCI part including a jointly encoded multiple component DCI in a PDSCH, wherein each of the component DCIs provides a resource allocation in conjunction with the first DCI part.

[0031] UE 104 may include a DCI and DCI piggyback receiving component 199 configured to receive multiple DCIs and multiple component DCIs in PDCCH and PDSCH. For example, the UE may receive a first DCI part in PDCCH, and the UE may receive a second DCI part in PDSCH including multiple component DCIs that are jointly coded, wherein each of the component DCIs may provide resource allocations in conjunction with the first DCI part.

[0032] The wireless communication system (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)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0033] 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 first backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG-RAN)) can interface with the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and device tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (eg, through the EPC 160 or the core network 190) via a third backhaul link 134 (eg, an X2 interface). The third backhaul link 134 may be wired or wireless.

[0034] 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' can have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network can also include a home evolved node B (eNB) (HeNB), which can provide services to a restricted group called a closed subscriber group (CSG). The communication link 120 between base station 102 and UE 104 can include an uplink (UL) (also called a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also called a forward link) transmission from base station 102 to UE 104. The communication link 120 can use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link can be through one or more carriers. The base station 102 / UE 104 may use up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) of bandwidth per carrier allocated in a carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. The carriers may be adjacent to each other, 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).

[0035] 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). The D2D communication may be through various wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 602.11 standard, LTE, or NR.

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

[0037] 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 used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may improve coverage and / or increase capacity of the access network.

[0038] The base station 102, whether a small cell 102' or a large cell (e.g., a macro base station), may include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180, may operate at millimeter wave (mmW) frequencies in the traditional sub-6 GHz spectrum and / or communicate with the UE 104 at near mmW frequencies. 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 RF in the electromagnetic spectrum. EHF ranges from 30 GHz to 300 GHz and has wavelengths between 1 mm and 10 mm. Radio waves in the band may be referred to as millimeter waves. Near mmW may extend down to 3 GHz frequencies with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz and is also referred to as centimeter waves. Communications using mmW / near mmW radio (RF) bands (e.g., 3 GHz-300 GHz) have extremely high path losses and short distances. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0039] 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 and transmit directions for each of base station 180 / UE 104. The transmit and receive directions of base station 180 may be the same, or may be different. The transmit and receive directions of UE 104 may be the same, or may be different.

[0040] 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 transmitted through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE 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 PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0041] 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. Typically, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted 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 packet switching (PS) streaming (PSS) service, and / or other IP services.

[0042] Base stations may include and / or be referred to as gNBs, Node Bs, eNBs, access points, base transceiver stations, radio base stations, radio transceivers, transceiver functions, basic service sets (BSSs), extended service sets (ESSs), transmit receive points (TRPs), or some other suitable terminology. Base stations 102 provide access points to EPC 160 or core network 190 for UEs 104. Examples of UEs 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some of UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, 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.

[0043] Figure 2A FIG200 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 Figure 250 illustrates an example of a second subframe within a 5G / NR frame structure. Figure 2D280 is a diagram illustrating an example of UL channels within a 5G / NR subframe. The 5G / NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that set of subcarriers are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that set of subcarriers are dedicated to both DL and UL. Figure 2A , 2C In the example provided, it is assumed that the 5G / NR frame structure is TDD, subframe 4 is configured with slot format 28 (mainly DL), where D is DL, U is UL, and X is flexible between DL / UL, and subframe 3 is configured with slot format 34 (mostly UL). Although subframes 3 and 4 are shown with slot formats 34 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically through DL control information (DCI), or semi-statically / statically through radio resource control (RRC) signaling). Note that the description below also applies to the 5G / NR frame structure for TDD.

[0044] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes (1ms) of equal size. 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-constrained scenarios; limited to single stream transmission). The number of time slots within a subframe is based on the time slot configuration and numerology. For slot configuration 0, different numerical parameters μ0 to 5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different numerical parameters 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Thus, for slot configuration 0 and numerical parameter μ, there are 14 symbols / slot, and 2 μ The subcarrier spacing and symbol length / duration are functions of digital parameters. The subcarrier spacing can be equal to 2μ *15kHz, where μ is a digital parameter 0 to 5. Likewise, a digital parameter μ=0 has a subcarrier spacing of 15kHz, and a digital parameter μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example is provided for slot configuration 0, for which there are 14 symbols per slot and 4 slots per subframe for a numerical parameter μ = 2. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

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

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

[0047] 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 particular subframe of the frame. The UE 104 uses the PSS to determine the subframe / symbol timing and the physical layer identity. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of the frame. The UE uses the SSS to determine the physical layer cell identification group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the location of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) may be logically grouped using the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides multiple RBs in the system bandwidth as well as a system frame number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information such as System Information Blocks (SIBs) that are not transmitted through the PBCH, and paging messages.

[0048] like Figure 2C As shown, some of the REs carry DM-RS for channel estimation at the base station (indicated as R for one specific configuration, but other DM-RS configurations are possible). The UE can send DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be sent in the first one or two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent, and depending on the specific PUCCH format used, the PUCCH DM-RS can be sent in different configurations. The UE can send a sounding reference signal (SRS). The SRS can be sent in the last symbol of the subframe. The SRS can have a comb structure, and the UE can send the SRS on one of these combs. The base station can use the SRS for channel quality estimation to achieve frequency-dependent scheduling on the UL.

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

[0050] Figure 33 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functions. 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 functions 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 functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with transmission 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 functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0051] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transmission channel, forward error correction (FEC) encoding / decoding of the transmission 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-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time domain and / or frequency domain, and then 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 precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine coding and modulation schemes, and for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition 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.

[0052] 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 functions 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 converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes separate OFDM symbol streams 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 the 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 functions.

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

[0054] Similar to the functions described in conjunction with the DL transmission of the base station 310, the controller / processor 359 provides RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression, and security (encryption, decryption, integrity protection, integrity checking); RLC layer functions associated with transmission 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 functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority processing, and logical channel priority.

[0055] The TX processor 368 may select an appropriate coding and modulation scheme and facilitate spatial processing using channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310. 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.

[0056] At the base station 310, the UL transmission is processed 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.

[0057] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, 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 an ACK and / or NACK protocol to support HARQ operations.

[0058] 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 198. 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 199 related aspects.

[0059] As described above, the authorization can be indicated to the UE in multiple parts. The first part can be sent in the PDCCH region, and the second part can be sent in the PDSCH region. As described herein, multiple DCI components can be indicated in the second part. Therefore, multiple downlink / uplink authorizations can be indicated by a combination of multiple DCI components included (e.g., piggybacked) in the first part indicated in the PDCCH region and in the PDSCH region. For example, the first DCI part in the PDCCH can be a UE authorization resource allocation in the PDSCH, and the first DCI part can also indicate to the UE that there is a second DCI part or more (e.g., DCI piggybacked) in the PDSCH. The second DCI part may include multiple component DCIs jointly encoded by the base station, and these multiple component DCIs may authorize other resources, signaling and / or information (e.g., additional PDSCH, PUSCH, CSI-RS, SRS, etc.) to the UE, which may be unrelated to the resources authorized in the first DCI part. The DCI in the PDCCH can provide downlink resource allocation and / or uplink resource authorization for one or more scheduled entities. Multiple PDCCHs may be sent in each time slot, and each PDCCH may carry user-specific DCI or common DCI (e.g., broadcasting control information to a group of scheduled entities). Each DCI may also include cyclic redundancy check (CRC) bits scrambled with a radio network temporary identifier (RNTI), which may be a specific user RNTI or a group RNTI, to allow the scheduled entity to determine the type of control information transmitted in the PDCCH.

[0060] Figure 4400 is a diagram illustrating an example of a level 2 PDCCH, such as a DMRS-based PDDCH (D-PDCCH). In order to reduce control overhead and improve processing timelines, the DCI for (multiple) DL grants may be divided into two or more parts. A first DCI part 402 may be sent within a control region (e.g., a PDCCH region 408), and a second DCI part 404 (which may be referred to as a DCI piggyback) may be sent within a downlink service region (e.g., a PDSCH region 410). The PDCCH region 408 and the PDSCH region 410 may together form a time slot. The first DCI part 402 may include initial control information about a downlink allocation, such as a resource allocation (RA), rank, and modulation order for the downlink allocation. In addition, the first DCI part 402 may also include piggyback control information about the second DCI part 404. In some examples, the piggyback control information may indicate the number (size) and code rate of resource elements of the second DCI part 404. The piggyback control information may also indicate the location (e.g., starting resource element) and code rate of the second DCI part 404. In some examples, multiple second DCI part formats may be maintained, each of which indicates the size and code rate of the second DCI part 404. The first DCI part 402 may be configured with semi-persistent scheduling (SPS) so that the UE may be RRC configured to receive the second DCI part 404 and related DL traffic 406 in the PDSCH region 410.

[0061] The second DCI part 404 may include the remaining control information about the downlink allocation. For example, the remaining control information may include non-time critical control information, such as HARQ process ID, redundancy version ID, new data indicator, transmit power control indicator, channel quality indicator request, sounding reference signal request, or downlink allocation index. The second DCI part 404 may be sent in the PDSCH region 410 within the RA assigned with the PDSCH rank and modulation order, and may also share the DMRS for demodulating data and / or other (multiple) DCI. In addition, the second DCI part 404 may also include other DCI, such as other uplink and / or downlink grants. The second DCI part 404 may also support multiple users, where the group RNTI may be included in the first DCI part 402, and addressing may be included in the second DCI part 404 so that different UEs can receive (e.g., obtain) their respective transmissions in the downlink traffic 406 of the PDSCH region 410.

[0062] By splitting the DCI into two parts, a better and more flexible transmission timeline can be configured for the UE and / or the base station. For example, the base station can send HARQ-related information in the second DCI part 404, which provides a more relaxed timeline for the base station to generate information because the base station is not limited to putting all information in one DCI (e.g., within the first DCI part 402 or the PDCCH region 408), which may have a very short duration. The base station may then have more time to prepare the payload corresponding to the PDCCH. DCI splitting can also provide more efficient information delivery because the rank and modulation order of the PDSCH can be used. PDDCH (e.g., the second DCI part 404) can also be sent in the same manner as the PDSCH region 410.

[0063] In some networks, the network may support the use of bandwidth parts (BWPs), where a BWP may be a set of adjacent PRBs on a given component carrier (CC). Data and control channels may be received and / or transmitted within a BWP. A BWP may be configured with various parameters, which may include digital parameters, frequency location, bandwidth size, and / or control resource set (CORESET). A CORESET may be a set of physical resources within a specific area of ​​a downlink resource grid used to carry a PDCCH DCI.

[0064] The UE may blindly decode the PDCCH candidate set delivered in the CORESET to identify the DCI for the UE, where the PDCCH candidates to be monitored by the UE may be configured via a search space (SS) set. For example, there may be a common SS set that is typically monitored by a group of UEs in a cell, and there may be a UE-specific SS set that is monitored by a specific UE. A UE may be configured with multiple SS sets. Each SS set may be associated with a CORESET. As shown in conjunction with Figure 1 As described, some communications between base station 102 / 180 and UE 104 may be based on directional beamforming transmission and reception using a large number of antennas between the base station and the UE (e.g., beamforming 182). In some examples, the PDCCH may be transmitted by the base station using a wider beam or a beam of the same size as the beam used by the base station to send the PDSCH. The blind decoding mechanism of the PDCCH enables multiple UEs to be served using the PDCCH at the same time. The mechanism can also reduce blocking between UEs by randomly hashing the location of the PDCCH in different ways for different UEs in the CORESET.

[0065] For networks operating at mmW frequencies and / or near mmW frequencies (e.g., FR2), due to analog beam transmission limitations and short slot durations in the time domain (e.g., due to increased subcarrier spacing scaling), it may be less likely to configure a base station to transmit multiple DCIs to different UEs than for networks operating at lower frequency bands (e.g., FR1). For example, with larger scaling of subcarrier spacing, the length of a symbol or slot may be relatively short. Since different UEs may use different analog beams, the base station may require additional time to switch beams in the time domain. Therefore, a network operating at FR2 may be more likely to configure a base station to transmit multiple downlink and / or uplink grants to a UE, such as to handle relatively long, bursty downlink and / or uplink traffic.

[0066] The aforementioned DCI piggyback (e.g., splitting the DCI into multiple parts and including the second part in the PDSCH) mechanism can be applied to networks operating at mmW frequencies or near mmW frequencies (e.g., FR2), where the DCI piggyback design may be very useful in mmW transmission or similar situations. Using DCI piggyback can reduce the need for the UE to perform PDCCH blind decoding, so the UE can process the PDCCH faster. For example, with the DCI piggyback design, there may be fewer DCIs in the PDCCH area because other DCIs may be sent in the data area (e.g., the PDSCH area). Therefore, the UE may have fewer PDCCHs to decode. In addition, the DCI piggyback (e.g., the second DCI part 404) can share the same beam used to send the PDSCH, such as having a quasi-coordinated co-location (QCL) relationship with the PDSCH. This can improve transmission efficiency because the beam used for the PDSCH may be narrower than the beam used for the PDCCH.

[0067] Various aspects presented herein may further improve the efficiency and use of DCI piggybacking in PDSCH. In one example, a DCI piggyback (e.g., a second DCI portion in a PDSCH region) may include multiple component DCIs (e.g., DCIs with multiple UL and / or DL ​​grants), and a first DCI portion (e.g., in a PDCCH region) may be used to provide information related to these multiple component DCIs in the DCI piggyback. Thus, a DCI piggyback carrying multiple component DCIs may contain information about one or more DCIs. Each component DCI may carry resource allocation information in conjunction with a DCI in a PDCCH region (e.g., a first DCI portion).

[0068] Figure 55 is a diagram illustrating multiple component DCIs in a DCI piggyback, where three component DCIs 502, 504, and 506 are transmitted within a DCI piggyback 510. Since each component DCI may include a CRC 508, the CRC 508 may use additional space in the transmission of each CRC, which may be 24 bits long, for example. When multiple component DCIs are transmitted, the additional bits for different CRCs may reduce transmission efficiency.

[0069] In order to reduce the space occupied by the CRC accompanying each component DCI, when multiple component DCIs are sent in the PDSCH, the base station may combine the multiple component DCIs into a single payload that is jointly encoded with one CRC. Figure 6 600 is a diagram illustrating an example of combining multiple component DCIs and encoding them with one CRC. For example, three component DCIs 602, 604, 606 may be included in a DCI piggyback 610, where each component DCI may have a corresponding CRC 608. When the DCI is sent in the PDDCH, each DCI may be associated with a CRC for decoding. However, when the DCI (e.g., component DCI) is sent in the PDSCH, the component DCI may be combined and encoded with one CRC. Therefore, the component DCIs 602, 604, and 606 may be combined into a payload 614 in the PDSCH and then jointly encoded with one CRC 612. Long polar codes may be used for the CRC 612 and the combined payload 614 (e.g., multiple component DCIs). By combining multiple component DCIs and encoding them with one CRC (e.g., 612), one decoding may be performed instead of multiple decodings, for example, three decodings may be required before combining because there are three separate CRCs 608 for the component DCIs 602, 604, 606. This may reduce the overall size of the payload, where each CRC that is reduced may save an additional 24 bits for the payload. As previously described, the CRC 612 may be scrambled by one RNTI, and the same RNTI may be used to scramble the combined payload 614. The RNTI may be a cell RNTI (C-RNTI), or may be a configurable new RNTI.

[0070] The various aspects presented herein illustrate ways to combine or aggregate component DCIs in a DCI piggyback. The UE may be configured to monitor component DCIs of different lengths (e.g., sizes) because different component DCIs may have different lengths. The length of each component DCI may depend on the configured DCI format. The UE may be configured to monitor multiple (e.g., up to four) DCIs of different lengths for each component carrier (CC). However, the UE may not know the DCI format (e.g., length) of each component DCI in the DCI piggyback in advance. In order for the UE to decode the combined payload (e.g., 614) with a CRC (e.g., 612), the first DCI part (e.g., the DCI in the PDDCH) may need to indicate to the UE the length of each component DCI. This may increase the overhead of the first DCI part.

[0071] In one example, zero padding (e.g., signal or spectrum extension with zeros) may be added to the component DCI(s) in the DCI piggyback so that the component DCIs have the same length as each other. For example, zero padding may be added to the component DCI(s) in the DCI piggyback until its length matches the longest component DCI length that the UE is monitoring minus the CRC. Figure 7 700 is a diagram illustrating the use of zero padding to match the length of component DCI. For example, three component DCIs 702, 704, 706 may be included in a DCI piggyback 710, where each component DCI may have a corresponding CRC 708. Component DCI 702 may be 50 bits long, component DCI 704 may be 100 bits long, and component DCI 706 may be 80 bits long. If the longest DCI length that the UE is configured to monitor is 100 bits, which is also the length of component DCI 704 (e.g., configured via the DCI format), the entity (e.g., a base station) that sends the DCI piggyback may add zero padding to the component DCI that lacks the longest monitoring length (e.g., 100 bits) so that they have the same length. For example, 50 bits of zero padding 716 may be added to component DCI 702 to make it 100 bits in length, and 20 bits of zero padding 718 may be added to component DCI 706 to make it 100 bits in length. Thus, the component DCIs 702 , 704 , and 706 may be combined into a payload 714 of the same size (eg, 100 bits each) and then jointly encoded using one CRC 712 .

[0072] In another example, if Figure 7If the longest DCI length that the UE is monitoring is 120 bits, zero padding may be added to all three component DCIs so that each of the three component DCIs is 120 bits in length, e.g., 70 bits of zero padding for component DCI 702, 20 bits of zero padding for component DCI 704, and 40 bits of zero padding for component DCI 706. Component DCIs 702, 704, and 706 may then be combined into a payload 714 of the same size (e.g., 120 bits each), and then jointly encoded using one CRC 712.

[0073] By utilizing zero padding, since the length of each component DCI is equal, the first DCI part (e.g., DCI in PDDCH) can indicate to the UE (e.g., in the auxiliary information part) how many component DCIs are included in the DCI piggyback, rather than indicating the length of each component DCI in the DCI piggyback. This may reduce the overhead size of the first DCI part, and the number of component DCIs in the DCI piggyback can be quantized.

[0074] Information related to the joint coding of multiple component DCIs (e.g., the size of the coding and the number of component DCIs, etc.) can be included in the first DCI part together with other DCI piggyback related information (e.g., piggyback control information). For example, the beta offset of the decoding rate control can be used to indicate the length and decoding rate of the DCI. Therefore, for larger DCI piggyback lengths (e.g., combined component DCIs), the base station can use the beta offset to indicate to the UE to use a higher decoding rate to reduce the resources used. Alternatively, information related to DCI piggybacking and component DCIs can also be RRC configured, such as within the content of the piggyback control field.

[0075] Since different DCI formats may provide different DCI lengths, the UE receiving the DCI can first perform blind decoding by monitoring DCI of different lengths. If the length of the received DCI matches one of the monitoring lengths, for DCI of the same length, the UE can try different RNTIs to determine whether the DCI (e.g., PDCCH) carries its control information. Different DCI formats can be distinguished based on the length of the DCI and its CRC scrambling. For example, when its length matches, the UL / DL mark can be marked between DCI formats 1_1 and 0_1. Similarly, when its length matches, the UL / DL mark can be marked between DCI formats 1_0 and 0_0. However, for DCI formats between 1_1 / 0_1 and 1_0 / 0_0, the DCI lengths between them may always be different, where, if necessary, 1-bit fillers can also be used to make them different. In addition, for DCIs with the same DCI format, different RNTI scrambling may result in different interpretations such as between C-RNTI and configured scheduling-RNTI (CS-RNTI). Therefore, if zero padding is applied to multiple component DCIs to match their lengths, and these multiple component DCIs are aggregated (eg, combined), a UE receiving the aggregated component DCI may not be able to distinguish the DCI format of each component DCI in some cases.

[0076] To avoid this, in one example, a configurable header may be included in each component DCI (e.g., 702, 704, 706) to indicate its RNTI and DCI format combination. For example, a two-bit header may be used, where 0 (e.g., bit 00) may indicate a non-fallback C-RNTI, 1 (e.g., bit 01) may indicate a fallback C-RNTI, and / or 2 (e.g., bit 10) may indicate a non-fallback CS-RNTI, etc. This may optionally be RRC configured for the UE, or the rules may be hard-coded (e.g., embedded in the source code). Therefore, after the UE decodes the combined payload (e.g., 714) using the CRC (e.g., 712) based on the configurable header in each component DCI (e.g., 702, 704, 706), the UE may determine the RNTI and DCI format combination for each component DCI. In some examples, fallback DCI or fallback component DCI may refer to DCI used in LTE, and non-fallback DCI or non-fallback component DCI may refer to DCI used in NR.

[0077] In another example, in order to enable the UE to distinguish the DCI format of each component DCI, the types of component DCI that may be included in the DCI piggyback may be limited or defined. For example, the fallback component DCI may be excluded from the DCI piggyback. For example, optimizing the efficiency of fallback DCI delivery may be less important. Therefore, the UE receiving the DCI piggyback can determine that the component DCI in the DCI piggyback is not the fallback component DCI. In other examples, only the C-RNTI-based DCI may be included in the DCI piggyback so that the UE receiving the DCI piggyback can determine that the component DCI is based on the C-RNTI. Since configurations or parameters such as configured grant (CG) and SPS activation may be time-critical, they may not need to be included in the DCI piggyback.

[0078] In some cases, multiple component DCIs may be sent for the same UE, and there may not be enough space to send the PDSCH data. In other cases, the PDSCH payload size may not take into account DCI piggybacking in a particular network, as it may have a severe impact on PDSCH decoding. Various aspects presented herein may be used to avoid or mitigate such situations. In one example, a special transmission mode may be configured for a base station or a transmitting entity, where the PDSCH may be configured to carry DCI piggybacking without carrying any data transport blocks (TBs). Figure 8 8 is an example diagram 800 showing a PDSCH region 810 carrying a DCI piggyback 808 without any TBs. Figure 4 , the DCI piggyback 404 occupies a portion of the PDSCH region 410, and the data TB can be sent in the downlink traffic 406 portion of the PDSCH region 410. Figure 8 In the embodiment of the present invention, the DCI piggyback 808 may occupy the entire PDSCH region 810, while the PDSCH may not carry any TBs. This configuration may be indicated by a special field or field combination in the first DCI part 802. For example, a special value may be configured in the DCI piggyback control information field of the first DCI part 802. Other values ​​of the DCI piggyback control information field may also be used to indicate a combination of the beta factor and the number of component DCIs. This configuration may reduce potential conflicts between the DCI piggyback and the PDSCH data TBs when the DCI piggyback may take up too much space or the DCI piggyback may affect PDSCH decoding.

[0079] Although multiple component DCIs may be aggregated together to form a codeword (e.g., a combined payload 614, 714 and its respective CRC 612, 712), different component DCIs in a DCI piggyback may have different purposes, requirements, and / or intended uses. For example, different groups of component DCIs may have different levels of reliability requirements, some of which may be intended for URLLC, while other component DCIs may be intended for eMBB, etc. In addition, different groups of component DCIs may also have different matching sizes (e.g., as combined with Figure 7 As described above, some may be 100 bits long and others may be 120 bits long). The sizes between fallback DCI and non-fallback DCI may also differ. Therefore, in some cases, it may be beneficial to group component DCIs with similar purposes, requirements, and / or intended uses into the same codeword (e.g., combined payload). In addition, polar codes (e.g., as combined with Figure 6 The DCI piggyback may be limited in length and the number of DCI payloads it can carry. In some cases, the control information in the DCI piggyback may take up too many bits, so that there may not be enough space to include all the information in one control codeword. For example, when there are too many component DCIs, a long polar code may be split into multiple groups.

[0080] In one example, multiple codewords (eg, combined component DCIs) may be configured for multiple (eg, up to 2) DCI piggybacks in PDSCH. Each DCI piggyback may be polarity coded, and the codewords may be rate matched in sequence. Fig.9A 900A illustrates the use of separate control fields for multiple codewords, where each codeword may be a set of component DCIs in a DCI piggyback. For example, a first DCI portion 902 may include separate control fields 912, 914, where a first control field 912 may be used to indicate control information for a codeword in a first DCI piggyback 904, and a second control field 914 may be used to indicate control information for a codeword in a second DCI piggyback 916. The configuration of the control fields 912, 914 may be different, such as using a set of beta factors. The control field for each codeword may also indicate a null codeword (e.g., when there is no corresponding DCI piggyback). Alternatively, as Fig. 9B As shown in diagram 900B in FIG. 1 , a single control field 912 may be included in the first DCI part 902, and the first control field 912 may be used to indicate control information of the codewords in the first DCI piggyback 904. The first DCI piggyback 904 may include another piggyback control field 914, which may be used to indicate control information of the second DCI piggyback 916. Similarly, the piggyback control field 914 in the first DCI piggyback 902 may indicate that there is no additional DCI piggyback (e.g., when there is no second DCI piggyback 916).

[0081] Fig.10 1 is a flow chart of a method 1000 for wireless communication. The method may be performed by a base station or a component of a base station (e.g., a base station 102, 180, 310; a processing system, which may include a memory 376 and may be the entire base station 310 or a component of the base station 310, such as a TX processor 316, an RX processor 370, and / or a controller / processor 375). Optional aspects are shown with dashed lines. The method may enable a base station to send DCI in multiple parts. For example, a first DCI part may be sent within a PDCCH region and a second DCI part may be sent within a PDSCH. The first DCI part may include initial control information for a downlink allocation and may also include control information about a second DCI part. The second DCI part may include multiple component DCIs, and each component DCI may include remaining control information about a downlink allocation.

[0082] At 1002, a base station may send a first DCI part (eg, 402, 802, 902) in a PDCCH (eg, 408, 808, 908), wherein the first DCI part indicates a second DCI part, such as in conjunction with Figure 4 , 8 and 9. For example, the first DCI part may be sent in the PDCCH region. The first DCI part may include initial control information for downlink allocation and may also include control information about the second DCI part. The transmission of the first DCI part may be, for example, by Fig.11 The first DCI part component 1108 and / or the sending component 1106 of the apparatus 1102 in the apparatus 1102 may be performed. The base station may indicate in the first DCI part of the PDCCH a number of component DCIs (e.g., 502, 504, 506, 602, 604, 606, 702, 704, 706) that may be transmitted in the second DCI part (e.g., 404, 510, 610, 710, 804, 904). The second DCI part may include a header that indicates a DCI format and RNTI combination for each of the plurality of component DCIs, such as in combination with Figure 7 described.

[0083] At 1004, the base station may position each of the component DCIs with zero padding (e.g., 716, 718) based on the longest DCI length monitored by the UE, such as in conjunction with Figure 7 The positioning can be done, for example, by Fig.11The location component 1112 of the device 1102 in the base station may be executed. The padding may be applied to one or more of the plurality of component DCIs based on the DCI length (e.g., the longest DCI length monitored by the UE). For example, if the longest DCI length that the UE is configured to monitor is 100 bits, the base station may add zero padding to the component DCI that is less than 100 bits to make it 100 bits in length. The base station may then send an indication of the (e.g., longest) DCI length to the UE, where the DCI length may be jointly encoded with a beta offset for decoding rate control, such as in combination with Figure 7 Alternatively or additionally, the base station may configure the DCI length for the UE in RRC signaling.

[0084] At 1006, the base station may jointly encode multiple component DCIs, each of which may provide resource allocations in conjunction with the first DCI portion, such as in conjunction with Figure 5-7 In some examples, the second DCI part may not include one or more types of (multiple) DCIs, which may be defined or configured by the network. For example, the base station may be configured to not include DCI (such as fallback DCI and / or non-C-RNTI based DCI) in the second DCI part, such as by setting a filtering mechanism and / or rules (e.g., by programming). Filtering may also be performed by an exclusion component of the base station (such as Fig.11 The exclusion component 1116 of the device 1102 in is executed.

[0085] The joint encoding can be done, for example, by Fig.11 The base station may jointly encode multiple component DCIs using a single CRC (e.g., 612, 712), such as in combination with Figure 6 and 7 In the above, the CRC can be encrypted using the joint RNTI. In addition, the base station can use a single polarization code to jointly encode multiple component DCIs, such as combining Figure 6 Each of the plurality of component DCIs in the second DCI part may allocate resources for at least one of: PDSCH transmission, PUSCH, PUCCH, CSI-RS, or SRS.

[0086] In some examples, the base station may first jointly encode multiple component DCIs to form a first codeword (eg, Fig.9A and 9B The base station may jointly encode additional sets of multiple component DCIs to form a second codeword (eg, Fig.9A and 9B Component DCI of the grouping in 916), such as combined Fig.9A and 9BThe second codeword may be sent in the PDSCH (e.g., 910) together with the first codeword in the second DCI part, such as in combination with Fig.9A and 9B The first codeword and the second codeword may be polarity encoded and sequentially mapped. The first DCI part (e.g., 902) may include a field having configuration information (e.g., 912, 914) of the first codeword and the second codeword, such as in combination with Fig.9A Alternatively, the first DCI part (e.g., 902) may include first configuration information for the first codeword (e.g., 912), and the second DCI part includes second configuration information for the second codeword (e.g., 914), as described in conjunction with Fig. 9B In a configuration with multiple codewords, the first DCI part may include configuration information for a codeword formed based on multiple component DCIs encoded jointly, and the second DCI part includes an indication that no additional component DCI is included in the PDSCH, such as in combination with Fig.9A and 9B described.

[0087] At 1008, the base station may transmit a second DCI part (e.g., 410, 810, 910) in the PDSCH including the jointly encoded multiple component DCIs. The second DCI part may be transmitted within the PDSCH. The second DCI part may include multiple component DCIs, and each component DCI may include the remaining control information about the downlink assignment. The transmission of the second DCI part may be, for example, by Fig.11 The second DCI part component 1110 and / or the sending component 1106 of the apparatus 1102 in the embodiment are performed. In some examples, the base station can send the second DCI part in the PDSCH without data, such as in combination with Figure 8 For example, the PDSCH may contain only the second DCI part without any user data. In this case, the first DCI part may indicate to the UE that the second DCI part will be sent in the PDSCH without data.

[0088] Fig.11 1100 is a conceptual data flow diagram illustrating data flow between different parts / components in an example apparatus 1102. The apparatus may be a base station or a component of a base station. The apparatus 1102 includes a receiving component 1104 that receives uplink communications from a UE 1150; and a transmitting component 1106 that transmits downlink communications to the UE 1150. The apparatus 1102 includes a first DCI part component 1108 that is configured to transmit a first DCI part in a PDCCH, e.g., as in conjunction with Fig.10The apparatus 1102 includes an encoding component 1114 configured to jointly encode a plurality of component DCIs, each of which is combined with the first DCI part to provide a resource allocation, such as in combination with Fig.10 The apparatus 1102 includes a second DCI part component 1110 configured to transmit a second DCI part including a plurality of component DCIs jointly coded in a PDSCH, for example, as combined with Fig.10 The apparatus 1102 includes a location component 1112 configured to locate each of the components of the DCI, for example, as described in conjunction with Fig.10 The apparatus 1102 includes an exclusion component 1116 configured to exclude one or more types of DCI from the second DCI portion, for example, as described in conjunction with Fig.10 As described in 1006.

[0089] The device 1102 may include executing Fig.10 Each of the blocks in the algorithm in the preceding flowchart is an additional component. Therefore, Fig.10 Each of the blocks in the foregoing flow charts and various aspects performed by the base station 102, 180, 310 may be performed by at least one component of the apparatus, each of which is one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process or algorithm, and stored in a computer-readable medium for implementation by the processor or some combination thereof. The component may be a software component that runs in the processor and resides / stored in a computer-readable medium / memory, one or more hardware components coupled to the processor, or some combination thereof. The system may be a component of the base station 310 and may include a memory 376 and / or at least one of the TX processor 316, the RX processor 370, and the controller / processor 375. Alternatively, the processing system may be the entire base station (e.g., see Figure 3 310).

[0090] Fig.121200 is a diagram illustrating an example of a hardware implementation for an apparatus 1102' employing a processing system 1214. The processing system 1214 may be implemented using a bus architecture, which is generally represented by a bus 1224. The bus 1224 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1214. The bus 1224 links together various circuits including one or more processors and / or hardware components, represented by the processor 1204, components 1104, 1106, 1108, 1110, 1112, 1114, 1116, and computer readable medium / memory 1206. The bus 1224 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be described in detail.

[0091] The processing system 1214 may be coupled to the transceiver 1210. The transceiver 1210 is coupled to one or more antennas 1220. The transceiver 1210 provides a means for communicating with various other devices over a transmission medium. The transceiver 1210 receives signals from the one or more antennas 1220, extracts information from the received signals, and provides the extracted information to the processing system 1214, particularly the receiving component 1104. In addition, the transceiver 1210 receives information from the processing system 1214 (particularly the transmitting component 1106), and based on the received information, generates signals to be applied to the one or more antennas 1220. The processing system 1214 includes a processor 1204 coupled to a computer-readable medium / memory 1206. The processor 1204 is responsible for general processing, including executing software stored on the computer-readable medium / memory 1206. When executed by the processor 1204, the software causes the processing system 1214 to perform the various functions described above for any particular device. The computer-readable medium / memory 1206 may also be used to store data that is manipulated by the processor 1204 when executing software. The processing system 1214 also includes at least one of the components 1104, 1106, 1108, 1110, 1112, 1114, 1116. The component may be a software component that runs in the processor 1204 and resides / stored in the computer-readable medium / memory 1206, one or more hardware components coupled to the processor 1204, or some combination thereof. The processing system 1214 may be a component of the base station 310 and may include the memory 376 and / or at least one of the TX processor 316, the RX processor 370, and the controller / processor 375. Alternatively, the processing system 1214 may be the entire base station (e.g., see Figure 3 310).

[0092] In one configuration, an apparatus for wireless communication at a base station may include means for transmitting a first DCI part in a PDCCH; means for jointly encoding a plurality of component DCIs, wherein each of the component DCIs provides a resource allocation in conjunction with the first DCI part; and means for transmitting a second DCI part in a PDSCH comprising the jointly encoded plurality of component DCIs, e.g., in conjunction with Figure 4-9B The aforementioned components may be one or more of the aforementioned components of the device and / or the processing system of the device, and the device is configured to perform the functions described by the aforementioned components. As described above, the processing system may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the aforementioned components may be a TX processor 316, an RX processor 370, and a controller / processor 375 configured to perform the functions described by the aforementioned components.

[0093] Fig.13 1300 is a flow chart of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., UE 104, 350; a processing system, which may include a memory 360 and may be the entire UE 350 or a component of the UE 350, such as a TX processor 368, an RX processor 356, and / or a controller / processor 359). Optional aspects are shown with dashed lines. The method may enable a UE to receive and decode DCI in multiple parts. For example, a UE may receive a first DCI part in a PDCCH and a second DCI part or more in a PDSCH. The first DCI part may include initial control information for a downlink allocation and may also include control information about a second DCI part. The second DCI part may include multiple component DCIs, and each component DCI may include remaining control information about a downlink allocation.

[0094] At 1302, the UE may receive a first DCI part (eg, 402, 802, 902) in a PDCCH (eg, 408, 808, 908), as described in conjunction with Figure 4 , 8 and 9. For example, the UE may receive a first DCI part in the PDCCH and a second DCI part in the PDSCH or more. The first DCI part may include initial control information for downlink allocation and may also include control information about the second DCI part. Reception of the first DCI part may be performed, for example, by Fig.14 The decoding of the first DCI part can be performed by the receiving component 1404 and / or the first DCI part receiving component 1408 of the device 1402 in the embodiment. Fig.14 The decoding component 1412 of the device 1402 is executed.

[0095] In addition, as shown in 1304, the first DCI part may include an indication of several component DCIs that may be transmitted by the base station in the second DCI part, such as in combination with Figure 7 The receipt of the indication may be, for example, by Fig.14 In some examples, each of the component DCIs may be positioned using (multiple) zero padding (e.g., 716, 718) based on the longest DCI length monitored by the UE. For example, one or more of the multiple component DCIs may be padded based on the DCI length (e.g., the longest DCI length monitored by the UE), such as in combination with Figure 7 The UE may receive an indication of the DCI length from the base station, wherein the indication of the DCI length may be jointly encoded with a beta offset for decoding rate control, such as in combination with Figure 7 Alternatively or additionally, the UE may receive the configuration of the DCI length in RRC signaling. The reception of the first RRC configuration may be performed by, for example Fig.14 The receiving component 1404 of the device 1402 is executed, and the RRC configuration can be performed by Fig.14 The RRC configuration component 1414 of the device 1402 is executed.

[0096] At 1306, the UE may receive a second DCI part (e.g., 404, 510, 610, 710, 804, 904) in a PDSCH (e.g., 410, 810, 910), the second DCI part including a plurality of component DCIs (e.g., 502, 504, 506, 602, 604, 606, 702, 704, 706) that are jointly encoded, each of the component DCIs may provide a resource allocation in conjunction with the first DCI part, such as in conjunction with the first DCI part. Figure 5-7 The reception of the second DCI part may be performed, for example, by Fig.14 The decoding of the second DCI part can be performed by the receiving component 1404 and / or the second DCI part receiving component 1410 of the device 1402 in the embodiment. Fig.14 The decoding component 1412 of the device 1402 in the second DCI part may include multiple component DCIs, and each component DCI may include remaining control information about the downlink allocation. The received multiple component DCIs may be jointly encoded using a single CRC, and the CRC may be scrambled using the RNTI. In addition, the multiple component DCIs are jointly encoded using a single polar code, such as in combination with Figure 6In some examples, the UE may receive the second DCI part in a PDSCH, where the PDSCH may not contain any user data. In other examples, the second DCI part may include a header indicating a DCI format and RNTI combination for each of the multiple component DCIs, such as in combination with Figure 7 Based on the allocation information decoded from the first DCI part and / or the second DCI part, the UE may send data to the base station based on the allocation information. The transmission may be performed, for example, by Fig.14 The sending component 1406 of the device 1402 is executed.

[0097] In some examples, multiple component DCIs are jointly encoded to form a first codeword (e.g., Fig.9A and Fig. 9B 904 of the grouped component DCI), and additional sets of multiple component DCIs may be jointly encoded to form a second codeword (e.g., the component DCI of the grouped component in 916), such as in combination Fig.9A and 9B The UE may receive the second codeword in the PDSCH together with the first codeword in the second DCI part. The first codeword and the second codeword may be polarity encoded and sequentially mapped. When multiple codewords are included, the first DCI part (e.g., 902) includes a field having configuration information (e.g., 912, 914) of the first codeword and the second codeword, such as in combination with Fig.9A Alternatively, the first DCI part (e.g., 902) may include first configuration information for the first codeword (e.g., 912), and the second DCI part may include second configuration information for the second codeword (e.g., 914). The first DCI part may include configuration information for a codeword formed based on a plurality of component DCIs encoded jointly, and the second DCI part may include an indication that no additional component DCI is included in the PDSCH, such as in combination with Fig.9A and 9B described.

[0098] Fig.14 1400 is a conceptual data flow diagram illustrating data flow between different parts / components in an example apparatus 1402. The apparatus may be a UE or a component of a UE. The apparatus 1102 includes a receiving component 1404 that receives downlink communications from a base station 1450; and a transmitting component 1406 that transmits uplink communications to the base station 1450. The apparatus 1402 includes a first DCI part receiving component 1408 that is configured to receive a first DCI part in a PDCCH, e.g., as in conjunction with Fig.13The apparatus 1402 includes a decoding component 1412 configured to decode a DCI (e.g., a first DCI part and / or a second DCI part). The decoded first DCI part may include an indication of several component DCIs to be transmitted in the second DCI part, such as in combination with Fig.13 The apparatus 1402 includes a second DCI part receiving component 1410, which is configured to receive a second DCI part including a plurality of component DCIs jointly encoded in a PDSCH, for example, as combined with Fig.13 The apparatus 1402 includes an RRC configuration component 1414 configured to receive RRC signaling and configure the UE based on the RRC signaling, for example, to determine the length of each component DCI.

[0099] The device 1402 may include executing Fig.13 Each of the additional components in the algorithm box in the preceding flowchart. In this way, Fig.13 Each of the blocks in the foregoing flow charts and the various aspects performed by UE 104, 350 may be performed by a component, and the apparatus may include one or more of these components. These components may be one or more hardware components that are specifically configured to perform the processing / algorithms, implemented by a processor configured to perform the processing / algorithms, stored in a computer-readable medium for implementation by a processor, or some combination of these. The system may be a component of UE 350, which may include memory 360, TX processor 368, RX processor 356, and controller / processor 359. Alternatively, the processing system may be the entire UE (e.g., see Figure 3 of 350).

[0100] Fig.15 1500 is a diagram illustrating an example of a hardware implementation for an apparatus 1402' employing a processing system 1514. The processing system 1514 may be implemented using a bus architecture, which is generally represented by a bus 1524. The bus 1524 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1514. The bus 1524 links together various circuits including one or more processors and / or hardware components, represented by the processor 1504, components 1404, 1406, 1408, 1410, 1412, 1414, and computer readable medium / memory 1506. The bus 1524 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be described in detail.

[0101] The processing system 1514 may be coupled to the transceiver 1510. The transceiver 1510 is coupled to one or more antennas 1520. The transceiver 1510 provides components for communicating with various other devices over a transmission medium. The transceiver 1510 receives signals from the one or more antennas 1520, extracts information from the received signals, and provides the extracted information to the processing system 1514, particularly the receiving component 1404. In addition, the transceiver 1510 receives information from the processing system 1514 (particularly the transmitting component 1406), and based on the received information, generates signals to be applied to the one or more antennas 1520. The processing system 1514 includes a processor 1504 coupled to a computer-readable medium / memory 1506. The processor 1504 is responsible for general processing, including executing software stored on the computer-readable medium / memory 1506. When executed by the processor 1504, the software causes the processing system 1514 to perform the various functions described above for any particular device. The computer-readable medium / memory 1506 may also be used to store data that is manipulated by the processor 1504 when executing software. The processing system 1514 also includes at least one of the components 1404, 1406, 1408, 1410, 1412, and 1414. These components may be software components that run in the processor 1504 and reside / stored in the computer-readable medium / memory 1506, one or more hardware components coupled to the processor 1504, or some combination thereof. The processing system 1514 may be a component of the UE 350 and may include the memory 360, the TX processor 368, the RX processor 356, and the controller / processor 359. Alternatively, the processing system may be the entire UE (e.g., see Figure 3 of 350).

[0102] In one configuration, an apparatus for wireless communication at a UE may include means for receiving a first DCI part in a PDCCH; and means for receiving a second DCI part in a PDSCH including a plurality of component DCIs jointly encoded, each of the component DCIs providing a resource allocation in conjunction with the first DCI part, e.g., as in conjunction with Figure 4-9B The aforementioned components may be one or more of the aforementioned components of the device and / or the processing system of the device, and the device may be configured to perform the functions described by the aforementioned components. The processing system may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the aforementioned components may be a TX processor 368, an RX processor 356, and a controller / processor 359, which are configured to perform the functions described for the aforementioned components.

[0103] The following examples are merely illustrative, and aspects thereof may be combined with aspects or teachings of other embodiments described herein without limitation.

[0104] Example 1 is a method for performing wireless communications at a base station, comprising: sending a first DCI part in a PDCCH, wherein the first DCI part indicates a second DCI part; jointly encoding multiple component DCIs, each of the component DCIs providing resource allocation in conjunction with the first DCI part; and sending a second DCI part including the jointly encoded multiple component DCIs in a PDSCH.

[0105] In Example 2, the method of Example 1 also includes allocating resources for each of the multiple component DCIs included in the second DCI part for at least one of: PDSCH transmission, physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), channel state information reference signal (CSI-RS), or sounding reference signal (SRS).

[0106] In Example 3, the method of Example 1 or Example 2 further includes the base station jointly encoding the multiple component DCIs with a single CRC.

[0107] In Example 4, the method of any of Examples 1-3 further includes scrambling the CRC with a joint RNTI.

[0108] In Example 5, the method of any one of Examples 1-4 further includes the base station jointly encoding multiple component DCIs using a single polarization code.

[0109] In Example 6, the method of any one of Examples 1-5 further includes padding each of the positioning component DCIs with zeros based on a longest DCI length monitored by the UE.

[0110] In Example 7, the method of any one of Examples 1-6 further includes the first DCI part including an indication of a number of component DCIs to be transmitted in the second DCI part.

[0111] In Example 8, the method of any one of Examples 1-7 further includes padding one or more of the plurality of component DCIs based on a DCI length.

[0112] In Example 9, the method of any one of Examples 1-8 also includes the DCI length being a longest DCI length monitored by the UE.

[0113] In Example 10, the method of any one of Examples 1-9 further includes sending an indication of the DCI length to the UE.

[0114] In Example 11, the method of any one of Examples 1-10 further includes the indication of the DCI length being jointly encoded with a beta offset for coding rate control.

[0115] In Example 12, the method of any one of Examples 1-11 further includes configuring the DCI length for the UE in radio resource control signaling.

[0116] In Example 13, the method of any one of Examples 1-12 further includes the second DCI part comprising a header indicating a DCI format and RNTI combination for each of the plurality of component DCIs.

[0117] In Example 14, the method of any one of Examples 1-13 further includes the second DCI portion not including one or more types of DCI.

[0118] In Example 15, the method of any one of Examples 1-14 further includes the base station excluding one or more of the fallback DCI or the non-C-RNTI based DCI from the second DCI part.

[0119] In Example 16, the method of any one of Examples 1-15 further includes the PDSCH not including user data.

[0120] In Example 17, the method of any one of Examples 1-16 further includes the first DCI part indicating that the PDSCH does not include user data.

[0121] In Example 18, the method of any one of Examples 1-17 further includes jointly encoding multiple component DCIs to form a first codeword, and the method further includes jointly encoding an additional set of the multiple component DCIs to form a second codeword, wherein the second codeword is sent in the PDSCH together with the first codeword in the second DCI part.

[0122] In Example 19, the method of any one of Examples 1-18 further includes the first codeword and the second codeword being polarity encoded and sequentially mapped.

[0123] In Example 20, the method of any one of Examples 1-19 further includes the first DCI part including a field having configuration information for the first codeword and the second codeword.

[0124] In Example 21, the method of any one of Examples 1-20 further includes the first DCI part including first configuration information for the first codeword, and the second DCI part including second configuration information for the second codeword.

[0125] In Example 22, the method of any one of Examples 1-21 further includes the first DCI part including configuration information of a codeword formed based on the jointly encoded multiple component DCIs, and the second DCI part including an indication that no additional component DCI is included in the PDSCH.

[0126] Example 23 is an apparatus for wireless communication at a base station, comprising a component for sending a first DCI part in a PDCCH; a component for jointly encoding multiple component DCIs, wherein each of the component DCIs provides a resource allocation in conjunction with the first DCI part; and a component for sending a second DCI part including the jointly encoded multiple component DCIs in a PDSCH.

[0127] In Example 24, the apparatus of Example 23 further includes components for performing the method of any one of claims 2-22.

[0128] Example 25 is an apparatus for wireless communication at a base station, comprising a memory and at least one processor coupled to the memory, the memory and the at least one processor being configured to: send a first DCI part in a PDCCH; jointly encode multiple component DCIs, wherein each of the component DCIs provides resource allocation in conjunction with the first DCI part; and send a second DCI part in a PDSCH including the jointly encoded multiple component DCIs.

[0129] In Example 26, the apparatus of Example 25 further includes the memory and the at least one processor being further configured to execute the method of any one of claims 2-22.

[0130] Example 27 is a non-transitory computer-readable medium storing computer-executable code for wireless communication at a base station, which code, when executed by a processor, causes the processor to perform the method of any one of claims 1-22.

[0131] Example 28 is a method of performing wireless communications at a UE, comprising receiving a first DCI part in a PDCCH; and receiving a second DCI part in a PDSCH comprising a plurality of component DCIs jointly encoded, each of the component DCIs providing a resource allocation in conjunction with the first DCI part.

[0132] In Example 29, the method of Example 28 further includes jointly encoding the multiple component DCIs using a single CRC.

[0133] In Example 30, the method of Example 28 or Example 29 further includes scrambling the CRC with a joint RNTI.

[0134] In Example 31, the method of any one of Examples 28-30 further includes jointly encoding the multiple component DCIs using a single polar code.

[0135] In Example 32, the method of any one of Examples 28-31 further includes padding the positioning component DCI with zeros based on a longest DCI length monitored by the UE.

[0136] In Example 33, the method of any one of Examples 28-32 further includes the first DCI part in the PDCCH including an indication of a number of component DCIs to be transmitted in the second DCI part.

[0137] In Example 34, the method of any one of Examples 28-33 further includes padding one or more of the multiple component DCIs based on the DCI length.

[0138] In Example 35, the method of any one of Examples 28-34 also includes the DCI length being a longest DCI length monitored by the UE.

[0139] In Example 36, the method of any one of Examples 28-35 further includes receiving an indication of a DCI length from a base station.

[0140] In Example 37, the method of any one of Examples 28-36 further includes the indication of the DCI length being jointly encoded with a beta offset for coding rate control.

[0141] In Example 38, the method of any one of Examples 28-37 further includes receiving a configuration of a DCI length in radio resource control signaling.

[0142] In Example 39, the method of any one of Examples 28-38 further includes: the second DCI part includes a header indicating a DCI format and RNTI combination for each of the plurality of component DCIs.

[0143] In Example 40, the method of any one of Examples 28-39 further includes: the PDSCH carrying the second DCI part does not include user data.

[0144] In Example 41, the method of any one of Examples 28-40 further includes: the first DCI part indicating that the PDSCH carrying the second DCI part does not contain user data.

[0145] In Example 42, the method of any one of Examples 28-41 further includes: multiple component DCIs are jointly encoded to form a first codeword, and the method further includes receiving a second codeword based on an additional set of jointly encoded multiple component DCIs, wherein the second codeword is received together with the first codeword in a second DCI part in the PDSCH.

[0146] In Example 43, the method of any one of Examples 28-42 further includes: the first codeword and the second codeword are polarity encoded and sequentially mapped.

[0147] In Example 44, the method of any one of Examples 28-43 further includes: the first DCI part includes a field having configuration information for the first codeword and the second codeword.

[0148] In Example 45, the method of any one of Examples 28-44 further includes: the first DCI part includes first configuration information for the first codeword, and the second DCI part includes second configuration information for the second codeword.

[0149] In Example 46, the method of any one of Examples 28-45 further includes: the first DCI part includes configuration information of a codeword formed based on the jointly encoded multiple component DCIs, and the second DCI part includes an indication that no additional component DCI is included in the PDSCH.

[0150] Example 47 is an apparatus for wireless communication at a UE, comprising: a component for receiving a first DCI part in a PDCCH; and a component for receiving a second DCI part in a PDSCH including a plurality of component DCIs jointly encoded, each of the component DCIs providing resource allocations in conjunction with the first DCI part.

[0151] In Example 48, the apparatus of Example 47 further includes: a component for executing the method of any one of claims 29-46.

[0152] Example 49 is an apparatus for performing wireless communications at a UE, comprising: a memory and at least one processor coupled to the memory, the memory and the at least one processor being configured to receive a first DCI part in a PDCCH; and receiving a second DCI part in a PDSCH comprising a plurality of component DCIs jointly encoded, each of the component DCIs providing resource allocations in conjunction with the first DCI part.

[0153] In Example 50, the apparatus of Example 49 further includes: the memory and the at least one processor are further configured to execute the method of any one of claims 28-45.

[0154] Example 51 is a non-transitory computer-readable medium storing a computer-executable code for wireless communication at a UE, which, when executed by a processor, causes the processor to perform the method of any one of claims 28-46.

[0155] It should be understood that the specific order or hierarchy of each frame in the disclosed process / flowchart is an illustration of an example scheme. Based on design preferences, it should be understood that the specific order or hierarchy of each frame in the process / flowchart can be rearranged. In addition, some frames can be combined or omitted. The attached method claims present the elements of each frame in a sample order and are not meant to be limited to the specific order or hierarchy presented.

[0156] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. For those skilled in the art, various modifications to these aspects will be apparent, and the general principles defined herein can be applied to other aspects. Therefore, the present claim is not intended to be limited to the various aspects shown herein, but to conform to the full scope consistent with the language claim, wherein, unless otherwise specified, the singular reference element is not intended to represent "one and only one", but to represent "one or more". The word "exemplary" is used herein to represent "used as an example, instance, or explanation". Any aspect described as "exemplary" herein does not have to be interpreted as being superior to or advantageous to other aspects. Unless otherwise clearly stated, the term "some" refers to one or more. 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, phrases 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 only A, only B, only C, 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 throughout the various aspects described in this disclosure that are known or will be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be included by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. The words "module," "mechanism," "element," "device," and the like may not replace the word "component." Therefore, unless a claim element is explicitly recited using the phrase "component for...", any claim element should not be interpreted as a component plus function.

Claims

1. A method for wireless communication at a base station, comprising: Sending a first downlink control information (DCI) part in a physical downlink control channel (PDCCH), wherein the first DCI part indicates a second DCI part; combining a plurality of component DCIs into a single payload, each of the component DCIs providing a resource allocation in conjunction with the first DCI part; jointly encoding the single payload using a single cyclic redundancy check (CRC); as well as The second DCI part including a jointly coded single payload is transmitted in a physical downlink shared channel, PDSCH.

2. The method according to claim 1, wherein: Each of the plurality of component DCIs included in the second DCI part allocates resources for at least one of: PDSCH transmission, Physical uplink shared channel PUSCH, Physical uplink control channel PUCCH, Channel State Information Reference Signal CSI-RS, or Sounding Reference Signal SRS.

3. The method according to claim 1, wherein: The CRC is scrambled using a joint radio network temporary identifier, RNTI.

4. The method according to claim 1, wherein: The base station jointly encodes the multiple component DCIs using a single polarization code.

5. The method according to claim 1, further comprising: Based on the longest DCI length monitored by the user equipment UE, each of the positioning component DCIs is padded with zeros.

6. The method according to claim 1, wherein: The first DCI part includes an indication of a number of component DCIs to be transmitted in the second DCI part.

7. The method according to claim 6, further comprising: One or more of the plurality of component DCIs are padded based on a DCI length.

8. The method according to claim 7, wherein: The DCI length corresponds to the longest DCI length monitored by the user equipment UE.

9. The method according to claim 7, further comprising: Sending an indication of the DCI length to a user equipment UE.

10. The method according to claim 9, wherein: The indication of the DCI length is jointly encoded with a beta offset for coding rate control.

11. The method according to claim 7, further comprising: The DCI length is configured for the user equipment UE in radio resource control signaling.

12. The method according to claim 1, wherein: The second DCI part includes a header indicating a DCI format and a Radio Network Temporary Identifier (RNTI) combination for each of the plurality of component DCIs.

13. The method according to claim 1, wherein: The second DCI part does not include one or more types of DCI.

14. The method according to claim 1, wherein: The base station excludes one or more of fallback DCI or non-cell radio network temporary identifier C-RNTI based DCI from the second DCI part.

15. The method according to claim 1, wherein: The PDSCH does not include user data.

16. The method according to claim 1, wherein: The first DCI part indicates that the PDSCH does not include user data.

17. A method for wireless communication at a base station, comprising: Sending a first downlink control information (DCI) part in a physical downlink control channel (PDCCH), wherein the first DCI part indicates a second DCI part; jointly encoding a plurality of component DCIs, each of the component DCIs providing a resource allocation in conjunction with the first DCI portion, wherein the plurality of component DCIs are jointly encoded to form a first codeword; jointly encoding an additional set of the plurality of component DCIs to form a second codeword; and The second DCI part including the jointly coded multiple component DCIs is transmitted in a physical downlink shared channel (PDSCH), wherein the second codeword is transmitted in the PDSCH together with the first codeword in a second DCI part.

18. The method according to claim 17, wherein: The first codeword and the second codeword are polarity encoded and sequentially mapped.

19. The method according to claim 17, wherein: The first DCI part includes a field having configuration information for the first codeword and the second codeword.

20. The method according to claim 17, wherein: The first DCI part includes first configuration information for the first codeword, and the second DCI part includes second configuration information for the second codeword.

21. A method for wireless communication at a base station, comprising: Sending a first downlink control information (DCI) part in a physical downlink control channel (PDCCH), wherein the first DCI part indicates a second DCI part; combining a plurality of component DCIs into a single payload, each of the component DCIs providing a resource allocation in conjunction with the first DCI part; jointly encoding the single payload using a single cyclic redundancy check (CRC); as well as The second DCI part including the jointly coded single payload is transmitted in a physical downlink shared channel (PDSCH), wherein the first DCI part includes configuration information of a codeword formed based on the jointly coded multiple component DCIs, and the second DCI part includes an indication that no additional component DCI is included in the PDSCH.

22. A method for wireless communication at a user equipment UE, comprising: Receiving a first downlink control information DCI part in a physical downlink control channel PDCCH; as well as A second DCI part is received in a physical downlink shared channel (PDSCH), the second DCI part comprising a single payload composed of a plurality of component DCIs, each of which provides a resource allocation in conjunction with the first DCI part, jointly encoded using a single cyclic redundancy check (CRC).

23. The method according to claim 22, wherein: The CRC is scrambled using a joint radio network temporary identifier, RNTI.

24. The method according to claim 22, wherein: The multiple component DCIs are jointly encoded using a single polar code.

25. The method according to claim 22, wherein: Each of the component DCIs is positioned with zero padding based on a longest DCI length monitored by the UE.

26. The method of claim 22, wherein: The first DCI part in the PDCCH includes an indication of a number of component DCIs to be transmitted in the second DCI part.

27. The method according to claim 26, wherein: One or more of the plurality of component DCIs are padded based on a DCI length.

28. The method according to claim 27, wherein: The DCI length is the longest DCI length monitored by the UE.

29. The method of claim 27, further comprising: A length indication of the DCI length is received from a base station.

30. The method of claim 29, wherein: The indication of the DCI length is jointly encoded with a beta offset for coding rate control.

31. The method of claim 27, further comprising: The configuration of the DCI length is received in radio resource control signaling.

32. The method of claim 22, wherein: The second DCI part includes a header indicating a DCI format and a Radio Network Temporary Identifier (RNTI) combination for each of a plurality of component DCIs.

33. The method of claim 22, wherein: The PDSCH carrying the second DCI part does not include user data.

34. The method of claim 22, wherein: The first DCI part indicates that the PDSCH carrying the second DCI part does not include user data.

35. A method for wireless communication at a user equipment UE, comprising: Receiving a first downlink control information DCI part in a physical downlink control channel PDCCH; receiving a second DCI part in a physical downlink shared channel (PDSCH), the second DCI part comprising a single payload composed of a plurality of component DCIs jointly encoded using a single cyclic redundancy check (CRC), each of the component DCIs providing a resource allocation in conjunction with the first DCI part, wherein the single payload is jointly encoded to form a first codeword; as well as A second codeword is received based on an additional set of joint encodings of multiple component DCIs, wherein the second codeword is received in the PDSCH along with the first codeword in the second DCI part.

36. The method of claim 35, wherein: The first codeword and the second codeword are polarity encoded and sequentially mapped.

37. The method of claim 35, wherein: The first DCI part includes a field having configuration information for the first codeword and the second codeword.

38. The method of claim 35, wherein: The first DCI part includes first configuration information for the first codeword, and the second DCI part includes second configuration information for the second codeword.

39. A method for wireless communication at a user equipment UE, comprising: Receiving a first downlink control information DCI part in a physical downlink control channel PDCCH; A second DCI part is received in a physical downlink shared channel (PDSCH), the second DCI part comprising a single payload composed of multiple component DCIs jointly encoded using a single cyclic redundancy check (CRC), each of the component DCIs providing resource allocation in conjunction with the first DCI part, wherein the first DCI part comprises configuration information of a codeword formed based on the jointly encoded multiple component DCIs, and the second DCI part comprises an indication that additional component DCI is not included in the PDSCH.

40. An apparatus for wireless communication performed at a base station, the apparatus comprising means for performing the method according to any one of claims 1-21.

41. An apparatus for wireless communication executed at a user equipment (UE), the apparatus comprising means for executing the method according to any one of claims 22-39.

42. A computer readable medium having program code recorded thereon, wherein: The program code may be executed by one or more processors of a base station, so that the one or more processors perform the method according to any one of claims 1-21.

43. A computer readable medium having program code recorded thereon, wherein: The program code may be executed by one or more processors of a user equipment UE, so that the one or more processors execute the method according to any one of claims 22-39.

Images