SAFE SERVICES FRAMEWORK

• US 20130054770A1
• Filed: 08/31/2011
• Published: 02/28/2013
• Est. Priority Date: 08/31/2011
• Status: Active Grant

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: Lawson, Richard Lougheed, Kelly, William Earnest
• Granted Patent: US 9,148,447 B2
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227

Abstract

Providing security-related services for enterprise service requests includes receiving a service request from an endpoint, determining the transaction parameter from the received service request, determining a subroutine for execution based on the transaction parameter, communicating with a data server to execute the subroutine, receiving subroutine results from the data server based on the executed subroutine, applying context-specific rules to the request based on instructive data specified in the subroutine results, determining a response based on the subroutine results and the applied context-specific rules, and communicating the response to the endpoint. Some embodiments may also include accessing transaction rules associated with the transaction parameter, determining an additional subroutine for execution based on the transaction rules, communicating with a data server to execute the additional subroutine, receiving additional subroutine results from the data server based on the executed additional subroutine, and communicating the results to the endpoint.

Claims

1. An apparatus, comprising:

an interface operable to receive a service request from an endpoint, wherein the service request comprises a transaction parameter;

a memory operable to store transaction rules corresponding to at least one type of service request; and

a processor communicatively coupled to the interface, the processor operable to;

determine the transaction parameter from the received service request;

determine a subroutine for execution based on the transaction parameter;

communicate with a data server to execute the subroutine;

receive subroutine results from the data server based on the executed subroutine;

apply context-specific rules to the service request based on instructive data specified in the subroutine results;

determine a response based on the subroutine results and the applied context-specific rules; and

communicate the response to the endpoint.

2. An apparatus of claim 1, wherein the processor is further operable to:

access transaction rules associated with the transaction parameter;

determine an additional subroutine for execution based on the transaction rules;

communicate with a data server to execute the additional subroutine;

receive additional subroutine results from the data server based on the executed additional subroutine; and

communicate the results to the endpoint.

3. An apparatus of claim 2, wherein determining an additional subroutine for execution based on the transaction rules comprises:

determining that the transaction parameter corresponds a transaction rule; and

identifying the additional subroutine that is associated with the transaction rule for execution by the data server.

4. An apparatus of claim 1, wherein determining a response based on the subroutine results and the applied context-specific results comprises:

determining that the received information matches one of the context-specific rules; and

creating the response based on the matched context-specific rule.

5. An apparatus of claim 4, wherein creating a response based on the matched context-specific rule comprises:

communicating with a second data server to execute an additional subroutine;

receiving the additional subroutine results from the additional subroutine; and

populating the response based on the received additional subroutine results.

6. An apparatus of claim 1, wherein the processor is further operable to:

determine whether additional data is required from the endpoint;

communicate with the endpoint to request the additional data; and

receive the requested additional data from the endpoint.

7. An apparatus of claim 6, wherein the processor is further operable to receive an indication from the data server executing the subroutine that the additional data is required from the endpoint to process the service request.

8. A method, comprising:

receiving a service request from an endpoint, wherein the service request comprises a transaction parameter; and

storing transaction rules corresponding to at least one type of service request; and

using a processor to;

determine the transaction parameter from the received service request;

determine a subroutine for execution based on the transaction parameter;

communicate with a data server to execute the subroutine;

receive subroutine results from the data server based on the executed subroutine;

apply context-specific rules to the service request based on instructive data specified in the subroutine results;

determine a response based on the subroutine results and the applied context-specific rules; and

communicate the response to the endpoint.

9. A method of claim 8, further comprising using the processor to:

access transaction rules associated with the transaction parameter;

determine an additional subroutine for execution based on the transaction rules;

communicate with a data server to execute the additional subroutine;

receive additional subroutine results from the data server based on the executed additional subroutine; and

communicate the results to the endpoint.

10. A method of claim 9, wherein determining an additional subroutine for execution based on the transaction rules comprises:

determining that the transaction parameter corresponds a transaction rule; and

identifying the additional subroutine that is associated with the transaction rule for execution by the data server.

11. A method of claim 8, wherein determining a response based on the subroutine results and the applied context-specific results comprises:

determining that the received information matches one of the context-specific rules; and

creating the response based on the matched context-specific rule.

12. A method of claim 11, wherein creating a response based on the matched context-specific rule comprises:

communicating with a second data server to execute an additional subroutine;

receiving the additional subroutine results from the additional subroutine; and

populating the response based on the received additional subroutine results.

13. A method of claim 8, wherein the processor is further operable to:

determine whether additional data is required from the endpoint;

communicate with the endpoint to request the additional data; and

receive the requested additional data from the endpoint.

14. A method of claim 13, wherein the processor is further operable to receive an indication from the data server executing the subroutine that the additional data is required from the endpoint to process the service request.

15. A non-transitory computer-readable medium comprising logic, the logic operable, when executed by a processor to:

receive a service request from an endpoint, wherein the service request comprises a transaction parameter;

store transaction rules corresponding to at least one type of service request;

determine the transaction parameter from the received service request;

determine a subroutine for execution based on the transaction parameter;

communicate with a data server to execute the subroutine;

receive subroutine results from the data server based on the executed subroutine;

apply context-specific rules to the service request based on instructive data specified in the subroutine results;

determine a response based on the subroutine results and the applied context-specific rules; and

communicate the response to the endpoint.

16. A non-transitory computer-readable medium of claim 15, wherein the logic is further operable, when executed by a processor to:

access transaction rules associated with the transaction parameter;

determine an additional subroutine for execution based on the transaction rules;

communicate with a data server to execute the additional subroutine;

receive additional subroutine results from the data server based on the executed additional subroutine; and

communicate the results to the endpoint.

17. A non-transitory computer-readable medium of claim 16, wherein determining an additional subroutine for execution based on the transaction rules comprises:

determining that the transaction parameter corresponds a transaction rule; and

identifying the additional subroutine that is associated with the transaction rule for execution by the data server.

18. A non-transitory computer-readable medium of claim 15, wherein determining a response based on the subroutine results and the applied context-specific results comprises:

determining that the received information matches one of the context-specific rules; and

creating the response based on the matched context-specific rule.

19. A non-transitory computer-readable medium of claim 18, wherein creating a response based on the matched context-specific rule comprises:

communicating with a second data server to execute an additional subroutine;

receiving the additional subroutine results from the additional subroutine; and

populating the response based on the received additional subroutine results.

20. A non-transitory computer-readable medium of claim 15, wherein the logic is further operable, when executed by a processor to:

determine whether additional data is required from the endpoint;

communicate with the endpoint to request the additional data; and

receive the requested additional data from the endpoint.

21. An apparatus of claim 20, wherein the logic is further operable, when executed by a processor to receive an indication from the data server executing the subroutine that the additional data is required from the endpoint to process the service request.