Service oriented architecture-based SCIM platform

• US 9,654,515 B2
• Filed: 01/23/2008
• Issued: 05/16/2017
• Est. Priority Date: 01/23/2008
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Maes, Stephane H.
• Primary Examiner(s): Kraft, Shih-Wei
• Application Number:
  US12/018,718
• Publication Number:
  US 20090187919A1
• Time in Patent Office: 3,401 Days
• Field of Search: None
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]

Abstract

Service Capability Interaction Manager (SCIM)-type functionality is provided at a horizontal service layer in an Service Oriented Architecture (SOA)-based approach. SCIM composition is provided at multiple levels, including the level of composition where servlets have full access to the context information of the service layer. SCIM composition also occurs at the level of an application dispatching messages to multiple applications/services for processing the messages. The functionality at the service layer also can be programmed using policies, such that routing decisions can be made dynamically as the result of processing conditions and actions. An incoming message can result in a Web service being triggered that in turn triggers a BPEL or SOA workflow, the workflow calling multiple operations to process the message as a result of a routing table or header, environmental and contextual information at the service level, and other information such as user preference or presence information.

Claims

1. A system for processing requests, the system comprising:

one or more processors; and

a memory coupled with the processors and having stored therein a sequence of instructions executed by the processors to execute;

a first layer comprising a plurality of applications that provide telephony control features, the plurality of applications comprising an application dispatcher;

a second layer comprising a plurality of abstract call control enablers comprising;

one or more call control enabler interfaces;

one or more Application Program Interfaces (APIs) providing an abstract interface for invoking a plurality of call control functions,

a third layer comprising a plurality of call control enabler instances that provide adapters to network resources to provide the plurality of call control functions, wherein one or more of the call control enabler instances are instantiated in response to one of the plurality of applications invoking one or more of the plurality of call control functions through the APIs; and

a fourth layer comprising a network layer of a plurality of network resources that are each coupled to corresponding ones of the call control enabler instances;

wherein the system is configured to perform operations comprising;

receiving, by the application dispatcher, a Session Initiation Protocol (SIP) request;

analyzing, by the application dispatcher, the request to extract a plurality of Uniform Resource Identifiers (URIs) to process the request from a header field of the request;

dynamically determining, by the application dispatcher, a first application to process the request based on a first URI in the plurality of URIs in the header field, subscriber profile information, and one or more policies, wherein the determination is made in the first layer;

routing the request to the first application to process the request;

receiving a response from the first application after processing the request;

dynamically determining, by the application dispatcher, a second application to process the request based on a second URI in the plurality of URIs in the header field, the response from the first application, the subscriber profile information, and the one or more policies; and

routing the request to the second application to process the request.

2. The system of claim 1, wherein the application dispatcher comprises a Service Capability Interaction Manager (SCIM)-based component operable to determine applications used to process the request.

3. The system of claim 1, wherein the application dispatcher dynamically determines the second application to process the request based at least in part on load balancing.

4. The system of claim 1, wherein the system is further configured to perform operations comprising:

executing a Web services component programmed to direct the request to the application dispatcher.

5. The system of claim 1, wherein:

the application dispatcher comprises a service layer dispatching component programmed to process the request based at least in part on a routing table or a routing application.

6. The system of claim 1, wherein the plurality of call control enabler instances comprises instances for interfacing or adapting to Parlay-based resources.

7. The system of claim 1, wherein the plurality of call control enabler instances comprises an SIP servlet providing an interface to an IP Multimedia Subsystem (IMS).

8. The system of claim 1, wherein routing the request to the first application to process the request includes launching a Service Oriented Architecture (SOA) process.

9. A non-transitory, computer-readable medium comprising instructions for processing requests, the instructions executed by one or more processors to perform operations comprising:

generating a first layer comprising a plurality of applications that provide telephony control features, the plurality of applications comprising an application dispatcher;

generating a second layer comprising a plurality of abstract call control enablers comprising;

one or more call control enabler interfaces;

one or more Application Program Interfaces (APIs) providing an abstract interface for invoking a plurality of call control functions,

generating a third layer comprising a plurality of call control enabler instances that provide adapters to network resources to provide the plurality of call control functions, wherein one or more of the call control enabler instances are instantiated in response to one of the plurality of applications invoking one or more of the plurality of call control functions through the APIs;

