Type-Independent Code Segmentation for Multi-Type Execution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing computing systems require multiple versions of code to be generated and managed for different data types and routine types, leading to inefficiencies in code modification and management across various devices.

Innovation Solution

The development of type-independent code that can be generated from and transformed into type-specific code, allowing a single version of code to be executed across different data types and routine types by separating and managing data type and routine type information separately.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple versions of code are generated for different data types and routine types, then code execution accuracy for specific device types is improved, but code management complexity and modification difficulty increase

Engineering Contradiction:
Improvecode execution accuracyVSAvoidcode management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments code into type-independent portions and type-specific portions. Type-independent code contains device-agnostic logic that can be executed on any device, while type-specific code contains device-specific implementations. This segmentation allows the system to maintain multiple code versions for different device types without managing complete separate codebases, reducing management complexity while preserving execution accuracy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal code framework where type-independent code can serve multiple device types simultaneously. This universal portion handles common functionality that doesn't depend on specific data types or routine types, allowing one version of code to be deployed across diverse devices while type-specific portions handle device variations.

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

2Productivity

If multiple versions of code are maintained for different devices, then device-specific optimization is improved, but time required for code modification and updates increases

Engineering Contradiction:
Improvedevice-specific optimizationVSAvoidcode modification time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

By segmenting code into type-independent and type-specific portions, the patent enables independent modification of each segment. When updates are needed, developers can modify only the affected portion rather than entire code versions, significantly reducing modification time while maintaining device-specific optimizations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary action by pre-identifying and separating type-specific elements during code development. This upfront segmentation creates a structured framework that anticipates future modification needs, making subsequent updates faster and more efficient compared to managing monolithic code versions.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If type-independent code is used across different devices, then code management efficiency is improved, but adaptability to specific data types and routine types may be reduced

Engineering Contradiction:
Improvecode management efficiencyVSAvoidadaptability to data types
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent segments code functionality into type-independent core logic and type-specific adaptation layers. This segmentation allows efficient management of the common codebase while maintaining full adaptability to different data types and routine types through the type-specific portions that can be selectively applied.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces type-specific portions as intermediaries between the type-independent code and device-specific implementations. These intermediary layers handle data type conversions and routine type adaptations, allowing the core type-independent code to remain efficient and manageable while still achieving full adaptability to various device types.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9244667B2Mechanism for transforming between type-independent and type-specific code
Publication Date: 2016.01.26 MATHWORKS INC
  • US9244667B2 patent drawing
  • US9244667B2 patent drawing
  • US9244667B2 patent drawing

AI summary

A system obtains first code that includes one or more lines of code, the lines of code including first information associated with one or more data types or one or more routine types. The system removes the first information from the lines of code; and generates one or more instructions that, when executed, enable the system to obtain the first information or second information. The second information is associated with at least one data type that is different than the one or more data types or at least one routine type that is different than the one or more routine types. The system modifies the lines of code based on the one or more instructions; generates second code based on the first code and the modified lines of code; and outputs the second code.