Claims:We claim:
1. A system (101) for a real-time monitoring of network data in a transaction event, the system (101) comprising:
one or more processors (201) communicatively coupled with a plurality of external systems (104-a-104-n), wherein each external system, of the plurality of the external system (104-a-104-n), is configured to generate a plurality of network data transaction sub events, corresponding to network data in at least one transaction event; and
one or more memories (203) coupled with one or more processors (201), wherein one or more processors (201) are configured to execute instructions for:
classifying each external system of the plurality of external systems (104-a-104-n) into a group of a plurality of predefined groups using a classification module (205) such that each group includes one or more external systems, generating one or more network data transaction subevents, corresponding to network data in a transaction event;
configuring and storing one or more predefined policies and rules for each group in a blockchain network module (207);
receiving one or more network data transaction sub events generated by one or more external systems corresponding to network data in a transaction event in a real time;
creating a reference value for each network data transaction sub event, generated by one or more external systems, using an Application Program Interface (API) module (206) communicatively coupled with the blockchain network module (207) and the plurality of the external systems (104-a-104-n);
storing the reference value for each network data transaction subevent, generated by one or more external systems, in a block of the plurality of blocks of blockchain network module (207), wherein the block corresponds to the group associated with the one or more external systems generating the one or more network data transaction sub events in a real time; and
monitoring network data in the transaction event using the reference value for each network data transaction sub event.

2. The system as claimed in claim 1, wherein network data in the transaction event is monitored using the reference value for each network data transaction sub event to trigger a scheduling module (208) to display a schedule to a user or a notification module (209) to notify the user or an analysing module (210) to generate a report based upon one or more predefined policies corresponding to the group.

3. The system as claimed in claim 1, wherein the reference value is stored in a form of a cryptographic hashtag.

4. The system as claimed in claim 1, wherein the one or more processors (201) are configured to detect an anomaly when at least one network data transaction sub events of the group fail to comply the predefined policy and rules associated with the said predefined policy.

5. The system as claimed in claim 1, wherein the one or more processors (201) are configured to create and store a reference value for logs of the plurality of the network data transaction sub events.

6. A method (500) for a real-time monitoring of network data in a transaction event, the method (500) comprising:
classifying, via one or more processors (201), each external system of a plurality of external systems (104-a- 104-n) into a group of a plurality of predefined groups using a classification module (205) such that each group includes one or more external systems, wherein each external system of the plurality of the external systems (104-a- 104-n) is configured to generate a plurality of network data transaction sub events, corresponding to network data in at least one transaction event;
configuring and storing, via the one or more processors (201), one or more predefined policies and rules for each group in a blockchain network module (207);
receiving, via the one or more processors (201), one or more network data transaction sub events generated by one or more external systems corresponding to network data in a transaction event in a real time;
creating, via the one or more processors (201), a reference value for each network data transaction sub event, generated by the one or more external systems, using an application interface (API) module (206) communicatively coupled with blockchain network module and the plurality of the external systems;
storing, via the one or more processors (201), the reference value for each network data transaction subevent, generated by one or more external systems, in a block of the plurality of blocks of blockchain network module (207), wherein the block corresponds to the group associated with the one or more external systems generating the one or more network data transaction sub events in real time; and
monitoring, via the one or more processors, network data in the transaction event using the reference value for each network data transaction sub event.

7. The method as claimed in claim 6, further comprising triggering a scheduling module (208) to display a schedule to a user or a notification module (209) to notify the user or an analysing module (210) to generate a report based upon one or more predefined policies corresponding to the group.

8. The method as claimed in claim 6, wherein the reference value is stored in the form of cryptographic hashtag.

9. The method as claimed in claim 6, further comprising detecting an anomaly when at least one of the network data transaction sub events of the group fail to comply with the predefined policy and the rules associated to the said predefined policy.

