API Source Code Conversion to Policy Documents

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Enterprise software deployed in production environments often requires separate runtime infrastructures for each API, leading to increased resource overhead, infrastructure costs, and complexity in governance and vulnerability management.

Innovation Solution

A code conversion platform that converts source code from API format to a lightweight XML-based policy document, allowing deployment in a shared runtime environment, reducing infrastructure footprint and simplifying management and vulnerability remediation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate runtime infrastructures are used for each API, then API execution reliability is improved, but infrastructure complexity and resource overhead increase

Engineering Contradiction:

ImproveAPI execution reliabilityVSAvoidinfrastructure complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges multiple separate runtime infrastructures into a single shared runtime infrastructure. Multiple APIs that previously required dedicated runtime environments are now consolidated to execute together in one shared environment, reducing overall infrastructure complexity while maintaining execution reliability through standardized isolation mechanisms.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The shared runtime infrastructure is designed to be universal, capable of executing multiple different APIs simultaneously. This multi-functional platform can handle various API types and workloads within a single infrastructure, eliminating the need for separate dedicated runtime environments for each API.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Stability of the object's composition

If separate runtime infrastructures are used for each API, then API isolation is improved, but resource overhead and infrastructure costs increase

Engineering Contradiction:

ImproveAPI isolationVSAvoidresource overhead

Core Design Contradiction:

Stability of the object's compositionVSQuantity of substance

Solution Approach 1:

Multiple API execution environments are merged into a single shared runtime infrastructure, reducing the total quantity of runtime resources required. This consolidation maintains necessary isolation between APIs while eliminating redundant resource allocation that would occur with separate dedicated infrastructures.

Inventive Principle:

Principle #5Merging (Combining)

3Adaptability or versatility

If source code is converted to policy documents, then deployment flexibility is improved, but conversion complexity increases

Engineering Contradiction:

Improvedeployment flexibilityVSAvoidconversion complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The code conversion platform serves as an intermediary tool that automatically transforms source code into executable policy documents. This intermediary system handles the complexity of conversion, allowing users to benefit from deployment flexibility without manually managing the transformation process.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The manual process of converting source code to policy documents is replaced with an automated code conversion platform. This substitution of mechanical manual work with automated digital processing reduces conversion complexity and enables flexible deployment through standardized policy document generation.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

4Quantity of substance

If multiple APIs execute on shared runtime infrastructure, then infrastructure costs are reduced, but governance and vulnerability management complexity increases

Engineering Contradiction:

Improveinfrastructure costsVSAvoidgovernance complexity

Core Design Contradiction:

Quantity of substanceVSDevice complexity

Solution Approach 1:

The shared runtime infrastructure provides self-service capabilities for governance and vulnerability management through standardized policies and automated enforcement mechanisms. The system automatically applies security policies and manages vulnerabilities across multiple APIs without requiring manual intervention, reducing governance complexity despite the shared environment.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS11893367B2Source code conversion from application program interface to policy document

Publication Date: 2024.02.06 CAPITAL ONE SERVICES LLC

AI summary

In some implementations, a device may receive source code associated with an application program interface (API) configured to execute on a dedicated runtime infrastructure. The device may generate an executable policy document including machine-readable text based on one or more code sections in the source code that implement one or more function calls associated with one or more function call types. The device may invoke a validation utility to cross-check the executable policy document against a design document associated with the API. The device may deploy the executable policy document in a common runtime environment that includes a shared runtime infrastructure to support multiple executable policy documents based on the validation utility indicating that the executable policy document satisfies functional requirements described in the design document associated with the API.