BACKGROUND
The present invention relates to managing transactions in a network. More specifically, it elates to real-time execution of the transactions between a plurality of network devices.
With the growth of wireless technology, various applications are being developed for network devices, which need to continuously synchronize their data with the server. The synchronization is performed by replicating the data from the server on to network devices, and vice versa. However, to be in sync with the server, applications need to stay connected all the time. Usually network devices move in and out of the connectivity network, resulting in loss in connectivity of the applications. This loss in connectivity results in incomplete synchronization of data or termination of transactions.
Various methods are available that solve the problem of occasional disconnectivity. One such method is integrating an acknowledgement request with the data. The acknowledgement request is sent back to the sender if connectivity is available and the data is replicated successfully. If the acknowledgement is not received, the data is replicated again. However, integration of the acknowledgement request with data is not efficient in real-time execution of transactions.
In light of the above discussion, there is a need for a method, system and computer program product for managing real-time execution of one or more transactions between network devices. Further, the method should mask the occasional network disconnectivity from the applications.
SUMMARY
An object of the invention is to manage real-time execution of transactions between requesting applications and server applications executing on a plurality of network devices.
Another object of the invention is to mask the network connectivity from the requesting applications and the server applications.

Another object of the invention is to provide a secure connection between the network devices.
To achieve the objectives mentioned above, the invention provides a method, system and computer program product for managing real-time execution of transactions between a plurality of network devices. The network devices include one or more requesting applications and one or more server applications. One or more transactions are conducted between the requesting applications and the server applications. Further, one or more middleware are installed on the plurality of network devices. The middleware is associated with the requesting applications and the server applications, and are used to synchronize the details of the transactions between the applications. In an embodiment of the invention, the details of the transaction may include the transaction identifier, the state of the transactions, the time of expiry, the security preference, the configuration details, the server application details, and the like. The synchronization masks the occasional network disconnectivity from the requesting applications and the server applications. Thereafter, the transactions are processed, based on the synchronized details.
BRIEF DESCRIPTION OF THE DRAWINGS
The various embodiments of the invention will hereinafter be described in conjunction with the appended drawings, provided to illustrate and not to limit the invention, wherein like designations denote like elements, and in which:
FIG. 1 illustrates an environment in which various embodiments of the invention may be practiced;
FIG. 2 is a block diagram of a system for managing real-time execution of one or more transactions, in accordance with an exemplary embodiment of the invention;
FIG. 3 is a block diagram of a system for managing real-time execution of one or more transactions, in accordance with another exemplary embodiment of the invention;
FIG. 4 is a flowchart of a method for managing real-time execution of one or more transactions, in accordance with an exemplary embodiment of the invention; and

FIG. 5a, FIG. 5b and FIG. 5c is a flowchart of a method for managing real-time execution of one or more transactions between a mobile device and an inventory store, in accordance with another exemplary embodiment of the invention,
DESCRIPTION OF VARIOUS EMBODIMENTS
The invention describes a method, system and computer program product for managing real-time execution of transactions between a plurality of network devices. The plurality of network devices may include one or more requesting applications and server applications. More specifically, the transactions are carried out between the requesting applications and the server applications. The requesting applications and the server applications interact with each other in a network through one or more middleware. The middleware synchronize the transactions between the applications in real-time. The synchronization of the transactions masks the occasional network disconnectvity from the requesting applications and the server applications.
FIG. 1 illustrates a network 100 in which various embodiments of the invention may be practiced. Network 100 includes a network device 102, a network device 104, a network device 106, and a network device 108, hereinafter, referred to as a plurality of network devices. The plurality of network devices may be a mobile phone, a computer, a Personal Digital Assistant (PDA), and the like. Network device 102 and network device 104 include one or more requesting applications 110, such as requesting applications 110a and requesting applications 110b. network device 106 and network device 108 include server applications 112, such as server applications 112a and server applications 112b. Requesting applications 110 conduct one or more transactions with server applications 112 through network 100.
In various embodiments of the invention, network 100 may be a wired or wireless network. Examples of network 100 include, but are not limited to, a Local Area Network (LAN), Metropolitan Area Network (MAN), a Wide Area Network (WAN), and the Internet. In various embodiments of the invention, the plurality of network devices communicate in network 00 through Bluetooth, WiFi, Zigbee, IEEE 802.11, Radio Frequency Identification (RFID), dedicated Short Range Communications (DSRC), or their combinations thereof. Examples of rquesting applications 110 include, but are not limited to, a gaming application, a search

