Patent Description:
Networks need to provide data quickly and reliably without taxing their resources. Hybrid automatic repeat request (HARQ) technology can make that happen. HARQ uses a stop and wait protocol. When a transmission has been made, the transmitting entity stops and waits until it receives an acknowledgement (ACK) or negative acknowledgement (NACK) back from the destination before transmitting the next block of data or retransmitting the same data block. Such transmission/reception processes that relies on ACK/NACK feedback are sometimes referred to as HARQ processes. The prior art document 3GPP DRAFT R1-<NUM> discloses updated proposals on issues B2, B6 and B11 that are prioritized for RAN1#101e among the issues identified for the NR-U Type-<NUM> HARQ-ACK codebook. The prior art document 3GPP DRAFT R1-<NUM> discloses remaining issues and corrections for Release <NUM> NR-U HARQ enhancement.

Some examples of circuits, apparatuses and/or methods will be described in the following by way of example only. In this context, reference will be made to the accompanying Figures.

Preferred embodiments are provided by the dependent claims. The embodiments and/or examples of the following description which are not covered by the claims, are provided for illustrative purpose only and are only intended to assist the reader in understanding the present invention. However, such embodiments and/or examples which are not covered by the claims do not form part of the present invention that is solely defined by the claims. In one embodiment of the disclosure, a user equipment (UE) device according to claim <NUM> is disclosed.

In one embodiment of the disclosure, a baseband (BB) processor for a base station according to claim <NUM> is disclosed.

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.

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. 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.

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 (RRC) signaling. Different categories of HARQ-ACK codebooks are defined in 3GPP. For example, a Type-<NUM> 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-<NUM> HARQ-ACK codebook comprising a dynamic codebook where the size of the codebook changes according to the number of resource allocations. Further, a Type-<NUM> 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 <NUM> 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 <NUM> 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 <NUM> 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-<NUM> HARQ-ACK codebook does not support HARQ-ACK feedback for SPS release. Specifically, when the Type-<NUM> 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-<NUM> 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-<NUM> 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-<NUM> 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-<NUM> 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> illustrates a simplified block diagram of a wireless communication system <NUM>, according to one embodiment of the disclosure. In some embodiments, the wireless communication system <NUM> supports SPS release together with Type-<NUM> HARQ-ACK codebook configuration. The wireless communication system <NUM> comprises a user equipment (UE) <NUM> and a base station (BS) <NUM>. In other embodiments, however, the wireless communication system <NUM> can comprise a plurality of UEs and is not shown here for clarity purposes. In some embodiments, base station <NUM> is equivalent to an eNodeB in LTE systems, gNodeB in <NUM> new radio (NR) systems etc. In some embodiments, the UE <NUM> may comprise a mobile phone, tablet computer, an internet of things (IoT) device, a vehicle-to-everything (V2X) UE, etc. The UE <NUM> and the base station <NUM> are configured to communicate with one another over a communication medium (e.g., air). In some embodiments, the wireless communication system <NUM> supports semi-persistent scheduling (SPS) release together with Type-<NUM> HARQ-ACK codebook configuration, as can be fully appreciated below.

In some embodiments, the BS <NUM> is configured to provide a downlink control information (DCI) <NUM> to the UE <NUM>. The DCI <NUM> is provided to the UE <NUM> as part of a physical downlink control channel (PDCCH). In some embodiments, the DCI <NUM> is configured to trigger a Type-<NUM> hybrid automatic repeat request (HARQ) ACK feedback signal <NUM> from the UE <NUM>. In such embodiments, the DCI <NUM> comprises an indication to trigger the Type-<NUM> HARQ ACK feedback signal <NUM>. Specifically, the DCI <NUM> comprises a one-shot HARQ-ACK frequent field, a value associated therewith providing an indication to the UE <NUM> to trigger the Type-<NUM> HARQ-ACK feedback signal <NUM>. For example, when the one-shot HARQ-ACK frequent field comprises a value of <NUM>, the UE <NUM> is configured to trigger the Type-<NUM> HARQ-ACK feedback signal <NUM>. Alternately, when the one-shot HARQ-ACK frequent field comprises a value of <NUM>, the UE <NUM> is configured not to trigger the Type-<NUM> HARQ-ACK feedback signal <NUM>. In some embodiments, the DCI <NUM> further comprises information of physical uplink control channel (PUCCH)/physical uplink shared channel (PUSCH) resources to be utilized by the UE <NUM> for the transmission of the Type-<NUM> HARQ-ACK feedback signal <NUM>.

The UE <NUM> is configured to receive and process the DCI <NUM>. Upon processing the DCI <NUM>, when the DCI <NUM> comprises the indication to trigger a Type-<NUM> HARQ-ACK feedback signal, the UE <NUM> is configured to generate a Type-<NUM> HARQ-ACK feedback signal <NUM>. In some embodiments, the Type-<NUM> HARQ-ACK feedback signal <NUM> may further be referred to as Type-<NUM> HARQ-ACK CB <NUM> or Type-<NUM> HARQ-ACK CB feedback signal <NUM>. In some embodiments, the Type-<NUM> HARQ-ACK feedback signal <NUM> is configured to include HARQ-ACK information associated with a set of HARQ processes that are configured for the UE <NUM>. In some embodiments, the set of HARQ processes configured for the UE <NUM> may comprise one or more SPS PDSCHs. In some embodiments, the Type-<NUM> HARQ-ACK feedback signal <NUM> further 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 UE <NUM> is further configured to determine whether the Type-<NUM> HARQ-ACK feedback signal <NUM> triggered by the DCI <NUM> and HARQ-ACK information associated with an SPS release are to be send to the base station <NUM> at a same slot, prior to generating the Type-<NUM> HARQ ACK feedback signal <NUM>. In such embodiments, the UE <NUM> is 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-<NUM> HARQ-ACK feedback signal <NUM>.

More particularly, in the embodiments where the UE <NUM> is 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 UE <NUM> or when a select SPS PDSCH of the one or more SPS PDSCHs is released, and it is determined that the UE <NUM> is to send the HARQ-ACK information for the select SPS release in a same slot when the Type-<NUM> HARQ-ACK feedback signal <NUM> is triggered, the UE <NUM> is configured to provide HARQ-ACK information for the SPS release in a HARQ-ACK bit of the one or more HARQ-ACK bits for SPS PDSCH release(s) within the Type-<NUM> HARQ-ACK feedback signal <NUM>. In some embodiments, the UE <NUM> is configured to receive an indication to release an SPS PDSCH within the DCI <NUM>. Alternately, in other embodiments, the UE <NUM> is configured to receive the indication to release the SPS PDSCH via radio resource control (RRC) signaling. Upon generating the Type-<NUM> HARQ-ACK feedback signal <NUM>, the UE <NUM> is further configured to provide the Type-<NUM> HARQ-ACK feedback signal <NUM> to the BS <NUM>. The BS <NUM> is configured to receive and process the Type-<NUM> HARQ-ACK feedback signal <NUM>.

