CN117044153A - Time line for multiplexing uplink control information on multislot transmission - Google Patents

Abstract

A method, computer-readable medium, and apparatus for wireless communication are provided. The apparatus applies a processing timeline to multiplex Uplink Control Information (UCI) in at least one slot of a multi-slot Physical Uplink Shared Channel (PUSCH) transmission. The apparatus transmits the multislot PUSCH transmission and the multiplexed UCI based on satisfying the processing timeline.

Description

Time line for multiplexing uplink control information on multislot transmission

Cross Reference to Related Applications

The present application claims the benefits and priorities of U.S. provisional application S/n.63/166,961 entitled "Timelines for Uplink Control Information Multiplexing Over Multiple Slot Transmissions (time line for uplink control information multiplexing over multislot transmission)" filed on day 26 of 2021, and U.S. non-provisional application S/n.17/656,209 entitled "Timelines for Uplink Control Information Multiplexing Over Multiple Slot Transmissions (time line for uplink control information multiplexing over multislot transmission)" filed on day 23 of 2022, both of which are expressly incorporated herein by reference in their entirety.

Technical Field

The present disclosure relates generally to communication systems, and more particularly, to wireless communication including Uplink Control Information (UCI).

Introduction to the invention

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple-access techniques capable of supporting communication with multiple users by sharing the available system resources. Examples of such multiple-access techniques include Code Division Multiple Access (CDMA) systems, time Division Multiple Access (TDMA) systems, frequency Division Multiple Access (FDMA) systems, orthogonal Frequency Division Multiple Access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division-synchronous code division multiple access (TD-SCDMA) systems.

These multiple access techniques have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). The 5G NR is part of the continuous mobile broadband evolution promulgated by the third generation partnership project (3 GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the internet of things (IoT)) and other requirements. The 5G NR includes services associated with enhanced mobile broadband (emmbb), large-scale machine type communication (emtc), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements in 5G NR technology. These improvements are also applicable to other multiple access techniques and telecommunication standards employing these techniques.

Brief summary of the invention

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

In an aspect of the disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus applies a processing timeline to multiplex Uplink Control Information (UCI) in at least one slot of a multi-slot physical uplink shared channel (PUCCH) transmission. The apparatus transmits the multislot PUSCH transmission and the multiplexed UCI based on satisfying the processing timeline.

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 various aspects may be employed and the present description is intended to include all such aspects and their equivalents.

Brief Description of Drawings

Fig. 1 is a diagram illustrating an example of a wireless communication system and an access network in accordance with various aspects of the present disclosure.

Fig. 2A is a diagram illustrating an example of a first frame in accordance with aspects of the present disclosure.

Fig. 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

Fig. 2C is a diagram illustrating an example of a second frame in accordance with aspects of the present disclosure.

Fig. 2D is a diagram illustrating an example of UL channels within a subframe in accordance with various aspects of the present disclosure.

Fig. 3 is a diagram illustrating an example of a base station and a User Equipment (UE) in an access network in accordance with various aspects of the disclosure.

Fig. 4 illustrates diagrams showing various options for transmission occasions for a multi-slot PUSCH transmission, in accordance with various aspects of the present disclosure.

Fig. 5A and 5B illustrate example aspects of Redundancy Version (RV) loops for multiple transmission opportunities for a multi-slot PUSCH in accordance with various aspects of the present disclosure.

Fig. 6 illustrates example aspects of transmission opportunity based interleaving for multi-slot PUSCH transmissions in accordance with various aspects of the disclosure.

Fig. 7 illustrates example aspects of slot-based interleaving for multi-slot PUSCH transmissions in accordance with various aspects of the present disclosure.

Fig. 8 illustrates example aspects of segment-based interleaving for multi-slot PUSCH transmissions in a transmission occasion with non-contiguous resource segments, in accordance with various aspects of the disclosure.

Fig. 9 illustrates an example of a UCI overlapping in time with a transmission occasion for a multi-slot PUSCH transmission with contiguous resources, according to aspects of the present disclosure.

Fig. 10 illustrates an example of multiplexing UCI in overlapping time slots of a transmission occasion for a multi-slot PUSCH transmission, the transmission occasion having contiguous resources, in accordance with aspects of the present disclosure.

Fig. 11 illustrates an example of multiplexing UCI across a transmission opportunity for multi-slot PUSCH transmission, the transmission opportunity having contiguous resources, in accordance with aspects of the present disclosure.

Fig. 12 illustrates an example of multiplexing UCI in overlapping time slots of a transmission occasion for a multi-slot PUSCH transmission, the transmission occasion having contiguous resources, in accordance with aspects of the present disclosure.

Fig. 13 illustrates an example of multiplexing UCI on a transmission occasion for a multi-slot PUSCH transmission with contiguous resources, in accordance with aspects of the present disclosure.

Fig. 14 illustrates an example of multiplexing repetitions of UCI in a transmission occasion for a multi-slot PUSCH transmission with contiguous resources, in accordance with various aspects of the disclosure.

Fig. 15 illustrates example processing timeline considerations for multiplexing UCI with a multislot PUSCH transmission in accordance with aspects of the present disclosure.

Fig. 16 illustrates example processing timeline considerations for multiplexing UCI with a multislot PUSCH transmission in accordance with aspects of the present disclosure.

Fig. 17 illustrates example processing timeline considerations for multiplexing UCI with a multislot PUSCH transmission in accordance with aspects of the present disclosure.

Fig. 18 illustrates an example where multiple UCI overlaps with a transmission occasion for a multi-slot PUSCH transmission with contiguous resources, in accordance with aspects of the present disclosure.

Fig. 19 illustrates an example of multiplexing multiple UCI overlapping transmission opportunities for a multi-slot PUSCH transmission on an overlapping slot basis in accordance with aspects of the present disclosure.

Fig. 20 illustrates an example of multiplexing multiple UCI overlapping with a transmission occasion for a multislot PUSCH transmission on a transmission occasion basis in accordance with aspects of the present disclosure.

Fig. 21 illustrates example processing timeline considerations for multiplexing UCI from multiple PUCCHs with a multislot PUSCH transmission in accordance with aspects of the present disclosure.

Fig. 22 illustrates an example of a UCI overlapping in time with a transmission occasion for a multi-slot PUSCH transmission with non-contiguous resource segments, according to aspects of the present disclosure.

Fig. 23 illustrates an example of multiplexing UCI overlapping with a transmission occasion for a multi-slot PUSCH transmission on a segment basis, the transmission occasion having non-contiguous resource segments, in accordance with various aspects of the disclosure.

Fig. 24 illustrates example processing timeline considerations for multiplexing UCI with a multislot PUSCH transmission in a transmission occasion with non-contiguous segments, in accordance with aspects of the present disclosure.

Fig. 25 is an example communication flow between a UE and a base station including an application of a processing timeline for multiplexing with multi-slot PUSCH transmissions in accordance with various aspects of the disclosure.

Fig. 26A and 26B are flowcharts of wireless communication methods including applying a processing timeline for multiplexing with multi-slot PUSCH transmissions in accordance with various aspects of the present disclosure.

Fig. 27 is a diagram illustrating an example of a hardware implementation for an example device in accordance with aspects of the present disclosure.

Fig. 28 is a diagram illustrating an example split base station architecture.

Detailed Description

The UE may transmit PUSCH on a transmission occasion spanning multiple slots. The UE may transmit a single TB in multiple slots of a transmission opportunity. Sometimes, the 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 PUSCH. Based on the time overlap, the UE may multiplex UCI with PUSCH. Aspects presented herein provide various ways for a UE to multiplex UCI with a multislot PUSCH. Multiplexing aspects (including any combination of number of resources for UCI, location of UCI, handling of multiplexing, timeline, rate matching of PUSCH, and/or interleaving of PUSCH) may differ based on the type of transmission occasion (e.g., contiguous or non-contiguous). The multiplexing aspects may differ based on overlapping time slots of PUSCH transmission occasions. Multiplexing aspects may differ based on the type of PUSCH treatment (e.g., per slot, per transmission occasion, or per segment interlace and RV cycle).

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

Several aspects of the telecommunications system will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

As an example, an element, or any portion of an element, or any combination of elements, may be implemented as a "processing system" that includes one or more processors. Examples of processors include: microprocessors, microcontrollers, graphics Processing Units (GPUs), central Processing Units (CPUs), application processors, digital Signal Processors (DSPs), reduced Instruction Set Computing (RISC) processors, system on a chip (SoC), baseband processors, field Programmable Gate Arrays (FPGAs), programmable Logic Devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in the processing system may execute the software. Software should be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subroutines, software components, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether described in software, firmware, middleware, microcode, hardware description language, or other terminology.

Accordingly, in one or more example embodiments, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded on a computer-readable medium as one or more instructions or code. Computer readable media includes computer storage media. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise Random Access Memory (RAM), read-only memory (ROM), electrically Erasable Programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

While aspects and implementations are described in this disclosure by way of illustration of some examples, those skilled in the art will appreciate that additional implementations and use cases may be produced in many different arrangements and scenarios. Aspects described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, implementations and/or uses may be generated via integrated chip implementations and other non-module component-based devices (e.g., end user devices, vehicles, communication devices, computing devices, industrial equipment, retail/shopping devices, medical devices, artificial Intelligence (AI) enabled devices, etc.). While some examples may or may not be specific to each use case or application, broad applicability of the described aspects may occur. Implementations may range from chip-level or module components to non-module, non-chip-level implementations, and further to aggregated, distributed, or Original Equipment Manufacturer (OEM) devices or systems incorporating one or more of the described aspects. In some practical environments, 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, the transmission and reception of wireless signals must include several components (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders/summers, etc.) for analog and digital purposes. The aspects described herein are intended to be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disassembled components, end-user devices, and the like, of various sizes, shapes, and configurations.

Fig. 1 is a diagram illustrating an example of a wireless communication system including a base station 102 or 180 and a UE 104 and an access network 100. As described herein, the UE 104 may include a UCI multiplexer component 198. In some aspects, UCI multiplexer component 198 may be configured to: the timeline is applied to multiplex UCI in at least one slot of a multi-slot PUSCH transmission. The UE 104 may be configured to: the multi-slot PUSCH transmission and the multiplexed UCI are transmitted based on satisfying a processing timeline. Base station 102 or 180 or a component of a 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 multislot PUSCH transmission. In some aspects, multiplexed UCI receiving component 199 may be configured to: a multi-slot PUSCH transmission is received based on a processing timeline for UCI multiplexing, the multi-slot PUSCH transmission including UCI multiplexed in at least one slot of the multi-slot PUSCH transmission. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

A wireless communication system, also known as a Wireless Wide Area Network (WWAN), includes a base station 102, a UE 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G core (5 GC)). Base station 102 may include macro cells (high power cell base stations) and/or small cells (low power cell base stations). The macrocell includes a base station. Small cells include femtocells, picocells, and microcells.

A base station 102 configured for 4G LTE, collectively referred to as an 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 a next generation RAN (NG-RAN), may interface with a core network 190 over a second backhaul link 184. Among other functions, the base station 102 may perform one or more of the following functions: user data delivery, radio channel ciphering and ciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio Access Network (RAN) sharing, multimedia Broadcast Multicast Services (MBMS), subscriber and equipment tracking, RAN Information Management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC 160 or the core network 190) over a third backhaul link 134 (e.g., an X2 interface). The first backhaul link 132, the second backhaul link 184 (e.g., an Xn interface), and the third backhaul link 134 may be wired or wireless.

In some aspects, the base station 102 or 180 may be referred to as a RAN and may include aggregated or disassembled components. As an example of a split RAN, a 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 illustrated in fig. 1. The RAN may be broken up with a split between RU 109 and the aggregated CUs/DUs. The RAN may be broken up with a split between CU 106, DU 105 and RU 109. The RAN may be broken up with a split between CU 106 and the aggregated DU/RU. CU 106 and one or more DUs 105 may be connected via an F1 interface. The DU 105 and RU 109 may be connected via an outbound interface. The connection between CU 106 and DU 105 may be referred to as mid-range (midhaul), while the connection between DU 105 and RU 109 may be referred to as out-range (fronthaul). The connection between the CU 106 and the core network may be referred to as backhaul. The RAN may be based on a functional partitioning between various components of the RAN (e.g., between CUs 106, DUs 105, or RUs 109). A CU may be configured to perform one or more aspects of the wireless communication protocol (e.g., to handle one or more layers of the protocol stack), and DU(s) may be configured to handle other aspects of the wireless communication protocol (e.g., other layers of the protocol stack). In different implementations, the splitting between the layers handled by the CU and the layers handled by the DU may occur at different layers of the protocol stack. As one non-limiting example, the DU 105 may provide a logical node to host at least a portion of a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer based on the functional split. An RU may provide a logical node configured to host at least a portion of a PHY layer and Radio Frequency (RF) processing. CU 106 may host higher layer functions (e.g., above the RLC layer), such as a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer. In other implementations, the split between layer functions provided by a CU, DU, or RU may be different.

The access network may include one or more Integrated Access and Backhaul (IAB) nodes 111, the one or more IAB nodes 111 exchanging wireless communications with UEs 104 or other IAB nodes 111 to provide access and backhaul to the core network. In an IAB network of multiple IAB nodes, the anchor node may be referred to as an IAB donor. The IAB donor may be a base station 102 or 180 that provides access to the core network 190 or EPC 160 and/or control of one or more IAB nodes 111. The IAB donor may include CU 106 and DU 105. The IAB node 111 may include a DU 105 and a Mobile Terminal (MT). The DU 105 of the IAB node 111 may operate as a parent node and the MT may operate as a child node.

The base station 102 may be in wireless communication with the UE 104. Each base station 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102 'may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network comprising both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a home evolved node B (eNB) (HeNB) that may provide services to a restricted group known as a Closed Subscriber Group (CSG). The communication link 120 between the base station 102 and the UE 104 may include Uplink (UL) (also known as reverse link) transmissions from the UE 104 to the base station 102 and/or Downlink (DL) (also known as forward link) transmissions from the base station 102 to the UE 104. Communication link 120 may use multiple-input multiple-output (MIMO) antenna techniques including spatial multiplexing, beamforming, and/or transmit diversity. These communication links may be through one or more carriers. For each carrier allocated in carrier aggregation up to yxmhz (x component carriers) in total for transmission in each direction, the base station 102/UE 104 may use a spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400MHz, etc.) bandwidth. These carriers may or may not be contiguous with each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL than UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL WWAN spectrum. The D2D communication link 158 may use one or more side link channels such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and a physical side link control channel (PSCCH). D2D communication may be through a variety of wireless D2D communication systems such as, for example, wiMedia, bluetooth, zigBee, wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

The wireless communication system may 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 a 5GHz unlicensed spectrum or the like. When communicating in the unlicensed spectrum, the STA 152/AP 150 may perform a Clear Channel Assessment (CCA) prior to communication to determine whether the channel is available.

The small cell 102' may operate in licensed and/or unlicensed spectrum. When operating in unlicensed spectrum, the small cell 102' may employ NR and use the same unlicensed spectrum (e.g., 5GHz, etc.) as used by the Wi-Fi AP 150. Small cells 102' employing NR in the unlicensed spectrum may push up access network coverage and/or increase access network capacity.

The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency/wavelength. In 5G NR, two initial operating bands have been identified as frequency range designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. Similar naming problems sometimes occur with respect to FR2, which is commonly (interchangeably) referred to as the "millimeter wave" band in various documents and articles, although it is different from the Extremely High Frequency (EHF) band (30 GHz-300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" band.

The frequency between FR1 and FR2 is commonly referred to as the mid-band frequency. Recent 5G NR studies have identified the operating band of these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). The frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics and thus may effectively extend the characteristics of FR1 and/or FR2 into mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation above 52.6 GHz. For example, three higher operating bands have been identified as frequency range designation FR2-2 (52.6 GHz-71 GHz), FR4 (71 GHz-114.25 GHz) and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF frequency band.

In view of the above, unless specifically stated otherwise, it is to be understood that, if used herein, the term "sub-6 GHz" or the like may broadly represent frequencies that may be less than 6GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless specifically stated otherwise, it should be understood that, if used herein, the term "millimeter wave" or the like may broadly mean frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2 and/or FR5, or may be within the EHF band.

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

The base station 180 may transmit the beamformed signals to the UE 104 in one or more transmit directions 182'. The UE 104 may receive the beamformed signals from the base station 180 in one or more receive directions 182 ". The UE 104 may also transmit the beamformed signals in one or more transmit directions to the base station 180. The base station 180 may receive the beamformed signals from the UEs 104 in one or more receive directions. The base stations 180/UEs 104 may perform beam training to determine the best receive direction and transmit direction for each of the base stations 180/UEs 104. The transmit direction and the receive direction of the base station 180 may be the same or may be different. The transmit direction and the receive direction of the UE 104 may be the same or may be different.

EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a serving gateway 166, a Multimedia Broadcast Multicast Service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a Packet Data Network (PDN) gateway 172.MME 162 may 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. Generally, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are communicated through the serving gateway 166, which serving gateway 166 itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation as well as other functions. The PDN gateway 172 and BM-SC 170 are connected to an IP service 176.IP services 176 may include the internet, intranets, IP Multimedia Subsystem (IMS), PS streaming services, and/or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may be used as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

The core network 190 may include access and mobility management functions (AMFs) 192, other AMFs 193, session Management Functions (SMFs) 194, and User Plane Functions (UPFs) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. In general, AMF 192 provides QoS flows and session management. All user Internet Protocol (IP) packets are delivered through UPF 195. The UPF 195 provides UE IP address assignment as well as other functions. The UPF 195 is connected to an IP service 197.IP services 197 may include the internet, intranets, IP Multimedia Subsystem (IMS), packet Switched (PS) streaming (PSs) services, and/or other IP services.

A base station may include and/or be referred to as a gNB, a node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a transmission-reception point (TRP), or some other suitable terminology. The base station 102 provides an access point for the UE 104 to the EPC 160 or core network 190. Examples of UEs 104 include a cellular telephone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a Personal Digital Assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electricity meter, an air pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functional device. Some UEs 104 may be referred to as IoT devices (e.g., parking timers, oil pumps, ovens, vehicles, heart monitors, etc.). The UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, or some other suitable terminology.

Fig. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. Fig. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. Fig. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. Fig. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be Frequency Division Duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), the subframes within that set of subcarriers are dedicated to DL or UL; or may be Time Division Duplex (TDD) in which for a particular set of subcarriers (carrier system bandwidth), the subframes within that set of subcarriers are dedicated to both DL and UL. In the example provided by fig. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 configured with slot format 28 (mostly DL) and subframe 3 configured with slot format 1 (all UL), where D is DL, U is UL, and F is flexible for use between DL/UL. Although subframes 3, 4 are shown as having slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. The slot formats 0, 1 are full DL, full UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with a slot format (dynamically configured by DL Control Information (DCI) or semi-statically/statically configured by Radio Resource Control (RRC) signaling) through a received Slot Format Indicator (SFI). The description also applies to a 5G NR frame structure for TDD.

Fig. 2A-2D illustrate frame structures, and aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and/or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more slots. The subframe may also include a mini slot, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols depending on whether the Cyclic Prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for 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 may be CP-OFDM symbols (for high throughput scenarios) or Discrete Fourier Transform (DFT) -spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to single stream transmission). The number of slots within a subframe is designed based on the CP and parameters. The parameter design defines the subcarrier spacing (SCS) and in practice defines the symbol length/duration, which is equal to 1/SCS.

For normal CP (14 symbols/slot), different parameter designs μ0 to 4 allow 1, 2, 4, 8 and 16 slots per subframe, respectively. For extended CP, parameter design 2 allows 4 slots per subframe. Accordingly, for normal CP and parameter design μ, there are 14 symbols/slot and 2 ^μ Each slot/subframe. The subcarrier spacing may be equal to 2 ^μ *15kHz, where μ is the parameter design 0 to 4. Thus, parameter design μ=0 has a subcarrier spacing of 15kHz, while parameter design μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing. Fig. 2A-2D provide examples of a normal CP of 14 symbols per slot and a parameter design μ=2 of 4 slots per subframe. The slot duration is 0.25ms, the subcarrier spacing is 60kHz, and the symbol duration is approximately 16.67 mus. Within the frame set there may be one or more different bandwidth portions (BWP) that are frequency division multiplexed (see fig. 2B). Each BWP may have a specific parameter design and CP (normal or extended).

The resource grid may be used to represent a frame structure. Each slot includes Resource Blocks (RBs) (also referred to as Physical RBs (PRBs)) that extend for 12 consecutive subcarriers. The resource grid is divided into a plurality of Resource Elements (REs). The number of bits carried by each RE depends on the modulation scheme.

As illustrated in fig. 2A, some REs carry a reference (pilot) signal (RS) for the UE. The RSs may include demodulation RSs (DM-RSs) for channel estimation at the UE (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RSs). The RSs may also include beam measurement RSs (BRSs), beam Refinement RSs (BRRSs), and phase tracking RSs (PT-RSs).

Fig. 2B illustrates an example of various DL channels within a subframe of a frame. A Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including 6 RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. The PDCCH within one BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring occasion on CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWP may be located at higher and/or lower frequencies across the channel bandwidth. The Primary Synchronization Signal (PSS) may be within 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 within symbol 4 of a particular subframe of a frame. 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 may determine a Physical Cell Identifier (PCI). Based on the PCI, the UE may determine the location of the DM-RS. A Physical Broadcast Channel (PBCH) carrying a Master Information Block (MIB) may be logically grouped with PSS and SSS to form a Synchronization Signal (SS)/PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth, and a System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information such as System Information Blocks (SIBs) not transmitted over the PBCH, and paging messages.

As illustrated in fig. 2C, some REs carry DM-RS for channel estimation at the base station (indicated as R for one particular configuration, but other DM-RS configurations are possible). The UE may transmit DM-RS for a Physical Uplink Control Channel (PUCCH) and DM-RS for a Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS may be transmitted in the previous or the previous two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether the short PUCCH or the long PUCCH is transmitted and depending on the specific PUCCH format used. The UE may transmit Sounding Reference Signals (SRS). The SRS may be transmitted in the last symbol of the subframe. The SRS may have a comb structure, and the UE may transmit the SRS on one of the comb. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

Fig. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries Uplink Control Information (UCI) such as a scheduling request, a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), a Rank Indicator (RI), and hybrid automatic repeat request (HARQ) Acknowledgement (ACK) (HARQ-ACK) information (ACK/Negative ACK (NACK)) feedback. PUSCH carries data and may additionally be used to carry Buffer Status Reports (BSR), power Headroom Reports (PHR), and/or UCI.

Fig. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In DL, IP packets from EPC 160 may be provided to controller/processor 375. Controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a Radio Resource Control (RRC) layer, and layer 2 includes a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. Controller/processor 375 provides RRC layer functionality associated with the broadcast of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection setup, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration of UE measurement reports; PDCP layer functionality associated with header compression/decompression, security (ciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer Packet Data Units (PDUs), error correction by ARQ, concatenation of RLC Service Data Units (SDUs), segmentation and reassembly, re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto Transport Blocks (TBs), de-multiplexing MAC SDUs from TBs, scheduling information reporting, error correction by HARQ, priority handling, and logical channel priority differentiation.

Transmit (TX) processor 316 and Receive (RX) processor 370 implement layer 1 functionality associated with a variety of signal processing functions. Layer 1, which includes a Physical (PHY) layer, may include error detection on a transport channel, forward Error Correction (FEC) encoding/decoding of a transport channel, interleaving, rate matching, mapping onto a physical channel, modulation/demodulation of a physical channel, and MIMO antenna processing. TX processor 316 handles the mapping to signal constellations based on various modulation schemes, such as binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM). The encoded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to OFDM subcarriers, multiplexed with reference signals (e.g., pilots) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying the time domain OFDM symbol stream. The OFDM streams are spatially precoded to produce a plurality of spatial streams. The channel estimates from the channel estimator 374 may be used to determine the coding and modulation scheme and for spatial processing. The channel estimate may be derived from reference signals and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318 TX. Each transmitter 318TX may modulate an RF carrier with a respective spatial stream for transmission.

At the UE 350, each receiver 354RX receives the signal via its respective antenna 352. Each receiver 354RX recovers information modulated onto an RF carrier and provides the information to the Receive (RX) processor 356.TX processor 368 and RX processor 356 implement layer 1 functionality associated with various signal processing functions. RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for UE 350. If there are multiple spatial streams destined for the UE 350, they may be combined into a single OFDM symbol stream by the RX processor 356. 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, as well as the reference signal, are recovered and demodulated by determining the signal constellation points most likely to be transmitted by the base station 310. These soft decisions may be based on channel estimates computed by channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. These data and control signals are then provided to a controller/processor 359 that implements layer 3 and layer 2 functionality.

A controller/processor 359 can be associated with the memory 360 that stores program codes and data. 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, cipher interpretation, 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.

Similar to the functionality described in connection with DL transmissions by the base station 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, integrity protection, integrity verification); RLC layer functionality associated with upper layer PDU delivery, error correction by ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto TBs, de-multiplexing MAC SDUs from TBs, scheduling information reporting, error correction by HARQ, priority handling, and logical channel priority differentiation.

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

UL transmissions are processed at the base station 310 in a manner similar to that described in connection with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its corresponding antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

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

At least one of TX processor 368, RX processor 356, and controller/processor 359 may be configured to perform aspects in conjunction with UCI multiplexer component 198 of fig. 1.

At least one of TX processor 316, RX processor 370, and controller/processor 375 may be configured to perform aspects in conjunction with multiplexed UCI receiving component 199 of fig. 1.

PUSCH may be transmitted across multiple slots as a multi-slot PUSCH transmission. PUSCH transmissions may span multiple transmission opportunities. The transmission occasion may include uplink resources (e.g., uplink time slots), where the resources allocated to the UE are used to transmit PUSCH. Fig. 4 illustrates a diagram 400 showing two different options for multi-slot PUSCH transmission. Fig. 4 also illustrates an example slot pattern 406, e.g., TDD uplink/downlink slot pattern. In a first option, e.g., as shown in option (a) in fig. 4, each transmission occasion of a multi-slot PUSCH transmission includes contiguous resources (e.g., contiguous symbols or contiguous slots) spanning one or more slots, e.g., as shown for transmission occasion 402. In some aspects, contiguous resources may include contiguous symbols extending into two different slots. Fig. 4 illustrates that the contiguous resources of each transmission occasion may be separated by resources that are not part of PUSCH transmission, such as downlink slots. In a second option, for example, as shown in option (b) of fig. 4, each transmission opportunity may include non-contiguous resources. The non-contiguous resources may include multiple contiguous resource sets, as shown for transmission opportunity 404.

A Time Domain Resource Allocation (TDRA) of a multislot PUSCH transmission occasion provides a set of consecutive or non-consecutive symbols of the transmission occasion. For a transmission opportunity of contiguous resources (e.g., option (a) in fig. 4), the TDRA may be indicated as a pairing, e.g., a pair (S, L), of a start symbol (S) of a contiguous resource and a length (L) of the contiguous resource of the transmission opportunity. Fig. 4 illustrates an example of (S, L) = (0, 20) to illustrate the concept. S=0 may correspond to the first symbol of the uplink slot of the uplink grant, and l=20 may correspond to a length of 20 symbols. For a transmission occasion of a non-contiguous resource (e.g., option (b) in fig. 4), TDRA may be indicated as a triplet (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 a slot indicated by the DCI as the start of a transmission occasion, which may be referred to as parameter K2. Fig. 4 illustrates 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 at 0 slots from the reference slot, s=0 indicates the first symbol of the slot as the starting symbol, and l=28 indicates the length of 28 symbols. In the second triplet, d=5 may indicate that the transmission occasion starts at 5 slots from the reference slot, s=0 indicates the first symbol of the slot as the starting symbol, and l=28 indicates the length of 28 symbols. Thus, the first triplet indicates a first contiguous set of resources and the second triplet indicates a second contiguous set of resources, the first and second contiguous sets of resources being non-contiguous with each other. L may be the same in both triples, as in this example. In other aspects, contiguous resource sets forming non-contiguous resources of a transmission opportunity may have different lengths.

A single Transport Block (TB) of PUSCH may be transmitted in a transmission occasion. If repetition is allowed, the TB may be transmitted on multiple transmission occasions. Thus, multislot PUSCH repetition may occur over a set of transmission occasions, with each repetition of a TB being transmitted within a single transmission occasion. Fig. 5A illustrates an example of four repetitions of PUSCH TB in four transmission occasions of contiguous resources according to option (a) and an example of two repetitions of PUSCH TB in two transmission occasions comprising non-contiguous resource sets according to option (b). In some aspects, the repetition factor may be indicated to the UE by the base station, e.g., along with a TDRA for a multislot PUSCH transmission. The repetition factor may indicate the number of repetitions 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 repeated interval to the UE. For example, the base station may indicate inter-repetition gaps in symbols or slots. Fig. 5A illustrates an example gap 502 between repetitions of option (a). For example, the gap may indicate a time interval between the end of one transmission occasion and the start of the next transmission occasion, or may indicate a time interval between the start of one transmission occasion and the start of the next transmission occasion.

Fig. 5A and 5B illustrate different examples of Redundancy Version (RV) cycles over repetitions of a TB transmitted as a multi-slot PUSCH transmission. The examples in fig. 5A and 5B may correspond to the same source payload of a TB and illustrate that the same source payload may be encoded differently across the resources of the transmission opportunity. In diagram 500 of fig. 5A, RV is refreshed (e.g., changed) between transmission opportunities (e.g., at gap 502). In fig. 5A, RV0 is applied to contiguous resources of a first transmission opportunity. The RV index becomes RV2 at the subsequent transmission opportunity. The RV index then becomes RV3 and RV1 for subsequent transmission opportunities. Similarly, for the transmission occasions of the non-contiguous resource sets in option (b), the RV index is similarly maintained across the non-contiguous resource sets of a single transmission occasion and changed or refreshed for subsequent transmission occasions. An example is shown for TB transmission on a single transmission occasion. Thus, the RV loops over TB repetition in different transmission opportunities.

Fig. 5B illustrates a diagram 550 in which the RV may cycle within individual transmission opportunities instead of cycling between transmission opportunities as in fig. 5A. As shown for option (B) in fig. 5B, a single RV index may be used on contiguous symbol sets for non-contiguous transmission opportunities and may become a different RV index at subsequent contiguous symbol sets within the same transmission opportunity. Thus, the RV may refresh or change at the gap between contiguous resources of a single transmission opportunity. As shown for option (a) in fig. 5B, a single RV index may be used on symbols of a single slot, and different RV indexes may be applied to symbols of subsequent slots of a transmission opportunity. Thus, the RV may refresh or change at the slot boundaries of a single transmission opportunity.

The aspects presented herein may be applied to multislot PUSCH transmissions with a single codebook. In some examples, aspects presented herein may be applied to multi-codebook PUSCH transmissions. However, a multi-codebook PUSCH transmission may provide less gain than the Shan Ma present implementation. In some aspects, the TB size may range from approximately 100 bits to 1000 bits, although aspects may be similarly applied to TB sizes less than or greater than this range.

When the UE transmits PUSCH across multiple slots, the UE may learn/store the transmission status across slots. In some aspects, the state may refer to the state of the last transmitted bit. Transmitting PUSCH across slots or across non-contiguous symbols can be challenging for a UE if the UE interleaves PUSCH transmissions. For example, the UE may use information about how many interleaved sequences were transmitted and/or may store untransmitted sequences. To simplify the operation of the UE, the UE may apply interleaving, for example, within a slot.

Fig. 6 illustrates a diagram 600 showing example aspects of interleaving TBs for transmission of a multi-slot PUSCH. Fig. 6 shows a pattern of transmission opportunities for contiguous resources, e.g., similar to option (a) in fig. 4. The TB may be transmitted within a single transmission opportunity, such as in time slot 0 (e.g., 604) and time slot 1 (e.g., 606) of transmission opportunity 602. The UE may read information bits of the TB from the circular buffer based on the starting position indicated by the RV index (e.g., as shown at 610). The information bits of the TB may start, for example, at RB0. The rate matching bits that have been read from the circular buffer are illustrated at 620. Rate matching may include a process in which the number of encoded bits that may be transmitted on the available resources for PUSCH transmission is determined. For example, the total number of bits may be equal to the total number of available REs multiplied by the modulation order. The determined number of encoded bits may then be read from the circular buffer. As used herein, "rate matching bits" refers to encoded bits selected for transmission based on rate matching requirements and/or principles. In some aspects, the number of bits may be selected based on the number of bits used for rate matching TBs within transmission opportunity 602. After reading out the bits, the UE may apply interleaving to the bits. For example, the channel coding process for PUSCH transmission may include a bit-level interleaver for each CB of a TB. Fig. 6 illustrates an example of row-column interleaving in which bits may be organized (e.g., read into or placed in) 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) on a column basis. Thus, the bits from the first column of row 630 correspond to bits 640 for transmission in slot 0. The bits from the first column of row 632 correspond to bits 642 for transmission in slot 0. This process is followed by the bits in the second column of row 630 being placed 644, followed by the bits in the second column of row 632 being placed 646, and so on. Bits for rate matching across the entire transmission opportunity may be interleaved and transmitted, as shown in fig. 6, which illustrates the interleaving applied across time slot 0 and time slot 1 of transmission opportunity 602. In other aspects, the bits for rate matching may be selected per slot and may be interleaved per slot prior to transmission, such as illustrated in fig. 7. Fig. 7 illustrates a diagram 700, which shows 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. Thus, bits for slot 0 are read from rows 730 and 732 in a column manner to form a slot-based interleaving pattern 740 for slot 0, and bits for slot 1 are read from rows 734 and 736 in a column manner to form a slot-based interleaving pattern 742 for slot 1.

Fig. 6, 7 and 8 are encoded in a single Code Block (CB) based on the entire TB. The TB may be encoded across multiple CBs. When the entire TB is encoded using a single CB, the encoded bits for transmission (encoded bits in the circular buffer) may be selected on a per-slot basis or a per-TO basis. These selected bits are referred to as 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 rate matched bits are selected per slot, the interleaver spans a single slot. When rate-matched bits are selected on a per-slot basis, multiple sets of rate-matched bits will be selected and individually interleaved so that resources across the entire TO are used.

The example in fig. 6 may be applied to transmission opportunity-based rate matching and interleaving of non-contiguous resources for a single transmission opportunity, such as in option (b) of fig. 4. Instead of bits for slot 0 and slot 1 (as in fig. 6), bits may be used for non-contiguous slots included in the same transmission opportunity. Fig. 8 illustrates a diagram 800 of an example of segment-based rate matching and interleaving for non-contiguous resources of a single transmission occasion, as in option (b) shown in fig. 8. Fig. 8 illustrates a transmission opportunity 802, the transmission opportunity 802 comprising a first segment 804 of contiguous resources and a second segment 806 of contiguous resources. Instead of rate matching and interleaving per slot (as in fig. 7), the bits may be read out to rate match and interleave (such as column-row interleaving) to obtain interleaved bits 840 of a first segment of contiguous resources (e.g., 804) and interleaved bits 842 of a second segment of contiguous resources (e.g., 806).

Thus, in a first option, rate matching and interleaving may be applied to bits across the entire transmission opportunity, which may be referred to as transmission opportunity-based rate matching and interleaving or may be referred to as rate matching and interleaving across transmission opportunities, as illustrated in fig. 6. Thus, bits for transmission occasions are selected, read or otherwise entered. The bits for the transmission opportunity may then be rate matched and interleaved and transmitted by the UE. In a second option, bits may be selected per slot and interleaving may be applied to the bits of that slot, as shown in fig. 7, which may be referred to as slot-based interleaving, per slot interleaving, or cross slot interleaving. Thus, bits for a slot may be selected, read, or otherwise input. The bits for the time slots may then be interleaved and transmitted by the UE. In a third option, bits may be selected per segment with transmission occasions of non-contiguous segments, and interleaving may be applied to bits of the respective segments, as shown in fig. 8, which may be referred to as segment-based interleaving, per-segment interleaving, or cross-segment interleaving. Thus, bits for segmentation may be selected, read, or otherwise input. The bits for segmentation may then be interleaved and transmitted by the UE.

If the UE rate-matches and interleaves bits per slot, as in fig. 7, the UE may use the starting position within the circular buffer for each slot. The UE may not need to buffer the interleaved bits and may instead protect the circular buffer. The per-slot rate matching and interleaving may provide improved timelines, resource management, and/or memory management for the UE. In some aspects, UCI may be multiplexed with PUSCH. UCI multiplexing may be considered on a per-slot basis, e.g., based on overlap between a slot in which UCI is to be transmitted and a slot in which PUSCH is to be transmitted. In some aspects, the timeline may be tied to a different reference point than the beginning of the multislot PUSCH transmission.

For rate matching and interleaving of bits per segment (as illustrated in the example in fig. 8), the UE may remember a starting position within the circular buffer for each segment, e.g., without buffering the interleaved bits, similar to slot-based interleaving.

Performance may be improved if the UE rate-matches and interleaves bits across transmission occasions (e.g., as in fig. 6), because systematic bits may occupy more reliable positions within the transmission occasions.

UCI multiplexing per slot may be easier when rate matching and interleaving are performed per slot than rate matching and interleaving bits across transmission occasions or segments of transmission occasions.

In some aspects, the UE may have UCI for transmission at times that overlap with a multislot PUSCH transmission. The UE may multiplex UCI with PUSCH transmissions. UCI may be scheduled within a slot and PUSCH may extend across multiple slots. Aspects presented herein enable a UE to determine how many resources allocated to PUSCH are to be used for UCI, the location of UCI within PUSCH, coding and rate matching for PUSCH and multiplexed UCI, and so on.

Fig. 9 illustrates an example 900 of a transmission opportunity 902 with contiguous resources (e.g., resources in time slots 904 and 906), similar to option (a) in fig. 4. Fig. 9 also illustrates PUCCH overlapping of UCI 908 with slot 906 of PUSCH 910. As given herein, the overlap between PUSCH and PUCCH may be handled independently per transmission occasion of PUSCH. UCI may include various types of information. In some aspects, UCI may include ACK/NACK information for PDSCH received from a base station, e.g., HARQ feedback. In other aspects, the UE may receive and measure CSI-RS from the base station and may have CSI reports to transmit as UCI to the base station.

For each transmission occasion in which one of a plurality of slots of contiguous resources of the transmission occasion overlaps in time with a PUCCH resource for transmitting UCI, the UE may consider whether PUCCH, e.g., UCI, is to be multiplexed in the resources of the transmission occasion.

The UE may consider, for example, whether UCI of the PUCCH is to be multiplexed in overlapping slots and UCI of the PUCCH is not to be multiplexed in other slots of the transmission opportunity. In some aspects, the timeline for multiplexing UCI may be based on overlapping time slots, e.g., time slot 906 in fig. 9. In other aspects, the timeline for multiplexing UCI may be based on the beginning of the transmission opportunity 902.

The UE may consider, for example, whether to multiplex UCI of the PUCCH on a transmission occasion, not limited to slots overlapping the UCI. The timeline for multiplexing UCI may be based on the beginning of transmission opportunity 902.

Table 1 illustrates examples of various scenarios (e.g., examples 1-5) that show various combinations of considerations for multiplexing UCI with contiguous resource transmission opportunities (e.g., option (a) of fig. 4) for multi-slot PUSCH transmission.

/>

TABLE 1

Fig. 10 illustrates an example diagram 1000 from example 1 of table 1, in which UCI 1008 overlaps in slot 0 (e.g., slot 1004) of a transmission occasion 1002, the transmission occasion 1002 having contiguous resources in slots 1004 and 1006. UCI overlaps in slot 0 of transmission occasion 1002 and is multiplexed in slot 0. Fig. 10 illustrates that resources of UCI may be included within a single slot (e.g., slot 0 1004). Slot 0 may also include other transmissions in the symbols of the slot. For example, UCI may be transmitted after transmission of the DMRS.

In the example in fig. 10, the UE may determine resources for UCI transmission based on the resources available in slot 0 1004. The UE may apply a beta factor over the resources available for PUSCH transmission in slot 0 1004. For single-slot PUSCH, the UE may determine the number of REs potentially available for UCI transmission across PUSCH symbols in which UCI may be multiplexed, dividing the number of REs by the total number of PUSCH bits.

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

As an example, for UCI including HARQ-ACK bits on a single-slot PUSCH, the UE may determine the number of coded modulation symbols per layer (denoted as Q 'for HARQ-ACK transmission' _ACK )：

In this example of formula 1, O _ACK Is the number of HARQ-ACK bits, and L _ACK Is the number of CRC bits for HARQ-ACKs.Is the scheduled bandwidth of PUSCH transmission expressed as the number of subcarriers. />Is the number of resource elements in OFDM symbol/that can be used for transmitting UCI in PUSCH transmission, where +. >And is also provided withIs the total number of OFDM symbols of PUSCH (including all OFDM symbols for DMRS), +.>Is the number of subcarriers in OFDM symbol/carrying PTRS in PUSCH transmission. Alpha is configured by higher layer parameters, such as scaling parameters. In this example, l ₀ Is the symbol index of the first OFDM symbol of PUSCH after the first DMRS symbol in PUSCH transmission, which does not carry DMRS. /> Is the beta offset.

Thus, in this single-slot PUSCH example, the one in equation 1Can correspond to the total number of PUSCH bits, and +.>May correspond to the number of REs potentially available for UCI across all PUSCH symbols.

In contrast, for the multislot PUSCH transmission occasion of fig. 10, equation 1May correspond to the number of REs potentially available for UCI 1008 across PUSCH symbols in slot 0 1004, and +.>May correspond to a 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 (e.g., including both slot 0 1004 and slot 1 1006). Such a determination preferably accounts for the overall burden imposed on PUSCH transmissions when UCI 1008 is multiplexed into slot 0.

After determining the number of resources to be used for UCI 1008 in slot 0 in fig. 10, the UE may identify the location of these resources within slot 0 1004. The UE may then use UCI symbols to populate the identified resources in slot 0 1004. The UE may first fill the frequency resources of a particular symbol and then fill the frequency resources in additional symbols, for example, in the case where all of the frequency resources of the symbol are filled with UCI. Such resource filling may be referred to as a frequency-first-time-last approach. The UE may determine PUSCH rate matching bits based on, for example, remaining resources of the transmission occasion using remaining resources in slot 0 1004 and slot 1 1006. The UE may interleave the rate-matched bits of PUSCH 1110. As shown in table 1, the rate matching and interleaving and/or RV loops for example 1 may be per slot (e.g., as described in connection with fig. 7) or per transmission occasion (e.g., as described in connection with fig. 6). After interleaving, the UE may use the interleaved bits mapped to the modulation symbols to populate the resources identified for transmission occasion 1002 of PUSCH 1010.

Fig. 11 is a diagram 1100 illustrating a PUCCH (e.g., UCI 1108) that overlaps PUSCH 1110 in slot 0 1004 of transmission occasion 1102 and is multiplexed based on transmission occasion 1102, rather than based solely on the overlapping slots. Fig. 11 corresponds to example 2 in table 1, where the overlapping time slots are time slot 0 and the multiplexing is based on transmission opportunities. As illustrated in fig. 11, the resources used to multiplex UCI 1108 may span multiple slots.

In the example in fig. 11, the UE may determine resources for UCI based on the resources available in transmission opportunity 1102. For example, in multislot PUSCH transmission occasion 1102 of fig. 11, equation 1PUSCH symbols, which may correspond to cross transmission occasion 1102 (including slot 0 1104 and slot 1 1106), are potentially available for the number of REs of UCI 1108, and in equation 1The total number of PUSCH bits for the multiple slots of the transmission occasion 1102 may correspond.

After determining the number of resources to use for UCI 1108 in transmission occasion 1102, the UE may identify the location of these resources within transmission occasion 1102. The UE may then populate the identified resources in transmission opportunity 1102 with UCI symbols. The UE may fill the resources in a frequency-first-time-last manner. The UE may use the remaining resources in transmission opportunity 1102 (e.g., in slot 0 1104 and slot 1 1106) to determine PUSCH rate matching bits. The UE may interleave the rate-matched bits of PUSCH. As illustrated in table 1, in example 2, the rate matching and interleaving and/or RV loops may be per slot (e.g., as described in connection with fig. 7) or per transmission occasion (e.g., as described in connection with fig. 6). After interleaving, the UE may populate the resources identified for transmission occasion 1102 of PUSCH 1110 with the interleaved bits mapped to the modulation symbols.

Fig. 12 illustrates a diagram 1200 showing a PUCCH (e.g., UCI 1208) that overlaps with slot 11206 of a transmission occasion 1202 for PUSCH 1210, but not with the first slot 1204 of the transmission occasion 1202 (as in fig. 10 and 11). Fig. 12 corresponds to example 3 in table 1, where the overlapping time slots are time slot 1 and are multiplexed in time slot 1. Fig. 12 illustrates an example in which UCI 1208 is multiplexed within a single slot (e.g., slot 1 1206).

The UE may determine the number of resources to use for UCI 1208 in slot 1 1206. Similar to the explanation in connection with fig. 10, the UE may determine the number of resources based on the number of REs potentially available for UCI in PUSCH symbols of slot 1 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 a transmission occasion.

For example, in formula 1May correspond to the number of REs potentially available for UCI 1208 across the PUSCH symbols in slot 11206, and +.>May correspond to a total number of PUSCH bits scaled by the number of symbols in slot 11206 divided by the total number of PUSCH symbols in transmission occasion 1202 (e.g., including both slot 0 1204 and slot 1 1206).

After determining the number of resources to be used for UCI 1208 in slot 1 in fig. 12, the UE may identify the location of UCI resources within slot 1 1204. The UE may then populate the identified resources in slot 1 1204 with UCI symbols. The UE may fill the resources in a frequency-first-time-last manner. The UE may use the remaining resources in slot 11206 to determine PUSCH rate matching bits. The UE may determine the rate-matched bits for slot 1 based on where slot 0 transmission ends. The UE may then interleave the rate-matched bits. As shown in table 1, the rate matching and interleaving and/or RV loops for example 3 may be per slot (e.g., as described in connection with fig. 7) or per transmission occasion (e.g., as described in connection with fig. 6). After interleaving, the UE may populate the resources identified for PUSCH 1210 with interleaved bits mapped to the modulation symbols.

Fig. 13 illustrates a diagram 1300 showing a PUCCH (e.g., UCI 1308) that overlaps with slot 1 1306 of a transmission occasion 1302 for PUSCH 1310 instead of overlapping with the first slot 1304 of the transmission occasion 1302 (as in fig. 10 and 11). In contrast to fig. 12, UCI is multiplexed based on transmission opportunities instead of overlapping slots in fig. 13. Thus, in fig. 12, UCI is multiplexed in slot 0 1304 without having to be multiplexed in the slot with which UCI overlaps. In some aspects, the multiplexed UCI may span multiple slots. Fig. 13 may correspond to example 4 in table 1.

In the example in fig. 13, the UE may determine resources for UCI 1308 based on the resources available in transmission occasion 1302. For example, in the multislot PUSCH transmission occasion 1302 of fig. 13, the one in equation 1The number of REs potentially available to UCI 1308 may correspond to PUSCH symbols spanning transmission occasion 1302 (including slot 0 1304 and slot 1 1306), and +.>The total number of PUSCH bits for the multiple slots of the transmission occasion 1302 may correspond.

After determining the number of resources to use for UCI 1308 in transmission occasion 1302, the UE may identify the location of these resources within transmission occasion 1302. The UE may then populate the identified resources in transmission occasion 1302 with UCI symbols. The UE may fill the resources in a frequency-first-time-last manner. The UE may use the remaining resources in transmission opportunity 1302 (e.g., in slot 0 1304 and slot 1 1306) to determine PUSCH rate matching bits. The UE may interleave the rate-matched bits of PUSCH. As illustrated in table 1, in example 4, the interleaving/RV cycle may be per slot (e.g., as described in connection with fig. 7) or per transmission occasion (e.g., as described in connection with fig. 6). After interleaving, the UE may populate the resources identified for transmission occasions 1302 of PUSCH 1310 with interleaved bits mapped to the modulation symbols.

Fig. 14 illustrates a diagram 1400 showing a PUCCH (e.g., UCI 1408 and/or 1409) multiplexed with a plurality of slots (e.g., slot 0 1404 and slot 1 1406) for transmission opportunity 1402 of PUSCH 1410. The resources to be used for multiplexing UCI may be included in a single slot and may be repeated in each slot. UCI may be repeated in each slot of transmission opportunity 1402. The timeline may be based on slot 0 1404 of transmission opportunity 1402. Fig. 14 may correspond to example 5 in table 1.

Fig. 15 illustrates a diagram 1500 that shows aspects of timeline considerations for multiplexing UCI in a multi-slot PUSCH transmission. As illustrated in fig. 15, the UE may consider UCI multiplexed for transmission in PUCCH 1510 that overlaps in time with a transmission opportunity for the multi-slot PUSCH 1504. The UE may apply the processing timeline in determining whether UCI (e.g., from PUCCH 1510) is to be multiplexed into PUSCH 1504. In some aspects, the processing timeline may be based on a minimum gap (N2) of symbols between receipt of the uplink grant DCI 1502 scheduling uplink resources for the PUSCH 1504 and a start of the multislot PUSCH transmission 1504. If the start of the multi-slot PUSCH transmission 1504 is greater than N2 symbols after receiving the uplink grant DCI 1502, 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 receiving the uplink grant DCI 1502, 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 between the received PDSCH 1508 and the beginning of the PUCCH 1510 carrying UCI (e.g., HARQ ACK/NACK payload for the received PDSCH) (N1). If the start of the PUCCH 1510 is greater than N1 symbols after receiving the PDSCH 1508, the UE may transmit UCI (e.g., HARQ ACK/NACK) in the PUCCH 1510. If the start of PUCCH 1510 is less than N1 symbols after receiving PDSCH 1508, the UE may not transmit UCI (e.g., HARQ ACK/NACK) in PUCCH 1510. When the UE considers multiplexing UCI from PUCCH 1510 into multi-slot PUSCH 1504, a reference time (e.g., S ₀ ) To measure whether the N2 and N1 based processing timelines are satisfied. The reference time may be different based on various aspects of UCI multiplexing (such as where PUCCH overlap occurs, where UCI is to be multiplexed, the manner in which UCI is to be multiplexed, etc.). As an additional consideration, if the downlink grant 1506 for the PDSCH 1508 is received before the uplink grant 1502 for the multi-slot PUSCH 1504, HARQ ACK/NACK bits from the PUCCH 1510 may be multiplexed into the multi-slot PUSCH 1504.

In a first example, if PUCCH 1510 overlap occurs in a first slot of multi-slot PUSCH transmission 1504 and UCI is multiplexed onto the first slot (such as in the example in fig. 10), then reference time S is made ₀ The start of the multislot PUSCH transmission 1504 may be based on as shown in fig. 15.

If PUCCH overlap occurs in the first slot of a multi-slot PUSCH transmission and UCI is multiplexed across the entire transmission opportunity (e.g., as described in connection with fig. 11), then reference time S is made ₀ The start of the multislot PUSCH transmission 1504 may be based on as shown in fig. 15.

Thus, reference time S at the beginning of the multislot PUSCH transmission 1504 ₀ May be applied to UCI overlapping with the first time of the transmission opportunity, whether the UCI is multiplexed based on the first time slot or across transmission opportunities.

Fig. 16 illustrates a diagram 1600 that shows aspects of timeline considerations for multiplexing UCI in a multi-slot PUSCH transmission. As illustrated in fig. 16, the UE may consider UCI multiplexed for transmission in PUCCH 1610 that overlaps in time with a transmission opportunity for multi-slot PUSCH 1604. In fig. 16, PUCCH 1610 overlaps PUSCH 1604 in a subsequent slot of a multi-slot transmission occasion (instead of in the first slot as in fig. 15), e.g., at 1612, and is multiplexed in the overlapped slot. Fig. 12 illustrates an example in which UCI overlaps with and is multiplexed in a second slot of a multi-slot PUSCH transmission occasion 1202.

In fig. 16, if PUCCH 1610 overlap occurs in a second or subsequent slot of multi-slot PUSCH transmission 1604 and UCI is multiplexed in the slot on a per transmission occasion basis, then reference time S ₀₁ May be determined by the start of a multislot PUSCH transmission, e.g., as shown at 1611. In some aspects, if rate matching and interleaving are performed on a per transmission occasion basis, then S ₀₁ Applicable. In use S ₀₁ A single interleaver may be applied per transmission occasion in this example of (a).

In contrast, if PUCCH 1610 overlap occurs in a second or subsequent slot of multi-slot PUSCH transmission 1604 and UCI is multiplexed in that slot, then reference time S ₀₂ This slot based on multi-slot PUSCH transmission, for example, as shown at 1611. In some aspects, if rate matching and interleaving are performed on a per-slot basis, S ₀₂ Applicable. In use S ₀₂ A single interleaver may be applied per slot for the multi-slot PUSCH transmission 1604.

If the PUCCH 1610 overlap occurs in the second or subsequent slots of the transmission opportunity for the multi-slot PUSCH transmission 1604 and UCI is multiplexed across the transmission opportunity instead of per slot, the reference time may be S ₀₁ And is based on the start of the multislot PUSCH transmission 1604.

As described in connection with fig. 15, the time gap between DCIs 1602 scheduling multi-slot PUSCH transmissions 1604 may satisfy N2 symbols to transmit PUSCH 1604, and DCI 1606 scheduling PDSCH 1608 (UE planning to transmit UCI for that PDSCH 1608 in PUCCH 1610) may be received before DCI 1602 to multiplex UCI with PUSCH 1604.

Fig. 17 illustrates an example 1700 similar to fig. 15 of CSI-RS (such as aperiodic CSI-RS 1708) based UCI that overlaps in time in a first symbol of a multi-slot PUSCH transmission 1704. The gap N2 between DCI 1702 and scheduled multislot PUSCH transmission 1704 may be the same as in fig. 15. For the packet in PUCCH 1710Including CSI reports, a minimum gap (Z) between the last symbol of CSI-RS1708 and the beginning of PUCCH 1710 carrying the CSI report may be measured. 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 multislot PUSCH transmission 1704. If the time slot is at least Z symbols, the UE may multiplex the CSI report with the PUSCH 1704. Additional aspects such as those described in connection with fig. 16 may be similarly applied to CSI-based UCI, e.g., from the last symbol of a received CSI-RS to reference symbol S ₀₂ 。

Fig. 18 illustrates a diagram 1800 showing multiple PUCCHs (e.g., UCI 1808, 1818, 1828, 1838, 1848, 1858, 1868) overlapping transmission opportunities for multi-slot PUSCH transmission in various combinations. For example, transmission occasion 1802a overlaps PUCCH for UCI 1808 in slot 0 of the transmission occasion and overlaps PUCCH for UCI 1818 in slot 1 of the transmission occasion, e.g., a single UCI overlaps a different time slot of transmission occasion 1802 a. The transmission occasion 1802b has a single slot overlapping multiple PUCCHs, e.g., for UCI 1828 and 1838. The transmission occasion 1802c has overlap of UCI 1848 and 1858 in one slot of the transmission occasion 1802c and overlap of UCI 1868 in another slot of the transmission occasion 1802 c.

When multiplexing a plurality of UCI for a plurality of PUCCHs in a single transmission occasion including a plurality of slots for PUSCH transmission, the UE may handle overlap on a per-slot basis and may multiplex UCI with PUSCH on a per-slot basis.

In other aspects, when multiplexing multiple UCI for multiple PUCCHs in a single transmission occasion including multiple slots for PUSCH transmission, the UE may handle overlapping across the transmission occasions. The UE may multiplex UCI across transmission occasions, e.g., even in cases where PUCCH does not occur in the same slot of a transmission occasion (such as for UCI 1808 and 1818, or for UCI 1848 and UCI 1868). In some aspects, the UE may jointly multiplex UCI.

If overlapping UCI is handled on a per-slot basis, the UE may multiplex UCI, whether there is a single UCI or multiple overlapping UCI within the overlapping corresponding slots of the transmission opportunity. Fig. 19 illustrates a diagram 1900 that shows, using arrows, slots in which UCI in fig. 18 is handled/multiplexed in a per-slot example. PUSCH may be rate matched on a per slot basis. Between slots, the UE may remember or store the starting position in the circular buffer. For example, circular buffer 1950 in fig. 19 illustrates a pointer 1955 for bits between slot 0 and slot 1. PUSCH may be interleaved on a per-slot basis, e.g., as described in connection with fig. 7.

If overlapping UCI is handled across transmission occasions, they affect multiplexing of each other even if they do not occur within the same slot. The UE may determine UCI resources for multiplexing purposes at the beginning of the transmission occasion. For timeline purposes, the UE may view the overlap in slot 1 prior to the start of the transmission opportunity. For PUSCH handling, the UE may rate match PUSCH across the entire transmission occasion. The UE may interleave the PUSCH across transmission occasions, such as described in connection with fig. 6. Fig. 20 illustrates diagram 2000, which shows, using arrows, the handling of UCI in fig. 18 per transmission occasion. PUSCH may be rate matched on a per slot basis. For example, circular buffer 2050 in fig. 20 illustrates applying a circular buffer to the combined bits of a transmission opportunity.

Fig. 21 illustrates a diagram 2100 that shows aspects of a timeline consideration for multiplexing multiple UCI in a multi-slot PUSCH transmission 2104. As illustrated in fig. 21, the UE may consider UCI multiplexed for transmission in PUCCH 2110 and/or 2120 that overlaps in time with the transmission opportunity for the multi-slot PUSCH 2104. In fig. 21, PUCCH 2110 overlaps PUSCH 2104 in the first slot of a multi-slot transmission occasion, rather than being similar to fig. 15.PUCCH 2120 overlaps PUSCH 2104 in a subsequent slot of the multi-slot transmission occasion, but not in the first slot. Both PUCCHs 2110 and 2120 are scheduled by DCIs 2106 and 2116 scheduling PDSCH 2108 and 2118, the DCIs 2106 and 2116 being received before uplink grant 2102 scheduling PUSCH 2104, and thus meeting the threshold for multiplexing with PUSCH 2104. In some aspects, the reference time may be based on a start of the multislot PUSCH 2104 (e.g., S ₀₁ ) Regardless of how and/or where UCI is multiplexed. For example, the UE may prepare a multislot PUSCH transmission in advance, andcan be based on S as a reference ₀₁ The start of the multislot PUSCH 1604 applies timeline considerations for each of the multiple PUCCHs (2110 and 2120).

In some aspects, the reference for multiplexing each PUCCH may be based on a multiplexed slot. For example, each of the multiple PUCCHs may independently have reference times based on multiplexed slots, or based on other considerations for the individual PUCCHs described in connection with fig. 15-17. For example, the reference time for PUCCH 2120 may be S ₀₂ While the reference time for PUCCH 2110 may be S ₀₁ . In some examples, determining the different reference times may be based on an interleaving and rate matching configuration. For example, if different PUCCHs are multiplexed on a per-slot basis (e.g., where rate matching is performed on a per-slot basis and/or interleaving is performed on a per-slot basis, such as described in connection with fig. 19), an independent determination of reference time per PUCCH may be applied.

If multiplexing of multiple UCI is handled across transmission occasions rather than per slot (e.g., as described in connection with fig. 20), the UE may apply a common reference time S to each PUCCH based on the start of the multislot PUSCH 2104 ₀₁ . The start of PUSCH may be applied as a reference time because UCI multiplexing decisions may be made in a joint manner for different PUCCHs. The common reference time may enable the UE to prepare for multislot PUSCH transmissions in advance.

Fig. 22 illustrates a diagram 2200 showing PUCCH resources for UCI 2208 and 2209, the UCI 2208 and 2209 overlapping with transmission opportunities 2202 and 2212 comprising non-contiguous resource segments, e.g., option (b) as described in connection with fig. 4. For example, transmission opportunity 2202 includes segments 2205 and 2207, segments 2205 and 2207 being separated in time by resources not included in transmission opportunity 2202. Segments 2205 and 2207 each include contiguous sets of resources. For example, segment 2205 is illustrated as having resources in first slot 2204 and second slot 2206. Each transmission occasion (e.g., 2202 and 2212) may be independently treated for multiplexing UCI with PUSCH transmitted on multiple slots of one transmission occasion. Each transmission occasion may have an aspect corresponding to a per-slot treatment of PUSCH and PUCCH. In some aspects, each contiguous segment within a transmission opportunity may be handled independently of the other segment(s).

In some aspects, the UE may consider (e.g., handle or apply) multiplexing PUCCHs within overlapping slots instead of non-overlapping slot(s). Aspects of multiplexing in this example may be applied similarly to multiplexing within overlapping time slots of contiguous transmission occasions, such as described in connection with example 1 and example 3 in table 1 and fig. 10 and 12, for example.

In some aspects, the UE may consider (e.g., handle or apply) multiplexing over the entire transmission opportunity (e.g., 2202) including non-contiguous segments 2205 and 2207. Aspects of multiplexing in this example may be applied similarly to multiplexing on transmission occasions for contiguous transmission occasions, such as described in connection with example 2 and example 4 in table 1 and fig. 11 and 13, for example.

In some aspects, the UE may consider (e.g., handle or apply) multiplexing over contiguous portions of the transmission opportunity (e.g., within overlapping segments 2207 of transmission opportunity 2202). Table 2 illustrates example aspects of multiplexing UCI with a multislot PUSCH per segment (including non-contiguous resource segments for UCI 2208) handling of a transmission occasion.

TABLE 2

Fig. 23 illustrates a diagram 2300 of UCI based on overlapping segment multiplexing of non-contiguous transmission opportunities 2302. The transmission opportunity includes non-contiguous segments 2305 and 2307. Segment 2307 overlaps in time with the PUCCH used to transmit UCI 1908. Based on this overlap, UCI 2308 may be multiplexed with PUSCH TBs for transmission in a transmission occasion. Multiplexing may be handled per segment, with multiplexing in segment 2307 handled independently of processing for segment 2305. Segment 2307 includes resources spanning two time slots (e.g., time slot 5 2304 and time slot 6 2306). The resources for multiplexing UCI 2308 may be determined based on the segment in which PUCCH is multiplexed. UCI resources may be determined based on segmented resources.

As an example, the number of resources for multiplexing UCI may be determined based on the number of REs potentially available for UCI for PUSCH symbols in the corresponding segment across transmission opportunities. The determination may also be based on a 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 formula 1, formula 1PUSCH symbols, which may correspond to corresponding segments across transmission occasions (e.g., segment 2307 of transmission occasion 2302), are potentially available for the number of REs of UCI 2308, and +.>The total number of PUSCH bits for transmission occasion 2302 may correspond to the number of symbols in the corresponding segment divided by the total number of PUSCH symbols in the transmission occasion.

After determining the number of resources to be used for UCI 2308 in slot 5 in fig. 23, the UE may identify the location of UCI resources within slot 5 2304. The UE may then use UCI symbols to populate the identified resources in slot 5 2304. The UE may fill the resources in a frequency-first-time-last manner. The UE may use the remaining resources to determine PUSCH rate matching bits and may interleave the rate matching bits. After interleaving, the UE may populate the resources identified for PUSCH using the interleaved bits mapped to the modulation symbols.

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

Fig. 24 illustrates two examples of potential timelines for PUCCH 2410a or 2410b, the PUCCH 2410a or 2410b overlapping with transmission opportunity 2402 for a multislot PUSCH. The PUCCH may include UCI that may be scheduled by a downlink grant in DCI 2406a or 2406b, such as an ACK/NACK for PDSCH 2408a or 2408 b.

In a first timeline example, the reference time for measurement of N1 and/or Z (if UCI includes CSI) may be based on the segment in which PUCCH is to be multiplexed. The reference time may be mapped to the beginning of the segment, e.g., as by S in FIG. 24 ₀₁ As shown. The use of timeline 1 may be based on an interleaving and rate matching configuration for PUSCH and multiplexed UCI, such as on a per-segment or per-slot basis, for example.

In a second example timeline, the reference time for the measurement of N1 and/or Z may be based on the start of the multislot PUSCH, e.g., as by S in fig. 24 ₀₂ As shown. In some aspects, the UE may apply the reference time S ₀₂ Regardless of how or where UCI is to be multiplexed within a multislot PUSCH transmission. Using the reference time at the beginning of the multislot PUSCH transmission may provide the UE with increased time to prepare for the multislot PUSCH.

Fig. 25 illustrates an example communication flow 2500 between a UE 2502 and a base station 2504 that includes UCI transmissions multiplexed with a multislot PUSCH transmission 2528. As illustrated at 2506, the base station 2504 may transmit DCI that allocates or grants resources for PUSCH transmission to the UE 2502. The allocated resources may include transmission opportunities that span multiple time slots, such as described in connection with fig. 4. At 2510, the ue may trigger multiplexing UCI with a multislot PUSCH transmission based on determining a time overlap between PUCCH resources for UCI and transmission occasions of PUSCH. As a non-limiting example illustrating this concept, a UE may receive a downlink transmission 2508, which may have UCI for the downlink transmission 2508 to transmit to a 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 about the PDSCH to be transmitted as UCI overlapping with resources for PUSCH. The PDSCH may be based on DCI 2505 scheduling the PDSCH, and the DCI 2505 may be received before the DCI with the uplink grant at 2506. As another example, downlink transmission 2508 may include CSI-RS, and the UE may have CSI to report as UCI to the base station.

As part of determining that UCI is to be multiplexed with a multislot PUSCH transmission at 2510, the UE may apply a processing timeline. The processing timeline may be based on N1 and/or Z, such as described in connection with any of fig. 15-17, 21, or 24. For example, when determining whether N1 or Z of PUCCH associated with UCI satisfies a minimum gap for multiplexing UCI with PUSCH, the UE may determine a reference time (e.g., S ₀ 、S ₀₁ Or S ₀₂ ) Applied to the processing timeline.

As illustrated at 2512, to multiplex UCI with PUSCH transmissions, 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, such as described in connection with 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 transmission occasions. The UE may also determine resources based on whether overlap occurs in the first time slot of a transmission occasion or segment or in a subsequent time slot. The determination may be based on any of the aspects described in connection with fig. 10-14, 18-20, and/or 22-23. This determination may be based on modified aspects of equation 1, as described herein.

At 2514, the ue may determine a location of the resources for UCI within a PUSCH transmission occasion. At 2516, the ue may populate the identified resources with UCI symbols. In some aspects, the UE may fill in resources in a frequency-first-time-second manner. At 2520, the ue identifies the remaining resources of the transmission occasion that are available for PUSCH transmission, e.g., the resources remaining after filling part of the resources of the transmission occasion with UCI. At 2522, the ue applies rate matching and interleaving based on the remaining resources. Rate matching and interleaving may be based on any of the aspects described in connection with the examples in fig. 4-24. As an example, interleaving may be per slot (as in fig. 7), per transmission occasion (as in fig. 6), or per segment (as in fig. 8). The type of rate matching and interleaving may be based on the type of transmission occasion and the manner in which 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 opportunity using PUSCH transmission by mapping the modulation symbols mapped at 2524 to the remaining resources of the transmission opportunity. At 2528, ue 2502 transmits PUSCH and multiplexed UCI to base station 2504. As illustrated at 2530, the base station may de-multiplex UCI from PUSCH to obtain information in UCI.

Fig. 26A is a flow chart 2600 of a wireless communication method. The method may be performed by a UE (e.g., UE 104, 350, 2502; device 2702). The method may enable a UE to multiplex UCI within a transmission occasion for a multi-slot PUSCH and provide a processing timeline for the UE to multiplex UCI within the multi-slot PUSCH.

At 2602, the ue applies a processing timeline to multiplex UCI in at least one slot of a multi-slot PUSCH transmission. Fig. 25 illustrates an example of the UE 2502 applying a processing timeline at 2511. The processing timeline may be based on any of the aspects described in connection with fig. 15-17, 21, and/or 24. The application of the timeline may be performed, for example, by the timeline component 2744 of the device 2702 in fig. 27.

At 2604, the ue transmits the multislot PUSCH transmission with the multiplexed UCI based on satisfying the processing timeline. Multiplexing and/or transmission may be based on any of the aspects described in connection with fig. 4-25. Fig. 25 illustrates an example in which UE 2502 transmits PUSCH and multiplexed UCI to base station 2504 at 2528. The transmission may be performed, for example, by PUSCH component 2742 of device 2702, e.g., via transmission component 2734 and/or RF transceiver 2722.

Fig. 26B is a flow chart 2650 of a wireless communication method. The method may be performed by a UE (e.g., UE 104, 350, 2502; device 2702). The method may include 2602 and 2604 as described in connection with fig. 26B.

In some aspects, the UCI may include HARQ feedback and the processing timeline may correspond to a time gap (e.g., N1) between receiving the PDSCH and the beginning of the PUCCH carrying the HARQ feedback payload for the PDSCH.

In some aspects, the UCI may include a CSI report, and the processing timeline may correspond to a time gap (e.g., Z) between a last symbol of the received CSI-RS and a beginning of a PUCCH carrying the CSI report based on measurements of the CSI-RS, e.g., as described in connection with fig. 17.

In some aspects, the UE may apply a processing timeline based on the start of the multi-slot PUSCH transmission, as illustrated at 2606. In some aspects, a multislot PUSCH transmission may be transmitted in a transmission occasion comprising a contiguous set of slots. In some aspects, the processing timeline is based on the start of a multislot PUSCH transmission according to one or more of: overlapping time slots of a multi-slot PUSCH transmission that overlap in time with UCI, multiplexing time slots in the multi-slot PUSCH transmission in which UCI is to be multiplexed, transmission occasion-based multiplexing for UCI within the multi-slot PUSCH transmission, transmission occasion-based interleaving for the multi-slot PUSCH transmission, or transmission occasion-based rate matching for the multi-slot PUSCH transmission. As an example, the timeline may be based on the beginning of a multislot PUSCH in accordance with any of the aspects described in connection with fig. 15-17.

In some aspects, the multislot PUSCH transmission may be transmitted in a transmission occasion comprising a contiguous set of slots (e.g., option (a) of fig. 4), and applying the processing timeline may include: a processing timeline based on the beginning of overlapping slots of a multi-slot PUSCH transmission is applied that overlaps and in which UCI is multiplexed, e.g., as illustrated at 2608. In some aspects, the processing timeline may be based on the beginning of overlapping slots of a multislot PUSCH transmission according to one or more of: UCI is multiplexed in overlapping slots of a multi-slot PUSCH transmission, slot-based multiplexing for UCI within a multi-slot PUSCH transmission, slot-based interleaving for a multi-slot PUSCH transmission, or slot-based rate matching for a multi-slot PUSCH transmission. Reference time S in FIG. 16 ₀₂ An example is illustrated in which the processing timeline is based on the beginning of overlapping time slots.

In some aspects, the UE may multiplex UCI from multiple PUCCHs overlapping with a multislot PUSCH. For example, as described in connection with any of fig. 18-21, the UE may multiplex the first UCI and the second UCI overlapping with the multislot PUSCH transmission. The UE may apply a processing timeline based on the start of the multislot PUSCH transmission for the first UCI and the second UCI at 2602, e.g., as by S in fig. 21 ₀₁ As shown.

In some aspects, the first UCI and the second UCI may overlap in different slots of a transmission opportunityAnd the processing timeline may be determined differently for the first UCI and the second UCI based on the respective slots of the transmission opportunity that are overlapped by the first UCI and the second UCI, e.g., as by S in fig. 21 ₀₂ As shown. In some aspects, the first UCI and the second UCI may be multiplexed across contiguous slots of a transmission opportunity.

In some aspects, a multislot PUSCH transmission may be transmitted in a transmission occasion including a non-contiguous set of slots (e.g., option (b) in fig. 4), and the processing timeline at 2610 may be based on a contiguous portion of the transmission occasion in which UCI is multiplexed. Fig. 24 illustrates an example of an overlap-based segmented processing timeline (e.g., timeline 1). The processing timeline may be based on the beginning of the contiguous portion, e.g., as by S in FIG. 21 ₀₁ As shown. In some aspects, the UE may multiplex the first UCI and the second UCI overlapping different contiguous portions of the multi-slot PUSCH transmission, and the processing timeline may be based on contiguous portions of the transmission opportunity in which the respective UCI is multiplexed.

At 2603, the ue multiplexes UCI in at least one slot of a multi-slot PUSCH transmission. As described in connection with fig. 25, the UE may determine to multiplex UCI based on resources on which to transmit UCI overlapping in time with a transmission opportunity for PUSCH transmission. Multiplexing may include any of the aspects described in connection with fig. 4-25. Multiplexing may be performed, for example, by UCI multiplexer component 2740 of device 2702 in fig. 27.

Fig. 27 is a diagram 2700 illustrating an example of a hardware implementation of the device 2702. Device 2702 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the device 2702 may include a cellular baseband processor 2704 (also referred to as a modem) coupled to a cellular RF transceiver 2722. The device 2702 may further include one or more Subscriber Identity Module (SIM) cards 2720, an application processor 2706 coupled to 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 supply 2718. The cellular baseband processor 2704 communicates with the UE 104 and/or the base stations 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 on 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 can also be used for storing data that is manipulated by the cellular baseband processor 2704 when executing software. The cellular baseband processor 2704 further includes a receiving component 2730, a communication manager 2732, and a transmitting component 2734. The communication manager 2732 includes the one or more illustrated components. Components within communication manager 2732 may be stored in a computer-readable medium/memory and/or configured as hardware within 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: a TX processor 368, an RX processor 356, and a controller/processor 359. In one configuration, the device 2702 may be a modem chip and include only the baseband processor 2704, and in another configuration, the device 2702 may be an entire UE (see, e.g., 350 of fig. 3) and include additional modules of the device 2702.

The communication manager 2732 includes a UCI multiplexer component 2740 that is configured to multiplex UCI in at least one slot of a multi-slot PUSCH transmission, e.g., as described in connection with 2603 in fig. 26B. The communication manager 2732 further includes a PUSCH component 2742 configured to: the multi-slot PUSCH transmission and multiplexed UCI are transmitted based on satisfying a processing timeline, e.g., as described in connection with 2604 in fig. 26A or 26B. The communication manager 2732 further includes a timeline component 2744 configured to: the processing timeline is applied to multiplex UCI in at least one slot of a multi-slot PUSCH transmission, e.g., as described in connection with 2602 in fig. 26A or 26B.

The apparatus may include additional components to perform each block of the algorithms in the flowcharts of fig. 26A, 26B, and/or aspects performed by the UE in fig. 25. As such, each block in the flow diagrams of fig. 26A, 26B and/or aspects performed by the UE in fig. 25 may be performed by components and the apparatus may include one or more of these components. These components may be one or more hardware components specifically configured to perform the process/algorithm, implemented by a processor configured to perform the process/algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

In one configuration, the device 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 the multislot PUSCH transmission and the multiplexed UCI based on satisfying the processing timeline. The apparatus may further comprise: means for multiplexing UCI within at least one slot of a multi-slot PUSCH transmission. The apparatus may be one or more of the components in device 2702 configured to perform the functions recited by the apparatus. As described herein, device 2702 may include TX processor 368, RX processor 356, and controller/processor 359. As such, in one configuration, the device may be a TX processor 368, an RX processor 356, and a controller/processor 359 configured to perform the functions recited by the device.

Deployment of a communication system, such as a 5G New Radio (NR) system, may have various components or constituent parts arranged in a variety of ways. In a 5G NR system or network, network nodes, network entities, mobility elements of a network, radio Access Network (RAN) nodes, core network nodes, network elements, or network equipment, such as a Base Station (BS), or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, BSs, such as Node BS (NB), evolved NB (eNB), NR BS, 5G NB, access Points (APs), transmission Reception Points (TRP), or cells, etc., may be implemented as aggregated base stations (also referred to as standalone BSs or monolithic BSs) or decomposed base stations.

The aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. The split 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 central or 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, may be geographically or virtually distributed among one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as virtual units, i.e., virtual Central Units (VCUs), virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs).

Base station type operation or network design may take into account the aggregate nature of the base station functionality. For example, the split base station may be used in an Integrated Access Backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration advocated by the O-RAN alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). The decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Each element of the split base station or split RAN architecture may be configured for wired or wireless communication with at least one other element.

Fig. 28 shows a diagram illustrating an example split base station 2800 architecture. The split 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 split base station units, such as Near real-time (Near-RT) RAN Intelligent Controllers (RIC) 2825 via E2 links, or Non-real-time (Non-RT) RIC 2815 associated with a Service Management and Orchestration (SMO) framework 2805, or both. CU 2810 can communicate with one or more Distributed Units (DUs) 2830 via respective medium range links, such as an F1 interface. DU 2830 may communicate with one or more Radio Units (RU) 2840 via respective outbound links. RU 2840 may communicate with corresponding UEs 104 via one or more Radio Frequency (RF) access links. In some implementations, the UE 104 may be served by multiple RUs 2840 simultaneously.

Each of the units (i.e., CU 2810, DU 2830, RU 2840, and near RT RIC 2825, non-RT RIC 2815, and SMO framework 2805) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively referred to as signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller that provides instructions to a communication interface of the units, may be configured to communicate with one or more of the other units via a transmission medium. For example, the units may include a wired interface configured to receive or transmit signals to one or more of the other units over a wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a Radio Frequency (RF) transceiver) configured to receive or transmit signals to one or more of the other units, or both, over a wireless transmission medium.

In some aspects, CU 2810 can host one or more higher layer control functions. Such control functions may include Radio Resource Control (RRC), packet Data Convergence Protocol (PDCP), service Data Adaptation Protocol (SDAP), etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 2810. CU 2810 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, CU 2810 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bi-directionally with the CU-CP unit via an interface, such as an E1 interface. CU 2810 can be implemented in communication with DU 2830 for network control and signaling, as desired.

DU 2830 may correspond to a logical unit including one or more base station functions to control the operation of one or more RUs 2840. In some aspects, 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 partitioning, such as that defined by the third generation partnership project (3 GPP). In some aspects, DU 2830 may further host one or more lower PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by DU 2830 or with control functions hosted by CU 2810.

The lower layer functionality may be implemented by one or more RUs 2840. In some deployments, RU 2840 controlled by DU 2830 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transforms (FFTs), inverse FFTs (iffts), digital beamforming, physical Random Access Channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional partitioning (such as lower layer functional partitioning). In such an architecture, RU(s) 2840 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, the real-time and non-real-time aspects of control and user plane communications with RU(s) 2840 may be controlled by corresponding DUs 2830. In some scenarios, this configuration may enable DU 2830(s) and CU 2810 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

