Dynamic HARQ-ACK codebook for scheduling multiple PDSCHs by a single DCI

Abstract

Apparatus, methods, and systems for constructing dynamic HARQ-ACK codebooks for multiple PDSCHs are disclosed. One method (1200) includes receiving (1205) a first DCI that schedules at least one first PDSCH transmission on a first serving cell, wherein the first DCI is capable of scheduling multiple PDSCH transmissions. The method (1200) includes receiving (1210) at least one second DCI that schedules at least one second PDSCH transmission on a second serving cell, and determining (1215) HARQ-ACK feedback for the scheduled first and second PDSCH transmissions. The method (1200) further includes determining (1220) a sequence of HARQ-ACK bits corresponding to the scheduled first and second PDSCH transmissions, based at least on a serving cell index and the occurrence time of the PDSCH, and reporting (1225) a HARQ-ACK codebook including the determined sequence of HARQ-ACK bits.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 186,71, filed May 10, 2021, entitled “DYNAMIC HARQ-ACK CODEBOOK FOR MULTIPLE PDSCH SCHEDULING BY SINGLE DCI” by Ankit Bhamri, Alexander Golitschek, Ali Ramadan Ali, Karthikeyan Ganesan, and Sher Ali Cheema, which is incorporated herein by reference. Technical Field

[0003] The subject matter disclosed herein generally relates to wireless communication, and more specifically to a dynamic hybrid automatic repeat request acknowledgment (“HARQ-ACK”) codebook for scheduling multiple physical downlink shared channels (“PDSCH”) by a single downlink control information (“DCI”). Background Technology

[0004] In New Radio (“NR”) Release 17 (“Rel-17”), for NR operation between 52.6–71 GHz, it has been agreed that multiple PDSCH scheduling by a single DCI will be used for higher subcarrier spacing (“SCS”) values, such as 480 kHz and 960 kHz. One issue arising from this enhancement is the construction of the HARQ-ACK codebook. Currently in NR Releases 15 and 16 (“Rel-15 / 16”), when dynamic HARQ-ACK is applied, the downlink allocation indicator (including the counter and the total downlink allocation indicator (“DAI”)) is counted based on the DCI. Summary of the Invention

[0005] A process for constructing a dynamic HARQ-ACK codebook for multiple PDSCHs is disclosed. This process can be implemented by an apparatus, system, method, or computer program product.

[0006] A method at a user equipment (“UE”) includes: receiving first downlink control information (“DCI”) that schedules at least one first physical downlink shared channel (“PDSCH”) transmission on a first serving cell, wherein the first DCI is capable of scheduling multiple PDSCH transmissions. The first method includes: receiving at least one second DCI that schedules at least one second PDSCH transmission on a second serving cell, and determining hybrid automatic repeat request acknowledgment (“HARQ-ACK”) feedback for the scheduled first and second PDSCH transmissions. The first method includes: determining a sequence of HARQ-ACK bits corresponding to the scheduled first and second PDSCH transmissions, and reporting a HARQ-ACK codebook corresponding to the determined HARQ-ACK feedback, wherein the HARQ-ACK codebook includes HARQ-ACK bits according to the determined sequence, and the sequence is determined at least based on a serving cell index and the occurrence time of the PDSCH.

[0007] A method at a network device includes: transmitting a first DCI that schedules at least one first PDSCH transmission on a first serving cell, wherein the first DCI is capable of scheduling multiple PDSCH transmissions. The method includes: transmitting at least one second DCI that schedules at least one second PDSCH transmission on a second serving cell, and transmitting the scheduled first and second PDSCH transmissions. The method includes: receiving a HARQ-ACK codebook containing a plurality of HARQ-ACK bits, and determining a sequence of HARQ-ACK bits corresponding to the scheduled first and second PDSCH transmissions, wherein the determination is based at least on a serving cell index and the occurrence time of the PDSCH. The method includes: determining HARQ-ACK feedback for the scheduled first and second PDSCH transmissions based on the determined sequence. Attached Figure Description

[0008] The embodiments briefly described above will be described in more detail with reference to the specific embodiments shown in the accompanying drawings. It should be understood that these drawings depict only some embodiments and are therefore not intended to limit the scope; these embodiments will be described and explained with additional specificity and detail using the drawings, in which:

[0009] Figure 1 This is a block diagram illustrating one embodiment of a wireless communication system for constructing dynamic HARQ-ACK codebooks for multiple PDSCHs;

[0010] Figure 2 This is a diagram illustrating one embodiment of the New Radio (“NR”) protocol stack;

[0011] Figure 3 This is a diagram illustrating one embodiment of multiple HARQ-ACK subcodebooks for multiple PDSCHs via a single DCI;

[0012] Figure 4 This is a diagram illustrating another embodiment of multiple HARQ-ACK subcodebooks for multiple PDSCHs via a single DCI;

[0013] Figure 5 This is a diagram illustrating one embodiment of HARQ-ACK codebook construction, which uses a single HARQ-ACK codebook for multiple PDSCHs scheduled by a single DCI;

[0014] Figure 6 This is a diagram illustrating one embodiment of HARQ-ACK codebook construction, which corresponds to two DCIs scheduling different numbers of PDSCHs for multiple HARQ-ACK sub-codebooks;

[0015] Figure 7 This is a diagram illustrating one embodiment of HARQ-ACK codebook construction, which addresses the overlap between actual and virtual assumed PDSCH in the same time slot and the same component carrier (“CC”);

[0016] Figure 8 This is a diagram illustrating an embodiment of HARQ-ACK codebook construction with multiple non-contiguous PDSCH schedules and PDSCH indices;

[0017] Figure 9 This is a diagram illustrating another embodiment of HARQ-ACK codebook construction with multiple non-contiguous PDSCH schedules and PDSCH indices;

[0018] Figure 10 This is a block diagram illustrating one embodiment of a user equipment apparatus that can be used to build a dynamic HARQ-ACK codebook for multiple PDSCHs;

[0019] Figure 11 This is a block diagram illustrating one embodiment of a network device that can be used to build dynamic HARQ-ACK codebooks for multiple PDSCHs;

[0020] Figure 12 This is a flowchart illustrating an embodiment of a method for constructing a dynamic HARQ-ACK codebook for multiple PDSCHs;

[0021] Figure 13 This is a flowchart illustrating another embodiment of a method for constructing a dynamic HARQ-ACK codebook for multiple PDSCHs. Detailed Implementation

[0022] As will be understood by those skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Therefore, embodiments may take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects.

[0023] For example, the disclosed embodiments can be implemented as hardware circuitry, including custom-designed very large-scale integration (“VLSI”) circuitry or gate arrays, off-the-shelf semiconductors (such as logic chips, transistors), or other discrete components. The disclosed embodiments can also be implemented in programmable hardware devices, such as field-programmable gate arrays, programmable array logic, programmable logic devices, or similar devices. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code, which may, for example, be organized into objects, procedures, or functions.

[0024] Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code (hereinafter referred to as code). The storage device may be tangible, non-transitory, and / or non-transitive. The storage device may not include signals. In certain embodiments, the storage device uses only signals to access the code.

[0025] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0026] More specific examples of storage devices (a non-exhaustive list) include the following: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable optical disc read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium that can contain or store programs for use by or in connection with an instruction execution system, apparatus, or device.

[0027] The code used to perform the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​(such as Python, Ruby, Java, Smalltalk, C++, etc.) and traditional procedural programming languages ​​(such as the "C" programming language, etc.) and / or machine languages ​​(such as assembly language). The code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer can be connected to the user's computer via any type of network, including a local area network ("LAN"), a wireless local area network ("WLAN"), or a wide area network ("WAN"), or can be connected to an external computer (e.g., via the Internet using an Internet service provider ("ISP").

[0028] Furthermore, the features, structures, or characteristics of the described embodiments can be combined in any suitable manner. Numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided in the following description to provide a comprehensive understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more specific details, or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the embodiments.

[0029] References to "an embodiment," "embodiment," or similar language in this specification indicate that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Therefore, unless expressly stated otherwise, the phrases "in an embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily, refer to the same embodiment, but rather to "one or more, but not all, embodiments." Unless expressly stated otherwise, the terms "including," "comprising," "having," and variations thereof mean "including, but not limited to," "including, but not limited to." Unless expressly stated otherwise, the list of items does not imply that any or all items are mutually exclusive. Unless expressly stated otherwise, the terms "a," "an," and "the" also refer to "one or more."

[0030] As used herein, a list with the conjunction “and / or” includes any single item in the list or a combination of items in the list. For example, a list of A, B, and / or C includes only A, only B, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term “one or more” includes any single item in the list or a combination of items in the list. For example, one or more of A, B, and C includes only A, only B, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term “one of” includes one and only one of any single item in the list. For example, “one of A, B, and C” includes only A, only B, or only C, excluding combinations of A, B, and C. As used herein, “a member of the group consisting of A, B, and C” includes and only includes one of A, B, or C, excluding combinations of A, B, and C. As used in this article, “members selected from A, B, and C and combinations thereof” includes only A, only B, only C, combinations of A and B, combinations of B and C, combinations of A and C, or combinations of A, B, and C.

[0031] The following description of aspects of embodiments is based on schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to generate a machine, such that instructions executable via the processor of the computer or other programmable data processing apparatus create components for implementing the functions / actions specified in the flowcharts and / or block diagrams.

[0032] Code may also be stored in a storage device that can instruct a computer, other programmable data processing apparatus or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of art, which includes instructions for implementing the functions / actions specified in the flowcharts and / or block diagrams.

[0033] Code may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be executed on the computer, other programmable apparatus or other device to produce a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for implementing the function / action specified in the flowchart and / or block diagram.

[0034] The flowcharts, diagrams, and / or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the flowcharts and / or block diagrams may represent a code module, segment, or portion, which includes one or more executable instructions for implementing the specified logical function(s).

[0035] It should also be noted that in some alternative implementations, the functions shown in the blocks may not appear in the order shown in the figures. For example, in fact, two blocks shown consecutively may be executed substantially simultaneously, or these blocks may sometimes be executed in reverse order, depending on the functions involved. Other steps and methods that are functionally, logically, or effectively equivalent to one or more blocks or portions thereof in the figures shown can be envisioned.

[0036] While various arrow types and line styles may be used in flowcharts and / or block diagrams, it should be understood that they do not limit the scope of the corresponding embodiments. In fact, some arrows or other connectors may be used only to indicate the logical flow of the depicted embodiment. For example, arrows may indicate waiting or monitoring periods of unspecified duration between enumerated steps of a depicted embodiment. It will also be noted that each block of the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a system based on dedicated hardware, or a combination of dedicated hardware and code, performing a specified function or action.

[0037] The description of the elements in each figure can be referenced to the elements in subsequent figures. Similar reference numerals refer to similar elements in all figures, including alternative embodiments of similar elements.

[0038] Generally, this disclosure describes systems, methods, and apparatuses for constructing dynamic HARQ-ACK codebooks for multiple PDSCHs. In some embodiments, these methods may be performed using computer code embedded in a computer-readable medium. In some embodiments, the apparatus or system may include a computer-readable medium containing computer-readable code that, when executed by a processor, causes the apparatus or system to perform at least a portion of the solutions described below.

[0039] For NR operation between 52.6-71 GHz, it has been agreed that for higher SCS values, such as 480 kHz and 960 kHz, multiple PDSCHs will be scheduled by a single DCI. One issue arising from this enhancement is the construction of the HARQ-ACK codebook. In particular, this disclosure addresses issues related to dynamic (Type 2) HARQ-ACK. Currently in NR Rel-15 / 16, when dynamic HARQ-ACK is applied, downlink allocation indicators (including the counter downlink allocation indicator (“C-DAI”) and the total downlink allocation indicator (“T-DAI”)) are counted on a DCI-based basis. However, when a single DCI can schedule multiple PDSCH transmissions (also referred to as “PDSCHs”), enhancements are needed to the counting of C-DAI and T-DAI, as well as the PDSCH index used for HARQ-ACK codebook construction.

[0040] For multi-PDSCH scheduling and HARQ-ACK, wireless networks can support the following enhancements: multi-PDSCH / PUSCH scheduling utilizing a single DCI and Hybrid Automatic Repeat Request (“HARQ”) support. Without these enhancements, based on the existing mechanism, it would be unclear how many PDSCHs were not received or missed when one of the DCIs was not received (considering that some DCIs might schedule multiple PDSCHs while others might schedule a single PDSCH).

[0041] Solutions for constructing dynamic HARQ-ACK codebooks for multiple PDSCHs are disclosed. These solutions can be implemented by apparatus, systems, methods, or computer program products. In some embodiments, when multiple PDSCH transmissions can be scheduled by a single DCI, the device (e.g., UE) determines the number of sub-HARQ-ACK codebooks and their construction. In some embodiments, when multiple PDSCH transmissions can be scheduled by a single DCI, HARQ-ACK sequences (e.g., PDSCH indices) are used for dynamic HARQ-ACK codebook construction. In some embodiments, the device performs time-domain bundling of HARQ-ACK bits corresponding to multiple PDSCH transmissions scheduled by a single DCI.