In some embodiments, the one or more HARQ-ACK bits for SPS PDSCH release(s) within the Type-<NUM> HARQ-ACK feedback signal <NUM> comprises 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-<NUM> HARQ-ACK feedback signal <NUM>. Alternately, in other embodiments, one or more reserved bits for SPS PDSCH release(s) are appended at the start of the Type-<NUM> HARQ-ACK feedback signal <NUM>. 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 UE <NUM> via 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-<NUM> HARQ-ACK feedback signal <NUM> is indicated to the UE <NUM> by the BS <NUM>. In some embodiments, the BS <NUM> is 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 DCI <NUM> (e.g., DCI format 1_1, DCI format 1_2 etc.). In some embodiments, the BS <NUM> is configured to directly provide the number of reserved bits comprising the one or more reserved bits for SPS PDSCH release(s) via the DCI <NUM>. In other embodiments, the DCI <NUM> includes 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-<NUM> HARQ ACK feedback signal <NUM>.

Specifically, in one embodiment, the T-SRI field comprises a <NUM>-bit field comprising a <NUM>-bit SPS release indicator value that indicates whether reserved bits for SPS PDSCH release(s) are included in Type-<NUM> HARQ ACK feedback signal <NUM> or not. For example, "<NUM>" for the SPS release indicator value means that reserved bits for SPS PDSCH release(s) are present in Type-<NUM> HARQ ACK feedback signal <NUM> and "<NUM>" for the SPS release indicator value means that reserved bits for SPS PDSCH release(s) are not present in Type-<NUM> HARQ ACK feedback signal <NUM>. If SPS release indicator value within the T-SRI field indicates that the reserved bits for SPS PDSCH release(s) are present, the UE <NUM> is 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 <NUM>, then total number of reserved bits is <NUM> and if the total number of HARQ processes for DL SPS configured for the UE is <NUM>, then total number of reserved bits is <NUM>, and so on.

Alternately, in another embodiment, the T-SRI field comprises a <NUM>-bit field comprising a <NUM>-bit SPS release indicator value that identifies the total number of reserved bits for SPS PDSCH release(s). In some embodiments, the <NUM>-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 <NUM>-bit SPS release indicator value and the total number of reserved bits for SPS PDSCH release(s), as shown in the Table <NUM> below.

Table <NUM> indicates a one to many mapping between the <NUM>-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 UE <NUM> is configured to determine a select value of the number of reserved bits from the multiple values of the number of reserved bits, for a <NUM>-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 UE <NUM>. 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 <NUM>, in one example embodiment, if the T-SRI field comprises <NUM>,<NUM> and the total number of HARQ processes for DL SPS configured for the UE is <NUM>, then the number of reserved bits is chosen to be <NUM>. However, if the T-SRI field comprises <NUM>,<NUM> and the total number of HARQ processes for DL SPS configured for the UE <NUM> is <NUM>, then the number of reserved bits could be <NUM> or <NUM>, based on Table <NUM>. In such embodiments, if the actual number of received SRS PDSCH release indications at the UE <NUM> is <NUM>, then the number of reserved bits is chosen to be <NUM>.

Appending reserved bits for SPS PDSCH release to the Type-<NUM> HARQ-ACK feedback signal <NUM>, as explained above, increases the HARQ-ACK payload of the Type-<NUM> HARQ-ACK feedback signal <NUM>. Therefore, in some embodiments, the one or more HARQ-ACK bits for SPS PDSCH release(s) are included within the Type-<NUM> HARQ-ACK feedback signal <NUM> without appending additional bits. For example, in one embodiment, the one or more HARQ-ACK bits for SPS PDSCH release(s) within the Type-<NUM> HARQ-ACK feedback signal <NUM> corresponds to bit positions associated with HARQ processes of the corresponding SPS PDSCH within the Type-<NUM> HARQ-ACK feedback signal <NUM>. More particularly, when the UE <NUM> is configured with a set of HARQ processes for DL SPS, the Type-<NUM> HARQ-ACK feedback signal <NUM> comprises 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-<NUM> HARQ-ACK feedback signal <NUM> corresponds 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 UE <NUM> by radio resource control (RRC) signaling.

<FIG> illustrates a simplified block diagram of a wireless communication system <NUM>, according to one embodiment of the disclosure. In some embodiments, the wireless communication system <NUM> supports group-based HARQ-ACK feedback. The wireless communication system <NUM> comprises a user equipment (UE) <NUM> and a base station (BS) <NUM>. In other embodiments, however, the wireless communication system <NUM> can comprise a plurality of UEs and is not shown here for clarity purposes. In some embodiments, base station <NUM> is equivalent to an eNodeB in LTE systems, gNodeB in <NUM> new radio (NR) systems etc. In some embodiments, the UE <NUM> may comprise a mobile phone, tablet computer, an internet of things (IoT) device, a vehicle-to-everything (V2X) UE, etc. The UE <NUM> and the base station <NUM> are configured to communicate with one another over a communication medium (e.g., air).

In some embodiments, the BS <NUM> is configured to configure a set of HARQ processes for the UE <NUM>. 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 BS <NUM> is 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 UE <NUM>. For example, <FIG> illustrates a set of <NUM> HARQ processes identified by HPIs <NUM> to <NUM>. Further, the <NUM> HARQ processes are grouped into <NUM> HPGs, HPG #<NUM>, HPG#<NUM> and HPG#<NUM>. The HPIs 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#<NUM> includes HPI <NUM>/<NUM>/<NUM>/<NUM> which may be intended to be utilized for ultra-reliable and low-latency communications (URLLC) with highest reliability requirement. Similarly, HPG#<NUM> and HPG#<NUM> 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 in <FIG>. 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 <NUM>/<NUM>/<NUM>/<NUM> have a same priority class, say priority class index <NUM> and are grouped into one HPG with a priority class index <NUM>. Similarly, the HPI <NUM>/<NUM>/<NUM>/<NUM>/<NUM>/<NUM>/<NUM>/<NUM>/<NUM>/<NUM>/<NUM>/<NUM> have a same priority class, say priority class index <NUM> and are grouped into another HPG with a priority class index <NUM>. 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 BS <NUM> is configured to generate an HPG configuration signal <NUM>. In some embodiments, the HPG configuration signal <NUM> comprises information of the plurality HARQ process groups (HPGs) configured for the UE <NUM>. The BS <NUM> is further configured to send the HPG configuration signal <NUM> to the UE <NUM>. <FIG> depicts two possible signal configurations for the HPG configuration signal <NUM>. Specifically, in <FIG>, 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 UE <NUM>. Each bit has either value <NUM> (indicating that the corresponding HARQ process is not included in the HPG) or value <NUM> (indicating that the corresponding HARQ process is included in the HPG).