SMO framework 2805 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 2805 may be configured to support deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, SMO framework 2805 may be configured to interact with a Cloud computing platform, such as open Cloud (O-Cloud) 2890, to perform network element lifecycle management (such as instantiating 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, CU 2810, DU 2830, RU 2840, and near RT RIC 2825. In some implementations, SMO framework 2805 may communicate with hardware aspects of the 4G RAN, such as open eNB (O-eNB) 2811, via an O1 interface. Additionally, in some implementations, SMO framework 2805 may communicate directly with one or more RUs 2840 via an O1 interface. SMO framework 2805 may also include a non-RT RIC 2815 configured to support the functionality of SMO framework 2805.

The non-RT RIC 2815 may be configured to include logic functions that implement RAN elements and resources, artificial intelligence/machine learning (AI/ML) workflows including model training and updating, or non-real-time control and optimization of policy-based guidance of applications/features in the near RT RIC 2825. non-RT RIC 2815 may be coupled to or communicate with a near RT RIC 2825 (such as via an A1 interface). 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 actions through an interface (such as via an E2 interface) that connects one or more CUs 2810, one or more DUs 2830, or both, and an O-eNB with near RT RIC 2825.

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

It is to be understood that the specific order or hierarchy of the various blocks in the disclosed process/flow diagrams is an illustration of an example approach. It will be appreciated that the specific order or hierarchy of blocks in the processes/flow diagrams may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more". Terms such as "if," "when … …," and "at … …" should be read to mean "under the conditions" rather than to imply a direct temporal relationship or reaction. That is, these phrases (e.g., "when … …") do not imply that an action will occur in response to or during the occurrence of an action, but rather merely that a condition is met, and do not require specific or immediate time constraints for the action to occur. The term "exemplary" is used herein to mean "serving as an example, instance, or illustration. Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects. The term "some" means one or more unless specifically stated otherwise. Combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C", and "A, B, C or any combination thereof" include any combination of A, B and/or C, and may include a plurality of a, a plurality of B, or a plurality of C. Specifically, combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C", and "A, B, C or any combination thereof" may be a alone, B alone, C, A and B, A and C, B and C, or a and B and C, wherein any such combination may comprise one or more members of A, B or C. The elements of the various aspects described throughout this disclosure are all structural and functional equivalents that are presently or later to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The terms "module," mechanism, "" element, "" device, "and the like may not be a substitute for the term" means. As such, no element of a claim should be construed as a means-plus-function unless the element is explicitly recited using the phrase "means for … …".

The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

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

In aspect 2, the method of aspect 1 further comprises: the UCI includes HARQ feedback and the processing timeline corresponds to a time gap between receiving a PDSCH and a start of a PUCCH carrying a HARQ feedback payload for the PDSCH.

In aspect 3, the method of aspect 1 further comprises: the UCI includes a CSI report, and the processing timeline corresponds to a time gap between a last symbol of a received CSI-RS and a beginning of a PUCCH carrying the CSI report based on measurements of the CSI-RS.

In aspect 4, the method of any one of aspects 1-3 further comprises: applying the processing timeline includes: the processing timeline based on the beginning of the multislot PUSCH transmission is applied.

In aspect 5, the method of any one of aspects 1-4 further comprises: the multislot PUSCH transmission is transmitted in a transmission occasion comprising a set of contiguous slots.

In aspect 6, the method of any one of aspects 1-5 further comprises: the processing timeline is based on the start of the multislot PUSCH transmission according to one or more of: overlapping time slots of the multi-slot PUSCH transmission that overlap in time with the UCI in which multiplexing time slots of the UCI are to be multiplexed within the multi-slot PUSCH transmission, transmission timing based multiplexing for the UCI within the multi-slot PUSCH transmission, transmission timing based interleaving for the multi-slot PUSCH transmission, or transmission timing based rate matching for the multi-slot PUSCH transmission.

In aspect 7, the method of any one of aspects 1-5 further comprises: the processing timeline is based on the beginning of overlapping time slots of the multi-slot PUSCH transmission according to one or more of: the UCI is multiplexed in the overlapping time slots of the multi-slot PUSCH, time slot based multiplexing for the UCI within the multi-slot PUSCH transmission, time slot based interleaving for the multi-slot PUSCH transmission, or time slot based rate matching for the multi-slot PUSCH transmission.

In aspect 8, the method of any one of aspects 1-7 further comprises: wherein multiplexing the UCI includes: the first UCI and the second UCI overlapping the multislot PUSCH transmission are multiplexed.

In aspect 9, the method of aspect 8 further comprises: the processing timeline based on the beginning of the multi-slot PUSCH transmission is applied for the first UCI and the second UCI.

In aspect 10, the method of aspect 8 further comprising: the first UCI and the second UCI overlap in different slots of a transmission occasion, and the processing timeline is determined differently for the second UCI and the second UCI based on the respective slots of the transmission occasion that are overlapped by the first UCI and the second UCI.

In aspect 11, the method of any one of aspects 1-3 further comprises: the multi-slot PUSCH transmission is transmitted in a transmission occasion comprising a set of non-contiguous slots, wherein the processing timeline is determined based on contiguous portions of the transmission occasion in which the UCI is multiplexed.

In aspect 12, the method of aspect 11 further comprising: the processing timeline is based on the beginning of the contiguous portion.

In aspect 13, the method of aspect 11 or aspect 12 further comprises: first UCI and second UCI overlapping different contiguous portions of the multi-slot PUSCH transmission are multiplexed, wherein the processing timeline is determined based on the contiguous portions of the transmission opportunity in which the respective UCI is multiplexed.

Aspect 14 is an apparatus for wireless communication at a user equipment, UE, comprising: a memory; and at least one processor coupled to the memory and configured to: applying a processing timeline to multiplex UCI in at least one slot of a multi-slot PUSCH transmission; and transmitting the multislot PUSCH transmission and the multiplexed UCI based on satisfying the processing timeline.

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

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

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

Aspect 18 is an apparatus for wireless communication at 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 the multislot PUSCH transmission and the multiplexed UCI based on satisfying the processing timeline.

In aspect 19, the apparatus for wireless communication as in aspect 18 further comprising means for performing the method as in any of aspects 2-13.

In aspect 20, the apparatus of any of aspects 18 or 19 further comprises at least one transceiver.

In aspect 21, the device of any one of aspects 18-20 further comprising at least one antenna.

Aspect 22 is a non-transitory computer-readable medium storing computer-executable code at a UE that, when executed by a processor, causes the processor to: applying a processing timeline to multiplex UCI in at least one slot of a multi-slot PUSCH transmission; and transmitting the multislot PUSCH transmission and the multiplexed UCI based on satisfying the processing timeline.

In aspect 23, the computer-readable medium of aspect 22 further comprising code that, when executed by the processor, causes the processor to perform the method of any of claims 2-13.

Claims (29)

1. A method of wireless communication at a User Equipment (UE), comprising:

applying a processing timeline to multiplex Uplink Control Information (UCI) in at least one time slot of a multi-slot Physical Uplink Shared Channel (PUSCH) transmission; and

the multi-slot PUSCH transmission and multiplexed UCI is transmitted based on satisfying the processing timeline.

2. The method of claim 1, wherein the UCI includes hybrid automatic repeat request (HARQ) feedback and the processing timeline corresponds to a time gap between receipt 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. 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 a last symbol of a received channel state information reference signal (CSI-RS) and a beginning 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 applying the processing timeline comprises:

the processing timeline based on the start of the multi-slot PUSCH transmission is applied.

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

6. The method of claim 5, wherein the processing timeline is based on a start of the multi-slot PUSCH transmission according to one or more of:

Overlapping time slots of the multi-slot PUSCH transmission that overlap in time with the UCI,

the multiplexing time slot in which the UCI is to be multiplexed in the multi-slot PUSCH transmission,

multiplexing based on transmission occasions for the UCI within the multislot PUSCH transmission,

interleaving based on transmission occasion for the multislot PUSCH transmission, or

Transmission opportunity based rate matching for the multi-slot PUSCH transmission.

7. The method of claim 5, wherein the processing timeline is based on a beginning of overlapping slots of the multi-slot PUSCH transmission according to one or more of:

the UCI is multiplexed in the overlapping slots of the multi-slot PUSCH,

time slot based multiplexing for the UCI within the multi-slot PUSCH transmission,

time slot based interleaving for the multi-slot PUSCH transmission, or

Time slot based rate matching for the multi-slot PUSCH transmission.

8. The method of claim 1, wherein multiplexing the UCI comprises:

and multiplexing a first UCI and a second UCI overlapped with the multi-slot PUSCH transmission.

9. The method of claim 8, further comprising:

the processing timeline based on the beginning of the multi-slot PUSCH transmission is applied for the first UCI and the second UCI.

10. The method of claim 8, 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 that are overlapped by the first UCI and the second UCI.

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

12. The method of claim 11, wherein the processing timeline is based on a beginning of the contiguous portion.

13. The method of claim 11, further comprising:

first UCI and second UCI overlapping different contiguous portions of the multi-slot PUSCH transmission are multiplexed, wherein the processing timeline is determined based on the contiguous portions of the transmission opportunity in which the respective UCI is multiplexed.

14. An apparatus for wireless communication at a User Equipment (UE), comprising:

a memory; and

at least one processor coupled to the memory and configured to:

Applying a processing timeline to multiplex Uplink Control Information (UCI) in at least one time slot of a multi-slot Physical Uplink Shared Channel (PUSCH) transmission; and

the multi-slot PUSCH transmission and multiplexed UCI is transmitted based on satisfying the processing timeline.

15. The apparatus of claim 14, wherein the UCI comprises hybrid automatic repeat request (HARQ) feedback and the processing timeline corresponds to a time gap between receipt 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.

16. The apparatus of claim 14, wherein the UCI comprises a Channel State Information (CSI) report and the processing timeline corresponds to a time gap between a last symbol of a received channel state information reference signal (CSI-RS) and a beginning of a Physical Uplink Control Channel (PUCCH) carrying the CSI report based on measurements of the CSI-RS.

17. The apparatus of claim 14, wherein to apply the processing timeline, the at least one processor is further configured to:

the processing timeline based on the start of the multi-slot PUSCH transmission is applied.

18. The apparatus of claim 17, wherein the multi-slot PUSCH transmission is transmitted in a transmission occasion comprising a contiguous set of slots.

19. The apparatus of claim 18, wherein the processing timeline is based on a start of the multi-slot PUSCH transmission according to one or more of:

overlapping time slots of the multi-slot PUSCH transmission that overlap in time with the UCI,

the multiplexing time slot in which the UCI is to be multiplexed in the multi-slot PUSCH transmission,

multiplexing based on transmission occasions for the UCI within the multislot PUSCH transmission,

interleaving based on transmission occasion for the multislot PUSCH transmission, or

Transmission opportunity based rate matching for the multi-slot PUSCH transmission.

20. The apparatus of claim 18, wherein the processing timeline is based on a beginning of overlapping slots of the multi-slot PUSCH transmission according to one or more of:

the UCI is multiplexed in the overlapping slots of the multi-slot PUSCH transmission,

time slot based multiplexing for the UCI within the multi-slot PUSCH transmission,

time slot based interleaving for the multi-slot PUSCH transmission, or

Time slot based rate matching for the multi-slot PUSCH transmission.

21. The apparatus of claim 14, wherein to multiplex the UCI, the at least one processor is further configured to:

and multiplexing a first UCI and a second UCI overlapped with the multi-slot PUSCH transmission.

22. The apparatus of claim 21, in which the at least one processor is further configured:

the processing timeline based on the beginning of the multi-slot PUSCH transmission is applied for the first UCI and the second UCI.

23. The apparatus of claim 21, 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 that are overlapped by the first UCI and the second UCI.

24. The apparatus of claim 14, wherein the multi-slot PUSCH transmission is in a transmission occasion comprising a non-contiguous set of slots, wherein the processing timeline is based on a contiguous portion of the transmission occasion in which the UCI is multiplexed.

25. The apparatus of claim 24, wherein the processing timeline is based on a beginning of the contiguous portion.

26. The apparatus of claim 24, in which the at least one processor is further configured:

first UCI and second UCI overlapping different contiguous portions of the multi-slot PUSCH transmission are multiplexed, wherein the processing timeline is determined based on the contiguous portions of the transmission opportunity in which the respective UCI is multiplexed.

27. The apparatus of claim 14, further comprising:

at least one transceiver coupled to the at least one processor.

28. An apparatus for wireless communication at a User Equipment (UE), comprising:

means for applying a processing timeline to multiplex Uplink Control Information (UCI) in at least one time slot of a multi-slot Physical Uplink Shared Channel (PUSCH) transmission; and

means for transmitting the multi-slot PUSCH transmission with multiplexed UCI based on satisfying the processing timeline.

29. A non-transitory computer-readable medium storing computer executable code at a User Equipment (UE), which when executed by a processor, causes the processor to:

applying a processing timeline to multiplex Uplink Control Information (UCI) in at least one time slot of a multi-slot Physical Uplink Shared Channel (PUSCH) transmission; and

The multi-slot PUSCH transmission and multiplexed UCI is transmitted based on satisfying the processing timeline.