Bluetooth Transport Sharing for GPS Data Multiplexing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The integration of multiple wireless technologies in mobile devices poses a challenge in balancing feature enhancement with cost, space, and battery life, as existing systems struggle to efficiently share Bluetooth transport for diverse data types like GPS, FM, and cellular data simultaneously.
Innovation Solution
A method and system that utilize vendor-specific commands to convert non-Bluetooth data into Bluetooth vendor-specific packets, allowing for multiplexing over a shared Bluetooth transport path, enabling simultaneous communication of various data types such as GPS, FM, and cellular data through UART, USB, SPI, and I2C interfaces.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple wireless technologies (GPS, FM, cellular) are integrated into mobile devices to enhance user experience, then device functionality and versatility are improved, but device complexity, cost, and battery consumption increase
Solution Approach 1:
The patent combines multiple wireless technology protocols (Bluetooth, GPS, FM, cellular) into a unified transport sharing architecture. Different protocol data are multiplexed over shared physical transport interfaces (UART, USB, SPI, I2C), merging previously separate communication paths into a consolidated system that reduces overall device complexity while maintaining all required functionalities.
Solution Approach 2:
The transport sharing mechanism creates universal interfaces that can carry multiple types of data traffic. The same physical transport path can dynamically handle Bluetooth packets, GPS data, FM radio signals, and cellular communications, making the transport layer multi-functional and adaptable to different protocol requirements without requiring dedicated separate paths for each technology.
2Reliability
If dedicated transport paths are allocated for each wireless technology (GPS, FM, cellular), then communication reliability is improved, but device space and cost increase
Solution Approach 1:
The patent merges multiple dedicated transport paths into shared physical interfaces. By multiplexing different protocol data streams over common transports (UART, USB, SPI, I2C), the system reduces the total number of physical connections required while maintaining reliable communication through protocol-specific processing and packet identification mechanisms.
3Adaptability or versatility
If multiple wireless technologies operate simultaneously in mobile devices, then user experience and functionality are enhanced, but battery life is reduced
Solution Approach 1:
The patent combines multiple wireless communication functions into a shared transport infrastructure. By allowing GPS, FM, cellular, and Bluetooth to share common physical transports through multiplexing, the system reduces redundant hardware operations and enables more efficient resource utilization, thereby lowering overall power consumption while maintaining simultaneous operation of multiple technologies.
4Reliability
If separate transport paths are used for each protocol (Bluetooth, GPS, FM), then protocol performance is maintained, but device cost and complexity increase
Solution Approach 1:
The patent segments data at the packet level, inserting protocol identification information into Bluetooth HCI packets. This segmentation allows the system to carry multiple protocol types (GPS, FM, cellular) within a unified Bluetooth transport framework, maintaining protocol-specific performance requirements while simplifying the overall transport architecture through centralized packet routing and processing.
Data Source
AI summary
Aspects of a method and system for Bluetooth transport sharing to carry GPS or other types of data are provided. A multi-standard Bluetooth enabled device may operate via integrated radios such as a GPS radio. The Bluetooth transport path may be shared to carry both Bluetooth data and non-Bluetooth data. The non-Bluetooth data may be converted to Bluetooth vendor specific packets using the assigned vendor specific commands. The Bluetooth vendor specific packets may be multiplexed with other Bluetooth HCI packets and communicate over the Bluetooth transport path. The Bluetooth vendor specific packets may be de-multiplexed based on the assigned vendor specific command and routed properly. Non-Bluetooth devices may be an on-chip and off-chip devices. The multi-standard Bluetooth enabled device may enable a downloadable driver to ensure communication with the off-chip devices. The Bluetooth transport path may be UART, USB, SPI, and/or I2C.