CN117480745A - Erasure LDPC rate matching for TB over multiple timeslots - Google Patents
Erasure LDPC rate matching for TB over multiple timeslots Download PDFInfo
- Publication number
- CN117480745A CN117480745A CN202280035222.XA CN202280035222A CN117480745A CN 117480745 A CN117480745 A CN 117480745A CN 202280035222 A CN202280035222 A CN 202280035222A CN 117480745 A CN117480745 A CN 117480745A
- Authority
- CN
- China
- Prior art keywords
- rate matching
- slot
- bits
- output bits
- matching output
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 claims abstract description 106
- 230000008569 process Effects 0.000 claims abstract description 34
- 238000004891 communication Methods 0.000 claims description 69
- 230000005540 biological transmission Effects 0.000 claims description 41
- 238000004364 calculation method Methods 0.000 claims description 6
- 230000006870 function Effects 0.000 description 35
- 230000001413 cellular effect Effects 0.000 description 29
- 238000010586 diagram Methods 0.000 description 27
- 238000012545 processing Methods 0.000 description 14
- 238000001228 spectrum Methods 0.000 description 10
- 239000000969 carrier Substances 0.000 description 7
- 238000012937 correction Methods 0.000 description 7
- 238000007726 management method Methods 0.000 description 7
- 239000000872 buffer Substances 0.000 description 5
- 238000013507 mapping Methods 0.000 description 5
- 230000011218 segmentation Effects 0.000 description 5
- 230000006837 decompression Effects 0.000 description 4
- 238000001514 detection method Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 238000005259 measurement Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 230000006835 compression Effects 0.000 description 3
- 238000007906 compression Methods 0.000 description 3
- 230000010287 polarization Effects 0.000 description 3
- 230000011664 signaling Effects 0.000 description 3
- 238000012384 transportation and delivery Methods 0.000 description 3
- 102100036409 Activated CDC42 kinase 1 Human genes 0.000 description 2
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 2
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 2
- 125000004122 cyclic group Chemical group 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000010363 phase shift Effects 0.000 description 2
- 238000012913 prioritisation Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 241000169170 Boreogadus saida Species 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 210000001520 comb Anatomy 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000005611 electricity Effects 0.000 description 1
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 1
- 239000007943 implant Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 239000011159 matrix material Substances 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000013138 pruning Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000009897 systematic effect Effects 0.000 description 1
- 239000003826 tablet Substances 0.000 description 1
- 238000012549 training Methods 0.000 description 1
Abstract
Methods, apparatuses, and computer-readable storage media for rate matching for TBoMS are provided. An example method includes: a time slot length is calculated for each of a plurality of UL time slots, the time slot length for each UL time slot being associated with a plurality of rate matching output bits, each UL time slot including a starting point for the plurality of rate matching output bits, the time slot length for each UL time slot being associated with a starting boundary, the plurality of UL time slots being associated with at least one of a single TB or a single rate matching. An example method may include allocating one or more bits of the plurality of rate-matched output bits for a modulation process. An example method may include avoiding allocation of at least one bit of the plurality of rate-matched output bits for the modulation procedure, the at least one bit corresponding to UCI multiplexing.
Description
Cross Reference to Related Applications
The present application claims the benefit and priority of U.S. provisional patent application Ser. No. 63/192,546 entitled "ERASURE STYLE LDPC RATE MATCHING FOR TB OVER MULTIPLE SLOTS" filed 24 at 2021 and U.S. non-provisional patent application Ser. No. 17/664,630 entitled "ERASURE STYLE LDPC RATE MATCHING FOR TB OVER MULTIPLE SLOTS" filed 23 at 2022, the entire contents of which are expressly incorporated herein by reference.
Technical Field
The present disclosure relates generally to communication systems, and more particularly, to wireless communication systems utilizing transport blocks (tbos) over multiple time slots.
Background
Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may use multiple-access techniques that enable communication with multiple users by sharing the available system resources. Examples of such multiple-access techniques 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.
These multiple access techniques have been employed in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An example of a telecommunications standard is the 5G New Radio (NR). The 5G NR is part of the continuous mobile broadband evolution promulgated by the third generation partnership project (3 GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the internet of things (IoT)), and other requirements. The 5G NR includes services associated with enhanced mobile broadband (emmbb), large-scale machine-type communication (emtc), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements in the 5G NR technology are needed. These enhancements are also applicable to other multiple access techniques and telecommunication standards employing these techniques.
Disclosure of Invention
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.
In one aspect of the disclosure, methods, computer-readable media, and apparatuses at a User Equipment (UE) are provided. The apparatus can include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to: a time slot length is calculated for each Uplink (UL) time slot of a plurality of UL time slots, the time slot length for each UL time slot being associated with a plurality of rate matching output bits, each UL time slot including a starting point for the plurality of rate matching output bits, the time slot length for each UL time slot being associated with a starting boundary, the plurality of UL time slots being associated with at least one of a single TB or a single rate matching. The memory and the at least one processor coupled to the memory may be further configured to allocate one or more of the plurality of rate matching output bits for the modulation process. The memory and the at least one processor coupled to the memory may be further configured to: skipping (e.g., avoiding) allocation of at least one bit of the plurality of rate matching output bits for the modulation process, the at least one bit corresponding to Uplink Control Information (UCI) multiplexing.
In an aspect of the disclosure, a method, computer-readable medium, and apparatus at a base station are provided. The apparatus can include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to: for the UE to transmit an indication of a PUSCH configuration associated with an allocation of a plurality of rate matching output bits for a modulation procedure, a slot length for each UL slot of a plurality of UL slots associated with a plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, a slot length for each UL slot associated with a starting boundary, the plurality of UL slots associated with at least one of a single TB or a single rate match. The memory and the at least one processor coupled to the memory may be further configured to: UL transmissions are received based on an allocation of one or more of the plurality of rate matching output bits and an allocation of at least one of the plurality of rate matching output bits, the at least one bit being associated with Uplink Control Information (UCI) multiplexing.
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 features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed and the present specification is intended to include all such aspects and their equivalents.
Drawings
Fig. 1 is a diagram illustrating an example of a wireless communication system and an access network.
Fig. 2A is a diagram illustrating an example of a first frame in accordance with aspects of the present disclosure.
Fig. 2B is a diagram illustrating an example of DL channels within a subframe in accordance with aspects of the present disclosure.
Fig. 2C is a diagram illustrating an example of a second frame in accordance with aspects of the present disclosure.
Fig. 2D is a diagram illustrating an example of UL channels within a subframe in accordance with aspects of the present disclosure.
Fig. 3 is a diagram illustrating an example of a base station and a User Equipment (UE) in an access network.
Fig. 4 is a diagram illustrating an example TBoMS.
Fig. 5 illustrates an example communication flow between a UE and a base station.
Fig. 6 is a diagram illustrating an example rate matching.
Fig. 7 is a diagram illustrating an example rate matching.
Fig. 8 is a diagram illustrating an example rate matching.
Fig. 9 is a flow chart of a method of wireless communication.
Fig. 10 is a flow chart of a method of wireless communication.
Fig. 11 is a diagram illustrating an example of a hardware implementation for an example apparatus.
Fig. 12 is a flow chart of a method of wireless communication.
Fig. 13 is a diagram illustrating an example of a hardware implementation for an example apparatus.
Detailed Description
The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be implemented. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. It will be apparent, however, to one skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring the concepts.
Several aspects of the telecommunications system will now be presented with reference to various apparatus and methods. These devices and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
For example, an element, or any portion of an element, or any combination of elements, may 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, system on a chip (SoC), baseband processors, field Programmable Gate Arrays (FPGAs), programmable Logic Devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in the processing system may execute the software. Software should be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subroutines, software components, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like, whether referred to as software, firmware, middleware, microcode, hardware description language, or other names.
Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded on a computer-readable medium as one or more instructions or code. Computer readable media includes computer storage media. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise 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 the foregoing, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.
Although aspects and implementations are described in this application by way of illustration of some examples, those skilled in the art will appreciate that additional implementations and use cases are possible in many different arrangements and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the implementations and/or uses may be produced via integrated chip implementations and other non-module component based devices (e.g., end user devices, vehicles, communication devices, computing devices, industrial devices, retail/purchase devices, medical devices, artificial Intelligence (AI) enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, applicability of the various types of innovations described may occur. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregate, distributed, or Original Equipment Manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical arrangements, devices incorporating the described aspects and features may also include additional components and features for implementation and practice of the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily includes a plurality of components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders/accumulators, etc.). The innovations described herein are intended to be practiced in a variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of different sizes, shapes, and configurations.
Fig. 1 is a diagram illustrating an example of a wireless communication system and access network 100. A wireless communication system, also referred to as a Wireless Wide Area Network (WWAN), includes a base station 102, a UE 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G core (5 GC)). Base station 102 may include a macrocell (high power cellular base station) and/or a small cell (low power cellular base station). The macrocell includes a base station. Small cells include femto cells, pico cells, and micro cells.
A base station 102 configured for 4G LTE, which is collectively referred to as evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN), may interface with the EPC 160 over a first backhaul link 132 (e.g., an S1 interface). A base station 102 configured for 5G NR, which is collectively referred to as a next generation RAN (NG-RAN), may interface with a core network 190 over a second backhaul link 184. Among other functions, the base station 102 may perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobile 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 Services (MBMS), subscriber and device tracking, RAN Information Management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC 160 or the core network 190) through a third backhaul link 134 (e.g., an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.
The base station 102 may communicate wirelessly with the UE 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102 'may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network comprising both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include home nodes B (eNB) (HeNB), which may provide services to a restricted group known as a Closed Subscriber Group (CSG). The communication link 120 between the base station 102 and the UE 104 may include Uplink (UL) (also referred to as reverse link) transmissions from the UE 104 to the base station 102 and/or Downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. Communication link 120 may use multiple-input multiple-output (MIMO) antenna techniques including spatial multiplexing, beamforming, and/or transmit diversity. The communication link may be through one or more carriers. The base station 102/UE 104 may use a spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc.) bandwidth per carrier allocated in carrier aggregation up to a total yxmhz (x component carriers) for transmission in each direction. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric for DL and UL (e.g., more or fewer carriers may be allocated for DL than UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).
Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a Physical Sidelink Broadcast Channel (PSBCH), a Physical Sidelink Discovery Channel (PSDCH), a Physical Sidelink Shared Channel (PSSCH), and a Physical Sidelink Control Channel (PSCCH). D2D communication may be through a variety of wireless D2D communication systems such as, for example, wiMedia, bluetooth, zigBee, wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.
The wireless communication system may also include a Wi-Fi Access Point (AP) 150 that communicates with Wi-Fi Stations (STAs) 152 via a communication link 154 (e.g., in the 5GHz unlicensed spectrum, etc.). When communicating in the unlicensed spectrum, STA 152/AP 150 may perform Clear Channel Assessment (CCA) prior to communication to determine whether a channel is available.
The small cell 102' may operate in licensed and/or unlicensed spectrum. When operating in unlicensed spectrum, the small cell 102' may employ NR and use the same unlicensed spectrum (e.g., 5GHz, etc.) as used by the Wi-Fi AP 150. Small cells 102' employing NRs in the unlicensed spectrum may improve access network coverage and/or increase access network capacity.
The electromagnetic spectrum is generally subdivided into various categories, bands, channels, etc., based on frequency/wavelength. In 5G NR, two initial operating bands have been identified as frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6GHz, FR1 is commonly referred to as the (interchangeably) "sub-6GHz" band in various documents and articles. Similar naming problems sometimes occur with respect to FR2, which is often (interchangeably) referred to in documents and articles as the "millimeter wave" band, although it is different from the Extremely High Frequency (EHF) band (30 GHz-300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" band.
The frequencies between FR1 and FR2 are commonly referred to as mid-band frequencies. Recent 5G NR studies have identified the operating band of these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). The frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend the characteristics of FR1 and/or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation above 52.6 GHz. For example, three higher operating bands have been identified as frequency range names FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz) and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF frequency band.
In view of the above aspects, unless specifically stated otherwise, it should be understood that the term "sub-6GHz" or similar term (if used herein) may broadly refer to frequencies that may be less than 6GHz, frequencies that may be within FR1, or frequencies that may include mid-band frequencies. Furthermore, unless specifically stated otherwise, it should be understood that if the term "millimeter wave" or the like is used herein, it may be broadly meant to include mid-band frequencies, frequencies that may be within FR2, FR4-a or FR4-1 and/or FR5, or may be within the EHF band.
The base station 102, whether small cell 102' or a large cell (e.g., macro base station), may include and/or be referred to as an eNB, next generation node B (gNB ), or another type of base station. Some base stations (e.g., gNB 180) may operate in the conventional sub 6GHz spectrum, in millimeter-wave frequencies, and/or near millimeter-wave frequencies to communicate with the UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. Millimeter-wave base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short distance. The base station 180 and the UE 104 may each include multiple antennas (e.g., antenna elements, antenna panels, and/or antenna arrays) to facilitate beamforming.
The base station 180 may transmit the beamformed signals to the UE 104 in one or more transmit directions 182'. The UE 104 may receive the beamformed signals from the base station 180 in one or more receive directions 182 ". The UE 104 may also transmit the beamformed signals in one or more transmit directions to the base station 180. The base station 180 may receive the beamformed signals from the UEs 104 in one or more receive directions. The base stations 180/UEs 104 may perform beam training to determine the best receive direction and transmit direction for each of the base stations 180/UEs 104. The transmit and receive directions of the base station 180 may or may not be the same. The transmit and receive directions of the UE 104 may or may not be the same.
EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a serving gateway 166, a Multimedia Broadcast Multicast Service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a Packet Data Network (PDN) gateway 172.MME 162 may communicate with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which serving gateway 166 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 BM-SC 170 are connected to an IP service 176.IP services 176 may include the internet, intranets, IP Multimedia Subsystem (IMS), PS streaming services, and/or other IP services. The BM-SC 170 may provide functionality for MBMS user service provision and delivery. The BM-SC 170 may act as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to allocate MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service and may be responsible for session management (start/stop) and collecting eMBMS related charging information.
The core network 190 may include access and mobility management function (AMF) 192, other AMFs 193, session Management Function (SMF) 194, and User Plane Function (UPF) 195. The AMF 192 may communicate with a Unified Data Management (UDM) 196. The AMF 192 is a control node for handling signaling between the UE 104 and the core network 190. In general, AMF 192 provides QoS flows and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. The UPF 195 provides UE IP address assignment as well as other functions. The UPF 195 is connected to an IP service 197. The IP services 197 may include internet, intranet, IP Multimedia Subsystem (IMS), packet Switched (PS) streaming (PSs) services, and/or other IP services.
A base station may include and/or be referred to as a gNB, a node B, eNB, an access point, a base station transceiver, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a transmit-receive point (TRP), or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for the UE 104. Examples of UEs 104 include a cellular telephone, 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 electricity meter, an air pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similarly functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). The 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 communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network in common and/or individually. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network in common and/or individually. The network node or network entity may be implemented as a base station (i.e., an aggregated base station), a disaggregated base station, an Integrated Access and Backhaul (IAB) node, a relay node, a sidelink node, and so on. The network node or network entity may be implemented as a base station (i.e., an aggregated base station), or alternatively, as a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a Near real-time (Near-RT) RAN Intelligent Controller (RIC), or a Non-real-time (Non-RT) RIC in an exploded base station architecture. In some aspects, a network node may be referred to as a network entity, and vice versa.
Referring again to fig. 1, in some aspects, the UE 104 may include a rate matching component 198. In some aspects, the rate matching component 198 may be configured to: a slot length is calculated for each UL slot of the plurality of UL slots, the slot length for each UL slot being associated with a plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, the slot length for each UL slot being associated with a starting boundary, the plurality of UL slots being associated with at least one of a single TB or a single rate match. In some aspects, the rate matching component 198 may also be configured to: one or more of the plurality of rate-matched output bits are allocated for the modulation process. In some aspects, the rate matching component 198 may also be configured to skip (e.g., avoid) allocation of at least one bit of the plurality of rate matching output bits for the modulation process, the at least one bit corresponding to UCI multiplexing. The slot length may be calculated based on the number of bits to be encoded in the slot. In some aspects, the slot length may be further calculated based on the number of REs that may be skipped in the slot due to UCI multiplexing.
In certain aspects, the base station 180 can include a receiving component 199. In some aspects, the receiving component 199 may be configured to: an indication of a PUSCH configuration is sent to the UE, the PUSCH configuration being associated with an allocation of a plurality of rate matching output bits for a modulation procedure, a slot length for each UL slot of a plurality of UL slots being associated with a plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, a slot length for each UL slot being associated with a starting boundary, the plurality of UL slots being associated with at least one of a single TB or a single rate match. In some aspects, the receiving component 199 may be further configured to receive UL transmissions from the UE based on: an allocation of one or more of the plurality of rate matching output bits, and a skip allocation of at least one of the plurality of rate matching output bits based on UCI multiplexing associated with the at least one bit.
Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.
Fig. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. Fig. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. Fig. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. Fig. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division multiplexed (FDD) in which subframes within a set of subcarriers are dedicated to either DL or UL for a particular set of subcarriers (carrier system bandwidth) or time division multiplexed (TDD) in which subframes within a set of subcarriers are dedicated to both DL and UL for a particular set of subcarriers (carrier system bandwidth). In the example provided in fig. 2A, 2C, assuming the 5G NR frame structure is TDD, subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and F is flexibly usable between DL/UL, and subframe 3 is configured with slot format 1 (all UL). Although subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. The slot formats 0, 1 are full DL, full UL, respectively. Other slot formats 2-61 include a mix of DL symbols, UL symbols, and flexible symbols. The UE is configured with a slot format (dynamically configured by DL Control Information (DCI) or semi-statically/statically configured by Radio Resource Control (RRC) signaling) through a received Slot Format Indicator (SFI). It should be noted that the above description also applies to the 5G NR frame structure as TDD.
Fig. 2A-2D illustrate frame structures, and aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and/or different channels. One frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more slots. The subframe may also include a minislot, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols depending on whether the Cyclic Prefix (CP) is normal or extended. For a normal CP, each slot may include 14 symbols, and for an extended CP, each slot may include 12 symbols. The symbols on DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or Discrete Fourier Transform (DFT) -spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to single stream transmission only). The number of slots within a subframe is based on CP and digital schemes. The digital scheme defines a subcarrier spacing (SCS) and effectively defines a symbol length/duration that is equal to 1/SCS.
TABLE 1
For a normal CP (14 symbols/slot), different digital schemes μ0 to 4 allow 1, 2, 4, 8 and 16 slots, respectively, per subframe. For extended CP, digital scheme 2 allows 4 slots per subframe. Thus, for a normal CP and digital scheme μ, there are 14 symbols/slot and 2 μ Each slot/subframe. The subcarrier spacing may be equal to 2 μ *15kHz, where μ is the digital schemes 0 through 4. As such, the digital scheme μ=0 has a subcarrier spacing of 15kHz, and the digital scheme μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely proportional to the subcarrier spacing. Fig. 2A-2D provide examples of a digital scheme μ=2 with a 14 symbol per slot normal CP and 4 slots per subframe. The slot duration is 0.25ms, the subcarrier spacing is 60kHz, and the symbolThe duration was approximately 16.67 mus. Within the frame set, there may be one or more different bandwidth portions (BWP) of the frequency division multiplexing (see fig. 2B). Each BWP may have a specific digital scheme and CP (normal or extended).
The frame structure may be represented using a resource grid. Each slot includes Resource Blocks (RBs) (also referred to as Physical RBs (PRBs)) that extend for 12 consecutive subcarriers. The resource grid is divided into a plurality of Resource Elements (REs). The number of bits carried by each RE depends on the modulation scheme.
As shown in fig. 2A, some of the REs carry a reference (pilot) signal (RS) for the UE. The RSs may include demodulation RSs (DM-RSs) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RSs) for channel estimation at the UE. The RSs may also include beam measurement RSs (BRSs), beam Refinement RSs (BRRSs), and phase tracking RSs (PT-RSs).
Fig. 2B shows an example of various DL channels within a subframe of a frame. A Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in one OFDM symbol of an RB. The PDCCH within one BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during a PDCCH monitoring occasion on CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWP may be located at higher and/or lower frequencies over the channel bandwidth. The Primary Synchronization Signal (PSS) may be within symbol 2 of a particular subframe of a frame. PSS is used by UE 104 to determine subframe/symbol timing and physical layer identity. The Secondary Synchronization Signal (SSS) may be within symbol 4 of a particular subframe of a frame. The UE uses SSS to determine the physical layer cell identification group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine a Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. A Physical Broadcast Channel (PBCH) carrying a Master Information Block (MIB) may be logically grouped with PSS and SSS to form a Synchronization Signal (SS)/PBCH block (also referred to as an SS block (SSB)). The MIB provides the 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 (e.g., system Information Blocks (SIBs)) not transmitted over the PBCH, and paging messages.
As shown in fig. 2C, some REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS of a Physical Uplink Control Channel (PUCCH) and DM-RS of a Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS may be transmitted in the previous or the previous two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations according to whether the short PUCCH or the long PUCCH is transmitted and according to a specific PUCCH format used. Although not shown, the UE may transmit a Sounding Reference Signal (SRS). The SRS may be transmitted in the last symbol of the subframe. The SRS may have a comb structure, and the UE may transmit the SRS on one of the combs. The base station may use SRS for channel quality estimation to enable scheduling in terms of frequency on the UL.
Fig. 2D shows examples of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries Uplink Control Information (UCI) such as a scheduling request, a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), a Rank Indicator (RI), and hybrid automatic repeat request (HARQ) Acknowledgement (ACK) (HARQ-ACK) feedback (e.g., one or more HARQ ACK bits indicating one or more ACKs and/or Negative ACKs (NACKs)). PUSCH carries data and may additionally be used to carry Buffer Status Reports (BSR), power Headroom Reports (PHR), and/or UCI.
Fig. 3 is a block diagram of a base station 310 in an access network in communication with a UE 350. In DL, IP packets from EPC 160 are provided to controller/processor 375. Controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a Radio Resource Control (RRC) layer, and layer 2 includes a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. Controller/processor 375 provides: RRC layer functions associated with: broadcast of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with: header compression/decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with: transmission of upper layer Packet Data Units (PDUs), error correction by ARQ, concatenation, segmentation and reassembly of RLC Service Data Units (SDUs), re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs onto Transport Blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction by HARQ, priority handling, and logical channel prioritization.
The Transmit (TX) processor 316 and the 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 on the transport channel, forward Error Correction (FEC) encoding/decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation/demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping for the signal constellation based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to OFDM subcarriers, 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 generate a physical channel for carrying the time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce a plurality of spatial streams. The channel estimates from channel estimator 374 may be used to determine the coding and modulation scheme, as well as spatial processing. The channel estimate may be derived from reference signals and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 by a separate transmitter 318 TX. Each transmitter 318TX may modulate a Radio Frequency (RF) carrier with a respective spatial stream for transmission.
At the UE 350, each receiver 354RX receives a signal via its respective antenna 352. Each receiver 354RX recovers information modulated onto an RF carrier and provides the information to the Receive (RX) processor 356.TX processor 368 and RX processor 356 implement layer 1 functions associated with various signal processing functions. RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for UE 350. If multiple spatial streams are destined for the UE 350, they may be combined into a single OFDM symbol stream by an RX processor 356. An RX processor 356 then uses a Fast Fourier Transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal comprises 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 likely signal constellation points transmitted by base station 310. These soft decisions may be based on channel estimates computed by 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 a controller/processor 359, which performs the functions of layer 3 and layer 2.
The controller/processor 359 can be associated with a memory 360 that stores program codes and data. Memory 360 may be referred to as a computer-readable medium. In the UL, controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from EPC 160. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
Similar to the functionality described in connection with DL transmissions of base station 310, controller/processor 359 provides: RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reports; PDCP layer functions associated with header compression/decompression and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functions associated with upper layer PDU delivery, error correction by ARQ, RLC SDU concatenation, segmentation and reassembly, RLC data PDU re-segmentation, and RLC data PDU re-ordering; MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, de-multiplexing of MAC SDUs from TBs, scheduling information reporting, error correction by HARQ, priority handling, and logical channel prioritization.
TX processor 368 can use channel estimates derived by channel estimator 358 from reference signals or feedback transmitted by base station 310 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via respective Transmitters (TX) 354. Each Transmitter (TX) 354 may modulate an RF carrier with a corresponding spatial stream for transmission.
UL transmissions are processed at the base station 310 in a manner similar to that described in connection with the receiver functionality at the UE 350. Each Receiver (RX) 318 receives a signal via its respective antenna 320. Each Receiver (RX) 318 recovers information modulated onto an RF carrier and provides the information to the RX processor 370.
The controller/processor 375 may be associated with a memory 376 that stores program codes and data. Memory 376 may be referred to as a computer-readable medium. In the UL, controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from UE 350. IP packets from controller/processor 375 may be provided to EPC 160. Controller/processor 375 is also responsible for error detection using ACK and/or NACK protocols to support HARQ operations.
At least one of TX processor 368, RX processor 356, and controller/processor 359 may be configured to perform various aspects related to rate-matching limiting component 198 of fig. 1.
At least one of TX processor 316, RX processor 370, and controller/processor 375 may be configured to perform various aspects related to receive component 199 of fig. 1.
In aspects of wireless communication, a TB may correspond to a payload including data to be jointly encoded by an upper layer, such as a Medium Access Control (MAC) layer, to a physical layer. Upper layer data may be multiplexed on the TBs and sent by the physical layer in the radio transmission link. The TB may be divided into one or more Coded Blocks (CBs) by a physical layer. The data and control flows from/to the MAC layer may be encoded/decoded to provide transport and control services over the radio transmission link. The channel coding scheme may be a combination of error detection, error correction, rate matching, interleaving, mapping onto/splitting transport channels or control information from physical channels.
Each CB may be associated with a Cyclic Redundancy Check (CRC). Each CB may be transferred to an encoder (such as an encoder for turbo encoding). The encoder may encode data using turbo coding in combination with CRC and polar codes (for error correction) or low density parity check codes (LDPC). For example, in some aspects, a polar code may be used for control information encoding (such as for PUCCH) and LDPC may be used for user data encoding (such as for PUSCH). The polarization code may also split the channel. Turbo coding may provide 1/3 rate coding (3 output bits may be generated based on one input bit, the first output bit may be a systematic bit corresponding to one input bit, and the other two output bits may be parity bits that are interleaved versions of the input bit). For the polarization code, if K information bits are transmitted in a block of N bits, the polarization code may be used to polarize the channel into a reliable bit channel and an unreliable bit channel, and the information bits may be transmitted on the most reliable K-bit channel, and the rest of the unreliable channels may be set to 0.
In some wireless communication systems, each PUSCH slot may be associated with one TB. In some wireless communication systems, one TB may be used on different PUSCH slots. One TB used across different PUSCH slots may be otherwise referred to as a tbomins. The rate matching process may extract an exact set of bits to be transmitted within a Transmission Time Interval (TTI), such as one or more slots. For example, rate matching may match the number of bits in a TB to the number of bits that may be transmitted in a given allocation. Rate matching may include sub-block interleaving, bit collection, and pruning. The rate matching may be performed on the CB and may be performed after the CB is turbo encoded. The rate matching output size may be determined before starting the first slot PUSCH of the tbomins. In some wireless communication systems, rate matching may use the available tones for PUSCH. The tone may refer to a portion of the TB/CB where bits may be stored. The available tones for PUSCH may be tones not used for Uplink Control Information (UCI) multiplexing. As one non-limiting example, UCI may be PUCCH including acknowledgement/non-acknowledgement (a/N) bits. For TBoMS, UCI multiplexing decisions may be made after TBoMS start (after the first time slot of TBoMS). Accordingly, UCI multiplexing decisions made after tbomins may change the number of available tones for PUSCH. Such changes may make rate matching for TBoMS difficult or inefficient. Some wireless communication systems may not support dynamic updating of rate matching. The UE may not delay UCI multiplexing such as PUCCH for a/N for a long time. Some aspects provided herein may provide rate matching for TBoMS. In some aspects, rate matching may be configured prior to the start of the tbomins. When there is dynamic UCI multiplexing, the rate matching output size may not change even without dynamic update of the rate matching, and rate matching with TBoMS may be efficient.
Fig. 4 is a diagram 400 illustrating an example TBoMS. As shown in fig. 4, the time frame 410 may include one or more time slots. One or more timeslots may be associated with a single TB for a tbomins. The one or more time slots may include DL time slots and UL time slots. Some of the UL slots may include PUSCH and may also be used for UCI multiplexing. For example, UL slot 402A may be used for PUSCH 404A and UCI multiplexing for PUCCH 406A. UL slot 402B may be used for PUSCH 404A and UCI multiplexing for PUCCH 406B. PUSCH 404A may be associated with Redundancy Version (RV) 0. UL slot 402C may be for PUSCH 404B. UL slot 402D may be used for UCI multiplexing for PUSCH 404B and for PUCCH 406C. UL slot 402E may be used for UCI multiplexing for PUSCH 404C and for PUCCH 406D. UL slot 402F may be used for UCI multiplexing for PUSCH 404C and for PUCCH 406E. UL slot 402A, UL slot 402B, UL slot 402D, UL slot 402E and UL slot 402F may each include tones that may be scheduled to be available for PUSCH at the beginning of time frame 410 but may ultimately be used for UCI multiplexing for PUCCH. Such conflicts may be resolved based on aspects provided herein.
Fig. 5 is a diagram illustrating an example communication flow 500 between a UE 502 and a base station 504. In some aspects, the base station 504 may be a network entity. The network entity may be a network node. Base station 504 may be implemented as an aggregated base station, a decomposed base station, an Integrated Access and Backhaul (IAB) node, a relay node, a sidelink node, or the like. The network entity may be implemented in an aggregated or monolithic base station architecture, or alternatively, in an decomposed base station architecture, and may include one or more of a CU, DU, RU, near-real-time (Near-RT) RAN Intelligent Controller (RIC), or Non-real-time (Non-RT) RIC. The base station 504 may send DCI 506, which may include a PUSCH configuration, to the UE 502. DCI 506 may schedule one or more TBs. The UE 502 may encode the PUSCH/PUCCH for transmission to the base station 504, which base station 504 may include rate matching for the PUSCH at 508 (and may also include calculating a rate matching output size/slot length, allocating one or more bits, and refraining from allocating one or more other bits). After encoding, the UE 502 may send PUSCH 510 and PUCCH 512 to the base station 504. PUSCH 510 may be encoded based on LDPC encoding, and rate matching at 508 may be rate matching for LDPC codes.
Rate matching for LDPC codes may be defined in terms of CB and may include bit selection and bit interleaving. The input bit sequence for rate matching can be expressed as: d, d 0 ,d 1 ,d 2 ,...,d N-1 . The output bit sequence after rate matching can be expressed as: f (f) 0 ,f 1 ,f 2 ,...,f E-1 。
Bit sequence d after encoding 0 ,d 1 ,d 2 ,...,d N-1 Can be written with respect toLength N of the r-th coding block cb Is included in the circular buffer of (a). N may be defined based on the LDCP base map. For the r code block, if ilbrm=0 and N cb ＝min(N,N ref ) (N and N) ref Minimum of (f) then N cb =n, otherwise whereinBuffer Rate Matching (LBRM) with limited Transport Block Size (TBS) may be defined. Parameter R LBRM May be 2/3. The parameter C may be the number of CBs of the transport block. N (N) ref May be a reference and may be equal to TBS LBRM divided by a parameter R LBRM And the number of CBs of the transport block.
The rate matching output sequence length for rCB can be expressed as E r And E is r The value of (2) may be determined as follows:
setting j=0
for r＝0 to C-1
if r-th encoded block is not scheduled for transmission as indicated by Code Block Group Transmission Information (CBGTI)
E r ＝0；
else
if j≤C'-mod(G/(N L ·Q m ),C')-1
else
end if
j＝j+1；
end if
end for
Parameter N L May be the number of transport layers to which the transport block is mapped. Parameter Q m Is the modulation order. In some wireless communication systems, the parameter G may be the total of coded bits available for transmission of the TB A number. In some aspects, G may be the total number of encoded bits available for transmission of a transport block, irrespective of the tones used for UCI multiplexing. If CBGTI is not present in the DCI (e.g., DCI 506) for scheduling a TB, the parameter C '=c, and if CBGTI is present in the DCI (e.g., DCI 506) for scheduling a TB, C' is the number of scheduled code blocks of the transport block. The redundancy version number (e.g., PUSCH 510) for transmission may be determined by rv id Representation, and rv id =0, 1,2 or 3. In some wireless communication systems, a rate matching output bit sequence e k K=0, 1,2, E-1, can be generated as follows:
k＝0；
j＝0；
While k＜E
k＝k+1；
end if
j＝j+1；
end while
k 0 the value of (2) may be based on the redundancy version number and the LDPC base graph.
In some aspects, the rate-matched output bit sequence e k K=0, 1,2, E-1 may be generated as follows:
k＝0；
j＝0；
While k＜E
if TBoMS slot end
k 0 ＝k 0 +N re_curr_slot ·N L ·Q m
j＝0
k＝k+1；
end if
j＝j+1；
end while
Parameter N re_curr_slot May be the number of available tones for PUSCH without regard to the tones used for UCI multiplexing.
In some wireless communication systems, bit sequence e 0 ,e 1 ,e 2 ,...,e E-1 Can be associated with bit sequence f according to the following 0 ,f 1 ,f 2 ,...,f E-1 Interleaving (or interleaving to bit sequence f 0 ,f 1 ,f 2 ,...,f E-1 )：
for j＝0 to E/Q m -1
for i＝0 to Q m -1
end for
end for
Bit interleaving can vary greatly if the value of E varies. In some aspects provided herein, prior to the beginning of tbomins, UE 502 may be configured with rate matching that does not consider UCI multiplexing. The rate matching output size may not change when there is dynamic UCI multiplexing. If a reduced number of PUSCH bits are consumed (e.g., for encoding) due to UCI multiplexing, the UE may skip (or erase) unused bits (e.g., when performing rate matching).
In some aspects, the UE 502 may be configured to calculate the rate matching output size for each slot without regard to UCI multiplexing (UCI known prior to the start of TBoMS or UCI unknown prior to the start of TBoMS). The UE 502 may remember (e.g., store in memory) from previous calculations the starting point of the rate matching output bit consumption (e.g., slot boundary or otherwise referred to as slot start boundary). If some slots consume a reduced number of PUSCH bits due to UCI multiplexing, the UE 502 may skip (erase) unused PUSCH bits. By skipping the unused PUSCH bits, the UE may perform rate matching for tbos while supporting dynamic updating of UCI multiplexing. The next time slot may begin at a predetermined location (e.g., boundary) that is determined prior to calculating the rate matching output size. Fig. 6 is a diagram 600 illustrating an example rate matching. The TB size determination, CB segmentation, and rate matching size determination may be performed without considering UCI multiplexing. The TB size determination may be based on the number of available subcarriers multiplied by the number of symbols within the slot minus the number of unavailable REs. As shown in fig. 6, the UE 502 may first determine one or more slot boundaries (which may also be referred to as slot start boundaries) 602, 604, 606, 608, 610, and 612 (e.g., such as based on DCI 506). The UE 502 may then proceed to encode PUSCH bits in the slot. When UCI multiplexing exists in a slot, a reduced number of bits may be consumed (e.g., allocated) for encoding PUSCH because some of the bits may be used for UCI multiplexing of PUCCH. For example, the UE 502 may avoid allocating bits for UCI multiplexing of PUCCH for encoding PUSCH. The UE 502 may skip those bits associated with UCI multiplexing and begin encoding at the next boundary (which is determined before encoding begins). For example, due to UCI multiplexing, tones before slot 0 boundary 602, tones before slot 2 boundary 606, and two tones before slot 5 boundary 612 may be skipped. In some aspects, the UE 502 may skip/erase tones by: PUSCH data is written in the tone and then is overwritten with UCI multiplexing data (such as PUCCH a/N) on top of the PUSCH data (e.g., because the UE may not know UCI multiplexing data before writing PUSCH data). In some aspects, the UE 502 may pre-compute the boundary (e.g., compute the boundary before encoding), and the UE 502 may skip/erase the tone by not using the tone for PUSCH data and starting (e.g., resuming) writing the PUSCH after the next boundary.
In some aspects, the UE 502 may be configured to calculate the rate matching output size for each slot without regard to unknown UCI multiplexing (UCI unknown before tbomins starts). The UE 502 may reflect the UCI known prior to the tbomins start in the rate matching output size (e.g., by marking REs associated with UCI as unavailable for PUSCH). The UE 502 may remember (e.g., store in memory) from previous calculations the starting point of the rate matching output bit consumption (e.g., slot boundary or otherwise referred to as slot start boundary). If some slots consume a reduced number of PUSCH bits due to UCI multiplexing, the UE 502 may skip (erase) unused PUSCH bits. The next time slot may begin at a predetermined location (e.g., boundary) that is determined prior to calculating the rate matching output size. Fig. 7 is a diagram 700 illustrating an example rate matching. The TB size determination, CB segmentation, and rate matching size determination may be performed without considering unknown UCI multiplexing. As shown in fig. 7, the UE 502 may first determine one or more slot boundaries (which may be referred to as slot start boundaries) 702, 704, 706, 708, 710, and 712. The UE 502 may know that tones before the boundary 702 are used for UCI multiplexing before the tbomins starts (e.g., by having UCI multiplexing data available before tbomins starts). The rate matching output size determined by the UE 502 may reflect a known UCI multiplexing (e.g., by marking REs associated with UCI as unavailable) before the boundary 702. The UE 502 may continue to encode PUSCH bits in the slot and mark REs associated with UCI as unavailable and avoid allocation of PUSCH bits in REs associated with UCI. When UCI multiplexing is present in a slot, a reduced number of bits (e.g., for PUSCH coding) may be consumed. The UE 502 may skip those bits associated with UCI multiplexing and begin encoding at the next boundary (which is determined before encoding begins). For example, due to UCI multiplexing, tones before slot 2 boundary 706 and two tones before slot 5 boundary 712 may be skipped. Because the tone prior to the slot 0 boundary is known to be used by UCI multiplexing for the UE 502, the UE 502 may determine a rate matching output size (which may correspond to the slot length) based on the known UCI multiplexing and may not skip PUSCH bits for the tone prior to the slot 0 boundary. In some aspects, the UE 502 may skip/erase tones by: PUSCH data is written in the tone and then is overwritten with UCI multiplexing data (such as PUCCH a/N) over the PUSCH data (e.g., because the UE may not know the UCI multiplexing data before writing the PUSCH data). In some aspects, the UE 502 may pre-compute the boundary (e.g., compute the boundary before encoding), and the UE 502 may skip/erase the tone by not using the tone for PUSCH data and starting (e.g., resuming) writing the PUSCH after the next boundary.
In some aspects, the UE 502 may be configured to calculate the rate matching output size for each slot without regard to UCI multiplexing (UCI known prior to the start of TBoMS or UCI unknown prior to the start of TBoMS). In some aspects, the UE 502 may not remember (e.g., stored in memory) from previous calculations a starting point (e.g., slot boundary or otherwise referred to as slot start boundary) for rate matching output bit consumption. If some slots consume a reduced number of PUSCH bits due to UCI multiplexing, the UE 502 stops at the end of the bits used. In the next slot, PUSCH transmission may resume after it stops in the last slot. In these aspects, erasures are accumulated at the last PUSCH bits for the rate matched output in the entire time frame of the TBoMS. In some aspects, the UE 502 may be configured to calculate the rate matching output size for each slot without regard to unknown UCI multiplexing (UCI unknown before tbomins starts). The UE 502 may reflect the UCI known prior to the tbomin start in the rate matching output size (e.g., by marking REs associated with UCI as unavailable).
Fig. 8 is a diagram 800 illustrating an example rate matching. The TB size determination, CB segmentation, and rate matching size determination may be performed without considering unknown or known UCI multiplexing. In some aspects, the UE 502 may pre-calculate (e.g., calculate before having data to send) or calculate a rate matching output buffer starting point for each slot. As shown in fig. 8, there may be one or more slot boundaries (which may otherwise be referred to as slot start boundaries) 802, 804, 806, 808, 810, and 812. When UCI multiplexing exists in a slot, a reduced number of bits may be consumed. The UE 502 continues to encode and centralize all erasures/skips at the end of the TB. For example, the tones skipped by UE 502 may be located at the end of the TB. In some aspects, the UE 502 may skip/erase tones by: PUSCH data is written in the tone and then is overwritten with UCI multiplexing data (such as PUCCH a/N) on top of the PUSCH data (e.g., because the UE may not know UCI multiplexing data before writing PUSCH data). In some aspects, the UE 502 may pre-compute the boundary (e.g., compute the boundary before encoding), and the UE 502 may skip/erase the tone by not using the tone for PUSCH data and starting (e.g., resuming) writing the PUSCH after the next boundary.
Fig. 9 is a flow chart 900 of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 502, device 1102).
At 902, the UE may calculate a slot length for each UL slot of a plurality of UL slots. The slot length for each UL slot may be associated with a plurality of rate matching output bits. Each UL slot may include a starting point for a plurality of rate matching output bits. The slot length for each UL slot may be associated with a starting boundary. Multiple UL slots may be associated with at least one of a single TB or a single rate matching. For example, the UE 502 may calculate a slot length for each of the plurality of UL slots, as described in connection with fig. 5. In some aspects, the computing component 1142 of fig. 11 may execute 902.
At 904, the UE may allocate one or more bits of the plurality of rate matching output bits for a modulation procedure. For example, the UE 502 may allocate one or more of the plurality of rate matching output bits for the modulation process as described in connection with fig. 5. In some aspects, 904 may be performed by the allocation component 1144 of fig. 11.
At 906, the UE may skip (e.g., avoid) allocation of at least one bit of the plurality of rate matching output bits for the modulation procedure, the at least one bit corresponding to UCI multiplexing. For example, UE 502 may skip (e.g., avoid) allocation of at least one bit of the plurality of rate-matched output bits for the modulation procedure, the at least one bit corresponding to UCI multiplexing, as described in connection with fig. 5. In some aspects, 906 may be performed by the allocation component 1144 of fig. 11.
Fig. 10 is a flow chart 1000 of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 502; means 1102).
At 1002, the UE may receive an indication of PUSCH configuration from a base station. The PUSCH configuration may be associated with an allocation of one or more bits and a skipped allocation of at least one bit. For example, the UE 502 may receive (in DCI 506) an indication of PUSCH configuration from the base station 504. In some aspects, 1002 may be performed by communication component 1146 of fig. 11. A base station may be a network entity, such as a network node.
At 1004, the UE may calculate a slot length for each UL slot of the plurality of UL slots. The slot length for each UL slot may be associated with a plurality of rate matching output bits. Each UL slot may include a starting point for a plurality of rate matching output bits. The slot length for each UL slot may be associated with a starting boundary. Multiple UL slots may be associated with at least one of a single TB or a single rate matching. For example, the UE 502 may calculate a slot length for each of the plurality of UL slots, as described in connection with fig. 5. In some aspects, 1004 may be performed by computing component 1142 in fig. 11. In some aspects, a single TB corresponds to a tbomins.
In some aspects, as part of 1004, the UE may store a starting boundary associated with each UL slot at 1042, e.g., as described in connection with boundaries 602-612 in fig. 6 and boundaries 702-712 in fig. 7. In some aspects, the skipped allocated at least one bit of the plurality of rate matching output bits may correspond to an end of one or more of the plurality of UL slots (such as an end of slot 0/2/5 in fig. 6 and 7).
In some aspects, as part of 1004, at 1044, the UE may determine one or more UCI bits to be multiplexed, which may not correspond to UCI multiplexing in 1008. For example, UE 502 may determine one or more known UCI bits at the end of slot 0 in fig. 7, and the UCI multiplexing used in 1008 may be based on the unknown UCI multiplexing. In some aspects, the UE may calculate and store a starting boundary associated with each UL slot based on one or more UCI bits (e.g., by avoiding the use of REs associated with the one or more UCI bits). In some aspects, the skipped allocated at least one bit of the plurality of rate matching output bits may correspond to an end of one or more of the plurality of UL slots (such as an end of slot 2/5 in fig. 7). In some aspects, the slot length may be calculated without storing a starting boundary associated with each UL slot. In such an aspect, the skipped allocated at least one bit of the plurality of rate matching output bits may correspond to an end of a plurality of UL slots (such as an end of a slot of the plurality of slots in fig. 8). In some aspects, the slot length may be calculated based on one or more UCI bits without storing a starting boundary associated with each UL slot, and the skipped at least one of the plurality of rate matching output bits may be allocated to correspond to an end of a plurality of UL slots (such as an end of a slot of the plurality of slots in fig. 8). In some aspects, as part of 1004, the UE may calculate a starting boundary for at least one subsequent time slot of the plurality of UL time slots based on at least one skipped bit of the plurality of rate matching output bits allocated for the modulation process at 1046. In some aspects, the starting boundary for at least one subsequent slot may be calculated without consideration of UCI multiplexing (e.g., ignoring UCI multiplexing or UCI multiplexing is not known). In some aspects, the calculation of the starting boundary for at least one subsequent time slot may be pre-calculated or pre-determined.
At 1006, the UE may allocate one or more bits of the plurality of rate matching output bits for the modulation process. For example, the UE 502 may allocate one or more of the plurality of rate matching output bits for the modulation process as described in connection with fig. 5. In some aspects, 1006 may be performed by the dispensing component 1144 of fig. 11. In some aspects, the plurality of rate matching output bits may correspond to a rate matching output size. In some aspects, each of the one or more bits may be allocated for a modulation procedure in one or more REs.
At 1008, the UE may skip (e.g., avoid) allocation of at least one bit of the plurality of rate matching output bits for the modulation procedure, the at least one bit corresponding to UCI multiplexing. For example, UE 502 may skip (e.g., avoid) allocation of at least one bit of the plurality of rate-matched output bits for the modulation procedure, the at least one bit corresponding to UCI multiplexing, as described in connection with fig. 5. In some aspects, 1008 may be performed by the allocation component 1144 of fig. 11. In some aspects, as part of 1008, the UE may determine, at 1082, whether at least one of the plurality of rate matching output bits corresponds to UCI multiplexing. In some aspects, at least one of the plurality of rate matching output bits that is skipped and allocated for the modulation procedure may correspond to at least one unused PUSCH bit. In some aspects, UCI multiplexing may be associated with one or more PUCCH acknowledgement bits or non-acknowledgement bits. In some aspects, as part of 1008, the UE may write PUSCH data in at least one bit at 1084. In some aspects, as part of 1008, the UE may overwrite UCI multiplexing data in at least one bit at 1086.
At 1010, the UE may send an UL transmission to the base station based on the allocated one or more bits and the skipped allocated at least one bit. For example, the UE 502 may send a UL transmission (PUSCH 510) to the base station 504 based on the allocated one or more bits and the skipped allocated at least one bit, as described in connection with fig. 5. In some aspects, 1010 may be performed by communication component 1146 of fig. 11. A base station may be a network entity, such as a network node.
Fig. 11 is a diagram 1100 illustrating an example of a hardware implementation for an apparatus 1102. The apparatus 1102 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1102 may include a cellular baseband processor 1104 (also referred to as a modem) coupled to a cellular RF transceiver 1122. In some aspects, the apparatus 1102 may also include one or more Subscriber Identity Module (SIM) cards 1120, an application processor 1106 coupled to the Secure Digital (SD) card 1108 and to the screen 1110, a bluetooth module 1112, a Wireless Local Area Network (WLAN) module 1114, a Global Positioning System (GPS) module 1116, or a power supply 1118. The cellular baseband processor 1104 communicates with the UE 104 and/or BS102/180 via the cellular RF transceiver 1122. The cellular baseband processor 1104 may include a computer readable medium/memory. The computer readable medium/memory may be non-transitory. The cellular baseband processor 1104 is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the cellular baseband processor 1104, causes the cellular baseband processor 1104 to perform the various functions described supra. The computer readable medium/memory can also be used for storing data that is manipulated by the cellular baseband processor 1104 when executing software. The cellular baseband processor 1104 also includes a receive component 1130, a communication manager 1132, and a transmit component 1134. The communications manager 1132 includes one or more of the illustrated components. The components within the communication manager 1132 may be stored in a computer-readable medium/memory and/or configured as hardware within the cellular baseband processor 1104. The cellular baseband processor 1104 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359. In one configuration, the apparatus 1102 may be a modem chip and include only the baseband processor 1104, while in another configuration, the apparatus 1102 may be an entire UE (e.g., see 350 of fig. 3) and include additional modules of the apparatus 1102.
The communication manager 1132 may include a computing component 1142, the computing component 1142 configured to: the method may further include calculating a slot length for each of a plurality of UL slots, the slot length for each UL slot being associated with a plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, the slot length for each UL slot being associated with a starting boundary, the plurality of UL slots being associated with at least one of a single TB or a single rate matching, e.g., as described in connection with 902 in fig. 9 and 1004 in fig. 10. The communication manager 1132 may also include a distribution component 1144, the distribution component 1144 may be configured to: one or more of the plurality of rate-matched output bits are allocated for the modulation process and at least one of the plurality of rate-matched output bits is allocated for the modulation process is skipped (e.g., avoided), the at least one bit corresponding to UCI multiplexing, e.g., as described in connection with 904 and 906 in fig. 9 and 1006 and 1008 in fig. 10. The communication manager 1132 may also include a communication component 1146, which communication component 1146 may be configured to: an indication of PUSCH configuration is received from the base station, and a UL transmission is sent to the base station based on the allocated one or more bits and the skipped allocated at least one bit, e.g., as described in connection with 1002 and 1010 in fig. 10. A base station may be a network entity, such as a network node.
The apparatus may include additional components to perform each of the blocks of the algorithms in the flowcharts of fig. 9 and 10 described above. Accordingly, each block in the flowcharts of fig. 9 and 10 may be performed by components, and the apparatus may include one or more of those components. A component may be one or more hardware components specifically configured to perform the process/algorithm, implemented by a processor configured to perform the process/algorithm, stored within a computer readable medium for implementation by a processor, or some combination thereof.
As shown, the device 1102 may include various components configured for various functions. In one configuration, the apparatus 1102, and in particular the cellular baseband processor 1104, may include: the apparatus includes means for calculating a slot length for each of a plurality of UL slots, the slot length for each UL slot being associated with a plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, the slot length for each UL slot being associated with a starting boundary, the plurality of UL slots being associated with at least one of a single TB or a single rate match. The cellular baseband processor 1104 may also include means for allocating one or more of the plurality of rate matching output bits for the modulation process. The cellular baseband processor 1104 may also include means for skipping (e.g., avoiding) allocation of at least one bit of the plurality of rate-matched output bits for the modulation process, the at least one bit corresponding to UCI multiplexing. The cellular baseband processor 1104 may also include means for storing a starting boundary associated with each UL slot. The cellular baseband processor 1104 may also include means for determining one or more UCI bits to be multiplexed that do not correspond to UCI multiplexing. The cellular baseband processor 1104 may also include means for calculating and storing a starting boundary associated with each UL slot based on one or more UCI bits. The cellular baseband processor 1104 may also include means for determining one or more UCI bits to be multiplexed that do not correspond to UCI multiplexing. The cellular baseband processor 1104 may also include means for receiving an indication of a PUSCH configuration from the base station, wherein the PUSCH configuration is associated with the allocation of the one or more bits and the skipped allocation of the at least one bit. The cellular baseband processor 1104 may also include means for determining whether at least one of the plurality of rate matching output bits corresponds to UCI multiplexing. The cellular baseband processor 1104 may also include means for calculating a starting boundary for at least one subsequent time slot of the plurality of UL time slots based on at least one of the plurality of rate matching output bits being skipped to be allocated for the modulation process. The cellular baseband processor 1104 may also include means for writing PUSCH data in at least one bit. The cellular baseband processor 1104 may also include a unit for rewriting UCI multiplexing data in at least one bit. The cellular baseband processor 1104 may also include a first transmitter for transmitting an UL transmission to the base station based on the allocated one or more bits and the skipped allocated at least one bit. The elements may be one or more components of the apparatus 1102 configured to perform the functions recited by the elements. As described above, the apparatus 1102 may include a TX processor 368, an RX processor 356, and a controller/processor 359. As such, in one configuration, the elements may be TX processor 368, RX processor 356, and controller/processor 359 configured to perform the functions recited by the elements.
Fig. 12 is a flow chart 1200 of a method of wireless communication. The method may be performed by a base station (e.g., base station 102/180, base station 504, device 1302). In some aspects, the base station may be a network entity, such as a network node.
At 1202, the base station may send an indication of PUSCH configuration to the UE. The PUSCH configuration may be associated with an allocation of a plurality of rate matching output bits for the modulation procedure, with a slot length for each of the plurality of UL slots being associated with the plurality of rate matching output bits. Each UL slot may include a starting point for a plurality of rate matching output bits. The slot length for each UL slot may be associated with a starting boundary, and multiple UL slots may be associated with at least one of a single TB or a single rate match. For example, the base station 504 may send an indication of PUSCH configuration (such as DCI 506) to the UE 502, as described in connection with fig. 5. In some aspects 1202 may be performed by the indication component 1342 in fig. 13. In some aspects, the plurality of rate matching output bits may correspond to a rate matching output size. In some aspects, a single TB may correspond to a tbomins.
At 1204, the base station may receive UL transmissions from the UE based on: the allocation of one or more of the plurality of rate matching output bits and the allocation of at least one of the plurality of rate matching output bits skipped based on UCI multiplexing associated with the at least one bit. For example, the base station 504 may receive UL transmissions (such as PUSCH 510) from the UE 502 based on: the method includes the steps of allocating one or more bits of the plurality of rate matching output bits, and allocating at least one bit of the plurality of rate matching output bits skipped based on UCI multiplexing associated with the at least one bit. In some aspects 1204 may be performed by UL receiving component 1344 in fig. 13. In some aspects, each of the one or more bits may be allocated for a modulation procedure in one or more REs. In some aspects, the skipped at least one bit allocated for the modulation procedure may correspond to at least one unused PUSCH bit. In some aspects, UCI multiplexing may be associated with one or more PUCCH acknowledgement bits or non-acknowledgement bits. In some aspects, a starting boundary for at least one subsequent time slot of the plurality of UL time slots may be calculated without consideration of UCI multiplexing and may be based on the skipped at least one bit allocated for the modulation process.
Fig. 13 is a diagram 1300 illustrating an example of a hardware implementation for an apparatus 1302. The apparatus 1302 may be a base station, a component of a base station, or may implement a base station functionality. In some aspects, the apparatus 1102 may include a baseband unit 1304. The baseband unit 1304 may communicate with the UE 104 via a cellular RF transceiver 1322. Baseband unit 1304 may include a computer readable medium/memory. The baseband unit 1304 is responsible for general processing, including the execution of software stored on a computer-readable medium/memory. The software, when executed by the baseband unit 1304, causes the baseband unit 1304 to perform the various functions described supra. The computer readable medium/memory may also be used for storing data that is manipulated by the baseband unit 1304 when executing software. Baseband unit 1304 also includes a receiving component 1330, a communication manager 1332, and a transmitting component 1334. The communications manager 1332 includes one or more illustrated components. The components within the communications manager 1332 may be stored in a computer readable medium/memory and/or configured as hardware within the baseband unit 1304. Baseband unit 1304 may be a component of base station 310 and may include memory 376 and/or at least one of TX processor 316, RX processor 370, and controller/processor 375.
The communication manager 1332 can include an indication component 1342, which indication component 1342 can transmit an indication of a PUSCH configuration associated with allocation of a plurality of rate matching output bits for a modulation procedure, a slot length for each of a plurality of UL slots associated with the plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, a slot length for each UL slot associated with a starting boundary, the plurality of UL slots associated with at least one of a single TB or a single rate match, e.g., as described in connection with 1202 in fig. 12. The communication manager 1332 can also include a UL reception component 1344, which can receive UL transmissions from a UE based on the allocation of one or more of the plurality of rate-matched output bits and the skipped allocation of at least one of the plurality of rate-matched output bits, which is associated with Uplink Control Information (UCI) multiplexing, e.g., as described in connection with 1204 in fig. 12.
The apparatus may include additional components to perform each of the blocks of the algorithm in the flowchart of fig. 12. Accordingly, each block in the flowchart of fig. 12 may be performed by components, and the apparatus may include one or more of those components. A component may be one or more hardware components specifically configured to perform the process/algorithm, implemented by a processor configured to perform the process/algorithm, stored within a computer readable medium for implementation by a processor, or some combination thereof.
As shown, the apparatus 1302 may include various components configured for various functions. In one configuration, the apparatus 1302, and in particular the baseband unit 1304, may comprise: the apparatus includes means for transmitting, to a UE, an indication of a PUSCH configuration associated with an allocation of a plurality of rate matching output bits for a modulation procedure, a slot length for each UL slot of a plurality of UL slots associated with a plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, the slot length for each UL slot associated with a starting boundary, the plurality of UL slots associated with at least one of a single TB or a single rate match. The baseband unit 1304 may further include: the apparatus includes means for receiving a UL transmission from a UE based on an allocation of one or more of the plurality of rate matching output bits and a skipped allocation of at least one of the plurality of rate matching output bits, the at least one bit associated with Uplink Control Information (UCI) multiplexing. These units may be one or more of the components of the apparatus 1302 configured to perform the functions described by these aforementioned units. As described above, the apparatus 1302 may include a TX processor 316, an RX processor 370, and a controller/processor 375. Thus, in one configuration, the elements may be TX processor 316, RX processor 370, and controller/processor 375 configured to perform the functions recited by the elements.
It should be understood that the specific order or hierarchy of blocks in the processes/flowcharts disclosed is an illustration of example approaches. It should be appreciated that the particular order or hierarchy of blocks in the process/flow diagram may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.
The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. 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 claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more". Terms such as "if," when "and" while at "should be interpreted as" under conditions of "when at" and not meaning immediate time relationships or reactions. That is, these phrases, such as "when," do not imply that an action will occur in response to or during the occurrence of an action, but simply imply that if a condition is met, no special or immediate time constraints are required for the action to occur. The word "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 advantageous over other aspects. The term "some" means one or more unless specifically stated otherwise. 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, a combination such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C" and "A, B, C or any combination thereof" may be a alone, B alone, C, A and B, A and C, B and C, or a and B and C, wherein any such combination may comprise one or more members of A, B or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The terms "module," mechanism, "" element, "" device, "and the like are not intended to be substituted for the term" unit. Thus, no claim element is to be construed as a functional unit unless the element is explicitly recited using the phrase "unit for.
The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.
Aspect 1 is an apparatus for wireless communication at a UE, comprising: a memory; and at least one processor coupled to the memory, the memory storing instructions executable by the at least one processor to configure the apparatus to: calculating a slot length for each UL slot of a plurality of UL slots, the slot length for each UL slot being associated with a plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, the slot length for each UL slot being associated with a starting boundary, the plurality of UL slots being associated with at least one of a single TB or a single rate match; allocating one or more bits of the plurality of rate-matched output bits for a modulation process; and refraining from allocating at least one bit of the plurality of rate-matched output bits for the modulation procedure, the at least one bit corresponding to UCI multiplexing.
Aspect 2 is the apparatus of aspect 1, wherein the plurality of rate-matched output bits corresponds to a rate-matched output size.
Aspect 3 is the apparatus of any one of aspects 1-2, wherein the single TB corresponds to a TBoMS.
Aspect 4 is the apparatus of any of aspects 1-3, wherein the instructions are further executable by the at least one processor to configure the UE to: storing the starting boundary associated with each UL slot; wherein the at least one of the plurality of rate matching output bits that is avoided from being allocated corresponds to an end of one or more of the plurality of UL slots.
Aspect 5 is the apparatus of any one of aspects 1-4, wherein the instructions are further executable by the at least one processor to configure the UE to: determining one or more UCI bits to be multiplexed, the one or more UCI bits not corresponding to the UCI multiplexing; and calculating and storing the starting boundary associated with each UL slot based on the one or more UCI bits; wherein the at least one of the plurality of rate matching output bits that is avoided from being allocated corresponds to an end of one or more of the plurality of UL slots.
Aspect 6 is the apparatus of any one of aspects 1-4, wherein the instructions are further executable by the at least one processor to configure the UE to: wherein the slot lengths are calculated without storing the starting boundary associated with each UL slot; and wherein the at least one bit of the plurality of rate matching output bits that is avoided from being allocated corresponds to an end of the plurality of UL slots.
Aspect 7 is the apparatus of any one of aspects 1-4, wherein the instructions are further executable by the at least one processor to configure the UE to: determining one or more UCI bits to be multiplexed, the one or more UCI bits not corresponding to the UCI multiplexing; and wherein the slot length is calculated based on the one or more UCI bits without storing the starting boundary associated with each UL slot; and wherein the at least one bit of the plurality of rate matching output bits that is avoided from being allocated corresponds to an end of the plurality of UL slots.
Aspect 8 is the apparatus of any one of aspects 1-7, wherein the instructions are further executable by the at least one processor to configure the UE to: an indication of a PUSCH configuration is received from a base station, and wherein the PUSCH configuration is associated with the allocation of the one or more bits and the avoided allocation of the at least one bit.
Aspect 9 is the apparatus of any one of aspects 1-8, wherein each of the one or more bits is allocated for the modulation procedure in one or more REs.
Aspect 10 is the apparatus of any one of aspects 1-9, wherein the instructions are further executable by the at least one processor to configure the UE to: determining whether the at least one of the plurality of rate matching output bits corresponds to UCI multiplexing.
Aspect 11 is the apparatus of any one of aspects 1-10, wherein the at least one of the plurality of rate-matched output bits that is avoided from being allocated for the modulation procedure corresponds to at least one unused PUSCH bit.
Aspect 12 is the apparatus of any one of aspects 1-11, wherein the UCI multiplexing is associated with one or more PUCCH acknowledgement bits or non-acknowledgement bits.
Aspect 13 is the apparatus of any one of aspects 1-12, wherein the instructions are further executable by the at least one processor to configure the UE to: a starting boundary for at least one subsequent time slot of the plurality of UL time slots is calculated based on the at least one bit of the plurality of rate matching output bits that is avoided from being allocated for the modulation process.
Aspect 14 is the apparatus of any one of aspects 1-13, wherein the starting boundary for the at least one subsequent slot is calculated without consideration of UCI multiplexing.
Aspect 15 is the apparatus of any one of aspects 1-14, wherein the calculation of the starting boundary for the at least one subsequent time slot is pre-calculated or predetermined.
Aspect 16 is the apparatus of any one of aspects 1-15, wherein the instructions are further executable by the at least one processor to configure the UE to avoid allocating the at least one bit by: writing PUSCH data in the at least one bit; and rewriting UCI multiplexing data in the at least one bit.
Aspect 17 is the apparatus of any one of aspects 1-16, wherein the instructions are further executable by the at least one processor to configure the UE to: the UL transmission is sent to the base station based on the allocated one or more bits and the at least one bit that is avoided from being allocated.
Aspect 18 is the apparatus of any one of aspects 1-17, further comprising: a transceiver or antenna coupled to the at least one processor.
Aspect 19 is an apparatus for wireless communication at a network entity, comprising: a memory; and at least one processor coupled to the memory, the memory storing instructions executable by the at least one processor to configure the apparatus to: transmitting, for a UE, an indication of a PUSCH configuration associated with allocation of a plurality of rate matching output bits for a modulation procedure, a slot length for each of a plurality of UL slots associated with the plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, the slot length for each UL slot associated with a starting boundary, the plurality of UL slots associated with at least one of a single TB or a single rate match; and receiving UL transmissions based on the allocation of one or more bits of the plurality of rate matching output bits and the avoided allocation of at least one bit of the plurality of rate matching output bits, the at least one bit associated with Uplink Control Information (UCI) multiplexing.
Aspect 20 is the apparatus of aspect 19, wherein the plurality of rate-matched output bits corresponds to a rate-matched output size.
Aspect 21 is the apparatus of any one of aspects 19-20, wherein the single TB corresponds to a TBoMS.
Aspect 22 is the apparatus of any one of aspects 19-21, wherein each of the one or more bits is allocated for the modulation procedure in one or more REs.
Aspect 23 is the apparatus of any one of aspects 19-22, wherein the at least one bit allocated for the modulation procedure that is skipped corresponds to at least one unused PUSCH bit.
Aspect 24 is the apparatus of any one of aspects 19-23, wherein the UCI multiplexing is associated with one or more PUCCH acknowledgement bits or non-acknowledgement bits.
Aspect 25 is the apparatus of any one of aspects 19-24, wherein the starting boundary for at least one subsequent time slot of the plurality of UL time slots is calculated without consideration of UCI multiplexing and is based on the at least one bit allocated for the modulation process that is skipped.
Aspect 26 is the apparatus of any one of aspects 19-25, further comprising: a transceiver coupled to the at least one processor.
Aspect 27 is a method of wireless communication at a UE, comprising: calculating a slot length for each UL slot of a plurality of UL slots, the slot length for each UL slot being associated with a plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, the slot length for each UL slot being associated with a starting boundary, the plurality of UL slots being associated with at least one of a single TB or a single rate match; allocating one or more bits of the plurality of rate-matched output bits for a modulation process; and refraining from allocating at least one bit of the plurality of rate-matched output bits for the modulation procedure, the at least one bit corresponding to UCI multiplexing.
Aspect 28 is the method of aspect 27, further comprising a method for implementing any of aspects 2 to 18.
Aspect 29 is an apparatus for wireless communication at a UE, comprising: means for calculating a slot length for each UL slot of a plurality of UL slots, the slot length for each UL slot being associated with a plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, the slot length for each UL slot being associated with a starting boundary, the plurality of UL slots being associated with at least one of a single TB or a single rate match; means for allocating one or more bits of the plurality of rate-matched output bits for a modulation process; and means for avoiding allocation of at least one bit of the plurality of rate-matched output bits for the modulation procedure, the at least one bit corresponding to UCI multiplexing.
Aspect 30 is the apparatus for wireless communication of aspect 29, further comprising: a unit for implementing any of aspects 2 to 18.
Aspect 31 is a computer-readable medium storing computer-executable code at a UE, which when executed by a processor causes the processor to: calculating a slot length for each UL slot of a plurality of UL slots, the slot length for each UL slot being associated with a plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, the slot length for each UL slot being associated with a starting boundary, the plurality of UL slots being associated with at least one of a single TB or a single rate match; allocating one or more bits of the plurality of rate-matched output bits for a modulation process; and refraining from allocating at least one bit of the plurality of rate-matched output bits for the modulation procedure, the at least one bit corresponding to UCI multiplexing.
Aspect 32 is the computer-readable medium of aspect 31, wherein the code, when executed by the processor, causes the processor to implement any one of aspects 2 to 18.
Aspect 33 is a method of wireless communication at a base station, comprising: transmitting, for a UE, an indication of a PUSCH configuration associated with allocation of a plurality of rate matching output bits for a modulation procedure, a slot length for each of a plurality of UL slots associated with the plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, the slot length for each UL slot associated with a starting boundary, the plurality of UL slots associated with at least one of a single TB or a single rate match; and receiving UL transmissions based on the allocation of one or more bits of the plurality of rate matching output bits and the avoided allocation of at least one bit of the plurality of rate matching output bits, the at least one bit associated with Uplink Control Information (UCI) multiplexing.
Aspect 34 is the method of aspect 33, further comprising a method for implementing any of aspects 20 to 26.
Aspect 35 is an apparatus for wireless communication at a base station, comprising: means for transmitting, for a UE, an indication of a PUSCH configuration associated with allocation of a plurality of rate matching output bits for a modulation procedure, a slot length for each of a plurality of UL slots associated with the plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, the slot length for each UL slot associated with a starting boundary, the plurality of UL slots associated with at least one of a single TB or a single rate match; and means for receiving a UL transmission based on the allocation of one or more bits of the plurality of rate matching output bits and the avoided allocation of at least one bit of the plurality of rate matching output bits, the at least one bit associated with Uplink Control Information (UCI) multiplexing.
Aspect 36 is the apparatus for wireless communication of aspect 35, further comprising: a unit for implementing any of aspects 20 to 26.
Aspect 37 is a computer-readable medium storing computer-executable code at a base station, which when executed by a processor causes the processor to: transmitting, for a UE, an indication of a PUSCH configuration associated with allocation of a plurality of rate matching output bits for a modulation procedure, a slot length for each of a plurality of UL slots associated with the plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, the slot length for each UL slot associated with a starting boundary, the plurality of UL slots associated with at least one of a single TB or a single rate match; and receiving UL transmissions based on the allocation of one or more bits of the plurality of rate matching output bits and the avoided allocation of at least one bit of the plurality of rate matching output bits, the at least one bit associated with Uplink Control Information (UCI) multiplexing.
Aspect 38 is the computer-readable medium of aspect 37, wherein the code, when executed by the processor, causes the processor to implement any one of aspects 20 to 26.
Claims (30)
1. An apparatus for wireless communication at a User Equipment (UE), comprising:
a memory; and
at least one processor coupled to the memory, the memory storing instructions executable by the at least one processor to configure the device to:
calculating a slot length for each of a plurality of Uplink (UL) slots, the slot length for each UL slot being associated with a plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, the slot length for each UL slot being associated with a starting boundary, the plurality of UL slots being associated with at least one of a single Transport Block (TB) or a single rate match;
allocating one or more bits of the plurality of rate-matched output bits for a modulation process; and
avoiding allocation of at least one bit of the plurality of rate matching output bits for the modulation procedure, the at least one bit corresponding to Uplink Control Information (UCI) multiplexing.
2. The apparatus of claim 1, wherein the plurality of rate matching output bits corresponds to a rate matching output size.
3. The apparatus of claim 1, wherein the single TB corresponds to a TB over multiple timeslots (TBoMS).
4. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to configure the UE to:
storing the starting boundary associated with each UL slot;
wherein the at least one of the plurality of rate matching output bits that is avoided from being allocated corresponds to an end of one or more of the plurality of UL slots.
5. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to configure the UE to:
determining one or more UCI bits to be multiplexed, the one or more UCI bits not corresponding to the UCI multiplexing; and
calculating and storing the starting boundary associated with each UL slot based on the one or more UCI bits;
wherein the at least one of the plurality of rate matching output bits that is avoided from being allocated corresponds to an end of one or more of the plurality of UL slots.
6. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to configure the UE to:
Wherein the slot lengths are calculated without storing the starting boundary associated with each UL slot;
wherein the at least one bit of the plurality of rate matching output bits that is avoided from being allocated corresponds to an end of the plurality of UL slots.
7. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to configure the UE to:
determining one or more UCI bits to be multiplexed, the one or more UCI bits not corresponding to the UCI multiplexing; and
wherein the slot length is calculated based on the one or more UCI bits without storing the starting boundary associated with each UL slot;
wherein the at least one bit of the plurality of rate matching output bits that is avoided from being allocated corresponds to an end of the plurality of UL slots.
8. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to configure the UE to:
an indication of a Physical Uplink Shared Channel (PUSCH) configuration is received from a base station, wherein the PUSCH configuration is associated with the allocation of the one or more bits and the avoided allocation of the at least one bit.
9. The apparatus of claim 1, wherein each of the one or more bits is allocated for the modulation procedure in one or more Resource Elements (REs).
10. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to configure the UE to:
determining whether the at least one of the plurality of rate matching output bits corresponds to UCI multiplexing.
11. The apparatus of claim 1, wherein the at least one of the plurality of rate matching output bits that is avoided from being allocated for the modulation procedure corresponds to at least one unused Physical Uplink Shared Channel (PUSCH) bit.
12. The apparatus of claim 11, wherein the UCI multiplexing is associated with one or more Physical Uplink Control Channel (PUCCH) acknowledgement bits or non-acknowledgement bits.
13. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to configure the UE to:
a first starting boundary for at least one subsequent time slot of the plurality of UL time slots is calculated based on the at least one bit of the plurality of rate matching output bits that is avoided from being allocated for the modulation process.
14. The apparatus of claim 13, wherein the starting boundary for the at least one subsequent time slot is calculated without consideration of UCI multiplexing.
15. The apparatus of claim 13, wherein the calculation of the starting boundary for the at least one subsequent time slot is pre-calculated or predetermined.
16. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to configure the UE to avoid allocating the at least one bit by:
writing Physical Uplink Shared Channel (PUSCH) data in the at least one bit; and
the UCI multiplexing data is rewritten in the at least one bit.
17. The apparatus of claim 1, wherein the instructions are further executable by the at least one processor to configure the UE to:
the UL transmission is sent to the base station based on the allocated one or more bits and the at least one bit that is avoided from being allocated.
18. The apparatus of claim 1, further comprising: a transceiver coupled to the at least one processor.
19. An apparatus for wireless communication at a network entity, comprising:
A memory; and
at least one processor coupled to the memory, the memory storing instructions executable by the at least one processor to configure the device to:
transmitting, for a User Equipment (UE), an indication of a Physical Uplink Shared Channel (PUSCH) configuration associated with an allocation of a plurality of rate matching output bits for a modulation procedure, a slot length for each of a plurality of UL slots associated with the plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, the slot length for each UL slot associated with a starting boundary, the plurality of UL slots associated with at least one of a single Transport Block (TB) or a single rate match; and
UL transmissions are received based on a first allocation of one or more of the plurality of rate matching output bits and an avoided allocation of at least one of the plurality of rate matching output bits, the at least one bit associated with Uplink Control Information (UCI) multiplexing.
20. The apparatus of claim 19, wherein the plurality of rate matching output bits corresponds to a rate matching output size.
21. The apparatus of claim 19, wherein the single TB corresponds to a TB over multiple timeslots (TBoMS).
22. The apparatus of claim 19, wherein each of the one or more bits is allocated for the modulation procedure in one or more Resource Elements (REs).
23. The apparatus of claim 19, wherein the at least one bit allocated for the modulation procedure that is skipped corresponds to at least one unused Physical Uplink Shared Channel (PUSCH) bit.
24. The apparatus of claim 23, wherein the UCI multiplexing is associated with one or more Physical Uplink Control Channel (PUCCH) acknowledgement bits or non-acknowledgement bits.
25. The apparatus of claim 19, wherein the starting boundary for at least one subsequent slot of the plurality of UL slots is calculated without consideration of UCI multiplexing and is based on the at least one bit allocated for the modulation process being skipped.
26. The apparatus of claim 19, further comprising: an antenna or transceiver coupled to the at least one processor.
27. A method of wireless communication at a User Equipment (UE), comprising:
Calculating a slot length for each of a plurality of Uplink (UL) slots, the slot length for each UL slot being associated with a plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, the slot length for each UL slot being associated with a starting boundary, the plurality of UL slots being associated with at least one of a single Transport Block (TB) or a single rate match;
allocating one or more bits of the plurality of rate-matched output bits for a modulation process; and
avoiding allocation of at least one bit of the plurality of rate matching output bits for the modulation procedure, the at least one bit corresponding to Uplink Control Information (UCI) multiplexing.
28. The method of claim 27, further comprising:
storing the starting boundary associated with each UL slot;
wherein the at least one of the plurality of rate matching output bits that is avoided from being allocated corresponds to an end of one or more of the plurality of UL slots.
29. The method of claim 27, wherein the single TB corresponds to a TB over multiple timeslots (TBoMS).
30. A method for wireless communication at a network entity, comprising:
transmitting, for a User Equipment (UE), an indication of a Physical Uplink Shared Channel (PUSCH) configuration associated with an allocation of a plurality of rate matching output bits for a modulation procedure, a slot length for each of a plurality of UL slots associated with the plurality of rate matching output bits, each UL slot including a starting point for the plurality of rate matching output bits, the slot length for each UL slot associated with a starting boundary, the plurality of UL slots associated with at least one of a single Transport Block (TB) or a single rate match; and
UL transmissions are received based on a first allocation of one or more of the plurality of rate matching output bits and an avoided allocation of at least one of the plurality of rate matching output bits, the at least one bit associated with Uplink Control Information (UCI) multiplexing.
Applications Claiming Priority (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US63/192,546 | 2021-05-24 | ||
| US17/664,630 US20220385398A1 (en) | 2021-05-24 | 2022-05-23 | Erasure style ldpc rate matching for tb over multiple slots |
| US17/664,630 | 2022-05-23 | ||
| PCT/US2022/030745 WO2022251229A1 (en) | 2021-05-24 | 2022-05-24 | Erasure style ldpc rate matching for tb over multiple slots |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117480745A true CN117480745A (en) | 2024-01-30 |
Family
ID=89624239
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202280035222.XA Pending CN117480745A (en) | 2021-05-24 | 2022-05-24 | Erasure LDPC rate matching for TB over multiple timeslots |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117480745A (en) |
-
2022
- 2022-05-24 CN CN202280035222.XA patent/CN117480745A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111357379B (en) | Physical layer enhancement for early data transmission | |
| KR102369215B1 (en) | Size Optimized Encoding of Capability Structures for Multicarrier Systems | |
| CN112005519B (en) | PDSCH rate matching for aperiodic CSI-RS | |
| CN115349293A (en) | DCI design for multi-cross-carrier scheduling | |
| US11424790B2 (en) | Techniques for frequency domain restriction for channel state information with frequency domain compression | |
| KR20230051177A (en) | Sidelink Carrier Aggregation Cross-Carrier Scheduling | |
| KR20230084130A (en) | Enhanced PUCCH transmission for repetition or frequency hopping | |
| CN117616836A (en) | RS availability indication through paging PDCCH and PEI | |
| CN116711423A (en) | PUSCH DMRS bundling indication for different transport blocks | |
| KR20230066563A (en) | Codebook generation for SPS with delayed HARQ | |
| CN116114217A (en) | Reporting of reduced synchronization signal blocks to enable beam management | |
| CN114651514A (en) | Method for configuring uplink cancellation indication for supplemental uplink carrier | |
| US20220232574A1 (en) | Channel coding with unequal error protection for lp uci and hp uci multiplexing in nr | |
| CN117441308A (en) | Transport block grouping for higher frequency bands | |
| KR20220167372A (en) | Time domain resource allocation-based HARQ-ACK feedback generation | |
| CN116783959A (en) | Enhanced frequency resource skipping | |
| CN116250335A (en) | Dynamic PUCCH repetition indication | |
| CN115552954A (en) | Method and apparatus for determining search window and SSB bitmap | |
| CN114303344A (en) | Network coding design | |
| US20220385398A1 (en) | Erasure style ldpc rate matching for tb over multiple slots | |
| US11722189B2 (en) | Fronthaul compression for sparse access and dense access | |
| CN117480745A (en) | Erasure LDPC rate matching for TB over multiple timeslots | |
| WO2022251229A1 (en) | Erasure style ldpc rate matching for tb over multiple slots | |
| CN117529901A (en) | Channel aware tone reservation percentage reporting for optimized PAPR performance | |
| KR20230164026A (en) | Dummy markings in DCI with integrated TCI marking |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |