Timeline for multiplexing of uplink control information on multiple-slot transmissions

Abstract

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

Description

[Technical Field]

[0001] Cross-reference of related applications

[0001] This application claims the benefits and priority of U.S. Provisional Application No. 63 / 166,961, filed on 26 March 2021, entitled “Timelines for Uplink Control Information Multiplexing Over Multiple Slot Transmissions,” and U.S. Non-Provisional Patent Application No. 17 / 656,209, filed on 23 March 2022, entitled “Timelines for Uplink Control Information Multiplexing Over Multiple Slot Transmissions.”

[0002]

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

[0003]

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunications services, including telephone, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies that enable communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0004]

[0004] These multiple access technologies are employed in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at urban, national, regional, and even global levels. An exemplary telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuing Mobile Broadband Development announced by the Third Generation Partnership Project (3GPP®) to satisfy new requirements related to latency, reliability, security, scalability (for example, related to the Internet of Things (IoT)), and other requirements. 5G NR includes services related to Enhanced Mobile Broadband (eMBB), Massive Machine Type Communications (mMTC), and Ultra-High Reliability Low Latency Communications (URLLC). Some aspects of 5G NR can be based on the 4G Long-Term Evolution (LTE®) standard. Further improvements to 5G NR technology are needed. These improvements may also be applicable to other multiple access technologies and the telecommunications standards that employ these technologies. [Overview of the Initiative]

[0005]

[0005] The following provides a simplified overview of one or more embodiments in order to provide a basic understanding of such embodiments. This overview is not a comprehensive overview of all intended embodiments, nor does it identify the main or important elements of all embodiments, nor does it define the scope of any or all embodiments. Its sole purpose is to present some concepts of one or more embodiments in a simplified form as an introduction to the more detailed explanations to be presented later.

[0006]

[0006] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus applies a processing timeline to multiplex uplink control information (UCI) in at least one slot of a multiple slot physical uplink shared channel (PUSCH) transmission. Based on the fulfillment of the processing timeline, the apparatus transmits the multiple slot PUSCH transmission together with the multiplexed UCI.

[0007]

[0007] In order to achieve the above-mentioned and related objectives, one or more embodiments shall have features that are fully described below and, in particular, indicated in the claims. The following description and accompanying drawings illustrate in detail some exemplary features of one or more embodiments. However, these features represent only a few of the various ways in which the principles of the various embodiments may be employed, and this description shall include all such embodiments and their equivalents. [Brief explanation of the drawing]

[0008] [Figure 1]

[0008] A diagram illustrating an example of a wireless communication system and access network according to various aspects of the present disclosure. [Figure 2A]

[0009] A diagram illustrating an example of the first frame according to various aspects of this disclosure. [Figure 2B]

[0010] A diagram illustrating an example of a DL channel within a subframe according to various aspects of this disclosure. [Figure 2C]

[0011] A diagram illustrating an example of a second frame according to various aspects of this disclosure. [Figure 2D]

[0012] A diagram illustrating an example of a UL channel within a subframe according to various aspects of this disclosure. [Figure 3]

[0013] A diagram showing an example of a base station and a user equipment (UE) in an access network according to various aspects of the present disclosure. [Figure 4]

[0014] A diagram showing various options of transmission opportunities for multi-slot PUSCH transmission according to various aspects of the present disclosure. [Figure 5A]

[0015] A diagram showing an exemplary aspect of a redundancy version (RV) cycle for multiple transmission opportunities of multi-slot PUSCH according to various aspects of the present disclosure. [Figure 5B] A diagram showing an exemplary aspect of a redundancy version (RV) cycle for multiple transmission opportunities of multi-slot PUSCH according to various aspects of the present disclosure. [Figure 6]

[0016] A diagram showing an exemplary aspect of transmission opportunity-based interleaving for multi-slot PUSCH transmission according to various aspects of the present disclosure. [Figure 7]

[0017] A diagram showing an exemplary aspect of slot-based interleaving for multi-slot PUSCH transmission according to various aspects of the present disclosure. [Figure 8]

[0018] A diagram showing an exemplary aspect of segment-based interleaving for multi-slot PUSCH transmission in a transmission opportunity having discontinuous segments of resources according to various aspects of the present disclosure. [Figure 9]

[0019] A diagram showing an example of UCI that temporally overlaps with a transmission opportunity having continuous resources for multi-slot PUSCH transmission according to various aspects of the present disclosure. [Figure 10]

[0020] A diagram showing an example of multiplexing UCI in overlapping slots of a transmission opportunity having continuous resources for multi-slot PUSCH transmission according to various aspects of the present disclosure. [Figure 11]

[0021] A diagram illustrating an example of multiplexing UCI across transmission occasions with continuous resources for multi-slot PUSCH transmissions according to various aspects of this disclosure. [Figure 12]

[0022] A diagram illustrating an example of multiplexing UCI in overlapping slots of transmission occasions with consecutive resources for multi-slot PUSCH transmissions according to various aspects of this disclosure. [Figure 13]

[0023] A diagram illustrating an example of multiplexing UCI on a transmission occasion with continuous resources for multi-slot PUSCH transmissions according to various aspects of this disclosure. [Figure 14]

[0024] A diagram illustrating an example of multiplexing UCI iterations in transmission occasions with continuous resources for multi-slot PUSCH transmissions according to various aspects of this disclosure. [Figure 15]

[0025] A diagram illustrating exemplary processing timeline considerations for multiplexing UCI with multiple slot push transmissions according to various aspects of this disclosure. [Figure 16]

[0026] A diagram illustrating exemplary processing timeline considerations for multiplexing UCI with multiple slot push transmissions according to various aspects of this disclosure. [Figure 17]

[0027] A diagram illustrating exemplary processing timeline considerations for multiplexing UCI with multiple slot push transmissions according to various aspects of this disclosure. [Figure 18]

[0028] A figure illustrating an example of multiple UCIs overlapping with transmission occasions having continuous resources for multi-slot PUSCH transmissions according to various aspects of this disclosure. [Figure 19]

[0029] A diagram illustrating an example of multiplexing multiple UCIs that overlap with transmission occasions for multi-slot push transmissions, according to various aspects of this disclosure, for each overlapping slot. [Figure 20]

[0030] A diagram illustrating an example of multiplexing multiple UCIs that overlap with transmission occasions for multi-slot PUSCH transmissions, according to various aspects of this disclosure. [Figure 21]

[0031] A diagram illustrating exemplary processing timeline considerations for multiplexing UCIs from multiple PUCCHs with multiple slot PUSCH transmissions, according to various aspects of this disclosure. [Figure 22]

[0032] A figure illustrating an example of a UCI that temporally overlaps with a transmission occasion having a discontinuous segment of resources for a multi-slot PUSCH transmission according to various aspects of this disclosure. [Figure 23]

[0033] This figure illustrates an example of multiplexing UCIs segment by segment for multiple-slot push transmissions that have discontinuous segments of resources for transmission occasions. [Figure 24]

[0034] A diagram illustrating exemplary processing timeline considerations for multiplexing UCI with multiple-slot push transmissions in transmission occasions having discontinuous segments, according to various aspects of this disclosure. [Figure 25]

[0035] Exemplary communication flows between a UE and a base station, including examples of the application of processing timelines for multiplexing and multiplexing of multiple-slot push transmissions according to various aspects of this disclosure. [Figure 26A]

[0036] A flowchart of a wireless communication method, including examples of applying a processing timeline for multiple-slot push transmission and multiplexing according to various aspects of the present disclosure. [Figure 26B] A flowchart of a wireless communication method, including examples of applying a processing timeline for multiple-slot push transmission and multiplexing according to various aspects of the present disclosure. [Figure 27]

[0037] A figure illustrating an example of a hardware implementation for an exemplary device according to various aspects of this disclosure. [Figure 28]

[0038] A diagram illustrating an exemplary disaggregated base station architecture. [Modes for carrying out the invention]

[0009]

[0039] A UE may transmit a PUSCH over a transmit occasion spanning multiple slots. A UE may transmit a single TB within multiple slots of a transmit occasion. Occasionally, a UE may have uplink control information (UCI) for a transmit on a physical uplink control channel (PUCCH) that temporally overlaps with a transmit occasion for a PUSCH. Based on the temporal overlap, the UE may multiplex the UCI with the PUSCH. The embodiments presented herein provide various methods for a UE to multiplex a UCI with a multi-slot PUSCH. Multiplexing embodiments, including any combination of the number of resources for the UCI, the location for the UCI, the multiplexing handling, the timeline, the PUSCH rate matching, and / or the PUSCH interleaving, may vary based on the type of transmit occasion (e.g., continuous or discontinuous). Multiplexing embodiments may vary based on the slots of the overlapping PUSCH transmit occasions. Multiplexing embodiments may vary based on the type of PUSCH handling, e.g., per-slot, per-transmit occasion, or per-segment interleaving and RV cycles.

[0010]

[0040] The modes for carrying out the invention described below with respect to the attached drawings are intended to describe various configurations and are not intended to represent only configurations in which the concepts described herein can be put into practice. The modes for carrying out the invention include specific details to provide a complete understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be put into practice without these specific details. In some cases, well-known structures and components are shown in the form of block diagrams to avoid obscuring such concepts.

[0011]

[0041] Next, several embodiments of telecommunications systems are presented with respect to various devices and methods. These devices and methods are described in embodiments for carrying out the following inventions and are shown in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0012]

[0042] For example, an element, or any part of an element, or any combination of elements, may be implemented as a “processing system” comprising 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-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout this disclosure. One or more processors in a processing system may execute software. Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., regardless of the names used, such as software, firmware, middleware, microcode, and hardware description languages.

[0013]

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

[0014]

[0044] While embodiments and implementations are described herein by description of several examples, those skilled in the art will understand that additional implementations and use cases may occur in many different configurations and scenarios. The embodiments described herein can be implemented across many different platform types, devices, systems, forms, sizes, and packaging configurations. For example, implementations and / or uses may occur through integrated chip implementations and other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Some examples may or may not specifically target use cases or applications, but a wide range of applicable combinations of the embodiments described may be possible. Implementations may range from chip-level or modular components to non-modular non-chip-level implementations, and even to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more embodiments of the embodiments described. In some practical settings, devices incorporating the embodiments and features described may also include additional components and features for the implementation and practice of the claimed and described embodiments. For example, wireless signal transmission and reception will inevitably include several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, (one or more) processors, interleavers, adders, etc.). The embodiments described herein are intended to be practiced in a wide variety of devices of different sizes, shapes and structures, chip-level components, systems, distributed configurations, aggregated or disaggregated components, end-user devices, and the like.

