FORM 2
THE PATENTS ACT,1970
(39 of 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See Section 10 and Rule 13)
Title of invention:
A YSTEM AND METHOD FOR STREAMLINING TRANSACTION FLOW IN A DISRUPTED OR FAILED COMMUNICATION
Applicant:
Entrib Technologies
Having address:
Concord Proxima. Survey # 85-A, Bldg C-202,
Baner,Pune411045,
Maharashtra, India
The following specification particularly describes the invention and the manner in which it is to be performed.

FIELD OF THE INVENTION
The present invention relates to the field of information and communication technology (ICT) for handling mobile/cellular communication network failures. More particularly, it relates to a system and method for streamlining transaction flow in a disrupted or failed communication between a mobile client and a data server.
BACKGROUND OF THE INVENTION
With the advent of a mobile phone also known as a cellular phone, cell phone and a handheld device, it becomes easier to make and receive telephone calls over a radio link whilst moving around a wide geographic area through a wireless communication network. The wireless communication network allows a mobile communication device that can move around a geographical area and can establish a communication between two or more parties. Further with the arrival of current telecommunication revolution, most of the mobile or handheld devices are now equipped with utilizing Edge, GPRS, 2G, 3G and 4G data along with voice networks. With the accessibility of such communication networks, the manufactures of mobile devices come up with a new mobile device which is commonly known as "Smartphone's". The smart phones combined the functions of a personal digital assistant (PDA) with a mobile phone. These Smartphone's can perform many interesting business tasks such as mobile application interaction with the data server, emails exchange, online banking etc with the use of communication networks along with traditional phone calling features that continue to use the voice network.
Information and communication technology (ICT) has evolved and now it is geared up to amend traditional processing and execution of such tasks. Due to certain limitations in the bandwidth of the communication network and geographical constraints, it is quite often that network connectivity disrupts while the application installed in the mobile device is communicating with the data server. It has been further observed that, the communication networks support provided by most of the telecom operators is still vulnerable and sometimes

not even available in certain remote areas or more particularly while the user is travelling. Under such scenarios, if the mobile device is being used to perform for certain business tasks that need communication network then, said business task can't be successfully executed due to lack of such communication networks.
In such situations of the intermittent or complete lack of network connectivity, the user experiences task failure, session expiration and incomplete operations or have to wait till the communication network becomes available. Even though, if certain operations are buffered in local mobile devices, the data server side updation and acknowledgement still remains a bottleneck. One of the attempts to solve the above identified problem is to completely work on the premise where no communication network is available and further enable the mobile application installed in the mobile device, functions as a local or native application. The application business logic saves the application data locally within the memory of the mobile device that allows performing the tasks in the offline mode. Further a 'sync' mechanism is used-to synchronize the local data stored in the memory-of-the mobile-device with the data-server. In such system, it is essential to periodically synchronize the data in a batch mode with the back-end servers by physically connecting the mobile device to the same network where the back-end servers are running.
It has been observed that some attempted solutions have tried to negotiate the aforesaid problem, but this has not sufficiently addressed the needs of the industry owing to its awkwardness and fragility. Thus, in view of the lacunae observed in the art there is a long-felt need in the art for a system and method that enables dynamic streamlining of transaction flow in a disrupted or failed communication between a mobile client and a data server. Further, there is a need in the art for the system and method that enables synchronization between the mobile device and the data server in the sequential order and thereby maintaining the session for each failed or disrupted transaction.

OBJECTS OF THE INVENTION
The primary object of a present invention is to enable a system and method for streamlining transaction flow in a disrupted or failed communication between a mobile client and a data server.
Yet another object of the invention is to provide a system and method for creating a replication copy of a data schema, employed at the data server, at the mobile client that allows a user to work offline in case of non-availability of a communication networks.
Yet another object of the invention is to provide a system and method for maintaining the transactional integrity over a number of disrupted or failed transactions in a disrupted transaction queue.
Yet another object of the-invention is to provide a system and method for sequentially synchronizing the failed or disrupted transaction with the data server in case of availability of the communication networks.
Yet another object of the invention is to provide a system and method for creating the user specific replication copy of data schema for each application at the local database of the mobile client.
Still another object of the present invention is to provide a computer-implemented system having one or more processor executable modules for achieving at least one of the aforesaid objects of the present invention.
SUMMARY OF THE INVENTION
Before the present systems and methods, enablement are described, it is to be understood that this application is not limited to the particular systems, and methodologies described, as there can be multiple possible embodiments which are not expressly illustrated in the present

