Service-Oriented Object Framework for Telephony Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current application development architectures, such as JAIN SLEE and PARLAY, face challenges in providing a robust development environment for telephony applications that can seamlessly integrate with web services infrastructure, leading to difficulties in deploying distributed, logical applications and connecting telephony services to web services.
Innovation Solution
A Service-Oriented Object Framework (SOOF) is introduced, which provides a multi-layer architecture with infrastructure objects, service objects, and business objects to facilitate the creation and deployment of telephony services within a SIP servlet container, enabling seamless integration with web services infrastructure and optimizing object life management, platform resources, and event management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional applications are built within isolated platforms with fixed functions, then application stability is maintained, but adaptability to new services and integration with other applications deteriorates
Solution Approach 1:
The patent segments applications into independent, reusable service components that can be individually developed, deployed, and combined. This allows new services to be integrated without redesigning entire applications, resolving the contradiction between adaptability and complexity by breaking down monolithic structures into manageable units.
Solution Approach 2:
The patent creates a universal service component architecture where standardized interfaces and protocols enable different service components to work together across various applications and platforms. This universal framework provides adaptability while maintaining manageable complexity through consistent design patterns.
2Adaptability or versatility
If applications are modified to accommodate new functions or service integrations, then adaptability improves, but development time and deployment complexity increase
Solution Approach 1:
The patent employs preliminary action by pre-defining standardized service interfaces, protocols, and integration patterns before actual service development. This preparation work enables rapid assembly and integration of new services without extensive modification work, reducing development time while maintaining adaptability.
Solution Approach 2:
The patent implements a nested architecture where service components are organized in hierarchical layers with reusable templates and frameworks. New services can be nested within existing service structures, allowing rapid deployment by leveraging pre-built foundational elements rather than creating everything from scratch.
3Ease of operation
If a detailed hierarchy of service components is established, then service organization and management improve, but deployment complexity and abstraction layers increase
Solution Approach 1:
The patent introduces intermediary layers and abstraction mechanisms that simplify service management while hiding deployment complexity. These intermediaries provide standardized control interfaces and automated management capabilities, allowing service operators to manage complex hierarchies without directly dealing with underlying deployment intricacies.
Data Source
Figure 1A~1B
Figure 2~3
AI summary
Systems and methods defining a service oriented object framework for use in providing an open application environment facilitating application function integration are shown. Embodiments provide object life management, platform resources management, and event management capabilities. A multi-layer architecture, defining object layers within an application container, may be used. A primary layer of such an architecture may comprise infrastructure objects providing foundational element blocks embodying protocol specific functions of the services that are to be built on top of a development container. An intermediate layer of such an architecture may comprise service objects providing service level functions. An upper layer of such an architecture may comprise business objects providing application orchestration element blocks defining the logical application created by combining the foregoing objects. Embodiments implement a framework that provides utilities that enable the object hierarchy to interact and function on top of a corresponding development container platform.