User-Defined .NET Class Creation in Distributed Control Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing operational control systems for managing distributed computing systems have limited flexibility in defining classes, as they rely on predefined templates that simulate new classes rather than creating real ones, leading to behavioral differences and reduced capabilities.

Innovation Solution

A method and apparatus that allow users to create user-defined .NET classes within distributed computing systems by defining properties and specifications, using a module to create real .NET classes that behave like predefined classes, providing a transparent interface and extending the feature set beyond initial capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If predefined templates are used to manage classes in operational control systems, then system stability and ease of implementation are improved, but class definition flexibility and behavioral consistency deteriorate

Engineering Contradiction:
Improveease of implementationVSAvoidclass definition flexibility
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The system transitions from static predefined templates to dynamic user-defined classes. Users can now create custom managed classes with specific properties and behaviors tailored to their needs, while the system dynamically generates the appropriate .NET class implementations. This allows the system to adapt to diverse management requirements without sacrificing implementation ease.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The invention changes the parameters of class definition from fixed template-based specifications to flexible user-defined properties. Users can specify custom property names, data types, and behaviors for each managed class, transforming the rigid parameter structure into an adaptable one while maintaining system stability through consistent underlying mechanisms.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If simulated classes are used instead of real .NET classes, then system compatibility is improved, but behavioral consistency and capability deteriorate

Engineering Contradiction:
Improvesystem compatibilityVSAvoidbehavioral consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system creates actual .NET class copies that replicate the functionality and behavior of predefined classes. Instead of simulating class behavior through software abstractions, the invention generates real .NET classes that inherit and implement the same interfaces and methods, ensuring both compatibility with existing systems and consistent, reliable behavior.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The invented mechanism provides universal class creation capability that works across different .NET platforms and environments. The same user-defined class specification can be instantiated multiple times with consistent behavior, and the generated classes can serve multiple purposes including inheritance, polymorphism, and interface implementation, enhancing both compatibility and reliability.

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

3Device complexity

If a limited template for class definition is provided, then implementation simplicity is improved, but feature set and functionality deteriorate

Engineering Contradiction:
Improveimplementation simplicityVSAvoidfeature set
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The class definition process is segmented into manageable components: users define properties with specific attributes (name, type, description), specify inheritance relationships, and set behavioral parameters. This segmentation allows complex class definitions to be broken down into simple, structured steps, maintaining implementation simplicity while enabling extensive customization and feature expansion.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8516438B2Method and apparatus for user-defined managed objects
Publication Date: 2013.08.20 UNISYS CORP
  • US8516438B2 patent drawing
  • US8516438B2 patent drawing
  • US8516438B2 patent drawing

AI summary

An apparatus creates a user-defined .NET class within an operational control environment of distributed computing systems. The apparatus includes a define module that allows a user to create a new class and define properties for the new class in a specification. After the user creates the new class, the define module creates a .NET class based on the specification. In addition, a method for creating a user-defined .NET class within an operational control environment of distributed computing systems includes receiving a user-defined class; receiving user-defined properties for the user-defined class; and creating a .NET class based on the user-defined class and properties.