Multiplexing of uplink transmissions

Abstract

This disclosure relates to techniques for performing wireless communications, including multiplexing of uplink control information communications with other communications between a user equipment device (UE) and a base station. Techniques for generating control information and performing multiplexing are disclosed. The UE can select resources for multiplexing and determine how / whether to generate response data for various downlink transmissions.

Description

Technical Field

[0001] This application relates to wireless communication, including multiplexing of uplink transmissions. Background Technology

[0002] The use of wireless communication systems is growing rapidly. Furthermore, wireless communication technology has evolved from solely voice communication to also include the transmission of data such as the internet and multimedia content.

[0003] Mobile electronic devices can take the form of smartphones or tablets that users typically carry. Wearable devices (also known as accessory devices) are a newer form of mobile electronic device; an example is a smartwatch. Additionally, low-cost, low-complexity wireless devices designed for static or dynamic deployment are rapidly increasing as part of the development of the “Internet of Things”. In other words, the range of required device complexity, capabilities, traffic patterns, and other characteristics is becoming increasingly broad. Generally, there is a desire to recognize and provide improved support for a wide range of desired wireless communication features. One feature could be multiplexing of uplink control and / or data communications. Improvements in this area are expected. Summary of the Invention

[0004] This document presents implementations of systems, apparatuses, and methods, particularly for performing multiplexing of uplink communications in wireless communication systems (e.g., New Radio (NR), for example, at frequencies above 52.6 GHz).

[0005] As mentioned above, the number of use cases for communicating with different types of user equipment (UEs) with a wide range of capabilities and usage expectations is increasing. One direction for expanding the possible use cases supported by wireless communication technologies can include increasing the use of techniques for scheduling multiple communications, such as multiple Physical Uplink Shared Channel (PUSCH) and / or Physical Downlink Shared Channel (PDSCH) transmissions (e.g., multiple PxSCH). Multiple PUSCH transmissions can, for example, be multiplexed with uplink control information (UCI) on the Physical Uplink Control Channel (PUCCH). Similarly, multiple PDSCH transmissions can, for example, be multiplexed with downlink control information (DCI) on the Physical Downlink Control Channel (PDCCH). Therefore, the techniques described herein include techniques for UEs and base stations to perform such multiplexing, for example, the multiplexing of UCI and uplink data in multiple PUSCHs that overlap with the PUCCH.

[0006] For example, the UE can establish communication with a base station. The base station can provide the UE with control and / or configuration information. The base station can transmit control information to the UE to schedule uplink and / or DL ​​transmissions, such as multiple PUSCH transmissions. The UE can exchange communication with the base station as scheduled by the control information. The UE can generate uplink control information. The uplink control information may include response data for one or more downlink transmissions. For example, UCI may include acknowledgments and / or negative acknowledgments for PDSCH transmissions. The UE can select resources to multiplex uplink control information with uplink data transmissions. To generate response data and / or select resources, the UE may consider factors such as scheduling, indications in the control information, processing delays, and / or the relative timing of various transmissions. The UE can transmit uplink control information.

[0007] The technologies described herein can be implemented in and / or used with a variety of different types of devices, including but not limited to mobile phones or smartphones (e.g., iPhones). TM Based on Android TM Phones), tablets (e.g., iPads) TM Samsung Galaxy TM ), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPhone TM Any of the following: wearable devices (e.g., smartwatches, smart glasses), laptops, PDAs, portable internet devices, music players, data storage devices, other handheld devices, vehicles, automobiles, unmanned aerial vehicles (e.g., drones) and unmanned flight controllers, other cellular network infrastructure equipment, servers, and various other computing devices.

[0008] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0009] A better understanding of the subject matter can be obtained by considering the following specific description of the implementation scheme in conjunction with the accompanying drawings.

[0010] Figure 1 An exemplary wireless communication system including accessory devices according to some embodiments is shown;

[0011] Figure 2 An exemplary wireless communication system is shown, according to some embodiments, in which two wireless devices are capable of performing direct device-to-device communication;

[0012] Figure 3 This is a block diagram illustrating an example wireless device according to some implementation schemes;

[0013] Figure 4 This is a block diagram illustrating an exemplary base station according to some implementation schemes;

[0014] Figure 5 This is a communication flowchart illustrating an exemplary method for multiplexed uplink communication according to some implementation schemes;

[0015] Figures 6 to 16 The multiplexing aspects of uplink communication according to some implementation schemes are illustrated.

[0016] While the features described herein are susceptible to various modifications and alternatives, specific embodiments thereof are illustrated by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit this document to the specific forms disclosed, but rather are intended to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0017] Acronyms and Abbreviations

[0018] The following acronyms and abbreviations are used in this disclosure:

[0019] 3GPP: Third Generation Partnership Project

[0020] 3GPP2: Third Generation Partnership Project 2

[0021] GSM: Global System for Mobile Communications

[0022] UMTS: Universal Mobile Telecommunication System

[0023] LTE: Long Term Evolution

[0024] RRC: Radio Resource Control

[0025] MAC: Media Access Control

[0026] CE: Control Element

[0027] Tx: Transmit (or transmit)

[0028] Rx: Accept (or receive)

[0029] RS: Reference signal

[0030] CSI: Channel State Information

[0031] PDCP: Packet Data Convergence Protocol

[0032] RLC: Radio Link Control

[0033] the term

[0034] The following are definitions of the terms used in this disclosure:

[0035] Memory media—any device of any type of nontransitory memory device or storage device. The term "memory media" is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory media" may include two or more memory media that may reside in different locations on different computer systems, for example, connected via a network. Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.

[0036] Carrier medium—the memory medium as described above, and physical transmission medium, such as buses, networks and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals or digital signals).

[0037] Programmable hardware elements—including a variety of hardware devices comprising multiple programmable functional blocks connected via programmable interconnects. Examples include FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field-Programmable Object Arrays), and CPLDs (Complex PLDs). Programmable functional blocks can vary from fine-grained (combinatorial logic units or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as “configurable logic units.”

[0038] Computer system—any of all types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, networked appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0039] User equipment (UE) (or “UE device”) — any of various types of computer systems or devices that are mobile or portable and perform wireless communication. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). TM Based on Android TM Phones), tablets (e.g., iPads) TM Samsung Galaxy TM ), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPhone TM Wearable devices (e.g., smartwatches, smart glasses), laptops, PDAs, portable internet devices, music players, data storage devices, other handheld devices, vehicles, automobiles, unmanned aerial vehicles (e.g., drones), and unmanned flight controllers, etc. Generally speaking, the term "UE" or "UE device" can be broadly defined as any electronic device, computing device, and / or telecommunications device (or a combination of these devices) that is easily transportable by the user and capable of wireless communication.

[0040] A wireless device is any of various types of computer systems or devices that perform wireless communication. A wireless device can be portable (or mobile), or it can be stationary or fixed in a location. A UE is an example of a wireless device.

[0041] A communication device is any of various types of computer systems or devices that perform communication, which may be wired or wireless. A communication device may be portable (or mobile), or it may be stationary or fixed in a location. A wireless device is one example of a communication device. A UE is another example of a communication device.

[0042] Base station—The term “base station” has the full range of its common meaning and includes at least a wireless communication station that is installed in a fixed location and used for communication as part of a wireless communication system.

[0043] Link budget constrained—encompassing the full range of its general meaning, and at least including the characteristics of a wireless device (e.g., a UE) that exhibits limited communication capabilities or limited power relative to devices that are not link budget constrained or relative to devices for which a Radio Access Technology (RAT) standard has been developed. Link budget constrained wireless devices may suffer from relatively limited receiving and / or transmitting capabilities, which may be due to one or more factors such as device design, device size, battery size, antenna size or design, transmit power, receive power, current transmission medium conditions, and / or other factors. Such devices may be referred to herein as “link budget constrained” (or “link budget limited”) devices. Devices may be inherently link budget constrained due to their size, battery power, and / or transmit / receive power. For example, a smartwatch communicating with a base station via LTE or LTE-A may be inherently link budget constrained due to its reduced transmit / receive power and / or reduced antenna. Wearable devices such as smartwatches are generally link budget constrained devices. Alternatively, the device may not be inherently link budget limited, for example, it may have sufficient size, battery power, and / or transmit / receive power for normal communication via LTE or LTE-A, but may be temporarily link budget limited due to current communication conditions, such as a smartphone at the cell edge. It should be noted that the term "link budget limited" includes or encompasses power limitations, and therefore a link-limited device can be considered a link budget-limited device.

[0044] A processing element (or processor) is a component or combination of components capable of performing the functions of a device (such as a user equipment device or a cellular network device). A processing element may include, for example: a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a single processor, a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware components such as a Field-Programmable Gate Array (FPGA), and any combination thereof.

[0045] Automatic—means an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform that action or operation. Therefore, the term "automatically" is the opposite of an operation performed or specified manually by a user, where the user provides input to directly perform the operation. An automatic process can be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input specifying information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system (e.g., software executed on the computer system) which analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, the user can invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.

[0046] "Configured as"—Various components can be described as being "configured as" to perform one or more tasks. In such contexts, "configured as" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured as" can also be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently powered on. Typically, the circuit forming the structure corresponding to "configured as" can include hardware circuitry.

[0047] For ease of description, various components may be described as performing one or more tasks. Such descriptions shall be interpreted as including the phrase “configured to”. The statement that a component is configured to perform one or more tasks is expressly intended not to invoke the interpretation of paragraph 6 of section 112 of title 35 of the United States Code.

[0048] Figures 1-2 —Wireless communication system

[0049] Figure 1 An example of a wireless cellular communication system is illustrated. It should be noted that... Figure 1This represents one of many possibilities, and the features of this disclosure can be implemented in any of various systems as needed. For example, the embodiments described herein can be implemented in any type of wireless device.

