Scheduling for multiple PDSCH / PUSCH operations

Abstract

Apparatus, systems, and methods for determining and scheduling multiple PDSCH / PUSCH operations in wireless communications (e.g., 5G NR systems and beyond), including methods for separate HARQ-ACK subcodebook operation, for collision handling between PDSCH / PUSCH with TDD configuration, and for multi-PXSCH scheduling signaling.

Description

Technical Field

[0001] The present invention relates to wireless communications, and more particularly to apparatuses, systems, and methods for determining and scheduling multiple PDSCH / PUSCH operations in wireless communications (e.g., 5G NR systems and beyond). Background Art

[0002] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smartphones and tablets have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices now also provide access to the Internet, email, text messaging, and navigation using the Global Positioning System (GPS), and are capable of operating sophisticated applications that utilize these capabilities.

[0003] Long Term Evolution (LTE) is currently the technology of choice for most wireless network operators worldwide, enabling them to provide mobile broadband data and high-speed internet access to their subscriber base. LTE was first proposed in 2004 and standardized in 2008. Since then, as the use of wireless communication systems has grown exponentially, the demand on wireless network operators has risen to support higher capacity for the increasing density of mobile broadband users. Consequently, research on new radio access technologies began in 2015, and the first version of Fifth Generation New Radio (5G NR) was standardized in 2017.

[0004] Compared to LTE, 5G-NR (also referred to as NR) offers higher capacity for a higher density of mobile broadband users, while also supporting ultra-reliable and massive machine-type device-to-device communications, lower latency, and / or lower battery consumption. Furthermore, NR allows for more flexible UE scheduling than current LTE. Consequently, efforts are underway to leverage the higher throughput possible at higher frequencies in the ongoing development of 5G-NR. Summary of the Invention

[0005] The embodiments relate to wireless communications, and more particularly to apparatus, systems, and methods for determining and scheduling multiple PDSCH / PUSCH operations in wireless communications (e.g., 5G NR systems and beyond).

[0006] For example, embodiments include methods for separate HARQ-ACK subcodebook operation, for collision handling between PDSCH / PUSCH with TDD configuration, and for multi-PXSCH scheduling signaling.

[0007] As an example, the UE may receive an indication of a threshold from a serving cell, such as a maximum number of physical downlink shared channels (PDSCHs) in a multi-PDSCH schedule that may be scheduled by a downlink control indicator (DCI). The indication may be received via a system information block (SIB) 1 message via a medium access control (MAC) control element (CE), for example, by selecting a threshold from a set of thresholds configured via radio resource control (RRC) signaling. In addition, the indication may be received via DCI or via group-specific DCI. In addition, the UE may divide the configured CCs into a first group and a second group based on the threshold and the maximum number of addressable PDSCHs for each component carrier (CC) according to the DCI. In addition, the UE may determine a first hybrid automatic repeat request (HARQ) acknowledgement (ACK) subcodebook and a second HARQ-ACK subcodebook based on one or more criteria, such as at least in part based on dividing the configured CCs into the first group and the second group.

[0008] As another example, the UE may add HARQ-ACK bits for the physical downlink shared channel (PDSCH) scheduled by fallback DCI format 1_0 to the first HARQ-ACK subcodebook. In addition, the UE may add HARQ-ACK bits for the PDSCH scheduled by the non-fallback DCI with an extended counter downlink allocation index (C-DAI) field and an extended total DAI (T-DAI) field to the second HARQ-ACK subcodebook. The size of the extended C-DAI field may be greater than two bits. In addition, the size of the extended T-DAI field may be greater than two bits.

[0009] As another example, the UE may receive DCI scheduling multiple PDSCHs / PUSCHs from a serving cell and determine a gap between consecutively scheduled PDSCHs / PUSCHs based on at least one K0 / K2 value. The at least one K0 / K2 value may be a K0 / K2 value for a first PDSCH / PUSCH, and determining the gap between consecutively scheduled PDSCHs / PUSCHs may be further based on an additional gap offset value between PDSCHs / PUSCHs per start and length indicator value. In some embodiments, the at least one K0 / K2 value may include a K0 / K2 value for each PDSCH / PUSCH per start and length indicator value.

[0010] As another example, the UE may, for example, index a valid physical uplink control channel (PUSCH) transmission opportunity within multiple PUSCHs scheduled by a single DCI, and determine the starting resource block (RB) of the PUSCH transmission opportunity based on the index of the PUSCH within the multiple PUSCHs scheduled by the single DCI and the starting PRB provided by the single DCI and the RB offset between two hop frequencies.

[0011] The techniques described herein may be implemented in and / or used with a number of different types of devices, including, but not limited to, any of unmanned aerial vehicles (UAVs), unmanned aerial controllers (UACs), UTM servers, base stations, access points, cellular telephones, tablet computers, wearable computing devices, portable media players, and various other computing devices.

[0012] This summary is intended to provide a brief overview of some of the subject matter described in this document. Therefore, it should be understood that the above-described features are merely examples and should not be construed as narrowing the scope or spirit of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following detailed description, accompanying drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] A better understanding of the present subject matter may be obtained when the following detailed description of various embodiments is considered in conjunction with the following drawings, in which:

[0014] Figure 1A An exemplary wireless communication system is shown in accordance with some embodiments.

[0015] Figure 1B Examples of base stations and access points communicating with user equipment (UE) devices are shown in accordance with some embodiments.

[0016] Figure 2 An exemplary block diagram of a base station according to some embodiments is shown.

[0017] Figure 3 An exemplary block diagram of a server according to some embodiments is shown.

[0018] Figure 4 An exemplary block diagram of a UE according to some embodiments is shown.

[0019] Figure 5 An example block diagram of cellular communication circuitry is shown in accordance with some embodiments.

[0020] Figure 6A An example of a 5G network architecture according to some embodiments is shown, which combines 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the 5G CN.

[0021] Figure 6B An example of a 5G network architecture in accordance with some embodiments is shown, which combines dual 3GPP (e.g., LTE and 5G NR) access to the 5G CN as well as non-3GPP access.

[0022] Figure 7 An example of a baseband processor architecture for a UE according to some embodiments is shown.

[0023] Figure 8 Examples of C-DAI and T-DAI settings for separate codebooks are shown according to some embodiments.

[0024] Figure 9 An example of a table for determining the maximum number of addressable PDSCHs for a single DCI for a given CC index for different CCs is shown according to some embodiments.

[0025] Figure 10A and Figure 10B An example of collision handling between PDSCH and PUSCH with a TDD configuration according to some embodiments is shown.

[0026] Figure 11A An example of multiple PDSCH scheduling according to some embodiments is shown.

[0027] Figure 11B An example of a table specifying K0 values ​​and offset values ​​based on PDSCH index according to some embodiments is shown.

[0028] Figure 12 An example of a block diagram of a method for scheduling for multiple PDSCH / PUSCH operations according to some embodiments is shown.

[0029] Figure 13 An example of a block diagram of a method for determining a first HARQ-ACK subcodebook and a second HARQ-ACK subcodebook in multi-PUSCH scheduling according to some embodiments is shown.

[0030] Figure 14 An example of a block diagram of a method for determining a first HARQ-ACK subcodebook and a second HARQ-ACK subcodebook in multi-PUSCH scheduling according to some embodiments is shown.

[0031] Figure 15 An example of a block diagram of a method for determining inter-slot frequency hopping for multiple PUSCH transmissions according to some embodiments is shown.

[0032] While the features described herein are susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and described in detail herein. It should be understood, however, that the drawings and detailed description thereof are not intended to limit this disclosure to the particular forms disclosed, but on the contrary, are intended to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims. DETAILED DESCRIPTION

[0033] Acronyms

[0034] Various acronyms are used throughout this disclosure. The definitions of the most prominent acronyms used that may appear throughout this disclosure are as follows:

[0035] 3GPP: Third Generation Partnership Project

[0036] UE: User Equipment

[0037] RF: Radio Frequency

[0038] BS: Base Station

[0039] DL: Downlink

[0040] UL: Uplink

[0041] LTE: Long Term Evolution

[0042] NR: New Radio

[0043] CBRS: Citizens Broadband Radio Service

[0044] DAS: Distributed Antenna System

[0045] 5GS: 5G system

[0046] 5GMM: 5GS Mobility Management

[0047] 5GC / 5GCN: 5G core network

[0048] SIM: Subscriber Identity Module

[0049] eSIM: Embedded Subscriber Identity Module

[0050] IE: Information Element

[0051] CE: Control Element

[0052] MAC: Media Access Control

[0053] SSB: Synchronous Signal Block

[0054] CSI-RS: Channel State Information Reference Signal

[0055] PDCCH: Physical Downlink Control Channel

[0056] PDSCH: Physical Downlink Shared Channel

[0057] RRC: Radio Resource Control

[0058] RRM: Radio Resource Management

[0059] CORESET: Control resource set

[0060] TCI: Transmission Configuration Indicator

[0061] DCI: Downlink Control Indicator

[0062] the term

[0063] The following is a glossary of terms used in this disclosure:

[0064] Memory medium—any of various types of non-transitory memory devices or storage devices. The term "memory medium" is intended to include installation media, such as CD-ROMs, floppy disks, or 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, for example, hard drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of non-transitory memory or combinations thereof. In addition, the memory medium may be located in the first computer system executing the program, or may be located 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 medium" may include two or more memory media that may reside in different locations in different computer systems connected, for example, via a network. The memory medium may store program instructions (e.g., expressed as a computer program) that may be executed by one or more processors.

[0065] Carrier Medium—storage media as described above, and physical transmission media such as a bus, network, and / or other physical transmission media that transport signals such as electrical, electromagnetic, or digital signals.

[0066] Programmable hardware elements—include various hardware devices that include multiple programmable function 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 function blocks can range from fine-grained (combinational 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."

[0067] Computer system (or computer)—any of various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, network appliances, Internet appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations of devices. 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.

[0068] User Equipment (UE) (or "UE device") - any of various types of computer system devices that are mobile or portable and perform wireless communication. Examples of UE devices include mobile phones or smartphones (e.g., iPhones). TM , based on Android TM phones), portable gaming devices (e.g., Nintendo DS TM PlayStation Portable TM 、Gameboy Advance TM , iPhone TM ), laptops, wearable devices (e.g., smart watches, smart glasses), PDAs, portable internet devices, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. In general, the term "UE" or "UE device" may be broadly defined to encompass any electronic, computing, and / or telecommunication device (or combination of devices) that is easily transportable by a user and capable of wireless communication.

[0069] Base Station—The term “base station” has the full breadth of its ordinary meaning and includes at least a wireless communication station that is installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.

[0070] Processing element (or processor)—refers to any element or combination of elements capable of performing functions in a device such as user equipment or a cellular network device. A processing element may include, for example, a processor and associated memory, portions or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as ASICs (application-specific integrated circuits), programmable hardware elements such as field-programmable gate arrays (FPGAs), and any combination thereof.

[0071] Channel - the medium used to transmit information from a sender (transmitter) to a receiver. It should be noted that since the characteristics of the term "channel" may vary according to different wireless protocols, the term "channel" as used in the present invention may be considered to be used in a manner that is consistent with the standard of the type of device to which the term is used. In some standards, the channel width may be variable (e.g., depending on device capabilities, frequency band conditions, etc.). For example, LTE may support scalable channel bandwidths of 1.4 MHz to 20 MHz. In contrast, a WLAN channel may be 22 MHz wide, while a Bluetooth channel may be 1 MHz wide. Other protocols and standards may include different definitions of channels. In addition, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0072] Frequency band—The term “frequency band” has the full breadth of its ordinary meaning and includes at least a segment of the spectrum (eg, radio frequency spectrum) in which channels are used or set aside for the same purpose.