10. The method as claimed in claim 6, further comprising creating and storing a reference value for logs of the plurality of the network data transaction sub events.

Dated this 24th day of October 2019

Priyank Gupta
Agent for the Applicant
IN/PA- 1454

, Description: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 SYSTEM AND A METHOD FOR REAL-TIME MONITORING OF NETWORK DATA IN A TRANSACTION EVENT

APPLICANT
Zensar Technologies Limited.
(An Indian entity having address)
Zensar Knowledge Park, Plot # 4, MIDC, Kharadi, Off Nagar Road, Pune-411014, Maharashtra, India

The following specification describes the invention and the manner in which it is to be performed.

TECHNICAL FIELD
The present subject matter described herein, in general, relates to a system and a method for real-time monitoring of network data in a transaction event.

BACKGROUND
The subject matter discussed in the background section should not be assumed to be prior art merely because of its mention in the background section. Similarly, a problem mentioned in the background section or associated with the subject matter of the background section should not be assumed to have been previously recognized in the prior art. The subject matter in the background section merely represents different approaches, which in and of themselves may also correspond to implementations of the claimed technology.

Existing process-oriented system consists of various subsystems. For example, the hiring system depends on several constituent system or subsystems such as Talent Management System, Human Resource Management System (HRMS), Project Management System, Document Management System. Therefore, it is evident that, the process-oriented systems are highly dependent on other subsystems to share data. The process-oriented systems are configured to receive data from the database associated with the subsystem. In most of the existing systems, the system is updated by batch process on daily/hourly or even weekly process, if any changes or updates occur at one sub system. For example, if a new request is being carried out by talent management system to on-board people, then data associated with the new request should also have to be reflected in HRMS, however HRMS fails to update the data immediately and to provide notification in a real time. Further, the existing systems fail to provide visibility in data flow as well as to track data in the real time. Further, the existing systems fail to perform audit of data in the real time. Existing audit process associated with the process flow oriented system is very costly and time-consuming process.

Further, the database synchronization is a big overhead and practically is not possible to synchronize the data amongst all the constituent systems or subsystems. These existing systems fail to provide the flexibility to intercommunicate with any of the subsystems. Therefore, it is very difficult to facilitate synchronization of multiple databases. The existing systems fail to monitor the data and process flow in the real time without synchronization of data. Further, the existing systems do not have the capability to act as scheduler, notifier and report generation tool. The existing systems do not have capability to add multiple complex system (process-oriented system). For example, the systems do not have the capability to add Hiring Management System (including its subsystems as well), same for Order Management System (OMS), etc. Thus, these exists a long-standing need of a system and method for a real-time monitoring of network data in a transaction event.

SUMMARY
This summary is provided to introduce concepts related to a and the concepts are further described below in the detailed description. This summary is not intended to identify essential features of the claimed subject matter nor is it intended for use in determining or limiting the scope of the claimed subject matter.

In one embodiment, a system for a real-time monitoring of network data in a transaction event is disclosed. The system may comprise one or more processors communicatively coupled with one or more memories and a plurality of external systems. Each external system of the plurality of the external system may be configured to generate a plurality of network data transaction sub events, corresponding to network data in at least one transaction event. The one or more processors may be configured to execute a plurality of modules stored in the one or more memories. The one or more processors may be configured for classifying each external system of the plurality of external systems into a group of a plurality of predefined groups using a classification module such that each group includes one or more external systems, generating one or more network data transaction subevents, corresponding to network data in a transaction event. Further, the one or more processors may be configured for configuring and storing one or more predefined policies and rules for each group in a blockchain network module. The one or more processors may be configured for receiving one or more network data transaction sub events generated by one or more external systems corresponding to network data in a transaction event in a real time. Further, the one or more processors may be configured for creating a reference value for each network data transaction sub event, generated by one or more external systems, using an application interface (API) module communicatively coupled with blockchain network module and the plurality of the external systems. Further, the one or more processors may be configured for storing the reference value for each network data transaction subevent, generated by one or more external systems, in a block of the plurality of blocks of blockchain network module, wherein the block corresponds to the group associated with the one or more external systems generating the one or more network data transaction sub events in real time. Further, the one or more processors may be configured for monitoring network data in the transaction event using the reference value for each network data transaction sub event.