[0050] As shown in the figure, an exemplary wireless communication system includes a cellular base station 102 that communicates with one or more wireless devices 106A, 106B, etc., and an accessory device 107 via a transmission medium. Wireless devices 106A, 106B, and 107 may be user equipment, which may be referred to herein as "user equipment" (UE) or UE device.

[0051] Base station 102 may be a transceiver base station (BTS) or a cell site and may include hardware and / or software to enable wireless communication with UE device 106A, UE device 106B, and UE device 107. If base station 102 is implemented in an LTE environment, it may be referred to as an "eNodeB" or "eNB". If base station 102 is implemented in a 5G NR environment, it may alternatively be referred to as a "gNodeB" or "gNB". Base station 102 may also be equipped to communicate with network 100 (e.g., the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet, and various other possible networks). Therefore, base station 102 facilitates communication between UE device 106 and UE device 107 and / or communication between UE device 106 / 107 and network 100. Also as used herein, in relation to the UE, a base station may sometimes be considered to represent the network, taking into account both uplink (UL) and downlink (DL) communication of the UE. Therefore, a UE that communicates with one or more base stations in the network can also be understood as a UE that communicates with the network.

[0052] In other specific implementations, base station 102 may be configured to provide communication via one or more other wireless technologies, such as an access point that supports one or more WLAN protocols (such as 802.11a, b, g, n, ac, ad and / or ax, or LTE in an unlicensed frequency band (LAA)).

[0053] The communication area (or coverage area) of base station 102 may be referred to as a "cell". Base station 102 and UE 106 / 107 may be configured to communicate using any of the following technologies via a transmission medium: Radio Access Technology (RAT), LTE, Advanced LTE (LTE-A), NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-Fi, etc.

[0054] Therefore, base station 102 and other similar base stations (not shown) operating according to one or more cellular communication technologies can be provided as a cell network that can provide continuous or near-continuous overlapping services to UE devices 106A-N and UE devices 107 and similar devices within a geographical area via one or more cellular communication technologies.

[0055] It should be noted that, at least in some cases, UE devices 106 / 107 may be able to communicate using any of a variety of wireless communication technologies. For example, UE devices 106 / 107 may be configured to communicate using one or more of the following: GSM, UMTS, CDMA2000, LTE, LTE-A, NR, WLAN, Bluetooth, one or more Global Navigation Satellite Systems (GNSS, such as GPS or GLONASS), one and / or more mobile television broadcasting standards (e.g., ATSC-M / H). Other combinations of wireless communication technologies (including more than two wireless communication technologies) are also possible. Similarly, in some cases, UE devices 106 / 107 may be configured to communicate using only a single wireless communication technology.

[0056] UE 106A and UE 106B may include handheld devices such as smartphones or tablets, and / or may include any of a variety of devices with cellular communication capabilities. For example, one or more of UE 106A and UE 106B may be wireless devices designed for static or dynamic deployment, such as home appliances, measuring devices, control devices, etc. UE 106B may be configured to communicate with UE device 107, which may be referred to as accessory device 107. Accessory device 107 may be any of a variety of wireless devices, which may typically be a wearable device with a small form factor and limited battery, output power, and / or communication capabilities relative to UE 106. As a common example, UE 106B may be a smartphone carried by a user, and accessory device 107 may be a smartwatch worn by the same user. UE 106B and accessory device 107 may communicate using any of a variety of short-range communication protocols such as Bluetooth or Wi-Fi. In some cases, UE106B and accessory device 107 may utilize ProSe technology, for example, in a manner supported by a cellular base station, to perform direct peer-to-peer communication. For instance, such ProSe communication may be performed as part of a relay link to support a radio resource control connection between accessory device 107 and BS102, as described in the various embodiments herein.

[0057] UE 106B can also be configured to communicate with UE 106A. For example, UE 106A and UE 106B may be able to perform direct device-to-device (D2D) communication. D2D communication may be supported by cellular base station 102 (e.g., easily discovered by BS 102, and with various possible forms of assistance), or may be performed in ways not supported by BS 102. For example, it is possible that UE 106A and UE 106B can deploy and perform D2D communication (e.g., including discovery communication) even when BS 102 and other cellular base stations have no coverage.

[0058] The BS 102 can control one or more Transmit and Receive Points (TRPs) and can use the TRPs to communicate with the UE. The TRPs can be arranged alongside the BS and / or located in separate physical locations.

[0059] Figure 2 An exemplary BS 102 is shown communicating with UE device 106, which in turn communicates with accessory device 107. UE device 106 and accessory device 107 can be any of a mobile phone, tablet or any other type of handheld device, smartwatch or other wearable device, media player, computer, laptop, unmanned aerial vehicle (UAV), unmanned flight controller, vehicle, or virtually any type of wireless device. In some embodiments, the accessory device may be a wireless device designed to have low cost and / or low power consumption and may support communication with BS 102 thanks to a relay link with UE device 106 (and / or another companion device). For example, in Figure 2 In the exemplary scenarios described herein, a device that communicates with a cellular base station using a relay link with another wireless device may also be referred to herein as a remote wireless device, a remote device, or a remote UE device, and a wireless device providing such a relay link may also be referred to herein as a relay wireless device, a relay device, or a relay UE device. According to some implementations, such BS 102, UE 106, and accessory device 107 may be configured to perform radio resource control procedures on the remote wireless device according to the various techniques described herein.

[0060] Both UE 106 and accessory device 107 may include a device or integrated circuit, referred to as a cellular modem, for facilitating cellular communication. The cellular modem may include one or more processors (processing elements) configured to execute program instructions stored in memory and / or various hardware components described herein. UE 106 and / or accessory device 107 may each execute any of the method embodiments described herein by executing such stored instructions. Alternatively or additionally, UE 106 and / or accessory device 107 may include programmable hardware elements, such as FPGAs (Field-Programmable Gate Arrays), integrated circuits, and / or various other possible hardware components, configured (e.g., individually or in combination) to perform any of or any portion of any of the method embodiments described herein. The cellular modem described herein can be used in UE devices as defined herein, wireless devices as defined herein, or communication devices as defined herein. The cellular modem described herein can also be used in base stations or other similar network-side devices.

[0061] UE 106 and / or accessory device 107 may include one or more antennas for communicating according to one or more RAT standards using one or more wireless communication protocols. In some embodiments, one or both of UE 106 or accessory device 107 may be configured to communicate using a single shared radio component. The shared radio may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communication. Typically, the radio component may include any combination of baseband processor, analog radio frequency (RF) signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.) or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains.

[0062] Alternatively, UE 106 and / or accessory device 107 may include two or more radio components. For example, in some embodiments, UE 106 and / or accessory device 107 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol for which it is configured to communicate. As another possibility, UE 106 and / or accessory device 107 may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components uniquely used by a single wireless communication protocol. For example, UE 106 and / or accessory device 107 may include shared radio components for communication using either LTE or CDMA2000 1xRTT (or LTE or NR, or LTE or GSM), and for communication using Wi-Fi and BLUETOOTH. TM Each component communicates with a separate radio unit. Other configurations are also possible.

[0063] Figure 3 —Block diagram of UE device

[0064] Figure 3 A possible block diagram of a UE device, such as UE device 106 or 107, is shown. As shown, UE device 106 / 107 may include a System-on-Chip (SOC) 300, which may include components for various purposes. For example, as shown, SOC 300 may include a processor 302 and display circuitry 304, the processor 302 executing program instructions for UE device 106 / 107, and the display circuitry 304 performing graphics processing and providing display signals to a display 360. SOC 300 may also include motion sensing circuitry 370, which may detect motion of UE 106, for example, using a gyroscope, accelerometer, and / or any of various other motion sensing components. Processor 302 may also be coupled to memory management unit (MMU) 340, which may be configured to receive addresses from processor 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, flash memory 310) and / or other circuitry or devices, such as display circuitry 304, radio components 330, I / F 320, and / or display 360. MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, MMU 340 may be included as part of processor 302.

[0065] As shown in the figure, the SOC 300 can be coupled to various other circuits of the UE 106 / 107. For example, the UE 106 / 107 may include various types of memory (e.g., including NAND flash memory 310), connector interface 320 (e.g., for coupling to computer systems, docking stations, charging stations, etc.), display 360, and wireless communication circuitry 330 (e.g., for LTE, LTE-A, NR, CDMA2000, Bluetooth, Wi-Fi, NFC, GPS, etc.).

[0066] UE device 106 / 107 may include at least one antenna and, in some embodiments, may include multiple antennas 335a and 335b for performing wireless communication with a base station and / or other devices. For example, UE device 106 / 107 may use antennas 335a and 335b to perform wireless communication. As described above, UE device 106 / 107 may be configured in some embodiments to perform wireless communication using multiple wireless communication standards or radio access technologies (RATs).

[0067] The wireless communication circuitry 330 may include a Wi-Fi logic component 332, a cellular modem 334, and a Bluetooth logic component 336. The Wi-Fi logic component 332 enables the UE device 106 / 107 to perform Wi-Fi communication over an 802.11 network. The Bluetooth logic component 336 enables the UE device 106 / 107 to perform Bluetooth communication. The cellular modem 334 may be a low-power cellular modem capable of performing cellular communication according to one or more cellular communication technologies.

[0068] As described herein, UE 106 / 107 may include hardware and software components for implementing embodiments of this disclosure. For example, by executing program instructions stored on a storage medium (e.g., a non-transitory computer-readable storage medium), the processor 302 of UE device 106 / UE device 107 may be configured to implement part or all of the methods described herein. In other embodiments, processor 302 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Furthermore, processor 302 may be coupled to, for example, Figure 3Other components shown and / or interoperable with said other components are used to perform radio resource control procedures for remote wireless devices according to various embodiments disclosed herein. Processor 302 may also implement various other applications and / or end-user applications running on UE 106. Alternatively or additionally, one or more components of the wireless communication circuitry 330 (e.g., cellular modem 334) of UE device 106 / 107 may be configured, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), a processor configured as an FPGA (Field Programmable Gate Array), and / or a processor using dedicated hardware components that may include ASICs (Application-Specific Integrated Circuits) to implement part or all of the methods described herein.

