Generic service component for telephony container server

• US 6,690,781 B2
• Filed: 06/18/2001
• Issued: 02/10/2004
• Est. Priority Date: 06/18/2001
• Status: Expired due to Term

• Current Assignee: Daedalus Blue LLC
• Original Assignee: International Business Machines Corporation
• Inventors: Creamer, Thomas E., Moore, Victor S., Walters, Glen R., Kallner, Samuel, Shachor, Gal
• Primary Examiner(s): Hong, Harry S.
• Application Number:
  US09/884,575
• Publication Number:
  US 20020191771A1
• Time in Patent Office: 967 Days
• Field of Search: 370/259, 379/201.01, 379/201.02, 379/201.03, 379/201.05, 379/201.12, 379/221.08, 379/221.09, 379/221.15, 709/203, 709/223, 709/224, 709/226, 709/229, 709/250, 709/318, 709/328
• US Class Current: 379/201.12
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications
• CPC Class Codes: H04Q 3/0029 Provisions for intelligent networking

Abstract

An advanced intelligent network for use with a call model can include a service logic execution environment (SLEE), at least one service application executing in the SLEE, and at least one generic service component communicatively linked to the service application. The generic service component can include an interface to a second service application which is external to the SLEE.

Claims

1. An advanced intelligent network for use with a call model comprising:

a service logic execution environment (SLEE);

at least one service application executing in said SLEE; and

at least one generic service component communicatively linked to said service application, said generic service component comprising an interface to a second service application which is external to said SLEE.

2. In a telephony environment having a service logic execution environment (SLEE), a generic service component, being registered with the SLEE, for interacting with a service application, said generic service component comprising:

at least one client service instance, each said client service instance corresponding to a service application; and

a service wrapper, said service wrapper providing a common interface to said at least one client service instance for routing events between the SLEE and said at least one client service instance.

3. The generic service component of claim 2, said service wrapper further comprising a deployment descriptor for providing configuration information to the SLEE.

4. The generic service component of claim 2, said service wrapper further comprising a service interface for publishing an interface to said service wrapper.

5. The generic service component of claim 2, said at least one client service instance further comprising a content interface for publishing an interface to said client service instance.

6. The generic service component of claim 2, wherein said generic service component interacts with other generic service components, external applications, service components, or protocol stacks.

7. The generic service component of claim 2, said service wrapper further comprising a protocol stack for managing communications in the telephony environment.

8. The generic service component of claim 2, wherein said service application is internal to the SLEE.

9. The generic service component of claim 2, wherein said service application is external to the SLEE.

10. In a telephony environment having a service logic execution environment (SLEE), a method of routing events between the SLEE and a generic service component, said method comprising:

the generic service component registering with the SLEE; and

the generic service component receiving a first event routed by the SLEE, said first event corresponding to a service application which the generic service component has registered to receive from the SLEE.

11. The method of claim 10, further comprising:

instantiating at least one client service instance for communicating with a service application, said client service instance interacting with said service application.

12. The method of claim 11, further comprising:

posting a second event to the SLEE responsive to said interaction between said client service instance and said service application, said second event corresponding to said interaction.

13. The method of claim 10, wherein said first event is from a protocol stack.

14. The method of claim 10, wherein said first event is from another generic service component.

15. The method of claim 10, wherein said first event is from a service component.

16. The method of claim 10, wherein said first event is from an external application.

17. A machine readable storage, having stored thereon a computer program having a plurality of code sections executable by a machine for causing the machine to perform the steps of:

a generic service component registering with a service logic execution environment (SLEE); and

the generic service component receiving a first event routed by the SLEE, said first event corresponding to a service application which the generic service component has registered to receive from the SLEE.

18. The machine readable storage of claim 17, further comprising:

instantiating at least one client service instance for communicating with a service application, said client service instance interacting with said service application.

19. The machine readable storage of claim 18, further comprising:

posting a second event to the SLEE responsive to said interaction between said client service instance and said service application, said second event corresponding to said interaction.

20. The machine readable storage of claim 17, wherein said first event is from a protocol stack.

21. The machine readable storage of claim 17, wherein said first event is from a service component.

22. The machine readable storage of claim 17, wherein said first event is from another generic service component.

23. The machine readable storage of claim 17, wherein said first event is from an external application.