Systems and methods for data interchange among autonomous processing entities

• US 7,752,603 B2
• Filed: 12/08/2004
• Issued: 07/06/2010
• Est. Priority Date: 12/08/2003
• Status: Active Grant

• Current Assignee: Kofax Incorporated
• Original Assignee: Notable Solutions (Microsoft Corporation)
• Inventors: Parsee, Kaveh, Tehranchi, Mehdi, Harutunian, Henric
• Primary Examiner(s): Dam; Tuan Q
• Assistant Examiner(s): Tecklu; Isaac T
• Application Number:
  US11/006,574
• Publication Number:
  US 20050204282A1
• Time in Patent Office: 2,036 Days
• Field of Search: None
• US Class Current: 717/121
• CPC Class Codes: G06F 9/54 Interprogram communication

Abstract

Data element values are shared between a first software component and a second software component of a document processing framework. The components can capture, process, or route a digital image of a document and access a configuration file that is generated for the image. A data element attribute and value pair is placed in the configuration file. The value of the data element is a tag that includes an identifier identifying the first software component and a tag name. The first software component is executed on the image, produces a tag value corresponding to the tag name, searches the configuration file for the tag by the identifier, replaces the tag with the tag value in the configuration file, and terminates. The second software component is executed on the image after the first software component has terminated and reads the data element attribute and value pair.

Claims

1. A system for sharing data element values among software components of a document processing framework that capture, process, and route a digital image of a document, comprising:

a first software component of the document processing framework;

a second software component of the document processing framework;

a configuration file generated for the digital image, the configuration file having at least one data element attribute paired with a runtime replacement tag that the first software component replaces with a value for the data element attribute, wherein the runtime replacement tag comprises;

a start tag delimiter,

an identifier for the first software component,

a tag name,

a separator that separates the identifier for the first software component from the tag name, and

an end tag delimiter; and

a processing device that executes the first software component and the second software component, wherein the processing device is configured to;

determine the first software component identified in the runtime replacement tag from the identifier in the runtime replacement tag;

execute the first software component on the digital image, wherein executing the first software component on the digital image causes the first software component to produce the value for the data element attribute and replace the runtime replacement tag with the value produced for the data element attribute;

terminate the first software component; and

execute the second software component on the digital image in response to terminating the first software component, wherein executing the second software component on the digital image causes the second software component to read the value that replaced the runtime replacement tag in the configuration file.

2. The system of claim 1, wherein the start tag delimiter comprises a first tilde character, the separator that separates the identifier from the tag name comprises two consecutive colon characters, and the end tag delimiter comprises a second tilde character.

3. The system of claim 1, wherein the identifier for the first software component comprises three characters that identify the first software component.

4. The system of claim 1, wherein the tag name comprises one or more of a reserved replacement tag name, a field replacement tag name, or a special set replacement tag name.

5. The system of claim 1, wherein the runtime replacement tag comprises an active runtime replacement tag, and wherein the tag name comprises an executable script that the first software component executes to produce the value for the data element attribute.

6. The system of claim 5, wherein the executable script comprises one or more of variables, variable assignments, conditional statements, loops, conditional loops, functions, operators, arithmetic operators, input functions, or output functions.

7. The system of claim 5, wherein the executable script comprises one or more of Visual Basic™

syntax or Java™

syntax.

8. A method for sharing data element values among software components of a document processing framework that capture, process, and route a digital image of a document, comprising:

generating a configuration file for the digital image, the configuration file having at least one at least one data element attribute paired with a runtime replacement tag that a first software component replaces with a value for the data element attribute, wherein the runtime replacement tag comprises;

a start tag delimiter,

an identifier for the first software component,

a tag name,

a separator that separates the identifier for the first software component from the tag name, and

an end tag delimiter; and

determining, by a processing device, the first software component identified in the runtime replacement tag from the identifier in the runtime replacement tag;

executing, by the processing device, the first software component on the digital image, wherein executing the first software component on the digital image causes the first software component to produce the value for the data element attribute and replace the runtime replacement tag with the value produced for the data element attribute;

terminating, by the processing device, the first software component;

executing, by the processing device, a second software component on the digital image in response to terminating the first software component, wherein executing the second software component on the digital image causes the second software component to read the value that replaced the runtime replacement tag in the configuration file.

9. The method of claim 8, wherein the start tag delimiter comprises a first tilde character, the separator that separates the identifier from the tag name comprises two consecutive colon characters, and the end tag delimiter comprises a second tilde character.

10. The method of claim 8, wherein the identifier for the first software component comprises three characters that identify the first software component.

11. The method of claim 8, wherein the tag name comprises one or more of a reserved replacement tag name, a field replacement tag name, or a special set replacement tag name.

