Multiple DCI transmitted through PDSCH

Abstract

A device obtains a downlink control information (DCI) message transmitted in a physical downlink control channel (PDCCH). The DCI message can include control information for obtaining a plurality of downlink control information (DCI) messages included in a physical downlink shared channel (PDSCH). The device receives the PDSCH including the plurality of DCI messages. The device obtains one or more of the plurality of DCI messages in the PDSCH based on the control information.

Description

TECHNICAL FIELD

[0001] The present disclosure relates generally to communication systems, and more particularly, to transmission of multiple downlink control information (DCI) over a physical downlink shared channel. BACKGROUND

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

[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is a set of enhancements to the LTE mobile standard promulgated by Third Generation Partnership Project (3GPP). It is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDMA with a cyclic prefix (CP) (OFDM). Unlike LTE, which uses orthogonal frequency-division multiplexing (OFDM) with a cyclic prefix, 5G NR uses OFDM with SUMMARY

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

[0005] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus obtains a downlink control information (DCI) message transmitted in a physical downlink control channel (PDCCH). The DCI message includes control information for obtaining a plurality of downlink control information (DCI) messages included in a physical downlink shared channel (PDSCH). The apparatus receives the PDSCH including the plurality of DCI messages. The apparatus obtains one or more of the plurality of DCI messages in the PDSCH based on the control information.

[0006] To the accomplishment of the foregoing and related ends, one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative aspects of the one or more aspects. These aspects are indicative, however, of but a few of the various ways in which the principles of various aspects can be employed and the description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF DRAWINGS

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

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

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

[0010] Figure 4 FIG. 4 is a signal flow diagram in accordance with various aspects of the disclosure.

[0011] Figure 5 FIG. 5 is a diagram illustrating downlink control information (DCI) included in a physical downlink shared channel (PDSCH) in accordance with various aspects of the disclosure.

[0012] Figure 6 FIG. 6 is a diagram illustrating separate decoding of coded blocks to obtain DCI messages included in a PDSCH in accordance with various aspects of the disclosure.

[0013] Figure 7 FIG. 7 is a diagram illustrating separate decoding of coded blocks to obtain DCI messages included in a PDSCH in accordance with various aspects of the disclosure.

[0014] Figure 8 ​​​is a diagram illustrating a single DCI message piggybacked in a PDSCH according to various aspects of the present disclosure.

[0015] Figure 9 is a flow diagram of a method of wireless communication according to various aspects of the present disclosure.

[0016] Figure 10 is a flow diagram of a method of wireless communication according to various aspects of the present disclosure.

[0017] Figure 11 is a conceptual data flow diagram illustrating the data flow between different means / components in an example apparatus.

[0018] Figure 12 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system. DETAILED DESCRIPTION

[0019] The detailed description set forth below, in connection with the appended drawings and embodiments described herinin, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0020] 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 can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0021] By way of example, an element, or any portion of an element, or any combination of elements can be implemented as a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), 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 the various functionality described throughout this disclosure. One or more processors in the processing system can execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0022] Accordingly, in one or more example embodiments, the functions described herein can be implemented in hardware, software, or any combination thereof. If implemented in software, the functions can be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that is suitable to store computer-executable instructions or data structures in the form of instructions or data

[0023] Figure 1 FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100. The wireless communications system, which can also be referred to as a wireless wide-area network (WWAN), includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G Core (5GC)). The base stations 102 can include macro cells (high power cellular base stations) and / or small cells (low power cellular base stations). The macro cells can include base stations. The small cells can include femtocells, picocells, and microcells.

[0024] The base stations 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can be connected by backhaul links 132 (e.g., S I interface) to the EPC 160. The base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can be connected by backhaul links 184 to the core network 190. In addition to other functions, the base stations 102 can perform one or more of the following functions: transfer of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 can also communicate directly or indirectly with one another (e.g., directly through backhaul links 134 or indirectly over the EPC 160 or core network 190). The backhaul links 134 can be wired or wireless.

[0025] The base stations 102 can wirelessly communicate with the UEs 104. Each of the base stations 102 can provide communication coverage for a respective geographic coverage area 110. There can be overlapping geographic coverage areas 110. For example, a small cell 102' can have a coverage area 110' that overlaps with one or more macrocells 102. A network that includes both small cell and macrocells can be known as a heterogeneous network. A heterogeneous network can also include Home Evolved Node Bs (eNBs) (HeNBs), which can provide service to a restricted group known as a closed subscriber group (CSG). The communication links 120 between the base stations 102 and the UEs 104 can include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 can use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links can be through one or more carriers, and each carrier can be a band of frequency waves having a predetermined width and can be used to transmit data between base stations 102 and UEs 104. The base stations 102 / UEs 104 can use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in the spectrum. The carriers can or can not be adjacent to each other. The allocation of carriers can be asymmetric with respect to the quantity of carriers allocated for DL versus UL (e.g., more or less carriers can be allocated for DL than for UL). The component carriers can include a primary component carrier and one or more secondary component carriers. A primary component carrier can be referred to as a primary cell (PCell) and a secondary component carrier can be referred to as a secondary cell (SCell).

[0026] Some UEs 104 can communicate using device-to-device (D2D) communication link 158. The D2D communication link 158 can use DL / UL WWAN spectrum. The D2D communication link 158 can use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication can be through a variety of wireless D2D communications systems, such as for example, FlashLinQ, WiMedia, Bluetooth, ZigBee (Zigbee), Wi-Fi based on IEEE 802.11 standards, LTE, or NR.

[0027] The wireless communications system can also include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154 in a 5 GHz unlicensed frequency spectrum. When communicating in an unlicensed frequency spectrum, the STAs 152 / AP 150 can perform clear channel assessment (CCA) prior to communicating so as to determine whether the channel is available.

[0028] The small cells 102' can operate in a licensed and / or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cells 102' can employ NR and use the same 5 GHz unlicensed frequency spectrum as used by the Wi-Fi AP 150. The small cells 102' employing NR in an unlicensed frequency spectrum can boost coverage and / or increase capacity for the access network.

[0029] The base stations 102, whether small cell 102' or large cell (e.g., macro base station), can include an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180 can operate in a traditional sub 6 GHz spectrum, in millimeter wave (mmW) frequencies, and / or near mmW frequencies in communication with the UEs 104. When the gNB 180 operates in mmW or near mmW frequencies, the gNB 180 can be referred to as a mmW base station. Extremely high frequency (EHF) is a portion of the RF in the electromagnetic spectrum. EHF has a range from 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in the EHF band can be referred to as a millimeter wave. Near mmW can extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW / near mmW radio frequency band (e.g., 3 GHz - 300 GHz) has extremely high path loss and a short range. The mmW base station 180 can utilize beamforming 182 with the UEs 104 to compensate for the extremely high path loss and short range.

