Method and apparatus for hybrid automatic repeat request (HARQ)-acknowledgment (ACK) feedback for semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release

Abstract

A user equipment (UE) device is disclosed. The UE device includes a processor configured to perform operations including receiving downlink control information (DCI) from a base station. In some embodiments, the DCI includes an indication for triggering a type 3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal. The operations further include generating a type 3 HARQ ACK feedback signal based on processing the DCI. In some embodiments, the type 3 HARQ ACK feedback signal includes one or more HARQ-ACK bits for a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release. In some embodiments, each of the one or more HARQ-ACK bits for the SPS PDSCH release is adapted to include HARQ-ACK information for the SPS PDSCH release associated with the UE. Additionally, the operations include transmitting the type 3 HARQ-ACK feedback signal to the base station.

Description

Technical Field

[0001] The present disclosure relates to the field of wireless communication systems, and more particularly, to systems and methods for hybrid automatic repeat request (HARQ)-acknowledgment (ACK) feedback for semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release. Background Art

[0002] Networks need to provide data quickly and reliably without overburdening their resources. Hybrid automatic repeat request (HARQ) techniques enable this to happen. HARQ uses a stop-and-wait protocol. When a transmission has been made, the transmitting entity stops and waits until it receives an acknowledgment (ACK) or a negative acknowledgment (NACK) from the destination, after which it transmits the next data block or retransmits the same data block. Such transmit / receive processes that rely on ACK / NACK feedback are sometimes referred to as HARQ processes. Brief Description of the Drawings

[0003] Some examples of circuits, devices, and / or methods will be described hereinafter only by way of example. In this context, reference will be made to the accompanying drawings.

[0004] Figure 1 A simplified block diagram of a wireless communication system supporting SPS release along with a type 3 HARQ-ACK codebook configuration according to an embodiment of the present disclosure is shown.

[0005] Figure 2a A simplified block diagram of a wireless communication system supporting group-based HARQ-ACK feedback according to an embodiment of the present disclosure is shown.

[0006] Figure 2b and Figure 2c A HARQ process grouping for HARQ feedback according to an embodiment of the present disclosure is shown.

[0007] Figure 3a and Figure 3b Two possible signal configurations for an HPG configuration signal according to an embodiment of the present disclosure are depicted.

[0008] Figure 4a and Figure 4b Two possible configurations of a HARQ reconstituted MAC CE according to an embodiment of the present disclosure are shown.

[0009] Figure 5 A simplified block diagram of a wireless communication system facilitating the provision of a new data indicator (NDI) as part of HARQ-ACK feedback according to an embodiment of the present disclosure is shown.

[0010] Figure 6A block diagram of an apparatus that can be employed at a base station (BS), eNodeB, gNodeB, or other network device according to various aspects described herein is shown.

[0011] Figure 7 A block diagram of an apparatus that can be employed at a user equipment (UE) or other network device (e.g., IoT device) according to various aspects described herein is shown.

[0012] Figure 8 A flowchart of a method for a UE associated with a wireless communication system that supports SPS release along with a Type 3 HARQ-ACK codebook configuration according to an embodiment of the present disclosure is shown.

[0013] Figure 9 A flowchart of a method for a base station (BS) associated with a wireless communication system that supports SPS release along with a Type 3 HARQ-ACK codebook configuration according to an embodiment of the present disclosure is shown.

[0014] Figure 10 A flowchart of a method for a UE associated with a wireless communication system that supports group-based HARQ-ACK feedback according to an embodiment of the present disclosure is shown.

[0015] Figure 11 A flowchart of a method for a base station associated with a wireless communication system that supports group-based HARQ-ACK feedback according to an embodiment of the present disclosure is shown.

[0016] Figure 12 A flowchart of a method for a UE associated with a wireless communication system that supports a new data indicator (NDI) as part of HARQ-ACK feedback according to an embodiment of the present disclosure is shown.

[0017] Figure 13 A flowchart of a method for a base station associated with a wireless communication system that supports a new data indicator (NDI) as part of HARQ-ACK feedback according to an embodiment of the present disclosure is shown.

[0018] Figure 14 An architecture of a system including a core network (CN) such as a fifth generation (5G) CN (5GC) according to various embodiments is shown.

[0019] Figure 15 An exemplary component of a device according to some embodiments is shown.

[0020] Figure 16 An exemplary interface of a baseband circuit according to some embodiments is shown. Detailed Description

[0021] In one embodiment of the present disclosure, a user equipment (UE) device is disclosed. The UE device includes a processor (or processing circuitry) configured to perform operations that include receiving downlink control information (DCI) from a base station associated with the UE device. In some embodiments, the DCI includes an indication for triggering a type 3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal. The operations further include generating a type 3 HARQ ACK feedback signal based on processing the DCI. In some embodiments, the type 3 HARQ ACK feedback signal includes one or more HARQ-ACK bits for a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release. In some embodiments, each of the one or more HARQ-ACK bits for the SPS PDSCH release is adapted to include HARQ-ACK information for the SPS PDSCH release associated with the UE. In some embodiments, the operations further include sending the type 3 HARQ-ACK feedback signal to the base station.

[0022] In one embodiment of the present disclosure, a base station (BS) is disclosed. The base station includes a processor (or processing circuitry) configured to perform operations that include sending downlink control information (DCI) to a user equipment (UE) associated with the base station. In some embodiments, the DCI includes an indication to the UE for triggering a type 3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal. The operations further include receiving a type 3 HARQ ACK feedback signal from the UE in response to providing the DCI. In some embodiments, the type 3 HARQ ACK feedback signal includes one or more HARQ-ACK bits for a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release. In some embodiments, each of the one or more HARQ-ACK bits for the SPS PDSCH release is adapted to include HARQ-ACK information for the SPS PDSCH release associated with the UE.

[0023] In one embodiment of the present disclosure, a baseband (BB) processor for a UE is disclosed. The BB processor is configured to perform operations that include receiving downlink control information (DCI) from a base station associated with the UE. In some embodiments, the DCI includes an indication for triggering a type 3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal. The operations also include generating a type 3 HARQ ACK feedback signal based on processing the DCI. In some embodiments, the type 3 HARQ ACK feedback signal includes one or more HARQ-ACK bits for semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release. In some embodiments, each of the one or more HARQ-ACK bits for SPS PDSCH release is adapted to include HARQ-ACK information for an SPS PDSCH release associated with the UE. Further, the operations include transmitting the type 3 HARQ-ACK feedback signal to the base station.

[0024] In one embodiment of the present disclosure, a baseband (BB) processor for a base station is disclosed. The BB processor is configured to perform operations that include transmitting downlink control information (DCI) to a user equipment (UE) associated with the base station. In some embodiments, the DCI includes an indication to the UE for triggering a type 3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal. The operations also include receiving a type 3 HARQ ACK feedback signal from the UE in response to providing the DCI. In some embodiments, the type 3 HARQ ACK feedback signal includes one or more HARQ-ACK bits for semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release. In some embodiments, each of the one or more HARQ-ACK bits for SPS PDSCH release is adapted to include HARQ-ACK information for an SPS PDSCH release associated with the UE.

[0025] The present disclosure will now be described with reference to the accompanying drawings, in which like reference numerals are used throughout to refer to like elements, and in which the structures and devices shown are not necessarily drawn to scale. As used herein, the terms "component", "system", "interface", "circuit", etc. are intended to refer to computer-related entities, hardware, software (e.g., in execution), and / or firmware. For example, a component can be a processor (e.g., a microprocessor, a controller, or other processing device), a process running on the processor, a controller, an object, an executable, a program, a storage device, a computer, a tablet, and / or a user equipment (e.g., a mobile phone, etc.) with a processing device. By way of example, an application running on a server and the server can also be components. One or more components can reside in a process, and components can be located on one computer and / or distributed between two or more computers. Element collections or other component collections may be described herein, where the term "collection" can be interpreted as "one or more".

[0026] In addition, these components can execute from various computer-readable storage media on which various data structures are stored, such as by way of example, using modules. Components can communicate, for example, via local and / or remote processes according to a signal having one or more data packets (e.g., data from one component interacts with another component in a local system, a distributed system, and / or across a network, such as the Internet, a local area network, a wide area network, or a similar network of other systems via a signal).

[0027] As another example, a component can be a device having a specific function provided by a mechanical component operated by an electrical or electronic circuit, where the electrical or electronic circuit can be operated by a software application or a firmware application executed by one or more processors. The one or more processors can be inside or outside the device and can execute at least a portion of the software or firmware application. As yet another example, a component can be a device that provides a specific function through an electronic component without a mechanical component; the electronic component can include one or more processors therein to execute at least a portion of the software and / or firmware that imparts the function to the electronic component.

[0028] The use of the term "exemplary" is intended to present concepts in a concrete manner. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clear from the context, "X employs A or B" is intended to mean any natural inclusive arrangement. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied in any of the foregoing instances. Additionally, the articles "a" and "an" as used in this application and the appended claims generally should be construed to mean "one or more" unless otherwise specified or clearly apparent from the context to be singular. Further, with respect to the use of the terms "comprising", "including", "having", "has", "with", or variants thereof in the detailed description and claims, such terms are intended to be inclusive in a manner similar to the term "containing".

[0029] The following detailed description refers to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, for purposes of illustration and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, technologies, etc., in order to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art who have benefited from the present disclosure that various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In some instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail.

[0030] It is well known that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use, and the nature of the authorized use should be clearly explained to the user.

[0031] As pointed out above, the HARQ process depends on receiving ACK / NACK for data packets. When the base station (BS) transmits data / transmissions to the user equipment (UE) via the physical downlink shared channel (PDSCH), the UE determines its correctness by checking the cyclic redundancy check (CRC) and reports it to the base station via the ACK / NACK bits. If the UE also has data to send and it is granted permission, the UE will send the ACK / NACK together with the data on the physical uplink shared channel (PUSCH), otherwise the UE will send the ACK / NACK on the physical uplink control channel (PUCCH). The HARQ-ACK codebook defines the format of the set used to signal HARQ acknowledgments (ACKs) to the base station. The codebook allows the UE to multiplex HARQ ACKs from multiple time slots, multiple carriers, multiple transport blocks, and multiple code block groups (CBGs) within a single transmission. Importantly, both the UE and the base station share the same understanding of the codebook format to ensure that each acknowledgment is linked to the appropriate transmission. The base station configures the use of a specific codebook category using the pdsch-HARQ-ACK-codebook information element via radio resource control (RRC) signaling. Different categories of HARQ-ACK codebooks are defined in 3GPP. For example, type 1 HARQ-ACK codebooks include semi-static codebooks where the size of the codebook is fixed by information provided by radio resource control (RRC) signaling, and type 2 HARQ-ACK codebooks include dynamic codebooks where the size of the codebook changes according to the number of resource allocations. Additionally, type 3 HARQ-ACK codebooks are defined, which are triggered on demand by the one-shot HARQ-ACK occasion field in DCI.

[0032] There are two types of scheduling for the downlink. One type of scheduling is referred to as 'dynamic scheduling', while the other type of scheduling is referred to as semi-persistent scheduling (SPS). Dynamic scheduling is a mechanism in which each PDSCH is scheduled via DCI (e.g., DCI1_0 or DCI 1_1). SPS is a mechanism in which PDSCH transmissions are configured via radio resource control (RRC) messages. SPS is a feature that significantly reduces the control channel overhead for applications that require continuous radio resource allocation such as VoIP. In dynamic scheduling, both the downlink (DL) and the uplink (UL) are fully scheduled because the DL and UL traffic channels are dynamically shared channels. This means that the physical DL control channel (PDCCH) must provide access grant information to indicate which users should decode the physical DL shared channel (PDSCH) in each subframe and which users are allowed to transmit on the physical UL shared channel (PUSCH) in each subframe. In the absence of SPS, each DL or UL physical resource block (PRB) allocation must be granted via an access grant message on the PDCCH. This is sufficient for most bursty best-effort type applications, which typically have large packet sizes and thus usually only a few users need to be scheduled in each subframe. However, for applications that require continuous allocation of smaller packets (i.e., VoIP), SPS can be utilized to greatly reduce the access grant control channel overhead. Once SPS is configured via an RRC message, the base station uses the downlink control information (DCI) of the PDCCH to activate SPS. When SPS is activated, SPS transmissions in the UL and DL are performed. In some embodiments, due to SPS activation, SPS release or SPS PDSCH release is also indicated by DCI. Alternatively, in other embodiments, SPS release can be indicated to the UE via RRC signaling or higher layer signaling.

[0033] The latest wireless communication technologies such as 5G are expected to support a wide range of emerging applications based on conventional cellular mobile broadband services. One of the key usage scenarios within 5G is ultra-reliable and low-latency communication (URLLC). URLLC will play an important role in providing connectivity for new services and applications from vertical domains such as factory automation, autonomous driving, etc. The most important key performance indicators (KPIs) associated with URLLC are latency, reliability, and availability. SPS-based PDSCH transmissions are widely used for URLLC service types to reduce signaling overhead and improve reliability. For example, for a given BWP of a serving cell, up to 8 DL SPS configurations are supported. Additionally, joint release in DCI for two or more SPS configurations is supported by means of M least significant bit (LSB) hybrid automatic repeat request (HARQ) process number (HPN) bits to minimize signaling overhead.

[0034] In the current specific implementation, the Type 3 HARQ-ACK codebook does not support HARQ-ACK feedback for SPS release. Specifically, when the Type 3 HARQ-ACK codebook is triggered in the same time slot in which the BS provides the SPS release indication to the UE, the HARQ-ACK information corresponding to the SPS release will be discarded because the Type 3 HARQ-ACK codebook does not support HARQ-ACK feedback for SPS release. When the URLLC service utilizes SPS-based PDSCH transmission, this greatly affects the reliability of the URLLC service. Therefore, the enhancement to support SPS release together with the Type 3 HARQ-ACK codebook configuration is important for efficiently operating URLLC traffic on the unlicensed band in a controlled environment. Systems, circuits, and techniques for supporting SPS release together with the Type 3 HARQ-ACK codebook configuration are disclosed herein.

[0035] In addition, in the current specific implementation, the HARQ-ACK information for multiple DL HARQ processes configured for the UE is included in the HARQ-ACK codebook. For example, the HARQ-ACK information for all DL HARQ processes configured for the UE is included in the Type 3 HARQ-ACK codebook. However, when one or more of the DL HARQ processes configured for the UE include the URLLC service, this affects the reliability of the HARQ-ACK feedback for high-reliability services such as the URLLC service. To overcome this drawback, systems, circuits, and techniques for providing a flexible process for controlling the HARQ-ACK codebook based on grouping the HARQ processes to improve reliability, for example, to meet the reliability requirements of the URLLC service type, are disclosed herein.

[0036] Figure 1 A simplified block diagram of a wireless communication system 100 according to an embodiment of the present disclosure is shown. In some embodiments, the wireless communication system 100 supports SPS release together with the Type 3 HARQ-ACK codebook configuration. The wireless communication system 100 includes a user equipment (UE) 102 and a base station (BS) 104. However, in other embodiments, the wireless communication system 100 may include multiple UEs, and for clarity, they are not shown here. In some embodiments, the base station 104 is equivalent to an eNodeB in an LTE system, a gNodeB in a 5G New Radio (NR) system, etc. In some embodiments, the UE 102 may include a mobile phone, a tablet computer, an Internet of Things (IoT) device, a vehicle-to-everything (V2X) UE, etc. The UE 102 and the base station 104 are configured to communicate with each other via a communication medium (e.g., air). In some embodiments, the wireless communication system 100 supports semi-persistent scheduling (SPS) release together with the Type 3 HARQ-ACK codebook configuration, as will be fully understood hereinafter.

[0037] In some embodiments, the BS 104 is configured to provide the UE 102 with downlink control information (DCI) 106. The DCI 106 is provided to the UE 102 as part of a physical downlink control channel (PDCCH). In some embodiments, the DCI 106 is configured to trigger a type 3 hybrid automatic repeat request (HARQ) ACK feedback signal 108 from the UE 102. In such embodiments, the DCI 106 includes an indication for triggering the type 3 HARQ ACK feedback signal 108. Specifically, the DCI 106 includes a single-slot HARQ-ACK occasion field, and the value associated with this field provides the UE 102 with an indication for triggering the type 3 HARQ-ACK feedback signal 108. For example, when the single-shot HARQ-ACK occasion field includes the value 1, the UE 102 is configured to trigger the type 3 HARQ-ACK feedback signal 108. Alternatively, when the single-shot HARQ-ACK occasion field includes the value 0, the UE 102 is configured not to trigger the type 3 HARQ-ACK feedback signal 108. In some embodiments, the DCI 106 further includes information on the physical uplink control channel (PUCCH) / physical uplink shared channel (PUSCH) resources to be used by the UE 102 for transmitting the type 3 HARQ-ACK feedback signal 108.

[0038] UE 102 is configured to receive and process DCI 106. After processing DCI 106, when DCI 106 includes an indication for triggering a type 3 HARQ-ACK feedback signal, UE 102 is configured to generate a type 3 HARQ-ACK feedback signal 108. In some embodiments, the type 3 HARQ-ACK feedback signal 108 may further be referred to as type 3 HARQ-ACK CB 108 or type 3 HARQ-ACK CB feedback signal 108. In some embodiments, the type 3 HARQ-ACK feedback signal 108 is configured to include HARQ-ACK information associated with a set of HARQ processes configured for UE 102. In some embodiments, the set of HARQ processes configured for UE 102 may include one or more SPS PDSCHs. In some embodiments, the type 3 HARQ-ACK feedback signal 108 further includes one or more HARQ-ACK bits for SPS PDSCH release. In some embodiments, each of the one or more HARQ-ACK bits for SPS PDSCH release is adapted to include HARQ-ACK information for SPS PDSCH release associated with one or more SPS PDSCHs. In some embodiments, UE 102 is further configured to determine whether to send the type 3 HARQ-ACK feedback signal 108 triggered by DCI 106 and the HARQ-ACK information associated with SPS release to the base station 104 in the same time slot, and then generate the type 3 HARQ ACK feedback signal 108. In such embodiments, UE 102 is further configured to include the HARQ-ACK information corresponding to the SPS release in the HARQ-ACK bits of the one or more HARQ-ACK bits for SPS PDSCH release in the type 3 HARQ-ACK feedback signal 108.

