Methods and apparatus for dc transmission on pdsch

Abstract

The present disclosure relates to methods and devices, including apparatuses (e.g., base stations and / or UEs), for wireless communication. The apparatus can calculate a number of coded bits based on a number of downlink control information (DCI) information bits. The apparatus can also determine a quantity of one or more code blocks (CBs) in the DCI, each of the one or more CBs including a plurality of coded bits, based on at least one of the number of coded bits or the number of DCI information bits. Further, the apparatus can transmit a physical downlink shared channel (PDSCH) including the DCI, where the DCI includes at least one of the one or more CBs or the one or more coded blocks. The apparatus can also encode the one or more CBs in the DCI based on the determined quantity of the one or more CBs.

Description

[0001] Cross-references to related applications

[0002] This application is the national phase application filed on April 4, 2020, pursuant to Section 371 of the United States Patent Act, entitled “METHODSAND APPARATUS FOR DCI TRANSMISSION OVER PDSCH”, PCT International Application Serial No. PCT / CN2020 / 083388, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] In summary, this disclosure relates to communication systems, and more specifically, to the transmission of downlink control information (DCI) in wireless communication systems. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable 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 telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, country, region, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Mobile Broadband Evolution (CMB) initiative released by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., in the case of 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. There is a need for further improvements to 5G NR technology. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0006] The following is a simplified overview of one or more aspects to provide a basic understanding of such aspects. This overview is not an exhaustive summary of all anticipated aspects, nor is it intended to identify key or important elements of all aspects, nor to depict 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 descriptions given later.

[0007] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be a base station. The apparatus may receive an indication of the number of downlink control information (DCI) information bits. The apparatus may also calculate the number of coded bits based on the number of downlink control information (DCI) information bits. The apparatus may also determine the amount of one or more code blocks (CBs) in the DCI based on at least one of the number of coded bits or the number of DCI information bits, each of the one or more CBs comprising multiple coded bits. Furthermore, the apparatus may divide the number of coded bits into the amount of the one or more CBs. The apparatus may also modulate the amount of coded bits into multiple symbols. The apparatus may also encode the one or more CBs in the DCI based on the determined amount of the one or more CBs, wherein the encoded one or more CBs may correspond to the one or more coded blocks. Additionally, the apparatus may transmit a physical downlink shared channel (PDSCH) including the DCI, wherein the DCI includes at least one of the one or more CBs or one or more coded blocks.

[0008] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth certain illustrative features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of each aspect may be employed, and this description is intended to include all such aspects and their equivalents. Attached Figure Description

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

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

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

[0012] Figure 4 This is an example schematic diagram of DCI segmentation based on one or more techniques according to this disclosure.

[0013] Figure 5 This is a schematic diagram illustrating example communication between a UE and a base station using one or more technologies according to this disclosure.

[0014] Figure 6 This is a flowchart of a wireless communication method. Detailed Implementation

[0015] The detailed description below, taken in conjunction with the accompanying drawings, is intended to describe various configurations and not to represent only the configurations in which the concepts described herein can be implemented. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be implemented without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0016] Several aspects of a telecommunications system will now be described with reference to various apparatuses and methods. These apparatuses and methods will be described in detail below and illustrated in the accompanying drawings, by way of 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 these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0017] For example, elements, or any part of elements, 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, system-on-a-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 this disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

[0018] Accordingly, in one or more example embodiments, the described functionality can be implemented using hardware, software, or any combination thereof. If implemented in software, the functionality can be stored on a computer-readable medium or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium accessible by a computer. By way of example, and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of computer-readable media of the types described above, or any other medium capable of storing computer-executable code in the form of instructions or data structures accessible by a computer.

[0019] Figure 1 This is a schematic diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a user interface unit (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 macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0020] Base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can also 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 of 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, location, and delivery of warning messages. Base stations 102 can communicate with each other directly or indirectly (e.g., via EPC 160 or core network 190) via a third backhaul link 134 (e.g., an X2 interface). The third backhaul link 134 can be wired or wireless.

[0021] Base station 102 can wirelessly communicate with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 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. The heterogeneous network may also include evolved home node B (eNB) (HeNB), which can provide services to restricted groups referred to as closed subscriber groups (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also referred to as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also referred to as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be via one or more carriers. Base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) bandwidth allocated to each carrier in carrier aggregation for transmission in each direction. Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carrier may be referred to as the secondary cell (SCell).

[0022] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sideline channels, such as the Physical Sideline Broadcast Channel (PSBCH), Physical Sideline Discovery Channel (PSDCH), Physical Sideline Shared Channel (PSSCH), and Physical Sideline Control Channel (PSCCH). D2D communication can be achieved through a variety of wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

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

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

[0025] Base station 102 (whether it is a small cell 102' or a large cell (e.g., a macro base station)) may include and / or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in conventional sub-6 GHz spectrum, in millimeter wave (mmW) frequencies, and / or near-mmW frequencies to communicate with UE 104. When gNB 180 operates in mmW or near-mmW frequencies, gNB 180 may be referred to as an mmW base station. Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains radio frequency (RF). EHF has a range from 30 GHz to 300 GHz and wavelengths between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near-mmW can extend down to frequencies of 3 GHz with wavelengths of 100 mm. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz and are also referred to as centimeter waves. Communication using mmW / near-mmW radio frequency bands (e.g., 3 GHz–300 GHz) has extremely high path loss and short range. mmW base station 180 can utilize beamforming 182 with UE 104 to compensate for extremely high path loss and short range. Base station 180 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0026] Base station 180 may transmit beamformed signals to UE 104 in one or more transmit directions 182'. 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 optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions for base station 180 may be the same or different. The transmit and receive directions for UE 104 may be the same or different.

[0027] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 can communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 provides functions for providing and delivering MBMS user services. The BM-SC 170 can act as an entry point for MBMS transmissions by content providers, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can distribute MBMS services to base stations 102 belonging to Multicast-Broadcast Single Frequency Network (MBSFN) areas belonging to broadcast-specific services, and can be responsible for session management (start / stop) and collecting billing information related to eMBMS.

[0028] The core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that processes signaling between UE 104 and the core network 190. Typically, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted via UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranets, IP Multimedia Subsystem (IMS), PS streaming services, and / or other IP services.

[0029] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver, radio base station, radio transceiver, transceiver function, Basic Services Set (BSS), Extended Services Set (ESS), Transmitter Receiver Point (TRP), or some other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radio units, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable term.

[0030] Refer again Figure 1In some aspects, base station 180 may include a transmitting component 198 configured to receive an indication of the number of downlink control information (DCI) information bits. Transmitting component 198 may also be configured to calculate the number of coded bits based on the number of downlink control information (DCI) information bits. Transmitting component 198 may also be configured to determine the amount of one or more code blocks (CBs) in the DCI based on at least one of the number of coded bits or the number of DCI information bits, each of the one or more CBs comprising multiple coded bits. Transmitting component 198 may also be configured to divide the number of coded bits into the amount of one or more CBs. Transmitting component 198 may also be configured to modulate the amount of coded bits into multiple symbols. Transmitting component 198 may also be configured to encode one or more CBs in the DCI based on the determined amount of one or more CBs, wherein the encoded one or more CBs may correspond to one or more coded blocks. Transmitting component 198 may also be configured to transmit a physical downlink shared channel (PDSCH) including the DCI, wherein the DCI includes at least one of one or more CBs or one or more coded blocks.

[0031] Although the following description may focus on 5G NR, the concepts described in this article can be applied to other similar areas, such as LTE, LTE-A, CDMA, GSM and other wireless technologies.

[0032] Figure 2A This is a schematic diagram 200 showing an example of the first subframe within a 5G / NR frame structure. Figure 2B This is a schematic diagram 230 illustrating an example of a DL channel within a 5G / NR subframe. Figure 2C This is a schematic diagram 250 showing an example of a second subframe within a 5G / NR frame structure. Figure 2D This is a schematic diagram 280 illustrating an example of a UL channel within a 5G / NR subframe. The 5G / NR frame structure can be FDD (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL), or TDD (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). In the context of... Figure 2A , 2CIn the provided example, the 5G / NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and X is flexibly used between DL and 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 all DL and all UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format by receiving a Slot Format Indicator (SFI) (dynamically via DL Control Information (DCI) or semi-statically / statically via Radio Resource Control (RRC) signaling). It should be noted that the following description also applies to the 5G / NR frame structure as TDD.

[0033] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, while for time slot configuration 1, each time slot may include 7 symbols. Symbols on the DL can be Cyclic Prefix (CP) OFDM (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (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 the numbering scheme. For slot configuration 0, different digital schemes μ0 to μ5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different digital schemes 0 to μ2 allow 2, 4, and 8 slots per subframe, respectively. Correspondingly, for slot configuration 0 and digital scheme μ, there are 14 symbols / slot and 2... μ Each time slot / subframe. Subcarrier spacing and symbol length / duration are functions of the digital scheme. Subcarrier spacing can be equal to 2. μ *15kHz, where μ is the digital scheme from 0 to 5. Therefore, digital scheme μ = 0 has a subcarrier spacing of 15kHz, and digital scheme μ = 5 has a subcarrier spacing of 480kHz. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A-2DExamples are provided for slot configuration 0 with 14 symbols per slot and digital scheme μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0034] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)), which 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.

[0035] like Figure 2A As shown, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulated RS (DM-RS) for channel estimation at the UE (indicated as R for a particular configuration). x (Where 100x is the port number, but other DM-RS configurations are possible) and Channel State Information Reference Signal (CSI-RS). RS may also include Beam Measurement RS (BRS), Beam Refinement RS (BRRS), and Phase Tracking RS (PT-RS).

[0036] Figure 2B Examples of various DL channels within a subframe of a frame are shown. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising nine RE Groups (REGs), each REG comprising four consecutive REs in an OFDM symbol. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by UE104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The Physical Broadcast Channel (PBCH) (which carries the Master Information Block (MIB)) may logically be grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Blocks (SIBs)) that are not transmitted via the PBCH, and paging messages.

[0037] like Figure 2CAs shown, some REs in the REs carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are possible). The UE can transmit 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 transmitted in the first one or two symbols preceding the PUSCH. In different configurations, the PUCCH DM-RS can be transmitted depending on whether a short or long PUCCH is transmitted and the specific PUCCH format used. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0038] Figure 2D Examples of various UL channels within a subframe of a frame are shown. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and can also be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0039] Figure 3This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with: broadcasting 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 via ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer 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 via HARQ, priority handling, and logical channel prioritization.

[0040] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection of the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation diagram 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 encoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is spatially precoded to generate multiple spatial streams. The channel estimate from channel estimator 374 can be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate can be derived based on a reference signal transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0041] At UE 350, each receiver 354RX receives signals through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides this information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on this information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 310. These soft decisions can be based on channel estimates calculated by channel estimator 358. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. This data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functions.

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

[0043] Similar to the functions described in conjunction with DL transmissions performed by base station 310, controller / processor 359 provides: RRC layer functions associated with: system information (e.g., MIB, SIB) capture, RRC connection, and measurement reporting; PDCP layer functions associated with: header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with: transmission of upper-layer PDUs, error correction via 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 via HARQ, priority processing, and logical channel prioritization.

