EP4014382A1 - Semipersistent scheduling hybrid automatic repeat request codebook design - Google Patents

Abstract

A method and wireless device for codebook construction are disclosed. According to one aspect, a method includes constructing a codebook by combining a first codebook and a second codebook, the first codebook being configured for hybrid automatic repeat request (HARQ) acknowledgment (ACK) response of dynamically scheduled physical shared channels and the second codebook being configured for HARQ-ACK response of semi-persistently scheduled (SPS) physical shared channels.

Description

SEMIPERSISTENT SCHEDULING HYBRID AUTOMATIC REPEAT REQUEST

CODEBOOK DESIGN

FIELD

[0001] The present disclosure relates to wireless communications, and in particular, to semipersi stent scheduling (SPS), hybrid automatic repeat request (HARQ) codebook design for wireless communications.

INTRODUCTION

[0002] Currently, according to the Release 15 (Rel-15) specification of the Third Generation Partnership Project (3 GPP), for a given wireless device (WD), if two hybrid automatic repeat request (HARQ) processes have overlapping timelines, the behavior of the WD is clearly defined, e.g., in 3GPP Technical Standard (TS) 38.214, section 5.1. According to TS 38.214, section 5.1:

• “For any two HARQ process IDs in a given scheduled cell, if the UE [WD] is scheduled to start receiving a first PDSCH starting in symbol j by a PDCCH ending in symbol i, the WD is not expected to be scheduled to receive a PDSCH starting earlier than the ending symbol of the first PDSCH with a PDCCH that does not end earlier than symbol i,” where PDSCH is the physical downlink shared channel and PDCCH is the physical downlink control channel. This is referred to herein as “condition 1” or “the legacy rule”.

[0003] Release 15 considers single stream SPS and does not define a HARQ design if there are two or more SPS streams or combinations between SPS and dynamic PDSCHs.

[0004] For 3GPP Release 16 (Rel-16), or for future Releases such as Release 17, some related scheduling and out of order (OOO) HARQ proposals and observations have been discussed. In Rel-16, there may be multiple SPS for which HARQ construction is undefined. [0005] Further, the legacy rule, which is applied to dynamic PDSCHs in 3GPP Rel-15, cannot be utilized as such for detection rules involving the HARQ ACK response to PDSCHs that are semi-persistently scheduled. According to 3GPP TS 38.214, section 5.1, if HARQ processes are not in order, then a scheduling error is considered to have occurred. See FIG. 1. However, this scenario is limited to dynamic PDSCHs in 3GPP Rel-15.

SUMMARY

[0006] Some embodiments advantageously provide methods, and wireless devices for semipersi stent scheduling (SPS) hybrid automatic repeat request (HARQ) codebook design.

[0007] In some embodiments, a HARQ codebook construction involves multiple SPSs and possibly addresses OOO conditions. It is noted that the discussion herein concerning downlink applications of embodiments herein may be applied to uplink SPS configured grants (CG).

[0008] According to one aspect, a method implemented in a wireless device is provided. The method includes constructing a codebook by combining at least a first codebook and a second codebook, the first codebook being configured for hybrid automatic repeat request (HARQ) acknowledgment (ACK) response of dynamically scheduled physical shared channels and the second codebook being configured for HARQ- ACK response of semi-persistently scheduled (SPS) physical shared channels.

[0009] According to one aspect, a wireless device is provided. The wireless device includes a radio interface and processing circuitry configured construct a codebook by combining at least a first codebook and a second codebook, the first codebook being configured for hybrid automatic repeat request (HARQ) acknowledgment (ACK) response of dynamically scheduled physical shared channels and the second codebook being configured for HARQ-ACK response of semi- persistently scheduled (SPS) physical shared channels.