[0039] More particularly, in embodiments in which the UE 102 is configured with one or more SPS PDSCHs, when an SPS PDSCH release indication for a selected SPS PDSCH of the one or more SPS PDSCHs is received at the UE 102 or when the selected SPS PDSCH of the one or more SPS PDSCHs is released and it is determined that the UE 102 is to transmit HARQ-ACK information for the selected SPS release in the same time slot in which the type 3 HARQ-ACK feedback signal 108 is triggered, the UE 102 is configured to provide, within the type 3 HARQ-ACK feedback signal 108, HARQ-ACK information for the SPS release of the HARQ-ACK bit(s) among the one or more HARQ-ACK bits for the SPS PDSCH release. In some embodiments, the UE 102 is configured to receive an indication of the SPS PDSCH in the release DCI 106. Alternatively, in other embodiments, the UE 102 is configured to receive an indication of the release of the SPS PDSCH via radio resource control (RRC) signaling. After generating the type 3 HARQ-ACK feedback signal 108, the UE 102 is further configured to provide the type 3 HARQ-ACK feedback signal 108 to the BS 104. The BS 204 is configured to receive and process the type 3 HARQ-ACK feedback signal 108.

[0040] In some embodiments, the one or more HARQ-ACK bits for the SPS PDSCH release within the type 3 HARQ-ACK feedback signal 108 include one or more reserved bits for the SPS PDSCH release, which are reserved to respectively include HARQ-ACK information for the one or more SPS PDSCH releases. In such embodiments, no information other than the HARQ-ACK information for the SPS PDSCH release may be included within the one or more reserved bits for the SPS PDSCH release. In some embodiments, the one or more reserved bits for the SPS PDSCH release are appended at the end of the type 3 HARQ-ACK feedback signal 108. Alternatively, in other embodiments, the one or more reserved bits for the SPS PDSCH release are appended at the beginning of the type 3 HARQ-ACK feedback signal 108. In some embodiments, the location / place at which the one or more or more reserved bits for the SPS PDSCH release are to be appended is pre-configured and provided to the UE 102 via higher layer signaling.

[0041] In some embodiments, the BS 104 indicates to the UE 102 the number of reserved bits including one or more reserved bits for SPS PDSCH release to be included in the type 3 HARQ-ACK feedback signal 108. In some embodiments, the BS 104 is configured to provide an indication of the number of reserved bits including one or more reserved bits for SPS PDSCH release via DCI 106 (e.g., DCI format 1_1, DCI format 1_2, etc.). In some embodiments, the BS 104 is configured to directly provide via DCI 106 the number of reserved bits including one or more reserved bits for SPS PDSCH release. In other embodiments, the DCI 106 includes a total SPS release indicator (T-SRI) field (i.e., a dedicated field), and the T-SRI field includes information enabling identification of the total number of reserved bits, which include one or more reserved bits for SPS PDSCH release to be included within the type 3 HARQ ACK feedback signal 108.

[0042] Specifically, in one embodiment, the T-SRI field includes a 1-bit field, and the 1-bit field includes a 1-bit SPS release indicator value indicating whether the reserved bits for SPS PDSCH release are included in the type 3 HARQ ACK feedback signal 108. For example, a "1" for the SPS release indicator value means that the reserved bits for SPS PDSCH release are present in the type 3 HARQ ACK feedback signal 108, and a "0" for the SPS release indicator value means that the reserved bits for SPS PDSCH release are not present in the type 3 HARQ ACK feedback signal 108. If the SPS release indicator value within the T-SRI field indicates that the reserved bits for SPS PDSCH release are present, the UE 102 is configured to determine the total number of reserved bits based on the total number of HARQ processes for downlink (DL) SPS configured for the UE. For example, if the total number of HARQ processes for DL SPS configured for the UE is 2, the total number of reserved bits is 2, and if the total number of HARQ processes for DL SPS configured for the UE is 4, the total number of reserved bits is 4, and so on.

[0043] Alternatively, in another embodiment, the T-SRI field includes a 2-bit field, and the 2-bit field includes a 2-bit SPS release indicator value identifying the total number of reserved bits for SPS PDSCH release. In some embodiments, the 2-bit SPS release indicator value identifies the total number of reserved bits for SPS PDSCH release according to a predefined mapping between the 2-bit SPS release indicator value and the total number of reserved bits for SPS PDSCH release, as shown in Table 1 below.

[0044] T-SRI field Number of reserved bits for SPS PDSCH release 0,0 1 or 5 or 9 or 13 0,1 2 or 6 or 10 or 14 1,0 3 or 7 or 11 or 15 1,1 0 or 4 or 8 or 12

[0045] Table 1: Predefined mapping between 2-bit T-SRI field and total number of reserved bits for SPS PDSCH release

[0046] Table 1 indicates a one-to-many mapping between 2-bit SPS release indicator values and the total number of reserved bits for SPS PDSCH release. Specifically, each value of the T-SRI field is associated with multiple values of the number of reserved bits. In some embodiments, UE 102 is configured to determine a selected value of the number of reserved bits from the multiple values of the number of reserved bits for a 2-bit SPS release indicator value (within the T-SRI field) based on the total number of HARQ processes for DL SPS configured for the UE and, in some embodiments, further based on the actual number of SRS PDSCH release indications received at UE 102. In some embodiments, the total number of reserved bits for SPS PDSCH release is selected to be less than or equal to the total number of HARQ processes for DL SPS configured for the UE. Referring to Table 1, in one exemplary embodiment, if the T-SRI field includes 0, 1 and the total number of HARQ processes for DL SPS configured for the UE is 4, the number of reserved bits is selected to be 2. However, if the T-SRI field includes 0, 1 and the total number of HARQ processes for DL SPS configured for UE 102 is 8, based on Table 1, the number of reserved bits can be 2 or 6. In such embodiments, if the actual number of SRS PDSCH release indications received at UE 102 is 4, the number of reserved bits is selected to be 6.

[0047] As explained above, appending the reserved bits for SPS PDSCH release to the type 3 HARQ-ACK feedback signal 108 increases the HARQ-ACK payload of the type 3 HARQ-ACK feedback signal 108. Thus, in some embodiments, one or more HARQ-ACK bits for SPS PDSCH release are included within the type 3 HARQ-ACK feedback signal 108 without appending additional bits. For example, in one embodiment, one or more HARQ-ACK bits for SPS PDSCH release within the type 3 HARQ-ACK feedback signal 108 correspond to bit positions associated with the HARQ processes of the corresponding SPS PDSCH within the type 3 HARQ-ACK feedback signal 108. More particularly, when the UE 102 is configured with a set of HARQ processes for DL SPS, the type 3 HARQ-ACK feedback signal 108 includes a set of bit positions configured to convey HARQ-ACK information for a set of SPS PDSCHs respectively associated with the feedback signal. In some embodiments, the HARQ-ACK bits for SPS PDSCH release for a set of SPS PDSCHs are respectively mapped to bit positions associated with the set of SPS PDSCHs. In another embodiment, one or more HARQ-ACK bits for SPS PDSCH release within the type 3 HARQ-ACK feedback signal 108 correspond to bit positions respectively associated with one or more HARQ processes, each HARQ process being identified by a corresponding HARQ process identifier (HPI). In some embodiments, the HPI associated with one or more HARQ processes whose bit positions are to be used to provide HARQ-ACK information for SPS PDSCH release is indicated to the UE 202 via radio resource control (RRC) signaling.

[0048] Figure 2a FIG. 4 shows a simplified block diagram of a wireless communication system 200 according to one embodiment of the present disclosure. In some embodiments, the wireless communication system 200 supports group-based HARQ-ACK feedback. The wireless communication system 200 includes a user equipment (UE) 202 and a base station (BS) 204. However, in other embodiments, the wireless communication system 200 may include multiple UEs, which are not shown here for clarity. In some embodiments, the base station 204 is equivalent to an eNodeB in an LTE system, a gNodeB in a 5G new radio (NR) system, etc. In some embodiments, the UE 202 may include a mobile phone, a tablet computer, an Internet of Things (IoT) device, a vehicle-to-everything (V2X) UE, etc. The UE 202 and the base station 204 are configured to communicate with each other via a communication medium (e.g., air).

[0049] In some embodiments, BS 204 is configured to configure a set of HARQ processes for UE 202. In some embodiments, each HARQ process in the set of HARQ processes is identified by a corresponding HARQ process identifier (HPI). In some embodiments, BS 204 is further configured to group the set of HARQ processes into a plurality of HARQ process groups (HPGs). In some embodiments, each HPG in the plurality of HPGs includes one or more HARQ processes in the set of HARQ processes configured for UE 202. For example, Figure 2b A set of 16 HARQ processes identified by HPIs 0 to 15 is shown. In addition, the 16 HARQ processes are grouped into 3 HPGs: HPG#0, HPG#1, and HPG#3. The number of HPIs included within each HPG and the configured HPGs may be different in different embodiments. In some embodiments, the set of HARQ processes is grouped to form a plurality of HPGs according to the reliability requirements of the associated service type. For example, HPG#0 includes HPIs 0 / 1 / 2 / 3, which may be intended for ultra-reliable and low-latency communication (URLLC) with the highest reliability requirements. Similarly, HPG#1 and HPG#2 may be associated with other reliability requirements. In some embodiments, each HPG may be restricted for data streams or logical channel IDs with the same priority.

[0050] In addition, in some embodiments, as Figure 2c shown, the set of HARQ processes may be grouped to form a plurality of HPGs based on the priority class assigned to each HARQ process in the set of HARQ processes associated with the UE. In such embodiments, each HPG is associated with a corresponding priority class index. In some embodiments, the priority class index of the HPG corresponds to the priority class index associated with one or more HARQ processes within the HPG. For example, HPIs 0 / 1 / 8 / 9 have the same priority class, such as priority class index 0, and are grouped into one HPG with priority class index 0. Similarly, HPIs 2 / 3 / 4 / 5 / 6 / 7 / 10 / 11 / 12 / 13 / 14 / 15 have the same priority class, such as priority class index 1, and are grouped into another HPG with priority class index 1. In addition, other different criteria for grouping the set of HARQ processes to form a plurality of HPGs are also contemplated within the scope of the present disclosure. In some embodiments, each HPG in the plurality of HPGs is identified by an HPG identifier (ID). In embodiments where the grouping is based on priority classes, the HPG ID may include the corresponding priority class index.

[0051] After configuring a set of HARQ processes as multiple HPGs, the BS 204 is configured to generate an HPG configuration signal 206. In some embodiments, the HPG configuration signal 206 includes information for a plurality of HARQ process groups (HPGs) configured for the UE 202. The BS 204 is further configured to send the HPG configuration signal 206 to the UE 202. Figure 3a And Figure 3b depicts two possible signal configurations for the HPG configuration signal 206. Specifically, in Figure 3a , a corresponding plurality of HARQProcessGroup fields are used to indicate the multiple HPGs and the HARQ processes associated with the multiple HPGs. In some embodiments, the HARQProcessGroup field identifies the HPG ID and indicates which HARQ processes are included in the HARQ process group (HPG). Each HARQProcessGroup field includes bits corresponding to a set of HARQ processes configured for the UE 202. Each bit has a value of 0 (indicating that the corresponding HARQ process is not included in the HPG) or a value of 1 (indicating that the corresponding HARQ process is included in the HPG).

[0052] In addition, in Figure 3b , a corresponding plurality of PriorityList fields are used to indicate the multiple HPGs and the HARQ processes associated with the multiple HPGs. This type of signaling is applicable when forming multiple HPGs based on the priority levels of the associated HARQ processes, as explained above in Figure 2c . In some embodiments, the PriorityList field identifies the HPG with a selected priority index and one or more HARQ processes associated with that priority index. However, other configurations for the HPG configuration signal 206 are also envisioned within the scope of the present disclosure. After receiving the HPG configuration signal 206 from the BS 204, the UE 202 is configured to receive and process the HPG configuration signal 206. In some embodiments, the UE 202 is configured to determine information for a plurality of HARQ process groups (HPGs) configured for the UE 202 based on processing the HPG configuration signal 206.

[0053] Return to reference Figure 2a, in some embodiments, BS 204 is further configured to provide downlink control information (DCI) 208 to UE 202. In some embodiments, DCI 208 is configured to trigger a hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback signal 210 from UE 202. In some embodiments, HARQ-ACK feedback signal 210 is configured to include HARQ-ACK information associated with one or more HARQ processes configured for UE 202. In some embodiments, DCI 208 includes information on physical uplink control channel (PUCCH) / physical uplink shared channel (PUSCH) resources to be used by UE 102 for transmitting HARQ-ACK feedback signal 210. In some embodiments, HARQ-ACK feedback signal 210 includes type 3 HARQ-ACK feedback or type 3 HARQ-ACK codebook. In such embodiments, DCI 208 includes a one-shot HARQ-ACK frequent field, and the value associated with this field provides an indication to UE 102 to trigger type 3 HARQ-ACK feedback. Alternatively, in other embodiments, HARQ-ACK feedback signal 210 may include other types of HARQ-ACK signals, e.g., type 1 HARQ-ACK feedback signal or type 1 HARQ-ACK codebook. In some embodiments, type 1 HARQ-ACK feedback signal may be configured by radio resource control (RRC) signaling. In some embodiments, DCI 208 is configured to trigger HARQ-ACK feedback signal 210 from UE 202 in response to a physical downlink shared channel (PDSCH) scheduled by DCI 208. Alternatively, in other embodiments, e.g., for type 3 HARQ-ACK feedback, DCI 208 may trigger HARQ-ACK feedback signal 210 without scheduling a PDSCH for UE 202. In some embodiments, DCI 208 further includes information identifying (through HPG configuration signal 206) one or more of the plurality of HPGs configured for UE 202, and the HARQ-ACK feedback information of the one or more HPGs is to be included in HARQ-ACK feedback signal 210 triggered by DCI 208.

[0054] Once the BS 202 provides / sends the DCI 208 to the UE 202, the UE 202 is configured to receive and process the DCI 208. After processing the DCI 208, the UE 202 is configured to identify one or more HPGs identified in the DCI 208. In addition, the UE 202 is configured to generate a HARQ-ACK feedback signal 210 that includes HARQ-ACK feedback information for HARQ processes associated with one or more HPGs (indicated by the DCI 208). In such embodiments, the HARQ-ACK feedback signal 210 will not include HARQ-ACK feedback information for HARQ processes associated with other HPGs within a plurality of HPGs different from the one or more HPGs indicated in the DCI 208. Subsequently, the UE 202 is configured to provide / send the HARQ-ACK feedback signal 210 to the BS 204.

[0055] The DCI 208 can be configured to indicate, in different embodiments, in different ways to the UE 202 information identifying one or more HPGs out of a plurality of HPGs configured for the UE 202. In a first embodiment, an HPG request field including an HPG request field value identifying one or more HPGs is included as part of the DCI 208. In some embodiments, the HPG request field value is mapped to one or more HPGs and serving cells according to a predefined mapping as shown in Table 2 below. Specifically, Table 2 indicates a predefined mapping between the HPG request field value and a pair of serving cell HPGs.

[0056] Value of the HPG request field Detailed implementation mode 00 The first set configured by the higher layer {serving cell, HPG} 01 The second set configured by the higher layer {serving cell, HPG} 10 The third set configured by the higher layer {serving cell, HPG} 11 The fourth set configured by the higher layer {serving cell, HPG}

[0057] Table 2: Predefined mapping between HPG request field values and HPGs.

[0058] Table 2 above indicates 2-bit values for the HPG request field. However, in other embodiments, the value of the HPG request field can have more or fewer than 2 bits, depending on the number of HPGs configured. In addition, the HPGs associated with each set can be different in different embodiments. In such embodiments, the UE 202 is configured to determine one or more HPGs based on processing the DCI 208, according to the predefined mapping between the HPG request field value and one or more HPGs, as given in Table 2 above. For example, if the HPG request field value indicated in the DCI 208 is 01, the UE 202 is configured to provide HARQ-ACK information associated with the 2nd set of HPGs from Table 2 as part of the HARQ-ACK feedback signal 210.

[0059] In a second embodiment, DCI 208 includes cyclic redundancy check (CRC) bits scrambled by a predefined HPG sequence, e.g., [w0, w1 …… w15]. In some embodiments, the predefined HPG sequence identifies one or more HPGs, and the HARQ-ACK feedback information of the one or more HPGs is to be included in the HARQ-ACK feedback signal 210. In some embodiments, the predefined HPG sequence identifies one or more HPGs based on a predefined mapping between a predefined HPG sequence and one or more HPGs among a plurality of HPGs. Table 3 shows an exemplary mapping between the predefined HPG sequence and one or more HPGs.

[0060] HPG sequence value [w0, w1, w2, w3……w15] 00 [0,0,0,0....,0] 01 [0,1,0,1....,0] 10 [1,0,1,0....,1] 11 [1,1,1,1....,1]

[0061] Table 3: Predefined mapping between the predefined HPG sequence and the HPG sequence value

[0062] Specifically, Table 3 provides a mapping between the predefined sequence and the corresponding HPG sequence value. In some embodiments, the HPG sequence value is mapped to one or more HPGs based on the predefined mapping in Table 4 below.

[0063] HPG sequence value Detailed implementation mode 00 The first set configured by the higher layer {serving cell, HPG} 01 The second set configured by the higher layer {serving cell, HPG} 10 The third set configured by the higher layer {serving cell, HPG} 11 The fourth set configured by the higher layer {serving cell, HPG}

