SYSTEM AND METHOD FOR FACILITATING FAIL-SAFE NODES IN A NETWORK - Patent application

Abstract

The present invention provides an efficient and reliable system and method for facilitating fail-safe potential in a network by utilizing 3GPP defined Radio Resource Control (RRC) T310 (Radio Link Failure Timer), N310 (Radio Link Failure Counter), T311 (Radio Link Re-establishment Timer), N311 (Radio Link Re-establishment Counter) timers and associated counters to enable L1 to recover within the combined duration of the sum of the T310 and T311 timers, e.g., typically within 100 milliseconds following an L1SW exception event.

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE Embodiments of the present disclosure relate generally to telecommunications deployments. More specifically, the present disclosure relates to systems and methods for facilitating fail-safe potential in networks. [Background technology]

[0002] The following description of related art is intended to provide background information regarding the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, this section should be understood as being used only to enhance the reader's understanding of the present disclosure and not as an admission of prior art.

[0003] A wireless communication system consists of a gNodeB Digital Unit (DU) coupled to at least one radio unit, through which the gNodeB transmits and receives wireless radio frequency signals to and from user equipment (UE) within the coverage area of ​​the radio unit. The digital unit stores the Layer 1 (L1), Layer 2 (L2) and Layer 3 (L3) protocols of the 5G wireless standard protocol stack. For such a wireless communication system to be deployed in a live network, two main criteria must be met by the gNode-B / core network subsystem. The criteria are (a) high availability, often cited as the five nines criterion, i.e., 99.999% availability, and (b) low gNodeB downtime, e.g., 21 minutes / year / gNodeB. Additionally, network key performance indicators (KPIs) defined by the 3G Partnership Project specifications (3GPP), such as call drop rate <0.1%; call success rate >99.5%, must also be met as Service Level Agreements (SLAs) of the network operator by Other Equipment Manufacturers (OEMs) of gNodeB.

[0004] In the state of the art, if the L1 software (L1SW) encounters an unexpected software error, the software asserts and crashes, and as a result, if the layer 2 software (L2SW) driving the L1SW does not receive periodic heartbeats from the L1SW, the L2SW communicates with the layer 3 software (L3SW) to stop cell transmission and reception, and eventually the entire DU housing the L1SW, L2SW and L3SW is rebooted or restarted. This usually takes a few minutes, during which time the working network experiences a service disruption and the network is considered out of service in that geographical area. In the state of the art, an unexpected L1SW event causes the L1SW to assert and the L1SW to crash. If there is no response from the L1SW for consecutive Transmission Time Intervals (TTIs), for example 15 TTIs, the L2SW realizes that something is wrong and then notifies the L3SW. The L3SW notifies the core network that the cell is down, and the core network can remove the cell and restart it. The time it takes to restart the cell after an unexpected L1SW event typically takes several seconds, resulting in configured 3GPP timers, T310 and T311 timers starting (timeout) in the UE, causing all UEs to go into hibernation, calls to be dropped, and network KPIs to be severely impaired.

[0005] Typically, parts of the 5G wireless L1 protocol stack are implemented in hardware accelerators, for example, performing Low-Density Parity Check (LDPC) and rate matching in the DL processing chain, and LDPC and rate dematching operations in the UL processing chain. This architecture allows the computationally intensive operations mentioned above to be offloaded to the hardware accelerator for time efficiency, rather than doing it in software. The hardware accelerator is driven with the configuration provided by the L1SW according to DL configuration request and UL configuration request messages received every 0.5 ms TTI from the L2SW. If there are out-of-range attributes received from the L2SW, or unexpected attributes passed to the hardware accelerator from the L1SW in a TTI, the hardware accelerator may take significant cycles to complete or may not complete at all. In state-of-the-art L1SW implementations, this can cause the L1SW to crash, the L2SW to not receive a response for several TTIs, and eventually the DU software to restart. It takes a few seconds for the gNodeB to become operational again, causing network disruption and call drops for all connected UEs.

[0006] Therefore, there is a need in the art to provide a system and method that can overcome the shortcomings of the existing prior art.

[0007] Some of the objectives of the present disclosure that will be satisfied by at least one embodiment herein are listed herein below.