disclosures. It is also to be understood that the terminology used in the description is for the purpose of describing the particular versions or embodiments only, and is not intended to limit the scope of the present application
The present invention discloses a system and method for streamlining transaction flow in a disrupted or failed communication between a mobile client that is communicatively coupled with a data server. Further, the system and method further enables the mobile client to communicate with the data stored at data server in both the scenarios where the communication network is available (online mode) and also when the communication network is not available (offline mode). In an exemplary embodiment, the present invention introduces a system and a method for enabling data communication in a disrupted or failed communication between the mobile client and the data server is disclosed herein. The system and method further facilitates, at the mobile client, to create at least one replication copy of a data schema employed at the data server. The system and method is further adapted to extract a pre-identified dataset from the data server and-storing said dataset in said replication copy by means of a data extraction module. The replication copy allows a user to work offline by processing transaction using said dataset on the replication copy stored in the local database. The system and method further comprising a disrupted transaction queue employed at the mobile and at the data server to sequentially store each disrupted or failed transaction in an order of disruption instance wherein the disruption instance enables the method of the invention to determine the time of occurrence of the disruption while the mobile client is communicating with the data server.
In one embodiment of the invention, to resume such disrupted transactions from the mobile client to the data server, a request background controller is configured to extract a current state of each transaction from the disrupted transaction queue and further enabled to create a new session for said extracted transaction having a unique session id. The system and method further reiteratively detects the availability of network connectivity and upon detection thereof a flag detector is configured to detect flag value at the data server for transaction pendency in a related disrupted transaction queue. The system and method further enabled to

synchronize one or more updated instance in the replication copy stored in the local database with the data server to resume sequentially disrupted transactions from the disrupted transaction queue by means of a synchronizing module.
In another embodiment of the invention, to resume the disrupted transactions from the data server to the mobile client, a request id manager is configured to receive the disrupted transaction from the disrupted transactions queue. The system and method further reiteratively detects the availability of network connectivity and upon detection thereof the flag detector is configured to detect flag value at the mobile client for request pendency in a related disrupted transaction queue. The system and method further enabled to synchronize one or more updated instance in the replication copy stored in the local database with the data server to resume sequentially disrupted transactions from the disrupted transaction queue by means of a synchronizing module.
BRIEF DESCRIPTION OF DRAWINGS
The foregoing summary, as well as the following detailed description of embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there is shown in the present document example constructions of the invention; however, the invention is not limited to the specific methods and apparatus disclosed in the document and the drawings:
Figure 1 is an architecture diagram (100) illustrating different elements required for streamlining transaction flow in a disrupted or failed communication platform according to an exemplary embodiment of the invention.
Figure 2 is an architecture diagram (200) illustrating different components configured with the mobile client to handle the data submission, according to an exemplary embodiment of the invention.

Figure 3 is an architecture diagram (300) depicts the components involved on the data server to handle the data request sent by the mobile client, according to an exemplary embodiment of the invention.
Figure 4 to 8 are the sequence diagram (400) depicts the message flow when the mobile network is available, when the mobile network is not available at the mobile or at the data server, according to an exemplary embodiment of the invention.
The figures depict various embodiments of the present invention for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the invention described herein.
DETAILED DESCRIPTION OF THE INVENTION
Some embodiments of this invention, illustrating all its features, will now be discussed in detail. The words "comprising," "having," "containing," and "including," and other forms thereof, are intended to be equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items, or meant to be limited to only the listed item or items. It must also be noted that as used herein and in the appended claims, the singular forms "a," "an," and "the" include plural references unless the context clearly dictates otherwise. Although any systems and methods similar or equivalent to those described herein can be used in the practice or testing of embodiments of the present invention, the exemplary, systems and methods are now described. The disclosed embodiments are merely exemplary of the invention, which may be embodied in various forms.
The present invention enables a system and method streamlining transaction flow in a disrupted or failed communication between a mobile client and a data server. The mobile client is configured with a local database to install a plurality of application. Each installed

