Edge Server AI Controller for Third-Party Software Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large enterprise organizations face challenges in managing and integrating third-party software into their complex computing environments due to regulatory and security testing requirements, latency issues, and the inability to log performance or detect errors in externally hosted third-party software.

Innovation Solution

Deploying an edge server within a secure internal network to manage and deliver third-party software, utilizing an AI content controller to transpile and test third-party content, and configuring it to conform to internal security and operational protocols, allowing integration with software development automation tools and version control systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If third-party software is hosted on third-party networks, then ease of operation is improved, but reliability and security compliance deteriorate

Engineering Contradiction:
Improveease of operationVSAvoidreliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces an intermediary system between the third-party software vendor and the enterprise organization's CDN. This intermediary hosts the third-party software in a controlled environment that enables both easy deployment (maintaining ease of operation) and enterprise-level security testing and performance logging (improving reliability). The intermediary acts as a buffer that reconciles the conflicting requirements of vendor convenience and enterprise security control.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If third-party software is externally hosted, then device complexity is reduced, but measurement precision and error detection deteriorate

Engineering Contradiction:
Improvedevice complexityVSAvoiderror detection
Core Design Contradiction:
Device complexityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements a feedback mechanism where the intermediary system continuously monitors and logs the performance and errors of third-party software. This feedback loop provides the enterprise organization with visibility into software execution issues, enabling proactive error detection and resolution while maintaining the simplicity of external hosting.

Inventive Principle:
Principle #23Feedback

3Reliability

If third-party software is integrated into enterprise development lifecycle, then reliability is improved, but device complexity increases

Engineering Contradiction:
ImprovereliabilityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by requiring third-party software to be pre-tested and validated in the intermediary environment before being deployed to the enterprise's CDN. This advance testing ensures reliability requirements are met while avoiding the complexity of integrating third-party software into the enterprise's ongoing development lifecycle. The security and performance testing are performed beforehand, eliminating the need for continuous complex integration processes.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12015502B2Artificial intelligence integration of third-party software into large-scale digital platforms
Publication Date: 2024.06.18 BANK OF AMERICA CORP
  • US12015502B2 patent drawing
  • US12015502B2 patent drawing
  • US12015502B2 patent drawing

AI summary

Aspects of this disclosure relate to using artificial intelligence (“AI”) to control integration of software developed by a third-party into an enterprise computing environment subject to more rigorous regulatory and security testing than typically provided by the third-party. AI software development automation tools will deploy third-party scripts to edge servers. Deploying to edge servers allows for integration of the third-party tags into testing environment pipelines. Local storage associated with third-party tags will be at a top-level domain, allowing third-party software tags to be treated as first party without the reputational and technical risks of cross-site storage.