Timeline for uplink control information multiplexing over multiple slot transmissions

Abstract

A method, computer-readable medium, and apparatus for wireless communications are provided that apply a processing timeline to multiplex uplink control information (UCI) in at least one slot of a multi-slot physical uplink shared channel (PUSCH) transmission, and transmit the multi-slot PUSCH transmission with the multiplexed UCI based on the processing timeline being satisfied.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of and priority to U.S. Provisional Application No. 63 / 166,961, entitled "Timelines for Uplink Control Information Multiplexing Over Multiple Slot Transmissions," filed on March 26, 2021, and U.S. Non-Provisional Application No. 17 / 656,209, entitled "Timelines for Uplink Control Information Multiplexing Over Multiple Slot Transmissions," filed on March 23, 2022, the entireties of which are expressly incorporated by reference into this specification.

[0002] The present disclosure relates generally to communication systems, and more particularly, to wireless communications including uplink control information (UCI). [Background technology]

[0003]

[0003] Wireless communication systems have been widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004]

[0004] These multiple access technologies are being adopted in various telecommunication standards to provide a common protocol that allows different wireless devices to communicate on a city, national, regional, or even global scale. An exemplary telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuing mobile broadband evolution promulgated by the 3rd Generation Partnership Project (3GPP®) to meet new requirements related to latency, reliability, security, scalability (e.g., for the Internet of Things (IoT)), and other requirements. 5G NR includes services related to enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE®) standard. Further improvements in 5G NR technology are needed. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the Invention

[0005]

[0005] 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 exhaustive overview of all contemplated aspects, nor is it intended to identify key or critical elements of all aspects or to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0006] In one aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided that apply a processing timeline to multiplex uplink control information (UCI) in at least one slot of a multiple slot physical uplink shared channel (PUSCH) transmission, and transmit the multiple slot PUSCH transmission with the multiplexed UCI based on the processing timeline being satisfied.

[0007]

[0007] To the accomplishment of the foregoing and related ends, the 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 the various aspects may be employed, and the description is intended to include all such aspects and their equivalents. [Brief description of the drawings]

[0008] [Figure 1]

[0008] FIG. 1 illustrates an example of a wireless communication system and access network in accordance with various aspects of the present disclosure. [Figure 2A]

[0009] FIG. 2 illustrates an example of a first frame, according to various aspects of the present disclosure. [Figure 2B]

[0010] FIG. 2 illustrates an example of a DL channel in a subframe, in accordance with various aspects of the present disclosure. [Figure 2C]

[0011] FIG. 13 illustrates an example of a second frame, according to various aspects of the present disclosure. [Figure 2D]

[0012] FIG. 2 illustrates an example of a UL channel in a subframe, in accordance with various aspects of the present disclosure. [Diagram 3]

[0013] FIG. 2 illustrates an example of a base station and user equipment (UE) in an access network, in accordance with various aspects of the present disclosure. [Figure 4]

[0014] 11A-11C illustrate various options for transmission occasions for a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 5A]

[0015] 1 illustrates an example aspect of redundancy version (RV) rotation for multiple transmission occasions of a multi-slot PUSCH in accordance with various aspects of the present disclosure. [Figure 5B] 1 illustrates an example aspect of redundancy version (RV) rotation for multiple transmission occasions of a multi-slot PUSCH in accordance with various aspects of the present disclosure. [Figure 6]

[0016] 1 illustrates an example aspect of transmission occasion-based interleaving for a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 7]

[0017] 4 illustrates an example aspect of slot-based interleaving for a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 8]

[0018] 1 illustrates an example aspect of segment-based interleaving for multi-slot PUSCH transmissions in transmission occasions having non-contiguous segments of resources, in accordance with various aspects of the present disclosure. [Figure 9]

[0019] 1 illustrates an example of UCI overlapping in time with transmission occasions having contiguous resources for a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 10]

[0020] 1 illustrates an example of multiplexing UCI in overlapping slots of a transmission occasion with contiguous resources for a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 11]

[0021] 1 illustrates an example of multiplexing UCI across transmission occasions with contiguous resources for a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 12]

[0022] 1 illustrates an example of multiplexing UCI in overlapping slots of a transmission occasion with contiguous resources for a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 13]

[0023] 1 illustrates an example of multiplexing UCI on transmission occasions with contiguous resources for a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 14]

[0024] 1 illustrates an example of multiplexing repetitions of UCI in transmission occasions with contiguous resources for a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 15]

[0025] 1 illustrates example processing timeline considerations for multiplexing UCI with a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 16]

[0026] 1 illustrates example processing timeline considerations for multiplexing UCI with a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 17]

[0027] 1 illustrates example processing timeline considerations for multiplexing UCI with a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 18]

[0028] 1 illustrates an example of multiple UCIs overlapping transmission occasions with contiguous resources for a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 19]

[0029] 1 illustrates an example of multiplexing multiple UCIs per overlapping slot that overlap with a transmission occasion for a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 20]

[0030] 1 illustrates an example of multiplexing multiple UCIs per transmission occasion that overlap with a transmission occasion for a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 21]

[0031] 1 illustrates example processing timeline considerations for multiplexing UCI from multiple PUCCHs with a multi-slot PUSCH transmission, in accordance with various aspects of the disclosure. [Figure 22]

[0032] 1 illustrates an example of UCI overlapping in time with transmission occasions having non-contiguous segments of resources for a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 23]

[0033] 1 illustrates an example of segment-by-segment multiplexing of overlapping UCI with transmission occasions having non-contiguous segments of resources for a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 24]

[0034] 1 illustrates example processing timeline considerations for multiplexing UCI with multi-slot PUSCH transmissions in transmission occasions having non-contiguous segments, in accordance with various aspects of the disclosure. [Diagram 25]

[0035] 1 illustrates an example communication flow between a UE and a base station, including an example application of a processing timeline for multiplexing with a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 26A]

[0036] 1 is a flowchart of a method of wireless communication including an example application of a processing timeline for multiplexing with a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 26B] 1 is a flowchart of a method of wireless communication including an example application of a processing timeline for multiplexing with a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure. [Figure 27]

[0037] FIG. 2 illustrates an example of a hardware implementation for an exemplary apparatus in accordance with various aspects of the present disclosure. [Figure 28]

[0038] FIG. 1 illustrates an example disaggregated base station architecture. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009]

[0039] A UE may transmit a PUSCH on a transmission occasion that spans multiple slots. A UE may transmit a single TB within multiple slots of a transmission occasion. Sometimes a UE may have uplink control information (UCI) for transmission in a physical uplink control channel (PUCCH) that overlaps in time with a transmission occasion for a PUSCH. Based on the time overlap, a UE may multiplex the UCI with a PUSCH. Aspects presented herein provide various ways for a UE to multiplex a UCI with a multi-slot PUSCH. Multiplexing aspects, including any combination of the number of resources for a UCI, the location for the UCI, multiplexing handling, timeline, rate matching of the PUSCH, and / or interleaving of the PUSCH, may differ based on the type of transmission occasion (e.g., contiguous or non-contiguous). The multiplexing aspects may differ based on the slots of the overlapped PUSCH transmission occasion. The multiplexing aspects may differ based on the type of PUSCH handling, e.g., per-slot, per-transmission occasion, or per-segment interleaving and RV rotation.

[0010]

[0040] The detailed description of the embodiments of the invention described below with reference to the accompanying drawings is intended as an illustration of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description of the invention includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those 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 to avoid obscuring such concepts.

[0011]

[0041] Next, several aspects of a telecommunications system are presented with respect to various apparatus and methods that are described in the detailed description that follows and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0012]

[0042] As an example, an element, or any portion of an element, or any combination of elements, may be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chips (SoCs), 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 various functions described throughout this disclosure. One or more processors in a processing system may execute software. Software should be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, and the like, regardless of whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0013]

[0043] Thus, in one or more exemplary embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on a computer-readable medium or encoded as one or more instructions or codes on the computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may 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 that type of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0014]

[0044] Although aspects and implementations are described in this application by way of illustration for some examples, those skilled in the art will appreciate that additional implementations and use cases may occur in many different configurations and scenarios. The aspects described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging configurations. For example, implementations and / or uses may occur via integrated chip implementations and other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Although some examples may or may not be specifically targeted to a use case or application, a wide combination of applicability of the described aspects may occur. Implementations may range from chip-level or modular components to non-modular non-chip-level implementations, and even aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described aspects. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, transmitting and receiving wireless signals necessarily includes several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processor(s), interleavers, adders / adders, etc.). It is intended that the aspects described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed configurations, aggregated or disaggregated components, end-user devices, etc. of different sizes, shapes and structures.

[0015]

[0045] FIG. 1 illustrates an example of a wireless communication system and access network 100 including a base station 102 or 180 and a UE 104. As described herein, the UE 104 may include a UCI multiplexer component 198. In some aspects, the UCI multiplexer component 198 may be configured to apply a timeline to multiplex UCI in at least one slot of a multi-slot PUSCH transmission. The UE 104 may be configured to transmit a multi-slot PUSCH transmission with multiplexed UCI based on the processing timeline being met. The base station 102 or 180, or a component of the base station, may include a multiplexed UCI receiving component 199. The base station 102 or 180, or a component of the base station, may allocate resources to the UE 104 for the multi-slot PUSCH transmission. In some aspects, the multiplexed UCI receiving component 199 may be configured to receive a multi-slot PUSCH transmission comprising multiplexed UCI in at least one slot of the multi-slot PUSCH transmission based on the processing timeline for UCI multiplexing. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0016]

[0046] The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., 5G core (5GC)). The base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femto cells, pico cells, and micro cells.

[0017]

[0047] A base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 through a first backhaul link 132 (e.g., an S1 interface). A base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with the core network 190 through a second backhaul link 184. In addition to other functions, the base stations 102 may perform one or more of the following functions: forwarding of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracing, RAN information management (RIM), paging, positioning, and distribution 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) over the third backhaul link 134 (e.g., X2 interface). The first backhaul link 132, the second backhaul link 184 (e.g., Xn interface), and the third backhaul link 134 may be wired or wireless.

[0018]

[0048] In some aspects, the base station 102 or 180 may be referred to as a RAN and may include aggregated or disaggregated components. As an example of a disaggregated RAN, the base station may include a central unit (CU) 106, one or more distributed units (DUs) 105, and / or one or more remote units (RUs) 109, as shown in FIG. 1. The RAN may be disaggregated by a split between the RU 109 and the aggregated CU / DU. The RAN may be disaggregated by a split between the CU 106, the DU 105, and the RU 109. The RAN may be disaggregated by a split between the CU 106 and the aggregated DU / RU. The CU 106 and one or more DUs 105 may be connected via an F1 interface. The DUs 105 and the RUs 109 may be connected via a fronthaul interface. The connection between the CU 106 and the DU 105 may be referred to as a midhaul, and the connection between the DU 105 and the RU 109 may be referred to as a fronthaul. The connection between the CU 106 and the core network may be referred to as a backhaul. The RAN may be based on a functional split between various components of the RAN, for example, between the CU 106, the DU 105, or the RU 109. The CU may be configured to implement one or more aspects of a wireless communication protocol, for example, handling one or more layers of a protocol stack, and the DU(s) may be configured to handle other aspects of the wireless communication protocol, for example, other layers of the protocol stack. In different implementations, the split between the layers handled by the CU and the layers handled by the DU may be at different layers of the protocol stack. As one non-limiting example, the DU 105 may provide logical nodes for hosting a radio link control (RLC) layer, a medium access control (MAC) layer, and at least a portion of a physical (PHY) layer, based on the functional split. The RU may provide a logical node configured to host at least a portion of the PHY layer and radio frequency (RF) processing.The CU 106 may host higher layer functions above the RLC layer, such as, for example, a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, etc. In other implementations, the split between the layer functions provided by the CU, DU, or RU may be different.

[0019]

[0049] An access network may include one or more IAB nodes 111 that exchange wireless communications with UEs 104 or other integrated access and backhaul (IAB) nodes 111 to provide access and backhaul to a core network. In an IAB network of multiple IAB nodes, an anchor node may be referred to as an IAB donor. An IAB donor may be a base station 102 or 180 that provides access to a core network 190 or an EPC 160 and / or control over one or more IAB nodes 111. An IAB donor may include a CU 106 and a DU 105. An IAB node 111 may include a DU 105 and a mobile termination (MT). The DU 105 of an IAB node 111 may act as a parent node, and the MT may act as a child node.

[0020]

[0050] The base stations 102 may wirelessly communicate with the UE 104. Each of the base stations 102 may provide communication coverage to a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be known as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB) that may serve a closed group known as a closed subscriber group (CSG). A communication link 120 between the base station 102 and the UE 104 may include uplink (UL) transmissions (also referred to as a reverse link) from the UE 104 to the base station 102, and / or downlink (DL) transmissions (also referred to as a forward link) from the base station 102 to the UE 104. The 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 spectrum with up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) bandwidth per carrier allocated in a carrier aggregation with up to Yx MHz total (x component carriers) used for transmission in each direction. The carriers may be adjacent or non-adjacent to each other. The carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​than for 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).

[0021]

[0051] Several UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use DL / UL WWAN spectrum. The D2D communication links 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through various wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0022]

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

[0023]

[0053] The small cell 102' may operate in licensed and / or unlicensed frequency spectrums. When operating in an unlicensed frequency spectrum, the small cell 102' may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, etc.) used by the Wi-Fi AP 150. A small cell 102' employing NR in an unlicensed frequency spectrum may boost coverage to and / or increase capacity of an access network.

[0024]

[0054] The electromagnetic spectrum is often subdivided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. A similar naming issue sometimes arises with respect to FR2, which is often referred to (interchangeably) as the "millimeter wave" band in documents and papers, even though FR2 is different from the extremely high frequency (EHF) bands (30 GHz - 300 GHz) identified as "millimeter wave" bands by the International Telecommunications Union (ITU).

[0025]

[0055] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR research has identified these mid-band frequency operating bands as frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands that fall within FR3 may inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0026]

[0056] With the above aspects in mind, it should be understood that unless otherwise specified, terms such as "sub-6 GHz," as used herein, may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, it should be understood that unless otherwise specified, terms such as "millimeter wave," as used herein, may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0027]

[0057] The base station 102, whether a small cell 102′ or a large cell (e.g., a macro base station), may include and / or be referred to as an eNB, g Node B (gNB), or another type of base station. Some base stations, such as the gNB 180, may operate in a conventional sub-6 GHz spectrum, in millimeter wave frequencies, and / or at near millimeter wave frequencies in communication with the UE 104. When the gNB 180 operates at millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for path loss and short range. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to enable beamforming.

[0028]

[0058] The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182′. The UE 104 may receive a beamformed signal from the base station 180 in one or more receive directions 182″. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive a beamformed signal from the UE 104 in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 180 / UE 104. The transmit direction and receive direction for the base station 180 may be the same or different. The transmit direction and receive direction for the UE 104 may be the same or different.

[0029]

[0059] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication 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, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are forwarded through the Serving Gateway 166, which is itself connected to the PDN Gateway 172. The PDN Gateway 172 provides IP address allocation for the UE as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176. The IP services 176 may include Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming services, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may act as an entry point for content provider MBMS transmissions, may be used to authorize and start MBMS bearer services in a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to deliver MBMS traffic to base stations 102 that belong to a Multicast Broadcast Single Frequency Network (MBSFN) area that broadcasts a particular service, and may be responsible for session management (start / stop) and collecting eMBMS-related charging information.

[0030]

[0060] The core network 190 may include an access and mobility management function (AMF) 192, another AMF 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may be in communication with an integrated data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are forwarded through the UPF 195. The UPF 195 provides IP address allocation for the UE as well as other functions. The UPF 195 is connected to IP services 197. The IP services 197 may include the Internet, intranet, IP multimedia subsystem (IMS), packet switched (PS) streaming (PSS) services, and / or other IP services.

[0031]

[0061] A base station may include and / or be referred to as a gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit reception 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 UEs 104. Examples of the UEs 104 include cellular phones, smartphones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, gaming consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas 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 device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0032]

[0062] FIG. 2A is a diagram 200 illustrating an example of a first subframe in a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of a DL channel in a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe in a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of a UL channel in a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) where for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to either DL or UL, or may be time division duplex (TDD) where for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to both DL and UL. In the example provided by FIG. 2A, FIG. 2C, the 5G NR frame structure is assumed to be TDD, subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and F is flexible for use between DL / UL, and subframe 3 is configured with slot format 1 (all UL). Although subframes 3 and 4 are shown with slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and UL, respectively. The other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with the slot format through a received slot format indicator (SFI) (dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling). The description also applies to 5G NR frame structures that are TDD.

[0033]

[0063] 2A-2D illustrate a frame structure, and aspects of the present disclosure may be applicable to other wireless communication technologies, which may have different frame structures and / or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. A subframe may also include a minislot, which may include 7, 4, or 2 symbols. Depending on whether the cyclic prefix (CP) is normal or extended, each slot may include 14 or 12 symbols. For a normal CP, each slot may include 14 symbols, and for an extended CP, each slot may include 12 symbols. The symbols on the DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL can be CP-OFDM symbols (for high throughput scenarios) or Discrete Fourier Transform (DFT) Spread OFDM (DFT-s-OFDM) symbols (also called Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-limited scenarios limited to single stream transmission). The number of slots in a subframe is based on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) and the symbol length / duration, which is effectively equal to 1 / SCS.

[0034] [Table 1]

[0035] For the normal CP (14 symbols / slot), the different numerologies μ0-4 allow for 1, 2, 4, 8, and 16 slots per subframe, respectively. For the extended CP, numerology 2 allows for 4 slots per subframe. Thus, for the normal CP and numerology μ, 14 symbols / slot and 2 μ There are slots / subframes. The subcarrier spacing is 2 μ*15 kHz, where μ is a numerology 0-4. Thus, numerology μ=0 has a subcarrier spacing of 15 kHz, and numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D provide an example of a normal CP with 14 symbols per slot and a numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see Figure 2B) that are frequency division multiplexed. Each BWP may have a specific numerology and CP (normal or extended).

[0036]

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

[0037]

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

[0038]

[0066] FIG. 2B illustrates an example of various DL channels in a subframe of a frame. A physical downlink control channel (PDCCH) carries DCI in one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including 6 RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. The PDCCHs in one BWP may be referred to as a control resource set (CORESET). A 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 the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be in symbol 2 of a particular subframe of a frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identity. The secondary synchronization signal (SSS) may be in symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH), which carries the master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also called SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data and broadcast system information not transmitted through the PBCH, such as the system information block (SIB), and paging messages.

[0039]

[0067] As shown in FIG. 2C, some of the REs carry DM-RS (denoted as R for one particular configuration, although other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and depending on the particular PUCCH format used. The UE may transmit a sounding reference signal (SRS). The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and the UE may transmit the SRS on one of the combs. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0040]

[0068] 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as shown in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQIs), precoding matrix indicators (PMIs), rank indicators (RIs), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) information (ACK / negative ACK (NACK)) feedback. The PUSCH carries data and may be further used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCIs.

[0041]

[0069] 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 375. The controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes a Radio Resource Control (RRC) layer, and Layer 2 includes a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. The controller / processor 375 controls RRC layer functions related to broadcasting of system information (e.g., MIBs, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting, as well as PDCP layer functions related to header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions, as well as RLC layer functions related to transfer of upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs, as well as mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) and MAC SDUs from the TBs. It provides MAC layer functions related to demultiplexing of SDUs, scheduling information reporting, error correction via HARQ, priority handling and logical channel prioritization.

[0042]

[0070] The transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions related to various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on transport channels, forward error correction (FEC) coding / decoding of transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols 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 domain and / or frequency domain, and then combined with each other using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM streams are spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a respective spatial stream for transmission.

[0043]

[0071] At the UE 350, each receiver 354RX receives a signal through its respective antenna 352. Each receiver 354RX recovers information modulated onto an RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement Layer 1 functions related to various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, the spatial streams may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 310. These soft decisions may be based on channel estimates calculated by a channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals 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 implements Layer 3 and Layer 2 functions.

[0044]

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

[0045]

[0073] Similar to the functions described with respect to DL transmission by the base station 310, the controller / processor 359 provides RRC layer functions related to system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting, as well as PDCP layer functions related to header compression / decompression and security (encryption, decryption, integrity protection, integrity verification), as well as RLC layer functions related to transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs, as well as MAC layer functions related to mapping between logical channels and transport channels, multiplexing and demultiplexing of MAC SDUs onto and from the TB, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0046]

[0074] Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select an appropriate coding and modulation scheme and to enable spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.

[0047]

[0075] The UL transmission is processed at the base station 310 in a manner similar to that described with respect to the receiver functions at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0048]

[0076] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0049]

[0077] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to implement aspects related to the UCI multiplexer component 198 of FIG.

[0050]

[0078] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to implement aspects related to the multiplexed UCI receiving component 199 of FIG.

[0051]

[0079] A PUSCH may be transmitted across multiple slots as a multi-slot PUSCH transmission. A PUSCH transmission may span multiple transmission occasions. A transmission occasion may include uplink resources, e.g., uplink slots, with resources allocated to a UE for transmission of the PUSCH. FIG. 4 shows a diagram 400 illustrating two different options for a multi-slot PUSCH transmission. FIG. 4 also shows an example slot pattern 406, e.g., a TDD uplink / downlink slot pattern. In a first option, e.g., shown as option (a) in FIG. 4, each transmission occasion of a multi-slot PUSCH transmission includes contiguous resources (e.g., contiguous symbols or contiguous slots) that span one or more slots, e.g., as shown for transmission occasion 402. In some aspects, the contiguous resources may include contiguous symbols that span two different slots. FIG. 4 shows that the contiguous resources of each transmission occasion may be separated by resources that are not part of the PUSCH transmission, such as downlink slots. For example, in a second option, shown as option (b) in FIG. 4, each transmission occasion may include non-contiguous resources, which may include multiple sets of contiguous resources, as shown for transmission occasion 404.

[0052]

[0080] The time domain resource allocation (TDRA) of a multi-slot PUSCH transmission occasion provides a set of consecutive or non-consecutive symbols of the transmission occasion. For a transmission occasion of consecutive resources, e.g., option (a) in FIG. 4, the TDRA may be indicated as a pair of a start symbol (S) for the consecutive resources and a length (L) of the consecutive resources of the transmission occasion, e.g., pair (S,L). FIG. 4 shows an example of (S,L)=(0,20) to illustrate the concept. S=0 may correspond to the first symbol of an uplink slot of an uplink grant, and L=20 may correspond to a length of 20 symbols. For a transmission occasion of non-consecutive resources, e.g., option (b) in FIG. 4, the TDRA may be indicated as a triplet of (D,S,L), where D further indicates a slot index relative to a reference slot. The reference slot may be a slot in which the UE receives DCI with an uplink grant from the base station. The reference slot may be the slot indicated by the DCI as the beginning of the transmission occasion, which may be referenced by the parameter K2. Figure 4 shows an example of (D,S,L) = {(0,0,28), (5,0,28)} to illustrate the concept. In the first triplet, D = 0 may indicate that the transmission occasion starts 0 slots from the reference slot, S = 0 indicates the first symbol of the slot as the starting symbol, and L = 28 indicates a length of 28 symbols. In the second triplet, D = 5 may indicate that the transmission occasion starts 5 slots from the reference slot, S = 0 indicates the first symbol of the slot as the starting symbol, and L = 28 indicates a length of 28 symbols. Thus, the first triplet indicates a first set of contiguous resources, and the second triplet indicates a second set of contiguous resources, where the first set of contiguous resources and the second set of contiguous resources are non-contiguous with each other. L may be the same in both triplets, as in this example. In other aspects, the sets of contiguous resources that form the non-contiguous resources of a transmission occasion may have different lengths.

[0053]

[0081] A single transport block (TB) of the PUSCH may be transmitted in a transmission occasion. If repetition is enabled, the TB may be transmitted on multiple transmission occasions. Thus, multi-slot PUSCH repetition may occur on a set of transmission occasions, with each repetition of the TB being transmitted within a single transmission occasion. FIG. 5A illustrates an example of four repetitions of a PUSCH TB in four transmission occasions of contiguous resources according to option (a) and two repetitions of a PUSCH TB in two transmission occasions with non-contiguous sets of resources according to option (b). In some aspects, a repetition factor may be indicated by the base station to the UE, e.g., along with the TDRA for a multi-slot PUSCH transmission. The repetition factor may indicate the amount of repetition to the UE. In some aspects, along with the TDRA, the base station may indicate a periodicity or offset parameter to the UE, which may indicate the interval for the repetition to the UE. For example, the base station may indicate an inter-repetition gap in symbols or slots. FIG. 5A illustrates an example gap 502 between repetitions for option (a). A gap may, for example, indicate a separation in time between the end of one transmission occasion and the beginning of the next transmission occasion, or may indicate a separation in time between the beginning of one transmission occasion and the beginning of the next transmission occasion.

[0054]

[0082] 5A and 5B show different examples of redundancy version (RV) rotation over repetitions of a TB transmitted as a multi-slot PUSCH transmission. The examples in FIG. 5A and 5B correspond to the same source payload for a TB and may show that the same source payload may be coded differently over resources of a transmission occasion. In the diagram 500 in FIG. 5A, the RV is refreshed, e.g., changed, between transmission occasions, e.g., in gaps 502. In FIG. 5A, RV0 is applied to contiguous resources of the first transmission occasion. The RV index is changed to RV2 in the subsequent transmission occasion. The RV index is then changed to RV3 and RV1 for the subsequent transmission occasion. Similarly, for transmission occasions of non-contiguous resource sets in option (b), the RV index is similarly maintained over the non-contiguous resource sets of a single transmission occasion and changed or refreshed for the subsequent transmission occasion. The examples are shown for transmission of a TB on a single transmission occasion. Thus, the RV cycles over repetitions of the TB at different transmission occasions.

[0055]

[0083] FIG. 5B shows a diagram 550 in which the RV may be cycled within each transmission occasion, rather than between transmission occasions as in FIG. 5A. As shown for option (b) in FIG. 5B, a single RV index may be used on a set of consecutive symbols of non-consecutive transmission occasions, and may be changed to a different RV index in a subsequent set of consecutive symbols in the same transmission occasion. Thus, the RV may be refreshed or changed in the gap between consecutive resources of a single transmission occasion. As shown for option (a) in FIG. 5B, a single RV index may be used on the symbols of a single slot, and a different RV index may be applied to the symbols of subsequent slots of the transmission occasion. Thus, the RV may be refreshed or changed at the slot boundaries of a single transmission occasion.

[0056]

[0084] The aspects presented herein may be applied for multi-slot PUSCH transmissions using a single codebook. In some examples, the aspects presented herein may be applied for multi-codebook PUSCH transmissions. However, multi-codebook PUSCH transmissions may provide less gain compared to single-codebook implementations. In some aspects, TB sizes may range from about 100 bits to 1000 bits, although the aspects may be applied to TB sizes smaller or larger than that range as well.

[0057]

[0085] When a UE transmits a PUSCH spanning multiple slots, the UE may know / store the status of the transmission across the slot. In some aspects, the status may refer to the status of the last transmitted bit. If the UE interleaves the PUSCH transmission, it may be difficult for the UE to transmit the PUSCH across slots or across non-consecutive symbols. For example, the UE may use information about how much of the interleaved sequence has been transmitted and / or may store the sequence that has not been transmitted. To simplify the UE operation, the UE may apply interleaving, for example, within a slot.

[0058]

[0086] FIG. 6 shows a diagram 600 illustrating an example aspect of interleaving TBs for a multi-slot PUSCH transmission. FIG. 6 shows a pattern of transmission occasions of contiguous resources, e.g., similar to option (a) in FIG. 4. The TB may be transmitted within a single transmission occasion, such as in slot 0, e.g., 604, and slot 1, e.g., 606, of transmission occasion 602. The UE may read information bits of the TB from the circular buffer based on a starting position indicated by an RV index, e.g., as shown at 610. The information bits of the TB may start, e.g., in RB0. Rate matching bits read from the circular buffer are shown at 620. Rate matching may include a process in which a number of coded bits that may be transmitted on available resources for a PUSCH transmission is determined. For example, the total number of bits may be equal to the total number of available REs multiplied by a modulation order. The determined number of coded bits may then be read from the circular buffer. "Rate matching bits" as used herein refers to coded bits selected for transmission based on rate matching requirements and / or principles. The amount of bits may be selected in some aspects based on the amount of bits for rate matching the TB within the transmission occasion 602. After reading the bits, the UE may apply interleaving to the bits. For example, the channel coding process for the PUSCH transmission may include a bit level interleaver for each CB of the TB. FIG. 6 illustrates an example of row-column interleaving, where bits may be organized, e.g., read or placed, into multiple columns. FIG. 6 illustrates a first row 630 and a second row 632. Bits are then read from the two rows (e.g., 630, 632) based on the column. Thus, bits from the first column of row 630 correspond to bits 640 for transmission in slot 0. Bits from the first column of row 632 correspond to bits 642 for transmission in slot 0.The process continues with the bits in the second column of row 630 being placed at 644, followed by the bits in the second column of row 632 being placed at 646, and so on. Bits for rate matching across transmission occasions may be interleaved and transmitted as shown in FIG. 6, which shows interleaving applied across slot 0 and slot 1 of transmission occasion 602. In other aspects, bits for rate matching may be selected per slot and interleaved per slot before transmission as shown in FIG. 7. FIG. 7 shows a diagram 700 showing that bits for slot 0 may be read into rows 730 and 732, and bits for slot 1 may be read into rows 734 and 736. In that case, the bits for slot 0 are read column-wise from rows 730 and 732 to form a slot-based interleaved pattern 740 for slot 0, and the bits for slot 1 are read column-wise from rows 734 and 736 to form a slot-based interleaved pattern 742 for slot 1.

[0059]

[0087] 6, 7, and 8 are based on the entire TB being coded in a single code block (CB). The TB may be coded across multiple CBs. When the entire TB is coded using a single CB, the coded bits (in the circular buffer) for transmission may be selected per slot or per TO. These selected bits are called rate-matched bits. The interleaver operates on the rate-matched bits. When the rate-matched bits are selected for the entire TO at once, the interleaver spans the entire TO. When the rate-matched bits are selected per slot, the interleaver spans a single slot. When the rate-matched bits are selected per slot, multiple sets of rate-matched bits will be selected and interleaved individually such that resources across the TO are used.

[0060]

[0088] The example in FIG. 6 may be applied for transmission occasion-based rate matching and interleaving for non-contiguous resources of a single transmission occasion, such as in option (b) of FIG. 4. Instead of bits for slot 0 and slot 1 as in FIG. 6, bits may be for non-contiguous slots comprised in the same transmission occasion. FIG. 8 shows a diagram 800 of an example of segment-based rate matching and interleaving for non-contiguous resources of a single transmission occasion, such as in option (b) shown in FIG. 8. FIG. 8 shows a transmission occasion 802 including a first segment 804 of contiguous resources and a second segment 806 of contiguous resources. Instead of being rate matched and interleaved slot by slot as in FIG. 7, bits may be read for rate matching and interleaving, such as row-column interleaving, to obtain interleaved bits 840 of the first segment (e.g., 804) of contiguous resources and interleaved bits 842 of the second segment (e.g., 806) of contiguous resources.

[0061]

[0089] Thus, in a first option, rate matching and interleaving may be applied to bits across transmission occasions, as shown in FIG. 6, which may be referred to as transmission occasion-based rate matching and interleaving, or rate matching and interleaving across transmission occasions. Thus, bits may be selected, read, or otherwise input for a transmission occasion. The bits for a transmission occasion may then be rate matched, interleaved, and transmitted by the UE. In a second option, bits may be selected per slot, as shown in FIG. 7, and interleaving may be applied to bits for a slot, which may be referred to as slot-based interleaving, per-slot interleaving, or interleaving across slots. Thus, bits may be selected, read, or otherwise input for a slot. The bits for a slot may then be interleaved and transmitted by the UE. In a third option, as shown in Figure 8, bits may be selected for each segment of a transmission occasion with non-contiguous segments, and interleaving may be applied to the bits for each segment, which may be referred to as segment-based interleaving, per-segment interleaving, or interleaving across segments. Thus, bits may be selected, read, or otherwise input for a segment. The bits for the segment may then be interleaved and transmitted by the UE.

[0062]

[0090] If the UE rate-matches and interleaves bits per slot, as in FIG. 7, the UE may use a starting position in the circular buffer for each slot. The UE may not need to buffer the interleaved bits and may instead save the circular buffer. Rate-matching and interleaving per slot may provide improved timeline, resource management, and / or memory management for the UE. In some aspects, UCI may be multiplexed with PUSCH. UCI multiplexing may be considered per slot, for example, based on the overlap between the slots in which UCI should be transmitted and the slots in which PUSCH should be transmitted. In some aspects, the timeline may be tied to a different reference point than the beginning of the multi-slot PUSCH transmission.

[0063]

[0091] As shown in the example in FIG. 8, to rate match and interleave bits per segment, the UE may remember the starting position in the circular buffer for each segment, e.g., without buffering the interleaved bits, similar to slot-based interleaving.

[0064]

[0092] For example, if the UE rate-matches and interleaves bits across transmission occasions, as in FIG. 6, performance may be improved because the system bits may occupy more reliable positions within the transmission occasions.

[0065]

[0093] UCI multiplexing per slot may be easier when rate matching and interleaving per slot compared to rate matching and interleaving bits across a transmission occasion or a segment of a transmission occasion.

[0066]

[0094] In some aspects, a UE may have UCI for transmission at a time that overlaps with a multi-slot PUSCH transmission. The UE may multiplex UCI with the PUSCH transmission. UCI may be scheduled within a slot, and PUSCH may span multiple slots. The aspects presented herein enable a UE to determine how many resources allocated for PUSCH to use for UCI, the location for UCI within PUSCH, coding and rate matching for PUSCH with multiplexed UCI, etc.

[0067]

[0095] FIG. 9 illustrates an example 900 of a transmission occasion 902 with contiguous resources (e.g., resources in slot 904 and slot 906) similar to option (a) in FIG. 4. FIG. 9 also illustrates a PUCCH overlap of UCI 908 with slot 906 of PUSCH 910. As presented herein, overlap between PUSCH and PUCCH may be handled independently for each transmission occasion of PUSCH. The UCI may include various types of information. In some aspects, the UCI may include ACK / NACK information for PDSCH received from the base station, e.g., HARQ feedback. In other aspects, the UE may receive and measure CSI-RS from the base station and have a CSI report to send to the base station as UCI.

[0068]

