Method and apparatus for supporting service enablers via service request handholding

• US 20050015340A1
• Filed: 05/28/2004
• Published: 01/20/2005
• Est. Priority Date: 06/27/2003
• Status: Abandoned Application

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Maes, Stephane H.
• Application Number:
  US10/855,999
• Publication Number:
  US 20050015340A1
• Time in Patent Office: Days
• US Class Current: 705/44
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: H04L 63/0227 Filtering policies mail message filtering H04L51/212
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227

Abstract

A system for enforcing an execution policy associated with a responder includes a framework configured to enforce the execution policy of a target responder in response to a request from a requester, wherein the framework is configured to intercept a request to the target responder, wherein the framework is configured to call at least one supporting finction specified by the execution policy, and wherein the framework is configured to pass the request to the target responder after the call to the one supporting function is successful.

Claims

1. A system for enforcing an execution policy associated with a responder comprises:

a framework configured to enforce the execution policy of a target responder in response to a request from a requester, wherein the framework is configured to intercept a request to the target responder, wherein the framework is configured to call at least one supporting function specified by the execution policy, and wherein the framework is configured to pass the request to the target responder after the call to the one supporting function is successful.

2. The system of claim 1 wherein the execution policy of the target responder includes functions requested from the requester.

3. The system of claim 1 wherein the framework is also configured to provide a filtered execution policy to the requester, and wherein the filtered execution policy indicates the one supporting function.

4. The system of claim 3 wherein the framework is also configured to receive a preference for the one supporting finction from the requestor.

5. The system of claim 3

wherein the execution policy specifies another supporting function,

wherein the framework is also configured to provide a filtered execution policy to the requestor,

wherein the filtered execution policy indicates the one supporting function and the other supporting function, and

wherein the requestor calls the other supporting function.

6. The system of claim 1 wherein the framework is also configured to prompt the requestor for input data.

7. The system of claim 1 wherein the framework is also configured to intercept a response from the requestor to the target responder.

8. The system of claim 1 wherein the requestor is selected from the group:

enabler, service, application, wireless.

9. The system of claim 8 wherein the requestor is in a domain selected from the group:

common domain with the target responder, different domain than the responder.

10. The system of claim 1 wherein the one supporting function is selected from the group:

authentication, authorization, charging, logging.

11. A method for a system comprises:

intercepting in a framework, a request to a target responder;

calling from the framework, at least one supporting function specified by an execution policy associated with the target responder;

determining in the framework, whether the one supporting function has successfully completed; and

passing from the framework, the request to the target responder after the one supporting function has successfully completed.

12. The method of claim 11 further comprising the requestor discovering the target responder interface.

13. The method of claim 12 further comprising:

receiving a preference from the requestor for the one supporting function; and

wherein calling at least one supporting function comprises calling the one supporting function in response to the preference.

14. The method of claim 11 wherein the responder interface is passed via side channels.

15. The method of claim 11 further comprising the requestor determining how to formulate the request to the target responder.

16. The method of claim 11 further comprising providing the execution policy to the framework.

17. The method of claim 11 wherein the one supporting function is selected from the group:

authentication, authorization, charging, logging.

18. The method of claim 11 wherein the framework comprises a plurality of services and enablers.