Method and apparatus for HARQ and ARQ interworking in wireless communication system
The adaptive retransmission system in 5G wireless networks optimizes HARQ and ARQ operations by predicting HARQ failures and transitioning to ARQ, addressing latency and reliability challenges for diverse communication services.
Patent Information
- Application Number
- PCT/KR2026/005809
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-05
- Filing Date
- 2026-05-04
- Publication Date
- 2026-11-12
AI Technical Summary
Existing 5G wireless communication systems face challenges in efficiently managing latency and reliability due to the inherent delays in Automatic Repeat Request (ARQ) mechanisms, which are not suited for emerging applications requiring ultra-low latency, and the inefficiencies in Hybrid Automatic Repeat Request (HARQ) processes, leading to suboptimal resource utilization and increased processing delays.
Implementing an adaptive retransmission system that integrates HARQ and ARQ by allowing the Radio Link Control (RLC) layer to predict early HARQ failures and signal the Medium Access Control (MAC) layer to halt HARQ retransmissions, transitioning to ARQ for selected packets, thereby optimizing retransmission strategies across protocol layers.
This approach enhances latency reduction and reliability by synchronizing HARQ and ARQ operations, ensuring faster and more dependable packet delivery, particularly in scenarios where HARQ is likely to fail, thus meeting the stringent requirements of next-generation communication systems.
Smart Images