[0064] Table 4: Predefined mapping between the predefined HPG sequence and the HPGs.

[0065] In such embodiments, the UE 202 is configured to descramble the CRC bits to determine the predefined HPG sequence, and based on the predefined HPG sequence, determine one or more HPGs according to the predefined mapping between the predefined HPG sequence and one or more HPGs. For example, if the predefined sequence is determined to be [0, 1, 0, 1...., 0], the UE 202 identifies the corresponding HPG sequence value as "01" according to Table 3 above, and determines one or more HPGs associated with the HPG sequence value "01" according to Table 4 above. However, in other embodiments, Table 3 may include a direct mapping between the predefined HPG sequence and one or more HPGs.

[0066] In a third embodiment, when the packet is based on a priority class index, DCI 208 further includes a priority indicator field, and the priority indicator field includes information about a selected priority class index (e.g., Figure 2c the priority class index 0 in Figure 2cin HPI 0 / 1 / 8 / 9). In addition, UE 202 is configured to generate a HARQ-ACK feedback signal 210 that includes HARQ feedback information for one or more HARQ processes associated with a selected priority class index.

[0067] Return reference Figure 2a , in some embodiments, BS 204 is further configured to generate a HARQ process reconfiguration signal 212 and provide it to UE 202. In some embodiments, the HARQ process reconfiguration signal 212 includes information for reconfiguring HARQ processes associated with one or more of the plurality of HPGs configured for UE 202 (e.g., via the HPG configuration signal 206). In some embodiments, the reconfiguration information is included in a HARQ reconfiguration medium access control (MAC) control element (CE) within the HARQ process reconfiguration signal 208. In some embodiments, a dedicated logical channel ID (LCID) in the MAC header or sub-header is used to identify the HARQ reconfiguration MAC CE. In a first embodiment, the HARQ process reconfiguration signal 212 includes one or more HARQ reconfiguration MAC CEs, each HARQ reconfiguration MAC CE associated with a respective HPG identifier (ID) that identifies an HPG of the plurality of HPGs configured for UE 202. Each HARQ reconfiguration MAC CE (as Figure 4a shown) has a fixed size and includes a plurality of octets that contain the respective HPG ID and a set of H fields corresponding to the set of HARQ processes configured for the UE. In some embodiments, each H field in the set of H fields identifies a HARQ process in the set of HARQ processes configured for UE202. In some embodiments, the value associated with each H field in the set of H fields identifies one or more HARQ processes included within the HPG identified by the respective HPG ID.

[0068] Figure 4a illustrates an exemplary HARQ reconfiguration MAC CE 400 associated with the first embodiment. The HARQ reconfiguration MAC CE 400 is associated with a selected HPG identified by the HPG ID. The HARQ reconfiguration MAC CE 400 has 3 octets: octet #1, octet #2, and octet #3. The HARQ reconfiguration MAC CE 400 also includes 16 H fields (which may be different in other embodiments) corresponding to the set of 16 HARQ processes configured for UE 202. Each H field in the H fields is identified as H i , where i identifies the corresponding HARQ process. If H iIf the field is set to "1", it can identify that the corresponding HARQ process is included in the HPG identified by the HPGID. Alternatively, if the i field is set to "0", it can identify that the corresponding HARQ process is excluded from the HPG identified by the HPGID. In some embodiments, the excluded HARQ processes are to be added to the default HPG. In some embodiments, the default HPG is configured by a higher layer.

[0069] In a second embodiment, the HARQ process reconfiguration signal 212 includes a HARQ reconfiguration MAC CE that includes one or more sets of H fields respectively associated with one or more of the multiple HPGs configured for the UE 202. The HARQ reconfiguration MAC CE has a fixed size and includes a plurality of octets that include one or more sets of H fields. Each set of H fields in the one or more sets of H fields corresponds to a set of HARQ processes configured for the UE. Specifically, each H field within the set of H fields in the one or more sets of H fields identifies a HARQ process within the set of HARQ processes configured for the UE 202. In some embodiments, the value associated with each H field in the set of H fields associated with an HPG identifies one or more HARQ processes included within the HPG.

[0070] Figure 4b An exemplary HARQ reconfiguration MAC CE 450 associated with the second embodiment is shown. The HARQ reconfiguration MAC CE 450 is associated with N HPGs identified by HPG IDs HPG#0…HPG#N-1. The HARQ reconfiguration MAC CE 400 also includes 16 H fields per HPGID (which may be different in other embodiments), where the 16 H fields (which may be different in other embodiments) correspond to a set of 16 HARQ processes configured for the UE 202. Each H field among the H fields is identified as H g,i, , where g identifies the HPGID and i identifies the corresponding HARQ process. If the H g,i, field is set to "1", it can identify that the HARQ process i is included in the HPG g. Alternatively, if the H g,i, field is set to "0", it can identify that the HARQ process i is excluded from the HPG g. Return reference Figure 2a , the UE 202 is further configured to receive and process the HARQ process reconfiguration signal 208. After processing the HARQ process reconfiguration signal 208, the UE 202 is configured to determine a plurality of updated HPGs configured for the UE 202.

[0071] Figure 5 FIG. 1 shows a simplified block diagram of a wireless communication system 500 in accordance with one embodiment of the present disclosure. In some embodiments, the wireless communication system 500 facilitates providing a new data indicator (NDI) as part of HARQ-ACK feedback. The wireless communication system 500 includes a user equipment (UE) 502 and a base station (BS) 504. However, in other embodiments, the wireless communication system 500 may include multiple UEs, which are not shown here for clarity. In some embodiments, the base station 504 is equivalent to an eNodeB in an LTE system, a gNodeB in a 5G new radio (NR) system, etc. In some embodiments, the UE 502 may include a mobile phone, a tablet computer, an Internet of Things (IoT) device, a vehicle-to-everything (V2X) UE, etc. The UE 502 and the base station 504 are configured to communicate with each other via a communication medium (e.g., air).

[0072] In some embodiments, the UE 502 is configured with a set of HARQ processes. In some embodiments, the set of HARQ processes is configured via radio resource control (RRC) signaling. In some embodiments, the BS 504 is configured to send / provide a new data indicator (NDI) configuration signal 506 to the UE 502. In some embodiments, the NDI configuration signal 506 is configured to configure the UE 502 to include the most recent NDI value detected by the UE 502 for one or more HARQ processes, along with HARQ-ACK information for the corresponding HARQ processes, as part of a HARQ-ACK feedback signal (e.g., HARQ-ACK feedback signal 510). In some embodiments, the NDI configuration signal 506 includes radio resource configuration (RRC) signaling. The UE 502 is configured to receive and process the NDI configuration signal 506.

[0073] In some embodiments, the BS 504 is further configured to provide downlink control information (DCI) 508 to the UE 502. The DCI 508 is configured to trigger a HARQ-ACK feedback signal 510 from the UE 502. In some embodiments, the DCI 508 includes information on physical uplink control channel (PUCCH) / physical uplink shared channel (PUSCH) resources to be used by the UE 502 for transmitting the HARQ-ACK feedback signal 510. In some embodiments, the HARQ-ACK feedback signal 510 includes type 3 HARQ-ACK feedback. In such embodiments, the DCI 508 includes a one-shot HARQ-ACK occasion field, and the value associated with this field provides an indication to the UE 502 to trigger type 3 HARQ-ACK feedback. Alternatively, in other embodiments, the HARQ-ACK feedback signal 510 may include other types of HARQ-ACK signals, e.g., type 1 HARQ-ACK feedback signals. In some embodiments, the DCI 508 is configured to trigger the HARQ-ACK feedback signal 510 from the UE 502 in response to a physical downlink shared channel (PDSCH) scheduled by the DCI 508. Alternatively, in other embodiments, e.g., for type 3 HARQ-ACK feedback, the DCI 508 may trigger the HARQ-ACK feedback signal 510 without scheduling a PDSCH for the UE 502. The UE 502 is configured to receive and process the DCI 508. In some embodiments, the UE 502 is further configured to generate the HARQ-ACK feedback signal 510 in response to processing the DCI 508. In some embodiments, the HARQ-ACK feedback signal 510 includes HARQ-ACK feedback information for one or more HARQ processes associated with the UE 502, and the NDI value (i.e., the most recent NDI value) detected by the UE 502 for the corresponding one or more HARQ processes. Subsequently, the UE 502 is configured to provide / transmit the HARQ-ACK feedback signal 510 to the BS 504. The BS 504 is further configured to receive and process the HARQ-ACK feedback signal 510.

[0074] In some embodiments, the UE 502 detects the NDI value for a corresponding HARQ process from the DCI (or the PDSCH for the HARQ process) that schedules the corresponding HARQ process. In some embodiments, including the NDI value as part of the HARQ-ACK feedback signal 510 facilitates the BS 504 in identifying any mismatch between the data provided by the BS 504 and the corresponding HARQ-ACK information provided by the UE 502. In some embodiments, the UE 502 may be configured with multiple HARQ process groups (HPGs), as described above with respect to Figure 2aAs explained. In such embodiments, if the DCI 508 includes information identifying one or more of the plurality of HPGs (similar to the DCI 208 in Figure 2a ), then the HARQ-ACK feedback signal 510 is configured to include the most recent new data indicator (NDI) value detected by the UE 502 for each HARQ process associated with one or more of the HPGs identified by the DCI 508.

[0075] Reference Figure 6 , shows a block diagram of an apparatus 600 that can be employed at a base station (BS), eNodeB, gNodeB, or other network device in accordance with various aspects described herein. In some embodiments, the apparatus 900 can be included within the BS 104, BS 204, and BS 504 in the above embodiments. However, in other embodiments, the apparatus 600 can be included within any gNodeB associated with a new radio (NR) system. The apparatus 600 can include: one or more processors 610 (e.g., one or more baseband processors, such as one or more baseband processors discussed in conjunction with Figure 15 and / or Figure 16 ), including processing circuitry and associated interfaces (e.g., one or more interfaces discussed in conjunction with Figure 16 ); transceiver circuitry 620 (e.g., the transceiver circuitry can include circuitry for one or more wired connections and / or portions or all of the RF circuitry 1506, which can include a transmitter circuitry (e.g., associated with one or more transmit chains) or a receiver circuitry (e.g., associated with one or more receive chains), where the transmitter circuitry and the receiver circuitry can employ common circuit elements, different circuit elements, or a combination thereof); and a memory 630 (which can include any of a variety of storage media and can store instructions and / or data associated with one or more of the processor 610 or the transceiver circuitry 620).

[0076] Specifically, the term memory is intended to include installation media such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media such as hard disk drives or optical storage devices; registers, or other similar types of memory elements, etc. Memory media may also include other types of memory or combinations thereof. In various aspects, apparatus 900 may be included within an evolved universal terrestrial radio access network (E-UTRAN) Node B (evolved Node B, eNodeB, or eNB), next-generation Node B (gNodeB or gNB), or other base station or TRP (transmit / receive point) in a wireless communication network. In some aspects, processor 610, transceiver circuitry 620, and memory 630 may be included in a single device, while in other aspects, they may be included in different devices, such as part of a distributed architecture.

[0077] Reference Figure 7 , a block diagram of apparatus 700 capable of being employed at a user equipment (UE) or other network device (e.g., IoT device) in accordance with various aspects described herein is shown. In some embodiments, apparatus 1000 may be included within UE 102, UE 202, and UE 502 in the above embodiments. However, in other embodiments, apparatus 700 may be included within any UE associated with a new radio (NR) system. Apparatus 700 may include one or more processors 710 (e.g., one or more baseband processors such as one or more baseband processors discussed in conjunction with Figure 15 and / or Figure 16 , including processing circuitry and associated interfaces (e.g., in conjunction with Figure 16one or more interfaces discussed); a transceiver circuit 720 (e.g., including some or all of the RF circuit 1506, which may include a transmitter circuit (e.g., associated with one or more transmit chains) and / or a receiver circuit (e.g., associated with one or more receive chains), and the transmitter circuit and the receiver circuit may employ common circuit elements, different circuit elements, or a combination thereof); and a memory 730 (which may include any of a variety of storage media and may store instructions and / or data associated with one or more of the processor 710 or the transceiver circuit 720). Specifically, the term memory is intended to include installation media, such as, for example, CD-ROM, floppy disk, or magnetic tape device; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, such as, for example, hard disk drive or optical storage device; registers, or other similar types of memory elements, etc. Memory media may also include other types of memory or combinations thereof. In various aspects, the apparatus 1000 may be included within a user equipment (UE).

[0078] In various aspects discussed herein, signals and / or messages may be generated and output for transmission, and / or the transmitted messages may be received and processed. Depending on the type of signal or message generated, output for transmission (e.g., by the processor 710) may include one or more of the following operations: generating a set of associated bits indicative of the content of the signal or message, encoding (e.g., may include adding a cyclic redundancy check (CRC) and / or encoding via turbo codes, low density parity check (LDPC) codes, truncated convolutional codes (TBCC), etc.), scrambling (e.g., based on a scrambling seed), modulating (e.g., via one of binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), or some form of quadrature amplitude modulation (QAM), etc.) and / or resource mapping (e.g., mapping to a scheduled set of resources, mapping to a set of time and frequency resources licensed for uplink transmission, etc.). Depending on the type of signal or message received, processing (e.g., by the processor 710) may include one or more of the following operations: identifying the physical resources associated with the signal / message, detecting the signal / message, resource element group deinterleaving, demodulating, descrambling, and / or decoding.

[0079] Figure 8 A flowchart of a method 800 of a UE associated with a wireless communication system supporting SPS release along with a type 3 HARQ-ACK codebook configuration according to an embodiment of the present disclosure is shown. Reference is made herein Figure 7 to the apparatus 700 in Figure 1 to explain the method 800. In some embodiments, the apparatus 700 may be included within theFigure 1 The method 800 will be explained with reference to the wireless communication system 100 in Figure 1 . At 802, one or more processors 710 are used to process downlink control information (DCI) (e.g., Figure 1 DCI 106 in Figure 1 ) received from a base station (e.g., Figure 1 BS 104 in Figure 1 ) associated with the UE. In some embodiments, the DCI includes an indication for triggering a type 3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal (e.g., Figure 1 type 3 HARQ-ACK feedback signal 108 in Figure 1 ).

[0080] At 804, one or more processors 710 are used to generate a type 3 HARQ ACK feedback signal based on the processed DCI. In some embodiments, the type 3 HARQ ACK feedback signal includes one or more HARQ-ACK bits for a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release. In some embodiments, each of the one or more HARQ-ACK bits for the SPS PDSCH release is adapted to include HARQ-ACK information for the SPS PDSCH release associated with the UE. At 806, one or more processors 710 are used to provide the type 3 HARQ-ACK feedback signal to the base station.

[0081] Figure 9 FIG. shows a flowchart of a method 900 of a base station (BS) associated with a wireless communication system supporting SPS release along with a type 3 HARQ-ACK codebook configuration according to an embodiment of the present disclosure. The method 900 will be explained herein with reference to Figure 6 the apparatus 600 in Figure 6 . In some embodiments, the apparatus 600 may be included within Figure 1 BS 104 in Figure 1 . Accordingly, the method 900 will be further explained with reference to Figure 1 the wireless communication system 100 in Figure 1 . At 902, one or more processors 610 are used to provide downlink control information (DCI) (e.g., Figure 1 DCI 106 in Figure 1 ) to a user equipment (UE) (e.g., Figure 1 UE 102 in Figure 1 ) associated with the base station. In some embodiments, the DCI includes an indication to trigger a type 3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal to the UE (e.g., Figure 1Indication of the Type 3 HARQ-ACK feedback signal 108) in. At 904, one or more processors 610 are used to process the Type 3 HARQ ACK feedback signal received from the UE in response to providing DCI. In some embodiments, the Type 3 HARQ ACK feedback signal includes one or more HARQ-ACK bits for the release of the semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH). In some embodiments, each of the one or more HARQ-ACK bits for the SPS PDSCH release is adapted to include HARQ-ACK information for the SPS PDSCH release associated with the UE.

[0082] Figure 10 FIG. 1000 is a flowchart of a method of a UE associated with a wireless communication system supporting group-based HARQ-ACK feedback according to an embodiment of the present disclosure. This is described herein with reference to Figure 7 the apparatus 700 in. In some embodiments, the apparatus 700 may be included in the Figure 2a UE 202 in. Thus, further reference is made to Figure 2a the wireless communication system 200 in to describe the method 1000. At 1002, one or more processors 710 are used to receive a hybrid automatic repeat request process group (HPG) configuration signal (e.g., Figure 2a the HPG configuration signal 206 in) from a base station (e.g., BS 204) associated with the UE. In some embodiments, the HPG configuration signal includes information of a plurality of HARQ process groups (HPGs), each HPG including one or more HARQ processes in a set of HARQ processes configured for the UE.

[0083] At 1004, based on processing the HPG configuration signal, one or more processors 710 are used to determine a plurality of HPGs associated with the set of HARQ processes configured for the UE. At 1006, one or more processors 710 are used to receive downlink control information (DCI) (e.g., Figure 2a the DCI 208 in) from the base station. In some embodiments, the DCI includes information identifying one or more HPGs among the plurality of HPGs, and the HARQ-ACK feedback information of the one or more HPGs is to be included in a HARQ-ACK feedback signal (e.g., Figure 2a the HARQ-ACK feedback signal 210 in) triggered by the DCI. At 1008, one or more processors 710 are used to generate a HARQ-ACK feedback signal including HARQ-ACK feedback information of HARQ processes associated with one or more HPGs. At 1010, one or more processors 710 are used to send the HARQ-ACK feedback signal to the base station.