[0069] Figure 4 —Block diagram of a base station

[0070] Figure 4 An exemplary block diagram of a base station 102 according to some embodiments is shown. It should be noted that... Figure 4 The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include a processor 404 capable of executing program instructions specific to base station 102. Processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuitry or device, which may be configured to receive addresses from processor 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450).

[0071] Base station 102 may include at least one network port 470. (As mentioned above...) Figure 1 and Figure 2 As described herein, network port 470 can be configured to be coupled to a telephone network and provide access to multiple devices, such as UE devices 106 / 107, that have access to the telephone network.

[0072] Network port 470 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider. This core network may provide mobility-related services and / or other services to multiple devices, such as UE devices 106 / 107. For example, the core network may include, for instance, a Mobility Management Entity (MME) for providing mobility management services, a Serving Gateway (SGW) and / or a Packet Data Network Gateway (PGW) for providing external data connections such as to the Internet, and so on. In some cases, network port 470 may be coupled to a telephone network via the core network, and / or the core network may provide the telephone network (e.g., between other UE devices served by the cellular service provider).

[0073] Base station 102 may include at least one antenna 434 and possibly multiple antennas. One or more antennas 434 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE device 106 / 107 via radio component 430. Antenna 434 communicates with radio component 430 via communication link 432. Communication link 432 may be a receive link, a transmit link, or both. Radio component 430 may be configured to communicate via various wireless communication standards, including but not limited to LTE, LTE-A, NR, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0074] Base station 102 can be configured to perform wireless communication using multiple wireless communication standards. In some cases, base station 102 may include multiple radios that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio for performing communication according to LTE and a Wi-Fi radio for performing communication according to Wi-Fi. In such a case, base station 102 may be able to operate as both an LTE base station and a Wi-Fi access point. As another possibility, base station 102 may include a multi-mode radio component capable of performing communication according to any of multiple wireless communication technologies (e.g., LTE and NR, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0075] As further described herein, base station 102 may include hardware and software components for implementing or supporting embodiments of the features described herein. According to some embodiments, processor 404 of base station 102 may be configured to implement some or all of the methods described herein, for example by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, processor 404 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 430, 432, 434, 440, 450, 460, 470, processor 404 of BS 102 may be configured to implement or support radio resource control procedures for remote wireless devices according to the various embodiments described herein, and / or any of the various other features of the features described herein.

[0076] Figure 5 Multiplexing

[0077] Using a single scheduling message to schedule multiple communications allows for a reduction in overhead, for example, compared to individual scheduling of communications. Therefore, wireless communications such as New Radio (NR) and Unlicensed NR (NR-U) can support mechanisms for scheduling multiple uplink (UL) and / or downlink (DL) communications (e.g., occurring within a certain time period) using a single scheduling message. For example, for a single UE, the base station can schedule multiple Physical UL Shared Channel (PUSCH) and / or Physical DL Shared Channel (PDSCH) transmissions together (e.g., multiple PxSCHs can refer to multiple UL and / or DL ​​communications on corresponding shared channels). Using a single scheduling message to schedule multiple communications also allows the base station to schedule across multiple time slots. For example, the PDCCH can be monitored (e.g., by the UE) / transmitted (e.g., by the base station) once every few time slots (e.g., every third time slot, etc.). In some implementations, such periodic PDCCH monitoring can reduce the complexity of PDCCH monitoring, which may arise from the reduction in time slot / symbol size due to the increased subcarrier spacing of 480 kHz and 960 kHz.

[0078] It should be understood that monitoring PDCCH in multiple time slots can differ from semi-persistent scheduling (SPS). In SPS, DCI can activate SPS transmission, and then the UE expects PDCCH every X time slots. A new DCI may not be needed until the SPS transmission is stopped by a second DCI. SPS can be applied to PDCCH, while multi-slot monitoring can be applied to PDCCH. In multi-slot monitoring, the UE can expect one DCI every X time slots. In this case, the UE can perform blind decoding every X time slots. The PDCCH monitoring budget (BD / CCE budget) can be defined over multiple new time slots. This can differ from previous standards, where they were defined at the time slot or sub-slot granularity. This can increase the timer (e.g., SCS t960), which can imply that the time slot duration decreases by a factor of 8 compared to the conventional approach. To prevent the UE from having to perform blind decoding 8 times as quickly as possible, the 8 time slots can be grouped into one, resulting in one PDCCH over the entire 8 time slots. Based on multiple PxSCH transmissions, one (e.g., a packet) PDCCH can schedule multiple PDSCH or PUSCH.

[0079] Downlink control information (DCI) messages can be examples of scheduling messages that can be used to schedule multiple communications (e.g., PDSCH, PUSCH, PDCCH, and / or PUCCH). In other words, scheduling for multiple communications can be provided in DCI signaling.

[0080] In cases where a single scheduling message schedules multiple uplink data transmissions (e.g., multiple PUSCHs), various possibilities exist for multiplexing uplink control information (UCI) (e.g., on the physical uplink control channel (PUCCH)). For example, such UCI may be or include response data, such as a hybrid automatic repeat request (HARQ) acknowledgment (ACK) or negative acknowledgment (NACK). The UE may generate response data to indicate whether one or more downlink data transmissions (e.g., downlink transmissions including control information) have been successfully received. The downlink transmission on which the response data is based may be scheduled by a single DCI or multiple DCIs. Among various possibilities, the UCI may also or alternatively include a scheduling request (SR) and / or channel state information (CSI).

[0081] It should be understood that, according to some implementation schemes, multiple PUSCHs may include different PUSCH transmissions in different time slots.

[0082] Figure 5 This is a communication flowchart illustrating an exemplary method for multiplexing one or more uplink data transmissions in UCI according to some embodiments. In various embodiments, some elements of the method shown may be performed simultaneously in a different order than shown, may be replaced by other method elements, or may be omitted. Additional method elements may also be performed as needed.

[0083] Figure 5 Various aspects of the method can be implemented by a UE such as UE 106 or 107, a cellular network, and / or one or more BSs 102, as needed as shown in and described with reference to the figures, or more generally in combination with any of the computer systems, circuits, elements, components, or devices shown in the figures. For example, one or more processors (or processing elements) (among various possibilities, such as processors 302, 404, baseband processors, processors associated with communication circuits such as 330, 332, 334, 336, 430, or 432, processors associated with various core network elements, etc.) can cause the UE, network elements, and / or BS to perform some or all of the illustrated method elements. It should be noted that while described in a manner involving the use of communication technologies and / or features associated with LTE, NR, and / or 3GPP specification documents... Figure 5 This description describes at least some elements of the method, but it is not intended to limit this disclosure and can be used in any suitable wireless communication system as needed. Figure 5 The method can be described in several aspects. As shown in the figure, the method can be operated as follows.

[0084] According to some implementation schemes, the UE and the base station can establish communication (502). The UE and the base station can communicate using one or more radio access technologies (RATs), such as NR. Among various possibilities, the UE and the base station can use any frequency resources for communication, including NR operation above 52.6 GHz. The UE and the base station can use one or more frequency carriers for communication, including licensed and / or unlicensed carriers. The base station can provide one or more cells and / or cell groups, and communication between the UE and the base station can use one or more cells and / or cell groups.

[0085] The base station can exchange configuration information with the UE. For example, the base station can use Radio Resource Control (RRC) and / or other higher-layer signaling to negotiate parameters and / or configure the UE. Among various possibilities, the configuration information may include various parameters related to the multiplexing UCI. The UE can provide, for example, capability information related to its multiplexing capabilities and / or other capabilities relative to the UCI. For example, the UE can provide information about relevant processing delay times.

[0086] For example, configuration information may include an indication of whether the UE can be expected to have more than one PUCCH overlapping with a PUSCH, such as in multiple PUSCHs scheduled by a single DCI. Furthermore, a specific or maximum number of PUCCHs that can overlap with multiple PUSCHs can be established. Additionally, one or more configurations for selecting specific PUSCHs for multiplexing PUCCHs may be included, for example, indicated by the BS to the UE. For example, configuration information may indicate that one or more last PUSCHs are available for multiplexing, or that a specific pattern of PUSCHs (e.g., every third PUCCH, etc.) is available for multiplexing.

[0087] As another example, the configuration may include one or more timelines for multiplexing PUCCH and PUSCH, such as in multiple PUSCH. For example, the UE and the base station may negotiate one or more processing delay values ​​for a specific situation. A first processing delay may describe the minimum amount of time the UE takes to receive downlink data transmission (e.g., PDSCH), generate response data, perform multiplexing of the response data with other uplink data and / or UCI, and transmit the response data (e.g., multiplexed on PUSCH). In various possibilities, such processing delay may be represented as multiple symbols following downlink data transmission.

[0088] Another processing delay can describe the time period during which the UE can provide a negative acknowledgment, for example, for any downlink data transmission scheduled during the time period (e.g., regardless of whether it is successfully received). The length of this time period may be the same as or different from the first processing delay described above. However, it can be applied at different times and / or may involve different behaviors.

[0089] Similarly, the processing delay associated with the handover bandwidth portion (BWP) can be configured. This processing delay can describe the minimum amount of time (e.g., in symbols, etc.) required for the UE to receive the DCI indicating a change in the BWP, prepare for uplink transmissions (e.g., PUCCH and / or PUSCH), and transmit on the new BWP. Among various possibilities, the processing delay associated with BWP handover may be referred to as N2.