[0073] Wi-Fi—The term "Wi-Fi" (or WiFi) has the full scope of its ordinary meaning and includes at least wireless communication networks, or RATs, that are served by wireless LAN (WLAN) access points and provide connectivity to the Internet through those access points. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name "Wi-Fi." Wi-Fi (WLAN) networks are distinct from cellular networks.

[0074] 3GPP access—refers to access (e.g., radio access technology) specified by the 3GPP standards. These accesses include, but are not limited to, GSM / GPRS, LTE, LTE-A, and / or 5G NR. Generally speaking, 3GPP access refers to various types of cellular access technologies.

[0075] Non-3GPP access - refers to any access (e.g., radio access technology) not specified by the 3GPP standards. These accesses include, but are not limited to, WiMAX, CDMA2000, Wi-Fi, WLAN, and / or fixed networks. Non-3GPP accesses can be divided into two categories, "trusted" and "untrusted": Trusted non-3GPP accesses can interact directly with the Evolved Packet Core (EPC) and / or 5G Core (5GC), while untrusted non-3GPP interworks with the EPC / 5GC via network entities (such as Evolved Packet Data Gateways and / or 5G NR Gateways). Generally speaking, non-3GPP access refers to various types of non-cellular access technologies.

[0076] Automatic—refers to an action or operation being performed by a computer system (e.g., software executed by the computer system) or a device (e.g., a circuit, a programmable hardware element, an ASIC, etc.) without requiring user input to directly specify or execute the action or operation. Thus, the term "automatically" is in contrast to an action being manually performed or specified by a user, where the user provides input to directly perform the action. An automatic process may be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user, i.e., they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing information, selecting checkboxes, radio selections, etc.) is not 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, where the computer system (e.g., software executing on the computer system) analyzes the fields of the form and fills it out without requiring any user input to specify the answers to the fields. As indicated above, a user can invoke the automatic filling of a form without participating in the actual filling out of the form (e.g., the user does not manually specify the answers to the fields; they are automatically completed). This specification provides various examples of operations that are automatically performed in response to actions that a user has taken.

[0077] About—refers to a value that is close to being correct or exact. For example, about can refer to a value that is within 1% to 10% of the exact (or desired) value. However, it should be noted that the actual threshold value (or tolerance) may depend on the application. For example, in some embodiments, "about" may mean within 0.1% of some specified or desired value, while in various other embodiments, the threshold value may be, for example, 2%, 3%, 5%, etc., depending on the desires or requirements of a particular application.

[0078] Concurrency—refers to parallel execution or implementation, where tasks, processes, or programs are executed in an at least partially overlapping manner. For example, concurrency can be achieved using "strong" or strict parallelism, where tasks are executed (at least partially) in parallel on respective computing elements, or using "weak parallelism," where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0079] Various components may be described as being "configured to" perform one or more tasks. In such contexts, "configured to" is a broad statement that generally means "having a structure" to perform one or more tasks during operation. Thus, a component can be configured to perform a task even when the component is not currently performing the task (e.g., a set of electrical conductors can be configured to electrically connect a module to another module even when the two modules are not connected). In some contexts, "configured to" can be a broad statement that generally means "having a structure" to carry out one or more tasks during operation. Thus, a component can be configured to perform a task even when the component is not currently turned on. Typically, the circuitry that forms the structure corresponding to "configured to" may include hardware circuitry.

[0080] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to." Representing a component as being configured to perform one or more tasks expressly intends that the component not be interpreted under 35 U.S.C. §112(f).

[0081] Figure 1A and Figure 1B :Communication System

[0082] Figure 1A 1 shows a simplified exemplary wireless communication system according to some embodiments. Note that Figure 1A The system is merely one example of a possible system, and features of the present disclosure may be implemented in any of a variety of systems, as desired.

[0083] As shown, the exemplary wireless communication system includes a base station 102A that communicates with one or more user devices 106A, 106B, 106N, etc. via a transmission medium. Each user device may be referred to herein as a "user equipment" (UE). Therefore, user device 106 is referred to as a UE or UE device.

[0084] Base station (BS) 102A may be a base transceiver station (BTS) or a cell site ("cellular base station") and may include hardware that enables wireless communications with UEs 106A through 106N.

[0085] The communication area (or coverage area) of a base station may be referred to as a "cell." The base station 102A and the UE 106 may be configured to communicate over a transmission medium using any of a variety of radio access technologies (RATs), also known as wireless communication technologies or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-Advanced (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), and the like. Note that if the base station 102A is implemented in the context of LTE, it may alternatively be referred to as an "eNodeB" or "eNB." Note that if the base station 102A is implemented in the context of 5G NR, it may alternatively be referred to as a "gNodeB" or "gNB."

[0086] As shown, base station 102A may also be configured to communicate with network 100 (e.g., a cellular service provider's core network, a telecommunications network such as the Public Switched Telephone Network (PSTN), and / or the Internet, among other possibilities). Thus, base station 102A may facilitate communications between user devices and / or between user devices and network 100. In particular, cellular base station 102A may provide UE 106 with various communication capabilities, such as voice, SMS, and / or data services.

[0087] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore be provided as a network of cells that can provide continuous or nearly continuous overlapping service to UEs 106A-N and similar devices over a geographic area via one or more cellular communication standards.

[0088] Thus, while base station 102A may serve as a "serving cell" for UEs 106A-N as shown in FIG1 , each UE 106 may also be able to receive signals from (and potentially be within communication range of) one or more other cells (which may be provided by base stations 102B-N and / or any other base stations), which may be referred to as "neighboring cells." Such cells may also be able to facilitate communications between user devices and / or between user devices and network 100. Such cells may include "macro" cells, "micro" cells, "pico" cells, and / or cells of any other variety of granularity in terms of service area size. For example, base stations 102A-102B shown in FIG1 may be macro cells, while base station 102N may be a micro cell. Other configurations are also possible.

[0089] In some embodiments, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or "gNB." In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, a gNB cell may include one or more transition and reception points (TRPs). Furthermore, a UE capable of operating in accordance with 5G NR may connect to one or more TRPs within one or more gNBs.

[0090] It is noted that the UE 106 is capable of communicating using multiple wireless communication standards. For example, in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.), the UE 106 can be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.). If desired, the UE 106 can also or alternatively be configured to communicate using one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcast standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocols. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0091] Figure 1B A user equipment 106 (e.g., one of devices 106A through 106N) is shown in accordance with some embodiments in communication with a base station 102 and an access point 112. The UE 106 may be a device having cellular and non-cellular communication capabilities (e.g., Bluetooth, Wi-Fi, etc.), such as a mobile phone, handheld device, computer or tablet, or virtually any type of wireless device.

[0092] The UE 106 may include a processor configured to execute program instructions stored in a memory. The UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively or in addition, the UE 106 may include a programmable hardware element, such as a field programmable gate array (FPGA) configured to perform any of the method embodiments described herein or any portion of any of the method embodiments described herein.

[0093] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD), LTE / LTE-Advanced, or 5G NR using a single shared radio and / or GSM, LTE, LTE-Advanced, or 5G NR using a single shared radio. The shared radio may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communications. Typically, the radio may include any combination of a 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 may implement one or more receive and transmit chains using the aforementioned hardware. For example, UE 106 may share one or more portions of a receive and / or transmit chain between multiple wireless communication technologies such as those discussed above.

[0094] In some embodiments, the UE 106 may include a separate transmit chain and / or receive chain (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As another possibility, the UE 106 may include one or more radio components shared between multiple wireless communication protocols, and one or more radio components used exclusively by a single wireless communication protocol. For example, the UE 106 may include a shared radio component for communicating using either LTE or 5GNR (or LTE or 1xRTT, or LTE or GSM), and a separate radio component for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0095] Figure 2 :Block diagram of base station

[0096] Figure 2 An exemplary block diagram of a base station 102 according to some embodiments is shown. Note that Figure 3 The base station 102 is merely one example of a possible base station. As shown, the base station 102 may include a processor 204 that may execute program instructions for the base station 102. The processor 204 may also be coupled to a memory management unit (MMU) 240 or other circuit or device that may be configured to receive addresses from the processor 204 and translate those addresses into locations in memory (e.g., memory 260 and read-only memory (ROM) 250).

[0097] The base station 102 may include at least one network port 270. The network port 270 may be configured to couple to a telephone network and provide access to the network as described above in FIG. Figure 2 Multiple devices (such as UE device 106) of the telephone network described in.

[0098] The network port 270 (or an additional network port) may also or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to a plurality of devices, such as the UE device 106. In some cases, the network port 270 may couple to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by the cellular service provider).

[0099] In some embodiments, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or "gNB." In such embodiments, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and reception points (TRPs). Furthermore, a UE capable of operating in accordance with 5G NR may connect to one or more TRPs within one or more gNBs.

[0100] Base station 102 may include at least one antenna 234 and possibly multiple antennas. The at least one antenna 234 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE device 106 via radio 230. Antenna 234 communicates with radio 230 via communication chain 232. Communication chain 232 may be a receive chain, a transmit chain, or both. Radio 230 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, and the like.

[0101] The base station 102 may be configured to perform wireless communications using multiple wireless communication standards. In some cases, the base station 102 may include multiple radios that enable the base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station 102 may include an LTE radio component for performing communications according to LTE and a 5G NR radio component for performing communications according to 5G NR. In this case, the base station 102 may be capable of operating as both an LTE base station and a 5G NR base station. As another possibility, the base station 102 may include a multimode radio component capable of performing communications according to any one of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0102] As further described later herein, BS 102 may include hardware and software components for implementing or supporting specific implementations of the features described herein. The processor 204 of the base station 102 may be configured to implement or support implementation of part 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, the processor 204 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit), or a combination thereof. Alternatively (or in addition), in combination with one or more of the other components 230, 232, 234, 240, 250, 260, 270, the processor 204 of the base station 102 may be configured to implement or support implementation of part or all of the features described herein.

[0103] Furthermore, as described herein, processor 204 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor 204. Thus, processor 204 may include one or more integrated circuits (ICs) configured to perform the functions of processor 204. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform one or more functions of processor 204.

[0104] Additionally, as described herein, radio 230 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio 230. Thus, radio 230 may include one or more integrated circuits (ICs) configured to perform the functions of radio 230. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio 230.

[0105] Figure 3 :Block diagram of the server

[0106] Figure 3 An exemplary block diagram of a server 104 according to some embodiments is shown. Note that Figure 3 The server 104 is just one example of a possible server. As shown, the server 104 may include a processor 344 that can execute program instructions for the server 104. The processor 344 may also be coupled to a memory management unit (MMU) 374, which may be configured to receive addresses from the processor 344 and translate those addresses to locations in memory (e.g., memory 364 and read-only memory (ROM) 354) or to other circuits or devices.

[0107] Server 104 may be configured to provide access network functionality to a plurality of devices, such as base station 102, UE device 106, and / or UTM 108, eg, as further described herein.

[0108] In some embodiments, server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) access network. In some embodiments, server 104 may be connected to a legacy Evolved Packet Core (EPC) network and / or to a NR Core (NRC) network.

[0109] As further described later herein, the server 104 may include hardware and software components for implementing or supporting the features described herein. The processor 344 of the server 104 may be configured to implement or support implementing part or all of the methods described herein, for example, by executing program instructions stored on a storage medium (e.g., a non-transitory computer-readable storage medium). Alternatively, the processor 344 may be configured as a programmable hardware element such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit) or a combination thereof. Alternatively (or in addition), in combination with one or more of the other components 354, 364, and / or 374, the processor 344 of the server 104 may be configured to implement or support implementing part or all of the features described herein.