[0030] The base stations 180 can transmit to the UEs 104 in one or more transmit directions 182'. The UEs 104 can receive from the base stations 180 in one or more receive directions 182". The UEs 104 can also transmit to the base stations 180 in one or more transmit directions. The base stations 180 can receive from the UEs 104 in one or more receive directions. The base station(s) 180 / UE(s) 104 can perform beam training to determine the best receive and transmit directions for each of the base station(s) 180 / UE(s) 104. The transmit and receive directions for the base station(s) 180 can or can not be the same. The transmit and receive directions for the UE(s) 104 can or can not be the same.

[0031] The EPC 160 can 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 can be in communication with a home subscriber server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation as well as other functions. The PDN gateway 172 and the BM-SC 170 are connected to the IP services 176. The IP services 176 can include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 can provide functions for MBMS user service provisioning and

[0032] The core network 190 can 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 can be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transferred

[0033] A base station can also be referred to as a gNB, NodeB, evolved NodeB (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit reception point (TRP), or some other suitable terminology. The base station 102 provides wireless access to the EPC 160 or core network 190 for the UEs 104. Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitch

[0034] Referring again to Figure 1 In some aspects, the UE 104 can be configured to obtain a downlink control information (DCI) message included in a physical downlink shared channel (PDSCH) 198.

[0035] Figure 2A FIG. 2 is a diagram 200 illustrating an example of a first subframe within a 5G / NR frame structure. Figure 2BFIG. 2 is a diagram 200 illustrating an example of DL channels within a 5G / NR subframe. The 5G / NR frame structure can be FDD, TDD, or a combination thereof. Figure 2C FIG. 2 is a diagram 200 illustrating an example of DL channels within a 5G / NR subframe. The 5G / NR frame structure can be FDD, TDD, or a combination thereof. Figure 2D FIG. 2 is a diagram 200 illustrating an example of DL channels within a 5G / NR subframe. The 5G / NR frame structure can be FDD, TDD, or a combination thereof. Figure 2A 、 Figure 2C In the examples provided, it is assumed that the 5G / NR frame structure is TDD, where subframe 4 is configured with slot format 28 (which is DL-heavy), where D is DL, U is UL, and X is flexible for use between DL / UL, and subframe 3 is configured with slot format 34 (which is UL-heavy). Although subframes 3, 4 are shown with slot format 34, slot format 28, respectively, any particular subframe can be configured with any of the various available slot formats 0 - 61. Slot formats 0, 1 are all DL, UL, respectively. The other slot formats 2 - 61 include a mixture of DL, UL, and flexible symbols. A UE is configured with a slot format (dynamically through DL control information (DCI), or semi- statically / statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the description infra also applies for 5G / NR frame structures that are TDD.

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

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

[0038] As shown in Figure 2A some of the REs carry reference (pilot) signals (RS) for the UEs. The RS can include demodulation RS (DM-RS) (indicated as R xwhere 100x is the port number, although other DM-RS configurations are possible, and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS can also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0039] Figure 2B An example of various DL channels are shown within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or several control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol. A primary synchronization signal (PSS) can be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe / symbol timing and physical layer identity. A secondary synchronization signal (SSS) can be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the aforementioned DM-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information such as system information blocks (SIBs), and paging messages.

[0040] As illustrated in Figure 2C Some of the REs carry downlink reference signals (DL-RS) for channel estimation at the UE. The DL-RS can be transmitted in the following patterns. The UE can transmit DM-RS for channel estimation at the base station in the first one or two symbols of each slot in a subframe. The UE can transmit CSI-RS for channel estimation at the UE in various patterns. The RS can also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0041] Figure 2DAn example of various UL channels is shown. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI) such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data, and can additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0042] Figure 3 FIG. 13 is a diagram of a system including an access network in accordance with some aspects of the present disclosure. The access network includes a base station 310 in communication with a UE 350. In the DL, IP packets from the EPC 160 can be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs), 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 and reporting for UEs 350; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error detection through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing / de-multiplexing of MAC SDUs onto / from transport blocks (TBs), scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0043] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, can include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations 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 a OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 can be used to determine the coding and modulation schemes, as well as for spatial processing. The channel estimate can be derived from a reference signal and / or channel condition feedback transmitted by the UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can modulate an RF carrier with a respective spatial stream for transmission.

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

[0045] The controller / processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 can be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, 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.

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

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

[0048] The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function 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.

[0049] The controller / processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 can be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 350. IP packets from the controller / processor 375 can 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.

[0050] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 can be configured to perform aspects of the methods 200 and 198 in Figure 1 FIG. 9.

[0051] A UE can transmit uplink control information (UCI) messages in a physical uplink shared channel (PUSCH). This can be referred to as piggybacking UCI messages in the PUSCH. In some examples, and as described previously, the UCI messages can include scheduling requests, channel quality indicators (CQIs), precoding matrix indicators (PMIs), rank indicators (RIs), and HARQ ACK / NACK feedback.

[0052] For rate matching of UCI messages in the PUSCH, an encoding rate offset factor β offset (e.g., β offset > 1) can be used to achieve a lower encoding rate compared to an encoding rate indicated by a modulation coding scheme (MCS) for the PUSCH. The number of resource elements (REs) per layer for the UCI message can be determined using Equation (1):

[0053]

[0054] where N RE，UCI represents the number of resource elements (REs) per layer for the UCI message, K UCI represents a payload size of the UCI message including a cyclic redundancy check (CRC) if any, β offset represents an encoding rate offset factor, K UL-SCH represents an uplink shared channel (UL-SCH) payload size including transport block (TB) / code block (CB) cyclic redundancy check (CRC) bits, and N RE represents a total number of REs per layer for the PUSCH. It should be understood that Equation (1) represents a simplified equation for determination of N RE，UCI , and in some cases, the determination of N RE，UCI may be more complex for ease of understanding.

[0055] In some examples, to prevent a UCI message from occupying too many PUSCH resources than necessary or desired, a fraction a e {0.5, 0.65, 0.8, 1.0} can be used to limit the maximum fraction of PUSCH resources that a UCI message can occupy. In these examples, N RE，UCI may be determined using Equation (2):

[0056]

[0057] Polar codes have been adopted as a channel coding technique for control channels (e.g., PDCCH) in 5G NR networks. In some examples, the maximum code block size can be 512 bits for downlink transmissions and 1024 bits for uplink transmissions. The minimum code rate can be 1 / 8. The maximum payload size without CRC can be 140 bits, and a 24-bit CRC can be appended to the payload. The rate matching scheme can include shortening, puncturing, and repetition. The decoding complexity can be expressed as O(N x log2(N)), where N is the number of coded bits. In other words, the decoding complexity can not be a direct function of the code rate. There can be a loss of coding gain in the case of more information bits.

[0058] Determinations of code block size will now be described. In one example, K can represent the number of data bits (also referred to as information bits, payload, or payload size) to be encoded. K can be a positive integer value, and the K number of data bits can be represented as a bit sequence c0, c1, c2,..., c K-1 K number of data bits can be encoded with a polar code to produce N = 2 n coded bits, where N represents the code length (also referred to as mother code size N) of the polar code. For example, the N coded bits can be represented as a bit sequence d0, d1, d2,..., d N-1 In determining the code length N = 2 n of the polar code, the value of n can be determined using Equation (3):