[0015]

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

[0016]

[0046] A wireless communication system (also called a Wireless Wide Area Network (WWAN)) includes a base station 102, a UE 104, an Advanced Packet Core (EPC) 160, and another core network 190 (for example, a 5G core (5GC)). Base station 102 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macrocells include base stations. Small cells include femtocells, picocells, and microcells.

[0017]

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

[0018]

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

[0019]

[0049] The access network may include one or more IAB nodes 111 that exchange wireless communications with UE 104 or other integrated access and backhaul (IAB) nodes 111 to provide access to and backhaul of the core network. In an IAB network of multiple IAB nodes, the anchor node is sometimes called the 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 over one or more IAB nodes 111. The IAB donor may include CU 106 and DU 105. The IAB node 111 may include DU 105 and mobile termination (MT). The DU 105 of the IAB node 111 may act as the parent node, and the MT may act as the child node.

[0020]

[0050] Base station 102 can communicate wirelessly with UE 104. Each base station 102 can provide communication coverage to its respective geographical coverage area 110. There may be overlapping geographical coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network containing both small cells and macro cells may be known as a heterogeneous network. A heterogeneous network may also include home-evolved node B (eNB) (HeNB) that can serve a limited group known as a limited subscriber group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) transmissions from UE 104 to base station 102 (also called a reverse link) and / or downlink (DL) transmissions from base station 102 to UE 104 (also called a forward link). Communication link 120 may use multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be through one or more carriers. Base station 102 / UE104 may use the spectrum of the highest Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) bandwidth per carrier, allocated in carrier aggregation of the highest total Yx MHz (x component carriers) used for transmission in each direction. Carriers may be adjacent or not adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​than for UL). Component carriers may include primary component carriers and one or more secondary component carriers. Primary component carriers may be called primary cells (PCells), and secondary component carriers may be called secondary cells (SCells).

[0021]

[0051] Some UE104s may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication may be through various wireless D2D communication systems, such as WiMedia, Bluetooth®, ZigBee®, Wi-Fi® based on the IEEE 802.11 standard, LTE, or NR.

[0022]

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

[0023]

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

[0024]

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

[0025]

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

[0026]

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

[0027]

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

[0028]

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

[0029]

[0059] EPC160 may include a Mobility Management Entity (MME) 162, another MME 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. MME 162 may communicate with a Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC160. Generally, MME 162 provides bearer and connectivity management. All user Internet Protocol (IP) packets are forwarded through the Serving Gateway 166, which itself connects to the PDN Gateway 172. The PDN Gateway 172 provides IP address allocation for the UE and other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Service 176. IP service 176 may include the Internet, intranet, IP multimedia subsystem (IMS), PS streaming service, and / or other IP services. BM-SC170 may provide functionality for MBMS user service provisioning and distribution. BM-SC170 may act as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. 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 specific services, and may be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0030]

[0060] The core network 190 may include Access and Mobility Management Function (AMF) 192, other AMFs 193, Session Management Function (SMF) 194, and User Plane Function (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is a control node that handles signaling between UE 104 and the core network 190. Generally, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are forwarded through UPF 195. UPF 195 provides IP address allocation for the UE and other functions. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switched (PS) Streaming (PSS) services, and / or other IP services.

[0031]

[0061] Base stations include and / or may be referred to as gNB, node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit / receive point (TRP), or any other preferred term. Base station 102 provides UE104 with an access point to EPC160 or core network 190. Examples of UE104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some of UE104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, cardiac monitors, etc.). The UE104 may also be referred to as station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or any other preferred term.

[0032]

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

[0033]

[0063] Figures 2A to 2D show the frame structure, and aspects of this 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 subframes (1 ms) of equal size. Each subframe may contain one or more time slots. A subframe may also contain minislots that may contain 7, 4, or 2 symbols. Depending on whether the cyclic prefix (CP) is normal or extended, each slot may contain 14 or 12 symbols. For a normal CP, each slot may contain 14 symbols, and for an extended CP, each slot may contain 12 symbols. Symbols on the DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. Symbols on a UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Spread OFDM (DFT-s-OFDM) symbols (also called Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-limited scenarios limited to single-stream transmissions). The number of slots within a subframe is based on CP and numerology. Numerology defines the subcarrier spacing (SCS) and the symbol length / duration, which is effectively equal to 1 / SCS.

[0034] [Table 1]

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

[0036]

[0064] A resource grid may be used to represent the frame structure. Each time slot contains RBs (also called physical resource blocks (RBs) (PRBs)) that extend 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0037]

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

[0038]

[0066] Figure 2B shows an example of various DL channels within a subframe of a frame. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., one, two, four, eight, or sixteen CCEs), each CCE containing six RE groups (REGs), each REG containing twelve consecutive REs within the OFDM symbol of the RB. A PDCCH within a single BWP may be called a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of the frame. The PSS is used by the UE104 to determine subframe / symbol timing and physical layer identification information. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identification information group number and radio frame timing. Based on the physical layer identification information and physical layer cell identification information group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) may be logically grouped using the PSS and SSS to form synchronization signal (SS) / PBCH blocks (also called SS blocks (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as the system information block (SIB), and paging messages.

[0039]

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

[0040]

[0068] Figure 2D shows an example of various UL channels within a frame subframe. In one configuration, the PUCCH may be located as shown. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic retransmission request (HARQ) acknowledgment (ACK) (HARQ-ACK) information (ACK / negative ACK (NACK)) feedback. The PUCCH may carry data and may be further used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0041]

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

[0042]

[0070] The transmit (TX) processor 316 and the receive (RX) processor 370 implement Layer 1 functions related to various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., 2-phase shift keying (BPSK), 4-phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). Coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier to generate a physical channel that carries a time-domain OFDM symbol stream, multiplexed with a reference signal (e.g., a pilot) in the time-domain and / or frequency-domain, and then synthesized with each other using an inverse fast Fourier transform (IFFT). The OFDM streams are spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine the coding and modulation scheme, as well as for spatial processing. Channel estimates can be derived from the reference signal and / or channel state feedback transmitted by UE350. Each spatial stream can then be provided to different antennas 320 via a separate transmitter 318TX. Each transmitter 318TX can modulate RF carriers on its respective spatial stream for transmission.

[0043]