[0044] The TX processor 368 can use the channel estimate derived by the channel estimator 358 based on a reference signal or feedback transmitted by the base station 310 to select an appropriate coding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0045] At base station 310, UL transmission is processed in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318RX receives signals through its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides that information to the RX processor 370.

[0046] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels 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 to support HARQ operation using ACK and / or NACK protocols.

[0047] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform coupling. Figure 1 198 in all aspects.

[0048] In some aspects of wireless communication, uplink control information (UCI) transmission can be carried over certain data channels (e.g., PUSCH). Therefore, UCI can be transmitted along with other uplink data in the PUSCH. In some aspects, a rate scaling factor (e.g., β) is used to rate match UCI on the PUSCH. offset >1) This can be used to obtain a lower code rate compared to the indicated modulation and coding scheme (MCS). For example, the number of resource elements (REs) per layer for UCI can be expressed by the following equation: Where, N RE K is the total number of REs in each layer of PUSCH. UL-SCH This is the payload size of the UL-SCH, including the cyclic redundancy check (CRC) bits of the transport block (TB) or code block (CB). Additionally, K UCI This is the size of the UCI payload, including CRC bits (if any). To prevent UCI from consuming too many PUSCH resources, a partial factor (e.g., α ∈ {0.5, 0.65, 0.8, 1.0}) can limit the maximum portion of resources that UCI can occupy. Furthermore, the number of REs per layer used for UCI can be expressed by the following equation:

[0049] In some aspects of wireless communication, channel coding can also be used for the PDCCH. Furthermore, in some wireless communications (e.g., NR), polar codes can be used for the control channel. In some aspects, the maximum coded block size can be 512 bits for the downlink and 1024 bits for the uplink. Additionally, the minimum coding 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. Rate matching schemes can also include shortening, puncturing, and repetition. Furthermore, the decoding complexity can be O(N×log2(N)), where N is the number of coded bits. In other words, the complexity does not necessarily have to be a direct function of the coding rate. It should be noted that with a large number of information bits, there may be a coding gain loss.

[0050] In wireless communication, the block size can also be determined. In some instances, the number of information bits can be K, and the number of coded bits can be N=2. n And the code block size (e.g., after rate matching) can be E. If and So If not, then also, and Furthermore, n = max{min{n1,n2,n max},n min}, where n min =5.

[0051] Some aspects of wireless communication can be carried over using DCI in PDSCH, similar to carrying over UCI in PUSCH. Carried DCI can be an aggregation of multiple downlink or uplink permissions; therefore, delivering these permissions in PDSCH can be more efficient than transmitting them in the PDCCH area under blind decoding. In some aspects, the maximum number of information bits (K) in the DCI used for PDCCH... DCI It can be 140 bits. In this case, if the number of information bits in the DCI (K) DCI If the value is greater than 140, it may not be sent in the PDCCH. Therefore, more bits may be needed to send the entire DCI. Consequently, it may be necessary to increase the number of information bits or the payload size of the DCI.

[0052] In some aspects, the aggregated embedded DCI length can exceed the maximum 164 bits supported in some PDCCHs. Even if the 164-bit limit can be increased, the embedded DCI may still be larger and may require a more general code block segmentation algorithm. Some aspects of wireless communication can utilize the beta offset parameter β.offset This indicates the amount of RE used for DCI and the payload size of DCI. If these values ​​can be calculated against PDSCH, then the amount of RE used for DCI can be calculated.

[0053] Some aspects of wireless communication can utilize the payload size (K) of DCI. DCI ) and β offset To control the coding rate of the mounted DCI, the number of REs used for the mounted DCI can be calculated as follows: The total number of encoded bits M can be equal to: M = N RE,DCI *Qm, where Qm is the number of bits per modulation symbol. For QPSK, Qm can be 2 bits per symbol. For 64QAM, Qm can be 6 bits per symbol. In some aspects, a modulation symbol can be mapped to a RE. So if Qm = 2, then N RE,DCI = M / 2. Therefore, M / 2 REs may then be needed to carry the total coded bits. Furthermore, if M = 512, the coded bits may need to be split or divided into multiple code blocks (CBs). Therefore, CBs can be the method used to organize the coded bits. If the DCI payload size and the beta offset parameter are known, the number of REs (N) can be calculated. RE,DCI By doing so, the total number of coded bits (M) can also be calculated.

[0054] As noted above, there is a current need for transmitting a large amount of DCI over the PDSCH. If the DCI payload size K includes CRC bits... DCI If it is greater than 140, then more than one CB can be used. If K DCI If it is less than 140, then a CB can be used. Therefore, if K DCI If the number is greater than 140, it may be necessary to divide it into more than one CB. Therefore, there are the total number of coded bits (M) and the number of information bits in the DCI (K). DCI The current need to divide or partition into one or more code blocks (CBs).

[0055] Various aspects of this disclosure allow for the transmission of a large number of DCIs on the PDSCH. For example, various aspects of this disclosure can increase the total number of coded bits (M) and the number of information bits in the DCI (K). DCI It can be divided or partitioned into one or more code blocks (CBs). Furthermore, if K... DCI If the number is greater than 140, this disclosure may be divided or divided into more than one CB.

[0056] Various aspects of this disclosure can also utilize CB segmentation based on coded bits. For example, this disclosure can calculate the number of available coded bits and determine the number of CBs used for CB segmentation, based on the principle that each CB has approximately 512 coded bits. This can result in increased coding gain. Furthermore, a transport block (TB) may include multiple CBs.