[0008] The objective of this disclosure is to build a network in which the nodes are fail-safe.

[0009] It is an object of the present disclosure to provide a system that facilitates minimizing network disruption time so that network KPIs are impacted as little as possible.

[0010] The objective of the present disclosure is to provide a method that enables the L1SW to achieve high availability and provides protection for the gNodeB against unexpected L1SW exceptions in a live deployment. Summary of the Invention

[0011] This section is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or the scope of the claimed subject matter.

[0012] Aspects of the present disclosure provide a system for minimizing cell outages and key performance indicator (KPI) degradation by ensuring fail-safe nodes. The system may include cells and features a plurality of user equipments (UEs) communicatively coupled to the network, one or more electronic devices (gnodes) in the network configured to perform one or a combination of creating, receiving, and transmitting information over a communication channel communicatively coupled to the plurality of user equipments, and one or more hardware accelerators communicatively coupled to the one or more gnodes. The one or more hardware accelerators may be configured by a layer 1 (L1) module to process information received over the communication in accordance with uplink and downlink configuration instructions received for each predefined transit time interval (TTI) received from a layer 2 (L2) module associated with the network. The L1 module is associated with a physical (PHY) layer of the network, and the L2 module is associated with a data link layer of the network. The L1 module may further include a processor that executes a set of executable instructions stored in the memory, where upon execution of the executable instructions, the processor causes the L1 layer to monitor one or more discrepancies in information received by the one or more hardware accelerators and extracts from the one or more discrepancies a set of attributes that relate to out-of-range attributes received from the L2 module or unexpected attributes passed by the L1 module to the one or more hardware accelerators within a predefined TTI that causes the one or more hardware accelerators to complete processing of the information using excessive cycles or not at all. Based on the extracted set of attributes, the L1 module may reset one or a combination of one or more queues in the hardware accelerator and cores of the hardware accelerator. The reset may take a predefined disruption time interval such that the predefined disruption time interval is less than an expiration time associated with a radio link failure timer (T310) timer connected to the network.The resetting of the hardware accelerator and any or a combination of one or more queues in the core of the hardware accelerator is performed in parallel with a request response communication by the L1 module with the L2 module simultaneously for a predefined time interval. The request response communication can include sending an error message to the L2 module such that the L2 module can deactivate functionality of the L1 module until the combination of one or more queues in the hardware accelerator and the core of the hardware accelerator is restarted. Further, a plurality of UEs in the cell can be configured to be in a radio resource connected (RRC) state because the predefined disruption time interval is less than an end time of a T310 timer.

[0013] Aspects of the present disclosure provide a method for minimizing cell outages and key performance indicator (KPI) degradation by ensuring a fail-safe node. The method may include monitoring one or more discrepancies in information received by one or more hardware accelerators communicatively coupled to one or more electronic devices (gnodes) configured to perform any or a combination of creating, receiving, and transmitting information over a communication channel communicatively coupled to a plurality of user equipment. The one or more hardware accelerators are configured by a layer 1 (L1) module to process the information received over the communication in accordance with uplink and downlink configuration instructions received for each predefined transit time interval (TTI) received from a layer 2 (L2) module associated with the network. The L1 module is associated with a physical (PHY) layer of the network, and the L2 module is associated with a data link layer of the network. The method may further include extracting from the one or more mismatches a set of attributes related to out-of-range attributes received from the L2 module or unexpected attributes passed by the L1 module to the one or more hardware accelerators within a predefined TTI that causes the one or more hardware accelerators to complete processing of the information using excessive cycles or not at all. Based on the extracted set of attributes, the method may include resetting one or a combination of one or more queues in the hardware accelerator and a core of the hardware accelerator. The resetting may take a predefined disruption time interval such that the predefined disruption time interval is less than an expiration time associated with a radio link failure timer (T310) timer coupled to the network, and resetting one or a combination of one or a combination of queues in the hardware accelerator and a core of the hardware accelerator may be performed in parallel with simultaneously performing a request-response communication by the L1 module with the L2 module for the predefined time interval.The request response communication can include sending an error message to the L2 module to cause the L2 module to deactivate functionality of the L1 module until a combination of one or more queues in the hardware accelerator and a core of the hardware accelerator is restarted, and a plurality of UEs in the cell can be configured to be in a radio resource connected (RRC) connected state because a predefined disruption time interval is less than an expiration time of a T310 timer.