[0071] In UE350, each receiver 354RX receives signals through its respective antenna 352. Each receiver 354RX reconstructs the information modulated on the RF carrier and provides that information to the receiver (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functions related to various signal processing functions. The RX processor 356 may perform spatial processing on the information to reconstruct any spatial stream destined for UE350. If multiple spatial streams are destined for UE350, those spatial streams may be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then uses a Fast Fourier Transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal has a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are reconstructed and demodulated by determining the most likely signal constellation point transmitted by the base station 310. These soft decisions are obtained based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals initially transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller / processor 359, which implements Layer 3 and Layer 2 functions.

[0044]

[0072] The controller / processor 359 may be associated with memory 360, which stores program code and data. Memory 360 is sometimes referred to as computer-readable media. In UL, the controller / processor 359 provides multiplex isolation between transport and logical channels, packet reassembly, decoding, header decompression, and control signal processing to reconstruct IP packets from the EPC160. The controller / processor 359 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operation.

[0045]

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

[0046]

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

[0047]

[0075] UL transmission is processed at base station 310 in a manner similar to that described for receiver functions in UE350. Each receiver 318RX receives the signal through its respective antenna 320. Each receiver 318RX reconstructs the information modulated on the RF carrier and provides that information to RX processor 370.

[0048]

[0076] The controller / processor 375 may be associated with memory 376, which stores program code and data. Memory 376 is sometimes referred to as computer-readable media. In UL, the controller / processor 375 provides multiplex isolation between transport and logical channels, packet reassembly, decoding, header decompression, and control signal processing to reconstruct IP packets from the UE350. IP packets from the controller / processor 375 may be supplied to the EPC160. The controller / processor 375 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operation.

[0049]

[0077] At least one of the TX processor 368, RX processor 356, and controller / processor 359 may be configured to implement an embodiment relating to the UCI multiplexer component 198 shown in Figure 1.

[0050]

[0078] At least one of the TX processor 316, RX processor 370, and controller / processor 375 may be configured to implement an embodiment relating to the multiplexed UCI receiver component 199 shown in Figure 1.

[0051]

[0079] A PUSCH can be transmitted across multiple slots as a multi-slot PUSCH transmission. A PUSCH transmission can span multiple transmission occasions. A transmission occasion may include uplink resources, such as uplink slots, that have resources allocated to the UE for transmitting PUSCH. Figure 4 shows Figure 400 illustrating two different options for multi-slot PUSCH transmissions. Figure 4 also shows an exemplary slot pattern 406, such as a TDD uplink / downlink slot pattern. For example, in the first option, shown as option (a) in Figure 4, each transmission occasion of a multi-slot PUSCH transmission includes a contiguous resource (e.g., a contiguous symbol or contiguous slot) spanning one or more slots, as shown for transmission occasion 402, for example. In some embodiments, the contiguous resource may include a contiguous symbol spanning two different slots. Figure 4 shows that the contiguous resource of each transmission occasion may be separated by resources that are not part of the PUSCH transmission, such as downlink slots. For example, in the second option, shown as option (b) in Figure 4, each transmission occasion may include discontinuous resources. Discontinuous resources may include multiple sets of continuous resources, as shown for transmission occasion 404.

[0052]

[0080] The Time-Domain Resource Allocation (TDRA) for a multi-slot push transmit occasion provides a set of consecutive or non-consecutive symbols for the transmit occasion. For a transmit occasion with consecutive resources, e.g., option (a) in Figure 4, the TDRA may be shown as a pair of a start symbol (S) for the consecutive resource and the length (L) of the consecutive resource for the transmit occasion, e.g., pair (S,L). Figure 4 shows an example of (S,L)=(0,20) to illustrate the concept. S=0 may correspond to the first symbol of the uplink slot for uplink permission, and L=20 may correspond to a length of 20 symbols. For a transmit occasion with non-consecutive resources, e.g., option (b) in Figure 4, the TDRA may be shown as a triplet of (D,S,L), where D further indicates the slot index relative to the reference slot. The reference slot may be the slot from which the UE receives a DCI with uplink permission from the base station. The reference slot may be the slot indicated by DCI as the beginning of a transmit occasion, which may be referenced by parameter K2. Figure 4 shows an example of (D,S,L)={(0,0,28),(5,0,28)} to illustrate the concept. In the first triplet, D=0 may indicate that the transmit occasion begins 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 transmit occasion begins 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 represents the first set of continuous resources, and the second triplet represents the second set of continuous resources, which are discontinuous from each other. L may be the same in both triplets, as in this example. In other embodiments, the set of continuous resources forming the discontinuous resources of a transmission occasion may have different lengths.

[0053]

[0081] A single transport block (TB) of PUSCH may be transmitted in a transmit occasion. If repeatability is enabled, the TB may be transmitted over multiple transmit occasions. Thus, multi-slot PUSCH repeats may occur over a set of transmit occasions, and each repeat of the TB may be transmitted within a single transmit occasion. Figure 5A shows an example of four repeats of a PUSCH TB in four transmit occasions of a continuous resource, according to option (a), and an example of two repeats of a PUSCH TB in two transmit occasions including a discontinuous set of resources, according to option (b). In some embodiments, the repeat coefficient may be indicated to the UE by the base station, for example, along with the TDRA for multi-slot PUSCH transmissions. The repeat coefficient may indicate the quantity of repeats to the UE. In some embodiments, along with the TDRA, the base station may indicate to the UE a periodicity or offset parameter, which may indicate the interval between repeats to the UE. For example, the base station may indicate the inter-repeat gap in a symbol or slot. Figure 5A shows an exemplary inter-repeat gap 502 for option (a). A gap may, for example, represent a temporal separation between the end of one transmission occasion and the beginning of the next transmission occasion, or between the beginning of one transmission occasion and the beginning of the next transmission occasion.

[0054]

[0082] Figures 5A and 5B illustrate different examples of redundant version (RV) cycles across iterations of a TB transmitted as a multi-slot push transmit. The examples in Figures 5A and 5B correspond to the same source payload for a TB and may demonstrate that the same source payload can be encoded differently across resources in transmit occasions. In Figure 500 in Figure 5A, the RV is refreshed, for example, modified, between transmit occasions, for example, in gap 502. In Figure 5A, RV0 is applied to a contiguous resource in the first transmit occasion. The RV index is changed to RV2 in the subsequent transmit occasion. The RV index is then changed to RV3 and RV1 for subsequent transmit occasions. Similarly, for transmit occasions with discontinuous resource sets in option (b), the RV index is similarly maintained across the discontinuous resource set of a single transmit occasion and modified or refreshed for subsequent transmit occasions. The examples shown are for the transmission of a TB on a single transmit occasion. Therefore, RV cycles across iterations of TB in different transmission occasions.

[0055]

[0083] Figure 5B shows Figure 550 in which the RV can cycle within individual transmit occasions, rather than between transmit occasions as in Figure 5A. As shown for option (b) in Figure 5B, a single RV index may be used on a set of consecutive symbols in discontinuous transmit occasions, and may be changed to a different RV index in subsequent sets of consecutive symbols within the same transmit occasion. Thus, the RV can be refreshed or changed in gaps between consecutive resources in a single transmit occasion. As shown for option (a) in Figure 5B, a single RV index may be used on symbols in a single slot, and a different RV index may be applied to symbols in subsequent slots of the transmit occasion. Thus, the RV can be refreshed or changed at slot boundaries in a single transmit occasion.

[0056]

[0084] The embodiments presented herein may be applied to multi-slot push transmissions using a single codebook. In some examples, the embodiments presented herein may be applied to multi-codebook push transmissions. However, multi-codebook push transmissions may provide less gain compared to single-codebook implementations. In some embodiments, the TB size may range from approximately 100 bits to 1000 bits, but the embodiments may also be applied to TB sizes smaller or larger than that range.

[0057]

[0085] When a UE sends a PUSCH that spans multiple slots, the UE may know / remember the state of the transmission across the slots. In some embodiments, the state may refer to the state of the last transmitted bit. If the UE interleaves PUSCH transmissions, it may be difficult for the UE to send PUSCHs across slots or across discontinuous symbols. For example, the UE may use information about how much of the interleaved sequence has been transmitted and / or remember the sequence that has not been transmitted. To simplify the operation of the UE, the UE may, for example, apply interleaving within a slot.

[0058]

[0086] Figure 6 shows Figure 600, which illustrates an exemplary embodiment of interleaving TBs for multiple slot PUSCH transmissions. Figure 6 shows, for example, a pattern of transmission occasions for consecutive resources, similar to option (a) in Figure 4. TBs may be transmitted within a single transmission occasion, such as in slot 0, e.g., 604, and slot 1, e.g., 606, of transmission occasion 602. The UE may read the TB information bits from the circular buffer based on the starting position indicated by the RV index, for example, as shown in 610. The TB information bits may start, for example, at RB0. The rate matching bits read from the circular buffer are shown in 620. Rate matching may involve a process that determines the number of coded bits that can be transmitted on the available resources for a PUSCH transmission. 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 coded bits may then be read from the circular buffer. As used herein, “rate matching bits” refers to coded bits selected for transmission based on rate matching requirements and / or principles. The bit amount may, in some embodiments, be selected based on the bit amount for rate matching the TB within the transmission occasion 602. After reading the bits, the UE may apply interleaving to the bits. For example, channel coding processing for PUSCH transmission may include bit-level interleaving for each CB of the TB. Figure 6 shows an example of row-column interleaving, where bits are organized into multiple columns, for example, they may be read or placed. Figure 6 shows a first row 630 and a second row 632. The bits are then read from the two rows (e.g., 630, 632) based on their columns. Thus, the bits from the first column of row 630 correspond to bit 640 for transmission in slot 0. The bits from the first column of row 632 correspond to bit 642 for transmission in slot 0.The process is as follows: the bit in the second column of row 630 is placed at 644, followed by the bit in the second column of row 632 being placed at 646, and so on. Bits for rate matching across the entire transmit occasion may be interleaved and transmitted, as shown in Figure 6, which illustrates the interleaving applied across slots 0 and 1 of transmit occasion 602. In other embodiments, bits for rate matching may be selected slot by slot and interleaved slot by slot before transmission, as shown in Figure 7. Figure 7 shows Figure 700, which illustrates that bits for slot 0 may be read in rows 730 and 732, and bits for slot 1 may be read in rows 734 and 736. In that case, the bits for slot 0 are read in column form from rows 730 and 732 to form a slot-based interleaved pattern 740 for slot 0, and the bits for slot 1 are read in column form from rows 734 and 736 to form a slot-based interleaved pattern 742 for slot 1.

[0059]

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

[0060]

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

[0061]

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

[0062]

[0090] As in Figure 7, if the UE rate-matches and interleaves bits slot by slot, the UE may use the starting position in the circular buffer for each slot. The UE may not need to buffer the interleaved bits and instead may save the circular buffer. Slot-by-slot rate matching and interleaving may provide the UE with improved timeline, resource management, and / or memory management. In some embodiments, UCI may be multiplexed with PUSCH. UCI multiplexing may be considered slot by slot, for example, based on the overlap between the slots where UCI should be transmitted and the slots where PUSCH should be transmitted. In some embodiments, the timeline may be tied to a different reference point than the start of multi-slot PUSCH transmissions.

[0063]

[0091] As illustrated in the example in Figure 8, in order to rate-match and interleave bits segment by segment, the UE may remember the starting position in the circular buffer for each segment, for example, without buffering the interleaved bits, similar to slot-based interleaving.

[0064]

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

[0065]

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

[0066]

[0094] In some embodiments, a UE may have a UCI for transmissions that overlap with multi-slot PUSCH transmissions. The UE may multiplex the UCI with the PUSCH transmissions. The UCI may be scheduled within a slot, and the PUSCH may span multiple slots. The embodiments presented herein enable the UE to determine how many resources are allocated for the PUSCH for use for the UCI, the location of the UCI within the PUSCH, coding and rate matching for the PUSCH with multiplexed UCI, and so on.

[0067]

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

[0068]

[0096] For each transmit occasion where one of several slots in a contiguous resource for a transmit occasion temporally overlaps with a PUCCH resource for a UCI transmit, the UE may consider whether to multiplex PUCCH, e.g., UCI, in the transmit occasion's resource.

[0069]

[0097] The UE may consider, for example, whether to multiplex the PUCCH UCI within the overlapping slot rather than within another slot of the transmit occasion. In some embodiments, the timeline for multiplexing the UCI may be based on the overlapping slot, for example, slot 906 in Figure 9. In other embodiments, the timeline for multiplexing the UCI may be based on the start of transmit occasion 902.

[0070]

[0098] The UE may consider whether the UCI of PUCCH should be multiplexed on the transmit occasion, rather than being limited to slots that overlap with the UCI. The timeline for multiplexing the UCI may be based on the start of transmit occasion 902.

[0071]

[0099] Table 1 shows examples of various scenarios (e.g., Examples 1-5) illustrating different combinations of considerations for multiplexing UCI with multiple slot push transmissions for consecutive resource transmission occasions (e.g., Option (a) in Figure 4).

[0072] [Table 2]

[0073]

[0100] Figure 10 shows an exemplary Figure 1000 of Example 1 from Table 1, where UCI 1008 overlaps in slot 0 (e.g., slot 1004) of transmission occasion 1002, which has consecutive resources in slots 1004 and 1006. The UCI overlaps in slot 0 and is multiplexed in slot 0 of transmission occasion 1002. Figure 10 shows that the resources of the UCI may reside in a single slot, e.g., slot 0 1004. Slot 0 may also contain other transmissions in the slot's symbol. For example, the UCI may be transmitted following a DMRS transmission.

[0074]

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

[0075]

[0102] In contrast, in the case of a multi-slot PUSCH transmission based on the example in Figure 10, the UE could instead determine the number of REs potentially available for UCI across the PUSCH symbols in a particular slot of the transmission occasion (e.g., slot 0 1004) by dividing by the total number of PUSCH bits after scaling by a coefficient based on the number of symbols in slot 0, which is divided by the total number of PUSCH symbols in the transmission occasion.

[0076]

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

[0077]

number

[0078] The number of coded modulation symbols per layer for HARQ-ACK transmissions, as shown below, can be determined as follows:

[0079]

number

[0080]

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

[0081]

number

[0082] This represents the scheduled bandwidth of a push transmission, expressed as the number of subcarriers.

[0083]

number

[0084] In PUSCH transmission,

[0085]

number

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

[0087]

number

[0088] This is the total number of OFDM symbols in a push transmission, including all OFDM symbols used for DMRS.

[0089]

number

[0090] α is the number of subcarriers in the OFDM symbol l that carries PTRS in a PUSCH transmission. α is comprised of higher-layer parameters, such as scaling parameters. In this example, l0 is the symbol index of the first OFDM symbol that does not carry DMRS in a PUSCH transmission, after the first DMRS symbol (one or more) in the PUSCH transmission.

[0091]

number

[0092] This is the beta offset.

[0093]

[0105] Therefore, in this single-slot PUSCH example, in Equation 1

[0094]

number

[0095] This can correspond to the total number of PUSCH bits, in Equation 1.

[0096]

number

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

[0098]

[0106] In contrast, in the case of the multi-slot PUSCH transmission occasion shown in Figure 10, Equation 1

[0099]

number

[0100] This may correspond to the number of REs potentially available for UCI1008 across the PUSCH symbol in slot 0 1004, in Equation 1.

[0101]

number

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

[0103]

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

[0104]

[0108] Figure 11 shows PUCCH (e.g., UCI1108) which overlaps with PUSCH1110 in slot 0 1104 of transmission occasion 1102 and is multiplexed based not only on the overlapping slot but also on transmission occasion 1102. Figure 11 corresponds to Example 2 in Table 1, where the overlapping slot is slot 0 and the multiplexing is based on the transmission occasion. As shown in Figure 11, the resources for multiplexing UCI1108 can extend to multiple slots.

[0105]

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

[0106]

number

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

[0108]

number

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

[0110]

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

[0111]

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

[0112]

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

[0113]

[0113] For example, in Equation 1

[0114]

number

[0115] This may correspond to the number of REs potentially available for UCI1208 across the PUSCH symbols in slot 1 1206, in Equation 1.

[0116]

number

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

[0118]

[0114] After determining the number of resources to be used for UCI 1208 in slot 1 in Figure 12, the UE may identify the location of the UCI resources in slot 1 1204. The UE may then fill the identified resources in slot 1 1204 with UCI symbols. The UE may fill the resources in frequency 1, time 2 mode. The UE may use the remaining resources in slot 1 1206 to determine the PUSCH rate matching bits. The UE may determine the rate-matched bits for slot 1 based on where the slot 0 transmission ended. The UE may then interleave the rate-matched bits. As shown in Table 1, the rate matching and interleaving and / or RV cycles for Example 3 may be either per slot (as described with respect to Figure 7, for example) or per transmission occasion (as described with respect to Figure 6, for example). After interleaving, the UE may fill the identified resources for PUSCH1210 with interleaved bits mapped to modulation symbols.

[0119]

[0115] Figure 13 shows a PUCCH (e.g., UCI 1308) that overlaps with slot 1 1306 of transmission occasion 1302 for PUSCH 1310, rather than the first slot 1304 of transmission occasion 1302, as in Figures 10 and 11. In contrast to Figure 12, in Figure 13 the UCI is multiplexed based on the transmission occasion rather than the overlapping slot. Thus, in Figure 12 the UCI is multiplexed in slot 0 1304, and not necessarily in the overlapping slot. In some embodiments, the multiplexed UCI may extend to multiple slots. Figure 13 may correspond to Example 4 in Table 1.

[0120]

[0116] In the example in Figure 13, the UE may determine the resources for the UCI 1308 based on the resources available in the transmission occasion 1302. For example, in the multi-slot PUSCH transmission occasion 1302 in Figure 13, Equation 1

[0121]

number

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

[0123]

number

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

[0125]

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

[0126]

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

[0127]

[0119] Figure 15 shows a representation of a timeline consideration for multiplexing a UCI in a multi-slot PUSCH transmission. As shown in Figure 15, the UE may consider multiplexing a UCI for a transmission in PUCCH 1510 that overlaps in time with a transmission occasion for multi-slot PUSCH 1504. The UE may apply a processing timeline when deciding whether to multiplex a UCI (e.g., from PUCCH 1510) to PUSCH 1504. In some embodiments, the processing timeline may be based on the minimum symbol gap (N2) between the reception of the uplink permission DCI 1502 scheduling uplink resources for PUSCH 1504 and the start of the multi-slot PUSCH transmission 1504. If the start of the multi-slot PUSCH transmission 1504 is more than N2 symbols after the uplink permission DCI 1502 is received, the UE may transmit the multi-slot PUSCH 1504. If the start of the multi-slot PUSCH transmit 1504 is less than N2 symbols after the uplink permission DCI 1502 is received, the UE may not transmit the multi-slot PUSCH 1504. In some embodiments, the processing timeline may be based on the minimum symbol gap (N1) between the reception of PDSCH 1508 and the start of PUCCH 1510 carrying the UCI (e.g., a HARQ ACK / NACK payload related to the reception of PDSCH). If the start of PUCCH 1510 is more than N1 symbols after PDSCH 1508 is received, the UE may transmit the UCI (e.g., a HARQ ACK / NACK) in PUCCH 1510. If the start of PUCCH 1510 is less than N1 symbols after PDSCH 1508 is received, the UE may not transmit the UCI (e.g., a HARQ ACK / NACK) in PUCCH 1510. When the UE considers multiplexing UCIs from PUCCH1510 into multiple slots PUSCH1504, a reference time (e.g., S0) may be used to measure whether the processing timeline based on N2 and N1 is satisfied.The reference time may vary depending on the various aspects of UCI multiplexing, such as when PUCCH overlap occurs, when UCI should be multiplexed, and the manner in which UCI should be multiplexed. As an additional consideration, the HARQ ACK / NACK bits from PUCCH1510 may be multiplexed to multi-slot PUSCH1504 if the downlink permit 1506 for PDSCH1508 is received before the uplink permit 1502 for multi-slot PUSCH1504.

[0128]

[0120] In the first example, as in the example in Figure 10, if the PUCCH 1510 overlap occurs in the first slot of the multiple slot PUSCH transmission 1504 and the UCI is multiplexed on the first slot, the reference time S0 can be based on the start of the multiple slot PUSCH transmission 1504, as shown in Figure 15.

[0129]

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

[0130]

[0122] Therefore, the reference time S0 at the start of the multi-slot PUSCH transmission 1504 can be applied for UCIs that overlap with the first slot of a transmission occasion, regardless of whether the UCIs are multiplexed based on the first slot or across transmission occasions.

[0131]

[0123] FIG. 16 shows a diagram 1600 illustrating an aspect of timeline consideration for multiplexing UCI in multiple-slot PUSCH transmission. As shown in FIG. 16, a UE may consider multiplexing UCI for transmission in PUCCH 1610 that temporally overlaps with the transmission occasion for multiple-slot PUSCH 1604. In FIG. 16, PUCCH 1610 overlaps with PUSCH 1604 in a subsequent slot of the multiple-slot transmission occasion, for example, at 1612, rather than in the first slot as in the case of FIG. 15, and is multiplexed in the overlapping slot. FIG. 12 shows an example of UCI that overlaps with the second slot of the multiple-slot PUSCH transmission occasion 1202 and is multiplexed in the second slot.

[0132]

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

[0133]

[0125] In contrast, when PUCCH 1610 overlap occurs in the second or subsequent slot of the multi-slot PUSCH transmission 1604 and UCI is multiplexed within that slot, the reference time S 02 can be based on that slot of the multi-slot PUSCH transmission, as shown, for example, at 1611. In some aspects, S 02 may be applicable when rate matching and interleaving are performed for each slot. S 02In a timeline with this configuration, a single interleaver may be applied per slot for multiple slot PUSCH transmissions 1604.

[0134]

[0126] If a PUCCH1610 duplicate occurs in the second or subsequent slot of a transmission occasion for multiple slot PUSCH transmission 1604, and the UCI is multiplexed across transmission occasions rather than per slot, the reference time is S 01 This is based on the initiation of a multiple slot PUSCH transmission 1604.

[0135]

[0127] As explained with respect to Figure 15, the time gap between DCI1602 scheduling the multiple slot PUSCH transmission 1604 may satisfy N2 symbols for transmitting PUSCH1604, and DCI1606 scheduling PDSCH1608, where the UE plans to transmit UCI in PUCCH1610, may be received before DCI1602 to multiplex the UCI with PUSCH1604.

[0136]

[0128] Figure 17 shows an example 1700 similar to Figure 15 for a UCI based on CSI-RS, such as a nonperiodic CSI-RS 1708 that temporally overlaps in the first symbol of a multi-slot PUSCH transmission 1704. The gap N2 between DCI 1702 and the scheduled multi-slot PUSCH transmission 1704 may be the same as in Figure 15. For a CSI report provided in PUCCH 1710, the minimum gap (Z) may be measured between the last symbol of CSI-RS 1708 and the start of PUCCH 1710 carrying the CSI report. If PUCCH 1710 is less than Z symbols from the last symbol of CSI-RS, the UE may not multiplex the CSI report with the multi-slot PUSCH transmission 1704. If the time gap is at least Z symbols, the UE may multiplex the CSI report with PUSCH 1704. For example, an additional aspect described with respect to Figure 16 is similarly, for example, from the last symbol of the received CSI-RS to the reference symbol S. 02This may be applicable to UCI based on CSI.

[0137]

[0129] Figure 18 shows Figure 1800, which illustrates multiple PUCCHs (e.g., UCI 1808, 1818, 1828, 1838, 1848, 1858, 1868) that overlap in various combinations of transmission occasions for multiple slot PUCCH transmissions. For example, transmission occasion 1802a overlaps with a single UCI for UCI 1808 in transmission occasion slot 0 and overlaps with a PUCCH for UCI 1818 in transmission occasion slot 1, for example. Transmission occasion 1802b has a single slot that overlaps with multiple PUCCHs, for example, UCI 1828 and 1838. Transmitting occasion 1802c has overlaps with UCI 1848 and 1858 in one slot, and with UCI 1868 in another slot.

[0138]

[0130] When multiple UCIs for multiple PUCCHs are multiplexed in a single transmission occasion having multiple slots for PUCCH transmissions, the UE can handle duplication for each slot and multiplex a UCI with a PUCCH for each slot.

[0139]

[0131] In other embodiments, when multiple UCIs for multiple PUCCHs are multiplexed in a single transmission occasion having multiple slots for PUCCH transmissions, the UE may handle overlaps across transmission occasions. The UE may multiplex UCIs across transmission occasions even if the PUCCHs do not occur in the same slot of the transmission occasion, for example, in the case of UCIs 1808 and 1818, or UCIs 1848 and 1868. In some embodiments, the UE may multiplex UCIs together.

[0140]

[0132] When duplicate UCIs are handled slot by slot, the UE can multiplex the UCIs, whether they are a single UCI or multiple duplicate UCIs in the corresponding slot of the transmission occasion. Figure 19 shows the slots in which the UCIs in Figure 18 are handled / multiplexed, indicated by arrows. PUSCH can be rate-matched slot by slot. Between slots, the UE remembers or may remember the starting position in the circular buffer. For example, circular buffer 1950 in Figure 19 shows point 1955 for the bits between slot 0 and slot 1. PUSCH can be interleaved slot by slot, for example, as described with respect to Figure 7.

[0141]

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

[0142]

[0134] Figure 21 shows Figure 2100, which illustrates a timeline consideration for multiplexing multiple UCIs in a multi-slot PUSCH transmit 2104. As shown in Figure 21, the UE may consider multiplexing UCIs for transmits in PUCCH 2110 and / or 2120 that overlap in time with the transmit occasion for multi-slot PUSCH 2104. In Figure 21, PUCCH 2110 overlaps with PUSCH 2104 in the first slot of the multi-slot transmit occasion, somewhat similar to Figure 15. PUCCH 2120 overlaps with PUSCH 2104 in a subsequent slot of the multi-slot transmit occasion, but not in the first slot. Both PUCCH2110 and PUCCH2120 are scheduled by DCI2106 and DCI2116, which schedule PDSCH2108 and PDSCH2118, and are received before uplink permission 2102, which schedules PUSCH2104, and thus satisfy its threshold for being multiplexed with PUSCH2104. In some embodiments, the reference time is the start of multi-slot PUSCH2104 (e.g., S) regardless of how and / or where the UCIs are multiplexed. 01 ) can be obtained based on. For example, UE can be prepared in advance for multi-slot PUSCH transmission, criterion S 01 Based on the start of the multi-slot PUSCH1604, timeline considerations can be applied for each of the multiple PUSCHs (2110 and 2120).

