Intermediate Module for Mobile Peripheral Protocol Translation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The integration of peripheral devices with mobile applications is complex and costly due to device-specific communication protocols, requiring extensive testing and customization, which hinders portability across platforms and increases development and maintenance costs.
Innovation Solution
An intermediate module is introduced that communicates with mobile peripherals using their specific protocols and with mobile applications using standardized protocols like HTTP and TCP/IP, allowing for socket-based communication and simplifying the interaction between peripherals and applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If peripheral devices use device-specific communication protocols, then the peripheral devices can be integrated into mobile applications, but the integration becomes complex and costly requiring extensive testing and customization
Solution Approach 1:
The patent introduces an intermediate module as a mediator between the peripheral device and the mobile application. This module translates device-specific communication protocols into a standardized protocol, allowing the application to interact with peripherals through a uniform interface without needing to understand the underlying device-specific protocols. The intermediate module handles protocol conversion, thus reducing the complexity of integration while maintaining reliable peripheral device communication.
2Adaptability or versatility
If a third-party consultant is engaged to integrate peripheral device functionality, then the mobile application can support multiple peripheral devices, but the implementation process becomes slower and more complicated
Solution Approach 1:
The patent implements a universal intermediate module that can handle multiple peripheral devices through a single standardized interface. Instead of requiring separate integration solutions for each peripheral device type, the system uses one intermediate module that provides multi-functional support for various devices. This approach enables the mobile application to support multiple peripheral devices without requiring extensive customization or specialized consulting for each device type, thereby reducing implementation time while maintaining versatility.
3Productivity
If peripheral device functionality is compiled together with the mobile application, then the integration is tight and efficient, but the application cannot be easily extended to another platform
Solution Approach 1:
The patent segments the system into distinct components: the mobile application, the intermediate module, and the peripheral device. The intermediate module acts as a separate, platform-independent layer that handles device-specific operations. This segmentation allows the mobile application to remain portable across different platforms while the intermediate module manages the complexities of peripheral device communication. The application does not need to be recompiled when moving to another platform, as the intermediate module handles the platform-specific details.
4Device complexity
If device functionality is exposed through a standardized layer, then the mobile application becomes simpler and more portable, but the peripheral device must adapt to the standardized protocol
Solution Approach 1:
The intermediate module serves as the mediator that handles the protocol adaptation from the peripheral device's native protocol to the standardized protocol. The peripheral device continues to operate with its original protocol, while the intermediate module translates its commands and responses into the standardized interface that the mobile application understands. This approach simplifies the application while maintaining peripheral device compatibility without requiring the peripheral devices themselves to change their protocols.
Data Source
AI summary
Communication between an integrated device and a mobile application client on a mobile personal communication device involves a command generated using a mobile application client implemented by non-managed code. The command is received by an operating system, is socket based and conforms with a standard network communications protocol. The command is forwarded to an intermediate module implemented by code executed on the mobile personal communication device and configured for socket based communication according to the standard network communications protocol. After receiving the command, the intermediate module generates a command communication, for receipt by the peripheral device, according to a protocol specific to the peripheral device. The command communication instructing the peripheral device to perform an operation corresponding to the command. The operation is performed using the peripheral device upon receiving the command communication.