[0014] The accompanying drawings, which are incorporated herein and form a part of the present invention, illustrate exemplary embodiments of the disclosed method and system, with like reference numerals referring to the same parts throughout the different drawings. The components in the drawings are not necessarily drawn to scale, emphasis instead being placed on clearly illustrating the principles of the present disclosure. Some figures may use block diagrams to illustrate components and may not represent the internal circuitry of each component. Those skilled in the art will appreciate that the inventions in such drawings include inventions of electrical components, electronic components, or circuits commonly used to implement such components. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 illustrates an exemplary system architecture in which the proposed system of the present disclosure may be implemented or may be practiced using the proposed system of the present disclosure, according to an embodiment of the present disclosure. [Diagram 2] FIG. 2 illustrates an exemplary representation of a flow diagram related to the proposed method, according to one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] The above will become more apparent from the following more detailed description of the invention.

[0017] In the following description, for purposes of explanation, various specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. However, it will be apparent that the embodiments of the present disclosure may be practiced without these specific details. Some features described below may be used independently of each other or in any combination with other features. Individual features may not address all of the above problems, or may address only some of the above problems. Some of the above problems may not be fully addressed by any of the features described herein.

[0018] The following description provides exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the following description of exemplary embodiments provides those skilled in the art with an effective description for implementing the exemplary embodiments. It should be understood that various changes can be made in the function and arrangement of elements without departing from the spirit and scope of the invention as described.

[0019] The present invention provides an efficient and reliable system and method for facilitating fail-safe potential in a network by utilizing 3GPP defined Radio Resource Control (RRC) T310 (Radio Link Failure Timer), N310 (Radio Link Failure Counter), T311 (Radio Link Re-establishment Timer), N311 (Radio Link Re-establishment Counter) timers and associated counters to enable L1 to recover within the combined duration of the sum of the T310 and T311 timers, e.g., typically within 100 milliseconds following an L1SW exception event.

[0020] 1, an exemplary network architecture (also referred to as network architecture (100)) for a wireless network (100) in which the system (110) of the present disclosure may be implemented in accordance with an embodiment of the present disclosure is shown. As shown, the exemplary network architecture (100) may include a Radio Resource Control (RRC), a Radio Link Failure Timer (T310), a Radio Link Failure Counter (N310), a Radio Link Re-establishment Timer (T311), and a Radio Link Re-establishment Counter (N311). The system (110) may be communicatively coupled to a plurality of first computing devices (102-1, 102-2, 102-3...102-N) -interchangeably referred to as user equipment (102-1, 102-2, 102-3...102-N) and (individually referred to as user equipment (UE) (102) and collectively referred to as UEs (102)) via second computing devices (104-1, 104-2,...104-N) (interchangeably referred to as base stations (104-1, 104-2,...104-N), individually referred to as base stations (104), and collectively referred to as base stations (104)), and the system (110) may be further operatively coupled to the base stations (104) via an open wireless access network radio unit (O-RU) (114). The system (110) may further be communicatively coupled to one or more third computing devices (106) (interchangeably referred to as gNB distributed units (DU) or gNBDU 106) and one or more fourth computing devices (116) (interchangeably referred to as gNB control units (CU) or gNBCU 116). The one or more fourth computing devices (116) may be communicatively coupled to a plurality of fifth computing devices (118) (hereinafter interchangeably referred to as first nodes (118)). The one or more third computing devices (106) or gNBDU (106) may be, but are not limited to, satellites or any non-terrestrial deployment.

[0021] In an exemplary implementation, the predefined expiry time of the Radio Link Failure Timer (also referred to as T310) may be at least 100 ms. Due to this momentary time, UEs (102) connected to a cell and running throughput with various traffic profiles may experience a momentary interruption if an unexpected L1 software (SW) event occurs, which will cause a Radio-link-Failure (RLF) to be experienced by the UE (102) within 100 ms. Since the RLF duration is within the T310 timer period (typically 100 ms), the UE (102) will remain in RRC connected state and will not go into RRC dormant state. Thus, none of the activated UEs will disconnect, and only a momentary (100 ms) disruption and loss of throughput will occur.