application in the mobile client is capable of communicating with a data server through a communication network. Further each application is adapted to extract data stored in server database which is further configured with the data server. In embodiment of the invention said server database is residing within the data server wherein in another embodiment, said server database is communicatively coupled with the remotely located data server. Each database is having a data schema that further comprises a plurality of data fields wherein each data field is configured to store a specific type of data.
The method and system of the present invention facilitates to create a replication copy of data schema employed at the data server and replicate in the local database during availability if the communication network. The present system further enabled to identify and extract a pre-identified dataset from the data server by means of a data extraction module and storing said pre-identified dataset in the replication copy employed at the mobile client. In one embodiment of the invention, the extracted pre-identified dataset stored in the replication copy further enable a user-to-substantially work offline in non-availability or partial availability of wireless communication networks. In offline mode, the user is allowed to execute and process the required tasks on the extracted dataset and further allows the mobile applications installed at the mobile client will continue to function even if there is no communication network available.
The method and system of the present invention further configured a related disruption transaction queue wherein said disruption transaction queue is delegated to maintain a list of failed or disrupted or the transaction that are executed offline in a sequential manner. The disruption transaction queue is a sequentially ordered First in First out (FIFO) queue adapted to enter each disrupted or failed transaction in an order of disruption instance and resume processing of said queued transactions, upon receiving network connectivity.
The method and system of the present invention further configured a flag detector employed at the data server and the mobile client for detecting flags in a related disrupted transaction queue in order to complete the transaction flow. In one embodiment of the invention, the a

request flag and a transaction flag is further respectively configured at the data server and the mobile client are the binary values such as "0" or "1" that are updated upon the state of each transaction. Each transaction flow is having a plurality of disruption or failed transactions that are determined based on a disruption instance. The disruption instance in the disrupted transaction queue is the time of occurrence of a complete disconnection or a partial disconnection state having signal strength below a predefined threshold value between the mobile client and the data server.
The method and system of the present invention further configured a synchronizing module to synchronize only the updated instance in the replication copy stored in the local database with the data server to resume sequentially earlier disrupted transaction wherein a previous state of the transaction is stored in a cache memory of the mobile client and upon confirmation therefrom, the processed dataset is updated with the server. In one embodiment of the invention, the synchronizing module further configured with a request count updater module that is communicatively coupled with a request background controller which is further communicatively coupled with the disrupted transaction queue. The request background controller is adapted to extract a current state of each transaction from the disrupted transaction queue of the mobile client and further adapted to create a new session for said extracted transaction having a unique session id. The request count updater module is further adapted to update, the count of pendency and the transactions performed in offline mode that are stored in the disrupted transaction queue, on a client user interface to keep informed user that how many requests are there in the in the disrupted transaction queue.
The request background controller is further configured with an offline storage manager module, a request timeout manager, a session ID module and a network status module that are collectively performing the synchronization of the failed or disrupted tasks stored in the disrupted transaction queue with the data server by reiteratively detecting the availability of the communication network connectivity. Further upon detection of the communication network, the system and method further adapted to detect the flag value at the data server for transaction pendency and further synchronize each detected pending disruption instance of

transaction with the associated data server by replacing an earlier session of each disruption instance in the disrupted transaction queue with a current session by means of the session ID module. The request timeout manager is adapted to dynamically check the timeouts for request submission. The request timeout manager is further adapted to check type of network (2G. 3G. and EDGE etc.) and accordingly increases or decreases the request timeout value. The offline storage manager module further adapted to store and fetch data and writes/update requests to and from the local database. The network status module is further adapted to check the status of the communication network availability and updates the request background controller with the status.
Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. For example, although the present invention will be described in the context of a system and method for streamlining transaction flow in a disrupted or failed communication between a mobile client communicatively coupled with a data server, one of ordinary_skill in the art will readily recognize that the system and method can be utilized in any situation where there is a need to manage the data integrity in a disrupted or failed communication between any communication device is communicating with a data server and further synchronizing the failed or disrupted tasks with the data server on resumption of the communication network. Thus, the present invention is not intended to be limited to the embodiments illustrated, but is to be accorded the widest scope consistent with the principles and features described herein. Various embodiments of the present invention will now be described with the help of appended figures.
Referring to figure 1 is a system architecture diagram (100) illustrating different elements required for streamlining transaction flow in a disrupted or failed communication platform according to an exemplary embodiment of the invention according to an exemplary embodiment of the invention. As illustrated in figure 1. the system comprises of a mobile client (102) that is communicatively coupled with a data server (106) through a communication network (104). In an exemplary embodiment the mobile client (102) is an electronic communication device selected from a group consisting of a computer, a laptop, a