[0042] Figure 1 A wireless communication system 100 for constructing dynamic HARQ-ACK codebooks for multiple PDSCHs according to embodiments of the present disclosure is described. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a radio access network (“RAN”) 120, and a mobile core network 140. The RAN 120 and the mobile core network 140 constitute a mobile communication network. The RAN 120 may consist of a base station unit 121 with which the remote unit 105 communicates using a wireless communication link 123. Although Figure 1The document describes a specific number of remote units 105, base station units 121, wireless communication links 123, RAN 120, and mobile core network 140, but those skilled in the art will recognize that the wireless communication system 100 may include any number of remote units 105, base station units 121, wireless communication links 123, RAN 120, and mobile core network 140.

[0043] In one implementation, RAN 120 conforms to the fifth-generation (“5G”) cellular system specifications as defined in the 3GPP (“3GPP”) program. For example, RAN 120 could be a next-generation radio access network (“NG-RAN”), implementing a new radio (“NR”) radio access technology (“RAT”) and / or a long-term evolution (“LTE”) RAT. In another example, RAN 120 could include a non-3GPP RAT (e.g., Alternatively, it may be a WLAN conforming to the Institute of Electrical and Electronics Engineers (“IEEE”) 802.11 series of standards. In another implementation, RAN 120 conforms to the LTE system specified in the 3GPP specification. However, more generally, the wireless communication system 100 may employ other open or proprietary communication networks, such as Global Microwave Access Interoperability (“WiMAX”) or IEEE 802.16 series of standards. This disclosure is not intended to limit itself to any particular wireless communication system architecture or protocol implementation.

[0044] In one embodiment, remote unit 105 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart TVs (e.g., internet-connected TVs), smart appliances (e.g., internet-connected appliances), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), etc. In some embodiments, remote unit 105 includes wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, remote unit 105 may be referred to as UE, subscriber unit, mobile station, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, user terminal, wireless transceiver unit (“WTRU”), device, or other terms used in the art. In various embodiments, remote unit 105 includes a user identity and / or identification module (“SIM”) and a mobile device providing mobile termination functionality (e.g., radio transmission, handover, voice codec, error detection and correction, SIM signaling and access). In some embodiments, the remote unit 105 may include a terminal device (“TE”) and / or be embedded in a device or apparatus (e.g., a computing device as described above).

[0045] Remote unit 105 can communicate directly with one or more base station units 121 in RAN 120 via uplink (“UL”) and downlink (“DL”) communication signals. Furthermore, the UL and DL communication signals can be transmitted via wireless communication link 123. Additionally, the UL communication signals may include one or more uplink channels, such as the Physical Uplink Control Channel (“PUCCH”) and / or the Physical Uplink Shared Channel (“PUSCH”), while the DL communication signals may include one or more downlink channels, such as the Physical Downlink Control Channel (“PDCCH”) and / or the Physical Downlink Shared Channel (“PDSCH”). Here, RAN 120 is an intermediate network providing access to the mobile core network 140 for remote unit 105.

[0046] In some embodiments, remote unit 105 communicates with application server 151 via a network connection to mobile core network 140. For example, application 107 in remote unit 105 (e.g., a web browser, media client, telephone, and / or Voice over Internet Protocol (“VoIP”) application) can trigger remote unit 105 to establish a Protocol Data Unit (“PDU”) session (or other data connection) with mobile core network 140 via RAN 120. The PDU session represents a logical connection between remote unit 105 and User Plane Function (“UPF”) 141. Mobile core network 140 then uses the PDU session to relay services between remote unit 105 and application server 151 in packet data network 150.

[0047] To establish a PDU session (or PDU connection), remote unit 105 must register with mobile core network 140 (also referred to as "attached to mobile core network" in the context of fourth-generation ("4G") systems). It should be noted that remote unit 105 can establish one or more PDU sessions (or other data connections) with the mobile core network. Therefore, remote unit 105 can have at least one PDU session for communicating with packet data network 150. Remote unit 105 can establish additional PDU sessions for communicating with other data networks and / or other communication peers.

[0048] In the context of a 5G system (“5GS”), the term “PDU session” refers to a data connection that provides an end-to-end (“E2E”) user plane (“UP”) connection between a remote unit 105 and a specific data network (“DN”) via UPF 141. A PDU session supports one or more Quality of Service (“QoS”) streams. In some embodiments, a one-to-one mapping may exist between QoS streams and QoS profiles, such that all packets belonging to a particular QoS stream have the same 5G QoS identifier (“5QI”).

[0049] In the context of 4G / LTE systems (such as Evolved Packet System (“EPS”)), a Packet Data Network (“PDN”) connection (also known as an EPS session) provides an end-to-end (E2E) connection between the remote unit and the PDN. The PDN connection procedure establishes an EPS bearer, i.e., a tunnel between the remote unit 105 and the PDN gateway (“PGW”, not shown) in the mobile core network 140. In some embodiments, there is a one-to-one mapping between the EPS bearer and a QoS profile, such that all packets belonging to a particular EPS bearer have the same QoS Class Identifier (“QCI”).

[0050] Base station unit 121 may be distributed within a geographical area. In some embodiments, base station unit 121 may also be referred to as an access terminal, access point, base station, base station, Node B (“NB”), evolved Node B (abbreviated as eNodeB or “eNB”, also known as Evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) Node B), 5G / NR Node B (“gNB”), home Node B, relay node, RAN node, or other terms used in the art. Base station unit 121 is typically part of an RAN (such as RAN 120), which may include one or more controllers communicatively coupled to one or more corresponding base station units 121. These and other elements of the radio access network are not shown, but are generally well known to those skilled in the art. Base station unit 121 is connected to mobile core network 140 via RAN 120.

[0051] Base station unit 121 can serve multiple remote units 105 within a service area (e.g., a cell or cell sector) via wireless communication link 123. Base station unit 121 can communicate directly with one or more remote units 105 via communication signals. Generally, base station unit 121 transmits DL communication signals in the time, frequency, and / or spatial domains to serve the remote units 105. Furthermore, DL communication signals can be transmitted via wireless communication link 123. Wireless communication link 123 can be any suitable carrier in the licensed or unlicensed radio spectrum. Wireless communication link 123 can facilitate communication between one or more remote units 105 and / or one or more base station units 121.

[0052] It should be noted that during NR operation (referred to as "NR-U") on unlicensed spectrum, base station unit 121 and remote unit 105 communicate via unlicensed (i.e., shared) radio spectrum. Similarly, during LTE operation (referred to as "LTE-U") on unlicensed spectrum, base station unit 121 and remote unit 105 also communicate via unlicensed (i.e., shared) radio spectrum.

[0053] In one embodiment, the mobile core network 140 is a 5G core network (“5GC”) or an evolved packet core (“EPC”), which can be coupled to packet data networks 150, such as the Internet and private data networks, as well as other data networks. The remote unit 105 may have a subscription or other account to the mobile core network 140. In various embodiments, each mobile core network 140 belongs to a single mobile network operator (“MNO”) and / or a public land mobile network (“PLMN”). This disclosure is not intended to limit implementation to any particular wireless communication architecture or protocol.

[0054] The mobile core network 140 includes multiple network functions (“NFs”). As shown, the mobile core network 140 includes at least one UPF 141. The mobile core network 140 also includes multiple control plane (“CP”) functions, including but not limited to Access and Mobility Management Functions (“AMF”) 143, Session Management Functions (“SMF”) 145, Policy Control Functions (“PCF”) 147, Unified Data Management Functions (“UDM”), and User Data Repository (“UDR”) serving RAN 120. In some embodiments, the UDM and UDR are co-located and described as a combined entity “UDM / UDR” 149. Although Figure 1 A specific number and type of network functions are described, but those skilled in the art will recognize that the mobile core network 140 may include any number and type of network functions.

[0055] In the 5G architecture, UPF 141 is responsible for packet routing and forwarding, packet inspection, QoS processing, and external PDU sessions for interconnecting data networks (“DN”). AMF 143 is responsible for non-access spectrum (“NAS”) signaling termination, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management. SMF 145 is responsible for session management (i.e., session establishment, modification, and release), remote unit (i.e., UE) Internet Protocol (“IP”) address allocation and management, DL data notification, and service bootstrapping configuration of UPF 141 to achieve correct service routing.

[0056] PCF 147 is responsible for unifying the policy framework, providing policy rules for CP functions, and providing access subscription information for policy decisions in the UDR. UDM is responsible for generating authentication and key protocol (“AKA”) credentials, processing user identification, access authorization, and subscription management. The UDR is a repository of subscriber information and can be used to provide services for many network functions. For example, the UDR can store subscription data, policy-related data, and subscriber-related data that can be exposed to third-party applications.

[0057] In various embodiments, the mobile core network 140 may also include a network repository function (“NRF”) (which provides network function (“NF”) service registration and discovery, enabling NFs to recognize appropriate services from each other and communicate with each other via an application programming interface (“API”), a network exposure function (“NEF”) (which is responsible for enabling customers and network partners to easily access network data and resources), an authentication server function (“AUSF”), or other NFs defined for the 5GC. When present, the AUSF may act as an authentication server and / or authentication proxy, thereby allowing the AMF 143 to authenticate the remote unit 105. In some embodiments, the mobile core network 140 may include an authentication, authorization, and accounting (“AAA”) server.

[0058] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, where each mobile data connection uses a specific network slice. Here, a "network slice" refers to a portion of the mobile core network 140 optimized for a specific service type or communication service. For example, one or more network slices may be optimized for enhanced mobile broadband ("eMBB") service. As another example, one or more network slices may be optimized for ultra-reliable low-latency communication (URLLC) service. In other examples, network slices may be optimized for machine-type communication ("MTC") service, massive MTC ("mMTC") service, and Internet of Things ("IoT") service. In still other examples, network slices may be deployed for specific application services, vertical services, specific use cases, etc.

[0059] Network slice instances can be identified by single network slice selection aid information (“S-NSSAI”), while a set of network slices authorized for use by remote unit 105 is identified by network slice selection aid information (“NSSAI”). Here, “NSSAI” refers to a vector value including one or more S-NSSAI values. In some embodiments, various network slices may include individual instances of network functions, such as SMF 145 and UPF 141. In some embodiments, different network slices may share some common network functions, such as AMF 143. For ease of illustration, Figure 1 Different network slices are not shown, but it is assumed that they are supported.

[0060] although Figure 1The components of the 5G RAN and 5G core network are described, but the embodiments described for building a dynamic HARQ-ACK codebook for multiple PDSCHs are applicable to other types of communication networks and RATs, including IEEE 802.11 variants, Global System for Mobile Communications (“GSM”, i.e., 2G digital cellular networks), General Packet Radio Service (“GPRS”), General Mobile Telecommunications System (“UMTS”), LTE variants, CDMA2000, Bluetooth, ZigBee, Sigfox, and others.

[0061] Furthermore, in the LTE variant where the mobile core network 140 is an EPC, the described network functions can be replaced by appropriate EPC entities, such as the Mobility Management Entity (“MME”), Serving Gateway (“SGW”), PGW, Home Subscriber Server (“HSS”), etc. For example, AMF 143 can be mapped to the MME, SMF 145 can be mapped to the control plane portion of the PGW and / or the MME, UPF 141 can be mapped to the SGW and the user plane portion of the PGW, UDM / UDR 149 can be mapped to the HSS, etc.

[0062] In the following description, the term "gNB" is used for base station / base station unit, but can be replaced by any other radio access node, such as RAN node, ng-eNB, eNB, base station ("BS"), access point ("AP"), NR BS, 5G NB, transmit and receive point ("TRP"), etc. Similarly, the term "UE" is used for mobile station / remote unit, but can be replaced by any other remote device, such as remote unit, MS, ME, etc. Furthermore, these operations are primarily described in the context of 5G NR. However, the solutions / methods described below are equally applicable to other mobile communication systems for building dynamic HARQ-ACK codebooks for multiple PDSCHs. As used herein, "HARQ-ACK" can uniformly represent positive acknowledgment ("ACK") and negative acknowledgment ("NACK"). ACK indicates that a transport block ("TB") was correctly received, while NACK (or NAK) indicates that a TB was incorrectly received (or not detected).

[0063] Figure 2 A protocol stack 200 according to embodiments of this disclosure is described. Although Figure 2The diagram shows UE 205, RAN node 207 (e.g., gNB), and 5G core network 209 (e.g., containing AMF), but these are representative of a group of remote units 105 interacting with base station unit 121 and mobile core network 140. As shown, protocol stack 200 includes user plane protocol stack 201 and control plane protocol stack 203. User plane protocol stack 201 includes a physical (“PHY”) layer 211, a media access control (“MAC”) sublayer 213, a radio link control (“RLC”) sublayer 215, a packet data convergence protocol (“PDCP”) sublayer 217, and a service data adaptation protocol (“SDAP”) layer 219. Control plane protocol stack 203 includes PHY layer 211, MAC sublayer 213, RLC sublayer 215, and PDCP sublayer 217. Control plane protocol stack 203 also includes a radio resource control (“RRC”) layer 221 and a non-access stratum (“NAS”) layer 223.

[0064] The AS layer 225 (also referred to as the "AS protocol stack") of the user plane protocol stack 201 consists of at least the SDAP sublayer 219, PDCP sublayer 217, RLC sublayer 215, and MAC sublayer 213, as well as the PHY layer 211. The AS layer 227 of the control plane protocol stack 203 consists of at least the RRC sublayer 221, PDCP sublayer 217, RLC sublayer 215, MAC sublayer 213, and PHY layer 211. Layer 1 ("L1") includes the PHY layer 211. Layer 2 ("L2") is divided into the SDAP sublayer 219, PDCP sublayer 217, RLC sublayer 215, and MAC sublayer 213. Layer 3 ("L3") includes the RRC sublayer 221 and the NAS layer 223 for the control plane, and includes, for example, an Internet Protocol ("IP") layer or a PDU layer (not shown) for the user plane. L1 and L2 are referred to as "lower layers", while L3 and above (such as transport layer and application layer) are referred to as "higher layers" or "upper layers".

[0065] Physical layer 211 provides a transport channel to MAC sublayer 213. MAC sublayer 213 provides a logical channel to RLC sublayer 215. RLC sublayer 215 provides an RLC channel to PDCP sublayer 217. PDCP sublayer 217 provides radio bearers to SDAP sublayer 219 and / or RRC layer 221. SDAP sublayer 219 maps QoS flows within a PDU session to corresponding data radio bearers on the air interface, and SDAP sublayer 219 connects QoS flows to 5GC (e.g., to User Plane Function, UPF). RRC layer 221 provides the addition, modification, and release of carrier aggregation (“CA”) and / or dual connectivity (“DC”). RRC layer 221 also manages the establishment, configuration, maintenance, and release of signaling radio bearers (“SRB”) and data radio bearers (“DRB”). In some embodiments, the function of the RRC entity is to detect and recover from radio link failures.

[0066] NAS layer 223 is located between UE 205 and the AMF in 5GC 509. NAS messages are transparently transmitted through the RAN. NAS layer 223 is used to manage the establishment of communication sessions and maintain continuous communication with UE 205 when UE 205 moves between different cells in the RAN. Conversely, AS layers 225 and 227 are located between UE 205 and the RAN (i.e., RAN node 207) and carry information through the radio portion of the network. Although Figure 2 It is not described in the document, but the IP layer exists above the NAS layer 223, the transport layer exists above the IP layer, and the application layer exists above the transport layer.

[0067] MAC layer 213 is the lowest sublayer in the Layer 2 architecture of the NR protocol stack. Its connection to the PHY layer 211 below is via a transport channel, and its connection to the RLC layer 215 above is via a logical channel. Therefore, MAC layer 213 performs multiplexing and demultiplexing between the logical and transport channels: the transmitting MAC layer 213 constructs a MAC PDU (called a transport block) from the MAC Service Data Unit (“SDU”) received via the logical channel, and the receiving MAC layer 213 recovers the MAC SDU from the MAC PDU received via the transport channel.

[0068] MAC layer 213 provides data transmission services to RLC layer 215 through logical channels. These logical channels are either control logical channels carrying control data (i.e., RRC signaling) or service logical channels carrying user plane data. Conversely, data from MAC layer 213 is exchanged with PHY layer 211 through transport channels, which are classified as downlink or uplink. Data is multiplexed into transport channels according to its over-the-air transmission method.

[0069] The Physical Layer 211 is responsible for the actual transmission of data and control information via the air interface; that is, the PHY layer 211 carries all information from the MAC transport channel via the air interface on the transmission side. Some important functions performed by the PHY layer 211 include coding and modulation, link adaptation (e.g., adaptive modulation and coding (“AMC”)), power control, cell search and random access (for initial synchronization and handover purposes), and other measurements for the RRC layer 221 (within and between 3GPP systems, i.e., NR and / or LTE systems). The PHY layer 211 transmits based on transport parameters such as modulation scheme, coding rate (i.e., modulation and coding scheme (“MCS”)), number of physical resource blocks, etc.

[0070] Clause 9.1.3.1 of 3GPP Technical Specification (“TS”) 38.213 of NR Rel-15 / 16 specifies the following details related to the downlink allocation indicator (“DAI”) used for the type 2 HARQ-ACK codebook: For the type 2 HARQ-ACK codebook in the physical uplink control channel, the UE uses DCI format scheduling to receive PDSCH or semi-persistent scheduling (“SPS”) to release PDSCH or to instruct the secondary cell (“SCell”) to sleep on the active DL BWP of the serving cell c (e.g., as described in Clause 10.1 of 3GPP TS 38.213) to determine the timing of PDCCH monitoring, and the UE sends HARQ-ACK information for it in the same PUCCH transmission in slot n.

[0071] For NR Rel-15 / 16, the PDCCH monitoring timing set is determined based on the following: A) the PDSCH-to-HARQ_feedback timing indicator field value for PUCCH transmission with HARQ-ACK information in slot n in response to PDSCH reception, SPS PDSCH release, or SCell sleep indication; and B) the slot offset K0 (defined in 3GPP TS 38.214), provided by the time domain resource allocation field in the DCI format scheduling of PDSCH reception and by the parameter pdsch-AggregationFactor, or pdsch-AggregationFactor-r16, or repetitionNumber (if any).

