Scalable Language Infrastructure for ESL Tools

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional electronic system level (ESL) tools face challenges in scalability and flexibility, requiring multiple language infrastructures to support new clients and design flows, leading to duplicative efforts and synchronization issues, as they are not well-suited for rapidly evolving design environments.

Innovation Solution

A scalable language infrastructure that encapsulates knowledge about types and functions in intelligent components, acting as a common backbone, allowing clients to interact with these components without maintaining knowledge within the infrastructure, enabling easy addition of new flows and types without duplicating infrastructure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a conventional ESL tool is tailored with hard-coded requirements for specific clients, then it can meet the requirements of its initial clients, but it becomes difficult to extend the tool to support new clients and requirements

Engineering Contradiction:
Improveability to support new clientsVSAvoidnumber of language infrastructures
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal language infrastructure that can serve multiple clients and requirements through a common framework. The type system is designed to be extensible and adaptable to different clients (C++ code generation, HDL generation, etc.) without requiring separate infrastructures, thus achieving multi-functionality while reducing overall system complexity

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent segments the language infrastructure into modular components, particularly the type system that can be independently configured for different clients. This segmentation allows the infrastructure to be extended for new clients by adding or modifying type definitions rather than creating entirely new infrastructures

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If multiple language infrastructures are created to support different clients, then each client's specific requirements can be met, but duplicative effort and resource waste occur

Engineering Contradiction:
Improvesupport for different design flowsVSAvoidduplicative development effort
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent implements a single universal language infrastructure that handles multiple design flows (C++ code generation, HDL generation, etc.) through a common type system and evaluation engine, eliminating the need to create separate infrastructures for each client and thus reducing duplicative development effort

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent merges previously separate language infrastructures into a single unified infrastructure that serves multiple clients. The type system combines functionality for different clients into one coherent framework, allowing shared code and data structures to be maintained in a single location rather than duplicated across multiple infrastructures

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If separate language infrastructures are maintained for different clients, then each infrastructure can be optimized for its specific client, but synchronization difficulties arise among multiple copies of type information

Engineering Contradiction:
Improveclient-specific optimizationVSAvoidsynchronization of type information
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent provides a single source of truth for type information that serves multiple clients simultaneously. The universal type system allows all clients to access and utilize the same type definitions, ensuring automatic synchronization and eliminating the information loss that occurs when maintaining separate copies in multiple infrastructures

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS8856731B2Scalable language infrastructure for electronic system level tools
Publication Date: 2014.10.07 MIPS HLDG INC
  • US8856731B2 patent drawing
  • US8856731B2 patent drawing
  • US8856731B2 patent drawing

AI summary

Systems and methods of scalable language infrastructure for electronic system level tools. In accordance with embodiments of the present invention, knowledge about types, functions and the like is encapsulated in a plurality of intelligent components called active component extension modules that are external to the infrastructure. The infrastructure implements a communication mechanism between the clients and these intelligent components, and acts as a common backbone. The infrastructure itself does not maintain any knowledge about any client, types, functions, etc. In accordance with a method embodiment of the present invention, a request is received from a client of a language infrastructure. The request is forwarded from the language infrastructure to an active component extension module. The active component extension module performs a service responsive to the request.