In another embodiment, a method for a real-time monitoring of network data in a transaction event is disclosed. The method may comprise classifying, via one or more processors, each external system of the plurality of external systems into a group of a plurality of predefined groups using a classification module such that each group includes one or more external systems, generating one or more network data transaction subevents, corresponding to network data in at least one transaction event. The method may further comprise configuring and storing, via the one or more processors, one or more predefined policies and rules for each group in a blockchain network module. The method may further comprise receiving, via the one or more processors, one or more network data transaction sub events generated by one or more external systems corresponding to network data in a transaction event in the real time. The method may further comprise creating, via the one or more processors, a reference value for each network data transaction sub event, generated by one or more external systems, using an application interface (API) module communicatively coupled with blockchain network module and the plurality of the external systems. The method may further comprise storing, via the one or more processors, the reference value for each network data transaction subevent, generated by one or more external systems, in a block of the plurality of blocks of blockchain network module, wherein the block corresponds to the group associated with the one or more external systems generating the one or more network data transaction sub events in real time. The method may further comprise monitoring, via the one or more processors, network data in the transaction event using the reference value for each network data transaction sub event.

BRIEF DESCRIPTION OF DRAWINGS

The detailed description is described with reference to the accompanying Figures. In the Figures, the left-most digit(s) of a reference number identifies the Figure in which the reference number first appears. The same numbers are used throughout the drawings to refer like features and components.

Figure 1 illustrates a network implementation 100 of a system 101 for a real-time monitoring of network data in a transaction event, in accordance with an embodiment of the present subject matter.

Figure 2 illustrates components of the system 101, in accordance with an embodiment of the present subject matter.

Figure 3 illustrates, a first exemplary embodiment of a system for real-time monitoring of network data in a transaction event, in accordance with the present subject matter.

Figure 4 illustrates, a second exemplary embodiment of a system for real-time monitoring of network data in a transaction event, in accordance with the present subject matter.

Figure 5 illustrates, a method 500 for a real-time monitoring of network data in a transaction event, in accordance with an embodiment of the present subject matter.

DETAILED DESCRIPTION

Reference throughout the specification to “various embodiments,” “some embodiments,” “one embodiment,” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in various embodiments,” “in some embodiments,” “in one embodiment,” or “in an embodiment” in places throughout the specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments.

While aspects of described system and method for a real-time monitoring of network data in a transaction event may be implemented in any number of different computing systems, environments, and/or configurations, the embodiments are described in the context of the following exemplary system.

Referring now to Figure 1, a network implementation 100 of a system 101 for a real-time monitoring of network data in a transaction event is illustrated, in accordance with an embodiment of the present subject matter.

Although the present subject matter is explained considering that the system 101 is implemented on a server, it may be understood that the system 101 may also be implemented in a variety of computing systems, such as a laptop computer, a desktop computer, a notebook, a workstation, a mainframe computer, a server, a network server, and the like. It will be understood that the system 101 may be accessed by multiple users through one or more user devices 103-1, 103-2…103-N, collectively referred to as user 103 hereinafter, or applications residing on the user devices 103. Examples of the user devices 103 may include, but are not limited to, a portable computer, a personal digital assistant, a handheld device, and a workstation. The user devices 103 are communicatively coupled to the system 101 through a network 102.

In one implementation, the network 102 may be a wireless network, a wired network or a combination thereof. The network 102 can be implemented as one of the different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and the like. The network 102 may either be a dedicated network or a shared network. The shared network represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), and the like, to communicate with one another. Further the network 102 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like.

