Method and apparatus for physical downlink shared channel (PDSCH) hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback in wireless communication

Abstract

A user equipment (UE) associated with a wireless communication system is disclosed. The UE includes a processor configured to receive a first downlink control information (DCI) to schedule a first physical downlink shared channel (PDSCH). The first DCI includes a non-numerical (NN) value K1 for hybrid automatic repeat request (HARQ)-ACK feedback. The processor is further configured to determine a first priority level associated with the first PDSCH and determine K1 values and priority levels associated with one or more subsequent PDSCHs received from the BS until a selected PDSCH having a numerical K1 value and a priority level same as the first priority level is identified. Further, the processor is configured to provide the HARQ-ACK feedback associated with the first PDSCH using a PUCCH / PUSCH occasion indicated by a second DCI scheduling the selected PDSCH.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the field of wireless communication systems, and in particular, to a system and method for Physical Downlink Shared Channel (PDSCH) Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) feedback in wireless communications. BACKGROUND

[0002] Networks need to provide data quickly and reliably without overburdening their resources. Hybrid Automatic Repeat Request (HARQ) techniques can accomplish this. 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 a negative acknowledgement (NACK) from the destination before transmitting the next block of data or retransmitting the same block of data. Such a transmission / reception process that relies on ACK / NACK feedback is sometimes referred to as a HARQ process. BRIEF DESCRIPTION OF DRAWINGS

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

[0004] Figure 1a And Figure 1b HARQ-ACK feedback timing determination in a legacy system when two HARQ-ACK codebooks with different priority levels are configured for a UE is shown.

[0005] Figure 2a A simplified block diagram of a wireless communication system according to one embodiment of the present disclosure is shown.

[0006] Figure 2b And Figure 2c HARQ-ACK feedback timing determination when two HARQ-ACK codebooks with different priority levels are configured for a UE according to one embodiment of the present disclosure is shown.

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

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

[0009] Figure 5 A flow diagram of a method for a UE associated with a wireless communication network when the UE is configured with two HARQ-ACK codebooks with different priority levels according to one embodiment of the present disclosure is shown.

[0010] Figure 6 A flow diagram illustrating a method for a base station (BS) associated with a wireless communication network when an associated UE is configured with two HARQ-ACK codebooks having different priority levels is shown, in accordance with one embodiment of the present disclosure.

[0011] Figure 7 An architecture of a system including a core network (CN), e.g., a Fifth Generation (5G) CN (5GC), is shown in accordance with various embodiments.

[0012] Figure 8 Exemplary components of a device, in accordance with some embodiments, are shown.

[0013] Figure 9 Exemplary interfaces of baseband circuitry, in accordance with some embodiments, are shown. DETAILED DESCRIPTION

[0014] In one embodiment of the disclosure, a user equipment (UE) associated with a wireless communication system is disclosed. The UE includes a processor configured to process a first downlink control information (DCI) for scheduling a first physical downlink shared channel (PDSCH) received from a base station (BS) associated with the UE. In some embodiments, the first DCI includes a non-numerical (NN) value of K1 for hybrid automatic repeat request (HARQ)-ACK feedback. In some embodiments, K1 indicates a time delay between a corresponding PDSCH and HARQ-ACK feedback associated with the corresponding PDSCH. The processor is further configured to process the first PDSCH received from the BS and determine a first priority level associated with the first PDSCH. In addition, the processor is configured to determine K1 values and priority levels associated with one or more subsequent PDSCHs received from the BS until a selected PDSCH having a numerical K1 value and a same priority level as the first priority level is identified. Furthermore, the processor is further configured to provide HARQ-ACK feedback associated with the first PDSCH using a physical uplink control channel (PUCCH) occasion or a physical uplink shared channel (PUSCH) occasion indicated by a second DCI scheduling the selected PDSCH having the same priority level.

[0015] In one embodiment of the disclosure, a base station associated with a wireless communication system is disclosed. The base station includes a processor configured to provide, to a user equipment (UE) associated with the base station, a first downlink control information (DCI) for scheduling a first physical downlink shared channel (PDSCH) having a first priority level associated therewith. In some embodiments, the first DCI includes a non-numerical (NN) value of K1 for hybrid automatic repeat request (HARQ)-ACK feedback. In some embodiments, K1 indicates a time delay between a corresponding PDSCH and HARQ-ACK feedback associated with the corresponding PDSCH. The processor is further configured to provide the first PDSCH to the UE. Further, the processor is configured to provide one or more subsequent PDSCHs to the UE. In some embodiments, a selected PDSCH of the one or more subsequent PDSCHs includes a numerical K1 value for HARQ-ACK feedback and a same priority level as the first priority level associated with the first PDSCH. Further, the processor is configured to process HARQ-ACK feedback associated with the first PDSCH received from the UE, wherein the HARQ-ACK feedback associated with the first PDSCH is received on a physical uplink control channel (PUCCH) occasion or a physical uplink shared channel (PUSCH) occasion indicated by a second DCI scheduling the selected PDSCH having the same priority level.

[0016] In one embodiment of the disclosure, a method for a user equipment (UE) associated with a wireless communication system is disclosed. The method includes processing, using one or more processors, a first downlink control information (DCI) received from a base station (BS) scheduling a first physical downlink shared channel (PDSCH) associated with the UE. In some embodiments, the first DCI includes a non-numerical (NN) value of K1 for hybrid automatic repeat request (HARQ)-ACK feedback. In some embodiments, K1 indicates a time delay between a corresponding PDSCH and HARQ-ACK feedback associated with the corresponding PDSCH. The method further includes processing, using the one or more processors, the first PDSCH received from the BS, and determining, using the one or more processors, a first priority level associated with the first PDSCH. In addition, the method includes determining, using the one or more processors, K1 values and priority levels associated with one or more subsequent PDSCHs received from the BS until a selected PDSCH with a numerical K1 value and a priority level same as the first priority level is identified. Furthermore, the method includes providing, using a physical uplink control channel (PUCCH) occasion or a physical uplink shared channel (PUSCH) occasion indicated by DCI scheduling the selected PDSCH with the same priority level, HARQ-ACK feedback associated with the first PDSCH from the one or more processors.

[0017] In one embodiment of the disclosure, a method for a base station (BS) associated with a wireless communication system is disclosed. The method includes providing, using one or more processors, a user equipment (UE) associated with the base station with a first downlink control information (DCI) scheduling a first physical downlink shared channel (PDSCH) having a first priority level associated therewith. In some embodiments, the first DCI includes a non-numerical (NN) value of K1 for hybrid automatic repeat request (HARQ)-ACK feedback. In some embodiments, K1 indicates a time delay between a corresponding PDSCH and HARQ-ACK feedback associated with the corresponding PDSCH. The method further includes providing, using the one or more processors, the UE with the first PDSCH. In addition, the method includes providing, using the one or more processors, the UE with one or more subsequent PDSCHs. In some embodiments, a selected PDSCH of the one or more subsequent PDSCHs includes a numerical K1 value for HARQ-ACK feedback and a same priority level as the first priority level associated with the first PDSCH. Moreover, the method includes processing, using the one or more processors, HARQ-ACK feedback associated with the first PDSCH received from the UE. In some embodiments, receiving HARQ-ACK feedback associated with the first PDSCH is on a physical uplink control channel (PUCCH) occasion or a physical uplink shared channel (PUSCH) occasion indicated by DCI scheduling a selected PDSCH having a same priority level.

[0018] The present disclosure will now be described with reference to the attached figures. Wherever possible, the same or like reference numbers will be used throughout the drawings to refer to same or like parts. Where indicated, structures and devices shown in the drawings have not necessarily been drawn to scale. As used herein, the terms “component,” “system,” “interface,” “circuit,” and the like are intended to refer to a computer-related entity, either 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, and / or a user equipment (e.g., a mobile phone, etc.) with a processor device. By way of illustration, both an application running on a server and the server can 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” of the elements.

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

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

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

[0022] The following detailed description relates to the drawings. Like reference numerals can be used in the different drawings to identify like or similar elements. In the following description, for the purposes of explanation, specific details are set forth in order to provide a thorough understanding of aspects of the various embodiments. However, it is apparent to one skilled in the art that various aspects of the various embodiments can be practiced without these specific details. In some instances, descriptions of well-known devices, circuits, and methods can be omitted so as not to obscure the description of the various embodiments with details that are well known to those skilled in the art.

[0023] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled in a manner that minimizes risks from unauthorized or unintended access or use, and that is in compliance with privacy policies and practices that are clearly communicated to users.

[0024] As noted above, HARQ processes rely on receiving ACK / NACK for data packets. When a base station (BS) transmits data to a user equipment (UE) over a physical downlink shared channel (PDSCH), the UE determines the correctness of the data by checking a cyclic redundancy check (CRC) and reports the data to the base station through an ACK / NACK bit. If the UE has data to transmit and it is authorized, it will send the ACK / NACK along with the data on a physical uplink shared channel (PUSCH), otherwise it will send the ACK / NACK on a physical uplink control channel (PUCCH). The HARQ-ACK codebook defines the format used to signal a set of HARQ acknowledgements (ACKs) to the base station. This HARQ-ACK codebook allows the UE to multiplex HARQ ACKs from multiple slots, multiple carriers, multiple transport blocks, and multiple code block groups (CBGs) within a single transmission. Importantly, both the UE and the base station share the same understanding of the codebook format to ensure that each acknowledgement is linked to the appropriate transmission. The base station configures the use of a particular codebook category using the pdsch-HARQ-ACK-Codebook information element in the downlink control information (DCI) that schedules the PDSCH. Different categories of HARQ-ACK codebooks are defined in 3GPP. For example, Type 1 HARQ-ACK codebooks, which include semi-static codebooks, where the size of the codebook is fixed according to information provided through radio resource control (RRC) signaling, and Type 2 HARQ-ACK codebooks, which include dynamic codebooks, where the size of the codebook varies according to the number of resource allocations. In addition, Type 3 HARQ-ACK codebooks are defined, which are triggered on demand by a one-shot HARQ-ACK field in the DCI.

