In-Vehicle Handsfree Call History Sync via Serial Bluetooth Linking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing in-vehicle handsfree systems face complexity in establishing reliable connectivity and data transfer for outgoing call history, incoming call history, and phone book data between cellular phones and in-vehicle handsfree apparatus, particularly due to the need for simultaneous connection of HFP and PBAP protocols, which can compromise communication stability and user experience.
Innovation Solution
The implementation of a serial connection procedure that alternates between HFP and PBAP protocols to establish and maintain communication links, ensuring stable data transfer and handsfree functionality while minimizing the complexity of software processes, allowing secure and reliable communication with cellular phones compliant with both protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If simultaneous connection of HFP and PBAP protocols is implemented, then data transfer capability is improved, but communication stability deteriorates
Solution Approach 1:
The patent divides the simultaneous protocol connection into sequential phases: first establishing HFP connection for handsfree functionality, then subsequently establishing PBAP connection for data transfer. This temporal segmentation allows each protocol to be stabilized independently, avoiding the interference that occurs when both protocols operate simultaneously, thus resolving the contradiction between data transfer capability and communication stability.
Solution Approach 2:
The patent performs preliminary establishment of the HFP connection before initiating PBAP connection. By pre-configuring the handsfree communication channel first, the system ensures that the voice communication foundation is stable before adding data transfer functionality. This preliminary action prevents protocol conflicts and maintains communication reliability while enabling comprehensive data transfer capability.
2Adaptability or versatility
If simultaneous connection of HFP and PBAP protocols is implemented, then data transfer capability is improved, but device complexity increases
Solution Approach 1:
The patent segments the protocol connection process into distinct sequential steps: HFP connection establishment, followed by PBAP connection establishment. This segmentation simplifies the software architecture by avoiding the need to manage simultaneous protocol interactions, reducing the complexity of error handling, resource management, and protocol coordination while still achieving both handsfree and data transfer functionalities.
3Device complexity
If serial connection procedure is used, then software complexity is reduced, but connection establishment time increases
Solution Approach 1:
The patent maintains continuous useful action during the serial connection process by ensuring that the first established connection (HFP) remains active and functional while the second connection (PBAP) is being established. This continuity allows the system to provide handsfree functionality immediately without waiting for data transfer setup, minimizing the perceived connection establishment time while keeping software complexity low.
Data Source
Figure 1
Figure 2
Figure 3A~3C
AI summary
An in-vehicle navigation apparatus (1) with a handsfree function establishes a Bluetooth communication link with a cellular phone (10). When receiving from the cellular phone (10) outgoing call history data and incoming call history data, which were stored in the cellular phone (10) before establishing the Bluetooth communication link, the in-vehicle navigation apparatus (1) stores, in a work memory (6), the received outgoing call history data and the received incoming call history data, equally to, of the navigation apparatus (1) itself, outgoing call history data and incoming call history data. An outgoing call operation then becomes possible using outgoing call history data and incoming call history data, which are stored in the work memory (6).