The aforementioned devices may support communication over one or more types of networks in accordance with the described embodiments. For example, some computing devices and networks may support communications over a Wide Area Network (WAN), the Internet, a telephone network (e.g., analog, digital, POTS, PSTN, ISDN, xDSL), a mobile telephone network (e.g., CDMA, GSM, NDAC, TDMA, E-TDMA, NAMPS, WCDMA, CDMA-2000, UMTS, 3G, 4G), a radio network, a television network, a cable network, an optical network (e.g., PON), a satellite network (e.g., VSAT), a packet-switched network, a circuit-switched network, a public network, a private network, and/or other wired or wireless communications network configured to carry data. Computing devices and networks also may support wireless wide area network (WWAN) communications services including Internet access such as EV-DO, EV-DV, CDMA/1×RTT, GSM/GPRS, EDGE, HSDPA, HSUPA, and others.

The aforementioned devices and networks may support wireless local area network (WLAN) and/or wireless metropolitan area network (WMAN) data communications functionality in accordance with Institute of Electrical and Electronics Engineers (IEEE) standards, protocols, and variants such as IEEE 802.11 (“WiFi”), IEEE 802.16 (“WiMAX”), IEEE 802.20x (“Mobile-Fi”), and others. Computing devices and networks also may support short range communication such as a wireless personal area network (WPAN) communication, Bluetooth® data communication, infrared (IR) communication, near-field communication, electromagnetic induction (EMI) communication, passive or active RFID communication, micro-impulse radar (MIR), ultra-wide band (UWB) communication, automatic identification and data capture (AIDC) communication, and others.

Referring now to Figure 2, the system 101 is illustrated in accordance with an embodiment of the present subject matter. In one embodiment, the system 101 may include one or more processors 201, an input/output (I/O) interfaces 202, and one or more memories 203. The one or more processors 201 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the one or more processors 201 are configured to fetch and execute computer-readable instructions stored in the memory 203.

The I/O interface 202 may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. The I/O interface 202 may allow the system 101 to interact with a user directly or through the client devices 103. Further, the I/O interface 202 may enable the system 101 to communicate with other computing devices, such as web servers and external data servers (not shown). The I/O interface 202 can facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as WLAN, cellular, or satellite. The I/O interface 202 may include one or more ports for connecting a number of devices to one another or to another server.

The memory 203 may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. The memory 203 may include modules 204 and data 212.

The modules 204 include routines, programs, objects, components, data structures, etc., which perform particular tasks or implement particular abstract data types. In one implementation, the modules 204 may include a classification module 205, an Application Program interface (API) module 206, a blockchain network module 207, a scheduling module 208, a notification module 209, an analysing module 210 and other modules 211. The other modules 211 may include programs or coded instructions that supplement applications and functions of the system 101.

The data 212, amongst other things, serves as a repository for storing data processed, received, and generated by one or more of the modules 204. The data 212 may also include a blockchain network 213 and other data 214. The other data 214 may include data generated as a result of the execution of one or more modules in the other module 211.

In one implementation, at first, a user may use the client device 103 to access the system 101 via the I/O interface 202. The user may register themselves using the I/O interface 202 in order to access the system 101. The system 101 may be used for the real-time monitoring of network data in the transaction event. One or more processors 201 may be communicatively coupled with a plurality of external systems. In one embodiment, the transaction event may be indicative of activities or operations or functionalities performed by one or more external systems for executing transaction e.g. process workflow) in the network. In one exemplary embodiment, the plurality of external systems may include, but not limited to, a Hiring Management System, a Talent Management System, a Document Management System, a Performance Management System (PMS), a HR Self Service (HRSS), an Order Management System (OMS). Each external system of the plurality of external systems may be configured to generate a plurality of network data transaction sub events, corresponding to network data in at least one transaction event. In one embodiment, network data transaction subevents may be indicative of steps involved in the activities or operations or functionalities performed by one or more external systems for executing transaction e.g. process workflow) in the network. In one exemplary embodiment, the Order Management System may be configured to generate network data in at least one transaction event such as an order processing event. The plurality of network data transaction sub events includes, but not limited to, order request event, order entry event, payment event, shipping event, collectively forms the order processing event.