[0010] The embodiments provide solutions for HARQ-ACK constructions for scenarios with SPS streams and dynamic scheduling of PDSCH, which would otherwise be undefined. The SPS streams may include multiple SPS streams. The embodiments also provide criterions for constructing the codebook or codebooks.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0012] FIG. 1 illustrates an out of order (OOO) hybrid automatic repeat request (HARQ) scenario;

[0013] FIG. 2 is a schematic diagram of an exemplary network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

[0014] FIG. 3 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure;

[0015] FIG. 4 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure; [0016] FIG. 5 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure;

[0017] FIG. 6 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure;

[0018] FIG. 7 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure;

[0019] FIG. 8 is a flowchart of an exemplary process in a wireless device for codebook construction;

[0020] FIG. 9 shows allocations of physical downlink shared channels (PDSCHs) and HARQ- ACK responses for two different semipersi stent scheduling (SPS) configurations;

[0021] FIG. 10 shows an out of order (OOO) condition;

[0022] FIG. 11 shows multiple timing offsets for a HARQ-ACK field for SPS; and [0023] FIG. 12 shows HARQ patterns for PDSCH with an OOO condition.

DETAILED DESCRIPTION

[0024] Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to semipersi stent scheduling (SPS) hybrid automatic repeat request (HARQ) codebook design. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

[0025] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

[0026] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication. [0027] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.

[0028] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi -standard radio (MSR) radio node such as MSR BS, multi -cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, integrated access and backhaul (IAB) node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

[0029] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (IoT) device, or a Narrowband IoT (NB-IOT) device etc.

[0030] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0031] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0032] Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0033] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0034] Embodiments provide semipersi stent scheduling (SPS), hybrid automatic repeat request (HARQ) codebook design for wireless communication networks. Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG.

2 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16c. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16a. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes

16 [0035] Also, it is contemplated that a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.

[0036] The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub networks (not shown).

[0037] The communication system of FIG. 2 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.

[0038] A wireless device 22 is configured to include a codebook combiner 34 which is configured to concatenate first and second codebooks.

[0039] Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 3. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read- Only Memory).

[0040] Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24.

[0041] The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22. [0042] The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.

[0043] In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory). [0044] Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16.

[0045] The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.

[0046] The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

[0047] Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

[0048] The processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 84 of the wireless device 22 may include a codebook combiner 34 which is configured to concatenate first and second codebooks.

[0049] In some embodiments, the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 3 and independently, the surrounding network topology may be that of FIG. 2.

[0050] In FIG. 3, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

[0051] The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

[0052] In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48,

90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors etc.

[0053] Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the WD 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the WD 22

[0054] In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16. In some embodiments, the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.

[0055] Although FIGS. 2 and 3 show various units such as the codebook combiner 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0056] FIG. 4 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIGS. 2 and 3, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 3. In a first step of the method, the host computer 24 provides user data (Block SI 00). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block S102). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application

50 executed by the host computer 24 (Block SI 08).

[0057] FIG. 5 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3. In a first step of the method, the host computer 24 provides user data (Block SI 10). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block S 112). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block SI 14).

[0058] FIG. 6 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (Block

5116). In an optional substep of the first step, the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18). Additionally or alternatively, in an optional second step, the WD 22 provides user data (Block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).

[0059] FIG. 7 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the WD 22 (Block S128). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (Block S130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).

[0060] FIG. 8 is a flowchart of an exemplary process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the codebook combiner 34), processor 86, radio interface 82 and/or communication interface 60. Wireless device 22, such as via processing circuitry 84 and/or processor 86 and/or radio interface 82, is configured to construct a codebook by combining a first codebook and a second codebook, the first codebook being configured for hybrid automatic repeat request, HARQ, acknowledgment, ACK response of dynamically scheduled physical shared channels and the second codebook being configured for HARQ-ACK response of semi -persistently scheduled physical shared channels (Block SI 34).

[0061] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for semipersi stent scheduling (SPS), hybrid automatic repeat request (HARQ) codebook design.