[0096] For each transmission occasion in which one of multiple slots of consecutive resources of the transmission occasion overlaps in time with a PUCCH resource for transmission of UCI, the UE may consider whether to multiplex the PUCCH, e.g., UCI, in the resources of the transmission occasion.

[0069]

[0097] The UE may consider, for example, whether to multiplex UCI of the PUCCH in the overlapping slot, but not in other slots of the transmission occasion. In some aspects, the timeline for multiplexing UCI may be based on the overlapping slot, e.g., slot 906 in FIG. 9. In other aspects, the timeline for multiplexing UCI may be based on the start of the transmission occasion 902.

[0070]

[0098] The UE may, for example, consider whether to multiplex UCI of the PUCCH onto a transmission occasion, rather than being limited to slots of overlap with the UCI. The timeline for multiplexing the UCI may be based on the start of the transmission occasion 902.

[0071]

[0099] Table 1 illustrates an example of various scenarios (eg, Examples 1-5) illustrating various combinations of considerations for multiplexing UCI with contiguous resource transmission occasions of a multi-slot PUSCH transmission (eg, option (a) of FIG. 4).

[0072] [Table 2]

[0073]

[0100] FIG. 10 shows an example diagram 1000 of Example 1 from Table 1 in which UCI 1008 overlaps in slot 0 (e.g., slot 1004) of a transmission occasion 1002 with contiguous resources in slots 1004 and 1006. The UCI overlaps in slot 0 and is multiplexed in slot 0 of the transmission occasion 1002. FIG. 10 shows that resources for the UCI may be comprised within a single slot, e.g., slot 0 1004. Slot 0 may also include other transmissions in the symbols of the slot. For example, the UCI may be transmitted following the transmission of the DMRS.

[0074]

[0101] In the example in Figure 10, the UE may determine resources for UCI transmission based on resources available in slot 0 1004. The UE may apply a beta factor on top of resources available for PUSCH transmission in slot 0 1004. In the case of a single-slot PUSCH, the UE may determine the number of REs potentially available for UCI transmission across the PUSCH symbols in which UCI may be multiplexed, which is that number of REs divided by the total number of PUSCH bits.

[0075]

[0102] In contrast, for a multi-slot PUSCH transmission based on the example in FIG. 10, the UE may instead determine the number of REs potentially available for UCI across PUSCH symbols in a particular slot of the transmission occasion (e.g., slot 0 1004) divided by the total number of PUSCH symbols in the transmission occasion, after scaling with a factor based on the number of symbols in slot 0.

[0076]

[0103] As an example, for a UCI including a HARQ-ACK bit on a single slot PUSCH, the UE

[0077]

number

[0078] The number of coded modulation symbols per layer for HARQ-ACK transmission, denoted as:

[0079]

number

[0080]

[0104] In this example of Eq. 1, O ACK is the number of HARQ-ACK bits, and L ACK is the number of CRC bits for HARQ-ACK.

[0081]

number

[0082] is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers.

[0083]

number

[0084] In PUSCH transmission,

[0085]

number

[0086] is the number of resource elements that can be used for transmission of UCI in OFDM symbol l,

[0087]

number

[0088] is the total number of OFDM symbols for PUSCH transmission, including all OFDM symbols used for DMRS.

[0089]

number

[0090] is the number of subcarriers in OFDM symbol l in a PUSCH transmission that carries PTRS. α is configured by a higher layer parameter, e.g., a scaling parameter. In this example, l0 is the symbol index of the first OFDM symbol in a PUSCH transmission that does not carry DMRS for PUSCH after the first DMRS symbol(s).

[0091]

number

[0092] is the beta offset.

[0093]

[0105] Therefore, in this single slot PUSCH example,

[0094]

number

[0095] may correspond to the total number of PUSCH bits,

[0096]

number

[0097] may correspond to the number of REs potentially available for UCI across all of the PUSCH symbols.

[0098]

[0106] In contrast, for the multi-slot PUSCH transmission occasion of FIG. 10,

[0099]

number

[0100] may correspond to the number of REs potentially available for UCI 1008 across the PUSCH symbols in slot 0 1004, and

[0101]

number

[0102] may correspond, for example, to the total number of PUSCH bits scaled by the number of symbols in slot 0 divided by the total number of PUSCH symbols in transmission occasion 1002, including both slot 0 1004 and slot 1 1006. Such a determination better takes into account the overall burden placed on a PUSCH transmission when multiplexing UCI 1008 into slot 0.

[0103]

[0107] After determining the number of resources to use for UCI 1008 in slot 0 in FIG. 10, the UE may identify the location of the resources in slot 0 1004. The UE may then fill the identified resources in slot 0 1004 with UCI symbols. The UE may first fill the frequency resources of a particular symbol, for example, if all of the frequency resources of the symbol are filled with UCI, and then fill in additional symbols. Such filling of resources may be referred to as a frequency first, time second manner. The UE may use the remaining resources in slot 0 1004 and slot 1 1006 to determine PUSCH rate matching bits, for example, based on the remaining resources of the transmission occasion. The UE may interleave the rate matched bits of the PUSCH 1110. As shown in Table 1, the rate matching and interleaving and / or RV cycling for Example 1 may be either per slot (e.g., as described with respect to FIG. 7) or per transmission occasion (e.g., as described with respect to FIG. 6). After interleaving, the UE may fill resources of the identified transmission occasion 1002 for the PUSCH 1010 with the interleaved bits mapped to modulation symbols.

[0104]

[0108] Figure 11 is a diagram 1100 illustrating a PUCCH (e.g., UCI 1108) overlapping with a PUSCH 1110 in slot 0 1104 of a transmission occasion 1102 and multiplexed based on the transmission occasion 1102 as well as the slot of the overlap. Figure 11 corresponds to Example 2 in Table 1, where the overlapping slot is slot 0 and the multiplexing is based on the transmission occasion. As shown in Figure 11, the resources for multiplexing the UCI 1108 may span multiple slots.

[0105]

[0109] In the example in FIG. 11, the UE may determine resources for UCI based on available resources in transmission occasion 1102. For example, in the multi-slot PUSCH transmission occasion 1102 in FIG. 11,

[0106]

number

[0107] may correspond to the number of REs potentially available for UCI 1108 across the PUSCH symbols of the transmission occasion 1102 (including slot 0 1104 and slot 1 1106), and

[0108]

number

[0109] may correspond to the total number of PUSCH bits for multiple slots of the transmission occasion 1102.

[0110] After determining the number of resources to use for UCI 1108 in the transmission occasion 1102, the UE may identify the location of the resources within the transmission occasion 1102. The UE may then fill the identified resources in the transmission occasion 1102 with UCI symbols. The UE may fill the resources in a frequency-first, time-second manner. The UE may determine PUSCH rate-matching bits using the remaining resources in the transmission occasion 1102 (e.g., in slot 0 1104 and slot 1 1106). The UE may interleave the rate-matched bits of the PUSCH. As shown in Table 1, in Example 2, the rate matching and interleaving and / or RV rotation may be per slot (e.g., as described with respect to FIG. 7) or per transmission occasion (e.g., as described with respect to FIG. 6). After interleaving, the UE may fill resources of the identified transmission occasion 1102 for the PUSCH 1110 with the interleaved bits mapped to modulation symbols.

[0111]

[0111] Figure 12 shows a diagram 1200 showing a PUCCH (e.g., UCI 1208) overlapping with slot 1 1206 of a transmission occasion 1202 for a PUSCH 1210, rather than the first slot 1204 of the transmission occasion 1202 as in Figures 10 and 11. Figure 12 corresponds to Example 3 in Table 1, where the overlapping slot is slot 1 and is multiplexed in slot 1. Figure 12 shows an example where UCI 1208 is multiplexed within a single slot (e.g., slot 1 1206).

[0112] The UE may determine the number of resources to use for UCI 1208 in slot 1 1206. Similar to the description with respect to FIG. 10, the UE may determine the number of resources based on the number of REs potentially available for UCI in the PUSCH symbols of slot 1 1206 and based on the total number of PUSCH bits scaled by the number of symbols in slot 1 and the total number of PUSCH symbols in the transmission occasion.

[0113] For example, in formula 1

[0114]

number

[0115] may correspond to the number of REs potentially available for UCI 1208 across the PUSCH symbols in slot 1 1206, and

[0116]

number

[0117] may correspond, for example, to the total number of PUSCH bits scaled by the number of symbols in slot 1 1206 divided by the total number of PUSCH symbols in transmission occasion 1202, which includes both slot 0 1204 and slot 1 1206.

[0118] After determining the number of resources to use for UCI 1208 in slot 1 in FIG. 12, the UE may identify the location of the UCI resources in slot 1 1204. The UE may then fill the identified resources in slot 1 1204 with UCI symbols. The UE may fill the resources in a frequency-first, time-second manner. The UE may determine the PUSCH rate-matching bits using the remaining resources in slot 1 1206. The UE may determine the rate-matched bits for slot 1 based on where the slot 0 transmission ended. The UE may then interleave the rate-matched bits. As shown in Table 1, the rate matching and interleaving and / or RV cycling for Example 3 may be either per slot (e.g., as described with respect to FIG. 7) or per transmission occasion (e.g., as described with respect to FIG. 6). After interleaving, the UE may fill the resources identified for the PUSCH 1210 with the interleaved bits mapped to modulation symbols.

[0119] FIG. 13 illustrates a diagram 1300 showing a PUCCH (e.g., UCI 1308) overlapping slot 1 1306 of a transmission occasion 1302 for a PUSCH 1310, rather than the first slot 1304 of the transmission occasion 1302, as in FIG. 10 and FIG. 11. In contrast to FIG. 12, in FIG. 13, UCI is multiplexed based on transmission occasion, rather than the slot of overlap. Thus, in FIG. 12, UCI is multiplexed in slot 0 1304, and not necessarily in the slots where UCI overlaps. In some aspects, multiplexed UCI may span multiple slots. FIG. 13 may correspond to Example 4 in Table 1.

[0120] In the example in FIG. 13, the UE may determine the resource for the UCI 1308 based on the available resources in the transmission occasion 1302. For example, in the multi-slot PUSCH transmission occasion 1302 in FIG. 13,

[0121]

number

[0122] may correspond to the number of REs potentially available for UCI 1308 across the PUSCH symbols of the transmission occasion 1302 (including slot 0 1304 and slot 1 1306), and

[0123]

number

[0124] may correspond to the total number of PUSCH bits for multiple slots of the transmission occasion 1302.

[0125] After determining the number of resources to use for UCI 1308 in the transmission occasion 1302, the UE may identify the location of the resources within the transmission occasion 1302. The UE may then fill the identified resources in the transmission occasion 1302 with UCI symbols. The UE may fill the resources in a frequency-first, time-second manner. The UE may determine PUSCH rate-matching bits using the remaining resources in the transmission occasion 1302 (e.g., in slot 0 1304 and slot 1 1306). The UE may interleave the rate-matched bits of the PUSCH. As shown in Table 1, in Example 4, the interleaving / RV rotation may be per slot (e.g., as described with respect to FIG. 7) or per transmission occasion (e.g., as described with respect to FIG. 6). After interleaving, the UE may fill resources of the identified transmission occasion 1302 for the PUSCH 1310 with the interleaved bits mapped to modulation symbols.

[0126] FIG. 14 shows a diagram 1400 illustrating a PUCCH (e.g., UCI 1408 and / or 1409) multiplexed with multiple slots (e.g., slot 0 1404 and slot 1 1406) of a transmission occasion 1402 for a PUSCH 1410. Resources to use for multiplexing the UCI may be comprised in a single slot and may be repeated in each slot. The UCI may be repeated in each slot of the transmission occasion 1402. The timeline may be based on slot 0 1404 of the transmission occasion 1402. FIG. 14 may correspond to Example 5 in Table 1.