[0084] Figure 11 FIG. 1100 is a flowchart of a method for a base station (BS) associated with a wireless communication system supporting group-based HARQ-ACK feedback, in accordance with one embodiment of the present disclosure. Method 1100 is explained herein with reference to Figure 6 apparatus 600 in FIG. 6. In some embodiments, apparatus 600 may be included within the Figure 2a BS 204 in FIG. 2. Thus, method 1100 is further explained with reference to Figure 2a wireless communication system 200 in FIG. 2. At 1102, a hybrid automatic repeat request process group (HPG) configuration signal (e.g., Figure 2a HPG configuration signal 206 in FIG. 6) is sent to a user equipment (UE) (e.g., Figure 2a UE 202 in FIG. 2) associated with the base station, using one or more processors 610. In some embodiments, the HPG configuration signal includes information of a plurality of HARQ process groups (HPGs), each HPG including one or more HARQ processes from a set of HARQ processes configured for the UE.

[0085] At 1104, a downlink control information (DCI) (e.g., Figure 2a DCI 208 in FIG. 6) is sent to the UE, using one or more processors 610. In some embodiments, the DCI includes information identifying one or more HPGs among the plurality of HPGs, and the HARQ-ACK feedback information of the one or more HPGs is to be included in a HARQ-ACK feedback signal (e.g., Figure 2a HARQ-ACK feedback signal 210 in FIG. 6) triggered by the DCI. At 1106, a HARQ-ACK feedback signal is received from the UE, using one or more processors 610. In some embodiments, the HARQ-ACK feedback signal includes HARQ-ACK feedback information of HARQ processes associated with one or more HPGs.

[0086] Figure 12 FIG. 1200 is a flowchart of a method for a user equipment (UE) associated with a wireless communication system supporting a new data indicator (NDI) as part of HARQ-ACK feedback, in accordance with one embodiment of the present disclosure. Method 1200 is explained herein with reference to Figure 7 apparatus 700 in FIG. 7. In some embodiments, apparatus 700 may be included within the Figure 5 UE 502 in FIG. 5. Thus, method 1200 is further explained with reference to Figure 5 wireless communication system 500 in FIG. 5. At 1202, a signal is received from a base station (e.g., Figure 5The BS 504 therein receives a new data indicator (NDI) configuration signal (e.g., Figure 5 the NDI configuration signal 506 therein). In some embodiments, the NDI configuration signal is configured to configure the UE to include the most recent NDI value detected by the UE for one or more HARQ processes, along with HARQ-ACK information for the corresponding HARQ processes, as part of the HARQ-ACK feedback signal. At 1204, downlink control information (DCI) (e.g., Figure 5 the DCI 508 therein) is received from a base station (BS) using one or more processors 710. In some embodiments, the DCI is configured to trigger a HARQ-ACK feedback signal (e.g., Figure 5 the HARQ-ACK feedback signal 510 therein). At 1206, a HARQ-ACK feedback signal is generated using one or more processors 710. In some embodiments, the HARQ-ACK feedback signal includes HARQ-ACK feedback information for one or more HARQ processes associated with the UE, and the NDI value detected by the UE for the corresponding one or more HARQ processes. At 1208, the HARQ-ACK feedback signal is sent to the BS using one or more processors 710.

[0087] Figure 13 FIG. 1300 is a flow chart of a method for a base station (BS) associated with a wireless communication system that supports a new data indicator (NDI) as part of HARQ-ACK feedback, in accordance with one embodiment of the present disclosure. This is explained herein with reference to Figure 6 apparatus 600 therein. In some embodiments, apparatus 1300 may be included within the Figure 5 BS 504 therein. Thus, method 1300 is further explained with reference to Figure 5 wireless communication system 500 therein. At 1302, a new data indicator (NDI) configuration signal (e.g., Figure 5 the NDI configuration signal 506 therein) is sent to a user equipment (UE) (e.g., Figure 5 the UE 502 therein) using one or more processors 610. In some embodiments, the NDI configuration signal is configured to configure the UE to include the most recent NDI value detected by the UE for one or more HARQ processes, along with HARQ-ACK information for the corresponding HARQ processes, as part of the HARQ-ACK feedback signal. At 1304, downlink control information (DCI) (e.g., Figure 5 the DCI 508 therein) is sent to the UE using one or more processors 610. In some embodiments, the DCI is configured to trigger a HARQ-ACK feedback signal from the UE (e.g., Figure 5The HARQ-ACK feedback signal in (510). At 1306, the HARQ-ACK feedback signal is received from the UE using one or more processors 610. In some embodiments, the HARQ-ACK feedback signal includes HARQ-ACK feedback information for one or more HARQ processes associated with the UE, and the NDI value detected by the UE for the corresponding one or more HARQ processes.

[0088] Although the methods are shown and described above as a series of actions or events, it should be understood that the order of such shown actions or events should not be construed as limiting. For example, some actions may occur in a different order and / or concurrently with other actions or events other than those shown and / or described herein. Additionally, not all of the shown actions may be required to implement one or more aspects or embodiments disclosed herein. Further, one or more of the actions shown herein may be carried out in one or more separate actions and / or phases.

[0089] The embodiments described herein may be implemented into a system using any appropriately configured hardware and / or software. Figure 14 The architecture of a system 1400 including a core network (CN) 1420 such as a fifth generation (5G) CN (5GC) is shown according to various embodiments. The system 1400 is shown to include a UE 1401, which may be the same as or similar to one or more other UEs discussed herein; a 3rd Generation Partnership Project (3GPP) radio access network (radio AN or RAN) or other (e.g., non-3GPP) AN, (R)AN 210, which may include one or more RAN nodes (e.g., evolved Node B (eNB)), next generation Node B (gNB and / or other nodes) or other nodes or access points; and a data network (DN) 203, which may be, for example, a carrier service, Internet access or a third-party service; and a fifth generation core network (5GC) 1420. The 5GC 1420 may include one or more of the following functions and network components: an authentication server function (AUSF) 1422; an access and mobility management function (AMF) 1421; a session management function (SMF) 1424; a network exposure function (NEF) 1423; a policy control function (PCF) 1426; a network repository function (NRF) 1425; a unified data management (UDM) 1427; an application function (AF) 1428; a user plane (UP) function (UPF) 1402; and a network slice selection function (NSSF) 1429.

[0090] The UPF 1402 can act as an anchor point for mobility within and between RATs, an external protocol data unit (PDU) session point interconnected with the DN 1403, and a branching point for supporting multi-homed PDU sessions. The UPF 1402 can also perform packet routing and forwarding, perform packet inspection, perform the user plane part of policy rules, legally intercept packets (UP collection), perform traffic usage reporting, perform QoS processing on the user plane (e.g., packet filtering, gating, uplink (UL) / downlink (DL) rate enforcement), perform uplink traffic verification (e.g., service data flow (SDF) to QoS flow mapping), perform transport-level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 1402 can include an uplink classifier for supporting routing traffic to the data network. The DN 1403 can represent various network operator services, Internet access, or third-party services. The DN 1403 can include or be similar to an application server. The UPF 1402 can interact with the SMF 1424 via the N4 reference point between the SMF 1424 and the UPF 1402.

[0091] The AUSF 1422 can store data for authenticating the UE 1401 and handle authentication-related functions. The AUSF 1422 can facilitate a common authentication framework for various access types. The AUSF 1422 can communicate with the AMF 1421 via the N12 reference point between the AMF 1421 and the AUSF 1422; and can communicate with the UDM 1427 via the N13 reference point between the UDM 1427 and the AUSF 1422. Additionally, the AUSF 1422 can expose an Nausf service-based interface.

[0092] The AMF 1421 can be responsible for registration management (e.g., responsible for registering the UE 1401, etc.), connection management, reachability management, mobility management, and legal interception of AMF-related events, and access authentication and authorization. The AMF 1421 can be the termination point of the N11 reference point between the AMF 1421 and the SMF 1424. The AMF 1421 can provide transmission for SM messages between the UE 1401 and the SMF 1424 and act as a transparent proxy for routing SM messages. The AMF 1421 can also be for the UE 1401 and the short message service (SMS) function (SMSF)( Figure 14Provide transmission of SMS messages between (not shown in the figure). The AMF 1421 can act as a Security Anchor Function (SEAF), which can include interactions with the AUSF 1422 and the UE 1401 and / or receive intermediate keys established due to the UE 1401 authentication process. In the case of using Universal Subscriber Identity Module (USIM)-based authentication, the AMF 1421 can retrieve security material from the AUSF 1422. The AMF 1421 can also include a Single Connectivity Mode (SCM) function that receives keys from the SEA for deriving access network-specific keys. In addition, the AMF 1421 can be a termination point of the Radio Access Network (RAN) control plane (CP) interface, and this AMF can include or can be the N2 reference point between the (R)AN 1410 and the AMF 1421; and the AMF 1421 can be a termination point of the non-access stratum (NAS) (N1) signaling and perform NAS encryption and integrity protection.

[0093] The AMF 1421 can also support NAS signaling with the UE 1401 through the non-3GPP (N3) Interworking Function (IWF) interface. The N3IWF can be used to provide access to untrusted entities. The N3IWF can be a termination point of the N2 interface between the (R)AN 1410 and the AMF 1421 in the control plane, and can be a termination point of the N3 reference point between the (R)AN 1410 and the UPF 1402 in the user plane. Therefore, the AMF 1421 can process N2 signaling for PDU sessions and QoS from the SMF 1424 and the AMF 1421, encapsulate / decapsulate packets for Internet Protocol (IP) security (IPSec) and N3 tunnels, mark N3 user plane packets on the uplink, and perform QoS corresponding to the N3 packet marking, thus taking into account the QoS requirements associated with such markings received through N2. The N3IWF can also relay uplink and downlink control plane NAS signaling between the UE 1401 and the AMF 1421 via the N1 reference point between the UE 1401 and the AMF 1421, and relay uplink and downlink user plane packets between the UE 1401 and the UPF 1402. The N3IWF also provides a mechanism for establishing an IPsec tunnel with the UE 1401. The AMF 1421 can present a Namf service-based interface and can be a termination point of the N14 reference point between two AMF 1421s and the N17 reference point between the AMF 1421 and the 5G Equipment Identity Register (5G-EIR) ( Figure 14 not shown in the figure).

[0094] UE 1401 can register with the AMF 1421 to receive network services. Registration Management (RM) is used to enable the UE 1401 to register or deregister with the network (e.g., AMF 1421), and to establish a UE context in the network (e.g., AMF 1421). The UE 1401 can operate in the RM-REGISTERED state or the RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE 1401 is not registered with the network, and the UE context in the AMF 1421 does not maintain valid location or routing information for the UE 1401, so the UE 1401 cannot be accessed by the AMF 1421. In the RM-REGISTERED state, the UE 1401 is registered with the network, and the UE context in the AMF 1421 can maintain valid location or routing information for the UE 1401, so the UE 1401 can be accessed by the AMF 1421. In the RM-REGISTERED state, the UE 1401 can perform a mobility registration update procedure, perform a periodic registration update procedure triggered by the expiration of a periodic update timer (e.g., to notify the network that the UE 1401 is still active), and perform a registration update procedure to update UE capability information or renegotiate protocol parameters with the network, etc.

[0095] The AMF 1421 can store one or more RM contexts for the UE 1401, where each RM context is associated with a specific access right to the network. The RM context can be a data structure, a database object, etc., which in particular indicates or stores the registration status and the periodic update timer for each access type. The AMF 1421 can also store a 5GC Mobility Management (MM) context that is the same as or similar to the (Evolved Packet System (EPS)) MM ((E)MM) context. In various embodiments, the AMF 1421 can store the Coverage Enhancement (CE) mode B restriction parameter of the UE 1401 in the associated MM context or RM context. The AMF 1421 can also derive values from the UE usage setting parameters that have been stored in the UE context (and / or MM / RM context) when needed.

[0096] Connection Management (CM) can be used to establish and release a signaling connection between the UE 1401 and the AMF 1421 over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 1401 and the CN 1420, and includes both the signaling connection between the UE and the AN (e.g., the RRC connection for non-3GPP access or the UE-N3IWF connection) and the N2 connection of the UE 1401 between the AN (e.g., the RAN 1410) and the AMF 1421. The UE 1401 can operate in one of two CM states, i.e., the CM-idle mode or the CM-connected mode. When the UE 1401 is operating in the CM-idle state / mode, the UE 1401 may not have a NAS signaling connection established with the AMF 1421 over the N1 interface, and there may be a (R)AN 1410 signaling connection (e.g., N2 and / or N3 connection) for the UE 1401. When the UE 1401 is operating in the CM-connected state / mode, the UE 1401 may have a NAS signaling connection established with the AMF 1421 over the N1 interface, and there may be a (R)AN 1410 signaling connection (e.g., N2 and / or N3 connection) for the UE 1401. The establishment of the N2 connection between the (R)AN 1410 and the AMF 1421 may cause the UE 1401 to transition from the CM-idle mode to the CM-connected mode, and when the N2 signaling between the (R)AN 1410 and the AMF 1421 is released, the UE 1401 may transition from the CM-connected mode to the CM-idle mode.

[0097] The SMF 1424 may be responsible for session management (SM) (e.g., session establishment, modification, and release, including tunnel maintenance between the UPF and the AN node); UE IP address allocation and management (including optional authorization); selection and control of the UPF function; configuring the traffic steering of the UPF to route traffic to the correct destination; terminating the interface towards the policy control function; the policy enforcement and the control part of QoS; lawful interception (for SM events and the interface with the lawful interception (LI) system); terminating the SM part of the NAS message; downlink data notification; initiating AN-specific SM information sent to the AN via the AMF over N2; and determining the session and service continuity (SSC) mode of the session. SM may refer to the management of the PDU session, and the PDU session or "session" may refer to the PDU connection service that provides or enables the exchange of PDUs between the UE 1401 and the data network (DN) 1403 identified by the data network name (DNN). The PDU session may be established upon request by the UE 1401, modified upon request by the UE 1401 and the 5GC 1420, and released upon request by the UE 1401 and the 5GC 1420, using the NAS SM signaling exchanged through the N1 reference point between the UE 1401 and the SMF 1424. When a request is issued by the application server, the 5GC 1420 may trigger a specific application in the UE 1401. In response to receiving the trigger message, the UE 1401 may pass the trigger message (or the relevant part / information of the trigger message) to one or more identified applications in the UE 1401. The identified applications in the UE 1401 may establish a PDU session to a specific DNN. The SMF 1424 may check whether the UE 1401 request complies with the user subscription information associated with the UE 1401. In this regard, the SMF 1424 may retrieve and / or request to receive an update notification regarding the SMF 1424-level subscription data from the UDM 1427.

[0098] The SMF 1424 may include the following roaming functions: handling local enforcement to apply the QoS service level agreement (SLA) (visited public land mobile network (VPLMN)); charging data collection and charging interface (VPLMN); lawful interception (for SM events and the interface with the LI system, in the VPLMN); and supporting the interaction with the external DN to transmit the signaling for PDU session authorization / authentication through the external DN. In a roaming scenario, the N16 reference point between two SMF 1424s may be included in the system 1400, which may be located between another SMF 1424 in the visited network and the SMF 1424 in the home network. Additionally, the SMF 1424 may present an Nsmf service-based interface.

[0099] The NEF 1423 can provide components for securely exposing the services and capabilities provided by 3GPP network functions to third parties, internal exposure / re-exposure, application functions (e.g., AF 1428), edge computing or fog computing systems, etc. In such embodiments, the NEF 1423 can authenticate, authorize, and / or restrict the AF. The NEF 1423 can also transform the information exchanged with the AF 1428 and the information exchanged with internal network functions. For example, the NEF 1423 can transform between an AF service identifier and internal 5GC information. The NEF 1423 can also receive information from other network functions (NFs) based on the exposure capabilities of other network functions. This information can be stored at the NEF 1423 as structured data, or stored at a data storage NF using a standardized interface. Then, the stored information can be re-exposed by the NEF 1423 to other NFs and AFs, and / or used for other purposes such as analysis. Additionally, the NEF1423 can present an interface based on the Nnef service.

[0100] The NRF 1425 can support a service discovery function, receive NF discovery requests from NF instances, and provide information about the discovered NF instances to the NF instances. The NRF 1425 also maintains information about available NF instances and the services they support. As used herein, terms such as "instantiation" etc. can refer to the creation of an instance, and an "instance" can refer to a specific occurrence of an object, which can occur, for example, during the execution of program code. Additionally, the NRF 1425 can present an interface based on the Nnrf service.

[0101] The PCF 1426 can provide control plane functions for executing their policy rules, and can also support a unified policy framework for managing network behavior. The PCF 1426 can also implement an FE to access subscription information related to policy decisions in the UDR of the UDM 1427. The PCF 1426 can communicate with the AMF 1421 via the N15 reference point between the PCF1426 and the AMF 1421, which can include the PCF 1426 in a visited network and the AMF 1421 in a roaming scenario. The PCF 1426 can communicate with the AF 1428 via the N5 reference point between the PCF1426 and the AF 1428; and communicate with the SMF 1424 via the N7 reference point between the PCF 1426 and the SMF 1424. The system 1400 and / or the CN 1420 can also include an N24 reference point between the PCF 1426 (in a home network) and the PCF 1426 in a visited network. Additionally, the PCF 1426 can present an interface based on the Npcf service.

[0102] The UDM 1427 can process subscription-related information to support the handling of communication sessions by network entities and can store the subscription data of the UE 1401. For example, subscription data can be transmitted between the UDM 1427 and the AMF via the N8 reference point between the UDM 1427 and the AMF 1421. The UDM 1427 can include two parts: an Application Function Entity (FE) and a Unified Data Repository (UDR) ( Figure 1 the FE and the UDR are not shown in ). The UDR can store the subscription data and policy data of the UDM 1427 and the PCF 1426, and / or the structured data for exposure and application data of the NEF 1423 (including Packet Flow Descriptions (PFDs) for application detection, application request information of multiple UEs 1401). An interface based on the Nudr service can be presented by the UDR 221 to allow the UDM1427, the PCF 1426, and the NEF 1423 to access a specific set of the stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. The UDM can include a UDM-FE that is responsible for handling credentials, location management, subscription management, etc. In different transactions, several different FEs can serve the same user. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. The UDR can interact with the SMF 1424 via the N10 reference point between the UDM 1427 and the SMF 1424. The UDM1427 can also support SMS management, where the SMS-FE implements similar application logic as discussed elsewhere in this document. Additionally, the UDM1427 can present an interface based on the Nudm service.

[0103] AF 1428 can provide the impact of the application on traffic routing, provide access to the NEF 1423, and interact with the policy framework for policy control. The 5GC 1420 and the AF 1428 can provide information to each other via the NEF 1423, which can be used for edge computing implementation. In such an implementation, the network operator and third-party services can be hosted near the access point of the attached UE 1401 to achieve efficient service delivery with reduced end-to-end latency and load on the transport network. For edge computing implementation, the 5GC can select a UPF 1402 near the UE 1401 and perform traffic steering from the UPF 1402 to the DN 1403 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by the AF 1428. In this way, the AF 1428 can affect UPF (re)selection and traffic routing. Based on the operator deployment, when the AF 1428 is considered a trusted entity, the network operator can allow the AF 1428 to directly interact with the relevant NF. Additionally, the AF 1428 can present an interface based on the Naf service.

[0104] The NSSF 1429 can select a set of network slice instances serving the UE 1401. As appropriate, the NSSF 1429 can also determine the allowed network slice selection assistance information (NSSAI) and the mapping to the subscribed single NSSAI (S-NSSAI). The NSSF 1429 can also determine, based on a suitable configuration and possibly by querying the NRF 1425, the set of AMFs or a list of candidate AMFs 1421 for serving the UE 1401. The selection of a set of network slice instances for the UE 1401 can be triggered by the AMF 1421, where the UE 1401 registers by interacting with the NSSF 1429, which can cause a change in the AMF 1421. The NSSF 1429 can interact with the AMF 1421 via the N22 reference point between the AMF 1421 and the NSSF 1429; and can communicate with another NSSF 1429 in the visited network via the N31 reference point ( Figure 14 not shown). Additionally, the NSSF 1429 can present an interface based on the Nnssf service.

[0105] As previously discussed, CN 1420 may include an SMSF, which may be responsible for SMS subscription checking and verification and relaying SM messages to / from UE1401 to / from other entities, such as an SMS-gateway mobile services switching center (GMSC) / interworking MSC (IWMSC) / SMS-router. The SMSF may also interact with the AMF 1421 and the UDM 1427 for notification procedures so that UE1401 can be used for SMS transmission (e.g., setting the UE unreachable flag and notifying the UDM1427 when UE 1401 is available for SMS).

[0106] CN 1420 may also include Figure 14 other elements not shown in the figure, such as a data storage system / architecture, a 5G-EIR, a security edge protection proxy (SEPP), etc. The data storage system may include a structured data storage function (SDSF), an unstructured data storage function (UDSF), etc. Any NF may store or retrieve unstructured data (e.g., UE context) into / from the UDSF via an N18 reference point between any NF and the UDSF ( Figure 1 not shown in the figure). Each NF may share the UDSF for storing its respective unstructured data, or each NF may have its own UDSF located at or near each NF. Additionally, the UDSF may present an interface based on the Nudsf service ( Figure 1 not shown in the figure). The 5G-EIR may be an NF that checks the status of a permanent equipment identifier (PEI) to determine whether to blacklist a specific piece of equipment / entity from the network; and the SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on the inter-PLMN control plane interface.

[0107] In addition, there may be more reference points and / or service-based interfaces between NF services in the NF; however, for clarity, Figure 14 these interfaces and reference points are omitted. In one example, CN1420 may include an Nx interface, which is an inter-CN interface between an MME (e.g., a non-5G MME) and the AMF 1421 to enable interworking between CN 1420 and a non-5G CN. Other exemplary interfaces / reference points may include an interface based on the N5g-EIR service presented by the 5G-EIR, an N27 reference point between the network repository function (NRF) in a visited network and the NRF in a home network; and an N31 reference point between the NSSF in a visited network and the NSSF in a home network.

[0108] Figure 15Shows exemplary components of a device 1500 according to some embodiments. In some embodiments, the device 1500 may include an application circuit 1502, a baseband circuit 1504, a radio frequency (RF) circuit 1506, a front-end module (FEM) circuit 1508, one or more antennas 1510, and a power management circuit (PMC) 1512 (coupled together as shown at least). The illustrated components of the device 1500 may be included in a UE or a RAN node. In some embodiments, the device 1500 may include fewer elements (e.g., a RAN node may not utilize the application circuit 1502 but include a processor / controller to process IP data received from a CN such as 5GC 1420 or an evolved packet core (EPC)). In some embodiments, the device 1500 may include additional elements such as a memory / storage device, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the following components may be included in more than one device (e.g., the circuits may be separately included in more than one device for a cloud-RAN (C-RAN) implementation).

[0109] The application circuit 1502 may include one or more application processors. For example, the application circuit 1502 may include circuitry such as but not limited to one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and dedicated processors (e.g., a graphics processor, an application processor, etc.). The processors may be coupled to a memory / storage device or may include a memory / storage device and may be configured to execute instructions stored in the memory / storage device to enable various application programs or operating systems to run on the device 1500. In some embodiments, the processor of the application circuit 1502 may process IP data packets received from the EPC.

[0110] The baseband circuit 1504 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 1504 may include one or more baseband processors or control logic components to process baseband signals received at the receive signal path of the RF circuit 1506 and generate baseband signals for the transmit signal path of the RF circuit 1506. The baseband circuit 1504 may interact with the application circuit 1502 to generate and process baseband signals and control the operation of the RF circuit 1506. For example, in some embodiments, the baseband circuit 1504 may include a third-generation (3G) baseband processor 1504A, a fourth-generation (4G) baseband processor 1504B, a fifth-generation (5G) baseband processor 1504C, or other baseband processors 1504D of other existing generations, generations under development, or generations to be developed in the future (e.g., second-generation (2G), sixth-generation (6G), etc.). The baseband circuit 1504 (e.g., one or more of the baseband processors 1504A-D) may process various radio control functions that may communicate with one or more radio networks via the RF circuit 1506. In other embodiments, some or all of the functions of the baseband processors 1504A-D may be included in modules stored in the memory 1504G and executed via the central processing unit (CPU) 1504E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuitry of the baseband circuit 1504 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of the baseband circuit 1504 may include convolutional, tail-biting convolutional, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functions. Embodiments of the modulation / demodulation and encoder / decoder functions are not limited to these examples and may include other suitable functions in other embodiments.

[0111] In some embodiments, the baseband circuit 1504 may include one or more audio digital signal processors (DSPs) 1504F. The audio DSP 1504F may include elements for compression / decompression and echo cancellation and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the constituent components of the baseband circuit 1504 and the application circuit 1502 may be implemented together, such as (for example) on a system-on-chip (SOC).

[0112] In some embodiments, the baseband circuit 1504 may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 1504 may support communications with NG-RAN, evolved universal terrestrial radio access network (EUTRAN), or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN), etc. Embodiments where the baseband circuit 1504 is configured to support radio communications for more than one wireless protocol may be referred to as multi-mode baseband circuits.

[0113] The RF circuit 1506 may communicate with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuit 1506 may include switches, filters, amplifiers, etc. to facilitate communications with the wireless network. The RF circuit 1506 may include a receive signal path that may include circuitry to down-convert an RF signal received from the FEM circuit 1508 and provide a baseband signal to the baseband circuit 1504. The RF circuit 1506 may also include a transmit signal path that may include circuitry to up-convert a baseband signal provided by the baseband circuit 1504 and provide an RF output signal to the FEM circuit 1508 for transmission.

[0114] In some embodiments, the receive signal path of the RF circuit 1506 may include a mixer circuit 1506a, an amplifier circuit 1506b, and a filter circuit 1506c. In some embodiments, the transmit signal path of the RF circuit 1506 may include the filter circuit 1506c and the mixer circuit 1506a. The RF circuit 1506 may also include a synthesizer circuit 1506d for synthesizing the frequencies used by the mixer circuits 1506a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 1506a of the receive signal path may be configured to down-convert an RF signal received from the FEM circuit 1508 based on the synthesized frequency provided by the synthesizer circuit 1506d. The amplifier circuit 1506b may be configured to amplify the down-converted signal, and the filter circuit 1506c may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 1504 for further processing. In some embodiments, although not required, the output baseband signal may be a zero-frequency baseband signal. In some embodiments, the mixer circuit 1506a of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this regard.

[0115] In some embodiments, the mixer circuit 1506a of the transmit signal path may be configured to up-convert an input baseband signal based on a synthesized frequency provided by the synthesizer circuit 1506d to generate an RF output signal for the FEM circuit 1508. The baseband signal may be provided by the baseband circuit 1504 and may be filtered by the filter circuit 1506c.

[0116] In some embodiments, the mixer circuit 1506a of the receive signal path and the mixer circuit 1506a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 1506a of the receive signal path and the mixer circuit 1506a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuit 1506a of the receive signal path and the mixer circuit 1506a may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 1506a of the receive signal path and the mixer circuit 1506a of the transmit signal path may be configured for superheterodyne operation.

[0117] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this regard. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 1506 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 1504 may include a digital baseband interface for communicating with the RF circuit 1506.

[0118] In some dual-mode embodiments, a separate radio IC circuit may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this regard.

[0119] In some embodiments, the synthesizer circuit 1506d may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, although the scope of the embodiments is not limited in this regard as other types of frequency synthesizers may be suitable. For example, the synthesizer circuit 1506d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0120] The synthesizer circuit 1506d may be configured to synthesize an output frequency based on a frequency input and a frequency divider control input for use by the mixer circuit 1506a of the RF circuit 1506. In some embodiments, the synthesizer circuit 1506d may be a fractional-N / N+1 synthesizer.

[0121] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by the baseband circuitry 1504 or the application circuitry 1502 according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a look-up table based on the channel indicated by the application circuitry 1502.

[0122] The synthesizer circuitry 1506d of the RF circuitry 1506 may include a divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide an input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascade of tunable delay elements, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay elements may be configured to divide the VCO period into Nd equal phase bins, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO period.

[0123] In some embodiments, the synthesizer circuitry 1506d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency), and may be used with a quadrature generator and a divider circuit to generate multiple signals having multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, the RF circuitry 1506 may include an IQ / polarity converter.