[0090] Furthermore, according to some embodiments, the configuration information may include the identification of transmissions for which their measurement processing delay occurs. For example, the processing delay may refer to a time period preceding any type of first uplink transmission. Alternatively, the processing delay may refer to a time period preceding a first uplink transmission including UCI (e.g., multiplexed with other UL data). As another possibility, the processing delay may be iteratively applied to corresponding time periods preceding respective uplink transmissions. For example, a first processing delay may be applied between a DL transmission and a UL transmission that will include response data for the DL transmission; a second processing delay may be applied between a second DL transmission and a second UL transmission that will include response data for the second DL transmission, which precedes a second uplink transmission that will include response data for the second DL transmission, etc. The second processing delay may have the same length as the first processing delay. In some embodiments, the length may be different. In some embodiments, the identification of transmissions for which their measurement processing delay occurs may be determined by standardization.

[0091] According to some implementations, the base station may transmit configuration information (504) to the UE. Control information may schedule UL and / or DL ​​communications, such as control information and / or data. Control information may include one or more DCI messages, such as any of various DCI formats. For example, one DCI may schedule one or more DL transmissions, including data transfers (e.g., PDSCH transmissions) and / or control information (e.g., PDCCH transmissions). Another DCI may schedule one or more uplink data transmissions (e.g., multiple PUSCHs). One or more PUSCHs of multiple PUSCHs may overlap with PUCCHs. PUSCHs overlapping with PUCCHs may be candidates for multiplexing UCIs (e.g., including SR, CSI, and / or HARQ response data, etc.). Any number of DCI messages scheduling UL and DL transmissions may be transmitted in any order. In some implementations, a single DCI message may schedule both UL and DL transmissions, for example, multiple PxSCHs.

[0092] In some implementations, control information may include semi-persistent scheduling (SPS). For example, control information may include SPS authorization for the PDSCH, such as scheduling periodic downlink transmissions. SPS may be scheduled by DCI.

[0093] In some implementations, the base station may include indications in the control information regarding how / whether the UE should multiplex UCI (e.g., response data) with other UL transmissions. For example, the base station may include one or more indications in the DCI, such as the PUCCH Resource Index (PRI) and / or the UL-Total DL Allocation Index (UL-TDAI), which can be used to determine multiplexing.

[0094] According to some implementation schemes, the UE and the base station may exchange some or all of the communications scheduled by control information (506). For example, the UE may receive one or more DL transmissions (e.g., data / PDSCH and / or control information / PDCCH) from the base station. In some cases, some or all of the scheduled DL transmissions may not be successfully received by the UE.

[0095] According to some implementation schemes, the UE can determine the UCI and multiplexing for the UCI (508). For example, the UE can determine which DL transmissions to affirmatively acknowledge and / or which DL transmissions to negatively acknowledge. In other words, the UE can determine the HARQ response data for the DL transmissions.

[0096] Response data can be determined based on whether DL data is received and / or based on scheduling information. For example, in some implementations, the UE can determine some or all of the response data based on when it receives the DCI that schedules the DL transmission (e.g., relative to other events, such as the DCI that schedules a UL transmission opportunity that the UE can use for multiplexed response data). As another example, the UE can determine some or all of the response data based on the scheduling time of the DL transmission (e.g., relative to other events, such as the UL transmission opportunity that the UE can use for multiplexed response data or the first UL transmission of multiple PUSCHs).

[0097] The UE can determine the resources to be used for transmitting response data. For example, the UE can select one or more PUSCHs that overlap with the PUCCH for multiplexing response data. The UE can select the PUSCH to be used for multiplexing (e.g., from multiple overlapping PUSCHs) based on control information and / or based on other factors (e.g., the timing of the PUSCH). For example, the UE can consider indications in the DCI, such as the PUCCH Resource Index (PRI) and / or the UL-Total DL Allocation Index (UL-TDAI). As another example, the UE can consider the timing of the PUSCH relative to other events, such as the timing of the associated DL transmission, the timing of the DCI, and / or the timing / location of the PUSCH relative to other PUSCHs in a multi-PUSCH configuration.

[0098] According to some implementations, the base station can similarly determine (e.g., predict) the resources available to the UE. For example, the base station may consider indications, scheduling information, relative timing, etc., included in the DCI. In other words, the base station can determine when (e.g., on what resources) UCI ​​is expected and how to interpret any response data received in various resources. For example, the base station can determine that response data received in a first resource corresponds to a first DL transmission, and response data received in a second resource corresponds to a second DL transmission. In other words, the base station can determine which PUSCH of multiple PUSCHs may include multiplexed UCI. In some implementations, the standards and / or configurations may be specific enough that they are explicit regarding the resources available to the UE. In some implementations, the specifications and / or configurations may allow for multiple possibilities. Therefore, the base station can determine multiple possible resources that the UE can use to provide UCI and can perform blind decoding of the possible resources.

[0099] According to some implementation schemes, the UE can multiplex the UCI and transmit the UCI in a defined resource (510). The base station can receive and decode the UCI. The base station can retransmit the UCI indicating any DL data for which its DL data was not received and / or any DL data that does not include its response data.

[0100] As mentioned above, Figure 5 The elements can occur in various orders and / or overlap. For example, it should be understood that 506, 508, and 510 can occur in any order and / or overlap. For example, communication (e.g., the communication in 506) can occur before and / or after generating response data (e.g., in 508) and / or transmitting response data (e.g., in 510).

[0101] Figures 6 to 9 —Digital and Signaling

[0102] Regarding multiplexing UCI and multiple PUSCH, various numbers of UCI transmissions (e.g., PUCCH) can be multiplexed. Similarly, various numbers of UL-TDAI fields can be defined for multiple PUSCH in a single DCI.

[0103] Figure 6 The diagram illustrates a timeline under some implementations where no more than one PUCCH can overlap with a PUSCH in a multi-PUSCH sequence. In other words, at most one PUCCH transmission can overlap with at most one PUSCH in a multi-PUSCH sequence.

[0104] As shown in the figure, the first DCI (e.g., format 1_Y) can schedule downlink transmissions (e.g., PDSCH 1). The first DCI may include an indication of the number of downlink transmissions, such as a counter downlink allocation index (CDAI). CDAI may be equal to 1, for example, corresponding to PDSCH 1. Y may be an integer describing a different DCI format, such as that used in the standard (e.g., 0-2, or possibly greater than 2, as additional DCI formats may be used).

[0105] The base station can transmit and the UE can (or may not) receive downlink data (e.g., PDSCH 1).

[0106] The second DCI (e.g., format 0_Z) can schedule a series of uplink transmissions (e.g., multiple PUSCHs, such as PUSCH 1-4 in the example). It may include a single UL-TDAI bit field, for example, set to 1. UL-TDAI may indicate that a PDSCH was previously transmitted, for example, and the base station has not yet received its response data (e.g., HARQ ACK / NACK). Z can be an integer describing a different DCI format, for example, as adopted by the standard (e.g., 0-2, or possibly greater than 2, as additional DCI formats may be adopted). In the various examples, Y and Z may be the same or different. In other words, any applicable DCI format can be used for the first or second DCI, for example, as needed.

[0107] The UE can generate response data, for example, based on whether downlink data was successfully received.

[0108] The UE can select time / frequency resources for multiplexed PUSCHs (e.g., PUSCHs of multiple PUSCHs) and response data (e.g., and / or other UCIs). For example, the UE can determine that only one PUSCH in the multiple PUSCHs overlaps with a PUCCH (e.g., PUSCH 3 in the example). Therefore, the UE can select the overlapping PUSCHs for multiplexed UCIs. Thus, the UE can transmit multiple PUSCHs scheduled by the DCI and having response data multiplexed on the selected resources.

[0109] According to some implementation plans Figure 6 The method may rely on relatively simple signaling and may not allow multiple response data transmissions with multiple PUSCH multiplexing.

[0110] Figure 7Another possibility according to some implementations is illustrated, where multiple possible resources may exist for multiplexing response data and uplink data, and the UE may select a single resource. In other words, the UE may use no more than one valid PUCCH (e.g., a PUCCH selected after UCI multiplexing) that overlaps with at most one PUSCH within a multi-slot PUSCH. For example, the valid PUCCH may be the final PUCCH.

[0111] As shown in the figure, a first DCI (e.g., format 1_0) can schedule a first downlink transmission (e.g., PDSCH 1) and a second DCI (e.g., format 1_0) can schedule a second downlink transmission (e.g., PDSCH 2). The first and second DCIs can include CDAIs of 1 and 2 (e.g., the second CDAI can count both PDSCH 1 and 2). It should be understood that a single DCI can schedule both PDSCH 1 and 2, and in this case, a single DCI can have 2 CDAIs.

[0112] The base station can transmit and the UE can (or may not) receive downlink data (e.g., PDSCH 1 and 2).

[0113] The third DCI (e.g., format 0_Z) can schedule a series of uplink transmissions (e.g., multiple PUSCHs, such as PUSCH 1-4 in the example). It may include a single UL-TDAI bit field, for example, set to 2. UL-TDAI may indicate that two PDSCHs were previously transmitted, for example, and the base station has not yet received their response data (e.g., HARQ ACK / NACK).

[0114] The UE can generate response data for the corresponding downlink data transmission. For example, it can generate two corresponding bits based on whether the corresponding downlink data was successfully received.

[0115] The UE can select time / frequency resources for multiplexing PUSCHs (e.g., PUSCHs of multiple PUSCHs) and response data (e.g., and / or other UCIs). For example, the UE can select a PUSCH that overlaps with a PUCCH in a multiple PUSCH (e.g., PUSCH 4 overlapping PUCCH 3 in the example). The UE can use the selected PUSCH to multiplex UCIs; for example, response data scheduled for downlink data transmission can be transmitted in (e.g., a single) selected PUSCH. Therefore, the UE can transmit multiple PUSCHs scheduled by the DCI and having response data multiplexed on the selected resources. In other words, a valid PUCCH (e.g., PUCCH 3 overlapping selected PUSCH 4) can be used for the transmission of response data.

