BACKGROUND

[0001] Embodiments of the present disclosure relate to apparatus and method for wireless communication.

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. A radio access technology (RAT) is the underlying physical connection method for a radio-based communication network. Many modem terminal devices, such as mobile devices, support several RATs in one device. In cellular communication, such as the 4th-generation (4G) Long Term Evolution (LTE) and the 5th-generation (5G) New Radio (NR), the 3rd Generation Partnership Project (3GPP) defines various mechanisms for processing downlink (DL) data packets at a receiving node.

SUMMARY

[0003] Embodiments of apparatus and method for managing timing violations related to downlink (DL) data processing are disclosed herein.

[0004] According to one aspect of the present disclosure, an apparatus for wireless communication of a receiver is provided. The apparatus may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to receive, from a transmitter, a first packet in a first subframe and a second packet in a second subframe. The at least one processor may be configured to perform a first processing of the first packet during a first time budget associated with the first packet. The at least one processor may be configured to determine that the first processing of the first packet will exceed the first time budget. The at least one processor may be configured to determine that a first retransmission number associated with the first packet is less than a second retransmission number associated with the second packet in response to determining that the first processing of the first packet will exceed the first time budget. The at least one processor may be configured to abort the first processing of the first packet at an end of the first time budget in response to determining that the first retransmission number associated with the first packet is less than the second retransmission number associated with the second packet. [0005] According to another aspect of the disclosure, a method of wireless communication of a receiver is provided. The method may include receiving, from a transmitter, a first packet in a first subframe and a second packet in a second subframe. The method may include performing first processing of the first packet during a first time budget associated with the first packet. The method may include determining that the first processing of the first packet will exceed the first time budget. The method may include determining that a first retransmission number associated with the first packet is less than a second retransmission number associated with the second packet in response to determining that the first processing of the first packet will exceed the first time budget. The method may include aborting the first processing of the first packet at an end of the first time budget in response to determining that the first retransmission number associated with the first packet is less than the second retransmission number associated with the second packet. [0006] According to yet another aspect of the present disclosure, anon-transitory computer- readable medium encoding instructions that, when executed by at least one processor, perform wireless communication of a receiver. The process may include receiving, from a transmitter, a first packet in a first subframe and a second packet in a second subframe. The process may include performing first processing of the first packet during a first time budget associated with the first packet. The process may include determining that the first processing of the first packet will exceed the first time budget. The process may include determining that a first retransmission number associated with the first packet is less than a second retransmission number associated with the second packet in response to determining that the first processing of the first packet will exceed the first time budget. The process may include aborting the first processing of the first packet at an end of the first time budget in response to determining that the first retransmission number associated with the first packet is less than the second retransmission number associated with the second packet.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate embodiments of the present disclosure and, together with the description, further serve to explain the principles of the present disclosure and to enable a person skilled in the pertinent art to make and use the present disclosure.

[0008] FIG. 1 illustrates an exemplary wireless network, according to some embodiments of the present disclosure. [0009] FIG. 2 illustrates a block diagram of an exemplary apparatus including a baseband chip, a radio frequency (RF) chip, and a host chip, according to some embodiments of the present disclosure.

[0010] FIG. 3 illustrates a flow chart of an exemplary abort/continue processing mechanism in the event of a DL processing timing violation, according to some embodiments of the present disclosure.

[0011] FIG. 4 illustrates a flow chart of an exemplary acknowledgement (ACK)/negative ACK (NACK) reporting mechanism in the event of a DL processing timing violation, according to some embodiments of the present disclosure.

[0012] FIG. 5 illustrates a flow chart of an exemplary retransmission processing mechanism in the event of a DL processing timing violation, according to some embodiments of the present disclosure.

[0013] FIG. 6 illustrates a block diagram of an exemplary node, according to some embodiments of the present disclosure.

[0014] FIG. 7A illustrates a first diagram of a conventional DL reception, processing, and ACK/NACK reporting mechanism without a timing violation.

[0015] FIG. 7B illustrates a second diagram of a conventional DL reception, processing, and ACK/NACK reporting mechanism with a timing violation that does not interfere with the processing of a subsequent data packet.

[0016] FIG. 7C illustrates a third diagram of a conventional DL reception, processing, and ACK/NACK reporting mechanism with a timing violation that interferes with the processing of a subsequent data packet.

[0017] Embodiments of the present disclosure will be described with reference to the accompanying drawings.

DETAILED DESCRIPTION

[0018] Although some configurations and arrangements are discussed, it should be understood that this is done for illustrative purposes only. A person skilled in the pertinent art will recognize that other configurations and arrangements can be used without departing from the spirit and scope of the present disclosure. It will be apparent to a person skilled in the pertinent art that the present disclosure can also be employed in a variety of other applications.

[0019] It is noted that references in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” “some embodiments,” “certain embodiments,” etc., indicate that the embodiment described may include a feature, structure, or characteristic, but every embodiment may not necessarily include the feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Further, when a feature, structure, or characteristic is described in connection with an embodiment, it would be within the knowledge of a person skilled in the pertinent art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0020] In general, terminology may be understood at least in part from usage in context. For example, the term “one or more” as used herein, depending at least in part upon context, may be used to describe any feature, structure, or characteristic in a singular sense or may be used to describe combinations of features, structures or characteristics in a plural sense. Similarly, terms, such as “a,” “an,” or “the,” again, may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context. In addition, the term “based on” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for existence of additional factors not necessarily expressly described, again, depending at least in part on context.

[0021] Various aspects of wireless communication systems will now be described with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, units, components, circuits, steps, operations, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, firmware, computer software, or any combination thereof. Whether such elements are implemented as hardware, firmware, or software depends upon the application and design constraints imposed on the overall system.