[0143]

[0135] In some embodiments, the criterion for multiplexing each PUCCH may be based on the multiplexing slot. For example, each of the multiple PUCCHs may independently have a reference time based on the multiplexing slot or on other considerations described with respect to Figures 15 to 17 for each individual PUCCH. For example, the reference time for PUCCH2120 is S 02 This is possible, and the reference time for PUCCH2110 is S 01This is possible. In some cases, the determination of different reference times may be based on interleaving and rate matching configurations. For example, independent determination of reference times per PUCCH may be applied using per-slot rate matching and / or per-slot interleaving, for example, as illustrated with respect to Figure 19, when different PUCCHs are multiplexed per slot.

[0144]

[0136] For example, if the multiplexing of multiple UCIs is handled across transmission occasions rather than per slot, as explained with respect to Figure 20, the UE will send S to each of the PUCCH based on the start of multiple slot PUSCH2104. 01 A common reference time can be applied. The start of a PUSCH can be applied as a reference time because UCI multiplexing decisions may be made in the same manner for different PUSCHs. A common reference time may allow the UE to prepare in advance for multiple slot PUSCH transmissions.

[0145]

[0137] Figure 22 shows PUCCH resources for UCIs 2208 and 2209 that overlap with transmission occasions 2202 and 2212, for example, option (b) described with respect to Figure 4, which includes discontinuous segments of resources. For example, transmission occasion 2202 includes segments 2205 and 2207, which are temporally separated by resources not included in transmission occasion 2202. Segments 2205 and 2207 each include a contiguous set of resources. For example, segment 2205 is shown as having resources in a first slot 2204 and a second slot 2206. Each transmission occasion, for example, 2202 and 2212, can be handled independently to multiplex the UCI with PUSCH transmitted on multiple slots of a single transmission occasion. Each transmission occasion may have a configuration corresponding to the slot-by-slot handling of PUSCH and PUCCH. In some embodiments, each consecutive segment within a transmission occasion may be handled independently of (one or more) other segments.