[0116] As a possibility, for a single PUSCH, if multiple PUCCHs are scheduled across multiple time slots, the UE can select the valid PUCCH (e.g., where all UCIs on the PUCCH are multiplexed), and then if the PUCCH overlaps with the PUSCH, the UE can then multiplex the UCIs and the PUSCH. It should be understood that if no PUSCH is scheduled, the UE can transmit UCIs without multiplexing the PUSCH.

[0117] As another possibility, for the single PUSCH case, if multiple PUCCHs are scheduled across multiple time slots, the UE can select the valid PUCCH, and then if it overlaps with the transmission of multiple PUSCHs, the UE can multiplex it on a specific PUSCH.

[0118] As a possibility, in the case of multiple PUSCHs, if multiple PUCCHs are scheduled across multiple time slots, the UE can select multiple valid PUCCHs derived from the multi-time slot PUCCHs, and then multiplex these on the PUSCHs selected for multiplexing.

[0119] In some implementations, the selected PUSCH can be the final PUSCH overlapping with the PUCCH. In other words, the UE can select the time / frequency resources for multiplexing response data and uplink data by selecting the last overlapping PUSCH among multiple PUSCHs. In some implementations, overlapping PUSCH / PUCCHs can be selected based on different factors. For example, the UE can select the first overlapping PUSCH / PUCCH, which allows the UE sufficient time for its processing delays (e.g., to generate, multiplex, and transmit response data). As another possibility, the UE can select overlapping PUSCH / PUCCHs based on indications from the base station (e.g., in the DCI). For example, the DCI that schedules the PDSCH may include a corresponding PUCCH Resource Index (PRI) value, for example, corresponding to a corresponding downlink transmission. The PRI value can indicate the appropriate PUCCH opportunity for the UE to transmit response data for the corresponding downlink transmission.

[0120] It should be understood that other PUCCH timings (e.g., PUCCH 1-3) may also overlap with PUSCHs (e.g., PUSCH 1-4 respectively). According to some implementations, these other PUCCH timings may not be used (e.g., only PUSCHs may be transmitted during these times). Alternatively, the UE may transmit other UCIs (e.g., SR, CSI, etc.) on these other PUCCH timings. Furthermore, not all PUSCHs may overlap with PUCCHs (e.g., PUSCH 2).

[0121] therefore, Figure 7This method allows for increased flexibility because multiple PUCCH opportunities can overlap with PUSCH opportunities. However, response data can be transmitted in a single opportunity, similar to PUSCH multiplexing.

[0122] Figure 8 Methods according to some embodiments are illustrated, wherein any number (e.g., potentially all) of overlap opportunities for uplink data and control transmissions can be used for multiplexing response data. For example, within a multi-slot PUSCH, all UEs may have all PUSCHs overlapped by valid PUCCHs. Multiple UL-TDAI bit fields can be signaled in the DCI, for example, one bit field for each PUSCH scheduled by the DCI. In some embodiments, a UE may not have more than one PUCCH overlapping with each PUSCH per unit (e.g., per slot or per multi-slot transmission). In some embodiments, multiple PUCCHs may overlap with multiple PUSCHs. In this case, PUCCHs may be collapsed (e.g., merged) to overlap with the corresponding PUSCHs. For example, if PUCCH 1 and 2 overlap with PUSCH 1 and PUCCH 3 and 4 overlap with PUSCH 2, then: PUCCH 1 and 2 can collapse into a first combination of PUCCHs overlapping with PUSCH 1, and PUCCH 3 and 4 can collapse into a second combination of PUCCHs overlapping with PUSCH 2. Various rules for this collapse of PUCCHs can be adopted in the technical specification and / or established by configuration information (e.g., in 502).

[0123] As shown in the figure, a first DCI (or multiple first DCIs) (e.g., format 1_y) can schedule multiple (e.g., PDSCH 1-N) of N downlink transmissions. The first DCI (or the last DCI of the multiple first DCIs) may include a CDAI of N, for example, corresponding to N scheduled transmissions. The CDAI may indicate an index of the number of HARQs that have been sent up to the time of the DCI associated with the PDSCH.

[0124] In some implementations, the first DCI may include a corresponding PRI value, for example, corresponding to a corresponding downlink transmission. The PRI value may indicate the corresponding PUCCH opportunity for the UE to transmit response data for the corresponding downlink transmission. In other words, the PRI may indicate the resources on which the HARQ ACK associated with the DCI scheduling the DL PDSCH should be transmitted.

[0125] The base station can transmit and the UE can (or may not) receive downlink data (e.g., PDSCH 1-N).

[0126] Additional DCI (e.g., format 0_Z) can schedule a series of uplink transmissions (e.g., multiple PUSCHs, such as PUSCH 1-4 in the example). Multiple (e.g., four in the example) UL-TDAI bit fields may be included, each corresponding to a series of uplink transmissions. UL-TDAI (e.g., common) may indicate N PDSCHs previously transmitted to the UE, for example, and for which the base station has not yet received their response data (e.g., HARQ ACK / NACK). In some implementations, the corresponding UL-TDAI field may indicate the corresponding number of downlink transmissions for which the UE can transmit response data multiplexed with the corresponding uplink transmissions.

[0127] The UE can generate response data for the corresponding downlink data transmission. For example, it can generate N response bits based on whether the corresponding downlink data was successfully received.

[0128] The UE can multiplex response data with other UCI and / or uplink data, and can partition the multiplexed data within uplink resources (e.g., PUCCH / PUSCH 1-4). The UE (and the base station) can determine in various ways which specific downlink transmissions should have corresponding response data multiplexed with said specific uplink resources.

[0129] As a possibility, the UE can determine which parts of the response data should be transmitted in the corresponding resource based on the corresponding PRI. For example, response data associated with PRI=1 can be multiplexed for transmission via PUSCH 1, etc.

[0130] As another possibility, the UE can determine which parts of the response data should be transmitted in the corresponding resource based on the corresponding UL-TDAI. For example, response data associated with the PDSCH from 1 to the first UL-TDAI value (e.g., the first UL-TDAI field in DCI format 0_z) can be multiplexed for transmission through PUSCH 1, etc. In other words, the first UL-TDAI field can determine the number of downlink transmissions of multiplexed response data in PUSCH 1.

[0131] Figure 9Examples according to some implementations are shown, in which a UE may have more than one uplink data transmission opportunity (e.g., X PUSCHs) overlapping with UCI transmission opportunities (e.g., active PUCCHs) within multiple PUSCHs. The specific PUSCHs that can be multiplexed may be specified or configured by the base station. In some implementations, a predefined number of UL-TDAI bit fields may be transmitted for each PUSCH. The number of PUSCHs that can be multiplexed (e.g., X) may be specified (e.g., via 3GPP, etc.) or configured by the base station. In some implementations, the UE may determine the value of X based on the number of PUSCH opportunities overlapping with PUCCH opportunities. According to some implementations, the UE may not have more than one PUCCH overlapping with each PUSCH per unit (e.g., transmitted per time slot or per multi-time slot). Figure 9 In the example, X = 2.

[0132] For example, a base station may transmit a first DCI that schedules multiple (e.g., at least X) downlink data transmissions (e.g., PDSCHs). As shown in the figure, the BS may transmit two DCIs, each scheduling one PDSCH. In some implementations, the DCI may indicate the PRI value associated with the corresponding PDSCH.

[0133] The base station can transmit and the UE can (or may not) receive downlink data (e.g., PDSCH 1 and 2).

[0134] The base station may transmit a second DCI to schedule multiple (e.g., more than X) uplink data transmissions (e.g., PUSCH). The second DCI may include X UL-TDAI fields. The X UL-TDAI fields may indicate to the UE corresponding downlink data transmissions including response data multiplexed with the corresponding uplink data transmissions. For example, a first UL-TDAI field may indicate to the UE a positive or negative acknowledgment of a first or more downlink data transmissions in a UCI multiplexed with a first uplink data transmission, and a second UL-TDAI field may indicate to the UE a positive or negative acknowledgment of a second or more downlink data transmissions in a UCI multiplexed with a second uplink data transmission, etc.

[0135] In some implementations, the base station may, for example, change the number of PDSCH transmissions before the last PUSCH in a multi-PUSCH transmission. For example, if the first DCI includes a first UL-TDAI, the base station may transmit a second UL-TDAI with a second DCI.

[0136] The UE can generate response data for the corresponding downlink data transmission. For example, it can generate two corresponding bits based on whether the corresponding downlink data was successfully received.

[0137] The UE can multiplex response data with other UCI and / or uplink data, and can partition the multiplexed data across X uplink resources available for multiplexing UCI and PUSCH (e.g., PUCCH1 and 2, which overlap with PUSCH 3 and 4, respectively). The UE can determine which responses are multiplexed on which resources based on PRI, UL-TDAI, and / or other indications from the base station (e.g., using the first or last available opportunity, etc.).

[0138] As one possibility, the UE may select the first X PUSCHs for multiplexing response data. For example, the UE may do so based on 3GPP standards, configuration information (e.g., as discussed in section 502), or instructions in the first or second DCI. The base station may set a schedule (e.g., in the first and / or second DCI) such that the multiplexing timeline allows the UE sufficient time (e.g., according to the processing delay discussed in section 502) to process the response data over the time of the first PUSCH (even if the first PUSCH does not necessarily overlap with the PUCCH).