[0059] n = max{min{n1, n2, n max}, n min}. (Equation 3)

[0060] where n min and n max provide a lower bound and an upper bound on the code length, respectively. In some examples, for a downlink channel, n min = 5 and n max = 9. The parameter Based on the minimum coding rate R recognized by the encoder. min (For example, R) min =1 / 8) is used to set the upper limit on the encoding rate. The value of parameter n1 can depend on the rate matching scheme, and is usually defined as Where E represents the code length after rate matching (also known as the code block size). However, if and Then n1 can be defined as

[0061] In all aspects described herein, multiple DCI messages may be transmitted in the PDSCH. As used herein, the terms “DCI” and “DCI message” are interchangeable. This may be referred to as carrying DCI messages in the PDSCH. In some aspects of this disclosure, multiple DCI messages may be transmitted in the PDSCH where the PDCCH may not have sufficient resources to carry one or more of the multiple DCI messages. These situations may arise when CORESET is reduced (e.g., when the base station operates in conventional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, etc.) and when multiple DCI messages cannot be accommodated. For example, a DCI message may be an aggregation of multiple DL / UL grants. In some cases, delivering these DL / UL grants in the PDSCH may be more efficient than transmitting them in the PDCCH, which would require the UE to perform blind decoding.

[0062] When the aggregated length of multiple DCI messages to be sent to the UE exceeds the maximum 164 bits supported by the PDCCH, the transport block (TB) can be segmented into multiple code blocks (CBs). For example, one of several segmentation schemes can be used to perform the segmentation of the transport block (TB). These aggregation and segmentation schemes can improve coding gain and single protection. However, encoding each DCI message individually using a single code block can still provide acceptable performance. In this case, the UE can attempt to decode each DCI message in the individually encoded DCI messages, and can use the successfully decoded DCI messages.

[0063] The determination of the total resource size for multiple DCI messages included in the PDSCH, and the allocation of resources for each DCI message encoded in a single code block, will now be described. In some aspects of this disclosure, a base station can transmit multiple individually encoded DCI messages, along with other data, to the same UE within an allocated PDSCH area. The multiple individually encoded DCI messages can have the same size (e.g., the same code length or payload size) and can be rate-matched within the allocated PDSCH area.

[0064] Figure 4 is a signal flow diagram in accordance with various aspects of the present disclosure. As shown in Figure 4 , the base station 404 can transmit a DCI message 406 to the UE 402 in a PDCCH. For example, with reference to Figure 5 , the DCI message 406 can include DCI bits 550 and CRC bits 552. As further shown in Figure 4 , the UE 402 can obtain 408 the DCI message 406 in the PDCCH by performing blind decoding (also referred to as blind detection). For example, the UE 402 can perform blind decoding by checking all possible PDCCH locations, PDCCH formats, and DCI formats and acting on messages with correct CRC. In some aspects of the present disclosure, the DCI message 406 can include control information for a PDSCH, a number A representing a number of DCI messages included in the PDSCH, and a downlink (DL) coding rate offset factor For example, A can be an integer greater than or equal to two. The DL coding rate offset factor (e.g., β offset > 1) can be used to achieve a lower coding rate compared to a coding rate indicated by a modulation coding scheme (MCS) for the PDSCH.

[0065] As shown in Figure 4 , the base station 404 can transmit A DCI messages 410 to the UE 402 in a PDSCH. For example, with reference to Figure 5 , in a scenario where two DCI messages are transmitted to the UE 402 in the PDSCH (e.g., A = 2), the DCI messages 410 can include a first DCI message 410_1 and a second DCI message 410_2 in the PDSCH 554. The first DCI message 410_1 can include DCI bits 556 (denoted as “DCI_1” in Figure 5 ) and CRC bits 558, and the second DCI message 410_2 can include DCI bits 560 (denoted as “DCI_2” in Figure 5 ) and CRC bits 562.

[0066] As shown in Figure 4As further shown, the UE 402 can obtain 412 the A DCI messages 410 in the PDSCH based on information in the DCI message 406 in the PDCCH. In some aspects of the disclosure, the UE 402 can determine the size of the A DCI messages included in a region of the PDSCH (also referred to as a DCI piggyback region). In some examples, the A DCI messages 410 can be zero-padded to the same size. For example, the bit length of the first DCI message 410_1 (e.g., the sum of DCI bits 556 and CRC bits 558) can be equal to the bit length of the second DCI message 410_2 (e.g., the sum of DCI bits 560 and CRC bits 562). In some examples, each of the A DCI messages 410 can have the same size (e.g., the same bit length) as the DCI message 406. The UE 402 can further determine the number of resource elements (REs) for each of the A DCI messages 410 and can decode the code blocks.

[0067] In scenarios where the codeword size is irregular, the UE can use Equation (4) to determine the total number of REs allocated to the A DCI messages 410:

[0068]

[0069] where N RE，DCI is the total number of REs allocated to the A DCI messages 410, K DCI is the payload size of each of the A DCI messages 410 after zero padding, is a DL coding rate offset factor (e.g., ), K DL-SCH is the payload size of a downlink shared channel (DL-SCH) including TB / CB CRC bits, and N RE is the total number of REs per layer of the PDSCH. It should be appreciated that Equation (4) represents a simplified equation for determining N RE，DCI and in some cases, the determination of N RE，DCI may be more complex.