[0025] 3GPP supports up to two HARQ-ACK codebooks for a UE. Specifically, a UE can be instructed by a pdsch-HARQ-ACK-Codebook-List indication to generate one or two HARQ-ACK codebooks. If a UE is instructed to generate two HARQ-ACK codebooks, the first HARQ-ACK codebook is associated with a PUCCH of priority index 0 (e.g., higher priority) and the second HARQ-ACK codebook is associated with a PUCCH of priority index 1 (e.g., lower priority). As noted above, a PUCCH or PUSCH occasion is used to provide a UE with HARQ-ACK feedback associated with a PDSCH transmission. In some embodiments, the terms HARQ-ACK feedback and HARQ-ACK codebook refer to the same entity. A DCI scheduling a PDSCH includes a PDSCH-to-HARQ_feedback timing indicator field that informs a UE about the HARQ ACK feedback timing (in slots) relative to the PDSCH reception. If a UE detects a DCI scheduling a PDSCH reception ending in slot n, the UE provides the corresponding HARQ-ACK information in a PUCCH / PUSCH transmission in slot n+k, where k is the number of slots indicated by the PDSCH-to-HARQ_feedback timing indicator field. For example, a K1 value is provided in the PDSCH-to-HARQ_feedback timing indicator field. Unless otherwise specified, the PDSCH-to-HARQ_feedback timing indicator field provides an applicable value (e.g., a numerical value).

[0026] However, in the case where the UE is configured with Type-2 / Enhanced Type-2 HARQ-ACK codebook, in some embodiments, the DCI scheduling the PDSCH can provide a PDSCH-to-HARQ_feedback timing indicator field including an inapplicable value, e.g., a non-numerical (NN)-K1 value for HARQ-ACK feedback. Thus, in such embodiments, the UE cannot identify the PUCCH / PUSCH occasion for HARQ-ACK feedback. In such embodiments, in the current implementation, the UE is configured to keep the HARQ-ACK feedback information associated with the PDSCH (with NN-K1 value for HARQ-ACK feedback), and the UE multiplexes the corresponding HARQ-ACK feedback information in the PUCCH or PUSCH transmission in the slot indicated by the K1 value (i.e., numerical value or applicable value) of the PDSCH-to-HARQ_feedback timing indicator field in the subsequent DCI format scheduling the subsequent PDSCH, as shown in Figure 1a and Figure 1b Specifically, in Figure 1a and Figure 1b , the HARQ-ACK1 associated with PDSCH1 with non-numerical value of K1 (i.e., NN-K1) is multiplexed with the HARQ-ACK2 associated with PDSCH2 with numerical value of K1.

[0027] In some embodiments, the PDSCH1 associated with HARQ-ACK1 and the PDSCH2 associated with HARQ-ACK2 are associated with the same priority level (i.e., priority level 1), as shown in Figure 1a Alternatively, in other embodiments, the PDSCH1 associated with HARQ-ACK1 and the PDSCH2 associated with HARQ-ACK2 can be associated with different priority levels, as shown in Figure 1b In embodiments where PDSCH1 and PDSCH2 have different priority levels, utilizing the same PUCCH / PUSCH to transmit the HARQ-ACK feedback associated with both PDSCH1 and PDSCH2 can impact the reliability requirement of the PDSCH with higher priority level. For example, in Figure 1bIn the case where PDSCH2 with priority level 0 (i.e., higher priority level) can be utilized to carry ultra-reliable low latency communications (URLLC), and PDSCH1 with priority level 1 (i.e., lower priority level) can be utilized to carry enhanced mobile broadband (eMBB) traffic. Thus, in such implementations, utilizing the same PUCCH / PUSCH to transmit HARQ-ACK feedback associated with both URLLC and eMBB can impact the reliability requirements associated with URLLC. To overcome the aforementioned shortcoming, systems, circuits, and techniques are disclosed herein for allowing a UE to multiplex HARQ-ACK feedback for PDSCHs with the same priority level on a PUCCH / PUSCH occasion when the UE is configured with two HARQ-ACK codebooks with different priority levels and when the UE receives a DCI with a non-numerical (NN)-K1 value for HARQ-ACK feedback.

[0028] Figure 2a A simplified block diagram of a wireless communication system 200 is shown in accordance with one embodiment of the present disclosure. The wireless communication system 200 includes a user equipment (UE) 202 and a base station (BS) 204. However, in other embodiments, the wireless communication system 200 can include multiple UEs and, for the sake of clarity, are not shown here. In some embodiments, the base station 204 is equivalent to an eNodeB in a LTE system, a gNodeB in a 5G New Radio (NR) system, and the like. In some embodiments, the UE 202 can include a mobile phone, a tablet computer, an Internet of Things (IoT) device, a vehicle-to-everything (V2X) UE, and the like. The UE 202 and the base station 204 are configured to communicate with each other over a communication medium (e.g., air). In some embodiments, the wireless communication system 200 allows the UE 202 to multiplex HARQ-ACK feedback for PDSCHs with the same priority level on a physical uplink control channel (PUCCH) / physical uplink shared channel (PUSCH) when the UE is configured with two HARQ-ACK codebooks with different priority levels and when the UE receives a DCI with a non-numerical (NN)-K1 value for HARQ-ACK feedback, as can be fully appreciated below.

[0029] In some embodiments, the BS 204 is configured to generate a first downlink control information (DCI) 206 for scheduling a first physical downlink shared channel (PDSCH) 208. In some embodiments, the first DCI 206 includes a non-numerical (NN) value of K1 for hybrid automatic repeat request (HARQ)-ACK feedback. In some embodiments, K1 indicates a time delay between the first PDSCH and the corresponding HARQ-ACK feedback. In some embodiments, the NN-K1 can correspond to any inapplicable value of K1. In some embodiments, the NN-K1 value is included in a PDSCH-to-HARQ_feedback timing indicator field within the first DCI 206. After generating the first DCI 206, the BS 204 is configured to provide the first DCI 206 to the UE 202. After providing the first DCI 206, the BS 204 is further configured to provide the first PDSCH 208. The UE 202 is configured to receive the first DCI 206 from the BS 204 and process the first DCI 206. After processing the first DCI 206, the UE 202 is configured to determine the NN-K1 value for the HARQ-ACK feedback.

[0030] The UE 202 is further configured to receive the first PDSCH 208 from the BS 204 and process the first PDSCH 208. After processing the first PDSCH 208, the UE 202 is configured to generate HARQ-ACK feedback information for the first PDSCH 206. Further, the UE 202 is configured to determine a first priority level / priority associated with the first PDSCH 208. In some embodiments, the first priority level associated with the first PDSCH 208 is indicated to the UE 202 as part of the first DCI 206. Alternatively, in other embodiments, the first priority level associated with the first PDSCH 206 is preconfigured and provided to the UE 202 via radio resource control (RRC) signaling from the BS 204.

[0031] Because the K1 value associated with the first DCI 206 includes the NN-K1, the UE 202 is configured to hold the HARQ-ACK feedback information associated with the first PDSCH 208 and provide the HARQ-ACK feedback information associated with the first PDSCH 208 on the PUCCH / PUSCH occasion associated with the subsequent PDSCH. Specifically, the UE 202 is configured to provide the HARQ-ACK feedback information on the PUCCH / PUSCH occasion associated with the subsequent PDSCH that has a numerical K1 value for HARQ-ACK feedback and a priority level that is the same as the first priority level. In such an implementation, the UE 202 is configured to determine the K1 value and the priority level associated with one or more subsequent PDSCHs (e.g., the second PDSCH 212 or the third PDSCH 218) received from the BS until a selected PDSCH is identified that has a numerical K1 value and a priority level that is the same as the first priority level. Upon identifying the selected PDSCH, the UE 202 is configured to provide the HARQ-ACK feedback associated with the first PDSCH 208 using the PUCCH occasion / PUSCH occasion indicated by the DCI that schedules the selected PDSCH having the same priority level, as explained in detail below.

[0032] Referring back Figure 2a, the BS 204 is further configured to provide the UE 202 with a second DCI 210 for scheduling a second PDSCH 212. Further, the BS 204 is configured to provide the UE 202 with the second PDSCH 212. In some embodiments, the second DCI 210 and the second PDSCH 212 are provided to the UE 202 from the BS 204 after or following the provision of the first DCI 206 and the first PDSCH 208 from the BS 204 to the UE 202. The UE 202 is configured to receive and process the second DCI 210 and the second PDSCH 212. Upon processing the second DCI 210, the UE 202 is configured to determine whether a numerical K1 value or a NN-K1 value is included in the PDSCH-to-HARQ_feedback timing indicator field within the second DCI 210. Further, the UE 202 is configured to generate second HARQ-ACK feedback information associated with the second PDSCH 212. Additionally, the UE 202 is configured to determine a priority level associated with the second PDSCH 212. In some embodiments, the priority level associated with the second PDSCH 212 is indicated to the UE 202 as part of the second DCI 210. Alternatively, in other embodiments, the priority level associated with the second PDSCH 212 is preconfigured and provided to the UE 202 via radio resource control (RRC) signaling from the BS 204.

