Technique for managing discontinuous receive timers - Patents.com

Abstract

The present application relates to devices and components, including apparatus, systems, and methods for techniques for managing discontinuous reception timers in wireless networks.

Description

[Background technology]

[0001] The Third Generation Partnership Project (3GPP) Technical Specifications (TS) define standards for New Radio (NR) wireless networks. One area of ​​research for developing these TSs is managing discontinuous reception (DRX) timers. [Brief explanation of the drawings]

[0002] [Figure 1] 1 illustrates a network environment according to some embodiments.

[0003] [Figure 2] 1 illustrates a postponement operation according to some embodiments.

[0004] [Figure 3] 1 illustrates a cell switching operation according to some embodiments.

[0005] [Figure 4] 1 illustrates a signaling diagram according to some embodiments.

[0006] [Figure 5] 1 illustrates codebook retransmission according to some embodiments.

[0007] [Figure 6] 1 illustrates a codebook according to some embodiments.

[0008] [Figure 7] 1 illustrates another codebook according to some embodiments.

[0009] [Figure 8] 1 illustrates another signaling diagram according to some embodiments.

[0010] [Figure 9] 1 illustrates an operational flow / algorithm structure according to some embodiments.

[0011] [Figure 10] 1 illustrates another operational flow / algorithm structure according to some embodiments.

[0012] [Figure 11] 1 illustrates another operational flow / algorithm structure according to some embodiments.

[0013] [Figure 12] 1 illustrates another operational flow / algorithm structure according to some embodiments.

[0014] [Figure 13] 1 illustrates another operational flow / algorithm structure according to some embodiments.

[0015] [Figure 14] 1 illustrates a user equipment according to some embodiments.

[0016] [Figure 15] 1 illustrates a network node according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0017] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details of particular structures, architectures, interfaces, and techniques are set forth in order to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to one skilled in the art having the benefit of this disclosure that various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In some instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For purposes of this document, the phrases "A / B" and "A or B" mean (A), (B), or (A and B).

[0018] The following is a glossary of terms that may be used in this disclosure.

[0019] As used herein, the term "circuitry" refers to, is a part of, or includes a hardware component configured to provide a described functionality. The hardware component may include electronic circuitry, logic circuitry, processors (shared, dedicated, or group), or memory (shared, dedicated, or group), application-specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-volume PLDs (HCPLDs), structured ASICs, programmable systems-on-chips (SoCs)), or digital signal processors (DSPs). In some embodiments, a circuit may execute one or more software or firmware programs to provide at least a portion of the described functionality. The term "circuitry" may also refer to the combination of one or more hardware elements (or a combination of circuitry used in an electrical or electronic system) with program code used to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0020] As used herein, the term "processor circuitry" refers to, is a part of, or includes circuitry capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transferring digital data. The term "processor circuitry" may refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions such as program code, software modules, or functional processes.

[0021] As used herein, the term "interface circuitry" refers to, is a part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, and a network interface card.

[0022] As used herein, the term "user equipment" or "UE" refers to a device with wireless communication capabilities that may enable a user to access network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, or reconfigurable mobile device. Furthermore, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0023] As used herein, the term "computer system" refers to any type of interconnected electronic device, computing device, or component thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computing devices or multiple computing systems that are communicatively coupled to each other and configured to share computing or networking resources.

[0024] As used herein, the term “resource” refers to a physical or virtual device, a physical or virtual component in a computing environment, or a physical or virtual component within a particular device, such as a computer device, a mechanical device, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, networks, databases and applications, or workload units. “Hardware resources” may refer to computational, storage, or network resources provided by physical hardware elements. “Virtualized resources” may refer to computational, storage, or network resources provided to an application, device, or system by a virtualization infrastructure. The terms “network resources” or “communication resources” may refer to resources accessible by a computer device / system via a communication network. The term “system resource” may refer to any kind of shared entity for providing services and may include computing resources or network resources. A system resource may be considered a set of coherent functions, network data objects, or services, whether such system resources reside on a single host or multiple hosts and are accessible through a clearly identifiable server.

[0025] As used herein, the term "channel" refers to any tangible or intangible transmission medium used to communicate data or data streams. The term "channel" may be synonymous with or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a path or medium over which data is communicated. Additionally, as used herein, the term "link" refers to a connection between two devices for the purpose of transmitting and receiving information.

[0026] As used herein, the terms "instantiate," "instantiation," and the like refer to the creation of an instance. An "instance" also refers to a specific occurrence of an object that may occur, for example, during the execution of program code.

[0027] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other via a communication channel, link, interface, or reference point.

[0028] As used herein, the term "network element" refers to a physical or virtualized device or infrastructure used to provide wired or wireless communications network services. The term "network element" may be considered or referred to as synonymous with networked computer, networking hardware, network equipment, network node, or virtualized network function.

[0029] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to an information element or an individual piece of content in a data element that contains content. An information element may contain one or more further information elements.

[0030] 1 illustrates a network environment 100 according to some embodiments. The network environment 100 may include a user equipment (UE) 104 communicatively coupled to a base station 108. The UE 104 and the base station 108 may communicate over an air interface compliant with 3GPP TS, such as that defining a Fifth Generation (5G) NR system standard. The base station 108 may be a gNB for providing one or more 5G New Radio (NR) cells, offering NR user plane and control plane protocol terminations towards the UE 104.

[0031] The UE 104 may be configured for discontinuous reception (DRX) operation, which allows the UE 104 to transition to low power operation during times when no signals are expected to be received from the base station 108. Some of these times may occur in connection with hybrid automatic repeat request (HARQ) operation.

[0032] 1 includes a simple signaling flow to illustrate DRX / HARQ operation according to some embodiments. At 112, the base station 108 may send a downlink transmission to the UE 104. The UE 104 may generate HARQ feedback based on an attempt to receive the downlink transmission. If the downlink transmission is properly received and decoded, the HARQ feedback may include a HARQ positive acknowledgement (ACK). If the downlink transmission is not properly received or decoded, the HARQ feedback may include a HARQ negative acknowledgement (NACK). At 116, the UE 104 may send the HARQ feedback to the base station 108. If the base station 108 receives a HARQ NACK, the base station 108 may send a downlink retransmission at 120.

[0033] The HARQ feedback may include one logical bit per transport block. The UE 104 may support multiple HARQ processes (e.g., up to 16 per component carrier), with separate feedback provided for each HARQ process. The HARQ-ACK codebook may be a sequence of bits constructed using the ACK / NACK feedback corresponding to multiple PDSCH reception attempts during a configured time window.

[0034] 3GPP Release 16 provides three types of HARQ-ACK codebooks: A Type 1 codebook may be a fixed-size codebook semi-statically configured by the base station 108 via radio resource control (RRC) signaling; a Type 2 codebook may have a dynamic size that varies with resource allocation; a Type 3 codebook may contain feedback for all HARQ processes and all configured cells; the base station 108 may request the Type 3 codebook using a one-shot trigger; Release 17 introduced an extended Type 3 codebook (e-Type 3) that leverages the design of the Type 3 codebook but reduces the feedback overhead; the e-Type 3 codebook is described in more detail elsewhere herein.

[0035] Type 1 and Type 2 codebooks may be supported for both licensed and unlicensed spectrum, and Type 3 codebooks may be applicable to NR-Unlicensed (NR-U).

[0036] 1, there may be periods during which the UE 104 does not expect to receive a transmission and other periods during which the UE 104 expects to receive a transmission. The UE 104 may utilize a DRX HARQ timer to track these periods and act accordingly.

[0037] The two DRX HARQ timers include a DRX HARQ round trip time (RTT) timer for the downlink (drx-HAR-RTT-TimerDL) and a DRX retransmission timer for the downlink (drx-RetransmissionTimerDL). The drx-HAR-RTT-TimerDL timer may also be referred to herein simply as the "RTT timer," and the drx-RetransmissionTimerDL may also be referred to herein simply as the "retransmission timer."

[0038] The RTT timer may provide a minimum duration before a downlink allocation for HARQ retransmission is expected by the medium access control (MAC) entity of the UE 104. One RTT timer may be configured per downlink HARQ process excluding the broadcast process. The retransmission timer may provide a maximum duration until a downlink retransmission is received. The retransmission timer may normally start when the RTT timer expires. One retransmission timer may be configured per downlink HARQ process excluding the broadcast process.