[0127] FIG. 15 illustrates a diagram 1500 illustrating aspects of timeline considerations for multiplexing UCI in a multi-slot PUSCH transmission. As illustrated in FIG. 15, a UE may consider multiplexing UCI for a transmission in a PUCCH 1510 that overlaps in time with a transmission occasion for a multi-slot PUSCH 1504. The UE may apply a processing timeline in determining whether to multiplex UCI (e.g., from the PUCCH 1510) into the PUSCH 1504. In some aspects, the processing timeline may be based on a minimum gap (N2) of symbols between the reception of an uplink grant DCI 1502 that schedules uplink resources for the PUSCH 1504 and the start of the multi-slot PUSCH transmission 1504. If the start of the multi-slot PUSCH transmission 1504 is more than N2 symbols after the uplink grant DCI 1502 is received, the UE may transmit the multi-slot PUSCH 1504. If the start of the multi-slot PUSCH transmission 1504 is less than N2 symbols after the uplink grant DCI 1502 is received, the UE may not transmit the multi-slot PUSCH 1504. In some aspects, the processing timeline may be based on a minimum gap of symbols (N1) between the reception of the PDSCH 1508 and the start of the PUCCH 1510 carrying the UCI (e.g., HARQ ACK / NACK payload for the reception of the PDSCH). If the start of the PUCCH 1510 is more than N1 symbols after the PDSCH 1508 is received, the UE may transmit the UCI (e.g., HARQ ACK / NACK) in the PUCCH 1510. If the start of the PUCCH 1510 is less than N1 symbols after the PDSCH 1508 is received, the UE may not transmit the UCI (e.g., HARQ ACK / NACK) in the PUCCH 1510. When the UE is considering multiplexing UCI from the PUCCH 1510 into a multi-slot PUSCH 1504, a reference time (e.g., S0) may be used to measure whether a processing timeline based on N2 and N1 is satisfied.The reference time may differ based on various aspects of UCI multiplexing, such as if PUCCH overlap occurs, if UCI should be multiplexed, and the manner in which UCI should be multiplexed. As an additional consideration, HARQ ACK / NACK bits from the PUCCH 1510 may be multiplexed into the multi-slot PUSCH 1504 if a downlink grant 1506 for the PDSCH 1508 is received before an uplink grant 1502 for the multi-slot PUSCH 1504.

[0128]

[0120] In a first example, such as in the example in FIG. 10, when the PUCCH 1510 overlap occurs in the first slot of a multi-slot PUSCH transmission 1504 and UCI is multiplexed onto the first slot, the reference time S0 may be based on the start of the multi-slot PUSCH transmission 1504, as shown in FIG. 15.

[0129]

[0121] For example, as described with respect to FIG. 11, if PUCCH overlap occurs in the first slot of a multi-slot PUSCH transmission and UCI is multiplied across the entire transmission occasion, the reference time S0 may be based on the start of the multi-slot PUSCH transmission 1504, as shown in FIG. 15.

[0130]

[0122] Thus, the reference time S0 at the start of the multi-slot PUSCH transmission 1504 may be applied for UCI that overlaps with the first slot of a transmission occasion, regardless of whether the UCI is multiplexed based on the first slot or across transmission occasions.

[0131]

[0123] Figure 16 shows a diagram 1600 illustrating aspects of timeline considerations for multiplexing UCI in a multi-slot PUSCH transmission. As shown in Figure 16, a UE may consider multiplexing UCI for a transmission in a PUCCH 1610 that overlaps in time with a transmission occasion for a multi-slot PUSCH 1604. In Figure 16, the PUCCH 1610 overlaps with the PUSCH 1604 in a subsequent slot of the multi-slot transmission occasion, e.g., at 1612, and is multiplexed in the overlapped slot, rather than in the first slot as in Figure 15. Figure 12 shows an example of UCI overlapping with a second slot of a multi-slot PUSCH transmission occasion 1202 and being multiplexed in the second slot.

[0132] In FIG. 16, when PUCCH 1610 overlap occurs in the second or subsequent slot of a multi-slot PUSCH transmission 1604 and UCI is multiplexed within that slot on a per transmission occasion basis, the reference time S 01 S may be determined by the start of a multi-slot PUSCH transmission, for example, as shown at 1611. In some aspects, S 01 may be applicable if rate matching and interleaving are performed for each transmission occasion. A single interleaver, S 01 and may be applied on a per transmission occasion basis.

[0133] In contrast, if a PUCCH 1610 overlap occurs in the second or subsequent slot of a multi-slot PUSCH transmission 1604 and UCI is multiplexed within that slot, the reference time S 02 S may be based on the slot of a multi-slot PUSCH transmission, for example as shown at 1611. 02 S may be applicable if rate matching and interleaving are performed on a slot-by-slot basis. 02In a timeline with ≠ 1604, a single interleaver may be applied per slot for multi-slot PUSCH transmission 1604.

[0134]

[0126] When PUCCH 1610 overlap occurs in the second or subsequent slot of a transmission occasion for a multi-slot PUSCH transmission 1604 and UCI is multiplexed across transmission occasions rather than slot by slot, the reference time is S 01 , which may be based on the start of the multi-slot PUSCH transmission 1604.

[0135]

[0127] As described with respect to FIG. 15, the time gap during which the DCI 1602 schedules the multi-slot PUSCH transmission 1604 may be sufficient for N2 symbols to transmit the PUSCH 1604, and the DCI 1606 scheduling the PDSCH 1608 in which the UE plans to transmit UCI in the PUCCH 1610 may be received before the DCI 1602 to multiplex the UCI with the PUSCH 1604.

[0136] FIG. 17 shows an example 1700 similar to FIG. 15 for UCI based on CSI-RS, such as aperiodic CSI-RS 1708 overlapping in time in the first symbol of a multi-slot PUSCH transmission 1704. The gap N2 between the DCI 1702 and the scheduled multi-slot PUSCH transmission 1704 may be the same as in FIG. 15. For a CSI report provided in a PUCCH 1710, a minimum gap (Z) may be measured between the last symbol of the CSI-RS 1708 and the start of the PUCCH 1710 carrying the CSI report. If the PUCCH 1710 is less than Z symbols from the last symbol of the CSI-RS, the UE may not multiplex the CSI report with the multi-slot PUSCH transmission 1704. If the time gap is at least Z symbols, the UE may multiplex the CSI report with the PUSCH 1704. For example, the additional aspects described with respect to FIG. 16 may also be implemented by, for example, subtracting the reference symbol S from the last symbol of the received CSI-RS. 02Up to 100% can be applied for UCI based on CSI.

[0137] 18 shows a diagram 1800 illustrating multiple PUCCHs (e.g., UCIs 1808, 1818, 1828, 1838, 1848, 1858, 1868) overlapping in various combinations with transmit occasions for multi-slot PUSCH transmissions. For example, transmit occasion 1802a overlaps with a PUCCH for UCI 1808 in slot 0 of the transmit occasion and overlaps with a PUCCH for UCI 1818 in slot 1 of the transmit occasion, e.g., a single UCI overlaps with different slots of transmit occasion 1802a. Transmit occasion 1802b has a single slot overlapped with multiple PUCCHs, e.g., for UCIs 1828 and 1838. Transmission occasion 1802c has an overlap of transmission occasion 1802c with UCIs 1848 and 1858 in one slot, and an overlap with UCI 1868 in another slot.

[0138]

[0130] When multiplexing multiple UCI for multiple PUCCHs in a single transmission occasion with multiple slots for PUSCH transmission, the UE may handle overlap on a slot-by-slot basis and may multiplex UCI with the PUSCH on a slot-by-slot basis.

[0139] In other aspects, when multiplexing multiple UCIs for multiple PUCCHs in a single transmission occasion with multiple slots for PUSCH transmission, the UE may handle overlap across transmission occasions. The UE may multiplex UCIs across transmission occasions even if the PUCCHs do not occur in the same slot of the transmission occasion, such as in the cases of UCIs 1808 and 1818, or UCIs 1848 and UCIs 1868. In some aspects, the UE may multiplex UCIs together.

[0140]

[0132] If overlapping UCI is handled per slot, the UE may multiplex UCI, whether it is a single UCI or multiple overlapping UCI in the corresponding slot of the overlapped transmission occasion. Figure 19 shows a diagram 1900 with arrows indicating the slots in which the UCI in Figure 18 is handled / multiplexed in a per slot example. The PUSCH may be rate matched per slot. Between slots, the UE may remember or store the starting position in the circular buffer. For example, the circular buffer 1950 in Figure 19 shows a point 1955 for the bits between slot 0 and slot 1. The PUSCH may be interleaved per slot, for example, as described with respect to Figure 7.

[0141]

[0133] When overlapping UCI are handled across transmission occasions, they may affect each other's multiplexing even if PUCCH does not occur in the same slot. The UE may determine the UCI resource for multiplexing purposes at the beginning of the transmission occasion. For timeline purposes, the UE may see the overlap in slot 1 before the beginning of the transmission occasion. For PUSCH handling, the UE may rate-match the PUSCH across the transmission occasion. The UE may interleave the PUSCH across the transmission occasion as described with respect to FIG. 6. FIG. 20 shows a diagram 2000 with arrows indicating that the UCI in FIG. 18 is handled per transmission occasion. The PUSCH may be rate-matched per slot. For example, the circular buffer 2050 in FIG. 20 shows an example of the application of a circular buffer for combined bits of a transmission occasion.

[0142]