In one embodiment, the one or more processors 201 of the system 101 may be configured for classifying each external system of the plurality of external systems into a group of a plurality of predefined groups using the classification module 205 such that each group includes one or more external systems, generating one or more network data transaction subevents, corresponding to network data in the transaction event. The system 101 may be configured to use a packed API to link one or more groups with each other. In one exemplary embodiment, the Hiring Management System, the Talent Management System, the Document management system may be classified into one group.

In one embodiment, the one or more processors 201 of the system 101 may be configured for configuring and storing one or more predefined policies and rules for each group in a blockchain network module 207. In one exemplary embodiment, the one or more predefined policies and rules may comprise a sequence of instructions which should be performed for network data in the transaction events corresponding to the one or more external systems classified into a particular group. Further, the one or more predefined policies and rules may define a sequence of instructions which should be performed in one or more network data transaction subevents, corresponding to the network data in a transaction event. In one exemplary embodiment, a predefined policy and rules for an Order management system may comprise that order entry event should happen after 5 seconds after receiving order request event. Further, the payment event should be happened before expiration of 2 min after order entry event. The system 101 may be configured to detect an anomaly when at least one network data transaction sub events of the group fail to comply with the predefined policy and the rules.

In one embodiment, the one or more processors 201 of the system 101 may be configured for receiving one or more network data transaction sub events generated by one or more external systems corresponding to network data in a transaction event in a real time. In one exemplary embodiment, the Order Management System may generate an order processing event by combining order request event, order entry event, payment event, shipping event.
In one embodiment, the one or more processors 201 of the system 101 may be configured for creating a reference value for each network data transaction sub event, generated by one or more external systems, using the Application Program Interface (API) module 206. Further, the system 101 may be configured for creating a reference value for logs of the plurality of the network data transaction sub events. In one embodiment, the reference value may be stored in the form of a cryptographic hashtag. In one embodiment, the API module 206 may be communicatively coupled with blockchain network module 207 and the plurality of the external systems 104-a- 104-n.

In one embodiment, the one or more processors 201 of the system 101 may be configured for storing the reference value for each network data transaction subevent, generated by one or more external systems, in a block of the plurality of blocks of blockchain network module 207. It is to be noted herein that the block corresponds to the group associated with the one or more external systems generating the one or more network data transaction sub events in a real time. Further, the block may be configured to store other information associated network data in each transaction event. Further, the system 101 may be configured for storing a reference value for logs of the plurality of the network data transaction sub events.
In one embodiment, the one or more processors 201 of the system 101 may be configured for monitoring the network data in the transaction event using the reference value for each network data transaction sub event in order to trigger a scheduling module 208 to display a schedule to a user, or a notification module 209 to notify the user, or an analysing module 210 to generate a report based upon one or more predefined policies corresponding to the group.