Further, in <FIG>, 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 in <FIG>. 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 signal <NUM> are also contemplated to be within the scope of this disclosure. Upon receiving the HPG configuration signal <NUM> from the BS <NUM>, the UE <NUM> is configured to receive and process the HPG configuration signal <NUM>. In some embodiments, the UE <NUM> is configured to determine the information of the plurality HARQ process groups (HPGs) configured for the UE <NUM>, based on processing the HPG configuration signal <NUM>.

Referring back to <FIG>, in some embodiments, the BS <NUM> is further configured to provide a downlink control information (DCI) <NUM> to the UE <NUM>. In some embodiments, the DCI <NUM> is configured to trigger a HARQ-ACK feedback signal <NUM> from the UE <NUM>. In some embodiments, the HARQ-ACK feedback signal <NUM> is configured to include HARQ-ACK information associated with one or more HARQ processes configured for the UE <NUM>. In some embodiments, the DCI <NUM> comprises information of physical uplink control channel (PUCCH)/physical uplink shared channel (PUSCH) resources to be utilized by the UE <NUM> for the transmission of the HARQ-ACK feedback signal <NUM>. In some embodiments, the HARQ-ACK feedback signal <NUM> comprises a Type-<NUM> HARQ-ACK feedback or a Type-<NUM> HARQ-ACK codebook. In such embodiments, the DCI <NUM> comprises a one-shot HARQ-ACK frequent field, a value associated therewith providing an indication to the UE <NUM> to trigger a Type-<NUM> HARQ-ACK feedback. Alternately, in other embodiments, the HARQ-ACK feedback signal <NUM> may comprise other types of HARQ-ACK signals, for example, Type-<NUM> HARQ-ACK feedback signal or a Type-<NUM> HARQ-ACK codebook. In some embodiments, the Type-<NUM> HARQ-ACK feedback signal is configured by radio resource control (RRC) signaling. In some embodiments, the DCI <NUM> is configured to trigger the HARQ-ACK feedback signal <NUM> from the UE <NUM>, in response to a physical downlink shared channel (PDSCH) scheduled by the DCI <NUM>. Alternately, in other embodiments, for example, in the case of Type-<NUM> HARQ-ACK feedback, the DCI <NUM> may trigger the HARQ-ACK feedback signal <NUM>, without scheduling the PDSCH to the UE <NUM>. In some embodiments, the DCI <NUM> further comprises information that identifies one or more HPGs of the plurality of HPGs configured for the UE <NUM> (by the HPG configuration signal <NUM>), the HARQ-ACK feedback information of which are to be included in the HARQ-ACK feedback signal <NUM> that is triggered by the DCI <NUM>.

Once the BS <NUM> provides/sends the DCI <NUM> to the UE <NUM>, the UE <NUM> is configured to receive and process the DCI <NUM>. Upon processing the DCI <NUM>, the UE <NUM> is configured to identify the one or more HPGs identified in the DCI <NUM>. Further, the UE <NUM> is configured to generate the HARQ-ACK feedback signal <NUM> comprising the HARQ-ACK feedback information of HARQ processes associated with the one or more HPGs (indicated by the DCI <NUM>). In such embodiments, the HARQ-ACK feedback signal <NUM> would 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 DCI <NUM>. Subsequently, the UE <NUM> is configured to provide/send the HARQ-ACK feedback signal <NUM> to the BS <NUM>.

The DCI <NUM> may be configured to indicate to the UE <NUM>, the information that identifies one or more HPGs of the plurality of HPGs configured for the UE <NUM>, 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 DCI <NUM>. 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 <NUM> below. Specifically, Table <NUM> indicates a predefined mapping between the HPG request field value and a pair of servings cells, HPG(s).

Table <NUM> above indicates a <NUM>-bit value for the HPG Request Field. However, in other embodiments, the value of the HPG request field may have more or less than <NUM> 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 UE <NUM> is configured to determine the one or more HPGs, based on processing the DCI <NUM>, in accordance with the predefined mapping between the HPG request field value and the one or more HPGs, as given in Table <NUM> above. For example, if the HPG request filed value indicated in the DCI <NUM> is <NUM>, the UE <NUM> is configured to provide HARQ-ACK information associated with the <NUM>nd set of HPGs from Table <NUM>, as part of the HARQ-ACK feedback signal <NUM>.

