Patent ID: 12206502

DETAILED DESCRIPTION

In one embodiment of the disclosure, a user equipment (UE) is disclosed. The UE comprises a processor (or processing circuitry) configured to perform operations comprising receiving a hybrid automatic repeat request process group (HPG) configuration signal from a base station associated therewith. In some embodiments, the HPG configuration signal comprises information of a plurality HARQ process groups (HPGs), each HPG comprising one or more HARQ processes of a set of HARQ processes configured for the UE. The operation further comprises determining the plurality of HPGs associated with the set of HARQ processes configured for the UE, based on processing the HPG configuration signal and receiving a downlink control information (DCI) from the base station. In some embodiments, the DCI is configured to trigger a HARQ-ACK feedback signal from the UE and the DCI comprises information that identifies one or more HPGs of the plurality of HPGs, the HARQ-ACK feedback information of which are to be included in the HARQ-ACK feedback signal. In addition, the operations comprise generating the HARQ-ACK feedback signal comprising the HARQ-ACK feedback information of HARQ processes associated with the one or more HPGs; and sending the HARQ-ACK feedback signal to the base station.

In one embodiment of the disclosure, a base station (BS) is disclosed. The BS comprises a processor (or processing circuitry) configured to perform operations comprising sending a hybrid automatic repeat request process group (HPG) configuration signal to a user equipment (UE) associated therewith. In some embodiments, the HPG configuration signal comprises information of a plurality HARQ process groups (HPGs), each HPG comprising one or more HARQ processes of a set of HARQ processes configured for the UE. The operations further comprise sending a downlink control information (DCI) to the UE. In some embodiments, the DCI is configured to trigger a HARQ-ACK feedback signal from the UE and the DCI comprises information that identifies one or more HPGs of the plurality of HPGs, HARQ-ACK feedback information of which are to be included in the HARQ-ACK feedback signal. In addition, the operations comprise receiving the HARQ-ACK feedback signal from the UE. In some embodiments, the HARQ-ACK feedback signal comprises the HARQ-ACK feedback information of HARQ processes associated with the one or more HPGs.

In one embodiment of the disclosure, a baseband (BB) processor for a user equipment (UE) is disclosed. The BB processor is configured to perform operations comprising receiving a hybrid automatic repeat request process group (HPG) configuration signal from a base station associated therewith. In some embodiments, the HPG configuration signal comprises information of a plurality HARQ process groups (HPGs), each HPG comprising one or more HARQ processes of a set of HARQ processes configured for the UE. The operations further comprise determining the plurality of HPGs associated with the set of HARQ processes configured for the UE, based on processing the HPG configuration signal. Furthermore, the operations comprise receiving a downlink control information (DCI) from the base station. In some embodiments, the DCI is configured to trigger a HARQ-ACK feedback signal from the UE and the DCI comprises information that identifies one or more HPGs of the plurality of HPGs, the HARQ-ACK feedback information of which are to be included in the HARQ-ACK feedback signal. In addition, the operations comprise generating the HARQ-ACK feedback signal comprising the HARQ-ACK feedback information of HARQ processes associated with the one or more HPGs; and sending the HARQ-ACK feedback signal to the base station.

In one embodiment of the disclosure, a baseband (BB) processor for a base station (BS) is disclosed. The BB processor is configured to perform operations comprising sending a hybrid automatic repeat request process group (HPG) configuration signal to a user equipment (UE) associated therewith. In some embodiments, the HPG configuration signal comprises information of a plurality HARQ process groups (HPGs), each HPG comprising one or more HARQ processes of a set of HARQ processes configured for the UE. The operations further comprise sending a downlink control information (DCI) to the UE. In some embodiments, the DCI is configured to trigger a HARQ-ACK feedback signal from the UE and the DCI comprises information that identifies one or more HPGs of the plurality of HPGs, HARQ-ACK feedback information of which are to be included in the HARQ-ACK feedback signal. In addition, the operations comprise receiving the HARQ-ACK feedback signal from the UE. In some embodiments, the HARQ-ACK feedback signal comprises the HARQ-ACK feedback information of HARQ processes associated with the one or more HPGs.

The present disclosure will now be described with reference to the attached drawing figures, wherein like reference numerals are used to refer to like elements throughout, and wherein the illustrated structures and devices are not necessarily drawn to scale. As utilized herein, terms “component,” “system,” “interface,” “circuit” and the like are intended to refer to a computer-related entity, 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 a processor, a controller, an object, an executable, a program, a storage device, a computer, a tablet PC and/or a user equipment (e.g., mobile phone, etc.) with a processing device. By way of illustration, an application running on a server and the server can also be a component. One or more components can reside within a process, and a component can be localized on one computer and/or distributed between two or more computers. A set of elements or a set of other components can be described herein, in which the term “set” can be interpreted as “one or more.”

Further, these components can execute from various computer readable storage media having various data structures stored thereon such as with a module, for example. The components can communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network, such as, the Internet, a local area network, a wide area network, or similar network with other systems via the signal).

As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, in which the electric or electronic circuitry can be operated by a software application or a firmware application executed by one or more processors. The one or more processors can be internal or external to the apparatus and can execute at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts; the electronic components can include one or more processors therein to execute software and/or firmware that confer(s), at least in part, the functionality of the electronic components.

Use of the word exemplary is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the event that the terms “including”, “includes”, “having”, “has”, “with”, or variants thereof are used in either the detailed description and the claims, such terms are intended to be inclusive in a manner similar to the term “comprising.”

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain 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.

It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

As indicated above, HARQ process relies upon receiving ACK/NACK for the data packets. When a base station (BS) sends data/transmission to a user equipment (UE) through physical downlink shared channel (PDSCH), the UE determines it's correctness by checking cyclic redundancy check (CRC) and report it to base station through ACK/NACK bit. If the UE also has data to send and it gets a grant, it'll send ACK/NACK on physical uplink shared channel (PUSCH) along with data, otherwise it'll send it on physical uplink control channel (PUCCH). A HARQ-ACK codebook defines the format used to signal a set of HARQ acknowledgements (ACKs) to the base station. The codebook allows the UE to multiplex the HARQ ACKs from multiple slots, multiple carriers, multiple transport blocks and multiple code block groups (CBGs) within a single transmission. It is important that both UE and base station share the same understanding of the codebook format to ensure that each acknowledgement 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 signaling. Different categories of HARQ-ACK codebooks are defined in 3GPP. For example, a Type-1 HARQ-ACK codebook comprising a semi-static codebook where the size of the codebook is fixed by information provided by radio resource control (RRC) signaling and a Type-2 HARQ-ACK codebook comprising a dynamic codebook where the size of the codebook changes according to the number of resource allocations. Further, a Type-3 HARQ-ACK codebook is defined that is triggered on demand by a one-shot HARQ-ACK frequent field in the DCI.

There are two types of scheduling for downlink. One is called ‘Dynamic Scheduling’ and the other one Semi Persistent Scheduling (SPS). Dynamic scheduling is the mechanism in which each and every PDSCH is scheduled by DCI (e.g., DCI 1_0 or DCI 1_1). SPS is the mechanism in which the PDSCH transmission is configured by radio resource control (RRC) message. SPS is a feature that significantly reduces control channel overhead for applications that require persistent radio resource allocations such as VoIP. In dynamic scheduling, both the downlink (DL) and uplink (UL) are fully scheduled since 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. Without SPS, every 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 types of applications which generally have large packet sizes and thus typically only a few users must be scheduled each subframe. However, for applications that require persistent allocations of small packets (i.e. VoIP), the access grant control channel overhead can be greatly reduced with SPS. Once the SPS is configured by an RRC message, the base station activates the SPS using downlink control information (DCI) of PDCCH. Upon activation of SPS, transmission of SPS in UL and DL is performed. As SPS activation, SPS release or SPS PDSCH release is also indicated by the DCI, in some embodiments. Alternately, in other embodiments, the SPS release may be indicated to the UE via RRC signaling or higher layer signaling.

Latest wireless communication technologies like 5G are expected to support a broad range of newly emerging applications on top of the regular cellular mobile broadband services. One of the key usage scenarios in the scope of 5G is ultra-reliable and low-latency communications (URLLC). URLLC will play an essential role in providing connectivity for the new services and applications from vertical domains, such as factory automation, autonomous driving and so on. The most important key performance indicators (KPIs) related to URLLC are latency, reliability and availability. SPS-based PDSCH transmission is widely used for URLLC service type to reduce signaling overhead and improve the reliability. For example, up to 8 DL SPS configurations is supported for a given BWP of a serving cell. In addition, joint release in a DCI for two or more SPS configurations is supported by means of M least significant bit (LSB) HARQ process number (HPN) bits to minimize the signaling overhead.

In current implementations, a 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 a same slot when the SPS release indication is provided by the BS to the UE, the HARQ-ACK information corresponding to the SPS release will be dropped, as the Type-3 HARQ-ACK codebook does not support HARQ-ACK feedback for SPS release. This greatly affects the reliability of URLLC services when the URLLC services utilized SPS based PDSCH transmission. Therefore, enhancement to support of SPS release together with Type-3 HARQ-ACK codebook configuration is important to efficiently operate URLLC traffic on unlicensed band in controlled environment. Disclosed herein are systems, circuitries, and techniques for that supports SPS release together with Type-3 HARQ-ACK codebook configuration.

Further, in current implementations, HARQ-ACK information for multiple DL HARQ processes configured for the UE is included in the HARQ-ACK codebooks. For example, the HARQ-ACK information for all DL HARQ processes configured for the UE are included in the Type-3 HARQ-ACK codebook. However, this affects the reliability of HARQ-ACK feedback for high reliability services like URLLC services, when one or more of the DL HARQ processes configured for the UE includes URLLC services. In order to overcome this disadvantage, disclosed herein are systems, circuitries, and techniques that provide a flexible procedure to control HARQ-ACK codebooks based on grouping HARQ processes to improve reliability, for example, to meet the reliability requirement of URLLC service types.

FIG.1illustrates a simplified block diagram of a wireless communication system100, according to one embodiment of the disclosure. In some embodiments, the wireless communication system100supports SPS release together with Type-3 HARQ-ACK codebook configuration. The wireless communication system100comprises a user equipment (UE)102and a base station (BS)104. In other embodiments, however, the wireless communication system100can comprise a plurality of UEs and is not shown here for clarity purposes. In some embodiments, base station104is equivalent to an eNodeB in LTE systems, gNodeB in 5G new radio (NR) systems etc. In some embodiments, the UE102may comprise a mobile phone, tablet computer, an internet of things (IoT) device, a vehicle-to-everything (V2X) UE, etc. The UE102and the base station104are configured to communicate with one another over a communication medium (e.g., air). In some embodiments, the wireless communication system100supports semi-persistent scheduling (SPS) release together with Type-3 HARQ-ACK codebook configuration, as can be fully appreciated below.

In some embodiments, the BS104is configured to provide a downlink control information (DCI)106to the UE102. The DCI106is provided to the UE102as part of a physical downlink control channel (PDCCH). In some embodiments, the DCI106is configured to trigger a Type-3 hybrid automatic repeat request (HARQ) ACK feedback signal108from the UE102. In such embodiments, the DCI106comprises an indication to trigger the Type-3 HARQ ACK feedback signal108. Specifically, the DCI106comprises a one-shot HARQ-ACK frequent field, a value associated therewith providing an indication to the UE102to trigger the Type-3 HARQ-ACK feedback signal108. For example, when the one-shot HARQ-ACK frequent field comprises a value of 1, the UE102is configured to trigger the Type-3 HARQ-ACK feedback signal108. Alternately, when the one-shot HARQ-ACK frequent field comprises a value of 0, the UE102is configured not to trigger the Type-3 HARQ-ACK feedback signal108. In some embodiments, the DCI106further comprises information of physical uplink control channel (PUCCH)/physical uplink shared channel (PUSCH) resources to be utilized by the UE102for the transmission of the Type-3 HARQ-ACK feedback signal108.

The UE102is configured to receive and process the DCI106. Upon processing the DCI106, when the DCI106comprises the indication to trigger a Type-3 HARQ-ACK feedback signal, the UE102is configured to generate a Type-3 HARQ-ACK feedback signal108. In some embodiments, the Type-3 HARQ-ACK feedback signal108may further be referred to as Type-3 HARQ-ACK CB108or Type-3 HARQ-ACK CB feedback signal108. In some embodiments, the Type-3 HARQ-ACK feedback signal108is configured to include HARQ-ACK information associated with a set of HARQ processes that are configured for the UE102. In some embodiments, the set of HARQ processes configured for the UE102may comprise one or more SPS PDSCHs. In some embodiments, the Type-3 HARQ-ACK feedback signal108further includes one or more HARQ-ACK bits for SPS PDSCH release(s). In some embodiments, each of the one or more HARQ-ACK bits for SPS PDSCH release(s) is adapted to include HARQ-ACK information for an SPS PDSCH release associated with the one or more SPS PDSCHs. In some embodiments, the UE102is further configured to determine whether the Type-3 HARQ-ACK feedback signal108triggered by the DCI106and HARQ-ACK information associated with an SPS release are to be send to the base station104at a same slot, prior to generating the Type-3 HARQ ACK feedback signal108. In such embodiments, the UE102is further configured to include the HARQ-ACK information corresponding to the SPS release in a HARQ-ACK bit of the one or more HARQ-ACK bits for SPS PDSCH release(s) within the Type-3 HARQ-ACK feedback signal108.

More particularly, in the embodiments where the UE102is configured with one or more SPS PDSCHs, when an SPS PDSCH release indication for a select SPS PDSCH of the one or more SPS PDSCHs is received at the UE102or when a select SPS PDSCH of the one or more SPS PDSCHs is released, and it is determined that the UE102is to send the HARQ-ACK information for the select SPS PDSCH release in a same slot when the Type-3 HARQ-ACK feedback signal108is triggered, the UE102is configured to provide HARQ-ACK information for the SPS PDSCH release in a HARQ-ACK bit of the one or more HARQ-ACK bits for SPS PDSCH release(s) within the Type-3 HARQ-ACK feedback signal108. In some embodiments, the UE102is configured to receive an indication to release an SPS PDSCH within the DCI106. Alternately, in other embodiments, the UE102is configured to receive the indication to release the SPS PDSCH via radio resource control (RRC) signaling. Upon generating the Type-3 HARQ-ACK feedback signal108, the UE102is further configured to provide the Type-3 HARQ-ACK feedback signal108to the BS104. The BS204is configured to receive and process the Type-3 HARQ-ACK feedback signal108.