Now referring to Figure 3, a real-time monitoring of network data in a transaction is depicted, in accordance with a first exemplary embodiment of the present subject matter. The system 101 is communicatively coupled with an external system 301 such as Order Management System (OMS). The external system 301 may be configured to generate at least one network data in a transaction event. The external system 301 may configured to generate a plurality of network data transaction sub events, corresponding to network data in at least one transaction event. Order Management System may generate a plurality of network data transaction subevents such as “order request event”, “order entry event, “payment event” etc, corresponding to “Order Management Event”. The external system 301 is coupled with the External system database (DB) 303 in order to store the plurality of network data transaction sub events, corresponding to network data in at least one transaction event. The external system 301 may be configured to update the external system database (DB) 303 based upon changes in the one or more network data transaction sub events of the plurality of network data transaction subevents, either through automation with backend API’s 302 or Manually. The external system 301 is communicatively coupled with the one or more processors 201 of the system 101. The one or more processors 201 of the system 101 may be configured to classify the external system 301 into a group I using the classification module 205. The group I may be indicative of Order Management event. The one or more processors 201 of the system 101 may be configured for configuring and storing, one or more predefined policies and rules for the group I in the blockchain network module 207. One or more predefined policies and rules for the group I may comprise a sequence of rules which need to be performed for monitoring Order Management event. The first rule may define that “order entry event” should happen after 5 seconds of receipt of “order request event”. Further, the second rule may define that “payment event” should be happened before expiration of 2 min after “order entry event”. The one or more processors 201 of the system 101 may configured for receiving one or more network data transaction sub events such as “order request event”, “order entry event”, “payment event” generated by external system 301 corresponding to network data in a transaction event in a real time. The one or more processors 201 may create reference value for one or more network data transaction sub event such as “order request event”, “order entry event”, “payment event”, generated by the external system 301, using the Application Program Interface (API) module 206, based upon changes in the one or more network data transaction sub events of the plurality of network data transaction subevents. The one or more processors 201 may update reference value for one or more network data transaction sub event in the blockchain network module 207. The blockchain network module 207 is configured to store the reference value for one or more network data transaction sub event generated by the external system 301, in a block of the plurality of blocks of blockchain network module 207. The block corresponds to the group associated with the external system 301 generating the one or more network data transaction sub events in real time. The one or more processors 201 may update reference value for one or more network data transaction sub event in the blockchain network 213 via backend API 304. The one or more processors 201 of the system 101 may be configured for monitoring network data in the transaction event of the external system 301 using the reference value for each network data transaction sub event in order to trigger a scheduling module to display a schedule to a user or a notification module to notify the user or an analysing module to generate a report based upon one or more predefined policies. In one embodiment, the schedule or notification or the report may be displayed on I/O interfaces 202.

Now referring to Figure 4, a real-time monitoring of a network data transaction is depicted, in accordance with a second exemplary embodiment of the present subject matter. The system 101 is communicatively coupled with a plurality of external systems 401-a, 401-b,401-c, ….401-n such as Hiring Management System, Talent Management System, Document Management System, Performance Monitoring System, HR self-service (HRSS), Order entry system, Financial processing system, Order processing system etc., collectively referred as external system 401. Each external system 401 may be configured to generate a plurality of network data transaction sub events, corresponding to network data in at least one transaction event. Each external system may be coupled with the corresponding External system database (DB) in order to store the plurality of network data transaction sub events, corresponding to network data in at least one transaction event. The one or more processors 201 of the system 101 may configured for classifying each external system of the plurality of external systems (104-a-104-n) into a group of a plurality of predefined groups using the classification module 205. Each group includes one or more external systems, generating one or more network data transaction subevents, corresponding to network data in a transaction event. In one scenario, the one or more processors 201 of the system 101 may classify “Order entry system”, “Financial processing system”, “Order processing system” into a group I. The group I includes “Order entry system”, “Financial processing system”, “Order processing system”, generating one or more network data transaction subevents, corresponding to network data in a “Order Management Event”. In this embodiment, “Order entry system” may generate one or more network data transaction subevents such as “product information entry event”, “inventory checking event”, “purchasing details entry event” etc. Further, “Financial processing system” may generate one or more network data transaction subevents such as “payment event” etc. Further, “Order processing event” may generate one or more network data transaction subevents such as “order picking event”, “order packing event” and “order shipping event” etc. The one or more processors 201 of the system 101 may configuring and storing one or more predefined policies and rules for each group in a blockchain network module 207. One or more predefined policies and rules for the group I may comprise a sequence of rules which need to be performed for monitoring network data in “Order Management event”. The first rule may define that “payment event” should happen within 1 minute of completion of “purchasing details entry event”. The second rule may define “order picking event” should happen after completion of “payment event”. The plurality of external systems 401-a, 401-b, 401-c….401-d are communicatively coupled with the one or more processors 201 of the system 101 via backend API 403-a, 403-b….403-n. The one or more processors 201 may create reference value for one or more network data transaction sub event, generated by one or more external systems 401-a, 401-b, 401-c…401-n, using the Application Program Interface (API) module 206. The one or more processors 201 may store the reference value for each network data transaction subevent, generated by the one or more external systems, in a block of the plurality of blocks of blockchain network module 207. The block corresponds to the group associated with the one or more external systems generating the one or more network data transaction sub events in real time. The blockchain network module 207 is configured to stores one or more predefined policies associated with network data in the transaction event in the blockchain network 213. The one or more processors 201 of the system 101 may be configured for monitoring network data in the transaction event of the external system using the reference value for each network data transaction sub event in order to trigger a scheduling module to display a schedule to a user or a notification module to notify the user or an analysing module to generate a report based upon one or more predefined policies corresponding to the group. In one embodiment, the schedule or notification or the report may be displayed on I/O interfaces 202.