[0124] The FEM circuitry 1508 may include a receive signal path that may include circuitry configured to operate on an RF signal received from one or more antennas 1510, amplify the received signal, and provide an amplified version of the received signal to the RF circuitry 1506 for further processing. The FEM circuitry 1508 may also include a transmit signal path that may include circuitry configured to amplify a transmit signal provided by the RF circuitry 1506 for transmission via one or more of the one or more antennas 1510. In various embodiments, amplification through the transmit or receive signal path may be accomplished only in the RF circuitry 1506, only in the FEM circuitry 1508, or in both the RF circuitry 1506 and the FEM circuitry 1508.

[0125] In some embodiments, the FEM circuit 1508 may include a TX / RX switch to switch between transmit mode and receive mode operations. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 1506). The transmit signal path of the FEM circuit 1508 may include a power amplifier (PA) to amplify the input RF signal (e.g., provided by the RF circuit 1506), and one or more filters to generate an RF signal for subsequent transmission (e.g., via one or more of the one or more antennas 1510).

[0126] In some embodiments, the PMC 1512 may manage the power provided to the baseband circuit 1504. Specifically, the PMC 1512 may control power selection, voltage scaling, battery charging, or DC-DC conversion. When the device 1500 is capable of being powered by a battery, e.g., when the device is included in a UE, the PMC 1512 is typically included. The PMC 1512 may improve power conversion efficiency while providing desired implementation size and thermal characteristics.

[0127] While Figure 15 the PMC 1512 is shown coupled only to the baseband circuit 1504. However, in other embodiments, the PMC 1512 may be additionally or alternatively coupled to other components such as, but not limited to, the application circuit 1502, the RF circuit 1506, or the FEM circuit 1508, and perform similar power management operations.

[0128] In some embodiments, the PMC 1512 may control or otherwise be part of various power saving mechanisms of the device 1500. For example, if the device 1500 is in the RRC_Connected state, where the device is still connected to a RAN node because it expects to receive traffic immediately, after a period of inactivity, the device may enter a state called discontinuous reception mode (DRX). During this state, the device 1500 may power off for short intervals, thus saving power.

[0129] If there is no data traffic activity for an extended period, the device 1500 may transition to the RRC_Idle state, where the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 1500 enters a very low power state and performs paging, where the device wakes up periodically again to listen for the network and then powers off again. The device 1500 may not receive data in this state; to receive data, the device may transition back to the RRC_Connected state.

[0130] An additional power saving mode can cause the device to be unable to use the network for a time period exceeding the paging interval (ranging from a few seconds to several hours). During this period, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this period will incur a significant delay, and it is assumed that the delay is acceptable.

[0131] The processors of the application circuit 1502 and the processors of the baseband circuit 1504 can be used to execute elements of one or more instances of the protocol stack. For example, the processors of the baseband circuit 1504 can be used, either alone or in combination, to execute functions of Layer 3, Layer 2, or Layer 1, while the processors of the application circuit 1502 can utilize the data received from these layers (e.g., packet data) and further execute functions of Layer 4 (e.g., Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) layers). As mentioned herein, Layer 3 can include the Radio Resource Control (RRC) layer, which will be described in further detail below. As mentioned herein, Layer 2 can include the Medium Access Control (MAC) layer, the Radio Link Control (RLC) layer, and the Packet Data Convergence Protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, Layer 1 can include the physical (PHY) layer of the UE / RAN node, which will be described in further detail below.

[0132] Figure 16 An exemplary interface of a baseband circuit according to some embodiments is shown. As discussed above, the baseband circuit 1504 of FIG. 2 can include processors 1504A - 1504E and a memory 1504G utilized by the processors. Each of the processors 1504A - 1504E can respectively include a memory interface 1604A - 1604E for sending / receiving data to / from the memory 1504G.

[0133] The baseband circuit 1504 can further include: one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 1612 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1504); an application circuit interface 1614 (e.g., an interface for sending / receiving data to / from the application circuit 1502 of FIG. 2); an RF circuit interface 1616 (e.g., an interface for sending / receiving data to / from the RF circuit 1506 of FIG. 2); a wireless hardware connection interface 1618 (e.g., an interface for sending / receiving data to / from near field communication (NFC) components, components (e.g., low power), components, and other communication components); and a power management interface 1620 (e.g., an interface for sending / receiving power or control signals to / from the PMC 1512).

[0134] In various aspects, the embodiments discussed herein can facilitate techniques for inter-cell BM (beam management) via L1 (layer 1) through one or more variations of a first set of techniques and / or a second set of techniques. The first set of techniques discussed herein can facilitate L1 inter-cell BM via SSB (synchronization signal block). The second set of techniques discussed herein can facilitate L1 inter-cell BM via synchronized CSI (channel state information)-RS (reference signal).

[0135] Embodiments can include a subject matter such as a method, an apparatus for performing actions or blocks of the method, at least one machine-readable medium including instructions that, when executed by a machine, cause the machine to perform actions of a method or an apparatus or a system for concurrent communication using multiple communication techniques according to the embodiments and examples described herein.

[0136] Embodiment 1 is a user equipment (UE) including a processor (or processing circuitry) configured to perform operations including receiving, from a base station associated with the UE, a hybrid automatic repeat request process group (HPG) configuration signal, where the HPG configuration signal includes information of a plurality of HARQ process groups (HPGs), each HPG including one or more HARQ processes from a set of HARQ processes configured for the UE; determining the plurality of HPGs based on processing the HPG configuration signal; receiving downlink control information (DCI) from the base station, where the DCI is configured to trigger a HARQ-ACK feedback signal from the UE, and where the DCI includes information identifying one or more HPGs among the plurality of HPGs, the HARQ-ACK feedback information of the one or more HPGs to be included in the HARQ-ACK feedback signal; generating the HARQ-ACK feedback signal including the HARQ-ACK feedback information of the HARQ processes associated with the one or more HPGs; and transmitting the HARQ-ACK feedback signal to the base station.

[0137] Embodiment 2 is a UE including the subject matter of Embodiment 1, where the plurality of HPGs are associated with corresponding plurality of priority class indices, and where each priority class index among the plurality of priority class indices corresponds to a priority index associated with one or more HARQ processes of the corresponding HPG.

[0138] Embodiment 3 is a UE including or omitting elements including the subject matter of Embodiments 1-2, where the DCI includes an HPG request field including an HPG request field value identifying one or more HPGs, and where the processor is configured to determine the one or more HPGs based on a predefined mapping between the HPG request field value and the one or more HPGs.

[0139] Example 4 is a UE including or omitting elements of the subject matter of Examples 1-3, wherein the DCI includes cyclic redundancy check (CRC) bits scrambled by a predefined HPG sequence, wherein the predefined HPG sequence identifies one or more HPGs, and wherein the processor is configured to descramble the CRC bits to determine the predefined HPG sequence and determine one or more HPGs based on the predefined HPG sequence according to a predefined mapping between the predefined HPG sequence and the one or more HPGs.

[0140] Example 5 is a UE including or omitting elements of the subject matter of Examples 1-4, wherein the DCI includes a priority indicator field that includes a selected priority class index among a plurality of priority class indices, wherein the selected priority class index identifies a selected HPG, and the HARQ-ACK feedback information of the selected HPG is to be included in the HARQ-ACK feedback signal.

[0141] Example 6 is a UE including or omitting elements of the subject matter of Examples 1-5, wherein the HARQ-ACK feedback signal further includes the most recent new data indicator (NDI) value detected by the UE for each HARQ process in the HARQ processes associated with one or more HPGs.

[0142] Example 7 is a UE including or omitting elements of the subject matter of Examples 1-6, wherein the operations further include receiving an NDI configuration signal from the BS, wherein the NDI configuration signal is adapted to configure the UE to include the NDI as part of the HARQ-ACK feedback signal.