[0039] For example, referring to FIG. 1, the UE 104 may start an RTT timer after transmitting the HARQ feedback 116. The UE 104 may enter a sleep mode when the RTT timer is running for the HARQ process and retransmission timers for other HARQ processes are not running. When the RTT timer expires, the UE 104 may power up the receive chain circuitry and start the retransmission timer for the HARQ process. While the retransmission timer is running, the UE 104 may monitor 120 the physical downlink control channel (PDCCH) in an attempt to decode scheduling information for downlink retransmissions.

[0040] In some embodiments, the base station 108 may manage the RTT and retransmission timers in a similar manner as the UE 104. The timers at the base station 108 may be synchronized with the timers at the UE 104. In this manner, the base station 108 can track or identify periods during which the UE 104 can receive a PDCCH, etc.

[0041] DRX operation regarding timers is described in section 5.7 of 3GPP TS 38.321 v16.7.0(2021-12) as follows: If DRX is configured, the MAC entity: 1> If a MAC PDU is received in the configured downlink allocation, 2>Starting the drx-HARQ-RTT-TimerDL of the corresponding HARQ process at the first symbol after the end of the corresponding transmission carrying DL HARQ feedback; 2> Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0042] 3GPP Release 17 provides several Layer 1 (L1) features designed to enhance HARQ feedback. These features include semi-persistent scheduling (SPS), PDSCH HARQ deferral, PUCCH cell switching, HARQ-ACK codebook retransmission, one-shot HARQ-ACK request, and enhanced Type 3 HARQ-ACK codebook reporting. These features may be used independently or in conjunction with one or more other features. Some embodiments describe simultaneous configurations for some of these features, although other independent / simultaneous configurations may also be used.

[0043] Embodiments describe extensions / updates to DRX HARQ timers that may be used in conjunction with one or more of these L1 features to help reduce power consumption, increase efficient utilization of system resources, and reduce latency. Many of the embodiments are described with respect to Release 17 features, although some embodiments may also be applicable to Release 16 features.

[0044] SPS HARQ-ACK deferral may address the situation where a PUCCH carrying SPS HARQ feedback is dropped due to a conflict with downlink symbols on a TDD carrier. This may occur when the SPS periodicity does not match the periodicity of the downlink / uplink partition, which may necessarily result in some opportunities for the PUCCH carrying SPS HARQ feedback to at least partially overlap with downlink symbols.

[0045] 2 illustrates an SPS HARQ-ACK postponement operation 200 according to some embodiments. The operation 200 may include the UE 104 attempting to receive a DL SPS PDSCH 204. The UE 104 may then identify a first PUCCH resource (PUCCH 1) 208 of the initial slot / subslot that carries SPS HARQ feedback indicating whether the DL SPS PDSCH was properly received. PUCCH 1 208 may be indicated by SPS-PUCCH-AN-list or n1PUCCH-AN. However, in this case, PUCCH 1 208 may not be valid due to a conflict with the DL symbol 212. Therefore, the UE 104 may postpone transmitting the SPS HARQ feedback on the second PUCCH resource (PUCCH 2) 216. In some embodiments, the delayed SPS HARQ-ACK bit may be appended to the non-delayed HARQ bit in PUCCH 2 216.

[0046] SPS HARQ ACK deferral may help avoid dropping SPS HARQ-ACK on TDD carriers, which may improve system capacity and power consumption by the UE 104.

[0047] SPS HARQ ACK deferral may be triggered after UCI multiplexing in some cases and may be largely transparent to the MAC entity. SPS HARQ ACK deferral may be applied to Type 1 or Type 2 HARQ-ACK codebooks.

[0048] As indicated above, when an SPS HARQ ACK is postponed, the corresponding HARQ-ACK may occur in the PUCCH on a later slot / subslot. This can be clarified by providing an annotation to provide additional context to clarify the MAC entity's behavior with respect to the DRX HARQ timer. In some embodiments, the annotation can be provided by adding underlined text to clause 5.7 of 3GPP TS 38.321 v16.7.0(2021-12) as follows: If DRX is configured, the MAC entity: 1> If a MAC PDU is received in the configured downlink allocation, 2>Starting the drx-HARQ-RTT-TimerDL of the corresponding HARQ process at the first symbol after the end of the corresponding transmission carrying DL HARQ feedback; 2> Stop the drx-RetransmissionTimerDL of the corresponding HARQ process. Note X: If the HARQ feedback is subject to SPS HARQ-ACK deferral as specified in TS 38.213 v17.0.0(2021-12), the corresponding transmission carrying the DL HARQ feedback occurs in the PUCCH resource together with the PUCCH transmission in a later slot.

[0049] 3 illustrates a PUCCH cell switching operation 300 according to some embodiments. PUCCH cell switching may be used to reduce HARQ feedback latency for inter-band time division duplexing (TDD). In this embodiment, two component carriers (CC1 and CC2) may be configured with different uplink / downlink TDD configurations. CC1 may be a primary serving cell (PCell) in band Y, and CC2 may be a secondary serving cell (SCell) in band Z.

[0050] Restricting HARQ feedback to the same carrier as its corresponding downlink transmission may result in unnecessarily long uplink control information (UCI) or HARQ feedback latency. For example, in CC1, HARQ feedback corresponding to a downlink transmission in the first slot may not be transmitted until the PUCCH of the uplink slot four slots later. PUCCH cell switching may allow HARQ feedback corresponding to a downlink transmission in CC1 to be transmitted earlier in the PUCCH in CC2. As shown, the PUCCH may be transmitted two slots after the downlink transmission.

[0051] PUCCH cell switching, sometimes referred to as PUCCH carrier switching, can be configured in a semi-static or dynamic manner. Typically, only one of semi-static (periodic) PUCCH carrier switching or dynamic PUCCH carrier switching is configured at a given time. PUCCH carrier switching can be enabled between two TDD cells with PUCCH configured on the normal uplink (NUL) carrier.

[0052] Semi-static (periodic) PUCCH carrier switching operation may be based on the RRC-configured PUCCH cell timing pattern of the applicable PUCCH cell. Semi-static PUCCH carrier switching may support switching across cells with different numerologies. Semi-static PUCCH cell switching may be applicable to all UCI types, including HARQ-ACK, scheduling request (SR), and channel state information (CSI). Semi-static PUCCH cell switching may be configured in conjunction with SPS HARQ-ACK deferral (e.g., for downlink SPS). Semi-static PUCCH cell switching may also be applied in combination with HARQ-ACK codebook type 1, 2, or 3, including, for example, HARQ-ACK retransmission and use of a type 3 HARQ-ACK codebook.

[0053] Dynamic PUCCH carrier switching may be based on a dynamic indication in the DCI format that schedules the PUCCH. This type of PUCCH carrier switching may be applicable only to HARQ-ACK. Dynamic PUCCH cell switching can be combined with HARQ-ACK codebook type 1, 2, or 3.

[0054] DCI format 1_1 / 1_2 may include a PUCCH cell indicator that provides a dynamic PUCCH target carrier indication. The indication may apply to: a HARQ-ACK for a PDSCH dynamically scheduled by the DCI, a HARQ-ACK corresponding to the first SPS PDSCH activated by the activation DCI based on an indication in the activation DCI, a HARQ-ACK corresponding to an SPS release DCI based on an indication in the release DCI, a HARQ-ACK corresponding to an SCell dormancy indication that does not schedule a PDSCH, a Release 16 Type 3 HARQ-ACK codebook (e.g., one-shot HARQ-ACK request), a Release 17 enhanced Type 3 HARQ-ACK codebook, or a Release 17 HARQ-ACK codebook retransmission based on an indication in the triggering DCI.

[0055] If PUCCH cell switching is applied, the corresponding HARQ-ACK occurs on a different PUCCH carrier. Apart from the RRC configuration, the PUCCH cell switching may be transparent to the MAC entity.