[0022] The system may further include one or more hardware accelerators communicatively coupled to the one or more gnodes (106) and configured by a layer 1 (L1) module to process information received over a communication channel according to uplink and downlink configuration instructions received at each predefined transit time interval (TTI) received from a layer 2 (L2) module associated with the network. The L1 module is associated with a physical (PHY) layer of the network, and the L2 module is associated with a data link layer of the network. The L1 module further comprises a processor that executes a set of executable instructions stored in a memory, which upon execution causes the L1 layer to monitor one or more discrepancies in the information received by the one or more hardware accelerators. The L1 module may then extract from the one or more discrepancies a set of attributes that relate to out-of-range attributes received from the L2 module or unexpected attributes passed by the L1 module at the predefined TTI to the one or more hardware accelerators, where the one or more hardware accelerators complete processing of the information using excessive cycles or do not complete at all. Based on the set of extracted attributes, the L1 module can reset one or a combination of one or more queues in the hardware accelerator and cores of the hardware accelerator cores. The resetting can obtain a predefined disruption time interval such that the predefined disruption time interval is less than an expiration time associated with a network-coupled T310 timer, and the resetting of one or a combination of one or more queues in the hardware accelerator and cores of the hardware accelerator can be performed in parallel with simultaneously performing request-response communication by the L1 module with the L2 module for the predefined time interval.The request response communication may include sending an error message to the L2 module, and the L2 module may deactivate functionality of the L1 module until a combination of one or more queues in the hardware accelerator and a core of the hardware accelerator core is restarted. A plurality of UEs in the cell may be configured to be in a Radio Resource Connected (RRC) Connected state because a predefined disruption time interval is less than an expiration time of a T310 timer.

[0023] In an exemplary embodiment, a plurality of UEs connected to the network experience a radio link failure for a second time interval, the duration of the second time interval being less than a duration of the predefined outage time interval.

[0024] In an exemplary embodiment, UEs connected to the network do not transition to an RRC idle state.

[0025] In an exemplary embodiment, the request response communication further includes stopping real-time downlink (DL), uplink (UL) processing chains and transitioning the L1 module from a running state to a dormant state. The L1 module may respond to the L2 module with a physical stop response message. The request response also includes deactivation of the L1 module by the L2 module, the L1 module continuing to perform one or a combination of: sending a SLOT indication to maintain the L2 scheduler from ticking of a system frame number (SFN), and not causing the L2 module to clear one or more contexts associated with the plurality of UEs and the plurality of databases associated with the plurality of UEs. The L2 module may then send a new cell configuration request with one or more predefined cell attributes, the one or more predefined cell attributes being associated with the attributes used to initially configure the L1 module. The L1 module may then configure the DL and UL processing chains of the L1 module and transition to a configured state, and the L1 module sends a cell configuration response message to the L2 module post transitioning to the configured state.

[0026] The request response communication includes sending a PHY start message by the L2 module to restart the cell at a given SFN (System Frame Number) obtained from the SLOT indication. The L1 module can then reset multiple databases, resume real-time DL and UL processing chains, and then send a PHY response message to the L2 module.

[0027] In an exemplary embodiment, the system (110) completes the request-response communication within a predefined expiration time T310 plus a timeout period of a timer of a second predetermined time T311, the predefined time interval of the request-response communication being less than or equal to the predefined disruption time interval.

[0028] In an exemplary embodiment, the system (110) can avoid reloading predefined channel associated lookup tables for multiple physical signals, including but not limited to those defined by the 5GL1 wireless protocol, from file input / output (file I / O) operations that take a predefined few hundred microseconds per load because they are slow file I / O operations, and instead store the lookup tables that were initially loaded when the cell was first brought up in secure memory and retrieve them from memory for L1SW operations.

[0029] In an exemplary embodiment, the communications network (108) may include at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or combinations thereof, etc., one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, etc. The networks may include, by way of example and not limitation, one or more of a wireless network, a wired network, the Internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad-hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, and some combination thereof.