[0143] Example 8 is a UE including or omitting elements of the subject matter of Examples 1-7, wherein one or more processors are further configured to receive a HARQ process reconfiguration signal from the base station, wherein the HARQ process reconfiguration signal includes information for reconfiguring the HARQ processes associated with one or more of the plurality of HPGs.

[0144] Example 9 is a UE including or omitting elements of the subject matter of Examples 1-8, wherein the HARQ process reconfiguration signal includes one or more HARQ reconfiguration medium access control (MAC) control elements (CEs), wherein each HARQ reconfiguration MAC CE in the one or more HARQ reconfiguration MAC CEs is associated with an HPG identifier (ID) of a selected HPG among the plurality of HPGs, wherein each HARQ reconfiguration MAC CE in the one or more HARQ reconfiguration MAC CEs includes a set of H fields corresponding to the set of HARQ processes configured for the UE, and wherein the value associated with each H field in the set of H fields identifies one or more HARQ processes included in the selected HPG identified by the HPG ID.

[0145] Embodiment 10 is a UE that includes or omits elements of the subject matter of Embodiments 1-9, wherein the HARQ process reconfiguration signal includes a HARQ reconfiguration medium access control (MAC) control element (CE), the CE including a set of one or more H fields respectively associated with one or more of a plurality of HPGs, wherein each set of H fields in the set of one or more H fields corresponds to a set of HARQ processes configured for the UE, and wherein the value associated with each H field in the set of H fields identifies one or more HARQ processes included within the corresponding HPG.

[0146] Embodiment 11 is a base station (BS) including a processor (or processing circuitry) configured to perform operations including sending a hybrid automatic repeat request process group (HPG) configuration signal to a user equipment (UE) associated with the BS, wherein the HPG configuration signal includes information of a plurality of HARQ process groups (HPGs), each HPG including one or more HARQ processes from a set of HARQ processes configured for the UE; sending downlink control information (DCI) to the UE, wherein the DCI is configured to trigger a HARQ-ACK feedback signal from the UE, and wherein the DCI includes information identifying one or more of the plurality of HPGs, the HARQ-ACK feedback information of which is to be included in the HARQ-ACK feedback signal; and receiving a HARQ-ACK feedback signal from the UE, wherein the HARQ-ACK feedback signal includes HARQ-ACK feedback information of HARQ processes associated with one or more HPGs.

[0147] Embodiment 12 is a BS including the subject matter of Embodiment 11, wherein the plurality of HPGs are associated with corresponding plurality of priority category indices, wherein each priority category index in the plurality of priority category indices corresponds to a priority index associated with one or more HARQ processes of the corresponding HPG.

[0148] Embodiment 13 is a BS including or omitting elements of the subject matter of Embodiments 11-12, wherein the DCI includes an HPG request field, the HPG request field including an HPG request field value that identifies one or more HPGs based on a predefined mapping between the HPG request field value and one or more HPGs.

[0149] Embodiment 14 is a BS including or omitting elements of the subject matter of Embodiments 11-13, wherein the DCI includes cyclic redundancy check (CRC) bits scrambled by a predefined HPG sequence, wherein the predefined HPG sequence identifies one or more HPGs according to a predefined mapping between the predefined HPG sequence and one or more HPGs.

[0150] Embodiment 15 is a BS including or omitting elements of the subject matter of Embodiments 11-14, wherein the DCI includes a priority indicator field that includes a selected priority class index from among a plurality of priority class indices, wherein the selected priority class index identifies a selected HPG, and HARQ-ACK feedback information for the selected HPG is to be included in the HARQ-ACK feedback signal.

[0151] Embodiment 16 is a BS including or omitting elements of the subject matter of Embodiments 11-15, wherein the HARQ-ACK feedback signal further includes the most recent new data indicator (NDI) value detected by the UE for each HARQ process in the HARQ processes associated with one or more HPGs.

[0152] Embodiment 17 is a BS including or omitting elements of the subject matter of Embodiments 11-16, wherein the operations further include generating an NDI configuration signal to be provided to the UE, wherein the NDI configuration signal is adapted to configure the UE to include the NDI as part of the HARQ-ACK feedback signal; and transmitting the NDI configuration signal to the UE.

[0153] Embodiment 18 is a BS including or omitting elements of the subject matter of Embodiments 11-17, wherein the operations further include generating a HARQ process reconfiguration signal to be provided to the UE, wherein the HARQ process reconfiguration signal includes information for reconfiguring HARQ processes associated with one or more HPGs among a plurality of HPGs; and transmitting the HARQ process reconfiguration signal to the UE.

[0154] Embodiment 19 is a UE including or omitting elements of the subject matter of Embodiments 11-18, wherein the HARQ process reconfiguration signal includes one or more HARQ reconfiguration medium access control (MAC) control elements (CEs), wherein each HARQ reconfiguration MAC CE among the one or more HARQ reconfiguration MAC CEs is associated with an HPG identifier (ID) of a selected HPG among a plurality of HPGs, wherein each HARQ reconfiguration MAC CE among the one or more HARQ reconfiguration MAC CEs includes a set of H fields corresponding to a set of HARQ processes configured for the UE, and wherein a value associated with each H field in the set of H fields identifies one or more HARQ processes included within the selected HPG identified by the HPG ID.

[0155] Example 20 is a BS that includes or omits elements of the subject matter of Examples 11 - 19, where the HARQ process reconfiguration signal includes a HARQ reconfiguration media access control (MAC) control element (CE), the CE including a set of one or more H fields respectively associated with one or more of a plurality of HPGs, where each set of H fields in the set of one or more H fields corresponds to a set of HARQ processes configured for a UE, and where the value associated with each H field in the set of H fields identifies one or more HARQ processes included within the corresponding HPG.

[0156] Example 21 is a baseband (BB) processor for a user equipment (UE), the BB processor being configured to perform operations that include receiving a hybrid automatic repeat request process group (HPG) configuration signal from a base station associated with the UE, where the HPG configuration signal includes information on a plurality of HARQ process groups (HPGs), each HPG including one or more HARQ processes from a set of HARQ processes configured for the UE; determining the plurality of HPGs based on processing the HPG configuration signal; receiving downlink control information (DCI) from the base station, where the DCI is configured to trigger a HARQ-ACK feedback signal from the UE, and where the DCI includes information identifying one or more of the plurality of HPGs, the HARQ-ACK feedback information of the one or more HPGs to be included in the HARQ-ACK feedback signal; generating the HARQ-ACK feedback signal, the HARQ-ACK feedback signal including the HARQ-ACK feedback information of the HARQ processes associated with the one or more HPGs; and transmitting the HARQ-ACK feedback signal to the base station.

[0157] Example 22 is a BB processor that includes the subject matter of Example 21, where the plurality of HPGs are associated with corresponding pluralities of priority class indices, where each priority class index in the plurality of priority class indices corresponds to a priority index associated with one or more HARQ processes of the corresponding HPG.

[0158] Example 23 is a BB processor that includes or omits elements of the subject matter of Examples 21 - 22, where the DCI includes an HPG request field, the HPG request field including an HPG request field value identifying one or more HPGs, and where the processor is configured to determine the one or more HPGs based on the HPG request field value and a predefined mapping between the one or more HPGs.

[0159] Embodiment 24 is a BB processor including or omitting elements of the subject matter of Embodiments 21-23, where the DCI includes cyclic redundancy check (CRC) bits scrambled by a predefined HPG sequence, where the predefined HPG sequence identifies one or more HPGs, and where the processor is configured to descramble the CRC bits to determine the predefined HPG sequence and determine one or more HPGs based on the predefined HPG sequence according to a predefined mapping between the predefined HPG sequence and the one or more HPGs.

[0160] Embodiment 25 is a BB processor including or omitting elements of the subject matter of Embodiments 21-24, where the DCI includes a priority indicator field that includes a selected priority class index among a plurality of priority class indexes, where the selected priority class index identifies a selected HPG, and where HARQ-ACK feedback information of the selected HPG is to be included in the HARQ-ACK feedback signal.

[0161] Embodiment 26 is a BB processor including or omitting elements of the subject matter of Embodiments 21-25, where the HARQ-ACK feedback signal further includes the most recent new data indicator (NDI) value detected by the UE for each HARQ process in the HARQ processes associated with one or more HPGs.

[0162] Embodiment 27 is a BB processor including or omitting elements of the subject matter of Embodiments 21-26, where the operations further include receiving an NDI configuration processor signal from the BS, where the NDI configuration signal is adapted to configure the UE to include the NDI as part of the HARQ-ACK feedback signal.

[0163] Embodiment 28 is a BB processor including or omitting elements of the subject matter of Embodiments 21-27, where one or more processors are further configured to receive a HARQ process reconfiguration processor signal from the base station, where the HARQ process reconfiguration signal includes information for reconfiguring the HARQ processes associated with one or more of the plurality of HPGs.

[0164] Embodiment 29 is a BB processor including or omitting elements of the subject matter of Embodiments 21-28, where the HARQ process reconfiguration signal includes one or more HARQ reconfiguration medium access control (MAC) control elements (CEs), and each HARQ reconfiguration MAC CE among the one or more HARQ reconfiguration MAC CEs is associated with the HPG identifier (ID) of a selected HPG among a plurality of HPGs. Each HARQ reconfiguration MAC CE among the one or more HARQ reconfiguration MAC CEs includes a set of H fields corresponding to a set of HARQ processes configured for the UE, and the value associated with each H field in the set of H fields identifies one or more HARQ processes included in the selected HPG identified by the HPG ID.

[0165] Embodiment 30 is a BB processor including or omitting elements of the subject matter of Embodiments 21-29, where the HARQ process reconfiguration signal includes a HARQ reconfiguration medium access control (MAC) control element (CE), and the CE includes a set of one or more H fields respectively associated with one or more HPGs among a plurality of HPGs. Each set of H fields among the set of one or more H fields corresponds to a set of HARQ processes configured for the UE, and the value associated with each H field in the set of H fields identifies one or more HARQ processes included in the corresponding HPG.

[0166] Embodiment 31 is a baseband (BB) processor for a base station (BS), and the BB processor is configured to perform operations including sending a hybrid automatic repeat request process group (HPG) configuration signal to a user equipment (UE) associated with the BS. The HPG configuration signal includes information on a plurality of HARQ process groups (HPGs), and each HPG includes one or more HARQ processes among a set of HARQ processes configured for the UE; sending downlink control information (DCI) to the UE, where the DCI is configured to trigger a HARQ-ACK feedback signal from the UE, and the DCI includes information identifying one or more HPGs among the plurality of HPGs, and the HARQ-ACK feedback information of the one or more HPGs is to be included in the HARQ-ACK feedback signal; and receiving a HARQ-ACK feedback signal from the UE, where the HARQ-ACK feedback signal includes the HARQ-ACK feedback information of the HARQ processes associated with one or more HPGs.

[0167] Embodiment 32 is a BB processor including the subject matter of Embodiment 31, where the plurality of HPGs are associated with a corresponding plurality of priority class indices, and each priority class index among the plurality of priority class indices corresponds to a priority index associated with one or more HARQ processes of the corresponding HPG.

[0168] Embodiment 33 is a BB processor including or omitting elements of the subject matter of Embodiments 31 - 32, where the DCI includes an HPG request field, the HPG request field includes an HPG request field value, and the HPG request field value identifies one or more HPGs based on a predefined mapping between the HPG request field value and one or more HPGs.

[0169] Embodiment 34 is a BB processor including or omitting elements of the subject matter of Embodiments 31 - 33, where the DCI includes cyclic redundancy check (CRC) bits scrambled by a predefined HPG sequence, and the predefined HPG sequence identifies one or more HPGs according to a predefined mapping between the predefined HPG sequence and one or more HPGs.

[0170] Embodiment 35 is a BB processor including or omitting elements of the subject matter of Embodiments 31 - 34, where the DCI includes a priority indicator field, the priority indicator field includes a selected priority class index among a plurality of priority class indexes, and the selected priority class index identifies a selected HPG, and the HARQ - ACK feedback information of the selected HPG is to be included in the HARQ - ACK feedback signal.

[0171] Embodiment 36 is a BB processor including or omitting elements of the subject matter of Embodiments 31 - 35, where the HARQ - ACK feedback signal further includes the most recent data indicator (NDI) value detected by the UE for each HARQ process in the HARQ processes associated with one or more HPGs.

[0172] Embodiment 37 is a BB processor including or omitting elements of the subject matter of Embodiments 31 - 36, where the operations further include generating an NDI configuration signal to be provided to the UE, the NDI configuration signal being adapted to configure the UE to include the NDI as part of the HARQ - ACK feedback signal; and sending the NDI configuration signal to the UE.

[0173] Embodiment 38 is a BB processor including or omitting elements of the subject matter of Embodiments 31 - 37, where the operations further include generating a HARQ process reorganization signal to be provided to the UE, the HARQ process reorganization signal including information for reorganizing the HARQ processes associated with one or more HPGs among a plurality of HPGs; and sending the HARQ process reorganization signal to the UE.

[0174] Example 39 is a BB processor including or omitting elements of the subject matter of Examples 31 - 38, wherein the HARQ process reconfiguration signal includes one or more HARQ reconfiguration media access control (MAC) control elements (CEs), and each HARQ reconfiguration MAC CE among the one or more HARQ reconfiguration MAC CEs is associated with an HPG identifier (ID) of a selected HPG among a plurality of HPGs, each HARQ reconfiguration MAC CE among the one or more HARQ reconfiguration MAC CEs includes a set of H fields corresponding to a set of HARQ processes configured for the UE, and a value associated with each H field in the set of H fields identifies one or more HARQ processes included within the selected HPG identified by the HPG ID.

[0175] Example 40 is a BB processor including or omitting elements of the subject matter of Examples 31 - 39, wherein the HARQ process reconfiguration signal includes a HARQ reconfiguration media access control (MAC) control element (CE) that includes a set of one or more H fields respectively associated with one or more HPGs among a plurality of HPGs, each set of H fields among the set of one or more H fields corresponds to a set of HARQ processes configured for the UE, and a value associated with each H field in the set of H fields identifies one or more HARQ processes included within the corresponding HPG.

[0176] Example 41 is a method for a user equipment (UE), the method including: receiving, using one or more processors, a hybrid automatic repeat request process group (HPG) configuration signal from a base station associated with the UE, wherein the HPG configuration signal includes information of a plurality of HARQ process groups (HPGs), each HPG including one or more HARQ processes among a set of HARQ processes configured for the UE; determining, using one or more processors, the plurality of HPGs based on processing the HPG configuration signal; receiving, using one or more processors, downlink control information (DCI) from the base station, wherein the DCI is configured to trigger a HARQ-ACK feedback signal from the UE, and wherein the DCI includes information identifying one or more HPGs among the plurality of HPGs, the HARQ-ACK feedback information of the one or more HPGs to be included in the HARQ-ACK feedback signal; generating, using one or more processors, a HARQ-ACK feedback signal including HARQ-ACK feedback information of HARQ processes associated with the one or more HPGs; and transmitting, using one or more processors, the HARQ-ACK feedback signal to the base station.

[0177] Example 42 is a method that includes the subject matter of Example 41, wherein a plurality of HPGs are associated with a corresponding plurality of priority class indices, and wherein each priority class index among the plurality of priority class indices corresponds to a priority index associated with one or more HARQ processes of a corresponding HPG.

[0178] Example 43 is a method of including or omitting elements that includes the subject matter of Examples 41-42, wherein the DCI includes an HPG request field that includes an HPG request field value identifying one or more HPGs, and wherein the processor is configured to determine one or more HPGs based on a predefined mapping between the HPG request field value and the one or more HPGs.

[0179] Example 44 includes a method of including or omitting elements that includes the subject matter of Examples 41-43, wherein the DCI includes cyclic redundancy check (CRC) bits scrambled by a predefined HPG sequence, wherein the predefined HPG sequence identifies one or more HPGs, and wherein the processor is configured to descramble the CRC bits to determine the predefined HPG sequence and to determine one or more HPGs based on the predefined HPG sequence according to a predefined mapping between the predefined HPG sequence and the one or more HPGs.

[0180] Example 45 is a method of including or omitting elements that includes the subject matter of Examples 41-44, wherein the DCI includes a priority indicator field that includes a selected priority class index among the plurality of priority class indices, wherein the selected priority class index identifies a selected HPG, and the HARQ-ACK feedback information of the selected HPG is to be included in the HARQ-ACK feedback signal.

[0181] Example 46 is a method of including or omitting elements that includes the subject matter of Examples 41-45, wherein the HARQ-ACK feedback signal further includes the most recent new data indicator (NDI) value detected by the UE for each HARQ process among the HARQ processes associated with one or more HPGs.

[0182] Example 47 is a method of including or omitting elements that includes the subject matter of Examples 41-46, the method further comprising receiving an NDI configuration signal from the BS, wherein the NDI configuration signal is adapted to configure the UE to include the NDI as part of the HARQ-ACK feedback signal.

[0183] Example 48 is a method of including or omitting elements that includes the subject matter of Examples 41-47, the method further comprising receiving, using one or more processors, a HARQ process reconfiguration signal from the base station, wherein the HARQ process reconfiguration signal includes information for reconfiguring HARQ processes associated with one or more HPGs among the plurality of HPGs.

[0184] Embodiment 49 is a method of including or omitting elements of the subject matter of Embodiments 41 - 48, wherein the HARQ process reconfiguration signal includes one or more HARQ reconfiguration medium access control (MAC) control elements (CEs), wherein each HARQ reconfiguration MAC CE among the one or more HARQ reconfiguration MAC CEs is associated with a HARQ process group (HPG) identifier (ID) of a selected HPG among a plurality of HPGs, wherein each HARQ reconfiguration MAC CE among the one or more HARQ reconfiguration MAC CEs includes a set of H fields corresponding to a set of HARQ processes configured for the UE, and wherein a value associated with each H field in the set of H fields identifies one or more HARQ processes included within the selected HPG identified by the HPG ID.