[0033] In one example embodiment, as shown in FIG. 2A, assume that the second DCI 210 includes a numerical value for K1 for HARQ-ACK feedback. Accordingly, the UE 202 is configured to provide the second HARQ-ACK feedback information associated with the second PDSCH 212 using a second PUCCH / PUSCH occasion 214 associated with the second PDSCH 212. In some embodiments, the second PUCCH / PUSCH occasion 214 associated with the second PDSCH 212 is determined based on the numerical value for K1 indicated within the second DCI 210. Further, assume that the priority level for the second PDSCH 212 includes the same priority level as the first priority level for the first PDSCH 208, as shown in FIG. 2A. Accordingly, the UE 202 is further configured to provide the first HARQ-ACK feedback associated with the first PDSCH 208 on the second PUCCH / PUSCH occasion 214, as shown in FIG. 2A. Figure 2b Figure 2b Figure 2b Figure 2b ​​​As can be seen, the first PDSCH 208 and the second PDSCH 212 have a priority level of 1 (i.e., the same priority level). Moreover, the second PDSCH 212 has a numeric value of K1. Thus, the first HARQ-ACK feedback associated with the first PDSCH 208 is multiplexed with the second HARQ-ACK feedback associated with the PDSCH 212 on the second PUCCH / PUSCH occasion 214.

[0034] However, in other embodiments, if the second PDSCH 212 has a NN-K1 value for HARQ-ACK feedback, or the second PDSCH 212 has a different priority level than the first priority level associated with the first PDSCH 208, or both, the UE 202 is configured to hold the first HARQ-ACK information associated with the first PDSCH 208 until a subsequent PDSCH is identified that has a numeric K1 value and the same priority level as the first priority level associated with the first PDSCH 208. Specifically, in Figure 2c In this case, it is assumed that the second PDSCH 212 has a different priority level than the first priority level associated with the first PDSCH 208. Referring back to Figure 2a In such embodiments, the BS 204 is further configured to provide a third DCI 216 for scheduling a third PDSCH 218. Moreover, the BS 204 is configured to provide the third PDSCH 218. The UE 202 is configured to receive and process the third DCI 216 and the third PDSCH 218. In processing the third DCI 216, the UE 202 is configured to determine whether a numeric K1 value or a NN-K1 value is included in the PDSCH-to-HARQ_feedback timing indicator field within the third DCI 216. Moreover, the UE 202 is configured to generate third HARQ-ACK information associated with the third PDSCH 218. Additionally, the UE 202 is configured to determine a priority level associated with the third PDSCH 218. In some embodiments, the priority level associated with the third PDSCH 218 is indicated to the UE 202 as part of the third DCI 216. Alternatively, in other embodiments, the priority level associated with the third PDSCH 218 is preconfigured and provided to the UE 202 via radio resource control (RRC) signaling from the BS 204.

[0035] If it is determined that the third DCI 216 includes a numeric value of K1 for HARQ-ACK feedback, the UE 202 is configured to provide third HARQ-ACK feedback information associated with the third PDSCH 218 using a third PUCCH / PUSCH occasion 220 associated with the third PDSCH 218. In some embodiments, the third PUCCH / PUSCH occasion 220 associated with the third PDSCH 218 is determined based on the numeric value of K1 indicated within the third DCI 216. Further, if it is determined that the priority level of the third PDSCH 218 includes the same priority level as the first priority level of the first PDSCH 208, the UE 202 is further configured to provide first HARQ-ACK feedback associated with the first PDSCH 208 on the third PUCCH / PUSCH occasion 220, as shown in Figure 2b In such embodiments, the first HARQ-ACK feedback associated with the first PDSCH 208 and the third HARQ-ACK feedback associated with the third PDSCH 218 are multiplexed on the third PUCCH / PUSCH occasion 220. Specifically, in Figure 2b , the first PDSCH 208 and the third PDSCH 218 have a priority level of 1 (i.e., the same priority level). Further, the third PDSCH 218 has a numeric value of K1. Accordingly, the first HARQ-ACK feedback associated with the first PDSCH 208 is multiplexed with the third HARQ-ACK feedback associated with the third PDSCH 218 on the third PUCCH / PUSCH occasion 220.

[0036] Referring to Figure 3 , a block diagram of an apparatus 300 capable of being employed at a base station (BS), eNodeB, gNodeB, or other network device is shown in accordance with various aspects described herein. In some embodiments, the apparatus 300 can be included within the base station 204 in the above embodiments. However, in other embodiments, the apparatus 300 can be included within any base station associated with a wireless communication system. The apparatus 300 can include one or more processors (e.g., one or more baseband processors, such as discussed in connection with Figure 8 and / or Figure 9 the one or more baseband processors) including processing circuitry 310 and an associated interface (e.g., a bus interface) to, for example, the one or more baseband processors), as discussed in connection with Figure 9one or more interfaces discussed); transceiver circuitry 320 (e.g., the transceiver circuitry can include portions of or all of circuitry for one or more wired connections and / or RF circuitry 806, which can include 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), where the transmitter circuitry and receiver circuitry can employ common circuit elements, distinct circuit elements, or a combination thereof); and memory 330 (which can include any of a variety of storage mediums and can store instructions and / or data associated with one or more of the processor(s) 310 or the transceiver circuitry 320).

[0037] In particular, the term memory is intended to include an installation medium, e.g., CD- ROM, floppy disks, or a tape device; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, e.g., a hard disk drive or optical storage; registers, or other similar types of memory elements, etc. Memory media can also include other types of memory or combinations thereof In various aspects, the apparatus 300 can be included within an evolved universal terrestrial radio access network (E-UTRAN) node B (evolved Node B, eNodeB, or eNB), a next generation node B (gNodeB or gNB), or other base station or TRP (transmit / receive point) in a wireless communication network. In some aspects, the processor(s) 310, transceiver circuitry 320, and memory 330 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. In some embodiments, the one or more processors 310, transceiver circuitry 320, and memory circuitry 330 can be implemented as part of a modem system on a single integrated circuit (IC). Alternatively, in other embodiments, the one or more processors 310, transceiver circuitry 320, and memory circuitry 330 can be implemented on different ICs.

[0038] Reference Figure 4 is shown a block diagram of an apparatus 400 that can be employed at a user equipment (UE) or other network device (e.g., an IoT device) in accordance with various aspects described herein. In some embodiments, the apparatus 400 can be included within the UE 202 in the above embodiments. However, in other embodiments, the apparatus 400 can be included within any UE associated with a wireless communication system. The apparatus 400 can include one or more processors 410 (e.g., one or more baseband processors, such as the baseband processor(s) described in connection with Figure 8 and / or Figure 9 one or more baseband processors discussed), which include processing circuitry and associated interfaces (e.g., in connection with one or more interfaces discussed).Figure 9 one or more interfaces under discussion); transceiver circuitry 420 (e.g., including portions of or all of the RF circuitry 806, which can include transmitter circuitry (e.g., associated with one or more transmit chains) and / or receiver circuitry (e.g., associated with one or more receive chains), which can employ common circuit elements, distinct circuit elements, or a combination thereof); and memory 430, which can include any of a variety of storage media, and which can store instructions and / or data associated with one or more of the processor(s) 410 or the transceiver circuitry 420. Specifically, the term memory is intended to include an installation medium, e.g., CD- ROM, floppy disks, or a tape device; a computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; or a non-volatile memory such as a magnetic media, e.g., a hard drive or optical storage; registers, or other similar types of storage elements, etc. The memory media can also include other types of storage media or combinations thereof In various aspects, the apparatus 1000 can be included within a user equipment (UE).

[0039] 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 the processor(s) 410) can include one or more of the following operations: generating a set of associated bits indicative of the content of the signal or message, encoding (e.g., which can include adding a cyclic redundancy check (CRC) and / or encoding by a turbo code, a low-density parity-check (LDPC) code, a tail-biting convolutional 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 set of scheduled resources, to a set of time and frequency resources authorized for uplink transmission, etc.). Depending on the type of signal or message received, processing (e.g., by the processor(s) 410) can include one or more of the following operations: identifying physical resources associated with the signal / message, detecting the signal / message, resource element group de-interleaving, demodulating, descrambling, and / or decoding. In some embodiments, the one or more processor(s) 410, transceiver circuitry 420, and memory circuitry 430 can be implemented as part of a modem system on a single integrated circuit (IC). Alternatively, in other embodiments, the one or more processor(s) 410, transceiver circuitry 420, and memory circuitry 430 can be implemented on different ICs.

[0040] Figure 5A flow diagram illustrating a method 500 for a UE associated with a wireless communication network when the UE is configured with two HARQ-ACK codebooks having different priority levels is shown, in accordance with one embodiment of the present disclosure. The method 500 is explained herein with reference to the apparatus 400 in Figure 4 In some embodiments, the apparatus 400 can be included within the UE 202 in Figure 2a Thus, the method 500 is further explained with reference to the wireless communication system 200 in Figure 2a At 502, using the one or more processors 410, a first downlink control information (DCI) (e.g., the first DCI 206 in Figure 2a ) received from a base station (e.g., the BS 204 in Figure 2a ) scheduling a first physical downlink shared channel (PDSCH) (e.g., the first PDSCH 208 in Figure 2a ) is processed, the first PDSCH having a first priority level associated therewith. In some embodiments, the first DCI includes a non-numerical (NN) value of K1 for hybrid automatic repeat request (HARQ)-ACK feedback. In some embodiments, K1 indicates a time delay between a corresponding PDSCH and HARQ-ACK feedback associated with the corresponding PDSCH.

[0041] At 504, using the one or more processors 410, the first PDSCH (e.g., the first PDSCH 208 in Figure 2a ) received from the BS is processed. At 506, using the one or more processors 410, a first priority level associated with the first PDSCH is determined. At 508, using the one or more processors 410, K1 values and priority levels associated with one or more subsequent PDSCHs (e.g., the second PDSCH 212 and the third PDSCH 218 in Figure 2a ) received from the BS are determined until a selected PDSCH having a numerical K1 value and a priority level that is the same as the first priority level is identified (e.g., the PDSCH 212 as shown in Figure 2b or the third PDSCH 218 as shown in Figure 2c ). At 510, using a physical uplink control channel (PUCCH) occasion or a physical uplink shared channel (PUSCH) occasion (e.g., the PUCCH / PUSCH 214 as shown in Figure 2b or the PUCCH / PUSCH 220 as shown in Figure 2c ) indicated by the DCI scheduling the selected PDSCH having the same priority level, HARQ-ACK feedback associated with the first PDSCH is provided to the base station from the one or more processors 410.