[0110] Furthermore, as described herein, processor 344 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor 344. Thus, processor 344 may include one or more integrated circuits (ICs) configured to perform the functions of processor 344. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 344.

[0111] Figure 4 : UE block diagram

[0112] Figure 41 shows an exemplary simplified block diagram of a communication device 106 according to some embodiments. Figure 4 The block diagram of the communication device is only an example of a possible communication device. According to the embodiment, the communication device 106 can be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, a notebook or a portable computing device), a tablet computer, an unmanned aerial vehicle (UAV), a UAV controller (UAC) and / or a combination of devices and other devices. As shown, the communication device 106 may include a group of components 400 configured to perform core functions. For example, the group of components can be implemented as a system on a chip (SOC), which may include parts for various purposes. Alternatively, the group of components 400 can be implemented as a separate component or group of components for various purposes. This group of components 400 can be (e.g., communicatively; directly or indirectly) coupled to various other circuits of the communication device 106.

[0113] For example, the communication device 106 may include various types of memory (e.g., including NAND flash memory 410), input / output interfaces such as a connector I / F 420 (e.g., for connecting to a computer system; a docking station; a charging station; input devices such as a microphone, a camera, a keyboard; output devices such as a speaker; etc.), a display 460 that may be integrated with the communication device 106 or external to the communication device, and cellular communication circuitry 430 such as for 5G NR, LTE, GSM, etc., and short-range to medium-range wireless communication circuitry 429 (e.g., Bluetooth TM and WLAN circuitry). In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0114] Cellular communication circuitry 430 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 435 and 436, as shown. Short-range to medium-range wireless communication circuitry 429 may also be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 437 and 438, as shown. Alternatively, short-range to medium-range wireless communication circuitry 429 may be (e.g., communicatively; directly or indirectly) coupled to antennas 435 and 436, in addition to or in lieu of being (e.g., communicatively; directly or indirectly) coupled to antennas 437 and 438. Short-range to medium-range wireless communication circuitry 429 and / or cellular communication circuitry 430 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input, multiple-output (MIMO) configuration.

[0115] In some embodiments, as further described below, the cellular communication circuitry 430 can include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). Furthermore, in some embodiments, the cellular communication circuitry 430 can include a single transmit chain that can switch between radios dedicated to specific RATs. For example, a first radio can be dedicated to a first RAT, such as LTE, and can communicate with a dedicated receive chain and a transmit chain shared with an additional radio, such as a second radio that can be dedicated to a second RAT (e.g., 5G NR) and can communicate with both the dedicated receive chain and the shared transmit chain.

[0116] The communication device 106 may also include and / or be configured for use with one or more user interface elements. User interface elements may include various elements such as a display 460 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of the touch screen display), a mouse, a microphone and / or speakers, one or more cameras, one or more buttons, and / or any of a variety of other elements capable of providing information to a user and / or receiving or interpreting user input.

[0117] The communication device 106 may also include one or more smart cards 445 with SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (one or more Universal Integrated Circuit Cards) 445. It should be noted that the term "SIM" or "SIM entity" is intended to include any of various types of SIM implementations or SIM functionality, such as one or more UICC cards 445, one or more eUICCs, one or more eSIMs, removable or embedded, etc. In some embodiments, the UE 106 may include at least two SIMs. Each SIM may execute one or more SIM applications and / or otherwise implement SIM functionality. Thus, each SIM may be a single smart card that may be embedded, for example, soldered to a circuit board in the UE 106, or each SIM 410 may be implemented as a removable smart card. Thus, the SIM may be one or more removable smart cards (such as UICC cards, sometimes referred to as "SIM cards"), and / or the SIM 410 may be one or more embedded cards (such as embedded UICCs (eUICCs), sometimes referred to as "eSIMs" or "eSIM cards"). In some embodiments (such as when the SIM includes an eUICC), one or more of the SIMs may implement embedded SIM (eSIM) functionality; in such embodiments, a single SIM in the SIM may execute multiple SIM applications. Each SIM may include components such as a processor and / or memory; instructions for performing SIM / eSIM functionality may be stored in the memory and executed by the processor. In some embodiments, the UE 106 may include a combination of removable smart cards and fixed / non-removable smart cards (such as one or more eUICC cards implementing eSIM functionality), as needed. For example, the UE 106 may include two embedded SIMs, two removable SIMs, or a combination of one embedded SIM and one removable SIM. Various other SIM configurations are also contemplated.

[0118] As described above, in some embodiments, the UE 106 may include two or more SIM cards. Including two or more SIM cards in the UE 106 may allow the UE 106 to support two different phone numbers and may allow the UE 106 to communicate on two or more corresponding networks. For example, a first SIM card may support a first RAT, such as LTE, and a second SIM card 410 may support a second RAT, such as 5G NR. Of course, other implementations and RATs are also possible. In some embodiments, when the UE 106 includes two SIM cards, the UE 106 may support Dual SIM Dual Active (DSDA) functionality. DSDA functionality may allow the UE 106 to connect to two networks simultaneously (using two different RATs), or to maintain two connections simultaneously on the same or different networks supported by two different SIM cards using the same or different RATs. DSDA functionality may also allow the UE 106 to receive voice calls or data traffic simultaneously on any phone number. In some embodiments, voice calls may be packet-switched communications. In other words, voice calls may be received using Voice over LTE (VoLTE) technology and / or Voice over NR (VoNR) technology. In some embodiments, the UE 106 may support Dual SIM Dual Standby (DSDS) functionality. The DSDS functionality may allow either of the two SIM cards in the UE 106 to be on standby for a voice call and / or data connection. In DSDS, while a call / data call is established on one SIM card, the other SIM card is no longer active. In some embodiments, the DSDx functionality (DSDA or DSDS functionality) may be implemented using a single SIM card (e.g., an eUICC) that executes multiple SIM applications for different carriers and / or RATs.

[0119] As shown, the SOC 400 may include a processor 402 that may execute program instructions for the communication device 106 and a display circuit 404 that may perform graphics processing and provide display signals to a display 460. The processor 402 may also be coupled to a memory management unit (MMU) 440 (the MMU may be configured to receive addresses from the processor 402 and translate those addresses into locations in memory (e.g., memory 406, read-only memory (ROM) 450, NAND flash memory 410)) and / or to other circuits or devices (such as the display circuit 404, short-range to medium-range wireless communication circuitry 429, cellular communication circuitry 430, connector I / F 420, and / or display 460). The MMU 440 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 440 may be included as part of the processor 402.

[0120] As described above, the communication device 106 may be configured to communicate using wireless and / or wired communication circuitry. The communication device 106 may be configured to perform methods for revoking and / or modifying user consent in MEC, for example, in 5G NR systems and beyond, as further described herein.

[0121] As described herein, the communication device 106 may include hardware and software components for implementing the above-described features of the communication device 106 to send a scheduling profile for power saving to the network. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 402 of the communication device 106 may be configured to implement some or all of the features described herein. Alternatively (or in addition), the processor 402 may be configured as a programmable hardware element, such as an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 400, 404, 406, 410, 420, 429, 430, 440, 445, 450, 460, the processor 402 of the communication device 106 may be configured to implement some or all of the features described herein.

[0122] Furthermore, as described herein, processor 402 may include one or more processing elements. Thus, processor 402 may include one or more integrated circuits (ICs) configured to perform the functions of processor 402. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 402.

[0123] Further, as described herein, cellular communication circuitry 430 and short-range to medium-range wireless communication circuitry 429 may each include one or more processing elements. In other words, one or more processing elements may be included in cellular communication circuitry 430, and similarly, one or more processing elements may be included in short-range to medium-range wireless communication circuitry 429. Thus, cellular communication circuitry 430 may include one or more integrated circuits (ICs) configured to perform the functions of cellular communication circuitry 430. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of cellular communication circuitry 430. Similarly, short-range to medium-range wireless communication circuitry 429 may include one or more ICs configured to perform the functions of short-range to medium-range wireless communication circuitry 429. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of short-range to medium-range wireless communication circuitry 429.

[0124] Figure 5 :Block diagram of cellular communication circuit

[0125] Figure 5An exemplary simplified block diagram of a cellular communication circuit according to some embodiments is shown. Note that Figure 5 The block diagram of the cellular communication circuitry is only one example of one possible cellular communication circuitry. Depending on the embodiment, the cellular communication circuitry 530 (which may be the cellular communication circuitry 430) may be included in a communication device such as the communication device 106 described above. As described above, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of devices, among other devices.

[0126] Cellular communication circuitry 530 may be (eg, communicatively; directly or indirectly) coupled to one or more antennas, such as ( Figure 4 In some embodiments, the cellular communication circuit 530 may include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). For example, Figure 5 As shown, cellular communication circuitry 530 may include a modem 510 and a modem 520. Modem 510 may be configured for communication according to a first RAT, such as, for example, LTE or LTE-A, and modem 520 may be configured for communication according to a second RAT, such as, for example, 5G NR.

[0127] As shown, the modem 510 may include one or more processors 512 and a memory 516 in communication with the processor 512. The modem 510 may communicate with a radio frequency (RF) front end 530. The RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 530 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534. In some embodiments, the receive circuitry 532 may communicate with a downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0128] Similarly, the modem 520 may include one or more processors 522 and a memory 526 in communication with the processor 522. The modem 520 may communicate with an RF front end 540. The RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 540 may include receive circuitry 542 and transmit circuitry 544. In some embodiments, the receive circuitry 542 may communicate with a DL front end 560, which may include circuitry for receiving radio signals via the antenna 335b.

[0129] In some embodiments, the switch 570 can couple the transmit circuitry 534 to an uplink (UL) front end 572. Furthermore, the switch 570 can couple the transmit circuitry 544 to the UL front end 572. The UL front end 572 can include circuitry for transmitting radio signals via the antenna 336. Thus, when the cellular communication circuitry 530 receives an instruction to transmit according to a first RAT (e.g., via a transmit chain including the transmit circuitry 534 and the UL front end 572), the switch 570 can be switched to a first state that allows the modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain including the transmit circuitry 534 and the UL front end 572). Similarly, when the cellular communication circuitry 530 receives an instruction to transmit according to a second RAT (e.g., via a transmit chain including the transmit circuitry 544 and the UL front end 572), the switch 570 can be switched to a second state that allows the modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain including the transmit circuitry 544 and the UL front end 572).

[0130] In some embodiments, the cellular communication circuit 530 may be configured to perform methods for determining and scheduling multiple PDSCH / PUSCH operations in wireless communications (e.g., 5G NR systems and beyond), as further described herein. For example, the cellular communication circuit 530 may be configured to perform methods for separate HARQ-ACK subcodebook operations, for collision handling between PDSCH / PUSCHs with TDD configurations, and for multi-PXSCH scheduling signaling.

[0131] As described herein, the modem 510 may include hardware and software components for implementing the above-described features or for time-division multiplexing UL data for NSA NR operations and various other technologies described herein. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 512 may be configured to implement part or all of the features described herein. Alternatively (or in addition), the processor 512 may be configured as a programmable hardware element such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 530, 532, 534, 550, 570, 572, 335, and 336, the processor 512 may be configured to implement part or all of the feature parts described herein.

[0132] Furthermore, as described herein, processor 512 may include one or more processing elements. Thus, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0133] As described herein, the modem 520 may include hardware and software components intended to implement the above-described features for transmitting a power-saving scheduling profile to a network, as well as various other techniques described herein. The processor 522 may be configured to implement a portion or all of the features described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 522 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit). Alternatively (or additionally), in combination with one or more of the other components 540, 542, 544, 550, 570, 572, 335, and 336, the processor 522 may be configured to implement a portion or all of the features described herein.