[0185] Embodiment 50 is a method of including or omitting elements of the subject matter of Embodiments 41 - 49, wherein the HARQ process reconfiguration signal includes a HARQ reconfiguration medium access control (MAC) control element (CE) that includes a set of one or more H fields respectively associated with one or more HPGs among a plurality of HPGs, wherein each set of H fields among the set of one or more H fields corresponds to a set of HARQ processes configured for the UE, and wherein a value associated with each H field in the set of H fields identifies one or more HARQ processes included within the corresponding HPG.

[0186] Embodiment 51 is a method for a base station (BS), the method comprising: transmitting, using one or more processors, a hybrid automatic repeat request process group (HPG) configuration signal to a user equipment (UE) associated with the BS, wherein the HPG configuration signal includes information of a plurality of HARQ process groups (HPGs), each HPG including one or more HARQ processes among a set of HARQ processes configured for the UE; transmitting, using one or more processors, downlink control information (DCI) to the UE, wherein the DCI is configured to trigger a HARQ-ACK feedback signal from the UE, and wherein the DCI includes information identifying one or more HPGs among the plurality of HPGs, the HARQ-ACK feedback information of which is to be included in the HARQ-ACK feedback signal; and receiving, using one or more processors, a HARQ-ACK feedback signal from the UE, wherein the HARQ-ACK feedback signal includes HARQ-ACK feedback information of HARQ processes associated with one or more HPGs.

[0187] Embodiment 52 is a method including the subject matter of Embodiment 51, wherein the plurality of HPGs are associated with a corresponding plurality of priority class indices, and wherein each priority class index among the plurality of priority class indices corresponds to a priority index associated with one or more HARQ processes of the corresponding HPG.

[0188] Example 53 is a method of including or omitting elements of the subject matter of Examples 51 - 52, where the DCI includes an HPG request field, the HPG request field includes an HPG request field value, and the HPG request field value identifies one or more HPGs based on a predefined mapping between the HPG request field value and one or more HPGs.

[0189] Example 54 is a method of including or omitting elements of the subject matter of Examples 51 - 53, where the DCI includes cyclic redundancy check (CRC) bits scrambled by a predefined HPG sequence, and the predefined HPG sequence identifies one or more HPGs according to a predefined mapping between the predefined HPG sequence and one or more HPGs.

[0190] Example 55 is a method of including or omitting elements of the subject matter of Examples 51 - 54, where the DCI includes a priority indicator field, the priority indicator field includes a selected priority class index among a plurality of priority class indices, and the selected priority class index identifies a selected HPG, and the HARQ - ACK feedback information of the selected HPG is to be included in the HARQ - ACK feedback signal.

[0191] Example 56 is a method of including or omitting elements of the subject matter of Examples 51 - 55, where the HARQ - ACK feedback signal further includes the most recent data indicator (NDI) value detected by the UE for each HARQ process in the HARQ processes associated with one or more HPGs.

[0192] Example 57 is a method of including or omitting elements of the subject matter of Examples 51 - 56, the method further including generating an NDI configuration signal to be provided to the UE, where the NDI configuration signal is adapted to configure the UE to include the NDI as part of the HARQ - ACK feedback signal; and transmitting the NDI configuration signal to the UE using one or more processors.

[0193] Example 58 is a method of including or omitting elements of the subject matter of Examples 51 - 57, the method further including generating, using one or more processors, a HARQ process reorganization signal to be provided to the UE, where the HARQ process reorganization signal includes information for reorganizing the HARQ processes associated with one or more HPGs among a plurality of HPGs; and transmitting the HARQ process reorganization signal to the UE using one or more processors.

[0194] Embodiment 59 is a method of including or omitting elements of the subject matter of Embodiments 51-58, wherein the HARQ process reconfiguration signal includes one or more HARQ reconfiguration medium access control (MAC) control elements (CEs), and each HARQ reconfiguration MAC CE in the one or more HARQ reconfiguration MAC CEs is associated with an HPG identifier (ID) of a selected HPG among a plurality of HPGs. Each HARQ reconfiguration MAC CE in the one or more HARQ reconfiguration MAC CEs includes a set of H fields corresponding to a set of HARQ processes configured for the UE, and a value associated with each H field in the set of H fields identifies one or more HARQ processes included within the selected HPG identified by the HPG ID.

[0195] Embodiment 60 is a method of including or omitting elements of the subject matter of Embodiments 51-59, wherein the HARQ process reconfiguration signal includes a HARQ reconfiguration medium access control (MAC) control element (CE), and the CE includes a set of one or more H fields respectively associated with one or more HPGs among a plurality of HPGs. Each set of H fields in the set of one or more H fields corresponds to a set of HARQ processes configured for the UE, and a value associated with each H field in the set of H fields identifies one or more HARQ processes included within the corresponding HPG.

[0196] Embodiment 61 is a user equipment (UE) device including a processor (or processing circuitry), the processor being configured to perform operations including receiving downlink control information (DCI) from a base station associated with the UE, wherein the DCI includes an indication for triggering a type 3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal; receiving a type 3 HARQ ACK feedback signal based on processing the DCI, wherein the type 3 HARQ ACK feedback signal includes one or more HARQ-ACK bits for a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release, and each HARQ-ACK bit in the one or more HARQ-ACK bits for the SPS PDSCH release is adapted to include HARQ-ACK information for the SPS PDSCH release associated with the UE; and transmitting the type 3 HARQ-ACK feedback signal to the base station.

[0197] Embodiment 62 is a UE including the subject matter of Embodiment 61, wherein the one or more HARQ-ACK bits for the SPS PDSCH release include one or more reserved bits reserved to respectively include HARQ-ACK information for one or more SPS PDSCH releases.

[0198] Example 63 is a UE that includes or omits elements of the subject matter of Examples 61 - 62, wherein the DCI further includes information on the number of reserved bits, where the reserved bits include one or more reserved bits for SPS PDSCH release that are to be included in the type 3 HARQ-ACK feedback signal.

[0199] Example 64 is a UE that includes or omits elements of the subject matter of Examples 61 - 63, wherein the DCI further includes a Total SPS Release Indicator (T-SRI) field, and the T-SRI field includes information enabling identification of the total number of reserved bits, where the reserved bits include one or more reserved bits for SPS PDSCH release that are to be included within the type 3 HARQ-ACK feedback signal.

[0200] Example 65 is a UE that includes or omits elements of the subject matter of Examples 61 - 64, wherein the T-SRI field includes a 1-bit field that includes an SPS release indicator value indicating whether the reserved bits for SPS PDSCH release are included in the type 3 HARQ ACK feedback signal.

[0201] Example 66 is a UE that includes or omits elements of the subject matter of Examples 61 - 65, wherein when the SPS release indicator value indicates inclusion of the reserved bits for SPS PDSCH release, the total number of reserved bits is determined based on the total number of HARQ processes for downlink (DL) SPS configured for the UE.

[0202] Example 67 is a UE that includes or omits elements of the subject matter of Examples 61 - 66, wherein the T-SRI field includes a 2-bit field that includes an SPS release indicator value that identifies the total number of reserved bits for SPS PDSCH release according to a predefined mapping between the SPS release indicator value and the total number of reserved bits for SPS PDSCH release.

[0203] Example 68 is a UE that includes or omits elements of the subject matter of Examples 61 - 67, wherein one or more reserved bits for SPS PDSCH release are appended to the end of the type 3 HARQ-ACK feedback signal.

[0204] Example 69 is a UE that includes or omits elements of the subject matter of Examples 61 - 68, wherein one or more reserved bits for SPS PDSCH release are appended to the beginning of the type 3 HARQ-ACK feedback signal.

[0205] Example 70 is a UE that includes or omits elements of the subject matter of Examples 61 - 69, wherein one or more HARQ-ACK bits for SPS PDSCH release correspond to bit positions associated with the HARQ process of the corresponding SPS PDSCH within a type 3 HARQ-ACK feedback signal.

[0206] Example 71 is a UE that includes or omits elements of the subject matter of Examples 61 - 70, wherein one or more HARQ-ACK bits for SPS PDSCH release correspond to bit positions associated with the HARQ process identified by a HARQ process identifier (HPI), where the HPI is indicated to the UE via radio resource control (RRC) signaling.

[0207] Example 72 is a base station (BS) that includes a processor (or processing circuitry) configured to perform operations that include transmitting downlink control information (DCI) to a user equipment (UE) associated with the BS, where the DCI includes an indication to the UE to trigger a type 3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal; and receiving, in response to providing the DCI, a type 3 HARQ ACK feedback signal from the UE, where the type 3 HARQ ACK feedback signal includes one or more HARQ-ACK bits for semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release, and wherein each HARQ-ACK bit of the one or more HARQ-ACK bits for SPS PDSCH release is adapted to include HARQ-ACK information for an SPS PDSCH release associated with the UE.

[0208] Example 73 is a BS that includes the subject matter of Example 72, wherein one or more HARQ-ACK bits for SPS PDSCH release include one or more reserved bits reserved to respectively include HARQ-ACK information for one or more SPS PDSCH releases.

[0209] Example 74 is a BS that includes or omits elements of the subject matter of Examples 72 - 73, wherein the DCI further includes information on the number of reserved bits that include one or more reserved bits to be included in the type 3 HARQ ACK feedback signal for SPS PDSCH release.

[0210] Example 75 is a BS that includes or omits elements of the subject matter of Examples 72 - 74, where the DCI further includes a Total SPS Release Indicator (T-SRI) field, and the T-SRI field includes information enabling identification of the total number of reserved bits, where the reserved bits include one or more reserved bits for SPS PDSCH release to be included within a Type 3 HARQ-ACK feedback signal.

[0211] Example 76 is a BS that includes or omits elements of the subject matter of Examples 72 - 75, where the T-SRI field includes a 1-bit field, and the 1-bit field includes an SPS release indicator value indicating whether the reserved bits for SPS PDSCH release are included within the Type 3 HARQ ACK feedback signal.

[0212] Example 77 is a BS that includes or omits elements of the subject matter of Examples 72 - 76, where the T-SRI field includes a 2-bit field, and the 2-bit field includes an SPS release indicator value that identifies the total number of reserved bits for SPS PDSCH release according to a predefined mapping between the SPS release indicator value and the total number of reserved bits for SPS PDSCH release.

[0213] Example 78 is a BS that includes or omits elements of the subject matter of Examples 72 - 77, where one or more reserved bits for SPS PDSCH release are appended to the end of the Type 3 HARQ-ACK feedback signal.

[0214] Example 79 is a BS that includes or omits elements of the subject matter of Examples 72 - 78, where one or more reserved bits for SPS PDSCH release are appended to the beginning of the Type 3 HARQ-ACK feedback signal.

[0215] Example 80 is a BS that includes or omits elements of the subject matter of Examples 72 - 79, where one or more HARQ-ACK bits for SPS PDSCH release correspond to bit positions associated with the HARQ process of the corresponding SPS PDSCH within the Type 3 HARQ-ACK feedback signal.

[0216] Example 81 is a BS that includes or omits elements of the subject matter of Examples 72 - 80, where one or more HARQ-ACK bits for SPS PDSCH release correspond to bit positions associated with the HARQ process identified by a predefined HARQ Process Identifier (HPI), where the HPI is indicated to the UE via Radio Resource Control (RRC) signaling.

[0217] Embodiment 82 is a baseband (BB) processor for a UE, the BB processor being configured to perform operations that include receiving downlink control information (DCI) from a base station associated with the UE, where the DCI includes an indication for triggering a type 3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal; receiving a type 3 HARQ ACK feedback signal based on processing the DCI, where the type 3 HARQ ACK feedback signal includes one or more HARQ-ACK bits for a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release, and where each HARQ-ACK bit among the one or more HARQ-ACK bits for the SPS PDSCH release is adapted to include HARQ-ACK information for the SPS PDSCH release associated with the UE; and transmitting the type 3 HARQ-ACK feedback signal to the base station.

[0218] Embodiment 83 is a BB processor including the subject matter of Embodiment 82, where the one or more HARQ-ACK bits for the SPS PDSCH release include one or more reserved bits reserved to respectively include HARQ-ACK information for one or more SPS PDSCH releases.

[0219] Embodiment 84 is a BB processor including or omitting elements of the subject matter of Embodiments 82 - 83, where the DCI further includes information on the number of reserved bits, the reserved bits including the one or more reserved bits for the SPS PDSCH release to be included in the type 3 HARQ-ACK feedback signal.

[0220] Embodiment 85 is a BB processor including or omitting elements of the subject matter of Embodiments 82 - 84, where the DCI further includes a total SPS release indicator (T-SRI) field, the T-SRI field including information enabling identification of the total number of reserved bits, the reserved bits including the one or more reserved bits for the SPS PDSCH release to be included within the type 3 HARQ-ACK feedback signal.

[0221] Embodiment 86 is a BB processor including or omitting elements of the subject matter of Embodiments 82 - 85, where the T-SRI field includes a 1-bit field, the 1-bit field including an SPS release indicator value indicating whether the reserved bits for the SPS PDSCH release are included in the type 3 HARQ ACK feedback signal.

[0222] Embodiment 87 is a BB processor including or omitting elements of the subject matter of Embodiments 82 - 86, where when the SPS release indicator value indicates the inclusion of a reserved bit for SPS PDSCH release, the total number of reserved bits is determined based on the total number of HARQ processes for downlink (DL) SPS configured for the UE.

[0223] Embodiment 88 is a BB processor including or omitting elements of the subject matter of Embodiments 82 - 87, where the T - SRI field includes a 2 - bit field that includes an SPS release indicator value that identifies the total number of reserved bits for SPS PDSCH release according to a predefined mapping between the SPS release indicator value and the total number of reserved bits for SPS PDSCH release.

[0224] Embodiment 89 is a BB processor including or omitting elements of the subject matter of Embodiments 82 - 88, where one or more reserved bits for SPS PDSCH release are appended to the end of a type 3 HARQ - ACK feedback signal.

[0225] Embodiment 90 is a BB processor including or omitting elements of the subject matter of Embodiments 82 - 89, where one or more reserved bits for SPS PDSCH release are appended to the beginning of a type 3 HARQ - ACK feedback signal.

[0226] Embodiment 91 is a BB processor including or omitting elements of the subject matter of Embodiments 82 - 90, where one or more HARQ - ACK bits for SPS PDSCH release correspond to the bit positions associated with the HARQ process of the corresponding SPS PDSCH within the type 3 HARQ - ACK feedback signal.

[0227] Embodiment 92 is a BB processor including or omitting elements of the subject matter of Embodiments 82 - 91, where one or more HARQ - ACK bits for SPS PDSCH release correspond to the bit positions associated with the HARQ process identified by a HARQ process identifier (HPI), where the HPI is indicated to the UE via radio resource control (RRC) signaling.

[0228] Embodiment 93 is a baseband (BB) processor for a base station, the BB processor being configured to perform operations including sending downlink control information (DCI) to a user equipment (UE) associated with the base station, where the DCI includes an indication to the UE for triggering a type 3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal; and receiving a type 3 HARQ ACK feedback signal from the UE in response to providing the DCI, where the type 3 HARQ ACK feedback signal includes one or more HARQ-ACK bits for semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release, and where each HARQ-ACK bit among the one or more HARQ-ACK bits for SPS PDSCH release is adapted to include HARQ-ACK information for SPS PDSCH release associated with the UE.

[0229] Embodiment 94 is a BB processor including the subject matter of Embodiment 93, where the one or more HARQ-ACK bits for SPS PDSCH release include one or more reserved bits reserved to respectively include HARQ-ACK information for one or more SPS PDSCH releases.

[0230] Embodiment 95 is a BB processor including or omitting elements of the subject matter of Embodiments 93-94, where the DCI further includes information on the number of reserved bits, the reserved bits including the one or more reserved bits for SPS PDSCH release to be included in the type 3 HARQ ACK feedback signal.

[0231] Embodiment 96 is a BB processor including or omitting elements of the subject matter of Embodiments 93-95, where the DCI further includes a total SPS release indicator (T-SRI) field, the T-SRI field including information enabling identification of the total number of reserved bits, the reserved bits including the one or more reserved bits for SPS PDSCH release to be included within the type 3 HARQ-ACK feedback signal.

[0232] Embodiment 97 is a BB processor including or omitting elements of the subject matter of Embodiments 93-96, where the T-SRI field includes a 1-bit field, the 1-bit field including an SPS release indicator value indicating whether the reserved bits for SPS PDSCH release are included in the type 3 HARQ ACK feedback signal.

[0233] Example 98 is a BB processor including or omitting elements of the subject matter of Examples 93-97, where the T-SRI field includes a 2-bit field that includes an SPS release indicator value, and the SPS release indicator value identifies the total number of reserved bits for SPS PDSCH release according to a predefined mapping between the SPS release indicator value and the total number of reserved bits for SPS PDSCH release.

[0234] Example 99 is a BB processor including or omitting elements of the subject matter of Examples 93-98, where one or more reserved bits for SPS PDSCH release are appended to the end of a type 3 HARQ-ACK feedback signal.

[0235] Example 100 is a BB processor including or omitting elements of the subject matter of Examples 93-99, where one or more reserved bits for SPS PDSCH release are appended to the beginning of a type 3 HARQ-ACK feedback signal.

[0236] Example 101 is a BB processor including or omitting elements of the subject matter of Examples 93-100, where one or more HARQ-ACK bits for SPS PDSCH release correspond to bit positions associated with the HARQ process associated with the corresponding SPS PDSCH within the type 3 HARQ-ACK feedback signal.

[0237] Example 102 is a BB processor including or omitting elements of the subject matter of Examples 93-101, where one or more HARQ-ACK bits for SPS PDSCH release correspond to bit positions associated with the HARQ process identified by a predefined HARQ process identifier (HPI), and the HPI is indicated to the UE via radio resource control (RRC) signaling.

