US2013179982A1PendingUtilityA1

Data Processing Engine System And Method

62
Assignee: EZSHIELD INCPriority: Jan 9, 2012Filed: Sep 21, 2012Published: Jul 11, 2013
Est. expiryJan 9, 2032(~5.5 yrs left)· nominal 20-yr term from priority
G06Q 30/0185H04L 63/168H04L 67/02G06F 21/60G06F 21/6218H04L 63/0823G06Q 50/265H04L 63/08H04L 63/14G06Q 10/00
62
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A computer implemented method for a data processing engine for an identity management system, can comprise: on a computer device having one or more processors and a memory storing one or more programs for execution by the one or more processors, the one or more programs including instructions for: configuring an inbound or outbound feed; executing the inbound feed; and executing the outbound feed. Also, a computer system and a non-transitory computer-readable storage medium for the same.

Claims

exact text as granted — not AI-modified
We claim: 
     
         1 . A computer implemented method for a data processing engine for an identity management system, comprising:
 on a computer device having one or more processors and a memory storing one or more programs for execution by the one or more processors, the one or more programs including instructions for:   configuring an inbound or outbound feed;   executing the inbound feed; and   executing the outbound feed.   
     
     
         2 . The computer implemented method of  claim 1 , wherein configuring the inbound or outbound feed comprises:
 defining a transmission detail;   defining a data feed;   defining a feed detail; and   defining a field mapping.   
     
     
         3 . The computer implemented method of  claim 2 , wherein defining the transmission detail comprises:
 defining a transfer protocol;   defining a server name;   defining a port; and   defining a credential.   
     
     
         4 . The computer implemented method of  claim 2 , wherein defining the data feed comprises:
 defining a topic of information or a pre-defined category; and   defining a direction of data flow.   
     
     
         5 . The computer implemented method of  claim 2 , wherein defining the feed detail comprises:
 defining source details; and   monitoring attributes.   
     
     
         6 . The computer implemented method of  claim 5 , wherein defining the source details comprises:
 defining a location;   defining a file type and a delimiter;   defining an extension;   defining a filename mask;   defining header or footer information; and   encrypting the data.   
     
     
         7 . The computer implemented method of  claim 5 , wherein monitoring attributes comprises:
 monitoring cadency;   monitoring frequency;   monitoring anomalies;   monitoring quality; and   monitoring traceability.   
     
     
         8 . The computer implemented method of  claim 2 , wherein defining the field mapping comprises defining data type, data length and data position. 
     
     
         9 . The computer implemented method of  claim 2 , wherein configuring the inbound or outbound feed further comprises:
 defining a destination detail;   defining business rule processing; and   repeating the step of configuring the inbound or outbound feed.   
     
     
         10 . The computer implemented method of  claim 2 , wherein executing the inbound feed comprises:
 obtaining a list of all data feeds to be executed; and   for each data feed to be executed, connecting the data feed to the transmission detail;   retrieving the feed detail for the data feed;   inserting execution results for the data feed into a data feed job; and   performing business rule processing for the data feed.   
     
     
         11 . The computer implemented method of  claim 10 , wherein obtaining a list of all data feeds to be executed comprises:
 looking at a status of the data feed; and   executing a run at least as often as a shortest cadence.   
     
     
         12 . The computer implemented method of  claim 10 , wherein retrieving the feed detail for the data feed comprises:
 obtaining a file;   decrypting the file;   validating a source to ensure that the source meets expected specifications;   processing the file according to the field mapping; and   storing the results of the processing in a staging database.   
     
     
         13 . The computer implemented method of  claim 10 , wherein performing business rule processing for the data feed comprises:
 evaluating each record against defined business rules;   disposing each record according to the evaluating step; and   inserting or updating a profile or a contract into a final destination database based on the evaluating and disposing steps.   
     
     
         14 . The computer implemented method of  claim 10 , wherein executing the outbound feed comprises:
 scheduling a job to call the data processing engine;   specifying an outbound integration to run;   setting a location of configuration data;   obtaining configuration information from the data feed and the feed detail;   constructing an execution string based on an object field and a parameter field;   executing the execution string;   returning a data set;   transforming the data set into a file specification based on the field mapping;   storing the data set with the file specification into a temporary local location;   logging the field mapping construct results to the data feed job and the feed detail log;   transmitting the file from a local source to a destination based on details in the transmission detail; and   logging the transmission results into the data feed job.   
     
     
         15 . A computer system for a data processing engine for an identity management system, comprising:
 one or more processors; and   memory to store:
 one or more programs, the one or more programs comprising instructions for:
 configuring an inbound or outbound feed; 
 
 executing the inbound feed; and 
 executing the outbound feed. 
   
     
     
         16 . The computer system of  claim 15 , wherein configuring the inbound or outbound feed comprises:
 defining a transmission detail;   defining a data feed;   defining a feed detail; and   defining a field mapping.   
     
     
         17 . The computer system of  claim 16 , wherein defining the transmission detail comprises:
 defining a transfer protocol;   defining a server name;   defining a port; and   defining a credential.   
     
     
         18 . The computer system of  claim 16 , wherein defining the data feed comprises:
 defining a topic of information or a pre-defined category; and   defining a direction of data flow.   
     
     
         19 . The computer system of  claim 16 , wherein defining the feed detail comprises:
 defining source details; and   monitoring attributes.   
     
     
         20 . The computer system of  claim 19 , wherein defining the source details comprises:
 defining a location;   defining a file type and a delimiter;   defining an extension;   defining a filename mask;   defining header or footer information; and   encrypting the data.   
     
     
         21 . The computer system of  claim 19 , wherein monitoring attributes comprises:
 monitoring cadency;   monitoring frequency;   monitoring anomalies;   monitoring quality; and   monitoring traceability.   
     
     
         22 . The computer system of  claim 16 , wherein defining the field mapping comprises defining data type, data length and data position. 
     
     
         23 . The computer system of  claim 16 , wherein configuring the inbound or outbound feed further comprises:
 defining a destination detail;   defining business rule processing; and   repeating the step of configuring the inbound or outbound feed.   
     
     
         24 . The computer system of  claim 16 , wherein executing the inbound feed comprises:
 obtaining a list of all data feeds to be executed; and   for each data feed to be executed,   connecting the data feed to the transmission detail;   retrieving the feed detail for the data feed;   inserting execution results for the data feed into a data feed job; and   performing business rule processing for the data feed.   
     
     
         25 . The computer system of  claim 24 , wherein obtaining a list of all data feeds to be executed comprises:
 looking at a status of the data feed; and   executing a run at least as often as a shortest cadence.   
     
     
         26 . The computer system of  claim 24 , wherein retrieving the feed detail for the data feed comprises:
 obtaining a file;   decrypting the file;   validating a source to ensure that the source meets expected specifications;   processing the file according to the field mapping; and   storing the results of the processing in a staging database.   
     
     
         27 . The computer system of  claim 24 , wherein performing business rule processing for the data feed comprises:
 evaluating each record against defined business rules;   disposing each record according to the evaluating step; and   inserting or updating a profile or a contract into a final destination database based on the evaluating and disposing steps.   
     
     
         28 . The computer system of  claim 24 , wherein executing the outbound feed comprises:
 scheduling a job to call the data processing engine;   specifying an outbound integration to run;   setting a location of configuration data;   obtaining configuration information from the data feed and the feed detail;   constructing an execution string based on an object field and a parameter field;   executing the execution string;   returning a data set;   transforming the data set into a file specification based on the field mapping;   storing the data set with the file specification into a temporary local location;   logging the field mapping construct results to the data feed job and the feed detail log;   transmitting the file from a local source to a destination based on details in the transmission detail; and   logging the transmission results into the data feed job.   
     
     
         29 . A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processing units at a computer for a data processing engine for an identity management system comprising instructions for:
 configuring an inbound or outbound feed;   executing the inbound feed; and   executing the outbound feed.   
     
     
         30 . The non-transitory computer-readable storage medium of  claim 29 , wherein configuring the inbound or outbound feed comprises:
 defining a transmission detail;   defining a data feed;   defining a feed detail; and   defining a field mapping.   
     
     
         31 . The non-transitory computer-readable storage medium of  claim 30 , wherein defining the transmission detail comprises:
 defining a transfer protocol;   defining a server name;   defining a port; and   defining a credential.   
     
     
         32 . The non-transitory computer-readable storage medium of  claim 30 , wherein defining the data feed comprises:
 defining a topic of information or a pre-defined category; and   defining a direction of data flow.   
     
     
         33 . The non-transitory computer-readable storage medium of  claim 30 , wherein defining the feed detail comprises:
 defining source details; and   monitoring attributes.   
     
     
         34 . The non-transitory computer-readable storage medium of  claim 33 , wherein defining the source details comprises:
 defining a location;   defining a file type and a delimiter;   defining an extension;   defining a filename mask;   defining header or footer information; and   encrypting the data.   
     
     
         35 . The non-transitory computer-readable storage medium of  claim 33 , wherein monitoring attributes comprises:
 monitoring cadency;   monitoring frequency;   monitoring anomalies;   monitoring quality; and   monitoring traceability.   
     
     
         36 . The non-transitory computer-readable storage medium of  claim 30 , wherein defining the field mapping comprises defining data type, data length and data position. 
     
     
         37 . The non-transitory computer-readable storage medium of  claim 30 , wherein configuring the inbound or outbound feed further comprises:
 defining a destination detail;   defining business rule processing; and   repeating the step of configuring the inbound or outbound feed.   
     
     
         38 . The non-transitory computer-readable storage medium of  claim 30 , wherein executing the inbound feed comprises:
 obtaining a list of all data feeds to be executed; and   for each data feed to be executed,   connecting the data feed to the transmission detail;   retrieving the feed detail for the data feed;   inserting execution results for the data feed into a data feed job; and   performing business rule processing for the data feed.   
     
     
         39 . The non-transitory computer-readable storage medium of  claim 38 , wherein obtaining a list of all data feeds to be executed comprises:
 looking at a status of the data feed; and   executing a run at least as often as a shortest cadence.   
     
     
         40 . The non-transitory computer-readable storage medium of  claim 38 , wherein retrieving the feed detail for the data feed comprises:
 obtaining a file;   decrypting the file;   validating a source to ensure that the source meets expected specifications;   processing the file according to the field mapping; and   storing the results of the processing in a staging database.   
     
     
         41 . The non-transitory computer-readable storage medium of  claim 38 , wherein performing business rule processing for the data feed comprises:
 evaluating each record against defined business rules;   disposing each record according to the evaluating step; and   inserting or updating a profile or a contract into a final destination database based on the evaluating and disposing steps.   
     
     
         42 . The non-transitory computer-readable storage medium of  claim 38 , wherein executing the outbound feed comprises:
 scheduling a job to call the data processing engine;   specifying an outbound integration to run;   setting a location of configuration data;   obtaining configuration information from the data feed and the feed detail;   constructing an execution string based on an object field and a parameter field;   executing the execution string;   returning a data set;   transforming the data set into a file specification based on the field mapping;   storing the data set with the file specification into a temporary local location;   logging the field mapping construct results to the data feed job and the feed detail log;   transmitting the file from a local source to a destination based on details in the transmission detail; and   logging the transmission results into the data feed job.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.