[0134] Furthermore, as described herein, processor 522 may include one or more processing elements. Thus, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0135] Figure 6A 、 Figure 6B and Figure 7 : 5G Core Network Architecture—Interoperability with Wi-Fi

[0136] In some embodiments, the 5G core network (CN) can be accessed via (or through) a cellular connection / interface (e.g., via a 3GPP communication architecture / protocol) and a non-cellular connection / interface (e.g., a non-3GPP access architecture / protocol such as a Wi-Fi connection). Figure 6AAn example of a 5G network architecture according to some embodiments is shown, which combines 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to a 5G CN. As shown, a user equipment device (e.g., such as UE 106) can access the 5G CN through both a radio access network (RAN, such as, for example, gNB 604, which can be base station 102) and an access point (e.g., AP 612). AP 612 can include a connection to the Internet 600 and a connection to a non-3GPP interworking function (N3IWF) 603 network entity. N3IWF can include a connection to the core access and mobility management function (AMF) 605 of the 5G CN. AMF 605 can include an instance of a 5G mobility management (5G MM) function associated with UE 106. In addition, the RAN (e.g., gNB 604) can also have a connection to AMF 605. Thus, the 5G CN can support unified authentication across both connections and allow UE 106 to be registered for access simultaneously via gNB 604 and AP 612. As shown, AMF 605 can include one or more functional entities associated with the 5G CN (e.g., network slice selection function (NSSF) 620, short message service function (SMSF) 622, application function (AF) 624, unified data management (UDM) 626, policy control function (PCF) 628, and / or authentication server function (AUSF) 630). Note that these functional entities can also be supported by the 5G CN's session management function (SMF) 606a and SMF 606b. AMF 605 can be connected to (or in communication with) SMF 606a. In addition, gNB 604 can communicate with (or be connected to) user plane function (UPF) 608a, which can also communicate with SMF 606a. Similarly, N3IWF 603 can communicate with UPF 608b, which can also communicate with SMF 606b. Both UPFs can communicate with data networks (e.g., DNs 610a and 610b) and / or the Internet 600 and Internet Protocol (IP) Multimedia Subsystem / IP Multimedia Core Subsystem (IMS) Core Network 610.

[0137] Figure 6BAn example of a 5G network architecture according to some embodiments is shown, which combines dual 3GPP (e.g., LTE and 5G NR) access to a 5G CN as well as non-3GPP access. As shown, a user equipment device (e.g., such as UE 106) can access the 5G CN via both a radio access network (RAN, such as, for example, gNB 604 or eNB 602, which may be base station 102) and an access point (e.g., AP 612). AP 612 may include a connection to the Internet 600 and to the N3IWF 603 network entity. The N3IWF may include a connection to the 5G CN's AMF 605. The AMF 605 may include an instance of the 5G MM function associated with the UE 106. In addition, the RAN (e.g., gNB 604) may also have a connection to the AMF 605. Thus, the 5G CN may support unified authentication across both connections and allow the UE 106 to be registered for access simultaneously via the gNB 604 and AP 612. In addition, the 5G CN may support dual registration of UEs on both legacy networks (e.g., LTE via eNB 602) and 5G networks (e.g., via gNB 604). As shown, the eNB 602 may have connections to a Mobility Management Entity (MME) 642 and a Serving Gateway (SGW) 644. The MME 642 may have connections to both the SGW 644 and the AMF 605. Furthermore, the SGW 644 may have connections to both the SMF 606a and the UPF 608a. As shown, the AMF 605 may include one or more functional entities associated with the 5G CN (e.g., NSSF 620, SMSF 622, AF 624, UDM 626, PCF 628, and / or AUSF 630). Note that the UDM 626 may also include Home Subscriber Server (HSS) functionality, and the PCF may also include a Policy and Charging Rules Function (PCRF). Note that these functional entities are also supported by the 5G CN's SMF 606a and SMF 606b. The AMF 606 can connect to (or communicate with) the SMF 606a. Furthermore, the gNB 604 can communicate with (or connect to) the UPF 608a, which can also communicate with the SMF 606a. Similarly, the N3IWF 603 can communicate with the UPF 608b, which can also communicate with the SMF 606b. Both UPFs can communicate with data networks (e.g., DNs 610a and 610b) and / or the Internet 600 and the IMS core network 610.

[0138] Note that in various embodiments, one or more of the above network entities may be configured to perform methods for determining and scheduling multiple PDSCH / PUSCH operations in wireless communications (e.g., 5G NR systems and higher), as further described herein. For example, one or more functional entities in the above network entities may be configured to perform methods for separate HARQ-ACK subcodebook operations, for collision handling between PDSCH / PUSCHs with TDD configurations, and for multi-PXSCH scheduling signaling.

[0139] Figure 7 An example of a baseband processor architecture for a UE (eg, such as UE 106 ) is shown in accordance with some embodiments. Figure 7 The baseband processor architecture 700 described in the accompanying drawings may be implemented on one or more radio components (e.g., radio components 429 and / or 430 described above) or modems (e.g., modems 510 and / or 520) as described above. As shown, the non-access stratum (NAS) 710 may include a 5G NAS 720 and a legacy NAS 750. The legacy NAS 750 may include a communication connection with a legacy access stratum (AS) 770. The 5G NAS 720 may include a communication connection with a 5G AS 740, a non-3GPP AS 730, and a Wi-Fi AS 732. The 5G NAS 720 may include functional entities associated with both access strata. Thus, the 5G NAS 720 may include multiple 5G MM entities 726 and 728 and 5G session management (SM) entities 722 and 724. The traditional NAS 750 may include functional entities such as a short message service (SMS) entity 752, an evolved packet system (EPS) session management (ESM) entity 754, a session management (SM) entity 756, an EPS mobility management (EMM) entity 758, and a mobility management (MM) / GPRS mobility management (GMM) entity 760. In addition, the traditional AS 770 may include functional entities such as an LTE AS 772, a UMTS AS 774, and / or a GSM / GPRS AS 776.

[0140] Thus, the baseband processor architecture 700 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access). Note that, as shown, the 5G MM can maintain a separate connection management and registration management state machine for each connection. In addition, a device (e.g., UE 106) can register to a single PLMN (e.g., 5G CN) using both 5G cellular access and non-cellular access. Furthermore, a device can be in a connected state in one access and idle state in another access, or vice versa. Finally, there may be common 5G-MM procedures (e.g., registration, deregistration, identification, authentication, etc.) for both accesses.

[0141] Note that in various embodiments, one or more of the above functional entities of the 5G NAS and / or 5G AS may be configured to perform methods for determining and scheduling multiple PDSCH / PUSCH operations in wireless communications (e.g., 5G NR systems and higher), for example, as further described herein. For example, one or more of the above functional entities may be configured to perform methods for separate HARQ-ACK subcodebook operations, for collision handling between PDSCH / PUSCHs with TDD configurations, and for multi-PXSCH scheduling signaling.

[0142] Determination and scheduling of multiple PDSCH / PUSCH operations

[0143] In the current embodiment, cellular systems, such as 5G NR systems, can be configured to operate at frequencies up to 71 gigahertz (GHz), taking into account both licensed and unlicensed operations. In addition, the cellular system can support a single DCI for multi-PDSCH / multi-PUSCH scheduling and hybrid automatic repeat request (HARQ). For example, in the current 5G NR, multiple HARQ ACK bits corresponding to multiple PDSCHs scheduled by a single DCI can be multiplexed using a dynamic codebook and transmitted in the same PUCCH or PUSCH resource. In addition, in order to handle the codebook size misalignment between the base station and the UE caused by DCI misdetection on the UE side, 5GNR introduces a counter downlink allocation index (C-DAI) and a total downlink allocation index (T-DAI) field in the scheduling DCI. More specifically, each downlink allocation index (DAI) field uses two bits, and the numbering can be wrapped around by a modulo four operation. Therefore, with 2-bit C-DAI and T-DAI, a misaligned HARQ-ACK codebook size occurs only when the UE misses three consecutive DCIs, e.g., assuming a PDCCH miss detection rate of 10 -2 , then the probability is 10 -6 However, for multi-PDSCH scheduling in which multiple PDSCHs are scheduled by a single DCI, there is a problem of how to efficiently and reliably report the corresponding HARQ feedback.

[0144] Various proposals for DAI counting to support HARQ ACK feedback in multiple PDSCH scheduling have been considered. For example, one proposal is C-DAI / T-DAI counted by DCI, as shown in Release 15 and / or Release 16. Another proposal is C-DAI / T-DAI counted by scheduled PDSCH. As another example, a third proposal is C-DAI / T-DAI counted by M scheduled PDSCHs, where M is a configurable parameter. In addition, with respect to C-DAI / T-DAI counted by DCI shown in 3GPP Release 15 and / or Release 16, if this proposal is adopted to generate a type 2 HARQ-ACK codebook corresponding to a DCI that can schedule multiple PDSCHs, at least two sub-codebooks can be generated for a PUCCH cell group, where the first sub-codebook will cover a case where the DCI is configured with a TDRA table containing at least one row with multiple SLIVs and schedules multiple PDSCHs.

[0145] However, there are still several unresolved issues, such as how to determine the first subcodebook and / or how to handle the HARQ process number when, for PDSCH or PUSCH, they collide with symbols having different directions indicated by the tdd-UL-DL-ConfigurationCommon parameter or the tdd-UL-DL-ConfigurationDedicated parameter.

[0146] The embodiments described herein provide systems, methods, and mechanisms for supporting determination and scheduling for multiple PDSCH / PUSCH operations in wireless communications. For example, the embodiments may include systems, methods, and mechanisms for separate HARQ-ACK subcodebook operations, for conflict handling between PDSCH / PUSCH with TDD configuration, and for multi-PXSCH scheduling signaling. Therefore, the embodiments described herein solve the above-mentioned problems by providing a method for a UE to determine a codebook for HARQ-ACK. In addition, the embodiments described herein provide methods for a UE to determine the HARQ process number for a PDSCH or PUSCH when the PDSCH or PUSCH is scheduled for a symbol that conflicts with a symbol having a different direction indicated by the TDD configuration, for example, the PDSCH is scheduled for a TDD uplink symbol and / or the PUSCH is scheduled for a TDD downlink symbol.