[0139] As a second possibility, the UE may select a first X overlapping PUSCHs. For example, the UE may do so based on 3GPP standards, configuration information (e.g., discussion regarding 502), or indications in the first or second DCI. The base station may set a schedule (e.g., in the second DCI) such that the multiplexing timeline allows the UE sufficient time (e.g., according to the processing delay discussed regarding 502) to process the response data via the first PUSCH (e.g., even if the response data is multiplexed at the first overlapping PUSCH) or the first symbol of the first overlapping PUSCH. In a second case (e.g., when the processing delay is completed via the first symbol of the first overlapping PUSCH), the base station may rely on the processing delay measured from the corresponding downlink transmission to the corresponding overlapping PUSCH. In other words, the base station may set a schedule (e.g., in the first and / or second DCI) such that if the processing delay is measured from the latest downlink transmission to which the response data is to be transmitted during the corresponding overlapping PUSCH, the processing delay is completed via the first symbol of the corresponding overlapping PUSCH. Therefore, this allows for the later scheduling of downlink transmissions, since the processing delay of a later downlink transmission can be completed by the corresponding uplink transmission later (e.g., but not necessarily by an earlier uplink transmission).

[0140] As a third possibility, the UE can select available opportunities (e.g., overlapping PUSCHs) based on the number of opportunities (e.g., PUSCHs to be multiplexed) and the total number of uplink opportunities (e.g., scheduled PUSCHs). For example, if M is the number of scheduled PUSCHs and X is the number of multiplexed PUSCHs, then:

[0141] If M is less than or equal to 2, the UE can use the Mth scheduled PUSCH for multiplexing response data.

[0142] If M is greater than 2, the UE can use the later of the M opportunities. For example, the UE can use the (M-1)th to (MX-1)th scheduling PUSCH, which would result in the selection of the Xth opportunity near the end of the M opportunities (e.g., except for the last, e.g., the Mth opportunity).

[0143] In the second possibility, the base station may set a schedule (e.g., in the first and / or second DCI, or the schedule may be set or configured by the specification) such that the multiplexing timeline (e.g., processing delay) can be completed via the first PUSCH, although HARQ-ACK can be multiplexed on a later PUSCH. Alternatively, in the second possibility, the base station may set a schedule that depends on the processing delay measured from the corresponding downlink transmission to the corresponding overlapping PUSCH.

[0144] In some implementation schemes, Figure 9 This method can be applied to multi-PDSCH scenarios. For example, a DCI that schedules PDSCHs can schedule multiple PDSCHs through one or more PUCCHs. In some implementations, each of the multiple PUCCHs can be processed in the same way as a single PUCCH (e.g., scheduled by multiple corresponding DCIs), such as... Figure 6 As shown. Similarly, in the case of multiple DCI scheduling corresponding to multiple PUCCH multi-PDSCH transmissions, multiple PUCCHs can be used, for example, as Figure 9 As shown in the image.

[0145] Figures 10 to 14 —Example of multiplexing behavior timeline

[0146] In some implementations, the base station may not provide an indication of the number of downlink transmissions for which the UE provides response data. For example, according to some implementations, the DCI format 0_0 may not include UL-TDAI. Therefore, if the DCI format used to schedule UL transmissions does not include UL-TDAI or another indication of the number of pending DL transmissions, the UE may not know the number of pending DL transmissions. For example, the UE may not be able to confirm whether the DCI for scheduling one or more DL transmissions may have been lost. In this case, the UE may determine whether any DL transmissions have been received (e.g., transmissions in a multi-PDSCH transmission, among various possibilities), and based on such determination, the UE may or may not multiplex the response data, for example, as... Figure 10-11As shown. For example, if the UE responds to multiple PDSCH transmissions in a PUSCH transmission scheduled by a DCI format without TDAI (e.g., DCI format 0_0), then if the UE receives at least one of the PDSCHs, the UE may generate a codebook; otherwise, the UE may not multiplex HARQ ACKs on the PUSCH transmission.

[0147] Figure 10 The diagram illustrates a scenario where at least one DL transmission has been received and the UE multiplexes response data according to some implementations. As shown, a first DCI (e.g., format 1_Y) can schedule multiple PDSCHs. A second DCI (e.g., format 0_Z, which may not include UL-TDAI) can schedule PUSCHs that overlap with the PUCCH. The UE can receive at least some PDSCHs. In the example, the UE can receive PDSCHs 1 and 2, but may not receive PDSCHs 3 and 4. In response to determining that at least one of the multiple PDSCHs has been received, the user UE can generate a codebook of response data (e.g., including ACKs for received DL transmissions and NACKs for known transmissions that were not received). The UE can multiplex the response data with the PUSCHs and transmit the response data to the base station. Based on the response data, the base station can determine when which PDSCHs (if any) were not received and retransmit them. It should be noted that if the codebook does not include responses (e.g., ACKs or NACKs) for at least some PDSCHs, the base station can determine that these PDSCHs were not received and retransmit them.

[0148] Figure 11The diagram illustrates a scenario where no DL transmission is received and the UE does not multiplex response data according to some implementations. As shown, a first DCI (e.g., format 1_Y) may schedule multiple PDSCHs. A second DCI (e.g., format 0_Z, which may not include UL-TDAI) may schedule PUSCHs that overlap with the PUCCH. The UE may not receive any of the PDSCHs (e.g., none of PDSCHs 1-4 were successfully received). In response to determining that a PDSCH among the multiple PDSCHs was not received, the user UE may not generate a codebook for response data. In other words, the UE may not send any NACKs for PDSCHs 1-4 multiplexed with the PUCCH, even though the PUCCH may overlap with the PUSCH. The UE may transmit the PUSCH. In some implementations, the UE may transmit other UCIs (e.g., CSI, SR) multiplexed with the PUCCH, but may not multiplex any response data from PDSCHs 1-4. In some implementations, response data from other DL transmissions may be multiplexed. Based on the lack of response data for PDSCH 1-4, the base station can determine that not all PDSCHs have been received and can retransmit them.

[0149] In some implementations, the base station can schedule a PUSCH that overlaps with the PUCCH before scheduling the PDSCH. Figures 12 to 14 An example of this situation is shown according to some implementation schemes. According to some implementation schemes, the UE may generate response data differently depending on the relative timing of various messages. In other words, the relative position of the DCI / PDSCH monitoring timing may affect how the UE generates and / or multiplexes HARQ responses.

[0150] Figure 12 The diagram illustrates a UE, according to some implementations, setting response data to NACK for DL ​​data transmission received too close (e.g., in time) to a UCI transmission opportunity. In other words, the UE can set any HARQ-ACK information in the HARQ-ACK codebook corresponding to a PDSCH reception or SPSPDSCH release scheduled by a DCI (e.g., format 1_0 or DCI format 1_1) detected by the UE during a PDCCH monitoring opportunity, which occurs after the UE detects a PDCCH monitoring opportunity of a DCI (e.g., format 0_0 or format 0_1, etc.) that schedules a PUSCH transmission and within a specified timeline on which the HARQ-ACKed PUSCH will be multiplexed. Therefore, negative acknowledgment of PDSCHs (e.g., regardless of whether they are successfully received) can be performed based on both the timing of the DCI and the timing of the DL transmission.

[0151] As shown in the figure, the first DCI (e.g., format 0_1) can schedule one or more PUSCHs that overlap with the PUCCH. For example, PUSCH 2 can overlap with the PUCCH. The second DCI (e.g., format 1_1) can schedule one or more PDSCHs, for example, before the PUSCH that overlaps with the PUCCH. PDSCH 1 can be transmitted sufficiently before the overlapping PUSCH, and the UE can positively acknowledge PDSCH 1 within the overlapping PUSCH (e.g., via multiplexed PUCCH) (e.g., if PDSCH 1 is successfully received). However, PDSCH 2 may not be transmitted sufficiently before the overlapping PUSCH to allow processing. In other words, PDSCH 2 can be transmitted relative to the overlapping PUSCH during a processing delay period (e.g., shown as Nx). Therefore, the UE can generate a NACK for PDSCH 2 and can multiplex the NACK for transmission via PUSCH 2. It should be understood that PDSCH 2 can be negatively acknowledged during PUSCH 2, regardless of whether PDSCH 2 is successfully received. The UE can, for example, determine the pre-generated NACK for PDSCH 2 based on scheduling information.

[0152] As discussed in 502, processing delay timelines (e.g., NX) may include PDSCH decoding time, HARQ preparation time, and PUSCH preparation time, depending on some implementation.

[0153] Figure 13 The diagram illustrates a UE, according to some implementations, setting response data to NACK for DL ​​data transmission received too close (e.g., temporally) to the earliest UL transmission opportunity. In other words, the UE can set any HARQ-ACK information in its HARQ-ACK codebook corresponding to a PDSCH reception or SPSPDSCH release scheduled by a DCI (e.g., format 1_0 or format 1_1, etc.) detected by the UE during a PDCCH monitoring opportunity that occurs after the UE detects a PDCCH monitoring opportunity of a DCI (e.g., format 0_0 or format 0_1, etc.) that schedules multiple PUSCH transmissions and within the reasonable delay period of the first PUSCH in the multiplexed HARQ-ACK.

[0154] As shown in the figure, the first DCI (e.g., format 0_1) can schedule one or more PUSCHs that overlap with the PUCCH. For example, PUSCH 2 can overlap with the PUCCH. The second DCI (e.g., format 1_1) can schedule one or more PDSCHs, for example, before the PUSCHs that overlap with the PUCCH. PDSCH 1 can be transmitted sufficiently before the first PUSCH, and the UE can affirmatively acknowledge PDSCH 1 in the overlapping PUSCH (e.g., via multiplexed PUCCH) (e.g., if PDSCH 1 is successfully received). However, PDSCH 2 may not be transmitted sufficiently before the first PUSCH to allow processing. In other words, PDSCH 2 may be transmitted relative to the first PUSCH during a processing delay period (e.g., denoted as Nx). Similarly, PDSCH 3 may not be transmitted before the first PUSCH. Therefore, it may also not be sufficiently preceded (e.g., regardless of its time relative to the overlapping PUSCH). Therefore, the UE can generate NACKs for PDSCH 2 and 3, and can multiplex the NACKs for transmission via PUSCH 2. It should be understood that PDSCH 2 and 3 can be negatively acknowledged during PUSCH 2, regardless of whether PDSCH 2 and / or 3 are successfully received. The UE can determine, for example, to pre-generate NACKs for PDSCH 2 and 3 based on scheduling information.