[0030] FIG. 2 shows an exemplary representation of a flow diagram related to the proposed method, according to one embodiment of the present disclosure.

[0031] As shown, the proposed method includes multiple steps, which may include reaching an unexpected state at the L1SW or encountering an unexpected event or unexpected attribute of the state, at 204, and an error indication message is notified from the L1SW to the L2SW, indicating to the L2SW that an unrecoverable error condition has occurred, which requires the L2SW to perform a fail-safe defense procedure and initiate a cell close process to newly resume L1SW cell transmission and reception, in which the L1SW terminates all currently ongoing uplink (UL) and downlink (DL) tasks and does not schedule any pending UL and DL tasks for 0.5 ms (for 5G mu=1 topology) transit time interval (TTI).

[0032] At 206, the method may include sending a stop message to the L1SW when the L2SW receives the error indication message from the L1SW. The L1SW is a software layer that provides services to the L2SW, and therefore the L2SW is a master of the L1SW.

[0033] At 208, the method may include executing a PHY stop service provided by the L1SW, where all uplink and downlink processing tasks are closed and the L1SW gracefully terminates L1UL and DL processing from that 0.5 ms TTI system frame number onwards, followed by the L1SW sending a PHY stop response to the L2SW.

[0034] At 210, the method can include reinitializing the L1SW, all its UL and DL structures, contexts, and pointers such that the L1SW is likely to be fully reset from the unexpected condition encountered in step 1. The state of the L1SW is then changed from a running state to a dormant state.

[0035] At 212, the method can include continuing to send the 0.5 ms SLOT indication by the L1SW to the L2SW even after receiving the PHY stop and its UL and DL processing chains have been stopped in steps 3-4. This is necessary because the L1SW is the timing master and must provide the 0.5 ms SLOT indication as a timing tick to the L2SW so that the L2SW timing (running or current system frame number (SFN)) and user equipment (UE) timing remain synchronized when the cell is eventually restarted in step 10.

[0036] At 212, the method may include retaining, by the L2SW, all UE contexts of UEs currently connected in the system when step 1 was encountered, and the L2SW continuing to tick its scheduler every SLOT indication tick. Although the L1SW has stopped operating, all UE contexts are kept active in the L2SW until the sum of timers T310 and T311 expire. Meanwhile, the L2SW sends a new configuration request message to configure the L1SW with the same cell attributes that were used to initially configure the cell.

[0037] At 214, the method may include reconfiguring the L1SW DL and UL processing chains and changing its software state from a dormant state to a configured state by the L1SW upon receiving a cell configuration request message from the L2SW.

[0038] At 216, the method may include sending, by the L1SW, a response message, referred to as a cell configuration response message, to the L2SW upon successful configuration of the cell.

[0039] At 218, the method may include, upon receiving the successful cell configuration response message, initiating the L1SW in the SFN currently being run by the L2SW by sending a PHY start message to the L1.

[0040] At 220, the method may include resetting DL and UL processing chains and associated task contexts and pointers to prepare for processing DL transmit packets and UL receive packets every 0.5 ms TTI by the L1SW upon receiving the PHY start message.

[0041] At 222, the method may further include transmitting, by the L1SW, a PHY response message indicating that the L1SW is now in a running state and will start processing DL transmit packets and UL receive packets every 0.5 ms TTI in accordance with the DL configuration request and UL configuration request configuration messages received, respectively, from the L2SW.

[0042] In an exemplary embodiment, the attribute can be checked by the L1SW, and if it is in error or encounters other unexpected cases where the HW accelerator requires too many cycles to complete, the step of 202 is triggered by the L1SW to reset and restart the queues of the hardware accelerator and the hardware accelerator core. This reset of step 0 is typically completed within 100 milliseconds while steps 202-220 are running in parallel. Thus, the cell is recovered within the disruption time of 100 milliseconds (the sum of the T310 and T311 timers), thus minimizing the impact in terms of cell disruption and KPI degradation as described in the method above.

[0043] Thus, the present disclosure provides a unique and efficient system that facilitates a fail-safe methodology in the network and ensures minimal impact in terms of cell outages and KPI degradation.