[0056] The operation of the DRX timer may be clarified to accommodate PUCCH cell switching according to some embodiments. The clarifications may be structured into different annotations. A first annotation, annotation Y, may be for configured downlink allocation / SPS HARQ-ACK deferral configured simultaneously with semi-static PUCCH cell switching. A second annotation, annotation X, may be for the case where PDCCH is monitored. In some embodiments, these annotations may be provided by adding underlined text to clause 5.7 of 3GPP TS 38.321, as follows: If DRX is configured, the MAC entity: 1> If a MAC PDU is received in the configured downlink allocation, 2>Starting the drx-HARQ-RTT-TimerDL of the corresponding HARQ process at the first symbol after the end of the corresponding transmission carrying DL HARQ feedback; 2> Stop the drx-RetransmissionTimerDL of the corresponding HARQ process. Note Y: If the UE is configured with a periodic cell switching pattern for PUCCH transmissions as specified in 3GPP TS 38.213, the corresponding transmission carrying DL HARQ feedback may occur on a different PUCCH cell. Note Z: When PUCCH cell switching is configured as specified in TS 38.213, the corresponding transmission carrying DL HARQ feedback may occur on a different PUCCH cell.

[0057] In some instances, the HARQ-ACK codebook transmitted by the UE 104 in the first PUCCH resource of the first slot may not be received by the base station 108. Release 17 provides a mechanism by which the base station 108 can explicitly request a HARQ-ACK codebook retransmission in a one-shot manner. The base station 108 can trigger a HARQ-ACK codebook retransmission by using a DCI format that does not schedule PDSCH reception. This type of HARQ-ACK retransmission may be applicable to HARQ-ACK codebook type 1 or 2. Thus, in some embodiments, a HARQ-ACK codebook retransmission request may be specific to only one HARQ process.

[0058] 4 is a signaling diagram 400 illustrating HARQ-ACK codebook retransmission according to some embodiments. The signaling diagram 400 may include, at 404, the UE 104 transmitting a capability report indicating the UE capability for supporting one-shot HARQ-ACK retransmission. In some embodiments, the capability report may report the UE capability for FG 25-7 (triggered HARQ-ACK codebook retransmission).

[0059] The signaling diagram 400 may further include, at 408, the base station 108 providing the RETX configuration to the UE 104 through RRC signaling. The RETX configuration may include a pdsch-HARQ-ACK-retx information element (IE) that configures the UE 104 with HARQ-ACK codebook retransmissions.

[0060] The signaling diagram 400 may further include, at 412, the base station 108 sending a RETX indication to the UE 104. The RETX indication may indicate a request for HARQ-ACK codebook retransmission. The indication may be provided in a new DCI field via DCI format 1_1 or 1_2.

[0061] Upon receiving the RETX indication, the UE 104 may retransmit HARQ feedback. The HARQ feedback may include a HARQ-ACK codebook that was previously transmitted by the UE 104 but not successfully received by the base station 108.

[0062] FIG. 5 illustrates a HARQ-ACK codebook retransmission 500 according to some embodiments.

[0063] The UE 104 may receive DCI 504 scheduling the HARQ-ACK transmission to be on a relatively low priority (LP) PUCCH resource 508. The LP PUCCH resource 508 may conflict with a relatively high priority (HP) channel 512, which may result in the HARQ-ACK transmission being dropped. The base station 108 may then send triggering DCI 516 for a one-shot HARQ-ACK retransmission in the PUCCH resource 520.

[0064] The triggering DCI 516 may dynamically indicate a "HARQ re-tx offset" used to define the offset in the number of PUCCH slots / subslots between the slot / subslot of the triggering DCI 516 and the slot / subslot of the PUCCH resource with the HARQ-ACK codebook to be retransmitted. If the triggering DCI 516 is received in slot / subslot m and indicates that a HARQ-ACK retransmission is to be transmitted in the PUCCH resource 520 in slot / subslot m+k and indicates HARQ_retx_offset, the slot / subslot of the PUCCH resource with the HARQ-ACK codebook to be retransmitted is determined as n=m−HARQ_retx_offset. The value range of HARQ_retx_offset may be fixed in the 3GPP TS.

[0065] HARQ-ACK codebook retransmissions may affect DRX timer processing by the MAC entity. For example, following reception of a HARQ-ACK retransmission indicator on the DCI, the UE 104 may need to start or restart the RTT timer in the first symbol after the end of the corresponding transmission carrying the retransmitted downlink HARQ feedback.

[0066] Updates to the language of section 5.7 of 3GPP TS 38.321 may be needed to handle the case where the PDCCH indicates a request for a HARQ-ACK retransmission without scheduling a downlink transmission. These updates may be provided according to one of the following two options:

[0067] In a first option, the following paragraph can be added to TS 38.321, section 5.7 to handle the case where the PDCCH indicates a HARQ-ACK retransmission without scheduling a DL transmission: 2> If PDCCH indicates HARQ-ACK retransmission without scheduling DL transmission: 3>Starting the drx-HARQ-RTT-TimerDL of the corresponding HARQ process at the first symbol after the end of the corresponding transmission carrying DL HARQ feedback; 3> Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0068] In a second option, the language of 3GPP TS 38.321, section 5.7 may be updated with underlined text to include the case where the PDCCH indicates a HARQ-ACK retransmission without scheduling a DL transmission, as follows: 1> If the DRX group is in active time: 2> Monitor the PDCCH on the serving cells in this DRX group as specified in TS 38.213 [6]; 2> If the PDCCH indicates a DL transmission or indicates a HARQ-ACK retransmission without scheduling a DL transmission: 3>Starting the drx-HARQ-RTT-TimerDL of the corresponding HARQ process at the first symbol after the end of the corresponding transmission carrying DL HARQ feedback; Note 3: As specified in TS 38.213 [6], if the HARQ feedback is postponed by a PDSCH-to-HARQ_feedback timing indicating a non-numeric k1 value, the corresponding transmission opportunity for sending the DL HARQ feedback is indicated in a later PDCCH requesting HARQ-ACK feedback. 3> Stop the drx-RetransmissionTimerDL of the corresponding HARQ process. 3>If the PDSCH-to-HARQ_feedback timing indicates a non-numeric k1 value as specified in TS 38.213 [6]: 4> Start drx-RetransmissionTimerDL at the first symbol after the (last) PDSCH transmission (in the bundle) for the corresponding HARQ process.

[0069] As briefly introduced above, Release 16 NR-U introduced the Type 3 codebook, allowing the base station 108 to request the UE 104 to send HARQ-ACK feedback for all HARQ processes of all configured cells via a one-shot trigger. Release 17 introduces an extended Type 3 HARQ-ACK codebook to reduce feedback overhead.

[0070] 6 and 7 show extended Type 3 HARQ-ACK codebooks 600 and 700, respectively, according to some embodiments. The UE 104 may be configured with these codebooks through RRC signaling.

[0071] In contrast to the Release 16 Type 3 HARQ-ACK codebook, codebooks 600 and 700 each contain HARQ feedback for a subset of HARQ processes, with each CC denoted with 16 HARQ Process IDs (HPIDs), one for each of the 16 HARQ processes.

[0072] The codebook 600 includes feedback for all HARQ processes corresponding to a subset of component carriers, particularly for all HARQ processes of CC1 and CC2.

[0073] The codebook 600 may be configured by a pdsch-HARQ-ACK-enhType3perCC IE, which configures one Enhanced Type 3 HARQ-ACK codebook using per-CC configurations. The IE may include an entry corresponding to each CC configuration. Thus, the number of entries may range from 1 to the maximum number of serving cells. Each entry may be a one-bit value indicating whether all HARQ processes of the corresponding CC are included in the codebook (e.g., the bit is set to '1') or whether none of the HARQ processes of the corresponding CC are included in the codebook (e.g., the bit is set to '0').

[0074] Codebook 700 includes a subset of configured HARQ processes for each CC. A different subset of HARQ processes can be configured for each CC using codebook 700. As shown, codebook 700 includes feedback for HPID0 to HPID7 of CC1, all HPIDs of CC2 except HPID3, HPID7, and HPID11, and HPID0 and HPID6 of CC3.

[0075] The codebook 700 may be configured by a pdsch-HARQ-ACK-enhType3perHARQ IE, which configures one Extended Type 3 HARQ-ACK codebook using a per-HARQ process and per-CC configuration. The IE may include an entry corresponding to each CC configuration. Thus, the number of entries may range from 1 to the maximum number of serving cells. Each entry may be a 16-bit value, with each bit corresponding to a respective HARQ process of the corresponding CC. The bit may indicate whether the corresponding HARQ process of the CC is included in the codebook (e.g., the bit is set to '1') or not (e.g., the bit is set to '0').