[0155] As discussed in 502, processing delay timelines (e.g., NX) may include PDSCH decoding time, HARQ preparation time, and multi-PUSCH preparation time, depending on some implementation.

[0156] Figure 14 The diagram illustrates how a UE sets response data to NACK for DL ​​data transmission scheduled by DCI after multiple PUSCHs are scheduled by DCI. For example, the UE can set any HARQ-ACK information in the HARQ-ACK codebook corresponding to a PDSCH reception or SPS PDSCH release scheduled by DCI (e.g., format 1_0 or 1_1) detected by the UE during a PDCCH monitoring event after the UE detects a PUSCH transmission scheduled by DCI (e.g., format 0_0 or 0_1, etc.).

[0157] As shown in the figure, the first DCI (e.g., format 0_1) can schedule one or more PUSCHs that overlap with the PUCCH. For example, PUSCH 2 can overlap with the PUCCH. The second DCI (e.g., format 1_1) can schedule one or more PDSCHs, for example, before the PUSCHs that overlap with the PUCCH. Based on the second DCI received after the first DCI, the UE can generate NACKs for PDSCHs 1, 2, and 3, and can multiplex the NACKs for transmission over PUSCH 2. It should be understood that PDSCHs 1-3 can be negatively acknowledged during PUSCH 2, regardless of whether PDSCHs 1, 2, and / or 3 are successfully received. The UE can predetermine the generation of NACKs for PDSCHs, for example, based on receiving the second DCI after receiving the first DCI. Processing delays can be disregarded.

[0158] Figures 15 to 16 —BWP Switching

[0159] Figure 15 and Figure 16 The processing latency relative to BWP switching and UL transmission is shown. The techniques in these figures are applicable to multiplexing on PUSCH for any DCI format.

[0160] Figure 15 The diagram illustrates processing delays relative to overlapping PUSCHs (e.g., PUSCH2) according to some implementation schemes. For example, at least N2 symbols preceding the first symbol of a specific PUSCH transmission in which the UE multiplexes HARQ-ACK information, the DCI format for handover of the DL BWP can be transmitted, where N2 is the PUSCH preparation time. In other words, the base station can determine to transmit the DCI for BWP handover. The base station can transmit the DCI at least N2 symbols preceding overlapping PUSCHs (e.g., PUSCH 2), for example, during the BWP handover area shown.

[0161] Figure 16 The diagram illustrates processing delays relative to the earliest PUSCH (e.g., PUSCH1) according to some implementation schemes. For example, at least N2 symbols prior to the first symbol of the first PUSCH transmission in a multi-PUSCH scheme may be transmitted in the DCI format for switching the DL BWP. N2 may be the PUSCH preparation time. In other words, the base station may determine to transmit the DCI for BWP switching. The base station may transmit the DCI at least N2 symbols prior to the first PUSCH (e.g., PUSCH 1), for example, during the BWP switching area shown.

[0162] exist Figure 15 and Figure 16In the example, it should be understood that the base station can adjust the timing of the DCI indicating BWP handover based on the processing delay N2. For example, the base station can transmit such a DCI earlier, such as before the processing delay of a previously scheduled PUSCH transmission. Alternatively, the base station can delay the transmission of the BWP handover DCI, such as until after the multi-PUSCH transmission is complete or until after the overlapping PUSCH transmission is complete. Therefore, the BWP handover DCI may not be applied to the current multi-PUSCH, but can be delayed. The BWP handover DCI can be transmitted after the current multi-PUSCH. Therefore, BWP handover can be implemented relative to a later transmission rather than the current multi-PUSCH. In other words, the base station can determine the latest time for the transmission of the BWP handover DCI. If the BWP handover DCI is transmitted before the latest time occurs, it can be transmitted after the current multi-PUSCH transmission or after any overlapping PUSCH in the current multi-PUSCH transmission.

[0163] In some implementations, the base station can be configured to avoid transmitting any DCI indicating a change in the BWP after the latest transmission time. Therefore, if the base station determines that the BWP has been changed and there is not enough time to transmit the DCI indicating the BWP change before the latest transmission time, the base station can wait until the multi-PUSCH is complete.

[0164] Additional Information and Implementation Plan

[0165] It should be understood that the DCI format described above and shown in the various figures is an example. In some implementations, different DCI formats may be used.

[0166] In some implementations, if multiple PUSCHs (e.g., scheduled by the same DCI) occur in the same time slot, the UE may revert to legacy behavior. For example, the UE may select a single PUSCH within the time slot. The UE can then use the selected PUSCH to multiplex any PUCCH to be transmitted during the time slot.

[0167] In a first set of embodiments, the apparatus may include: a processor configured to cause a user equipment (UE) to establish communication with a base station; to receive, at a first time, a first downlink control information (DCI) from the base station scheduling at least one uplink data transmission, the at least one uplink data transmission including uplink data transmission multiplexed with uplink Hybrid Automatic Repeat Request (HARQ) transport multiplexing; to receive, at a second time, a second DCI from the base station scheduling at least one downlink data transmission, wherein the second time is after the first time; and to determine a time period for which any corresponding downlink data transmission received during the at least one downlink data transmission during the time period will be negatively acknowledged regardless of whether the data transmission was successfully received. The corresponding downlink data transmission, wherein the time period is relative to one of: the time of a specific uplink data transmission in the at least one uplink data transmission; or the first time; receiving the specific downlink transmission in the at least one downlink data transmission from the base station during the time period; generating a negative acknowledgment for the specific downlink transmission in the at least one downlink data transmission based on receiving the specific downlink transmission in the at least one downlink data transmission during the time period; and transmitting the uplink data transmission multiplexed with the uplink HARQ transmission to the base station, the uplink HARQ transmission including the negative acknowledgment for the specific downlink transmission in the at least one downlink data transmission.

[0168] In some implementation schemes, the first and second timeframes include different monitoring times.

[0169] In some implementations, the time period is relative to the time of the specific uplink data transmission; and the specific uplink data transmission in the at least one uplink data transmission is the uplink data transmission multiplexed with the uplink HARQ transport.

[0170] In some implementations, the time period is relative to the time of the specific uplink data transmission; and the specific uplink data transmission in the at least one uplink data transmission is the earliest uplink data transmission in the at least one uplink data transmission.

[0171] In some implementations, the time period is relative to a first time; and the time period begins at the first time.

[0172] In some implementations, the time period ends when the uplink data transmission multiplexed with the uplink HARQ transport is being transmitted.

[0173] In some implementations, the time period is relative to the time of the specific uplink data transmission; and the time period includes multiple symbols prior to the start of transmission of the specific uplink data transmission.

[0174] In a second set of embodiments, the User Equipment (UE) may include: a radio component; and a processor operatively connected to the radio component and configured to cause the UE to: establish communication with a base station; receive one or more downlink control information (DCI) messages from the base station, the one or more DCI messages being: scheduling a plurality of uplink data transmissions; scheduling at least one downlink data transmission; and including at least one downlink allocation indicator associated with the at least one downlink data transmission; determining whether a first downlink data transmission of the at least one downlink data transmission has been received; generating uplink control information, the uplink control information including a first portion indicating whether the first downlink data transmission of the at least one downlink data transmission has been received; selecting the first uplink data transmission of the plurality of uplink data transmissions for multiplexing with at least the first portion of the uplink control information, at least in part based on the at least one downlink allocation indicator; and transmitting the plurality of uplink data transmissions to the base station, wherein the first uplink data transmission is multiplexed with the at least first portion of the uplink control information.

[0175] In some implementations, the one or more DCI messages include a first DCI message and a second DCI message, the first DCI message scheduling the at least one downlink data transmission, and the second DCI message scheduling the plurality of uplink data transmissions and including the at least one downlink allocation indicator.

[0176] In some implementations, during the time when the PUSCH overlaps with the Physical Uplink Control Channel (PUCCH), the first uplink data transmission, which is multiplexed with at least a first portion of the uplink control information, is transmitted on the Physical Uplink Shared Channel (PUSCH).

[0177] In some implementations, at least two of the plurality of uplink data transmissions overlap with the opportunity to transmit the UCI, wherein the last of the at least two uplink data transmissions is selected.

[0178] In some implementations, the at least one downlink allocation indicator includes X downlink allocation indicators; selecting the first uplink data transmission includes selecting a subset of the plurality of uplink data transmissions, the subset including X corresponding uplink data transmissions; and the X corresponding uplink data transmissions are multiplexed with X corresponding portions of the uplink control information.

[0179] In some implementations, the X corresponding uplink transmissions are first performed in the plurality of uplink data transmissions.

[0180] In some implementations, the X corresponding uplink transmissions are first included in a second subset of the plurality of uplink data transmissions, the second subset overlapping with the opportunity to transmit uplink control information.

[0181] In some implementations, the plurality of uplink data transmissions include M uplink data transmissions; X uplink data transmissions are selected for multiplexing with X corresponding portions of the uplink control information; and the X uplink data transmissions are selected from the range of the (M-1)th uplink data transmission to the (MX-1)th uplink data transmission.

