Linguistic Interface Containment via Unique Variant Translation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current techniques for controlling computing resources are inadequate as they rely on validation checks, shared secrets, or finite name spaces, failing to limit system usage effectively when software computes or obtains new commands to execute.

Innovation Solution

A method and system that modify software to use a unique variant of a linguistic interface, with an interceptor pre-processing invocations to re-translate requests, limiting usage to only pre-translated software and preventing execution of arbitrary inputs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If standard linguistic interfaces are used, then software can execute arbitrary commands and programs, but system usage cannot be limited to specific software

Engineering Contradiction:
Improvesoftware execution capabilityVSAvoidsystem usage control
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an intermediary translation layer between the software and the linguistic interface. The software is translated to use a unique variant of the linguistic interface, and an interceptor component pre-processes invocations to re-translate them to the standard language. This intermediary mechanism enables both software execution capability and system usage control by ensuring only pre-translated software can successfully communicate with the system.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If encryption-based techniques are used, then pre-execution checks can be performed, but system usage cannot be limited once the check succeeds

Engineering Contradiction:
Improvepre-execution validationVSAvoidcontinuous usage control
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent applies preliminary action by translating software to use a unique variant of the linguistic interface before execution. This translation is performed in advance, and the translated software must continuously use this unique interface variant. The interceptor pre-processes all invocations, ensuring that even during execution, only the pre-translated software can successfully interact with the system, providing continuous usage control rather than just pre-execution validation.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If virtualization techniques are used, then name spaces can be variantized, but only for fixed sets of existing system resources

Engineering Contradiction:
Improvename space variationVSAvoidinterface containment
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies parameter changes by modifying the linguistic interface parameters themselves. Instead of virtualizing fixed name spaces for existing resources, the system creates a unique variant of the linguistic interface by changing its language parameters. The translator modifies software to use this unique variant, and the interceptor re-translates invocations. This approach contains the interface at the linguistic level rather than requiring complex virtualization of resource name spaces, reducing device complexity while maintaining adaptability.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS7840968B1Method and system for containment of usage of language interfaces
Publication Date: 2010.11.23 MCAFEE LLC
  • US7840968B1 patent drawing
  • US7840968B1 patent drawing
  • US7840968B1 patent drawing

AI summary

Client software is modified by a translator to use unique variant of linguistic interface of a service. An interceptor pre-processes subsequent client service requests from translated unique linguistic interface to standard linguistic interface implemented by service. Usage of linguistic interfaces of service is contained, rendering service incapable of executing arbitrary input, even if such input is crafted specifically for the service interface.