In some embodiments, the one or more HARQ-ACK bits for SPS PDSCH release(s) within the Type-3 HARQ-ACK feedback signal108comprises one or more reserved bits for SPS PDSCH release(s) that are reserved to include HARQ-ACK information for one or more SPS PDSCH release(s), respectively. In such embodiments, no information other than HARQ-ACK information for SPS PDSCH release(s) may be included within the one or more reserved bits for SPS PDSCH release(s). In some embodiments, the one or more reserved bits for SPS PDSCH release(s) are appended at the end of the Type-3 HARQ-ACK feedback signal108. Alternately, in other embodiments, one or more reserved bits for SPS PDSCH release(s) are appended at the start of the Type-3 HARQ-ACK feedback signal108. In some embodiments, the position/location where the one or more reserved bits for SPS PDSCH release(s) are to be appended is preconfigured and provided to the UE102via higher layer signaling.

In some embodiments, the number of reserved bits comprising the one or more reserved bits for SPS PDSCH release(s) that are to be included in the Type-3 HARQ-ACK feedback signal108is indicated to the UE102by the BS104. In some embodiments, the BS104is configured to provide the indication of the number of reserved bits comprising the one or more reserved bits for SPS PDSCH release(s) via the DCI106(e.g., DCI format 1_1, DCI format 1_2 etc.). In some embodiments, the BS104is configured to directly provide the number of reserved bits comprising the one or more reserved bits for SPS PDSCH release(s) via the DCI106. In other embodiments, the DCI106includes a total SPS release indicator (T-SRI) field (i.e., a dedicated filed) comprising information that enables to identify a total number of reserved bits comprising the one or more reserved bits for SPS PDSCH release(s) that are to be included within the Type-3 HARQ ACK feedback signal108.

Specifically, in one embodiment, the T-SRI field comprises a 1-bit field comprising a 1-bit SPS release indicator value that indicates whether reserved bits for SPS PDSCH release(s) are included in Type-3 HARQ ACK feedback signal108or not. For example, “1” for the SPS release indicator value means that reserved bits for SPS PDSCH release(s) are present in Type-3 HARQ ACK feedback signal108and “0” for the SPS release indicator value means that reserved bits for SPS PDSCH release(s) are not present in Type-3 HARQ ACK feedback signal108. If SPS release indicator value within the T-SRI field indicates that the reserved bits for SPS PDSCH release(s) are present, the UE102is configured to determine the total number of reserved bits based on a 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, then total number of reserved bits is 2 and if the total number of HARQ processes for DL SPS configured for the UE is 4, then total number of reserved bits is 4, and so on.

Alternately, in another embodiment, the T-SRI field comprises a 2-bit field comprising a 2-bit SPS release indicator value that identifies the total number of reserved bits for SPS PDSCH release(s). In some embodiments, the 2-bit SPS release indicator value identifies the total number of reserved bits for SPS PDSCH release(s), in accordance with a predefined mapping between the 2-bit SPS release indicator value and the total number of reserved bits for SPS PDSCH release(s), as shown in the Table 1 below.

TABLE 1Predefined mapping between the 2-bit T-SRI field and thetotal number of reserved bits for SPS PDSCH release(s)Number of reserved bits for SPST-SRI FieldPDSCH release(s)0, 01 or 5 or 9 or 130, 12 or 6 or 10 or 141, 03 or 7 or 11 or 151, 10 or 4 or 8 or 12

Table 1 indicates a one to many mapping between the 2-bit SPS release indicator value and the total number of reserved bits for SPS PDSCH release(s). Specifically, each value of the T-SRI field is associated with multiple values of the number of reserved bits. In some embodiments, the UE102is configured to determine a select 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 a total number of HARQ processes for DL SPS configured for the UE and in some embodiments, further based on an actual number of received SRS PDSCH release indications at the UE102. In some embodiments, the total number of reserved bits for SPS PDSCH release(s) is chosen 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 example embodiment, if the T-SRI field comprises 0,1 and the total number of HARQ processes for DL SPS configured for the UE is 4, then the number of reserved bits is chosen to be 2. However, if the T-SRI field comprises 0,1 and the total number of HARQ processes for DL SPS configured for the UE102is 8, then the number of reserved bits could be 2 or 6, based on Table 1. In such embodiments, if the actual number of received SRS PDSCH release indications at the UE102is 4, then the number of reserved bits is chosen to be 6.

Appending reserved bits for SPS PDSCH release to the Type-3 HARQ-ACK feedback signal108, as explained above, increases the HARQ-ACK payload of the Type-3 HARQ-ACK feedback signal108. Therefore, in some embodiments, the one or more HARQ-ACK bits for SPS PDSCH release(s) are included within the Type-3 HARQ-ACK feedback signal108without appending additional bits. For example, in one embodiment, the one or more HARQ-ACK bits for SPS PDSCH release(s) within the Type-3 HARQ-ACK feedback signal108corresponds to bit positions associated with HARQ processes of the corresponding SPS PDSCH within the Type-3 HARQ-ACK feedback signal108. More particularly, when the UE102is configured with a set of HARQ processes for DL SPS, the Type-3 HARQ-ACK feedback signal108comprises a set of bit positions configured to convey HARQ-ACK information for a set of SPS PDSCHs, respectively associated therewith. In some embodiments, HARQ-ACK bits for SPS PDSCH release(s) for the set of SPS PDSCHs are respectively mapped to the bit positions associated with the set of SPS PDSCHs. In another embodiment, the one or more HARQ-ACK bits for SPS PDSCH release(s) within the Type-3 HARQ-ACK feedback signal108corresponds to bit positions respectively associated with one or more HARQ processes, each of which is identified by a respective HARQ process identifier (HPI). In some embodiments, the HPI associated with one or more HARQ processes, the bit positions of which are to be utilized for providing HARQ-ACK information for SPS PDSCH release, are indicated to the UE202by radio resource control (RRC) signaling.

FIG.2aillustrates a simplified block diagram of a wireless communication system200, according to one embodiment of the disclosure. In some embodiments, the wireless communication system200supports group-based HARQ-ACK feedback. The wireless communication system200comprises a user equipment (UE)202and a base station (BS)204. In other embodiments, however, the wireless communication system200can comprise a plurality of UEs and is not shown here for clarity purposes. In some embodiments, base station204is equivalent to an eNodeB in LTE systems, gNodeB in 5G new radio (NR) systems etc. In some embodiments, the UE202may comprise a mobile phone, tablet computer, an internet of things (IoT) device, a vehicle-to-everything (V2X) UE, etc. The UE202and the base station204are configured to communicate with one another over a communication medium (e.g., air).

In some embodiments, the BS204is configured to configure a set of HARQ processes for the UE202. In some embodiments, each HARQ process of the set of HARQ processes is identified by a respective HARQ process identifier (HPI). In some embodiments, the BS204is further configured to group the set of HARQ processes into a plurality of HARQ process groups (HPGs). In some embodiments, each HPG of the plurality of HPGs comprises one or more HARQ processes of the set of HARQ processes configured for the UE202. For example,FIG.2billustrates a set of 16 HARQ processes identified by HP's 0 to 15. Further, the 16 HARQ processes are grouped into 3 HPGs, HPG #0, HPG #1 and HPG #3. The HP's included within each HPG and number of HPGs configured may be different in different embodiments. In some embodiments, the set of HARQ processes are grouped to form the plurality of HPGs in accordance with a reliability requirement of the associated service types. For example, the HPG #0 includes HPI 0/1/2/3 which may be intended to be utilized for ultra-reliable and low-latency communications (URLLC) with highest reliability requirement. Similarly, HPG #1 and HPG #2 may be associated with other reliability requirements. In some embodiments, each HPG may be restricted for dataflows or logical channel IDs having a same priority.

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

Upon configuring the set of HARQ processes into the plurality of HPGs, the BS204is configured to generate an HPG configuration signal206. In some embodiments, the HPG configuration signal206comprises information of the plurality HARQ process groups (HPGs) configured for the UE202. The BS204is further configured to send the HPG configuration signal206to the UE202.FIG.3aandFIG.3bdepicts two possible signal configurations for the HPG configuration signal206. Specifically, inFIG.3a, the plurality of HPGs and the HARQ processes associated therewith are indicated using a respective plurality of HARQProcessGroup fields. In some embodiments, the field HARQProcessGroup identifies an HPG ID and indicates which HARQ processes are included in the HARQ process group (HPG). Each HARQProcessGroup field comprises bits corresponding to the set of HARQ processes configured for the UE202. Each bit has either value 0 (indicating that the corresponding HARQ process is not included in the HPG) or value 1 (indicating that the corresponding HARQ process is included in the HPG).

Further, inFIG.3b, the plurality of HPGs and the HARQ processes associated therewith are indicated using a respectively plurality of PriorityList fields. This type of signaling is applicable when the plurality of HPGs are formed based on the priority class of the associated HARQ processes, as explained above inFIG.2c. In some embodiments, the field PriorityList identifies an HPG with a select priority index and the one or more HARQ process that are associated with the priority index. However, other configurations for the HPG configuration signal206are also contemplated to be within the scope of this disclosure. Upon receiving the HPG configuration signal206from the BS204, the UE202is configured to receive and process the HPG configuration signal206. In some embodiments, the UE202is configured to determine the information of the plurality HARQ process groups (HPGs) configured for the UE202, based on processing the HPG configuration signal206.

Referring back toFIG.2a, in some embodiments, the BS204is further configured to provide a downlink control information (DCI)208to the UE202. In some embodiments, the DCI208is configured to trigger a HARQ-ACK feedback signal210from the UE202. In some embodiments, the HARQ-ACK feedback signal210is configured to include HARQ-ACK information associated with one or more HARQ processes configured for the UE202. In some embodiments, the DCI208comprises information of physical uplink control channel (PUCCH)/physical uplink shared channel (PUSCH) resources to be utilized by the UE102for the transmission of the HARQ-ACK feedback signal210. In some embodiments, the HARQ-ACK feedback signal210comprises a Type-3 HARQ-ACK feedback or a Type-3 HARQ-ACK codebook. In such embodiments, the DCI208comprises a one-shot HARQ-ACK frequent field, a value associated therewith providing an indication to the UE102to trigger a Type-3 HARQ-ACK feedback. Alternately, in other embodiments, the HARQ-ACK feedback signal210may comprise other types of HARQ-ACK signals, for example, Type-1 HARQ-ACK feedback signal or a Type-1 HARQ-ACK codebook. In some embodiments, the Type-1 HARQ-ACK feedback signal is configured by radio resource control (RRC) signaling. In some embodiments, the DCI208is configured to trigger the HARQ-ACK feedback signal210from the UE202, in response to a physical downlink shared channel (PDSCH) scheduled by the DCI208. Alternately, in other embodiments, for example, in the case of Type-3 HARQ-ACK feedback, the DCI208may trigger the HARQ-ACK feedback signal210, without scheduling the PDSCH to the UE202. In some embodiments, the DCI208further comprises information that identifies one or more HPGs of the plurality of HPGs configured for the UE202(by the HPG configuration signal206), the HARQ-ACK feedback information of which are to be included in the HARQ-ACK feedback signal210that is triggered by the DCI208.

Once the BS202provides/sends the DCI208to the UE202, the UE202is configured to receive and process the DCI208. Upon processing the DCI208, the UE202is configured to identify the one or more HPGs identified in the DCI208. Further, the UE202is configured to generate the HARQ-ACK feedback signal210comprising the HARQ-ACK feedback information of HARQ processes associated with the one or more HPGs (indicated by the DCI208). In such embodiments, the HARQ-ACK feedback signal210would not include HARQ-ACK feedback information of HARQ processes associated with other HPGs within the plurality of HPGs that are different from the one or more HPGs indicated in the DCI208. Subsequently, the UE202is configured to provide/send the HARQ-ACK feedback signal210to the BS204.

The DCI208may be configured to indicate to the UE202, the information that identifies one or more HPGs of the plurality of HPGs configured for the UE202, differently in different embodiments. In a first embodiment, an HPG request field comprising an HPG request field value that identifies the one or more HPGs is included as part of the DCI208. In some embodiments, the HPG request field value is mapped to one or more HPGs and serving cell(s), in accordance with a predefined mapping as illustrated in Table 2 below. Specifically, Table 2 indicates a predefined mapping between the HPG request field value and a pair of servings cells, HPG(s).

TABLE 2Predefined mapping between the HPG requestfield value and HPG(s).Value of the HPGRequest FieldDescription00A 1st set {serving cells(s), HPG(s)}configured by higher layers01A 2nd set {serving cells(s), HPG(s)}configured by higher layers10A 3rd set {serving cells(s), HPG(s)}configured by higher layers11A 4th set {serving cells(s), HPG(s)}configured by higher layers

Table 2 above indicates a 2-bit value for the HPG Request Field. However, in other embodiments, the value of the HPG request field may have more or less than 2 bits depending on the number of HPGs configured. Further, the HPGs associated with each set may be different in different embodiments. In such embodiments, the UE202is configured to determine the one or more HPGs, based on processing the DCI208, in accordance with the predefined mapping between the HPG request field value and the one or more HPGs, as given in Table 2 above. For example, if the HPG request filed value indicated in the DCI208is 01, the UE202is configured to provide HARQ-ACK information associated with the 2ndset of HPGs from Table 2, as part of the HARQ-ACK feedback signal210.

In a second embodiment, the DCI208comprises cyclic redundancy check (CRC) bits that are scrambled by a predefined HPG sequence, say [w0, w1 . . . w15]. In some embodiments, the predefined HPG sequence identifies the one or more HPGs, the HARQ-ACK feedback information of which are to be included in the HARQ-ACK feedback signal210. In some embodiments, the predefined HPG sequence identifies the one or more HPGs, based on a predefined mapping between the predefined HPG sequence and the one or more HPGs of the plurality of HPGs. Table 3 illustrates an example mapping between the predefined HPG sequence and the one or more HPGs.

TABLE 3Predefined mapping between the predefinedHPG sequence and HPG sequence valueHPG sequencevalue[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]

Specifically, Table 3 provides a mapping between the predefined sequence and a 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.

