Expandable Text Messaging Protocol for Two-Way Radio Transceivers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing text messaging service protocols rely on server-based systems, making them complex and inefficient for mobile environments, particularly in low data rate communication links, as they require infrastructure for device-to-device communication and are bulky, leading to increased data transmission overhead.
Innovation Solution
An expandable text messaging service protocol that allows direct communication between devices without a server, using a simplified protocol stack with an expandable header structure to minimize data transmission and optimize message routing, enabling device-to-device communication using two-way radio transceivers as modems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If server-based protocols are used for text messaging, then message delivery reliability is improved, but device complexity and data transmission overhead increase
Solution Approach 1:
The patent extracts the essential messaging functions from complex server-based protocols and implements a simplified device-to-device protocol. The expandable text messaging service protocol removes unnecessary server infrastructure dependencies while retaining core message delivery reliability through direct peer-to-peer communication between radio transceivers.
Solution Approach 2:
The protocol is segmented into expandable message blocks that can be transmitted in smaller units over low data rate channels. This segmentation allows reliable message delivery through incremental transmission while reducing the complexity of handling large protocol overhead in single transmissions.
2Adaptability or versatility
If traditional messaging protocols are used, then comprehensive message features are achieved, but data transmission efficiency deteriorates in low data rate environments
Solution Approach 1:
The protocol implements dynamic message structure with expandable fields that adapt to the available data rate and channel conditions. Message blocks can be expanded or compressed based on network capabilities, allowing comprehensive features when bandwidth permits while maintaining efficiency in constrained low data rate environments.
Solution Approach 2:
The protocol changes transmission parameters dynamically by adjusting message block size, expansion flags, and transmission timing based on channel quality. This allows the system to maintain feature completeness while optimizing data transmission efficiency for low data rate radio channels.
3Loss of information
If bulky protocol fields are used, then comprehensive control information is transmitted, but transmission overhead increases
Solution Approach 1:
The protocol uses nested message blocks where control information is embedded within compact headers and optional expansion fields. Essential control information is transmitted in minimal form in the base protocol, with additional control details nested in expandable sections that are only transmitted when needed, reducing overall transmission volume while maintaining information completeness.
4Ease of operation
If server infrastructure is required, then message routing is simplified, but system dependency and complexity increase
Solution Approach 1:
The protocol implements self-service routing where each radio transceiver independently determines message routing based on embedded destination identifiers in the message blocks. Devices autonomously route messages directly to intended recipients without requiring external server infrastructure, maintaining routing simplicity while eliminating system dependency.
Data Source
AI summary
An expandable text messaging service protocol for use with a two-way radio transceiver includes an extension bit field for creating an expandable header for controlling the overall size of data packets used for communicating message traffic. The protocol further includes a control bit field for designing the message as a control message or user message and a protocol data unit (PDU) type field for identifying the message type. A payload field may further be used for carrying message content.