[0134] Figure 21 shows a diagram 2100 illustrating aspects of timeline considerations for multiplexing multiple UCI in a multi-slot PUSCH transmission 2104. As shown in Figure 21, a UE may consider multiplexing UCI for transmissions in a PUCCH 2110 and / or 2120 that overlap in time with a transmission occasion for the multi-slot PUSCH 2104. In Figure 21, the PUCCH 2110 overlaps with the PUSCH 2104 in the first slot of the multi-slot transmission occasion, somewhat similar to Figure 15. The PUCCH 2120 overlaps with the PUSCH 2104 in a subsequent slot of the multi-slot transmission occasion, but not in the first slot. Both the PUCCH 2110 and the PUCCH 2120 are scheduled by the DCI 2106, which schedules the PDSCH 2108 and the DCI 2116, which schedules the PDSCH 2108 and the PDSCH 2118, and are received before the uplink grant 2102, which schedules the PUSCH 2104, and therefore meet their threshold for being multiplexed with the PUSCH 2104. In some aspects, the reference time is the start of the multi-slot PUSCH 2104 (e.g., S 01 For example, the UE may prepare in advance for a multi-slot PUSCH transmission and may be based on the criterion S 01 Based on the start of the multi-slot PUSCH 1604 as a time slot, timeline considerations may be applied for each of the multiple PUCCHs (2110 and 2120).

[0143] In some aspects, the criterion for multiplexing each PUCCH may be based on the slot of multiplexing. For example, each of the multiple PUCCHs may have an independent reference time based on the slot of multiplexing or based on other considerations discussed with respect to Figures 15-17 for the individual PUCCHs. For example, the reference time for PUCCH 2120 may be S 02 and the reference time for PUCCH 2110 may be S 01In some examples, the determination of the different reference times may be based on an interleaving and rate matching configuration. For example, an independent determination of the reference time per PUCCH may be applied when different PUCCHs are multiplexed per slot, e.g., with per-slot rate matching and / or per-slot interleaving, as described with respect to FIG. 19.

[0144] For example, as described with respect to FIG. 20, when multiplexing of multiple UCIs is handled across transmission occasions rather than slot by slot, the UE may assign S to each of the PUCCHs based on the start of the multi-slot PUSCH 2104. 01 A common reference time of 100 ms may be applied. The start of the PUSCH may be applied as the reference time since UCI multiplexing decisions may be made in a joint manner for different PUCCHs. The common reference time may enable the UE to prepare in advance for multi-slot PUSCH transmissions.

[0145]

[0137] Figure 22 shows a diagram 2200 illustrating PUCCH resources for UCI 2208 and 2209 overlapping transmission occasions 2202 and 2212, e.g., option (b) described with respect to Figure 4, including non-contiguous segments of resources. For example, transmission occasion 2202 includes segment 2205 and segment 2207, which are separated in time by resources not included in transmission occasion 2202. Segments 2205 and 2207 each include a contiguous set of resources. For example, segment 2205 is shown as having resources in a first slot 2204 and a second slot 2206. Each transmission occasion, e.g., 2202 and 2212, can be handled independently to multiplex UCI with PUSCH transmitted over multiple slots of one transmission occasion. Each transmission occasion can have an aspect corresponding to slot-by-slot handling of PUSCH and PUCCH. In some aspects, each successive segment within a transmission occasion may be handled independently from the other segment(s).

[0146] In some aspects, the UE may consider, e.g., handle or apply, multiplexing of PUCCH in overlapping slots rather than in non-overlapping slot(s). The multiplexing aspects in this example may be applied similarly to multiplexing in overlapping slots for consecutive transmission occasions, e.g., as described with respect to Examples 1 and 3 in Table 1 and Figures 10 and 12.

[0147] In some aspects, a UE may consider, e.g., handle or apply, multiplexing over an entire transmission occasion, e.g., 2202, including non-contiguous segments 2205 and 2207. The multiplexing aspects in this example may be applied similarly to multiplexing over transmission occasions for consecutive transmission occasions, e.g., as described with respect to Examples 2 and 4 in Table 1 and Figures 11 and 13.

[0148] In some aspects, a UE may consider, e.g., handle or apply, multiplexing on contiguous portions of a transmission occasion, e.g., within overlapping segments 2207 of a transmission occasion 2202. Table 2 illustrates an example aspect of handling UCI multiplexing with a multi-slot PUSCH per segment of a transmission occasion that includes non-contiguous segments of resources for UCI 2208.

[0149] [Table 3]

[0150] FIG. 23 shows a diagram 2300 illustrating UCI multiplexed based on overlapped segments of a discontinuous transmission occasion 2302. The transmission occasion includes discontinuous segments 2305 and 2307. Segment 2307 is overlapped in time with PUCCH for transmission of UCI 1908. Based on the overlap, UCI 2308 may be multiplexed with PUSCH TB for transmission in the transmission occasion. Multiplexing may be handled on a segment-by-segment basis, and multiplexing in segment 2307 is handled independently from the processing for segment 2305. Segment 2307 includes resources spanning two slots, e.g., slot 5 2304 and slot 6 2306. Resources for multiplexing UCI 2308 may be determined based on the segment into which PUCCH is multiplexed. UCI resources may be determined based on the resources of the segment.

[0151]

[0142] As an example, the number of resources for multiplexing UCI may be determined based on the number of REs potentially available for UCI across PUSCH symbols in a corresponding segment of a transmission occasion. The determination may also be based on the total number of PUSCH bits scaled by the number of symbols in the corresponding segment and the total number of PUSCH symbols. For example, in Equation 1,

[0152]

number

[0153] may correspond to the number of REs potentially available for UCI 2308 over the PUSCH symbols of a corresponding segment of a transmission occasion (e.g., segment 2307 of transmission occasion 2302), and

[0154]

number

[0155] may correspond to the total number of PUSCH bits for a transmission occasion 2302 scaled by the number of symbols in the corresponding segment divided by the total number of PUSCH symbols in the transmission occasion.

[0156] After determining the number of resources to use for UCI 2308 in slot 5 in FIG. 23, the UE may identify the location of the UCI resources in slot 5 2304. The UE may then fill the identified resources in slot 5 2304 with UCI symbols. The UE may fill the resources in a frequency-first, time-second manner. The UE may determine PUSCH rate matching bits using the remaining resources and may interleave the rate-matched bits. After interleaving, the UE may fill the identified resources for PUSCH with the interleaved bits mapped to modulation symbols.

[0157] FIG. 24 shows a diagram 2400 with two potential timelines for an overlapping PUCCH with a transmission occasion 2402 having discontinuous segments, for example based on option (b) described with respect to FIG. 4 and / or FIG. 23. The transmission occasion 2402 includes discontinuous segments 2405 and 2407. Each segment includes a contiguous set of resources, similar to the example in FIG. 23, for example, segment 2405 includes resources in slots 0 and 1, and segment 2407 includes resources in slots 5 and 6 of the set of slots spanned by the transmission occasion 2402. A multi-slot PUSCH transmission may be scheduled by DCI 2401 with an uplink grant, as described with respect to FIG. 15-17, and may have a processing timeline based on N2.

[0158] 24 shows two examples of potential timelines for a PUCCH 2410a or 2410b that overlap with a transmission occasion 2402 for a multi-slot PUSCH. The PUCCH may include UCI, such as an ACK / NACK for a PDSCH 2408a or 2408b, which may be scheduled by a downlink grant in a DCI 2406a or 2406b.

[0159] In the first timeline example, the reference time for measurement of N1 and / or Z when the UCI includes CSI may be based on the segment into which the PUCCH should be multiplexed. 01 The use of timeline 1 may be based on an interleaving and rate matching configuration for the PUSCH with multiplexed UCI, such as, for example, on a per segment basis or on a per slot basis.

[0160] In a second exemplary timeline, the reference time for the measurement of N1 and / or Z is, for example, S in FIG. 02 In some aspects, the reference time S may be based on the start of the multi-slot PUSCH, as shown by 02 may be applied by the UE regardless of how or where the UCI is to be multiplexed within the multi-slot PUSCH transmission. Using a reference time at the beginning of a multi-slot PUSCH transmission may provide the UE with additional time to prepare for the multi-slot PUSCH.

[0161] FIG. 25 illustrates an example communication flow 2500 between a UE 2502 and a base station 2504, including a transmission 2528 of UCI multiplexed with a multi-slot PUSCH transmission. As shown at 2506, the base station 2504 may transmit a DCI allocating or granting resources to the UE 2502 for a PUSCH transmission. The allocated resources may include transmission occasions spanning multiple slots, as described with respect to FIG. 4. At 2510, the UE may trigger multiplexing of the UCI with a multi-slot PUSCH transmission based on determining a time overlap between the PUCCH resources for the UCI and the transmission occasions for the PUSCH. As a non-limiting example to illustrate the concept, the UE may receive a downlink transmission 2508 with UCI for the UE to transmit to the base station 2504. The downlink transmission may include a PDSCH, which may be transmitted before or after the uplink grant at 2506. The UE may have ACK / NACK information for the PDSCH to transmit as UCI that overlaps with resources for the PUSCH. The PDSCH may be based on a DCI 2505 that schedules the PDSCH, which may be received before the DCI with the uplink grant at 2506. As another example, the downlink transmission 2508 may include CSI-RS and the UE may have CSI to report to the base station as UCI.

[0162] As part of determining to multiplex the UCI with a multi-slot PUSCH transmission, at 2510, the UE may apply a processing timeline. The processing timeline may be based on N1 and / or Z, as described with respect to any of Figures 15-17, 21, or 24. The UE may, for example, use a reference time (e.g., S0, S1, S2, S3, S4, S5, S6, S7, S8, S9, S10, S11, S12, S13, S14, S15, S16, S17, S18, S19, S20, S21, S22, S23, S24, S25, S26, S27, S28, S29, S30, S31, S32, S33, S34, S35, S36, S37, S38, S39, S40, S41, S42, S43, S44, S45, S46, S47, S48, S50, S51, S52, S53, S54, S55, S56, S57, S58, S59, S60, S61, S62, S63, S64, S65, S66, S67, S68, S69, S70, S71, S72, S73, S74, S75, S76, S77, S78, S80, S81, S82, S83, S84, S85, S86, S87, S88, S99, S90, S91, S91, S92, S93, S94, S95, S96, S97, S98, S99, S109, S109, S109, S109, S110, S120 01 , or S 02 ) may be applied.

[0163]

[0150] As shown in 2512, to multiplex UCI with PUSCH transmission, the UE may determine an amount of resources for UCI. The UE may determine the resources based on the type of transmission occasion (e.g., contiguous or non-contiguous segments as described with respect to FIG. 4). The UE may also determine the resources based on whether the multiplexing is handled per slot, per transmission occasion, or per segment of a transmission occasion. The UE may also determine the resources based on whether the overlap occurs in the first slot or in a subsequent slot of a transmission occasion or segment. The determination may be based on any of the aspects described with respect to FIGS. 10-14, 18-20, and / or 22-23. The determination may be based on a modified aspect of Equation 1 as described herein.

[0164]

[0151] At 2514, the UE may determine a location of resources for UCI within the PUSCH transmission occasion. At 2516, the UE may fill the identified resources with UCI symbols. In some aspects, the UE may fill the resources in a frequency-first, time-second manner. At 2520, the UE identifies remaining resources of the transmission occasion that are available for PUSCH transmission, e.g., remaining after filling a portion of the resources of the transmission occasion with UCI. At 2522, the UE applies rate matching and interleaving based on the remaining resources. The rate matching and interleaving may be based on any of the aspects described with respect to the examples in Figures 4-24. As an example, the interleaving may be per slot as in Figure 7, per transmission occasion as in Figure 6, or per segment as in Figure 8. The type of rate matching and interleaving may be based on the type of transmission occasion and the manner in which the UCI is multiplexed, as described herein. At 2524, the UE maps the interleaved bits to modulation symbols, and at 2526, the UE fills the remaining resources of the transmission occasion with a PUSCH transmission by mapping the modulation symbols mapped at 2524 to the remaining resources of the transmission occasion. At 2528, the UE 2502 transmits the PUSCH and multiplexed UCI to the base station 2504. As shown at 2530, the base station may demultiplex the UCI from the PUSCH to obtain information on the UCI.

[0165] 26A is a flowchart 2600 of a method of wireless communication. The method may be performed by a UE (e.g., a UE 104, 350, 2502, device 2702). The method may enable the UE to multiplex UCI within a transmission occasion for a multi-slot PUSCH and provides a processing timeline for the UE to multiplex UCI with a multi-slot PUSCH.

[0166] At 2602, the UE applies a processing timeline for multiplexing UCI in at least one slot of a multi-slot PUSCH transmission. FIG. 25 illustrates an example of the UE 2502 applying the processing timeline at 2511. The processing timeline may be based on any of the aspects described with respect to FIGS. 15-17, 21, and / or 24. The application of the timeline may be performed, for example, by a timeline component 2744 of the apparatus 2702 in FIG.

[0167] At 2604, the UE transmits a multi-slot PUSCH transmission with the multiplexed UCI based on the processing timeline being satisfied. The multiplexing and / or transmission may be based on any of the aspects described with respect to FIG. 4-FIG. 25. FIG. 25 illustrates an example of the UE 2502 transmitting a PUSCH with the multiplexed UCI to the base station 2504 at 2528. The transmission may be performed, for example, by the PUSCH component 2742 of the apparatus 2702, for example, via the transmitting component 2734 and / or the RF transceiver 2722.

[0168] 26B is a flowchart 2650 of a method of wireless communication. The method may be performed by a UE (e.g., a UE 104, 350, 2502, device 2702). The method may include 2602 and 2604 as described with respect to FIG. 26B.

[0169]

[0156] In some aspects, the UCI may comprise HARQ feedback and the processing timeline may correspond to a time gap (eg, N1) between reception of the PDSCH and the start of a PUCCH carrying a HARQ feedback payload for the PDSCH.

[0170]

[0157] In some aspects, the UCI may comprise a CSI report, and the processing timeline may correspond to a time gap (e.g., Z) between receipt of the last symbol of the CSI-RS and the start of a PUCCH carrying a CSI report based on measurements of the CSI-RS, e.g., as described with respect to FIG. 17.

[0171]

[0158] In some aspects, the UE may apply a processing timeline based on a start of a multi-slot PUSCH transmission, as shown at 2606. In some aspects, the multi-slot PUSCH transmission may be transmitted in a transmission occasion comprising a set of consecutive slots. In some aspects, the processing timeline is based on a start of a multi-slot PUSCH transmission based on one or more of: an overlapped slot of the multi-slot PUSCH transmission that overlaps in time with the UCI, a multiplexing slot in which the UCI should be multiplexed in the multi-slot PUSCH transmission, a transmission occasion-based multiplexing for the UCI within the multi-slot PUSCH transmission, a transmission occasion-based interleaving for the multi-slot PUSCH transmission, or a transmission occasion-based rate matching for the multi-slot PUSCH transmission. As an example, the timeline may be based on a start of a multi-slot PUSCH based on any of the aspects described with respect to Figures 15-17.

[0172]

[0159] In some aspects, the multi-slot PUSCH transmission may be transmitted in a transmission occasion comprising a set of consecutive slots, e.g., option (a) of FIG. 4, and, e.g., as shown at 2608, applying the processing timeline may include applying the processing timeline based on a start of an overlapping slot of the multi-slot PUSCH transmission that overlaps with the UCI and in which the UCI is multiplexed. In some aspects, the processing timeline may be based on a start of an overlapping slot of the multi-slot PUSCH transmission based on one or more of UCI being multiplexed in the overlapping slot of the multi-slot PUSCH transmission, slot-based multiplexing for UCI within the multi-slot PUSCH transmission, slot-based interleaving for the multi-slot PUSCH transmission, or slot-based rate matching for the multi-slot PUSCH transmission. 02 shows an example where the processing timeline is based on the start of overlapping slots.

[0173] In some aspects, the UE may multiplex UCI from multiple PUCCHs that overlap with a multi-slot PUSCH. For example, as described with respect to any of FIG. 18-FIG. 21, the UE may multiplex a first UCI and a second UCI that overlap with a multi-slot PUSCH transmission. The UE may, in 2602, perform a multiple-slot PUSCH multiplexing process, e.g., ... 01 A processing timeline may be applied for the first UCI and the second UCI based on the start of the multi-slot PUSCH transmission, as shown by:

[0174]

[0161] In some aspects, the first UCI and the second UCI may overlap in different slots of a transmission occasion, and the processing timeline may be, for example, S in FIG. 02The first UCI and the second UCI may be determined differently based on the respective slots of the transmission occasion overlapped by the first UCI and the second UCI, as shown by: In some aspects, the first UCI and the second UCI may be multiplexed across consecutive slots of the transmission occasion.

[0175] In some aspects, a multi-slot PUSCH transmission may be transmitted in a transmission occasion comprising a set of non-contiguous slots, e.g., option (b) in FIG. 4, and a processing timeline may be determined at 2610 based on contiguous portions of the transmission occasion in which the UCI is multiplexed. FIG. 24 illustrates an example of a processing timeline (e.g., timeline 1) based on a segment of overlap. The processing timeline may be determined, e.g., in S 01 In some aspects, the UE may multiplex a first UCI and a second UCI that overlap with different consecutive portions of a multi-slot PUSCH transmission, and the processing timeline may be based on the consecutive portions of the transmission occasions in which the respective UCIs are multiplexed.

[0176] At 2603, the UE multiplexes the UCI in at least one slot of the multi-slot PUSCH transmission. As described with respect to FIG. 25, the UE may determine to multiplex the UCI based on a resource on which the UCI should be transmitted overlapping in time with a transmission occasion for the PUSCH transmission. The multiplexing may include any of the aspects described with respect to FIG. 4-FIG. 25. The multiplexing may be performed, for example, by the UCI multiplexer component 2740 of the apparatus 2702 in FIG. 27.

[0177] FIG. 27 is a diagram 2700 illustrating an example of a hardware implementation for an apparatus 2702. The apparatus 2702 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 2702 may include a cellular baseband processor 2704 (also referred to as a modem) coupled to a cellular RF transceiver 2722. The apparatus 2702 may further include an application processor 2706 coupled to one or more subscriber identity module (SIM) cards 2720, a secure digital (SD) card 2708, and a screen 2710, a Bluetooth module 2712, a wireless local area network (WLAN) module 2714, a global positioning system (GPS) module 2716, and / or a power source 2718. The cellular baseband processor 2704 communicates with the UE 104 and / or base station 102 / 180 through the cellular RF transceiver 2722. The cellular baseband processor 2704 may include a computer readable medium / memory. The computer readable medium / memory may be non-transitory. The cellular baseband processor 2704 is responsible for general processing, including the execution of software stored in the computer readable medium / memory. The software, when executed by the cellular baseband processor 2704, causes the cellular baseband processor 2704 to perform various functions described herein. The computer readable medium / memory may also be used to store data that is manipulated by the cellular baseband processor 2704 when executing the software. The cellular baseband processor 2704 further includes a receiving component 2730, a communications manager 2732, and a transmitting component 2734. The communications manager 2732 includes one or more of the illustrated components. The components in the communications manager 2732 may be stored in the computer readable medium / memory and / or configured as hardware in the cellular baseband processor 2704.The cellular baseband processor 2704 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 2702 may be a modem chip and may include just the baseband processor 2704, and in another configuration, the apparatus 2702 may be an entire UE (e.g., see 350 in FIG. 3) and may include additional modules of the apparatus 2702.

[0178]

[0165] The communications manager 2732 includes a UCI multiplexer component 2740 configured to multiplex UCI in at least one slot of a multi-slot PUSCH transmission, e.g., as described with respect to 2603 in FIG. 26B. The communications manager 2732 further includes a PUSCH component 2742 configured to transmit a multi-slot PUSCH transmission with the multiplexed UCI based on a processing timeline being satisfied, e.g., as described with respect to 2604 in FIG. 26A or FIG. 26B. The communications manager 2732 further includes a timeline component 2744 configured to apply a processing timeline to multiplex UCI in at least one slot of a multi-slot PUSCH transmission, e.g., as described with respect to 2602 in FIG. 26A or FIG. 26B.

[0179]

[0166] The apparatus may include additional components that implement each of the blocks of the algorithms in the flowcharts of Figures 26A, 26B, and / or the aspects performed by the UE in Figure 25. Thus, each block in the flowcharts of Figures 26A, 26B, and / or the aspects performed by the UE in Figure 25 may be implemented by a component, and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to perform the described process / algorithm, implemented by a processor configured to perform the described process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0180]