[0146]

[0138] In some embodiments, the UE may consider, for example, handling or applying, multiplexing PUCCH within overlapping slots rather than within non-overlapping slots (one or more). The embodiments of multiplexing in this example may be applied to continuous transmission occasions in the same way as multiplexing within overlapping slots, for example, as described with respect to Examples 1 and 3 in Table 1, and Figures 10 and 12.

[0147]

[0139] In some embodiments, the UE may consider, handle, or apply multiplexing over the entire transmission occasion, e.g., 2202, including discontinuous segments 2205 and 2207. The embodiments of multiplexing in this example may be applied to continuous transmission occasions in the same way as multiplexing over transmission occasions, as described, for example, with respect to Examples 2 and 4 in Table 1, and Figures 11 and 13.

[0148]

[0140] In some embodiments, the UE may consider, handle, or apply multiplexing on a contiguous portion of a transmit occasion, for example, within an overlapping segment 2207 of transmit occasion 2202. Table 2 shows an exemplary embodiment of handling UCI multiplexing with multiple slot PUSCH for each segment of a transmit occasion that includes a discontinuous segment of resources for UCI 2208.

[0149] [Table 3]

[0150]

[0141] Figure 23 shows Figure 2300, which illustrates the UCI being multiplexed based on overlapping segments of a discontinuous transmission occasion 2302. The transmission occasion includes discontinuous segments 2305 and 2307. Segment 2307 overlaps temporally with PUCCH for transmission of UCI 1908. Based on the overlap, UCI 2308 can be multiplexed with PUSCH TB for transmission in the transmission occasion. Multiplexing can be handled segment by segment, and the multiplexing in segment 2307 is handled independently of the processing for segment 2305. Segment 2307 includes resources spanning two slots, for example, slot 5 2304 and slot 6 2306. The resources for multiplexing UCI 2308 can be determined based on the segment in which PUCCH is multiplexed. UCI resources can be determined based on the resources of the segment.

[0151]

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

[0152]

number

[0153] This may correspond to the number of REs potentially available for UCI2308 across the PUSCH symbols of the corresponding segments of the transmission occasion (for example, segment 2307 of transmission occasion 2302), in Equation 1.

[0154]

number

[0155] This may correspond to the total number of PUSCH bits in transmit occasion 2302, scaled by the number of symbols in the corresponding segment, divided by the total number of PUSCH symbols in the transmit occasion.

[0156]

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

[0157]

[0144] Figure 24 shows Figure 2400 with two potential timelines for a PUCCH overlapping with a transmit occasion 2402 having discontinuous segments, based on option (b) described with respect to Figure 4 and / or Figure 23, for example. Transmit occasion 2402 includes discontinuous segments 2405 and 2407. Each segment includes a contiguous set of resources, as in the example in Figure 23, for example, segment 2405 includes resources in slots 0 and 1 of the set of slots to which transmit occasion 2402 extends, and segment 2407 includes resources in slots 5 and 6. A multi-slot PUCCH transmit may be scheduled by DCI 2401 with uplink permission, as described with respect to Figures 15-17, and may have a processing timeline based on N2.

[0158]

[0145] Figure 24 shows two examples of potential timelines for PUCCH2410a or 2410b that overlap with the transmission occasion 2402 for multi-slot PUCCH. PUCCH may include UCIs such as ACK / NACK for PDSCH2408a or 2408b, which may be scheduled by downlink permission in DCI2406a or 2406b.

[0159]

[0146] In the 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 should be multiplexed. The reference time is, for example, S in Figure 24. 01 As shown, it can be mapped to the start of a segment. The use of Timeline 1 may be based on interleaving and rate matching configurations for PUSCH with multiplexed UCIs, for example, being segment-based or slot-based.

[0160]

[0147] In the second exemplary timeline, the reference time for the measurement of N1 and / or Z is, for example, S in Figure 24. 02 As shown, this may be based on the start of multiple slot PUSCH. In some embodiments, the reference time S 02 This can be applied by the UE regardless of how or where the UCI will be multiplexed within a multi-slot push transmission. Using a reference time at the start of a multi-slot push transmission may provide the UE with additional time to prepare for the multi-slot push.

[0161]

[0148] Figure 25 shows an exemplary communication flow 2500 between UE 2502 and base station 2504, including a multi-slot PUSCH transmission and a transmission 2528 of a multiplexed UCI. As shown in 2506, base station 2504 may transmit a DCI that allocates or authorizes resources to UE 2502 for a PUSCH transmission. The allocated resources may include a transmission occasion spanning multiple slots, as described with respect to Figure 4. In 2510, UE may trigger a UCI multiplexing with a multi-slot PUSCH transmission based on determining the temporal overlap between the PUCCH resources for the UCI and the transmission occasion for PUSCH. As a non-limiting example to illustrate the concept, UE may receive a downlink transmission 2508 in which the UE has a UCI to transmit to base station 2504. The downlink transmission may include a PDSCH, which may be transmitted before or after the uplink authorization in 2506. The UE may have ACK / NACK information regarding the PDSCH to transmit as a UCI that overlaps with the resources for the PUSCH. The PDSCH is obtained based on DCI 2505 which schedules the PDSCH, and this may be received before the DCI with uplink permission in 2506. As another example, the downlink transmit 2508 may include CSI-RS, and the UE may have a CSI to report to the base station as a UCI.

[0162]

[0149] As part of deciding to multiplex the UCI with multiple slot PUSCH transmissions, in 2510, the UE may apply a processing timeline. The processing timeline may be based on N1 and / or Z, as described with respect to any of Figures 15-17, Figure 21, or Figure 24. When the UE determines, for example, whether N1 or Z for PUCCH related to the UCI satisfies the minimum gap for multiplexing the UCI with PUSCH, a reference time (e.g., S0, S) for the processing timeline is used. 01 , or S 02 ) may be applied.

[0163] As shown in

