SOA-Based Telephony Service Composition via Reusable Widgets

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing electronic network-based telephony systems do not fully leverage the capabilities of new electronic environments, leading to inefficiencies and resource wastage due to proprietary implementations and duplication of code across different networks.

Innovation Solution

A service delivery platform (SDP) and service-oriented architecture (SOA)-based approach that uses reusable 'widgets' to provide telephony functionality, enabling composition of services across disparate networks and protocols, abstracting underlying network technologies to offer unified multimedia and telephony services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If proprietary implementations are used for telephony services on different networks, then each network can be optimized for its specific protocol, but code duplication and resource wastage occur across networks

Engineering Contradiction:
Improvenetwork optimizationVSAvoidcode duplication
Core Design Contradiction:
ReliabilityVSLoss of substance

Solution Approach 1:

The patent implements a universal service logic layer that can operate across multiple network protocols (PSTN, IP-based, mobile networks). The service logic is designed to be protocol-agnostic, allowing the same telephony services to be deployed on different network infrastructures without requiring separate proprietary implementations for each network type.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system architecture segments telephony services into independent, modular service logic components that can be selectively deployed. This segmentation allows the service logic to be separated from network-specific protocol handling, enabling reuse across networks while maintaining protocol optimization through separate adaptation layers.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If separate service logic is developed for each network protocol, then protocol-specific requirements are met, but development time and complexity increase

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidservice logic complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary service logic layer that mediates between the universal service requirements and network-specific protocol implementations. This intermediary layer handles protocol adaptation and translation, allowing service logic to remain simple and protocol-agnostic while still meeting specific protocol requirements through the mediation of adaptation layers.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The service logic is designed with universal functionality that can adapt to multiple protocols through configuration rather than separate implementation. This universality reduces the need for multiple versions of service logic while maintaining protocol-specific compatibility through adaptive interfaces.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Speed

If telephony services are implemented natively on each network, then performance is optimized for that network, but resource utilization decreases due to duplication

Engineering Contradiction:
Improveservice performanceVSAvoidresource utilization
Core Design Contradiction:
SpeedVSProductivity

Solution Approach 1:

The patent merges service logic functionality across multiple networks into a unified, reusable framework. By combining common telephony service logic into a shared implementation that can be deployed across PSTN, IP-based networks, and mobile networks, the system eliminates resource duplication while maintaining performance through network-specific optimization layers.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentEP2438737B1Multimedia telephony application service creation environment
Publication Date: 2017.03.08 ORACLE INT CORP
  • EP2438737B1 patent drawingFigure 1(a)~1(b)
  • EP2438737B1 patent drawingFigure 2~3
  • EP2438737B1 patent drawingFigure 4~5

AI summary

Telephony application services are provided through use of a service delivery platform (SDP) and by implementing a service-oriented architecture (SOA)-based approach. Various "widgets" of telephony functionality are selected, each widget providing functionality such as call forwarding, call blocking, conferencing, etc. These widgets provide not only call manipulation, but can provide the logic used to process a call. An application or application service thus can combine and/or compose these widgets as needed to provide telephony functionality.