[0076] Depending on the capabilities of the UE 104, the base station 108 can configure up to eight extended Type 3 HARQ-ACK codebooks, which can be dynamically requested on the DCI along with or as one-shot HARQ-ACK.

[0077] FIG. 8 is a signaling diagram 800 to illustrate a Type 3 codebook reporting process according to some embodiments.

[0078] The signaling diagram 800 may include, at 804, the UE 104 sending a capability report indicating the UE capability of supporting extended Type 3 HARQ-ACK codebook reporting. If the UE 104 supports the reporting, the capability report may also indicate the number of extended Type 3 codebooks supported.

[0079] The signaling diagram 800 may further include, at 808, the base station 108 providing a Type 3 configuration to the UE 104 through RRC signaling. The Type 3 configuration may include one or more IEs to configure the UE 104 for Type 3 reporting. The IEs may include, but are not limited to, a pdsch-HARQ-ACK-enhType3IE, a pdsch-HARQ-ACK-enhType3ListIE, and a pdsch-HARQ-ACK-enhType3DCI fieldIE.

[0080] The signaling diagram 800 may further include, at 812, the base station 108 sending a reporting indication to the UE 104. The reporting indication may include a one-shot HARQ-ACK request (e.g., for Release 16 Type 3 codebook reporting) or an extended Type 3 codebook indicator (e.g., for Release 17 extended Type 3 codebook reporting). The reporting indication may be provided through DCI format 1_1 or 1_2, which may also schedule a PDSCH in some circumstances.

[0081] Upon receiving the reporting indication, the UE 104 may send HARQ feedback along with the selected Type 3 codebook.

[0082] There are two main cases for using one-shot HARQ-ACK requests for the Extended Type 3 HARQ-ACK codebook: In Case 1, the one-shot HARQ-ACK request may be indicated in a DCI format that schedules PDSCH reception (e.g., the DCI includes a valid Frequency Domain Resource Allocation (FDRA) field). In Case 2, the one-shot HARQ-ACK request may be indicated in a DCI format that does not schedule PDSCH (e.g., the FDRA field is disabled).

[0083] When a one-shot HARQ-ACK request is given on the DCI, for example, when the "One-Shot HARQ-ACK Request" field is set to "1", the UE 104 may refer to Table 1 for PDSCH scheduling and Enhanced Type 3 HARQ-ACK codebook lookup. [Table 1]

[0084] When a one-shot HARQ-ACK request is given on the DCI, the PDSCH-to-HARQ_feedback timing indicator field must not provide an inapplicable value from dl-DataToUL-ACK, i.e., the value K1 must be indicated along with the one-shot HARQ-ACK request.

[0085] If the DCI indicates a non-value K1, the one-shot HARQ request can be placed in a later DCI. Thus, a first DCI scheduling a PDSCH (with a non-value K1) can be followed by a second DCI that does not schedule a PDSCH with timing for the HARQ-ACK in the value K1. Embodiments herein define how the DRX timers (for all HARQ processes associated with the one-shot HARQ-ACK) should be handled in such a scenario.

[0086] TS 38.213 describes various other combination possibilities for Case 1 / 2 and value / non-value K1. For example, other possibilities include only the first DCI not scheduling a PDSCH or only the second DCI scheduling a PDSCH.

[0087] To account for situations where a Type 3 HARQ-ACK codebook request is provided with a DCI format that may or may not schedule PDSCH reception, various updates to TS 38.321 may be provided according to some embodiments.

[0088] In the first option, separate DRX HARQ RTT timer DL and DRX retransmission timer DL may be introduced just for Type 3 HARQ-ACK codebook / One-Shot HARQ-ACK request. These timers may not be linked to any other HARQ process. The use of these timers may be captured in TS language dedicated to One-Shot HARQ-ACK / Extended Type 3 HARQ-ACK codebook, which may be common for both scheduled and unscheduled PDSCH reception. For example, the language of clause 5.7 of TS 38.321 may be updated with the underlined text as follows: RRC controls the DRX operation by configuring the following parameters: ... -drx-RetransmissionTimerDL (one for Type 3 HARQ-ACK codebook, one per DL HARQ process excluding broadcast processes): maximum duration until a DL retransmission is received, ... -drx-HARQ-RTT-TimerDL (one for the Type 3 HARQ-ACK codebook, one per DL HARQ process excluding the broadcast process): the minimum duration before a DL allocation for HARQ retransmission is expected by the MAC entity, ... If DRX is configured, the MAC entity: ... 1>If drx-HARQ-RTT-TimerDL expires: 2>If drx-HARQ-RTT-TimerDL is for a Type 3 HARQ-ACK codebook: 3>Start drx-RetransmissionTimerDL for Type 3 HARQ-ACK codebook at the first symbol after expiration of drx-HARQ-RTT-TimerDL. 2> If the data of the corresponding HARQ process is not successfully decoded: 3>Start the drx-RetransmissionTimerDL for the corresponding HARQ process at the first symbol after the expiration of the drx-HARQ-RTT-TimerDL. ... 1> If the DRX group is in active time: ... 2> If the PDCCH indicates a one-shot HARQ-ACK request or contains a request for an extended type 3 HARQ-ACK codebook report: 3>Starting or restarting the drx-HARQ-RTT-TimerDL for the Type 3 HARQ-ACK codebook at the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback; 3> Stop the drx-RetransmissionTimerDL for the Type 3 HARQ-ACK codebook. Note Z: When PUCCH cell switching is configured as specified in TS 38.213, the corresponding transmission carrying DL HARQ feedback may occur on a different PUCCH cell.

[0089] A second option to capture the DRX timing behavior dedicated to the One-Shot HARQ-ACK / Extended Type 3 HARQ-ACK codebook could be to selectively manage (e.g., stop, start, restart) timers for only a subset of HARQ processes, e.g., the most important ones. This can be achieved by updating TS 38.321, clause 5.7 to include the following text: 2> If the PDCCH indicates a one-shot HARQ-ACK request or contains a request for an extended type 3 HARQ-ACK codebook report: 3> For each HARQ process reported in the HARQ-ACK codebook that is not running either drx-HARQ-RTT-TimerDL or drx-RetransmissionTimerDL: 4>Start drx-HARQ-RTT-TimerDL of the corresponding HARQ process at the first symbol after the end of the corresponding transmission carrying DL HARQ feedback. Note Z: When PUCCH cell switching is configured as specified in TS 38.213, the corresponding transmission carrying DL HARQ feedback may occur on a different PUCCH cell.

[0090] It should be noted that the text of the first and second options does not specify the conditions for whether the DCI schedules or does not schedule PDSCH reception. Therefore, the text of both the first and second options can implicitly include both. For example, the first and second options may apply to both scheduling and not scheduling PDSCH reception.

[0091] Given the various options with which a one-shot HARQ-ACK request may be indicated or combined, it may in some cases be advantageous to address one-shot HARQ-ACK in a separate paragraph in TS 38.321, as explained above. This may avoid referring to cases with / without PDSCH scheduling, and may also avoid overlapping definitions of what constitutes a corresponding HARQ process (among the HARQ processes associated with a one-shot HARQ-ACK).

[0092] The embodiments describe various method options for managing the HARQ RTT timer based on the configuration and triggering aspects of the Type 3 HARQ-ACK codebook. These options provide a way for the UE to select which HARQ processes should start / restart their HARQ RTT timers based on triggering conditions as described elsewhere herein.

[0093] The first option may include a first sub-option and a second sub-option. In the first sub-option, if the configuration of the extended Type 3 HARQ-ACK codebook is per-HARQ (e.g., via pdsch-HARQ-ACK-enhType3perHARQ), the UE 104 may start / restart the HARQ RTT timers for all HARQ processes in the codebook. This may be feasible if the list of HARQ processes reported based on the one-shot HARQ-ACK request in this situation is a subset of the total number of HARQ processes.