[0238] Embodiment 103 is a method for a user equipment (UE), the method comprising receiving, by use of one or more processors, downlink control information (DCI) from a base station associated with the UE, wherein the DCI includes an indication for triggering a type 3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal; receiving, by use of one or more processors, a type 3 HARQ ACK feedback signal based on processing the DCI, wherein the type 3 HARQ ACK feedback signal includes one or more HARQ-ACK bits for a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release, and wherein each HARQ-ACK bit of the one or more HARQ-ACK bits for the SPS PDSCH release is adapted to include HARQ-ACK information for the SPS PDSCH release associated with the UE; and transmitting, by use of one or more processors, the type 3 HARQ-ACK feedback signal to the base station.

[0239] Embodiment 104 is a method including the subject matter of Embodiment 103, wherein the one or more HARQ-ACK bits for the SPS PDSCH release include one or more reserved bits reserved to respectively include HARQ-ACK information for one or more SPS PDSCH releases.

[0240] Embodiment 105 is a method including or omitting elements including the subject matter of Embodiments 103-104, wherein the DCI further includes information on the number of reserved bits, the reserved bits including the one or more reserved bits for the SPS PDSCH release to be included in the type 3 HARQ-ACK feedback signal.

[0241] Embodiment 106 is a method including or omitting elements including the subject matter of Embodiments 103-105, wherein the DCI further includes a total SPS release indicator (T-SRI) field, the T-SRI field including information enabling identification of the total number of reserved bits, the reserved bits including the one or more reserved bits for the SPS PDSCH release to be included within the type 3 HARQ-ACK feedback signal.

[0242] Embodiment 107 is a method including or omitting elements including the subject matter of Embodiments 103-106, wherein the T-SRI field includes a 1-bit field, the 1-bit field including an SPS release indicator value indicating whether the reserved bits for the SPS PDSCH release are included in the type 3 HARQ ACK feedback signal.

[0243] Embodiment 108 is a method of including or omitting elements including the subject matter of Embodiments 103-107, wherein when the SPS release indicator value indicates the inclusion of reserved bits for SPS PDSCH release, the total number of reserved bits is determined based on the total number of HARQ processes for downlink (DL) SPS configured for the UE.

[0244] Embodiment 109 is a method of including or omitting elements including the subject matter of Embodiments 103-108, wherein the T-SRI field includes a 2-bit field that includes an SPS release indicator value that identifies the total number of reserved bits for SPS PDSCH release according to a predefined mapping between the SPS release indicator value and the total number of reserved bits for SPS PDSCH release.

[0245] Embodiment 110 is a method of including or omitting elements including the subject matter of Embodiments 103-109, wherein one or more reserved bits for SPS PDSCH release are appended to the end of a type 3 HARQ-ACK feedback signal.

[0246] Embodiment 111 is a method of including or omitting elements including the subject matter of Embodiments 103-110, wherein one or more reserved bits for SPS PDSCH release are appended to the beginning of a type 3 HARQ-ACK feedback signal.

[0247] Embodiment 112 is a method of including or omitting elements including the subject matter of Embodiments 103-111, wherein one or more HARQ-ACK bits for SPS PDSCH release correspond to the bit positions associated with the HARQ process of the corresponding SPS PDSCH within the type 3 HARQ-ACK feedback signal.

[0248] Embodiment 113 is a method of including or omitting elements including the subject matter of Embodiments 103-112, wherein one or more HARQ-ACK bits for SPS PDSCH release correspond to the bit positions associated with the HARQ process identified by a HARQ process identifier (HPI), where the HPI is indicated to the UE via radio resource control (RRC) signaling.

[0249] Embodiment 114 is a method for a base station, the method including transmitting, using one or more processors, downlink control information (DCI) to a user equipment (UE) associated with the base station, where the DCI includes an indication to the UE for triggering a type 3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal; and receiving, in response to providing the DCI, using one or more processors, a type 3 HARQ ACK feedback signal from the UE, where the type 3 HARQ ACK feedback signal includes one or more HARQ-ACK bits for a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release, and where each HARQ-ACK bit of the one or more HARQ-ACK bits for the SPS PDSCH release is adapted to include HARQ-ACK information for the SPS PDSCH release associated with the UE.

[0250] Embodiment 115 is a method including the subject matter of Embodiment 114, where the one or more HARQ-ACK bits for the SPS PDSCH release include one or more reserved bits reserved to respectively include HARQ-ACK information for one or more SPS PDSCH releases.

[0251] Embodiment 116 is a method including or omitting elements including the subject matter of Embodiments 113 - 114, where the DCI further includes information on the number of reserved bits, the reserved bits including the one or more reserved bits for the SPS PDSCH release to be included in the type 3 HARQ-ACK feedback signal.

[0252] Embodiment 117 is a method including or omitting elements including the subject matter of Embodiments 113 - 116, where the DCI further includes a total SPS release indicator (T-SRI) field, the T-SRI field including information enabling identification of the total number of reserved bits, the reserved bits including the one or more reserved bits for the SPS PDSCH release to be included within the type 3 HARQ-ACK feedback signal.

[0253] Embodiment 118 is a method including or omitting elements including the subject matter of Embodiments 113 - 117, where the T-SRI field includes a 1-bit field, the 1-bit field including an SPS release indicator value indicating whether the reserved bits for the SPS PDSCH release are included in the type 3 HARQ ACK feedback signal.

[0254] Embodiment 119 is a method of including or omitting elements of the subject matter of Embodiments 113-118, wherein the T-SRI field includes a 2-bit field, the 2-bit field includes an SPS release indicator value, and the SPS release indicator value identifies the total number of reserved bits for SPS PDSCH release according to a predefined mapping between the SPS release indicator value and the total number of reserved bits for SPS PDSCH release.

[0255] Embodiment 120 is a method of including or omitting elements of the subject matter of Embodiments 113-119, wherein one or more reserved bits for SPS PDSCH release are appended to the end of a type 3 HARQ-ACK feedback signal.

[0256] Embodiment 121 is a method of including or omitting elements of the subject matter of Embodiments 113-120, wherein one or more reserved bits for SPS PDSCH release are appended to the beginning of a type 3 HARQ-ACK feedback signal.

[0257] Embodiment 122 is a method of including or omitting elements of the subject matter of Embodiments 113-121, wherein one or more HARQ-ACK bits for SPS PDSCH release correspond to bit positions associated with the HARQ process of the corresponding SPS PDSCH within the type 3 HARQ-ACK feedback signal.

[0258] Embodiment 123 is a method of including or omitting elements of the subject matter of Embodiments 113-122, wherein one or more HARQ-ACK bits for SPS PDSCH release correspond to bit positions associated with the HARQ process identified by a predefined HARQ process identifier (HPI), where the HPI is indicated to the UE via radio resource control (RRC) signaling.

[0259] Embodiment 124 is a UE including or omitting elements of the subject matter of Embodiments 1-10, wherein the HARQ-ACK feedback signal triggered by DCI includes a type 1 HARQ-ACK codebook.

[0260] Embodiment 125 is a UE including or omitting elements of the subject matter of Embodiments 1-10, wherein the HARQ-ACK feedback signal triggered by DCI includes a type 3 HARQ-ACK codebook.

[0261] Embodiment 126 is a BS including or omitting elements of the subject matter of Embodiments 11-20, wherein the HARQ-ACK feedback signal triggered by DCI includes a type 1 HARQ-ACK codebook.

[0262] Embodiment 127 is a BS including or omitting elements of the subject matter of Embodiments 11 - 20, wherein the HARQ-ACK feedback signal triggered by DCI includes a Type 3 HARQ-ACK codebook.

[0263] Embodiment 128 is a UE including or omitting elements of the subject matter of Embodiments 61 - 71, wherein the operations further include: determining whether to transmit a Type 3 HARQ-ACK feedback signal and HARQ-ACK information associated with SPS PDSCH release to the base station in the same time slot, and then generating a Type 3 HARQ ACK feedback signal based on the determination and including HARQ-ACK information corresponding to the SPS PDSCH release among the HARQ-ACK bits for one or more HARQ-ACK bits for SPS PDSCH release in the Type 3 HARQ-ACK feedback signal.

[0264] Embodiment 129 is a BB processor including or omitting elements of the subject matter of Embodiments 82 - 92, wherein the operations further include: determining whether to transmit a Type 3 HARQ-ACK feedback signal and HARQ-ACK information associated with SPS PDSCH release to the base station in the same time slot, and then generating a Type 3 HARQ ACK feedback signal based on the determination and including HARQ-ACK information corresponding to the SPS PDSCH release among the HARQ-ACK bits for one or more HARQ-ACK bits for SPS PDSCH release in the Type 3 HARQ-ACK feedback signal.

[0265] Although the invention has been shown and described with respect to one or more particular embodiments, changes and / or modifications may be made to the illustrated examples without departing from the spirit and scope of the appended claims. In particular, with respect to the various functions performed by the above-described components or structures (components, devices, circuits, systems, etc.), unless otherwise specified, the terms used to describe such components (including references to "means") are intended to correspond to any component or structure that performs the specified function of the described component (e.g., functionally equivalent), even if not structurally equivalent to the disclosed structure that performs the functions in the exemplary specific embodiments of the invention shown herein.

[0266] The above description of the exemplary embodiments of the subject matter of the present disclosure, which includes what is described in the abstract of the specification, is not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. While specific embodiments and examples are described herein for illustrative purposes, various modifications can be contemplated within the scope of such embodiments and examples, as will be recognized by those skilled in the relevant art.

Claims

1. A user equipment (UE) device for communication, the UE device comprising a processor configured to perform operations including the following: Receive downlink control information (DCI) from a base station associated with the UE device, wherein the DCI includes an indication for triggering a type 3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal, and wherein the DCI further includes information on the number of reserved bits having one or more reserved bits reserved to include HARQ-ACK information for one or more semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) releases, the one or more SPS PDSCH releases to be included in the type 3 HARQ-ACK feedback signal; Generate the type 3 HARQ ACK feedback signal based on processing the DCI, wherein the type 3 HARQ ACK feedback signal includes the one or more reserved bits, and wherein each of the one or more reserved bits is adapted to include HARQ-ACK information for an SPS PDSCH release associated with the UE; and Transmit the type 3 HARQ-ACK feedback signal to the base station.

2. The UE device according to claim 1, wherein the DCI further includes a total SPS release indicator (T-SRI) field, the T-SRI field including information enabling identification of the total number of reserved bits, the reserved bits including the one or more reserved bits to be included within the type 3 HARQ-ACK feedback signal.

3. The UE device according to claim 2, wherein the T-SRI field includes a 1-bit field, the 1-bit field including an SPS release indicator value indicating the one or more reserved bits included in the type 3 HARQ ACK feedback signal.

4. The UE device according to claim 3, wherein when the SPS release indicator value indicates inclusion of the one or more reserved bits, the total number of reserved bits is determined based on the total number of HARQ processes for downlink (DL) SPS configured for the UE.

5. The UE device according to claim 2, wherein the T-SRI field includes a 2-bit field, the 2-bit field including an SPS release indicator value that identifies the total number of reserved bits for SPS PDSCH releases according to a predefined mapping between the SPS release indicator value and the total number of reserved bits.

6. The UE device according to claim 2, wherein the one or more reserved bits are appended at the end of the type 3 HARQ-ACK feedback signal.

7. The UE device according to claim 2, wherein the one or more reserved bits are appended at the beginning of the type 3 HARQ-ACK feedback signal.

8. The UE device according to claim 1, wherein the operation further comprises: Determine whether to send the type 3 HARQ-ACK feedback signal and the HARQ-ACK information associated with the SPS PDSCH release in the same time slot to the base station, and then generate the type 3 HARQ ACK feedback signal based on the determination and include the HARQ-ACK information corresponding to the SPS PDSCH release in the HARQ-ACK bits of the one or more reserved bits in the type 3 HARQ-ACK feedback signal.

9. A base station BS for communication, the BS includes a processor configured to perform operations, the operations include: Send downlink control information DCI to a user equipment UE associated with the base station, where the DCI includes an indication to the UE for triggering a type 3 hybrid automatic repeat request HARQ acknowledgment ACK feedback signal, and where the DCI further includes information on the number of reserved bits having one or more reserved bits, the one or more reserved bits being reserved to include HARQ-ACK information for one or more semi-persistent scheduling SPS physical downlink shared channel PDSCH releases, the one or more SPS PDSCH releases to be included in the type 3 HARQ-ACK feedback signal; And In response to providing the DCI, receive the type 3 HARQ ACK feedback signal from the UE, where the type 3 HARQ ACK feedback signal includes the one or more reserved bits, and where each of the one or more reserved bits is adapted to include HARQ-ACK information for an SPS PDSCH release associated with the UE.

10. The BS according to claim 9, where the DCI further includes a total SPS release indicator T-SRI field, the T-SRI field includes information enabling identification of the total number of reserved bits, the reserved bits including the one or more reserved bits to be included in the type 3 HARQ-ACK feedback signal.

11. The BS according to claim 10, where the T-SRI field includes a 1-bit field, the 1-bit field includes an SPS release indicator value indicating the one or more reserved bits included in the type 3 HARQ ACK feedback signal.

12. The BS according to claim 10, where the T-SRI field includes a 2-bit field, the 2-bit field includes an SPS release indicator value, the SPS release indicator value identifying the total number of reserved bits according to a predefined mapping between the SPS release indicator value and the total number of reserved bits for the SPS PDSCH release.

13. The BS according to claim 9, where the one or more reserved bits are appended at the end of the type 3 HARQ-ACK feedback signal.

14. The BS according to claim 9, where the one or more reserved bits are appended at the beginning of the type 3 HARQ-ACK feedback signal.

15. A baseband (BB) processor for a user equipment (UE) used for communication, the BB processor being configured to perform operations, the operations including: Receiving downlink control information (DCI) from a base station associated with the UE, wherein the DCI includes an indication for triggering a type 3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal, and wherein the DCI further includes information on the number of reserved bits having one or more reserved bits reserved to include HARQ-ACK information for one or more semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) releases, and the one or more SPS PDSCH releases are to be included in the type 3 HARQ-ACK feedback signal; Generating the type 3 HARQ ACK feedback signal based on processing the DCI, wherein the type 3 HARQ ACK feedback signal includes the one or more reserved bits, and each of the one or more reserved bits is adapted to include HARQ-ACK information for an SPS PDSCH release associated with the UE; and Sending the type 3 HARQ-ACK feedback signal to the base station.

16. The BB processor according to claim 15, wherein the DCI further includes a total SPS release indicator (T-SRI) field, the T-SRI field including information enabling identification of the total number of reserved bits, the reserved bits including the one or more reserved bits to be included within the type 3 HARQ-ACK feedback signal.

17. The BB processor according to claim 16, wherein the T-SRI field includes a 1-bit field, the 1-bit field including an SPS release indicator value indicating the one or more reserved bits included in the type 3 HARQ ACK feedback signal.

18. The BB processor according to claim 17, wherein when the SPS release indicator value indicates inclusion of the one or more reserved bits, the total number of reserved bits is determined based on the total number of HARQ processes for downlink (DL) SPS configured for the UE.

19. The BB processor according to claim 16, wherein the T-SRI field includes a 2-bit field, the 2-bit field including an SPS release indicator value that identifies the total number of reserved bits according to a predefined mapping between the SPS release indicator value and the total number of reserved bits for SPS PDSCH releases.

20. The BB processor according to claim 15, wherein the one or more reserved bits are appended at the end of the type 3 HARQ-ACK feedback signal.

21. The BB processor according to claim 15, wherein the one or more reserved bits are appended at the beginning of the type 3 HARQ-ACK feedback signal.

22. The BB processor according to claim 15, wherein the operation further comprises: Determine whether to send the type 3 HARQ-ACK feedback signal and the HARQ-ACK information associated with the SPS PDSCH release to the base station in the same time slot, and then generate the type 3 HARQ ACK feedback signal based on the determination and include the HARQ-ACK information corresponding to the SPS PDSCH release in the HARQ-ACK bits of the one or more reserved bits in the type 3 HARQ-ACK feedback signal.

23. A baseband BB processor for a base station used for communication, the BB processor being configured to perform operations, the operations including: Send downlink control information DCI to a user equipment UE associated with the base station, where the DCI includes an indication to the UE for triggering a type 3 hybrid automatic repeat request HARQ acknowledgement ACK feedback signal, and where the DCI further includes information on the number of reserved bits having one or more reserved bits, the one or more reserved bits being reserved to include HARQ-ACK information for one or more semi-persistent scheduling SPS physical downlink shared channel PDSCH releases, the one or more SPS PDSCH releases being to be included in the type 3 HARQ-ACK feedback signal; And In response to providing the DCI, receive the type 3 HARQ ACK feedback signal from the UE, where the type 3 HARQ ACK feedback signal includes the one or more reserved bits, and where each of the one or more reserved bits is adapted to include HARQ-ACK information for an SPS PDSCH release associated with the UE.

24. The BB processor according to claim 23, where the DCI further includes a total SPS release indicator T-SRI field, the T-SRI field including information enabling identification of the total number of reserved bits, the reserved bits including the one or more reserved bits to be included in the type 3 HARQ-ACK feedback signal.

25. The BB processor according to claim 24, where the T-SRI field includes a 1-bit field, the 1-bit field including an SPS release indicator value indicating the one or more reserved bits included in the type 3 HARQ ACK feedback signal.

26. The BB processor according to claim 24, where the T-SRI field includes a 2-bit field, the 2-bit field including an SPS release indicator value, the SPS release indicator value identifying the total number of reserved bits according to a predefined mapping between the SPS release indicator value and the total number of reserved bits for the SPS PDSCH release.

27. The BB processor according to claim 23, where the one or more reserved bits are appended to the end of the type 3 HARQ-ACK feedback signal.

28. The BB processor according to claim 23, wherein the one or more reserved bits are appended at the beginning of the type 3 HARQ-ACK feedback signal.

Images