Smartphone and combinations thereof. In one embodiment, the mobile client (102) is a stand alone electronic device. Tn alternative embodiments, the mobile client (102) is an electronic device electronically coupled to various other electronic devices in the communication network (104).
In an exemplary embodiment of the invention, the method of the present invention further enables the multiple applications installed at the mobile client (102) to perform data processing tasks on the data that is stored at the data server (106) by means of the communication network (104). Further it has been observed while moving in the remote location or the places where the communication network (104) coverage is less spotty, the mobile client (102) is unable to communicate with the data server (106) and hence could not able to perform the desired task. In such scenarios the present invention enables to create a replication copy of data schema at the mobile client (102) that enables said mobile client (102) to execute the desired tasks in offline mode or in non availability of communication network(104):
Referring to figure 2 is a system architecture diagram of the mobile client (200) illustrating different components configured with the mobile client (200) to handle the data submission, according to an exemplary embodiment of the invention. As illustrated in figure 2, the mobile client (200) further comprises of a client user interface (202) that is configured with a synchronization module (204) wherein said synchronization module (204) further comprises of a request count updater module (206), a background request background controller (208), and a disrupted transaction queue (210). The background request background controller (208) further configured with an offline storage manager module (212), a request timeout manager (214), a session ID module (216) and a network status module (218). The synchronization module (204) further electronically coupled with a local database (220), a data extraction module (222) and a flag detector (224).
In an exemplary embodiment of the invention, the method for the resumption of disrupted transactions or a transaction flow from the mobile client (200) to the data server enables the

mobile client (200) to create a replication copy of the data schema stored in the local database (220). Further the data extraction module (222) is adapted to extract a pre-identified dataset from the data server and store said pre-identified data in the local database (220). In one embodiment of the present invention, the system and method further enables a user of the mobile client (200) to perform plurality of data processing tasks on the pre-identified dataset in offline mode or during non-availability of the communication network. In an embodiment of the invention, the system and method further enables to serially maintain the failed or disrupted transactions stored in the disrupted transactions queue (210) during loss of the communication network while pursuing communication between the mobile client (200) and the data server. The present invention further enables to synchronize the failed or disrupted transactions stored in the disrupted transactions queue (210) with the data server by means of the synchronizing module (204).
In an exemplary embodiment of the invention, the synchronizing module (204) further comprises the request background controller (208) adapted to extract a current state of each-transaction from the disrupted transaction queue (210) from the mobile client (200) and further adapted to manage background request submission. The request background controller (208) further scheduled to run periodically at a pre-defined interval of time to fetch failed or disrupted transactions from the disrupted transaction queue (210) which is further stored in the offline storage manager module (212). In an embodiment, the replication copy is configured to cooperate with the local database (220) of the mobile client (200) by means of user specific key-value pairs as identified by the offline storage manager module (212). In one embodiment of the invention, the session ID module (216) in the synchronizing module (204), further adapted to create a new session for each failed or disrupted transaction by assigning a new session ID. To synchronize the fetched failed or disrupted transactions, with the data server, the network status module (218) in the synchronizing module (204) reiteratively detecting the communication network connectivity and upon detection thereof, the flag detector (224) in the synchronizing module (204) further detects a flag value at the data server for transaction pendency to synchronize each detected pending disruption or failed transaction with the associated data server using the new session ID. The request

