Unified Services Platform for Telecommunication API Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Telecommunications service providers face challenges in integrating advanced services and applications with legacy telephone services due to the use of different IDs and policies by third-party ecosystems, leading to complexity in service management and billing.

Innovation Solution

A unified services platform that uses a telephone number as a common subscriber identifier to integrate multiple application service provider systems, enabling provisioning, billing, and service invocation across different ecosystems, with a policy and rules engine to manage triggering events and actions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple third-party application service provider systems with different IDs and policies are integrated with legacy telephone service, then service versatility and functionality are improved, but system complexity and integration difficulty increase

Engineering Contradiction:
Improveservice versatilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A unified services platform acts as an intermediary layer between legacy telephone service and multiple third-party application service provider systems. This platform translates between different ecosystem IDs and policies, enabling seamless integration without requiring direct complex connections between each provider and the legacy system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The unified services platform provides universal interface capabilities that work across multiple different third-party ecosystems. It implements a standardized API interface that can accommodate various application service providers with different original interfaces, making the integration process uniform and manageable.

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

2Adaptability or versatility

If multiple different API interfaces from different application service provider systems are integrated, then service functionality is improved, but integration complexity and compatibility challenges increase

Engineering Contradiction:
Improveservice functionalityVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The unified services platform serves as a mediator that receives various different API interfaces from multiple application service provider systems and translates them into a standardized internal interface. This eliminates the need for the legacy telephone service to directly handle multiple incompatible APIs.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The integration architecture is segmented into distinct layers: the original diverse API interfaces from third-party providers, the unified services platform that handles translation and standardization, and the legacy telephone service that interacts with the standardized interface. This segmentation isolates complexity to the unified platform layer.

Inventive Principle:
Principle #1Segmentation

3Reliability

If multiple services from different providers are managed separately, then service independence is maintained, but service management complexity and billing complexity increase

Engineering Contradiction:
Improveservice independenceVSAvoidservice management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The unified services platform merges the management of multiple independent services into a single unified interface. It maintains service independence through modular architecture while providing consolidated service management, provisioning, and billing capabilities through the standardized API.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS10015321B2Event triggers for performing multiple services from a single action
Publication Date: 2018.07.03 ZILKR CLOUD TECH LLC
  • US10015321B2 patent drawing
  • US10015321B2 patent drawing
  • US10015321B2 patent drawing

AI summary

A method of provisioning a plurality of applications from different application developer systems to a network provider system comprises establishing a plurality of service accounts for a corresponding plurality of application service provider systems, receiving a plurality of API interfaces from the plurality of application service provider systems, integrating, by the processor system, each of the plurality of API interfaces with a unified services platform API interface, receiving a provider API interfaces for a network provider system, and integrating the provider API interface with the unified services platform API interface. The plurality of application service provider systems provide services for use in association with a telephone number of a subscriber of telecommunication services. At least two of the API interfaces are different, and at least one of the plurality of API interfaces from the plurality of application service provider systems is not compatible with the provider API interface.