[0072] The set of PDCCH monitoring opportunities used for DCI format scheduling of PDSCH reception or SPS PDSCH release or indicating SCell hibernation is defined as the union of PDCCH monitoring opportunities on the active DL BWP of the configured serving cell. The set of PDCCH monitoring opportunities is indexed in ascending order of the start time of the search space set associated with the PDCCH monitoring opportunity. The cardinality of the set of PDCCH monitoring opportunities defines the total number M of PDCCH monitoring opportunities.

[0073] In the DCI format, the value of the C-DAI field represents the cumulative number of {serving cell, PDCCH monitoring time} pairs associated with the DCI format, including (multiple) PDSCH receptions, SPS PDSCH releases, or SCell sleep indicators, that occurred before the current serving cell and the current PDCCH monitoring time.

[0074] First, if the UE indicates via parameter type2-HARQ-ACK-Codebook that it supports receiving multiple PDSCHs from the serving cell scheduled during the same PDCCH monitoring time, then the PDSCH reception start times of the same {serving cell, PDCCH monitoring time} pair will be received in ascending order.

[0075] Second, in ascending order of the serving cell index, and

[0076] Third, sort the PDCCH monitoring timing index m in ascending order, where 0 ≤ m < M.

[0077] For the active DL BWP of the serving cell, if the UE is not provided with the parameter coresetPoolIndex for one or more first CORESETs (or is provided with the parameter coresetPoolIndex with a value of "0"), and is provided with the parameter coresetPoolIndex with a value of "1" for one or more second CORESETs, and is provided with the parameter ackNackFeedbackMode with a value of "joint", then the value of the counter DAI is in the following order: for the same serving cell index and the same PDCCH monitoring timing index, first for the first CORESET, then for the second CORESET.

[0078] When present (see 3GPP TS 38.212), the total DAI value (“T-DAI”) in the DCI format represents the total number of {serving cell, PDCCH monitoring time} pairs that occur before the current PDCCH monitoring time m, associated with the DCI format, including PDSCH reception, SPS PDSCH release, or SCell sleep indication, and is updated from PDCCH monitoring time to PDCCH monitoring time. For the active DL BWP of the serving cell, if the UE is not provided with a coresetPoolIndex, or is provided with a coresetPoolIndex parameter with a value of “0” for one or more first CORESETs, and is provided with a coresetPoolIndex parameter with a value of “1” for one or more second CORESETs, and is provided with ackNackFeedbackMode = 'joint', then the total DAI value is counted for both the first and second CORESETs for the {serving cell, PDCCH monitoring time} pairs.

[0079] Please note that throughout this disclosure, the scheduling of a single PDSCH transmission (also referred to as "single PDSCH") is assumed to be for the 120kHz SCS associated with the PDSCH, while the scheduling of multiple PDSCH transmissions (also referred to as "multiple PDSCH") is assumed to be for both the 480kHz SCS and the 960kHz SCS. The maximum number of PDSCH transmissions scheduled for the 480kHz SCS is assumed to be 4, and the maximum number of PDSCH transmissions scheduled for the 960kHz SCS is assumed to be 8. However, different values ​​for the maximum number of PDSCH transmissions associated with each SCS value are also available (other SCS values, such as 240kHz, 1920kHz, etc.). The embodiments described in this disclosure are primarily considered for dynamic HARQ-ACK codebooks, i.e., type 2 HARQ-ACK codebooks, but can also be applied to other types. As mentioned above, the proposed solution may be applicable to DCIs capable of scheduling multiple PDSCH transmissions, even if, in a particular implementation, such a DCI may actually only schedule a single PDSCH transmission. Therefore, the term "multiple PDSCH scheduling via a single DCI" and similar language should be understood in a broad sense, including the case of scheduling a single PDSCH transmission via a DCI capable of scheduling multiple PDSCH transmissions.

[0080] According to an embodiment of the first solution, when the UE supports scheduling multiple PDSCHs by a single DCI and scheduling a single PDSCH by a single DCI, where the maximum number of PDSCH transmissions that a single DCI can schedule is associated with the number of parameter sets (numerology) applied to these PDSCH transmissions, the number of HARQ-ACK subcodebooks is associated with the number of parameter sets supported by the UE. For example, if the UE supports scheduling only a single PDSCH via a single DCI for a 120kHz SCS, supports scheduling up to four PDSCH transmissions via a single DCI for a 480kHz SCS, and supports scheduling up to eight PDSCH transmissions via a single DCI for a 960kHz SCS, then at least three HARQ-ACK subcodebooks can be constructed associated with the 120kHz SCS (with a maximum of one PDSCH), the 480kHz SCS (with a maximum of four PDSCH transmissions), and the 960kHz SCS (with a maximum of eight PDSCH transmissions), respectively. When HARQ-ACK feedback is determined / sent on a per-transmission-block (“TB”) basis, such a HARQ-ACK subcodebook can be called a TB-level HARQ-ACK subcodebook.

[0081] Furthermore, if a block-based transport (“CBG”) is associated with one or more parameter sets, a CBG-level HARQ-ACK subcodebook can be constructed for each such parameter set. For example, for a CBG-based transport with only a 120kHz SCS, but a TB-based transport with only 480kHz and 960kHz SCS, multiple HARQ-ACK subcodebooks can be constructed, where two CBG-level HARQ-ACK subcodebooks are associated with the 120kHz SCS, and each 480kHz and 960kHz SCS has a TB-level HARQ-ACK subcodebook. Note that in 3GPP NR, a TB can be divided into multiple CBGs. In various embodiments, a CBG can consist of multiple blocks of code (“CB”). In one example, a TB consists of multiple CBGs, and a CBG typically consists of multiple CBs. In other embodiments, a TB can consist of a single CBG and / or a CBG can consist of a single CB.

[0082] All HARQ-ACK subcodebooks are concatenated in ascending order of SCS value (or alternatively, in ascending order of the maximum number of PDSCH transmissions scheduled by a single DCI) or in descending order. The HARQ-ACK subcodebook associated with the second CBG for the 120kHz SCS is appended to the sub-HARQ-ACK subcodebook associated with the first CBG for all SCS. Notably, TB-based transmissions on the 480kHz and 960kHz SCS are considered to have only a single (first) CBG. Therefore, the concatenated codebooks will be constructed as "subcodebook 1-1 + subcodebook 2 + subcodebook 3 + subcodebook 1-2".

[0083] In an alternative implementation of the first solution, the concatenation is “subcodebook 1-1 + subcodebook 1-2 + subcodebook 2 + subcodebook 3”, that is, first concatenate all HARQ-ACK subcodebooks associated with the same SCS value, and then concatenate HARQ-ACK subcodebooks associated with other SCS values.

[0084] Figure 3 An exemplary implementation 300 according to embodiments of the present disclosure is described for multiple HARQ-ACK subcodebooks for scheduling multiple PDSCH transmissions by a single DCI, having different SCS values ​​associated with different subcodebooks. In implementation 300, the UE has PDCCH monitoring timings to receive single and / or multiple PDSCH schedulings for 5 CCs, wherein up to 8 PDSCH transmissions (with 960kHz SCS) are scheduled for PDCCH, CC1 is monitored, wherein at most 1 PDSCH transmission (including CBG transmission) (with 120kHz SCS) is scheduled for PDCCH, CC2 is monitored, wherein up to 4 PDSCH transmissions (with 480kHz SCS) are scheduled for PDCCH, CC3 is monitored, wherein up to 8 PDSCH transmissions (with 960kHz SCS) are scheduled for PDCCH, CC4 is monitored, and wherein up to 4 PDSCH transmissions (with 480kHz SCS) are scheduled for PDCCH, CC5 is monitored. In the described embodiment, it is assumed that the UE receives a first DCI that schedules 8 consecutive PDSCH transmissions for CC1, a second DCI that schedules 1 PDSCH (including two CBGs) for CC2, a third DCI that schedules 4 consecutive PDSCH transmissions for CC3, a fourth DCI that schedules 8 consecutive PDSCH transmissions for CC4, and a fifth DCI that schedules 4 consecutive PDSCH transmissions for CC5.

[0085] The UE receives (or attempts to receive) and attempts to decode the PDSCH transmissions scheduled on CC1, CC2, CC3, CC4, and CC5. In the described embodiment, two HARQ-ACK subcodebooks are constructed for 120kHz (subcodebook 1-1 for CBG-1 and subcodebook 1-2 for CBG-2), one HARQ-ACK subcodebook (subcodebook 2) is constructed for 480kHz, and one HARQ-ACK subcodebook (subcodebook 2) is constructed for 960kHz.