[0150] 2512, in order to multiplex the UCI with a PUSCH transmission, the UE may determine the amount of resources for the UCI. The UE may determine resources based on the type of transmission occasion (e.g., consecutive or discontinuous segments, as described with respect to Figure 4). The UE may also determine resources based on whether the multiplexing is handled per slot, per transmission occasion, or per segment of the transmission occasion. The UE may also determine resources based on whether the overlap occurs in the first slot of the transmission occasion or segment, or in subsequent slots. The determination may be based on any of the embodiments described with respect to Figures 10–14, Figures 18–20, and / or Figures 22–23. The determination may be based on a modified embodiment of Equation 1, as described herein.

[0164]

[0151] In 2514, the UE may determine the location of resources for UCIs within a PUSCH transmission occasion. In 2516, the UE may fill the identified resources with UCI symbols. In some embodiments, the UE may fill resources in a frequency-first, time-second manner. In 2520, the UE identifies the remaining resources of a transmission occasion that are available for PUSCH transmission after filling some of the resources of the transmission occasion with UCIs, for example. In 2522, the UE applies rate matching and interleaving based on the remaining resources. Rate matching and interleaving may be based on any of the embodiments described with respect to the examples in Figures 4 to 24. For example, interleaving may be per slot, as in Figure 7, per transmission occasion, as in Figure 6, or per segment, as in Figure 8. The type of rate matching and interleaving may be based on the type of transmission occasion and the manner in which the UCIs are 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 transmit occasion with a PUSCH transmit by mapping the modulation symbols mapped at 2524 to the remaining resources of the transmit occasion. At 2528, UE 2502 transmits the PUSCH and the multiplexed UCI to base station 2504. As shown at 2530, the base station may multiplex the UCI from the PUSCH in order to obtain information in the UCI.

[0165]

[0152] Figure 26A is a flowchart 2600 of a wireless communication method. This method can be implemented by a UE (e.g., UE 104, 350, 2502, device 2702). This method may enable the UE to multiplex UCIs within a transmission occasion for multiple slot PUSCHs and provides a processing timeline for the UE to multiplex UCIs with multiple slot PUSCHs.

[0166]

[0153] In 2602, the UE applies a processing timeline for multiplexing the UCI in at least one slot of the multi-slot PUSCH transmission. Figure 25 shows an example of UE 2502 applying a processing timeline in 2511. The processing timeline may be based on any of the embodiments described with respect to Figures 15-17, Figure 21, and / or Figure 24. The application of the timeline may be carried out, for example, by the timeline component 2744 of the device 2702 in Figure 27.

[0167]

[0154] In 2604, the UE transmits a multiplexed UCI along with a PUSCH transmission based on the fulfillment of the processing timeline. The multiplexing and / or transmission may be based on any of the embodiments described with respect to Figures 4 to 25. Figure 25 shows an example in which UE 2502 transmits a PUSCH along with a multiplexed UCI to base station 2504 in 2528. The transmission may be carried out, for example, by the PUSCH component 2742 of device 2702, via the transmitting component 2734 and / or RF transceiver 2722.

[0168]

[0155] Figure 26B is a flowchart 2650 of a wireless communication method. This method can be carried out by UEs (e.g., UEs 104, 350, 2502, and device 2702). This method may include 2602 and 2604 as described with respect to Figure 26B.

[0169]

[0156] In some embodiments, the UCI may be equipped with HARQ feedback, and the processing timeline may correspond to a time gap (e.g., N1) between the reception of the PDSCH and the start of the PUCCH carrying the HARQ feedback payload about the PDSCH.

[0170]

[0157] In some embodiments, the UCI may include a CSI report, and the processing timeline may correspond to a time gap (e.g., Z) between the reception of the last symbol of the CSI-RS and the start of the PUCCH carrying the CSI report based on the measurement of the CSI-RS, as described with respect to Figure 17, for example.

[0171]

[0158] In some embodiments, the UE may apply a processing timeline based on the start of a multi-slot PUSCH transmission, as shown in 2606. In some embodiments, a multi-slot PUSCH transmission may be transmitted in a transmission occasion comprising a set of consecutive slots. In some embodiments, the processing timeline is based on the start of a multi-slot PUSCH transmission based on one or more of the following: overlapping slots of the multi-slot PUSCH transmission that temporally overlap with the UCI; multiplexed slots in the multi-slot PUSCH transmission where the UCI should be multiplexed; transmission occasion-based multiplexing for the 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 start of a multi-slot PUSCH based on any of the embodiments described with respect to Figures 15 to 17.

[0172]

[0159] In some embodiments, a multi-slot PUSCH transmission may be transmitted in a transmission occasion comprising a set of consecutive slots, for example, option (a) in Figure 4, and applying a processing timeline may include applying a processing timeline based on the start of overlapping slots of the multi-slot PUSCH transmission where the UCI overlaps and the UCI is multiplexed therein. In some embodiments, the processing timeline may be based on the start of overlapping slots of the multi-slot PUSCH transmission where the UCI is multiplexed in the overlapping slots of the multi-slot PUSCH transmission, based on one or more of the following: the UCI is multiplexed in the overlapping slots of the multi-slot PUSCH transmission, slot-based multiplexing for the UCI within the multi-slot PUSCH transmission, slot-based interleaving for the multi-slot PUSCH transmission, or slot-based rate matching for the multi-slot PUSCH transmission. Reference time S in Figure 16 02 This illustrates an example where the processing timeline is based on the start of overlapping slots.

[0173]

[0160] In some embodiments, the UE may multiplex UCIs from multiple PUCCHs that overlap with a multi-slot PUSCH. For example, as described with respect to any of Figures 18 to 21, the UE may multiplex a first UCI and a second UCI that overlap with a multi-slot PUSCH transmission. In 2602, for example, S in Figure 21 01 As shown, a processing timeline can be applied to the first UCI and the second UCI based on the initiation of a multi-slot PUSCH transmission.

[0174]

[0161] In some embodiments, the first UCI and the second UCI may overlap in different slots of transmission occasions, and the processing timeline may be, for example, S in Figure 21. 02As shown, the first UCI and the second UCI may be determined separately based on the respective slots of transmission occasions that overlap with the first UCI and the second UCI. In some embodiments, the first UCI and the second UCI may be multiplexed across consecutive slots of transmission occasions.

[0175]

[0162] In some embodiments, a multi-slot PUSCH transmission may be transmitted in a transmission occasion comprising a discontinuous set of slots, for example, option (b) in Figure 4, and the processing timeline may be determined in 2610 based on the contiguous portion of the transmission occasion where the UCI is multiplexed therein. Figure 24 shows an example of a processing timeline based on overlapping segments (e.g., timeline 1). The processing timeline is, for example, S in Figure 21. 01 As shown, it may be based on the start of a contiguous portion. In some embodiments, the UE may multiplex a first UCI and a second UCI that overlap with different contiguous portions of a multi-slot PUSCH transmission, and the processing timeline may be based on the contiguous portion of the transmission occasion in which each UCI is multiplexed.

[0176]

[0163] In 2603, the UE multiplexes the UCI in at least one slot of the multiple slot PUSCH transmission. As described with respect to Figure 25, the UE may decide to multiplex the UCI based on resources that should be transmitted in a timely overlap with the transmission occasions for the PUSCH transmission. Multiplexing may include any of the embodiments described with respect to Figures 4 to 25. Multiplexing may be performed, for example, by the UCI multiplexer component 2740 of the device 2702 in Figure 27.

[0177]

[0164] Figure 27 is Figure 2700 showing an example of a hardware implementation for device 2702. Device 2702 may be a UE, a component of a UE, or implement UE functions. In some embodiments, device 2702 may include a cellular baseband processor 2704 (also called a modem) coupled to a cellular RF transceiver 2722. Device 2702 may further include one or more subscriber identification module (SIM) cards 2720, a secure digital (SD) card 2708, an application processor 2706 coupled to 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 UE 104 and / or base stations 102 / 180 through the cellular RF transceiver 2722. The cellular baseband processor 2704 may include computer-readable media / memory. The computer-readable media / memory may be non-transient. The cellular baseband processor 2704 is responsible for general processing, including the execution of software stored in the computer-readable media / memory. When executed by the cellular baseband processor 2704, the software causes the cellular baseband processor 2704 to perform various functions described herein. The computer-readable media / memory may also be used to store data manipulated by the cellular baseband processor 2704 when the software is executed. The cellular baseband processor 2704 further includes a receiving component 2730, a communications manager 2732, and a transmitting component 2734. The communications manager 2732 includes one or more illustrated components. Components within the communications manager 2732 may be stored in computer-readable media / memory and / or configured as hardware within the cellular baseband processor 2704.The cellular baseband processor 2704 may be a component of the UE350 and may include memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, device 2702 is a modem chip and may include only the baseband processor 2704, while in another configuration, device 2702 is the entire UE (see, for example, 350 in Figure 3) and may include additional modules of device 2702.

[0178]

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

[0179]

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

[0180]

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

[0181]

[0168] The deployment of communication systems, such as 5G new radio (NR) systems, can be composed of various components or parts in multiple ways. In a 5G NR system or network, network equipment such as network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements, or base stations (BS), or one or more units (or one or more components) that perform base station functions, can be implemented in aggregated or disaggregated architectures. For example, a BS (such as a node B (NB), advanced NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell) can be implemented as an aggregated base station or a disaggregated base station (also known as a standalone BS or a monolithic BS).

[0182]

[0169] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among 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 embodiments, a CU may be implemented within a RAN node, and one or more DUs may be collocated with the CU or, alternatively, geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, DU, and RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0183]

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

[0184]

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

[0185]

[0172] Each of the units, namely CU2810, DU2830, RU2840, and the near-RT RIC2825, non-RT RIC2815, and SMO framework 2805, may include, or be coupled to, one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) over a wired or wireless transmission medium. Each of the units, or any associated processor or controller providing instructions to the communication interfaces of the units, may be configured to communicate with one or more of the other units over a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Furthermore, a unit 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, or both, over a wireless transmission medium to one or more of the other units.

[0186]

[0173] In some embodiments, the CU2810 may host one or more higher-layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptive protocol (SDAP), etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU2810. The CU2810 may be configured to handle user plane functions (i.e., central unit-user plane (CU-UP)), control plane functions (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU2810 may 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 units may communicate bidirectionally with the CU-CP units via an interface, such as the E1 interface. The CU2810 may be implemented to communicate with the DU2830 for network control and signaling, if necessary.

[0187]

[0174] The DU2830 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU2840s. In some embodiments, the DU2830 may host one or more of the following, at least in part, depending on the functional split, such as as defined by the Third Generation Partnership Project (3GPP): 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) coding and decoding, scrambling, modulation and demodulation). In some embodiments, the DU2830 may further host one or more low PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU2830, or with control functions hosted by the CU2810.

