Information gathering system and method

• US 20100174826A1
• Filed: 12/23/2004
• Published: 07/08/2010
• Est. Priority Date: 12/23/2003
• Status: Abandoned Application

• Current Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Original Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Inventors: Sharma, Anupam, Patole, Devendra, Sharma, Abhimanyu
• Application Number:
  US11/020,290
• Publication Number:
  US 20100174826A1
• Time in Patent Office: Days
• US Class Current: 709/235
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/105 Multiple levels of security
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

A system and a method for gathering information in a secure and efficient manner is provided. A two-level security procedure ensures that communication occurs only between authorized parties. Communications between parties are according to the XML convention, which enables the parties to communicate or transfer information with each other even if they use incompatible communications systems. Communications may occur synchronously or asynchronously depending on predetermined parameters, such as the complexity of the communication and the amount of information being communicated or transferred.

Claims

1. A System for communicating information, comprising:

an agent module configured to receive from an external party requests for information, wherein the requests for information include at least two verifications from the external party, wherein the verifications comprise (i) a digital certificate corresponding to the external party and (ii) separate credential information for each type of information requested;

a security module configured to authenticate the digital certificate and to verify the credential information;

a controller module configured to throttle an amount of traffic to prevent the request for information from the external party from putting an excessive load on the system;

a request handler module configured to handle the requests for information and to package information from the external party into objects suitable for processing by the system;

a request distributor module configured to determine whether a request for information is to be handled synchronously or asynchronously;

a queue module configured to manage requests to be handled asynchronously by inserting each request in a processing queue corresponding to a type of information requested;

a business adapters module configured to, upon receipt of a request for information from the queue module or from the request distributor module, translate the request for information into a format suitable to be processed by an application server corresponding to the request for information; and

at least one data storage unit configured to store information.

2. A system according to claim 1, wherein the request handler is configured to handle XML requests for information from the external party and to determine in which data storage unit the information requested by the external party is stored.

3. A system according to claim 1,

wherein the security module is configured to authenticate the digital certificate once for a plurality of requests for information from the external party, and

wherein, for each type of information requested, the corresponding credential information provided by the external party is verified based on credential information stored for that type of information.

4. A system according to claim 1, wherein the request distributor makes a determination based on predefined rules, such that simple requests are to be handled synchronously and complex requests are to be handled asynchronously.

5. A system according to claim 4, wherein a simple request is a request for an amount of information less than a predetermined amount.

6. A system according to claim 4, wherein a complex request is a request for multiple types of information.

7. A system according to claim 1,

wherein the business adapters module includes a plurality of business adapters,

wherein the plurality of business adapters corresponds to a respective plurality of subsystems of the system,

wherein each business adapter encapsulates a workflow procedure for obtaining data or information from a corresponding subsystem of the system, and

wherein the business adapters module is expandable to accommodate a new business adapter corresponding to a new subsystem of the system.

8. A system according to claim 1, further comprising a business rules module configured to provide rules for handling the requests for information, wherein the business rules module determines whether requested information is a type of information not to be provided to the external party.

9. A system according to claim 1, wherein the business rules module provides rules for at least one of retrieving, formatting, and sending requested information to the external party.

10. A system according to claim 1, further comprising a response processor module configured to package information received from one or more application servers into a format suitable for the external party.

11. A system according to claim 10, wherein the response processor module packages information into an XML format suitable for the external party.

12. A system according to claim 1, further comprising an external framework module configured to establish a transport mode from a plurality of transport modes for transferring information between the system and the external entity, wherein the transport mode is a HTTP, a HTTPS, a Database, a MQ, a SOAP, a TCP/IP, or a legacy transport mode.

13. A system according to claim 1, wherein at least one of the modules comprising the system is a software routine residing in a server.

28. A system according to claim 1, wherein, if credential information for a type of information cannot be verified although credential information for another type of information can be verified, the business adapters module translates a request for information corresponding to the other type of information.

30. A system according to claim 4, wherein a response to a complex request is forwarded to a proxy server from where the response is may be retrieved by the external party.