[0086] In addition, the UE determines the sequence of HARQ-ACK bits for scheduling PDSCH transmissions. In one embodiment, the HARQ-ACK subcodebooks are concatenated in ascending order of SCS. The UE generates a (i.e., concatenated) HARQ-ACK codebook with HARQ-ACK bits for PDSCH transmissions and reports the HARQ-ACK codebook to the RAN.

[0087] In some embodiments of the first solution, if PDSCH grouping is applied such that the codebook sizes of two different SCSs associated with two different maximum numbers of PDSCH transmissions (scheduled via a single DCI) are aligned, then a separate HARQ-ACK subcodebook is not applied to each of the SCSs (maximum number of PDSCH transmissions).

[0088] Figure 4An exemplary implementation 400 according to embodiments of the present disclosure is described for multiple HARQ-ACK subcodebooks for multiple PDSCH transmissions scheduled by a single DCI, having different SCS associated with the same subcodebook. In implementation 400, the UE has PDCCH monitoring timing to receive single and / or multiple PDSCH scheduling for 5 CCs, wherein up to 8 PDSCH transmissions (with 960kHz SCS) are scheduled for PDCCH, CC1 is monitored, wherein up to 1 PDSCH transmission (including CBG transmission) (with 120kHz SCS) is scheduled for PDCCH, CC2 is monitored, wherein up to 4 PDSCH transmissions (with 480kHz SCS) are scheduled for PDCCH, CC3 is monitored, wherein up to 8 PDSCH transmissions (with 960kHz SCS) are scheduled for PDCCH, CC4 is monitored, and CC5 is monitored, wherein up to 4 PDSCH transmissions (with 480kHz SCS) are scheduled for PDCCH. In the described embodiment, it is assumed that the UE receives a first DCI that schedules 8 consecutive PDSCH transmissions for CC1, a second DCI that schedules 1 PDSCH (including two CBGs) for CC2, a third DCI that schedules 4 consecutive PDSCH transmissions for CC3, a fourth DCI that schedules 8 consecutive PDSCH transmissions for CC4, and a fifth DCI that schedules 4 consecutive PDSCH transmissions for CC5.

[0089] The UE receives (or attempts to receive) and attempts to decode scheduled PDSCH transmissions on CC1, CC2, CC3, CC4, and CC5. In the described embodiment, two HARQ-ACK subcodebooks (i.e., subcodebook 1-1 and subcodebook 1-2) are constructed for the 120kHz SCS, but a single HARQ-ACK subcodebook (i.e., subcodebook 2) is constructed for the 480kHz SCS and 960kHz SCS.

[0090] In addition, the UE determines the sequence of HARQ-ACK bits for scheduling PDSCH transmissions. In one embodiment, the HARQ-ACK subcodebooks are concatenated in ascending order of SCS. The UE generates a (i.e., concatenated) HARQ-ACK codebook with HARQ-ACK bits for PDSCH transmissions and reports the HARQ-ACK codebook to the RAN.

[0091] PDSCH packets are applied to the 960kHz SCS such that the codebook size for this SCS is equal to the codebook size for the 480kHz SCS. Since a maximum of four PDSCH transmissions can be scheduled for the 480kHz SCS, the codebook size is 4 (for one TB). Therefore, to ensure that the codebook size associated with the 960kHz SCS is 4, two consecutive PDSCH transmissions are combined, and the corresponding HARQ-ACK bits are time-bound between those two consecutive PDSCH transmissions. Similarly, if no HARQ-ACK subcodebook is required between a single PDSCH scheduling (120kHz SCS) and multiple PDSCH schedulings (480kHz SCS and 960kHz SCS), then a packet of four PDSCH transmissions can be associated with the 480kHz SCS (assuming a maximum of four PDSCH transmissions are scheduled for the 480kHz SCS), and a packet of eight PDSCH transmissions can be associated with the 960kHz SCS (assuming a maximum of eight PDSCH transmissions are scheduled for the 960kHz SCS).

[0092] The cascading method is also applicable to any number of serving cells or component carriers (“CC”) associated with different subcarrier spacings, and is not limited to... Figure 4 The five cases used are merely examples of one approach. It should be understood that the SCS can be associated with the bandwidth portion (“BWP”) rather than with the component carrier, therefore the concatenation method is equally applicable to different BWPs.

[0093] Similarly, the concatenation method is not limited to self-scheduling of each CC (or BWP, respectively), i.e., where PDSCH resources are scheduled by DCI transmitted on the same CC / BWP as the PDSCH resources, but can also be applied to cross-carrier scheduling, i.e., where (multiple) PDSCH resources are scheduled by DCI transmitted on different CC / BWPs as the PDSCH resources. In this regard, the SCS discussed (with regard to concatenation) is associated with the SCS of the CC / BWP of (multiple) scheduled PDSCH resources, and not with the SCS associated with the CC / BWP in which the DCI used to schedule (multiple) PDSCH resources is transmitted.

[0094] In some embodiments of the first solution, the number of HARQ-ACK subcodebooks is determined by the number of SCSs configured / configurable by the UE and / or the DCI format that the UE needs to monitor. In alternative embodiments of the first solution, the number of HARQ-ACK subcodebooks is indicated to the UE via DCI and / or semi-static configuration.

[0095] In some embodiments of the first solution, the UE can be configured and / or instructed whether to apply the same codebook to all multi-PDSCH transport scheduling DCIs (where size alignment can be achieved by time-domain binding or adding NACK bits), or whether to construct different sub-HARQ ACK codebooks corresponding to DCIs that can schedule different maximum numbers of PDSCH transports.

[0096] In some embodiments of the first solution, when the UE is configured to monitor the same DCI, that DCI can be used to schedule a single PDSCH transmission or multiple PDSCH transmissions. If the UE misses a DCI, the number of NACKs to be added is based on the maximum number of PDSCH transmissions that the DCI can schedule. In this case, if the DAI is counted per DCI, the counter only increments by 1, even if multiple PDSCH transmissions may have been scheduled; if the DAI is counted per PDSCH, the counter increments by an amount equal to the maximum number of PDSCH transmissions that a single DCI can schedule.

[0097] In an alternative embodiment of the first solution, when the UE is configured to monitor the same DCI, that DCI can be used to schedule a single PDSCH or multiple PDSCHs. If the UE misses a DCI, the number of NACKs to be added is equal to 1. In this case, if the DAI is counted per DCI, the counter only increments by 1, even if multiple PDSCH transmissions may have been scheduled. If the DAI is counted per PDSCH, the counter increments by the same number as the maximum number of PDSCH transmissions that a single DCI can schedule.

[0098] In some embodiments of the first solution, such as when the UE is configured to monitor the same DCI, which can be used to schedule a single PDSCH or multiple PDSCHs (but not limited to this example), then two separate DAI fields can exist in the DCI. One DAI field corresponds to single PDSCH scheduling, while the other DAI field corresponds to multiple PDSCH scheduling.

[0099] In some embodiments of the first solution, there are two DAI fields in the DCI, with one DAI field counted per DCI and the other DAI field counted per PDSCH. In this case, if the UE misses a DCI monitoring opportunity, one DAI field increments by 1, but the other DAI field increments by the maximum number of schedulable PDSCHs or the actual number of PDSCHs transmitted by the missed DCI.

[0100] According to an embodiment of the second solution, when a single DCI can schedule multiple PDSCH transmissions, a HARQ-ACK codebook is constructed using the sequence of PDSCH transmissions, wherein the sequence / order of HARQ-ACK bits in the codebook is determined at least based on the serving cell (or CC) index and the occurrence time of the PDSCH transmission.

[0101] In one implementation of the second solution, when a single DCI can schedule multiple PDSCH transmissions, the HARQ-ACK codebook is constructed in the following sequence: first, PDSCH transmissions occurring on all CCs (serving cells) in a given time slot (transmission time interval), followed by PDSCH transmissions that may have been scheduled as multiple PDSCHs by a single DCI in subsequent time slots (TTIs).

[0102] Figure 5 An exemplary implementation 500 of HARQ-ACK codebook construction (i.e., PDSCH index) for a single HARQ-ACK codebook at the UE according to embodiments of the present disclosure is described for multiple PDSCH transmissions scheduled by a single DCI. In implementation 500, there are three CCs (denoted as "CC1", "CC2", and "CC3" respectively). CC1 schedules two PDSCH transmissions through one DCI received on CC1 in time slot 1, and CC2 schedules two PDSCH transmissions through one DCI received on CC2 in time slot 1. Furthermore, CC3 also schedules two PDSCH transmissions through one DCI received in time slot 2.

[0103] As shown in the figure, in implementation 500, PDSCH transmissions are first indexed according to the order of the CCs in time slot 1 (i.e., CC1 and CC2), then according to the order of the CCs in time slot 2 (i.e., CC1, CC2, and CC3), and so on. In this example, for all CCs, it is assumed that a single codebook of the same size is used, since the maximum number of PDSCH transmissions scheduled for a single DCI is 2. When multiple CCs have PDSCH transmissions scheduled for the same time slot, the PDSCH index for that time slot can be ordered from the lowest CC index to the highest CC index. Corresponding to the PDSCH index, HARQ-ACK bits corresponding to the PDSCH transmission are added to generate the codebook.

[0104] In another implementation of the second solution, multiple HARQ-ACK subcodebooks are constructed associated with different SCSs (or with DCIs that schedule different maximum numbers of PDSCH transmissions). The indexing of PDSCH transmissions and the corresponding HARQ-ACK construction are independent for each codebook, wherein each HARQ-ACK subcodebook is constructed in the following sequence: first, PDSCH transmissions occurring on all CCs (serving cells) in a given time slot (or transmission time interval), followed by PDSCH transmissions that may have been scheduled as multiple PDSCHs by a single DCI in subsequent time slots (TTIs).

[0105] Figure 6 An exemplary implementation 600 of HARQ-ACK codebook construction (i.e., PDSCH index) at a UE for multiple HARQ-ACK subcodebooks according to embodiments of the present disclosure is described, the multiple HARQ-ACK subcodebooks corresponding to two DCIs scheduling different numbers of PDSCH transmissions. In implementation 600, there are 4 CCs (denoted as "CC1", "CC2", "CC3" and "CC4" respectively), CC1 schedules 2 PDSCH transmissions through one DCI received on CC1 in time slot 1, CC2 schedules 4 PDSCH transmissions through one DCI received on CC2 in time slot 1, CC3 schedules 4 PDSCH transmissions through one DCI received on CC3 in time slot 1, and CC4 schedules 2 PDSCH transmissions through one DCI received on CC4 in time slot 1.

[0106] As described above, in the embodiment of the first solution, multiple sub-codebooks are used because the maximum number of PDSCH transmissions scheduled by a single DCI varies among the CCs. In implementation 600, two HARQ-ACK sub-codebooks are constructed, where the first sub-codebook is associated with PDSCH transmissions scheduled on CC1 and CC4, and the second sub-codebook is associated with PDSCH transmissions scheduled on CC2 and CC3. For each HARQ-ACK sub-codebook, when multiple CCs have PDSCH transmissions scheduled for the same time slot, the PDSCH index for that time slot can be sorted from the lowest CC index to the highest CC index. Corresponding to the PDSCH index, HARQ-ACK bits corresponding to the PDSCH transmissions are added to generate the sub-codebook.

[0107] In some embodiments of the second solution, the HARQ-ACK codebook size (or sub-codebook size) is fixed based on the maximum number of PDSCH transmissions that a single DCI can schedule. For example, if two different HARQ-ACK sub-codebooks are applied to a 480kHz SCS (where a single DCI can schedule up to 4 PDSCH transmissions) and a 980kHz SCS (where a single DCI can schedule up to 8 PDSCH transmissions), the corresponding HARQ-ACK sub-codebook sizes are 4 (for one TB / PDSCH) and 8 (for one TB / PDSCH), respectively.

[0108] In an alternative embodiment of the second solution, the same single HARQ-ACK subcodebook is applied to different SCSs, such as 480kHz and 960kHz. In these embodiments, for the 480kHz SCS, four additional (virtual) PDSCH transmissions can be assumed, and NACKs are reported accordingly for each. In other words, the HARQ-ACK subcodebook for CCs with smaller SCS values ​​can be extended by assuming virtual PDSCH transmissions (i.e., fictitious PDSCH transmissions that are known to both the sender (network) and receiver (UE) to be non-existent) for each actual PDSCH transmission (i.e., the actual transmission performed), with NACKs reported for each virtual PDSCH transmission. The extended subcodebook is the same size as the HARQ-ACK subcodebook for CCs with larger SCS values, and these two subcodebooks can be merged into a single HARQ-ACK(sub)codebook.

[0109] When the same single HARQ-ACK subcodebook is applied to different SCS values, the sequence of HARQ-ACK bits (the index of PDSCH) can be constructed as described in the above embodiments / implementations, while also considering virtual PDSCH transmissions. In some implementations of the second solution, even for a single SCS value, such as 480kHz, although a single DCI can schedule up to four PDSCH transmissions, a smaller number of PDSCH transmissions are actually scheduled, such as two. In this case, the assumption of two additional (virtual) PDSCH transmissions can be applied, and a similar method to that described above can be used to determine the PDSCH index used for HARQ-ACK codebook construction.

