Systems and methods for real-time correction of core applications

Abstract

A method for correcting connectivity failures of core applications on a user equipment (UE) is disclosed. The method comprises a client detecting a plurality of request-reply message sequences between a core application and a corresponding server, and learning a set of request-reply message sequences within the plurality of request-reply message sequences that are not producing a connection error with the corresponding server. The method further includes creating a series of ghost replies that each mimic a reply that is one of the set of learned replies coming from the corresponding server and not producing a connection error, and then retaining the series of ghost replies. The method then includes detecting at least one connection error between the core application and the corresponding server, and feeding a ghost reply to the core application.

What is claimed is: 
     
       1. A method for correcting connectivity failures of core applications on a user equipment (UE), the method comprising:
 detecting, via execution of a client on a processor of the UE, a plurality of request-reply message sequences between a core application of a plurality of core applications and a corresponding server; 
 learning, by execution of the client, a set of reply messages within the plurality of request-reply message sequences that are coming from the corresponding server and not producing a connection error with the corresponding server; 
 based on the set of reply messages, creating, by execution of a ghost client on the processor of the UE, a series of ghost replies that each mimics a reply that is one of the set of learned reply messages coming from the corresponding server; 
 retaining, by execution of the client within a memory of the UE, the series of ghost replies; 
 subsequent to retaining the series of ghost replies, detecting, by the client, that the core application has exceeded a threshold number of request messages that are unanswered by the corresponding server due to a lack of reply by the corresponding server; and 
 based on the detecting, feeding, by execution of the client, a ghost reply from the retained series to the core application. 
 
     
     
       2. The method of  claim 1 , further comprising verifying, by execution of the client, that the ghost reply was accepted by the core application without the core application making a connection with the corresponding server. 
     
     
       3. The method of  claim 1 , wherein the client is embedded in at least one of an operating system of the UE and a firmware of the UE. 
     
     
       4. The method of  claim 1 , wherein each of the plurality of core applications are executing on a system level of the UE. 
     
     
       5. The method of  claim 1 , wherein the request messages that are unanswered by the corresponding server due a lack of reply by the corresponding server are based on at least one of a Uniform Resource Locator no longer existing at the corresponding server and the corresponding server no longer being in operation. 
     
     
       6. The method of  claim 1 , further comprising determining, by the ghost client, whether the core application is associated with a security restriction defined by an operating system of the UE, wherein feeding the ghost reply to the core application is responsive to determination that the core application is not associated with the security restriction. 
     
     
       7. The method of  claim 1 , further comprising instantiating, by the ghost client, an identifier for each series of ghost replies created by the ghost client. 
     
     
       8. The method of  claim 7 , wherein the identifier corresponds with at least one of the plurality of core applications such that ghost replies are retrievable based on the identifier. 
     
     
       9. A system for correcting connectivity failures of core applications on a user equipment (UE), the system comprising:
 a UE comprising:
 a transceiver; 
 a memory storing a plurality of core applications; a processor; and 
 a client stored in the memory that, upon being executed and configuring the processor, the processor:
 detects a plurality of request-reply message sequences between a core application of the plurality of core applications and a corresponding server via the transceiver; 
 learns, over a defined time period, a set of reply messages within the plurality of request-reply message sequences that do not produce a connection error with the corresponding server; 
 creates a series of ghost replies that each mimics a reply that is one of the set of learned reply messages coming from the corresponding server and not producing a connection error; 
 retains the series of ghost replies within the memory, 
 subsequent to retention of the series of ghost replies, detects that the core application has exceeded a threshold number of request messages that are unanswered by the corresponding server due to a lack of reply by the corresponding server; and 
 based on the detection, feeds a ghost reply from the retained series to the core application. 
 
 
 
     
     
       10. The system of  claim 9 , wherein the client further configures the processor to verify that the ghost reply was accepted by the core application without the core application making a connection with the corresponding server. 
     
     
       11. The system of  claim 9 , wherein the client is embedded in at least one of an operating system of the UE and a firmware of the UE. 
     
     
       12. The system of  claim 9 , wherein each of the plurality of core applications are executing on a system level of the UE and do not receive at least one of an update and patch that overwrite or alter the core applications to resolve connection errors. 
     
     
       13. The system of  claim 9 , wherein the request messages that are unanswered by the corresponding server due a lack of reply by the corresponding server are based on at least one of a Uniform Resource Locator no longer existing at the corresponding server and the corresponding server no longer being in operation. 
     
     
       14. The system of  claim 9 , wherein the client further configures the processor to: determine whether the core application is associated with a security restriction defined by an operating system of the UE, wherein the ghost reply is fed to the core application responsive to a determination that the core application is not associated with the security restriction. 
     
     
       15. The system of  claim 9 , wherein the client further configures the processor to: instantiate an identifier for each series of ghost replies created by the client. 
     
     
       16. The system of  claim 15 , wherein the identifier corresponds with at least one of the plurality of core applications such that ghost replies are retrievable based on the identifier. 
     
     
       17. A method for correcting connectivity failures of core applications on a user equipment (UE), the method comprising:
 detecting, via execution of a client on a processor of the UE, a plurality of request-reply message sequences between a core application of a plurality of core applications and a corresponding server; 
 learning, by execution of the client over a defined time period, a set of reply messages within the plurality of request-reply message sequences that are not producing a connection error with the corresponding server; 
 creating, by execution of the client, a series of ghost replies that each mimics a reply that is one of the set of learned reply messages coming from the corresponding server and not producing a connection error; 
 retaining, by execution of the client, the series of ghost replies on a memory communicatively coupled to the UE via a wireless network; 
 determining, by the client, that the core application is experiencing a frequency of connection errors with the corresponding server in excess of a predefined threshold; 
 responsive to the frequency of connection errors exceeding the predefined threshold, obtaining, by the client, a ghost reply from the retained series corresponding to the core application; and 
 feeding, by execution of the client, the ghost reply from the retained series to the core application, wherein the ghost reply maintains execution of the core application. 
 
     
     
       18. The method of  claim 17 , further comprising: verifying, by execution of the client, that the ghost reply resolved the at least one connection error without the core application making a connection with the corresponding server. 
     
     
       19. The method of  claim 17 , wherein each of the plurality of core applications are executing on a system level of the UE and do not receive at least one of an update and patch that overwrite or alter the core applications to resolve connection errors. 
     
     
       20. The method of  claim 17 , wherein the connection error is based on request messages from the core application going unanswered by the corresponding server due to at least one of a Uniform Resource Locator no longer existing at the corresponding server and the corresponding server no longer being in operation.