[0062] Constructing a codebook may include the use of determination algorithms. Exemples of codebook determination algorithm are Type 1 and Type 2. Further examples of codebook determination algorithm are available in TS 38.213 and TS 38.331.

[0063] In a first embodiment, SPS configuration HARQ codebooks not combined with dynamic PDSCH codebook, then multiple options may arise. According to one option of this embodiment, all SPS configurations have separate independent codebooks. See, for example, FIG. 9, where the upper row represents a first SPS configuration and the second row represents a second SPS configuration. In another option of this embodiment, all SPS configurations have a combined codebook. According to another option of this embodiment, some SPS configurations have a combined codebook and some SPS configurations have independent codebooks.

[0064] In a second embodiment, an SPS configuration codebook can be attached with a dynamic

PDSCH codebook. [0065] Depending on applicability, the combination (which may be, for example, a concatenation) of codebooks in these two embodiments, can be based on some condition, e.g., SPSs having a same periodicity, or transport blocks (TBs) from SPSs and/or dynamic allocations having a same reliability, or same K1 timing, etc.

[0066] In the combined codebook, bundle feedback can be transmitted (i.e., the resultant bit from an AND operation on HARQ-ACK bits belonging to two different HARQ operations/PDSCHs/TBs or more). The following scenarios may exist:

• Bundle N/ACK for TBs belonging to multiple SPSs;

• Bundle N/ACK for TBs belonging to multiple dynamic PDSCHs; and

• Bundle N/ACK for TBs belonging to multiple SPSs and dynamic PDSCHs.

[0067] Additional Properties

[0068] 1 Concatenation: For a Type 2 HARQ-ACK codebook (i.e., a dynamic codebook), two codebooks are constructed. The first codebook is for the HARQ-ACK response of dynamically scheduled PDSCH, each of which have an associated PDCCH. The second codebook is for HARQ-ACK response for PDSCH of the SPS configurations.

[0069] The two HARQ-ACK codebooks can be concatenated in, for example, two ways.

• The codebook for dynamic PDSCH may be put in front of the codebook for DL SPS.

This is consistent with 3GPP Rel-15.

• The codebook for dynamic PDSCH (i.e., the first codebook) may be put behind the codebook for DL SPS (i.e., the second codebook). This provides a benefit in which the size of the second codebook is deterministic, and therefore, there is no concern about HARQ-ACK bit misalignment, which may happen due to misdetection of PDCCH.

[0070] 2. DAI: Since time-domain resource allocation of DL SPS may be known, there may be no concern of mis-aligned HARQ-ACK bits. There may be no need of DAI, either counter downlink assignment indicator (cDAI) or total DAI (tDAI). The second HARQ-ACK codebook is hence composed of a ACK/NACK response for each of related DL SPS configurations, where the ACK/NACK response is for either DL SPS PDSCH reception or SPS PDSCH release.

[0071] 3. Generalized Codebook Construction: Different SPS can arrive at any time. For a dynamic codebook, including both dynamic PDSCH and SPS, and assuming no downlink assignment index (DAI) for SPS, the WD 22 can supply ACK information in a number of ways. In FIG. 9, an example is presented where transport blocks (TBs) belonging to different SPS and dynamic PDSCHs are allocated, and in the dynamic codebook construction: a) SPS HARQ-ACKs can be in front: i) Referring to the example of FIG. 9, the ACKs in HARQ-ACK field represented as HARQ - ACK = {lx, 2a, 1 y, 0,1, 2, 3, 4, 5), b) SPS HARQ-ACKs can be in the back: i) Referring to the example of FIG. 9, the ACKs in HARQ-ACK field represented as HARQ - ACK = (0,1, 2, 3, 4, 5, lx, 2a, 1 y), c) SPS HARQ-ACK can follow the order of corresponding SPS PDSCH’ s carrier (first) and time (second) allocation: i) Referring to the example of FIG. 9, the ACKs in HARQ-ACK field represented as HARQ - ACK = (lx, 0,1,2,3,4,2a, ly, 5). [0072] 4. HARO Timing: There may be a timing field (offset) for an uplink (UL) acknowledgement in the downlink control information (DCI) for dynamic PDSCH allocation.