generating a fourth layer comprising a network layer of a plurality of network resources that are each coupled to corresponding ones of the call control enabler instances;

receiving, by the application dispatcher, a Session Initiation Protocol (SIP) request;

analyzing, by the application dispatcher, the request to extract a plurality of Uniform Resource Identifiers (URIs) to process the request from a header field of the request;

dynamically determining, by the application dispatcher, a first application to process the request based on a first URI in the plurality of URIs in the header field, subscriber profile information, and one or more policies, wherein the determination is made in the first layer;

routing the request to the first application to process the request;

receiving a response from the first application after processing the request;

dynamically determining, by the application dispatcher, a second application to process the request based on a second URI in the plurality of URIs in the header field, the response from the first application, the subscriber profile information, and the one or more policies; and

routing the request to the second application to process the request.

10. The non-transitory, computer-readable medium of claim 9, wherein the application dispatcher comprises a Service Capability Interaction Manager (SCIM)-based component operable to determine applications used to process the request.

11. The non-transitory, computer-readable medium of claim 9, wherein the application dispatcher dynamically determines the second application to process the request based at least in part on load balancing.

12. The non-transitory, computer-readable medium of claim 9, comprising additional instructions that cause the one or more processors to perform additional operations comprising executing a Web services component programmed to direct the request to the application dispatcher.

13. The non-transitory, computer-readable medium of claim 9, wherein the application dispatcher comprises a service layer dispatching component programmed to process the request based at least in part on a routing table or a routing application.

14. The non-transitory, computer-readable medium of claim 9, wherein the plurality of call control enabler instances comprises instances for interfacing or adapting to Parlay-based resources.

15. The non-transitory, computer-readable medium of claim 9, wherein the plurality of call control enabler instances comprises an SIP servlet providing an interface to an IP Multimedia Subsystem (IMS).

16. The non-transitory, computer-readable medium of claim 9, wherein routing the request to the first application to process the request includes launching a Service Oriented Architecture (SOA) process.

17. A method for processing requests, the method comprising:

generating a first layer comprising a plurality of applications that provide telephony control features, the plurality of applications comprising an application dispatcher;

generating a second layer comprising a plurality of abstract call control enablers comprising;

one or more call control enabler interfaces;

one or more Application Program Interfaces (APIs) providing an abstract interface for invoking a plurality of call control functions,

generating a third layer comprising a plurality of call control enabler instances that provide adapters to network resources to provide the plurality of call control functions, wherein one or more of the call control enabler instances are instantiated in response to one of the plurality of applications invoking one or more of the plurality of call control functions through the APIs;

generating a fourth layer comprising a network layer of a plurality of network resources that are each coupled to corresponding ones of the call control enabler instances;

receiving, by the application dispatcher, a Session Initiation Protocol (SIP) request;

analyzing, by the application dispatcher, the request to extract a plurality of Uniform Resource Identifiers (URIs) to process the request from a header field of the request;

dynamically determining, by the application dispatcher, a first application to process the request based on a first URI in the plurality of URIs in the header field, subscriber profile information, and one or more policies, wherein the determination is made in the first layer;

routing the request to the first application to process the request;

receiving a response from the first application after processing the request;

dynamically determining, by the application dispatcher, a second application to process the request based on a second URI in the plurality of URIs in the header field, the response from the first application, the subscriber profile information, and the one or more policies; and

routing the request to the second application to process the request.

18. The method of claim 17, wherein the application dispatcher comprises a Service Capability Interaction Manager (SCIM)-based component operable to determine applications used to process the request.

19. The method of claim 17, wherein the application dispatcher dynamically determines the second application to process the request based at least in part on load balancing.

20. The method of claim 17, further comprising executing a Web services component programmed to direct the request to the application dispatcher.

21. The method of claim 17, wherein the application dispatcher comprises a service layer dispatching component programmed to process the request based at least in part on a routing table or a routing application.

22. The method of claim 17, wherein the plurality of call control enabler instances comprises instances for interfacing or adapting to Parlay-based resources.

23. The method of claim 17, wherein the plurality of call control enabler instances comprises an SIP servlet providing an interface to an IP Multimedia Subsystem (IMS).

24. The method of claim 17, wherein routing the request to the first application to process the request includes launching a Service Oriented Architecture (SOA) process.