[0044] Although considerable emphasis has been placed herein on the preferred embodiment, it should be understood that many embodiments may be made and many changes may be made in the preferred embodiment without departing from the principles of the invention. These and other changes in the preferred embodiment of the invention will be apparent to those skilled in the art from the disclosure herein, and it should be clearly understood that the foregoing description is to be taken merely as illustrative and not limiting of the invention.

[0045] The present disclosure provides techniques for constructing networks in which nodes are fail-safe.

[0046] The present disclosure provides a system that facilitates minimal network disruption time so that network KPIs are impacted as little as possible.

[0047] The present disclosure provides a method that enables the L1SW to meet high availability and is a defense of the gNodeB against unexpected L1SW exceptions in live deployment.

Claims

1. 1. A system for minimizing cell outages and key performance indicator (KPI) degradation by ensuring fail-safe nodes, the system comprising: A cell is provided. a plurality of user equipments (UEs) communicatively coupled to the network; one or more electronic devices (gnodes) in the network configured to create, receive, and / or transmit information over a communication channel communicatively coupled to the plurality of user equipment; one or more hardware accelerators communicatively coupled to the one or more gnodes, the one or more hardware accelerators configured to process the information received via communication by a layer 1 (L1) module associated with a physical (PHY) layer of the network in accordance with uplink and downlink configuration instructions received for each predefined transit time interval (TTI) received from a layer 2 (L2) module associated with a data link layer of the network; Including, The L1 module further includes a processor that executes a set of executable instructions stored in a memory, the processor, upon execution of the executable instructions, transmitting to the L1 layer: monitoring one or more inconsistencies in the information received by the one or more hardware accelerators; extracting from the one or more mismatches a set of attributes that relate to out-of-range attributes received from the L2 module or unexpected attributes passed by the L1 module to the one or more hardware accelerators in the predefined TTI, causing the one or more hardware accelerators to use excessive cycles to complete processing of the information or not at all; resetting one or more queues in the hardware accelerator and / or cores of the hardware accelerator based on the extracted set of attributes; Run the command, the resetting takes the predefined outage time interval such that the predefined outage time interval is less than an expiration time associated with a Radio Link Failure Timer (T310) timer coupled to the network; resetting the one or more queues in the hardware accelerator and any or a combination of the cores of the hardware accelerator is performed in parallel with performing a request response communication for cell restart by the L1 module simultaneously with the L2 module for a predefined time interval, the request response communication for cell restart including sending an error indication message to the L2 module; the L2 module deactivates functionality of the L1 module until the combination of one or more queues in the hardware accelerator and the cores of the hardware accelerator is restarted; the UEs in the cell are configured to remain in a Radio Resource Connected (RRC) connected state because the predefined outage time interval is less than an expiration time of the T310 timer. A system characterized in that

2. 2. The system of claim 1, wherein the plurality of UEs connected to the network experience a radio link failure in a second time interval, the duration of the second time interval being less than a duration of the predefined disruption time interval.

3. The system of claim 1 , wherein UEs connected to the network do not transition to an RRC idle state.

4. 2. The system of claim 1, wherein the request response communication further includes stopping real-time downlink (DL), uplink (UL) processing chains and transitioning an L1 module from a running state to a dormant state, and the L1 module responds to the L2 module with a physical stop response message.

5. 5. The system of claim 4, wherein the request response communication further includes deactivation of the L1 module by the L2 module, the L1 module continuing to perform one or a combination of: sending a SLOT indication to keep an L2 scheduler running from a tick of a system frame number (SFN) and not causing the L2 module to clear one or more contexts associated with the plurality of UEs and a plurality of databases associated with the plurality of UEs.

6. 6. The system of claim 5, wherein the request response communication further comprises sending, by the L2 module, a new cell configuration request having one or more predefined cell attributes, the one or more predefined cell attributes being associated with the attributes used to initially configure the L1 module.

7. 7. The system of claim 6, wherein the request response communication includes configuring the DL and UL processing chains of the L1 module to transition to a configured state, and the L1 module sends a cell configuration response message to the L2 module post transitioning to a configured state.

8. 8. The system of claim 7, wherein the request response communication includes sending a PHY start message by an L2 module to restart the cell at a predefined SFN (System Frame Number) derived from the SLOT indication.