[0147] It should be noted that a common disadvantage of some of the above proposals is the overhead of HARQ-ACK bits, since a fixed number of HARQ-ACK bits are generated for multi-PDSCH scheduling regardless of the actual number of scheduled PDSCHs. Therefore, in some embodiments, to avoid such disadvantages, the component carriers (CCs) configured for a given UE can be divided into two groups based on the maximum number of PDSCHs in a multi-PDSCH schedule that can be scheduled by a single DCI. In addition, a threshold value (e.g., N ) can be provided to the UE in one of various ways. PDSCH ). Note that if no threshold is provided, the UE may assume a single HARQ-ACK codebook for multi-PDSCH and single PDSCH reception. In some embodiments, a single value for the threshold may be indicated as part of the SIB1 message and applied to all UEs residing on the cell. This approach may have advantages due to its simplicity and is technically feasible for cells of relatively small size and UEs with similar signal-to-noise ratio (SNR) geometry and communication traffic characteristics. In some embodiments, a set of values ​​may first be configured as candidate thresholds for a given UE. One of these configured values ​​may then be selected for the HARQ-ACK codebook generated by the MAC-CE or DCI format. Note that for DCI-based methods, a field may be added to the existing scheduling DCI format to dynamically indicate the value of the threshold. As another option, group-specific DCI for multiple UEs may be introduced to signal the value of the threshold for each UE. For example, a field index may be provided to the UE via radio resource control (RRC) signaling to determine the position of the field in the group-specific DCI to obtain the value of the threshold. In addition, the maximum number of addressable PDSCHs for a given CC index by a single DCI can be expressed as N MAX,i , for example, based on RRC configuration (e.g., multiple separate time domain resource allocation (TDRA) elements associated with the TDRA field in the scheduling DCI format). The configured CCs may then be based on the maximum number of addressable PDSCHs for a given CC index (e.g., N MAX,i ) and threshold (N PDSCH ) is divided into two groups. For example, when MAX,i Less than or equal to N PDSCH When , the CC with index i may be included in CC group #1, and when MAX,i Greater than N PDSCH, the CC may be included in CC group #2. Once divided into CC groups, a HARQ-ACK subcodebook may be determined for each group. As a first example, HARQ-ACK subcodebook #1 may include HARQ-ACK bits for PDSCHs scheduled on CCs of group #1. As a second example, when the number of PDSCHs actually scheduled is less than a threshold, HARQ-ACK subcodebook #1 may include HARQ-ACK bits for PDSCHs scheduled on CCs of group #2. As a third example, when fallback DCI format 1_0 is used for scheduling, HARQ-ACK subcodebook #1 may include only a single PDSCH, regardless of whether it is transmitted in CC group #1 or group #2. In other words, the HARQ-ACK bits of the PDSCH scheduled by fallback DCI are always included in subcodebook #1. As a fourth example, HARQ-ACK subcodebook #1 may include HARQ-ACK bits for PDCCHs for PDSCH release or secondary cell (SCell) sleep indication for semi-persistent scheduling. Note that the values ​​of the counter DAI (C-DAI) and the total DAI (T-DAI) in the DCI format can be accumulated or counted across all valid {CC, PDCCH monitoring opportunity} pairs, where PDSCH reception or PDCCH belongs to one of the above examples across CCs in not only CC group #1 but also CC group #2. Note that in all other cases, the HARQ-ACK bits for PDSCH not covered by the above examples can be added to HARQ-ACK subcodebook #2. After determining the HARQ-ACK subcodebook, the HARQ-ACK subcodebook connection can be performed. For example, the sequential connection of HARQ-ACK subcodebook #1 and subcodebook #2 can be in a hard-coded order, for example, HARQ-ACK subcodebook #1 can be placed first.

[0148] Figure 8 An example of C-DAI and T-DAI settings for separate codebooks according to some embodiments is shown. As shown, a UE (e.g., UE 106) may be configured with 8 CCs and may count C-DAI and T-DAI per scheduled DCI. Additionally, a threshold may be set to a value of 2, e.g., N PDSCH =2, and can be based on Figure 9 The table shown configures the maximum number of PDSCHs that can be addressed by a single DCI for a given CC index (e.g., NMAX,i). This table is an example of a table for determining the maximum number of PDSCHs that can be addressed by a single DCI for a given CC index for different CCs according to some embodiments. In addition, based on the above CC grouping scheme, CC group #1 may include CC1, CC2, CC3, and CC4, and CC group #2 may include CC5, CC6, CC7, and CC8. Figure 8As shown. As shown in the figure, fallback DCI formats 810 and 850 can be transmitted on CC6 and CC5, respectively. In addition, DCI format 820 transmitted on CC6 can be used for semi-persistent scheduling (SPS) release, and DCI format 840 transmitted on CC8 and DCI format 830 transmitted on CC6 can schedule PDSCH. In addition, the HARQ-ACK bits for PDSCH in CC group #1 and the HARQ-ACK bits of DCI formats 810, 820, 830, 840 and 850 for CCs in CC group #2 can be included in the HARQ-ACK subcodebook #1. It should be noted that the values ​​of C-DAI and T-DAI can be counted not only across CCs in CC group #1 but also across CCs in CC group #2, as long as it belongs to one of the four examples mentioned above. It should be noted that based on Figure 8 , the UE may generate N for the PDSCH scheduled by DCI formats 810, 820, 830, 840, and 850 PDSCH = 2 HARQ-ACK bits, even though the DCI is transmitted on CC of CC group #2. Therefore, the size of the HARQ-ACK bit payload of these DCIs can be reduced from 40 bits to 10 bits compared to a single HARQ-ACK codebook operation. Specifically, the following HARQ-ACK codebook based on 8 CCs is generated: Figure 8 HARQ-ACK subcodebook:

[0149] -HARQ-ACK subcodebook #1: The UE may generate 24 bits for all PDSCHs on CCs in group #1 and PDSCHs scheduled by DCI formats 810, 820, 830, 840, and 850.

[0150] HARQ-ACK subcodebook #2: UE can generate 6*max(N MAX,5 ,N MAX,6 ,N MAX,7 ,N MAX,8 )=48 bits. Then, the two HARQ-ACK subcodebooks can be concatenated by placing HARQ-ACK subcodebook #1 before HARQ-ACK subcodebook #2.

[0151] Note that in 3GPP Release 15 and Release 16, there are only 2 bits of C-DAI in the fallback DCI format 1_0, but no T-DAI. One possible solution for HARQ-ACK feedback for multi-PDSCH scheduling is then to increase the bit width of C-DAI and T-DAI to ensure that missing up to 3 consecutive DCI formats will not result in a misalignment of the HARQ-ACK codebook size between the base station and the UE. However, due to the size alignment with the traditional broadcast DCI, at least for the CSS, the extension of C-DAI is not impossible for the fallback DCI format 1_0. Therefore, according to some embodiments, assuming that the C-DAI and T-DAI field sizes are extended and counted per PDSCH, two HARQ-ACK subcodebooks can be created. For example, HARQ-ACK subcodebook #1 can be used to transmit HARQ-ACK bits for the PDSCH scheduled by fallback DCI 1_0. Similarly, HARQ-ACK subcodebook #2 can be used to transmit HARQ-ACK bits for PDSCH scheduled by non-fallback DCI with an extended C-DAI / T-DAI field for multi-PDSCH scheduling. Note that these two HARQ-ACK subcodebooks can be concatenated. In addition, these two HARQ-ACK subcodebooks can be transmitted on a single PUCCH resource and / or may not be multiplexed and can be transmitted on separate PUCCH resources.