[0042] Figure 6 A flow diagram illustrating a method 600 for a base station (BS) associated with a wireless communication network when an associated UE is configured with two HARQ-ACK codebooks having different priority levels is shown, according to one embodiment of the disclosure. The method 600 is explained herein with reference to the apparatus 300 in Figure 3 In some embodiments, the apparatus 300 can be included within a BS 204 in Figure 2a Thus, the method 600 is further explained with reference to the wireless communication system 200 in Figure 2a At 602, using the one or more processors 310, a first downlink control information (DCI) (e.g., the first DCI 206 in Figure 2a ) is provided to a user equipment (UE) (e.g., the UE 202 in Figure 2a ) associated with the BS for scheduling a first physical downlink shared channel (PDSCH) (e.g., the first PDSCH 208 in Figure 2a ) having a first priority level associated therewith. In some embodiments, the first DCI includes a non-numerical (NN) value of K1 for hybrid automatic repeat request (HARQ)-ACK feedback. In some embodiments, K1 indicates a time delay between a corresponding PDSCH and HARQ-ACK feedback associated with the corresponding PDSCH.

[0043] At 604, using the one or more processors 310, the first PDSCH is provided to the UE. At 606, using the one or more processors 310, one or more subsequent PDSCHs (e.g., the second PDSCH 212 and the third PDSCH 218 in Figure 2a ) are provided to the UE. In some embodiments, one of the one or more subsequent PDSCHs (e.g., the PDSCH 212 as shown in Figure 2b or the third PDSCH 218 as shown in Figure 2c ) includes a numerical K1 value for HARQ-ACK feedback and a same priority level as the first priority level associated with the first PDSCH. At 608, using the one or more processors 310, HARQ-ACK feedback associated with the first PDSCH is processed received from the UE. In some embodiments, the HARQ-ACK feedback associated with the first PDSCH is in a physical uplink control channel (PUCCH) occasion or a physical uplink shared channel (PUSCH) occasion (e.g., the PUCCH / PUSCH 214 as shown in Figure 2b or the PUSCH 216 as shown in Figure 2creceived on the PUCCH / PUSCH 220) is shown.

[0044] While the method is 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 can occur in different orders and / or concurrently with other acts or events apart from those shown and / or described herein. In addition, not all illustrated acts can be required to implement one or more aspects or embodiments of the disclosure herein. Also, one or more of the acts illustrated herein can be carried out in one or more separate acts and / or phases.

[0045] Embodiments described herein can be implemented into a system using any suitable configuration of hardware and / or software. Figure 7 An architecture of a system 700 including a core network (CN) 720, such as a Fifth Generation (5G) CN (5GC), is shown according to various embodiments. The system 700 is shown to include a UE 701, which can be the same or similar to one or more other UEs discussed herein; a Third Generation Partnership Project (3GPP) Radio Access Network (wireless AN or RAN or RAN) 210, which can include one or more RAN nodes (such as an evolved Node B (eNB), a next Generation Node B (gNB and / or other node), or other node or access point); and a Data Network (DN) 203, which can be, for example, operator services, Internet access or third party services; and a Fifth Generation Core Network (5GC) 720. The 5GC 720 can include one or more of the following functions and network components: an Authentication Server Function (AUSF) 722; an Access and Mobility Management Function (AMF) 721; a Session Management Function (SMF) 724; a Network Exposure Function (NEF) 723; a Policy Control Function (PCF) 726; a Network Repository Function (NRF) 725; a Unified Data Management (UDM) 727; an Application Function (AF) 728; a User Plane (UP) Function (UPF) 702; and a Network Slice Selection Function (NSSF) 729.

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

[0047] The AUSF 722 can store data for authentication of the UE 701 and handle authentication-related functionality. The AUSF 722 can facilitate a common authentication framework for various access types. The AUSF 722 can communicate with the AMF 721 via a N12 reference point between the AMF 721 and the AUSF 722, and can communicate with the UDM 727 via a N13 reference point between the UDM 727 and the AUSF 722. Additionally, the AUSF 722 can exhibit Nausf service-based interfaces.