application, a shopping application and various utility applications. Examples of server applications 112 include, but are not limited to, a gaming server, a database server, a shopping application server and a utility application server.
FIG. 2 is a block diagram of a system 200 for managing real-time execution of one or more transactions between network device 102 and network device 106, in accordance with an exemplary embodiment of the invention. System 200 includes a middleware 202a and a middleware 202b. Middleware 202a and middleware 202b are present on network device 102 and network device 106, respectively. Moreover, middleware 202a and 202b are configured to manage transactions between network devices 102 and 106. Middleware 202a includes a command engine 204a, a synchronization engine 206a and a request-response engine 208a. Further, middleware 202b includes a command engine 204b, a synchronization engine 206b and a request-response engine 208b.
Command engines 204a and 204b are configured to receive one or more transaction identifiers from the plurality of network devices, such as network device 102 and network device 106. In an embodiment of the invention, the transaction identifiers may be transaction requests or transaction responses that are received from requesting applications 110 and server applications 112, respectively. In an embodiment of the invention, command engines 204a and 204b assign one or more transaction identifiers to the transaction requests or transaction responses received from the plurality of network devices. In an embodiment of the invention, the transaction identifiers uniquely identify the one or more transactions.
Synchronization engines 206a and 206b are configured to synchronize the details of the transactions on to the plurality of network devices in real-time. A transaction is said to be executed in real-time if a transaction response is received before the time of expiry for that transaction. In an embodiment of the invention, synchronization engine 206a synchronizes the details of the transactions on to middleware 202b present on network device 106 in real-time. The details of the transactions may include the transaction identifiers, the state of the transactions, the time of expiry, the security preferences, the configuration details, the server application details, and the like. The state of the transaction includes the temporary parameters, data and variables associated with the transaction. The time of expiry determines the validity of a

transactions request, for which a response corresponding to the request is valid. Further, the security preferences define the encryption details for transmitting the transactions.
Request-response engines 208a and 208b are configured to process the transactions based on the synchronized details of the transactions. In various embodiments of the invention, the synchronized details are compared with the earlier synchronized details each time the synchronization takes place, to determine the new and updated transaction identifiers. Request-response engines 208a and 208b, on synchronized details being updated, process the new and updated transactions. In an embodiment of the invention, request-response engines 208a and 208b process the transactions with requesting applications 110 and server applications 112, irrespective of the network connectivity between the plurality of network devices.
In various embodiments of the invention, different elements of system 200, such as command engines 204a and 204b, synchronization engines 206a and 206b, request-response engines 208a and 208b, may be implemented in the form of hardware, software, firmware, or their combinations thereof.
FIG. 3 is a block diagram of a system 300 for managing real-time execution of one or more transactions between network device 102 and network device 106, in accordance with another exemplary embodiment of the invention. System 300 includes a middleware 302a and a middleware 302b. Middleware 302a and middleware 302b are present on network device 102 and network device 106, respectively. Moreover, middleware 302a and 302b are configured to manage transactions between network devices 102 and 106. Middleware 302a includes a registration engine 304a, a personalization engine 306a, a priority engine 308a, a data store 310a, a network availability checker 312a, a data security engine 314a, command engine 204a (not shown in FIG. 3), synchronization engine 206a (not shown in FIG. 3), and request-response engine 208a. Middleware 302b includes a registration engine 304b, a personalization engine 306b, a priority engine 308b, a data store 310b, a service availability checker 312b, a data security engine 314b, command engine 204b (not shown in FIG. 3), synchronization engine 206b (not shown in FIG. 3), and request-response engine 208b. Further, request-response engine 208a and 208b includes stale request-response engines 316a and 316b respectively.