timeout manager (214) in the synchronizing module (204) is further configured to update the client user interface (202) after the receiving the successful acknowledgement from the data server of each disrupted or failed transaction. The request timeout manager (214) is adapted to manage the dynamic variance of data speeds and response time due to variable nature of data type of networks. The mobile/cellular data networks are still spotty and the type of network (Edge, 2G, 3G, and 4G) and bandwidth available for the mobile phones while submitting data requests may vary. Based on the available network and the bandwidth the time taken to submit the data requests can also vary. This can result in the request getting timed-out on the client since now response is received from the server within a given period of time. In order to manage such spotty and variable type of data network, the request timeout manager (214) is adapted to intelligently check type of network (2G, 3G, and EDGE etc.) and accordingly increases or decreases the request timeout value to ensures that optimum time is given for request submission before timeout happens. In order to achieve such dynamic variance in request submission and response thereof depending on the different types of network to deal with, the request-timeout-manager (214) is configured to include a specific request timeout value dependent on the available network type and the bandwidth in each of the requests submitted by the mobile client app. For example, if the network type is 2G, 3G or 4G the request timeout duration specified can be of 15 seconds while if the network type is Edge then the request timeout duration can be of 30 seconds so as to handle data submission on low network bandwidth.
Referring to figure 3 is a system architecture diagram of the data server (300) illustrating the components involved on the data server (300) to handle the data request sent by the mobile client, according to an exemplary embodiment of the invention. As illustrated in figure 3, the data server (300) comprises of a request ID manager module (302) a server database (304) and a server flag detector (306). In one embodiment of the invention, the server database (304) is residing within the data server (300) wherein in another embodiment the server database (304) is remotely located and communicatively coupled with the data server (300) to store the synchronized transactions enabled by the synchronizing module on resumption of the communication network. In an exemplary embodiment of the invention, the request ID

manager module (302) is configured to manage the request sent by the mobile client in the form of failed or disrupted transactions for synchronizing with the data server (300). The request ID manager module (302) is further adapted to maintain the request ID in the server database to ensure that the transactions have been made by the mobile client. The request ID manager module (302) further manages the data integrity on the server side by ensuring the dirtiness check that not allows the user of the mobile client to do any further changes to the made transactions until the request is synchronized with the data server (300).
Referring to figure 4 to 9 are the sequence diagram (400) depicts the message flow when the mobile network is available, when the mobile network is not available at the mobile or at the data server in different scenarios, according to an exemplary embodiment of the invention.
As illustrated in figure 4, the sequence diagram depicting the message flows when mobile data network is available in following pre-condition:
• Mobile/Cellular data network connection is-available
Following is the typical mobile client system behavior,
At step (408) and (410), user successfully logs-in to the data server (406).
At step (412), on successful log-in, the mobile client user interface (402) saves the user's one-way encrypted (SHA-1) password in the local database (404).
At step (416). mobile client user interface (402) fetches data needed for next subsequent screens.
At step (420), each dataset fetched from server is stored in mobile phone's local database (404) specific to logged-in user.
At step (422). the dataset stored in the local database (404) is thus always refreshed/synced with the data server (406) at each login.
As illustrated in figure 5, the sequence diagram depicting the message flows when data network is available, mobile client does background submission of data using background

timer wherein background timer also takes care of data integrity and data request submission spanning multiple sessions in following pre-conditions:
• Mobile data network is available.
• There are pending write/update requests available in local data store for the logged-in user
Following is the mobile client app behavior,
At step (510). user successfully logs-in to the data server (508).
At step (514), the mobile client user interface (502) starts the background timer (504).
At step (508). the background timer (504) checks for the pending write/update requests in local database (506).
At step (522) and (528), for each pending write/update requests found, update the session id with the current session id.
At step (530), the background timer (504) submits the request.
At step (538), on successful submission, background timer (504) updates the pending request count on the mobile client user interface (502).
As illustrated in figure 6, the sequence diagram depicting the message flow when mobile the communication network is not available at the time of mobile client application launch in following pre-conditions:
• Mobile communication network is not available.
• User launches the mobile application.
• User has done one successful login earlier when the communication network was available.
Following is the typical mobile client system behavior in this scenario:
At step (608), during availability of the communication network: the mobile client sends the
user login request to data server (606).
At step (610), the user login request times-out and mobile client gets an error.

At step (612), the mobile client offers whether the user wants to continue using the
application in offline mode.
At step (614), if user is answers 'yes' for offline mode, mobile client authenticates users
password against encrypted password stored in local database (604).
At step (618), mobile client application then extracts data stored in local database (604) for
logged-in user.
At step (620), mobile client application builds client user interface (602) screens using data fetched and stored in the local database (604).
As illustrated in figure 7, the sequence diagram depicting the message flow during data connection loss on data submits at the mobile client. Following are the pre-conditions for the aforesaid sequence diagram:
• Mobile data network is available.
• User has logged in successfully.
• User enters some data,en_teredjn the mobile client user interface and has„c.licked.on submit.
• Mobile data network is not available after submitting the task.
Following is the typical mobile client system behavior in this scenario:
At step (710), the mobile client submits the data write/update request to the data server (706).
At step (714), the data write request times-out and mobile client gets an error.
At step (718), the mobile client simply writes the data write/update request to local database
(704).
At step (722), the pending write/update request count gets displayed on the mobile client user
interface (702).
As illustrated in figure 8, the sequence diagram depicting the message flow during data connection loss after successful data write to the data server. Following are the preconditions for the aforesaid sequence diagram:
• Mobile communication network is available.