[0110] In one embodiment of the second solution, an additional PDSCH transmission (i.e., a virtual PDSCH transmission) is assumed to be aligned with the maximum PDSCH transmission and the corresponding HARQ-ACK codebook size, and if the additional PDSCH transmission is scheduled by a DCI received in a subsequent time slot such that the actually scheduled PDSCH transmission overlaps with the additional (virtual) assumed PDSCH in time (and on the same CC), the PDSCH index of the HARQ-ACK codebook is expanded to take into account the first DCI and the subsequently received DCI.

[0111] Figure 7 An exemplary implementation 700 of HARQ-ACK codebook construction (i.e., PDSCH index) at the UE according to embodiments of the present disclosure is described, addressing the overlap between actual and virtual assumed PDSCH transmissions in the same time slot and the same CC, and a single HARQ-ACK codebook for scheduling multiple PDSCH transmissions for a single DCI. In implementation 700, there are two CCs (denoted as "CC1" and "CC2" respectively). CC1 schedules one PDSCH transmission through a DCI received on CC1 in time slot 1, and CC2 also schedules one PDSCH transmission through another DCI received on CC2 in time slot 1. In the described embodiment, the UE assumes additional (i.e., virtual) PDSCH transmissions to align with the maximum PDSCH transmission, as described above.

[0112] As shown in the figure, for CC1 in time slot 1, an actual PDSCH transmission is scheduled, while for CC1 in time slots 2, 3, and 4, a virtual PDSCH transmission is scheduled. Similarly, for CC2, an actual PDSCH transmission is scheduled in time slot 1, while a virtual PDSCH transmission is scheduled in time slots 2, 3, and 4. However, CC1 also has one PDSCH transmission scheduled through another DCI received on CC1 in time slot 3, resulting in time overlap within the same CC.

[0113] like Figure 7 As shown, when there is overlap between actual PDSCH transmissions (i.e., scheduled by the later DCI) and virtual PDSCH transmissions (i.e., scheduled by the earlier DCI), the PDSCH index also considers the time when the scheduled DCI is received. Therefore, virtual PDSCH transmissions (i.e., scheduled by the earlier DCI) receive a lower index, while actual PDSCH transmissions (i.e., scheduled by the later DCI) receive a higher index. Essentially, if two PDSCH transmissions overlap in the same CC on a time slot (assuming the same codebook is applied to both), the index is always based on the sequence of received DCIs corresponding to these PDSCH transmissions.

[0114] Figure 8 An example implementation 800 of HARQ-ACK codebook construction (i.e., PDSCH index) at the UE is described, wherein multiple non-contiguous PDSCH transmissions are scheduled by a single DCI on at least one CC, and consecutive PDSCH transmissions are scheduled by a single DCI on at least one other CC. Figure 8 In this example, two CCs (referred to as "CC1" and "CC2") are scheduled. CC1 schedules two non-contiguous PDSCH transmissions in time slots 1 and 3, while CC2 schedules two contiguous PDSCH transmissions in time slots 1 and 2. In the described embodiment, PDSCH indexing and corresponding HARQ-ACK sorting are first performed for the PDSCH transmissions scheduled across all CCs in time slot 1, and then for the PDSCH transmissions scheduled in later time slots.

[0115] In an alternative embodiment, the PDSCH index is performed in the following order: first, multiple PDSCH transmissions scheduled on a single CC by a single DCI, followed by PDSCH transmissions scheduled on another CC within the same time slot. This implementation is advantageous when there is no assumption of separate HARQ-ACK codebooks corresponding to different SCSs (or different maximum numbers of PDSCH transmissions scheduled by a single DCI). Furthermore, avoiding any ambiguity in the PDSCH index (HARQ-ACK codebook construction) may be even more beneficial when a single DCI can schedule non-contiguous PDSCH transmissions.

[0116] Figure 9 An exemplary implementation 900 of HARQ-ACK codebook construction (i.e., PDSCH index) at the UE is described, wherein multiple non-contiguous PDSCH transmissions are scheduled by a single DCI on at least one CC, and consecutive PDSCH transmissions are scheduled by a single DCI on at least one other CC. In implementation 900, HARQ-ACK ordering is performed as follows: first, the PDSCH index of all PDSCHs scheduled by the same DCI is calculated, and then they are ordered in ascending order according to CC order. Figure 9 In this embodiment, two CCs (referred to as "CC1" and "CC2") are scheduled. CC1 schedules two non-contiguous PDSCH transmissions in time slots 1 and 3, while CC2 schedules two contiguous PDSCH transmissions in time slots 1 and 2. In the described embodiment, the PDSCH index and the corresponding HARQ-ACK ordering are first performed in ascending order of the time of the PDSCH transmissions scheduled by the DCI on CC1, and then the PDSCH index and the corresponding HARQ-ACK ordering are performed in ascending order of the time of the PDSCH transmissions scheduled by the DCI on CC2.

[0117] According to an embodiment of the third solution, for multiple PDSCHs scheduled by a single DCI, to avoid a significant increase in the HARQ-ACK codebook size, PDSCH packetization and / or time-domain HARQ-ACK binding can be applied based on the following factors:

[0118] Option 1: Priority indicator, for example, if the scheduled PDSCH transmission is of type URLLC (high priority) or eMMB (low priority), then grouping is applied only when scheduling low-priority traffic, and no grouping is applied for high-priority traffic. Essentially, high-priority PDSCH uses a larger bundle size compared to low-priority PDSCH. Alternatively, a separate HARQ-ACK subcodebook can be used for DCI scheduling of URLLC, such as DCI 2_1, which does not apply binding or applies a smaller binding size compared to the HARQ-ACK subcodebook used for low-priority traffic scheduling. In another implementation, an ascending priority value combining serving cells can be implemented to prioritize multiplexing in a separate HARQ-ACK codebook for high-priority URLLC, taking all serving cells into account. In yet another implementation, CBG-based transmissions can be implemented in ascending order of serving cells, allowing multiplexing in a separate HARQ-ACK codebook considering eMBB of all serving cells.

[0119] Option 2: The number of TRPs for multiple PDSCH transmissions is scheduled by the DCI. For example, if 4 PDSCH transmissions are scheduled for TRP1 and 4 PDSCH transmissions are scheduled for TRP2, two groups can be created, with group 1 applied to TRP1 and group 2 applied to TRP2. Based on this grouping, two separate HARQ-ACK subcodebooks can be applied. Furthermore, HARQ-ACK bindings can be applied to each group so that only 1 HARQ-ACK bit is generated per group (each PDSCH transmission is a transport block (“TB”)).

[0120] Option 3: The SCS value and the corresponding maximum number of PDSCH transmissions that can be scheduled by a single DCI. For example, if a maximum of 4 PDSCH transmissions can be scheduled by a DCI for a 480kHz SCS and a maximum of 8 PDSCH transmissions can be scheduled by a DCI for a 960kHz SCS, then the group size can be set to 2 to apply to the 960kHz SCS, so that the same codebook size is possible regardless of the SCS value (the maximum number of PDSCH transmissions that can be scheduled by the DCI).

[0121] Option 4: Any combination of Option 1, Option 2 and / or Option 3.

[0122] Figure 10User equipment apparatus 1000, according to embodiments of the present disclosure, is described for constructing dynamic HARQ-ACK codebooks for multiple PDSCHs. In various embodiments, user equipment apparatus 1000 is used to implement one or more of the solutions described above. User equipment apparatus 1000 may be an embodiment of a UE endpoint, such as remote unit 105 and / or UE 205 as described above. Furthermore, user equipment apparatus 1000 may include processor 1005, memory 1010, input device 1015, output device 1020, and transceiver 1025.

[0123] In some embodiments, input device 1015 and output device 1020 are combined into a single device, such as a touchscreen. In some embodiments, user equipment device 1000 may not include any input device 1015 and / or output device 1020. In various embodiments, user equipment device 1000 may include one or more of the following: processor 1005, memory 1010, and transceiver 1025, and may not include input device 1015 and / or output device 1020.

[0124] As shown in the figure, transceiver 1025 includes at least one transmitter 1030 and at least one receiver 1035. In some embodiments, transceiver 1025 communicates with one or more cells (or radio coverage areas) supported by one or more base station units 121. In various embodiments, transceiver 1025 may operate on unlicensed spectrum. Furthermore, transceiver 1025 may include multiple UE panels supporting one or more beams. Additionally, transceiver 1025 may support at least one network interface 1040 and / or application interface 1045. The application interface(s) 1045 may support one or more APIs. The network interface(s) 1040 may support 3GPP reference points such as Uu, N1, PC5, etc. Other network interfaces 1040 may be supported, as will be understood by those skilled in the art.

[0125] In one embodiment, processor 1005 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 1005 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, processor 1005 executes instructions stored in memory 1010 to perform the methods and routines described herein. Processor 1005 is communicatively coupled to memory 1010, input device 1015, output device 1020, and transceiver 1025.

[0126] In various embodiments, processor 1005 controls user equipment device 1000 to implement the UE behaviors described above. In some embodiments, processor 1005 may include an application processor (also referred to as a "main processor") that manages application domain and operating system ("OS") functions, and a baseband processor (also referred to as a "baseband radio processor") that manages radio functions.

[0127] In various embodiments, processor 1005 monitors and receives a first DCI via transceiver 1025, the first DCI scheduling at least one first PDSCH transmission on a first serving cell, wherein the first DCI is capable of scheduling multiple PDSCH transmissions. Furthermore, via transceiver 1025, processor 1005 monitors and receives at least one second DCI, the second DCI scheduling at least one second PDSCH transmission on a second serving cell. Based on the received DCI, processor 1005 attempts to receive the scheduled first and second PDSCH transmissions.

[0128] Processor 1005 determines HARQ-ACK feedback for the scheduled first and second PDSCH transmissions, and determines the sequence of HARQ-ACK bits corresponding to the scheduled first and second PDSCH transmissions. This determination is based at least on the serving cell index and the PDSCH occurrence time. Via transceiver 1025, processor 1005 reports the HARQ-ACK codebook corresponding to the determined HARQ-ACK feedback, which includes the HARQ-ACK bits in the determined sequence.

[0129] In some embodiments, the sequence of HARQ-ACK bits comprises multiple subsequences specific to each serving cell, each subsequence comprising HARQ-ACK bits in reception time order for each data unit transmitted for PDSCH. In these embodiments, the multiple subsequences are concatenated to form the sequence of HARQ-ACK bits. In some embodiments, the multiple subsequences are ordered from the lowest serving cell index to the highest serving cell index.

[0130] In some embodiments, the sequence of HARQ-ACK bits includes multiple subsequences specific to each time slot in which at least one PDSCH transmission is received, each subsequence including HARQ-ACK bits ordered by the serving cell index for each data element of the PDSCH transmission. In these embodiments, the multiple subsequences are concatenated to form the sequence of HARQ-ACK bits. In some embodiments, the multiple subsequences are ordered according to the reception time from the earliest received data element to the latest received data element.

[0131] In some embodiments, the determination of the sequence of HARQ-ACK bits is further based on the occurrence time of each DCI. In some embodiments, at least two PDSCH transmissions are scheduled (i.e., but not necessarily transmitted) at the same time (e.g., the same time slot or TTI) and the same serving cell, scheduled by two different DCIs monitored at different times. In such embodiments, the sequence of HARQ-ACK bits first includes the bits of the PDSCH corresponding to the earlier received DCI, and then includes the bits of the PDSCH corresponding to the later received DCI.

[0132] In some embodiments, the sequence of HARQ-ACK bits includes a negative acknowledgment for a combination of time slots and serving cell indices, for which neither the first DCI nor the second DCI schedules PDSCH transmissions. In some embodiments, processor 1005 receives, via transceiver 1025, a third DCI that schedules at least one third PDSCH transmission on a first serving cell, wherein the sequence of HARQ-ACK bits includes a negative acknowledgment bit for a specific time slot for which the first DCI does not schedule PDSCH transmissions, and additional HARQ-ACK bits for that specific time slot (i.e., the same time slot) for which the third DCI schedules third PDSCH transmissions.

[0133] In some embodiments, a first DCI schedules a first number of (maximum) PDSCH transmissions, and a second DCI schedules a second number of (maximum) PDSCH transmissions, different from the first number. In these embodiments, the HARQ-ACK codebook includes a first sub-codebook corresponding to each serving cell scheduled with the first number of PDSCH transmissions, and a second sub-codebook corresponding to each serving cell scheduled with the second number of PDSCH transmissions. In some embodiments, the processor 1005 determines the sequence of HARQ-ACK bits by determining the sequence of HARQ-ACK bits, including determining a first sequence corresponding to the first sub-codebook and a second sequence corresponding to the second sub-codebook, wherein the first sequence is determined independently of the second sequence.

[0134] In some embodiments, a first serving cell is associated with a first subcarrier spacing value, and a second serving cell is associated with a second subcarrier spacing value. In these embodiments, the HARQ-ACK codebook includes a first subcodebook corresponding to each serving cell associated with the first subcarrier spacing value, and a second subcodebook corresponding to each serving cell associated with the second subcarrier spacing value. In some embodiments, the processor 1005 determines the sequence of HARQ-ACK bits by determining the sequence of HARQ-ACK bits, including determining a first sequence corresponding to the first subcodebook and a second sequence corresponding to the second subcodebook, wherein the first sequence is determined independently of the second sequence.