[0048] The AMF 721 can be responsible for registration management (e.g., for registering the UE 701, etc.), connection management, access authorization, and authentication, and lawful interception of AMF-related events. The AMF 721 can be the termination point of a N11 reference point between the AMF 721 and the SMF 724. The AMF 721 can provide transfer for SM messages between the UE 701 and the SMF 724, and act as a transparent proxy for routing SM messages. The AMF 721 can also provide access to the UE 701 and the short message service (SMS) function (SMSF) 726 for SMS messages (for example, SMS over Figure 7SMS message provide transport between the UE 701 and the AMF 721. The AMF 721 can act as a Security Anchor Function (SEAF), which can include interaction with the AUSF 722 and the UE 701 and / or receipt of an intermediate key established due to the UE 701 authentication process. In cases where authentication based on a Universal Subscriber Identity Module (USIM) is used, the AMF 721 can retrieve the security material from the AUSF 722. The AMF 721 can also include a Single Connection Mode (SCM) function that receives a key from the SEA to derive access-network specific keys. Further, the AMF 721 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 710 and the AMF 721; and the AMF 721 can be a termination point of Non-Access Stratum (NAS) (N1) signaling, and perform NAS ciphering and integrity protection.

[0049] The AMF 721 can also support NAS signaling with the UE 701 through a Non-3GPP (N3) InterWorking Function (IWF) interface. The N3IWF can be used to provide access to untrusted entities. The N3IWF can be a termination point for the N2 interface between the (R)AN 710 and the AMF 721 for the control plane, and can be a termination point for the N3 reference point between the (R)AN 710 and the UPF 702 for the user plane. Thus, the AMF 721 can handle N2 signaling from the SMF 724 and the AMF 721 for PDU sessions and QoS, encapsulate / decapsulate packets for Internet Protocol (IP) security (IPsec) and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS requirements corresponding to N3 packet marking, taking into account QoS requirements associated with such marking received over N2. The N3IWF can also relay uplink and downlink control-plane NAS signaling between the UE 701 and the AMF 721 via an Nl reference point between the UE 701 and the AMF 721, and relay uplink and downlink user-plane packets between the UE 701 and the UPF 702. The N3IWF also provides mechanisms for establishment of IPsec tunnels with the UE 701. The AMF 721 can exhibit a Namf service-based interface, and can be a termination point for an N14 reference point between two AMFs 721 and an N17 reference point between the AMF 721 and a 5G Equipment Identity Register (5G-EIR) (not shown in FIG. 7). Figure 7 The AMF 721 can also support NAS signaling with the UE 701 through a Non-3GPP (N3) InterWorking Function (IWF) interface. The N3IWF can be used to provide access to untrusted entities. The N3IWF can be a termination point for the N2 interface between the (R)AN 710 and the AMF 721 for the control plane, and can be a termination point for the N3 reference point between the (R)AN 710 and the UPF 702 for the user plane. Thus, the AMF 721 can handle N2 signaling from the SMF 724 and the AMF 721 for PDU sessions and QoS, encapsulate / decapsulate packets for Internet Protocol (IP) security (IPsec) and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS requirements corresponding to N3 packet marking, taking into account QoS requirements associated with such marking received over N2. The N3IWF can also relay uplink and downlink control-plane NAS signaling between the UE 701 and the AMF 721 via an Nl reference point between the UE 701 and the AMF 721, and relay uplink and downlink user-plane packets between the UE 701 and the UPF 702. The N3IWF also provides mechanisms for establishment of IPsec tunnels with the UE 701. The AMF 721 can exhibit a Namf service-based interface, and can be a termination point for an N14 reference point between two AMFs 721 and an N17 reference point between the AMF 721 and a 5G Equipment Identity Register (5G-EIR) (not shown in FIG. 7).

[0050] The UE 701 can register with the AMF 721 in order to receive network services. Registration Management (RM) is used to register or deregister the UE 701 with the network (e.g., AMF 721), and establish a UE context in the network (e.g., AMF 721). The UE 701 can operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE 701 is not registered with the network, and the UE context in AMF 721 holds no valid location or routing information for the UE 701 so the AMF 721 cannot reach the UE 701. In the RM-REGISTERED state, the UE 701 is registered with the network, and the UE context in AMF 721 can hold a valid location or routing information for the UE 701 so the AMF 721 can reach the UE 701. In the RM-REGISTERED state, the UE 701 can perform mobility registration update procedures, perform periodic registration update procedures triggered by expiration of a periodic update timer (e.g., to inform the network that the UE 701 is still active), and perform a registration update procedure to update UE capability information or to re-negotiate protocol parameters with the network, among other examples.

[0051] The AMF 721 can store one or more RM contexts for the UE 701, where each RM context is associated with a specific access to the network. The RM context can be a data structure, database object, or the like, that indicates or stores, among other things, a registration state for each access type and a periodic update timer. The AMF 721 can also store a 5GC mobility management (MM) context, which can be the same or similar to an (enhanced packet system (EPS)) MM ((E)MM) context. In various embodiments, the AMF 721 can store a coverage enhancement (CE) mode B restriction parameter for the UE 701 in an associated MM context or an RM context. The AMF 721 can also derive a value, when needed, from a UE’s usage setting parameter already stored in the UE context (and / or MM / RM context).

[0052] Connection Management (CM) can be used to establish and release a signaling connection between the UE 701 and the AMF 721 over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 701 and the CN 720 and comprises of a signaling connection between the UE and the AN (e.g., RRC connection or UE-N3IWF connection for non-3GPP access) and a N2 connection for the UE 701 between an AN (e.g., RAN 710) and the AMF 721. The UE 701 can operate in one of two CM states (CM IDLE mode or CM-CONNECTED mode). When the UE 701 is operating in the CM-IDLE state / mode, the UE 701 can not have NAS signaling connection established with AMF 721 over the N1 interface, and there can be a (R)AN 710 signaling connection (e.g., N2 and / or N3 connection) for the UE 701. When the UE 701 is operating in the CM-CONNECTED state / mode, the UE 701 can have a NAS signaling connection established with the AMF 721 over the N1 interface, and there can be a (R)AN 710 signaling connection (e.g., N2 and / or N3 connection) for the UE 701. Establishment of a N2 connection between the (R)AN 710 and the AMF 721 can cause the UE 701 to transition from the CM-IDLE mode to the CM-CONNECTED mode, and the UE 701 can transition from the CM-CONNECTED mode to the CM-IDLE mode when the N2 signaling between the (R)AN 710 and the AMF 721 is released.

[0053] The SMF 724 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 interfaces to Lawful Intercept (LI) system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information via AMF over N2 to AN; and determining session's Session and Service Continuity (SSC) mode. 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 an exchange of PDUs between a UE 701 and a Data Network (DN) 703 identified by a Data Network Name (DNN). A PDU Session can be established at the request of a UE 701 using NAS SM signaling exchanged between the UE 701 and a SMF 724 over an N1 reference point, may

[0054] The SMF 724 can include the following roaming functionality: handling local enforcement for application of QoS Service Level Agreements (SLAs) (Visited Public Land Mobile Network (VPLMN)); charging data collection and charging interface (VPLMN); lawful intercept (for SM events and interfaces to LI system, in the VPLMN); and support for interaction with external DN for transmission of signaling for PDU session authorization / authentication by external DN. In roaming scenarios, an N16 reference point between two SMFs 724 can be included in the system 700, which can be located between another SMF 724 in a visited network and the SMF 724 in a home network. Additionally, the SMF 724 can exhibit an Nsmf service-based interface.

[0055] The NEF 723 can provide means for securely exposing services and capabilities offered by 3 GPP network functions to third parties, internal exposure / reexposure, application functions (e.g., AFs 728), edge computing or fog computing systems, or the like. In such embodiments, the NEF 723 can authenticate, authorize, and / or throttle the AFs. NEF 723 can also translate information exchanged with the AFs 728 and information exchanged with internal network functions. For example, the NEF 723 can translate between an AF service identifier and an internal 5GC information. NEF 723 can also receive information from other network functions (NFs) based on their exposure capabilities. The information can be stored at the NEF 723 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 723 to other NFs and AFs, and / or used for other purposes such as analytics. In addition, the NEF 723 can exhibit an Nnef service-based interface.

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

[0057] The PCF 726 can provide a control plane function to enforce their policy rules, and can also support unified policy framework to govern network behavior. The PCF 726 can also implement an FE to access subscription information relevant for policy decisions in a UDR of the UDM 727. The PCF 726 can be in communication with the AMF 721 via an N15 reference point between the PCF 726 and the AMF 721, which can include a PCF 726 in a visited network and the AMF 721 in case of roaming scenarios. The PCF 726 can be in communication with the AF 728 via an N5 reference point between the PCF 726 and the AF 728, and can be in communication with the SMF 724 via an N7 reference point between the PCF 726 and the SMF 724. The system 700 and / or CN 720 can also include an N24 reference point between the (home network) PCF 726 and a PCF 726 in a visited network. In addition, the PCF 726 can exhibit an Npcf service-based interface.

[0058] The UDM 727 can handle subscription-related information to support the network entity's handling of communication sessions and can store subscription data of UEs 701. For example, subscription data can be transferred between the UDM 727 and the AMF 721 via an N8 reference point between the UDM 727 and the AMF. The UDM 727 can include two parts: an Application Function entity (FE) and a Unified Data Repository (UDR) (neither of which are shown in FIG. 7). Figure 7 The UDR can store subscription data and policy data for the UDM 727 and the PCF 726, and / or structured data exposed by the NEF 723 for application detection, as well as application data (including packet flow descriptions (PFDs), application request information for multiple UEs 701) for the NEF 723. Nudr-based interfaces can be presented by the UDR 221 to allow the UDM 727, PCF 726, and NEF 723 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. The UDM can include a UDM-FE, which is responsible for credential processing, location management, subscription management, and the like. 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 processing, access authorization, registration / mobility management, and subscription management. The UDR can interact with the SMF 724 via an N10 reference point between the UDM 727 and the SMF 724. The UDM 727 can also support SMS management, with an SMS-FE implementing similar application logic as discussed elsewhere herein. In addition, the UDM 727 can exhibit Nudm-based interfaces.

[0059] The AF 728 can provide application influence on traffic routing, provide access to the NEF 723, and interact with the policy framework to enforce policies. The 5GC 720 and the AF 728 can expose information to each other via the NEF 723, which can be used for edge computing implementations. In such implementations, network operators and third party services can be hosted close to the UE 701 access point of attachment to achieve efficient service delivery with reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC can choose a UPF 702 close to the UE 701 and steer traffic from the UPF 702 to the DN 703 via the N6 interface. This can be based on the UE subscription data, UE location, and information provided by the AF 728. In this way, the AF 728 can influence UPF (re)selection and traffic routing. Based on operator deployment, when the AF 728 is considered a trusted entity, the network operator can allow the AF 728 to interact directly with relevant NFs. Additionally, the AF 728 can exhibit Naf-based interfaces.

[0060] NSSF 729 can select a set of network slice instances to serve UE 701. NSSF 729 can also appropriately determine the allowed network slice selection assistance information (NSSAI) and the mapping to the subscribed individual NSSAI (S-NSSAI). NSSF 729 can also determine the AMF set, or list of candidate AMFs 721, for serving UE 701 based on appropriate configuration and possibly by querying NRF 725. The selection of a set of network slice instances for UE 701 can be triggered by AMF 721, where UE 701 registers through interaction with NSSF 729, which can result in a change to AMF 721. NSSF 729 can interact with AMF 721 via the N22 reference point between AMF 721 and NSSF 729, and via the N31 reference point (…). Figure 7 (Not shown) communicates with another NSSF 729 in the visited network. Additionally, the NSSF 729 can exhibit an interface based on the Nnssf service.

[0061] As discussed above, CN 720 may include an SMSF responsible for SMS subscription checks and authentication, and relaying SM messages to / from UE 701 and to / from other entities such as SMS-Gateway Mobile Switching Center (GMSC) / Interoperable MSC (IWMSC) / SMS routers. The SMSF may also interact with AMF 721 and UDM 727 for notification procedures indicating that UE 701 is available for SMS delivery (e.g., setting a UE unreachable flag and notifying UDM 727 when UE 701 is available for SMS).

[0062] CN 720 may also include Figure 7 Other elements not shown in Figure 1 include data storage systems / architecture, 5G-EIR, and Secure Edge Protection Proxy (SEPP). Data storage systems may include Structured Data Storage Functions (SDSF), Unstructured Data Storage Functions (UDSF), etc. Any NF can store or retrieve unstructured data from or from a UDSF (e.g., UE context) via an N18 reference point between any NF and the UDSF (not shown in Figure 1). Individual NFs may share a UDSF for storing their respective unstructured data, or each NF may have its own UDSF located at or near the respective NF. Additionally, the UDSF may exhibit an interface based on Nudsf services (not shown in Figure 1). The 5G-EIR may be an NF that checks the status of the Permanent Equipment Identifier (PEI) to determine whether a specific piece of equipment / entity should be blacklisted from the network; and the SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on the inter-PLMN control plane interface.

[0063] In addition, there can be more reference points and / or service-based interfaces between NFs in the NF service; however, for clarity, Figure 7 These interfaces and reference points are omitted for clarity. In one example, the CN 720 can include an Nx interface, which is an inter-CN interface between an MME (e.g., a non-5G MME) and the AMF 721 in order to enable interworking between the CN 720 and a non-5G CN. Other example interfaces / reference points can include an N5g-EIR service-based interface exhibited by a 5G-EIR, the N27 reference point between a Network Repository Function (NRF) in a visited network and a NRF in a home network; and the N31 reference point between a NSSF in a visited network and a NSSF in a home network.

[0064] Figure 8 Exemplary components of the device 800 in accordance with some embodiments are illustrated. In some embodiments, the device 800 can include application circuitry 802, baseband circuitry 804, Radio Frequency (RF) circuitry 806, front-end module (FEM) circuitry 808, one or more antennas 810, and power management circuitry (PMC) 812, which can be coupled together as shown in the example of Figure 8. The components of the illustrated device 800 can be included in a UE or a RAN node. In some embodiments, the device 800 can include less functionality, such as a RAN node that does not include the application circuitry 802, but rather includes a processor / controller to process IP data

[0065] The application circuitry 802 can include one or more application processors. For example, the application circuitry 802 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, dedicated processors, and / or dedicated circuitry for providing graphics

[0066] The baseband circuitry 804 can include circuitry such as one or more single-core or multi-core processors. The baseband circuitry 804 can include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 806 and to generate baseband signals for a transmit signal path of the RF circuitry 806. The baseband processing circuitry 804 can interface with the application circuitry 802 for generation and processing of the baseband signals and for control of at least

[0067] In some embodiments, the baseband circuitry 804 can include one or more audio digital signal processor(s) (DSP) 804F. The audio DSP(s) 804F can include elements for compression / decompression and echo cancellation, among other things, and in some embodiments, can include other suitable processing elements. In some embodiments, the components of the baseband circuitry can be combined on a single chip or set of chips (e.g., a system on a chip).

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

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

[0070] In some embodiments, the receive signal path of the RF circuitry 806 can include mixer circuitry 806a, amplifier circuitry 806b and filter circuitry 806c. In some embodiments, the transmit signal path of the RF circuitry 806 can include filter circuitry 806c and mixer circuitry 806a. RF circuitry 806 can also include synthesizer circuitry 806d for synthesizing frequencies for use by the mixer circuitry 806a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 806a of the receive signal path can be configured to down-convert RF signals received from the FEM circuitry 808 based on the synthesized frequencies provided by synthesizer circuitry 806d. The amplifier circuitry 806b can be configured to amplify the down-converted signals, and the filter circuitry 806c 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 804 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 806a of the receive signal path can include passive mixers, although the scope of the embodiments is not limited in this respect.

[0071] In some embodiments, the mixer circuitry 806a of the transmit signal path can be configured to up-convert input baseband signals based on the synthesis frequency provided by the synthesizer circuitry 806d to generate RF output signals for the FEM circuitry 808. The baseband signals can be provided by the baseband circuitry 804 and can be filtered by filter circuitry 806c.

[0072] In some embodiments, the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a 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 806a of the receive signal path and the mixer circuitry 806a 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 806a of the receive signal path and the mixer circuitry 806a can be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path can be configured for superheterodye operation.

[0073] 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 as digital baseband signals can be used in other embodiments. In some alternative embodiments, the output baseband signals and the input baseband signals can be digital baseband signals. In these alternative embodiments, the RF circuitry 806 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 804 can include a digital baseband interface to communicate with the RF circuitry 806.

[0074] In some dual-mode embodiments, separate radio ICs can be provided for processing signals for the

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

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

[0077] In some embodiments, the frequency input can be provided by a voltage-controlled oscillator (VCO), although this is not a requirement. The divider control input can be provided by the baseband circuitry 804 or the application processor 802 in dependence on the desired output frequency. In some embodiments, the divider control input (e.g., N) can be determined from a look-up table based on the channel indicated by the application processor 802.

[0078] Synthesizer circuitry 806d of the RF circuitry 806 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+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements can be configured to break a VCO period up into Nd equal phase segments. In this way, the DLL provides negative feedback to help assure that the total delay through the delay line is one VCO cycle.

[0079] In some embodiments, synthesizer circuitry 806d can be configured to generate a carrier frequency as an 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 806 can include an IQ / polar converter.

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

[0081] In some embodiments, the FEM circuitry 808 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 a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 806). The transmit signal path of the FEM circuitry 808 can include a power amplifier (PA) to amplify input RF signals (e.g., provided by the RF circuitry 806), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 810).

