Service Chaining via Session Context Mediation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication systems face challenges in coordinating events and context between telephony and web services domains, limiting the ability to share data and integrate applications seamlessly across different network types and services.
Innovation Solution
Implementing a Service Delivery Platform (SDP) that uses Web Services standards to chain applications together by retrieving and utilizing session context information, such as buddy lists and location data, stored in a context repository, to invoke subsequent applications in a telephony session, leveraging ccXML and UDDI for interoperability between telephony and web services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If proprietary methods are used to coordinate events and context between web applications and telephony, then integration between specific applications is achieved, but the system lacks universality and requires involvement from multiple application developers
Solution Approach 1:
The patent introduces a service controller as an intermediary component that mediates between telephony events and web services. The service controller subscribes to telephony events, processes them according to service definitions, and invokes appropriate web services automatically. This eliminates the need for proprietary point-to-point integration methods and removes the burden from application developers, as the service controller handles all coordination centrally using standardized protocols.
Solution Approach 2:
The patent implements a universal service controller that can handle multiple types of telephony events and invoke various web services through a single standardized interface. The service controller uses service definitions stored in a database to dynamically determine which web services to invoke based on event type, parameters, and service logic. This multi-functional approach replaces multiple proprietary integration methods with a single universal coordination mechanism.
2Reliability
If individual applications contain their own session context, then each application operates independently, but data sharing between applications is limited and requires developer involvement
Solution Approach 1:
The patent merges the previously distributed session context from individual applications into a centralized service controller. The service controller maintains a unified view of telephony session context and automatically shares this information with relevant web services based on service definitions. This allows all applications to access the same context information without requiring direct integration between them, preserving application independence while enabling seamless context sharing.
3Adaptability or versatility
If multiple application developers are involved to integrate applications, then comprehensive service features can be achieved, but the process is not economically feasible for large numbers of services
Solution Approach 1:
The patent implements a self-service system where the service controller automatically determines which web services to invoke based on telephony events and pre-configured service definitions. The system uses service logic stored in the database to automatically subscribe to relevant events, process parameters, and invoke appropriate services without human intervention. This automation eliminates the need for continuous developer involvement in service integration, making it economically feasible to deploy and maintain large numbers of services.
Solution Approach 2:
The patent employs preliminary action by pre-configuring service definitions that specify which web services should be invoked for each type of telephony event, along with the required parameters and logic. These service definitions are stored in a database before runtime, allowing the service controller to automatically execute the correct integration logic without requiring developers to write custom integration code for each service combination. This preliminary configuration dramatically reduces integration effort for large numbers of services.
Data Source
AI summary
Systems and methods, including computer executable instructions, are provided for telephony service chaining. One method includes invoking a first application in a telephony session. The method includes retrieving a session context associated with the first application and using the session context an input to invoke a second application in the telephony session.