For SPS, there can be more than one timing values in activation DCI or RRC. There are at least two scenarios, e.g., where: a) One HARQ timing value points to an ACK field for one PDSCH; and b) Multiple HARQ timing values point to an ACK field for many PDSCHs, e.g., see FIG. 11; and further

(1) ACK bits are bundled; or

(2) ACK bits are not bundled.

The timing offset can be measured in terms of slots, or mini-slots, or time symbols.

[0073] Referring again to FIG. 9, allocations of PDSCHs and HARQ-ACK responses for two different SPS configurations are shown, the top row having PDSCH 1 and 4, and each PDSCH having its corresponding HARQ ACK response in a PUCCH for a first SPS configuration. The bottom row has assignments for another SPS configuration.

[0074] 5. OOP Condition: While allocating these codebook resources, the order of codebook allocation may or may not follow the order of PDSCH allocations. An example is shown in FIG. 12. FIG. 12 shows that HARQ for PDSCH 2 is out of order (OOO) (as it comes earlier than HARQ of PDSCH 1). PDSCH 1 and PDSCH 4 are part of SPS 1, and PDSCH 2, PDSCH 3 and PDSCH 5 are part of SPS2. According to a legacy rule of 3GPP Rel-15, this is not permitted, and such allocation can be deemed erroneous. Further, only one SPS is allowed in 3 GPP Rel-15. However, for future releases of 3 GPP standards, there may be no limitation due to an OOO condition. Therefore, the ACK 1 bit can be transmitted in physical uplink control channel (PUCCH 1), and the ACK 2 bit can be transmitted in PUCCH 2 (i.e., an OOO resource). It is noted that the PUCCH resources in FIG. 12 can be part of different SPSs or dynamic allocation or both.

[0075] The above discussion can be extended for codebook allocation in the UL where there may be dynamic PUSCH (like dynamic PDSCH in DL), and CG (similar to SPS in DL) with allowable HARQ transmission from a base station (e.g., gNB). Note that in 3GPP Rel-15, CG does not support HARQ transmission.

[0076] According to one aspect, a WD 22 is configured to communicate with a network node and includes processing circuitry 84 configured to construct a codebook by combining a first codebook and a second codebook , the first codebook being configured for hybrid automatic repeat request, HARQ, acknowledgment, ACK, response of dynamically scheduled physical shared channels and the second codebook being configured for HARQ-ACK response of semi- persistently scheduled physical shared channels.

[0077] According to this aspect, in some embodiments, the physical shared channels are physical downlink shared channels, PDSCH. In some embodiments, an order of the first and second codebooks is not in the same order as an order of physical shared channels. In some embodiments, the first codebook follows the second codebook. In some embodiments, a plurality of SPS configurations have independent codebooks. In some embodiments, a plurality of SPS configurations have independent codebooks. In some embodiments, the combining of codebooks is based on a condition, the condition including at least one of SPS periodicity, transport block reliability and K1 timing. In some embodiments, SPS configuration HARQ codebooks are allocated separately. In some embodiments, SPS configurations have separate independent codebooks. In some embodiments, all SPS configuration have a combined codebook. In some embodiments, forming the combined codebook is based on a condition. In some embodiments, an SPS configuration codebook is attached by a dynamic physical downlink shared channel, PDSCH, codebook. In some embodiments, the combining of the first and second codebooks is in a predetermined order. In some embodiments, the radio interface and/or processing circuitry is further configured to receive a timing field indicating multiple HARQ timing values, each HARQ timing value pointing to an ACK field of physical shared channel. In some embodiments, the timing field further indicates whether ACK bits are bundled.

