Integration Platform Unifying Multi-Network Service Channels

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Integrating computer-implemented service platforms into traditional networks is burdensome due to the need for multiple, complex integration architectures across different network infrastructures, which is time-consuming, costly, and often not feasible for legacy systems.

Innovation Solution

A transition layer at the front-end and a service layer at the back-end facilitate communication between channels and back-end service providers, providing a unified input format and enabling interaction with multiple back-end services without requiring separate integrations for each network infrastructure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If separate integration architectures are implemented for each network infrastructure, then compatibility with different networks is achieved, but integration complexity and costs increase significantly

Engineering Contradiction:
Improvenetwork compatibilityVSAvoidintegration architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an integration platform as an intermediary layer between service platforms and multiple network infrastructures. This platform provides standardized integration interfaces and protocols, allowing service platforms to communicate with different networks (telephony, messaging, social media, etc.) through a unified architecture rather than requiring separate integration implementations for each network type.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The integration platform is designed with universal functionality to handle multiple network types and communication protocols through a single standardized interface. It implements adaptors and connectors that can work with various network infrastructures (traditional telephony, IP-based networks, messaging networks, social media platforms) using the same core architecture, making the integration system multi-functional and network-agnostic.

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

2Adaptability or versatility

If multiple separate integration architectures are deployed for different networks, then comprehensive network coverage is achieved, but time and resources required for integration increase

Engineering Contradiction:
Improvenetwork coverageVSAvoidintegration time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The integration platform performs preliminary actions by pre-configuring standardized interfaces, protocols, and connection templates for multiple network types. Common integration patterns, authentication mechanisms, and data formatting rules are established in advance within the platform, so that when a new network integration is needed, the platform can quickly adapt using pre-built components rather than requiring从零 integration from scratch.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The integration architecture is segmented into modular components including network adaptors, protocol converters, and service connectors that can be independently configured and activated. This segmentation allows the system to selectively enable only the network integrations that are needed, rather than deploying and maintaining all possible network connections, thereby reducing integration time and resource requirements.

Inventive Principle:
Principle #1Segmentation

3Ease of operation

If traditional networks are integrated with service platforms, then service accessibility is improved, but integration costs and technical resource requirements increase

Engineering Contradiction:
Improveservice accessibilityVSAvoidintegration cost
Core Design Contradiction:
Ease of operationVSEase of manufacture

Solution Approach 1:

The integration platform enforces homogeneous data formats, communication protocols, and interface standards across all network integrations. By standardizing data structures (such as unified message formats, consistent authentication mechanisms, and standardized response protocols), the platform reduces the need for custom integration development for each network type, thereby lowering integration costs and technical resource requirements while maintaining broad service accessibility.

Inventive Principle:
Principle #33Homogeneity

Data Source

PatentEP3413540B1Integration platform for multi-network integration of service platforms
Publication Date: 2021.03.17 ACCENTURE GLOBAL SOLUTIONS LTD
  • EP3413540B1 patent drawingFigure 1
  • EP3413540B1 patent drawingFigure 2
  • EP3413540B1 patent drawingFigure 3

AI summary

Implementations are directed to integrating a computer-executed service platform with multiple channels, and include actions of providing a transition layer as an application executed on a client-side device, which receives input from a channel of the multiple channels, and providing a unified input that is in a unified format for processing by the service platform, receiving, by the service platform, the unified input, identifying, by the service platform, a set of actions based on the unified input, the set of actions including to be executed by one or more back-end services, providing a service layer including a plurality of bots, each bot interacting with a back-end service based on an action to receive at least one result from the respective back-end service, receiving result data including data describing the at least one result, and transmitting an output based on the result data through the transition layer of the client-side device.