• User has logged in successfully.
• Data Write/Update request is sent from the mobile client.
• Data write/update request reaches the data server successfully and data gets written/ updated at the data server.
• At this time, mobile communication network connection between the mobile client and the data server is lost.
• Data server tries to send the response but since there is no communication network available, mobile client times out waiting for the response from the data server.
• Mobile communication network may become available after some time.
Following is the typical mobile client system behavior in this scenario:
At step (816). mobile client sends write/update request to data server (806) with a unique
request identifier.
At step (818) the data server checks the request identifier with Requestld_manager module
(808).
• if request identifier is not found, data server (806) executes the write/update request and data gets written in server database (810).
• if request identifier is found, data server (806) simply returns success that response again may or may not reach the mobile client. If response is reached, offline synchronization module deletes the request from local database (804) else tries resending on resumption of the communication network.
At step (826), the data server (806) saves the successful request identifier into request id
manager module (826).
At step (830), timeout occurs due to connection failure when the request id manager module
(826) tries to send acknowledgement to the local database (804). the mobile client (802) at
step (832) saves the write/update request in the local database (804) for logged-in user.
At step (836), the pending write/update request count gets displayed on the client user
interface (802).

ADVANTAGES OF THE INVENTION
• The present invention enables to streamline the transaction flow in a disrupted or failed communication between a mobile client and a data server.
• The present invention also enables a user to execute the desired tasks from the mobile communication device in offline mode by accessing the data stored at the data server during non-avai I ability of communication network.
• The present invention further enables to synchronize the accessed and updated data with the data server and thereby maintaining the data integrity on resumption of communication network.
• The present invention further enables to dynamically change the request timeout duration
-by- detecting the type of communication network (Hke-2G 3G, Edge, GPRS) and
accordingly increases or decreases the request timeout value.
• The present invention further enables to submit data requests for a particular user to span across multiple sessions.
• The present invention further enables a user to execute business tasks by manually selecting the mode (offline/online) while communicating with the data server during spotty communication network or weaken bandwidth.

Claims:
1. A method for streamlining transaction flow in a disrupted or failed communication
between a mobile client and a data server, the method comprising steps of:
a) at the mobile client, creating at least one replication copy of a data schema employed at the data server;
b) extracting from the data server and storing a pre-identified dataset in said replication copy in a manner such that the replication copy allows a user to work offline by processing transaction using said dataset on the replication copy stored in a local database;
c) at the data server and the mobile client, detecting flags in a related disrupted transaction queue for completing the transaction flow, wherein the related disrupted transaction queue is determined based on a disruption instance; and
d) synchronizing one or more updated instance in the replication copy stored in the local database with the data—server—to resume sequentially earlier disrupted — transactions, wherein a previous state of the transaction is stored in a cache memory of the mobile client and upon confirmation therefrom, the processed dataset is updated with the server by means of a synchronizing module.

2. The method of claim 1, wherein the transaction flow is resumed for a plurality of wireless communication networks including 2G, 3G, 4G, Edge, GPRS, Wi-Fi and Wi-Max networks.
3. The method of claim 1, wherein the replication copy is further configured to allow the user to work offline in non-availability or partial availability of wireless communication networks.
4. The method of claim 1, wherein the disrupted transaction queue is a sequentially ordered First in First out (FIFO) queue adapted to enter each disrupted or failed transaction in an order of disruption instance thereof and resume processing of said queued transactions, upon receiving connectivity, in the said order.

