Module Management Apparatus Dynamic Symbolic Name Namespace

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In module management infrastructures, collisions of definition information between bundles can lead to incorrect dependency relationships and unexpected execution results, particularly when bundles with the same version number and symbolic name are added, causing loading errors and incorrect references.

Innovation Solution

A module management apparatus and method that dynamically changes definition information, such as symbolic names, when loading bundles from folders to avoid collisions, ensuring correct reference relationships and dependency management without modifying the bundle bodies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a module management infrastructure enforces unique version number and symbolic name pairs for bundles, then definition information collision is avoided, but bundles with the same definition information cannot coexist and loading errors occur

Engineering Contradiction:

Improvedefinition information uniquenessVSAvoidbundle coexistence capability

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the uniqueness requirement by introducing a namespace concept that divides the definition space into multiple isolated domains. Bundles with the same version number and symbolic name can coexist by belonging to different namespaces, effectively segmenting the collision problem into separate manageable units.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent adds a namespace dimension to the existing definition information structure. Instead of relying solely on version number and symbolic name for uniqueness, a namespace identifier is introduced as an additional dimension, allowing bundles to be distinguished in a multi-dimensional space rather than a flat two-dimensional space.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

2Ease of operation

If bundles are loaded with automatic bundle ID assignment, then loading convenience is improved, but dependency relationships become incorrect and unexpected execution results occur

Engineering Contradiction:

Improvebundle loading convenienceVSAvoiddependency relationship accuracy

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent introduces a namespace as an intermediary layer between the bundle definition information and the bundle loading mechanism. This intermediary ensures that bundles are loaded with correct namespace context, maintaining accurate dependency relationships while preserving loading convenience.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent performs preliminary namespace assignment and definition information registration before bundle loading. By pre-establishing the namespace context and validating dependency relationships in advance, the system ensures correct bundle loading without requiring complex runtime resolution.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS9274759B2Module management apparatus, module management system and module management method

Publication Date: 2016.03.01 NEC CORP

AI summary

There is provided a module management apparatus, that coordinates, in a time of start of a module management infrastructure carrying out integrated management of: a bundle having a module formed by a program described by an object oriented language and definition information including an attribute of the module; and a module group including a plurality of pieces of the bundle, when the bundle is loaded from a folder, and, if the definition information collides between different bundles, a reference relationship of the bundle by changing the definition information dynamically.