In a second embodiment, the DCI <NUM> comprises cyclic redundancy check (CRC) bits that are scrambled by a predefined HPG sequence, say [w0, w1. 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 signal <NUM>. 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 <NUM> illustrates an example mapping between the predefined HPG sequence and the one or more HPGs.

Specifically, Table <NUM> 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 <NUM> below.

In such embodiments, the UE <NUM> 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 the predefined mapping between the predefined HPG sequence and the one or more HPGs. For example, if the predefined sequence is determined to be [<NUM>,<NUM>,<NUM>,<NUM>. ,<NUM>], the UE <NUM> identifies the corresponding HPG sequence value as "<NUM>" from the Table <NUM> above and determine the one or more HPGs associated with the HPG sequence value "<NUM>" from Table <NUM> above. However, in other embodiments, Table <NUM> 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 DCI <NUM> further includes a priority indicator field that comprises information on a select priority class index (e.g., priority class index <NUM> in <FIG>) associated with an HPG configured for the UE <NUM>. In such embodiments, the UE <NUM> is configured to determine the one or more HARQ processes (e.g., HPI <NUM>/<NUM>/<NUM>/<NUM> in <FIG>) associated with the HPG identified by the select priority class index, based on processing the DCI <NUM>. Further, the UE <NUM> is configured to generate the HARQ-ACK feedback signal <NUM> comprising HARQ feedback information of the one or more HARQ processes associated with the select priority class index.

Referring back to <FIG>, in some embodiments, the BS <NUM> is further configured to generate and provide a HARQ process regrouping signal <NUM> to the UE <NUM>. In some embodiments, the HARQ process regrouping signal <NUM> comprises information to regroup the HARQ processes associated with one or more HPGs of the plurality of HPGs configured for the UE <NUM> (e.g., by the HPG configuration signal <NUM>). In some embodiments, the regrouping information is included in a HARQ regroup media access control (MAC) control element (CE) within the HARQ process regrouping signal <NUM>. 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 signal <NUM> comprises 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 UE <NUM>. Each HARQ regroup MAC CE (as illustrated in <FIG>) 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 UE <NUM>. 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> illustrates an example HARQ regroup MAC CE <NUM> associated with the first embodiment. The HARQ regroup MAC CE <NUM> is associated with a select HPG identified by an HPGID. The HARQ regroup MAC CE <NUM> has <NUM> octets, Octet#<NUM>, Octet#<NUM> and Octet#<NUM>. The HARQ regroup MAC CE <NUM> further includes <NUM>-fields (can be different in other embodiments) that correspond to a set of <NUM> HARQ processes configured for the UE <NUM>. Each of the H-fields is identified as Hi, where i identifies the corresponding HARQ process. If the Hi field is set as "<NUM>", 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 "<NUM>", 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 signal <NUM> comprises 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 UE <NUM>. 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 UE <NUM>. 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> illustrates an example HARQ regroup MAC CE <NUM> associated with the second embodiment. The HARQ regroup MAC CE <NUM> is associated with N HPGs identified by the HPG IDs HPG#<NUM>. HPG#N-<NUM>. The HARQ regroup MAC CE <NUM> further includes <NUM>-fields (can be different in other embodiments) per HPGID, wherein the <NUM>-fields (can be different in other embodiments) correspond to a set of <NUM> HARQ processes configured for the UE <NUM>. 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 "<NUM>", it can be identified that the HARQ process i is included in the HPG g. Alternately, if the Hg,i, field is set as "<NUM>", it can be identified that the HARQ process i is excluded from the HPG g. Referring back to <FIG>, the UE <NUM> is further configured to receive and process the HARQ process regrouping signal <NUM>. Upon processing the HARQ process regrouping signal <NUM>, the UE <NUM> is configured to determine a plurality of updated HPGs configured for the UE <NUM>.

<FIG> illustrates a simplified block diagram of a wireless communication system <NUM>, according to one embodiment of the disclosure. In some embodiments, the wireless communication system <NUM> facilitates to provide new data indicator (NDI) as part of HARQ-ACK feedback. The wireless communication system <NUM> comprises a user equipment (UE) <NUM> and a base station (BS) <NUM>. In other embodiments, however, the wireless communication system <NUM> can comprise a plurality of UEs and is not shown here for clarity purposes. In some embodiments, base station <NUM> is equivalent to an eNodeB in LTE systems, gNodeB in <NUM> new radio (NR) systems etc. In some embodiments, the UE <NUM> may comprise a mobile phone, tablet computer, an internet of things (IoT) device, a vehicle-to-everything (V2X) UE, etc. The UE <NUM> and the base station <NUM> are configured to communicate with one another over a communication medium (e.g., air).

In some embodiments, the UE <NUM> is 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 BS <NUM> is configured to send/provide a new data indicator (NDI) configuration signal <NUM> to the UE <NUM>. In some embodiments, the NDI configuration signal <NUM> is configured to configure the UE <NUM> to include a latest NDI value detected by the UE <NUM> 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 (e.g., the HARQ-ACK feedback signal <NUM>). In some embodiments, the NDI configuration signal <NUM> comprises a radio resource configuration (RRC) signal. The UE <NUM> is configured to receive and process the NDI configuration signal <NUM>.

In some embodiments, the BS <NUM> is further configured to provide a downlink control information (DCI) <NUM> to the UE <NUM>. The DCI <NUM> is configured to trigger a HARQ-ACK feedback signal <NUM> from the UE <NUM>. In some embodiments, the DCI <NUM> comprises information of physical uplink control channel (PUCCH)/physical uplink shared channel (PUSCH) resources to be utilized by the UE <NUM> for the transmission of the HARQ-ACK feedback signal <NUM>. In some embodiments, the HARQ-ACK feedback signal <NUM> comprises a Type-<NUM> HARQ-ACK feedback. In such embodiments, the DCI <NUM> comprises a one-shot HARQ-ACK frequent field, a value associated therewith providing an indication to the UE <NUM> to trigger a Type-<NUM> HARQ-ACK feedback. Alternately, in other embodiments, the HARQ-ACK feedback signal <NUM> may comprise other types of HARQ-ACK signals, for example, Type-<NUM> HARQ-ACK feedback signal. In some embodiments, the DCI <NUM> is configured to trigger the HARQ-ACK feedback signal <NUM> from the UE <NUM>, in response to a physical downlink shared channel (PDSCH) scheduled by the DCI <NUM>. Alternately, in other embodiments, for example, in the case of Type-<NUM> HARQ-ACK feedback, the DCI <NUM> may trigger the HARQ-ACK feedback signal <NUM>, without scheduling the PDSCH to the UE <NUM>. The UE <NUM> is configured to receive and process the DCI <NUM>. In some embodiments, the UE <NUM> is further configured to generate the HARQ-ACK feedback signal <NUM>, in response to processing the DCI <NUM>. In some embodiments, the HARQ-ACK feedback signal <NUM> comprises a HARQ-ACK feedback information for one or more HARQ processes associated with the UE <NUM>, and an NDI value (i.e., a latest NDI value) detected by the UE <NUM> for the corresponding one or more HARQ processes. Subsequently, the UE <NUM> is configured to provide/send the HARQ-ACK feedback signal <NUM> to the BS <NUM>. The BS <NUM> is further configured to receive and process the HARQ-ACK feedback signal <NUM>.

In some embodiments, the NDI value for the corresponding HARQ processes are detected by the UE <NUM> from the DCIs 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 signal <NUM> facilitates the BS <NUM> to identify any mismatch between the data provided by the BS <NUM> and the respective HARQ-ACK information provided by the UE <NUM>. In some embodiments, the UE <NUM> may be configured with a plurality of HARQ process groups (HPGs), as explained above with respect to <FIG>. In such embodiments, if the DCI <NUM> includes information that identifies one or more HPGs of the plurality of HPGs (similar to the DCI <NUM> in <FIG>), the HARQ-ACK feedback signal <NUM> is configured to include a latest new data indicator (NDI) value detected by the UE <NUM> for each of the HARQ processes associated with the one or more HPGs that are identified by the DCI <NUM>.

Referring to <FIG>, illustrated is a block diagram of an apparatus <NUM> employable at a Base Station (BS), eNodeB, gNodeB or other network device, according to various aspects described herein. In some embodiments, the apparatus <NUM> may be included within the BS <NUM>, the BS <NUM> and the BS <NUM> in the above embodiments. However, in other embodiments, the apparatus <NUM> could be included within any gNodeB associated with a new radio (NR) system. The apparatus <NUM> can include one or more processors <NUM> (e.g., one or more baseband processors such as one or more of the baseband processors discussed in connection with <FIG> and/or <FIG>) comprising processing circuitry and associated interface(s) (e.g., one or more interface(s) discussed in connection with <FIG>), transceiver circuitry <NUM> (e.g., which can comprise circuitry for one or more wired connections and/or part or all of RF circuitry <NUM>, 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 memory <NUM> (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) <NUM> or transceiver circuitry <NUM>).

In particular, the term memory is intended to include an installation medium , e. , 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, apparatus <NUM> can 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) <NUM>, transceiver circuitry <NUM>, and the memory <NUM> can 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 to <FIG>, illustrated is a block diagram of an apparatus <NUM> employable at a user equipment (UE) or other network device (e.g., loT device), according to various aspects described herein. In some embodiments, the apparatus <NUM> may be included within the UE <NUM>, the UE <NUM> and the UE <NUM> in the above embodiments. However, in other embodiments, the apparatus <NUM> could be included within any UE associated with a new radio (NR) system. Apparatus <NUM> can include one or more processors <NUM> (e.g., one or more baseband processors such as one or more of the baseband processors discussed in connection with <FIG> and/or <FIG>) comprising processing circuitry and associated interface(s) (e.g., one or more interface(s) discussed in connection with <FIG>), transceiver circuitry <NUM> (e.g., comprising part or all of RF circuitry <NUM>, 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 memory <NUM> (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) <NUM> or transceiver circuitry <NUM>). In particular, the term memory is intended to include an installation medium , e. , 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, apparatus <NUM> can 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) <NUM>) 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) <NUM>) 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> illustrates a flowchart of a method <NUM> for a UE associated with a wireless communication system that supports SPS release together with Type-<NUM> HARQ-ACK codebook configuration, according to one embodiment of the disclosure. The method <NUM> is explained herein with reference to the apparatus <NUM> in <FIG>. In some embodiments, the apparatus <NUM> could be included within the UE <NUM> in <FIG>. Therefore, the method <NUM> is further explained with reference to the wireless communication system <NUM> in <FIG>. At <NUM>, a downlink control information (DCI) (e.g., the DCI <NUM> in <FIG>) received from a base station (e.g., the BS <NUM> in <FIG>) associated therewith, is processed using the one or more processors <NUM>. In some embodiments, the DCI comprises an indication to trigger a Type-<NUM> hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal (e.g., the Type-<NUM> HARQ-ACK feedback signal <NUM> in <FIG>).