Registration engine 304a registers requesting applications 110 with middleware 302a. Similarly, registration engine 304b registers server applications 112 with middleware 302b.
Personalization engines 306a and 306b define personalization details, such as the state of application, the configuration of application, the time of expiry, the number of retransmissions, and the security preference, associated with the transaction requests and responses, respectively. In an embodiment of the invention, personalization engines 306a and 306b associate one or more time periods, such as a time of expiry, with requesting application 110 and server application 112. The time of expiry determines the validity of the transaction requests and the transaction response associated with requesting applications 110 and server applications 112. In various embodiments of the invention, a global time of expiry may also be associated with requesting applications 110 and server applications 112. The global time of expiry determines the validity of all the transaction requests and responses, i.e., all the transactions on middleware 302a and middleware 302b expire on the expiry of this global time period. The global time of expiry is used to notify the applications, if network connectivity is not available for a long time. The applications are notified about the network disconnection if the time period of disconnectivity exceeds the global time of expiry. In an embodiment of the invention, the global time of expiry may be used for determining the validity of transactions that do not have the time of expiry associated with them.
Priority engines 308a and 308b assign priorities to requesting applications 110 and server applications 112, respectively. A transaction associated with an application with a higher priority is given preference over the transactions of another application with a lower priority. In an embodiment of the invention, priority engines 308a and 308b assign priorities based on the time of expiry of requesting applications 110 and server applications 112. For example, an application with a shorter time of expiry is given a priority over another application with a longer time of expiry.
Data store 310a and 310b store the details of the transactions. Examples of the details may include, but are not limited to, personalization details, transaction identifiers, priorities, and configuration details associated with the applications and their corresponding transactions.

Network availability checker 312a checks the network connectivity between network device 102 and network device 106. If the network connection is unavailable, request-response engines 204a and 204b maintains a queue of transaction requests and responses based on various time periods.
However, if the network connection is available, synchronization engine 206a synchronizes the details stored in data store 310a with synchronization engine 206b in real-time, and vice versa. In an embodiment of the invention, synchronization engine 206a synchronizes details stored in command engine 204a and command engine 204b. Synchronization of details includes replicating the details of the transactions requests and responses on to middleware 302b and 302a, respectively.
Data security engines 314a and 314b encrypt the details of the transactions and maintain a secure connection between network device 102 and network device 106. Example of the type of encryption may include https, http, ssh, ssl, and the like. In an embodiment of the invention, the transaction request and response is sent for processing to middleware 302a and 302b through the secure connection.
Stale request-response engines 316a and 316b defines a transaction request or response as a stale, if the time during which the transaction request or response is present in the queue exceeds the time of expiry of the transaction. In an embodiment of the invention, the stale requests and responses are not processed by middleware 302a and 302b respectively.
Stale request-response engines 316a and 316b further verifies the validity of the transaction request and response based on the details of the transaction. For example, stale request-response engines 316a verifies the validity of the transaction response based on the status of the corresponding transaction request. If the status of the transaction request is identified as stale, the transaction response is defined as stale and is not processed by middleware 302a. In an embodiment of the invention, if the transaction response exceeds the time of expiry associated with the transaction request, stale request-response engine 316a defines the response as a stale response, and the response is not processed by middleware 302a. In an embodiment of the invention, stale request-response engines 316a and 316b periodically identify the validity of the transaction requests and responses after a predefined stale period, based on the time of expiry

associated with the requests and responses. In an embodiment of the invention, the value of the predefined stale period is less than or equal to the shortest time of expiry amongst all the time of expiry associated with transaction requests and responses.
Service availability checker 312b checks the availability of server applications 112 that serve the transaction requests. If server applications 112 are available, command engine 204b sends the transaction requests to server applications 112, for execution. Server applications 112 send transaction responses corresponding to transaction requests to request-response engine 208b. The transactions responses are thereby synchronized with middleware 302a. This has been described in detail in conjunction with FIG. 4.
In various embodiments of the invention, different elements of system 300, such as registration engines 304a and 304b, personalization engines 306a and 306b, priority engines 308a and 308b, data stores 310a and 310b, network availability checker 312a, service availability checker 312b, data security engines 314a and 314b, and stale request-response engines 316a and 316b may be implemented in the form of hardware, software, firmware, or combinations thereof.
FIG. 4 is a flowchart of a method for managing real-time execution of one or more transactions, in accordance with an exemplary embodiment of the invention. The transactions are executed between a plurality of network devices, such as network devices 102 and 106. Network devices 102 and 106 include a requesting middleware such as middleware 202a, and a server middleware such as middleware 202b, respectively.
At step 402, one or more transaction identifiers associated with the transactions are received by a middleware. In an embodiment of the invention, the transaction identifiers associated with the transaction requests are received by the requesting middleware. In another embodiment of the invention, transaction identifiers associated with the transaction responses, corresponding to the transaction requests, are received by the server middleware.
At step 404, the details of the transactions are synchronized between the middleware in real-time. In an embodiment of the invention, the synchronization includes replicating the details, such as the state of the transaction on the middleware in real-time. In an embodiment of the invention, the details of the transaction requests, from the requesting middleware, are

