Service Delivery Platform Protocol Translation for Legacy Network Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods fail to enable seamless interaction and coordination between legacy and next-generation networks, limiting the integration of legacy applications with new networks and protocols, which is costly and time-consuming, hindering the adoption of next-generation networks.

Innovation Solution

A Service Delivery Platform (SDP) is used to translate communications between different protocols, identify additional service layer components, and dispatch translated communications, abstracting underlying network technologies to facilitate interactions between legacy and next-generation networks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If legacy applications are modified to operate on next generation networks, then compatibility with new networks is improved, but cost and time consumption increase

Engineering Contradiction:
Improvecompatibility with next generation networksVSAvoidcost and time of modification
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent introduces a Service Layer as an intermediary between legacy applications and next generation networks. This Service Layer includes components such as a Service Layer Gateway and Service Components that translate and adapt communications without requiring changes to the legacy applications themselves, thereby achieving compatibility while avoiding modification costs and time consumption.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If legacy applications are modified to interact with new networks, then integration capability is improved, but complexity of implementation increases

Engineering Contradiction:
Improveintegration capabilityVSAvoidcomplexity of implementation
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the integration functionality into distinct components: the Service Layer Gateway handles protocol translation and message routing, while separate Service Components provide specific services. This segmentation allows legacy applications to interact with the standardized Service Layer interface without dealing with the complexity of multiple network protocols and integration details.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If protocol translation is implemented, then interoperability between networks is improved, but service coordination complexity increases

Engineering Contradiction:
ImproveinteroperabilityVSAvoidservice coordination complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The Service Layer Gateway is designed as a universal component that handles multiple functions including protocol translation, message routing, and service coordination through a standardized interface. This multi-functionality reduces the need for separate coordination mechanisms for each protocol translation task, thereby managing complexity while maintaining interoperability.

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

Data Source

PatentUS8990413B2Service level cross network coordinated interaction
Publication Date: 2015.03.24 ORACLE INT CORP
  • US8990413B2 patent drawing
  • US8990413B2 patent drawing
  • US8990413B2 patent drawing

AI summary

Embodiments of the invention provide systems and methods for orchestrating or coordinating interactions between different types of networks such as a legacy network and a next generation network. According to one embodiment, a method for coordinating interactions between different types of networks can comprise receiving at a service layer component a communication in a communication session from a first communication network. The communication can be in a first protocol. The communication can be translated from the first protocol to a second protocol with the service layer component, wherein the first protocol is different from the second protocol. One or more additional service layer components for providing at least one service in the communication session can be identified with an application dispatcher of the service layer component. The translated communication can be dispatched to the one or more additional service layer components from the application dispatcher.