At <NUM>, the Type-<NUM> HARQ ACK feedback signal is generated, based on processing the DCI, using the one or more processors <NUM>. In some embodiments, the Type-<NUM> 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. At <NUM>, the Type-<NUM> HARQ-ACK feedback signal is provided to the base station, using the one or more processors <NUM>.

<FIG> illustrates a flowchart of a method <NUM> for a base station (BS) associated with a wireless communication system that supports SPS release together with Type-<NUM> HARQ-ACK codebook configuration, according to one embodiment of the disclosure. The method <NUM> is explained herein with reference to the apparatus <NUM> in <FIG>. In some embodiments, the apparatus <NUM> could be included within the BS <NUM> in <FIG>. Therefore, the method <NUM> is further explained with reference to the wireless communication system <NUM> in <FIG>. At <NUM>, a downlink control information (DCI) (e.g., the DCI <NUM> in <FIG>) is provided to a user equipment (UE) (e.g., the UE <NUM> in <FIG>) associated therewith, using the one or more processors <NUM>. In some embodiments, the DCI comprises an indication to the UE to trigger a Type-<NUM> hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback signal (e.g., the Type-<NUM> HARQ-ACK feedback signal <NUM> in <FIG>). At <NUM>, the Type-<NUM> HARQ ACK feedback signal received from the UE, in response to providing the DCI, is processed using the one or more processors <NUM>. In some embodiments, the Type-<NUM> 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> illustrates a flowchart of a method <NUM> for a UE associated with a wireless communication system that supports group-based HARQ-ACK feedback, according to one embodiment of the disclosure. The method <NUM> is explained herein with reference to the apparatus <NUM> in <FIG>. In some embodiments, the apparatus <NUM> could be included within the UE <NUM> in <FIG>. Therefore, the method <NUM> is further explained with reference to the wireless communication system <NUM> in <FIG>. At <NUM>, a hybrid automatic repeat request process group (HPG) configuration signal (e.g., the HPG configuration signal <NUM> in <FIG>) is received from a base station (e.g., the BS <NUM>) associated therewith, using the one or more processors <NUM>. 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.

At <NUM>, the plurality of HPGs associated with the set of HARQ processes configured for the UE, is determined using the one or more processors <NUM>, based on processing the HPG configuration signal. At <NUM>, a downlink control information (DCI) (e.g., the DCI <NUM> in <FIG>) is received from the base station, using the one or more processors <NUM>. 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 signal <NUM> in <FIG>) that is triggered by the DCI. At <NUM>, 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 processors <NUM>. At <NUM>, the HARQ-ACK feedback signal is send to the base station, using the one or more processors <NUM>.

<FIG> illustrates a flowchart of a method <NUM> for 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 method <NUM> is explained herein with reference to the apparatus <NUM> in <FIG>. In some embodiments, the apparatus <NUM> could be included within the BS <NUM> in <FIG>. Therefore, the method <NUM> is further explained with reference to the wireless communication system <NUM> in <FIG>. At <NUM>, a hybrid automatic repeat request process group (HPG) configuration signal (e.g., the HPG configuration signal <NUM> in <FIG>) is send to a user equipment (UE) (e.g., the UE <NUM> in <FIG>) associated therewith, using the one or more processors <NUM>. 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.

At <NUM>, a downlink control information (DCI) (e.g., the DCI <NUM> in <FIG>) is send to the UE, using the one or more processors <NUM>. 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 signal <NUM> in <FIG>) that is triggered by the DCI. At <NUM>, the HARQ-ACK feedback signal is received from the UE, using the one or more processors <NUM>. 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> illustrates a flowchart of a method <NUM> for 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 method <NUM> is explained herein with reference to the apparatus <NUM> in <FIG>. In some embodiments, the apparatus <NUM> could be included within the UE <NUM> in <FIG>. Therefore, the method <NUM> is further explained with reference to the wireless communication system <NUM> in <FIG>. At <NUM>, a new data indicator (NDI) configuration signal (e.g., the NDI configuration signal <NUM> in <FIG>) is received from a base station (e.g., the BS <NUM> in <FIG>), using the one or more processors <NUM>. 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. At <NUM>, a downlink control information (DCI) (e.g., the DCI <NUM> in <FIG>) is received from the base station (BS), using the one or more processors <NUM>. In some embodiments, the DCI is configured to trigger a HARQ-ACK feedback signal (e.g., the HARQ-ACK feedback signal <NUM> in <FIG>). At <NUM>, the HARQ-ACK feedback signal is generated using the one or more processors <NUM>. 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. At <NUM>, the HARQ-ACK feedback signal is send to the BS, using the one or more processors <NUM>.

