Extended WSDL for SIP Call Flow Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current SIP call flow interactions in Web service description language (WSDL) lack flexibility and granularity, making it difficult to effectively manage complex call flows and integrate SIP and HTTP sessions within converged applications.
Innovation Solution
Extending WSDL with additional bindings that associate operations with call flow segments and interaction points, allowing for bi-directional interactions and fine-grained control, and introducing a lifecycle listener interface to manage binding points between a converged Web service processing engine and application implementation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional WSDL is used for SIP call flow interactions, then interface description is provided, but flexibility and granularity for managing complex call flows is insufficient
Solution Approach 1:
The patent segments the call flow into distinct segments that can be independently associated with Web service operations. Each call flow segment represents a specific portion of the overall call flow, allowing for fine-grained control and management of complex SIP interactions while maintaining interface description capabilities.
Solution Approach 2:
The patent extends WSDL by adding a new dimension - call flow segment associations. This extension allows operations to be linked with specific call flow segments, providing both interface description and call flow control in a unified framework without increasing inherent complexity.
2Measurement precision
If traditional WSDL is used for SIP call flow interactions, then interface description is provided, but granularity for controlling call flow interaction points is insufficient
Solution Approach 1:
The patent divides the call flow into multiple segments, each representing a specific interaction point or phase. This segmentation enables precise control over where and how Web service operations are invoked within the call flow, providing the necessary granularity for managing complex SIP interactions.
Solution Approach 2:
The patent applies local quality by allowing different call flow segments to be associated with different Web service operations based on their specific requirements. Each segment can have its own binding and interaction characteristics, enabling precise, localized control without affecting the entire call flow structure.
3Adaptability or versatility
If converged applications bridge SIP and HTTP sessions, then protocol integration is achieved, but session management complexity increases
Solution Approach 1:
The patent merges SIP call flow management with Web service interface description by extending WSDL to include call flow segment associations. This integration allows converged applications to manage both SIP and HTTP sessions through a unified framework, reducing the complexity of handling multiple protocol sessions separately.
Solution Approach 2:
The extended WSDL framework serves multiple functions: it provides interface description, defines binding operations, associates call flow segments, and manages interaction points. This multi-functionality reduces the need for separate mechanisms for each aspect of converged application management, simplifying overall session management.
Data Source
AI summary
An extended Web services description language (WSDL) is provided to allow for the merging of call flow XML with the interface description. This is accomplished through additional WSDL bindings for operations that associate an operation with segments or message points within the call flow. In addition, the extension to WSDL defines a set of interactions that provide additional semantics for how the operation interacts with the call flow. These interactions capture the interaction points between the WSDL. The WSDL interfaces that are created may be used for outbound interactions (i.e. initiated through Web services from some event within the call flow) or for the usual inbound request response. An additional lifecycle listener interface is used to convey different binding points between an enhanced converged Web service processing engine and a converged application implementation of the WSDL.