Software Bus Port Analysis for Dynamic Component Reconstruction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional component models for embedded systems face challenges in adapting to dynamic reconstruction and multi-core computing environments due to resource limitations and inefficiencies in connecting components with varying attributes, leading to resource waste and performance deterioration.
Innovation Solution
A system and method utilizing a software bus with a port analyzing unit, execution attribute-determination unit, and port controller to differentiate between data transmission and function interface calling ports, enabling efficient thread management and parallel function execution through on-demand and on-load function calling attributes, thereby optimizing resource usage and adapting to computing environment changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a conventional component model is used to improve recycling property and design facilitation, then component reuse is enhanced, but the system cannot adapt to dynamic reconstruction and multi-core computing environments
Solution Approach 1:
The patent implements dynamic reconstruction capability by allowing components to be created, destroyed, and reconfigured at runtime based on connection attribute information. The runtime environment dynamically adjusts the computing environment to match required connection attributes, enabling the system to adapt to changing requirements without requiring complete software redesign.
Solution Approach 2:
The system changes execution parameters by selecting different runtime execution environments based on connection attribute information. When components need different connection attributes, the system dynamically switches between different RTE configurations, allowing a single component model to support multiple execution scenarios without increasing overall system complexity.
2Productivity
If a runtime execution environment is provided to enable component arrangement and execution, then component functionality is achieved, but resource waste occurs in embedded systems with severe resource limitations
Solution Approach 1:
The patent applies local quality by providing different runtime execution environments tailored to specific connection attribute requirements. Instead of providing a single heavy-duty RTE for all components, the system selects the appropriate lightweight RTE based on the specific needs of each component connection, reducing overall resource consumption while maintaining full functionality.
Solution Approach 2:
The system uses partial action by only loading and executing the necessary runtime execution environment features required for specific connection attributes. Rather than maintaining a complete RTE always ready, the system loads only the required partial functionality when needed, reducing resource waste during idle periods while maintaining full capability when required.
3Adaptability or versatility
If components are connected with varying connection attributes in embedded systems, then system functionality is enhanced, but resource overhead increases and performance deteriorates
Solution Approach 1:
The patent implements universality by creating a single component model that can support multiple connection attributes through dynamic runtime environment selection. The same component can be connected with different attributes (e.g., different data types, communication protocols) by dynamically switching the runtime environment, eliminating the need for multiple specialized component models and reducing resource overhead.
Data Source
AI summary
A method for inter-connection between components using a software bus, which may analyze whether a port in which at least one component is connected with each other is a data transmission port or a function interface calling port in accordance with an application of the port, determine an execution attribute of the port based on an analyzed result, and control the port in accordance with the execution attribute of the port. The function interface calling port may be divided into any one of a thread generation-connection port for each request using an attribute of an on-demand function calling port, or a recursive server connection port using an attribute of an on load function calling port in accordance with a type of the called port.