TABLE 4Predefined mapping between the predefinedHPG sequence and HPG(s).HPG SequenceValueDescription00A 1st set {serving cells(s), HPG(s)}configured by higher layers01A 2nd set {serving cells(s), HPG(s)}configured by higher layers10A 3rd set {serving cells(s), HPG(s)}configured by higher layers11A 4th set {serving cells(s), HPG(s)}configured by higher layers

In such embodiments, the UE202is configured to descramble the CRC bits to determine the predefined HPG sequence and determine the one or more HPGs, based on the predefined HPG sequence, in accordance with the predefined mapping between the predefined HPG sequence and the one or more HPGs. For example, if the predefined sequence is determined to be [0, 1, 0, 1 . . . , 0], the UE202identifies the corresponding HPG sequence value as “01” from the Table 3 above and determine the one or more HPGs associated with the HPG sequence value “01” from Table 4 above. However, in other embodiments, Table 3 may comprise a direct mapping between the predefined HPG sequence and the one or more HPGs.

In a third embodiment, when the grouping is based on priority class index, the DCI208further includes a priority indicator field that comprises information on a select priority class index (e.g., priority class index 0 inFIG.2c) associated with an HPG configured for the UE202. In such embodiments, the UE202is configured to determine the one or more HARQ processes (e.g., HPI 0/1/8/9 inFIG.2c) associated with the HPG identified by the select priority class index, based on processing the DCI208. Further, the UE202is configured to generate the HARQ-ACK feedback signal210comprising HARQ feedback information of the one or more HARQ processes associated with the select priority class index.

Referring back toFIG.2a, in some embodiments, the BS204is further configured to generate and provide a HARQ process regrouping signal212to the UE202. In some embodiments, the HARQ process regrouping signal212comprises information to regroup the HARQ processes associated with one or more HPGs of the plurality of HPGs configured for the UE202(e.g., by the HPG configuration signal206). In some embodiments, the regrouping information is included in a HARQ regroup media access control (MAC) control element (CE) within the HARQ process regrouping signal208. In some embodiments, the HARQ regroup MAC CE is identified using a dedicated logical channel ID (LCID) in MAC header or sub-header. In a first embodiment, the HARQ process regrouping signal212comprises one or more HARQ regroup MAC CEs, each HARQ regroup MAC CE being associated with a respective HPG identifier (ID) that identifies an HPG of the plurality of HPGs configured for the UE202. Each HARQ regroup MAC CE (as illustrated inFIG.4a) has a fixed size and comprises a plurality of octets containing a respective HPGID and a set of H-fields that corresponds to the set of HARQ processes configured for the UE. In some embodiments, each H-field of the set of H-fields identifies a HARQ process of the set of HARQ processes configured for the UE202. In some embodiments, a value associated with each H-field of the set of H-fields identifies one or more HARQ processes that are included within an HPG identified by the respective HPGID.

FIG.4aillustrates an example HARQ regroup MAC CE400associated with the first embodiment. The HARQ regroup MAC CE400is associated with a select HPG identified by an HPGID. The HARQ regroup MAC CE400has 3 octets, Octet #1, Octet #2 and Octet #3. The HARQ regroup MAC CE400further includes 16 H-fields (can be different in other embodiments) that correspond to a set of 16 HARQ processes configured for the UE202. Each of the H-fields is identified as Hi, where i identifies the corresponding HARQ process. If the Hi field is set as “1”, it can be identified that the corresponding HARQ process is included in the HPG identified by the HPGID. Alternately, if the Hi field is set as “0”, it can be identified 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 a default HPG. In some embodiments, the default HPG is configured by higher layers.

In a second embodiment, the HARQ process regrouping signal212comprises a HARQ regroup MAC CE that comprises one or more set of H-fields respectively associated with one or more HPGs of plurality of HPGs configured for the UE202. The HARQ regroup MAC CE has a fixed size and comprises a plurality of octets comprising the one or more sets of H-fields. Each set of H-fields of the one or more sets of H-fields corresponds to the set of HARQ processes configured for the UE. Specifically, each H-field within a set of H-fields of the one or more sets of H-fields identifies a HARQ process of the set of HARQ processes configured for the UE202. In some embodiments, a value associated with each H-field of the set of H-fields associated with an HPG identifies one or more HARQ processes that are included within the HPG.

FIG.4billustrates an example HARQ regroup MAC CE450associated with the second embodiment. The HARQ regroup MAC CE450is associated with N HPGs identified by the HPG IDs HPG #0 . . . HPG #N−1. The HARQ regroup MAC CE400further includes 16 H-fields (can be different in other embodiments) per HPGID, wherein the 16 H-fields (can be different in other embodiments) correspond to a set of 16 HARQ processes configured for the UE202. Each of the H-fields is identified as Hg,i, where g identifies the HPGID and i identifies the corresponding HARQ process. If the Hg,i, field is set as “1”, it can be identified that the HARQ process i is included in the HPG g. Alternately, if the Hg,i, field is set as “0”, it can be identified that the HARQ process i is excluded from the HPG g. Referring back toFIG.2a, the UE202is further configured to receive and process the HARQ process regrouping signal208. Upon processing the HARQ process regrouping signal208, the UE202is configured to determine a plurality of updated HPGs configured for the UE202.

FIG.5illustrates a simplified block diagram of a wireless communication system500, according to one embodiment of the disclosure. In some embodiments, the wireless communication system500facilitates to provide new data indicator (NDI) as part of HARQ-ACK feedback. The wireless communication system500comprises a user equipment (UE)502and a base station (BS)504. In other embodiments, however, the wireless communication system500can comprise a plurality of UEs and is not shown here for clarity purposes. In some embodiments, base station504is equivalent to an eNodeB in LTE systems, gNodeB in 5G new radio (NR) systems etc. In some embodiments, the UE502may comprise a mobile phone, tablet computer, an internet of things (IoT) device, a vehicle-to-everything (V2X) UE, etc. The UE502and the base station504are configured to communicate with one another over a communication medium (e.g., air).

In some embodiments, the UE502is configured with a set of HARQ processes. In some embodiments, the set of HARQ processes are configured by radio resource control (RRC) signaling. In some embodiments, the BS504is configured to send/provide a new data indicator (NDI) configuration signal506to the UE502. In some embodiments, the NDI configuration signal506is configured to configure the UE502to include a latest NDI value detected by the UE502for one or more HARQ processes along with the HARQ-ACK information for the corresponding HARQ processes, as part of a HARQ-ACK feedback signal (e.g., the HARQ-ACK feedback signal510). In some embodiments, the NDI configuration signal506comprises a radio resource configuration (RRC) signal. The UE502is configured to receive and process the NDI configuration signal506.

In some embodiments, the BS504is further configured to provide a downlink control information (DCI)508to the UE502. The DCI508is configured to trigger a HARQ-ACK feedback signal510from the UE502. In some embodiments, the DCI508comprises information of physical uplink control channel (PUCCH)/physical uplink shared channel (PUSCH) resources to be utilized by the UE502for the transmission of the HARQ-ACK feedback signal510. In some embodiments, the HARQ-ACK feedback signal510comprises a Type-3 HARQ-ACK feedback/codebook. In such embodiments, the DCI508comprises a one-shot HARQ-ACK frequent field, a value associated therewith providing an indication to the UE502to trigger a Type-3 HARQ-ACK feedback. Alternately, in other embodiments, the HARQ-ACK feedback signal510may comprise other types of HARQ-ACK signals, for example, Type-1 HARQ-ACK feedback signal/Type-1 HARQ-ACK codebook. In some embodiments, the DCI508is configured to trigger the HARQ-ACK feedback signal510from the UE502, in response to a physical downlink shared channel (PDSCH) scheduled by the DCI508. Alternately, in other embodiments, for example, in the case of Type-3 HARQ-ACK feedback, the DCI508may trigger the HARQ-ACK feedback signal510, without scheduling the PDSCH to the UE502. The UE502is configured to receive and process the DCI508. In some embodiments, the UE502is further configured to generate the HARQ-ACK feedback signal510, in response to processing the DCI508. In some embodiments, the HARQ-ACK feedback signal510comprises a HARQ-ACK feedback information for one or more HARQ processes associated with the UE502, and an NDI value (i.e., a latest NDI value) detected by the UE502for the corresponding one or more HARQ processes. Subsequently, the UE502is configured to provide/send the HARQ-ACK feedback signal510to the BS504. The BS504is further configured to receive and process the HARQ-ACK feedback signal510.

In some embodiments, the NDI value for the corresponding HARQ processes are detected by the UE502from the Das that schedules the corresponding HARQ processes (or PDSCHs for the HARQ processes). In some embodiments, including NDI value as part of the HARQ-ACK feedback signal510facilitates the BS504to identify any mismatch between the data provided by the BS504and the respective HARQ-ACK information provided by the UE502. In some embodiments, the UE502may be configured with a plurality of HARQ process groups (HPGs), as explained above with respect toFIG.2a. In such embodiments, if the DCI508includes information that identifies one or more HPGs of the plurality of HPGs (similar to the DCI208inFIG.2a), the HARQ-ACK feedback signal510is configured to include a latest new data indicator (NDI) value detected by the UE502for each of the HARQ processes associated with the one or more HPGs that are identified by the DCI508.

Referring toFIG.6, illustrated is a block diagram of an apparatus600employable at a Base Station (BS), eNodeB, gNodeB or other network device, according to various aspects described herein. In some embodiments, the apparatus900may be included within the BS104, the BS204and the BS504in the above embodiments. However, in other embodiments, the apparatus600could be included within any gNodeB associated with a new radio (NR) system. The apparatus600can include one or more processors610(e.g., one or more baseband processors such as one or more of the baseband processors discussed in connection withFIG.15and/orFIG.16) comprising processing circuitry and associated interface(s) (e.g., one or more interface(s) discussed in connection withFIG.16), transceiver circuitry620(e.g., which can comprise circuitry for one or more wired connections and/or part or all of RF circuitry1506, which can comprise one or more of transmitter circuitry (e.g., associated with one or more transmit chains) or receiver circuitry (e.g., associated with one or more receive chains), wherein the transmitter circuitry and receiver circuitry can employ common circuit elements, distinct circuit elements, or a combination thereof), and memory630(which can comprise any of a variety of storage mediums and can store instructions and/or data associated with one or more of processor(s)610or transceiver circuitry620).

In particular, the term memory is intended to include an installation medium, e. g., a CD-ROM, floppy disks, or tape device; a computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media, e.g., a hard drive, or optical storage; registers, or other similar types of memory elements, etc. The memory medium may comprise other types of memory as well or combinations thereof. In various aspects, apparatus900can 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 communications network. In some aspects, the processor(s)610, transceiver circuitry620, and the memory630can be included in a single device, while in other aspects, they can be included in different devices, such as part of a distributed architecture.

Referring toFIG.7, illustrated is a block diagram of an apparatus700employable at a user equipment (UE) or other network device (e.g., IoT device), according to various aspects described herein. In some embodiments, the apparatus1000may be included within the UE102, the UE202and the UE502in the above embodiments. However, in other embodiments, the apparatus700could be included within any UE associated with a new radio (NR) system. Apparatus700can include one or more processors710(e.g., one or more baseband processors such as one or more of the baseband processors discussed in connection withFIG.15and/orFIG.16) comprising processing circuitry and associated interface(s) (e.g., one or more interface(s) discussed in connection withFIG.16), transceiver circuitry720(e.g., comprising part or all of RF circuitry1506, which can comprise transmitter circuitry (e.g., associated with one or more transmit chains) and/or receiver circuitry (e.g., associated with one or more receive chains) that can employ common circuit elements, distinct circuit elements, or a combination thereof), and a memory730(which can comprise any of a variety of storage mediums and can store instructions and/or data associated with one or more of processor(s)710or transceiver circuitry720). In particular, the term memory is intended to include an installation medium, e. g., a CD-ROM, floppy disks, or tape device; a computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media, e.g., a hard drive, or optical storage; registers, or other similar types of memory elements, etc. The memory medium may comprise other types of memory as well or combinations thereof. In various aspects, apparatus1000can be included within a user equipment (UE).