<FIG> illustrates a flowchart of a method <NUM> for 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 method <NUM> is explained herein with reference to the apparatus <NUM> in <FIG>. In some embodiments, the apparatus <NUM> could be included within the BS <NUM> in <FIG>. Therefore, the method <NUM> is further explained with reference to the wireless communication system <NUM> in <FIG>. At <NUM>, a new data indicator (NDI) configuration signal (e.g., the NDI configuration signal <NUM> in <FIG>) is send to a user equipment (UE) (e.g., the UE <NUM> in <FIG>), using the one or more processors <NUM>. 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. At <NUM>, a downlink control information (DCI) (e.g., the DCI <NUM> in <FIG>) is send to the UE, using the one or more processors <NUM>. In some embodiments, the DCI is configured to trigger a HARQ-ACK feedback signal (e.g., the HARQ-ACK feedback signal <NUM> in <FIG>) from the UE. At <NUM>, the HARQ-ACK feedback signal is received from the UE using the one or more processors <NUM>. 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> illustrates an architecture of a system <NUM> including a Core Network (CN) <NUM>, for example a Fifth Generation (<NUM>) CN (5GC), in accordance with various embodiments. The system <NUM> is shown to include a UE <NUM>, 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)AN <NUM>, 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) <NUM>, which can be, for example, operator services, Internet access or third party services; and a Fifth Generation Core Network (5GC) <NUM>. The 5GC <NUM> can comprise one or more of the following functions and network components: an Authentication Server Function (AUSF) <NUM>; an Access and Mobility Management Function (AMF) <NUM>; a Session Management Function (SMF) <NUM>; a Network Exposure Function (NEF) <NUM>; a Policy Control Function (PCF) <NUM>; a Network Repository Function (NRF) <NUM>; a Unified Data Management (UDM) <NUM>; an Application Function (AF) <NUM>; a User Plane (UP) Function (UPF) <NUM>; and a Network Slice Selection Function (NSSF) <NUM>.

The UPF <NUM> can act as an anchor point for intra-RAT and inter-RAT mobility, an external Protocol Data Unit (PDU) session point of interconnect to DN <NUM>, and a branching point to support multi-homed PDU session. The UPF <NUM> can 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. UPF <NUM> can include an uplink classifier to support routing traffic flows to a data network. The DN <NUM> can represent various network operator services, Internet access, or third-party services. DN <NUM> can include, or be similar to, an application server. The UPF <NUM> can interact with the SMF <NUM> via an N4 reference point between the SMF <NUM> and the UPF <NUM>.

The AUSF <NUM> can store data for authentication of UE <NUM> and handle authentication-related functionality. The AUSF <NUM> can facilitate a common authentication framework for various access types. The AUSF <NUM> can communicate with the AMF <NUM> via an N12 reference point between the AMF <NUM> and the AUSF <NUM>; and can communicate with the UDM <NUM> via an N13 reference point between the UDM <NUM> and the AUSF <NUM>. Additionally, the AUSF <NUM> can exhibit an Nausf service-based interface.

The AMF <NUM> can be responsible for registration management (e.g., for registering UE <NUM>, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. The AMF <NUM> can be a termination point for the an N11 reference point between the AMF <NUM> and the SMF <NUM>. The AMF <NUM> can provide transport for SM messages between the UE <NUM> and the SMF <NUM>, and act as a transparent proxy for routing SM messages. AMF <NUM> can also provide transport for SMS messages between UE <NUM> and a Short Message Service (SMS) Function (SMSF) (not shown in <FIG>). AMF <NUM> can act as SEcurity Anchor Function (SEAF), which can include interaction with the AUSF <NUM> and the UE <NUM> and/or receipt of an intermediate key that was established as a result of the UE <NUM> authentication process. Where Universal Subscriber Identity Module (USIM) based authentication is used, the AMF <NUM> can retrieve the security material from the AUSF <NUM>. AMF <NUM> can 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, AMF <NUM> can be a termination point of a RAN Control Plane (CP) interface, which can include or be an N2 reference point between the (R)AN <NUM> and the AMF <NUM>; and the AMF <NUM> can be a termination point of Non Access Stratum (NAS) (N1) signaling, and perform NAS ciphering and integrity protection.

AMF <NUM> can also support NAS signaling with a UE <NUM> over 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)AN <NUM> and the AMF <NUM> for the control plane, and can be a termination point for the N3 reference point between the (R)AN <NUM> and the UPF <NUM> for the user plane. As such, the AMF <NUM> can handle N2 signaling from the SMF <NUM> and the AMF <NUM> for 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 UE <NUM> and AMF <NUM> via an N1 reference point between the UE <NUM> and the AMF <NUM>, and relay uplink and downlink user-plane packets between the UE <NUM> and UPF <NUM>. The N3IWF also provides mechanisms for IPsec tunnel establishment with the UE <NUM>. The AMF <NUM> can exhibit an Namf service-based interface, and can be a termination point for an N14 reference point between two AMFs <NUM> and an N17 reference point between the AMF <NUM> and a <NUM> Equipment Identity Register (<NUM>-EIR) (not shown in <FIG>).

The UE <NUM> can be registered with the AMF <NUM> in order to receive network services. Registration Management (RM) is used to register or deregister the UE <NUM> with the network (e.g., AMF <NUM>), and establish a UE context in the network (e.g., AMF <NUM>). The UE <NUM> can operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE <NUM> is not registered with the network, and the UE context in AMF <NUM> holds no valid location or routing information for the UE <NUM> so the UE <NUM> is not reachable by the AMF <NUM>. In the RM-REGISTERED state, the UE <NUM> is registered with the network, and the UE context in AMF <NUM> can hold a valid location or routing information for the UE <NUM> so the UE <NUM> is reachable by the AMF <NUM>. In the RM-REGISTERED state, the UE <NUM> can 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 UE <NUM> is 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 AMF <NUM> can store one or more RM contexts for the UE <NUM>, 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 AMF <NUM> can 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 AMF <NUM> can store a Coverage Enhancement (CE) mode B Restriction parameter of the UE <NUM> in an associated MM context or RM context. The AMF <NUM> can 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 UE <NUM> and the AMF <NUM> over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE <NUM> and the CN <NUM>, 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 UE <NUM> between the AN (e.g., RAN <NUM>) and the AMF <NUM>. The UE <NUM> can operate in one of two CM states, CM-IDLE mode or CM-CONNECTED mode. When the UE <NUM> is operating in the CM-IDLE state/mode, the UE <NUM> may have no NAS signaling connection established with the AMF <NUM> over the N1 interface, and there can be (R)AN <NUM> signaling connection (e.g., N2 and/or N3 connections) for the UE <NUM>. When the UE <NUM> is operating in the CM-CONNECTED state/mode, the UE <NUM> can have an established NAS signaling connection with the AMF <NUM> over the N1 interface, and there can be a (R)AN <NUM> signaling connection (e.g., N2 and/or N3 connections) for the UE <NUM>. Establishment of an N2 connection between the (R)AN <NUM> and the AMF <NUM> can cause the UE <NUM> to transition from CM-IDLE mode to CM-CONNECTED mode, and the UE <NUM> can transition from the CM-CONNECTED mode to the CM-IDLE mode when N2 signaling between the (R)AN <NUM> and the AMF <NUM> is released.