[0078] According to another aspect, a method implemented in a WD 22 includes constructing a codebook by combining a first codebook and a second codebook , the first codebook being configured for hybrid automatic repeat request, HARQ, acknowledgment, ACK, response of dynamically scheduled physical shared channels and the second codebook being configured for HARQ-ACK response of semi -persistently scheduled physical shared channels.

[0079] According to this aspect, in some embodiments, the physical shared channels are physical downlink shared channels, PDSCH. In some embodiments, an order of the first and second codebooks is not in the same order as an order of physical shared channels. In some embodiments, the first codebook follows the second codebook. In some embodiments, a plurality of SPS configurations have independent codebooks. In some embodiments, a plurality of SPS configurations have a combined codebook. In some embodiments, the combining of codebooks is based on a condition, the condition including at least one of SPS periodicity, transport block reliability and K1 timing. In some embodiments, SPS configuration HARQ codebooks are allocated separately. In some embodiments, SPS configurations have separate independent codebooks. In some embodiments, all SPS configuration have a combined codebook. In some embodiments, forming the combined codebook is based on a condition. In some embodiments, an SPS configuration codebook is attached by a dynamic physical downlink shared channel, PDSCH, codebook. In some embodiments, the combining of the first and second codebooks is in a predetermined order. In some embodiments, the process further includes receiving a timing field indicating multiple HARQ timing values, each HARQ timing value pointing to an ACK field of physical shared channel. In some embodiments, the timing field further indicates whether ACK bits are bundled.

[0080] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0081] Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[0082] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

[0083] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[0084] It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0085] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0086] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0087] Abbreviations that may be used in the preceding description include:

[0088] Abbreviation Explanation

[0089] 3 GPP 3rd Generation Partnership Project [0090] 5G 5th Generation [0091] ACK Acknowledgement [0092] CE Control Element [0093] CG Configured Grant

[0094] DCI Downlink Control Information [0095] DL Downlink [0096] DMRS Demodulation Reference Signal [0097] GF Grant-Free [0098] gNB Next Generation NodeB [0099] ID Identity

[00100] LCH Logical Channel

[00101] LTE Long-Term Evolution

[00102] MCS Modulation and Coding Scheme

[00103] NACK No Acknowledgement

[00104] NR New Radio

[00105] OOO Out-of-Order

[00106] PUSCH Physical Uplink Shared Channel

[00107] SNR Signal-to-Noise Ratio

[00108] SPS Semi -Persistent Scheduling

[00109] TTI Transmission Time Interval

[00110] TO Transmission Opportunity

[00111] UE User Equipment [00112] UL Uplink

[00113] URLLC Ultra-Reliable and Low-Latency Communications

[00114] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings.

Embodiments:

Embodiment A1. A wireless device, WD, configured to communicate with a network node, the WD configured to, and/or comprising a radio interface and/or processing circuitry configured to: construct a codebook by combining a first codebook and a second codebook, the first codebook being configured for hybrid automatic repeat request, HARQ, acknowledgment, ACK, response of dynamically scheduled physical shared channels and the second codebook being configured for HARQ-ACK response of semi-persistently scheduled, SPS, physical shared channels.

Embodiment A2. The wireless device of Embodiment Al, wherein the physical shared channels are physical downlink shared channels, PDSCH.

Embodiment A3. The wireless device of Embodiment Al, wherein an order of the first and second codebooks is not in the same order as an order of physical shared channels.

Embodiment A4. The wireless device of any of Embodiments A1-A3, wherein the first codebook follows the second codebook.

Embodiment A5. The wireless device of any of Embodiments A1-A4, wherein a plurality of SPS configurations have independent codebooks. Embodiment A6. The wireless device of any of Embodiments A1-A4, wherein a plurality of SPS configurations have a combined codebook.

Embodiment A7. The wireless device of any of Embodiments A1-A6, wherein the combining of codebooks is based on a condition, the condition including at least one of SPS periodicity, transport block reliability and K1 timing.