[0094] In a second sub-option, if the Type 3 HARQ-ACK configuration is per CC (e.g., via pdsch-HARQ-ACK-enhType3perCC) or one-shot HARQ-ACK request is applied according to Release 16, the UE 104 may start the HARQ RTT timers for a subset of the HARQ processes in the codebook. The subset HARQ processes may be identified through a secondary / selective approach that involves identifying HARQ processes reported in the HARQ-ACK codebook that have neither drx-HARQ-RTT-TimerDL nor drx-RetransmissionTimerDL running.

[0095] The second option may be similar to the first option, except that the entire list of HARQ processes configured in the pdsch-HARQ-ACK-enhType3perHARQ list may only be used if triggering is via a DCI with the pdsch-HARQ-enhType3DCI field configured. If triggering is via a DCI with the pdsch-HARQ-enhType3DCI field configured, the DCI may be used to identify one list from the multiple configured pdsch-HARQ-ACK-enhType3perHARQ lists, and the HARQ RTT timers for all HARQ processes from the identified list may be started / restarted. If the pdsch-HARQ-enhType3DCI field is not configured, the extended Type 3 HARQ-ACK codebook may still be triggered via a one-shot HARQ-ACK request field on the DCI with the pdsch-HARQ-ACK-enhType3List included. In this case, the secondary / selective approach described above with respect to the first option may be used to identify a subset of HARQ processes for which the corresponding HARQ RTT timers should be started.

[0096] In a third option, if one of the Release 17 options for the Extended Type 3 HARQ-ACK codebook is active, the UE 104 may apply the DRX timer setting to the entire list of configured (and potentially reduced) number of HARQ processes. The secondary / selective approach may be used in all other cases.

[0097] In a fourth option, the DRX timer can be started / restarted for all HARQ processes associated with the HARQ-ACK codebook, which can be applied to any Type 3 HARQ-ACK codebook.

[0098] In the fifth option, a secondary / selective approach may be used in all cases, e.g., a DRX timer may be started for each HARQ process reported in the HARQ-ACK codebook that has neither drx-HARQ-RTT-TimerDL nor drx-RetransmissionTimerDL running.

[0099] In a sixth option, one additional DRX HARQ RTT timer and one additional DRX retransmission timer may be provided only for the (extended) Type 3 HARQ-ACK codebook, regardless of the associated HARQ process.

[0100] 9 illustrates an operational flow / algorithm structure 900 according to some embodiments. The operational flow / algorithm structure 900 may be performed by a UE, such as UE 104 or UE 1400, or a component thereof, such as processing circuitry 1404.

[0101] The operational flow / algorithm structure 900 may include generating HARQ feedback, at 904. The HARQ feedback may be generated based on an attempt to receive a downlink transmission, e.g., a PDSCH transmission carrying a MAC PDU. The downlink transmission may be received in a configured downlink assignment (e.g., an SPS assignment) or in any other manner.

[0102] The operational flow / algorithm structure 900 may further include identifying a conflict with a first PUCCH resource, at 908. The first PUCCH resource may be a resource originally scheduled to carry HARQ feedback. The conflict may be due to a PUCCH resource that at least partially overlaps with a downlink symbol that may have a higher priority.

[0103] The operational flow / algorithm structure 900 may further include, at 912, transmitting the HARQ feedback in a second PUCCH resource. The second PUCCH resource may occur later than the first PUCCH resource. For example, the second PUCCH resource may be in a slot that occurs after the slot having the first PUCCH resource.

[0104] The operational flow / algorithm structure 900 may further include starting a DRX RTT timer after transmitting the HARQ feedback at 916. The DRX RTT timer may be started at the first symbol after transmitting the HARQ feedback. Some embodiments may further include stopping the DRX retransmission timer based on receiving the downlink transmission.

[0105] 10 illustrates an operational flow / algorithm structure 1000 according to some embodiments. The operational flow / algorithm structure 1000 may be performed by a UE, such as UE 104 or UE 1400, or a component thereof, such as processing circuitry 1404.

[0106] The operational flow / algorithm structure 1000 may include, at 1004, attempting to receive a PDSCH transmission on a first serving cell. The PDSCH transmission may carry a MAC PDU. The first serving cell, which may be a PCell or an SCell, may be provided on a first component carrier in a first band.

[0107] The operational flow / algorithm structure 1000 may further include switching to a second serving cell at 1008. The second serving cell, which may be a PCell or an SCell, may be provided on a second component carrier in a second band.

[0108] In some embodiments, switching between the first and second serving cells may be performed according to a semi-static PUCCH carrier switching configuration or a dynamic PUCCH carrier switching configuration. RRC signaling may be used to provide the UE with a periodic cell switching pattern to enable semi-static PUCCH carrier switching. Dynamic PUCCH carrier switching may be accomplished by the base station including an instruction in the DCI prompting the UE to switch serving cells.

[0109] The operational flow / algorithm structure 1000 may further include transmitting HARQ feedback in the second cell at 1012. The HARQ feedback may correspond to an attempt to receive a PDSCH transmission in the first serving cell. The HARQ feedback may be transmitted on PUCCH resources of the second serving cell.

[0110] The operational flow / algorithm structure 1000 may further include starting a DRX RTT timer after transmitting the HARQ feedback, at 1016. The DRX RTT timer may be started at the first symbol after transmitting the HARQ feedback.

[0111] 11 illustrates an operational flow / algorithm structure 1100 according to some embodiments. The operational flow / algorithm structure 1100 may be performed by a UE, such as UE 104 or UE 1400, or a component thereof, such as processing circuitry 1404.

[0112] The operational flow / algorithm structure 1100 may include, at 1104, identifying a first resource for transmitting DL HARQ feedback. The first resource may be a slot or a subslot. The DL HARQ feedback may correspond to an attempt to receive a downlink transmission. The first resource may be determined based on a timing of the attempt to receive the downlink transmission or may be scheduled by a DCI.

[0113] The operational flow / algorithm structure 1100 may further include receiving a PDCCH transmission indicating a HARQ-ACK retransmission, at 1108. The PDCCH transmission may be received in a resource that occurs after the first resource identified for transmitting DL HARQ feedback.

[0114] The operational flow / algorithm structure 1100 may further include transmitting the DL HARQ feedback as an HARQ retransmission, at 1112. The HARQ retransmission may be performed on a resource that occurs after the resource on which the PDCCH transmission was received.

[0115] In some embodiments, the UE may identify the offset and identify the DL HARQ feedback as a HARQ transmission based on the offset and the resource on which the PDCCH transmission is received.

[0116] The operational flow / algorithm structure 1100 may further include starting a DRX RTT timer after transmitting the DL HARQ feedback, at 1116. The DRX RTT timer may be started at the first symbol after transmitting the DL HARQ feedback. Some embodiments may further include stopping the DRX retransmission timer based on receiving the PDSCH transmission.

[0117] 12 illustrates an operational flow / algorithm structure 1200 according to some embodiments. The operational flow / algorithm structure 1200 may be performed by a UE, such as UE 104 or UE 1400, or a component thereof, such as processing circuitry 1404.

[0118] The operational flow / algorithm structure 1200 may include, at 1204, receiving a PDCCH transmission having a request for a Type 3 codebook. The codebook may be a non-extended Type 3 codebook (e.g., a Release 16 codebook) or an extended Type 3 codebook (e.g., a Release 17 codebook). The request, which may be a DCI transmission, may be a one-shot HARQ-ACK request or a request for an extended Type 3 HARQ-ACK codebook report.

[0119] The operational flow / algorithm structure 1200 may further include transmitting HARQ feedback based on the request, at 1208. The HARQ feedback may include feedback for HARQ processes of a corresponding Type 3 codebook, which may include some or all of the HARQ processes of the component carrier.

[0120] The operational flow / algorithm structure 1200 may further include starting or restarting a DRX HARQ RTT timer for the Type 3 codebook, at 1212. The timer may be started or restarted at the first symbol following the symbol at which the HARQ feedback was transmitted. In some embodiments, the DRX retransmission timer for the Type 3 HARQ-ACK codebook may be stopped based on receiving a PDCCH transmission.

[0121] 13 illustrates an operational flow / algorithm structure 1300 according to some embodiments. The operational flow / algorithm structure 1300 may be performed by a UE, such as UE 104 or UE 1400, or a component thereof, such as processing circuitry 1404.