[0135] In some embodiments, the HARQ-ACK codebook includes time-domain bundling of HARQ-ACK bits of the serving cell, wherein two or more HARQ-ACK bits of the serving cell are bundled into a single HARQ-ACK bit. Here, the serving cell is a first serving cell or a second serving cell.

[0136] In one embodiment, memory 1010 is a computer-readable storage medium. In some embodiments, memory 1010 includes volatile computer storage media. For example, memory 1010 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 1010 includes non-volatile computer storage media. For example, memory 1010 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 1010 includes both volatile and non-volatile computer storage media.

[0137] In some embodiments, memory 1010 stores data related to building dynamic HARQ-ACK codebooks for multiple PDSCHs. For example, memory 1010 may store various parameters, panel / beam configurations, resource allocations, strategies, etc., similar to those described above. In some embodiments, memory 1010 also stores program code and related data, such as an operating system or other controller algorithms running on user equipment device 1000.

[0138] In one embodiment, input device 1015 may include any known computer input device, including a touchscreen, button, keyboard, stylus, microphone, etc. In some embodiments, input device 1015 may be integrated with output device 1020, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, input device 1015 includes a touchscreen, enabling text input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 1015 includes two or more different devices, such as a keyboard and a touch panel.

[0139] In one embodiment, output device 1020 is designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 1020 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 1020 may include, but is not limited to, a liquid crystal display (“LCD”), a light-emitting diode (“LED”) display, an organic LED (“OLED”) display, a projector, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, output device 1020 may include a wearable display, such as a smartwatch, smart glasses, a head-up display, etc., separate from but communicatively coupled to the rest of user equipment device 1000. Furthermore, output device 1020 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0140] In some embodiments, output device 1020 includes one or more speakers for generating sound. For example, output device 1020 may generate an audible alarm or notification (e.g., a beep or buzzer). In some embodiments, output device 1020 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of output device 1020 may be integrated with input device 1015. For example, input device 1015 and output device 1020 may form a touchscreen or similar touch-sensitive display. In other embodiments, output device 1020 may be located near input device 1015.

[0141] Transceiver 1025 communicates with one or more network functions of a mobile communication network via one or more access networks. Transceiver 1025 operates under the control of processor 1005 to send and receive messages, data, and other signals. For example, processor 1005 may selectively activate transceiver 1025 (or a portion thereof) at specific times to send and receive messages.

[0142] Transceiver 1025 includes at least a transmitter 1030 and at least one receiver 1035. One or more transmitters 1030 may be used to provide UL communication signals to base station unit 121, such as the UL transmissions described herein. Similarly, one or more receivers 1035 may be used to receive DL communication signals from base station unit 121, as described herein. Although only one transmitter 1030 and one receiver 1035 are shown, user equipment device 1000 may have any suitable number of transmitters 1030 and receivers 1035. Furthermore, transmitters 1030 and receivers 1035 may be of any suitable type. In one embodiment, transceiver 1025 includes a first transmitter / receiver pair for communicating with a mobile communication network via licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network via unlicensed radio spectrum.

[0143] In some embodiments, a first transmitter / receiver pair for communicating with a mobile communication network via licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network via unlicensed radio spectrum may be combined into a single transceiver unit, such as a single chip for performing functions using both licensed and unlicensed radio spectrum capabilities. In some embodiments, the first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, some transceivers 1025, transmitters 1030, and receivers 1035 may be implemented as physically separate components that access shared hardware and / or software resources, such as network interface 1040.

[0144] In various embodiments, one or more transmitters 1030 and / or one or more receivers 1035 may be implemented and / or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-a-chip, an application-specific integrated circuit (“ASIC”), or other types of hardware components. In some embodiments, one or more transmitters 1030 and / or one or more receivers 1035 may be implemented and / or integrated into a multi-chip module. In some embodiments, other components (such as network interface 1040 or other hardware components / circuit) may be integrated with any number of transmitters 1030 and / or receivers 1035 into a single chip. In such embodiments, transmitters 1030 and receivers 1035 may be logically configured as transceivers 1025 using one or more common control signals, or configured as modular transmitters 1030 and receivers 1035 implemented in the same hardware chip or multi-chip module.

[0145] Figure 11A network apparatus 1100, which can be used to build dynamic HARQ-ACK codebooks for multiple PDSCHs according to embodiments of the present disclosure, is described. In one embodiment, the network apparatus 1100 may be an implementation of a network endpoint, such as base station unit 121 and / or RAN node 207 as described above. Furthermore, the network apparatus 1100 may include a processor 1105, a memory 1110, an input device 1115, an output device 1120, and a transceiver 1125.

[0146] In some embodiments, input device 1115 and output device 1120 are combined into a single device, such as a touchscreen. In some embodiments, network device 1100 may not include any input device 1115 and / or output device 1120. In various embodiments, network device 1100 may include one or more of processor 1105, memory 1110, and transceiver 1125, and may not include input device 1115 and / or output device 1120.

[0147] As shown in the figure, transceiver 1125 includes at least one transmitter 1130 and at least one receiver 1135. Here, transceiver 1125 communicates with one or more remote units 105. Furthermore, transceiver 1125 may support at least one network interface 1140 and / or application interface 1145. The application interface(s) 1145 may support one or more APIs. The network interface(s) 1140 may support 3GPP reference points such as Uu, N1, N2, and N3. Other network interfaces 1140 may be supported, as will be understood by those skilled in the art.

[0148] In one embodiment, processor 1105 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 1105 may be a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or similar programmable controller. In some embodiments, processor 1105 executes instructions stored in memory 1110 to perform the methods and routines described herein. Processor 1105 is communicatively coupled to memory 1110, input device 1115, output device 1120, and transceiver 1125.

[0149] In various embodiments, network device 1100 is a RAN node (e.g., gNB) communicating with one or more UEs, as described herein. In these embodiments, processor 1105 controls network device 1100 to perform the RAN behaviors described above. In some embodiments, network device 1100 may configure one or more endpoint devices with training sequences to be used during key verification. When operating as a RAN node, processor 1105 may include an application processor (also referred to as the "main processor") that manages application domain and operating system ("OS") functions, and a baseband processor (also referred to as the "baseband radio processor") that manages radio functions.

[0150] In various embodiments, processor 1105 transmits a first DCI to the UE via transceiver 1125. This first DCI schedules at least one first PDSCH transmission on a first serving cell, wherein the first DCI is capable of scheduling multiple PDSCH transmissions. Transceiver 1125 also transmits at least one second DCI to the UE via transceiver 1105. This second DCI schedules at least one second PDSCH transmission on a second serving cell and transmits the scheduled first and second PDSCH transmissions to the UE. Transceiver 1125 receives a HARQ-ACK codebook from the UE, including a sequence of HARQ-ACK bits. Processor 1105 determines a sequence of HARQ-ACK bits corresponding to the scheduled first and second PDSCH transmissions, wherein this determination is based at least on the serving cell index and the occurrence time of the PDSCH. Processor 1105 determines HARQ-ACK feedback for the scheduled first and second PDSCH transmissions, for example, based on the received HARQ-ACK bits and the determined sequence.

[0151] In some embodiments, the sequence of HARQ-ACK bits comprises multiple subsequences specific to each serving cell, each subsequence comprising HARQ-ACK bits ordered by reception time (e.g., starting from the earliest received data unit) for each data unit (e.g., TB or CBG) transmitted for PDSCH. In these embodiments, the multiple subsequences are concatenated to form the sequence of HARQ-ACK bits. In some embodiments, the multiple subsequences are ordered from the lowest serving cell index to the highest serving cell index.

[0152] In some embodiments, the sequence of HARQ-ACK bits comprises multiple subsequences specific to each time slot in which at least one PDSCH transmission is received, each subsequence comprising HARQ-ACK bits ordered by serving cell index (e.g., starting from the lowest serving cell index) for each data unit (e.g., TB or CBG) of the PDSCH transmission. In these embodiments, the multiple subsequences are concatenated to form the sequence of HARQ-ACK bits. In some embodiments, the multiple subsequences are ordered according to the reception time from the earliest received data unit to the latest received data unit.

[0153] In some embodiments, the determination of the sequence of HARQ-ACK bits is also based on the occurrence time of each DCI. In some embodiments, at least two PDSCH transmissions are scheduled (i.e., but not necessarily sent) for the same time (e.g., the same time slot and / or TTI) and the same serving cell (e.g., the same CC) by two different DCIs monitored at different times. In these embodiments, the sequence of HARQ-ACK bits first includes bits for the PDSCH of the corresponding DCI that was received earlier in time, and then includes bits for the PDSCH of the corresponding DCI that was received later in time.

[0154] In some embodiments, the sequence of HARQ-ACK bits includes a negative acknowledgment for a combination of time slots and serving cell indices, for which neither the first DCI nor the second DCI schedules PDSCH transmissions. In some embodiments, processor 1105 controls transceiver 1125 to transmit a third DCI that schedules at least one third PDSCH transmission on the first serving cell. In these embodiments, the sequence of HARQ-ACK bits includes a negative acknowledgment for a specific time slot for which the first DCI does not schedule PDSCH transmissions, and additional HARQ-ACK bits for that specific time slot (i.e., the same time slot) for which the third DCI schedules third PDSCH transmissions.

[0155] In some embodiments, the first DCI can schedule up to a first number (maximum) of PDSCH transmissions, and the second DCI can schedule up to a second number (maximum) of PDSCH transmissions, the second number being different from the first number. In these embodiments, the HARQ-ACK codebook includes a first sub-codebook corresponding to each serving cell that schedules the first number of PDSCH transmissions, and a second sub-codebook corresponding to each serving cell that schedules the second number of PDSCH transmissions. In some embodiments, the processor 1105 determines the sequence of HARQ-ACK bits by determining a first sequence corresponding to the first sub-codebook and a second sequence corresponding to the second sub-codebook, wherein the first sequence is determined independently of the second sequence (i.e., by applying sorting / indexing rules without considering the PDSCH occurrence time, serving cell index, etc., associated with other sequences).

[0156] In some embodiments, a first serving cell is associated with a first subcarrier spacing value, and a second serving cell is associated with a second subcarrier spacing value. The HARQ-ACK codebook includes a first subcodebook corresponding to each serving cell associated with the first subcarrier spacing value, and a second subcodebook corresponding to each serving cell associated with the second subcarrier spacing value. In some embodiments, the processor 1105 determines the sequence of HARQ-ACK bits by: determining a first sequence corresponding to the first subcodebook and a second sequence corresponding to the second subcodebook, wherein the first sequence is determined independently of the second sequence (i.e., by applying sorting / indexing rules without considering the PDSCH occurrence time, serving cell index, etc., associated with other sequences).

[0157] In some embodiments, the HARQ-ACK codebook includes time-domain bundling of HARQ-ACK bits of the serving cell, wherein two or more HARQ-ACK bits of the serving cell are bundled into a single HARQ-ACK bit. Here, the serving cell is a first serving cell or a second serving cell.

[0158] In one embodiment, memory 1110 is a computer-readable storage medium. In some embodiments, memory 1110 includes volatile computer storage media. For example, memory 1110 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 1110 includes non-volatile computer storage media. For example, memory 1110 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 1110 includes both volatile and non-volatile computer storage media.

[0159] In some embodiments, memory 1110 stores data related to building dynamic HARQ-ACK codebooks for multiple PDSCHs. For example, memory 1110 may store parameters, configurations, resource allocations, policies, etc., as described above. In some embodiments, memory 1110 also stores program code and related data, such as operating system or other controller algorithms running on network device 1100.

[0160] In one embodiment, input device 1115 may include any known computer input device, including a touchscreen, button, keyboard, stylus, microphone, etc. In some embodiments, input device 1115 may be integrated with output device 1120, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, input device 1115 includes a touchscreen, enabling text input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 1115 includes two or more different devices, such as a keyboard and a touchscreen.

[0161] In one embodiment, output device 1120 is designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 1120 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 1120 may include, but is not limited to, LCD displays, LED displays, OLED displays, projectors, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, output device 1120 may include a wearable display, such as a smartwatch, smart glasses, head-up display, etc., separate from but communicatively coupled to the rest of network device 1100. Furthermore, output device 1120 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0162] In some embodiments, output device 1120 includes one or more speakers for generating sound. For example, output device 1120 may generate an auditory alarm or notification (e.g., a buzzer or ringtone). In some embodiments, output device 1120 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of output device 1120 may be integrated with input device 1115. For example, input device 1115 and output device 1120 may form a touchscreen or similar touch-sensitive display. In other embodiments, output device 1120 may be located near input device 1115.

[0163] Transceiver 1125 includes at least a transmitter 1130 and at least one receiver 1135. One or more transmitters 1130 can be used to communicate with the UE, as described herein. Similarly, one or more receivers 1135 can be used to communicate with network functions in a Public Land Mobile Network (“PLMN”) and / or RAN, as described herein. Although only one transmitter 1130 and one receiver 1135 are shown, network device 1100 can have any suitable number of transmitters 1130 and receivers 1135. Furthermore, the transmitter(s) 1130 and receiver(s) 1135 can be of any suitable type.