[0022] The techniques described herein may be used for various wireless communication networks, such as code division multiple access (CDMA) system, time division multiple access (TDMA) system, frequency division multiple access (FDMA) system, orthogonal frequency division multiple access (OFDMA) system, single-carrier frequency division multiple access (SC- FDMA) system, wireless local area network (WLAN) system, and other networks. The terms “network” and “system” are often used interchangeably. A CDMA network may implement a radio access technology (RAT), such as Universal Terrestrial Radio Access (UTRA), evolved UTRA (E-UTRA), CDMA 2000, etc. A TDMA network may implement a RAT, such as global system for mobile communications (GSM). An OFDMA network may implement a first RAT, such as LTE or NR. A WLAN system may implement a second RAT, such as Wi-Fi. The techniques described herein may be used for the wireless networks and RATs mentioned above, as well as other wireless networks and RATs.

[0023] In wireless communication, after receiving a DL data packet (hereinafter, “data packet”), a receiving node performs a receiving process, which includes decoding the data packet and performing an error correction check. The receiving process is performed within a predetermined time period known as a time budget. Once a data packet has been processed, ACK/NACK feedback is sent to the transmitting node. For low latency applications such as, e.g., ultra-reliable low latency communication (URLLC), the receiving node may have difficulty completing the entire receiving and feedback process as low latency procedures are performed within a reduced time budget as compared to applications that can tolerate longer latency times (e.g., enhance mobile broadband (eMBB) communications). In certain timing-critical use cases of URLLC, the time budget allotted for the receiving and feedback process may be as short as 4.5 symbols (e.g., 0.32ms). In instances when the receiving node is unable to complete the receiving/feedback process within the allotted time budget, a timing violation of DL data processing may occur. Such a timing violation may lead to various consequences that negatively impact user experience. Whether the receiving node can perform data processing within the allotted time budget may depend on various factors. Examples of these factors may include, e.g., 1) the processing capability of the receiving node (e.g., namely, how many processing engines are available, the operational clock frequency, etc.), and 2) the amount of data delivered by the transmitting node (e.g., the transmission throughput), just to name a few. Illustrative examples of the receiving/feedback process and timing violations mentioned above are depicted in FIGs. 7A- 7C.

[0024] For example, FIG. 7A illustrates a diagram 700 that depicts a receiving/feedback process without a timing violation. FIG. 7B illustrates a diagram 710 that depicts a receiving/feedback process with a timing violation that does not impact a subsequent receiving/feedback process. FIG. 7C illustrates a diagram 720 that depicts a receiving/feedback process with a timing violation that impacts a subsequent receiving/feedback process.

[0025] More specifically, diagram 700 of FIG. 7A shows the flow of DL reception and ACK/NACK feedback. Here, the transmitter 702 (e.g., transmitting node, base station, evolved NodeB (eNB), gNodeB (gNB), etc.) sends a first data packet in subframe n and a second data packet in subframe n + 1, which are received by receiver 704 (e.g., receiving node, user equipment, etc.). The processing (at 703) of the first data packet may begin before the reception of the second data packet. A first time budget T1 is allotted for the processing of the first data packet. In the example of FIG. 7A, the receiver 704 processes the first data packet within the allotted first time budget Tl. Thus, no timing violation occurs in this example. At the end of the first time budget Tl, an ACK or a NACK is sent (at 705) to the transmitter 702 depending on whether the reception/decoding of the first data packet was successful. Then, the receiver 704 processes the second data packet within the second time budget T2. Here, the receiver 704 processes the second data packet within the second time budget T2, and hence, no timing violation occurs here either. At the end of the second time budget T2, an ACK/NACK is sent to the transmitter 702 for the second data packet.

[0026] A first example of a timing violation is depicted in the diagram 710 of FIG. 7B. Here, receiver 704 is unable to complete the data processing (at 703) for the first data packet within the first time budget Tl . Hence, a timing violation occurs in this example. However, because the timing violation does not collide with the start of the processing procedure for the second data packet, a disruption of the processing of the second data packet does not occur. However, at the end of the first time budget Tl, receiver 704 may send a NACK to transmitter 702 even when the first data packet is properly received/decoded. This is because receiver 704 is scheduled by transmitter 702 to send an ACK/NACK report at this time, which is before the completion of the processing procedure.

[0027] A second example of a timing violation is depicted in the diagram 720 of FIG. 7C. Here again, receiver 704 is unable to complete the data processing (at 703) for the first data packet within the first time budget Tl, and a timing violation occurs. In this example, however, the processing of the first data packet collides with the start of the processing procedure for the second data packet, and hence, the processing of the second data packet is skipped. Once the processing and error correction check of the first data packet is complete, receiver 704 sends an ACK/NACK report to transmitter 702.

[0028] In both timing violation scenarios of FIGs. 7B and 7B, if the time violation is not properly handled, receiver 704 may report a NACK to transmitter 702, which can lead to processing and signaling overhead in instances when the packet is properly decoded after the end of the time budget. Receiver 704 may even crash if a fallback method is not implemented. Conventional approaches address this issue by over-designing of receiver capability, e.g., namely, processors designed to meet the shorted timing requirement at the highest possible throughput. This aggressive approach employs powerful receiver processors intended to meet worst-case scenario timing violations, which may rarely occur in real-life scenarios. The use of these processors can lead to an undesirable and often unnecessary drain of the receiver’ s power reserves. Moreover, manufacturing processors of such power and complexity comes at great expense, but with little to no performance improvement visible to the user. Still further, even though these conventional processors are designed for worst-case scenarios, there may be unforeseeable situations that cause even longer processing times than those considered in the design phase of these powerful processors. When this happens, conventional approaches lack a mechanism to provide a remedy to these unforeseen timing violations. This causes calls to be dropped, receiver systems to crash, negative throughput, and/or other random consequences that negatively impact device performance and user experience.