12. The method of claim 8, wherein the runtime replacement tag comprises an active runtime replacement tag, and wherein the tag name comprises an executable script that the first software component executes to produce the value for the data element attribute.

13. The method of claim 12, wherein the executable script comprises one or more of variables, variable assignments, conditional statements, loops, conditional loops, functions, operators, arithmetic operators, input functions, or output functions.

14. The method of claim 12, wherein the executable script comprises one or more of Visual Basic™

syntax or Java™

syntax.

15. A system for sharing information among autonomous processing entities that manipulate an instance of digital content, comprising:

a shared memory space corresponding to the instance of digital content;

a first autonomous processing entity;

a second autonomous processing entity, wherein the shared memory space contains at least one data element attribute paired with a runtime replacement tag that the second autonomous processing entity reads from the shared memory space, wherein the runtime replacement tag comprises an identifier for the first autonomous processing entity and a tag name; and

a processing device that executes the first autonomous processing entity and the second autonomous processing entity, wherein the processing device is configured to;

determine the first autonomous processing entity identified in the runtime replacement tag from the identifier in the runtime replacement tag;

execute the first autonomous processing entity on the instance of digital content, wherein executing the first autonomous processing entity on the instance of digital content causes the first autonomous processing entity to produce the value for the data element attribute and replace the runtime replacement tag with the value produced for the data element attribute; and

execute the second autonomous processing entity on the instance of digital content in response to terminating the first autonomous processing entity, wherein executing the second autonomous processing entity on the instance of digital content causes the second autonomous processing entity to read the value that replaced the runtime replacement tag in the shared memory space.

16. The system of claim 15, wherein the instance of digital content comprises digital data created by one or more of a digital camera, a digital audio recorder, a digital video recorder, a digital audio player, a digital video player, a fax, a multifunctional peripheral, a scanner, a printer, a computer, a point of sale machine, an automated teller machine, a mail server, an address book manager, or a database.

17. The system of claim 15, wherein the instance of digital content comprises one or more of a digital image, a digital audio recording, a digital video recording, a binary file, or a text file.

18. The system of claim 15, wherein the shared memory space comprises one or more of a configuration file or a location in volatile memory.

19. The system of claim 15, wherein first autonomous processing entity comprises one or more of a capture software component, a processing software component, or a routing software component.

20. The system of claim 15, wherein second autonomous processing entity comprises one or more of a capture software component, a process software component, or a route software component.

21. The system of claim 15, wherein the runtime replacement tag has a format that comprises a first tilde character, followed by the identifier, followed by two consecutive colon characters, followed by the tag name, and ended with a second tilde character.

22. The system of claim 15, wherein the identifier for the first autonomous processing entity comprises three characters that identify the first autonomous processing entity.

23. The system of claim 15, wherein the tag name comprises one or more of a reserved replacement tag name, a field replacement tag name, or a special set replacement tag name.

24. The system of claim 15, wherein the runtime replacement tag comprises an active runtime replacement tag, and wherein the tag name comprises an executable script that the first autonomous processing entity executes to produce the value for the data element attribute.

25. The system of claim 24, wherein the executable script comprises one or more of variables, variable assignments, conditional statements, loops, conditional loops, functions, operators, arithmetic operators, input functions, or output functions.

26. The system of claim 24, wherein the executable script comprises one or more of Visual Basic™

syntax or Java™

syntax.

27. A method for sharing information among autonomous processing entities that manipulate an instance of digital content, comprising:

allocating a shared memory space corresponding to the instance of digital content;

selecting a first autonomous processing entity to be executed on the instance of digital content;

selecting a second autonomous processing entity to be executed on the instance of digital content sequentially in response to the first autonomous processing entity terminating;

placing at least one data element attribute paired with a runtime replacement tag in the shared memory space, wherein the second autonomous processing entity reads the at least one data element attribute paired with the runtime replacement tag from the shared memory space, and wherein the runtime replacement tag comprising an identifier for the first autonomous processing entity and a tag name;

determining, by a processing device, the first autonomous processing entity identified in the runtime replacement tag from the identifier in the runtime replacement tag;

executing, by the processing device, the first autonomous processing entity on the instance of digital content, wherein executing the first autonomous processing entity on the instance of digital content causes the first autonomous processing entity to produce the value for the data element attribute and replace the runtime replacement tag with the value produced for the data element attribute; and

executing, by the processing device, the second autonomous processing entity on the instance of digital content in response to terminating the first autonomous processing entity, wherein executing the second autonomous processing entity on the instance of digital content causes the second autonomous processing entity to read the value that replaced the runtime replacement tag in the shared memory space.

28. The method of claim 27, wherein the instance of digital content comprises digital data created by one or more of a digital camera, a digital audio recorder, a digital video recorder, a digital audio player, a digital video player, a fax, a multifunctional peripheral, a scanner, a printer, a computer, a point of sale machine, an automated teller machine, a mail server, an address book manager, or a database.