[0122] The operational flow / algorithm structure 1300 may include, at 1304, receiving a PDCCH transmission having a request for a Type 3 codebook. The codebook may be a non-extended Type 3 codebook (e.g., a Release 16 codebook) or an extended Type 3 codebook (e.g., a Release 17 codebook). The request, which may be a DCI transmission, may be a one-shot HARQ-ACK request or a request for an extended Type 3 HARQ-ACK codebook report.

[0123] The operational flow / algorithm structure 1300 may further include transmitting HARQ feedback based on the request, at 1308. The HARQ feedback may include feedback for HARQ processes of a corresponding Type 3 codebook, which may include some or all of the HARQ processes of the component carrier.

[0124] The operational flow / algorithm structure 1300 may further include identifying one or more HARQ processes without a running DRX timer, at 1312. The DRX timer may be a DRX HARQ RTT timer or a DRX retransmission timer. In some embodiments, the identifying performed at 1312 may include identifying one or more HARQ processes for which neither a corresponding DRX HARQ RTT timer nor a corresponding DRX retransmission timer is running.

[0125] The operational flow / algorithm structure 1300 may further include starting a DRX HARQ RTT timer for one or more HARQ processes, at 1316. Thus, a DRX HARQ RTT timer may be started for HARQ processes that do not have a DRX HARQ RTT timer or a DRX retransmission timer running upon transmission of HARQ feedback.

[0126] 9-13 describe the operational flow / algorithm structure from the perspective of the UE. However, as noted above, the base station may need to manage the DRX HARQ timers in a similar manner as the UE to coordinate communications. Therefore, embodiments may also include operational flows / algorithm structures from the perspective of the base station similar to those described with respect to FIGS. 9-13 or any other embodiment herein.

[0127] 14 illustrates a UE 1400 according to some embodiments. The UE 1400 may be similar to and substantially interchangeable with the UE 104 of FIG.

[0128] The UE 1400 may be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an XR device, glasses, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a barometric pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, or an actuator), a video surveillance / monitoring device (e.g., a camera or a video camera), a wearable device (e.g., a smart watch), or an Internet of Things device.

[0129] The UE 1400 may include a processor 1404, an RF interface circuit 1408, memory / storage 1412, a user interface 1416, sensors 1420, driver circuitry 1422, a power management integrated circuit (PMIC) 1424, an antenna structure 1426, and a battery 1428. The components of the UE 1400 may be implemented as an integrated circuit (IC), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof. The block diagram of FIG. 14 is intended to illustrate a high-level view of some components of the UE 1400. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other embodiments.

[0130] The components of the UE 1400 may be coupled to various other components via one or more interconnects 1432, which may represent any type of interface, input / output, bus (local, system, or expansion), transmission line, trace, optical connection, or the like that allows various circuit components (on a common or different chips or chipsets) to interact with one another.

[0131] The processor 1404 may include processor circuitry such as, for example, a baseband processor circuit (BB) 1404A, a central processing unit circuit (CPU) 1404B, and a graphics processing unit circuit (GPU) 1404C. The processor 1404 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory / storage 1412, to cause the UE 1400 to perform the operations described herein.

[0132] In some embodiments, the baseband processor circuitry 1404A may access a communications protocol stack 1436 in memory / storage 1412 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuitry 1404A may access the communications protocol stack 1436 to perform user plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, SDAP sublayer, and higher layers, and control plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, RRC layer, and NAS layer. In some embodiments, PHY layer operations may additionally / alternatively be performed by components of the RF interface circuitry 1408.

[0133] The baseband processor circuit 1404A may generate or process baseband signals or waveforms that carry information in a 3GPP-compliant network. In some embodiments, waveforms for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0134] The memory / storage 1412 may include one or more non-transitory computer-readable media (e.g., communication protocol stack 1436) that include instructions that may be executed by one or more of the processors 1404 to cause the UE 1400 to perform various operations described herein. The memory / storage 1412 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1400. In some embodiments, some of the memory / storage 1412 may be located on the processor 1404 itself (e.g., L1 and L2 cache), while other memory / storage 1412 may be external to the processor 1404 but accessible via a memory interface. The memory / storage 1412 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0135] The RF interface circuitry 1408 may include transceiver circuitry and a radio frequency front end module (RFEM) that enable the UE 1400 to communicate with other devices over a radio access network. The RF interface circuitry 1408 may include various elements disposed in the transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, combiner circuits, and control circuits.

[0136] In the receive path, the RFEM may receive a radiated signal from the air interface via the antenna structure 1426 and proceed to filter and amplify the signal (using a low noise amplifier). The signal may be provided to a transceiver receiver that downconverts the RF signal to a baseband signal that is provided to a baseband processor of the processor 1404.

[0137] On the transmit path, the transmitter of the transceiver upconverts the baseband signal received from the baseband processor and provides an RF signal to the RFEM, which may amplify the RF signal through a power amplifier before the signal is radiated over the air interface via the antenna 1426.

[0138] In various embodiments, the RF interface circuitry 1408 may be configured to transmit and receive signals in a manner that complies with NR access technologies.

[0139] The antenna 1426 may include antenna elements that convert electrical signals into radio waves that travel through the air and convert received radio waves into electrical signals. The antenna elements may be arranged in one or more antenna panels. The antenna 1426 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple-input, multiple-output communications. The antenna 1426 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, or phased array antennas. The antenna 1426 may have one or more panels designed for a specific frequency band, including the FR1 or FR2 bands.

[0140] User interface circuitry 1416 includes various input / output (I / O) devices designed to enable user interaction with UE 1400. User interface 1416 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input, including, among other things, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying or otherwise communicating information, such as sensor readings, actuator position(s), or other similar information. The output device circuitry may include any number or combination of audio or visual displays, including, among other things, one or more simple visual outputs / indicators (e.g., binary status indicators such as light emitting diodes (LEDs) and multi-character visual outputs), or more complex outputs such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, or projectors), and output such as text, graphics, multimedia objects, etc. generated or created from operation of the UE 1400.

[0141] Sensors 1420 may include devices, modules, or subsystems whose purpose is to detect events or changes in their environment and transmit information about the detected events (sensor data) to some other devices, modules, or subsystems. Examples of such sensors include inertial measurement units with accelerometers, gyroscopes, or magnetometers; microelectromechanical or nanoelectromechanical systems with three-axis accelerometers, three-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless iris sensors); light detection and ranging sensors, proximity sensors (e.g., infrared detectors, etc.), depth sensors, ambient light sensors, ultrasonic transceivers, and microphones or other similar audio capture devices.

[0142] The driver circuitry 1422 may include software and hardware elements that operate to control particular devices embedded in, attached to, or otherwise communicatively coupled to the UE 1400. The driver circuitry 1422 may include individual drivers that enable other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE 1400. For example, the driver circuitry 1422 may include a display driver that controls and enables access to a display device, a touchscreen driver that controls and enables access to a touchscreen interface, a sensor driver that obtains sensor readings of the sensor circuitry 1420 and controls and enables access to the sensor circuitry 1420, a driver that obtains actuator positions of or controls and enables access to electromechanical components, a camera driver that controls and enables access to an embedded image capture device, and an audio driver that controls and enables access to one or more audio devices.

[0143] The PMIC 1424 may manage the power supplied to various components of the UE 1400. In particular, with respect to the processor 1404, the PMIC 1424 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0144] In some embodiments, the PMIC 1424 may control or otherwise be part of various power saving mechanisms of the UE 1400, including DRX as discussed herein.

[0145] The battery 1428 may provide power to the UE 1400, although in some examples the UE 1400 may be deployed and attached to a fixed location and may have a power source coupled to a power grid. The battery 1428 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in vehicle-based applications, the battery 1428 may be a typical automotive lead-acid battery.

[0146] 15 illustrates a network node 1500 according to some embodiments. The network node 1500 may be similar to, and substantially interchangeable with, the base station 108 of FIG.

[0147] The network node 1500 may include a processor 1504, RF interface circuitry 1508 (if implemented as an access node), core network (CN) interface circuitry 1512, memory / storage circuitry 1516, and antenna structure 1526 (if implemented as an access node).

[0148] The components of network node 1500 may be coupled to various other components via one or more interconnects 1528 .

[0149] The processor 1504, RF interface circuitry 1508, memory / storage circuitry 1516 (including communication protocol stack 1510), antenna structure 1526, and interconnect 1528 may be similar to the like-named elements shown and described with respect to FIG.