[0029] Thus, there exists an unmet need for a mechanism that can correct timing violations, both foreseeable and unforeseeable, without the use of these powerful, complex, and expensive processors.

[0030] To overcome these and other timing violation challenges, the present disclosure provides a software enhancement feature that can properly handle all timing violation scenarios without negatively impacting performance, power, and manufacturing cost. For example, the present disclosure provides a software module that determines whether to abort or continue processing of a current data packet when a timing violation occurs. The software module makes this determination based on a comparison of the retransmission number of the current data packet and the subsequent data packet. More specifically, when the retransmission number of the current data packet is greater than that of the subsequent data packet, the processing of the current data packet may continue until completion. Here, the processing of the subsequent data packet is skipped, and a NACK for the subsequent packet is automatically sent. This way, the transmitter retransmits the subsequent data packet to the receiver for processing/decoding so that packet drop is avoided. On the other hand, when the retransmission number of the current data packet is less than that of the subsequent packet, processing of the current packet may be aborted at the end of the time budget, and the processing of the subsequent data packet may begin. Here, a NACK may be sent for the current data packet, and the processing of the subsequent packet may begin. In other words, the retransmission number can be used to prioritize the processing of data packets. In another example, the present disclosure provides an ACK/NACK feedback scheme based on the abort/continue processing scheme described above. This way, whenever the processing of a data packet is aborted or skipped, the receiver will receive a corresponding retransmission, which may reduce the negative impact on performance or user experience. Still further, the abort/continue scheme and ACK/NACK feedback scheme can be applied to an initial transmission of a data packet or to any retransmission, which increases the probability that the receiver correctly receives/decodes data packets in the event of a timing violation. Additional details of the abovedescribed mechanisms of the present disclosure are provided below in connection with FIGs. 1-6. [0031] FIG. 1 illustrates an exemplary wireless network 100, in which some aspects of the present disclosure may be implemented, according to some embodiments of the present disclosure. As shown in FIG. 1, wireless network 100 may include a network of nodes, such as a user equipment 102, an access node 104, and a core network element 106. User equipment 102 may be any terminal device, such as a mobile phone, a desktop computer, a laptop computer, a tablet, a vehicle computer, a gaming console, a printer, a positioning device, a wearable electronic device, a smart sensor, or any other device capable of receiving, processing, and transmitting information, such as any member of a vehicle to everything (V2X) network, a cluster network, a smart grid node, or an Intemet-of-Things (loT) node. It is understood that user equipment 102 is illustrated as a mobile phone simply by way of illustration and not by way of limitation.

[0032] Access node 104 may be a device that communicates with user equipment 102, such as a wireless access point, a base station (BS), a Node B, an enhanced Node B (eNodeB or eNB), a next-generation NodeB (gNodeB or gNB), a cluster master node, or the like. Access node 104 may have a wired connection to user equipment 102, a wireless connection to user equipment 102, or any combination thereof. Access node 104 may be connected to user equipment 102 by multiple connections, and user equipment 102 may be connected to other access nodes in addition to access node 104. Access node 104 may also be connected to other user equipments. When configured as a gNB, access node 104 may operate in millimeter wave (mmW) frequencies and/or near mmW frequencies in communication with the user equipment 102. When access node 104 operates in mmW or near mmW frequencies, the access node 104 may be referred to as an mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in the band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW or near mmW radio frequency band have extremely high path loss and a short range. The mmW base station may utilize beamforming with user equipment 102 to compensate for the extremely high path loss and short range. It is understood that access node 104 is illustrated by a radio tower by way of illustration and not by way of limitation.

[0033] Access nodes 104, which are collectively referred to as E-UTRAN in the evolved packet core network (EPC) and as NG-RAN in the 5G core network (5GC), interface with the EPC and 5GC, respectively, through dedicated backhaul links (e.g., SI interface). In addition to other functions, access node 104 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. Access nodes 104 may communicate directly or indirectly (e.g., through the 5GC) with each other over backhaul links (e.g., X2 interface). The backhaul links may be wired or wireless.

[0034] Core network element 106 may serve access node 104 and user equipment 102 to provide core network services. Examples of core network element 106 may include a home subscriber server (HSS), a mobility management entity (MME), a serving gateway (SGW), or a packet data network gateway (PGW). These are examples of core network elements of an evolved packet core (EPC) system, which is a core network for the LTE system. Other core network elements may be used in LTE and in other communication systems. In some embodiments, core network element 106 includes an access and mobility management function (AMF), a session management function (SMF), or a user plane function (UPF) of the 5GC for the NR system. The AMF may be in communication with a Unified Data Management (UDM). The AMF is the control node that processes the signaling between the user equipment 102 and the 5GC. Generally, the AMF provides quality-of-service (QoS) flow and session management. All user Internet protocol (IP) packets are transferred through the UPF. The UPF provides UE IP address allocation as well as other functions. The UPF is connected to the IP Services. The IP Services may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services. It is understood that core network element 106 is shown as a set of rack-mounted servers by way of illustration and not by way of limitation. [0035] Core network element 106 may connect with a large network, such as the Internet 108, or another Internet Protocol (IP) network, to communicate packet data over any distance. In this way, data from user equipment 102 may be communicated to other user equipments connected to other access points, including, for example, a computer 110 connected to Internet 108, for example, using a wired connection or a wireless connection, or to a tablet 112 wirelessly connected to Internet 108 via a router 114. Thus, computer 110 and tablet 112 provide additional examples of possible user equipments, and router 114 provides an example of another possible access node. [0036] A generic example of a rack-mounted server is provided as an illustration of core network element 106. However, there may be multiple elements in the core network including database servers, such as a database 116, and security and authentication servers, such as an authentication server 118. Database 116 may, for example, manage data related to user subscription to network services. A home location register (HLR) is an example of a standardized database of subscriber information for a cellular network. Likewise, authentication server 118 may handle authentication of users, sessions, and so on. In the NR system, an authentication server function (AUSF) device may be the entity to perform user equipment authentication. In some embodiments, a single server rack may handle multiple such functions, such that the connections between core network element 106, authentication server 118, and database 116, may be local connections within a single rack.