Embodiment A8. The wireless device of any of Embodiments A1-A6, wherein SPS configuration ELARQ codebooks are allocated separately.

Embodiment A9. The wireless device of Embodiment A7, wherein all SPS configurations have separate independent codebooks.

Embodiment A10. The wireless device of Embodiment A7, wherein all SPS configuration have a combined codebook.

Embodiment A11. The wireless device of Embodiment A9, wherein forming the combined codebook is based on a condition.

Embodiment A12. The wireless device of any of Embodiments A1-A9, wherein an

SPS configuration codebook is attached by a dynamic physical downlink shared channel,

PDSCH, codebook. Embodiment A13. The wireless device of any of Embodiments A1-A12, wherein the combining of the first and second codebooks is in a predetermined order.

Embodiment A14. The wireless device of any of Embodiments A1-A13, wherein the radio interface and/or processing circuitry is further configured to receive a timing field indicating multiple ELARQ timing values, each ELARQ timing value pointing to an ACK field of physical shared channel.

Embodiment A15. The wireless device of Embodiment A14, wherein the timing field further indicates whether ACK bits are bundled.

Embodiment Bl. A method implemented in a wireless device (WD), the method comprising: constructing a codebook by combining a first codebook and a second codebook, the first codebook being configured for hybrid automatic repeat request, ELARQ, acknowledgment, ACK, response of dynamically scheduled physical shared channels and the second codebook being configured for HARQ-ACK response of semi-persistently scheduled, SPS, physical shared channels.

Embodiment B2. The method of Embodiment B 1, wherein the physical shared channels are physical downlink shared channels, PDSCH. Embodiment B3. The method of Embodiment Bl, wherein an order of the first and second codebooks is not in the same order as an order of physical shared channels.

Embodiment B4. The method of any of Embodiments B 1-B3, wherein the first codebook follows the second codebook.

Embodiment B5. The method of any of Embodiments B1-B4, wherein a plurality of SPS configurations have independent codebooks.

Embodiment B6. The method of any of Embodiments B1-B4, wherein a plurality of SPS configurations have a combined codebook.

Embodiment B7. The method of any of Embodiments B 1-B5, wherein the combining of codebooks is based on a condition, the condition including at least one of SPS periodicity, transport block reliability and K1 timing.

Embodiment B8. The method of any of Embodiments B1-B6, wherein SPS configuration HARQ codebooks are allocated separately.

Embodiment B9. The method of Embodiment B7, wherein all SPS configurations have separate independent codebooks. Embodiment BIO. The method of Embodiment B7, wherein all SPS configuration have a combined codebook.

Embodiment B 11. The method of Embodiment B9, wherein forming the combined codebook is based on a condition.

Embodiment B 12. The method of any of Embodiments B1-B9, wherein an SPS configuration codebook is attached by a dynamic physical downlink shared channel, PDSCH, codebook.

Embodiment B 13. The method of any of Embodiments B1-B12, wherein the combining of the first and second codebooks is in a predetermined order.

Embodiment B 14. The method of any of Embodiments B1-B13, further comprising receiving a timing field indicating multiple HARQ timing values, each HARQ timing value pointing to an ACK field of physical shared channel.

Embodiment B 15. The method of Embodiment B 14, wherein the timing field further indicates whether ACK bits are bundled.

Claims

Claims:

1. A wireless device, WD, configured to communicate with a network node, the WD comprising a radio interface and processing circuitry configured to: construct a codebook by combining at least a first codebook and a second codebook, the first codebook being configured for hybrid automatic repeat request, HARQ, acknowledgment, ACK, response of dynamically scheduled physical shared channels and the second codebook being configured for HARQ-ACK response of semi-persistently scheduled, SPS, physical shared channels.

2. The wireless device of Claim 1, wherein the physical shared channels are physical downlink shared channels, PDSCH.