[0164] Figure 12 An embodiment of a method 900 for constructing a dynamic HARQ-ACK codebook for multiple PDSCHs, according to embodiments of the present disclosure, is described. In various embodiments, method 900 is performed by an endpoint device, such as remote unit 105, UE 205, and / or user equipment device 1000, as described above. In some embodiments, method 1200 is performed by a processor, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0165] Method 1200 begins and receives 1205 a first DCI, which schedules at least one first PDSCH transmission on a first serving cell, wherein the first DCI is capable of scheduling multiple PDSCH transmissions. Method 1200 includes receiving 1210 at least one second DCI, which schedules at least one second PDSCH transmission on a second serving cell. Method 1200 includes determining 1215 HARQ-ACK feedback for the scheduled first and second PDSCH transmissions. Method 1200 includes determining 1220 a sequence of HARQ-ACK bits corresponding to the scheduled first and second PDSCH transmissions, wherein the sequence is determined at least based on the serving cell index and the occurrence time of the PDSCH. Method 1200 includes reporting 1225 a HARQ-ACK codebook corresponding to the determined HARQ-ACK feedback, wherein the HARQ-ACK codebook includes HARQ-ACK bits according to the determined sequence. Method 1200 ends.

[0166] Figure 13 An embodiment of a method 1300 for constructing a dynamic HARQ-ACK codebook for multiple PDSCHs, according to embodiments of the present disclosure, is described. In various embodiments, method 1300 is performed by a network device, such as basic unit 121, RAN node 207, and / or network device 1100, as described above. In some embodiments, method 1300 is performed by a processor, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0167] Method 1300 begins and transmits 1305 a first DCI, which schedules at least one first PDSCH transmission on a first serving cell, wherein the first DCI is capable of scheduling multiple PDSCH transmissions. Method 1300 includes transmitting 1310 at least one second DCI, which schedules at least one second PDSCH transmission on a second serving cell. Method 1300 includes transmitting 1315 the scheduled first and second PDSCH transmissions. Method 1300 includes receiving 1320 a HARQ-ACK codebook including multiple HARQ-ACK bits. Method 1300 includes determining 1325 a sequence of HARQ-ACK bits corresponding to the scheduled first and second PDSCH transmissions, wherein this determination is based at least on the serving cell index and the occurrence time of the PDSCH. Method 1300 includes determining 1330 HARQ-ACK feedback for the scheduled first and second PDSCH transmissions based on the determined sequence. Method 1300 ends.

[0168] According to embodiments of this disclosure, a first apparatus for constructing a dynamic HARQ-ACK codebook for multiple PDSCHs is disclosed herein. The first apparatus may be implemented by an endpoint device, such as remote unit 105, UE 205, and / or the aforementioned user equipment apparatus 1000. The first device includes a processor coupled to a transceiver configured to communicate with a mobile communication network, the processor being configured to cause the first device to: A) monitor and receive a first DCI that schedules at least one first PDSCH transmission on a first serving cell, wherein the first DCI is capable of scheduling multiple PDSCH transmissions; B) monitor and receive at least one second DCI that schedules at least one second PDSCH transmission on a second serving cell; C) determine a hybrid automatic repeat request acknowledgment (“HARQ-ACK”) feedback for the scheduled first PDSCH transmission and the second PDSCH transmission; D) determine a sequence of HARQ-ACK bits corresponding to the scheduled first PDSCH transmission and the second PDSCH transmission, wherein the determination is based at least on the serving cell index and the occurrence time of the PDSCH; and E) report a HARQ-ACK codebook corresponding to the determined HARQ-ACK feedback, the HARQ-ACK codebook including HARQ-ACK bits in the determined sequence.

[0169] In some embodiments, the sequence of HARQ-ACK bits comprises multiple subsequences specific to each serving cell, each subsequence comprising HARQ-ACK bits ordered by reception time for each data unit transmitted for the PDSCH. In these embodiments, the multiple subsequences are concatenated to form the sequence of HARQ-ACK bits. In some embodiments, the multiple subsequences are ordered from the lowest serving cell index to the highest serving cell index.

[0170] In some embodiments, the sequence of HARQ-ACK bits includes multiple subsequences specific to each time slot in which at least one PDSCH transmission is received, each subsequence including HARQ-ACK bits ordered by the serving cell index for each data element of the PDSCH transmission. In these embodiments, the multiple subsequences are concatenated to form the sequence of HARQ-ACK bits. In some embodiments, the multiple subsequences are ordered according to the reception time from the earliest received data element to the latest received data element.

[0171] In some embodiments, the determination of the sequence of HARQ-ACK bits is further based on the occurrence time of each DCI. In some embodiments, for the same time (e.g., the same time slot or TTI) and the same serving cell, at least two PDSCH transmissions are scheduled (i.e., but not necessarily transmitted) by two different DCIs monitored at different times. In these embodiments, the sequence of HARQ-ACK bits first includes bits for the PDSCH whose corresponding DCI was received earlier in time, followed by bits for the PDSCH whose corresponding DCI was received later in time.

[0172] In some embodiments, the sequence of HARQ-ACK bits includes a negative acknowledgment for a combination of time slots and serving cell indices, for which neither the first DCI nor the second DCI schedules PDSCH transmissions. In some embodiments, the processor is further configured to cause the first device to receive a third DCI that schedules at least one third PDSCH transmission on the first serving cell, wherein the sequence of HARQ-ACK bits includes a negative acknowledgment bit for a specific time slot for which the first DCI does not schedule PDSCH transmissions, and additional HARQ-ACK bits for that specific time slot (i.e., the same time slot) for which the third DCI schedules third PDSCH transmissions.

[0173] In some embodiments, a first DCI schedules a first number of (maximum) PDSCH transmissions, and a second DCI schedules a second number of (maximum) PDSCH transmissions, different from the first number. In these embodiments, the HARQ-ACK codebook includes a first sub-codebook corresponding to each serving cell that schedules the first number of PDSCH transmissions, and a second sub-codebook corresponding to each serving cell that schedules the second number of PDSCH transmissions. In some embodiments, to determine the sequence of HARQ-ACK bits, the processor is further configured to: determine the sequence of HARQ-ACK bits includes determining a first sequence corresponding to the first sub-codebook and a second sequence corresponding to the second sub-codebook, wherein the first sequence is determined independently of the second sequence.

[0174] In some embodiments, a first serving cell is associated with a first subcarrier spacing value, and a second serving cell is associated with a second subcarrier spacing value. In these embodiments, the HARQ-ACK codebook includes a first subcodebook corresponding to each serving cell associated with the first subcarrier spacing value and a second subcodebook corresponding to each serving cell associated with the second subcarrier spacing value. In some embodiments, the processor is further configured to: determine the sequence of HARQ-ACK bits includes: determining a first sequence corresponding to the first subcodebook and a second sequence corresponding to the second subcodebook, wherein the first sequence is determined independently of the second sequence.

[0175] In some embodiments, the HARQ-ACK codebook includes time-domain bundling of HARQ-ACK bits of the serving cell, wherein two or more HARQ-ACK bits of the serving cell are bundled into a single HARQ-ACK bit. Here, the serving cell is a first serving cell or a second serving cell.

[0176] According to embodiments of this disclosure, a first method for constructing a dynamic HARQ-ACK codebook for multiple PDSCHs is disclosed herein. The first method may be implemented by an endpoint device, such as remote unit 105, UE 205, and / or the aforementioned user equipment device 1000. The first method includes receiving a first DCI, which schedules at least one first PDSCH transmission on a first serving cell, wherein the first DCI is capable of scheduling multiple PDSCH transmissions. The first method includes receiving at least one second DCI, which schedules at least one second PDSCH transmission on a second serving cell, and determining HARQ-ACK feedback for the scheduled first and second PDSCH transmissions. The first method includes determining a sequence of HARQ-ACK bits corresponding to the scheduled first and second PDSCH transmissions, and reporting a HARQ-ACK codebook corresponding to the determined HARQ-ACK feedback, the HARQ-ACK codebook including HARQ-ACK bits according to the determined sequence, the determination of which is based at least on the serving cell index and the occurrence time of the PDSCH.

[0177] In some embodiments, the sequence of HARQ-ACK bits comprises multiple subsequences specific to each serving cell, each subsequence comprising HARQ-ACK bits in reception time order for each data unit transmitted for PDSCH. In these embodiments, the multiple subsequences are concatenated to form the sequence of HARQ-ACK bits. In some embodiments, the multiple subsequences are ordered from the lowest serving cell index to the highest serving cell index.

[0178] In some embodiments, the sequence of HARQ-ACK bits includes multiple subsequences specific to each time slot in which at least one PDSCH transmission is received, each subsequence including HARQ-ACK bits ordered by the serving cell index for each data element of the PDSCH transmission. In these embodiments, the multiple subsequences are concatenated to form the sequence of HARQ-ACK bits. In some embodiments, the multiple subsequences are ordered according to the reception time from the earliest received data element to the latest received data element.

[0179] In some embodiments, the determination of the sequence of HARQ-ACK bits is further based on the occurrence time of each DCI. In some embodiments, for the same time (e.g., the same time slot or TTI) and the same serving cell, at least two PDSCH transmissions are scheduled (i.e., but not necessarily transmitted) by two different DCIs monitored at different times. In these embodiments, the sequence of HARQ-ACK bits first includes bits for the PDSCH whose corresponding DCI was received earlier in time, followed by bits for the PDSCH whose corresponding DCI was received later in time.

[0180] In some embodiments, the sequence of HARQ-ACK bits includes a negative acknowledgment for a combination of time slots and serving cell indices, for which neither the first DCI nor the second DCI schedules PDSCH transmissions. In some embodiments, the first method further includes receiving a third DCI that schedules at least one third PDSCH transmission on a first serving cell, wherein the sequence of HARQ-ACK bits includes a negative acknowledgment bit for a specific time slot for which the first DCI does not schedule PDSCH transmissions, and additional HARQ-ACK bits for that specific time slot (i.e., the same time slot) for which the third DCI schedules third PDSCH transmissions.

[0181] In some embodiments, a first DCI schedules a first number of (maximum) PDSCH transmissions, and a second DCI schedules a second number of (maximum) PDSCH transmissions, different from the first number. In these embodiments, the HARQ-ACK codebook includes a first sub-codebook corresponding to each serving cell scheduling the first number of PDSCH transmissions, and a second sub-codebook corresponding to each serving cell scheduling the second number of PDSCH transmissions. In some embodiments, determining the sequence of HARQ-ACK bits includes determining a first sequence corresponding to the first sub-codebook and a second sequence corresponding to the second sub-codebook, wherein the first sequence is determined independently of the second sequence.

[0182] In some embodiments, a first serving cell is associated with a first subcarrier spacing value, and a second serving cell is associated with a second subcarrier spacing value. In these embodiments, the HARQ-ACK codebook includes a first subcodebook corresponding to each serving cell associated with the first subcarrier spacing value and a second subcodebook corresponding to each serving cell associated with the second subcarrier spacing value. In some embodiments, determining the sequence of HARQ-ACK bits includes determining a first sequence corresponding to the first subcodebook and a second sequence corresponding to the second subcodebook, wherein the first sequence is determined independently of the second sequence.

[0183] In some embodiments, the HARQ-ACK codebook includes time-domain bundling of HARQ-ACK bits of the serving cell, wherein two or more HARQ-ACK bits of the serving cell are bundled into a single HARQ-ACK bit. Here, the serving cell is a first serving cell or a second serving cell.

[0184] According to embodiments of this disclosure, a second apparatus for constructing a dynamic HARQ-ACK codebook for multiple PDSCHs is disclosed herein. The second apparatus may be implemented by network devices such as base station unit 121, RAN node 207, and / or the aforementioned network device 1100. The second apparatus includes a processor coupled to a transceiver configured to communicate with a UE network, the processor being configured to cause the second apparatus to: A) send to the UE a first DCI scheduling at least one first PDSCH transmission on a first serving cell, wherein the first DCI is capable of scheduling multiple PDSCH transmissions; B) send to the UE at least one second DCI scheduling at least one second PDSCH transmission on a second serving cell; C) send to the UE the scheduled first PDSCH transmission and second PDSCH transmission; D) receive from the UE a HARQ-ACK codebook including multiple HARQ-ACK bits; E) determine a sequence of HARQ-ACK bits corresponding to the scheduled first PDSCH transmission and second PDSCH transmission, wherein the determination is based at least on a serving cell index and the occurrence time of the PDSCH; and F) determine HARQ-ACK feedback for the scheduled first PDSCH transmission and second PDSCH transmission based on the determined sequence.

[0185] In some embodiments, the sequence of HARQ-ACK bits comprises multiple subsequences specific to each serving cell, each subsequence comprising HARQ-ACK bits ordered by reception time for each data unit transmitted for the PDSCH. In these embodiments, the multiple subsequences are concatenated to form the sequence of HARQ-ACK bits. In some embodiments, the multiple subsequences are ordered from the lowest serving cell index to the highest serving cell index.

[0186] In some embodiments, the sequence of HARQ-ACK bits includes multiple subsequences specific to each time slot in which at least one PDSCH transmission is received, each subsequence including HARQ-ACK bits ordered by the serving cell index for each data element of the PDSCH transmission. In these embodiments, the multiple subsequences are concatenated to form the sequence of HARQ-ACK bits. In some embodiments, the multiple subsequences are ordered according to the reception time from the earliest received data element to the latest received data element.