[0167] In one configuration, the apparatus 2702, and in particular the cellular baseband processor 2704, includes means for applying a processing timeline to multiplex UCI in at least one slot of a multi-slot PUSCH transmission, and means for transmitting a multi-slot PUSCH transmission with the multiplexed UCI based on the processing timeline being satisfied. The apparatus may further include means for multiplexing UCI in at least one slot of a multi-slot PUSCH transmission. The means may be one or more of the components of the apparatus 2702 configured to perform the functions recited by the means. As described herein, the apparatus 2702 may include a TX processor 368, a RX processor 356, and a controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by the means.

[0181]

[0168] The deployment of a communication system, such as a 5G New Radio (NR) system, may be configured in multiple ways with various components or components. In a 5G NR system, or network, network equipment, such as a network node, a network entity, a mobility element of the network, a Radio Access Network (RAN) node, a core network node, a network element, or a base station (BS), or one or more units (or one or more components) performing a base station function, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), a NR BS, a 5G NB, an access point (AP), a transmit reception point (TRP), or a cell) may be implemented as an aggregated or disaggregated base station (also known as a standalone BS or a monolithic BS).

[0182]

[0169] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU or alternatively geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0183]

[0170] Base station type operation or network design may take into account the aggregation characteristics of base station functions. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration sponsored by the O-RAN alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functions across two or more units in various physical locations, as well as virtually distributing functions for at least one unit, which may allow flexibility in network design. Various units of a disaggregated base station, or a disaggregated RAN architecture, may be configured for wired or wireless communication with at least one other unit.

[0184]

[0171] Figure 28 shows a diagram illustrating an example disaggregated base station 2800 architecture. The disaggregated base station 2800 architecture may include one or more central units (CUs) 2810 that may communicate directly with the core network 2820 via a backhaul link or indirectly with the core network 2820 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 2825 via an E2 link, or a non-real-time (non-RT) RIC 2815 associated with a Service Management and Orchestration (SMO) framework 2805, or both). The CUs 2810 may communicate with one or more distributed units (DUs) 2830 via respective midhaul links, such as an F1 interface. The DUs 2830 may communicate with one or more radio units (RUs) 2840 via respective fronthaul links. The RUs 2840 may communicate with each UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served by multiple RUs 2840 simultaneously.

[0185] Each of the units, i.e., CU2810, DU2830, RU2840, as well as near-RT RIC2825, non-RT RIC2815 and SMO framework2805, may include or be coupled to one or more interfaces configured to receive or transmit signals, data or information (collectively, signals) over a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the communication interfaces of the units, may be configured to communicate with one or more of the other units over a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally, a unit may include a wireless interface, which may include a receiver, a transmitter or a transceiver (such as a radio frequency (RF) transceiver) configured to receive and / or transmit signals over a wireless transmission medium to one or more of the other units.

[0186] In some aspects, the CU 2810 may host one or more upper layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), and the like. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 2810. The CU 2810 may be configured to handle user plane functions (i.e., Central Unit-User Plane (CU-UP)), control plane functions (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 2810 may be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP units, when implemented in an O-RAN configuration, may communicate bidirectionally with the CU-CP units via an interface, such as an E1 interface. The CU 2810 may be implemented to communicate with the DU 2830 for network control and signaling, as needed.

[0187]

[0174] The DU 2830 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 2840. In some aspects, the DU 2830 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split, such as that defined by the 3rd Generation Partnership Project (3GPP). In some aspects, the DU 2830 may further host one or more low PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 2830 or with control functions hosted by the CU 2810.

[0188]

[0175] The lower layer functions may be implemented by one or more RUs 2840. In some deployments, the RUs 2840, controlled by the DUs 2830, may correspond to logical nodes hosting RF processing functions, or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split, such as a lower layer functional split. In such an architecture, the RU(s) 2840 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU(s) 2840 may be controlled by the corresponding DUs 2830. In some scenarios, this configuration may enable the DU(s) 2830 and the CU 2810 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0189]

[0176] The SMO framework 2805 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 2805 may be configured to support deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 2805 may be configured to interact with a cloud computing platform (such as an open cloud (O-cloud) 2890) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, a CU 2810, a DU 2830, a RU 2840, and a near-RT RIC 2825. In some implementations, the SMO framework 2805 may communicate with hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 2811, via an O1 interface. Additionally, in some implementations, the SMO framework 2805 can communicate directly with one or more RUs 2840 via an O1 interface. The SMO framework 2805 may also include a non-RT RIC 2815 configured to support the functionality of the SMO framework 2805.

[0190]

[0177] The non-RT RIC 2815 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the near-RT RIC 2825. The non-RT RIC 2815 may be coupled to or communicate with the near-RT RIC 2825 (such as via an A1 interface). The near-RT RIC 2825 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and action on interfaces (such as via an E2 interface) that connect one or more CUs 2810, one or more DUs 2830, or both, and the O-eNB with the near-RT RIC 2825.