Now referring to Figure 5, a method for real-time monitoring of network data in a transaction event, is illustrated. At step 501, one or more processors 201 may be configured for classifying each external system of the plurality of external systems into a group of a plurality of predefined groups using the classification module 205 such that each group includes one or more external systems, generating one or more network data transaction subevents, corresponding to network data in at least one transaction event.

At step 502, the one or more processors 202 may be configured for configuring and storing, one or more predefined policies and rules for each group in the blockchain network module 207.

At step 503, the one or more processors 202 may be configured for receiving, one or more network data transaction sub events generated by one or more external systems corresponding to network data a transaction event in the real time.

At step 504, the one or more processors 202 may be configured for creating, a reference value for each network data transaction sub event, generated by one or more external systems, using an application interface (API) module communicatively coupled with blockchain network module 207 and the plurality of the external systems 104a-104n.

At step 505, the one or more processors 202 may be configured for storing the reference value for each network data transaction subevent, generated by one or more external systems, in a block of the plurality of blocks of blockchain network module 207, wherein the block corresponds to the group associated with the one or more external systems generating the one or more network data transaction sub events in real time.

At step 506, the one or more processors 201 may be configured for monitoring, network data in the transaction event using the reference value for each network data transaction sub event in order to trigger a scheduling module 208 to display a schedule to a user or a notification module 209 to notify the user or an analysing module 210 to generate a report based upon one or more predefined policies corresponding to the group.

Some embodiments of the system and method use blockchain based solution in order to store all the inter system communications logs.

Some embodiments of the system and method may be configured to create API’s, which can be referred or utilize by other systems irrespective of their underlying technologies and implementation, for storing all those network data in the transaction events and logs or changes in the blockchain network.

Some embodiments of the system and method may be configured to group one or more external systems and transaction logs for all complex process-oriented subsystems which can be generated, with minimal computation costs.

Some embodiments of the system may have capability to generate reports for analytics purpose.

Some embodiments of the system may provide tamper proof system. The system reduces the dependencies of one system to other, as the data sharing will be reduced with the help of reference values stored in blockchain network. Thereby, the system may enable audibility and visibility of data with multiple separate process with the existing system.

Some embodiments of the system may provide highly scalable system with no ownership overhead problem.

Some embodiments of the present system may provide data transparency and visibility.

Some embodiments of the present system may reduce the cost, time and burden of Database Synchronization to huge extent.

Some embodiment of the present system may provide immediate notification to the plurality of external systems.

Although implementations for a system and a method for real-time monitoring of network data in a transaction event have been described in language specific to structural features and/or methods, it is to be understood that the appended claims are not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as examples of implementations for real-time monitoring of network data in a transaction event.