synchronized on to the server middleware for further processing. In another embodiment of the invention, the details of the transaction responses, from the server middleware, are synchronized on to the requesting middleware. In various embodiments of the invention, the synchronization takes place independent of the details of the transactions.
At step 406, the transactions are processed by the middleware based on the synchronized details of the transactions. In an embodiment of the invention, processing includes identifying the changes in synchronized details on the middleware, such as the requesting middleware and the server middleware, in comparison with earlier synchronized details, to determine the new and updated transactions. The new and updated transactions are forwarded by the middleware to the requesting applications and server applications for execution.
FIG. 5a, FIG. 5b, and FIG. 5c is a flowchart of a method for managing the real-time execution of one or more transactions between a mobile device and an inventory store, in accordance with another exemplary embodiment of the invention. At step 502, a user sends a transaction request through a shopping application installed on the mobile device to buy a shirt from the inventory store. The transaction request is required to be served by a server application installed on an inventory server. The mobile device and the inventory server include a requesting middleware and a server middleware, respectively.
At step 504, the requesting middleware checks the registration information pertaining to the shopping application. In various embodiments of the invention, each application installed on a network device needs to be registered with the middleware, to be able to transact with other network devices through the middleware.
At step 506, it is determined if the shopping application is registered with the requesting middleware. If the shopping application is not registered, the transaction request is not processed by the requesting middleware, at step 508. However, if the shopping application is registered, the details of the transaction request are stored in the requesting middleware, at step 510. The details of the transaction request may include the state of the shopping application, the configuration parameters of the shopping application, the priority details, and the time of expiry of the transaction request.

In an embodiment of the invention, one or more requesting applications and one or more server applications are present in the mobile device and the inventory server respectively. The requesting applications and the server applications are registered with the requesting middleware and the server middleware respectively. The user may simultaneously use the requesting applications to send one or more transaction request to the server applications. In an embodiment of the invention, the requesting applications and the server applications are prioritized based on the details of the transactions. The priority determines the preference of execution of these transactions.
Further, it is checked, at step 512, if network connectivity is available between the mobile device and the inventory server. If the network connectivity is not available, the transaction request is stored in a queue, at step 514. In an embodiment of the invention, subsequent transaction requests are also stored in the queue until network connectivity is available. In another embodiment of the invention, a transaction request is stored in the queue till its time of expiry. If the transaction request is present in the queue for longer than the time of expiry, the request is defined as a stale request and is not processed by the requesting middleware. In an alternate embodiment of the invention, the transaction requests may be terminated if network connectivity is not available.
If the network connectivity is available, the details of the transaction request are synchronized with the server middleware, at step 516. In an embodiment of the invention, synchronization is performed by replicating the details stored on the requesting middleware on to the server middleware in real-time, and vice-versa. In an embodiment of the invention, the details include the registration information of the applications, the state of the applications, the configuration of the applications, the state of the transactions, the priority of the transactions, and the security preference of the transactions. Replication is performed by encrypting the details based on the security preferences associated with the transaction request. Example of security preference may include https, http, ssh, ssl and the like.
At step 518, the server middleware determines the availability of the server application. In an embodiment of the invention, the availability of the server application is based on its