[0187] In some embodiments, the determination of the sequence of HARQ-ACK bits is also based on the occurrence time of each DCI. In some embodiments, for the same time (e.g., the same time slot or TTI) and the same serving cell (e.g., the same CC), at least two PDSCH transmissions are scheduled (i.e., but not necessarily transmitted) by two different DCIs monitored at different times. In these embodiments, the sequence of HARQ-ACK bits first includes bits for the PDSCH whose corresponding DCI was received earlier in time, followed by bits for the PDSCH whose corresponding DCI was received later in time.

[0188] In some embodiments, the sequence of HARQ-ACK bits includes a negative acknowledgment for a combination of time slots and serving cell indices, for which neither the first DCI nor the second DCI schedules PDSCH transmissions. In some embodiments, the processor is further configured to cause the second means to send a third DCI that schedules at least one third PDSCH transmission on the first serving cell. In these embodiments, the sequence of HARQ-ACK bits includes a negative acknowledgment bit for a specific time slot for which the first DCI does not schedule PDSCH transmissions, and additional HARQ-ACK bits for that specific time slot (i.e., the same time slot) for which the third DCI schedules third PDSCH transmissions.

[0189] In some embodiments, a first DCI schedules a first number (maximum) of PDSCH transmissions, and a second DCI schedules a second number (maximum) of PDSCH transmissions, different from the first number. In these embodiments, the HARQ-ACK codebook includes a first sub-codebook corresponding to each serving cell scheduling the first number of PDSCH transmissions, and a second sub-codebook corresponding to each serving cell scheduling the second number of PDSCH transmissions. In some embodiments, to determine the sequence of HARQ-ACK bits, the processor is further configured to: determine the sequence of HARQ-ACK bits includes determining a first sequence corresponding to the first sub-codebook and a second sequence corresponding to the second sub-codebook, wherein the first sequence is determined independently of the second sequence.

[0190] In some embodiments, a first serving cell is associated with a first subcarrier spacing value, and a second serving cell is associated with a second subcarrier spacing value, wherein the HARQ-ACK codebook includes a first subcodebook corresponding to each serving cell associated with the first subcarrier spacing value, and a second subcodebook corresponding to each serving cell associated with the second subcarrier spacing value. In some embodiments, to determine the sequence of HARQ-ACK bits, the processor is further configured to: determine the sequence of HARQ-ACK bits includes determining a first sequence corresponding to the first subcodebook and a second sequence corresponding to the second subcodebook, wherein the first sequence is determined independently of the second sequence.

[0191] In some embodiments, the HARQ-ACK codebook includes time-domain bundling of HARQ-ACK bits of the serving cell, wherein two or more HARQ-ACK bits of the serving cell are bundled into a single HARQ-ACK bit. Here, the serving cell is a first serving cell or a second serving cell.

[0192] According to embodiments of this disclosure, a second method for constructing a dynamic HARQ-ACK codebook for multiple PDSCHs is disclosed herein. The second method can be performed by a network device, such as the basic unit 121, RAN node 207, and / or network device 1100 described above. The second method includes transmitting a first DCI that schedules at least one first PDSCH transmission on a first serving cell, wherein the first DCI is capable of scheduling multiple PDSCH transmissions. The second method includes transmitting at least one second DCI that schedules at least one second PDSCH transmission on a second serving cell, and transmitting the scheduled first PDSCH transmission and the second PDSCH transmission. The second method includes receiving a HARQ-ACK codebook comprising multiple HARQ-ACK bits, and determining a sequence of HARQ-ACK bits corresponding to the scheduled first PDSCH transmission and the second PDSCH transmission, wherein the determination is based at least on the serving cell index and the occurrence time of the PDSCH. The second method includes determining HARQ-ACK feedback for the scheduled first PDSCH transmission and the second PDSCH transmission based on the determined sequence.

[0193] In some embodiments, the sequence of HARQ-ACK bits comprises multiple subsequences specific to each serving cell, each subsequence comprising HARQ-ACK bits in reception time order for each data unit transmitted for PDSCH. In these embodiments, the multiple subsequences are concatenated to form the sequence of HARQ-ACK bits. In some embodiments, the multiple subsequences are ordered from the lowest serving cell index to the highest serving cell index.

[0194] In some embodiments, the sequence of HARQ-ACK bits includes multiple subsequences specific to each time slot in which at least one PDSCH transmission is received, each subsequence including HARQ-ACK bits ordered by the serving cell index for each data element of the PDSCH transmission. In these embodiments, the multiple subsequences are concatenated to form the sequence of HARQ-ACK bits. In some embodiments, the multiple subsequences are ordered according to the reception time from the earliest received data element to the latest received data element.

[0195] In some embodiments, the determination of the sequence of HARQ-ACK bits is further based on the occurrence time of each DCI. In some embodiments, for the same time (e.g., the same time slot or TTI) and the same serving cell (e.g., the same CC), at least two PDSCH transmissions are scheduled (i.e., but not necessarily transmitted) by two different DCIs monitored at different times. In these embodiments, the sequence of HARQ-ACK bits first includes bits for the PDSCH whose corresponding DCI was received earlier in time, followed by bits for the PDSCH whose corresponding DCI was received later in time.

[0196] In some embodiments, the sequence of HARQ-ACK bits includes a negative acknowledgment for a combination of time slots and serving cell indices, for which neither the first DCI nor the second DCI schedules PDSCH transmissions. In some embodiments, the second method includes sending a third DCI that schedules at least one third PDSCH transmission on the first serving cell. In these embodiments, the sequence of HARQ-ACK bits includes a negative acknowledgment bit for a specific time slot for which the first DCI does not schedule PDSCH transmissions, and additional HARQ-ACK bits for that specific time slot (i.e., the same time slot) for which the third DCI schedules third PDSCH transmissions.

[0197] In some embodiments, a first DCI schedules a first number of (maximum) PDSCH transmissions, and a second DCI schedules a second number of (maximum) PDSCH transmissions, different from the first number. In these embodiments, the HARQ-ACK codebook includes a first sub-codebook corresponding to each serving cell scheduling the first number of PDSCH transmissions, and a second sub-codebook corresponding to each serving cell scheduling the second number of PDSCH transmissions. In some embodiments, determining the sequence of HARQ-ACK bits includes determining a first sequence corresponding to the first sub-codebook and a second sequence corresponding to the second sub-codebook, wherein the first sequence is determined independently of the second sequence.

[0198] In some embodiments, a first serving cell is associated with a first subcarrier spacing value, and a second serving cell is associated with a second subcarrier spacing value, wherein the HARQ-ACK codebook includes a first subcodebook corresponding to each serving cell associated with the first subcarrier spacing value and a second subcodebook corresponding to each serving cell associated with the second subcarrier spacing value. In some embodiments, determining the sequence of HARQ-ACK bits includes determining a first sequence corresponding to the first subcodebook and a second sequence corresponding to the second subcodebook, wherein the first sequence is determined independently of the second sequence.

[0199] In some embodiments, the HARQ-ACK codebook includes time-domain bundling of HARQ-ACK bits of the serving cell, wherein two or more HARQ-ACK bits of the serving cell are bundled into a single HARQ-ACK bit. Here, the serving cell is a first serving cell or a second serving cell.

[0200] The embodiments may be practiced in other specific forms. The described embodiments are to be considered illustrative rather than restrictive in all respects. Therefore, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All modifications within the meaning and equivalent scope of the claims should be included within their scope.

Claims

1. A method at a UE device, the method comprising: Receive first downlink control information (DCI), the first downlink control information (DCI) schedules at least one first physical downlink shared channel (PDSCH) transmission on the first serving cell, wherein the first DCI is capable of scheduling multiple PDSCH transmissions; Receive at least one second DCI, the second DCI scheduling at least one second PDSCH transmission on the second serving cell; For the first PDSCH transmission and the second PDSCH transmission scheduled, determine the Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback; Determine a sequence of HARQ-ACK bits corresponding to the scheduled first PDSCH transmission and the second PDSCH transmission for the dynamic HARQ-ACK codebook, wherein the determination is based at least on the serving cell index and the occurrence time of the PDSCH. as well as The report corresponds to the dynamic HARQ-ACK codebook that has been determined as HARQ-ACK feedback, the dynamic HARQ-ACK codebook comprising the HARQ-ACK bits according to the determined sequence.

2. The method of claim 1, wherein the sequence of HARQ-ACK bits comprises a plurality of subsequences specific to each serving cell, each subsequence comprising HARQ-ACK bits in reception time order for each data unit transmitted via PDSCH, wherein the plurality of subsequences are concatenated to form the sequence of HARQ-ACK bits.

3. The method of claim 2, wherein the plurality of subsequences are ordered from the lowest serving cell index to the highest serving cell index.

4. The method of claim 1, wherein the sequence of HARQ-ACK bits comprises a plurality of subsequences specific to each time slot in which at least one PDSCH transmission is received, each subsequence comprising HARQ-ACK bits ordered by serving cell index for each data unit of the PDSCH transmission, wherein the plurality of subsequences are concatenated to form the sequence of HARQ-ACK bits.

5. The method of claim 4, wherein the plurality of subsequences are ordered according to the reception time from the earliest received data unit to the latest received data unit.

6. The method of claim 1, wherein the determination of the sequence of HARQ-ACK bits is further based on the occurrence time of each DCI.

7. The method of claim 1, wherein the sequence of HARQ-ACK bits includes a negative acknowledgment for a combination of time slots and serving cell indices, and neither the first DCI nor the second DCI schedules PDSCH transmissions for the combination of time slots and serving cell indices.

8. The method of claim 7, further comprising: Receive and schedule the third DCI transmitted by the third PDSCH on the first serving cell. The sequence of HARQ-ACK bits includes: For a negative acknowledgment bit in a specific time slot, the first DCI did not schedule PDSCH transmission for that specific time slot, and For the additional HARQ-ACK bits of the specific time slot, the third DCI schedules the third PDSCH transmission for the specific time slot.

9. The method of claim 1, wherein the first DCI schedules a first number of PDSCH transmissions, and the second DCI schedules a second number of PDSCH transmissions different from the first number, wherein the dynamic HARQ-ACK codebook comprises: A first subcodebook corresponding to each serving cell that schedules the first number of PDSCH transmissions, and a second subcodebook corresponding to each serving cell that schedules the second number of PDSCH transmissions.

10. The method of claim 9, wherein determining the sequence of HARQ-ACK bits comprises: A first sequence corresponding to the first subcodebook and a second sequence corresponding to the second subcodebook are determined, wherein the first sequence is determined independently of the second sequence.

11. The method of claim 1, wherein the first serving cell is associated with a first subcarrier spacing value, and the second serving cell is associated with a second subcarrier spacing value, wherein the dynamic HARQ-ACK codebook comprises: A first subcodebook for each serving cell associated with the first subcarrier spacing value, and a second subcodebook for each serving cell associated with the second subcarrier spacing value.

12. The method of claim 11, wherein determining the sequence of HARQ-ACK bits comprises: A first sequence corresponding to the first subcodebook and a second sequence corresponding to the second subcodebook are determined, wherein the first sequence is determined independently of the second sequence.

13. The method of claim 1, wherein the dynamic HARQ-ACK codebook comprises time-domain bundling of HARQ-ACK bits of a serving cell, wherein two or more HARQ-ACK bits of the serving cell are bundled into a single HARQ-ACK bit, and wherein the serving cell is selected from either the first serving cell or the second serving cell.

14. A user equipment apparatus, comprising: The transceiver is configured to communicate with a second endpoint via a wireless channel; as well as A processor coupled to the transceiver, the processor being configured to cause the device to: The first downlink control information (DCI) is received, which schedules at least one first physical downlink shared channel (PDSCH) transmission on the first serving cell, wherein the first DCI is capable of scheduling multiple PDSCH transmissions. Receive at least one second DCI, the second DCI scheduling at least one second PDSCH transmission on the second serving cell; For the first and second PDSCH transmissions scheduled for the dynamic HARQ-ACK codebook, determine the Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback; Determine the sequence of HARQ-ACK bits corresponding to the scheduled first PDSCH transmission and the second PDSCH transmission, wherein the determination is based at least on the serving cell index and the occurrence time of the PDSCH; as well as The report corresponds to the dynamic HARQ-ACK codebook that has been determined as HARQ-ACK feedback, the dynamic HARQ-ACK codebook comprising HARQ-ACK bits according to the determined sequence.

15. A network device, comprising: transceiver; as well as A processor coupled to the transceiver, the processor being configured to cause the device to: Sending first downlink control information (DCI) to user equipment (UE), the first downlink control information (DCI) schedules at least one first physical downlink shared channel (PDSCH) transmission on the first serving cell, wherein the first DCI is capable of scheduling multiple PDSCH transmissions; Send at least one second DCI to the UE, wherein the second DCI schedules at least one second PDSCH transmission on the second serving cell; Send the scheduled first PDSCH transmission and second PDSCH transmission to the UE; Receive from the UE a dynamically hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook containing multiple HARQ-ACK bits; Determine the sequence of HARQ-ACK bits corresponding to the scheduled first PDSCH transmission and the second PDSCH transmission, wherein the determination is based at least on the serving cell index and the occurrence time of the PDSCH; as well as Based on the determined sequence, HARQ-ACK feedback is determined for the scheduled first PDSCH transmission and the second PDSCH transmission.

Images