[0057] Various aspects of this disclosure also use the number of coded bits (M) to determine the number of code blocks (CBs). Therefore, by determining the amount of CBs, this disclosure can perform coded bit segmentation. In some aspects, this disclosure may use padding bits to align the payload size of each CB (used in UCI CB segmentation), so the number of information bits in each CB can be similar. This disclosure may also use repetition to align the coded bit size of each CB (also used in UCICB segmentation).

[0058] To perform the aforementioned calculations and determinations, various aspects of this disclosure may utilize one or more algorithms or equations. In some aspects, this disclosure may utilize a single CB when M ≤ 512 * α, where α = 9 / 8. By doing so, encoding can utilize existing designs for PDCCH. When M > 512 * α, this disclosure may also utilize multiple CBs with segmentation. This can result in all CBs having the same encoder, with the same number of information bits and encoded bits.

[0059] In some respects, the quantity A of CB can be: Furthermore, the number of information bits per CB without CRC can be: The number of coded bits per CB can be: Furthermore, if E ≤ 512*α, this disclosure allows the use of existing designs for PDCCH. As noted herein, a number of padding bits can be utilized for the DCI payload. In some instances, K*AK will be used. DCI Appending a zero to the DCI payload of the first CB helps ensure that the number of information bits per CB is similar. Furthermore, if the DCI payload is a multiple of A, padding bits may not be necessary. Aspects of this disclosure may also utilize a number of repeated coded bits for the final coded block. This disclosure may also repeat coded bits for the final coded block (e.g., ME*A coded bits) to ensure that the number of coded bits per CB is similar. Furthermore, if M is a multiple of E, there may be no need to add repeating bits.

[0060] Figure 4This is an example schematic diagram 400 of DCI segmentation based on one or more techniques according to this disclosure. Schematic diagram 400 includes a DCI payload 410, padding bits 412, code blocks 421, 422, 423, 424, 425, 426, coded blocks 431, 432, 433, 434, 435, 436, and repeating bits 440. Figure 4 As shown, the DCI payload 410 and padding bits 412 can undergo segmentation and the addition of CRC bits to be converted into code blocks 421-426. Furthermore, code blocks 421-426 can undergo polar coding to be converted into code blocks 431-436.

