Interoperability Software for .NET and COM Interface Translation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Standard translation tools fail to provide suitable interface definitions for interoperability between standard .NET and COM software architectures and proprietary variants used in large businesses, such as financial institutions, leading to restricted access to legacy COM component libraries in proprietary .NET architectures.

Innovation Solution

An interoperability method and software that receives interface definitions from one software architecture, generates and maps them to a format compatible with another software architecture, using intermediate interface definitions and wrappers like runtime callable wrappers (RCW) and COM callable wrappers (CCW), enabling seamless access to standard libraries across different proprietary architectures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If standard translation tools (TLBIMP) are used to generate interface definitions from COM components, then interoperability between standard .NET and COM architectures is achieved, but the generated interface definitions are unsuitable for proprietary .NET architectures used by financial institutions

Engineering Contradiction:

Improveinterface definition compatibilityVSAvoidinteroperability functionality

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an intermediary translation tool that sits between standard COM components and proprietary .NET architectures. This intermediary generates customized interface definitions that are compatible with both standard COM and proprietary .NET architectures, resolving the contradiction by adapting the interface definitions to work with the specific proprietary architecture while maintaining the underlying COM functionality.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent modifies the interface definition parameters generated by standard translation tools to match the specific requirements of proprietary .NET architectures. By changing the parameter structure, data types, and interface conventions to align with proprietary architecture specifications, the tool enables reliable interoperability while maintaining compatibility with the target architecture.

Inventive Principle:

Principle #35Parameter changes

2Reliability

If standard translation tools generate interface definitions with all standard COM fields and data, then complete COM functionality is preserved, but the interface definitions become confusing and difficult to understand for users with detailed knowledge of proprietary architecture

Engineering Contradiction:

ImproveCOM functionality completenessVSAvoidinterface definition understandability

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent extracts and removes unnecessary standard COM fields and data from the generated interface definitions, keeping only those elements that are relevant to proprietary architecture users. This extraction process eliminates confusing standard COM-specific fields while preserving the essential functionality, making the interface definitions easier to understand for users familiar with proprietary architectures.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies local quality by customizing different portions of the interface definitions according to the specific needs of proprietary architecture users. Rather than uniformly translating all COM fields, the tool selectively adapts only the relevant portions while maintaining standard COM compatibility, creating interface definitions that are locally optimized for both completeness and understandability.

Inventive Principle:

Principle #3Local quality

3Adaptability or versatility

If proprietary variants of .NET and COM architectures are used in large businesses, then specific business requirements are met, but access to legacy COM component libraries is restricted

Engineering Contradiction:

Improvebusiness architecture customizationVSAvoidaccess to legacy components

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent introduces an intermediary translation capability that enables proprietary .NET architectures to access legacy COM component libraries. This intermediary layer translates between the proprietary architecture interface definitions and standard COM interfaces, allowing businesses to maintain their customized proprietary architectures while still accessing and utilizing legacy COM components without restriction.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS8484627B2Interoperability method and software

Publication Date: 2013.07.09 NCR ATLEOS CORP

AI summary

Interoperability software modules comprise an architected .NET layer, an architected interpreter, an automatic interpreter and a library of COM objects. The architected interpreter where they are mapped to intermediate .NET interfaces compatible with the automatic interpreter by means of a Runtime Callable Wrapper (RCW). The architected interpreter also comprises an architected COM Callable Wrapper (CCW) that maps the intermediate COM interfaces into architected interfaces.