[0037] Each element in FIG. 1 may be considered a node of wireless network 100. More detail regarding the possible implementation of a node is provided by way of example in the description of a node 600 in FIG. 6. Node 600 may be configured as user equipment 102, access node 104, or core network element 106 in FIG. 1. Similarly, node 600 may also be configured as computer 110, router 114, tablet 112, database 116, or authentication server 118 in FIG. 1. As shown in FIG. 6, node 600 may include a processor 602, a memory 604, and a transceiver 606. These components are shown as connected to one another by a bus, but other connection types are also permitted. When node 600 is user equipment 102, additional components may also be included, such as a user interface (UI), sensors, and the like. Similarly, node 600 may be implemented as a blade in a server system when node 600 is configured as core network element 106. Other implementations are also possible.

[0038] Transceiver 606 may include any suitable device for sending and/or receiving data. Node 600 may include one or more transceivers, although only one transceiver 606 is shown for simplicity of illustration. An antenna 608 is shown as a possible communication mechanism for node 600. Multiple antennas and/or arrays of antennas may be utilized for receiving multiple spatially multiplex data streams. Additionally, examples of node 600 may communicate using wired techniques rather than (or in addition to) wireless techniques. For example, access node 104 may communicate wirelessly to user equipment 102 and may communicate by a wired connection (for example, by optical or coaxial cable) to core network element 106. Other communication hardware, such as a network interface card (NIC), may be included as well.

[0039] As shown in FIG. 6, node 600 may include processor 602. Although only one processor is shown, it is understood that multiple processors can be included. Processor 602 may include microprocessors, microcontroller units (MCUs), digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout the present disclosure. Processor 602 may be a hardware device having one or more processing cores. Processor 602 may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Software can include computer instructions written in an interpreted language, a compiled language, or machine code. Other techniques for instructing hardware are also permitted under the broad category of software. [0040] As shown in FIG. 6, node 600 may also include memory 604. Although only one memory is shown, it is understood that multiple memories can be included. Memory 604 can broadly include both memory and storage. For example, memory 604 may include random-access memory (RAM), read-only memory (ROM), static RAM (SRAM), dynamic RAM (DRAM), ferroelectric RAM (FRAM), electrically erasable programmable ROM (EEPROM), compact disc readonly memory (CD-ROM) or other optical disk storage, hard disk drive (HDD), such as magnetic disk storage or other magnetic storage devices, Flash drive, solid-state drive (SSD), or any other medium that can be used to carry or store desired program code in the form of instructions that can be accessed and executed by processor 602. Broadly, memory 604 may be embodied by any computer-readable medium, such as a non-transitory computer-readable medium.

[0041] Processor 602, memory 604, and transceiver 606 may be implemented in various forms in node 600 for performing wireless communication functions. In some embodiments, processor 602, memory 604, and transceiver 606 of node 600 are implemented (e.g., integrated) on one or more system-on-chips (SoCs). In one example, processor 602 and memory 604 may be integrated on an application processor (AP) SoC (sometimes known as a “host,” referred to herein as a “host chip”) that handles application processing in an operating system (OS) environment, including generating raw data to be transmitted. In another example, processor 602 and memory 604 may be integrated on a baseband processor (BP) SoC (sometimes known as a “modem,” referred to herein as a “baseband chip”) that converts the raw data, e.g., from the host chip, to signals that can be used to modulate the carrier frequency for transmission, and vice versa, which can run a real-time operating system (RTOS). In still another example, processor 602 and transceiver 606 (and memory 604 in some cases) may be integrated on an RF SoC (sometimes known as a “transceiver,” referred to herein as an “RF chip”) that transmits and receives RF signals with antenna 608. It is understood that in some examples, some or all of the host chip, baseband chip, and RF chip may be integrated as a single SoC. For example, a baseband chip and an RF chip may be integrated into a single SoC that manages all the radio functions for cellular communication.

[0042] Referring back to FIG. 1, in some embodiments, user equipment 102 may be configured to properly handle all timing violation scenarios without negatively impacting performance, power, and manufacturing cost. This is because user equipment 102 employs the software enhancement feature of the present disclosure rather than the complex processors of conventional wireless devices. For example, user equipment 102 may include one or more modules that determine whether to abort or continue the processing of a current data packet when a timing violation occurs. Here, user equipment 102 makes this determination based on a comparison of the retransmission number of the current data packet and the subsequent data packet. More specifically, when the retransmission number of the current data packet is greater than that of the subsequent data packet, user equipment 102 may continue processing the current data packet until completion. In this example, user equipment 102 may skip the subsequent data packet, and a NACK for the subsequent packet may be automatically sent. This way, access node 104 retransmits the subsequent data packet to user equipment 102 for processing/decoding, so that packet drop is avoided. On the other hand, when the retransmission number of the current data packet is less than that of the subsequent packet, user equipment 102 may abort processing the current packet at the end of the time budget, and the processing of the subsequent data packet may begin. In this example, a NACK may be sent for the current data packet, and the processing of the subsequent packet may begin. In other words, the retransmission number can be used by user equipment 102 to prioritize the processing of data packets. In another example, user equipment 102 may perform an ACK/NACK feedback scheme based on the determination of the abort/continue processing scheme described above. This way, when the processing of a data packet is aborted or skipped, user equipment 102 will receive a corresponding retransmission, which may increase performance and user experience. Still further, the abort/continue scheme and ACK/NACK feedback scheme can be applied to an initial transmission of a data packet or to any retransmission, which increases the probability that user equipment 102 correctly receives/decodes data packets in the event of a timing violation. Additional details of each of these schemes are provided below in connection with FIGs. 2-5.