registration with the server middleware. In another embodiment of the invention, the availability of the server application is checked in terms of its load and resources.
If the server application is available, at step 520, the request is processed by the server middleware based on synchronized details. The processing includes identifying the changes in the synchronized details, as compared to the earlier synchronized details. The server middleware determines a new or updated transaction request based on the changes in the synchronized details. In an embodiment of the invention, processing includes mapping the transaction request on to the server application. At step 522, the transaction request is sent to the server application for execution.
At step 524, a transaction response corresponding to the transaction request is generated by the server application. At step 526, the details of the transaction response are stored in the server middleware. Thereafter, at step 528, the details stored on the server middleware are synchronized with the details stored on the requesting middleware. In various embodiments of the invention, step 528 is performed only when the network connectivity is available between the network devices.
At step 530, the requesting middleware processes the transaction response, based on synchronized details. In an embodiment of the invention, processing includes identifying the time period between the transaction request being sent and the transaction response being received. If the time period exceeds the time of expiry, the transaction response is defined as a stale transaction and the transaction is not considered to be a valid transaction. At step 532, the transaction response is sent to the shopping application.
However, if the server application is unavailable at step 518, step 534 is performed. At step 534, an error message is generated on the server middleware as a transaction response. In an embodiment of the invention, the server middleware waits for the time of expiry of the transaction response, for the server application to be available. Thereafter, the process is continued at step 526.
The method, system and computer program product described above have a number of advantages. The method manages real-time execution of one or more transactions between a

plurality of network devices. It also determines a secure way of completing a transaction in a network. The method masks the occasional network disconnectivity from the applications. Moreover, the method eliminates the dependence of the applications on network-level security. Further, the method improves the efficiency of the execution of a plurality of transactions by assigning priorities to the transactions.
The system for managing real-time execution of one or more transactions between a plurality of network devices, as described in the present invention or any of its components, may be embodied in the form of a computer system. Typical examples of a computer system includes a general-purpose computer, a programmed microprocessor, a micro-controller, a peripheral integrated circuit element, and other devices or arrangements of devices that are capable of implementing the steps that constitute the method of the present invention.
The computer system comprises a computer, an input device, a display unit and the Internet. The computer further comprises a microprocessor. The microprocessor is connected to a communication bus. The computer also includes a memory. The memory may include Random Access Memory (RAM) and Read Only Memory (ROM). The computer system further comprises a storage device. The storage device can be a hard disk drive or a removable storage drive such as a floppy disk drive, optical disk drive, etc. The storage device can also be other similar means for loading computer programs or other instructions into the computer system. The computer system also includes a communication unit. The communication unit allows the computer to connect to other databases and the Internet through an I/O interface. The communication unit allows the transfer as well as reception of data from other databases. The communication unit may include a modem, an Ethernet card, or any similar device which enables the computer system to connect to databases and networks such as LAN, MAN, WAN and the Internet. The computer system facilitates inputs from a user through input device, accessible to the system through I/O interface.
The computer system executes a set of instructions that are stored in one or more storage elements, in order to process input data. The storage elements may also hold data or other information as desired. The storage element may be in the form of an information source or a physical memory element present in the processing machine.

The set of instructions may include various commands that instruct the processing machine to perform specific tasks such as the steps that constitute the method of the present invention. The set of instructions may be in the form of a software program. Further, the software may be in the form of a collection of separate programs, a program module with a larger program or a portion of a program module, as in the present invention. The software may also include modular programming in the form of object-oriented programming. The processing of input data by the processing machine may be in response to user commands, results of previous processing or a request made by another processing machine.
While the preferred embodiments of the invention have been illustrated and described, it will be clear that the invention is not limited to these embodiments only. Numerous modifications, changes, variations, substitutions and equivalents will be apparent to those skilled in the art without departing from the spirit and scope of the invention as described in the claims.

We claim:
1. A computer program product for use with a computer, the computer program product comprising a computer usable medium having a computer readable program code embodied therein for managing real-time execution of one or more transactions between a plurality of network devices, the plurality of network devices having one or more requesting applications and one or more server applications, the computer readable program code performing:
a. receiving one or more transaction identifiers for the one or more transactions, the one or more transaction identifiers being received from at least one of the plurality of network devices;
b. synchronizing details of the one or more transactions on to at least one of the plurality of network devices using the one or more transaction identifiers; and
c. processing the one or more transactions based on synchronized details of the one or more transactions.
2. The computer program product of claim 1? wherein the computer program code further performs checking availability of the one or more server applications.
3. The computer program product of claim 1, wherein the computer readable program code further performs prioritizing the one or more transactions based on the details of the one or more transactions.
4. The computer program product of claim 1, wherein the computer readable program code further performs assigning one or more security preferences to the one or more transactions.
5. The computer program product of claim 1, wherein the computer readable program code further performs processing the one or more transactions based on one or more time periods, the one or more time periods determining validity of the one or more transactions.
6. The computer readable program code of claim 1, wherein the computer readable program code further performs identifying the one or more transactions as stale transactions, if the