[0150] The CN interface circuitry 1512 can provide connectivity to a core network, e.g., a fifth-generation network interface (5GC), using a 5GC-compatible core network protocol, such as the Carrier Ethernet protocol, or some other suitable protocol. Network connectivity can be provided to / from the base station 1500 via optical fiber or wireless backhaul. The CN interface circuitry 1512 can include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 1512 can include multiple controllers to provide connectivity to other networks using the same or different protocols.

[0151] In some embodiments, the network node 1500 may be coupled to a transmission reception point (TRP) using an antenna structure 1526, a CN interface circuit, or other interface circuit.

[0152] It is understood that use of personally identifiable information should comply with generally recognized privacy policies and practices that meet or exceed industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of permitted uses should be clearly indicated to users.

[0153] For one or more embodiments, at least one of the components depicted in one or more of the foregoing figures may be configured to perform one or more of the operations, techniques, processes, or methods described in the example section below. For example, the baseband circuitry described above in connection with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below. As another example, circuitry associated with a UE, a base station, or a network element such as those described above in connection with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below in the example section. Example

[0154] Further exemplary embodiments are provided in the following sections.

[0155] Example 1 includes a method that includes generating hybrid automatic repeat request (HARQ) feedback based on an attempt to receive a medium access control (MAC) protocol data unit (PDU) on a configured downlink allocation; identifying a conflict associated with a first physical uplink control channel (PUCCH) resource scheduled to carry the HARQ feedback; transmitting the HARQ feedback on a second PUCCH resource based on the identification of the conflict; and starting a discontinuous reception (DRX) HARQ round trip time (RTT) timer at a first symbol after transmitting the HARQ feedback.

[0156] Example 2 includes the method of example 1 or any other example herein, further including stopping the DRX retransmission timer based on receiving the MAC PDU.

[0157] Example 3 includes the method of example 1 or any other example herein, wherein the configured downlink assignment includes a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH).

[0158] Example 4 includes the method of Example 1 or any other example herein, wherein the first PUCCH resource is in a first slot and the second PUCCH resource is in a second slot that occurs after the first slot.

[0159] Example 5 includes a method that includes attempting to receive a physical downlink shared channel (PDSCH) transmission in a first serving cell, switching to a second serving cell after attempting to receive the PDSCH transmission, transmitting hybrid automatic repeat request (HARQ) feedback corresponding to attempting to receive the PDSCH transmission on a physical uplink control channel (PUCCH) resource of the second serving cell, and starting a discontinuous reception (DRX) HARQ round trip time (RTT) timer at a first symbol after transmitting the HARQ feedback.

[0160] Example 6 includes the method of Example 5 or any other example herein, further including receiving a radio resource control (RRC) message configuring the UE with a periodic cell switching pattern; and switching to the second serving cell based on the periodic cell switching pattern.

[0161] Example 7 includes the method of example 6 or any other example herein, further including attempting to receive a PDSCH transmission in a semi-persistent scheduling (SPS) downlink allocation.

[0162] Example 8 includes the method of Example 5 or any other example herein, further including receiving an indication in downlink control information (DCI) and switching to the second serving cell based on the indication.

[0163] Example 9 includes the method of Example 8 or any other example herein, further including monitoring a physical downlink control channel (PDCCH); and based on the monitoring, detecting a PDCCH transmission that schedules a PDSCH transmission.

[0164] Example 10 includes a method including identifying a first resource for transmitting downlink (DL) hybrid automatic repeat request (HARQ) feedback; receiving a physical downlink channel (PDCCH) transmission indicating a HARQ-acknowledgement (ACK) retransmission; transmitting the DL HARQ feedback as a HARQ-ACK retransmission in a physical uplink control channel (PUCCH) of a second resource; and starting a discontinuous reception (DRX) HARQ round trip time (RTT) timer at a first symbol after transmitting the DL HARQ feedback.

[0165] Example 11 includes the method of Example 10 or any other example herein, wherein the first resource is a first slot or sub-slot, and the second resource is a second slot or sub-slot.

[0166] Example 12 includes the method of example 10 or any other example herein, wherein the PDCCH transmission does not schedule a downlink transmission.

[0167] Example 13 includes the method of example 10 or any other example herein, further including stopping the DRX retransmission timer based on receiving the PDCCH transmission.

[0168] Example 14 includes the method of example 10 or any other example herein, wherein the PDCCH transmission is received on a third resource, and the method further includes identifying an offset and identifying DL HARQ feedback based on the offset and the third resource.

[0169] Example 15 includes a method that includes receiving a physical downlink control channel (PDCCH) transmission including a request to report a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook, where the request is a one-shot HARQ-ACK request or a request for an enhanced type-3 HARQ-ACK codebook report; transmitting HARQ feedback corresponding to the HARQ-ACK codebook based on the request; and starting or restarting a discontinuous reception (DRX) hybrid automatic repeat request (HARQ) round-trip time (RTT) timer for the type-3 HARQ-ACK codebook after transmitting the HARQ feedback.

[0170] Example 16 includes the method of Example 15 or any other example herein, wherein transmitting the HARQ feedback includes transmitting the HARQ feedback in a first symbol, and the method further includes starting or restarting a DRX HARQ RTT timer for the Type-3 HARQ-ACK codebook in a second symbol following the first symbol.

[0171] Example 17 includes the method of Example 15 or any other example herein, further including stopping a DRX retransmission timer for the Type 3 HARQ-ACK codebook based on receiving the PDCCH transmission.

[0172] Example 18 includes a method that includes receiving a physical downlink control channel (PDCCH) transmission indicating a one-shot hybrid automatic repeat request (HARQ)-acknowledgement (ACK) request or including a request for an extended type 3 HARQ-ACK codebook report; transmitting HARQ feedback corresponding to a plurality of HARQ processes of the HARQ-ACK codebook based on the PDCCH transmission; identifying one or more HARQ processes among the plurality of HARQ processes for which neither a corresponding discontinuous reception (DRX) hybrid automatic repeat request (HARQ) round trip time (RTT) timer nor a corresponding DRX retransmission timer is running; and starting a DRX HARQ RTT timer corresponding to each of the one or more HARQ processes.

[0173] Example 19 includes the method of Example 18 or any other example herein, wherein transmitting the HARQ feedback includes transmitting the HARQ feedback in a first symbol, and the method further includes starting a DRX HARQ RTT timer corresponding to each of the one or more HARQ processes in a second symbol following the first symbol.

[0174] Example 20 includes the method of Example 19 or any other example herein, further including: determining that a DRX HARQ RTT timer for a first HARQ process of the plurality of HARQ processes is running; and refraining from restarting the DRX HARQ RTT timer for the first HARQ process based on the sending of the HARQ feedback.

[0175] Example 21 includes a method including receiving a request to report a type 3 hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook with HARQ feedback information for a set of HARQ processes of one or more component carriers, reporting the type 3 HARQ-ACK codebook, selecting one or more HARQ processes from the set of HARQ processes, and starting or restarting a discontinuous reception (DRX) HARQ timer corresponding to the one or more HARQ processes.

[0176] Example 22 includes the method of Example 21 or any other example herein, wherein the Type 3 HARQ-ACK codebook is an extended Type 3 HARQ-ACK codebook, and the method further includes receiving, from the base station, information for configuring the extended Type 3 HARQ-ACK codebook.

[0177] Example 23 includes the method of Example 22 or any other example herein, wherein the information is for configuring an extended Type 3 HARQ-ACK codebook using a per HARQ process and per component carrier (CC) configuration, and the one or more HARQ processes include all HARQ processes of the set of HARQ processes.

[0178] Example 24 includes the method of example 22 or any other example herein, wherein the information is for configuring an extended Type 3 HARQ-ACK codebook using the per HARQ process and per component carrier (CC) configuration, and the method further includes: selecting one or more HARQ processes to include all HARQ processes of the set of HARQ processes if the request is received via downlink control information (DCI); and selecting one or more HARQ processes to include HARQ processes of the set of HARQ processes for which neither a discontinuous reception (DRX) hybrid automatic repeat request (HARQ) round trip time (RTT) timer nor a DRX retransmission timer is running if the request is not received via DCI.