[0043] FIG. 2 illustrates a block diagram of an apparatus 200 including a baseband chip 202, an RF chip 204, and a host chip 206, according to some embodiments of the present disclosure. Apparatus 200 may be implemented as user equipment 102 of wireless network 100 in FIG. 1. As shown in FIG. 2, apparatus 200 may include baseband chip 202, RF chip 204, host chip 206, and one or more antennas 210. In some embodiments, baseband chip 202 is implemented by processor 602 and memory 604, and RF chip 204 is implemented by processor 602, memory 604, and transceiver 606, as described above with respect to FIG. 6. Besides the on-chip memory 218 (also known as “internal memory,” e.g., registers, buffers, or caches) on each chip 202, 204, or 206, apparatus 200 may further include an external memory 208 (e.g., the system memory or main memory) that can be shared by each chip 202, 204, or 206 through the system/main bus. Although baseband chip 202 is illustrated as a standalone SoC in FIG. 2, it is understood that in one example, baseband chip 202 and RF chip 204 may be integrated as one SoC; in another example, baseband chip 202 and host chip 206 may be integrated as one SoC; in still another example, baseband chip 202, RF chip 204, and host chip 206 may be integrated as one SoC, as described above.

[0044] In the uplink, host chip 206 may generate raw data and send it to baseband chip 202 for encoding, modulation, and mapping. Interface 214 of baseband chip 202 may receive the data from host chip 206. Baseband chip 202 may also access the raw data generated by host chip 206 and stored in external memory 208, for example, using the direct memory access (DMA). Baseband chip 202 may first encode (e.g., by source coding and/or channel coding) the raw data and modulate the coded data using any suitable modulation techniques, such as multi-phase shift keying (MPSK) modulation or quadrature amplitude modulation (QAM). Baseband chip 202 may perform any other functions, such as symbol or layer mapping, to convert the raw data into a signal that can be used to modulate the carrier frequency for transmission. In the uplink, baseband chip 202 may send the modulated signal to RF chip 204 via interface 214. RF chip 204, through the transmitter, may convert the modulated signal in the digital form into analog signals, i.e., RF signals, and perform any suitable front-end RF functions, such as filtering, digital pre-distortion, up-conversion, or sample-rate conversion. Antenna 210 (e.g., an antenna array) may transmit the RF signals provided by the transmitter of RF chip 204.

[0045] In the downlink, antenna 210 may receive RF signals from an access node or other wireless device. The RF signals may be passed to the receiver (Rx) of RF chip 204. RF chip 204 may perform any suitable front-end RF functions, such as filtering, IQ imbalance compensation, down-paging conversion, or sample-rate conversion, and convert the RF signals (e.g., transmission) into low-frequency digital signals (baseband signals) that can be processed by baseband chip 202.

[0046] As seen in FIG. 2, baseband chip 202 may include first, second, and third time violation management blocks 220a, 220b, 220c. In some embodiments, each of these blocks may be implemented using software (e.g., such as separate processors), firmware (e.g., such as separate microcontrollers), or hardware (e.g., separate circuits). In some other embodiments, two or more of these time violation management blocks may be combined into the same processing unit.

[0047] First time violation management block 220a may be configured to perform the abort/continue processing scheme described below in connection with FIG. 3. For example, first time violation management block 220a may be configured to determine whether to abort or continue the processing of a current data packet when a timing violation occurs. Here, first time violation management block 220a may make this determination based on a comparison of the retransmission number of the current data packet and the subsequent data packet. More specifically, when the retransmission number of the current data packet is greater than that of the subsequent data packet, first time violation management block 220a may continue processing the current data packet until completion. In this example, first time violation management block 220a may skip the subsequent data packet, and a NACK for the subsequent packet may be automatically sent by second time violation management block 220b. This way, access node 104 retransmits the subsequent data packet to apparatus 200 for processing/decoding so that packet drop is avoided. On the other hand, when the retransmission number of the current data packet is less than that of the subsequent packet, first time violation management block 220a may abort processing the current packet at the end of the time budget. In this example, a NACK may be sent by second time violation management block 220b for the current data packet, and the processing of the subsequent packet by first time violation management block 220a may begin. In other words, the retransmission number can be used by first time violation management block 220a to prioritize the processing of data packets.

[0048] Second time violation management block 220b may be configured to perform an ACK/NACK feedback scheme (see FIG. 4) based on the determination of the abort/continue processing scheme performed by first time violation management block 220a. This way, whenever the processing of a data packet is aborted or skipped, the apparatus may receive a corresponding retransmission, which may reduce the negative impact on performance or user experience.

[0049] Third time violation management block 220c may be configured to perform a retransmission scheme (see FIG. 5) based on the outcome of the abort/continue scheme and/or ACK/NACK scheme. In other words, the abort/continue scheme and ACK/NACK feedback scheme can be applied to an initial transmission of a data packet but also to any retransmission, which increases the probability that the apparatus correctly receives/decodes data packets in the event of a timing violation. Additional details of the abort/continue processing scheme, ACK/NACK feedback scheme, and handling of retransmission schemes are provided below in connection with FIGs. 3-5.

[0050] FIG. 3 illustrates a flow chart of an exemplary abort/continue processing mechanism 300 in the event of a DL processing timing violation, according to some embodiments of the present disclosure. FIG. 4 illustrates a flow chart of an exemplary ACK/ NACK reporting mechanism 400 in the event of a DL processing timing violation, according to some embodiments of the present disclosure. FIG. 5 illustrates a flow chart of an exemplary retransmission processing mechanism 500 in the event of a DL processing timing violation, according to some embodiments of the present disclosure.