The SMF <NUM> can 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 UE <NUM> and a data network (DN) <NUM> identified by a Data Network Name (DNN). PDU sessions can be established upon UE <NUM> request, modified upon UE <NUM> and 5GC <NUM> request, and released upon UE <NUM> and 5GC <NUM> request using NAS SM signaling exchanged over the N1 reference point between the UE <NUM> and the SMF <NUM>. Upon request from an application server, the 5GC <NUM> can trigger a specific application in the UE <NUM>. In response to receipt of the trigger message, the UE <NUM> can pass the trigger message (or relevant parts/information of the trigger message) to one or more identified applications in the UE <NUM>. The identified application(s) in the UE <NUM> can establish a PDU session to a specific DNN. The SMF <NUM> can check whether the UE <NUM> requests are compliant with user subscription information associated with the UE <NUM>. In this regard, the SMF <NUM> can retrieve and/or request to receive update notifications on SMF <NUM> level subscription data from the UDM <NUM>.

The SMF <NUM> can 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 SMFs <NUM> can be included in the system <NUM>, which can be between another SMF <NUM> in a visited network and the SMF <NUM> in the home network in roaming scenarios. Additionally, the SMF <NUM> can exhibit the Nsmf service-based interface.

The NEF <NUM> can 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., AF <NUM>), edge computing or fog computing systems, etc. In such embodiments, the NEF <NUM> can authenticate, authorize, and/or throttle the AFs. NEF <NUM> can also translate information exchanged with the AF <NUM> and information exchanged with internal network functions. For example, the NEF <NUM> can translate between an AF-Service-Identifier and an internal 5GC information. NEF <NUM> can also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information can be stored at the NEF <NUM> as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF <NUM> to other NFs and AFs, and/or used for other purposes such as analytics. Additionally, the NEF <NUM> can exhibit an Nnef service-based interface.

The NRF <NUM> can support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF <NUM> also 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 NRF <NUM> can exhibit the Nnrf service-based interface.

The PCF <NUM> can provide policy rules to control plane function(s) to enforce them, and can also support unified policy framework to govern network behavior. The PCF <NUM> can also implement an FE to access subscription information relevant for policy decisions in a UDR of the UDM <NUM>. The PCF <NUM> can communicate with the AMF <NUM> via an N15 reference point between the PCF <NUM> and the AMF <NUM>, which can include a PCF <NUM> in a visited network and the AMF <NUM> in case of roaming scenarios. The PCF <NUM> can communicate with the AF <NUM> via an N5 reference point between the PCF <NUM> and the AF <NUM>; and with the SMF <NUM> via an N7 reference point between the PCF <NUM> and the SMF <NUM>. The system <NUM> and/or CN <NUM> can also include an N24 reference point between the PCF <NUM> (in the home network) and a PCF <NUM> in a visited network. Additionally, the PCF <NUM> can exhibit an Npcf service-based interface.

The UDM <NUM> can handle subscription-related information to support the network entities' handling of communication sessions, and can store subscription data of UE <NUM>. For example, subscription data can be communicated between the UDM <NUM> and the AMF <NUM> via an N8 reference point between the UDM <NUM> and the AMF. The UDM <NUM> can include two parts, an application Functional Entity (FE) and a Unified Data Repository (UDR) (the FE and UDR are not shown in <FIG>). The UDR can store subscription data and policy data for the UDM <NUM> and the PCF <NUM>, and/or structured data for exposure and application data (including Packet Flow Descriptions (PFDs) for application detection, application request information for multiple UEs <NUM>) for the NEF <NUM>. The Nudr service-based interface can be exhibited by the UDR <NUM> to allow the UDM <NUM>, PCF <NUM>, and NEF <NUM> to 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 SMF <NUM> via an N10 reference point between the UDM <NUM> and the SMF <NUM>. UDM <NUM> can also support SMS management, wherein an SMS-FE implements similar application logic as discussed elsewhere herein. Additionally, the UDM <NUM> can exhibit the Nudm service-based interface.

The AF <NUM> can provide application influence on traffic routing, provide access to NEF <NUM>, and interact with the policy framework for policy control. 5GC <NUM> and AF <NUM> can provide information to each other via NEF <NUM>, which can be used for edge computing implementations. In such implementations, the network operator and third party services can be hosted close to the UE <NUM> access 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 UPF <NUM> close to the UE <NUM> and execute traffic steering from the UPF <NUM> to DN <NUM> via the N6 interface. This can be based on the UE subscription data, UE location, and information provided by the AF <NUM>. In this way, the AF <NUM> can influence UPF (re)selection and traffic routing. Based on operator deployment, when AF <NUM> is considered to be a trusted entity, the network operator can permit AF <NUM> to interact directly with relevant NFs. Additionally, the AF <NUM> can exhibit an Naf service-based interface.

The NSSF <NUM> can select a set of network slice instances serving the UE <NUM>. The NSSF <NUM> can also determine allowed Network Slice Selection Assistance Information (NSSAI) and the mapping to the subscribed Single NSSAIs (S-NSSAls), as appropriate. The NSSF <NUM> can also determine the AMF set to be used to serve the UE <NUM>, or a list of candidate AMF(s) <NUM> based on a suitable configuration and possibly by querying the NRF <NUM>. The selection of a set of network slice instances for the UE <NUM> can be triggered by the AMF <NUM> with which the UE <NUM> is registered by interacting with the NSSF <NUM>, which can lead to a change of AMF <NUM>. The NSSF <NUM> can interact with the AMF <NUM> via an N22 reference point between AMF <NUM> and NSSF <NUM>; and can communicate with another NSSF <NUM> in a visited network via an N31 reference point (not shown in <FIG>). Additionally, the NSSF <NUM> can exhibit an Nnssf service-based interface.

As discussed previously, the CN <NUM> can include an SMSF, which can be responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE <NUM> to/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 AMF <NUM> and UDM <NUM> for a notification procedure that the UE <NUM> is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM <NUM> when UE <NUM> is available for SMS).

The CN <NUM> can also include other elements that are not shown in <FIG>, such as a Data Storage system/architecture, a <NUM>-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 in <FIG>). 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 in <FIG>). The <NUM>-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 from <FIG> for clarity. In one example, the CN <NUM> can include an Nx interface, which is an inter-CN interface between the MME (e.g., a non-<NUM> MME) and the AMF <NUM> in order to enable interworking between CN <NUM> and a non-<NUM> CN. Other example interfaces/reference points can include an N5g-EIR service-based interface exhibited by a <NUM>-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> illustrates example components of a device <NUM> in accordance with some embodiments. In some embodiments, the device <NUM> can include application circuitry <NUM>, baseband circuitry <NUM>, Radio Frequency (RF) circuitry <NUM>, front-end module (FEM) circuitry <NUM>, one or more antennas <NUM>, and power management circuitry (PMC) <NUM> coupled together at least as shown. The components of the illustrated device <NUM> can be included in a UE or a RAN node. In some embodiments, the device <NUM> can include fewer elements (e.g., a RAN node may not utilize application circuitry <NUM>, and instead include a processor/controller to process IP data received from a CN such as 5GC <NUM> or an Evolved Packet Core (EPC)). In some embodiments, the device <NUM> can 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 circuitry <NUM> can include one or more application processors. For example, the application circuitry <NUM> can 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 device <NUM>. In some embodiments, processors of application circuitry <NUM> can process IP data packets received from an EPC.