[0191] In some implementations, the non-RT RIC 2815 may receive parameters or external enrichment information from an external server to generate an AI / ML model to be deployed in the near-RT RIC 2825. Such information may be utilized by the near-RT RIC 2825 and may be received in the SMO framework 2805 or the non-RT RIC 2815 from a non-network data source or from a network function. In some examples, the non-RT RIC 2815 or the near-RT RIC 2825 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 2815 may monitor long-term trends and patterns in performance and employ the AI / ML model to take corrective action through the SMO framework 2805 (such as reconfiguration via O1) or via creation of a RAN management policy (such as an A1 policy).

[0192]

[0179] It should be understood that the particular order or hierarchy of the blocks in the disclosed processes / flowcharts is an example of an example approach. Based on design preferences, it should be understood that the particular order or hierarchy of the blocks in the processes / flowcharts may be rearranged. Additionally, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in an example order, and are not limited to the particular order or hierarchy presented.

[0193]

[0180] The above description is provided to enable those 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 general principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects set forth herein, but are to be accorded the full scope consistent with the claim language, in which reference to an element in the singular does not mean "one and only," unless so expressly stated, but rather means "one or more." Terms such as "if," "when," and "while" should be construed to mean "under the condition that," rather than implying an immediate time relationship or reaction. That is, these phrases, for example, "when," do not imply an immediate action in response to or during the occurrence of an action, but merely imply that if a condition is met, an action occurs, but does not require a specific or immediate time constraint 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" should not necessarily be construed as preferred or advantageous over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple As, multiple Bs, or multiple Cs.In particular, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements of the various embodiments described throughout this disclosure that are known or that later become known to those of skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is made public, regardless of whether such disclosure is expressly recited in the claims. The words "module," "mechanism," "element," "device," and the like may not be substitutes for the word "means." Therefore, no claim element should be construed as a means-plus-function unless the element is expressly recited using the phrase "means for."

[0194]

[0181] The following aspects are illustrative only and can be combined with, but not limited to, other aspects or teachings described herein.

[0195]

[0182] Aspect 1 is a method of wireless communication in a UE, comprising: applying a processing timeline to multiplex UCI in at least one slot of a multi-slot PUSCH transmission; and transmitting the multi-slot PUSCH transmission with the multiplexed UCI based on the processing timeline being satisfied.

[0196]

[0183] In aspect 2, the method described in aspect 1 further includes that the UCI comprises HARQ feedback, and the processing timeline corresponds to a time gap between reception of the PDSCH and a start of a PUCCH carrying a HARQ feedback payload for the PDSCH.

[0197]

[0184] In aspect 3, the method described in aspect 1 further includes that the UCI comprises a CSI report, and the processing timeline corresponds to a time gap between reception of the last symbol of the CSI-RS and a start of a PUCCH carrying a CSI report based on measurements of the CSI-RS.

[0198]

[0185] In aspect 4, the method of any of aspects 1 to 3 further includes applying the processing timeline includes applying the processing timeline based on a start of a multi-slot PUSCH transmission.

[0199]

[0186] In example 5, the method of any of examples 1 to 4 further includes the multi-slot PUSCH transmission being transmitted in a transmission occasion comprising a set of consecutive slots.

[0200]

[0187] In aspect 6, the method of any of aspects 1 to 5 further includes the processing timeline being based on initiation of the multi-slot PUSCH transmission based on one or more of: an overlapped slot of the multi-slot PUSCH transmission that overlaps in time with the UCI, a multiplexing slot in the multi-slot PUSCH transmission in which the UCI should be multiplexed, transmit occasion-based multiplexing for the UCI within the multi-slot PUSCH transmission, transmit occasion-based interleaving for the multi-slot PUSCH transmission, or transmit occasion-based rate matching for the multi-slot PUSCH transmission.

[0201]

[0188] In aspect 7, the method of any of aspects 1 to 5 further includes, the processing timeline being based on the start of the overlapped slots of the multi-slot PUSCH transmission based on one or more of: UCI being multiplexed in the overlapped slots of the multi-slot PUSCH transmission, slot-based multiplexing for UCI within the multi-slot PUSCH transmission, slot-based interleaving for the multi-slot PUSCH transmission, or slot-based rate matching for the multi-slot PUSCH transmission.

[0202]

[0189] In aspect 8, the method described in any of aspects 1 to 7 further includes, wherein multiplexing the UCI includes multiplexing a first UCI and a second UCI that overlap with a multi-slot PUSCH transmission.

[0203]

[0190] In aspect 9, the method of aspect 8 further includes applying a processing timeline for the first UCI and the second UCI based on a start of the multi-slot PUSCH transmission.

[0204]

[0191] In aspect 10, the method described in aspect 8 further includes, wherein the first UCI and the second UCI overlap in different slots of a transmission occasion, and the processing timeline is determined differently for the first UCI and the second UCI based on the respective slots of the transmission occasion overlapped by the first UCI and the second UCI.

[0205]

[0192] In aspect 11, the method described in any of aspects 1 to 3 further includes, in which the multi-slot PUSCH transmission is transmitted in a transmission occasion having a set of discontinuous slots, and in which the processing timeline is determined based on consecutive portions of the transmission occasion in which the UCI is multiplexed.

[0206]

[0193] In aspect 12, the method of aspect 11 further includes the processing timeline being based on a start of the consecutive portion.

[0207]

[0194] In aspect 13, the method described in aspect 11 or aspect 12 further includes multiplexing the first UCI and the second UCI that overlap with different consecutive portions of a multi-slot PUSCH transmission, wherein the processing timeline is determined based on consecutive portions of the transmission occasions in which the respective UCIs are multiplexed.

[0208]

[0195] Aspect 14 is an apparatus for wireless communication in a user equipment UE, comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: apply a processing timeline to multiplex UCI in at least one slot of a multi-slot PUSCH transmission; and transmit the multi-slot PUSCH transmission with the multiplexed UCI based on the processing timeline being satisfied.

[0209]

[0196] In aspect 15, the apparatus for wireless communication as described in aspect 14 includes a memory and at least one processor further configured to perform a method as described in any of aspects 2 to 13.

[0210]

[0197] In aspect 16, the apparatus of any of aspects 14 or 15 further includes at least one transceiver coupled to the at least one processor.

[0211]

[0198] In aspect 17, the apparatus of any of aspects 14-16 further includes at least one antenna coupled to the at least one processor.

[0212]

[0199] Aspect 18 is an apparatus for wireless communication in a UE, comprising: means for applying a processing timeline to multiplex UCI in at least one slot of a multi-slot PUSCH transmission; and means for transmitting a multi-slot PUSCH transmission with the multiplexed UCI based on the processing timeline being satisfied.

[0213]

[0200] In aspect 19, the apparatus for wireless communication as defined in aspect 18 further comprises means for performing the method as defined in any of claims 2 to 13.

[0214]

[0201] In aspect 20, the apparatus described in any of aspects 18 or 19 further includes at least one transceiver.

[0215]

[0202] In aspect 21, the device described in any of aspects 18 to 20 further includes at least one antenna.

[0216]

[0203] Aspect 22 is a non-transitory computer-readable medium storing computer-executable code in a UE, the code which, when executed by a processor, causes the processor to apply a processing timeline to multiplex UCI in at least one slot of a multi-slot PUSCH transmission, and, based on the processing timeline being satisfied, transmit a multi-slot PUSCH transmission with the multiplexed UCI.

[0217]

[0204] In aspect 23, the computer-readable medium according to aspect 22 further comprises code which, when executed by a processor, causes the processor to perform a method according to any of claims 2 to 13.

Claims

1. 1. A method of wireless communication in a user equipment (UE), comprising: in response to determining that a start of a multi-slot physical uplink shared channel (PUSCH) transmission will exceed a processing timeline, multiplexing uplink control information (UCI) in at least one slot of the multi-slot PUSCH transmission; Transmitting the multi-slot PUSCH transmission with multiplexed UCI. A method comprising:

2. 2. The method of claim 1, wherein the UCI comprises Hybrid Automatic Repeat Request (HARQ) feedback, and the processing timeline corresponds to a time gap between reception of a Physical Downlink Shared Channel (PDSCH) and a start of a Physical Uplink Control Channel (PUCCH) carrying a HARQ feedback payload for the PDSCH.

3. 2. The method of claim 1, wherein the UCI comprises a channel state information (CSI) report, and the processing timeline corresponds to a time gap between receipt of a last symbol of a channel state information reference signal (CSI-RS) and a start of a physical uplink control channel (PUCCH) carrying the CSI report based on measurements of the CSI-RS.

4. The method of claim 1 , wherein the multi-slot PUSCH transmission is transmitted in a transmission occasion comprising a set of consecutive slots.

5. The processing timeline includes: an overlapped slot of the multi-slot PUSCH transmission that overlaps in time with the UCI; a multiplexing slot in which the UCI should be multiplexed in the multi-slot PUSCH transmission; transmission occasion based multiplexing of the UCI within the multi-slot PUSCH transmission; transmission occasion based interleaving of the multi-slot PUSCH transmission; or Transmission occasion-based rate matching for the multi-slot PUSCH transmission 5. The method of claim 4, further comprising: based on the initiation of the multi-slot PUSCH transmission based on one or more of:

6. The processing timeline includes: the UCI is multiplexed in overlapping slots of the multi-slot PUSCH transmission; Slot-based multiplexing of the UCI within the multi-slot PUSCH transmission; Slot-based interleaving of the multi-slot PUSCH transmission; or Slot-based rate matching for the multi-slot PUSCH transmission 5. The method of claim 4, further comprising: based on the start of the overlapped slots of the multi-slot PUSCH transmission based on one or more of:

7. Multiplexing the UCI multiplexing a first UCI and a second UCI that overlap with the multi-slot PUSCH transmission; The method of claim 1 , comprising:

8. 8. The method of claim 7, wherein the first UCI and the second UCI overlap in different slots of a transmission occasion, and the processing timeline is determined differently for the first UCI and the second UCI based on respective slots of the transmission occasion overlapped by the first UCI and the second UCI.

9. 2. The method of claim 1, wherein the multi-slot PUSCH transmission is transmitted in a transmission occasion comprising a set of discontinuous slots, and wherein the processing timeline is determined based on a contiguous portion of the transmission occasion into which the UCI is multiplexed.

10. The method of claim 9 , wherein the processing timeline is based on a start of the successive portions.

11. multiplexing a first UCI and a second UCI that overlap different consecutive portions of the multi-slot PUSCH transmission; 10. The method of claim 9, further comprising: wherein the processing timeline is determined based on the successive portions of the transmission occasions in which respective UCI are multiplexed.

12. An apparatus for wireless communication in a user equipment (UE), comprising: Memory, at least one processor coupled to the memory; wherein the at least one processor: in response to determining that a start of a multi-slot physical uplink shared channel (PUSCH) transmission will exceed a processing timeline, multiplexing uplink control information (UCI) in at least one slot of the multi-slot PUSCH transmission; Transmitting the multi-slot PUSCH transmission with multiplexed UCI. An apparatus configured to:

13. An apparatus for wireless communication in a user equipment (UE), comprising: means for multiplexing uplink control information (UCI) in at least one slot of a multi-slot physical uplink shared channel (PUSCH) transmission in response to determining that a start of the multi-slot PUSCH transmission will exceed a processing timeline; means for transmitting the multi-slot PUSCH transmission with multiplexed UCI; An apparatus comprising:

14. A non-transitory computer readable medium storing computer executable code in a user equipment (UE), the code, when executed by a processor, causing the processor to: in response to determining that a start of a multi-slot physical uplink shared channel (PUSCH) transmission will exceed a processing timeline, multiplexing uplink control information (UCI) in at least one slot of the multi-slot PUSCH transmission; Transmitting the multi-slot PUSCH transmission with multiplexed UCI. A non-transitory computer-readable medium for causing

Images