[0051] Each of the exemplary abort/continue processing mechanism 300 of FIG. 3, the exemplary ACK/NACK feedback mechanism 400 of FIG. 4, and the exemplary retransmission processing mechanism 500 of FIG. 5 may be performed by a receiver. The receiver may include one or more of, e.g., user equipment 102, apparatus 200, baseband chip 202, first time violation management block 220a, second time violation management block 220b, and/or third time violation management block 220c. It is to be appreciated that some of the steps may be optional, and some of the steps may be performed simultaneously, or in a different order than shown in FIGs. 3-5. FIGs. 3-5 will be described together. [0052] Referring to FIG. 3, at 302, the receiver may receive a first data packet and a second data packet. The first data packet may be received in a first subframe, and the second data packet may be received in a second subframe subsequent to the first subframe.

[0053] At 304, the receiver may determine a transmission granularity of the first subframe and/or the second subframe. Using the first data packet as an example, the transmission granularity may indicate whether the first data packet should be decoded as a whole packet or in multiple code blocks. When decoded as a whole packet, the receiver may perform a single error correction check (e.g., cyclic redundancy check (CRC)) for the entire data packet once the decoding has been performed. Here, only a single ACK/NACK is feedback to the transmitter for the entire data packet. On the other hand, when decoded in multiple code blocks, the receiver may perform a different error correction check for each of the code blocks. In the code block example, a different ACK/NACK report may be returned to the transmitter for each of the code blocks, or a single ACK/NACK report including the ACK/NACK for each of the code blocks may be sent. Then, for either transmission granularity type, the receiver may perform first processing (e.g., decoding) of the first data packet during a first time budget.

[0054] With respect to the whole packet granularity type, and in response to determining that the first processing of the first data packet will exceed the first time budget, the receiver may determine (at 306) whether the retransmission number of the second data packet is greater than the retransmission number of the first data packet. In other words, the receiver may prioritize the processing of the data packet with the highest retransmission number. For example, when the retransmission number of the second data packet is greater than that of the first data packet, the receiver may abort (at 308) the first processing of the first data packet at the end of the first time budget (referred to herein as “Case A”) As seen in FIG. 4, at 404, the receiver may send a NACK for the first data packet in response to aborting (at 308) the first processing of the first data packet. Referring again to FIG. 3, at 310, the receiver may begin second processing at the second data packet after the end of the first time budget.

[0055] Conversely, in response to determining that the first processing of the first data packet will exceed the first time budget, and further in response to determining (at 306) that the retransmission number of the first data packet is higher than the second data packet, the receiver may continue (at 312) the first processing of the first data packet until its completion (referred to herein as “Case B”). As seen in FIG. 4, at 408, the receiver may determine whether a hybridautomatic repeat request (HARQ) report (e.g., ACK/NACK feedback) for the first data packet is due with the transmitter while the first processing is ongoing. In other words, the receiver may determine (at 408) whether a HARQ report is due before the error correction check (e.g., CRC) of the first data packet has been performed/completed. The due time of the HARQ report may be preconfigured based on messaging (e.g., radio resource control (RRC) messaging) from the transmitter, for example.

[0056] In response to determining (at 408) that the HARQ report is due with the transmitter prior to the completion of the first processing, the receiver may send (at 410) a NACK for the first data packet at its due time. Otherwise, when a HARQ report is not due while the first processing is ongoing, the receiver may send (at 412) an ACK or a NACK at the end of the first processing, depending on the outcome of the CRC.

[0057] Referring again to FIG. 3, the receiver may skip (at 314) the second processing of the second data packet when the first processing extends into (e.g., will collide with) the second time budget allotted for the second processing of the second data packet. Referring to FIG. 4, because the second processing of the second packet was skipped (at 314), the receiver may transmit (at 414) a NACK for the second data packet.

[0058] In some embodiments, in response to determining (at 304) that the transmission granularity includes code blocks, and in response to determining that the first processing of the code blocks of the first data packet will exceed the first time budget, the receiver may process (at 316) as many code blocks at it can until the end of the first time budget. Referring again to FIG. 4, the receiver may determine (at 418) whether the ACK/NACK feedback is for the entire first data packet that includes an ACK/NACK for each code block in a single transmission or whether an ACK/NACK is sent individually for each code block. When a single ACK/NACK report is sent, the receiver may transmit (at 420) a NACK since all of the code blocks have not been processed by the end of the first time budget. On the other hand, the receiver may transmit (at 422) an ACK or a NACK for each code block that was processed before the end of the first time budget. The receiver may transmit (at 422) a NACK for each code block that was not processed before the end of the first time budget.

[0059] When the receiver sends (at 404) a NACK for the first data packet after aborting (at 308) the first processing of the first data packet, a retransmission of the first data packet may be sent by the transmitter. Referring to FIG. 5, by way of one example, the retransmission may be handled using the abort/continue process (at 520) seen in FIG. 3.

[0060] When the receiver sends (at 410) a NACK for the first data packet in response to a HARQ report being due prior to the completion of the first processing, a retransmission of the first data packet may be sent by the transmitter. Again, the NACK is sent (at 410) because the CRC check had not been performed prior to the due time of the HARQ report. Here, when the retransmission is received, the receiver may determine (at 510) whether the CRC check passed or failed for the first data packet. In response to determining that the CRC check passed, the receiver may skip processing the retransmission and send (at 512) an ACK to the transmitter. Conversely, in response to determining that the CRC check did not pass, the operation may move to 306 and proceed according to the abort/continue process for either Case A (at 516) or Case B (at 518).