The baseband circuitry <NUM> can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry <NUM> can include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry <NUM> and to generate baseband signals for a transmit signal path of the RF circuitry <NUM>. Baseband circuity <NUM> can interface with the application circuitry <NUM> for generation and processing of the baseband signals and for controlling operations of the RF circuitry <NUM>. For example, in some embodiments, the baseband circuitry <NUM> can include a third generation (<NUM>) baseband processor 1504A, a fourth generation (<NUM>) baseband processor 1504B, a fifth generation (<NUM>) baseband processor 1504C, or other baseband processor(s) 1504D for other existing generations, generations in development or to be developed in the future (e.g., second generation (<NUM>), sixth generation (<NUM>), etc.). The baseband circuitry <NUM> (e.g., one or more of baseband processors 1504A-D) can handle various radio control functions that enable communication with one or more radio networks via the RF circuitry <NUM>. In other embodiments, some or all of the functionality of baseband processors 1504A-D can be included in modules stored in the memory <NUM> 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 circuitry <NUM> can include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry <NUM> can 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 circuitry <NUM> can 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 circuitry <NUM> and the application circuitry <NUM> can be implemented together such as, for example, on a system on a chip (SOC).

In some embodiments, the baseband circuitry <NUM> can provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry <NUM> can 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 circuitry <NUM> is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry.

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

In some embodiments, the receive signal path of the RF circuitry <NUM> can include mixer circuitry 1506a, amplifier circuitry 1506b and filter circuitry 1506c. In some embodiments, the transmit signal path of the RF circuitry <NUM> can include filter circuitry 1506c and mixer circuitry 1506a. RF circuitry <NUM> can also include synthesizer circuitry 1506d for synthesizing a frequency for use by the mixer circuitry 1506a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 1506a of the receive signal path can be configured to down-convert RF signals received from the FEM circuitry <NUM> based on the synthesized frequency provided by synthesizer circuitry 1506d. The amplifier circuitry 1506b can be configured to amplify the down-converted signals and the filter circuitry 1506c can 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 circuitry <NUM> for 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 circuitry 1506a of 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 circuitry 1506a of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1506d to generate RF output signals for the FEM circuitry <NUM>. The baseband signals can be provided by the baseband circuitry <NUM> and can be filtered by filter circuitry 1506c.

In some embodiments, the mixer circuitry 1506a of the receive signal path and the mixer circuitry 1506a of 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 circuitry 1506a of the receive signal path and the mixer circuitry 1506a of 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 circuitry 1506a of the receive signal path and the mixer circuitry 1506a can be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 1506a of the receive signal path and the mixer circuitry 1506a of 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 circuitry <NUM> can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry <NUM> can include a digital baseband interface to communicate with the RF circuitry <NUM>.

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 circuitry 1506d can be a fractional-N synthesizer or a fractional N/N+<NUM> 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 circuitry 1506d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

The synthesizer circuitry 1506d can be configured to synthesize an output frequency for use by the mixer circuitry 1506a of the RF circuitry <NUM> based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 1506d can be a fractional N/N+<NUM> 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 circuitry <NUM> or the applications circuitry <NUM> depending 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 circuitry <NUM>.

Synthesizer circuitry 1506d of the RF circuitry <NUM> can 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+<NUM> (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 circuitry 1506d can 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 circuitry <NUM> can include an IQ/polar converter.

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

In some embodiments, the FEM circuitry <NUM> can 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 circuitry <NUM>). The transmit signal path of the FEM circuitry <NUM> can include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry <NUM>), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas <NUM>).

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

While <FIG> shows the PMC <NUM> coupled only with the baseband circuitry <NUM>. However, in other embodiments, the PMC <NUM> may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry <NUM>, RF circuitry <NUM>, or FEM circuitry <NUM>.

In some embodiments, the PMC <NUM> can control, or otherwise be part of, various power saving mechanisms of the device <NUM>. For example, if the device <NUM> is 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 device <NUM> can 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 device <NUM> can transition off to an RRC_ldle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device <NUM> goes 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 device <NUM> may 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.

Processors of the application circuitry <NUM> and processors of the baseband circuitry <NUM> can be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry <NUM>, alone or in combination, can be used execute Layer <NUM>, Layer <NUM>, or Layer <NUM> functionality, while processors of the application circuitry <NUM> can utilize data (e.g., packet data) received from these layers and further execute Layer <NUM> functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer <NUM> can comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer <NUM> 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 <NUM> can comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.

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

The baseband circuitry <NUM> can further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface <NUM> (e.g., an interface to send/receive data to/from memory external to the baseband circuitry <NUM>), an application circuitry interface <NUM> (e.g., an interface to send/receive data to/from the application circuitry <NUM> of <FIG>), an RF circuitry interface <NUM> (e.g., an interface to send/receive data to/from RF circuitry <NUM> of <FIG>), a wireless hardware connectivity interface <NUM> (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 interface <NUM> (e.g., an interface to send/receive power or control signals to/from the PMC <NUM>).

In various aspects, embodiments discussed herein can facilitate techniques of inter-cell BM (Beam Management) via L1 (Layer <NUM>) 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.

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. 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.

Claim 1:
A user equipment, UE (<NUM>, <NUM>, <NUM>, <NUM>), device comprising a processor (<NUM>, <NUM>, 1504A-E) configured to perform operations comprising:
receiving a downlink control information, DCI (<NUM>, <NUM>, <NUM>), from a base station (<NUM>, <NUM>, <NUM>) associated therewith, wherein the DCI (<NUM>, <NUM>, <NUM>) comprises an indication to trigger a Type-<NUM> hybrid automatic repeat request, HARQ,-acknowledgement, ACK, feedback signal, and wherein the DCI (<NUM>, <NUM>, <NUM>) further comprises information of a number of reserved bits including one or more reserved bits that are reserved to include HARQ-ACK information for one or more semi-persistent scheduling, SPS, physical downlink shared channel, PDSCH, release(s) that are to be included in the Type-<NUM> HARQ-ACK feedback signal (<NUM>);
generating the Type-<NUM> HARQ-ACK feedback signal (<NUM>), based on processing the DCI (<NUM>, <NUM>, <NUM>), wherein the Type-<NUM> HARQ-ACK feedback signal (<NUM>) comprises the one or more reserved bits, wherein each of the one or more reserved bits is adapted to include HARQ-ACK information for an SPS PDSCH release associated with the UE (<NUM>, <NUM>, <NUM>, <NUM>); and
sending the Type-<NUM> HARQ-ACK feedback signal (<NUM>) to the base station (<NUM>, <NUM>, <NUM>).