In various aspects discussed herein, signals and/or messages can be generated and output for transmission, and/or transmitted messages can be received and processed. Depending on the type of signal or message generated, outputting for transmission (e.g., by processor(s)710) can comprise one or more of the following: generating a set of associated bits that indicate the content of the signal or message, coding (e.g., which can include adding a cyclic redundancy check (CRC) and/or coding via one or more of turbo code, low density parity-check (LDPC) code, tailbiting convolution code (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., to a scheduled set of resources, to a set of time and frequency resources granted for uplink transmission, etc.). Depending on the type of received signal or message, processing (e.g., by processor(s)710) can comprise one or more of: identifying physical resources associated with the signal/message, detecting the signal/message, resource element group deinterleaving, demodulation, descrambling, and/or decoding.

FIG.8illustrates a flowchart of a method800for a UE associated with a wireless communication system that supports SPS release together with Type-3 HARQ-ACK codebook configuration, according to one embodiment of the disclosure. The method800is explained herein with reference to the apparatus700inFIG.7. In some embodiments, the apparatus700could be included within the UE102inFIG.1. Therefore, the method800is further explained with reference to the wireless communication system100inFIG.1. At802, a downlink control information (DCI) (e.g., the DCI106inFIG.1) received from a base station (e.g., the BS104inFIG.1) associated therewith, is processed using the one or more processors710. In some embodiments, the DCI comprises an indication to trigger a Type-3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal (e.g., the Type-3 HARQ-ACK feedback signal108inFIG.1).

At804, the Type-3 HARQ ACK feedback signal is generated, based on processing the DCI, using the one or more processors710. In some embodiments, the Type-3 HARQ ACK feedback signal comprises one or more HARQ-ACK bits for semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release(s). In some embodiments, each of the one or more HARQ-ACK bits for SPS PDSCH release(s) is adapted to include HARQ-ACK information for an SPS PDSCH release associated with the UE. At806, the Type-3 HARQ-ACK feedback signal is provided to the base station, using the one or more processors710.

FIG.9illustrates a flowchart of a method900for a base station (BS) associated with a wireless communication system that supports SPS release together with Type-3 HARQ-ACK codebook configuration, according to one embodiment of the disclosure. The method900is explained herein with reference to the apparatus600inFIG.6. In some embodiments, the apparatus600could be included within the BS104inFIG.1. Therefore, the method900is further explained with reference to the wireless communication system100inFIG.1. At902, a downlink control information (DCI) (e.g., the DCI106inFIG.1) is provided to a user equipment (UE) (e.g., the UE102inFIG.1) associated therewith, using the one or more processors610. In some embodiments, the DCI comprises an indication to the UE to trigger a Type-3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal (e.g., the Type-3 HARQ-ACK feedback signal108inFIG.1). At904, the Type-3 HARQ ACK feedback signal received from the UE, in response to providing the DCI, is processed using the one or more processors610. In some embodiments, the Type-3 HARQ ACK feedback signal comprises one or more HARQ-ACK bits for semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release(s). In some embodiments, each of the one or more HARQ-ACK bits for SPS PDSCH release(s) is adapted to include HARQ-ACK information for an SPS PDSCH release associated with the UE.

FIG.10illustrates a flowchart of a method1000for a UE associated with a wireless communication system that supports group-based HARQ-ACK feedback, according to one embodiment of the disclosure. The method1000is explained herein with reference to the apparatus700inFIG.7. In some embodiments, the apparatus700could be included within the UE202inFIG.2a. Therefore, the method1000is further explained with reference to the wireless communication system200inFIG.2a. At1002, a hybrid automatic repeat request process group (HPG) configuration signal (e.g., the HPG configuration signal206inFIG.2a) is received from a base station (e.g., the BS204) associated therewith, using the one or more processors710. In some embodiments, the HPG configuration signal comprises information of a plurality HARQ process groups (HPGs), each HPG comprising one or more HARQ processes of a set of HARQ processes configured for the UE.

At1004, the plurality of HPGs associated with the set of HARQ processes configured for the UE, is determined using the one or more processors710, based on processing the HPG configuration signal. At1006, a downlink control information (DCI) (e.g., the DCI208inFIG.2a) is received from the base station, using the one or more processors710. In some embodiments, the DCI comprises information that identifies one or more HPGs of the plurality of HPGs, the HARQ-ACK feedback information of which are to be included in a HARQ-ACK feedback signal (e.g., the HARQ-ACK feedback signal210inFIG.2a) that is triggered by the DCI. At1008, the HARQ-ACK feedback signal comprising the HARQ-ACK feedback information of HARQ processes associated with the one or more HPGs, is generated using the one or more processors710. At1010, the HARQ-ACK feedback signal is send to the base station, using the one or more processors710.

FIG.11illustrates a flowchart of a method1100for a base station (BS) associated with a wireless communication system that supports group based HARQ-ACK feedback, according to one embodiment of the disclosure. The method1100is explained herein with reference to the apparatus600inFIG.6. In some embodiments, the apparatus600could be included within the BS204inFIG.2a. Therefore, the method1100is further explained with reference to the wireless communication system200inFIG.2a. At1102, a hybrid automatic repeat request process group (HPG) configuration signal (e.g., the HPG configuration signal206inFIG.2a) is send to a user equipment (UE) (e.g., the UE202inFIG.2a) associated therewith, using the one or more processors610. In some embodiments, the HPG configuration signal comprises information of a plurality HARQ process groups (HPGs), each HPG comprising one or more HARQ processes of a set of HARQ processes configured for the UE.

At1104, a downlink control information (DCI) (e.g., the DCI208inFIG.2a) is send to the UE, using the one or more processors610. In some embodiments, the DCI comprises information that identifies one or more HPGs of the plurality of HPGs, HARQ-ACK feedback information of which are to be included in a HARQ-ACK feedback signal (e.g., the HARQ-ACK feedback signal210inFIG.2a) that is triggered by the DCI. At1106, the HARQ-ACK feedback signal is received from the UE, using the one or more processors610. In some embodiments, the HARQ-ACK feedback signal comprises the HARQ-ACK feedback information of HARQ processes associated with the one or more HPGs.

FIG.12illustrates a flowchart of a method1200for a UE associated with a wireless communication system that supports new data indicator (NDI) as part of HARQ-ACK feedback, according to one embodiment of the disclosure. The method1200is explained herein with reference to the apparatus700inFIG.7. In some embodiments, the apparatus700could be included within the UE502inFIG.5. Therefore, the method1200is further explained with reference to the wireless communication system500inFIG.5. At1202, a new data indicator (NDI) configuration signal (e.g., the NDI configuration signal506inFIG.5) is received from a base station (e.g., the BS504inFIG.5), using the one or more processors710. In some embodiments, the NDI configuration signal is configured to configure the UE to include a latest NDI value detected by the UE for one or more HARQ processes along with the HARQ-ACK information for the corresponding HARQ processes, as part of a HARQ-ACK feedback signal. At1204, a downlink control information (DCI) (e.g., the DCI508inFIG.5) is received from the base station (BS), using the one or more processors710. In some embodiments, the DCI is configured to trigger a HARQ-ACK feedback signal (e.g., the HARQ-ACK feedback signal510inFIG.5). At1206, the HARQ-ACK feedback signal is generated using the one or more processors710. In some embodiments, the HARQ-ACK feedback signal comprises HARQ-ACK feedback information for one or more HARQ processes associated with the UE, and an NDI value detected by the UE for the corresponding one or more HARQ processes. At1208, the HARQ-ACK feedback signal is send to the BS, using the one or more processors710.

FIG.13illustrates a flowchart of a method1300for a base station (BS) associated with a wireless communication system that supports new data indicator (NDI) as part of HARQ-ACK feedback, according to one embodiment of the disclosure. The method1300is explained herein with reference to the apparatus600inFIG.6. In some embodiments, the apparatus1300could be included within the BS504inFIG.5. Therefore, the method1300is further explained with reference to the wireless communication system500inFIG.5. At1302, a new data indicator (NDI) configuration signal (e.g., the NDI configuration signal506inFIG.5) is send to a user equipment (UE) (e.g., the UE502inFIG.5), using the one or more processors610. In some embodiments, the NDI configuration signal is configured to configure the UE to include a latest NDI value detected by the UE for one or more HARQ processes along with the HARQ-ACK information for the corresponding HARQ processes, as part of a HARQ-ACK feedback signal. At1304, a downlink control information (DCI) (e.g., the DCI508inFIG.5) is send to the UE, using the one or more processors610. In some embodiments, the DCI is configured to trigger a HARQ-ACK feedback signal (e.g., the HARQ-ACK feedback signal510inFIG.5) from the UE. At1306, the HARQ-ACK feedback signal is received from the UE using the one or more processors610. In some embodiments, the HARQ-ACK feedback signal comprises HARQ-ACK feedback information for one or more HARQ processes associated with the UE, and an NDI value detected by the UE for the corresponding one or more HARQ processes.

While the methods are illustrated and described above as a series of acts or events, it will be appreciated that the illustrated ordering of such acts or events are not to be interpreted in a limiting sense. For example, some acts may occur in different orders and/or concurrently with other acts or events apart from those illustrated and/or described herein. In addition, not all illustrated acts may be required to implement one or more aspects or embodiments of the disclosure herein. Also, one or more of the acts depicted herein may be carried out in one or more separate acts and/or phases.

Embodiments described herein can be implemented into a system using any suitably configured hardware and/or software.FIG.14illustrates an architecture of a system1400including a Core Network (CN)1420, for example a Fifth Generation (5G) CN (5GC), in accordance with various embodiments. The system1400is shown to include a UE1401, which can be the same or similar to one or more other UEs discussed herein; a Third Generation Partnership Project (3GPP) Radio Access Network (Radio AN or RAN) or other (e.g., non-3GPP) AN, (R)AN210, which can include one or more RAN nodes (e.g., Evolved Node B(s) (eNB(s)), next generation Node B(s) (gNB(s), and/or other nodes) or other nodes or access points; and a Data Network (DN)203, which can be, for example, operator services, Internet access or third party services; and a Fifth Generation Core Network (5GC)1420. The 5GC1420can comprise 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.

The UPF1402can act as an anchor point for intra-RAT and inter-RAT mobility, an external Protocol Data Unit (PDU) session point of interconnect to DN1403, and a branching point to support multi-homed PDU session. The UPF1402can also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a 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), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF1402can include an uplink classifier to support routing traffic flows to a data network. The DN1403can represent various network operator services, Internet access, or third-party services. DN1403can include, or be similar to, an application server. The UPF1402can interact with the SMF1424via an N4 reference point between the SMF1424and the UPF1402.

The AUSF1422can store data for authentication of UE1401and handle authentication-related functionality. The AUSF1422can facilitate a common authentication framework for various access types. The AUSF1422can communicate with the AMF1421via an N12 reference point between the AMF1421and the AUSF1422; and can communicate with the UDM1427via an N13 reference point between the UDM1427and the AUSF1422. Additionally, the AUSF1422can exhibit an Nausf service-based interface.

The AMF1421can be responsible for registration management (e.g., for registering UE1401, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. The AMF1421can be a termination point for the an N11 reference point between the AMF1421and the SMF1424. The AMF1421can provide transport for SM messages between the UE1401and the SMF1424, and act as a transparent proxy for routing SM messages. AMF1421can also provide transport for SMS messages between UE1401and a Short Message Service (SMS) Function (SMSF) (not shown inFIG.14). AMF1421can act as SEcurity Anchor Function (SEAF), which can include interaction with the AUSF1422and the UE1401and/or receipt of an intermediate key that was established as a result of the UE1401authentication process. Where Universal Subscriber Identity Module (USIM) based authentication is used, the AMF1421can retrieve the security material from the AUSF1422. AMF1421can also include a Single-Connection Mode (SCM) function, which receives a key from the SEA that it uses to derive access-network specific keys. Furthermore, AMF1421can be a termination point of a RAN Control Plane (CP) interface, which can include or be an N2 reference point between the (R)AN1410and the AMF1421; and the AMF1421can be a termination point of Non Access Stratum (NAS) (N1) signaling, and perform NAS ciphering and integrity protection.

AMF1421can also support NAS signaling with a UE1401over an Non-3GPP (N3) Inter Working Function (IWF) interface. The N3IWF can be used to provide access to untrusted entities. N3IWF can be a termination point for the N2 interface between the (R)AN1410and the AMF1421for the control plane, and can be a termination point for the N3 reference point between the (R)AN1410and the UPF1402for the user plane. As such, the AMF1421can handle N2 signaling from the SMF1424and the AMF1421for PDU sessions and QoS, encapsulate/de-encapsulate packets for Internet Protocol (IP) Security (IPSec) and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking taking into account QoS requirements associated with such marking received over N2. N3IWF can also relay uplink and downlink control-plane NAS signaling between the UE1401and AMF1421via an N1 reference point between the UE1401and the AMF1421, and relay uplink and downlink user-plane packets between the UE1401and UPF1402. The N3IWF also provides mechanisms for IPsec tunnel establishment with the UE1401. The AMF1421can exhibit an Namf service-based interface, and can be a termination point for an N14 reference point between two AMFs1421and an N17 reference point between the AMF1421and a 5G Equipment Identity Register (5G-EIR) (not shown inFIG.14).

The UE1401can be registered with the AMF1421in order to receive network services. Registration Management (RM) is used to register or deregister the UE1401with the network (e.g., AMF1421), and establish a UE context in the network (e.g., AMF1421). The UE1401can operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE1401is not registered with the network, and the UE context in AMF1421holds no valid location or routing information for the UE1401so the UE1401is not reachable by the AMF1421. In the RM-REGISTERED state, the UE1401is registered with the network, and the UE context in AMF1421can hold a valid location or routing information for the UE1401so the UE1401is reachable by the AMF1421. In the RM-REGISTERED state, the UE1401can perform mobility Registration Update procedures, perform periodic Registration Update procedures triggered by expiration of the periodic update timer (e.g., to notify the network that the UE1401is still active), and perform a Registration Update procedure to update UE capability information or to re-negotiate protocol parameters with the network, among others.

The AMF1421can store one or more RM contexts for the UE1401, where each RM context is associated with a specific access to the network. The RM context can be a data structure, database object, etc. that indicates or stores, inter alia, a registration state per access type and the periodic update timer. The AMF1421can also store a 5GC Mobility Management (MM) context that can be the same or similar to an (Enhanced Packet System (EPS))MM ((E)MM) context. In various embodiments, the AMF1421can store a Coverage Enhancement (CE) mode B Restriction parameter of the UE1401in an associated MM context or RM context. The AMF1421can also derive the value, when needed, from the UE's usage setting parameter already stored in the UE context (and/or MM/RM context).

Connection Management (CM) can be used to establish and release a signaling connection between the UE1401and the AMF1421over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE1401and the CN1420, and comprises both the signaling connection between the UE and the AN (e.g., RRC connection or UE-N3IWF connection for non-3GPP access) and the N2 connection for the UE1401between the AN (e.g., RAN1410) and the AMF1421. The UE1401can operate in one of two CM states, CM-IDLE mode or CM-CONNECTED mode. When the UE1401is operating in the CM-IDLE state/mode, the UE1401may have no NAS signaling connection established with the AMF1421over the N1 interface, and there can be (R)AN1410signaling connection (e.g., N2 and/or N3 connections) for the UE1401. When the UE1401is operating in the CM-CONNECTED state/mode, the UE1401can have an established NAS signaling connection with the AMF1421over the N1 interface, and there can be a (R)AN1410signaling connection (e.g., N2 and/or N3 connections) for the UE1401. Establishment of an N2 connection between the (R)AN1410and the AMF1421can cause the UE1401to transition from CM-IDLE mode to CM-CONNECTED mode, and the UE1401can transition from the CM-CONNECTED mode to the CM-IDLE mode when N2 signaling between the (R)AN1410and the AMF1421is released.

The SMF1424can be responsible for Session Management (SM) (e.g., session establishment, modify and release, including tunnel maintain between UPF and AN node); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement and QoS; lawful intercept (for SM events and interface to Lawful Interception (LI) system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF over N2 to AN; and determining Session and Service Continuity (SSC) mode of a session. SM can refer to management of a PDU session, and a PDU session or “session” can refer to a PDU connectivity service that provides or enables the exchange of PDUs between a UE1401and a data network (DN)1403identified by a Data Network Name (DNN). PDU sessions can be established upon UE1401request, modified upon UE1401and 5GC1420request, and released upon UE1401and 5GC1420request using NAS SM signaling exchanged over the N1 reference point between the UE1401and the SMF1424. Upon request from an application server, the 5GC1420can trigger a specific application in the UE1401. In response to receipt of the trigger message, the UE1401can pass the trigger message (or relevant parts/information of the trigger message) to one or more identified applications in the UE1401. The identified application(s) in the UE1401can establish a PDU session to a specific DNN. The SMF1424can check whether the UE1401requests are compliant with user subscription information associated with the UE1401. In this regard, the SMF1424can retrieve and/or request to receive update notifications on SMF1424level subscription data from the UDM1427.

The SMF1424can include the following roaming functionality: handling local enforcement to apply QoS Service Level Agreements (SLAs) (Visited Public Land Mobile Network (VPLMN)); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI system); and support for interaction with external DN for transport of signaling for PDU session authorization/authentication by external DN. An N16 reference point between two SMFs1424can be included in the system1400, which can be between another SMF1424in a visited network and the SMF1424in the home network in roaming scenarios. Additionally, the SMF1424can exhibit the Nsmf service-based interface.

The NEF1423can provide means for securely exposing the services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, Application Functions (e.g., AF1428), edge computing or fog computing systems, etc. In such embodiments, the NEF1423can authenticate, authorize, and/or throttle the AFs. NEF1423can also translate information exchanged with the AF1428and information exchanged with internal network functions. For example, the NEF1423can translate between an AF-Service-Identifier and an internal 5GC information. NEF1423can also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information can be stored at the NEF1423as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF1423to other NFs and AFs, and/or used for other purposes such as analytics. Additionally, the NEF1423can exhibit an Nnef service-based interface.

The NRF1425can support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF1425also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like can refer to the creation of an instance, and an “instance” can refer to a concrete occurrence of an object, which can occur, for example, during execution of program code. Additionally, the NRF1425can exhibit the Nnrf service-based interface.

The PCF1426can provide policy rules to control plane function(s) to enforce them, and can also support unified policy framework to govern network behavior. The PCF1426can also implement an FE to access subscription information relevant for policy decisions in a UDR of the UDM1427. The PCF1426can communicate with the AMF1421via an N15 reference point between the PCF1426and the AMF1421, which can include a PCF1426in a visited network and the AMF1421in case of roaming scenarios. The PCF1426can communicate with the AF1428via an N5 reference point between the PCF1426and the AF1428; and with the SMF1424via an N7 reference point between the PCF1426and the SMF1424. The system1400and/or CN1420can also include an N24 reference point between the PCF1426(in the home network) and a PCF1426in a visited network. Additionally, the PCF1426can exhibit an Npcf service-based interface.

The UDM1427can handle subscription-related information to support the network entities' handling of communication sessions, and can store subscription data of UE1401. For example, subscription data can be communicated between the UDM1427and the AMF1421via an N8 reference point between the UDM1427and the AMF. The UDM1427can include two parts, an application Functional Entity (FE) and a Unified Data Repository (UDR) (the FE and UDR are not shown inFIG.1). The UDR can store subscription data and policy data for the UDM1427and the PCF1426, and/or structured data for exposure and application data (including Packet Flow Descriptions (PFDs) for application detection, application request information for multiple UEs1401) for the NEF1423. The Nudr service-based interface can be exhibited by the UDR221to allow the UDM1427, PCF1426, and NEF1423to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM can include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different FEs can serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. The UDR can interact with the SMF1424via an N10 reference point between the UDM1427and the SMF1424. UDM1427can also support SMS management, wherein an SMS-FE implements similar application logic as discussed elsewhere herein. Additionally, the UDM1427can exhibit the Nudm service-based interface.

The AF1428can provide application influence on traffic routing, provide access to NEF1423, and interact with the policy framework for policy control. 5GC1420and AF1428can provide information to each other via NEF1423, which can be used for edge computing implementations. In such implementations, the network operator and third party services can be hosted close to the UE1401access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC can select a UPF1402close to the UE1401and execute traffic steering from the UPF1402to DN1403via the N6 interface. This can be based on the UE subscription data, UE location, and information provided by the AF1428. In this way, the AF1428can influence UPF (re)selection and traffic routing. Based on operator deployment, when AF1428is considered to be a trusted entity, the network operator can permit AF1428to interact directly with relevant NFs. Additionally, the AF1428can exhibit an Naf service-based interface.

The NSSF1429can select a set of network slice instances serving the UE1401. The NSSF1429can also determine allowed Network Slice Selection Assistance Information (NSSAI) and the mapping to the subscribed Single NSSAIs (S-NSSAIs), as appropriate. The NSSF1429can also determine the AMF set to be used to serve the UE1401, or a list of candidate AMF(s)1421based on a suitable configuration and possibly by querying the NRF1425. The selection of a set of network slice instances for the UE1401can be triggered by the AMF1421with which the UE1401is registered by interacting with the NSSF1429, which can lead to a change of AMF1421. The NSSF1429can interact with the AMF1421via an N22 reference point between AMF1421and NSSF1429; and can communicate with another NSSF1429in a visited network via an N31 reference point (not shown inFIG.14). Additionally, the NSSF1429can exhibit an Nnssf service-based interface.

As discussed previously, the CN1420can include an SMSF, which can be responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE1401to/from other entities, such as an SMS-Gateway Mobile services Switching Center (GMSC)/Inter-Working MSC (IWMSC)/SMS-router. The SMSF can also interact with AMF1421and UDM1427for a notification procedure that the UE1401is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM1427when UE1401is available for SMS).

The CN1420can also include other elements that are not shown inFIG.14, such as a Data Storage system/architecture, a 5G-EIR, a Security Edge Protection Proxy (SEPP), and the like. The Data Storage system can include a Structured Data Storage Function (SDSF), an Unstructured Data Storage Function (UDSF), and/or the like. Any NF can store and retrieve unstructured data into/from the UDSF (e.g., UE contexts), via N18 reference point between any NF and the UDSF (not shown inFIG.1). Individual NFs can share a UDSF for storing their respective unstructured data or individual NFs can each have their own UDSF located at or near the individual NFs. Additionally, the UDSF can exhibit an Nudsf service-based interface (not shown inFIG.1). The 5G-EIR can be an NF that checks the status of Permanent Equipment Identifier (PEI) for determining whether particular equipment/entities are blacklisted from the network; and the SEPP can be a non-transparent proxy that performs topology hiding, message filtering, and policing on inter-PLMN control plane interfaces.

Additionally, there can be many more reference points and/or service-based interfaces between the NF services in the NFs; however, these interfaces and reference points have been omitted fromFIG.14for clarity. In one example, the CN1420can include an Nx interface, which is an inter-CN interface between the MME (e.g., a non-5G MME) and the AMF1421in order to enable interworking between CN1420and a non-5G CN. Other example interfaces/reference points can include an N5g-EIR service-based interface exhibited by a 5G-EIR, an N27 reference point between the Network Repository Function (NRF) in the visited network and the NRF in the home network; and an N31 reference point between the NSSF in the visited network and the NSSF in the home network.

FIG.15illustrates example components of a device1500in accordance with some embodiments. In some embodiments, the device1500can include application circuitry1502, baseband circuitry1504, Radio Frequency (RF) circuitry1506, front-end module (FEM) circuitry1508, one or more antennas1510, and power management circuitry (PMC)1512coupled together at least as shown. The components of the illustrated device1500can be included in a UE or a RAN node. In some embodiments, the device1500can include fewer elements (e.g., a RAN node may not utilize application circuitry1502, and instead include a processor/controller to process IP data received from a CN such as 5GC1420or an Evolved Packet Core (EPC)). In some embodiments, the device1500can include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below can be included in more than one device (e.g., said circuitries can be separately included in more than one device for Cloud-RAN (C-RAN) implementations).

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

The baseband circuitry1504can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry1504can include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry1506and to generate baseband signals for a transmit signal path of the RF circuitry1506. Baseband circuitry1504can interface with the application circuitry1502for generation and processing of the baseband signals and for controlling operations of the RF circuitry1506. For example, in some embodiments, the baseband circuitry1504can include a third generation (3G) baseband processor1504A, a fourth generation (4G) baseband processor1504B, a fifth generation (5G) baseband processor1504C, or other baseband processor(s)1504D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry1504(e.g., one or more of baseband processors1504A-D) can handle various radio control functions that enable communication with one or more radio networks via the RF circuitry1506. In other embodiments, some or all of the functionality of baseband processors1504A-D can be included in modules stored in the memory1504G and executed via a Central Processing Unit (CPU)1504E. The radio control functions can include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry1504can include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry1504can include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and can include other suitable functionality in other embodiments.

In some embodiments, the baseband circuitry1504can include one or more audio digital signal processor(s) (DSP)1504F. The audio DSP(s)1504F can include elements for compression/decompression and echo cancellation and can include other suitable processing elements in other embodiments. Components of the baseband circuitry can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry1504and the application circuitry1502can be implemented together such as, for example, on a system on a chip (SOC).

In some embodiments, the baseband circuitry1504can provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry1504can support communication with a NG-RAN, an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN), etc. Embodiments in which the baseband circuitry1504is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry.

