Generic service component for message formatting

• US 6,876,733 B2
• Filed: 12/03/2002
• Issued: 04/05/2005
• Est. Priority Date: 12/03/2002
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Creamer, Thomas E., Moore, Victor S., Walters, Glen R., McIntyre, Joseph H.
• Primary Examiner(s): Tieu, Benny
• Application Number:
  US10/308,590
• Publication Number:
  US 20040105537A1
• Time in Patent Office: 854 Days
• Field of Search: 37922108-22112, 379/219, 379/220.01, 379/229, 379/230, 379/201.12, 709/223, 719/310, 719/328
• US Class Current: 379/201.12
• CPC Class Codes: H04Q 3/0058 using service-independent building blocks (SIBBs) or "primitives"

Abstract

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

Claims

1. An advanced intelligent network for use with a telecommunication service comprising:

a service logic execution environment (SLEE);

at least one service application executing in said SLEE; and

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

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

at least one client service instance, each said client service instance corresponding to a message formatting 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 message formatting generic service component of claim 2, said service wrapper further comprising a deployment descriptor for providing configuration information to the SLEE.

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

5. The message formatting 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 message formatting generic service component of claim 2, wherein said message formatting generic service component interacts with other generic service components, external applications, service components, or protocol stacks.

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

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

9. The message formatting generic service component of claim 2, wherein said message formatting 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 message formatting generic service component, said method comprising:

the message formatting generic service component registering with the SLEE; and

,

the message formatting generic service component receiving a first event routed by the SLEE said first event corresponding to a service application which the message formatting 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 an application external to the SLEE, said client service instance interacting with said 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 application, said second event corresponding to said interaction.

13. The method of claim 12, wherein said second event is directed to a service application executing within the SLEE.

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

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

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

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

18. 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 message formatting generic service component registering with a service logic execution environment (SLEE); and

,

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

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

instantiating at least one client service instance for communicating with an application external to the SLEE, said client service instance interacting with said application.

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

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

21. The machine readable storage of claim 20, wherein said second event is directed to a service application executing within the SLEE.

22. The machine readable storage of claim 18, wherein said first event is from protocol stack.

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

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

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