29. The method of claim 27, wherein the instance of digital content comprises one or more of a digital image, a digital audio recording, a digital video recording, a binary file, or a text file.

30. The method of claim 27, wherein the shared memory space comprises one or more of a configuration file or a location in shared volatile memory.

31. The method of claim 27, wherein first autonomous processing entity comprises one or more of a capture software component, a processing software component, or a routing software component.

32. The method of claim 27, wherein second autonomous processing entity comprises one or more of a capture software component, a process software component, or a route software component.

33. The method of claim 31, wherein the capture software component comprises one or more of a digital sender reader, an address book manager exporter, an extensible markup language reader, a multifunctional peripheral interface, a poll directory software component, a content management queue software component, a batch importer, an email importer, or an application extractor.

34. The method of claim 31, wherein the process software component comprises one or more of an extensible markup language processing software component, an optical character recognition software component, an image management utility, an encryption or decryption software component, a barcode reader, a file utility, a notification software component, a database connectivity interface, a data interchange software component, a watermark creation software component, or a Visual Basic™

or Java™

scripting software component.

35. The method of claim 31, wherein the route software component comprises one or more of a fax software component, a directory software component, a printer software component, a portal or server interface, a content management software interface, a database connectivity interface, or a relational database interface.

36. The method of claim 32, wherein the capture software component comprises one or more of a digital sender reader, an address book manager exporter, an extensible markup language reader, a multifunctional peripheral interface, a poll directory software component, a content management queue software component, a batch importer, an email importer, or an application extractor.

37. The method of claim 32, wherein the process software component comprises one or more of an extensible markup language processing software component, an optical character recognition software component, an image management utility, an encryption or decryption software component, a barcode reader, a file utility, a notification software component, a database connectivity interface, a data interchange software component, a watermark creation software component, or a Visual Basic™

or Java™

scripting software component.

38. The method of claim 32, wherein the route software component comprises one or more of a fax software component, a directory software component, a printer software component, a portal or server interface, a content management software interface, a database connectivity interface, or a relational database interface.

39. The method of claim 27, wherein the runtime replacement tag has a format that comprises a first tilde character, followed by the identifier, followed by two consecutive colon characters, followed by the tag name, and ended with a second tilde character.

40. The method of claim 27, wherein the identifier for the first autonomous processing entity comprises three characters that identify the first autonomous processing entity.

41. The method of claim 27, wherein the tag name comprises one or more of a reserved replacement tag name, a field replacement tag name, or a special set replacement tag name.

42. The method of claim 27, wherein the runtime replacement tag comprises an active runtime replacement tag and wherein the tag name comprises an executable script that the first autonomous processing entity executes to produce the value for the data element attribute.

43. The method of claim 42, wherein the executable script comprises one or more of variables, variable assignments, conditional statements, loops, conditional loops, functions, operators, arithmetic operators, input functions, or output functions.

44. The method of claim 42, wherein the executable script comprises one or more of Visual Basic™

syntax or Java™

syntax.

45. A system for sharing data element values in a document processing framework, comprising:

a first software component;

a second software component;

a configuration file generated for a digital object, the configuration file having at least one data element attribute paired with an active runtime replacement tag that the first software component replaces with a value for the data element attribute, wherein the active runtime replacement tag comprises an identifier for the first software component and an executable script; and

a processing device that executes the first software component and the second software component, wherein the processing device is configured to;

determine the first software component identified in the active runtime replacement tag from the identifier in the active runtime replacement tag;

execute the first software component on the digital object, wherein executing the first software component on the digital object causes the first software component to execute the executable script in the active runtime replacement tag to produce the value for the data element attribute and replace the active runtime replacement tag with the value produced for the data element attribute; and

execute the second software component on the digital object in response to the first software component terminating, wherein executing the second software component on the digital object causes the second software component to read the value that replaced the active runtime replacement tag in the configuration file.

46. A method for sharing data element values in a document processing framework, comprising:

generating, by a processing device, a configuration file for a digital object, the configuration file having at least one data element attribute paired with an active runtime replacement tag, wherein the active runtime replacement tag comprises an identifier for a first software component and an executable script;

executing, by the processing device, the first software component identified in the active runtime replacement tag on the digital object, wherein executing the first software component on the digital object causes the first software component to execute the executable script in the active runtime replacement tag to produce the value for the data element attribute and replace the active runtime replacement tag with the value produced for the data element attribute; and

executing, by the processing device, a second software component on the digital object in response to the first software component terminating, wherein executing the second software component on the digital object causes the second software component to read the value that replaced the active runtime replacement tag in the configuration file.