3. The wireless device of 1, wherein an order of the first and second codebooks is not in the same order as an order of physical shared channels.

4. The wireless device of any of Claims 1-3, wherein the first codebook follows the second codebook.

5. The wireless device of any of Claims 1-4, wherein a plurality of SPS configurations have independent codebooks.

6. The wireless device of any of Claims 1-4, wherein a plurality of SPS configurations have a combined codebook.

7. The wireless device of any of Claims 1-6, wherein the combining of codebooks is based on a condition, the condition including at least one of SPS periodicity, transport block reliability and Kl timing.

8. The wireless device of any of Claims 1-6, wherein SPS configuration HARQ codebooks are allocated separately.

9. The wireless device of Claim 7, wherein all SPS configurations have separate independent codebooks.

10. The wireless device of Claim 7, wherein all SPS configuration have a combined codebook.

11. The wireless device of Claim 9, wherein forming the combined codebook is based on a condition.

12. The wireless device of any of Claims 1-9, wherein an SPS configuration codebook is attached by a dynamic physical downlink shared channel, PDSCH, codebook.

13. The wireless device of any of Claims 1-12, wherein the combining of the first and second codebooks is in a predetermined order.

14. The wireless device of any of Claims 1-13, wherein the radio interface and/or processing circuitry is further configured to receive a timing field indicating multiple HARQ timing values, each HARQ timing value pointing to an ACK field of physical shared channel.

15. The wireless device of Claim 14, wherein the timing field further indicates whether ACK bits are bundled.

16. The wireless device of Claim 1, wherein the processing circuitry is further configured to construct a codebook by combining the at least first codebook, the second codebook and a third codebook, wherein the third codebook being configured for HARQ-ACK response of semi-persistently scheduled, SPS, physical shared channels.

17. A method implemented in a wireless device (WD), the method comprising: constructing a codebook by combining at least a first codebook and a second codebook, the first codebook being configured for hybrid automatic repeat request, HARQ, acknowledgment, ACK, response of dynamically scheduled physical shared channels and the second codebook being configured for HARQ-ACK response of semi-persistently scheduled, SPS, physical shared channels.

18. The method of Claim 17, wherein the physical shared channels are physical downlink shared channels, PDSCH.

19. The method of Claim 17, wherein an order of the first and second codebooks is not in the same order as an order of physical shared channels.

20. The method of any of Claims 17-19, wherein the first codebook follows the second codebook.

21. The method of any of Claims 17-20, wherein a plurality of SPS configurations have independent codebooks.

22. The method of any of Claims 17-20, wherein a plurality of SPS configurations have a combined codebook.

23. The method of any of Claims 17-21, wherein the combining of codebooks is based on a condition, the condition including at least one of SPS periodicity, transport block reliability and Kl timing.

24. The method of any of Claims 17-22, wherein SPS configuration HARQ codebooks are allocated separately.

25. The method of Claim 23, wherein all SPS configurations have separate independent codebooks.

26. The method of Claim 23, wherein all SPS configuration have a combined codebook.

27. The method of Claim 25, wherein forming the combined codebook is based on a condition.

28. The method of any of Claims 17-25, wherein an SPS configuration codebook is attached by a dynamic physical downlink shared channel, PDSCH, codebook.

29. The method of any of Claims 17-28, wherein the combining of the first and second codebooks is in a predetermined order.

30. The method of any of Claims 17-29, further comprising receiving a timing field indicating multiple HARQ timing values, each HARQ timing value pointing to an ACK field of physical shared channel.

31. The method of Claim 30, wherein the timing field further indicates whether ACK bits are bundled.

32. The method of Claim 31, wherein the method further comprises constructing a codebook by combining the at least first codebook, the second codebook and a third codebook, wherein the third codebook being configured for HARQ-ACK response of semi-persistently scheduled, SPS, physical shared channels.