[0152] In some embodiments, two types of PDSCH / PUSCH may be defined for multi-PDSCH / multi-PUSCH scheduling. For example, a first type (e.g., type 1 PDSCH / type 1 PUSCH) may be defined for the PDSCH / PUSCH in multi-PDSCH / multi-PUSCH that is scheduled by a single DCI and conflicts with uplink / downlink symbols indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. As another example, a second type (e.g., type 2 PDSCH / type 2 PUSCH) may be defined for the remaining PDSCH / PUSCH in multi-PDSCH / multi-PUSCH that is not scheduled by a single DCI and conflicts with uplink / downlink symbols indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DLConfigurationDedicated parameters. In addition, for HARQ process numbering and HARQ-ACK bit generation, the HARQ process number may be incremented on the type 2 PDSCH / PUSCH. In other words, type 1 PDSCH / PUSCH may not be counted for HARQ process increment operation. Correspondingly, the UE does not generate HARQ-ACK bits for type 2 PDSCH for both type 1 and type 2 HARQ-ACK codebook determination. For example, Figure 10A As shown, the HARQ process ID may only count for type 2 PDSCH. Therefore, for a time division duplex (TDD) configuration of 3 downlink slots followed by 2 uplink slots and 3 downlink slots (e.g., (D, D, D, U, U, D, D, D), only the type 2 PDSCH corresponding to the downlink slot may increment the HARQ process ID. Alternatively, for HARQ process numbering and HARQ-ACK bit generation, the HARQ process number may be incremented on both type 1 and type 2 PDSCH / PUSCH. In such a case, the UE may generate HARQ-ACK bits for all types of PDSCH. In particular, the UE may set the value of each corresponding HARQ-ACK information bit to NACK for type 1 PDSCH. Note that such a scheme may be advantageous because it may fix the HARQ-ACK payload at least for the type 1 HARQ-ACK codebook and may simplify the UE implementation. For example, as Figure 10BAs shown, HARQ process ID counting can be performed for Type 1 PDSCH and Type 2 PDSCH. Therefore, for a time division duplex (TDD) configuration of 3 downlink slots followed by 2 uplink slots and 3 downlink slots (e.g., (D, D, D, U, U, D, D, D), both Type 1 PDSCH and Type 2 PDSCH can have incrementing HARQ process IDs.

[0153] In some embodiments, various methods may be considered to indicate the gap between two consecutive scheduled PDSCHs / PUSCHs of a single DCI. For example, a single K0 / K2 value for the first PDSCH / PUSCH and an additional gap offset value between PDSCHs / PUSCHs per start and length indicator value (SLIV) may be used to indicate the gap. Note that the offset value may be counted in units of OFDM symbols or time slots. For example, Figure 11A As shown in FIG, an example of multiple PDSCH scheduling in a single time slot with K0=1 is shown. As shown in the figure, according to some embodiments, PDSCH 2 and PDSCH 3 may be located in the same time slot, which may be as shown in FIG. Figure 11B As shown, it is enabled by setting Δ3 to 0. Figure 11B A table specifying K0 and an offset based on the PDSCH index is shown. As another example, separate K0 / K2 values ​​for each PDSCH / PUSCH per SLIV may be used to indicate a gap.

[0154] Note that multiple PDSCH / PUSCH scheduled by a single DCI in a single timeslot may be supported for 120kHz, 480kHz, and 960kHz SCSs or a subset of these (e.g., only for 120kHz SCS and not for 480kHz and 960kHz SCSs to address UE complexity and bookkeeping issues). Additionally, support for multiple PDSCH / PUSCH may depend on UE capability / feature reporting on a per-SCS basis. In some embodiments, this may be further limited to a given deployment scenario, such as a single transmit reception point (s-TRP) or multiple TRPs (m-TRP).

[0155] In some embodiments, to support multiple PUSCH scheduling via a single DCI distributed over non-contiguous time slots, an inter-slot hopping pattern may be determined for multiple PUSCH transmissions. First, the UE may index the valid PUSCH transmission opportunities scheduled by a single DCI by "i" (where i ≥ 0), (e.g., after excluding invalid opportunities with different directions configured by the tdd-UL-DL-ConfigurationCommon parameter or the tdd-UL-DL-ConfigurationDedicated parameter). Then, in the case of inter-slot hopping, the UE indexes the starting RB of the PUSCH transmission opportunity index i, where i is the PUSCH index within the multiple PUSCHs scheduled by the single DCI. The number of PUSCHs within the uplink (UL) bandwidth part (BWP) is determined by RBs. start The starting RB indicated is provided by the DCI format, and RB offset is the frequency offset in RBs between two frequency hops and can be defined as shown in equation [1]:

[0156]

[0157] Figure 12 An example of a block diagram illustrating a method for scheduling multiple PDSCH / PUSCH operations according to some embodiments is shown. Figure 12 The method shown in the figure can also be used together with any one of the systems, methods or devices shown in the figure. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figure, the method can be operated as follows.

[0158] At 1202, a UE (e.g., UE 106) may receive an indication of a threshold from a serving cell, e.g., a maximum number of physical downlink shared channels (PDSCHs) in a multi-PDSCH schedule that may be scheduled by a downlink control indicator (DCI). The indication may be received via a system information block (SIB) 1 message. Alternatively, the indication may be received via a medium access control (MAC) control element (CE), e.g., by selecting a threshold from a set of thresholds configured via radio resource control (RRC) signaling. Additionally, the indication may be received via DCI, e.g., by selecting a threshold from a set of thresholds configured via radio resource control (RRC) signaling. Additionally, the indication may be received via group-specific DCI. In such cases, the UE may receive an index (e.g., a DCI field index) via radio resource control (RRC) signaling to locate the position of the indication within the group-specific DCI.

[0159] At 1204, the UE may divide the configured CCs into a first group and a second group based on a threshold and a maximum number of addressable PDSCHs per component carrier (CC) by the DCI. In some embodiments, dividing the configured CCs into the first group and the second group based on the threshold and the maximum number of addressable PDSCHs per CC by the DCI may include the UE adding each CC having a maximum number of addressable PDSCHs for DCI that is less than or equal to the maximum number of PDSCHs in a multi-PDSCH schedule scheduled by the DCI to the first group, and the UE adding each CC having a maximum number of addressable PDSCHs for DCI that is greater than the maximum number of PDSCHs in a multi-PDSCH schedule scheduled by the DCI to the second group.

[0160] At 1206, the UE may determine a first hybrid automatic repeat request (HARQ) acknowledgement (ACK) subcodebook and a second HARQ-ACK subcodebook based on one or more criteria, such as based at least in part on dividing the configured CCs into the first group and the second group. In some embodiments, determining the first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook based on one or more criteria may include the UE adding to the first HARQ-ACK subcodebook HARQ-ACK bits for PDSCHs scheduled on CCs in the first group, HARQ-ACK bits for a number of PDSCHs less than or equal to a threshold scheduled on CCs in the second group, HARQ-ACK bits for PDSCHs scheduled by fallback DCI regardless of whether the PDSCH is transmitted on CCs in the first group or CCs in the second group, and HARQ-ACK bits for a physical downlink control channel (PDCCH) for semi-persistent scheduling of PDSCH release or secondary cell dormancy indication, and the UE adding to the second HARQ-ACK subcodebook any remaining HARQ-ACK bits that were not added to the first HARQ-ACK subcodebook.

[0161] In some embodiments, the UE may sequentially concatenate the first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook. The concatenation may include placing the first HARQ-ACK subcodebook before the second HARQ-ACK subcodebook.

[0162] In some embodiments, the UE may increment the counter downlink allocation index (C-DAI) and the total DAI (T-DAI) for each valid [CC, physical downlink control channel (PDCCH) monitoring opportunity] where PDSCH is received or PDCCH is included in the first HARQ-ACK subcodebook.

[0163] In some embodiments, the UE may define a first type of physical downlink shared channel / physical uplink shared channel (PDSCH / PUSCH) for multi-PDSCH / multi-PUSCH scheduling and a second type of PDSCH / PUSCH for multi-PDSCH / multi-PUSCH scheduling. In addition, the UE may only receive / transmit the second type of PDSCH / PUSCH. In some embodiments, the UE may increment the hybrid automatic repeat request (HARQ) process number only on the second type of PDSCH / PUSCH. In some embodiments, the UE may increment the hybrid automatic repeat request (HARQ) process number on the first type of PDSCH / PUSCH and the second type of PDSCH / PUSCH, and generate HARQ acknowledgement (ACK) bits for the first type of PDSCH / PUSCH and the second type of PDSCH / PUSCH. Note that the HARQ-ACK bit corresponding to the first type of PDSCH / PUSCH may be set to not ACK (NACK). In some embodiments, the first type of PDSCH may include a PDSCH in multiple PDSCHs scheduled by a downlink control indicator (DCI) that collides with an uplink symbol indicated by a time division duplex (TDD) configuration. The second type of PDSCH may include a PDSCH in multiple PDSCHs scheduled by the DCI that does not collide with an uplink symbol indicated by the TDD configuration. In some embodiments, the first type of PUSCH may include a PUSCH in multiple PUSCHs scheduled by a downlink control indicator (DCI) that collides with an uplink symbol indicated by a time division duplex (TDD) configuration. The second type of PUSCH may include a PUSCH in multiple PUSCHs scheduled by the DCI that does not collide with an uplink symbol indicated by the TDD configuration.

[0164] In some embodiments, the UE may receive a downlink control indicator (DCI) scheduling multiple PDSCHs / PUSCHs from a serving cell and determine a gap between consecutively scheduled PDSCHs / PUSCHs based on at least one K0 / K2 value. The at least one K0 / K2 value may be a K0 / K2 value for a first PDSCH / PUSCH, and determining the gap between consecutively scheduled PDSCHs / PUSCHs may be further based on an additional gap offset value between PDSCHs / PUSCHs per start and length indicator value. In some embodiments, the at least one K0 / K2 value may include a K0 / K2 value for each PDSCH / PUSCH per start and length indicator value.

[0165] In some embodiments, the UE may, for example, index a valid physical uplink control channel (PUSCH) transmission opportunity within multiple PUSCHs scheduled by a single DCI, and determine the starting resource block (RB) of the PUSCH transmission opportunity based on the PUSCH index within the multiple PUSCHs scheduled by the single DCI and the starting PRB provided by the single DCI and the RB offset between the two frequencies.

[0166] Figure 13 An example of a block diagram of a method for determining a first HARQ-ACK subcodebook and a second HARQ-ACK subcodebook in multi-PUSCH scheduling according to some embodiments is shown. Figure 13 The method shown in the figure can also be used together with any one of the systems, methods or devices shown in the figure. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figure, the method can be operated as follows.

[0167] At 1302, a UE (e.g., UE 106) may add HARQ-ACK bits for a physical downlink shared channel (PDSCH) scheduled by fallback DCI format 1_0 to a first HARQ-ACK subcodebook.

[0168] At 1304, the UE may add HARQ-ACK bits for a PDSCH scheduled by a non-fallback DCI with an extended counter downlink allocation index (C-DAI) field and an extended total DAI (T-DAI) field to the second HARQ-ACK subcodebook. The size of the extended C-DAI field may be greater than two bits. Additionally, the size of the extended T-DAI field may be greater than two bits.

[0169] In some embodiments, the first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook may be concatenated to generate a concatenated HARQ-ACK codebook. The UE may then transmit the concatenated HARQ-ACK codebook via one physical uplink shared channel (PUSCH) resource.

[0170] In some implementations, the UE may transmit a first HARQ-ACK subcodebook on a first physical uplink shared channel (PUSCH) resource. Additionally, the UE may transmit a second HARQ-ACK subcodebook on a second PUSCH resource.

[0171] In some embodiments, the UE may define a first type of physical downlink shared channel / physical uplink shared channel (PDSCH / PUSCH) for multi-PDSCH / multi-PUSCH scheduling and a second type of PDSCH / PUSCH for multi-PDSCH / multi-PUSCH scheduling. In addition, the UE may only receive / transmit the second type of PDSCH / PUSCH. In some embodiments, the UE may increment the hybrid automatic repeat request (HARQ) process number only on the second type of PDSCH / PUSCH. In some embodiments, the UE may increment the hybrid automatic repeat request (HARQ) process number on the first type of PDSCH / PUSCH and the second type of PDSCH / PUSCH, and generate HARQ acknowledgement (ACK) bits for the first type of PDSCH / PUSCH and the second type of PDSCH / PUSCH. Note that the HARQ-ACK bit corresponding to the first type of PDSCH / PUSCH may be set to not ACK (NACK). In some embodiments, the first type of PDSCH may include a PDSCH in multiple PDSCHs scheduled by a downlink control indicator (DCI) that conflicts with an uplink symbol indicated by a time division duplex (TDD) configuration. The second type of PDCCH may include a PDSCH in multiple PDSCHs scheduled by the DCI that does not conflict with an uplink symbol indicated by the TDD configuration. In some embodiments, the first type of PUSCH may include a PUSCH in multiple PUSCHs scheduled by a downlink control indicator (DCI) that conflicts with an uplink symbol indicated by a time division duplex (TDD) configuration. The second type of PUSCH may include a PUSCH in multiple PUSCHs scheduled by the DCI that does not conflict with an uplink symbol indicated by the TDD configuration.

[0172] In some embodiments, the UE may receive a downlink control indicator (DCI) scheduling multiple PDSCHs / PUSCHs from a serving cell and determine a gap between consecutively scheduled PDSCHs / PUSCHs based on at least one K0 / K2 value. The at least one K0 / K2 value may be a K0 / K2 value for a first PDSCH / PUSCH, and determining the gap between consecutively scheduled PDSCHs / PUSCHs may be further based on an additional gap offset value between PDSCHs / PUSCHs per start and length indicator value. In some embodiments, the at least one K0 / K2 value may include a K0 / K2 value for each PDSCH / PUSCH per start and length indicator value.

[0173] In some embodiments, the UE may, for example, index a valid physical uplink control channel (PUSCH) transmission opportunity within multiple PUSCHs scheduled by a single DCI, and determine the starting resource block (RB) of the PUSCH transmission opportunity based on the PUSCH index within the multiple PUSCHs scheduled by the single DCI and the starting PRB provided by the single DCI and the RB offset between the two frequencies.

[0174] Figure 14 An example of a block diagram of a method for determining a first HARQ-ACK subcodebook and a second HARQ-ACK subcodebook in multi-PUSCH scheduling according to some embodiments is shown. Figure 14 The method shown in the figure can also be used together with any one of the systems, methods or devices shown in the figure. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figure, the method can be operated as follows.

[0175] At 1402, a UE (eg, UE 106) may receive a downlink control indicator (DCI) scheduling a plurality of PDSCHs / PUSCHs from a serving cell.

[0176] At 1404, the UE may determine a gap between consecutively scheduled PDSCHs / PUSCHs based on at least one K0 / K2 value. The at least one K0 / K2 value may be a K0 / K2 value for a first PDSCH / PUSCH, and determining the gap between consecutively scheduled PDSCHs / PUSCHs may be further based on an additional gap offset value between PDSCHs / PUSCHs per start and length indicator value. In some embodiments, the at least one K0 / K2 value may include a K0 / K2 value for each PDSCH / PUSCH per start and length indicator value.

[0177] In some embodiments, the UE may define a first type of physical downlink shared channel / physical uplink shared channel (PDSCH / PUSCH) for multi-PDSCH / multi-PUSCH scheduling and a second type of PDSCH / PUSCH for multi-PDSCH / multi-PUSCH scheduling. In addition, the UE may only receive / transmit the second type of PDSCH / PUSCH. In some embodiments, the UE may increment the hybrid automatic repeat request (HARQ) process number only on the second type of PDSCH / PUSCH. In some embodiments, the UE may increment the hybrid automatic repeat request (HARQ) process number on the first type of PDSCH / PUSCH and the second type of PDSCH / PUSCH, and generate HARQ acknowledgement (ACK) bits for the first type of PDSCH / PUSCH and the second type of PDSCH / PUSCH. Note that the HARQ-ACK bit corresponding to the first type of PDSCH / PUSCH may be set to not ACK (NACK). In some embodiments, the first type of PDCCH may include a PDCCH in multiple PDSCHs scheduled by a downlink control indicator (DCI) that conflicts with an uplink symbol indicated by a time division duplex (TDD) configuration. The second type of PDCCH may include a PDCCH in multiple PDSCHs scheduled by the DCI and that does not conflict with an uplink symbol as indicated by the TDD configuration. In some embodiments, the first type of PUCCH may include a PUSCH in multiple PUSCHs scheduled by a downlink control indicator (DCI) that conflicts with an uplink symbol indicated by a time division duplex (TDD) configuration. The second type of PUSCH may include a PUSCH in multiple PUSCHs scheduled by the DCI that does not conflict with an uplink symbol indicated by the TDD configuration.

[0178] In some embodiments, the UE may, for example, index a valid physical uplink control channel (PUSCH) transmission opportunity within multiple PUSCHs scheduled by a single DCI, and determine the starting resource block (RB) of the PUSCH transmission opportunity based on the PUSCH index within the multiple PUSCHs scheduled by the single DCI and the starting PRB provided by the single DCI and the RB offset between the two frequencies.

[0179] In some embodiments, the UE may add HARQ-ACK bits for the physical downlink shared channel (PDSCH) scheduled by fallback DCI format 1_0 to the first HARQ-ACK subcodebook. In addition, the UE may add HARQ-ACK bits for the PDSCH scheduled by the non-fallback DCI with an extended counter downlink allocation index (C-DAI) field and an extended total DAI (T-DAI) field to the second HARQ-ACK subcodebook. The size of the extended C-DAI field may be greater than two bits. In addition, the size of the extended T-DAI field may be greater than two bits. In some embodiments, the first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook may be concatenated to generate a concatenated HARQ-ACK codebook. The UE may then transmit the concatenated HARQ-ACK codebook over one physical uplink shared channel (PUSCH) resource. In some embodiments, the UE may transmit the first HARQ-ACK subcodebook on the first physical uplink shared channel (PUSCH) resource. In addition, the UE may transmit a second HARQ-ACK subcodebook on a second PUSCH resource.

[0180] In some embodiments, the UE may receive an indication of a threshold from the serving cell, for example, the maximum number of physical downlink shared channels (PDSCHs) in a multi-PDSCH schedule that can be scheduled by a downlink control indicator (DCI). The indication may be received via a system information block (SIB) 1 message. Alternatively, the indication may be received via a medium access control (MAC) control element (CE), for example, by selecting a threshold from a set of thresholds configured via radio resource control (RRC) signaling. In addition, the indication may be received via DCI, for example, by selecting a threshold from a set of thresholds configured via radio resource control (RRC) signaling. In addition, the indication may be received via group-specific DCI. In such cases, the UE may receive an index (e.g., a DCI field index) via radio resource control (RRC) signaling to locate the position of the indication within the group-specific DCI. In addition, the UE may divide the configured CCs into a first group and a second group based on the threshold and the maximum number of addressable PDSCHs for each component carrier (CC) in the DCI. In some embodiments, dividing the configured CCs into a first group and a second group based on a threshold and a maximum number of addressable PDSCHs per CC by DCI may include the UE adding each CC with a maximum number of addressable PDSCHs for DCI that is less than or equal to the maximum number of PDSCHs in a multi-PDSCH schedule scheduled by the DCI to the first group, and the UE adding each CC with a maximum number of addressable PDSCHs for DCI that is greater than the maximum number of PDSCHs in a multi-PDSCH schedule scheduled by the DCI to the second group. In addition, the UE may determine a first hybrid automatic repeat request (HARQ) acknowledgement (ACK) subcodebook and a second HARQ-ACK subcodebook based on one or more criteria, for example, based at least in part on dividing the configured CCs into the first group and the second group. In some embodiments, determining the first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook based on one or more criteria may include the UE adding to the first HARQ-ACK subcodebook HARQ-ACK bits for PDSCHs scheduled on CCs in the first group, HARQ-ACK bits for a number of PDSCHs less than or equal to a threshold scheduled on CCs in the second group, HARQ-ACK bits for PDSCHs scheduled by fallback DCI regardless of whether the PDSCH is transmitted on CCs in the first group or CCs in the second group, and HARQ-ACK bits for a physical downlink control channel (PDCCH) for semi-persistent scheduling of PDSCH release or secondary cell dormancy indication, and the UE adding to the second HARQ-ACK subcodebook any remaining HARQ-ACK bits that were not added to the first HARQ-ACK subcodebook. In some embodiments, the UE may sequentially concatenate the first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook.The concatenation may include placing the first HARQ-ACK subcodebook before the second HARQ-ACK subcodebook.

[0181] In some embodiments, the UE may increment the counter downlink allocation index (C-DAI) and the total DAI (T-DAI) for each valid [CC, physical downlink control channel (PDCCH) monitoring opportunity] where PDSCH is received or PDCCH is included in the first HARQ-ACK subcodebook.

[0182] Figure 15 An example of a block diagram illustrating a method for determining inter-slot frequency hopping for multiple PUSCH transmissions according to some embodiments is shown. Figure 14 The method shown in the figure can also be used together with any one of the systems, methods or devices shown in the figure. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figure, the method can be operated as follows.

[0183] At 1502, a UE, such as UE 106, may index a valid physical uplink control channel (PUSCH) transmission opportunity, such as within multiple PUSCHs scheduled by a single DCI.

[0184] At 1504, the UE may determine a starting resource block (RB) for a PUSCH transmission opportunity based on an index of a PUSCH within multiple PUSCHs scheduled by a single DCI and a starting PRB provided by the single DCI and an RB offset between two hop frequencies.

[0185] In some embodiments, the UE may define a first type of physical downlink shared channel / physical uplink shared channel (PDSCH / PUSCH) for multi-PDSCH / multi-PUSCH scheduling and a second type of PDSCH / PUSCH for multi-PDSCH / multi-PUSCH scheduling. In addition, the UE may only receive / transmit the second type of PDSCH / PUSCH. In some embodiments, the UE may increment the hybrid automatic repeat request (HARQ) process number only on the second type of PDSCH / PUSCH. In some embodiments, the UE may increment the hybrid automatic repeat request (HARQ) process number on the first type of PDSCH / PUSCH and the second type of PDSCH / PUSCH, and generate HARQ acknowledgement (ACK) bits for the first type of PDSCH / PUSCH and the second type of PDSCH / PUSCH. Note that the HARQ-ACK bit corresponding to the first type of PDSCH / PUSCH may be set to not ACK (NACK). In some embodiments, the first type of PDSCH may include a PDSCH in multiple PDSCHs scheduled by a downlink control indicator (DCI) that collides with an uplink symbol indicated by a time division duplex (TDD) configuration. The second type of PDSCH may include a PDSCH in multiple PDSCHs scheduled by the DCI and that does not collide with an uplink symbol indicated by the TDD configuration. In some embodiments, the first type of PUCCH may include a PUSCH in multiple PUSCHs scheduled by a downlink control indicator (DCI) that collides with an uplink symbol indicated by a time division duplex (TDD) configuration. The second type of PUSCH may include a PUSCH in multiple PUSCHs scheduled by the DCI that does not collide with an uplink symbol indicated by the TDD configuration.

[0186] In some embodiments, the UE may receive a downlink control indicator (DCI) scheduling multiple PDSCHs / PUSCHs from a serving cell and determine a gap between consecutively scheduled PDSCHs / PUSCHs based on at least one K0 / K2 value. The at least one K0 / K2 value may be a K0 / K2 value for a first PDSCH / PUSCH, and determining the gap between consecutively scheduled PDSCHs / PUSCHs may be further based on an additional gap offset value between PDSCHs / PUSCHs per start and length indicator value. In some embodiments, the at least one K0 / K2 value may include a K0 / K2 value for each PDSCH / PUSCH per start and length indicator value.

[0187] In some embodiments, the UE may add HARQ-ACK bits for the physical downlink shared channel (PDSCH) scheduled by fallback DCI format 1_0 to the first HARQ-ACK subcodebook. In addition, the UE may add HARQ-ACK bits for the PDSCH scheduled by the non-fallback DCI with an extended counter downlink allocation index (C-DAI) field and an extended total DAI (T-DAI) field to the second HARQ-ACK subcodebook. The size of the extended C-DAI field may be greater than two bits. In addition, the size of the extended T-DAI field may be greater than two bits. In some embodiments, the first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook may be concatenated to generate a concatenated HARQ-ACK codebook. The UE may then transmit the concatenated HARQ-ACK codebook over one physical uplink shared channel (PUSCH) resource. In some embodiments, the UE may transmit the first HARQ-ACK subcodebook on the first physical uplink shared channel (PUSCH) resource. In addition, the UE may transmit a second HARQ-ACK subcodebook on a second PUSCH resource.

[0188] In some embodiments, the UE may receive an indication of a threshold from the serving cell, for example, the maximum number of physical downlink shared channels (PDSCHs) in a multi-PDSCH schedule that can be scheduled by a downlink control indicator (DCI). The indication may be received via a system information block (SIB) 1 message. Alternatively, the indication may be received via a medium access control (MAC) control element (CE), for example, by selecting a threshold from a set of thresholds configured via radio resource control (RRC) signaling. In addition, the indication may be received via DCI, for example, by selecting a threshold from a set of thresholds configured via radio resource control (RRC) signaling. In addition, the indication may be received via group-specific DCI. In such cases, the UE may receive an index (e.g., a DCI field index) via radio resource control (RRC) signaling to locate the position of the indication within the group-specific DCI. In addition, the UE may divide the configured CCs into a first group and a second group based on the threshold and the maximum number of addressable PDSCHs for each component carrier (CC) in the DCI. In some embodiments, dividing the configured CCs into a first group and a second group based on a threshold and a maximum number of addressable PDSCHs per CC by DCI may include the UE adding each CC with a maximum number of addressable PDSCHs for DCI that is less than or equal to the maximum number of PDSCHs in a multi-PDSCH schedule scheduled by the DCI to the first group, and the UE adding each CC with a maximum number of addressable PDSCHs for DCI that is greater than the maximum number of PDSCHs in a multi-PDSCH schedule scheduled by the DCI to the second group. In addition, the UE may determine a first hybrid automatic repeat request (HARQ) acknowledgement (ACK) subcodebook and a second HARQ-ACK subcodebook based on one or more criteria, for example, based at least in part on dividing the configured CCs into the first group and the second group. In some embodiments, determining the first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook based on one or more criteria may include the UE adding to the first HARQ-ACK subcodebook HARQ-ACK bits for PDSCHs scheduled on CCs in the first group, HARQ-ACK bits for a number of PDSCHs less than or equal to a threshold scheduled on CCs in the second group, HARQ-ACK bits for PDSCHs scheduled by fallback DCI regardless of whether the PDSCH is transmitted on CCs in the first group or CCs in the second group, and HARQ-ACK bits for a physical downlink control channel (PDCCH) for semi-persistent scheduling of PDSCH release or secondary cell dormancy indication, and the UE adding to the second HARQ-ACK subcodebook any remaining HARQ-ACK bits that were not added to the first HARQ-ACK subcodebook. In some embodiments, the UE may sequentially concatenate the first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook.The concatenation may include placing the first HARQ-ACK subcodebook before the second HARQ-ACK subcodebook.

[0189] In some embodiments, the UE may increment the counter downlink allocation index (C-DAI) and the total DAI (T-DAI) for each valid [CC, physical downlink control channel (PDCCH) monitoring opportunity] where PDSCH is received or PDCCH is included in the first HARQ-ACK subcodebook.

[0190] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining 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 stated to users.

[0191] The embodiments of the present 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.

[0192] In some embodiments, a non-transitory computer-readable storage medium may be configured such that it stores program instructions and / or data, wherein the program instructions, if executed by a computer system, cause the computer system to perform a method, such as any one of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein or any combination of such subsets.

[0193] In some embodiments, a device (e.g., UE 106) may be configured to include a processor (or a group of processors) and a memory medium, wherein the memory medium stores program instructions, wherein the processor is configured to read and execute the program instructions from the memory medium, wherein the program instructions are executable to implement any of the various method embodiments described herein (or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein, or any combination of such subsets). The device may be implemented in any of various forms.

[0194] By interpreting each message / signal X received by a user equipment (UE) in the downlink as a message / signal X transmitted by the base station, and interpreting each message / signal Y transmitted by the UE in the uplink as a message / signal Y received by the base station, any of the methods for operating a UE described herein may become the basis for the corresponding method for operating a base station.

[0195] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.

Claims

1. A user equipment (UE), comprising: at least one antenna; at least one radio component, wherein the at least one radio component is configured to perform cellular communications utilizing at least one radio access technology (RAT); one or more processors coupled to the at least one radio, wherein the one or more processors and the at least one radio are configured to perform communications; The one or more processors are configured to cause the UE to: receiving an indication of a threshold from a serving cell, wherein the threshold is a maximum number of physical downlink shared channels (PDSCHs) in a multiple physical downlink shared channel (PDSCH) schedule that can be scheduled by a downlink control indicator (DCI); Dividing the configured CCs into a first group and a second group based on the threshold and a maximum number of addressable PDSCHs for each component carrier CC by the DCI; as well as A first hybrid automatic repeat request acknowledgement (HARQ-ACK) subcodebook and a second HARQ-ACK subcodebook are determined based on one or more criteria, at least in part, based on dividing the configured CCs into the first group and the second group.

2. The UE according to claim 1, The one or more processors are further configured to cause the UE to: The first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook are sequentially connected.

3. The UE according to claim 1, Wherein said indication of the threshold is received via a System Information Block (SIB) 1 message.

4. The UE according to claim 1, Wherein said indication of a threshold value is received via a Medium Access Control (MAC) Control Element (CE).

5. The UE according to claim 1, wherein the indication of a threshold is received via the DCI.

6. The UE according to claim 1, wherein said indication of a threshold is received via a group-specific DCI; and The UE receives a DCI field index via radio resource control (RRC) signaling to locate the position of the indication within the group-specific DCI.

7. The UE according to claim 1, in, To divide the configured CCs into the first group and the second group based on the threshold and the maximum number of addressable PDSCHs per CC by the DCI, the one or more processors are further configured to cause the UE to: adding to the first group each CC having a maximum number of addressable PDSCHs of the DCI, the maximum number being less than or equal to the threshold; as well as Each CC having a maximum number of addressable PDSCHs of the DCI, the maximum number being greater than the threshold, is added to the second group.

8. The UE according to claim 1, in, To determine the first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook based on one or more criteria, the one or more processors are further configured to cause the UE to: Adding to the first HARQ-ACK subcodebook a HARQ-ACK bit for a PDSCH scheduled on a CC in the first group, a HARQ-ACK bit for a number of PDSCHs less than or equal to the threshold scheduled on a CC in the second group, a HARQ-ACK bit for a PDSCH scheduled by fallback DCI, regardless of whether the PDSCH is transmitted on a CC in the first group or a CC in the second group, and a HARQ-ACK bit for a physical downlink control channel PDCCH for semi-persistent scheduling PDSCH release or secondary cell dormancy indication; and Any remaining HARQ-ACK bits not added to the first HARQ-ACK subcodebook are added to the second HARQ-ACK subcodebook.

9. The UE according to claim 1, The one or more processors are further configured to cause the UE to: A counter downlink allocation index C-DAI and a total downlink allocation index T-DAI are incremented for each valid [CC, physical downlink control channel PDCCH monitoring opportunity], where PDSCH reception or PDCCH is included in the first HARQ-ACK subcodebook.

10. The UE according to claim 1, The one or more processors are further configured to cause the UE to: Define a first type of PDSCH / PUSCH for multi-PDSCH / multi-PUSCH scheduling; defining a second type of PDSCH / PUSCH for multi-PDSCH / multi-PUSCH scheduling; and Only the second type of PDSCH / PUSCH is received / transmitted.

11. The UE according to claim 10, The one or more processors are further configured to cause the UE to: The hybrid automatic repeat request HARQ process number is incremented only on the second type of PDSCH / PUSCH.

12. The UE according to claim 10, The one or more processors are further configured to cause the UE to: Incrementing a hybrid automatic repeat request HARQ process number on the first type of PDSCH / PUSCH and the second type of PDSCH / PUSCH; and HARQ acknowledgement ACK bits are generated for the first type of PDSCH and the second type of PDSCH, wherein the HARQ acknowledgement ACK bit corresponding to the first type of PDSCH is set to not-ACK (NACK).

13. The UE according to claim 10, The first type of PDSCH includes a PDSCH in the multiple PDSCHs scheduled by a downlink control indicator DCI and colliding with an uplink symbol indicated by a time division duplex (TDD) configuration.

14. The UE according to claim 13, The second type of PDSCH includes a PDSCH in the multiple PDSCHs that is scheduled by the DCI and does not conflict with the uplink symbol indicated by the TDD configuration.

15. The UE according to claim 10, The first type of PUSCH includes a PUSCH in the multiple PUSCHs scheduled by a downlink control indicator DCI and colliding with a downlink symbol indicated by a time division duplex TDD configuration.

16. The UE according to claim 15, The second type of PUSCH includes a PUSCH in the multiple PUSCHs that is scheduled by the DCI and does not conflict with a downlink symbol indicated by the TDD configuration.

17. The UE according to claim 1, The one or more processors are further configured to cause the UE to: Receive a downlink control indicator (DCI) scheduling multiple PDSCHs / PUSCHs from a serving cell; and A gap between consecutively scheduled PDSCHs / PUSCHs is determined based on at least one K0 / K2 value.

18. The UE according to claim 17, wherein the at least one K0 / K2 value is a K0 / K2 value for a first PDSCH / PUSCH, and wherein determining the gap between consecutively scheduled PDSCH / PUSCHs is further based on an additional gap offset value between PDSCH / PUSCHs per start and length indicator value.

19. The UE according to claim 17, The at least one K0 / K2 value comprises a K0 / K2 value for each PDSCH / PUSCH per start and length indicator value.

20. The UE according to claim 1, The one or more processors are further configured to cause the UE to: Indexing valid Physical Uplink Control Channel (PUSCH) transmission opportunities within multiple PUSCHs scheduled by a single DCI; and A starting RB of a PUSCH transmission opportunity is determined based on an index of a PUSCH within the multiple PUSCHs scheduled by the single DCI, a starting PRB provided by the single DCI, and a resource block (RB) offset between two hopping frequencies.

21. An apparatus for wireless communication, comprising: Memory; as well as at least one processor in communication with the memory, wherein the at least one processor is configured to: receiving an indication of a threshold from a serving cell; Dividing the configured CCs into a first group and a second group based on the threshold and a maximum number of addressable physical downlink shared channels (PDSCHs) for each component carrier (CC) according to a downlink control indicator (DCI); Determining a first hybrid automatic repeat request acknowledgement (HARQ-ACK) subcodebook and a second HARQ-ACK subcodebook based on one or more criteria; Adding HARQ-ACK bits for PDSCH scheduled by fallback DCI format 1_0 to the first HARQ-ACK subcodebook; and HARQ-ACK bits for a PDSCH scheduled by a non-fallback DCI with an extended counter downlink allocation index C-DAI field and an extended total counter downlink allocation index T-DAI field are added to the second HARQ-ACK subcodebook.

22. The device according to claim 21, The size of the extended C-DAI field is greater than two bits.

23. The device according to claim 21, The size of the extended T-DAI field is greater than two bits.

24. The device according to claim 21, The first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook are concatenated to generate a concatenated HARQ-ACK codebook.

25. The device according to claim 24, wherein the at least one processor is further configured to: The HARQ-ACK codebook for the connection is transmitted on a physical uplink shared channel PUSCH resource.

26. The device according to claim 21, wherein the at least one processor is further configured to: Transmitting the first HARQ-ACK subcodebook on a first physical uplink shared channel (PUSCH) resource; and Transmitting the second HARQ-ACK subcodebook on a second PUSCH resource.

27. The device according to claim 21, wherein the at least one processor is further configured to: Define a first type of PDSCH / PUSCH for multi-PDSCH / multi-PUSCH scheduling; defining a second type of PDSCH / PUSCH for multi-PDSCH / multi-PUSCH scheduling; and Only the second type of PDSCH / PUSCH is received / transmitted.

28. A non-transitory computer-readable memory medium storing program instructions, the program instructions being executable by a processor of a user equipment (UE) to: receiving an indication of a threshold from a serving cell; Dividing the configured CCs into a first group and a second group based on the threshold and a maximum number of addressable physical downlink shared channels (PDSCHs) for each component carrier (CC) according to a downlink control indicator (DCI); Determining a first hybrid automatic repeat request acknowledgement (HARQ-ACK) subcodebook and a second HARQ-ACK subcodebook based on one or more criteria; Receiving, from the serving cell, a DCI for scheduling a plurality of PDSCHs / physical uplink shared channels (PUSCHs); as well as A gap between consecutively scheduled PDSCHs / PUSCHs is determined based on at least one K0 / K2 value.

29. The non-transitory computer-readable memory medium of claim 28, wherein the at least one K0 / K2 value is a K0 / K2 value for a first PDSCH / PUSCH, and wherein determining the gap between consecutively scheduled PDSCH / PUSCHs is further based on an additional gap offset value between PDSCH / PUSCHs per start and length indicator value.

30. The non-transitory computer readable memory medium of claim 28, The at least one K0 / K2 value comprises a K0 / K2 value for each PDSCH / PUSCH per start and length indicator value.

31. The non-transitory computer-readable memory medium of claim 28, wherein the program instructions are further executable by the processor to cause the UE to: The first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook are sequentially connected.

32. The non-transitory computer readable memory medium of claim 28, Wherein said indication of the threshold is received via a System Information Block (SIB) 1 message.

33. The non-transitory computer readable memory medium of claim 28, wherein the indication of the threshold is received via a Medium Access Control (MAC) Control Element (CE) by selecting a value from a set of values ​​configured by Radio Resource Control (RRC) signaling.

34. The non-transitory computer readable memory medium of claim 28, wherein the indication of the threshold is received via the DCI by selecting a value from a set of values ​​configured by radio resource control (RRC) signaling.

35. The non-transitory computer readable memory medium of claim 28, wherein said indication of a threshold is received via a group-specific DCI; and The UE receives a DCI field index via radio resource control (RRC) signaling to locate the position of the indication within the group-specific DCI.

36. The non-transitory computer readable memory medium of claim 28, in, To divide the configured CCs into the first group and the second group based on the threshold and the maximum number of addressable PDSCHs per CC by the DCI, the program instructions are further executable by the processor to cause the UE to: adding to the first group each CC having a maximum number of addressable PDSCHs of the DCI, the maximum number being less than or equal to the threshold; as well as Each CC having a maximum number of addressable PDSCHs of the DCI, the maximum number being greater than the threshold, is added to the second group.

37. The non-transitory computer readable memory medium of claim 28, in, To determine the first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook based on one or more criteria, the program instructions can be further executed by the processor to cause the UE to: Adding to the first HARQ-ACK subcodebook a HARQ-ACK bit for a PDSCH scheduled on a CC in the first group, a HARQ-ACK bit for a number of PDSCHs less than or equal to the threshold scheduled on a CC in the second group, a HARQ-ACK bit for a PDSCH scheduled by fallback DCI, regardless of whether the PDSCH is transmitted on a CC in the first group or a CC in the second group, and a HARQ-ACK bit for a physical downlink control channel PDCCH for semi-persistent scheduling PDSCH release or secondary cell dormancy indication; and Any remaining HARQ-ACK bits not added to the first HARQ-ACK subcodebook are added to the second HARQ-ACK subcodebook.

38. The non-transitory computer readable memory medium of claim 28, The program instructions are further executable by the processor to cause the UE to: A counter downlink allocation index C-DAI and a total downlink allocation index T-DAI are incremented for each valid [CC, physical downlink control channel PDCCH monitoring opportunity], where PDSCH reception or PDCCH is included in the first HARQ-ACK subcodebook.

39. The non-transitory computer readable memory medium of claim 38, The program instructions are further executable by the processor to cause the UE to: Define a first type of PDSCH / PUSCH for multi-PDSCH / multi-PUSCH scheduling; A second type of PDSCH / PUSCH is defined for multi-PDSCH / multi-PUSCH scheduling; Only the second type of PDSCH / PUSCH is received / transmitted.

Images