RF circuitry1506can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry1506can include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry1506can include a receive signal path which can include circuitry to down-convert RF signals received from the FEM circuitry1508and provide baseband signals to the baseband circuitry1504. RF circuitry1506can also include a transmit signal path which can include circuitry to up-convert baseband signals provided by the baseband circuitry1504and provide RF output signals to the FEM circuitry1508for transmission.

In some embodiments, the receive signal path of the RF circuitry1506can include mixer circuitry1506a, amplifier circuitry1506band filter circuitry1506c. In some embodiments, the transmit signal path of the RF circuitry1506can include filter circuitry1506cand mixer circuitry1506a. RF circuitry1506can also include synthesizer circuitry1506dfor synthesizing a frequency for use by the mixer circuitry1506aof the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry1506aof the receive signal path can be configured to down-convert RF signals received from the FEM circuitry1508based on the synthesized frequency provided by synthesizer circuitry1506d. The amplifier circuitry1506bcan be configured to amplify the down-converted signals and the filter circuitry1506ccan be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals can be provided to the baseband circuitry1504for further processing. In some embodiments, the output baseband signals can be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry1506aof the receive signal path can comprise passive mixers, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry1506aof the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry1506dto generate RF output signals for the FEM circuitry1508. The baseband signals can be provided by the baseband circuitry1504and can be filtered by filter circuitry1506c.

In some embodiments, the mixer circuitry1506aof the receive signal path and the mixer circuitry1506aof the transmit signal path can include two or more mixers and can be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry1506aof the receive signal path and the mixer circuitry1506aof the transmit signal path can include two or more mixers and can be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry1506aof the receive signal path and the mixer circuitry1506acan be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry1506aof the receive signal path and the mixer circuitry1506aof the transmit signal path can be configured for super-heterodyne operation.

In some embodiments, the output baseband signals and the input baseband signals can be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals can be digital baseband signals. In these alternate embodiments, the RF circuitry1506can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry1504can include a digital baseband interface to communicate with the RF circuitry1506.

In some dual-mode embodiments, a separate radio IC circuitry can be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry1506dcan be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers can be suitable. For example, synthesizer circuitry1506dcan be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

The synthesizer circuitry1506dcan be configured to synthesize an output frequency for use by the mixer circuitry1506aof the RF circuitry1506based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry1506dcan be a fractional N/N+1 synthesizer.

In some embodiments, frequency input can be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input can be provided by either the baseband circuitry1504or the applications circuitry1502depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) can be determined from a look-up table based on a channel indicated by the applications circuitry1502.

Synthesizer circuitry1506dof the RF circuitry1506can include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA). In some embodiments, the DMD can be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements can be configured to break a VCO period up into Nd equal packets of phase, 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 cycle.

In some embodiments, synthesizer circuitry1506dcan be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency can be a LO frequency (fLO). In some embodiments, the RF circuitry1506can include an IQ/polar converter.

FEM circuitry1508can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas1510, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry1506for further processing. FEM circuitry1508can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by the RF circuitry1506for transmission by one or more of the one or more antennas1510. In various embodiments, the amplification through the transmit or receive signal paths can be done solely in the RF circuitry1506, solely in the FEM circuitry1508, or in both the RF circuitry1506and the FEM circuitry1508.

In some embodiments, the FEM circuitry1508can include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry can include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry1506). The transmit signal path of the FEM circuitry1508can include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry1506), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas1510).

In some embodiments, the PMC1512can manage power provided to the baseband circuitry1504. In particular, the PMC1512can control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC1512can often be included when the device1500is capable of being powered by a battery, for example, when the device is included in a UE. The PMC1512can increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

WhileFIG.15shows the PMC1512coupled only with the baseband circuitry1504. However, in other embodiments, the PMC1512may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry1502, RF circuitry1506, or FEM circuitry1508.

In some embodiments, the PMC1512can control, or otherwise be part of, various power saving mechanisms of the device1500. For example, if the device1500is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it can enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device1500can power down for brief intervals of time and thus save power.

If there is no data traffic activity for an extended period of time, then the device1500can transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device1500goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device1500may not receive data in this state; in order to receive data, it can transition back to RRC_Connected state.

An additional power saving mode can allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and can power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

Processors of the application circuitry1502and processors of the baseband circuitry1504can be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry1504, alone or in combination, can be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry1502can utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 can comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 can comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 can comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.

FIG.16illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry1504ofFIG.2can comprise processors1504A-1504E and a memory1504G utilized by said processors. Each of the processors1504A-1504E can include a memory interface,1604A-1604E, respectively, to send/receive data to/from the memory1504G.