[0182] In a third set of embodiments, an apparatus may include: a processor configured to: establish communication with a user equipment (UE); transmit to the UE an indication to use a first bandwidth portion (BWP); determine for the UE a first schedule of multiple uplink communications over a period of time, wherein the multiple uplink communications include uplink control information (UCI) communications multiplexed with a second uplink communication; transmit to the UE first downlink control information (DCI) indicating the first schedule of the multiple uplink communications; determine a latest time to transmit to the UE a second DCI indicating the use of a second BWP, wherein the latest time of transmission is relative to the time of transmission of a specific uplink communication among the multiple uplink communications; receive the first uplink communication among the multiple uplink communications from the UE; transmit the second DCI to the UE at or before the latest time of transmission; and communicate with the UE using the second BWP.

[0183] In some implementations, the specific uplink communication in the plurality of uplink communications includes the UCI communication multiplexed with the second uplink communication.

[0184] In some implementations, the specific uplink communication among the plurality of uplink communications includes the earliest uplink communication among the plurality of uplink communications.

[0185] In some implementations, the latest time of the transmission is N2 symbols prior to the first symbol of the particular uplink communication in the plurality of uplink communications.

[0186] In some implementations, the processor is further configured to cause the base station to: at a second time: determine that the UE uses the third BWP, wherein the determination of the UE using the third BWP occurs after a second latest time relative to the transmission of the third uplink communication; and based on the second latest time of the transmission, delay transmitting a DCI indicating the use of the third BWP, such that a fourth uplink communication is scheduled to use the third BWP, but the third uplink communication is scheduled to use the second BWP.

[0187] In some implementations, the processor is further configured to avoid transmitting any DCI indicating a change in the BWP after the latest transmission time.

[0188] In some implementations, at least one of the plurality of uplink communications occurs prior to the specific uplink communication among the plurality of uplink communications.

[0189] In various implementation schemes, various combinations of the above implementation schemes can be combined together.

[0190] Another exemplary implementation may include a method comprising: a wireless device performing any or all of the foregoing examples.

[0191] Another exemplary embodiment may include a wireless device comprising: an antenna; a radio component coupled to the antenna; and a processing element operatively coupled to the radio component, wherein the device is configured to implement any or all of the foregoing examples.

[0192] Another exemplary embodiment may include an apparatus comprising a processing element configured to cause a wireless device to implement any or all of the foregoing examples.

[0193] Another set of exemplary embodiments may include a non-transitory computer-accessible memory medium comprising program instructions that, when executed at the device, cause the device to implement any or all of the portions of any of the foregoing examples.

[0194] Another exemplary set of implementations may include a computer program comprising instructions for performing any or all portions of any of the examples described above.

[0195] Another exemplary set of embodiments may include an apparatus that includes means for performing any or all elements of any of the examples described above.

[0196] By interpreting each message / signal X received by the user equipment (UE) in the DL as a message / signal X transmitted by the base station, and interpreting each message / signal Y transmitted by the UE in the UL as a message / signal Y received by the base station, any method described herein for operating the UE can serve as the basis for a corresponding method for operating the base station. Furthermore, methods described relative to the base station can be interpreted as methods used for the UE in a similar manner.

[0197] In addition to the exemplary embodiments described above, further embodiments of this disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0198] In some embodiments, a non-transitory computer-readable storage medium may be configured to store program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system performs a method, such as any method embodiment of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset or combination of any such subset of any method embodiments described herein.

[0199] In some implementations, a device (e.g., UE 106 or 107) may be configured to include a processor (or a set of processors) and a memory medium, wherein the memory medium stores program instructions, and the processor is configured to read from the memory medium and execute the program instructions, wherein the program instructions can be executed to implement any of the various method implementations described herein (or any combination of the method implementations described herein, or any subset or combination of any such subset of any method implementations described herein). The device may be implemented in any of a variety of forms.

[0200] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0201] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. A method for wireless communication, comprising: At the User Equipment (UE) device: Establish communication with the base station; The system receives first downlink control information (DCI) from the base station at the first time to schedule at least one uplink data transmission, wherein the at least one uplink data transmission includes uplink data transmission multiplexed with uplink hybrid automatic repeat request (HARQ) transport multiplexing. A second DCI is received from the base station at a second time to schedule at least one downlink data transmission, wherein the second time is after the first time. A defined time period is specified, during which any corresponding downlink data transmission received in the at least one downlink data transmission will be negatively acknowledged, regardless of whether the corresponding downlink data transmission was successfully received, wherein the time period is determined relative to one of the following: The timing of a specific uplink data transmission in the at least one uplink data transmission; or The first time; During the time period, a specific downlink transmission in the at least one downlink data transmission is received from the base station; A negative acknowledgment is generated for the specific downlink transmission in the at least one downlink data transmission received during the time period. as well as The uplink data transmission, multiplexed with the uplink HARQ transmission, is transmitted to the base station. The uplink HARQ transmission includes the negative acknowledgment for the specific downlink transmission in the at least one downlink data transmission.

2. The method according to claim 1, wherein: The time period is relative to the time of the specific uplink data transmission; and The specific uplink data transmission in the at least one uplink data transmission is the uplink data transmission multiplexed with the uplink HARQ transmission.

3. The method according to claim 1, wherein: The time period is relative to the time of the specific uplink data transmission; and The specific uplink data transmission in the at least one uplink data transmission is the earliest uplink data transmission in the at least one uplink data transmission.

4. The method according to claim 1, wherein: The time period is relative to the first time; and The time period begins at the first time.

5. The method according to claim 4, wherein: The time period ends when the uplink data transmission, which is multiplexed with the uplink HARQ transport, is being transmitted.

6. The method according to claim 1, wherein: The time period is relative to the time of the specific uplink data transmission; and The time period includes multiple symbols prior to the commencement of transmission of the specific uplink data.

7. A method for wireless communication, comprising: At the user equipment (UE) level: Establish communication with the base station; Receive one or more downlink control information (DCI) messages from the base station, wherein the one or more DCI messages are: Schedule multiple uplink data transmissions; Schedule at least one downlink data transmission; as well as Includes at least one downlink allocation indicator associated with the at least one downlink data transmission; Determine whether the first downlink data transmission in the at least one downlink data transmission has been received; Generate uplink control information, the uplink control information including a first part indicating whether the first downlink data transmission in the at least one downlink data transmission is received; The first uplink data transmission among the plurality of uplink data transmissions is selected, at least in part, based on the at least one downlink allocation indicator, for multiplexing with at least the first portion of the uplink control information; as well as The plurality of uplink data transmissions are transmitted to the base station, wherein the first uplink data transmission is multiplexed with at least a first portion of the uplink control information.

8. The method of claim 7, wherein the one or more DCI messages include a first DCI message and a second DCI message, the first DCI message scheduling the at least one downlink data transmission, and the second DCI message scheduling the plurality of uplink data transmissions and including the at least one downlink allocation indicator.

9. The method of claim 7, wherein when the Physical Uplink Shared Channel (PUSCH) overlaps with the Physical Uplink Control Channel (PUCCH), the first uplink data transmission multiplexed with the at least first portion of the uplink control information is transmitted on the PUSCH.

10. The method of claim 7, wherein at least two of the plurality of uplink data transmissions overlap with the opportunity to transmit the uplink control information, wherein the last uplink data transmission of the at least two uplink data transmissions is selected.

11. The method according to claim 7, wherein: The at least one downlink allocation indicator includes X downlink allocation indicators; Selecting the first uplink data transmission includes selecting a subset of the plurality of uplink data transmissions, the subset comprising X corresponding uplink data transmissions; and The X corresponding uplink data transmissions are multiplexed with the X corresponding portions of the uplink control information.

12. The method according to claim 7, wherein: The multiple uplink data transmissions include M uplink data transmissions; Select X uplink data transmissions for multiplexing with X corresponding portions of the uplink control information; and The X uplink data transmissions are selected from the range of the (M-1)th uplink data transmission to the (MX-1)th uplink data transmission.

13. An apparatus including a processor configured to cause a user equipment (UE) to perform the method according to any one of claims 1 to 12.

14. The apparatus of claim 13, further comprising a radio component operatively coupled to the processor.

15. A method for wireless communication, comprising: At the base station, Establish communication with the user equipment (UE); Transmit an instruction to the UE to use the first bandwidth portion (BWP); For the UE, a first scheduling of multiple uplink communications within a certain time period is determined, wherein the multiple uplink communications include uplink control information (UCI) communications multiplexed with a second uplink communication; Transmit first downlink control information (DCI) of the first schedule, which indicates the plurality of uplink communications, to the UE; The latest time of transmitting a second DCI indicating the use of a second BWP to the UE is determined, wherein the latest time of transmission is determined relative to the time of transmission of a specific uplink communication among the plurality of uplink communications; Receive the specific uplink communication from the plurality of uplink communications from the UE; The second DCI is transmitted to the UE at or before the latest time of the transmission; as well as The second BWP is used to communicate with the UE.

16. The method of claim 15, wherein the specific uplink communication in the plurality of uplink communications includes the UCI communication multiplexed with the second uplink communication.

17. The method of claim 15, wherein the specific uplink communication in the plurality of uplink communications includes the earliest uplink communication in the plurality of uplink communications.

18. The method of claim 15, wherein the latest time of the transmission is N2 symbols preceding the first symbol of the particular uplink communication in the plurality of uplink communications.

19. The method of claim 15, further comprising: Second time: A determination is made regarding the UE using the third BWP, wherein the determination regarding the UE using the third BWP occurs after a second latest time relative to the transmission of the third uplink communication; as well as The transmission delay indication based on the second latest time of the transmission uses the DCI of the third BWP, such that the fourth uplink communication is scheduled to use the third BWP, but the third uplink communication is scheduled to use the second BWP.

20. A computer program product comprising program instructions configured to cause a device to perform the method according to any one of claims 1 to 12 or 15 to 19.

Images