[0061] An illustrative example of the processes of FIGs. 3-5 is provided below in connection with Table 1. Table 1 illustrates an example when the whole packet is encoded together (Case A or Case B). The packets are assumed to arrive consecutively one after another in each slot (or subframe), and a collision happens between the processing of the current and the next data packet. It is also assumed the receiver will immediately report the ACK/NACK results to the transmitter when the end of the time budget is reached.

Table 1

[0062] As seen in Table 1, in slot 0, the first data packet of HARQ process 0 arrives. The processing of the first data packet continues into slot 1 with a CRC check pass. However, a NACK is reported to the transmitter at the end of the time budget.

[0063] In slot 1, a second data packet of HARQ process 1 arrives. The processing of the second data packet is skipped to allow for the processing of the first data packet of slot 0.

[0064] In slot 2, the same data packet as the first data packet of slot 0 is retransmitted. Here, the receiver skips the data processing of the retransmission, and an ACK for the retransmission is sent to the transmitter.

[0065] In slot 3, the same data packet as the second data packet in slot 1 is retransmitted. The receiver reports NACK even though the CRC check passes after the end of the first time budget.

[0066] In slot 4, a third data packet of HARQ process 0 arrives at the receiver. Processing of the third data packet is skipped because the processing of the second data packet exceeds the second time budget.

[0067] In slot 5, a second retransmission of the second data packet received in slot 1 is retransmitted. Here, the receiver skips the processing of the second retransmission, and an ACK is reported to the transmitter. This is because the first retransmission of the second data packet was successfully decoded after slot 3.

[0068] Thus, the techniques described above in connection with FIGs. 3-5 how the receiver of the present disclosure can properly handle all timing violation scenarios without negatively impacting performance, power, and manufacturing cost, as compared to the complex processors of known approaches.

[0069] In various aspects of the present disclosure, the functions described herein may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or encoded as instructions or code on a non-transitory computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computing device, such as node 600 in FIG. 6. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, HDD, such as magnetic disk storage or other magnetic storage devices, Flash drive, SSD, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a processing system, such as a mobile device or a computer. Disk and disc, as used herein, includes CD, laser disc, optical disc, DVD, and floppy disk where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0070] According to one aspect of the present disclosure, an apparatus for wireless communication of a receiver (e.g., user equipment) is provided. The apparatus may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to receive, from a transmitter, a first packet in a first subframe and a second packet in a second subframe. The at least one processor may be configured to perform a first processing of the first packet during a first time budget associated with the first packet. The at least one processor may be configured to determine that the first processing of the first packet will exceed the first time budget. The at least one processor may be configured to determine that a first retransmission number associated with the first packet is less than a second retransmission number associated with the second packet in response to determining that the first processing of the first packet will exceed the first time budget. The at least one processor may be configured to abort the first processing of the first packet at an end of the first time budget in response to determining that the first retransmission number associated with the first packet is less than the second retransmission number associated with the second packet.

[0071] In some embodiments, the at least one processor may be further configured to complete the first processing of the first packet by exceeding the first time budget in response to determining that the first retransmission number associated with the first packet is greater than the second retransmission number associated with the second packet.

[0072] In some embodiments, the at least one processor may be further configured to send a NACK associated with the first packet when the first processing is aborted at the end of the first time budget. In some embodiments, the at least one processor may be further configured to perform second processing of the second packet during a second time budget when the first processing of the first packet is aborted at the end of the first time budget.

[0073] In some embodiments, the at least one processor may be further configured to determine that the first processing will collide with a second time budget associated with the second packet when the first processing is completed by exceeding the first time budget. In some embodiments, the at least one processor may be further configured to skip second processing of the second packet in response to determining that the first processing will collide with the second time budget.

[0074] In some embodiments, the at least one processor may be further configured to determine that a HARQ report associated with the first packet is due with the transmitter while the first processing is ongoing. In some embodiments, the at least one processor may be further configured to send a first NACK associated with the first packet and a second NACK associated with the second packet to the transmitter in response to determining that the HARQ report is due with the transmitter while the first processing is ongoing.

[0075] In some embodiments, the at least one processor may be further configured to determine that an error correction check associated with the first packet passes in response to determining that the HARQ report is not due with the transmitter while the first processing is ongoing. In some embodiments, the at least one processor may be further configured to send an ACK associated with the first packet to the transmitter when it is determined that an error correction check associated with the first packet passes. In some embodiments, the at least one processor may be further configured to send a third NACK associated with the first packet to the transmitter in response to determining that the error correction check associated with the first packet fails.

[0076] In some embodiments, the at least one processor may be further configured to determine a transmission granularity associated with the first packet. In some embodiments, the transmission granularity may indicate whole packet processing of the first packet or code block processing of the first packet. In some embodiments, the first processing of the first packet may be performed when the transmission granularity indicates the whole packet processing. In some embodiments, the at least one processor may be further configured to perform second processing of the first packet when the transmission granularity indicates code block processing of the first packet. In some embodiments, the second processing of the first packet may include processing one or more code blocks of the first packet until the end of the first time budget is reached.

[0077] In some embodiments, the at least one processor may be further configured to receive, from the transmitter, a retransmission of the first packet. In some embodiments, the at least one processor may be further configured to send an ACK associated with the first packet in response to determining that an error correction check associated with the first processing of the first packet passed.

[0078] According to another aspect of the disclosure, a method of wireless communication of a receiver is provided. The method may include receiving, from a transmitter, a first packet in a first subframe and a second packet in a second subframe. The method may include performing first processing of the first packet during a first time budget associated with the first packet. The method may include determining that the first processing of the first packet will exceed the first time budget. The method may include determining that a first retransmission number associated with the first packet is less than a second retransmission number associated with the second packet in response to determining that the first processing of the first packet will exceed the first time budget. The method may include aborting the first processing of the first packet at an end of the first time budget in response to determining that the first retransmission number associated with the first packet is less than the second retransmission number associated with the second packet.