[0179] Example 25 includes the method of example 22 or any other example herein, wherein the information is for configuring an extended Type 3 HARQ-ACK codebook using a per HARQ process and per component carrier (CC) configuration, and the method further includes, if the request is received with a downlink control information (DCI) field configured to dynamically indicate a list of HARQ processes from a plurality of lists of HARQ processes, selecting one or more HARQ processes to include all HARQ processes of the list of HARQ processes, and if the request is received without a DCI field configured to dynamically indicate a list of HARQ processes from a plurality of lists of HARQ processes, selecting one or more HARQ processes to include HARQ processes of the set of HARQ processes for which neither a discontinuous reception (DRX) hybrid automatic repeat request (HARQ) round trip time (RTT) timer nor a DRX retransmission timer is running.

[0180] Example 26 includes the method of Example 22 or any other example herein, wherein the information is for configuring an enhanced Type 3 HARQ-ACK codebook using processes per component carrier (CC), and the selecting of one or more HARQ processes includes selecting a subset of HARQ processes from a set of HARQ processes.

[0181] Example 27 includes the method of example 26 or any other example herein, wherein selecting a subset of HARQ processes includes selecting HARQ processes from the set of HARQ processes for which neither a discontinuous reception (DRX) hybrid automatic repeat request (HARQ) round trip time (RTT) timer nor a DRX retransmission timer is running.

[0182] Example 28 includes the method of example 21 or 22 or any other example herein, further including selecting one or more HARQ processes to include all HARQ processes in the set of HARQ processes.

[0183] Example 29 includes the method of example 21 or 22 or any other example herein, further including selecting one or more HARQ processes to include HARQ processes from the set of HARQ processes that have neither a discontinuous reception (DRX) hybrid automatic repeat request (HARQ) round trip time (RTT) timer nor a DRX retransmission timer running.

[0184] Example 30 includes the method of Example 21 or any other example herein, wherein the DRX HARQ timer comprises a DRX round trip time (RTT) timer and a DRX retransmission timer dedicated to the Type 3 HARQ-ACK codebook.

[0185] Example 31 includes a method including: transmitting a physical downlink channel (PDCCH) transmission indicating a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) retransmission; receiving downlink HARQ feedback as a HARQ-ACK retransmission in a physical uplink control channel (PUCCH) transmission; and starting a discontinuous reception (DRX) HARQ round trip time (RTT) timer at a first symbol after receiving the DL HARQ feedback.

[0186] Example 32 includes the method of example 31 or any other example herein, wherein the PDCCH transmission does not schedule a downlink transmission.

[0187] Example 33 includes the method of example 31 or any other example herein, further including stopping the DRX retransmission timer based on transmitting the PDCCH transmission.

[0188] Example 34 includes the method of Example 31 or any other example herein, wherein the PDCCH transmission is received on a third resource, and the method further includes identifying an offset and identifying DL HARQ feedback based on the offset and the third resource.

[0189] Example 35 may include an apparatus comprising means for performing one or more elements of a method described or related to any of Examples 1-34, or any other method or process described herein.

[0190] Example 36 may include one or more non-transitory computer-readable media containing instructions that, upon execution by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of Examples 1-34, or any other method or process described herein.

[0191] Example 37 may include an apparatus having logic, modules, or circuitry for performing one or more elements of a method described or related to any of Examples 1-34, or any other method or process described herein.

[0192] Example 38 may include any method, technique, or process described in or related to any of Examples 1-34, or any part or portion thereof.

[0193] Example 39 may include an apparatus having one or more processors and one or more computer-readable media having instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any of Examples 1 to 34, or portions thereof.

[0194] Example 40 may include a signal described in or related to any of Examples 1-34, or a portion or part thereof.

[0195] Example 41 may include a datagram, information element, packet, frame, segment, PDU, or message described or associated with any of Examples 1-34, or a portion or part thereof, or others described in this disclosure.

[0196] Example 42 may include a signal encoded with data described in or related to any of Examples 1-34, or a portion or part thereof, or any other signal described in this disclosure.

[0197] Example 43 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message described or associated with any of Examples 1-34, or a portion or part thereof, or a signal described otherwise in this disclosure.

[0198] Example 44 may include an electromagnetic signal carrying a plurality of computer-readable instructions, the execution of which by one or more processors causes the one or more processors to perform a method, technique, or process described in or related to any of Examples 1-34 or portions thereof.

[0199] Example 45 may include a computer program including instructions, where execution of the program by a processing element causes the processing element to perform a method, technique, or process, or a portion thereof, described in or related to any of Examples 1-34.

[0200] Example 46 may include signals in a wireless network as shown and described herein.

[0201] Example 47 may include a method of communicating in a wireless network as shown and described herein.

[0202] Example 48 may include a system for providing wireless communication as shown and described herein.

[0203] Example 49 may include a device for providing wireless communication as shown and described herein.

[0204] Any of the above examples may be combined with any other example (or combination of examples) unless otherwise stated. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0205] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated, and it is intended that the following claims be interpreted to embrace all such variations and modifications.

Claims

1. One or more computer-readable media having instructions that, when executed, cause a processor circuit to: receiving a physical downlink control channel (PDCCH) transmission indicating a retransmission of hybrid automatic repeat request (HARQ) feedback; outputting a downlink (DL) HARQ feedback for transmission as a retransmission of the HARQ-ACK feedback; One or more computer-readable media for starting a discontinuous reception (DRX) HARQ round trip time (RTT) timer at a first symbol after transmitting the DL HARQ feedback.

2. 10. The one or more computer-readable media of claim 1, wherein the PDCCH transmission does not schedule a downlink transmission.

3. The instructions, when executed, further cause the processor circuitry to: The one or more computer-readable media of claim 1 , further comprising stopping a DRX retransmission timer based on receiving the PDCCH transmission.

4. The PDCCH transmission is received on a resource, and the instructions, when executed, further cause the processor circuit to: Identify the offset, The one or more computer-readable media of claim 1 , further comprising: identifying the DL HARQ feedback based on the offset and the resource.

5. 4. The one or more computer-readable media of claim 1, wherein both the DL HARQ feedback and the DRX HARQ RTT timer are associated with a HARQ process.

6. 1. An apparatus comprising a circuit, the circuit comprising: Implementing a discontinuous reception (DRX) hybrid automatic repeat request (HARQ) round trip time (RTT) timer; receiving a physical downlink control channel (PDCCH) transmission indicating feedback, the feedback being a retransmission of hybrid automatic repeat request (HARQ) feedback; generating the feedback based on the PDCCH transmission; outputting said feedback for transmission; The apparatus is configured to start or restart the DRX HARQ RTT timer based on the output of the feedback for transmission.

7. The feedback is output for transmission in a first symbol, the circuit further comprising:

7. The apparatus of claim 6, for starting or restarting the DRX HARQ RTT timer at a second symbol following the first symbol.

8. The circuit further comprises: The apparatus of claim 6 or 7, for stopping a DRX retransmission timer for a Type 3 HARQ-ACK codebook based on receiving the PDCCH transmission.

9. The apparatus according to claim 6 or 7, wherein the DRX HARQ RTT timer is for a Type 3 HARQ-ACK codebook.

10. The apparatus of claim 6 or 7, wherein both the feedback and the DRX HARQ RTT timer are associated with a HARQ process.

11. 1. A method comprising: receiving a physical downlink control channel (PDCCH) transmission indicating feedback, the feedback being a retransmission of hybrid automatic repeat request (HARQ) feedback; generating the feedback based on the PDCCH transmission; and outputting the feedback for transmission; starting or restarting a discontinuous reception (DRX) hybrid automatic repeat request (HARQ) round trip time (RTT) timer based on outputting the feedback for transmission; A method comprising:

12. The feedback is output for transmission in a first symbol, the method further comprising: The method of claim 11 , comprising starting or restarting the DRX HARQ RTT timer at a second symbol following the first symbol.

13. The method comprises: The method of claim 11 or 12, further comprising stopping a DRX retransmission timer for a Type 3 HARQ-ACK codebook based on receiving the PDCCH transmission.

14. The method according to claim 11 or 12, wherein the DRX HARQ RTT timer is for a Type 3 HARQ-ACK codebook.

15. The method of claim 11 or 12, wherein both the feedback and the DRX HARQ RTT timer are associated with a HARQ process.

Images