The baseband circuitry1504can further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface1612(e.g., an interface to send/receive data to/from memory external to the baseband circuitry1504), an application circuitry interface1614(e.g., an interface to send/receive data to/from the application circuitry1502ofFIG.2), an RF circuitry interface1616(e.g., an interface to send/receive data to/from RF circuitry1506ofFIG.2), a wireless hardware connectivity interface1618(e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface1620(e.g., an interface to send/receive power or control signals to/from the PMC1512).

In various aspects, embodiments discussed herein can facilitate techniques of inter-cell BM (Beam Management) via L1 (Layer 1) via 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 Synchronization CSI (Channel State Information)-RS (Reference Signal).

Examples can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including instructions that, when performed by a machine cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described herein.

Example 1 is a user equipment (UE) comprising a processor (or processing circuitry) configured to perform operations comprising receiving a hybrid automatic repeat request process group (HPG) configuration signal from a base station associated therewith, wherein the HPG configuration signal comprises information of a plurality HARQ process groups (HPGs), each HPG comprising one or more HARQ processes of a set of HARQ processes configured for the UE; determining the plurality of HPGs, based on processing the HPG configuration signal; receiving a 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 comprises information that identifies one or more HPGs of the plurality of HPGs, the HARQ-ACK feedback information of which are to be included in the HARQ-ACK feedback signal; generating the HARQ-ACK feedback signal comprising the HARQ-ACK feedback information of HARQ processes associated with the one or more HPGs; and sending the HARQ-ACK feedback signal to the base station.

Example 2 is a UE, including the subject matter of example 1, wherein the plurality of HPGs are associated with a respective plurality of priority class indices, wherein each priority class index of the plurality of priority class indices corresponds to a priority index associated with the one or more HARQ processes of the respective HPG.

Example 3 is a UE, including the subject matter of examples 1-2, including or omitting elements, wherein the DCI comprises an HPG request field comprising an HPG request field value that identifies the one or more HPGs and wherein 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.

Example 4 is a UE, including the subject matter of examples 1-3, including or omitting elements, wherein the DCI comprises cyclic redundancy check (CRC) bits that are scrambled by a predefined HPG sequence, wherein the predefined HPG sequence identifies the one or more HPGs, and wherein the processor is configured to descramble the CRC bits to determine the predefined HPG sequence and determine the one or more HPGs, based on the predefined HPG sequence, in accordance with a predefined mapping between the predefined HPG sequence and the one or more HPGs.

Example 5 is a UE, including the subject matter of examples 1-4, including or omitting elements, wherein the DCI comprises a priority indicator field that comprises a select priority class index of the plurality of priority class indices, wherein the select priority class index identifies a select HPG, the HARQ-ACK feedback information of which is to be included in the HARQ-ACK feedback signal.

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

Example 7 is a UE, including the subject matter of examples 1-6, including or omitting elements, wherein the operations further comprise 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.

Example 8 is a UE, including the subject matter of examples 1-7, including or omitting elements, wherein the one or more processors is further configured to receive a HARQ process regrouping signal from the base station, wherein the HARQ process regrouping signal comprises information to regroup the HARQ processes associated with one or more HPGs of the plurality of HPGs.

Example 9 is a UE, including the subject matter of examples 1-8, including or omitting elements, wherein the HARQ process regrouping signal comprises one or more HARQ regroup media access control (MAC) control elements (CEs), wherein each HARQ regroup MAC CE of the one or more HARQ regroup MAC CEs is associated with an HPG identifier (ID) of a select HPG of the plurality of HPGs, wherein each HARQ regroup MAC CE of the one or more HARQ regroup MAC CEs comprises a set of H-fields that corresponds to the set of HARQ processes configured for the UE, and wherein a value associated with each H-field of the set of H-fields identifies one or more HARQ processes that are included within the select HPG identified by the HPGID.

Example 10 is a UE, including the subject matter of examples 1-9, including or omitting elements, wherein the HARQ process regrouping signal comprises a HARQ regroup media access control (MAC) control element (CE) comprising one or more sets of H-fields respectively associated with one or more HPGs of the plurality of HPGs, wherein each set of H-fields of the one or more sets of H-fields correspond to the set of HARQ processes configured for the UE and wherein a value associated with each H-field of the set of H-fields identifies one or more HARQ processes that are included within a respective HPG.

Example 11 is a base station (BS) comprising a processor (or processing circuitry) configured to perform operations comprising sending a hybrid automatic repeat request process group (HPG) configuration signal to a user equipment (UE) associated therewith, wherein the HPG configuration signal comprises information of a plurality HARQ process groups (HPGs), each HPG comprising one or more HARQ processes of a set of HARQ processes configured for the UE; sending a 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 comprises information that identifies one or more HPGs of the plurality of HPGs, HARQ-ACK feedback information of which are to be included in the HARQ-ACK feedback signal; and receiving the HARQ-ACK feedback signal from the UE, wherein the HARQ-ACK feedback signal comprises the HARQ-ACK feedback information of HARQ processes associated with the one or more HPGs.

Example 12 is a BS, including the subject matter of example 11, wherein the plurality of HPGs are associated with a respective plurality of priority class indices, wherein each priority class index of the plurality of priority class indices corresponds to a priority index associated with the one or more HARQ processes of the respective HPG.

Example 13 is a BS, including the subject matter of examples 11-12, including or omitting elements, wherein the DCI comprises an HPG request field comprising an HPG request field value that identifies the one or more HPGs based on a predefined mapping between the HPG request field value and the one or more HPGs.

Example 14 is a BS, including the subject matter of examples 11-13, including or omitting elements, wherein the DCI comprises cyclic redundancy check (CRC) bits that are scrambled by a predefined HPG sequence, wherein the predefined HPG sequence identifies the one or more HPGs, in accordance with a predefined mapping between the predefined HPG sequence and the one or more HPGs.

Example 15 is a BS, including the subject matter of examples 11-14, including or omitting elements, wherein the DCI comprises a priority indicator field that comprises a select priority class index of the plurality of priority class indices, wherein the select priority class index identifies a select HPG, the HARQ-ACK feedback information of which is to be included in the HARQ-ACK feedback signal.

Example 16 is a BS, including the subject matter of examples 11-15, including or omitting elements, wherein the HARQ-ACK feedback signal further includes a latest new data indicator (NDI) value detected by the UE for each of the HARQ processes associated with the one or more HPGs.

Example 17 is a BS, including the subject matter of examples 11-16, including or omitting elements, wherein the operations further comprise 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 sending the NDI configuration signal to the UE.

Example 18 is a BS, including the subject matter of examples 11-17, including or omitting elements, wherein the operations further comprise generating a HARQ process regrouping signal to be provided to the UE, wherein the HARQ process regrouping signal comprises information to regroup the HARQ processes associated with one or more HPGs of the plurality of HPGs; and sending the HARQ process regrouping signal to the UE.

Example 19 is a BS, including the subject matter of examples 11-18, including or omitting elements, wherein the HARQ process regrouping signal comprises one or more HARQ regroup media access control (MAC) control elements (CEs), wherein each HARQ regroup MAC CE of the one or more HARQ regroup MAC CEs is associated with an HPG identifier (ID) of a select HPG of the plurality of HPGs, wherein each HARQ regroup MAC CE of the one or more HARQ regroup MAC CEs comprises a set of H-fields that corresponds to the set of HARQ processes configured for the UE, and wherein a value associated with each H-field of the set of H-fields identifies one or more HARQ processes that are included within the select HPG identified by the HPGID.

Example 20 is a BS, including the subject matter of examples 11-19, including or omitting elements, wherein the HARQ process regrouping signal comprises a HARQ regroup media access control (MAC) control element (CE) comprising one or more sets of H-fields respectively associated with one or more HPGs of the plurality of HPGs, wherein each set of H-fields of the one or more sets of H-fields correspond to the set of HARQ processes configured for the UE and wherein a value associated with each H-field of the set of H-fields identifies one or more HARQ processes that are included within a respective HPG.

Example 21 is a baseband (BB) processor for a user equipment (UE) configured to perform operations comprising receiving a hybrid automatic repeat request process group (HPG) configuration signal from a base station associated therewith, wherein the HPG configuration signal comprises information of a plurality HARQ process groups (HPGs), each HPG comprising one or more HARQ processes of a set of HARQ processes configured for the UE; determining the plurality of HPGs, based on processing the HPG configuration signal; receiving a 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 comprises information that identifies one or more HPGs of the plurality of HPGs, the HARQ-ACK feedback information of which are to be included in the HARQ-ACK feedback signal; generating the HARQ-ACK feedback signal comprising the HARQ-ACK feedback information of HARQ processes associated with the one or more HPGs; and sending the HARQ-ACK feedback signal to the base station.

Example 22 is a BB processor, including the subject matter of example 21, wherein the plurality of HPGs are associated with a respective plurality of priority class indices, wherein each priority class index of the plurality of priority class indices corresponds to a priority index associated with the one or more HARQ processes of the respective HPG.

Example 23 is a BB processor, including the subject matter of examples 21-22, including or omitting elements, wherein the DCI comprises an HPG request field comprising an HPG request field value that identifies the one or more HPGs and wherein 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.

Example 24 is a BB processor, including the subject matter of examples 21-23, including or omitting elements, wherein the DCI comprises cyclic redundancy check (CRC) bits that are scrambled by a predefined HPG sequence, wherein the predefined HPG sequence identifies the one or more HPGs, and wherein the processor is configured to descramble the CRC bits to determine the predefined HPG sequence and determine the one or more HPGs, based on the predefined HPG sequence, in accordance with a predefined mapping between the predefined HPG sequence and the one or more HPGs.

Example 25 is a BB processor, including the subject matter of examples 21-24, including or omitting elements, wherein the DCI comprises a priority indicator field that comprises a select priority class index of the plurality of priority class indices, wherein the select priority class index identifies a select HPG, the HARQ-ACK feedback information of which is to be included in the HARQ-ACK feedback signal.

Example 26 is a BB processor, including the subject matter of examples 21-25, including or omitting elements, wherein the HARQ-ACK feedback signal further includes a latest new data indicator (NDI) value detected by the UE for each of the HARQ processes associated with the one or more HPGs.

Example 27 is a BB processor, including the subject matter of examples 21-26, including or omitting elements, wherein the operations further comprise 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.

Example 28 is a BB processor, including the subject matter of examples 21-27, including or omitting elements, wherein the one or more processors is further configured to receive a HARQ process regrouping signal from the base station, wherein the HARQ process regrouping signal comprises information to regroup the HARQ processes associated with one or more HPGs of the plurality of HPGs.

Example 29 is a BB processor, including the subject matter of examples 21-28, including or omitting elements, wherein the HARQ process regrouping signal comprises one or more HARQ regroup media access control (MAC) control elements (CEs), wherein each HARQ regroup MAC CE of the one or more HARQ regroup MAC CEs is associated with an HPG identifier (ID) of a select HPG of the plurality of HPGs, wherein each HARQ regroup MAC CE of the one or more HARQ regroup MAC CEs comprises a set of H-fields that corresponds to the set of HARQ processes configured for the UE, and wherein a value associated with each H-field of the set of H-fields identifies one or more HARQ processes that are included within the select HPG identified by the HPGID.

Example 30 is a BB processor, including the subject matter of examples 21-29, including or omitting elements, wherein the HARQ process regrouping signal comprises a HARQ regroup media access control (MAC) control element (CE) comprising one or more sets of H-fields respectively associated with one or more HPGs of the plurality of HPGs, wherein each set of H-fields of the one or more sets of H-fields correspond to the set of HARQ processes configured for the UE and wherein a value associated with each H-field of the set of H-fields identifies one or more HARQ processes that are included within a respective HPG.

Example 31 is a baseband (BB) processor for a base station (BS) configured to perform operations comprising sending a hybrid automatic repeat request process group (HPG) configuration signal to a user equipment (UE) associated therewith, wherein the HPG configuration signal comprises information of a plurality HARQ process groups (HPGs), each HPG comprising one or more HARQ processes of a set of HARQ processes configured for the UE; sending a 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 comprises information that identifies one or more HPGs of the plurality of HPGs, HARQ-ACK feedback information of which are to be included in the HARQ-ACK feedback signal; and receiving the HARQ-ACK feedback signal from the UE, wherein the HARQ-ACK feedback signal comprises the HARQ-ACK feedback information of HARQ processes associated with the one or more HPGs.

Example 32 is a BB processor, including the subject matter of example 31, wherein the plurality of HPGs are associated with a respective plurality of priority class indices, wherein each priority class index of the plurality of priority class indices corresponds to a priority index associated with the one or more HARQ processes of the respective HPG.

Example 33 is a BB processor, including the subject matter of examples 31-32, including or omitting elements, wherein the DCI comprises an HPG request field comprising an HPG request field value that identifies the one or more HPGs based on a predefined mapping between the HPG request field value and the one or more HPGs.

Example 34 is a BB processor, including the subject matter of examples 31-33, including or omitting elements, wherein the DCI comprises cyclic redundancy check (CRC) bits that are scrambled by a predefined HPG sequence, wherein the predefined HPG sequence identifies the one or more HPGs, in accordance with a predefined mapping between the predefined HPG sequence and the one or more HPGs.

Example 35 is a BB processor, including the subject matter of examples 31-34, including or omitting elements, wherein the DCI comprises a priority indicator field that comprises a select priority class index of the plurality of priority class indices, wherein the select priority class index identifies a select HPG, the HARQ-ACK feedback information of which is to be included in the HARQ-ACK feedback signal.

Example 36 is a BB processor, including the subject matter of examples 31-35, including or omitting elements, wherein the HARQ-ACK feedback signal further includes a latest new data indicator (NDI) value detected by the UE for each of the HARQ processes associated with the one or more HPGs.

Example 37 is a BB processor, including the subject matter of examples 31-36, including or omitting elements, wherein the operations further comprise 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 sending the NDI configuration signal to the UE.

Example 38 is a BB processor, including the subject matter of examples 31-37, including or omitting elements, wherein the operations further comprise generating a HARQ process regrouping signal to be provided to the UE, wherein the HARQ process regrouping signal comprises information to regroup the HARQ processes associated with one or more HPGs of the plurality of HPGs; and sending the HARQ process regrouping signal to the UE.

Example 39 is a BB processor, including the subject matter of examples 31-38, including or omitting elements, wherein the HARQ process regrouping signal comprises one or more HARQ regroup media access control (MAC) control elements (CEs), wherein each HARQ regroup MAC CE of the one or more HARQ regroup MAC CEs is associated with an HPG identifier (ID) of a select HPG of the plurality of HPGs, wherein each HARQ regroup MAC CE of the one or more HARQ regroup MAC CEs comprises a set of H-fields that corresponds to the set of HARQ processes configured for the UE, and wherein a value associated with each H-field of the set of H-fields identifies one or more HARQ processes that are included within the select HPG identified by the HPGID.

Example 40 is a BB processor, including the subject matter of examples 31-39, including or omitting elements, wherein the HARQ process regrouping signal comprises a HARQ regroup media access control (MAC) control element (CE) comprising one or more sets of H-fields respectively associated with one or more HPGs of the plurality of HPGs, wherein each set of H-fields of the one or more sets of H-fields correspond to the set of HARQ processes configured for the UE and wherein a value associated with each H-field of the set of H-fields identifies one or more HARQ processes that are included within a respective HPG.

Example 41 is a method for a user equipment (UE) comprising receiving a hybrid automatic repeat request process group (HPG) configuration signal from a base station associated therewith, using one or more processors, wherein the HPG configuration signal comprises information of a plurality HARQ process groups (HPGs), each HPG comprising one or more HARQ processes of a set of HARQ processes configured for the UE; determining the plurality of HPGs, based on processing the HPG configuration signal, using the one or more processors; receiving a downlink control information (DCI) from the base station, using the one or more processors, wherein the DCI is configured to trigger a HARQ-ACK feedback signal from the UE and wherein the DCI comprises information that identifies one or more HPGs of the plurality of HPGs, the HARQ-ACK feedback information of which are to be included in the HARQ-ACK feedback signal; generating the HARQ-ACK feedback signal comprising the HARQ-ACK feedback information of HARQ processes associated with the one or more HPGs, using the one or more processors; and sending the HARQ-ACK feedback signal to the base station, using the one or more processors.

Example 42 is a method, including the subject matter of example 41, wherein the plurality of HPGs are associated with a respective plurality of priority class indices, wherein each priority class index of the plurality of priority class indices corresponds to a priority index associated with the one or more HARQ processes of the respective HPG.

Example 43 is a method, including the subject matter of examples 41-42, including or omitting elements, wherein the DCI comprises an HPG request field comprising an HPG request field value that identifies the one or more HPGs and wherein 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.

Example 44 is a method, including the subject matter of examples 41-43, including or omitting elements, wherein the DCI comprises cyclic redundancy check (CRC) bits that are scrambled by a predefined HPG sequence, wherein the predefined HPG sequence identifies the one or more HPGs, and wherein the processor is configured to descramble the CRC bits to determine the predefined HPG sequence and determine the one or more HPGs, based on the predefined HPG sequence, in accordance with a predefined mapping between the predefined HPG sequence and the one or more HPGs.

Example 45 is a method, including the subject matter of examples 41-44, including or omitting elements, wherein the DCI comprises a priority indicator field that comprises a select priority class index of the plurality of priority class indices, wherein the select priority class index identifies a select HPG, the HARQ-ACK feedback information of which is to be included in the HARQ-ACK feedback signal.

Example 46 is a method, including the subject matter of examples 41-45, including or omitting elements, wherein the HARQ-ACK feedback signal further includes a latest new data indicator (NDI) value detected by the UE for each of the HARQ processes associated with the one or more HPGs.

Example 47 is a method, including the subject matter of examples 41-46, including or omitting elements, further comprising receiving an NDI configuration signal from the BS, using the one or more processors, wherein the NDI configuration signal is adapted to configure the UE to include the NDI as part of the HARQ-ACK feedback signal.

Example 48 is a method, including the subject matter of examples 41-47, including or omitting elements, further comprising receiving a HARQ process regrouping signal from the base station, using the one or more processors, wherein the HARQ process regrouping signal comprises information to regroup the HARQ processes associated with one or more HPGs of the plurality of HPGs.

Example 49 is a method, including the subject matter of examples 41-48, including or omitting elements, wherein the HARQ process regrouping signal comprises one or more HARQ regroup media access control (MAC) control elements (CEs), wherein each HARQ regroup MAC CE of the one or more HARQ regroup MAC CEs is associated with an HPG identifier (ID) of a select HPG of the plurality of HPGs, wherein each HARQ regroup MAC CE of the one or more HARQ regroup MAC CEs comprises a set of H-fields that corresponds to the set of HARQ processes configured for the UE, and wherein a value associated with each H-field of the set of H-fields identifies one or more HARQ processes that are included within the select HPG identified by the HPGID.

Example 50 is a method, including the subject matter of examples 41-49, including or omitting elements, wherein the HARQ process regrouping signal comprises a HARQ regroup media access control (MAC) control element (CE) comprising one or more sets of H-fields respectively associated with one or more HPGs of the plurality of HPGs, wherein each set of H-fields of the one or more sets of H-fields correspond to the set of HARQ processes configured for the UE and wherein a value associated with each H-field of the set of H-fields identifies one or more HARQ processes that are included within a respective HPG.

Example 51 is a method for a base station (BS) comprising sending a hybrid automatic repeat request process group (HPG) configuration signal to a user equipment (UE) associated therewith, using one or more processors, wherein the HPG configuration signal comprises information of a plurality HARQ process groups (HPGs), each HPG comprising one or more HARQ processes of a set of HARQ processes configured for the UE; sending a downlink control information (DCI) to the UE, using the one or more processors, wherein the DCI is configured to trigger a HARQ-ACK feedback signal from the UE and wherein the DCI comprises information that identifies one or more HPGs of the plurality of HPGs, HARQ-ACK feedback information of which are to be included in the HARQ-ACK feedback signal; and receiving the HARQ-ACK feedback signal from the UE, using the one or more processors, wherein the HARQ-ACK feedback signal comprises the HARQ-ACK feedback information of HARQ processes associated with the one or more HPGs.

Example 52 is a method, including the subject matter of example 51, wherein the plurality of HPGs are associated with a respective plurality of priority class indices, wherein each priority class index of the plurality of priority class indices corresponds to a priority index associated with the one or more HARQ processes of the respective HPG.

Example 53 is a method, including the subject matter of examples 51-52, including or omitting elements, wherein the DCI comprises an HPG request field comprising an HPG request field value that identifies the one or more HPGs based on a predefined mapping between the HPG request field value and the one or more HPGs.

Example 54 is a method, including the subject matter of examples 51-53, including or omitting elements, wherein the DCI comprises cyclic redundancy check (CRC) bits that are scrambled by a predefined HPG sequence, wherein the predefined HPG sequence identifies the one or more HPGs, in accordance with a predefined mapping between the predefined HPG sequence and the one or more HPGs.

Example 55 is a method, including the subject matter of examples 51-54, including or omitting elements, wherein the DCI comprises a priority indicator field that comprises a select priority class index of the plurality of priority class indices, wherein the select priority class index identifies a select HPG, the HARQ-ACK feedback information of which is to be included in the HARQ-ACK feedback signal.

Example 56 is a method, including the subject matter of examples 51-55, including or omitting elements, wherein the HARQ-ACK feedback signal further includes a latest new data indicator (NDI) value detected by the UE for each of the HARQ processes associated with the one or more HPGs.

Example 57 is a method, including the subject matter of examples 51-56, including or omitting elements, further comprising generating an NDI configuration signal to be provided to the UE, using the one or more processors, wherein the NDI configuration signal is 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, using the one or more processors.

Example 58 is a method, including the subject matter of examples 51-57, including or omitting elements, further comprising generating a HARQ process regrouping signal to be provided to the UE, using the one or more processors, wherein the HARQ process regrouping signal comprises information to regroup the HARQ processes associated with one or more HPGs of the plurality of HPGs; and sending the HARQ process regrouping signal to the UE, using the one or more processors.

Example 59 is a method, including the subject matter of examples 51-58, including or omitting elements, wherein the HARQ process regrouping signal comprises one or more HARQ regroup media access control (MAC) control elements (CEs), wherein each HARQ regroup MAC CE of the one or more HARQ regroup MAC CEs is associated with an HPG identifier (ID) of a select HPG of the plurality of HPGs, wherein each HARQ regroup MAC CE of the one or more HARQ regroup MAC CEs comprises a set of H-fields that corresponds to the set of HARQ processes configured for the UE, and wherein a value associated with each H-field of the set of H-fields identifies one or more HARQ processes that are included within the select HPG identified by the HPGID.

Example 60 is a method, including the subject matter of examples 51-59, including or omitting elements, wherein the HARQ process regrouping signal comprises a HARQ regroup media access control (MAC) control element (CE) comprising one or more sets of H-fields respectively associated with one or more HPGs of the plurality of HPGs, wherein each set of H-fields of the one or more sets of H-fields correspond to the set of HARQ processes configured for the UE and wherein a value associated with each H-field of the set of H-fields identifies one or more HARQ processes that are included within a respective HPG.

Example 61 is a user equipment (UE) device comprising a processor (or processing circuitry) configured to perform operations comprising receiving a downlink control information (DCI) from a base station associated therewith, wherein the DCI comprises an indication to trigger a Type-3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal; generating the Type-3 HARQ ACK feedback signal, based on processing the DCI, wherein the Type-3 HARQ ACK feedback signal comprises one or more HARQ-ACK bits for semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release(s) and wherein each of the one or more HARQ-ACK bits for SPS PDSCH release(s) 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.

Example 62 is a UE, including the subject matter of example 61, wherein the one or more HARQ-ACK bits for SPS PDSCH release(s) comprises one or more reserved bits that are reserved to include HARQ-ACK information for one or more SPS PDSCH release(s), respectively.

Example 63 is a UE, including the subject matter of examples 61-62, including or omitting elements, wherein the DCI further includes information of the number of reserved bits comprising the one or more reserved bits for SPS PDSCH release(s) that are to be included in the Type-3 HARQ-ACK feedback signal.

Example 64 is a UE, including the subject matter of examples 61-63, including or omitting elements, wherein the DCI further includes a total SPS release indicator (T-SRI) field comprising information that enables to identify a total number of reserved bits comprising the one or more reserved bits for SPS PDSCH release(s) that are to be included within the Type-3 HARQ ACK feedback signal.

Example 65 is a UE, including the subject matter of examples 61-64, including or omitting elements, wherein the T-SRI field comprises a 1-bit field comprising an SPS release indicator value that indicates whether reserved bits for SPS PDSCH release(s) are included in Type-3 HARQ ACK feedback signal or not.

Example 66 is a UE, including the subject matter of examples 61-65, including or omitting elements, wherein, when the SPS release indicator value indicates that the reserved bits for SPS PDSCH release(s) are included, the total number of reserved bits is determined based on a total number of HARQ processes for downlink (DL) SPS configured for the UE.

Example 67 is a UE, including the subject matter of examples 61-66, including or omitting elements, wherein the T-SRI field comprises a 2-bit field comprising an SPS release indicator value that identifies the total number of reserved bits for SPS PDSCH release(s) in accordance with a predefined mapping between the SPS release indicator value and the total number of reserved bits for SPS PDSCH release(s).

Example 68 is a UE, including the subject matter of examples 61-67, including or omitting elements, wherein the one or more reserved bits for SPS PDSCH release(s) are appended at the end of the Type-3 HARQ-ACK feedback signal.

Example 69 is a UE, including the subject matter of examples 61-68, including or omitting elements, wherein the one or more reserved bits for SPS PDSCH release(s) are appended at the start of the Type-3 HARQ-ACK feedback signal.

Example 70 is a UE, including the subject matter of examples 61-69, including or omitting elements, wherein the one or more HARQ-ACK bits for SPS PDSCH release(s) corresponds to bit positions associated with HARQ processes of the corresponding SPS PDSCH within the Type-3 HARQ-ACK feedback signal.

Example 71 is a UE, including the subject matter of examples 61-70, including or omitting elements, wherein the one or more HARQ-ACK bits for SPS PDSCH release(s) corresponds to a bit position associated with a HARQ process identified by a HARQ process identifier (HPI), wherein the HPI is indicated to the UE by radio resource control (RRC) signaling.

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

Example 73 is a BS, including the subject matter of example 72, wherein the one or more HARQ-ACK bits for SPS PDSCH release(s) comprises one or more reserved bits that are reserved to include HARQ-ACK information for one or more SPS PDSCH release(s), respectively.

Example 74 is a BS, including the subject matter of examples 72-73, including or omitting elements, wherein the DCI further includes information of the number of reserved bits comprising the one or more reserved bits for SPS PDSCH release(s) that are to be included in the Type-3 HARQ ACK feedback signal.

Example 75 is a BS, including the subject matter of examples 72-74, including or omitting elements, wherein the DCI further includes a total SPS release indicator (T-SRI) field comprising information that enables to identify a total number of reserved bits comprising the one or more reserved bits for SPS PDSCH release(s) that are to be included within the Type-3 HARQ ACK feedback signal.

Example 76 is a BS, including the subject matter of examples 72-75, including or omitting elements, wherein the T-SRI field comprises a 1-bit field comprising an SPS release indicator value that indicates whether reserved bits for SPS PDSCH release(s) are included in Type-3 HARQ ACK feedback signal or not.

Example 77 is a BS, including the subject matter of examples 72-76, including or omitting elements, wherein the T-SRI field comprises a 2-bit field comprising an SPS release indicator value that identifies the total number of reserved bits for SPS PDSCH release(s) in accordance with a predefined mapping between the SPS release indicator value and the total number of reserved bits for SPS PDSCH release(s).

Example 78 is a BS, including the subject matter of examples 72-77, including or omitting elements, wherein the one or more reserved bits for SPS PDSCH release(s) are appended at the end of the Type-3 HARQ-ACK feedback signal.

Example 79 is a BS, including the subject matter of examples 72-78, including or omitting elements, wherein the one or more reserved bits for SPS PDSCH release(s) are appended at the start of the Type-3 HARQ-ACK feedback signal.

Example 80 is a BS, including the subject matter of examples 72-79, including or omitting elements, wherein the one or more HARQ-ACK bits for SPS PDSCH release(s) corresponds to bit positions associated with HARQ processes of the corresponding SPS PDSCH within the Type-3 HARQ-ACK feedback signal.

Example 81 is a BS, including the subject matter of examples 72-80, including or omitting elements, wherein the one or more HARQ-ACK bits for SPS PDSCH release(s) corresponds to a bit position associated with a HARQ process identified by a predefined HARQ process identifier (HPI), wherein the HPI is indicated to the UE by radio resource control (RRC) signaling.

Example 82 is a baseband (BB) processor for a UE configured to perform operations comprising receiving a downlink control information (DCI) from a base station associated therewith, wherein the DCI comprises an indication to trigger a Type-3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal; generating the Type-3 HARQ ACK feedback signal, based on processing the DCI, wherein the Type-3 HARQ ACK feedback signal comprises one or more HARQ-ACK bits for semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release(s) and wherein each of the one or more HARQ-ACK bits for SPS PDSCH release(s) 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.

Example 83 is a BB processor, including the subject matter of example 82, wherein the one or more HARQ-ACK bits for SPS PDSCH release(s) comprises one or more reserved bits that are reserved to include HARQ-ACK information for one or more SPS PDSCH release(s), respectively.

Example 84 is a BB processor, including the subject matter of examples 82-83, including or omitting elements, wherein the DCI further includes information of the number of reserved bits comprising the one or more reserved bits for SPS PDSCH release(s) that are to be included in the Type-3 HARQ-ACK feedback signal.

Example 85 is a BB processor, including the subject matter of examples 82-84, including or omitting elements, wherein the DCI further includes a total SPS release indicator (T-SRI) field comprising information that enables to identify a total number of reserved bits comprising the one or more reserved bits for SPS PDSCH release(s) that are to be included within the Type-3 HARQ ACK feedback signal.

Example 86 is a BB processor, including the subject matter of examples 82-85, including or omitting elements, wherein the T-SRI field comprises a 1-bit field comprising an SPS release indicator value that indicates whether reserved bits for SPS PDSCH release(s) are included in Type-3 HARQ ACK feedback signal or not.

Example 87 is a BB processor, including the subject matter of examples 82-86, including or omitting elements, wherein, when the SPS release indicator value indicates that the reserved bits for SPS PDSCH release(s) are included, the total number of reserved bits is determined based on a total number of HARQ processes for downlink (DL) SPS configured for the UE.

Example 88 is a BB processor, including the subject matter of examples 82-87, including or omitting elements, wherein the T-SRI field comprises a 2-bit field comprising an SPS release indicator value that identifies the total number of reserved bits for SPS PDSCH release(s) in accordance with a predefined mapping between the SPS release indicator value and the total number of reserved bits for SPS PDSCH release(s).

Example 89 is a BB processor, including the subject matter of examples 82-88, including or omitting elements, wherein the one or more reserved bits for SPS PDSCH release(s) are appended at the end of the Type-3 HARQ-ACK feedback signal.

Example 90 is a BB processor, including the subject matter of examples 82-89, including or omitting elements, wherein the one or more reserved bits for SPS PDSCH release(s) are appended at the start of the Type-3 HARQ-ACK feedback signal.

Example 91 is a BB processor, including the subject matter of examples 82-90, including or omitting elements, wherein the one or more HARQ-ACK bits for SPS PDSCH release(s) corresponds to bit positions associated with HARQ processes of the corresponding SPS PDSCH within the Type-3 HARQ-ACK feedback signal.

Example 92 is a BB processor, including the subject matter of examples 82-91, including or omitting elements, wherein the one or more HARQ-ACK bits for SPS PDSCH release(s) corresponds to a bit position associated with a HARQ process identified by a HARQ process identifier (HPI), wherein the HPI is indicated to the UE by radio resource control (RRC) signaling.

Example 93 is a baseband (BB) processor for a base station configured to perform operations comprising sending a downlink control information (DCI) to a user equipment (UE) associated therewith, wherein the DCI comprises an indication to the UE to trigger a Type-3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal; and receiving the Type-3 HARQ ACK feedback signal from the UE, in response to providing the DCI, wherein the Type-3 HARQ ACK feedback signal comprises one or more HARQ-ACK bits for semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release(s) and wherein each of the one or more HARQ-ACK bits for SPS PDSCH release(s) is adapted to include HARQ-ACK information for an SPS PDSCH release associated with the UE.

Example 94 is a BB processor, including the subject matter of example 93, wherein the one or more HARQ-ACK bits for SPS PDSCH release(s) comprises one or more reserved bits that are reserved to include HARQ-ACK information for one or more SPS PDSCH release(s), respectively.

Example 95 is a BB processor, including the subject matter of examples 93-94, including or omitting elements, wherein the DCI further includes information of the number of reserved bits comprising the one or more reserved bits for SPS PDSCH release(s) that are to be included in the Type-3 HARQ ACK feedback signal.

Example 96 is a BB processor, including the subject matter of examples 93-95, including or omitting elements, wherein the DCI further includes a total SPS release indicator (T-SRI) field comprising information that enables to identify a total number of reserved bits comprising the one or more reserved bits for SPS PDSCH release(s) that are to be included within the Type-3 HARQ ACK feedback signal.

Example 97 is a BB processor, including the subject matter of examples 93-96, including or omitting elements, wherein the T-SRI field comprises a 1-bit field comprising an SPS release indicator value that indicates whether reserved bits for SPS PDSCH release(s) are included in Type-3 HARQ ACK feedback signal or not.

Example 98 is a BB processor, including the subject matter of examples 93-97, including or omitting elements, wherein the T-SRI field comprises a 2-bit field comprising an SPS release indicator value that identifies the total number of reserved bits for SPS PDSCH release(s) in accordance with a predefined mapping between the SPS release indicator value and the total number of reserved bits for SPS PDSCH release(s).

Example 99 is a BB processor, including the subject matter of examples 93-98, including or omitting elements, wherein the one or more reserved bits for SPS PDSCH release(s) are appended at the end of the Type-3 HARQ-ACK feedback signal.

Example 100 is a BB processor, including the subject matter of examples 93-99, including or omitting elements, wherein the one or more reserved bits for SPS PDSCH release(s) are appended at the start of the Type-3 HARQ-ACK feedback signal.

Example 101 is a BB processor, including the subject matter of examples 93-100, including or omitting elements, wherein the one or more HARQ-ACK bits for SPS PDSCH release(s) corresponds to bit positions associated with HARQ processes of the corresponding SPS PDSCH within the Type-3 HARQ-ACK feedback signal.

Example 102 is a BB processor, including the subject matter of examples 93-101, including or omitting elements, wherein the one or more HARQ-ACK bits for SPS PDSCH release(s) corresponds to a bit position associated with a HARQ process identified by a predefined HARQ process identifier (HPI), wherein the HPI is indicated to the UE by radio resource control (RRC) signaling.

Example 103 is a method for a user equipment (UE) comprising receiving a downlink control information (DCI) from a base station associated therewith, using one or more processors, wherein the DCI comprises an indication to trigger a Type-3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal; generating the Type-3 HARQ ACK feedback signal, based on processing the DCI, using the one or more processors, wherein the Type-3 HARQ ACK feedback signal comprises one or more HARQ-ACK bits for semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release(s) and wherein each of the one or more HARQ-ACK bits for SPS PDSCH release(s) 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, using the one or more processors.

Example 104 is a method, including the subject matter of example 103, wherein the one or more HARQ-ACK bits for SPS PDSCH release(s) comprises one or more reserved bits that are reserved to include HARQ-ACK information for one or more SPS PDSCH release(s), respectively.

Example 105 is a method, including the subject matter of examples 103-104, including or omitting elements, wherein the DCI further includes information of the number of reserved bits comprising the one or more reserved bits for SPS PDSCH release(s) that are to be included in the Type-3 HARQ-ACK feedback signal.

Example 106 is a method, including the subject matter of examples 103-105, including or omitting elements, wherein the DCI further includes a total SPS release indicator (T-SRI) field comprising information that enables to identify a total number of reserved bits comprising the one or more reserved bits for SPS PDSCH release(s) that are to be included within the Type-3 HARQ ACK feedback signal.

Example 107 is a method, including the subject matter of examples 103-106, including or omitting elements, wherein the T-SRI field comprises a 1-bit field comprising an SPS release indicator value that indicates whether reserved bits for SPS PDSCH release(s) are included in Type-3 HARQ ACK feedback signal or not.

Example 108 is a method, including the subject matter of examples 103-107, including or omitting elements, wherein, when the SPS release indicator value indicates that the reserved bits for SPS PDSCH release(s) are included, the total number of reserved bits is determined based on a total number of HARQ processes for downlink (DL) SPS configured for the UE.

Example 109 is a method, including the subject matter of examples 103-108, including or omitting elements, wherein the T-SRI field comprises a 2-bit field comprising an SPS release indicator value that identifies the total number of reserved bits for SPS PDSCH release(s) in accordance with a predefined mapping between the SPS release indicator value and the total number of reserved bits for SPS PDSCH release(s).

Example 110 is a method, including the subject matter of examples 103-109, including or omitting elements, wherein the one or more reserved bits for SPS PDSCH release(s) are appended at the end of the Type-3 HARQ-ACK feedback signal.

Example 111 is a method, including the subject matter of examples 103-110, including or omitting elements, wherein the one or more reserved bits for SPS PDSCH release(s) are appended at the start of the Type-3 HARQ-ACK feedback signal.

Example 112 is a method, including the subject matter of examples 103-111, including or omitting elements, wherein the one or more HARQ-ACK bits for SPS PDSCH release(s) corresponds to bit positions associated with HARQ processes of the corresponding SPS PDSCH within the Type-3 HARQ-ACK feedback signal.

Example 113 is a method, including the subject matter of examples 103-112, including or omitting elements, wherein the one or more HARQ-ACK bits for SPS PDSCH release(s) corresponds to a bit position associated with a HARQ process identified by a HARQ process identifier (HPI), wherein the HPI is indicated to the UE by radio resource control (RRC) signaling.

Example 114 is a method for a base station comprising sending a downlink control information (DCI) to a user equipment (UE) associated therewith, using one or more processors, wherein the DCI comprises an indication to the UE to trigger a Type-3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal; and receiving the Type-3 HARQ ACK feedback signal from the UE, in response to providing the DCI, using the one or more processors, wherein the Type-3 HARQ ACK feedback signal comprises one or more HARQ-ACK bits for semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release(s) and wherein each of the one or more HARQ-ACK bits for SPS PDSCH release(s) is adapted to include HARQ-ACK information for an SPS PDSCH release associated with the UE.

Example 115 is a method, including the subject matter of example 114, wherein the one or more HARQ-ACK bits for SPS PDSCH release(s) comprises one or more reserved bits that are reserved to include HARQ-ACK information for one or more SPS PDSCH release(s), respectively.

Example 116 is a method, including the subject matter of examples 113-114, including or omitting elements, wherein the DCI further includes information of the number of reserved bits comprising the one or more reserved bits for SPS PDSCH release(s) that are to be included in the Type-3 HARQ ACK feedback signal.

Example 117 is a method, including the subject matter of examples 113-116, including or omitting elements, wherein the DCI further includes a total SPS release indicator (T-SRI) field comprising information that enables to identify a total number of reserved bits comprising the one or more reserved bits for SPS PDSCH release(s) that are to be included within the Type-3 HARQ ACK feedback signal.

Example 118 is a method, including the subject matter of examples 113-117, including or omitting elements, wherein the T-SRI field comprises a 1-bit field comprising an SPS release indicator value that indicates whether reserved bits for SPS PDSCH release(s) are included in Type-3 HARQ ACK feedback signal or not.

Example 119 is a method, including the subject matter of examples 113-118, including or omitting elements, wherein the T-SRI field comprises a 2-bit field comprising an SPS release indicator value that identifies the total number of reserved bits for SPS PDSCH release(s) in accordance with a predefined mapping between the SPS release indicator value and the total number of reserved bits for SPS PDSCH release(s).

Example 120 is a method, including the subject matter of examples 113-119, including or omitting elements, wherein the one or more reserved bits for SPS PDSCH release(s) are appended at the end of the Type-3 HARQ-ACK feedback signal.

Example 121 is a method, including the subject matter of examples 113-120, including or omitting elements, wherein the one or more reserved bits for SPS PDSCH release(s) are appended at the start of the Type-3 HARQ-ACK feedback signal.

Example 122 is a method, including the subject matter of examples 113-121, including or omitting elements, wherein the one or more HARQ-ACK bits for SPS PDSCH release(s) corresponds to bit positions associated with HARQ processes of the corresponding SPS PDSCH within the Type-3 HARQ-ACK feedback signal.

Example 123 is a method, including the subject matter of examples 113-122, including or omitting elements, wherein the one or more HARQ-ACK bits for SPS PDSCH release(s) corresponds to a bit position associated with a HARQ process identified by a predefined HARQ process identifier (HPI), wherein the HPI is indicated to the UE by radio resource control (RRC) signaling.

Example 124 is a UE, including the subject matter of examples 1-10, including or omitting elements, wherein the HARQ-ACK feedback signal triggered by the DCI comprises a Type-1 HARQ-ACK codebook.

Example 125 is a UE, including the subject matter of examples 1-10, including or omitting elements, wherein the HARQ-ACK feedback signal triggered by the DCI comprises a Type-3 HARQ-ACK codebook.

Example 126 is a BS, including the subject matter of examples 11-20, including or omitting elements, wherein the HARQ-ACK feedback signal triggered by the DCI comprises a Type-1 HARQ-ACK codebook.

Example 127 is a BS, including the subject matter of examples 11-20, including or omitting elements, wherein the HARQ-ACK feedback signal triggered by the DCI comprises a Type-3 HARQ-ACK codebook.

Example 128 is a UE, including the subject matter of examples 61-71, including or omitting elements, wherein the operations further comprise determining whether the Type-3 HARQ-ACK feedback signal and HARQ-ACK information associated with an SPS PDSCH release are to be send to the base station at a same slot, prior to generating the Type-3 HARQ ACK feedback signal and including the HARQ-ACK information corresponding to the SPS PDSCH release in a HARQ-ACK bit of the one or more HARQ-ACK bits for SPS PDSCH release(s) within the Type-3 HARQ-ACK feedback signal, based on the determination.

Example 129 is a BB processor, including the subject matter of examples 82-92, including or omitting elements, wherein the operations further comprise determining whether the Type-3 HARQ-ACK feedback signal and HARQ-ACK information associated with an SPS PDSCH release are to be send to the base station at a same slot, prior to generating the Type-3 HARQ ACK feedback signal and including the HARQ-ACK information corresponding to the SPS PDSCH release in a HARQ-ACK bit of the one or more HARQ-ACK bits for SPS PDSCH release(s) within the Type-3 HARQ-ACK feedback signal, based on the determination.

While the invention has been illustrated, and described with respect to one or more implementations, alterations and/or modifications may be made to the illustrated examples without departing from the spirit and scope of the appended claims. In particular regard to the various functions performed by the above described components or structures (assemblies, devices, circuits, systems, etc.), the terms (including a reference to a “means”) used to describe such components are intended to correspond, unless otherwise indicated, to any component or structure which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations of the invention.

The above description of illustrated embodiments of the subject disclosure, including what is described in the Abstract, 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 are possible that are considered within the scope of such embodiments and examples, as those skilled in the relevant art can recognize.