[0070] In some aspects of the disclosure, the UE 402 can be configured to separately decode each of the A DCI messages 410 from a single code block. For example, the UE 402 can first determine the coded bits belonging to each code block. Then, the UE 402 can separately decode each code block to obtain each DCI message. This approach is shown in Figure 6 Figure 6 ​As shown, UE 402 can first determine the A-coded block carrying A DCI messages 410. For example, the A-coded block may include a first coded block 602 (in Figure 6 (marked as "coded block_1") to the A-th coded block 604 (in Figure 6 (This is marked as "coded block _A"). The Ath coded block 604 can represent the last coded block. UE 402 can decode the first coded block 602 to obtain the first DCI message 606, where DCI message 606 includes DCI bit 610 and CRC bit 612. Finally, UE 402 can decode the Ath coded block 604 to obtain the Ath DCI message 608, where DCI message 608 includes DCI bit 614 and CRC bit 616.

[0071] To determine the coded bits belonging to each coded block, UE 402 can first determine the total number of coded bits carrying A DCI messages 410. For example, the total number of coded bits could be M = N. RE，DCI ·Q m Q m Q is the number of data modulation bits on a single modulation symbol (e.g., for QPSK, QAM16, and QAM64, respectively). m =2, 4, 6). Then, UE 402 can determine the number of coded bits for each coded block used to carry the DCI message. In some aspects of this disclosure, UE 402 can evenly divide the REs of different DCI messages. In these aspects, for example, UE 402 can use the ratio M / A to determine the number of coded bits for each coded block (e.g., for each DCI message). UE 402 can also allocate any remaining coded bits 606 (e.g., (100 bits) are assigned to the last code block. In some examples, UE 402 can use K=K DCI and To determine the mother code size N (e.g., N = 2). n After determining the coded bits belonging to each coded block, UE 402 can then proceed to decode each coded block individually. Therefore, even if one or more coded blocks in a coded block cannot be decoded, UE 402 may still be able to successfully obtain the DCI message from the remaining coded blocks.

[0072] In other aspects of this disclosure, instead of uniformly dividing the REs of the A different DCI messages 410 as described above, UE 402 can divide the coded bits into different DCI messages at the RE level. Using this method, for example, each DCI message 410 in the A DCI messages 410 can include... A DCI messages 410, will include residual bits. The UE 402 can divide the total number of REs allocated for the A DCI messages 410 (e.g., N ) based on the number of REs carrying each of the A DCI messages 410 (e.g., RE，DCI ), to obtain a number of code blocks. The UE 402 can then individually decode each of the code blocks to obtain each DCI message.

[0073] In scenarios where the codeword size is consistent, the UE 402 can use Equation (5) or Equation (6) to determine the total number of REs allocated for the A DCI messages 410 (e.g., N RE，DCI ):

[0074]

[0075]

[0076] where N RE，DCI , A, K DCI , K DL-SCH and N RE are described herein with reference to Equation (4). It should be noted that Equation (5) includes a floor function, while Equation (6) includes a ceiling function. Thus, Equation (5) or Equation (6) can ensure that the value of N RE，DCI (e.g., the total number of REs allocated for the A DCI messages 410) is a multiple of A.

[0077] In some aspects of the disclosure, the UE 402 can be configured to individually decode each of the A DCI messages 410 from a single code block. For example, the UE 402 can first determine the coded bits belonging to each code block. The UE 402 can then individually decode each code block to obtain each DCI message. This approach is illustrated in Figure 7 . As shown in Figure 7 , the UE 402 can first determine the A code blocks carrying the A DCI messages 410. For example, the A code blocks can include a first code block 702 (labeled “Code Block 1” in Figure 7 ) through an A-th code block 704 (labeled “Code Block A” in Figure 7(This is marked as "coded block A"). The Ath coded block 704 can represent the last coded block. UE 402 can decode the first coded block 702 to obtain the first DCI message 706, where DCI message 706 includes DCI bit 710 and CRC bit 712. Finally, UE 402 can decode the Ath coded block 704 to obtain the Ath DCI message 708, where DCI message 708 includes DCI bit 714 and CRC bit 716.

[0078] To determine the coded bits belonging to each coded block, UE 402 can first determine the total number of coded bits carrying A DCI messages 410. For example, the total number of coded bits could be M = N. RE，DCI ·Q m Q m Q is the number of data modulation bits on a single modulation symbol (e.g., for QPSK, QAM16, and QAM64, respectively). m =2, 4, 6). Then, UE 402 can determine the number of encoded bits for each encoded block used to carry the DCI message. In some aspects of this disclosure, UE 402 can evenly divide the REs of different DCI messages. In these aspects, for example, UE 402 can use the ratio M / A to determine the number of encoded bits for each encoded block (e.g., for each DCI message). In some examples, UE 402 can use K = K DCI and To determine the mother code size N (e.g., N = 2). n After determining the coded bits belonging to each coded block, UE 402 can then proceed to decode each coded block individually. Therefore, even if one or more coded blocks in a coded block cannot be decoded, UE 402 can still successfully obtain DCI messages from the remaining coded blocks.

[0079] Blind decoding of DCI messages of different sizes

[0080] In some aspects of the disclosure, the A DCI messages 410 in the PDSCH can have different sizes (e.g., different bit lengths). For example, in one scenario, the PDSCH can include a first DCI message having DCI format 0 1 and a second DCI message having DCI format 1 1, where the first and second DCI messages have different sizes. For example, in another scenario, the PDSCH can include a first DCI message having DCI format 0 1, a second DCI message having DCI format 1 1, a third DCI message having DCI format 0 2, and a fourth DCI message having DCI format 1 2. In this scenario, the first and second DCI messages can have the same size, but the third and / or fourth DCI messages can have a different size relative to the first and second DCI messages.

[0081] When the A DCI messages 410 in the PDSCH have different sizes, the UE 402 can apply different assumptions regarding the payload size of each DCI message, and can perform multiple decoding operations to obtain the A DCI messages 410. However, it can be difficult for the UE 402 to apply different assumptions to determine the total payload size of the A DCI messages 410, which is needed for the determination of the number of REs (e.g., N RE，DCI ) for each DCI message.

[0082] In some aspects of the disclosure, if the A DCI messages 410 can include DCI messages having different sizes, the UE 402 can use a nominal DCI payload size when determining the total payload size of the A DCI messages 410 and the number of REs for each DCI message. The REs can still be partitioned evenly among the A DCI messages 410. As a result, the coding gain can be higher for the smaller DCI messages. For example, although the previously described payload size K DCI may vary for DCI messages having different DCI formats, the UE 402 can instead use a nominal payload size K' DCI (e.g., a common value for different DCI message sizes) for the determination of the K and E values.

[0083] It should be noted that when decoding the PDCCH, the UE 402 can try different K DCI values, which can significantly increase the decoding complexity. Thus, the previously described aspects of the disclosure that include the use of a nominal payload size K' DCI may achieve an appropriate tradeoff between decoding complexity (e.g., the number of decoding operations needed to be performed by the UE 402) and coding gap (e.g., avoidance of zero padding).

[0084] Decoding multiple DCI messages with different sizes without blind decoding

[0085] In some aspects of the disclosure, to avoid blind decoding (reduce complexity), the UE 402 can receive information indicating sizes of multiple DCI messages included in a PDSCH. For example, the UE 402 can receive the information via RRC configuration and / or a DCI message in a PDCCH.

[0086] In some aspects of the disclosure, if all DCI messages in a PDSCH have a same size, the UE 402 can receive control information indicating the size of the DCI messages. For example, the UE 402 can receive the control information via a DCI message in a PDCCH. In some aspects of the disclosure, all DCI messages in the PDSCH can be configured to have a same size selected from a set of candidate DCI message sizes. For example, the set of candidate DCI message sizes can include a first size and a second size, where the first size is different from the second size. In this example, the control information can indicate the first size or the second size. The control information can be a single bit, where the single bit is set to a first value (e.g., the single bit is set to ‘0’) to indicate the first size and set to a second value (e.g., the single bit is set to ‘1’) to indicate the second size. The set of candidate DCI message sizes (e.g., the first size and the second size) can be configured via RRC configuration. In other examples, the previously described set of candidate DCI message sizes can include more than two candidate DCI message sizes.

[0087] In some aspects of the disclosure, two sets of control information can be included in a DCI message in a PDCCH. A first set of control information can indicate to the UE 402 a number of DCI messages having a first size and a first coding rate offset factor for the DCI messages having the first size, and a second set of control information can indicate to the UE 402 a number of DCI messages having a second size and a second coding rate offset factor for the DCI messages having the second size. The first size can be different from the second size. In some examples, the first coding rate offset factor and the second coding rate offset factor can be the same for the DCI messages having the first size and the second size.

[0088] In some implementations, an order in which DCI messages of different sizes appear in the DCI piggyback region of the PDSCH (e.g., with respect to DCI message size) can be predetermined and known by the UE 402. For example, a DCI message having a first size can appear in the PDSCH before a DCI message having a second size, where the first size is smaller than the second size. Or, a DCI message having the second size can appear in the PDSCH before a DCI message having the first size. The two candidate DCI message sizes (e.g., the first DCI message size and the second DCI message size) can be configured via RRC configuration. In this case, for example, the UE 402 can accurately determine the total payload size of the A DCI messages 410 by summing the payload sizes of the different DCI messages having different sizes. The number of REs can be allocated differently / proportionally between the DCI messages having different sizes. In other examples, more than two candidate DCI message sizes can be configured.

[0089] In some aspects of the disclosure, the PDSCH can include (e.g., in the DCI message piggyback region of the PDSCH) different combinations of DCI message formats and DCI message sizes in the PDSCH transmission. In one aspect, the DCI messages included in the PDSCH can be configured to have one size. For example, the DCI messages can have the same size and can be based on DCI format 0 1 and DCI format 1 1. As another example, the DCI messages can have the same size and can be based on DCI format 0 2 and DCI format 1 2.

[0090] In another aspect, the DCI messages included in the PDSCH can be configured to have two sizes. For example, the DCI messages can have one size for DCI format 0 1 and another size for DCI format 1 1. As another example, the two DCI message size configurations can be selected from a set of DCI message size configurations. The set of DCI message size configurations can include a first configuration in which the DCI messages can have the same size and can be based on DCI format 0 1 and DCI format 1 1, a second configuration in which the DCI messages can have the same size and can be based on DCI format 0 2 and DCI format 1 2, and a third configuration in which the DCI messages can have the same size and can be based on DCI format 0 0 and DCI format 1 0.

[0091] On the other hand, DCI messages included in the PDSCH can be configured to have three different DCI message sizes. For example, DCI messages based on DCI format 0_1 ​​and DCI format 1_1 can both have a first size, DCI messages based on DCI format 0_2 and DCI format 1_2 can both have a second size, and DCI messages based on DCI format 0_0 and DCI format 1_0 can both have a third size. The first, second, and third sizes discussed above may differ from each other. It should be understood that the combinations of DCI message formats and DCI message sizes described above are not intended to be exhaustive, and additional and / or different combinations related to the combinations described herein may be used.

[0092] In some aspects of this disclosure, the number of DCI messages included in the PUSCH or PDSCH may be based on the capabilities of the UE (e.g., UE 104). For example, since a low-performance UE may not be able to support decoding multiple DCI messages carried in the PDSCH, such a low-performance UE may still be able to decode a single DCI message carried in the PDSCH. Therefore, in some aspects of this disclosure, only a single DCI message may be allowed in the PUSCH or PDSCH. Regarding the uplink (UL), for example, the UE may use multiple PUSCH permission to permit multiple time slots. Regarding the downlink (DL), for example, a DCI message in one time slot of the PDSCH (e.g., in the carrying area of ​​the PDSCH) may include control information for the next time slot of the PDSCH (e.g., DL permission). The next time slot of the PDSCH may include another DCI message (e.g., in the carrying area of ​​the next time slot of the PDSCH). Figure 8 The example implementation of this aspect is shown in the figure.

[0093] Figure 8 The diagram shows DCI message 802 included in the PDCCH, where DCI message 802 includes DCI bit 804 and CRC bit 806. The UE can obtain DCI message 802 from the PDCCH using blind decoding. DCI message 802 can indicate control information for the first PDSCH resource 808. Figure 8 As shown, the first PDSCH resource 808 may include a DCI message 810, wherein the DCI message 810 includes DCI bits 812 and CRC bits 814. Figure 8 As indicated by arrow 816, DCI message 810 can indicate control information for the second PDSCH resource 818. The second PDSCH resource 818 may include DCI message 820, wherein DCI message 820 includes DCI bits 822 and CRC bits 824. Figure 8As shown with arrow 826, the DCI message 820 can indicate control information for a third PDSCH resource 828. The third PDSCH resource 828 can include a DCI message 830, where the DCI message 830 includes DCI bits 832 and CRC bits 834.

[0094] In reference to Figure 8 Aspects described, transmission of the piggybacked DCI messages 810, 820, 830 to the UE does not require a control region (e.g., CORESET), and can not require rate matching. Further, the piggybacked DCI messages 810, 820, 830 can be decoded based on aspects described herein, and thus the UE can not need to perform blind decoding to obtain the DCI messages 810, 820, 830. As a result, the UE can avoid additional processing, and can reduce power consumption.

[0095] Figure 9 FIG. 9 is a flowchart 900 of a method of wireless communication. The method can be performed by a UE (e.g., the UE 104, 402; the apparatus 1102 / 1102’; the processing system 1214, which can include the memory 360 and which can be entire UE 104, 402 or components of the UE 104, 402, such as the TX processor 368, the RX processor 356, and / or the controller / processor 359).

[0096] At 902, the UE obtains a downlink control information (DCI) message transmitted in a physical downlink control channel (PDCCH). The DCI message includes control information for obtaining a plurality of downlink control information (DCI) messages included in a physical downlink shared channel (PDSCH).

[0097] In some aspects of the disclosure, the control information indicates at least a total number of the plurality of DCI messages and a coding rate offset factor. For example, the total number of the plurality of DCI messages can be represented by a parameter A, and the coding rate offset factor can be a DL coding rate offset factor where

[0098] In some aspects of the disclosure, each of the plurality of DCI messages in the PDSCH has a same payload size. In these aspects, the control information indicates at least a total number of the plurality of DCI messages and the payload size. In some aspects, the payload size is one of a set of preconfigured payload sizes.

[0099] In some aspects of the disclosure, a first number of the plurality of DCI messages in the PDSCH has a first payload size and a second number of the plurality of DCI messages in the PDSCH has a second payload size. The first number of the plurality of DCI messages can be configured to appear in the PDSCH before the second number of the plurality of DCI messages. In these aspects, the control information indicates the first number of the plurality of DCI messages and the second number of the plurality of DCI messages. In some aspects, the control information further indicates a first coding rate offset factor for the first number of the plurality of DCI messages and a second coding rate offset factor for the second number of the plurality of DCI messages.

[0100] At 904, the UE receives the PDSCH including the plurality of DCI messages.

[0101] Finally, at 906, the UE obtains one or more of the plurality of DCI messages in the PDSCH based on the control information.

[0102] In some aspects of the disclosure, the plurality of DCI messages in the PDSCH have the same size (e.g., the same payload size K = K DCI ). In these aspects, the UE obtains one or more of the plurality of DCI messages in the PDSCH by determining a total number of resource elements (REs) allocated for the plurality of DCI messages in the PDSCH. For example, the total number of resource elements (REs) allocated for the plurality of DCI messages in the PDSCH can be N RE，DCI · K in Equation (4). The UE can then determine a total number of coded bits for the plurality of DCI messages in the PDSCH based on the total number of REs. For example, the total number of coded bits for the plurality of DCI messages in the PDSCH can be M = N RE，DCI · Q m . The UE determines a number of coded bits for each of the plurality of DCI messages in the PDSCH. For example, the number of coded bits for each of the plurality of DCI messages in the PDSCH can be The UE can partition the total number of coded bits based on the number of coded bits to obtain a plurality of coded blocks (e.g., coded blocks 602, 604). In some scenarios, one or more residual coded bits can remain after partitioning the total number of coded bits. In these scenarios, the UE assigns the one or more residual coded bits to a last coded block of the plurality of coded blocks. The UE then decodes each of the plurality of coded blocks, respectively, to determine the plurality of DCI messages 606, 608 in the PDSCH.

[0103] In some aspects of the disclosure, the multiple DCI messages in the PDSCH have the same size (e.g., the same payload size K = K DCI ). In these aspects, the UE obtains one or more of the multiple DCI messages in the PDSCH by determining a total number of resource elements (REs) allocated for the multiple DCI messages in the PDSCH. For example, the total number of resource elements (REs) allocated for the multiple DCI messages in the PDSCH can be N RE，DCI . The UE can then determine a number of REs for each of the multiple DCI messages in the PDSCH. For example, the number of REs for each of the multiple DCI messages can be The UE can partition the total number of REs based on the number of REs for each of the multiple DCI messages to obtain a plurality of encoding blocks (e.g., encoding blocks 602, 604). In some scenarios, one or more residual REs can remain after partitioning the total number of REs. In these scenarios, the UE allocates the one or more residual REs to a last encoding block of the plurality of encoding blocks. The UE then decodes each of the plurality of encoding blocks, respectively, to determine the multiple DCI messages 606, 608 in the PDSCH.

[0104] In some aspects of the disclosure, the multiple DCI messages in the PDSCH have the same size (e.g., the same payload size K = K DCI ). In these aspects, the UE obtains one or more of the multiple DCI messages in the PDSCH by determining a total number of resource elements (REs) allocated for the multiple DCI messages in the PDSCH. For example, the total number of resource elements (REs) allocated for the multiple DCI messages in the PDSCH can be N RE，DCI . In some aspects of the disclosure, the total number of REs is a multiple of the total number of the multiple DCI messages. The UE can then determine a total number of encoding bits for the multiple DCI messages in the PDSCH based on the total number of REs. For example, the total number of encoding bits for the multiple DCI messages in the PDSCH can be M = N RE，DCI · Q m . The UE determines a number of encoding bits for each of the multiple DCI messages in the PDSCH. For example, the number of encoding bits for each of the multiple DCI messages in the PDSCH can be The UE can partition the total number of coded bits based on the number of coded bits to obtain a plurality of coded blocks (e.g., coded blocks 702, 704). The UE can then separately decode each of the plurality of coded blocks to determine the plurality of DCI messages 706, 708 in the PDSCH.

[0105] In some aspects of the disclosure, at least two of the plurality of DCI messages in the PDSCH have different sizes (e.g., different payload sizes K). In these aspects, the UE obtains one or more of the plurality of DCI messages in the PDSCH by determining a total number of resource elements (REs) allocated for the plurality of DCI messages in the PDSCH based on a nominal payload size for each of the plurality of DCI messages in the PDSCH. The UE determines a total number of coded bits for the plurality of DCI messages in the PDSCH based on the total number of REs. The UE determines a number of coded bits for each of the plurality of DCI messages in the PDSCH. The UE partitions the total number of coded bits based on the number of coded bits to obtain a plurality of coded blocks. The UE separately decodes each of the plurality of coded blocks to determine the plurality of DCI messages in the PDSCH.

[0106] Figure 10 is a flowchart 1000 of a method of wireless communication. The method can be performed by a UE (e.g., the UE 104, 402; the apparatus 1102 / 1102’; the processing system 1214, which can include the memory 360 and can be the entire UE 104, 402 or a component of the UE 104, 402, such as the TX processor 368, the RX processor 356, and / or the controller / processor 359).

[0107] At 1002, the UE obtains a first downlink control information (DCI) message transmitted in a physical downlink control channel (PDCCH). The first DCI message includes first control information for a physical downlink shared channel (PDSCH) that includes a second DCI message.

[0108] At 1004, the UE receives the PDSCH including the second DCI message.

[0109] Finally, at 1006, the UE obtains the second DCI message in the PDSCH based on the first control information. The second DCI message includes second control information for a next slot of the PDSCH.

[0110] Figure 11This is a conceptual data flow diagram 1100 illustrating the data flow between different units / components in example device 1102. The device may be a UE. The device includes a receiving component 1104 that receives a Physical Downlink Control Channel (PDCCH) 1112 and a Physical Downlink Shared Channel (PDSCH) 1114 from a base station 1150. In some implementations, base station 1150 may be a 5G NR base station. PDSCH 1114 may include a number A DCI messages (e.g., in the resources of PDSCH 1114, referred to as a back area for carrying A DCI messages).

[0111] The apparatus also includes a downlink control information (DCI) acquisition component 1106 in the PDCCH, which obtains control information 1120 from PDCCH 1112. The downlink control information (DCI) acquisition component 1106 in the PDCCH can provide PDSCH configuration information 1118 to the receiving component 1104 to enable reception of PDSCH 1114. In some examples, the control information 1120 at least indicates the total number (e.g., A) of the multiple DCI messages included in PDSCH 1114 and the coding rate offset factor.

[0112] The device also includes a downlink control information (DCI) acquisition component 1108 in the PDSCH, which acquires one or more DCI messages among a plurality of DCI messages in the PDSCH 1114 based on control information 1120. In some examples, the DCIs in the PDSCH include DL authorization 1124 and / or UL authorization 1126.

[0113] The device may include means for performing Figure 9 and Figure 10 Additional components to each box in the algorithm's box in the aforementioned flowchart. Accordingly, in Figure 9 and Figure 10 Each block in the aforementioned flowchart can be executed by a component, and the apparatus can include one or more of these components. A component can be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by a processor configured to perform the stated process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0114] Figure 12is a diagram 1200 illustrating an example of a hardware implementation for an apparatus 1102' employing a processing system 1214. The processing system 1214 can be implemented with a bus architecture, as represented by bus 1224. The bus 1224 can include any number of buses and bridges, depending on the specific application of the processing system 1214 and the overall design constraints. The bus 1224 links together various circuits such as the processor 1204, and / or hardware components, represented by the components 1104, 1106, 1108, 1110, and the computer-readable medium / memory 1206. The bus 1224 can also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

[0115] The processing system 1214 can be coupled to a transceiver 1210. The transceiver 1210 is coupled to one or more antennas 1220. The transceiver 1210 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 1210 receives a signal from the one or more antennas 1220, extracts information from the received signal, and provides the extracted information to the processing system 1214, specifically the reception component 1104. In addition, the transceiver 1210 receives information from the processing system 1214, specifically the transmission component 1110, and based on the received information, generates a signal to be applied to the one or more antennas 1220. The processing system 1214 includes the processor 1204 coupled to the computer-readable medium / memory 1206. The processor 1204 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1206. The software, when executed by the processor 1204, causes the processing system 1214 to perform the various functions described supra for any particular apparatus. The computer-readable medium / memory 1206 can also be used for storing data that is manipulated by the processor 1204 when executing software. The processing system 1214 further includes at least one of the components 1104, 1106, 1108, 1110. The components can be software components running in the processor 1204, resident / 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 can be a component of the UE 350 and can include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. Alternatively, the processing system 1214 can be the entire UE (e.g., see 350). Figure 3

[0116] ​In one configuration, the apparatus 1102 / 1102' for wireless communication includes means for obtaining a downlink control information (DCI) message transmitted in a physical downlink control channel (PDCCH), wherein the DCI message includes control information for obtaining a plurality of downlink control information (DCI) messages included in a physical downlink shared channel (PDSCH); means for receiving the PDSCH including the plurality of DCI messages; means for obtaining one or more of the plurality of DCI messages in the PDSCH based on the control information; means for obtaining a first downlink control information (DCI) message transmitted in a physical downlink control channel (PDCCH), wherein the first DCI message includes: first control information for a physical downlink shared channel (PDSCH) including a second DCI message; means for receiving the PDSCH including the second DCI message; and means for obtaining the second DCI message in the PDSCH based on the first control information, the second DCI message including second control information for a next slot of the PDSCH.

[0117] The aforementioned means can be one or more of the aforementioned components of the apparatus 1102 and / or the processing system 1214 of the apparatus 1102' configured to perform the functions recited by the aforementioned means. As described supra, the processing system 1214 can include the TX Processor 368, the RX Processor 356, and the controller / processor 359. As such, in one configuration, the aforementioned means can be the TX Processor 368, the RX Processor 356, and the controller / processor 359 configured to perform the functions recited by the aforementioned means.

[0118] It should be understood that the particular order in which the operations in the processes / flow diagrams have been described is merely an example. And, the order in which the operations are described is not necessarily the order in which the operations will be performed. Concepts have been presented with reference to particular means for performing the functions described herein. These concepts are intended to encompass not only the means specifically identified as performing the functions but also other means for performing the functions. The means for performing the functions can be implemented using hardware, software, firmware, or any combination thereof. The means for performing the functions can be implemented using a processor, controller, or other processing device that executes machine-readable instructions, such as software. The means for performing the functions can be implemented using, for example, at least one integrated circuit or at least one microprocessor.

[0119] The foregoing description has provided by way of example of the various aspects described herein. Various modifications will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects without departing from the scope of the aspects defined herein. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language of the claims, wherein, unless indicated to the contrary, the

[0120] Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combinatorial combination of A, B, and / or C, and can include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" can be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combination can contain one or more members of A, B, or C. For purposes of the disclosure, the expression "at least one of A, B, and C" means A alone, B alone, C alone, or any combination of A, B, and C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or will be known to those of ordinary skill in the art are expressly incorporated herein by reference and intended to be encompassed by the claims. Moreover, 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 can not be a substitute for the word "means." As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase "means for."

Claims

1. A method of wireless communication, comprising: obtaining, at a user equipment (UE), a downlink control information (DCI) message transmitted in a physical downlink control channel (PDCCH), wherein the DCI message includes control information for obtaining a plurality of downlink control information (DCI) messages included in a physical downlink shared channel (PDSCH), wherein each of the DCI messages is separately encoded in a single code block; receiving, at the UE, the PDSCH including the plurality of DCI messages; and obtaining one or more of the plurality of DCI messages in the PDSCH based on the control information.

2. The method of claim 1, wherein, the control information for obtaining the plurality of DCI messages included in the PDSCH indicates at least a total number of the plurality of DCI messages and a coding rate offset factor.

3. The method of claim 1, wherein, the plurality of DCI messages in the PDSCH have a same size, and wherein the obtaining the one or more of the plurality of DCI messages in the PDSCH includes: determining a total number of resource elements (REs) allocated for the plurality of DCI messages in the PDSCH; determining a total number of coded bits for the plurality of DCI messages in the PDSCH based on the total number of REs; determining a number of coded bits for each of the plurality of DCI messages in the PDSCH; segmenting the total number of coded bits based on the number of coded bits to obtain a plurality of code blocks; and separately decoding each of the plurality of code blocks to determine the plurality of DCI messages in the PDSCH.

4. The method of claim 3, wherein, one or more residual coded bits remain after segmenting the total number of coded bits, and wherein the segmenting the total number of coded bits includes: assigning the one or more residual coded bits to a last code block of the plurality of code blocks.

5. The method of claim 1, wherein, the plurality of DCI messages in the PDSCH have a same size, and wherein the obtaining the one or more of the plurality of DCI messages in the PDSCH includes: determining a total number of resource elements (REs) allocated for the plurality of DCI messages in the PDSCH; determining a number of REs for each of the plurality of DCI messages in the PDSCH; segmenting the total number of REs based on the number of REs to obtain a plurality of code blocks; and separately decoding each of the plurality of code blocks to determine the plurality of DCI messages in the PDSCH.

6. The method of claim 5, wherein, one or more residual REs remain after segmenting the total number of REs, and wherein the segmenting the total number of REs includes: assigning the one or more residual REs to a last code block of the plurality of code blocks.

7. The method of claim 1, wherein, The plurality of DCI messages in the PDSCH have a same size, and wherein the obtaining the one or more DCI messages of the plurality of DCI messages in the PDSCH comprises: determining a total number of resource elements (REs) allocated for the plurality of DCI messages in the PDSCH, wherein the total number of REs is a multiple of a total number of the plurality of DCI messages; determining a total number of coded bits for the plurality of DCI messages in the PDSCH based on the total number of REs; determining a number of coded bits for each DCI message of the plurality of DCI messages in the PDSCH; segmenting the total number of coded bits based on the number of coded bits to obtain a plurality of coded blocks; and decoding each coded block of the plurality of coded blocks individually to determine the plurality of DCI messages in the PDSCH.

8. The method of claim 1, wherein, At least two DCI messages of the plurality of DCI messages in the PDSCH have different sizes, and wherein the obtaining the one or more DCI messages of the plurality of DCI messages in the PDSCH comprises: determining a total number of resource elements (REs) allocated for the plurality of DCI messages in the PDSCH based on a nominal payload size for each DCI message of the plurality of DCI messages in the PDSCH; determining a total number of coded bits for the plurality of DCI messages in the PDSCH based on the total number of REs; determining a number of coded bits for each DCI message of the plurality of DCI messages in the PDSCH; segmenting the total number of coded bits based on the number of coded bits to obtain a plurality of coded blocks; and decoding each coded block of the plurality of coded blocks individually to determine the plurality of DCI messages in the PDSCH.

9. The method of claim 1, wherein, Each DCI message of the plurality of DCI messages in the PDSCH has a same payload size, and wherein the control information for obtaining the plurality of DCI messages included in the PDSCH indicates at least a total number of the plurality of DCI messages and the payload size.

10. The method of claim 9, wherein, The payload size is one of a set of pre-configured payload sizes.

11. The method of claim 1, wherein, A first number of DCI messages of the plurality of DCI messages in the PDSCH have a first payload size, and a second number of DCI messages of the plurality of DCI messages in the PDSCH have a second payload size, wherein the first number of DCI messages of the plurality of DCI messages appear in the PDSCH before the second number of DCI messages of the plurality of DCI messages, wherein the control information indicates the first number and the second number.

12. The method of claim 11, wherein, The control information also indicates a first coding rate offset factor for the first number of DCI messages of the plurality of DCI messages and a second coding rate offset factor for the second number of DCI messages of the plurality of DCI messages.

13. The method of claim 1, wherein, The plurality of DCI messages includes at least one DCI message with DCI format 0_1 and at least one DCI message with DCI format 1_1, and wherein each of the plurality of DCI messages included in the PDSCH has a same size.

14. The method of claim 1, wherein, The plurality of DCI messages includes at least one DCI message with DCI format 0_2 and at least one DCI message with DCI format 1_2, and wherein each of the plurality of DCI messages included in the PDSCH has a same size.

15. The method of claim 1, wherein, The plurality of DCI messages includes at least one DCI message with DCI format 0_1 and at least one DCI message with DCI format 1_1, and wherein the at least one DCI message with DCI format 0_1 has a first size and the at least one DCI message with DCI format 1_1 has a second size.

16. The method of claim 1, wherein, The plurality of DCI messages includes: at least one DCI message with DCI format 0_1 and at least one DCI message with DCI format 1_1, and wherein the at least one DCI message with DCI format 0_1 and the at least one DCI message with DCI format 1_1 have a first size; and at least one DCI message with DCI format 0_0 and at least one DCI message with DCI format 1_0, and wherein the at least one DCI message with DCI format 0_0 and the at least one DCI message with DCI format 1_0 have a second size.

17. The method of claim 1, wherein, The plurality of DCI messages includes: at least one DCI message with DCI format 0_1 and at least one DCI message with DCI format 1_1, and wherein the at least one DCI message with DCI format 0_1 and the at least one DCI message with DCI format 1_1 have a first size; at least one DCI message with DCI format 0_2 and at least one DCI message with DCI format 1_2, and wherein the at least one DCI message with DCI format 0_2 and the at least one DCI message with DCI format 1_2 have a second size; or at least one DCI message with DCI format 0_0 and at least one DCI message with DCI format 1_0, and wherein the at least one DCI message with DCI format 0_0 and the at least one DCI message with DCI format 1_0 have a third size.

18. An apparatus for wireless communication, comprising: means for obtaining a downlink control information (DCI) message transmitted in a physical downlink control channel (PDCCH), wherein the DCI message includes control information for obtaining a plurality of downlink control information (DCI) messages included in a physical downlink shared channel (PDSCH), wherein each of the DCI messages is separately encoded in a single code block; means for receiving the PDSCH including the plurality of DCI messages; and means for obtaining one or more of the plurality of DCI messages in the PDSCH based on the control information.

19. An apparatus for wireless communication, comprising: a memory; and at least one processor coupled to the memory and configured to: obtain a downlink control information (DCI) message transmitted in a physical downlink control channel (PDCCH), wherein the DCI message includes control information for obtaining a plurality of downlink control information (DCI) messages included in a physical downlink shared channel (PDSCH), wherein each of the DCI messages is separately encoded in a single code block; receive the PDSCH including the plurality of DCI messages; and obtain one or more of the plurality of DCI messages in the PDSCH based on the control information.

20. A computer-readable medium storing computer-executable code, the code, when executed by a processor, causing the processor to: obtaining a downlink control information (DCI) message transmitted in a physical downlink control channel (PDCCH), wherein, obtain a downlink control information (DCI) message transmitted in a physical downlink control channel (PDCCH), wherein the DCI message includes control information for obtaining a plurality of downlink control information (DCI) messages included in a physical downlink shared channel (PDSCH), wherein each of the DCI messages is separately encoded in a single code block; receive the PDSCH including the plurality of DCI messages; and obtain one or more of the plurality of DCI messages in the PDSCH based on the control information.

21. A method of wireless communication, comprising: obtaining, at a user equipment (UE), a first downlink control information (DCI) message transmitted in a physical downlink control channel (PDCCH), wherein the first DCI message includes first control information for a physical downlink shared channel (PDSCH) including a second DCI message; receiving, at the UE, the PDSCH including the second DCI message; and obtaining, at the UE, the second DCI message in the PDSCH based on the first control information, the second DCI message including second control information for a next slot of the PDSCH for the UE to obtain a DCI message in the next slot of the PDSCH based on the second control information.

22. An apparatus for wireless communication, comprising: means for obtaining a first downlink control information (DCI) message transmitted in a physical downlink control channel (PDCCH), wherein the first DCI message includes first control information for a physical downlink shared channel (PDSCH) including a second DCI message; means for receiving the PDSCH including the second DCI message; and means for obtaining the second DCI message in the PDSCH based on the first control information, the second DCI message including second control information for a next slot of the PDSCH for the UE to obtain a DCI message in the next slot of the PDSCH based on the second control information.

23. An apparatus for wireless communication, comprising: a memory; and at least one processor coupled to the memory and configured to: obtain a first downlink control information (DCI) message transmitted in a physical downlink control channel (PDCCH), wherein the first DCI message includes first control information for a physical downlink shared channel (PDSCH) including a second DCI message; receive the PDSCH including the second DCI message; and obtain the second DCI message in the PDSCH based on the first control information, the second DCI message including second control information for a next slot of the PDSCH for the UE to obtain a DCI message in the next slot of the PDSCH based on the second control information.

24. A computer-readable medium storing computer executable code, the code when executed by a processor causes the processor to: obtaining a first downlink control information (DCI) message transmitted in a physical downlink control channel (PDCCH), wherein, obtain a first downlink control information (DCI) message transmitted in a physical downlink control channel (PDCCH), wherein the first DCI message includes first control information for a physical downlink shared channel (PDSCH) including a second DCI message; receive the PDSCH including the second DCI message; and obtain the second DCI message in the PDSCH based on the first control information, the second DCI message including second control information for a next slot of the PDSCH for the UE to obtain a DCI message in the next slot of the PDSCH based on the second control information.

Images