Bridge Messaging Middleware for Multi-Protocol Android PANs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing message-oriented middleware systems are designed for TCP-IP networks and lack the ability to efficiently communicate and share data across multiple applications in an Android OS environment, particularly in a multi-protocol soldier personal area network (PAN).
Innovation Solution
The development of a middleware messaging system, referred to as the Bridge system, which operates on a multi-protocol PAN and converts messages between different protocols, enabling communication between applications and devices regardless of the network protocol used. This system includes bridge service modules that package and communicate information in a generic format, independent of the specific device or devices that generated the information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If message-oriented middleware is designed for TCP-IP networks, then network communication is standardized, but it cannot efficiently communicate and share data across multiple applications in Android OS environment and multi-protocol PAN
Solution Approach 1:
The patent introduces a Bridge system as an intermediary layer between applications and the underlying multi-protocol network infrastructure. The Bridge system includes bridge service modules that translate and route messages between different protocols (USB, ISW, Bluetooth, Wi-Fi) and applications, allowing standardized communication without requiring each application to handle protocol complexity directly
Solution Approach 2:
The Bridge system is designed to operate across multiple communication protocols simultaneously, providing universal message routing capabilities. The system can select appropriate networks for message distribution based on availability, preferred networks, and network load, making a single system serve multiple protocol functions
2Ease of manufacture
If solutions operate at hardware and electronics layer, then device-specific communication is optimized, but specific knowledge of device details is required and device-specific solutions are needed
Solution Approach 1:
The Bridge system operates at the application layer as an intermediary, abstracting away hardware and electronics layer details. This allows generic solutions that work across multiple devices without requiring specific knowledge of device implementation details, while still enabling efficient communication
Solution Approach 2:
The system separates communication functionality into distinct layers: the Bridge service modules handle protocol translation and routing at the application layer, while the underlying hardware layer remains unchanged. This segmentation allows independent optimization at each layer without requiring changes throughout the entire system
3Adaptability or versatility
If multiple network protocols are available for message distribution, then communication flexibility is improved, but protocol selection and routing complexity increases
Solution Approach 1:
The Bridge system acts as an intelligent mediator that automatically selects appropriate networks for message distribution. It considers factors such as network availability, preferred networks, and network load to make routing decisions, eliminating the need for manual protocol selection and simplifying operation
Solution Approach 2:
The routing behavior of the Bridge system is dynamic rather than static. It can adapt its message distribution strategy based on current network conditions, selecting from USB, ISW, Bluetooth, or Wi-Fi protocols as appropriate, and can change routing decisions in real-time based on network availability and load
Data Source
AI summary
A bridge system includes messaging middleware that is configured to operate on a multi-protocol soldier personal area network (PAN) and to enable sharing of data with multiple applications in an Android OS. The bridge system is implemented on smart and semi-smart multi-protocol hubs and is used to support sharing of live power data between PAN components. The data is displayed to a user on a user interface and is used by components of the system to model and predict power requirements and power usage of the PAN components.