time taken to process the one or more transactions exceeds at least one of the one or more time periods.
7. The computer program product of claim 1, wherein the computer readable program code further performs checking network connectivity between the plurality of network devices.
8. The computer program code of claim 1, wherein the computer readable program code further performs storing the details of the one or more transactions.
9. A method for managing real-time execution of one or more transactions between a plurality of network devices, the plurality of network devices having one or more requesting applications and one or more server applications, the method comprising:
a. receiving one or more transaction identifiers for the one or more transactions, the one or more transaction identifiers being received from at least one of the plurality of network devices;
b. synchronizing details of the one or more transactions on to at least one of the plurality of network devices using the one or more transaction identifiers; and
c. processing the one or more transactions based on synchronized details of the one or more transactions.
10. The method of claim 9, wherein the one or more transaction identifiers comprise at least one of one or more transaction requests and one or more transaction responses.
11.The method of claim 9, wherein the one or more transaction identifiers comprise identification information of at least one of the one or more requesting applications and the one or more server applications.
12.The method of claim 9 further comprising checking availability of the one or more server applications.
13.The method of claim 9, wherein the synchronization is performed over a secure network connection between the plurality of network devices.

14.The method of claim 9, wherein the one or more transactions are processed based on one or more time periods, the one or more time periods determining validity of the one or more transactions.
15.The method of claim 145 wherein the one or more transactions are identified as stale transactions, if the time taken to process the one or more transactions exceeds at least one of the one or more time periods.
16.The method of claim 9 further comprising checking registration information of the one or more requesting applications.
17.The method of claim 9 further comprising prioritizing the one or more transactions based on the details of the one or more transactions.
18.The method of claim 9 further comprising assigning one or more security preferences to the one or more transactions.
19.The method of claim 9 further comprising encrypting details of the one or more transactions.
20.The method of claim 9 further comprising checking network connectivity between the plurality of network devices.
21 .The method of claim 9 further comprising storing the details of the one or more transactions.
22. A system for managing real-time execution of one or more transactions between a plurality of network devices, the plurality of network devices having one or more requesting applications and one or more server applications, wherein the one or more requesting applications and the one or more server applications being registered with one or more middleware present in the plurality of network devices, each of the one or more middleware comprising:
a. a command engine configured for receiving one or more transaction identifiers from at least one of the plurality of network devices;

b. a synchronization engine configured for synchronizing the details of the one or more transactions on to at least one of the plurality of network devices using the one or more transaction identifiers; and
c. a request-response engine configured for processing the one or more transactions based on synchronized details of the one or more transactions.
23.The system of claim 22, wherein the one or more transaction identifiers comprise at least one of one or more transaction requests and one or more transaction responses.
24.The system of claim 22, wherein the one or more transaction identifiers comprise identification information of at least one of the one or more requesting applications and the one or more server applications.
25.The system of claim 22, wherein each of the one or more middleware further comprises a registration engine, the registration engine configured for registering at least one of the one or more server applications and the one or more requesting applications on the one or more middleware.
26.The system of claim 22, wherein at least one of the one or more middleware further comprises a service availability checker configured for verifying availability of the one or more server applications.
27. The system of claim 22, wherein each of the one or more middleware further comprises a data store, the data store configured for storing the details of the one or more transactions.
28.The system of claim 22, wherein each of one or more middleware further comprises a personalization engine configured for providing one or more time periods for determining validity of the one or more transactions, the personalization engine further providing one or more security preferences for the one or more transactions.
29.The system of claim 22, wherein the request-response engine comprises a stale request-response engine configured for determining validity of the one or more transactions based on one or more time periods.

30.The system of claim 22, wherein each of the one or more middleware further comprises a data security engine configured for ensuring a secure connection between the plurality of network devices.
31.The system of claim 22, wherein each of the one or more middleware further comprises a network availability checker configured for checking the network connectivity between the plurality of network devices.
32.The system of claim 22, wherein the one or more middleware further comprises a priority engine configured for prioritizing the one or more transactions.