Figure KR2026005809_12112026_PF_FP_ABST
Abstract
Description
METHOD AND APPARATUS FOR HARQ AND ARQ INTERWORKING IN WIRELESS COMMUNICATION SYSTEM
[0001] The present disclosure generally relates to wireless communication networks. More particularly, the present disclosure relates to a method and a system for Hybrid Automatic Repeat Request (HARQ), and Automatic Repeat Request (ARQ) interworking in beyond Fifth Generation (5G) and Sixth Generation (6G) Radio Access Networks (RAN).
[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.
[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.
[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.
[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.
[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.
[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.
[0008] The information in this section merely provides background information related to the present disclosure and may not constitute prior art(s) for the present disclosure.
[0009] In recent years, several broadband wireless technologies have been developed to meet the growing number of broadband subscribers by providing better applications and services. Second-generation (2G) wireless communication systems were initially developed to provide voice services while ensuring user mobility. Third generation (3G) wireless communication systems expanded capabilities to support both voice and data services. Fourth generation (4G) wireless communication systems or Long-Term Evolution (LTE) wireless communication systems were subsequently developed to deliver high-speed data services. However, the 4G / LTE wireless communication systems currently face resource limitations when meeting the growing demand for high-speed data services. Fifth generation (5G) wireless communication systems, also known as New Radio (NR), were developed to address these limitations by providing increased data capacity, ultra-reliability, and support for low-latency applications.
[0010] Basic Architecture of a Cellular Network. A typical cellular system comprises User Equipment (UE) communicating over a radio interface with a Radio Access Network (RAN). In 5G, the RAN is commonly realized as a Next Generation RAN (NG-RAN) composed of one or more gNodeBs (gNBs), which may be functionally split into centralized and distributed components (e.g., Centralized Unit (CU) and Distributed Unit (DU)) to optimize fronthaul / backhaul utilization and processing. Within the protocol stack, the PHY and Medium Access Control (MAC) layers handle physical transmission and scheduling; Radio Link Control (RLC) provides segmentation / reassembly and error recovery functions; Packet Data Convergence Protocol (PDCP) manages header compression, ciphering and integrity; and the Service Data Adaptation Protocol (SDAP) maps QoS flows to data radio bearers. The RAN interfaces with a Core Network (CN), which in 5G is a service-based architecture (SBA) including control-plane and user-plane functions (e.g., AMF / SMF for access and session management; UPF for user-plane forwarding). This layered architecture supports mobility, QoS, reliability, and security across heterogeneous services and spectrum.
[0011] Further, an ecosystem of connecting devices has expanded beyond traditional smartphones and mobile devices. Various wearable devices with enhanced capabilities, such as smartwatches and smart gear, have entered the ecosystem, requiring continuous connectivity. Advanced devices, for example, Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (XR) glasses demand high processing capabilities. The increasing demands for data throughput, bandwidth, and processing capabilities necessitate advancements in next-generation wireless communication systems beyond 5G and toward sixth generation (6G) systems. Additionally, industrial sensor network devices continue to become smaller and more cost-effective, extending to completely passive devices such as Ambient Internet of Things (Ambient IoT) sensors. Connectivity requirements now vary significantly across devices with different dimensions, power constraints, processing capabilities, memory capacities, and cost profiles. These diverse devices cannot provide identical services, requiring future communication technology to accommodate varied requirements while supporting an expanding range of services.
[0012] The Third Generation Partnership Project (3GPP) Release 15 New Radio (NR) technology aims to support a diverse use case. The diverse use cases include high data rates through Enhanced Mobile Broadband (eMBB), extremely low latency via Ultra-Reliable Low Latency Communication (uRLLC), and numerous connections through Massive Machine Type Communication (mMTC). Each of these service categories targets specific Key Performance Indicators (KPIs) related to throughput, latency, and connectivity, but does not address all KPIs simultaneously. Emerging immersive applications such as Extended Reality (XR), Digital Twin, and Holography require both high throughput and low latency simultaneously. Further, next-generation communication systems must also provide connectivity to machine-based applications with requirements exceeding those of human-driven communication. Given the emerging use cases, multiple communication service verticals, and strict Quality of Service (QoS) expectations, next-generation communication protocols must adapt efficiently to the diverse requirements. The Radio Access Network (RAN) architecture requires lightweight, flexible, and scalable designs, as the traditional one-model-fits-all approach may prove inadequate for 6G RAN deployments.
[0013] Further, RAN deployments must remain sustainable, power-efficient, and utilize an optimal number of resources. Processors implementing RAN protocol stacks contain significant complexity, with processing requirements dependent on the number of protocol headers to be handled. Packet processing requirements scale exponentially with increasing users, applications, and throughput demand. Processor capabilities often fail to scale proportionally with these increasing requirements. Therefore, protocol simplification is crucial for achieving higher performance and efficiently processing high-speed data.
[0014] Communication protocol stacks and RAN architectures have evolved to support the basic communication requirements. Technological and processing advancements have progressed in parallel, enabling major shifts in wireless communication. Even though applications kept on changing the basic operations supported on higher layers of the RAN architecture have always been more or less similar. The basic operations include providing in-order packet delivery, error detection and recovery, duplication elimination, and security provision. The higher layers deliver reliable, secure, in-order service for packet transfer over wireless links without interference between users. The higher layers adapt to lower-layer fluctuations and uncertainties while ensuring effective data handling. Specific higher protocol layer functionalities include identifiers, error recovery mechanisms, duplication detection, and scheduling of packets.
[0015] Communication protocols have evolved to ensure the mobility and continuity of service. Additional functionalities of the RAN architecture include data encryption through ciphering, integrity protection, and header compression. Although developed a decade after its predecessor, 5G introduced fewer changes to traditional Radio Access Protocol architecture than anticipated. Major enhancements included lower layer modifications supporting channel coding, Low-Density Parity Check (LDPC), multiple subcarriers spacing for various bandwidths, and different carrier frequencies, with minimal changes to higher layer protocols. The backbone of any Radio Access deployment is a Core Network. The Core Network underwent a significant transformation from a monolithic to a service-based architecture. A new layer, Service Data Adaptation Protocol (SDAP) is introduced in the communication protocol for managing Quality of Service mapping across different data packets.
[0016] In Layer 2 processing at the RAN, ensuring accurate packet delivery between transmitter and receiver remains critical. The communication protocol stack implements multiple verification mechanisms for packet recovery. A Medium Access Control (MAC) layer implements a Hybrid Automatic Repeat Request (HARQ) procedure to ensure reliable data transmission in 5G NR through specialized procedures. Important aspects of HARQ in NR include:
[0017] a. Error detection and correction: HARQ combines error detection through Cyclic Redundancy Check (CRC) and correction via Forward Error Correction (FEC) to ensure reliable data transmission.
[0018] b. Retransmission: If errors are detected, the receiver requests retransmission of the erroneous data.
[0019] c. Combining: The receiver combines original transmission with retransmitted data to improve decoding accuracy.
[0020] The HARQ procedures provide several benefits:
[0021] a. Improved reliability: HARQ ensures reliable data transmission even under challenging radio conditions.
[0022] b. Efficient resource utilization: HARQ minimizes unnecessary retransmissions, optimizing network resources.
[0023] Thus, HARQ plays an essential role in ensuring reliable data transmission in 5G networks, particularly for applications requiring high reliability and low latency.
[0024] The Radio Link Control (RLC) layer implements recovery mechanisms for data packets when HARQ procedures fail. Automatic Repeat Request (ARQ) in 5G RLC ensures reliable data transmission by:
[0025] a. Detecting errors in received data
[0026] b. Requesting retransmission of erroneous data
[0027] The ARQ protocol ensures data continuity and reliability but may introduce additional latency. Since ARQ activation occurs only after HARQ completion, the 5G methodology inherently duplicates recovery mechanisms and introduces additional delay in packet recovery.
[0028] Figure 1 illustrates the functionalities of different layers in the 5G New Radio (NR) protocol stack, according to an existing art. In conventional NR protocol stacks, the PHY layer handles modulation, coding, and physical transmission; the MAC layer performs scheduling, multiplexing, and HARQ-based recovery; the RLC layer manages sequencing, segmentation / reassembly, and ARQ-based recovery (in Acknowledged Mode); PDCP performs header compression, ciphering, and integrity; SDAP maps QoS to data bearers; and the RRC and core network layers ensure control signalling, mobility, and service orchestration.
[0029] In conventional protocols, Radio Link Control (RLC) is primarily responsible for packet sequence number management, packet segmentation, and recovery of lost packets in Acknowledged Mode (AM). A Medium Access Control (MAC) is responsible for scheduling, multiplexing, and recovery through the HARQ. The RLC uses the ARQ for the recovery of lost packets. The ARQ uses a selective recovery mechanism through RLC status reports that indicate missing RLC sequence numbers or segments. The MAC uses the HARQ, as a combination of Forward Error Correction (FEC) with retransmissions to enhance data reliability. The MAC uses HARQ Acknowledgement / Negative Acknowledgement (ACK / NACK) feedback from a receiver to decide on the next retransmission opportunity during different redundancy versions. If a packet is recovered during MAC retransmission, RLC recovery is not needed. However, if MAC is not able to recover after reaching maximum HARQ retransmissions, the missing packet is detected at the RLC and the RLC triggers a recovery mechanism.
[0030] Figure 2 illustrates a process flow associated with the transmission and reception of data packets in the 5G NR network, according to an existing art. The figure depicts the end-to-end workflow between a transmitter (TX) and a receiver (RX), spanning PDCP / SDAP, RLC, MAC / HARQ, and PHY layers, and shows how packets are prepared, scheduled, transmitted, verified, and, if necessary, retransmitted and recovered.
[0031] As per the existing art, in NR or 5G networks, the RLC layer at the transmitter side plays a crucial role in handling data transmission. The RLC layer receives RLC Service Data Units (SDUs) or packets from the upper Packet Data Convergence Protocol (PDCP) layer. The RLC assigns a unique Sequence Number (SN) to each packet and forwards these packets to the lower MAC layer. Based on grants received from the MAC, the MAC concatenates RLC Protocol Data Units (PDUs) and packs the PDUs into a Transport Block (TB). If the grant size is insufficient to accommodate an entire RLC PDU, segmentation occurs, and only parts of the PDU are included in the TB.
[0032] Further, at the MAC transmitter, the TB is assigned to the HARQ process and sent to a Physical (PHY) layer. The transmitter monitors ACK feedback, which is received either synchronously or asynchronously based on the HARQ configuration. If the NACK or no feedback is received, the transmitter retransmits the TB with a different Redundancy Version (RV).
[0033] Figure 3 illustrates different RVs supported for the HARQ retransmission in the 5G NR network, according to an existing art. These RVs are applied by the MAC / HARQ entity across successive retransmission opportunities.
[0034] The different RVs alter the redundancy bits to enhance data reliability. The HARQ employs incremental redundancy, where each retransmission carries a unique subset of information and parity bits, enabling the receiver to combine these transmissions for more reliable decoding. Retransmissions continue until the maximum number allowed by a control plane is reached.
[0035] Further, at the MAC receiver, the PHY or lower MAC layer calculates a Cyclic Redundancy Check (CRC) to verify the TB's integrity. If the CRC passes, the TB is forwarded to the upper layers for further processing otherwise, the NACK is sent as feedback. The receiver uses chase combining to recover erroneous parts of the TB during retransmissions and discards previous packets if a new TB is received.
[0036] Further, at the RLC receiver, out-of-order RLC PDUs may arrive due to missed or recovering transport blocks at lower layers as shown in Figure 2. Upon detecting such PDUs, the RLC initiates a t-reassembly timer. The RLC is responsible for segmentation, reassembly, and packet reordering. If the t-reassembly timer expires, the RLC generates a status report, indicating missing RLC PDUs or segments, and sends the status report to the peer transmitter. The RLC transmitter processes this report, identifies missing packets, and prepares the missing packets for retransmission at the RLC layer before delivering the packets to the MAC. The MAC prioritizes retransmissions over new transmissions. Upon receiving retransmitted RLC PDUs, the RLC receiver advances the receiver window and restarts the reordering process for any newly detected missing PDUs, maintaining continuous reporting and recovery procedures.
[0037] Additionally, the MAC and RLC layers work closely together to ensure reliable data transmission, with their functionalities deeply interconnected. When the HARQ process at the MAC layer fails to recover the TB within a configured maximum number of retransmissions, the MAC discards the TB and initiates a new transmission. Simultaneously, at the RLC layer, if a failure is detected at the receiver, the RLC requests retransmission through a status report. The RLC transmitter keeps track of how many times a specific RLC SN has been retransmitted and continues attempting retransmissions until a retransmission count reaches the maximum allowed value. If the maximum allowed value is exceeded, the RLC declares a Radio Link Failure (RLF), triggering the re-establishment of the RLC connection and initiating a fresh connection when possible. The retransmission process demonstrates the dependency of RLC's ARQ functionality on MAC's HARQ functionality.
[0038] However, there is another mode of RLC operation called Unacknowledged Mode (RLC UM), which does not support ARQ. In RLC UM, the RLC layer focuses solely on segmentation and maintaining in-order delivery to the upper layer, relying entirely on MAC's HARQ for packet recovery. Any packets lost due to lower-layer fluctuations cannot be recovered by RLC UM, resulting in packet loss. While RLC UM simplifies processing compared to RLC AM does not guarantee packet recovery. Meanwhile, MAC's HARQ operates independently of the RLC mode, employing different RVs to attempt packet recovery across all modes. With close dependencies on both recovery-related functionalities, RLC and MAC can have additional tight coupling.
[0039] Thus, the motivation in NR or 5G networks is to make use of commonalities across RLC and MAC layers. The RLC ARQ process typically waits for the MAC HARQ to complete HARQ retransmissions. For instance, in Frequency Range 1 (FR1) Time Division Duplex (TDD) configurations, HARQ retransmissions using RVs 0, 2, 3, and 1 can take approximately 15 milliseconds (ms) or more. However, emerging services like Extended Reality (XR) have packet delay budget (PDB) requirements that may fall below the 15-millisecond threshold, rendering ARQ operations ineffective. If the RLC retransmission timer is set too low (e.g., less than 15 ms), the RLC layer cannot leverage the benefits of HARQ's redundancy and recovery capabilities. As new applications and the 6G use cases demand increasingly strict latency requirements, optimizing the overall system to reduce waiting times due to processing delays becomes crucial.
[0040] Further, HARQ retransmissions are inherently faster than ARQ retransmissions, enabling quicker packet recovery. To further enhance efficiency, the reliability of HARQ retransmissions may be improved to ensure faster and more dependable recovery. However, it is important to recognize that ARQ may not be entirely eliminated, as HARQ does not guarantee 100% packet recovery in all scenarios. Therefore, supporting both ARQ and HARQ is essential. Interworking of ARQ-HARQ may be implemented for a more robust and efficient data transmission system. The combined ARQ-HARQ approach not only addresses latency challenges but also ensures reliable packet delivery in the evolving landscape of advanced network applications.
[0041] Figure 4 illustrates one or more options for sending the HARQ feedback based on a configurable time slot in the 5G NR network, according to existing arts. In the existing art, the HARQ ACK feedback timing is configured using RRC parameters, such as k1 values, as shown in Figure 4. The RRC parameters determine the timing of HARQ-ACK feedback for a HARQ transmission that has occurred before. For example, if k1=2, the HARQ feedback is sent, 2 slots later in UL resource for a DL HARQ transmission. Moreover, there are mechanisms where the Downlink Control Information (DCI) also is used to indicate dynamically the HARQ-ACK feedback timing and resource allocation. This flexibility in configuring the HARQ-ACK feedback gives ease of operation for the existing HARQ NR framework.
[0042] To implement the early failure detection, the RLC-MAC interface may require minimal updates, including the exchange of TB to PDU mapping, HARQ feedback from MAC to RLC, and an indication from the RLC layer to stop HARQ retransmissions. For downlink (DL) transmissions, all formats of Downlink (DL), and Downlink Control Information (DCI) may inform the User Equipment (UE) of the stopped retransmission action by sending a new transmission request. In the Uplink (UL), Uplink Control Information (UCI) may include a provision for a New Data Indicator (NDI), allowing the UE to ignore the HARQ ACK / NACK information received from a base station for previously transmitted packets.
[0043] Furthermore, to provision the HARQ ACK / NACK ignoring functionality, an additional Network Device Information (NDI) bit may be added to the UCI bit structure for future networks. The disclosed modifications to RLC-MAC information exchange may be implemented as proprietary solutions, with minimal impact on the specification. At the MAC layer, a condition may be added to the HARQ entity management to check whether RLC has indicated to ignore the retransmission of a specific TB. Further, various Code Block Groups (CBGs) are implemented for the specific TB at the MAC layer.
[0044] Figure 5 illustrates various CBGs for the specific TB at the MAC layer in the 5G NR network, according to an existing art. The CBG is a concept in 5G NR that facilitates efficient data transmission over Physical Downlink Shared Channel (PDSCH). When the TB is processed, it is divided into smaller segments called Code Blocks (CBs) to address the limitations of the channel coding process. The CBG is formed by grouping the Code Blocks together for transmission. The grouping allows for more efficient retransmissions in cases where errors occur during data reception. Rather than retransmitting the entire Transport Block when errors are detected, the network can retransmit only the specific CBGs that contain the failed Code Blocks. Transmitting only specific CBG enhances overall efficiency, reduces latency, and saves bandwidth. The number and size of CBGs are determined by higher-layer configurations, enabling the network to adapt based on the required reliability and throughput. CBG-based transmission is a key feature that improves the robustness and flexibility of modern wireless communication systems. Combining ARQ with other techniques such as HARQ may optimally balance reliability and latency requirements. Even when considering trends toward reduced latency and focus on ultra-reliable low-latency communications, ARQ-HARQ interworking provides significant latency benefits. The ARQ-HARQ interworking leads to a considerable improvement in networks beyond 5G and 6G. To meet latency and reliability requirements, communication protocols for modems at both a Base Station (BS) and a User Equipment (UE) must exchange specific information across the protocol hierarchy. The information exchange enables synchronized management of recovery procedures across multiple protocol layers.
[0045] Therefore, there exists a need for systems and methods to overcome one or more of the above-mentioned limitations.
[0046] The drawbacks / difficulties or the disadvantages / limitations of conventional techniques explained in the background section are just for exemplary purposes and the disclosure would never limit its scope only to such limitations. A person skilled in the art would understand that this disclosure and below mentioned description may also solve other problems or overcome the other drawbacks / disadvantages of the conventional arts which are not explicitly captured above.
[0047] This summary is provided to introduce a selection of concepts, in a simplified format, that are further described in the detailed description of the invention. This summary is neither intended to identify key or essential inventive concepts of the invention nor is it intended for determining the scope of the invention.
[0048] According to an embodiment of the present disclosure, disclosed herein is a method performed by a transceiver device in a wireless communication system. The method includes transmitting, by a Radio Link Control (RLC) layer, one or more protocol data units (PDUs) to a Medium Access Control (MAC) layer to initiate a Hybrid Automatic Repeat Request (HARQ) transmission procedure. The method further includes receiving, by the RLC layer, transmission related metrics from the MAC layer and predicting an early HARQ failure based on the received metrics. Additionally, the method includes signalling the MAC layer to halt an HARQ retransmission procedure for selected PDUs in response to the predicted early failure, receiving identification information of those PDUs for which retransmission has been skipped, and initiating an Automatic Repeat reQuest (ARQ) retransmission procedure for the corresponding PDUs.
[0049] According to an embodiment of the present disclosure, disclosed herein is a transceiver device for adaptive retransmission in a wireless communication system. The transceiver device includes a memory and at least one processor configured to implement an RLC layer and a MAC layer. The at least one processor is configured to transmit PDUs to initiate an HARQ transmission procedure, receive transmission related metrics from the MAC layer, predict an early HARQ failure based on the metrics, signal the MAC layer to halt HARQ retransmission for associated PDUs, receive identification information of skipped PDUs, and initiate an ARQ retransmission procedure for those PDUs.
[0050] To further clarify the advantages and features of the present invention, a more particular description of the invention will be rendered by reference to specific embodiments thereof, which are illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail with the accompanying drawings.
[0051] These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
[0052] Figure 1 illustrates the functionalities of different layers in a Fifth Generation (5G) New Radio (NR) protocol stack, according to an existing art;
[0053] Figure 2 illustrates a process flow associated with the transmission and reception of data packets in the 5G NR network, according to an existing art;
[0054] Figure 3 illustrates Redundancy Versions (RVs) supported for Hybrid Automatic Repeat reQuest (HARQ) retransmission in the 5G NR network, according to an existing art;
[0055] Figure 4 illustrates one or more options for sending the HARQ feedback based on a configurable time slot in the 5G NR network, according to existing arts;
[0056] Figure 5 illustrates various Code Block Groups (CBGs) for a Transport Block (TB) at a Medium Access Control (MAC) layer in the 5G NR network, according to an existing art;
[0057] Figure 6 illustrates various process flows for optimization of latency in 5G NR, according to an embodiment of the present disclosure;
[0058] Figure 7 illustrates a system for adaptive retransmission in a wireless communication system, according to an embodiment of the present disclosure;
[0059] Figure 8A illustrates a process flow of a method for adaptive retransmission in a wireless communication system, according to an embodiment of the present disclosure;
[0060] Figure 8B illustrates a process flow depicting an exchange between the RLC and the MAC for stopping ongoing HARQ retransmission, according to an embodiment of the present disclosure;
[0061] Figure 9 illustrates a process flow between an RLC and a MAC, where an adaptive retransmission module may reside within the RLC and act as the coordinating actor for cross-layer reliability decisions, according to an embodiment of the present disclosure;
[0062] Figure 10 illustrates a call-flow for a method between the RLC and the MAC, where an adaptive retransmission module may be installed inside the MAC and orchestrate upper-layer data handling for reliability, according to an embodiment of the present disclosure; and
[0063] Figure 11 illustrates the internal structural transformation of a TB when TB splitting is performed, according to an embodiment of the present disclosure.
[0064] Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have necessarily been drawn to scale.
[0065] Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.
[0066] For the purpose of promoting an understanding of the principles of the present disclosure, reference will now be made to the various embodiments and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the present disclosure is thereby intended, such alterations and further modifications in the illustrated system, and such further applications of the principles of the present disclosure as illustrated therein being contemplated as would normally occur to one skilled in the art to which the present disclosure relates.
[0067] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are explanatory of the present disclosure and are not intended to be restrictive thereof.
[0068] Whether or not a certain feature or element was limited to being used only once, it may still be referred to as "one or more features" or "one or more elements" or "at least one feature" or "at least one element." Furthermore, the use of the terms "one or more" or "at least one" feature or element do not preclude there being none of that feature or element, unless otherwise specified by limiting language including, but not limited to, "there needs to be one or more..." or "one or more elements is required."
[0069] Reference is made herein to some "embodiments." It should be understood that an embodiment is an example of a possible implementation of any features and / or elements of the present disclosure. Some embodiments have been described for the purpose of explaining one or more of the potential ways in which the specific features and / or elements of the proposed disclosure fulfil the requirements of uniqueness, utility, and non-obviousness.
[0070] Use of the phrases and / or terms including, but not limited to, "a first embodiment," "a further embodiment," "an alternate embodiment," "one embodiment," "an embodiment," "multiple embodiments," "some embodiments," "other embodiments," "further embodiment", "furthermore embodiment", "additional embodiment" or other variants thereof do not necessarily refer to the same embodiments. Unless otherwise specified, one or more particular features and / or elements described in connection with one or more embodiments may be found in one embodiment, or may be found in more than one embodiment, or may be found in all embodiments, or may be found in no embodiments. Although one or more features and / or elements may be described herein in the context of only a single embodiment, or in the context of more than one embodiment, or in the context of all embodiments, the features and / or elements may instead be provided separately or in any appropriate combination or not at all. Conversely, any features and / or elements described in the context of separate embodiments may alternatively be realized as existing together in the context of a single embodiment.
[0071] Any particular and all details set forth herein are used in the context of some embodiments and therefore should not necessarily be taken as limiting factors to the proposed disclosure.
[0072] The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such process or method. Similarly, one or more devices or sub-systems or elements or structures or components proceeded by "comprises... a" does not, without more constraints, preclude the existence of other devices or other sub-systems or other elements or other structures or other components or additional devices or additional sub-systems or additional elements or additional structures or additional components.
[0073] Embodiments of the present disclosure will be described below in detail with reference to the accompanying drawings.
[0074] Figure 6 illustrates various process flows for optimization of latency in 5G NR, according to an embodiment of the present disclosure. According to the present disclosure, the latency can be reduced by implementing Hybrid Automatic Repeat reQuest (HARQ), and Automatic Repeat reQuest (ARQ) either by the RLC or MAC. In one example, as shown by block 602, HARQ may be disabled whereas at block 604, ARQ may be disabled. Specifically, at block 602, the ARQ may be disabled. Disabling the ARQ may impact application recovery in cases where HARQ retransmissions fail. After HARQ failure no recovery mechanism may remain in place. On the other hand, at block 604, the HARQ may be disabled. When the HARQ is disabled, the recovery may continue through RLC-level retransmissions only. When the HARQ is disabled, the number of HARQ transmissions may be restricted to 1.
[0075] Alternatively, as shown by block 606, either of HARQ and ARQ may be disabled smartly. As shown at block 606, an interworking between the ARQ and the HARQ may be implemented. The RLC may identify the scenarios where the HARQ is likely to fail. The failure prediction may be based on heuristics or a threshold derived from observing parameters such as previous HARQ failure instances, rate of failure, or average failure ratio in addition to the channel conditions. If the HARQ failure ratio is high while the channel conditions are also deteriorating, HARQ is likely to fail. A manner in which each block is implemented is explained with respect to Figure 7 onwards by a system 700.
[0076] Figure 7 illustrates a system 700 for adaptive retransmission in a wireless communication system, according to an embodiment of the present disclosure. The system 700 may include a memory 710, a processor 720, a communicator 730, and a notification management module 740. In one or more embodiments, the system 101 may be implemented on one or multiple electronic devices (not shown in FIG. 2). The system may include the RLC 702 and the MAC 704. The system may be implemented in a network entity, a network device, or a transceiver device.
[0077] In an embodiment, the memory 710 stores instructions to be executed by the processor 720 for handling one or more notifications within the IMS architecture, as discussed throughout the disclosure. The memory 710 may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory 710 may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory 710 is non-movable. In some examples, the memory 710 can be configured to store larger amounts of information than the memory. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache). The memory 710 can be an internal storage unit, or it can be an external storage unit, a cloud storage, or any other type of external storage.
[0078] The processor 720 communicates with the memory 710, the communicator 730, and the notification management module 740. The processor 720 is configured to execute instructions stored in the memory 710 and to perform various processes for handling the one or more notifications within the IMS architecture, as discussed throughout the disclosure. The processor 720 may include one or a plurality of processors, maybe a general-purpose processor, such as a Central Processing Unit (CPU), an Application Processor (AP), or the like, a graphics-only processing unit such as a Graphics Processing Unit (GPU), a Visual Processing Unit (VPU), and / or an Artificial intelligence (AI) dedicated processor such as a Neural Processing Unit (NPU).
[0079] The communicator 730 is configured for communicating internally between internal hardware components and with external devices (e.g., server) via one or more networks (e.g., radio technology). The communicator 730 includes an electronic circuit specific to a standard that enables wired or wireless communication.
[0080] In one or more embodiments, the adaptive retransmission module 740 is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.
[0081] In one example, the adaptive retransmission module 740 may be adapted to perform steps. For instance, the adaptive retransmission module 740 may be adapted to actuate the RLC to send one or more RLC PDUs to the MAC for forming a transport block (TB).
[0082] The adaptive retransmission module 740 may further be adapted to facilitate the MAC in sharing transmission-related information, such as average HARQ failure statistics, Reference Signal Received Power (RSRP), or other channel-quality metrics, with the RLC. Based on the received information, the adaptive retransmission module 740 may enable the RLC to predict a likelihood of HARQ failure.
[0083] Several techniques may be employed by the adaptive retransmission module 740 to support HARQ failure prediction. The prediction logic is not limited to the above-mentioned techniques and may leverage any suitable algorithm, heuristic method, statistical model, or machine-learning-based technique depending on network requirements. The type of information exchanged between the layers is also not limited to specific parameters and may include any data that enhances the accuracy of HARQ failure prediction.
[0084] When the adaptive retransmission module 740 determines that the HARQ process is likely to fail, it may be adapted to actuate the RLC to signal the MAC to stop the ongoing HARQ retransmission. The module may also be adapted to enable the MAC to report back identification details of the PDUs for which retransmissions have been skipped, allowing the RLC to prepare those PDUs for ARQ-based retransmissions.
[0085] In certain embodiments, the adaptive retransmission module 740 may further support scenarios in which the MAC layer forces an additional HARQ retransmission based on prevailing recovery conditions.
[0086] A manner in which the adaptive retransmission module 740 operates will now be explained with respect to Figures 8A and 8B.
[0087] Specifically, Figure 8A illustrates a process flow of a method 800A for adaptive retransmission in a wireless communication system, according to an embodiment of the present disclosure. The method 800 depicts coordinated interactions between the Radio Link Control (RLC) layer and the Medium Access Control (MAC) layer, controlled via an adaptive retransmission module 740 to optimize retransmission behaviour.
[0088] The order in which the method steps are described below is not intended to be construed as a limitation, and any number of the described method steps can be combined in any appropriate order to execute the method or an alternative method. Additionally, individual steps may be deleted from the method without departing from the spirit and scope of the subject matter described herein.
[0089] The method 800A can be performed by programmed computing devices, for example, based on instructions retrieved from non-transitory computer readable media. The computer readable media can include machine-executable or computer-executable instructions to perform all or portions of the described method. The computer readable media may be, for example, digital memories, magnetic storage media, such as magnetic disks and magnetic tapes, hard drives, or optically readable data storage media.
[0090] In one example, the method 800A may be performed partially or completely by the system 700 shown in Figure 7.
[0091] At step 802, the adaptive retransmission module 740 may actuate the RLC layer of the transceiver device to transmit one or more protocol data units (PDUs) to the MAC layer to initiate a Hybrid Automatic Repeat Request (HARQ) transmission procedure. As depicted in Figure 8A, the RLC provides the PDUs to the MAC for subsequent transport block formation and HARQ processing.
[0092] At step 804, the adaptive retransmission module 740 may enable the RLC layer to receive one or more transmission-related metrics from the MAC layer. Figure 8A shows the MAC conveying HARQ statistics, channel-quality feedback, or similar parameters indicative of ongoing transmission performance.
[0093] At step 806, the adaptive retransmission module 740 may facilitate the RLC layer in predicting an early HARQ failure based on the received transmission-related metrics. Figure 8A reflects this predictive decision, during which the RLC analyses the metrics to anticipate whether continued HARQ retransmissions are likely to be ineffective.
[0094] At step 808, after predicting a likely HARQ failure, the adaptive retransmission module 740 may actuate the RLC layer to signal the MAC layer to halt the HARQ retransmission procedure for PDUs mapped to the relevant HARQ instance. As illustrated in Figure 8A, this halt instruction is transmitted from the RLC to the MAC to prevent further HARQ attempts.
[0095] At step 810, the adaptive retransmission module 740 may enable the RLC layer to receive identification information from the MAC layer corresponding to the PDUs for which HARQ retransmission has been skipped. Figure 8A depicts this reporting from MAC back to RLC, which identifies the affected PDUs.
[0096] At step 812, the adaptive retransmission module 740 may actuate the RLC layer to initiate an Automatic Repeat reQuest (ARQ) retransmission procedure for the PDUs identified by the MAC as skipped. As shown in Figure 8A, this action transitions recovery responsibility from HARQ at the MAC layer to ARQ at the RLC layer.
[0097] A detailed explanation of the aforementioned process will now be explained with respect to Figure 8B.
[0098] Figure 8B illustrates a process flow 800B depicting an exchange between the RLC 702 and the MAC 704, for stopping ongoing HARQ retransmission, according to an embodiment of the present disclosure. As may be understood, the processes implemented in the process flow 800B are identical to steps in method 800A.
[0099] At step 802, the adaptive retransmission module 740 may enable the RLC 702 to transmit one or more PDUs to the MAC 704 to initiate a Hybrid Automatic Repeat Request (HARQ) transmission procedure. This initial handoff is shown as an arrow from the RLC 702 to the MAC 704, marking the beginning of the lower-layer delivery chain.
[0100] A HARQ transmission procedure may refer to the process of sending an initial transport block (TB) over the wireless medium with an expectation of timely feedback from the receiver. Each TB may be linked to a specific HARQ process managed by the MAC 704, enabling parallel, pipelined transmissions.
[0101] At step 804, after receiving the PDUs, the MAC 704 may generate one or more TBs by segmenting or concatenating the PDUs in accordance with scheduling and coding requirements. This preparation may ensure compatibility with the physical layer's modulation, coding scheme, and resource allocations.
[0102] Following TB formation, the MAC 704 may assign each TB to a designated HARQ process. This association may allow the MAC 704 to maintain state for each process, including redundancy version (RV) counters, maximum retransmission limits, and timer management for expected feedback intervals.
[0103] Once TBs are assigned, the MAC 704 may forward them to the physical layer for over-the-air transmission. This transition can be shown in the call-flow as an outward arrow from the MAC 704, representing the point at which TBs enter the radio interface for delivery.
[0104] The HARQ framework may rely on rapid feedback in the form of acknowledgments (ACKs) or negative acknowledgments (NACKs). An ACK may indicate that the receiver successfully decoded the TB without requiring additional redundancy, whereas a NACK may convey that decoding failed and that a retransmission could be needed.
[0105] A HARQ retransmission procedure may commence upon receipt of a NACK or failure to decode within a specified interval. The MAC 704 may dispatch subsequent transmissions using predefined redundancy versions to provide additional coded bits, improving the chance of successful decoding on the next attempt.
[0106] An important feature of HARQ is soft combining at the receiver, in which soft bits or log-likelihood information from multiple transmissions of the same TB may be combined. Chase combining may reuse identical coded bits, while incremental redundancy may deliver additional parity bits, both allowing the receiver's soft buffer to strengthen the decoding attempt.
[0107] Despite the benefits of soft combining, certain conditions such as deep fades, mobility-induced channel variation, or interference spikes may reduce the effectiveness of repeated HARQ attempts. Under such circumstances, continuing retransmissions could provide marginal improvement while consuming significant radio resources.
[0108] To anticipate such scenarios, the MAC 704 may monitor the ratio of NACKs over a given observation period. This NACK ratio, calculated for one or more HARQ processes, may indicate whether retransmissions appear to be converging toward success or diverging toward failure.
[0109] In addition to monitoring NACK ratios, the MAC 704 may observe link-quality indicators relevant to downlink and uplink operation. These may include Channel Quality Indicator (CQI), Rank Indicator (RI), Precoding Matrix Indicator (PMI), and receiver Block Error Rate (BLER), each offering insight into instantaneous and long-term channel behaviour.
[0110] A relationship may often be present between NACK trends and link-indicator movement. For example, a sustained increase in NACKs may coincide with a drop in CQI, or a sudden shift in RI / PMI may correlate with higher BLER, suggesting reduced spatial or precoding efficiency.
[0111] Based on this context, the MAC 704 may detect anomalies that signal emerging channel degradation, such as unexpected RI changes, PMI jumps, BLER spikes, or sudden CQI drops. These anomaly flags can serve as early-warning triggers that supplement the NACK-ratio analysis. The MAC 704 may also apply filtering or smoothing functions to avoid unnecessary alarms caused by short-term fluctuations. Conditions may need to persist or reach severity thresholds before being treated as indications of likely HARQ difficulty. Using the NACK-ratio behaviour and the identified anomalies, the MAC 704 may generate transmission-related metrics representing the overall reliability of the link. Such metrics may include a NACK-ratio trend index, a CQI degradation score, an RI / PMI variance measure, or a BLER severity index.
[0112] The MAC 704 may additionally compute a composite risk indicator that integrates relevant features including residual HARQ redundancy availability and estimated soft-buffer advantages at the receiver into a single predicted-risk value for ongoing HARQ processes. Upon generating these metrics, the MAC 704 may transmit them to the RLC 702. The upward arrow in the call-flow may indicate this transfer, equipping the adaptive retransmission module 740 with the necessary data to assess the viability of continuing with HARQ retransmissions.
[0113] At step 806, the adaptive retransmission module 740 may normalize and align the received metrics with their corresponding HARQ processes and mapped RLC PDUs. This alignment may include matching timestamps, process identifiers, and PDU associations for coherent decision-making.
[0114] The adaptive retransmission module 740 may then apply a threshold-based prediction mechanism, combining the normalized metrics into a decision variable using predefined mathematical functions or weighted sums. When the decision variable surpasses a threshold representing high failure likelihood, early HARQ failure may be predicted.
[0115] Alternatively, the adaptive retransmission module 740 may rely on a machine-learning-based technique, drawing from historical HARQ outcomes, CQI / RI / PMI sequences, BLER trajectories, and channel-variation characteristics to infer failure likelihood from real-time metrics fed to a trained model.
[0116] A hybrid approach may combine both the thresholding mechanism and the ML-based inference, for example by blending the outputs through confidence weighting or selecting the more conservative result. Such fusion may mitigate false positives and false negatives across varied channel conditions.
[0117] At step 808, after determining that a HARQ failure is likely based on the selected mechanism, the adaptive retransmission module 740 may cause the RLC 702 to send a halt-transmission instruction to the MAC 704. The downward arrow from RLC 702 to MAC 704 may represent this directive to stop further redundancy-version transmissions for the affected PDUs.
[0118] At step 810, in response to the halt message, the MAC 704 may return identification information for the PDUs associated with the stopped HARQ procedure. This feedback, depicted as an upward arrow, may allow precise mapping of the PDUs that require upper-layer recovery.
[0119] At step 812, the adaptive retransmission module 740 may enable the RLC 702 to initiate an Automatic Repeat reQuest (ARQ) retransmission procedure for the affected PDUs. ARQ, typically implemented through Acknowledged Mode (AM), may rely on sequence numbers, polling, and status reports to ensure reliable end-to-end delivery.
[0120] The ARQ process may involve re-segmentation, re-queuing, priority handling, and timer-based pacing sufficient to ensure efficient retransmission. This shift from lower-layer HARQ to upper-layer ARQ may improve service performance when continuing HARQ retransmissions would be ineffective.
[0121] Because predictive mechanisms may occasionally yield uncertain or low-confidence outcomes, the RLC 702 may maintain a fallback recovery mechanism based on traditional AM procedures. This ensures robust delivery even when early-halt conditions are not triggered.
[0122] According to the present disclosure, the MAC 704 may also determine if HARQ retransmission procedure should be continued in scenarios where the network connection improves. An exemplary implementation is now explained with respect to Figure 9.
[0123] Figure 9 illustrates a process flow 900 between an RLC 702 and a MAC 704, where an adaptive retransmission module 740 may reside within the RLC 702 and act as the coordinating actor for cross-layer reliability decisions, according to an embodiment of the present disclosure. The figure emphasizes how MAC-level Hybrid Automatic Repeat Request (HARQ) behaviour can be extended, under favourable radio conditions, to avoid or defer RLC-level Automatic Repeat reQuest (ARQ), while keeping the RLC 702 informed to maintain consistent recovery logic.
[0124] At step 902, the adaptive retransmission module 740 may cause the RLC 702 to transmit one or more RLC PDUs to the MAC 704 for transport-block (TB) formation. The MAC 704 may segment or concatenate the incoming PDUs in accordance with scheduling, modulation-and-coding, and resource allocation constraints, producing TBs that are then assigned to respective HARQ processes. The figure's first arrow from RLC 702 to MAC 704 may depict this handoff that initiates the lower-layer delivery pipeline.
[0125] Following TB formation, the MAC 704 may map each TB to a distinct HARQ process and queue it to the physical layer for scheduled over-the-air transmission. Acknowledge (ACK) and negative acknowledge (NACK) feedback may be expected on a defined timeline, enabling tight retransmission control. This initial HARQ transmission establishes the process state for subsequent actions if decoding is unsuccessful.
[0126] When a NACK is reported or decoding fails within the expected interval, a HARQ retransmission procedure may be triggered. The MAC 704 may dispatch additional transmissions using configured redundancy versions (RVs), and the receiver may apply soft combining across attempts. Chase combining may reuse the same coded bits, and incremental redundancy may deliver additional parity bits both increasing the chance of successful decoding.
[0127] As part of this decision-making, the MAC 704 may continuously evaluate the quality of the channel. Because HARQ relies on physical-layer behaviour, channel conditions play a central role in deciding whether additional retransmissions are worthwhile. This includes evaluating whether the channel is improving sufficiently to support one more HARQ attempt rather than escalating recovery to ARQ.
[0128] One significant indicator influencing HARQ decisions is the Channel Quality Indicator (CQI), which reflects the receiver's assessment of achievable modulation-and-coding settings. A rising CQI generally indicates that the channel can support higher throughput or more robust decoding, which directly increases the likelihood that the next HARQ retransmission will succeed. Therefore, an upswing or stabilization trend in CQI may motivate the MAC 704 to attempt an additional retransmission instead of involving ARQ prematurely.
[0129] Conversely, a declining CQI may signal deteriorating radio conditions, making further HARQ attempts less productive. If CQI drops below certain internal thresholds, the MAC 704 may determine that incremental redundancy is unlikely to yield successful decoding, even with soft combining. This behaviour helps prevent wasteful transmissions and instead initiates an escalation to ARQ.
[0130] At step 904, the MAC 704 may determine whether the count of HARQ retransmission occurrences for a TB has reached or exceeded a preconfigured maximum HARQ attempt value. Rather than immediately yielding to ARQ at this limit, the MAC 704 may assess whether supplemental HARQ attempts enabled by improving CQI values or other link indicators could offer shorter latency recovery.
[0131] In response to this determination, the MAC 704 may monitor a plurality of channel-quality parameters tightly coupled to the physical layer. These may include CQI, Rank Indicator (RI), Precoding Matrix Indicator (PMI), and receiver Block Error Rate (BLER). This multi-metric observation enables the MAC 704 to detect whether the radio environment is transitioning into a more favourable state. Continuous feedback reports further help distinguish temporary fluctuations from genuine channel recovery.
[0132] The MAC 704 may apply thresholds or averaging filters to CQI values to avoid reacting to momentary spikes. For example, if CQI improves consistently over a sliding window, the MAC 704 may infer that the link is stabilizing due to mobility settling or reduced interference. This trending behaviour may strongly support a decision to extend HARQ retransmissions, as the probability of successful decoding increases meaningfully when CQI stabilizes above a minimum operating range.
[0133] Based on these continuous observations, the MAC 704 may determine whether monitored conditions represent real improvement. A combination of rising CQI, reducing BLER, and stable RI / PMI patterns may indicate that channel fading is diminishing, making the next HARQ attempt more promising. The figure may illustrate this through MAC-internal evaluation arrows.
[0134] Once the MAC 704 confirms the improvement, it may select an additional HARQ retransmission instead of transitioning recovery responsibilities to the RLC-level ARQ mechanism. This has the benefit of preserving soft-combining gains accumulated from earlier transmissions and reducing the overhead of initiating ARQ. The MAC 704 may reuse the existing TB for this retransmission instead of creating a new TB, ensuring continuity of bit patterns at the receiver.
[0135] To support the additional attempt, the MAC 704 may update the preconfigured maximum HARQ attempt value for the active HARQ process. This update may be tracked in MAC state and aligns with the decision to opportunistically exploit improved radio conditions. In deployments where policies or specifications allow, these updated limits may be dynamically tuned based on field performance.
[0136] After deciding on the additional retransmission, the MAC 704 may transmit the TB using an RV selected based on current channel conditions. If the channel is significantly improved, the MAC 704 may favour incremental redundancy to maximize the likelihood of decoding success. The figure may depict this with a MAC-to-PHY arrow labelled "Additional HARQ RV"
[0137] Upon initiating this extra HARQ attempt, the MAC 704 may also update the RLC 702 with the new effective maximum HARQ attempt value. The upward arrow in the diagram may represent this communication, ensuring that ARQ timers or retransmission operations at the RLC side remain paused. Maintaining alignment between the layers prevents premature RLC-level recovery actions.
[0138] At step 906, the MAC 704 may configure the RV value and the updated attempt count as part of the HARQ retransmission procedure. During this period, the MAC 704 may repeatedly evaluate likelihood of success using receiver feedback, which may include implicit indicators such as decoding progress, chase-combining status, or CBG-level error patterns. These signals enable the MAC 704 to refine its strategy and determine whether further extension is justified.
[0139] If the likelihood of successful decoding remains strong, the MAC 704 may dynamically update RV or extend attempts beyond even the newly updated maximum. This behaviour supports flexible link adaptation that moves beyond static attempt ceilings (e.g., traditional four-attempt limits) and instead capitalizes on evolving radio conditions that favour success.
[0140] The MAC 704 may also engage in enhanced MAC-RLC information exchange by notifying the RLC 702 about the ongoing HARQ extension. This notification may prompt the RLC 702 to pause any ARQ timer or pending retransmission process. The RLC 702 may maintain this paused state until the MAC 704 reports that the HARQ procedure is completed, either successfully or unsuccessfully.
[0141] Upon completion of the extended HARQ window, if the receiver sends an ACK, the MAC 704 may release the TB and consider the HARQ recovery successful. The RLC 702 may cancel any pending ARQ attempts for the associated PDUs. If the HARQ fails despite extension, the RLC 702 may resume or initiate ARQ procedures to complete upper-layer recovery.
[0142] Finally, CQI trends may continue to influence decisions throughout the extension window. If CQI begins to drop during an extended HARQ attempt, the MAC 704 may conclude that continuing the extension is no longer viable, prompting an early termination of the extended HARQ procedure and a transition to ARQ. Conversely, a steadily rising CQI may encourage completion of the last HARQ attempt even if the extension window is nearing its upper bound.
[0143] Figure 10 illustrates a call-flow for a method 100 between the RLC 702 and the MAC 704, where an adaptive retransmission module 740 may be installed inside the MAC 705 and orchestrate upper-layer data handling for reliability, according to an embodiment of the present disclosure. Directional arrows may depict the sequence of PDUs, Transport Blocks (TBs), control indications, and status messages exchanged between the RLC and MAC layers during adaptive retransmission. Further, Figure 11 illustrates the internal structural transformation of a TB when TB splitting is performed, according to an embodiment of the present disclosure.
[0144] Figures 10 and 11 may be described in conjunction with one another. Together, they present both the procedural signalling between layers and the data-structure changes (e.g., Split TBs 1102, 1104) that enable lower-MCS retransmissions under adverse channel conditions.
[0145] At step 1002, the adaptive retransmission module 740 may receive one or more PDUs from the RLC 702 to initiate a Hybrid Automatic Repeat Request (HARQ) transmission procedure for a lower layer. The arrow from RLC 702 to MAC 704 may represent this handover, marking the transition from RLC-level PDUs to MAC-level TB construction and scheduling.
[0146] At step 1004, the adaptive retransmission module 740 may form one or more TBs from the received PDUs. Formation may include segmentation, concatenation, and aggregation under scheduler policy, supported Modulation and Coding Scheme (MCS) levels, and allocation constraints. Each TB may comprise a MAC header and a MAC payload encapsulating the forwarded PDUs.
[0147] At step 1006, the adaptive retransmission module 740 may assign each newly formed TB to a corresponding HARQ process. This assignment ensures that HARQ state such as redundancy-version history, expected feedback timing, and soft-combining buffers is tracked across transmissions and potential retransmissions.
[0148] At step 1008, the adaptive retransmission module 740 may transmit one or more TBs to the lower layer for scheduled over-the-air delivery. The call-flow may depict this as an arrow from MAC 704 to the physical layer, indicating that the TB is queued for radio transmission whenever an uplink or downlink grant becomes available.
[0149] At step 1010, the adaptive retransmission module 740 may initiate a HARQ retransmission procedure based on feedback from the lower layer. Subsequent HARQ retransmissions may employ redundancy versions (RVs) and receiver-side soft combining e.g., chase combining (reusing the same coded bits) or incremental redundancy (supplying additional parity) to raise the probability of successful decoding.
[0150] At step 1012, the adaptive retransmission module 740 may dynamically adjust a TB size during an ongoing HARQ retransmission procedure in accordance with monitored channel conditions. The module may detect an early HARQ failure prior to a next scheduled HARQ retransmission by analysing CQI / RI / PMI and BLER trends, concluding that retransmitting the same larger TB under the same MCS is unlikely to succeed.
[0151] Responsive to the detection, the adaptive retransmission module 740 may determine a smaller TB size selected from among sizes supported by the transceiver device. Selection may be guided by mapping tables that relate MCS, code rate, and TB size, with lower MCS levels typically corresponding to smaller, more robust TBs suitable for degraded channel conditions.
[0152] To implement the size reduction, the adaptive retransmission module 740 may map an original TB onto newly formed TBs of smaller size. As shown conceptually by Figure 11, a first Split TB 1102 may continue on the same HARQ process, while a second Split TB 1104 may be transmitted on a different HARQ process, together representing a partition aligned with the updated MCS constraints.
[0153] The adaptive retransmission module 740 may obtain Channel State Information (CSI) indicative of current channel conditions and update the MCS for the retransmission without modifying lower-layer protocol behaviour. According to the updated MCS, the module may segment the original MAC payload into Split TBs sized to satisfy transport-block constraints of the lower MCS, while preserving MAC header semantics.
[0154] The adaptive retransmission module 740 may further ensure that Downlink Control Information (DCI) or corresponding control signalling carries an indicator that the first Split TB 1102 continues within the same HARQ process at a different MCS / TB size. The remaining portion of the original TB may be reformatted into Split TB 1104 using MAC-layer segmentation options and prioritized for immediate scheduling on a different HARQ process to minimize reassembly delay.
[0155] The adaptive retransmission module 740 may generate each Split TB to include a Sequence Number (SN), Segmentation Information (SI), and a Split TB payload. The SN may identify each segment and its order among the plurality of Split TBs, while the SI may indicate the relationship between the split and the original TB (e.g., original TB identifier, total number of Split TBs, segment index, start-of-segment / end-of-segment indicators, byte offset, and segment length).
[0156] Where implementation limits splitting to two segments, the adaptive retransmission module 740 may simplify the SI potentially to a single bit distinguishing "first half" vs. "second half" to reduce header overhead. For advanced policies that permit more than two segments, an optional segmentation offset field may be included, although repeated splitting of already split TBs may be avoided to keep receiver complexity bounded.
[0157] On the receiving side, the adaptive retransmission module 740 (as interpreted at the receiver's MAC) may facilitate reassembly by maintaining a reassembly buffer and timer. The receiver may process the plurality of Split TBs (each including MAC header + SN + SI + split payload), identify the original TB and total number of segments from SI, order the splits by SN and / or SI's segment index, and reassemble the original payload by concatenation, verifying completeness against the segment count.
[0158] In one example, the adaptive retransmission module 740 at the receiver may generate feedback indicating successful reassembly or identifying missing segments. This enables selective retransmission of only the missing Split TB(s), improving spectral efficiency relative to retransmitting the entire original TB under adverse channel conditions.
[0159] The adaptive retransmission module 740 may address the problem that conventional HARQ retransmissions typically reuse the original MCS and TB size, which can undermine success when the channel has degraded. By lowering the MCS and reducing TB size as conditions worsen, the module increases retransmission robustness, leveraging code-rate / TB-size mappings to select feasible split sizes that match current radio conditions.
[0160] A split-threshold policy may be applied by the adaptive retransmission module 740 to decide when to transition from a single larger TB to two smaller Split TBs (e.g., 50:50, 40:60, or 30:70). The chosen ratio may ensure that each Split TB maps cleanly to a valid lower-MCS TB size and that the sum of the new sizes approximates the original TB size, preserving payload efficiency while improving decoding probability.
[0161] To minimize receiver burden, the adaptive retransmission module 740 may avoid subsequent splitting of an already split TB. This prevents cascading complexity, keeps SI structure simple, and stabilizes buffer / timer management at the receiver. If policy permits more than two segments, the optional segmentation offset in SI may provide robust mapping, though such use is not mandatory.
[0162] From a control perspective, the adaptive retransmission module 740 may keep the first Split TB 1102 on the original HARQ process while mapping Split TB 1104 to a different HARQ process and queuing it with priority. This preserves continuity for soft combining on the first portion and accelerates delivery of the remainder for timely, complete reassembly.
[0163] Where DCI carries the segmentation / change indicator, the adaptive retransmission module 740 may ensure the receiver aligns soft-combining buffers and HARQ expectations immediately for the first split (same process), while preparing a second process state for the remaining split. This explicit signalling mitigates mis-association and reduces the chance of process confusion.
[0164] Throughout, the adaptive retransmission module 740 may remain cross-layer aware of HARQ status and segmentation mappings to ensure that RLC ARQ behaviour (e.g., status polling and retransmission timers) remains consistent. The RLC transmitter may continue waiting for RLC-receiver feedback in the ordinary course; additional changes at the RLC transmitter are generally not required for compatibility with dynamic TB resizing and segmentation.
[0165] When CSI trends improve during the HARQ cycle, the adaptive retransmission module 740 may elect to proceed with a standard HARQ attempt without splitting; conversely, when early failure is predicted for the current TB size / MCS, the module may invoke step 1012 to split and downgrade MCS proactively. This policy allows implementations to balance segmentation overhead against retransmission success probability.
[0166] Upon successful ACK for all segments, the adaptive retransmission module 740 may release the original TB and free the associated HARQ processes for new TBs. If reassembly remains incomplete after the timer expires, receiver feedback may identify missing segments, and the module may selectively schedule retransmission for only those missing Split TBs at the updated MCS.
[0167] The adaptive retransmission module 740 may continue monitoring channel conditions and combining outcomes during the extended retransmission phase, allowing further refinement of RV choices and scheduling priorities for any missing segments. This ongoing adaptation helps exploit transient improvements while curbing waste under deteriorating conditions.
[0168] The embodiments disclosed herein may be implemented through at least one software program running on at least one hardware device and performing network management functions to control network elements. The network elements can be at least one of a hardware device or a combination of a hardware device and a software module.
[0169] The system 700 of the present disclosure provides an interworking mechanism between ARQ and HARQ functionalities that effectively reduces the processing latency otherwise incurred during multi-layer recovery operations, thereby substantially improving the overall efficiency of data transmission across wireless communication networks. By intelligently coordinating when to continue HARQ at the MAC layer and when to elevate recovery to ARQ at the RLC layer, system 700 minimizes unnecessary retransmission loops, lowers end-to-end recovery delays, and enhances throughput consistency even under fluctuating radio conditions.
[0170] Further, the system 700 incorporates an early HARQ-failure detection mechanism that enables proactive and timely initiation of ARQ procedures, thereby eliminating redundant HARQ retransmission attempts and optimizing utilization of radio and network resources. Through the adaptive retransmission module 740, the system is able to evaluate trends in NACK ratios, CQI / RI / PMI variations, BLER patterns, and other link measurements, ensuring that each retransmission whether MAC-level or RLC-level yields tangible recovery benefits and avoids wasteful consumption of spectrum or computational resources.
[0171] Additionally, the system 700 of the present disclosure maintains backward compatibility with existing RLC / MAC / HARQ network architectures while simultaneously delivering notable performance improvements, particularly for services and applications operating under strict packet-delay budgets. The system integrates seamlessly with standardized retransmission behaviours, requiring no disruptive changes to deployed network infrastructure, and nevertheless provides accelerated failure detection, reduced latency, and improved packet-delivery reliability for delay-sensitive traffic.
[0172] While specific language has been used to describe the present disclosure, any limitations arising on account thereto, are not intended. As would be apparent to a person in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein. The drawings and the foregoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment.
Claims
1.A method performed by a transceiver device in a wireless communication system, the method comprising:transmitting, by a radio link control (RLC) layer of the transceiver device to a medium access control (MAC) layer of the transceiver device, one or more protocol data units (PDUs) to initiate a hybrid automatic repeat request (HARQ) transmission procedure for a lower layer;receiving, by the RLC layer from the MAC layer, transmission-related metrics in response to transmitting the one or more PDUs;predicting, by the RLC layer, an early HARQ failure based on the received transmission-related metrics;signalling, by the RLC layer to the MAC layer, to halt an HARQ retransmission procedure for the PDUs mapped to a HARQ procedure in response to predicting the early HARQ failure;receiving, by the RLC layer from the MAC layer, identification information of PDUs that are mapped to the HARQ retransmission procedure for which retransmission has been skipped in response to receipt of the halt signalling; andinitiating, by the RLC layer, an automatic repeat request (ARQ) retransmission procedure for the PDUs associated with the received identification information.2.The method of claim 1, wherein receiving transmission-related metrics comprises:forming, by the MAC layer responsive to the receiving of the PDUs, one or more transport blocks (TBs) from the one or more PDUs;assigning, by the MAC layer upon forming the TBs, each TB to the corresponding HARQ procedure;transmitting, by the MAC layer subsequent to the assigning to a lower layer, the one or more TBs for scheduled transmission over a physical interface;initiating the HARQ retransmission procedure based on feedback from the lower layer, wherein the feedback comprises a negative acknowledgment (NACK);monitoring, by the MAC layer during and after the initiating the HARQ retransmission procedure, a ratio of NACKs over a defined timeline for same or different HARQ procedures to quantify retransmission behaviour;observing, by the MAC layer concurrently with the monitoring, one or more link indicators associated with downlink (DL) and uplink (UL) transmissions, the one or more link indicators comprising at least one of channel quality indicator (CQI), rank indicator (RI), precoding matrix indicator (PMI), and receiver block error rate (BLER);detecting, by the MAC layer, based on the one or more observed link indicators, one or more anomalies indicative of channel quality degradation, one or more anomalies comprising at least one of: a sudden CQI drop, an unexpected RI change, an unexpected PMI change, or a high BLER condition;generating, by the MAC layer responsive to (i) the monitored NACK ratio and (ii) the one or more detected anomalies, the transmission-related metrics that characterize link reliability and expected failure prediction,wherein the transmission-related metrics include at least one metric element selected from: a NACK ratio trend value, a CQI degradation score, an RI / PMI variance measure, a BLER severity index, and a composite risk indicator; andtransmitting, by the MAC layer subsequent to the generating to the RLC layer, the transmission-related metrics, thereby enabling the RLC layer to adapt data handling and retransmission strategies in real time.3.The method of claim 1, wherein predicting the early HARQ comprises:predicting, by the RLC layer, the early HARQ failure, based on the received transmission-related metrics, using one of:- a threshold-based calculation that generates a decision variable by combining the transmission-related metrics and compares a decision variable against a predefined threshold for prediction; or- a machine learning prediction, wherein the RLC layer or an associated process entity trains a model using historical HARQ outcomes, time-series, at least one of channel quality indicator (CQI), rank indicator (RI), precoding matrix indicator (PMI) data, and channel variation features, and the RLC layer uses the trained model for prediction.4.The method of claim 3, wherein predicting the early HARQ failure using the threshold-based calculation comprises:generating a decision variable, by the RLC layer, by combining the normalized transmission-related metrics through a predefined mathematical function or weighted aggregation;comparing the decision variable against a predefined threshold value, wherein the predefined threshold value represents a failure likelihood criterion; andpredicting, by the RLC layer, the early HARQ failure when the decision variable exceeds the predefined threshold value, thereby enabling proactive initiation of corrective measures, including the ARQ retransmission procedure.5.The method of claim 3, wherein predicting the early HARQ failure using the machine learning prediction comprises:collecting, by the RLC layer or an associated process entity, historical data;training, by the RLC layer or an associated process entity, a machine learning (ML) model using the collected historical data;aligning and normalizing, by the RLC layer or an associated process entity, real-time transmission-related metrics across HARQ procedure using time stamps and procedure identifiers to match an input format expected by the trained ML model;feeding, by the RLC layer or an associated process entity, the normalized metrics into the trained ML model for inference; andpredicting an early HARQ failure, by the RLC layer based on the output of the trained model, wherein the prediction enables proactive initiation of corrective measures, including the ARQ retransmission procedure.6.The method of claim 5,wherein the historical data comprises past HARQ outcomes, time-series measurements of at least one of channel quality indicator (CQI), rank indicator (RI), precoding matrix indicator (PMI), and channel variation features; andwherein the ML model is configured to learn patterns indicative of HARQ failure based on feature correlation and temporal dependencies.7.The method of claim 1, further comprising:configuring, by the RLC layer, a backup recovery mechanism using acknowledged mode (AM) procedures when predictive halting is inactive.8.The method of claim 1, further comprising:determining, at the MAC layer, whether a count of HARQ retransmission occurrences exceeds a preconfigured maximum HARQ attempt value;monitoring, in response to the determination, a plurality of channel quality parameters associated with a physical layer, the plurality of parameters including channel quality indicator (CQI), rank indicator (RI), precoding matrix indicator (PMI), and block error rate (BLER), wherein the monitoring comprises receiving continuous feedback reports indicative of channel conditions;determining, by the MAC layer, whether the monitored channel conditions are improved based on the continuous feedback reports;deciding, based on the determination, whether to initiate an additional HARQ retransmission attempt instead of triggering an automatic repeat request (ARQ) procedure, thereby enabling faster recovery and reducing signalling overhead;updating, by the MAC layer, the preconfigured maximum HARQ attempt value to accommodate the additional HARQ retransmission attempt;transmitting, by the MAC layer, the additional HARQ by utilizing the existing TB rather than generating a new TB; andindicating, upon initiating the additional HARQ retransmission, to the RLC layer regarding the updated preconfigured maximum HARQ attempt value.9.The method of claim 8, further comprising:configuring, by the MAC layer, at least one redundancy version (RV) and the maximum HARQ attempt value for the TB;determining, during a HARQ retransmission procedure, a likelihood of successful recovery of the TB based on at least one recovery condition, wherein the at least one recovery condition comprises receiver feedback, signal quality metrics, or historical combining success;dynamically updating the at least one RV and extending the maximum HARQ attempt value beyond the preconfigured maximum HARQ attempt value in response to the determined likelihood of successful recovery; andnotifying, by the MAC layer, the RLC layer for an extended HARQ retransmission duration,wherein the RLC layer pauses an ARQ recovery timer or retransmission procedure during the extended HARQ retransmission duration, and resumes or aborts, upon completion of the HARQ retransmission procedure, the ARQ retransmission procedure based on an outcome of the HARQ retransmission procedure.10.A transceiver device for adaptive retransmission in a wireless communication system, the system comprising:a memory; andat least one processor in communication with the memory and configured to implement a radio link control (RLC) layer and a medium access control (MAC) layer, the at least one processor configured to:transmit, by the RLC layer to the MAC layer, one or more protocol data units (PDUs) to initiate a hybrid automatic repeat request (HARQ) transmission procedure for a lower layer;receive, by the RLC layer, transmission-related metrics from the MAC layer in response to the transmitting of the one or more PDUs;predict, by the RLC layer, an early HARQ failure based on the received transmission-related metrics;signal, by the RLC layer to the MAC layer, to halt a HARQ retransmission procedure for PDUs mapped to a HARQ procedure in response to predicting the early HARQ failure;receive, by the RLC layer from the MAC layer, identification information of PDUs that are mapped to the HARQ retransmission procedure for which retransmission has been skipped in response to receipt of the halt signalling; andinitiate, by the RLC layer, an automatic repeat request (ARQ) retransmission procedure for the PDUs associated with the received identification information.11.The transceiver device of claim 10, wherein the at least one processor is further configured to:form, by the MAC layer responsive to receiving the PDUs, one or more transport blocks (TBs) from the one or more PDUs;assign, by the MAC layer upon forming the TBs, each TB to a corresponding HARQ procedure;transmit, by the MAC layer subsequent to the assigning to a lower layer, the one or more TBs for scheduled transmission over a physical interface;initiate the HARQ retransmission procedure based on feedback from the lower layer, wherein the feedback comprises a negative acknowledgment (NACK);monitor, by the MAC layer during and after initiating the HARQ retransmission procedure, a ratio of NACKs over a defined timeline for same or different HARQ procedures to quantify retransmission behaviour;observe, by the MAC layer concurrently with the monitoring, one or more link indicators associated with DL and UL transmissions, the one or more link indicators comprising at least one of channel quality indicator (CQI), rank indicator (RI), precoding matrix indicator (PMI), and receiver block error rate (BLER);detect, by the MAC layer, based on the one or more observed link indicators, one or more anomalies indicative of channel quality degradation;generate, by the MAC layer responsive to (i) the monitored NACK ratio and (ii) the detected anomalies, transmission-related metrics including at least one metric element selected from: a NACK ratio trend value, a CQI degradation score, an RI / PMI variance measure, a BLER severity index, and a composite risk indicator; andtransmit, by the MAC layer subsequent to the generating to the RLC layer, the transmission-related metrics.12.The transceiver device of claim 10, wherein the at least one processor is configured to predict the early HARQ failure using one of:- a threshold-based calculation that generates a decision variable by combining the transmission-related metrics and compares the decision variable against a predefined threshold; or- a machine learning prediction using a model trained on historical HARQ outcomes, time-series of CQI, RI, PMI, and channel variation features.13.The transceiver device of claim 12, wherein the at least one processor is further configured to:generate a decision variable by combining normalized transmission-related metrics through a predefined mathematical function or weighted aggregation;compare the decision variable against a predefined threshold value representing a failure likelihood criterion; andpredict the early HARQ failure when the decision variable exceeds the predefined threshold value.14.The transceiver device of claim 12, wherein the at least one processor is further configured to:collect historical data;train a machine learning (ML) model using the collected historical data;align and normalize real time transmission-related metrics across HARQ procedures using timestamps and identifiers;feed normalized metrics into the trained ML model; andpredict an early HARQ failure based on the model's output.15.The transceiver device of claim 14, wherein:the historical data comprises past HARQ outcomes, time-series measurements of at least one of channel quality indicator (CQI), rank indicator (RI), precoding matrix indicator (PMI), and channel variation features; andthe ML model is configured to learn patterns indicative of HARQ failure based on feature correlation and temporal dependencies.