[0188]

[0175] Lower layer functions may be implemented by one or more RU2840s. In some deployments, controlled by a DU2830, the RU2840 may correspond to logical nodes that host RF processing functions, or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least partially on a functional split, such as a lower layer functional split. In such architectures, (one or more) RU2840s may be implemented to handle over-the-air (OTA) communication with one or more UE104s. In some implementations, real-time and non-real-time aspects of control plane communication and user plane communication with (one or more) RU2840s may be controlled by the corresponding DU2830s. In some scenarios, this configuration can enable (one or more) DU2830s and CU2810s to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0189]

[0176] The SMO framework 2805 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 2805 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operational and maintenance interfaces (such as the O1 interface). For virtualized network elements, the SMO framework 2805 may be configured to interact with a cloud computing platform (such as the 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 the O2 interface). Such virtualized network elements may include, but are not limited to, the CU2810, DU2830, RU2840, and near RT RIC2825. In some implementations, the SMO framework 2805 may communicate with hardware aspects of the 4G RAN, such as the Open eNB (O-eNB) 2811, via the O1 interface. Furthermore, in some implementations, the SMO framework 2805 can communicate directly with one or more RU2840s via the O1 interface. The SMO framework 2805 may also include a non-RT RIC2815 configured to support the functionality of the SMO framework 2805.

[0190]

[0177] The non-RT RIC2815 may be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance for applications / features in the near-RT RIC2825. The non-RT RIC2815 may be coupled to or communicate with the near-RT RIC2825 (e.g., via the A1 interface). The near-RT RIC2825 may be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data acquisition and actions on an interface (e.g., via the E2 interface) that connects one or more CU2810s, one or more DU2830s, or both, as well as an O-eNB, to the near-RT RIC2825.

[0191]

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

[0192]

[0179] It should be understood that the specific order or hierarchy of blocks in the disclosed process / flowchart is an example of an exemplary technique. It should be understood that the specific order or hierarchy of blocks in the process / flowchart may be rearranged based on design preferences. Furthermore, some blocks may be combined or omitted. The attached method claims present elements of various blocks in an exemplary order and are not limited to the specific order or hierarchy presented.

[0193]

[0180] The above description is provided to enable a person skilled in the art to carry out the various embodiments described herein. Various modifications to these embodiments will be readily apparent to a person skilled in the art, and the general principles defined herein may apply to other embodiments. Accordingly, the claims should not be limited to the embodiments shown herein, but should be given the full scope consistent with the claim language, where references to singular elements mean "one or more" and not "one unique" unless otherwise explicitly stated. Terms such as "if," "when," and "while" should be interpreted as meaning "under the condition that," rather than implying an immediate temporal relationship or response. That is, these phrases, for example, "when," do not imply an immediate action in response to or during the occurrence of an action, but simply imply that an action occurs if the condition is met, but does not require a specific or immediate temporal constraint on which the action should occur. The word "exemplary" is used herein to mean "to serve as an example, case, or illustration." Any embodiment described herein as “exemplary” should not necessarily be construed as being preferable or more advantageous than any other embodiment. Unless otherwise specified, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C.More 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 only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the various aspects of the elements described throughout this disclosure, known to those skilled in the art or to be known thereafter, are expressly incorporated herein by reference and are included in the claims. Furthermore, nothing disclosed herein, whether such disclosure is expressly represented in the claims or not, is not made public. Words such as “module,” “mechanism,” “element,” and “device” may not be substitutes for the word “means.” Therefore, no claim element should be interpreted as means plus function unless it is explicitly stated using the phrase “means for.”

[0194]

[0181] The following embodiments are illustrative and not limiting, but may be combined with other embodiments or teachings described herein.

[0195]

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

[0196]

[0183] In Embodiment 2, the method described in Embodiment 1 further includes the UCI having HARQ feedback, and the processing timeline corresponding to the time gap between the reception of the PDSCH and the start of the PUCCH carrying the HARQ feedback payload about the PDSCH.

[0197]

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

[0198]

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

[0199]

[0186] In embodiment 5, the method according to any one of embodiments 1 to 4 further includes the transmission of a multi-slot PUSCH transmission in a transmission occasion comprising a set of consecutive slots.

[0200]

[0187] In embodiment 6, the method of any embodiment 1 to 5 further includes the initiation of a multi-slot PUSCH transmission based on one or more of the following: overlapping slots of a multi-slot PUSCH transmission that temporally overlap with the UCI; multiplexed slots in a multi-slot PUSCH transmission where the UCI should be multiplexed; transmission occasion-based multiplexing for the UCI within a multi-slot PUSCH transmission; transmission occasion-based interleaving for a multi-slot PUSCH transmission; or transmission occasion-based rate matching for a multi-slot PUSCH transmission.

[0201]

[0188] In Embodiment 7, the method of any one of Embodiments 1 to 5 further comprises the processing timeline being based on the initiation of overlapping slots of a multi-slot PUSCH transmission, on one or more of the following: UCI being 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.

[0202]

[0189] In embodiment 8, the method according to any one of embodiments 1 to 7 further includes multiplexing a first UCI and a second UCI which overlap with a multiple slot PUSCH transmission.

[0203]

[0190] In embodiment 9, the method described in embodiment 8 further includes applying a processing timeline to a first UCI and a second UCI based on the commencement of a multi-slot PUSCH transmission.

[0204]

[0191] In embodiment 10, the method according to embodiment 8 further includes the fact that the first UCI and the second UCI overlap in different slots of transmission occasion, and the processing timeline is determined separately for the first UCI and the second UCI based on the respective slots of transmission occasion that overlap by the first UCI and the second UCI.

[0205]

[0192] In embodiment 11, the method according to any one of embodiments 1 to 3 further includes that a multi-slot PUSCH transmission is transmitted in a transmission occasion comprising a set of discontinuous slots, wherein the processing timeline is determined based on a contiguous portion of the transmission occasion in which the UCI is multiplexed.

[0206]

[0193] In embodiment 12, the method described in embodiment 11 further includes the fact that the processing timeline is based on the start of a continuous portion.

[0207]

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

[0208]

[0195] Embodiment 14 is a device for wireless communication in a user device UE, comprising a memory and at least one processor coupled to the memory, wherein the at least one processor is configured to apply a processing timeline to multiplex UCI in at least one slot of a multiple slot PUSCH transmission and to transmit the multiple slot PUSCH transmission together with the multiplexed UCI based on the processing timeline being satisfied.

[0209]

[0196] In embodiment 15, the apparatus for wireless communication described in embodiment 14 further includes memory and at least one processor, configured to carry out the method described in any of embodiments 2 to 13.

[0210]

[0197] In embodiment 16, the apparatus according to either embodiment 14 or 15 further includes at least one transceiver coupled to at least one processor.

[0211]

[0198] In embodiment 17, the apparatus according to any one of embodiments 14 to 16 further includes at least one antenna coupled to at least one processor.

[0212]

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

[0213]

[0200] In embodiment 19, the apparatus for wireless communication described in embodiment 18 further comprises means for carrying out the method described in any one of claims 2 to 13.

[0214]

[0201] In embodiment 20, the apparatus according to either embodiment 18 or 19 further includes at least one transceiver.

[0215]

[0202] In embodiment 21, the apparatus described in any of embodiments 18 to 20 further includes at least one antenna.

[0216]

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

[0217]