9. 10. The system of claim 8, wherein the request response communication further comprises: resetting, by the L1 module, the plurality of databases to restart the real-time DL and UL processing chains, and then sending a PHY response message to the L2 module after the L1 module transitions to a running state.

10. The system of claim 1 , wherein the predefined time interval for the request response communication for cell restart is less than or equal to the predefined disruption time interval.

11. 1. A method for minimizing cell outages and key performance indicator (KPI) degradation by ensuring fail-safe nodes, the method comprising: monitoring for one or more discrepancies in information received by one or more hardware accelerators, the one or more hardware accelerators being communicatively coupled to one or more electronic devices (gnodes), the gnodes being configured to perform one or a combination of: creating, receiving, and transmitting information over a communication channel communicatively coupled to a plurality of user equipment; the one or more hardware accelerators are configured to process the information received via communication by a Layer 1 (L1) module associated with a physical (PHY) layer of the network according to uplink and downlink configuration instructions received for each predefined transit time interval (TTI) from a Layer 2 (L2) module associated with a data link layer of the network, the L1 module further comprising a processor for executing a set of executable instructions stored in a memory; extracting from the one or more mismatches a set of attributes that relate to out-of-range attributes received from the L2 module or unexpected attributes passed by the L1 module to the one or more hardware accelerators within the predefined TTI, where the one or more hardware accelerators use excessive cycles to complete processing of the information or do not complete at all; resetting one or more queues in the hardware accelerator and / or cores of the hardware accelerator based on the extracted set of attributes; Including, the resetting takes the predefined outage time interval such that the predefined outage time interval is less than an expiration time associated with a Radio Link Failure Timer (T310) timer coupled to the network; the step of resetting the one or more queues in the hardware accelerator and the any or combination of the cores of the hardware accelerator is performed in parallel with simultaneously performing a request-response communication by the L1 module with the L2 module for a predefined time interval, the request-response communication for cell restart including sending an error indication message to the L2 module; the L2 module deactivates functionality of the L1 module until the combination of one or more queues in the hardware accelerator and the cores of the hardware accelerator is restarted; the UEs in the cell are configured to remain in a Radio Resource Connected (RRC) connected state because the predefined outage time interval is less than the expiration time of the T310 timer. method.

12. 12. The method of claim 11, wherein the plurality of UEs connected to the network experience a radio link failure for a second time interval, the duration of the second time interval being less than a duration of the predefined disruption time interval.

13. The method of claim 11 , wherein the UEs connected to the network do not enter an RRC idle state.

14. 12. The method of claim 11, wherein the request response communication further includes stopping real-time downlink (DL), uplink (UL) processing chains and transitioning an L1 module from a running state to a dormant state, and the L1 module responds to the L2 module with a physical stop response message.

15. 15. The method of claim 14, wherein the request response communication further includes deactivating the L1 module by the L2 module, the L1 module continuing to perform one or a combination of: sending a SLOT indication to keep an L2 scheduler running from a tick of a method frame number (SFN); and causing the L2 module not to clear one or more contexts associated with the plurality of UEs and a plurality of databases associated with the plurality of UEs.

16. 16. The method of claim 15, wherein the request response communication includes sending, by the L2 module, a new cell configuration request having one or more predefined cell attributes, the one or more predefined cell attributes being associated with the attributes used to originally configure the L1 module.

17. 17. The method of claim 16, wherein the request response communication includes configuring the DL and UL processing chains of the L1 module and transitioning the L1 module to a configured state, the L1 module sending a cell configuration response message to the L2 module post transitioning to the configured state.

18. 20. The method of claim 17, wherein the request response communication includes transmitting, by the L2 module, a PHY start message to restart the cell at a predefined Method Frame Number (SFN) obtained from the SLOT indication.

19. 20. The method of claim 18, wherein the request response communication further comprises resetting, by the L1 module, the plurality of databases, restarting the real-time DL and UL processing chains, and then transmitting a PHY response message to the L2 module following the L1 module transitioning to a running state.

20. The method of claim 11 , wherein the predefined time interval for the request response communication for cell restart is less than or equal to the predefined disruption time interval.

Images