[0082] In some embodiments, the PMC 812 can manage power provided to the baseband circuitry 804. In particular, the PMC 812 can control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 812 can typically be included when the device 800 is capable of being powered by a battery, for example when the device is included in a UE. The PMC 812 can increase the power conversion efficiency in providing the desired implementation size and heat dissipation characteristics.

[0083] Although Figure 8 The PMC 812 is shown to be coupled to only the baseband circuitry 804. However, in other embodiments, the PMC 812 can be additionally or alternatively coupled to other components such as, but not limited to, the application circuitry 802, RF circuitry 806, or FEM 808, and perform similar power management operations for those components.

[0084] In some embodiments, the PMC 812 can control, or otherwise be part of, various power-saving mechanisms of the device 800. For example, if the device 800 is in an RRC_Connected state, where it is still connected to a 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 800 can power down for short durations of time, thus saving power. The device 800 can periodically wake up to monitor for traffic. If there is no traffic for it to receive in the DRX cycle, it can power down again.

[0085] If there is no data traffic activity for an extended period of time, then the device 800 can transition off to an RRCJdle state where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 800 in the RRCJdle state can wake up periodically to listen to the network for paging signals from the network. The device 800 can transition back to an RRC_Connected state to receive data when traffic is present.

[0086] An additional power save mode can leave the device unable to use the network for more than the paging interval (ranging from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time incurs a large delay, and the delay is assumed to be acceptable.

[0087] The processors of application circuitry 802 and the processors of baseband circuitry 804 can be used to execute instructions for one or more instances of a protocol stack. For example, the processors of baseband circuitry 804 can be used to execute functions of the third layer (L3), the second layer (L2), or the first layer (Ll) of the protocol stack, while the processors of application circuitry 804 can utilize data (e.g., packet data) received from these layers and further execute functions of the fourth layer (L4) (e.g., the transport communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, the third layer can include a radio resource control (RRC) layer, described in further detail below. As referred to herein, the second layer can include 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, the first layer can include a physical (PHY) layer of a UE / RAN node, described in further detail below.

[0088] Figure 9 Exemplary interfaces of baseband circuitry are shown, in accordance with some embodiments. As discussed above, baseband circuitry 804 of FIG. 2 can include processors 804A-804E and memory 804G utilized by the processors. Each of the processors 804A-804E can include a memory interface 904A-904E, respectively, to send / receive data to / from the memory 804G.

[0089] The baseband circuitry 804 can further include one or more interfaces to communicate with other circuitries / devices, such as a memory interface 912 (e.g., an interface to send / receive data to / from memory external to the baseband circuitry 804), an application circuitry interface 914 (e.g., an interface to send / receive data to / from the application circuitry 802 of FIG. 2), an RF circuitry interface 916 (e.g., an interface to send / receive data to / from RF circuitry 806 of FIG. 2), a wireless hardware connectivity interface 918 (e.g., an interface to send / receive data to / from Near Field Communication (NFC) components, Bluetooth® components (e.g., low power consumption), Wi- components and other communication components to send / receive data), and a power management interface 920 (e.g., an interface to send / receive power or control signals to / from the PMC 812).

[0090] In various aspects, the embodiments discussed herein can facilitate techniques for inter-cell BM (beam management) via LI (Layer 1) by 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 LI inter-cell BM via SSB (synchronization signal block). The second set of techniques discussed herein can facilitate LI inter-cell BM via synchronization CSI (channel state information)-RS (reference signal).

[0091] Embodiments 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.

[0092] Embodiment 1 is a user equipment (UE) device comprising: a processor (or processing circuitry) configured to perform operations comprising: receiving, from a base station (BS) associated with the UE device, a first downlink control information (DCI) for scheduling a first physical downlink shared channel (PDSCH), wherein the first DCI includes a non-numerical (NN) value of K1 for hybrid automatic repeat request (HARQ)-ACK feedback, wherein K1 indicates a time delay between a corresponding PDSCH and HARQ-ACK feedback associated with the corresponding PDSCH; receiving the first PDSCH received from the BS; determining a first priority level associated with the first PDSCH; determining K1 values and priority levels associated with one or more subsequent PDSCHs received from the BS until a selected PDSCH having a numerical K1 value and a same priority level as the first priority level is identified; and transmitting HARQ-ACK feedback associated with the first PDSCH using a physical uplink control channel (PUCCH) occasion or a physical uplink shared channel (PUSCH) occasion indicated by a second DCI scheduling the selected PDSCH having the same priority level.

[0093] Embodiment 2 is the UE device of embodiment 1, comprising subject matter, wherein the first DCI further includes information of the first priority level associated with the first PDSCH, and wherein the one or more processors are configured to determine the first priority level based on processing the first DCI.

[0094] Embodiment 3 is the UE device of embodiments 1-2, comprising or omitting elements, wherein the first priority level associated with the first PDSCH and the priority levels associated with the one or more subsequent PDSCHs are preconfigured and received at the UE via radio resource control (RRC) signaling from the BS.

[0095] Example 4 is a UE device including the subject matter of Examples 1-3, the UE device including or omitting elements, wherein the K1 value associated with the one or more subsequent PDSCHs is included as part of one or more subsequent DCIs respectively associated with the one or more subsequent PDSCHs, and wherein the one or more processors are configured to determine the K1 value associated with the one or more subsequent PDSCHs based on processing the one or more subsequent DCIs.

[0096] Example 5 is a UE device including the subject matter of Examples 1-4, the UE device including or omitting elements, wherein the one or more subsequent DCIs further include information of a priority level associated with the one or more subsequent PDSCHs, and wherein the one or more processors are configured to determine the priority level associated with the one or more subsequent PDSCHs based on processing the one or more subsequent DCIs.

[0097] Example 6 is a base station that includes a processor (or processing circuitry) configured to perform operations comprising: transmitting, to a user equipment (UE) associated with the base station, a first downlink control information (DCI) for scheduling a first physical downlink shared channel (PDSCH), the first PDSCH having a first priority level associated therewith, wherein the first DCI includes a non-numerical (NN) value of K1 for hybrid automatic repeat request (HARQ)-ACK feedback, wherein K1 indicates a time delay between a corresponding PDSCH and HARQ-ACK feedback associated with the corresponding PDSCH; transmitting, to the UE, the first PDSCH; transmitting, to the UE, one or more subsequent PDSCHs, wherein one PDSCH of the one or more subsequent PDSCHs includes a numerical K1 value for HARQ-ACK feedback and a priority level that is the same as the first priority level associated with the first PDSCH; and receiving, from the UE, HARQ-ACK feedback associated with the first PDSCH, wherein the HARQ-ACK feedback associated with the first PDSCH is received on a physical uplink control channel (PUCCH) occasion or a physical uplink shared channel (PUSCH) occasion indicated by a second DCI scheduling the one PDSCH having the same priority level.

[0098] Example 7 is the base station of Example 6, wherein the first DCI further includes information of the first priority level associated with the first PDSCH.

[0099] Example 8 is a base station including the subject matter of Examples 6-7, the base station including or omitting elements, wherein the one or more processors are configured to provide, to the UE via radio resource control (RRC) signaling, the first priority level associated with the first PDSCH and priority levels associated with one or more subsequent PDSCHs.

[0100] Example 9 is a method for a user equipment (UE) associated with a wireless communication system, the method comprising: receiving, using one or more processors, first downlink control information (DCI) for scheduling a first physical downlink shared channel (PDSCH) from a base station (BS) associated with the UE device, wherein the first DCI includes a non-numerical (NN) value of K1 for hybrid automatic repeat request (HARQ)-ACK feedback, wherein K1 indicates a time delay between a corresponding PDSCH and HARQ-ACK feedback associated with the corresponding PDSCH; receiving, using the one or more processors, the first PDSCH received from the BS; determining, using the one or more processors, a first priority level associated with the first PDSCH; determining, using the one or more processors, K1 values and priority levels associated with one or more subsequent PDSCHs received from the BS until a selected PDSCH with a numerical K1 value and a same priority level as the first priority level is identified; and transmitting, using the one or more processors, HARQ-ACK feedback associated with the first PDSCH using a physical uplink control channel (PUCCH) occasion or a physical uplink shared channel (PUSCH) occasion indicated by a second DCI scheduling the selected PDSCH with the same priority level.

[0101] Example 10 is the method including the subject matter of Example 9, wherein the first DCI further includes information of the first priority level associated with the first PDSCH, and wherein the one or more processors are configured to determine the first priority level based on processing the first DCI.

[0102] Example 11 is the method including the subject matter of Examples 9-10, the method including or omitting elements, wherein the first priority level associated with the first PDSCH and priority levels associated with the one or more subsequent PDSCHs are preconfigured and received at the UE via radio resource control (RRC) signaling from the BS.

[0103] Example 12 is a method including the subject matter of Examples 9-11, the method including or omitting elements, wherein the K1 value associated with the one or more subsequent PDSCHs is included as part of one or more subsequent DCIs respectively associated with the one or more subsequent PDSCHs, and wherein the one or more processors are configured to determine the K1 value associated with the one or more subsequent PDSCHs based on processing the one or more subsequent DCIs.

[0104] Example 13 is a method including the subject matter of Examples 9-12, the method including or omitting elements, wherein the one or more subsequent DCIs further include information of a priority level associated with the one or more subsequent PDSCHs, and wherein the one or more processors are configured to determine the priority level associated with the one or more subsequent PDSCHs based on processing the one or more subsequent DCIs.

[0105] Example 14 is a method for a base station (BS) associated with a wireless communication system, the method comprising: transmitting, using one or more processors, a first downlink control information (DCI) to a user equipment (UE) associated with the base station for scheduling a first physical downlink shared channel (PDSCH), the first PDSCH having a first priority level associated therewith, wherein the first DCI includes a non-numerical (NN) value of K1 for hybrid automatic repeat request (HARQ)-ACK feedback, wherein K1 indicates a time delay between a corresponding PDSCH and HARQ-ACK feedback associated with the corresponding PDSCH; transmitting, using the one or more processors, the first PDSCH to the UE; transmitting, using the one or more processors, one or more subsequent PDSCHs to the UE, wherein one PDSCH of the one or more subsequent PDSCHs includes a numerical K1 value for HARQ-ACK feedback and a priority level that is the same as the first priority level associated with the first PDSCH; and receiving, using the one or more processors, HARQ-ACK feedback associated with the first PDSCH from the UE, wherein the HARQ-ACK feedback associated with the first PDSCH is received on a physical uplink control channel (PUCCH) occasion or a physical uplink shared channel (PUSCH) occasion indicated by a second DCI scheduling the one PDSCH having the same priority level.

[0106] Example 15 is a method including the subject matter of Example 14, wherein the first DCI further includes information of the first priority level associated with the first PDSCH.

[0107] Example 16 is a method including the subject matter of Examples 14-15, the method including or omitting elements, wherein the first priority level associated with the first PDSCH and the priority levels associated with the one or more subsequent PDSCHs are signaled to the UE via radio resource control (RRC) signaling.

[0108] Example 17 is a baseband (BB) processor for a user equipment (UE) configured to perform operations, the operations comprising: receiving, from a base station (BS) associated with the UE device, a first downlink control information (DCI) for scheduling a first physical downlink shared channel (PDSCH), wherein the first DCI includes a non-numerical (NN) value of K1 for hybrid automatic repeat request (HARQ)-ACK feedback, wherein K1 indicates a time delay between a corresponding PDSCH and HARQ-ACK feedback associated with the corresponding PDSCH; receiving the first PDSCH received from the BS; determining a first priority level associated with the first PDSCH; determining K1 values and priority levels associated with one or more subsequent PDSCHs received from the BS until a selected PDSCH with a numerical K1 value and a same priority level as the first priority level is identified; and transmitting HARQ-ACK feedback associated with the first PDSCH using a physical uplink control channel (PUCCH) occasion or a physical uplink shared channel (PUSCH) occasion indicated by a second DCI scheduling the selected PDSCH with the same priority level.

[0109] Example 18 is the BB processor of Example 17, wherein the first DCI further includes information of the first priority level associated with the first PDSCH, and wherein the one or more processors are configured to determine the first priority level based on processing the first DCI.

[0110] Example 19 is the BB processor of Examples 17-18, the BB processor including or omitting elements, wherein the first priority level associated with the first PDSCH and the priority levels associated with the one or more subsequent PDSCHs are preconfigured and received at the UE via radio resource control (RRC) signaling from the BS.

[0111] Example 20 is a BB processor including the subject matter of Examples 17-19, the BB processor including or omitting elements, wherein the K1 value associated with the one or more subsequent PDSCHs is included as part of one or more subsequent DCIs respectively associated with the one or more subsequent PDSCHs, and wherein the one or more processors are configured to determine the K1 value associated with the one or more subsequent PDSCHs based on processing the one or more subsequent DCIs.

[0112] Example 21 is a BB processor including the subject matter of Examples 17-20, the BB processor including or omitting elements, wherein the one or more subsequent DCIs further include information of a priority level associated with the one or more subsequent PDSCHs, and wherein the one or more processors are configured to determine the priority level associated with the one or more subsequent PDSCHs based on processing the one or more subsequent DCIs.

[0113] Example 22 is a baseband (BB) processor for a base station, the BB processor configured to perform operations comprising: transmitting, to a user equipment (UE) associated with the base station, a first downlink control information (DCI) for scheduling a first physical downlink shared channel (PDSCH), the first PDSCH having a first priority level associated therewith, wherein the first DCI includes a non-numerical (NN) value of K1 for hybrid automatic repeat request (HARQ)-ACK feedback, wherein K1 indicates a time delay between a corresponding PDSCH and HARQ-ACK feedback associated with the corresponding PDSCH; transmitting, to the UE, the first PDSCH; transmitting, to the UE, one or more subsequent PDSCHs, wherein one PDSCH of the one or more subsequent PDSCHs includes a numerical K1 value for HARQ-ACK feedback and a priority level that is the same as the first priority level associated with the first PDSCH; and receiving, from the UE, HARQ-ACK feedback associated with the first PDSCH, wherein the HARQ-ACK feedback associated with the first PDSCH is received on a physical uplink control channel (PUCCH) occasion or a physical uplink shared channel (PUSCH) occasion indicated by a second DCI scheduling the one PDSCH having the same priority level.

[0114] Example 23 is the BB processor of Example 22, wherein the first DCI further includes information of the first priority level associated with the first PDSCH.

[0115] Example 24 is a BB processor including the subject matter of Examples 22-23, the BB processor including or omitting elements, wherein the one or more processors are configured to transmit, to the UE via radio resource control (RRC) signaling, the first priority level associated with the first PDSCH and priority levels associated with the one or more subsequent PDSCHs.

[0116] While the present application has been illustrated and described with respect to one or more particular embodiments, various modifications and changes can be made in the illustrated embodiments without departing from the spirit and scope of the appended claims. In particular, with respect to the various functions described above with regard to the components or structures (assemblies, devices, circuits, systems, etc.) described above, unless otherwise specified, terms describing such components (including references to “means”) are intended to refer to any components or structure which performs the specified function of the component (e.g., that is functionally equivalent), even if the structure is not structurally identical to the disclosed structure of the example implementations of the application shown herein.

[0117] The above description of example implementations of the present subject matter, including that in the Summary, is not intended to be exhaustive or to limit the disclosed implementations to the precise forms disclosed. While specific implementations and examples are described herein for illustrative purposes, various modifications are possible within the scope of such implementations and examples as those skilled in the relevant art will recognize.

Claims

1. A user equipment (UE) device, the UE device comprising: a processor configured to perform operations comprising: receiving a first downlink control information, DCI, including an inapplicable value of a timing indicator of hybrid automatic repeat request, HARQ-ACK, feedback associated with a first physical downlink shared channel, PDSCH, wherein the timing indicator indicates a time delay between a corresponding PDSCH and the HARQ-ACK feedback associated with the corresponding PDSCH; receiving, via the first DCI, a first priority level associated with the first PDSCH; determining timing indicators and priority levels associated with a second PDSCH and a third PDSCH of at least two subsequent PDSCHs, wherein the second PDSCH is scheduled between the first PDSCH and the third PDSCH, wherein the third PDSCH has an applicable timing indicator value and a same priority level as the first priority level, wherein the second PDSCH has an inapplicable value of a timing indicator or a different priority level from the first priority level or both, and wherein the HARQ-ACK feedback associated with the first PDSCH is held until the third PDSCH is identified; and multiplexing the HARQ-ACK feedback associated with the first PDSCH and scheduled HARQ-ACK feedback associated with the third PDSCH without multiplexing HARQ-ACK feedback associated with the second PDSCH.

2. The UE device of claim 1, wherein the multiplexed HARQ-ACK feedback is scheduled and transmitted using a physical uplink control channel, PUCCH, occasion or a physical uplink shared channel, PUSCH, occasion determined based on the applicable timing indicator value associated with the third PDSCH.

3. The UE device of claim 1, wherein the timing indicator values associated with the at least two subsequent PDSCHs are included as part of at least two subsequent DCIs respectively associated with the at least two subsequent PDSCHs, and wherein the processor is configured to determine the timing indicator values associated with the at least two subsequent PDSCHs based on processing the at least two subsequent DCIs.

4. The UE device of claim 3, wherein the at least two subsequent DCIs further include information of the priority levels associated with the at least two subsequent PDSCHs, and wherein the processor is configured to determine the priority levels associated with the at least two subsequent PDSCHs based on processing the at least two subsequent DCIs.

5. A base station comprising a processor configured to perform operations comprising: sending, via a first downlink control information, DCI, and / or a radio resource control, RRC, message, an inapplicable value of a timing indicator associated with a hybrid automatic repeat request, HARQ-ACK, feedback for a first physical downlink shared channel, PDSCH, wherein the timing indicator indicates a time delay between a corresponding PDSCH and the HARQ-ACK feedback associated with the corresponding PDSCH; sending a second PDSCH and a third PDSCH of at least two subsequent PDSCHs, wherein the second PDSCH is scheduled between the first PDSCH and the third PDSCH, wherein the third PDSCH has an applicable timing indicator value for HARQ-ACK feedback and a priority level that is the same as a first priority level associated with the first PDSCH, wherein the second PDSCH has an inapplicable value of a timing indicator or a priority level that is different from the first priority level, or both; and receiving the HARQ-ACK feedback associated with the first PDSCH, wherein the HARQ-ACK feedback associated with the first PDSCH is multiplexed with scheduled HARQ-ACK feedback associated with the third PDSCH, without multiplexing HARQ-ACK feedback associated with the second PDSCH.

6. The base station of claim 5, wherein the processor is configured to schedule and transmit the multiplexed HARQ-ACK feedback using a physical uplink control channel, PUCCH, occasion or a physical uplink shared channel, PUSCH, occasion determined based on the applicable timing indicator value associated with the third PDSCH.

7. A method for a user equipment, UE, associated with a wireless communication system, the method comprising: receiving a first downlink control information, DCI, including an inapplicable value of a timing indicator associated with a hybrid automatic repeat request, HARQ-ACK, feedback for a first physical downlink shared channel, PDSCH, wherein the timing indicator indicates a time delay between a corresponding PDSCH and the HARQ-ACK feedback associated with the corresponding PDSCH; receiving, via the first DCI and / or a radio resource control, RRC, message, a first priority level associated with the first PDSCH; determining a timing indicator and a priority level associated with a second PDSCH and a third PDSCH of at least two subsequent PDSCHs, wherein the second PDSCH is scheduled between the first PDSCH and the third PDSCH, wherein the third PDSCH has an applicable timing indicator value and a priority level that is the same as the first priority level, wherein the second PDSCH has an inapplicable value of a timing indicator or a priority level that is different from the first priority level, or both, and wherein the HARQ-ACK feedback associated with the first PDSCH is held until the third PDSCH is identified; and receiving the HARQ-ACK feedback associated with the first PDSCH, wherein the HARQ-ACK feedback associated with the first PDSCH is multiplexed with scheduled HARQ-ACK feedback associated with the third PDSCH, without multiplexing HARQ-ACK feedback associated with the second PDSCH. multiplexing HARQ-ACK feedback associated with the first PDSCH and scheduled HARQ-ACK feedback associated with the third PDSCH without multiplexing HARQ-ACK feedback associated with the second PDSCH.

8. The method of claim 7, wherein the multiplexed HARQ-ACK feedback is scheduled and transmitted using a physical uplink control channel (PUCCH) occasion or a physical uplink shared channel (PUSCH) occasion determined based on the applicable timing indicator value associated with the third PDSCH.

9. The method of claim 7, wherein the timing indicator values associated with the at least two subsequent PDSCHs are included as part of at least two subsequent DCIs respectively associated with the at least two subsequent PDSCHs, and wherein the one or more processors are configured to determine the timing indicator values associated with the at least two subsequent PDSCHs based on processing the at least two subsequent DCIs.

10. The method of claim 9, wherein the at least two subsequent DCIs further include information of the priority levels associated with the at least two subsequent PDSCHs, and wherein the one or more processors are configured to determine the priority levels associated with the at least two subsequent PDSCHs based on processing the at least two subsequent DCIs.

11. A method for a base station (BS) associated with a wireless communication system, the method comprising: sending, via a first downlink control information (DCI) and / or a radio resource control (RRC) message, an inapplicable value of a timing indicator of a hybrid automatic repeat request (HARQ)-ACK feedback associated with a first physical downlink shared channel (PDSCH), wherein the timing indicator indicates a time delay between a corresponding PDSCH and the HARQ-ACK feedback associated with the corresponding PDSCH; sending, using one or more processors, a second PDSCH and a third PDSCH of at least two subsequent PDSCHs, wherein the second PDSCH is scheduled between the first PDSCH and the third PDSCH, wherein the third PDSCH has an applicable timing indicator value for HARQ-ACK feedback and a same priority level as a first priority level associated with the first PDSCH, wherein the second PDSCH has an inapplicable value of a timing indicator or a different priority level from the first priority level or both; and receiving, using the one or more processors, HARQ-ACK feedback associated with the first PDSCH, wherein the HARQ-ACK feedback associated with the first PDSCH and scheduled HARQ-ACK feedback associated with the third PDSCH are multiplexed without multiplexing HARQ-ACK feedback associated with the second PDSCH.

12. The method of claim 11, further comprising scheduling and transmitting multiplexed HARQ-ACK feedback using a physical uplink control channel (PUCCH) occasion or a physical uplink shared channel (PUSCH) occasion determined based on the applicable timing indicator value associated with the third PDSCH.

13. A baseband (BB) processor for a user equipment (UE), the BB processor configured to perform operations comprising: receiving a first downlink control information (DCI) comprising an inapplicable value of a timing indicator for hybrid automatic repeat request (HARQ)-ACK feedback associated with a first physical downlink shared channel (PDSCH), wherein the timing indicator indicates a time delay between a corresponding PDSCH and HARQ-ACK feedback associated with the corresponding PDSCH; determining a first priority level, wherein the first priority level is received via the first DCI and / or a radio resource control (RRC) message; determining timing indicators and priority levels associated with a second PDSCH and a third PDSCH of at least two subsequent PDSCHs, wherein the second PDSCH is scheduled between the first PDSCH and the third PDSCH, wherein the third PDSCH has an applicable timing indicator value and a same priority level as the first priority level, wherein the second PDSCH has an inapplicable value of a timing indicator or a different priority level from the first priority level or both, and wherein HARQ-ACK feedback associated with the first PDSCH is held until the third PDSCH is identified; and multiplexing HARQ-ACK feedback associated with the first PDSCH and scheduled HARQ-ACK feedback associated with the third PDSCH without multiplexing HARQ-ACK feedback associated with the second PDSCH.

14. The BB processor of claim 13, wherein the BB processor is configured to determine the first priority level based on processing the first DCI.

15. The BB processor of claim 13, wherein the multiplexed HARQ-ACK feedback is scheduled and transmitted using a physical uplink control channel (PUCCH) occasion or a physical uplink shared channel (PUSCH) occasion determined based on the applicable timing indicator value associated with the third PDSCH.

16. The BB processor of claim 13, wherein the timing indicator values associated with the at least two subsequent PDSCHs are included as part of at least two subsequent DCIs respectively associated with the at least two subsequent PDSCHs, and wherein the BB processor is configured to determine the timing indicator values associated with the at least two subsequent PDSCHs based on processing the at least two subsequent DCIs.

17. The BB processor of claim 16, wherein the at least two subsequent DCIs further comprise information of the priority level associated with the at least two subsequent PDSCHs, and wherein the BB processor is configured to determine the priority level associated with the at least two subsequent PDSCHs based on processing the at least two subsequent DCIs.

18. A baseband (BB) processor for a base station, the BB processor configured to perform operations comprising: transmitting a first downlink control information (DCI) to schedule a first physical downlink shared channel (PDSCH), the first DCI comprising an inapplicable value of a timing indicator of hybrid automatic repeat request (HARQ)-ACK feedback associated with the first PDSCH, wherein the timing indicator indicates a time delay between a corresponding PDSCH and the HARQ-ACK feedback associated with the corresponding PDSCH; transmitting at least two subsequent PDSCHs to a UE, wherein the second PDSCH is scheduled between the first PDSCH and the third PDSCH, and wherein the third PDSCH has an applicable timing indicator value for HARQ-ACK feedback and a same priority level as a first priority level associated with the first PDSCH, wherein the second PDSCH has an inapplicable value of a timing indicator or a different priority level than the first priority level, or both; and receiving, from the UE, HARQ-ACK feedback associated with the first PDSCH, wherein the HARQ-ACK feedback associated with the first PDSCH and scheduled HARQ-ACK feedback associated with the third PDSCH are multiplexed without multiplexing HARQ-ACK feedback associated with the second PDSCH.

19. The BB processor of claim 18, wherein the operations further comprise: scheduling and conveying the multiplexed HARQ-ACK feedback using a physical uplink control channel (PUCCH) occasion or a physical uplink shared channel (PUSCH) occasion determined based on the applicable timing indicator value associated with the third PDSCH. transmitting a first downlink control information (DCI) to schedule a first physical downlink shared channel (PDSCH), the first DCI comprising an inapplicable value of a timing indicator of hybrid automatic repeat request (HARQ)-ACK feedback associated with the first PDSCH, wherein the timing indicator indicates a time delay between a corresponding PDSCH and the HARQ-ACK feedback associated with the corresponding PDSCH; transmitting at least two subsequent PDSCHs to a UE, wherein the second PDSCH is scheduled between the first PDSCH and the third PDSCH, and wherein the third PDSCH has an applicable timing indicator value for HARQ-ACK feedback and a same priority level as a first priority level associated with the first PDSCH, wherein the second PDSCH has an inapplicable value of a timing indicator or a different priority level than the first priority level, or both; and receiving, from the UE, HARQ-ACK feedback associated with the first PDSCH, wherein the HARQ-ACK feedback associated with the first PDSCH and scheduled HARQ-ACK feedback associated with the third PDSCH are multiplexed without multiplexing HARQ-ACK feedback associated with the second PDSCH. scheduling and conveying the multiplexed HARQ-ACK feedback using a physical uplink control channel (PUCCH) occasion or a physical uplink shared channel (PUSCH) occasion determined based on the applicable timing indicator value associated with the third PDSCH.

Images