Abstract: The invention provides a method and apparatus for an extensible markup language (XML) calendar-telephony interface. The method can include the steps of defining an markup language element having a user defined tag that represents a calendar entry. The markup language element can have attributes which can represent call control instructions or information. The attributes can also be formatted using a markup language format that utilizes user defined tags. The elements and/or attributes can be formatted using XML format. The call control instruction can be provided to a telephony application upon initiation of a call or by request. A calendar application program can be used for maintaining calendar entries which can be stored in a database and made accessible to the telephony call control application.

Abstract: A method of communication among telephony services using an event context cache can include, in a messaging telephony service, receiving a telephony event from a node in the public switched telephony network specifying a called directory number, a calling directory number, and service context data. The service context data can be stored as an entry within the event context cache. The event context cache can be accessible by at least one other telephony service. The entry can be associated with a key for the event context cache. The key can be specified by the called directory number and the calling directory number.

Abstract: A method for visually generating a service component can include specifying at least one service building block, wherein the specification includes visually selecting a plurality of event handlers for inclusion in the at least one service building block. The method can also include exporting the at least one service building block. The exporting step can produce a deployment descriptor which describes events for which the at least one service building block has been configured to handle. The at least one service block can be visually arranged, wherein the arrangement can form the service component. Finally, the service component produced by the visual arrangement can be configured for insertion in a SLEE in an advanced intelligent network. Notably, in one aspect of the method, the method can further include the step of encapsulating the service component in a service application container.

Abstract: The invention provides a method and apparatus for an extensible markup language (XML) calendar-telephony interface. The method can include the steps of defining an markup language element having a user defined tag that represents a calendar entry. The markup language element can have attributes which can represent call control instructions or information. The attributes can also be formatted using a markup language format that utilizes user defined tags. The elements and/or attributes can be formatted using XML format. The call control instruction can be provided to a telephony application upon initiation of a call or by request. A calendar application program can be used for maintaining calendar entries which can be stored in a database and made accessible to the telephony call control application.

Abstract: The present invention provides a method and apparatus for providing an XML calendar-telephony interface. A calendar-telephony interface permits interchange of information between an electronic calendar and a telephony call control application. A telephony call control application (telephony application) can be interfaced to a PSTN through a TCAP interface utilizing, for example, Java APIs for Integrated Networks (JAIN). JAIN provides standardized open APIs which can be utilized to build and integrated services and components for communications networks such as the PSTN. In response to a call request initiated in the PSTN by a calling party, the telephony application can determine from callerlD information associated with the call request, the identity of the called party. This can include the called party's name or identity.

Abstract: A method of directly administering a service component through a hypermedia document can include a series of steps. The hypermedia document can provide an interface to a service logic execution environment (SLEE). At least one administrative option embodied in the hypermedia document can be provided. The at least one administrative option can correspond to a function to be performed by the service component. A user specified administrative option can be received in the hypermedia document and a SLEE compatible event can be generated based on the user specified administrative option. The event can be a type which the service component has been registered in the SLEE to receive. Also, the event can be routed to the service component via the SLEE. The service component can process the event and perform an administrative function consistent with the event.

Abstract: A method of directly changing a service attribute corresponding to a service component through a hypermedia document. The hypermedia document can provide an interface to a service logic execution environment (SLEE). The method can include providing a plurality of selections embodied in the hypermedia document. The plurality of selections can correspond to the service attribute. The method further can include receiving a user specified selection in the hypermedia document and generating a SLEE compatible event based on the user selection. The event can be of a type which the service component has been registered in the SLEE to receive. Also, the event can be routed to the service component via the SLEE. The service component can process the event and update service attribute information corresponding to the service attribute consistent with the event.

Abstract: An advanced intelligent network according to the present invention can include a service logic execution environment (SLEE). The SLEE can include an event handler for routing messages between and among client components and service components. The advanced intelligent network further can include at least one service component configured to post and receive messages to and from other service components in the SLEE through the event handler. At least one Internet enabled service component (IESC) executing in the SLEE also can be included. The IESC can be configured to post and receive messages to and from other service components in SLEE through the event handler. The IESC can be communicatively linked to a server side program external to the SLEE.

Abstract: A telephone system provides subscribers with access to a service provider's platform logic and data implemented in any runtime environment. In one embodiment, the service logic is embodied in Java applets and Java beans in a JAVA virtual machine for subscriber personalizing and modifying the service logic. The provider provides the subscriber a tool kit or access to a support server for writing service logic modifications as JAVA beans. The service logic modification is achieved in a process in which the service requirements and objectives are set. The service specifications are designed, implemented, tested, and rolled out. Initial service provisioning and support is provided a subscriber, service modification by the subscriber is made to subscriber data provisioning and subscriber service logic provisions. A modified service logic is locally tested by the subscriber, followed by remote testing of the modification on the service provider's premises.

Abstract: To allow concurrent operation with more than one facility through the same standard programming interface, a data processing system is disclosed in which an application program can communicate with two or more system facilities via a programming interface common to the facilities, the system comprising a look-up table relating each of the facilities to corresponding entry point information for an implementation therefor of the programming interface, whereby an application program can select at any particular time which of the facilities to communicate with using the interface by extracting from the look-up table the entry point information corresponding to the implementation of the programming interface for the selected facility.