[0204] In embodiment 23, the computer-readable medium described in embodiment 22 further comprises code that, when executed by a processor, causes the processor to carry out the method according to any one of claims 2 to 13. The invention described in the original claims of this application is listed below. [C1] A method for wireless communication in user equipment (UE), Applying a processing timeline to multiplex uplink control information (UCI) in at least one slot of a multi-slot physical uplink shared channel (PUSCH) transmission, Based on the fulfillment of the processing timeline, the multiple slot PUSCH transmission is transmitted along with the multiplexed UCI. A method that includes [a certain feature]. [C2] The method according to C1, wherein the UCI includes hybrid automatic retransmission request (HARQ) feedback, and the processing timeline corresponds to a time gap between the reception of a physical downlink shared channel (PDSCH) and the initiation of a physical uplink control channel (PUCCH) carrying a HARQ feedback payload for the PDSCH. [C3] The method according to C1, wherein the UCI includes a channel status information (CSI) report, and the processing timeline corresponds to a time gap between the reception of the last symbol of the channel status information reference signal (CSI-RS) and the start of a physical uplink control channel (PUCCH) that carries the CSI report based on the measurement of the CSI-RS. [C4] Applying the aforementioned processing timeline The processing timeline is applied based on the start of the multiple slot PUSCH transmission. The method described in C1, including the method described in C1. [C5] The method of C4, wherein the multi-slot PUSCH transmission is transmitted in a transmission occasion that includes a set of consecutive slots. [C6] The aforementioned processing timeline is: The overlapping slots of the multiple slot PUSCH transmissions that overlap in time with the aforementioned UCI, In the aforementioned multiple slot PUSCH transmission, the UCI should be multiplexed therein, multiplexed slots, Multiplexing of the UCI within the aforementioned multi-slot push transmission, Transmit occasion-based interleaving for the aforementioned multi-slot push transmission, or Transmit Occasion-Based Rate Matching for the Multiple Slot Push Transmissions The method of C5, based on the commencement of the multiple slot PUSCH transmission, based on one or more of the following. [C7] The aforementioned processing timeline is: The aforementioned UCI is multiplexed in the overlapping slots of the multiple slot PUSCH transmission. Slot-based multiplexing of the UCI within the aforementioned multi-slot PUSCH transmission, Slot-based interleaving for the aforementioned multiple slot PUSCH transmissions, or Slot-based rate matching for the aforementioned multi-slot push transmission. The method of C5, based on the start of the overlapping slots of the multiple slot PUSCH transmission, based on one or more of the above. [C8] Multiplexing the aforementioned UCI Multiplexing the first and second UCIs that overlap with the aforementioned multi-slot PUSCH transmission. The method described in C1, including the method described in C1. [C9] Applying the processing timeline to the first UCI and the second UCI based on the start of the multiple slot PUSCH transmission. A method using C8 that further includes these features. [C10] The method according to C8, wherein the first UCI and the second UCI overlap in different slots of transmission occasion, and the processing timeline is determined separately for the first UCI and the second UCI based on each of the slots of transmission occasion that overlap with the first UCI and the second UCI. [C11] The method according to C1, wherein the multiple-slot PUSCH transmission is transmitted in a transmission occasion comprising a set of discontinuous slots, wherein the processing timeline is determined based on the continuous portion of the transmission occasion in which the UCI is multiplexed. [C12] The method according to C11, wherein the processing timeline is based on the start of the continuous portion. [C13] Multiplexing the first UCI and the second UCI that overlap with different consecutive portions of the aforementioned multi-slot PUSCH transmission. The method according to C11, further comprising, wherein the processing timeline is determined based on the contiguous portion of the transmission occasion in which each UCI is multiplexed therein. [C14] A device for wireless communication in user equipment (UE), Memory and At least one processor coupled to the memory and The at least one processor is Applying a processing timeline to multiplex uplink control information (UCI) in at least one slot of a multi-slot physical uplink shared channel (PUSCH) transmission, Based on the fulfillment of the processing timeline, the multiple slot PUSCH transmission is transmitted along with the multiplexed UCI. A device configured to perform the following actions. [C15] The apparatus according to C14, wherein the UCI includes hybrid automatic retransmission request (HARQ) feedback, and the processing timeline corresponds to a time gap between the reception of a physical downlink shared channel (PDSCH) and the initiation of a physical uplink control channel (PUCCH) carrying a HARQ feedback payload for the PDSCH. [C16] The apparatus according to C14, wherein the UCI includes a channel status information (CSI) report, and the processing timeline corresponds to a time gap between the reception of the last symbol of the channel status information reference signal (CSI-RS) and the start of a physical uplink control channel (PUCCH) that carries the CSI report based on the measurement of the CSI-RS. [C17] In order to apply the processing timeline, at least one processor, The processing timeline is applied based on the start of the multiple slot PUSCH transmission. The apparatus described in C14, further configured to perform the following actions. [C18] The apparatus according to C17, wherein the multiple slot PUSCH transmission is transmitted in a transmission occasion comprising a set of consecutive slots. [C19] The aforementioned processing timeline is: The overlapping slots of the multiple slot PUSCH transmissions that overlap in time with the aforementioned UCI, In the aforementioned multiple slot PUSCH transmission, the UCI should be multiplexed therein, multiplexed slots, Multiplexing of the UCI within the aforementioned multi-slot push transmission, Transmit occasion-based interleaving for the aforementioned multi-slot push transmission, or Transmit Occasion-Based Rate Matching for the Multiple Slot Push Transmissions The apparatus according to C18, based on the initiation of the multiple slot PUSCH transmission, based on one or more of the above. [C20] The aforementioned processing timeline is: The aforementioned UCI is multiplexed in the overlapping slots of the multiple slot PUSCH transmission. Slot-based multiplexing of the UCI within the aforementioned multi-slot PUSCH transmission, Slot-based interleaving for the aforementioned multiple slot PUSCH transmissions, or Slot-based rate matching for the aforementioned multi-slot push transmission. The apparatus according to C18, based on the start of the overlapping slots of the multiple slot PUSCH transmission, based on one or more of the above. [C21] In order to multiplex the UCI, at least one processor, Multiplexing the first and second UCIs that overlap with the aforementioned multi-slot PUSCH transmission. The apparatus described in C14, further configured to perform the following actions. [C22] The aforementioned at least one processor, Applying the processing timeline to the first UCI and the second UCI based on the start of the multiple slot PUSCH transmission. The apparatus described in C21, further configured to perform the following actions. [C23] The apparatus according to C21, wherein the first UCI and the second UCI overlap in different slots of transmission occasion, and the processing timeline is determined separately for the first UCI and the second UCI based on each of the slots of transmission occasion overlapped by the first UCI and the second UCI. [C24] The apparatus according to C14, wherein the multiple-slot push transmission is in a transmission occasion comprising a set of discontinuous slots, wherein the processing timeline is based on a continuous portion of the transmission occasion in which the UCI is multiplexed. [C25] The apparatus according to C24, wherein the processing timeline is based on the start of the continuous portion. [C26] The aforementioned at least one processor, Multiplexing the first UCI and the second UCI that overlap with different consecutive portions of the aforementioned multi-slot PUSCH transmission. The apparatus according to C24, further configured to perform, wherein the processing timeline is determined based on the contiguous portion of the transmission occasion in which each UCI is multiplexed therein. [C27] At least one transceiver coupled to the at least one processor The apparatus described in C14, further comprising the above. [C28] A device for wireless communication in user equipment (UE), Means for applying a processing timeline to multiplex uplink control information (UCI) in at least one slot of a multi-slot physical uplink shared channel (PUSCH) transmission, Based on the fulfillment of the processing timeline, means for transmitting the multiple slot PUSCH transmission together with the multiplexed UCI. A device equipped with the following features. [C29] A non-temporary computer-readable medium for storing computer executable code in a user device (UE), wherein the code, when executed by a processor, is transmitted to the processor. Applying a processing timeline to multiplex uplink control information (UCI) in at least one slot of a multi-slot physical uplink shared channel (PUSCH) transmission, Based on the fulfillment of the processing timeline, the multiple slot PUSCH transmission is transmitted along with the multiplexed UCI. A non-temporary computer-readable medium that enables the operation of [the process].

Claims

1. A method of wireless communication in user equipment (UE), Applying a processing timeline for multiplexing uplink control information (UCI) in at least one slot of a multi-slot physical uplink shared channel (PUSCH) transmission, Based on the satisfaction of the processing timeline, the multiple slot PUSCH transmission is transmitted along with the multiplexed UCI. Equipped with, The aforementioned processing timeline is: The initiation of the multi-slot PUSCH transmission is based on one or more of the following: transmission occasion-based interleaving for the multi-slot PUSCH transmission, or transmission occasion-based rate matching for the multi-slot PUSCH transmission, or The initiation of overlapping slots of the multi-slot PUSCH transmission based on one or more of the following: slot-based interleaving for the multi-slot PUSCH transmission, or slot-based rate matching for the multi-slot PUSCH transmission, Based on, method.

2. The method according to claim 1, wherein the UCI includes hybrid automatic retransmission request (HARQ) feedback, and the processing timeline corresponds to a time gap between the reception of a physical downlink shared channel (PDSCH) and the initiation of a physical uplink control channel (PUCCH) carrying a HARQ feedback payload for the PDSCH.

3. The method according to claim 1, wherein the UCI includes a channel status information (CSI) report, and the processing timeline corresponds to a time gap between the reception of the last symbol of a channel status information reference signal (CSI-RS) and the start of a physical uplink control channel (PUCCH) that carries the CSI report based on a measurement of the CSI-RS.

4. The method according to any one of claims 1 to 3, wherein the multiple slot PUSCH transmission is transmitted in a transmission occasion comprising a set of consecutive slots.

5. The aforementioned processing timeline is: The overlapping slots of the multiple slot PUSCH transmission that overlap in time with the UCI, In the aforementioned multiple-slot PUSCH transmission, the UCI should be multiplexed therein, in the multiplexed slot, or Multiplexing of the UCI within the aforementioned multi-slot PUSCH transmission, The method according to claim 4, further based on the initiation of the multiple slot PUSCH transmission based on one or more of the above.

6. The aforementioned processing timeline is: The UCI is multiplexed in the overlapping slots of the multiple slot PUSCH transmission, or Slot-based multiplexing of the UCI within the aforementioned multi-slot PUSCH transmission, The method according to claim 1, further based on the start of the overlapping slots of the multiple slot PUSCH transmission, based on one or more of the above.

7. Multiplexing the aforementioned UCI Multiplexing the first UCI and the second UCI that overlap with the aforementioned multi-slot PUSCH transmission. The method according to claim 1, including the method described in claim 1.

8. The method according to claim 7, wherein the first UCI and the second UCI overlap in different slots of transmission occasion, and the processing timeline is determined separately for the first UCI and the second UCI based on each of the slots of transmission occasion that overlap with the first UCI and the second UCI.

9. The method according to claim 1, wherein the multiple slot PUSCH transmission is transmitted in a transmission occasion comprising a set of discontinuous slots, wherein the processing timeline is determined based on a continuous portion of the transmission occasion in which the UCI is multiplexed.

10. The method according to claim 9, wherein the processing timeline is based on the start of the continuous portion.

11. Multiplexing the first UCI and the second UCI that overlap with different consecutive portions of the aforementioned multi-slot PUSCH transmission. The method according to claim 9, further comprising, wherein the processing timeline is determined based on the contiguous portion of the transmission occasion in which each UCI is multiplexed therein.

12. A device for wireless communication in user equipment (UE), Memory and At least one processor coupled to the memory and The at least one processor is equipped with Applying a processing timeline for multiplexing uplink control information (UCI) in at least one slot of a multi-slot physical uplink shared channel (PUSCH) transmission, Based on the satisfaction of the processing timeline, the multiple slot PUSCH transmission is transmitted along with the multiplexed UCI. It is configured to do the following: The aforementioned processing timeline is: The initiation of the multi-slot PUSCH transmission is based on one or more of the following: transmission occasion-based interleaving for the multi-slot PUSCH transmission, or transmission occasion-based rate matching for the multi-slot PUSCH transmission, or The initiation of overlapping slots of the multi-slot PUSCH transmission based on one or more of the following: slot-based interleaving for the multi-slot PUSCH transmission, or slot-based rate matching for the multi-slot PUSCH transmission, Based on, Device.

13. A non-temporary computer-readable medium for storing computer executable code in user equipment (UE), wherein the code, when executed by a processor, is transmitted to the processor. Applying a processing timeline for multiplexing uplink control information (UCI) in at least one slot of a multi-slot physical uplink shared channel (PUSCH) transmission, Based on the satisfaction of the processing timeline, the multiple slot PUSCH transmission is transmitted along with the multiplexed UCI. Have them do it, The aforementioned processing timeline is: The initiation of the multi-slot PUSCH transmission is based on one or more of the following: transmission occasion-based interleaving for the multi-slot PUSCH transmission, or transmission occasion-based rate matching for the multi-slot PUSCH transmission, or The initiation of overlapping slots of the multi-slot PUSCH transmission based on one or more of the following: slot-based interleaving for the multi-slot PUSCH transmission, or slot-based rate matching for the multi-slot PUSCH transmission, Based on, Non-temporary computer-readable media.

Images