5. The method of claim 4, wherein the disruption instance is the time of occurrence of a complete disconnection or a partial disconnection state having signal strength below a predefined threshold value between the mobile client and the data server.
6. The method of claim 1. wherein the updated instances are the transactions that are processed offline by the user at the mobile client, wherein each such updated instance is populated into the replication copy for facilitating synchronization with the data server.
7. The method of claim 1. wherein the resumption of disrupted transactions or a transaction flow from the mobile client to the data server comprises steps of:
i) extracting a current state of each transaction from the user specific
disrupted transaction queue of the mobile client by means of a request
background controller; ii) creating a new session for said extracted transaction having a unique —
session id by means of the session-ID module; iii) detecting reiteratively for the availability of network connectivity and,
upon detection thereof, detecting a flag value at the data server for
transaction pendency; and iv) synchronizing each detected pending disruption instance of transaction
with the associated data server using the new session id.
8. The method of claim 1, wherein the resumption of disrupted transactions for a
transaction flow from the data server to the mobile client comprises steps of:
i) receiving from the disrupted transaction queue of the server having a
transaction request id for each transaction associated with the corresponding disruption instances;
ii) detecting a flag value at the mobile client for request pendency; and

iii) synchronizing the each disruption instances with the each detected corresponding pending requests in the local database of at least one associated mobile client.
9. The method of claim 7, wherein the synchronization is performed by replacing an earlier session of each disruption instance in the disrupted transaction queue with a current session.
10. The method of claim 8, wherein the request and transaction flags in the mobile client and the data server are binary values that are updated upon the state of each transaction.
11. A system for streamlining transaction flow in a disrupted or failed communication between a mobile client (200) communicatively coupled with a data server (300). the system comprising: -

a) a local database (220), installed at the mobile client (200), is configured to store a pre-identified dataset for each user;
b) a disrupted transaction queue (210) at the mobile client (200) and the data server (300) is configured to sequentially store each disrupted or failed transaction in an order of disruption instance;
c) a replication copy of a data schema fetched from the associated data server (300) wherein said replication copy is stored in the local database (220) and an client user interface (202);
d) a request background controller (208) communicatively coupled with the local database (220) is configured to extract a current state of each transaction from the associated disrupted transaction queue (210) and to create a new session each for each said extracted transaction, wherein the request background controller is further coupled with a plurality of programmable modules;
e) at the data server (300): a request-id manager module (302) is coupled with the data server for managing the disrupted transaction queue (210) of the server

having a transaction request id for each transaction associated with the corresponding disruption instances;
f) a data extraction module (222) is configured to extract a pre-identified dataset from the data server (300) and storing said replication copy in the local database (220);
g) a server flag detector (306) and flag detector (224), configured at the data server (300) and the mobile client (200) respectively, to detect flags in a related disrupted transaction queue (210); and
h) a synchronizing module (204) configured to populate one or more updated instance in the replication copy stored in the local database (220) and synchronize the updated replication copy at a pre-determined interval with the data server (300) to sequentially resume earlier disrupted transactions.
12. The system of claim 11, wherein the mobile client (200) can be selected from a group
- of cell phone, personal digital assistant (PDA), I-Pad or combinations thereof.
13. The system of claim 11, wherein the replication copy is configured to cooperate with the local database (220) of the mobile client (200) by means of user specific key-value pairs as identified by the offline storage manager module (212).
14. The method of claim 11, wherein the disrupted transaction queue (210) is a sequentially ordered First in First out (FIFO) queue adapted to enter each disrupted or failed transaction in an order of disruption instance.
15. The system of claim II, wherein the request timeout module (214) is further configured to dynamically check the wireless communication networks including 2G, 3G, 4G. Edge, GPRS. Wi-Fi, and Wi-Max networks and accordingly increases or decreases the timeout value.

16. The system of claim 11. wherein said programmable modules coupled with the
request background controller (208) comprise of:
i. an offline storage manager module (212) configured to store and extract the disrupted transaction from the disrupted transaction queue (210) stored in the local database (220);
ii. a session-id module (216) internally coupled with a request timeout module (214) and configured to create a new session-id each for each disrupted transaction in the disrupted transaction queue (210);
iii. a request count updater module (206) configured to facilitate said request background controller to update the current state of each transaction on the client user interface (202); and
iv. a network status module (218) configured to iteratively detect an availability of communication network (104) and communicate alteration therein the network to the request background controller (208).
17. The system of claim 11, wherein the request background controller (208) is adapted to assign a unique session id each for the each extracted transaction and updating
18. The system of claim 11, wherein the each replication copy is stored in the local database (220) for enabling offline operation at the mobile client (200) by processing transaction locally using extracted dataset on the replication copy stored in the local database (220).
19. The system of claim 11, wherein while resuming the disrupted transaction the synchronization module (204) is further adapted to detect a resumption point by accessing a previous state of the transaction stored in a cache memory of the mobile client (200).