[0079] In some embodiments, the method may further include completing the first processing of the first packet by exceeding the first time budget in response to determining that the first retransmission number associated with the first packet is greater than the second retransmission number associated with the second packet.

[0080] In some embodiments, the method may further include sending a NACK associated with the first packet when the first processing is aborted at the end of the first time budget. In some embodiments, the method may further include performing second processing of the second packet during a second time budget when the first processing of the first packet is aborted at the end of the first time budget.

[0081] In some embodiments, the method may further include determining that the first processing will collide with a second time budget associated with the second packet when the first processing is completed by exceeding the first time budget. In some embodiments, the method may further include skipping second processing of the second packet in response to determining that the first processing will collide with the second time budget.

[0082] In some embodiments, the method may further include determining that a HARQ report associated with the first packet is due with the transmitter while the first processing is ongoing. In some embodiments, the method may further include sending a first NACK associated with the first packet and a second NACK associated with the second packet to the transmitter in response to determining that the HARQ report is due with the transmitter while the first processing is ongoing.

[0083] In some embodiments, the method may further include determining that an error correction check associated with the first packet passes in response to determining that the HARQ report is not due with the transmitter while the first processing is ongoing. In some embodiments, the method may further include sending an ACK associated with the first packet to the transmitter when it is determined that an error correction check associated with the first packet passes. In some embodiments, the method may further include sending a third NACK associated with the first packet to the transmitter in response to determining that the error correction check associated with the first packet fails.

[0084] In some embodiments, the method may further include determining a transmission granularity associated with the first packet. In some embodiments, the transmission granularity may indicate whole packet processing of the first packet or code block processing of the first packet. In some embodiments, the first processing of the first packet may be performed when the transmission granularity indicates the whole packet processing. In some embodiments, the method may further include performing second processing of the first packet when the transmission granularity indicates code block processing of the first packet, wherein the second processing of the first packet includes processing one or more code blocks of the first packet until the end of the first time budget is reached.

[0085] In some embodiments, the method may further include receiving, from the transmitter, a retransmission of the first packet. In some embodiments, the method may further include sending an ACK associated with the first packet in response to determining that an error correction check associated with the first processing of the first packet passed.

[0086] According to yet another aspect of the present disclosure, anon-transitory computer- readable medium encoding instructions that, when executed by at least one processor, perform wireless communication of a receiver. The process may include receiving, from a transmitter, a first packet in a first subframe and a second packet in a second subframe. The process may include performing first processing of the first packet during a first time budget associated with the first packet. The process may include determining that the first processing of the first packet will exceed the first time budget. The process may include determining that a first retransmission number associated with the first packet is less than a second retransmission number associated with the second packet in response to determining that the first processing of the first packet will exceed the first time budget. The process may include aborting the first processing of the first packet at an end of the first time budget in response to determining that the first retransmission number associated with the first packet is less than the second retransmission number associated with the second packet.

[0087] In some embodiments, the process may further include completing the first processing of the first packet by exceeding the first time budget in response to determining that the first retransmission number associated with the first packet is greater than the second retransmission number associated with the second packet. In some embodiments, the process may further include sending a NACK associated with the first packet when the first processing is aborted at the end of the first time budget. In some embodiments, the process may further include performing second processing of the second packet during a second time budget when the first processing of the first packet is aborted at the end of the first time budget. In some embodiments, the process may further include determining that the first processing will collide with a second time budget associated with the second packet when the first processing is completed by exceeding the first time budget. In some embodiments, the process may further include skipping second processing of the second packet in response to determining that the first processing will collide with the second time budget. In some embodiments, the process may further include determining that a HARQ report associated with the first packet is due with the transmitter while the first processing is ongoing. In some embodiments, the process may further include sending a first NACK associated with the first packet and a second NACK associated with the second packet to the transmitter in response to determining that the HARQ report is due with the transmitter while the first processing is ongoing. In some embodiments, the process may further include determining that an error correction check associated with the first packet passes in response to determining that the HARQ report is not due with the transmitter while the first processing is ongoing. In some embodiments, the process may further include sending an ACK associated with the first packet to the transmitter when it is determined that an error correction check associated with the first packet passes. In some embodiments, the process may further include sending a third NACK associated with the first packet to the transmitter in response to determining that the error correction check associated with the first packet fails.

[0088] The foregoing description of the embodiments will so reveal the general nature of the present disclosure that others can, by applying knowledge within the skill of the art, readily modify and/or adapt for various applications such embodiments, without undue experimentation, without departing from the general concept of the present disclosure. Therefore, such adaptations and modifications are intended to be within the meaning and range of equivalents of the disclosed embodiments, based on the teaching and guidance presented herein. It is to be understood that the phraseology or terminology herein is for the purpose of description and not of limitation, such that the terminology or phraseology of the present specification is to be interpreted by the skilled artisan in light of the teachings and guidance. Embodiments of the present disclosure have been described above with the aid of functional building blocks illustrating the implementation of specified functions and relationships thereof. The boundaries of these functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternate boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed.

[0089] The Summary and Abstract sections may set forth one or more but not all exemplary embodiments of the present disclosure as contemplated by the inventor(s), and thus, are not intended to limit the present disclosure and the appended claims in any way.

[0090] Various functional blocks, modules, and steps are disclosed above. The arrangements provided are illustrative and without limitation. Accordingly, the functional blocks, modules, and steps may be re-ordered or combined in different ways than in the examples provided above. Likewise, certain embodiments include only a subset of the functional blocks, modules, and steps, and any such subset is permitted. The breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.