Custom Inter-ORB Protocol Header Optimization for Embedded Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
CORBA GIOP messaging protocols are inefficient and cumbersome for embedded systems due to large message headers, which result in inefficiencies and assurance issues, and existing optimizations like nORB, GIOPLite, and CAN/EIOP do not retain all CORBA features while reducing header size effectively.
Innovation Solution
A custom Inter-ORB Protocol (custom-IOP) that supports only Request and Reply message types with reduced header sizes, maintaining all CORBA features, and includes IDL compile directives for minimal or full custom-IOP definitions, optimizing performance and information assurance by reducing data transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If standard CORBA GIOP protocol is used for communication, then all CORBA features are supported, but message header size becomes large causing inefficiency and assurance issues in embedded systems
Solution Approach 1:
The patent extracts and removes unnecessary fields from the GIOP message header structure, keeping only the essential fields required for embedded system communication. This selective extraction reduces the header size from the standard GIOP format while maintaining support for critical CORBA features, directly resolving the contradiction between reducing data quantity and preserving reliability.
Solution Approach 2:
The patent applies local quality by making the message header structure adaptive to specific embedded system requirements. Different header formats can be selected based on the communication needs, allowing optimization for particular embedded scenarios while maintaining overall CORBA feature support, thus balancing header size reduction with reliability preservation.
2Productivity
If message header size is reduced for efficiency, then performance improves, but existing optimizations like nORB, GIOPLite, and CAN/EIOP fail to retain all CORBA features
Solution Approach 1:
The patent creates a universal message header structure that can support multiple CORBA features within embedded systems. The custom-IOP protocol design allows a single optimized header format to handle various CORBA operations and features that previous solutions could not accommodate, achieving both efficiency and versatility simultaneously.
Solution Approach 2:
The patent changes key parameters of the message header structure, such as field sizes, data types, and organization, to optimize for embedded systems while preserving CORBA feature support. By carefully adjusting these parameters, the protocol achieves smaller header sizes without sacrificing the adaptability needed to support all CORBA features.
3Loss of time
If full GIOP protocol is used, then complete CORBA functionality is available, but latency increases due to larger data transmission
Solution Approach 1:
The patent extracts and removes redundant and optional fields from the GIOP protocol structure, keeping only the essential elements needed for embedded system communication. This extraction reduces the overall data transmission size, directly decreasing communication latency while maintaining the protocol's ability to handle complete CORBA functionality when needed.
Data Source
AI summary
A non-transient computer-readable storage medium that stores computer program code is provided. When this code is loaded into a computer system and executed thereon, it causes the computer to compile an interface definition language (IDL) configured to provide a custom inter-orb protocol (custom IOP), configure a message header for a message in accordance with to a specification in the IDL for at least a custom-IOP message header, and define a custom-IOP message header to replace the corresponding Common Object Resource Broker Architecture (CORBA) General Inter-Orb (GIOP) message header, wherein the custom-IOP message header requires fewer bits overall than the corresponding GIOP message header by changing or eliminating at least a portion of the fields in the corresponding GIOP message header.