EDI Service Autoscaling for On-Demand High-Availability Adapters

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing electronic information exchange platforms waste resources by deploying and deploying numerous unused managed services, which are not used, taking up significant service execution space, memory, and processing power, etc. The inefficiency of which existing platforms in the network environment, and memory, and memory resources, particularly hardware resources, particularly hardware resources, particularly hardware resources, particularly hardware resources, needed in providing managed services to disparate networked computer systems through an electronic information exchange platform.

Innovation Solution

Implementing an electronic data interchange service auto-scaler that scales up only when needed, deploying a minimum of two computing units for high availability, and generating an alert for operator action to ensure the managed service is included in subsequent deployments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If managed services are deployed in advance on the electronic information exchange platform, then service availability and response time are improved, but hardware resource waste increases due to deployment of unused services

Engineering Contradiction:
Improveservice availabilityVSAvoidhardware resource waste
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system dynamically adjusts service deployment based on real-time demand detection. When a service is detected as needed, the auto-scaler automatically scales up the service deployment. This dynamic approach allows the system to maintain high availability for needed services while avoiding resource waste from pre-deploying unused services.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system performs preliminary detection of service needs through itinerary analysis before full service deployment. The orchestration engine detects when a service is required by analyzing the itinerary, and only then triggers the auto-scaler to deploy the service. This preliminary detection action prevents unnecessary deployment while ensuring services are ready when needed.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the auto-scaler deploys a minimum of two computing units for each service, then high availability is achieved, but resource consumption increases

Engineering Contradiction:
Improvehigh availabilityVSAvoidcomputing unit quantity
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system changes the deployment parameter from zero or one computing unit to a minimum of two computing units only when service need is detected. The auto-scaler adjusts the quantity parameter dynamically based on actual service requirements, ensuring high availability (two units) only for services that are truly needed, rather than uniformly deploying two units for all possible services.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system uses self-service mechanisms where the orchestration engine automatically detects service needs and triggers appropriate scaling actions without manual intervention. The auto-scaler monitors service usage patterns and automatically adjusts computing unit quantities, enabling the system to maintain high availability only where necessary while minimizing overall resource consumption.

Inventive Principle:
Principle #25Self-service

3Speed

If all managed services are pre-deployed to ensure immediate service delivery, then service delivery speed is improved, but system complexity and resource management burden increase

Engineering Contradiction:
Improveservice delivery speedVSAvoidsystem complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system transitions from static pre-deployment of all services to dynamic on-demand deployment. The auto-scaler continuously monitors for service needs and automatically deploys services when detected, maintaining fast service delivery for needed services while reducing overall system complexity by eliminating deployment of unused services.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms where the orchestration engine monitors itinerary execution and detects when services are needed. This feedback loop triggers automatic service deployment through the auto-scaler, ensuring services are delivered quickly when needed while avoiding the complexity of pre-deploying all possible services. The feedback-driven approach simplifies resource management compared to universal pre-deployment.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250348367A1Electronic data interchange service autoscaler for electronic information exchange platform
Publication Date: 2025.11.13 OPEN TEXT CORP
  • US20250348367A1 patent drawing
  • US20250348367A1 patent drawing
  • US20250348367A1 patent drawing

AI summary

An orchestration engine receives an itinerary requiring a managed service provided by an electronic information exchange platform to process a document. The itinerary defines a process model specific to a document type of the document. The orchestration engine is operable to determine whether an adapter for the managed service is currently in use. Responsive to not finding the adapter for the managed service currently in use, the orchestration engine communicates or otherwise indicates to an auto-scaler, a need for the adapter for the managed service. Responsive to the need for the adapter, the auto-scaler automatically scales up deployment of the adapter to a minimum of two computing units for high availability of the managed service. Once the adapter is ready, the managed service operates on the document per the itinerary.