[0061] Figure 4 Some aspects may include the following values: DCI payload (K DCI The code has 808 bits and a coding rate (R) of 1 / 4. Therefore, the number of coded bits (M) = K. DCI / R = 808 / (1 / 4) = 3232. The number of encoded bits can also be calculated using the following equation: M = N RE,DCI *Qm. In addition, the number of CBs. It consists of approximately 6 code blocks. The amount of padding bits added can also lead to K. DCI It is a multiple of A. This ensures that the number of information bits added to each CB includes the same value. In this case, there can be 2 padding bits appended to an 808-bit DCI payload = 808 + 2 = 810 bits, which is a multiple of 6.

[0062] Furthermore, the number of information bits (K) per CB without CRC is equal to: K = K DCI / A = 808 / 6 = 134.67, which is approximately 135. The number of information bits per CB with a 16-bit CRC = K + 16 = 135 + 16 = 151. Furthermore, the coded block size, or the number of coded bits per CB (E), is equal to: E = M / A = 3232 / 6 = 538. If M is not a multiple of E, repeating bits can be added. Here, since 3232 is not a multiple of 538, there can be 4 repeating bits added to the last block to make it a multiple of 538.

[0063] As described above, an 808-bit (plus 2 padding bits) DCI payload can be segmented or divided into 6 blocks. This results in 135 information bits per block (without CRC). Therefore, each block contains 151 information bits (with 16 bits of CRC). Furthermore, polar coding can result in a 538-bit code block size (with 4 repeating bits).

[0064] Some aspects of this disclosure may include an improved coding gain angle. For example, the maximum CB size K. max It can have an impact on UE implementation. Maximum number of CBs (Continuous Controllers) C max This could be a UE capability. Various aspects of this disclosure can also introduce a minimum CB size K. min Therefore, these aspects of this disclosure may include similar steps as mentioned above, but with a maximum and minimum CB size and / or a maximum CB number.

[0065] This disclosure may also include multiple steps for the maximum and minimum CB size and / or the maximum number of CBs. For example, this disclosure may use the calculated number of coded bits C to determine the number of code blocks. If C > C max (The maximum number of CBs that the UE can handle), then this disclosure can set C=C max In some instances, if (Maximum CB size) may contain errors. Furthermore, if... And if C>1, then C=C-1.

[0066] Various aspects of this disclosure may also use multiple CRC bits for a Transport Block (TB). For PDSCH or PUSCH CB segmentation, a 24-bit CRC may exist for a TB. If CB segmentation exists, a 24-bit CRC may be added for each CB. For UCI segmentation (up to 2 CBs), an 11-bit CRC may exist for each CB. In some aspects, the entire DCI payload may correspond to a TB. Since the DCI payload may include a number of CRC bits, each TB may include a number of CRC bits. Therefore, the amount of information bits in each TB may be segmented into one or more CBs.

[0067] As noted above, aspects of this disclosure may include embedded DCI CB segmentation. In some aspects, embedded DCI decoding may not comply with blind decoding, for example, because a long CRC may not be necessary. In some instances, this disclosure may reuse the UCI CRC insertion mechanism and add 11 bits of CRC to the TB. This disclosure may also utilize 16 bits of CRC for the TB. This can be the same amount of CRC bits in the PDSCH. Furthermore, this disclosure may utilize 19 bits of CRC for the TB. Thus, this disclosure may utilize three more bits for a Sequential Elimination List (SCL) decoder with L=8, for example, for a single block without CB CRC. Therefore, if the TB is smaller than the maximum payload of the CB, segmentation may not be necessary. By doing so, the decoder can directly decode the TB. Therefore, the amount of CRC bits used for each TB can be 0, 11, 16, or 19.

[0068] Various aspects of this disclosure may also utilize a number of CRC bits for each CB. In some aspects, this disclosure may reuse the UCI CRC insertion mechanism and add 11 bits of CRC for each CB. This may not have an impact based on, for example, polar code CB segmentation applied to a UCI with two CBs. This disclosure may also apply a 16-bit CRC. For example, more CBs may exist for DCI carrying, thus requiring improved CRC protection. Various aspects of this disclosure may also utilize a 19-bit CRC. Therefore, this disclosure may utilize three more bits for an SCL decoder with L=8 for each CB. Various aspects of this disclosure may also choose between 11-bit and 19-bit CRC depending on the number of CBs. Thus, the number of CRC bits for each CB can be 0, 11, 16, or 19. Therefore, the number of CRC bits for each CB may depend on the number of CBs.

[0069] Figure 5 This is a schematic diagram 500 illustrating example communication between UE 502 and base station 504. At 510, base station 504 may receive an indication of the number of downlink control information (DCI) bits. At 520, base station 504 may calculate the number of encoded bits based on the number of DCI information bits. In some aspects, the number of encoded bits may be further calculated based on at least one of a beta offset parameter or the number of resource elements (REs) used for DCI. Furthermore, the number of DCI information bits may include the number of cyclic redundancy check (CRC) bits, wherein the number of CRC bits may be equal to 0, 11, 16, or 19.

[0070] At 530, base station 504 can determine the amount of one or more code blocks (CBs) in the DCI based on at least one of the number of coded bits or the number of DCI information bits, wherein each CB in the one or more CBs may include multiple coded bits. Furthermore, the amount of one or more CBs may be equal to the number of coded bits divided by the product of the alpha parameter and 512. In some aspects, when the number of DCI information bits is not a multiple of the amount of one or more CBs, the number of DCI information bits may include the number of padding bits.

[0071] At 540, base station 504 can divide the number of coded bits into one or more blocks (CBs). In some aspects, the number of coded bits per CB can be equal to the number of coded bits divided by the number of one or more CBs. Alternatively, when the number of coded bits is not a multiple of the number of coded bits per CB, the number of coded bits per coded block can include the number of repeating bits.

[0072] At 550, base station 504 can modulate this number of coded bits into multiple symbols. In some aspects, multiple symbols can be mapped to multiple resource elements (REs). At 560, base station 504 can encode one or more CBs in the DCI based on the determined amount of one or more CBs, wherein the encoded one or more CBs can correspond to one or more coded blocks.

[0073] At 570, base station 504 may transmit a Physical Downlink Shared Channel (PDSCH) including the DCI (e.g., PDSCH 572). At 580, UE 502 may receive a PDSCH including the DCI (e.g., PDSCH 572). In some instances, the DCI may include at least one or more CBs or one or more coded blocks.

[0074] In some respects, the DCI can be divided into one or more CBs or at least one of one or more coded blocks. Furthermore, each CB in the one or more CBs may include a number of Cyclic Redundancy Check (CRC) bits, wherein the number of CRC bits may be equal to 0, 11, 16, or 19. Additionally, the number of coded bits may be equal to the number of DCI information bits divided by the coding rate. Furthermore, the number of DCI information bits may correspond to a transport block (TB).

[0075] Figure 6This is a flowchart 600 of a wireless communication method. The method can be performed by a base station or a component of a base station (e.g., base station 102, 180, 310, 504; apparatus; processing system, which may include memory 376 and may be the entire base station or a component of a base station, such as TX processor 316, RX processor 370, and / or controller / processor 375). Optional aspects are shown in dashed lines. The method described herein can provide several benefits, such as improved communication signaling, resource utilization, and / or power savings.

[0076] At position 602, the device can receive an indication of the number of downlink control information (DCI) bits, such as in conjunction with... Figure 4 and 5 The example described in [the document / reference] is as follows.

[0077] At position 604, the device can calculate the number of coded bits based on the number of downlink control information (DCI) bits, such as by combining... Figure 4 and 5 The example described in [the document] illustrates this. In some aspects, the number of encoded bits can be further calculated based on at least one of the beta offset parameter or the number of resource elements (REs) used for DCI, such as in combination with [other parameters]. Figure 4 and 5 The example described in [the document] further illustrates this. Additionally, the number of DCI information bits can include the number of Cyclic Redundancy Check (CRC) bits, where the number of CRC bits can be equal to 0, 11, 16, or 19, as described in [the document]. Figure 4 and 5 The example described in [the document / reference] is as follows.

[0078] At 606, the device can determine the amount of one or more code blocks (CBs) in the DCI based on at least one of the number of coded bits or the number of DCI information bits, wherein each of the one or more CBs may include multiple coded bits, such as in combination Figure 4 and 5 The example described in [the document] further illustrates this. Additionally, the amount of one or more CBs can be equal to the number of encoded bits divided by the product of the alpha parameter and 512, as in [the context of] combining [the data]. Figure 4 and 5 The example described in [the document] illustrates this. In some aspects, when the number of DCI information bits is not a multiple of the amount of one or more CBs, the number of DCI information bits may include the number of padding bits, such as in combination with [other elements]. Figure 4 and 5 The example described in [the document / reference] is as follows.

[0079] At 608, the device can divide the number of coded bits into one or more CBs, such as in combination. Figure 4 and 5The example described in [the document] illustrates this. In some respects, the amount of coded bits per CB can be equal to the number of coded bits divided by the amount of one or more CBs, as in [the context of] combining [various methods]. Figure 4 and 5 The example described in [the document] further illustrates this. Additionally, when the number of coded bits is not a multiple of the number of coded bits per CB, the number of coded bits per coded block may include the number of repeating bits, as combined with [other parameters]. Figure 4 and 5 The example described in [the document / reference] is as follows.

[0080] At position 610, the device can modulate this number of coded bits into multiple symbols, such as combining... Figure 4 and 5 The examples described in [the document] illustrate this. In some aspects, multiple symbols can be mapped to multiple resource elements (REs), such as combining [symbols]. Figure 4 and 5 The example described in [the document / reference] is as follows.

[0081] In 612, the device can encode one or more CBs in the DCI based on the determined amount of one or more CBs, such as in combination with Figure 4 and 5 The examples described herein. In some aspects, one or more encoded CBs may correspond to one or more encoded blocks, such as in combination. Figure 4 and Figure 5 The example described in [the document / reference] is as follows.

[0082] At position 614, the device can transmit the Physical Downlink Shared Channel (PDSCH) including DCI, such as in combination with Figure 4 and 5 The examples described herein. In some instances, the DCI may include at least one of one or more CBs or one or more coded blocks, such as in combination. Figure 4 and 5 The example described in [the document / reference] is as follows.

[0083] In some respects, the DCI can be divided into at least one of one or more CBs or one or more coded blocks, such as in combination. Figure 4 and 5 The example described in [the document] further illustrates this. Additionally, each of one or more CBs may include a number of Cyclic Redundancy Check (CRC) bits, wherein the number of CRC bits may be equal to 0, 11, 16, or 19, as combined with [other parameters]. Figure 4 and 5 The example described in [the document] further illustrates this. Additionally, the number of encoded bits can be equal to the number of DCI information bits divided by the coding rate, as in [the context of] combining [various methods]. Figure 4 and 5 The example described in [the document] further illustrates this. Additionally, the number of DCI information bits can correspond to a transport block (TB), as combined with [other data]. Figure 4 and 5 The example described in [the document / reference] is as follows.

[0084] Further disclosures are included in the appendix.

[0085] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowchart is illustrative of the example method. It should be understood that the specific order or hierarchy of the boxes in the process / flowchart may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims give the elements of each box in the order of instance, but this does not imply limitation to the specific order or hierarchy given.

[0086] The foregoing description is provided to enable any person skilled in the art to implement the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are given the full scope consistent with the textual claims, wherein, unless expressly stated otherwise, references to elements in the singular form are not intended to mean “one and only one,” but rather “one or more.” The term “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless expressly stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include 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, wherein any such combination may contain one or more members of A, B, or C. All structural and functional equivalents of the elements described throughout the various aspects of this disclosure are expressly incorporated herein by reference and intended to be included by the claims, and such structural and functional equivalents are known to or will be known later to those skilled in the art. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly stated in the claims. The terms "module", "mechanism", "element", "device", etc., may not be a substitute for the term "unit". Therefore, no element of a claim should be construed as a unit function unless that element is expressly stated using the phrase "unit for...".

[0087] appendix

[0088] Larger DCI transmission on PDSCH

[0089] Background - UCI Transmission on PUSCH

[0090] • Current specifications already support UCI-enabled transmission within the PUSCH.

[0091] For rate matching of UCI on PUSCH, the rate scaling factor β offset>1 is used to obtain a comparison with the indicated MCS.

[0092] low bitrate

[0093] • Omitting some details, the number of REs per layer used for UCI is

[0094]

[0095] Where, N RE K is the total number of Re in each layer of PUSCH. UL-SCH It is the payload size of UL-SCH including TB / CB CRC bits, and K UCI This is the number of UCI payload sizes, including CRC bits (if any).

[0096] To prevent UCI from consuming excessive PUSCH resources, a partial factor α∈{0.5,0.65,0.8,1.0} will limit the maximum amount of resources that UCI can consume, and

[0097]

[0098] Background - Channel Coding for PDCCH

[0099] • Polar codes are used for the control channel in NR.

[0100] The maximum coded block size is 512 bits for downlink and 1024 bits for uplink.

[0101] The minimum coding rate is 1 / 8

[0102] The maximum payload size without CRC is 140 bits.

[0103] Append a 24-bit CRC to the payload.

[0104] Rate matching schemes include shortening, punching, and repeating.

[0105] The decoding complexity is O(N×log2(N)), where N is the number of encoded bits.

[0106] In other words, complexity is not a direct function of coding rate.

[0107] Of course, with a large number of information bits, there will be a loss in coding gain.

[0108] • Code block size determined

[0109] Assume the number of information bits is K, and the number of encoded bits is N = 2. n And the block size (after rate matching) is E

[0110] If and but

[0111] Otherwise

[0112] ο

[0113] οn=max{min{n1,n2,n max},n min}, where n min =5

[0114] Question - How to send long-carry DCI in PDSCH

[0115] • The previous proposal was to use DCI onboarding in PDSCH, which is similar to UCI onboarding in PUSCH.

[0116] The embedded DCI is an aggregation of multiple DL / UL permissions, therefore delivering these permissions in the PDSCH is more efficient than sending them in the PDCCH area in the case of blind decoding.

[0117] • The aggregated onboard DCI length can be greater than the maximum of 164 bits supported in the current PDCCH.

[0118] Even if we increase the limit to 164, the size of the embedded DCI could be even larger, and we would need a general-purpose code block segmentation algorithm.

[0119] • Previous proposals used the payload sizes KDCI and β for DCI. offset To control the coding rate of the mounted DCI, the number of REs used for the mounted DCI can be calculated as follows: (The calculations may be more complex)

[0120] The total number of encoded bits will be: M = N RE,DCI *Qm, where Qm is the number of bits on a single modulation symbol.

[0121] In previous attempts, the maximum number of information bits used for the PDCCH was 140 bits.

[0122] The question is how to combine M (the total number of encoded bits) and K DCI (The number of information bits in the DCI, e.g., the size of the DCI payload including CRC bits) is divided into code blocks.

[0123] Design 1: CB segmentation based on encoded bits

[0124] The key idea is to first calculate the number of available coded bits, based on the principle that the coded bits per CB are approximately 512 (optimal coding gain), and then determine the number of CBs used for CB segmentation.

[0125] • Proposal: Use the calculated number of coded bits to determine the number of code blocks.

[0126] Use padding to align the payload size of each CB (already used in UCI CB segmentation).

[0127] Repetition is used to align the encoded bit size of each CB (already used in UCI CB segmentation).

[0128] ·algorithm:

[0129] When M≤512*α, where α=9 / 8, a single CB

[0130] Therefore, we can use the existing design for encoding PDCCH.

[0131] When M > 512 * α, multiple CBs are used, and all CBs have the same encoder, with the same number of information bits and encoded bits.

[0132] • Quantity of CB:

[0133] • Number of information bits per CB without CRC:

[0134] • Number of coded bits per CB:

[0135] Since E≤512*α, the existing design is also used for PDCCH.

[0136] • Stuffing bits used for DCI payload

[0137] ο K*AK DCI Add a zero before the DCI payload of the first CB to ensure that the information bits are the same for each CB.

[0138] • Repeated encoded bits for the last block

[0139] Repeat the last ME*A coded bits for the last coded block to ensure that the coded bits for each CB are the same.

[0140] Example of DCI segmentation

[0141] ·parameter

[0142] οK DCI=808; M=3232 (R=1 / 4)

[0143] oA = 6 code blocks

[0144] The number of information bits K = 135, and the block size E = 538.

[0145] ο2 padding bits are appended to the DCI payload

[0146] Repeat the last 4 bits for the last block.

[0147]

[0148] Design 2

[0149] Design 2 is derived from the optimal coding gain angle and needs to take into account:

[0150] ο Maximum CB size K max (This can have implications for UE implementation)

[0151] ο Maximum number of CB C max (This could be a UE capability)

[0152] ο We can also introduce a minimum CB size K min

[0153] ·proposal:

[0154] Step 1: Use the calculated number of coded bits C to determine the number of code blocks.

[0155] Step 2: If C > C max (The number of CBs that the UE can process), then C = C max

[0156] Step 3: If (Maximum CB size), then error cases

[0157] Step 4: When And when C>1, C=C-1

[0158] The remaining steps follow Design 1

[0159] Number of CRC bits used for TB

[0160] ·background:

[0161] For PDSCH / PUSCH CB splits, we have a 24-bit CRC for TB, and if a CB split exists, we will add a 24-bit CRC for each CB.

[0162] For UCI splits (up to 2 CBs), we will have an 11-bit CRC for each CB.

[0163] Question: What will we do for mounted DCI CB segmentation?

[0164] • Considering that onboard DCI decoding does not comply with blind decoding, a long CRC seems unnecessary. Option 1: Reuse the UCICRC insertion mechanism and add an 11-bit CRC to the TB.

[0165] Option 2: 16 bits

[0166] This is the same as the CRC bits in PDSCH.

[0167] Option 3: 19 bits

[0168] • For single blocks without CB CRC, three additional bits are used for the SCL decoder with L=8.

[0169] Number of CRC bits used for CB

[0170] Option 1: Reuse the UCI CRC insertion mechanism and add an 11-bit CRC to each CB.

[0171] This may not have canonical implications, as the current specification discusses polar code CB segmentation (although it is only applied to UCI with two CBs).

[0172] Option 2: Considering we can have more CBs for DCI mounting, better CRC protection may be needed, and a 16-bit CRC can be applied.

[0173] Option 3: 19 bits

[0174] For each CB, 3 more bits are used for the SCL decoder with L=8.

[0175] Option 4: Choose between 11-bit and 19-bit CRC, depending on how many CBs we have.

[0176]

Claims

1. A method of wireless communication of a base station, comprising: calculating a number of coded bits based on a number of downlink control information (DCI) information bits; determining a quantity of one or more code blocks (CBs) in a DCI based on at least one of the number of coded bits or the number of DCI information bits, each of the one or more CBs comprising a plurality of coded bits, wherein the quantity of the one or more CBs is based on the number of coded bits divided by a product of an alpha parameter and a maximum code block size; and transmitting a physical downlink shared channel (PDSCH) comprising the DCI, wherein the DCI comprises at least one of the one or more CBs or one or more coded blocks.

2. The method of claim 1, further comprising: receiving an indication of the number of DCI information bits.

3. The method of claim 1, further comprising: encoding the one or more CBs in the DCI based on the determined quantity of one or more CBs, wherein the encoded one or more CBs correspond to the one or more coded blocks; and modulating the number of coded bits as a plurality of symbols, wherein the plurality of symbols are mapped to a plurality of resource elements (REs).

4. The method of claim 1, further comprising: splitting the number of coded bits into the quantity of one or more CBs.

5. The method of claim 4, wherein, a first quantity of coded bits per CB is equal to the number of coded bits divided by the quantity of one or more CBs.

6. The method of claim 4, wherein, a first quantity of coded bits per code block includes a number of repetition bits when the number of coded bits is not a multiple of the quantity of coded bits per CB.

7. The method of claim 1, wherein, the DCI is split into at least one of the one or more CBs or the one or more coded blocks.

8. The method of claim 1, wherein, the maximum code block size is 512 and the quantity of one or more CBs is equal to the number of coded bits divided by the product of the alpha parameter and 512.

9. The method of claim 1, wherein, each of the one or more CBs includes a number of cyclic redundancy check (CRC) bits, wherein the number of CRC bits is equal to 0, 11, 16, or 19.

10. The method of claim 1, wherein, the number of DCI information bits includes a number of padding bits when the number of DCI information bits is not a multiple of the quantity of one or more CBs.

11. The method of claim 1, wherein, the number of coded bits is equal to the number of DCI information bits divided by a coding rate.

12. The method of claim 1, wherein, the number of DCI information bits corresponds to a transport block (TB).

13. The method of claim 1, wherein, the number of DCI information bits includes a number of cyclic redundancy check (CRC) bits, wherein the number of CRC bits is equal to 0, 11, 16, or 19.

14. The method of claim 1, wherein, the number of coded bits is further calculated based on at least one of a beta offset parameter or a number of resource elements (REs) for the DCI.

15. An apparatus for wireless communication of a base station, comprising: a memory; and at least one processor coupled to the memory and configured to: calculate a number of coded bits based on a number of downlink control information (DCI) information bits; determining a quantity of one or more code blocks (CBs) in a DCI based on at least one of the number of coded bits or the number of DCI information bits, each of the one or more CBs comprising a plurality of coded bits, wherein the quantity of the one or more CBs is based on the number of coded bits divided by a product of an alpha parameter and a maximum code block size; and transmitting a physical downlink shared channel (PDSCH) comprising the DCI, wherein the DCI comprises at least one of the one or more CBs or one or more coded blocks. determine a quantity of one or more code blocks (CBs) in the DCI based on at least one of a quantity of the coded bits or a quantity of the DCI information bits, each of the one or more CBs including a plurality of coded bits, wherein the quantity of the one or more CBs is based on the quantity of the coded bits divided by a product of an alpha parameter and a maximum code block size; and transmit a physical downlink shared channel (PDSCH) including the DCI, wherein the DCI includes at least one of the one or more CBs or one or more code blocks.

16. The apparatus of claim 15, wherein, the at least one processor is further configured to: receive an indication of the quantity of the DCI information bits.

17. The apparatus of claim 15, wherein, the at least one processor is further configured to: encode the one or more CBs in the DCI based on the determined quantity of the one or more CBs, wherein the encoded one or more CBs correspond to the one or more code blocks.

18. The apparatus of claim 17, wherein, the at least one processor is further configured to: modulate the quantity of coded bits as a plurality of symbols.

19. The apparatus of claim 18, wherein, the plurality of symbols are mapped to a plurality of resource elements (REs).

20. The apparatus of claim 15, wherein, the at least one processor is further configured to: divide the quantity of coded bits into the quantity of the one or more CBs.

21. The apparatus of claim 20, wherein, a first quantity of coded bits per CB is equal to the quantity of the coded bits divided by the quantity of the one or more CBs.

22. The apparatus of claim 20, wherein, a first quantity of coded bits per code block includes a quantity of repetition bits when the quantity of the coded bits is not a multiple of the quantity of coded bits per CB.

23. The apparatus of claim 15, wherein, the DCI is divided into at least one of the one or more CBs or the one or more code blocks.

24. The apparatus of claim 15, wherein, the maximum code block size is 512 and the quantity of the one or more CBs is equal to the quantity of the coded bits divided by the product of the alpha parameter and 512.

25. The apparatus of claim 15, wherein, each of the one or more CBs includes a quantity of cyclic redundancy check (CRC) bits, wherein the quantity of the CRC bits is equal to 0, 11, 16, or 19.

26. The apparatus of claim 15, wherein, the quantity of the DCI information bits includes a quantity of padding bits when the quantity of the DCI information bits is not a multiple of the quantity of the one or more CBs.

27. The apparatus of claim 15, wherein, the quantity of the coded bits is equal to the quantity of the DCI information bits divided by a coding rate.

28. The apparatus of claim 15, further comprising: a transceiver coupled to the at least one processor.

29. An apparatus for wireless communication at a base station, comprising: means for calculating a quantity of coded bits based on a quantity of downlink control information (DCI) information bits; means for determining a quantity of one or more code blocks (CBs) in the DCI based on at least one of a quantity of the coded bits or a quantity of the DCI information bits, each of the one or more CBs including a plurality of coded bits, wherein the quantity of the one or more CBs is based on the quantity of the coded bits divided by a product of an alpha parameter and a maximum code block size; and means for transmitting a physical downlink shared channel (PDSCH) including the DCI, wherein the DCI includes at least one of the one or more CBs or one or more code blocks. means for transmitting a physical downlink shared channel (PDSCH) including the DCI, wherein the DCI includes at least one of the one or more CBs or one or more code blocks.

30. A non-transitory computer-readable medium storing computer-executable code for wireless communication by a base station, the code when executed by a processor cause the processor to: calculate a number of coded bits based on a number of downlink control information (DCI) information bits; determining a quantity of one or more code blocks (CBs) in the DCI based on at least one of the number of coded bits or the number of DCI information bits, each of the one or more CBs including a plurality of coded bits, wherein a quantity of the one or more CBs is based on a product of the number of coded bits divided by an alpha parameter and a maximum code block size; and transmit a physical downlink shared channel (PDSCH) including the DCI, wherein the DCI includes at least one of the one or more CBs or one or more code blocks.

Images