14. A method for communicating information between a system and an external party, comprising the steps of:

receiving from the external party requests for information, wherein the requests for information include at least two verifications from the external party, wherein the verifications comprise (i) a digital certificate corresponding to the external party and (ii) separate credential information for each type of information requested;

authenticating the digital certificate to determine whether the external party is authorized to obtain information from the system;

verifying, for each type of information requested, whether the corresponding credential information is valid for that type of information requested;

controlling an amount of traffic to prevent the request for information from the external party from putting an excessive load on the system;

packaging information from the external party into objects suitable for processing by the system;

determining whether a request for information is to be handled synchronously or asynchronously;

for requests to be handled asynchronously, inserting each request in a processing queue corresponding to a type of information requested; and

translating each request for information into a format suitable to be processed by an application server corresponding to the request for information.

15. A method according to claim 14, wherein the requests for information are XML requests.

16. A method according to claim 14,

wherein the step of authenticating authenticates the digital certificate once for a plurality of requests for information from the external party, and

wherein, for each type of information requested, the corresponding credential information provided by the external party is verified based on credential information stored for that type of information.

17. A method according to claim 14, wherein the step of determining is performed based on predefined rules, such that simple requests are to be handled synchronously and complex requests are to be handled asynchronously.

18. A method according to claim 17, wherein a simple request is a request for an amount of information less than a predetermined amount.

19. A method according to claim 17, wherein a complex request is a request for multiple types of information.

20. A method according to claim 14,

wherein the step of translating is performed by a business adapter module that includes a plurality of business adapters,

wherein the plurality of business adapters corresponds to a respective plurality of subsystems of the system,

wherein each business adapter encapsulates a workflow procedure for obtaining data or information from a corresponding subsystem of the system, and

wherein the business adapters module is expandable to accommodate a new business adapter corresponding to a new subsystem of the system.

21. A method according to claim 14, further comprising the step of providing rules for handling the requests for information and determining whether requested information is a type of information not to be provided to the external party.

22. A method according to claim 21, wherein the step of providing rules provides rules for at least one of retrieving, formatting, and sending requested information to the external party.

23. A method according to claim 14, further comprising the step of packaging information received from one or more application servers into a format suitable for the external party.

24. A method according to claim 23, wherein the step of packaging information packages information into an XML format suitable for the external party.

25. A method according to claim 14, further comprising the step of establishing a transport mode from a plurality of transport modes for transferring information between the system and the external entity, wherein the transport mode is a HTTP, a HTTPS, a Database, a MQ, a SOAP, a TCP/IP, or a legacy transport mode.

26. A method according to claim 14, wherein at least one of the steps of comprising the method is performed by a software routine residing in a server.

27. A method according to claim 17, wherein a response to a complex request is forwarded to a proxy server from where the response is may be retrieved by the external party.

29. A method according to claim 14, wherein, if credential information for a type of information cannot be verified although credential information for another type of information can be verified, the step of translating translates a request for information corresponding to the other type of information.

31. A computer-readable storage medium storing computer code for implementing a method of communicating information between a system and an external party, wherein the computer code comprises:

an agent module configured to receive from an external party requests for information, wherein the requests for information include at least two verifications from the external party, wherein the verifications comprise (i) a digital certificate corresponding to the external party and (ii) separate credential information for each type of information requested;

a security module configured to authenticate the digital certificate and to verify the credential information;

a controller module configured to throttle an amount of traffic to prevent the request for information from the external party from putting an excessive load on the system;

a request handler module configured to handle the requests for information and to package information from the external party into objects suitable for processing by the system;

a request distributor module configured to determine whether a request for information is to be handled synchronously or asynchronously;

a queue module configured to manage requests to be handled asynchronously by inserting each request in a processing queue corresponding to a type of information requested; and

a business adapters module configured to, upon receipt of a request for information from the queue module or from the request distributor module, translate the request for information into a format suitable to be processed by an application server corresponding to the request for information.