Hands-free device, hands-free system and data transfer method

The in-vehicle hands-free device enhances user convenience by automatically transferring and managing call history and directory data from mobile phones, improving hands-free calling and emergency call functionality.

JP7593718B2Active Publication Date: 2024-12-03PANASONIC AUTOMOTIVE SYST CO LTD
View PDF 16 Cites 0 Cited by

Patent Information

Application Number
JP2021032843
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-03-31
Filing Date
2021-03-02
Publication Date
2024-12-03
Estimated Expiration
2041-03-02

AI Technical Summary

Technical Problem

Existing hands-free devices do not fully leverage the convenience of wireless connectivity to enhance user experience by automatically transferring and managing call history and directory data from mobile phones, particularly in vehicles.

Method used

An in-vehicle hands-free device wirelessly connects to a mobile phone to receive and store incoming, outgoing, and missed call history data, as well as telephone directory data, using a control unit to manage data transfer protocols and display information on a user interface, ensuring seamless integration and user-friendly operation.

Benefits of technology

The solution improves the convenience of hands-free calling by allowing easy access to call history and directory data, enabling hands-free operations without manual input, and enhancing safety by allowing emergency calls with simplified redialing capabilities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007593718000001
    Figure 0007593718000001
  • Figure 0007593718000002
    Figure 0007593718000002
  • Figure 0007593718000003
    Figure 0007593718000003
Patent Text Reader

Abstract

To determine a data transfer sequence in consideration of data update frequency, at the transfer of telephone directory data, calling history data, and incoming history data which are included in history data.SOLUTION: An on-vehicle hands-free device includes a control unit, a data receiver unit, and a data memory unit. When a mobile phone exists in a radio connection area, the control unit controls data transfer using a transfer protocol to achieve the transfer of history data and telephone directory data stored in the mobile phone. The data receiver unit receives the history data and the telephone directory data from the mobile phone through communication by the transfer protocol. The data memory unit stores the received history data and the telephone directory data. The control unit performs control of transferring the history data prior to the telephone directory data.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a hands-free device, a hands-free system and a data transfer method. [Background technology]

[0002] As a configuration in which a mobile phone automatically transfers phonebook data showing the correspondence between telephone numbers and registered names to an in-vehicle hands-free device, for example, when a user gets into a vehicle carrying a mobile phone and the mobile phone enters the short-distance communication range of the in-vehicle hands-free device, a communication line is established between the mobile phone and the in-vehicle hands-free device, and the mobile phone automatically transfers the phonebook data to the in-vehicle hands-free device. According to this configuration, a user can select a desired phone number from the phonebook data of the mobile phone and make a call by operating the in-vehicle hands-free device (see, for example, Patent Document 1). In addition, a technology for improving user convenience in a system in which an in-vehicle device and a mobile device are connected has been proposed (see, for example, Patent Document 2 and Patent Document 3). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2002-193046 A [Patent Document 2] International Publication No. 2014 / 050459 [Patent Document 3] JP 2006-109292 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, there is a demand for further improvements in the convenience of hands-free devices that enable hands-free calling.

[0005] An object of the present disclosure is to further improve the convenience of hands-free devices. [Means for solving the problem]

[0006] The in-vehicle hands-free device according to the present disclosure enables hands-free calling by wirelessly connecting to a mobile phone that stores incoming call history data, outgoing call history data, telephone numbers, and phone book data, and includes a control unit, a data receiving unit, and a data storage unit. When the mobile phone is present in a wireless connection area, the control unit controls data transfer using a transfer protocol to transfer history data including incoming call history data and outgoing call history data, and phone book data, which are stored in the mobile phone. The data receiving unit receives the history data and phone book data from the mobile phone through communication using the transfer protocol. The data storage unit stores the history data and phone book data received by the data receiving unit. The control unit controls transfer of the history data before the phone book data. stomach , When the mobile phone is set to prohibit or limit the transfer of the history data or the phone book data, information indicating that the transfer of the history data or the phone book data is not possible is displayed on the display unit. Effect of the Invention

[0007] According to the present disclosure, the convenience of a hands-free device can be improved. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing an example of a usage pattern of an in-vehicle hands-free device according to the first embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of the in-vehicle hands-free device according to the first embodiment. [Diagram 3] FIG. 3 is a diagram showing an example of functions included in the in-vehicle hands-free device according to the first embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of detailed functions of the control unit of the in-vehicle handsfree device according to the first embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an example of the flow of a data transfer process according to the first embodiment. [Figure 6A]FIG. 6A is a diagram showing an example of a screen transition when displaying a calling operation screen that allows a calling operation based on a calling history of an emergency call according to the first embodiment. [Figure 6B] FIG. 6B is a diagram showing an example of a screen transition when displaying a calling operation screen that allows a calling operation based on a calling history of an emergency call according to the first embodiment. [Figure 7A] FIG. 7A is a diagram showing an example of a transition of a display screen when a user performs a calling operation from a calling history including emergency history data according to the first embodiment. [Figure 7B] FIG. 7B is a diagram showing an example of a transition of a display screen when a user performs a calling operation from a calling history including emergency history data according to the first embodiment. [Figure 7C] FIG. 7C is a diagram showing an example of a transition of a display screen when a user performs a calling operation from a calling history including emergency history data according to the first embodiment. [Figure 8A] FIG. 8A is a diagram showing an example of a correspondence relationship between outgoing call history data and telephone directory data according to the first embodiment. [Figure 8B] FIG. 8B is a diagram showing an example of a correspondence relationship between outgoing call history data and telephone directory data according to the first embodiment. [Figure 8C] FIG. 8C is a diagram showing an example of a correspondence relationship between outgoing call history data and telephone directory data according to the first embodiment. [Figure 9A] FIG. 9A is a diagram showing an example of a correspondence relationship between missed call history data and phone book data according to the first embodiment. [Figure 9B] FIG. 9B is a diagram showing an example of a correspondence relationship between missed call history data and telephone directory data according to the first embodiment. [Figure 9C] FIG. 9C is a diagram showing an example of a correspondence relationship between missed call history data and telephone directory data according to the first embodiment. [Figure 10] FIG. 10 is a diagram showing an example of outgoing call history data, incoming call history data, missed call history data, and all history data according to the first embodiment. [Figure 11]FIG. 11 is a diagram showing an example of a flow of a process for making a call using outgoing call history data, incoming call history data, and telephone directory data, which is executed in the in-vehicle handsfree device of the first embodiment. [Figure 12] FIG. 12 is a diagram showing an example of a flow of a process for making a call using outgoing call history data, incoming call history data, and telephone directory data, which is executed in the in-vehicle handsfree device of the first embodiment. [Figure 13A] FIG. 13A is a diagram showing an example of outgoing call history data according to the first embodiment. [Figure 13B] FIG. 13B is a diagram showing an example of outgoing call history data according to the first embodiment. [Figure 14A] FIG. 14A is a diagram showing an example of incoming call history data according to the first embodiment. [Figure 14B] FIG. 14B is a diagram showing an example of incoming call history data according to the first embodiment. [Figure 15A] FIG. 15A is a diagram showing an example of a transition of a display screen when a user performs a call operation from the call history according to the first embodiment. [Figure 15B] FIG. 15B is a diagram showing an example of a transition of a display screen when a user performs a call operation from the call history according to the first embodiment. [Figure 15C] FIG. 15C is a diagram showing an example of a transition of a display screen when a user performs a call operation from the call history according to the first embodiment. [Figure 16A] FIG. 16A is a diagram showing an example of a transition of a display screen when a user performs a call originating operation from an incoming call history according to the first embodiment. [Figure 16B] FIG. 16B is a diagram showing an example of a transition of a display screen when a user performs a call originating operation from an incoming call history according to the first embodiment. [Figure 16C] FIG. 16C is a diagram showing an example of a transition of a display screen when a user performs a call making operation from the incoming call history according to the first embodiment. [Figure 17A] FIG. 17A is a diagram showing an example of a transition of a display screen when a user performs a call operation from the telephone directory according to the first embodiment. [Figure 17B] FIG. 17B is a diagram showing an example of a transition of a display screen when a user performs a call operation from the telephone directory according to the first embodiment. [Figure 18] FIG. 18 is a diagram showing an example of telephone directory data according to the first embodiment. [Figure 19] FIG. 19 is a flowchart showing details of the flow of the HFP process according to the first embodiment. [Figure 20A] FIG. 20A is a diagram showing another example of transition of a display screen when a user performs a call originating operation from the incoming call history according to the first embodiment. [Figure 20B] FIG. 20B is a diagram showing another example of transition of a display screen when a user performs a call originating operation from the incoming call history according to the first embodiment. [Figure 20C] FIG. 20C is a diagram showing another example of transition of a display screen when a user performs a call making operation from the incoming call history according to the first embodiment. [Figure 21] FIG. 21 is a diagram illustrating an example of functions included in the hands-free device according to the first embodiment. [Figure 22] FIG. 22 is a diagram illustrating an example of detailed functions of the control unit of the hands-free device according to the first embodiment. [Figure 23] FIG. 23 is a diagram illustrating an example of the flow of a data transfer process according to the first embodiment. [Figure 24] FIG. 24 is a diagram illustrating an example of the flow of a data transfer process according to the second embodiment. [Figure 25A] FIG. 25A is a diagram showing an example of a screen transition when displaying a calling operation screen that enables a calling operation based on a calling history of an emergency call according to another embodiment. [Figure 25B] FIG. 25B is a diagram showing an example of a screen transition when displaying a calling operation screen that allows a calling operation based on a calling history of an emergency call according to another embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, embodiments of a hands-free device, a hands-free system, and a data transfer method according to the present disclosure will be described with reference to the drawings.

[0010] (First embodiment) FIG. 1 is a diagram showing an example of a usage form of an in-vehicle hands-free device 1 according to this embodiment. As shown in FIG. 1, the in-vehicle hands-free device 1 according to this embodiment can be mounted on a vehicle 3. The in-vehicle hands-free device 1 is communicatively connected to a mobile phone 2. The mobile phone 2 also wirelessly communicates with a base station 40 via a mobile phone network. The mobile phone 2 is, for example, a smartphone, and has a communication function according to the Bluetooth (registered trademark) method, which is a short-range wireless communication means. Note that the mobile phone 2 may be a type of mobile phone other than a smartphone, so long as it has a communication function according to the Bluetooth method.

[0011] In-vehicle hands-free device 1 connects to a mobile phone network via mobile phone 2. This allows, for example, a driver of vehicle 3 to make and receive calls by operating in-vehicle hands-free device 1 without operating mobile phone 2. In-vehicle hands-free device 1 may be realized, for example, as one function of an in-vehicle hands-free device mounted in vehicle 3.

[0012] 2 is a diagram showing an example of the hardware configuration of the in-vehicle hands-free device 1 according to the present embodiment. The in-vehicle hands-free device 1 according to the present embodiment is, for example, an in-vehicle hands-free device with a hands-free function. The in-vehicle hands-free device 1 is configured to include a control device 12, a Bluetooth communication unit 13, an operation unit 14, a display unit 15, a working memory 16, a storage memory 17, a microphone 18, and a speaker 19.

[0013] The control device 12 controls the overall operation of the in-vehicle hands-free device 1, such as the communication operation and data management operation. The control device 12 is, for example, a processor such as a CPU (Central Processing Unit). The control device 12 is an example of a control means, a determination means, a display control means, a transfer protocol control means, a transfer protocol disconnection means, a hands-free call protocol control means, an initial hands-free protocol communication means, a communication maintenance means, a phonebook transfer setting means, a data transfer designation means, and a manual transfer protocol designation means.

[0014] The Bluetooth communication unit 13 is compatible with the Bluetooth system, which is a short-range wireless communication means, and establishes a wireless communication line with the mobile phone 2 that is present within the Bluetooth wireless communication range to perform communication in accordance with the Bluetooth communication standard. Note that in this case, it is assumed that the mobile phone 2 has a Bluetooth communication function and is present within the Bluetooth wireless communication range of the in-vehicle hands-free device 1.

[0015] The Bluetooth communication unit 13 in this example supports the well-known HFP (Hands Free Profile) for hands-free calling and PBAP (Phone Book Access Profile) for transferring phone book data and outgoing / incoming call history data. These profiles refer to communication protocols defined for each function. The Bluetooth communication unit 13 is an example of outgoing call history data receiving means, incoming call history data receiving means, data receiving means, short-range wireless communication means, wireless communication means, hands-free call protocol connection means, and data transfer protocol connection means.

[0016] As is well known, the mobile phone 2 is configured to be able to establish a mobile phone line with a base station 40 of a mobile phone network and independently process outgoing and incoming calls when it is alone (when the HFP is not connected to the in-vehicle hands-free device 1 which is a hands-free device). In this case, the mobile phone 2 is configured to be able to independently process outgoing and incoming calls by establishing a mobile phone line with a base station 40 of a mobile phone network. In this case, when the user operates the dial keys (numeric keys "0" to "9") (not shown) to input the telephone number of the callee, and then operates the call key (not shown), the mobile phone 2 can make a call to the telephone number as the callee, and can make a call with the mobile phone of the callee.

[0017] In addition, in terms of incoming call processing, when mobile phone 2 receives an incoming call signal from base station 40 in response to a call made by the calling mobile phone specifying mobile phone 2 as the destination, it receives the telephone number of the calling mobile phone from base station 40 as the incoming call telephone number, and when the user operates the answer key (not shown), the calling mobile phone can be answered, making it possible to conduct a call between the calling mobile phone and the calling mobile phone.

[0018] The mobile phone 2 also has a clock unit (not shown) that keeps track of the date and time (date and time), and stores and holds multiple outgoing call history data items, each item being a correspondence between the calling phone number entered from the dial keys in the above-mentioned outgoing call process and the calling date and time based on the date and time kept by the clock unit.The mobile phone 2 also stores and holds multiple incoming call history data items, each item being a correspondence between the incoming phone number received from the base station 40 in the above-mentioned incoming call process and the incoming date and time based on the date and time kept by the clock unit.

[0019] The mobile phone 2 also stores and holds multiple missed call history data, each of which corresponds to a phone number received from the base station 40 when the mobile phone 2 did not respond to an incoming call and the date and time of the incoming call based on the date and time kept by the clock unit. The mobile phone 2 also holds multiple phone book data, each of which corresponds to a phone number and a registered name. The phone book data is stored in a non-volatile memory (not shown) with, for example, about 500 entries of phone numbers and registered names entered by the user in association with each other.

[0020] If the mobile phone 2 has phonebook data, the outgoing call history data and incoming call history data include the registered name. Specifically, it is checked whether the incoming phone number received from the base station 40 is a phone number registered in the phonebook data, and whether a registered name is registered for this phone number in the phonebook data. If so, the incoming call history data consists of the phone number, the date and time of the incoming call, and the registered name. The missed call history data is similarly processed and consists of the phone number, the date and time of the incoming call, and the registered name. The outgoing call history data is also checked whether the phone number called in the outgoing process is a phone number registered in the phonebook data, and if so, it consists of the date and time of the outgoing call, the outgoing phone number, and the registered name.

[0021] By reading out the phonebook data and selecting one phone number to make a call, the user can easily make a call without having to input all the numeric keys corresponding to the numbers that make up the phone number. The mobile phone 2 can store, for example, the latest 20 outgoing call history data, incoming call history data, and missed call history data, and automatically erases the oldest data each time an outgoing call is made, an incoming call is made, or a missed call is made, and updates the outgoing call history data, incoming call history data, and missed call history data. The mobile phone 2 is compatible with the well-known HFP for hands-free calling, and PBAP for transferring phonebook data and outgoing / incoming call history data.

[0022] If the mobile phone 2 supports the PBAP that specifies the automatic transfer of call history data, the PBAP is connected immediately after establishing a communication line with the Bluetooth communication unit 13, and the phone book data stored at that time is automatically transferred, and further the outgoing call history data, incoming call history data, and missed call history data stored at that time are automatically transferred. As a result, when the in-vehicle hands-free device 1 is present within the Bluetooth communication range, the mobile phone 2 automatically transfers to the in-vehicle hands-free device 1 up to 20 outgoing call history data that have been previously processed independently and stored, up to 20 incoming call history data that have been previously processed independently and stored, and up to 20 missed call history data that have been previously processed independently and stored.

[0023] In this embodiment, outgoing call history data, incoming call history data, and missed call history data are sometimes collectively referred to simply as history data. Here, the history data includes at least outgoing call history data and incoming call history data. The history data may be in a form consisting of outgoing call history data and incoming call history data, or in a form consisting of outgoing call history data, incoming call history data, and missed call history data.

[0024] Furthermore, when the mobile phone 2 does not respond to an incoming call, the mobile phone 2 stores the voice message left by the caller in a non-volatile memory (not shown). The voice message is also called a message memo, for example, and the user of the mobile phone 2 can play it back to listen to the contents.

[0025] The operation unit 14 is an operation means in this embodiment for operation by the user, and is composed of, for example, touch keys formed on the display unit 15, detects the user's operation, and outputs an operation signal representing the operation content to the control device 12. The display unit 15 is a display means in this embodiment, and when a display signal is input from the control device 12, it displays a display screen based on the input display signal, and displays, for example, a display screen on which dial keys corresponding to "0" to "9" are arranged as a display screen on which the user inputs a phone number.

[0026] The working memory 16 is an outgoing call history data storage means, an incoming call history data storage means, and a data storage means in this embodiment, and is composed of a volatile memory. The working memory 16 stores outgoing call history data, incoming call history data, missed call history data, and phone book data that are automatically transferred from the mobile phone 2 without any user operation. In this case, the working memory 16 can store, for example, five items each of the outgoing call history data, incoming call history data, and missed call history data. The working memory 16 is, for example, a RAM (Random Access Memory) or the like.

[0027] The storage memory 17 is composed of a non-volatile memory and stores various data. The storage memory 17 is, for example, a ROM (Read Only Memory). The storage memory 17 may also be a writable storage medium such as a HDD (Hard Disk Drive) or a flash memory.

[0028] In this case, when the user makes a display request for outgoing call history data through the operation unit 14, the control device 12 causes the display unit 15 to display the outgoing call history data stored in the work memory 16, when the user makes a display request for incoming call history data through the operation unit 14, the control device 12 causes the display unit 15 to display the incoming call history data stored in the work memory 16, and when the user makes a display request for phonebook data through the operation unit 14, the control device 12 causes the display unit 15 to display the phonebook data stored in the work memory 16. In the in-vehicle hands-free device 1 of this embodiment, as described above, five outgoing call history data and five incoming call history data are stored in the work memory 16, and the maximum number of data items displayed on the display unit 15 is also five. The number of data items stored in the work memory 16 is merely an example, and is not limited to the above example.

[0029] The microphone 18 is a voice input means for inputting voice, and inputs voice uttered by the user when making a hands-free call using the mobile phone 2, and the speaker 19 is a voice output means for outputting the incoming voice of the call partner when making a hands-free call using the mobile phone 2. That is, when a Bluetooth communication line is established between the Bluetooth communication unit 13 and the mobile phone 2 and wireless communication is connected in HFP, the control device 12 causes the Bluetooth communication unit 13 to transmit the voice input by the microphone 18 to the mobile phone 2 and causes the mobile phone 2 to transmit the voice to the mobile phone network, and also causes the Bluetooth communication unit 13 to receive the voice received by the mobile phone 2 from the mobile phone network and output it from the speaker 19.

[0030] In addition to the functional blocks shown in the figure, the above-mentioned in-vehicle hands-free device 1 may also be configured with functional blocks necessary for navigation operations, such as a GPS device as a current position detection unit that detects the current position of the vehicle, a route search unit that searches for a route from the current position to the destination, a map data reading unit that reads map data from a recording medium on which the map data is recorded, a VICS information receiving unit that receives VICS information distributed from a VICS (registered trademark) center, and a voice recognition unit that recognizes voices uttered by the user. In this case, the in-vehicle hands-free device 1 may obtain the date and time by extracting GPS date and time information from a GPS radio signal received by the GPS device from a GPS satellite, and use the obtained date and time as the date and time of transmission or the date and time of reception.

[0031] The above-mentioned in-vehicle hands-free device 1 is configured to start and stop in conjunction with the on / off of an ACC switch (a switch that turns on and off the power supply to vehicle equipment). When the ACC switch is switched from on to off in response to, for example, a user's operation, the in-vehicle hands-free device 1 stops the power supply, and as a result, the device power changes from on to off. In this case, the various data stored in the storage memory 17 immediately before that is not erased (but is retained), but the outgoing call history data, incoming call history data, missed call history data, and phone book data stored in the working memory 16 immediately before that are erased.

[0032] Next, the details of the functions of the in-vehicle hands-free device 1 of this embodiment will be described. Fig. 3 is a diagram showing an example of the functions of the in-vehicle hands-free device 1 according to this embodiment. Note that the functions of the in-vehicle hands-free device 1 are not limited to the example of Fig. 3, and the in-vehicle hands-free device 1 may further have other functions. In the example of Fig. 3, the in-vehicle hands-free device 1 of this embodiment includes a reception unit 101, a control unit 102, a data receiving unit 103, and a storage unit 104.

[0033] In this embodiment, the functions of the reception unit 101, the control unit 102, and the data receiving unit 103 are realized by the control device 12 reading and executing a program from the storage memory 17. However, this is not limited to the above, and for example, some or all of the functions of the reception unit 101, the control unit 102, and the data receiving unit 103 may be realized by a dedicated hardware circuit. Also, the storage unit 104 is realized by the storage memory 17, for example.

[0034] The reception unit 101 receives various operations from a user. For example, the reception unit 101 receives an input in response to a user's operation of the operation unit 14. More specifically, the reception unit 101 receives an instruction operation (for example, an operation of pressing an icon) for various images displayed on the display unit 15.

[0035] The control unit 102 performs various controls related to the in-vehicle hands-free function. In this example, the control unit 102 has a function of connecting to the mobile phone 2 so that a hands-free call can be made, and a function of controlling data transfer in a transfer protocol for realizing the transfer of incoming call history data, outgoing call history data, and phonebook data stored in the mobile phone 2 when the mobile phone 2 is in a wireless connection area. In this example, the control unit 102 causes the mobile phone 2 to make an emergency call to a destination when an emergency call sending condition is satisfied, and when the hands-free call protocol control means is in a hands-free call protocol connection state and in an incoming call state, causes the data transfer protocol connection means to receive the outgoing call history data from the mobile phone 2 in a data transfer protocol (PBAP in this example) when the incoming call state ends and the communication state changes to a different state from the incoming call state. The outgoing call history data from the mobile phone 2 includes the telephone number of the destination of the emergency call or the identification information of the destination. In this example, when the conditions for sending an emergency call are satisfied, the control unit 102 controls the mobile phone 2 to send an emergency call to the destination, and when it detects that the call with the destination of the emergency call has ended, it controls the mobile phone 2 to transfer emergency history data indicating a history of emergency calls to the in-vehicle hands-free device 1. After receiving the call history data from the mobile phone 2, the control unit 102 controls the display unit 15 to display a call operation screen that allows a call operation based on the call history in response to a user operation. Details of the various functions of the control unit 102 will be described later.

[0036] Here, the emergency call may be, for example, a call used in a predetermined emergency call system established by a public institution such as a country. In addition, in this case, the telephone number for the emergency call may be, for example, predetermined by the public institution. One example of the emergency call system is the eCall system established in Europe, and in this case, the telephone number for the emergency call is a predetermined European common number (for example, "112"). Alternatively, the emergency call may be a call used in a dedicated call system introduced by a company (for example, an automobile manufacturer or an insurance company). In this case, the emergency call may be, for example, designed to be available to users such as customers of the company, and the telephone number for the emergency call may be, for example, predetermined by the company.

[0037] Fig. 4 is a diagram showing an example of detailed functions of the control unit 102. As shown in Fig. 4, the control unit 102 has a hands-free call connection control unit 111, a data transfer control unit 112, an emergency communication control unit 113, and a display control unit 114. Note that the functions of the control unit 102 are not limited to these, and the control unit 102 may further have other functions for realizing an in-vehicle hands-free function.

[0038] The hands-free call connection control unit 111 connects to the mobile phone 2 so as to enable a hands-free call in accordance with the HFP. More specifically, the hands-free call connection control unit 111 connects to the mobile phone 2 so as to enable a hands-free call by controlling the Bluetooth communication unit 13. The hands-free call connection control unit 111 is an example of a "hands-free call protocol connection means" and connects between the mobile phone 2 and the hands-free call protocol for realizing a hands-free call by the mobile phone 2.

[0039] The data transfer control unit 112 controls data transfer in the transfer protocol (PBAP in this example). The emergency communication control unit 113 controls communication during an emergency. The display control unit 114 controls the display of various screens on the display unit 15. For example, the display control unit 114 controls the display of the call operation screen and the like on the display unit 15. Specific details of these will be described later.

[0040] In this embodiment, the various functions of the in-vehicle hands-free device 1 are realized by one device, but the present invention is not limited to this, and the various functions of the in-vehicle hands-free device 1 may be distributed among multiple devices. In other words, the various functions of the in-vehicle hands-free device 1 may be realized by a system (in-vehicle hands-free system) composed of multiple devices.

[0041] Next, the operation of the above-mentioned configuration will be described. In this embodiment, the mobile phone 2 already holds (stores) 20 outgoing call history data, 20 incoming call history data, and 20 missed call history data, which are the maximum number that can be stored, and the description will be given on the premise that in this state, a user carrying the mobile phone 2 approaches the vehicle 3, gets in the vehicle, and turns on the ACC switch, causing the mobile phone 2 to enter the Bluetooth communication range of the in-vehicle hands-free device 1.

[0042] First, a procedure in which the control device 12 in the in-vehicle hands-free device 1 receives outgoing call history data, incoming call history data, missed call history data, and phone book data from the mobile phone 2 will be described with reference to Fig. 5. Note that the user pre-registers the mobile phone 2 with which Bluetooth communication will be performed in the in-vehicle hands-free device 1.

[0043] For example, the user inputs a four-digit password for each mobile phone 2 into the in-vehicle hands-free device 1 at the time of initial communication setting. The in-vehicle hands-free device 1 and the mobile phone 2 generate a link key to be used for connection with each other, and hold the link key. The in-vehicle hands-free device 1 selects the mobile phone 2 to be connected for communication by authenticating the link key at the time of initial connection. In other words, communication connection in HFP and communication connection in PBAP are not performed between the in-vehicle hands-free device 1 and an unregistered mobile phone. Basically, the mobile phone 2 of the owner of the vehicle 3 is preregistered, and Bluetooth communication is performed between the mobile phone 2 and the in-vehicle hands-free device 1. Note that the above-mentioned method for preregistering the mobile phone 2 to be communicated with by the in-vehicle hands-free device 1 is one example, and is not limited thereto.

[0044] In this example, it is assumed that a plurality of mobile phones 2 to be communication connection targets are registered in the in-vehicle hands-free device 1. In addition, for example, a user operates the operation unit 14 to set priorities in advance for the plurality of mobile phones 2, and the work memory 16 or the storage memory 17 stores the priorities. For example, some drivers may own a plurality of mobile phones 2, so the in-vehicle hands-free device 1 allows registration of a plurality of mobile phones 2 in this way.

[0045] As a premise of this example, the Bluetooth communication unit 13 of the in-vehicle hands-free device 1 supports both the HFP wireless communication protocol and the PBAP wireless communication protocol, and can connect these two profiles simultaneously (multi-profile connection). However, this simultaneous connection process is intentionally not performed. There are three main reasons for this:

[0046] (1) The mobile phone 2, which is the communication partner, like the in-vehicle hands-free device 1, supports wireless communication via HFP and wireless communication via PBAP, but may not support simultaneous connection.

[0047] (2) Although mobile phone 2, which is the communication partner, is compatible with wireless communication via HFP and wireless communication via PBAP and may also support simultaneous connection, maintaining a simultaneous connection requires complex software processing in Bluetooth communication unit 13 of in-car hands-free device 1, which may cause concerns about the stability of the communication connection.

[0048] (3) Mobile phones 2 are manufactured by many manufacturers around the world, and the in-vehicle hands-free device 1 is required to be able to connect to all mobile phones that support wireless communication via HFP and PBAP.

[0049] For the above reasons, in the in-vehicle hands-free device 1 of this example, as a more reliable processing procedure for wireless communication via HFP and wireless communication via PBAP, in order to eliminate simultaneous connections between wireless communication via HFP and wireless communication via PBAP as much as possible, the wireless communication via HFP and the wireless communication via PBAP are serially connected in a time-separated manner.

[0050] Returning to the explanation, the control unit 102 (hands-free call connection control unit 111) selects the mobile phone 2 with the highest priority as a communication connection target for wireless communication in HFP (S1). Here, in this example, without first performing a communication connection in PBAP, first an initial communication in HFP is automatically attempted and a connection is started.

[0051] Next, the control unit 102 (hands-free call connection control unit 111) executes a process of automatically connecting the initial communication in HFP to the selected mobile phone 2 (S2). In addition, the control unit 102 (hands-free call connection control unit 111) determines whether or not the wireless communication connection in HFP has been successful (S3).

[0052] When the control unit 102 (hands-free call connection control unit 111) determines that the wireless communication connection in the HFP has been successful (S3 "YES"), it automatically disconnects the connected wireless communication in the HFP (S4).

[0053] Next, the control unit 102 (data transfer control unit 112) automatically establishes wireless communication via PBAP with the mobile phone 2 with which the wireless communication connection via HFP has been successful (S5).

[0054] Next, the control unit 102 (data transfer control unit 112) transmits a history data transfer request to the mobile phone 2 to start the transfer process of the history data (in this example, outgoing call history data, incoming call history data, and missed call history data) (S6).

[0055] The mobile phone 2 that has received the history data transfer request transfers the history data to the in-vehicle hands-free device 1 by Bluetooth communication conforming to the PBAP. The control unit 102 (data transfer control unit 112) stores the history data transferred (downloaded) from the mobile phone 2 in the working memory 16 or the storage memory 17.

[0056] When the transfer process of the history data is completed, the control unit 102 (data transfer control unit 112) transmits a telephone directory data transfer request to the mobile phone 2 to start the transfer process of the telephone directory data (S7).

[0057] Upon receiving the request to transfer the phone book data, the mobile phone 2 transfers the phone book data to the in-vehicle hands-free device 1 by Bluetooth communication conforming to the PBAP. The control unit 102 (data transfer control unit 112) stores the phone book data transferred from the mobile phone 2 in the working memory 16 or the storage memory 17.

[0058] When the transfer of the telephone directory data is completed, the control unit 102 (data transfer control unit 112) disconnects the wireless communication with the mobile phone 2 by the PBAP (S8).

[0059] Next, the control unit 102 (data transfer control unit 112) automatically connects the mobile phone 2 to wireless communication using HFP again (S9).

[0060] Then, when HFP wireless communication with the mobile phone 2 is established, the control unit 102 (hands-free call connection control unit 111) transitions to hands-free (HF) standby processing (S10). During the hands-free standby processing, the in-vehicle hands-free device 1 is in a state in which it is possible to make or receive calls via the mobile phone 2. The hands-free standby processing continues until the power supply of the in-vehicle hands-free device 1 is cut off or the HFP wireless communication with the mobile phone 2 is terminated. The HFP wireless communication with the mobile phone 2 is terminated when the user performs a disconnection operation on the in-vehicle hands-free device 1 or the mobile phone 2, or when the mobile phone 2 leaves the Bluetooth communication range of the in-vehicle hands-free device 1, etc.

[0061] In this manner, in this embodiment, wireless communication is automatically switched to serial communication in the order of HFP→PBAP→HFP. This makes it possible to reliably and stably perform communication processing for mobile phones from many manufacturers that support wireless communication in HFP and wireless communication in PBAP. In addition, this method can reduce the complexity of software processing in the in-vehicle hands-free device 1.

[0062] In the hands-free (HF) standby process, when the emergency call sending condition is satisfied (S11 "YES"), the control unit 102 (emergency communication control unit 113) sends an emergency call via the mobile phone 2 (S12). Then, the control unit 102 (emergency communication control unit 113) transmits the position information of the vehicle (S13). The emergency call sending condition can be set arbitrarily, and may be, for example, that an impact exceeding a reference value has been detected, that an airbag has been activated, or that a rollover of the vehicle has been detected. In addition, it may be, for example, that an instruction to send an emergency call has been received. The method of receiving the instruction to send an emergency call is arbitrary, and may be, for example, that an operation is performed on a GUI (Graphical User Interface) (for example, an icon, etc.) for sending instructions displayed on the display unit 15, that a telephone number for an emergency call is directly input via the operation unit 14, or that an instruction to send an emergency call is received by receiving a press of a hardware button arranged in the vehicle cabin. The hardware button may be disposed, for example, at any location in the cabin of the vehicle 3 (for example, on a wall such as the ceiling, the dashboard, or the steering wheel) or may be disposed on the display unit 15. The hardware button may be configured integrally with the operation unit 14.

[0063] In this example, when the control unit 102 (emergency communication control unit 113) determines that the above-mentioned emergency call sending conditions are satisfied, it sends an emergency call to the number of the emergency call destination (for example, "112") via the mobile phone 2. When connected to the emergency call destination, the control unit 102 (emergency communication control unit 113) automatically transmits information about the vehicle 3 (for example, the model and color) as well as time and location information, and also connects a voice line, enabling a conversation between the driver and an operator at the emergency call destination.

[0064] Then, when the control unit 102 (emergency communication control unit 113) detects the end of the call with the destination of the emergency call (end of the conversation with the operator) (S14 "YES"), it controls the transfer of emergency history data including at least the call history of the emergency call and indicating the history related to the emergency call from the mobile phone 2 to the in-vehicle hands-free device 1 (S15). The method of detecting the end of the call is arbitrary, but the end of the call can also be detected by detecting, for example, a change from an incoming call state or a talking state to a communication state different from the state (for example, a transition from an incoming call state to a standby state, a transition from a talking state to a standby state, or a transition from an incoming call state to an incoming call state and then a transition to a standby state). In addition, the timing of the transfer of the emergency history data can be set arbitrarily, and is not limited to the timing of detecting the end of the call.

[0065] In this example, the control unit 102 (emergency communication control unit 113) automatically starts transferring emergency history data when it detects the end of a call with the destination of the emergency call (end of conversation with the operator). However, the present invention is not limited to this, and the transfer of emergency history data may be started when an instruction to start transfer is received by operating a GUI or a hardware button, for example.

[0066] Furthermore, when the control unit 102 (emergency communication control unit 113) transfers emergency history data from the mobile phone 2, the control unit 102 receives the call history data consisting of the registered name, the calling telephone number, and the calling date and time from the mobile phone 2 and stores the data in the working memory 16. After that, when the control unit 102 receives a request to display the call history data, the control unit 102 can display the call history data stored in the working memory 16 and perform a call processing using the call history data. The call history data from the mobile phone 2 includes the telephone number of the call destination of the emergency call or the identification information of the call destination. For example, when the control unit 102 (display control unit 114) receives a press of the "History" button from the screen of FIG. 6A, the control unit 102 controls the display unit 15 to display the screen shown in FIG. 6B. The screen shown in FIG. 6B displays the call history of the emergency call (the number "112" shown in FIG. 6B is the number of the call destination of the emergency call). When the control unit 102 receives a selection of the number of the call destination of the emergency call via the screen shown in FIG. 6B, the control unit 102 can perform a call processing to call the selected number as the call destination telephone number. That is, the screen shown in Fig. 6B is a calling operation screen that allows calling operation based on the calling history of emergency calls. Specific steps of calling operation based on the calling history will be described later.

[0067] For example, a dedicated call operation screen (referred to as an "emergency call call operation screen") that allows call operation using only the call history of an emergency call may be prepared separately from a call operation screen that allows call operation using a normal call history. In this form, for example, a dedicated operation unit (e.g., a GUI or a hardware button) for calling up the emergency call call operation screen may be separately provided, and the control unit 102 may display the emergency call call operation screen when it receives an operation on the dedicated operation unit.

[0068] When the transfer of the emergency history data is completed, the control unit 102 (hands-free call connection control unit 111) transitions again to hands-free (HF) standby processing.

[0069] Furthermore, when the control unit 102 (hands-free call connection control unit 111) determines that the wireless communication connection via HFP was not successful (failed) (S3 “No”), it determines whether or not there is a mobile phone 2 with the next highest priority (S16).

[0070] If the control unit 102 (hands-free call connection control unit 111) determines that a mobile phone 2 with the next highest priority exists (S16 "Yes"), it selects the mobile phone 2 with the next highest priority as the wireless communication connection target (S17), returns to S2 described above, and repeats the above processing.

[0071] Moreover, when the control unit 102 (hands-free telephone connection control unit 111) determines that there is no mobile phone 2 with the next highest priority (S16 "No"), it ends the process of this flowchart.

[0072] Next, the transfer process of the outgoing call history data, the incoming call history data, and the missed call history data described above with reference to FIG. 5 etc. will be described in more detail.

[0073] 7A to 7C are diagrams showing an example of the correspondence between outgoing call history data and phonebook data according to this embodiment. More specifically, FIG. 7A is an example of outgoing call history data stored in the mobile phone 2. FIG. 7B is an example of phonebook data stored in the mobile phone 2. FIG. 7C is an example of outgoing call history data stored or displayed in the in-vehicle hands-free device 1.

[0074] Fig. 8 is a diagram showing an example of the correspondence between incoming call history data and phone book data according to this embodiment. More specifically, Fig. 8A is an example of incoming call history data stored in the mobile phone 2. Fig. 8B is an example of phone book data stored in the mobile phone 2. Fig. 8C is an example of incoming call history data stored or displayed in the in-vehicle hands-free device 1.

[0075] 9A to 9C are diagrams showing an example of the correspondence between missed call history data and phone book data according to this embodiment. More specifically, FIG. 9A is an example of missed call history data stored in the mobile phone 2. FIG. 9B is an example of phone book data stored in the mobile phone 2. FIG. 9C is an example of missed call history data stored or displayed in the in-vehicle hands-free device 1.

[0076] The control unit 102 (data transfer control unit 112) receives the call history data consisting of the registered name, the calling telephone number, and the calling date and time shown in FIG.

[0077] In addition, the control unit 102 (data transfer control unit 112) receives incoming call history data consisting of the registered name, incoming call telephone number, and incoming call date and time shown in FIG.

[0078] In addition, the control unit 102 (data transfer control unit 112) receives missed call history data consisting of the registered name, missed call telephone number, and missed call date and time shown in FIG. 9A from the mobile phone 2, and stores it in the working memory 16 or the storage memory 17.

[0079] In addition, when the incoming call history data, outgoing call history data, and missed call history data in the mobile phone 2 do not include a registered name, the control unit 102 (data transfer control unit 112) may add the registered name to the incoming call history data, outgoing call history data, and missed call history data by associating the telephone number included in the incoming call history data, outgoing call history data, and missed call history data with the registered name associated with the telephone number in the phonebook data, and store the registered name in the working memory 16 or the storage memory 17. Then, when there is a display request for the outgoing call history data, incoming call history data, and missed call history data, the control unit 102 (display control unit 114) causes the display unit 15 to display the outgoing call history data, incoming call history data, and missed call history data stored in the working memory 16 or the storage memory 17. In other words, the control unit 102 (display control unit 114) can display the registered name transferred from the mobile phone 2 on the display unit 15 without reading out the registered name from the phonebook data stored in the working memory 16 or the storage memory 17.

[0080] The incoming call history data, outgoing call history data, and missed call history data may be stored in the working memory 16 or the storage memory 17 without including the registered name. In this case, the control unit 102 (display control unit 114) displays on the display unit 15 the telephone numbers included in the incoming call history data, outgoing call history data, and missed call history data in association with the registered name associated with the telephone number in the telephone directory data.

[0081] When the control unit 102 (hands-free call connection control unit 111) completes the HFP connection processing described in S25 of FIG. 5, the user can make and receive calls by operating the operation unit 14 on the in-car hands-free device 1 side.

[0082] After the control unit 102 (data transfer control unit 112) receives the outgoing call history data, incoming call history data, and missed call history data from the mobile phone 2 by the initial connection process with the mobile phone 2 described in Fig. 5, a new outgoing call process, a new incoming call process, or a new missed call process may be executed in the in-vehicle hands-free device 1 or the mobile phone 2. When the user operates the operation unit 14 to request the display of the outgoing call history data, incoming call history data, or missed call history data, if the registered name corresponding to the outgoing call telephone number, incoming call telephone number, and missed call telephone number for which the new outgoing call process, incoming call process, or missed call process is executed exists in the phonebook data transferred from the mobile phone 2, the control unit 102 (display control unit 114) causes the display unit 15 to display the registered name as shown in Figs. 7C, 8C, and 9C.

[0083] More specifically, it is assumed that the control unit 102 (hands-free telephone connection control unit 111) performs a call process to the telephone number of "Kato Ichiro" as a new call process. In this case, if the registered name of "Kato Ichiro" is registered in the telephone directory data, the control unit 102 (display control unit 114) reads out the registered name of "Kato Ichiro" from the telephone directory data and displays it on the display unit 15 as shown in FIG. 7C. Also, if there is a call from the telephone number of "Yoshimoto Ichiro" as a new incoming call process, the control unit 102 (display control unit 114) reads out the registered name of "Yoshimoto Ichiro" from the telephone directory data and displays it on the display unit 15 as shown in FIG. 8C if this incoming telephone number is registered in the telephone directory data. Also, if there is a new missed call from the telephone number of "Watanabe Saburo", the control unit 102 (display control unit 114) reads out the registered name of "Watanabe Saburo" from the telephone directory data and displays it on the display unit 15 as shown in FIG. 9C.

[0084] In addition, when there is a request to display all history data (all outgoing and incoming call histories) that compiles outgoing call history data, incoming call history data, and missed call history data and displays them in order of the latest time, the control unit 102 (display control unit 114) selects and displays a predetermined number of incoming call history data and missed call history data with newer incoming call dates or missed call dates and times from all, regardless of whether the incoming call phone number or missed call phone number is the same (duplicate).In addition, the control unit 102 (display control unit 114) selects and displays only the latest outgoing call history data from among the outgoing call history data with the same (duplicate) outgoing phone number.

[0085] Fig. 10 is a diagram showing an example of outgoing call history data, incoming call history data, missed call history data, and all history data according to this embodiment. In the example shown in Fig. 10, the outgoing phone number of "Abe Taro" is duplicated. In this case, the control unit 102 (display control unit 114) displays only the outgoing call history with the latest outgoing date and time (outgoing call history data with the outgoing date and time of August 10th at 12:15) among the outgoing call history of "Abe Taro", and does not display the outgoing call history with the latest outgoing date and time.

[0086] Next, we will explain the procedure by which the control device 12 in the in-vehicle hands-free device 1 receives and stores outgoing call history data, incoming call history data, missed call history data, and phone book data from the mobile phone 2, and the procedure by which the control device 12 makes calls using the stored outgoing call history data, incoming call history data, and missed call history data. Note that, although the outgoing call history data and incoming call history data are explained here, the same applies to missed call history data.

[0087] 11 and 12 are diagrams showing an example of the flow of a process for making a call using outgoing call history data, incoming call history data, and telephone directory data executed by the in-vehicle hands-free device 1 of this embodiment. Note that the process executed by the control device 12 in Fig. 11 and Fig. 12 is, for example, a process realized by the control unit 102 described in Fig. 3, etc.

[0088] Here, Fig. 13A to Fig. 13B described in Fig. 11 and Fig. 12 are diagrams showing an example of outgoing call history data according to this embodiment. Fig. 14A to Fig. 14B are diagrams showing an example of incoming call history data according to this embodiment. Fig. 15A to Fig. 15C are diagrams showing an example of a transition of a display screen when a user performs an outgoing call operation from the outgoing call history according to this embodiment. Fig. 16A to Fig. 16C are diagrams showing an example of a transition of a display screen when a user performs an outgoing call operation from the incoming call history according to this embodiment. Fig. 17A to Fig. 17B are diagrams showing an example of a transition of a display screen when a user performs an outgoing call operation from the phone book according to this embodiment. Fig. 18 is a diagram showing an example of phone book data according to this embodiment.

[0089] Returning to the flowchart of FIG. 11, first, when the control device 12 of the in-car hands-free device 1 determines that the mobile phone 2 is within the Bluetooth communication range of the in-car hands-free device 1 and that the Bluetooth communication unit 13 has established a communication line with the mobile phone 2 (S121 "Yes"), it waits for the outgoing call history data, incoming call history data and phone book data to be automatically transferred from the mobile phone 2 to the Bluetooth communication unit 13 (S122).

[0090] Then, when the control device 12 determines that the outgoing call history data, incoming call history data, and phone book data have been automatically transferred from the mobile phone 2 (S122 "Yes"), it stores the outgoing call history data, incoming call history data, and phone book data automatically transferred from the mobile phone 2 in the working memory 16 or the storage memory 17 (S123).

[0091] Here, it is assumed that the number of outgoing call history data and incoming call history data automatically transferred from the mobile phone 2 is, for example, 20. Also, it is assumed that the number of outgoing call history data and incoming call history data that can be stored in the working memory 16 is, for example, 5. In other words, the number of outgoing call history data and incoming call history data that can be stored in the working memory 16 is less than the number of outgoing call history data and incoming call history data automatically transferred from the mobile phone 2.

[0092] In this case, the control device 12, for example, discards outgoing call history data with an older call date and time among the outgoing call history data automatically transferred from the mobile phone 2, and prioritizes the five outgoing call history data with the newest call date and time among the 20 outgoing call history data automatically transferred from the mobile phone 2, and stores them in the working memory 16 as mobile-side outgoing call history data. Also, the control device 12 discards incoming call history data with an older call date and time among the incoming call history data, and prioritizes the five outgoing call history data with the newest call date and time among the 20 outgoing call history data automatically transferred from the mobile phone 2, and stores them in the working memory 16 as mobile-side incoming call history data.

[0093] Immediately after the outgoing call history data is automatically transferred from the mobile phone 2, the control device 12 holds the outgoing call history data shown in Fig. 13A as the outgoing call history data in the working memory 16. When the user performs an operation to display the outgoing call history data from this state, the control device 12 displays the display screen shown in Fig. 15B on the display unit 15. Immediately after the incoming call history data is automatically transferred from the mobile phone 2, the control device 12 holds the incoming call history data shown in Fig. 14A as the incoming call history data in the working memory 16, and when the user performs an operation to display the incoming call history data from this state, the control device 12 displays the display screen shown in Fig. 16B on the display unit 15.

[0094] In this way, when the mobile phone 2 and the in-vehicle hands-free device 1 establish a Bluetooth communication line, the outgoing call history data and incoming call history data stored in the mobile phone 2 before the establishment of the Bluetooth communication line are automatically transferred to the working memory 16 of the in-vehicle hands-free device 1, and the mobile phone 2 and the in-vehicle hands-free device 1 form one telephone system, which enables hands-free calling. After the mobile phone 2 and the in-vehicle hands-free device 1 form one telephone system in this way, the user can select one of the following to make a call: a call using dial keys, a call using the outgoing call history, a call using the incoming call history, or a call using the phone book, and can wait for an incoming call from the mobile phone network.

[0095] In this embodiment, as a procedure of Bluetooth communication, serial profile switching is performed in which after establishing a wireless communication connection in PBAP in S7 shown in the flowchart of Fig. 5, the wireless communication in PBAP is disconnected in S24, and a wireless communication connection in HFP is established in S25. Therefore, if there is a new incoming call to the mobile phone 2 after establishing a wireless communication connection in HFP in S25, or if a new outgoing call process is performed by the operation unit 14, the incoming call history data and outgoing call history data including the incoming and outgoing calls are ultimately its own history data, and are therefore stored in its own memory. Therefore, the control device 12 of the in-vehicle hands-free device 1 can perform wireless communication (simultaneous connection) in PBAP during wireless communication in HFP in order to obtain the latest outgoing and incoming call history data from the mobile phone 2 again.

[0096] However, if simultaneous connections are to be avoided as much as possible, in a serial connection, if the wireless communication connection in HFP is disconnected and a wireless communication connection in PBAP is established, the mobile phone 2 and the in-vehicle hands-free device 1, which constitute one telephone system for hands-free calling, are essentially separated during that time, and a state occurs in which hands-free calling cannot be performed. Therefore, in this embodiment, when a wireless communication connection in HFP is established in S25, the latest outgoing and incoming call history data is acquired and managed by the in-vehicle hands-free device 1 by itself, with only the wireless communication connection in HFP thereafter. This will be described below.

[0097] Returning to the flowchart of Fig. 11, the control device 12 judges whether or not the user has performed a call originating operation by dial key input (S124), and judges whether or not the user has performed a call originating operation by the outgoing call history (S125). Following the flowchart of Fig. 12, the control device 12 judges whether or not the user has performed a call originating operation by the incoming call history (S126), whether or not the user has performed a call originating operation by the phone book (S127), and whether or not the call has been received from the mobile phone network (S128).

[0098] Here, when the control device 12 judges that the user has performed a dialing operation by inputting the dial keys (S124 "YES"), it performs a dialing process to make a call using the telephone number input by the user with the dial keys as the calling telephone number (S129). Then, when the control device 12 ends the dialing process by inputting the dial keys, as shown in Fig. 13B, it erases the dialing history data with the oldest calling date and time among the dialing history data stored in the working memory 16 at that time (S130), and additionally stores the latest dialing history data of the device itself, which represents the call by inputting the dial keys, in the working memory 16 as its own dialing history data (S131).

[0099] That is, when the user operates the dial key to input, for example, a telephone number "09000000100" and performs an operation to make a call using the telephone number "09000000100" as a calling telephone number, the control device 12 additionally stores the calling history data representing the telephone number "09000000100" as its own calling history data in the working memory 16 as shown in FIG. 13B. In this case, the control device 12 stores the date and time acquired by the GPS device of the in-vehicle hands-free device 1 as a time stamp as the calling date and time corresponding to the telephone number "09000000100". That is, in FIG. 13B, the calling date and time of the latest telephone number "09000000100" is the date and time acquired by the GPS device of the in-vehicle hands-free device 1, and the calling dates and times of the remaining four telephone numbers are the dates and times acquired by the clock unit of the mobile phone 2. Note that, when the user performs an operation to display the calling history data from this state, the control device 12 displays the display screen shown in FIG. 15C on the display unit 15.

[0100] In addition, when the control device 12 determines that the user has pressed the "history button" 4a and then the "outgoing call history button" 4b, thereby performing an outgoing call operation using the outgoing call history (S125 "YES"), it refers to the outgoing call history data stored in the working memory 16 (S132), refers to the phonebook data stored in the working memory 16 (S133), and displays an outgoing call operation screen using the outgoing call history on the display unit 15 (S134), as shown in Figures 15B and 15C. In this case, if the outgoing phone number in the outgoing call history data is registered in the phonebook data, the control device 12 displays the registered name corresponding to the phone number on the display unit 15, whereas if the outgoing phone number in the outgoing call history data is not registered in the phonebook data, it displays the phone number on the display unit 15.

[0101] Next, the control device 12 performs a call process to call the telephone number selected by the user as the calling telephone number (S135). Then, when the control device 12 ends the call process based on the call history, it also erases the call history data with the oldest call date and time among the call history data stored in the working memory 16 at that time (S130), and additionally stores the latest call history data of the device itself, which represents a call based on that call history, in the working memory 16 as its own call history data (S131). In this case, too, the control device 12 stores the date and time acquired by the GPS device of the in-vehicle hands-free device 1 as the call date and time corresponding to the calling telephone number as a time stamp.

[0102] In addition, when the control device 12 determines that the user has pressed the "history button" 4a and then the "incoming call history button" 4c to perform a call operation based on the incoming call history (S126 "YES"), it refers to the incoming call history data stored in the working memory 16 (S136), refers to the phonebook data stored in the working memory 16 (S137), and displays a call operation screen based on the incoming call history on the display unit 15 (S138), as shown in Figures 16B and 16C. In this case, if the calling phone number in the incoming call history data is registered in the phonebook data, the control device 12 displays the registered name corresponding to the phone number on the display unit 15, whereas if the calling phone number in the incoming call history data is not registered in the phonebook data, it displays the phone number on the display unit 15.

[0103] Next, the control device 12 performs a call process to call the telephone number selected by the user as the calling telephone number (S139). Then, when the control device 12 ends the call process based on the incoming call history, it also erases the call history data with the oldest call date and time among the call history data stored in the working memory 16 at that time (S130), and additionally stores the latest call history data of the device itself, which represents a call based on the incoming call history, in the working memory 16 as its own call history data (S131). In this case, the control device 12 also stores the date and time acquired by the GPS device of the in-vehicle hands-free device 1 as the call date and time corresponding to the calling telephone number as a time stamp.

[0104] In addition, when the control device 12 determines that the user has pressed the "phonebook button" 4d to perform a call operation using the phonebook (S127 "YES"), it refers to the phonebook data stored in the working memory 16 (S140) and displays a call operation screen using the phonebook on the display unit 15 as shown in FIG. 17B (S141). Next, the control device 12 performs a call process to call a phone number selected by the user from the data as a call phone number (S142). Then, when the control device 12 ends the call process using the phonebook, it also erases the call history data with the oldest call date and time among the call history data stored in the working memory 16 at that time (S130), and additionally stores the latest call history data of the device, which represents a call using the phonebook, in the working memory 16 as its own call history data (S131). In this case, too, the control device 12 stores the date and time acquired by the GPS device of the in-vehicle hands-free device 1 as a time stamp for the call date and time corresponding to the call phone number.

[0105] Furthermore, when the control device 12 determines that a call has been received from the mobile phone network via the mobile phone 2 via the Bluetooth communication unit 13 (S128 "YES"), it performs call processing such as an alert to notify the caller of the call (S143), and when the call processing is completed, it erases the call history data with the oldest call date and time among the call history data stored in the working memory 16 at that time (S144), and additionally stores the latest call history data of its own device representing that call in the working memory 16 as its own call history data (S145).

[0106] That is, when the control device 12 receives the telephone number "09000000200" as an incoming call telephone number from the mobile phone network via the Bluetooth communication unit 13, it additionally stores the incoming call history data representing the telephone number "09000000200" in the working memory 16 as its own incoming call history data.

[0107] In this way, even if a wireless communication connection is not made via PBAP after the wireless communication connection via HFP in S25, when a new incoming call or outgoing call is processed after S1, the device's own outgoing and incoming call history data can be added and displayed on display unit 15. As a result, it is not necessary to simultaneously connect to the HFP and PBAP, and it is not necessary to disconnect the HFP wireless communication connection and connect wireless communication via PBAP after the HFP wireless communication connection is made in S25, so that it is possible to prevent the mobile phone 2 and the in-vehicle hands-free device 1, which have become one telephone system, from being substantially separated.

[0108] Next, a description will be given of the display process of the call history data received via wireless communication in the PBAP and the call history data generated in the outgoing call process and the incoming call process that occur after S25.

[0109] In S25, in the HFP wireless connection state, the mobile phone 2 transmits the incoming call telephone number to the in-vehicle hands-free device 1 when a call is received, but does not transmit the incoming call date and time information. Therefore, the control device 12 stores the date and time acquired by the GPS device of the in-vehicle hands-free device 1 as the incoming call date and time corresponding to the telephone number "09000000200" as a time stamp. That is, in FIG. 14B, the incoming call date and time of the latest telephone number "09000000200" is the date and time acquired by the GPS device of the in-vehicle hands-free device 1, and the incoming call dates and times of the remaining four telephone numbers are the dates and times acquired by the clock unit of the mobile phone 2. When the user performs an operation to display the incoming call history data from this state, the control device 12 causes the display unit 15 to display the display screen shown in FIG. 16C.

[0110] In the above, we have described a case where, when the number of outgoing call history data and incoming call history data that can be stored in the working memory 16 is smaller than the number of outgoing call history data and incoming call history data automatically transferred from the mobile phone 2, the outgoing call history data and incoming call history data with older outgoing call dates and times or incoming call dates and times are discarded, and the outgoing call history data and incoming call history data with newer outgoing call dates and times or incoming call dates and times are preferentially stored in the working memory 16 among the outgoing call history data and incoming call history data automatically transferred from the mobile phone 2. However, when connecting wireless communication via PBAP, the in-car hands-free device 1 may specify the number of items to be automatically transferred to the mobile phone 2 (five in this embodiment), and the outgoing call history data and incoming call history data with newer outgoing call dates and times or incoming call dates and times may be preferentially stored in the working memory 16.

[0111] In the above configuration, when a new call process or a new incoming call process is performed in the in-vehicle hands-free device 1, the oldest outgoing call history data and the oldest incoming call history data stored in the working memory 16 are deleted. However, from the user's point of view, there may be a request as follows, so the control device 12 may perform the following alternative process. This process is required when a wireless communication connection is not established using the PBAP after S25, as in this example.

[0112] In other words, when comparing the date and time kept by the clock unit of mobile phone 2 with the date and time obtained by the GPS device of the car-mounted hands-free device 1, the date and time kept by the clock unit of mobile phone 2 may have a large error and may be inaccurate compared to the date and time obtained by the GPS device. Also, since the user can set it arbitrarily, the user may intentionally set it ahead by a certain amount (for example, 10 minutes) or set it behind.

[0113] Therefore, if the user sets the date and time of the mobile phone 2 forward by a predetermined time, and the in-vehicle hands-free device 1 stores the advanced date and time in the working memory 16, when the outgoing call history data and incoming call history data automatically transferred from the mobile phone 2 and the outgoing call history data and incoming call history data of the in-vehicle hands-free device 1 are rearranged in chronological order from this state, the outgoing call history data and incoming call history data for which a new outgoing call process or a new incoming call process has been performed in the in-vehicle hands-free device 1 will not be displayed in the topmost column on the display screen of the list display, even though they are the latest on the time axis, but will be displayed in a column other than the topmost column (for example, the second or third column). This causes a discrepancy between the time axis stored by the user and the time axis displayed by the display unit 15, causing the user to feel uncomfortable.

[0114] To deal with such a problem, the control device 12 displays the outgoing call history data and incoming call history data automatically transferred from the mobile phone 2 in chronological order in a column other than the top column within the scope of the data, and displays new outgoing call history data and new incoming call history data of the device in the top column. This allows the data to be displayed in harmony with the time axis remembered by the user, and prevents the user from feeling uncomfortable.

[0115] When the control device 12 displays the outgoing call history data and incoming call history data automatically transferred from the mobile phone 2 in chronological order, the control device 12 does not have to sort the data based on the date and time data contained in the outgoing call history data and incoming call history data. If the outgoing call history data and incoming call history data contain outgoing call order data or incoming call order data indicating the order of incoming calls, the control device 12 may display the outgoing call history data and incoming call history data in chronological order.

[0116] Even if the outgoing call order data and incoming call order data are not explicitly included, when data is transmitted from mobile phone 2 in a list format as shown in Figures 7A, 8A, and 9A and received by in-vehicle hands-free device 1, it may be displayed based on the rule that the higher the data, the more recent the data. In other words, mobile phone 2 transmits data in a format that enables in-vehicle hands-free device 1 to identify the actual outgoing call order and incoming call order.

[0117] In this case, for example, depending on the mobile phone 2, if a call is received from person A at 12:00:00 and from person B at 12:00:30, if the time stamp is set to the minute instead of the second, it will be exactly the same 12:00, and this is stored as the incoming call history data of the mobile phone 2. Even if this data is received by the in-vehicle hands-free device 1 and rearranged in chronological order, the order cannot be determined, so it is convenient to have the mobile phone 2 give outgoing call order data and incoming call order data or send it in the above-mentioned list format. This allows the data to be displayed in harmony with the time axis remembered by the user, and prevents the user from feeling uncomfortable.

[0118] In these cases, the date and time data included in the outgoing call history data and incoming call history data becomes ancillary, and the outgoing call order data and incoming call order data described above become the actual incoming call order and outgoing call order of the user. The mobile phone 2 repeats incoming call processing and outgoing call processing in its independent operation, but since it is an independent operation, it can grasp the order of outgoing and incoming calls, and can manage the outgoing and incoming call history in that order. For this reason, regardless of the outgoing call date and time and the incoming call date and time of its own clock unit, outgoing call order data and incoming call order data are added to each outgoing call and each incoming call, and transmitted to the in-vehicle hands-free device 1, and the outgoing and incoming call history data is arranged in the in-vehicle hands-free device 1 based on the incoming call order data and outgoing call order data. Alternatively, the above list, which is constructed by determining the actual outgoing call order and incoming call order at the mobile phone 2 without adding the outgoing call order data and incoming call order data, is transmitted to the in-vehicle hands-free device 1, and the in-vehicle hands-free device 1 arranges the outgoing and incoming call order according to the above rule.

[0119] In this way, if the clock of the mobile phone 2 is set forward or backward at a certain timing, and an outgoing call or incoming call occurs immediately after this, the outgoing call history display and incoming call history display on the mobile phone 2 will be displayed in the actual order, but the outgoing call date and time and incoming call date and time added to each data will be different from this display order. Therefore, if such outgoing call history data is rearranged based on the outgoing call date and time and the incoming call date and time by the in-vehicle hands-free device 1, it will be displayed in a different order from the actual order. For this reason, the above-mentioned outgoing call order data and incoming call order data method, or the list format method, can be said to be convenient for arranging calls in the actual order.

[0120] As a result, the control device 12 can display data on the display unit 15 in the order of actual outgoing calls and incoming calls on the mobile phone 2. After such data processing, when the in-vehicle hands-free device 1 performs outgoing call processing by its own dial key input, outgoing call processing by outgoing call history, outgoing call processing by incoming call history, or outgoing call processing by phonebook data as described above, the control device 12 erases the outgoing call history data with the oldest outgoing call order data or the outgoing call history data considered to be the oldest outgoing call history data stored in the working memory 16 at that time, and additionally stores the latest outgoing call history data of the device representing the outgoing call from that outgoing call history in the working memory 16 as its own outgoing call history data. On the other hand, when a new incoming call processing occurs, the control device 12 erases the outgoing call history data with the oldest outgoing call order data or the incoming call history data considered to be the oldest outgoing call history data stored in the working memory 16 at that time, and additionally stores the latest incoming call history data of the device representing the incoming call from that incoming call history in the working memory 16 as its own incoming call history data.

[0121] In the case of these outgoing call processing and incoming call processing, the control device 12 stores, as a time stamp, the date and time acquired by the GPS device of the in-vehicle hands-free device 1 as the outgoing call date and time corresponding to the outgoing telephone number and the incoming call date and time corresponding to the incoming telephone number. In this way, it is possible to display in harmony with the time axis remembered by the user, and to prevent the user from feeling uncomfortable.

[0122] In addition, when there is a display request for all history data that collectively displays the outgoing call history data and the incoming call history data, the control device 12 needs to perform a predetermined sorting process compared to when only the outgoing call history data or the incoming call history data is displayed. In other words, when the incoming call history data or the outgoing call history data is transmitted from the mobile phone 2 according to the actual time axis so that the latest order can be seen including the outgoing call order data and the incoming call order data as described above, or when the outgoing call history data or the outgoing call history data is transmitted in the above list format without including these data, if the in-vehicle hands-free device 1 displays the data in the order as notified without using the outgoing call date and time and the incoming call date and time included in the received data as a reference as described above, when only the outgoing call history data or the incoming call history data is displayed, the data will be displayed in the order displayed on the mobile phone 2.

[0123] Here, when displaying all the history data, the in-vehicle hands-free device 1 can grasp the latest data among the outgoing call history data and the latest data among the incoming call history data, but it may be difficult to actually specify which of the two latest data is the latest. Therefore, in this example, when displaying all the history data, the control device 12 compares the outgoing call date and time included in the outgoing call history data and the incoming call date and time included in the incoming call history data, and displays the one with the latest date and time as the latest data. For example, in the case of five incoming call history data and five outgoing call history data, the control device 12 sorts the 10 data in order of date and time and displays them in this order. This makes it possible to display the outgoing call history data and the incoming call history data in order almost according to the user's actual time axis in most cases. However, if the time stamp function of the mobile phone 2 is up to "minutes," if a call is made from person A at 12:00:00 and a call is made to person B at 12:00:30, the outgoing call date and the incoming call date and time will be exactly the same, 12:00, so the control device 12 performs a predetermined sorting process in this case, such as displaying the outgoing call as the latest call rather than the incoming call, or vice versa.

[0124] In addition, when the latest order of the three incoming call history data (A to C) received via wireless communication at the PBAP can be determined as described above, and the latest order of the outgoing call history data (D to F) received at the PBAP can be determined, the control device 12 performs a sorting process by comparing the dates and times of the outgoing call history data and the incoming call history data as follows.

[0125] First, the control device 12 compares the dates and times of A and D, placing the newer one first (for example, A), then compares B and D, placing the newer one second (for example, B). Next, it compares C and D, placing the newer one third (for example, D), then compares the dates and times of C and E, placing the newer one fourth (for example, C). Next, as for the remaining E and F, since E is the latest, the control device 12 places E fifth and F sixth. If the compared dates and times are the same, the control device 12 rearranges the calls according to a predetermined rearrangement rule, such as prioritizing outgoing calls over incoming calls, or vice versa.

[0126] In addition, when transferring phonebook data in the mobile phone 2, the data format of the phonebook data needs to be converted into the "vCard" data format defined in the Bluetooth communication standard before transferring it, and the phonebook data is generally updated less frequently than the outgoing call history data and the incoming call history data. For this reason, the control device 12 may first receive the outgoing call history data and the incoming call history data from the mobile phone 2 via the Bluetooth communication unit 13, and then receive the phonebook data from the mobile phone 2 via the Bluetooth communication unit 13. In addition, the control device 12 may receive the outgoing call history data and the incoming call history data from the mobile phone 2 via the Bluetooth communication unit 13, and then receive the phonebook data from the mobile phone 2 via the Bluetooth communication unit 13 only when the user performs a predetermined operation on the operation unit 14.

[0127] In addition, whether to transfer the phone book data by such a user operation or automatically may be set by the user in the in-vehicle hands-free device 1 by selecting manual transfer or automatic transfer, and the transfer process may be performed according to this setting. With the automatic transfer setting set to "no transfer", after the wireless connection in HFP in S9, the user may perform a manual transfer operation to transfer only the phone book data. However, this manual transfer operation disconnects the wireless communication connection in HFP in S9 and establishes a wireless communication connection in PBAP, and when the data transfer is completed, the wireless communication in HFP is reconnected to the mobile phone 2, making it possible to make a hands-free call.

[0128] When this "do not forward" is set, outgoing call history data and incoming call history data, which are updated frequently, can be received with priority over phone book data, which is updated infrequently. Also, because data conversion is not required to transfer outgoing call history data and incoming call history data, but data conversion is required to transfer phone book data, outgoing call history data and incoming call history data, which have a short transfer time, can be received with priority over phone book data, which has a long transfer time. By transferring only outgoing call history data and incoming call history data, the amount of data to be transferred can be reduced. As a result, communication can be performed early using the transfer protocol, and subsequent communication can be performed early using the hands protocol, so that when the mobile phone is brought into a vehicle, the time until a hands-free call can be made can be shortened. Furthermore, whether or not to receive phone book data, which is updated infrequently and has a long transfer time, can be selected as necessary, improving convenience.

[0129] When the user transfers the phone book data as necessary by the above-mentioned manual transfer operation, communication is automatically performed in the Handsfree protocol when the transfer is completed, so that the phone book data can be used to make a hands-free call when making a call, improving convenience. Furthermore, when the phone book data is transferred by the manual transfer operation, only the phone book data is stored in the non-volatile storage memory 17, and the stored data is read out from the storage memory 17 the next time the in-vehicle hands-free device 1 is started and used as the phone book data.

[0130] The control device 12 may store the outgoing call history data, incoming call history data, and phone book data received from the mobile phone 2 in the working memory 16, distinguishing them for each mobile phone 2. In this case, the control device 12 associates the mobile phone 2 with the data stored in the working memory 16, for example, as follows. That is, when storing the outgoing call history data, incoming call history data, and phone book data received from the mobile phone 2 in the working memory 16, the control device 12 generates a link key based on the mobile phone ID individually assigned to the mobile phone 2 and the device ID individually assigned to the in-vehicle hands-free device 1, which are received from the mobile phone 2, and stores the generated link key in the working memory 16 in association with various data. Then, when the control device 12 receives the mobile phone ID from the mobile phone 2 thereafter, the control device 12 generates a link key again based on the received mobile phone ID and device ID, and updates various data stored in the working memory 16 in association with the generated link key.

[0131] Next, a detailed description will be given of the HFP process in S2 in the flowchart of Fig. 5. Fig. 19 is a flowchart showing the details of the flow of the HFP process according to this embodiment.

[0132] When the control unit 102 (hands-free call connection control unit 111) determines that a communication line has been established with the mobile phone 2 present within the Bluetooth communication range, it establishes (starts) wireless communication via HFP (S151) and determines whether the mobile phone 2 is in a call or on standby (S152). Whether the mobile phone 2 is in a call or on standby is notified by wireless communication via HFP, and is received by the in-vehicle hands-free device 1, and is determined based on the received communication state. S151 corresponds to the processing of S2.

[0133] Here, when the control unit 102 (hands-free call connection control unit 111) determines that the mobile phone 2 is not in a call, that is, is in a standby state waiting for an incoming call (S152 “No”), it disconnects (ends) the wireless communication in the connected HFP (S154), and the control unit 102 (data transfer control unit 112) connects the wireless communication in the PBAP (S155). In other words, if the mobile phone 2 is not in a call, the control unit 102 (hands-free call connection control unit 111) automatically disconnects the wireless communication in the connected HFP immediately and automatically connects the wireless communication in the PBAP, thereby causing the Bluetooth communication unit 13 to receive the outgoing call history data, incoming call history data, and phonebook data transmitted from the mobile phone 2.

[0134] Furthermore, when the control unit 102 (hands-free call connection control unit 111) determines that the mobile phone 2 is in a call (S152 "YES"), it maintains wireless communication in HFP, assuming that there is a possibility of executing a hands-free call for that call using the in-vehicle hands-free device 1. Whether or not to execute this call basically depends on the mobile phone 2, and when the mobile phone 2 establishes a wireless communication connection in HFP during a call, it may automatically transmit the received voice to the Bluetooth communication unit 13, or may transmit the received voice to the Bluetooth communication unit 13 by operating the mobile phone 2.

[0135] Then, the control unit 102 (hands-free call connection control unit 111) judges whether the mobile phone 2 has ended the call (S153), and when it judges that the mobile phone 2 has ended the call (S153 "Yes"), it disconnects (ends) the wireless communication in the connected HFP (S154 "No"), and the control unit 102 (data transfer control unit 112) connects the wireless communication in the PBAP (S155). In other words, if the mobile phone 2 is in a call, the control unit 102 (hands-free call connection control unit 111) disconnects the wireless communication in the connected HFP after the call ends and connects the wireless communication in the PBAP, so that the outgoing call history data, incoming call history data, and phonebook data transmitted from the mobile phone 2 after the user ends the hands-free call are received by the Bluetooth communication unit 13. Note that S152 and S153 correspond to the processes between S3 and S4.

[0136] When the mobile phone 2 is connected to the in-vehicle hands-free device 1 in this way, the in-vehicle hands-free device 1 determines whether the mobile phone 2 is on a call, and if it is, switching to a wireless communication connection via PBAP would prevent the call from switching to a hands-free call, so the in-vehicle hands-free device 1 maintains wireless communication via HFP and does not establish a wireless communication connection via PBAP during the call. Then, when it is determined that the call has ended, the wireless communication via HFP is disconnected and a wireless communication connection via PBAP is established. As a result, when the mobile phone 2 is on a call by itself, it is possible to smoothly switch to a hands-free call.

[0137] The control device 12 may receive and store, as incoming call history data, incoming call histories that have been answered and incoming call histories that have not been answered (missed calls) separately from each other. Figs. 20A to 20C are diagrams showing another example of the transition of the display screen when the user performs an outgoing call operation from the incoming call history according to this embodiment. When the control device 12 determines that an outgoing call operation has been performed from the incoming call history by the user pressing the "history button" 4a and then pressing the "incoming call history button" 4c, the control device 12 refers to the incoming call history data stored in the working memory 16 and refers to the phonebook data stored in the working memory 16, and displays an outgoing call operation screen from the incoming call history on the display unit 15 as shown in Figs. 20B and 20C, and displays either an icon figure (a figure made up of a combination of a handset and an arrow) that indicates that the incoming call is answered or an icon figure (a figure made up of a combination of a handset and an X) that indicates that the incoming call is not answered (missed call) for each data.

[0138] In this embodiment, the outgoing call history data, incoming call history data, and phone book data transferred from the mobile phone 2 are stored in the working memory 16, and the phone book data is stored in the storage memory 17. However, the outgoing call history data, incoming call history data, and phone book data transferred from the mobile phone 2 may be stored in the storage memory 17. In such a configuration, the outgoing call history data, incoming call history data, and phone book data stored in the storage memory 17 are retained even when the power of the in-vehicle hands-free device 1 is turned off.

[0139] As described above, the in-vehicle hands-free device 1 of this embodiment performs a time-division serial connection between the HFP and the PBAP in order to eliminate simultaneous connections between the HFP and the PBAP as much as possible as a more reliable processing procedure for the HFP and the PBAP. This makes it possible to reliably and stably perform communication processing for mobile phones compatible with the HFP and PBAP from many manufacturers. In addition, it is possible to execute processing between the PBAP and the HFP with simple processing without complicating the processing in the in-vehicle hands-free device 1.

[0140] In addition, the in-vehicle hands-free device 1 of the present embodiment transmits an emergency call via the mobile phone 2 when the conditions for transmitting an emergency call are satisfied, and when the end of the call with the destination of the emergency call is detected, performs control to transfer emergency history data indicating a history of the emergency call from the mobile phone 2 to the in-vehicle hands-free device 1. Then, after performing control to transfer the emergency history data, the in-vehicle hands-free device 1 of the present embodiment performs control to display a call operation screen that allows a call operation based on the call history of the emergency call in response to a user's operation. This allows the user to easily make a call to the same emergency call destination again after transmitting an emergency call in an emergency such as an accident. For example, since redialing can be easily performed in an emergency, the user can also talk to the operator who was contacted immediately before again. This improves the user's convenience when an accident occurs.

[0141] Furthermore, when the in-vehicle hands-free device 1 of this embodiment makes a call to or receives a call from the mobile phone network during wireless communication connection via HFP after wireless communication via PBAP is disconnected, it erases the outgoing call history data or incoming call history data with the oldest outgoing call date / time or the oldest incoming call date / time among the outgoing call history data or incoming call history data stored in the working memory 6 at that time, and additionally stores the outgoing call history data or incoming call history data of its own device in the working memory 6. This makes it possible to store the latest outgoing call history data or incoming call history data of its own device every time a call is made to or a call is received from the mobile phone network.

[0142] Furthermore, after establishing a communication line with the mobile phone 2, the in-vehicle hands-free device 1 of this embodiment connects the HFP in S2 and then determines whether the mobile phone 2 is in a call, and if the mobile phone 2 is in a call, after the call ends, connects wireless communication via the PBAP to receive outgoing call history data, incoming call history data, and phone book data from the mobile phone 2. This allows hands-free calling to be performed without being affected by the transfer of outgoing call history data, incoming call history data, and phone book data from the mobile phone 2.

[0143] Furthermore, when the in-vehicle hands-free device 1 of this embodiment establishes a Bluetooth communication line with the mobile phone 2 and receives from the mobile phone 2 outgoing call history data and incoming call history data that were stored before the mobile phone 2 established the Bluetooth communication line, the in-vehicle hands-free device 1 stores the outgoing call history data and incoming call history data in the working memory 16 in the same manner as the outgoing call history data and incoming call history data of the device itself, and thereafter, enables outgoing call operations using the outgoing call history data and incoming call history data stored in the working memory 16. This allows the user to select a desired phone number from the outgoing call history data and incoming call history data automatically transferred from the mobile phone 2 and make a call, and also to select a desired phone number from the outgoing call history data and incoming call history data of the device itself and make a call, improving convenience.

[0144] Furthermore, when a display request for outgoing call history data or incoming call history data occurs, the in-vehicle hands-free device 1 of this embodiment displays the registered name corresponding to the telephone number if the same telephone number as the outgoing call history data or incoming call history data stored in the working memory 16 is stored. This makes it possible to display the outgoing call history data or incoming call history data received from the mobile phone 2 by the registered name stored in the phone book data.

[0145] Moreover, the in-vehicle hands-free device 1 of this embodiment displays the outgoing call history data of its own device as the outgoing call history data with the latest outgoing date and time on the display screen that displays the outgoing call history data in a list every time it performs an outgoing call process. Moreover, the in-vehicle hands-free device 1 of this embodiment displays the incoming call history data of its own device as the incoming call history data with the latest incoming call date and time on the display screen that displays the incoming call history data in a list every time it performs an incoming call process. This makes it possible to prevent the user from feeling uncomfortable due to a difference in date and time between the devices, even if the date and time acquired by the mobile phone 2 and the date and time acquired by the in-vehicle hands-free device 1 do not match, and the outgoing date and time of the outgoing call history data or the incoming call history data of the incoming call history data automatically transferred from the mobile phone 2 do not match on the time axis with the outgoing date and time of the outgoing call history data or the incoming call history data of the device.

[0146] Moreover, the in-vehicle hands-free device 1 of this embodiment stores outgoing call history data, incoming call history data, and phone book data in the working memory 16 separately for each mobile phone 2. This allows the outgoing call history data, incoming call history data, and phone book data to be managed for each mobile phone 2. Moreover, the in-vehicle hands-free device 1 of this embodiment stores outgoing call history data, incoming call history data, and phone book data in the storage memory 17 separately for each mobile phone 2. This eliminates the need to receive phone book data from the mobile phone 2 every time the device is turned on, and allows the user to quickly use the phone book data stored and held in correspondence with his or her own mobile phone 2, significantly improving the convenience of using the phone book function.

[0147] Furthermore, when the in-vehicle hands-free device 1 of this embodiment displays all call history data, incoming call history data, and missed call history data together, it displays only the phone number with the latest call date and time for call history data with the same (duplicate) calling phone number. This allows the history information to be increased.

[0148] The programs executed by the in-vehicle hands-free device 1 of the above-mentioned embodiments are provided by being pre-installed in a ROM, etc. The programs executed by the in-vehicle hands-free device 1 of each of the above-mentioned embodiments may be provided by being recorded in a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a digital versatile disk (DVD) in the form of an installable or executable file.

[0149] Furthermore, the programs executed by the in-vehicle hands-free device 1 of each of the above-mentioned embodiments may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Also, the programs executed by the in-vehicle hands-free device 1 of each of the above-mentioned embodiments may be provided or distributed via a network such as the Internet.

[0150] Second Embodiment Fig. 1 is a diagram showing an example of a usage form of an in-vehicle hands-free device 1A according to this embodiment. As shown in Fig. 1, the in-vehicle hands-free device 1A of this embodiment can be mounted on a vehicle 3. The in-vehicle hands-free device 1A is communicatively connected to a mobile phone 2. Note that the same functions as those in the first embodiment are given the same reference numerals, and detailed description thereof will be omitted.

[0151] In-vehicle hands-free device 1A connects to a mobile phone network via mobile phone 2. This allows, for example, the driver of vehicle 3 to make and receive calls by operating in-vehicle hands-free device 1A without operating mobile phone 2. In-vehicle hands-free device 1A may be realized, for example, as one function of a hands-free device mounted in vehicle 3.

[0152] The hardware configuration of the in-vehicle hands-free device 1A according to this embodiment is similar to that of the in-vehicle hands-free device 1 according to the above embodiment, and therefore a detailed description thereof will be omitted.

[0153] Next, the details of the functions of the in-vehicle hands-free device 1A of this embodiment will be described. FIG. 21 is a diagram showing an example of the functions of the in-vehicle hands-free device 1A according to this embodiment. The functions of the in-vehicle hands-free device 1A are not limited to the example of FIG. 21, and the in-vehicle hands-free device 1A may further have other functions. In the example of FIG. 21, the in-vehicle hands-free device 1A of this embodiment includes a reception unit 101, a control unit 120, a data receiving unit 103, and a storage unit 104.

[0154] In this embodiment, the functions of the reception unit 101, the control unit 120, and the data receiving unit 103 are realized by the control device 12 reading and executing a program from the storage memory 17. However, this is not limited to the above, and for example, some or all of the functions of the reception unit 101, the control unit 120, and the data receiving unit 103 may be realized by a dedicated hardware circuit. Also, the storage unit 104 is realized by the storage memory 17, for example.

[0155] The reception unit 101 and the data receiving unit 103 are similar to those of the in-vehicle hands-free device 1 of the first embodiment. That is, the in-vehicle hands-free device 1A of the present embodiment is similar to the in-vehicle hands-free device 1 of the first embodiment, except that it includes a control unit 120 instead of the control unit 102.

[0156] The control unit 120 performs various controls related to the hands-free function. Like the control unit 102 in the first embodiment, the control unit 120 has a function of connecting to the mobile phone 2 so as to enable hands-free calling, and a function of controlling data transfer using a transfer protocol for realizing the transfer of incoming call history data, outgoing call history data, and phone book data stored in the mobile phone 2 when the mobile phone 2 is in a wireless connection area.

[0157] The transfer protocol is PBAP (Phone Book Access Profile). When the connection in PBAP is interrupted during the transfer of history data or phone book data, the control unit 120 displays an error and causes the display unit 15 to display a reconnection screen for receiving an input instructing reconnection in PBAP. Then, when the control unit 120 receives an input instructing reconnection in PBAP via the reconnection screen, it executes reconnection in PBAP. Furthermore, when the mobile phone 2 is set to prohibit or limit the transfer of history data or phone book data, the control unit 120 causes the display unit 15 to display information (e.g., a message) indicating that the transfer of history data or phone book data is not possible. In this example, it is assumed that security is set in the mobile phone 2 to prohibit or limit the transfer of both history data and phone book data. Details of various functions of the control unit 120 will be described later.

[0158] Fig. 22 is a diagram showing an example of detailed functions of the control unit 120. As shown in Fig. 22, the control unit 120 has a hands-free telephone call connection control unit 111, a data transfer control unit 122, and a display control unit 123. Note that the functions of the control unit 120 are not limited to these, and the control unit 120 may further have other functions for realizing the hands-free function. The hands-free telephone call connection control unit 111 is the same as in the first embodiment.

[0159] The data transfer control unit 122 controls data transfer in the transfer protocol (PBAP in this example). In this example, the data transfer control unit 122 also has a function of generating all history data that compiles outgoing call history data, incoming call history data, and missed call history data transferred from the mobile phone 2 and displays them in order of the latest call. However, this is not limited to the above, and for example, the control unit 120 may have a function of generating all history data separately from the data transfer control unit 122. The display control unit 123 controls the display of various screens on the display unit 15. For example, the display control unit 123 controls the display of the reconnection screen, the message, and the like on the display unit 15. Specific details of these will be described later.

[0160] In this embodiment, the various functions of the in-vehicle hands-free device 1A are realized by one device, but the present invention is not limited to this, and the various functions of the in-vehicle hands-free device 1A may be distributed among multiple devices. In other words, the various functions of the in-vehicle hands-free device 1A may be realized by a system (hands-free system) composed of multiple devices.

[0161] Next, the operation of the above-mentioned configuration will be described. In this embodiment, the mobile phone 2 already holds (stores) 20 outgoing call history data, 20 incoming call history data, and 20 missed call history data, which are the maximum number that can be stored, and the description will be given on the premise that in this state, a user carrying the mobile phone 2 approaches the vehicle 3, gets in the vehicle, and turns on the ACC switch, causing the mobile phone 2 to enter the Bluetooth communication range of the in-vehicle hands-free device 1A.

[0162] First, a procedure in which the control device 12 in the in-vehicle hands-free device 1A receives outgoing call history data, incoming call history data, missed call history data, and phone book data from the mobile phone 2 will be described with reference to Fig. 23. Note that the user pre-registers the mobile phone 2 with which Bluetooth communication will be performed in the in-vehicle hands-free device 1A.

[0163] For example, the user inputs a four-digit password for each mobile phone 2 into the in-vehicle hands-free device 1A at the time of initial communication setting. The in-vehicle hands-free device 1A and the mobile phone 2 generate a link key used for connecting with each other and hold the link key. The in-vehicle hands-free device 1A selects the mobile phone 2 to be connected for communication by authenticating the link key at the time of initial connection. In other words, communication connection in HFP and communication connection in PBAP are not performed between the in-vehicle hands-free device 1A and an unregistered mobile phone. Basically, the mobile phone 2 of the owner of the vehicle 3 is preregistered, and Bluetooth communication is performed between the mobile phone 2 and the in-vehicle hands-free device 1A. Note that the above-mentioned method for preregistering the mobile phone 2 to be communicated with by the in-vehicle hands-free device 1A is one example, and is not limited thereto.

[0164] In this example, it is assumed that a plurality of mobile phones 2 to be communication connection targets are registered in the in-vehicle hands-free device 1A. In addition, for example, a user operates the operation unit 14 to set priorities in advance for the plurality of mobile phones 2, and the work memory 16 or the storage memory 17 stores the priorities. For example, some drivers may own a plurality of mobile phones 2, so the in-vehicle hands-free device 1A allows registration of a plurality of mobile phones 2 in this way.

[0165] As a premise of this example, the Bluetooth communication unit 13 of the in-vehicle hands-free device 1A supports both the HFP wireless communication protocol and the PBAP wireless communication protocol, and can connect these two profiles to a simultaneous connection (multi-profile connection). However, this simultaneous connection process is intentionally not performed. The reason for not performing the simultaneous connection process is the same as that of the in-vehicle hands-free device 1 of the first embodiment.

[0166] In the in-vehicle hands-free device 1A of this example, like the in-vehicle hands-free device 1 of the first embodiment described above, as a more reliable processing procedure for wireless communication via HFP and wireless communication via PBAP, in order to eliminate simultaneous connections between wireless communication via HFP and wireless communication via PBAP as much as possible, the wireless communication via HFP and the wireless communication via PBAP are serially connected in a time-separated manner.

[0167] Returning to the explanation, the control unit 120 (hands-free call connection control unit 111) selects the mobile phone 2 with the highest priority as a communication connection target for wireless communication in HFP (S21). Here, in this example, without first performing communication connection in PBAP, first, initial communication in HFP is automatically attempted and connection is started.

[0168] Next, the control unit 120 (hands-free call connection control unit 111) executes a process of automatically connecting the initial communication in HFP to the selected mobile phone 2 (S22). In addition, the control unit 120 (hands-free call connection control unit 111) determines whether or not the wireless communication connection in HFP has been successful (S23).

[0169] When the control unit 120 (hands-free call connection control unit 111) determines that the wireless communication connection in the HFP has been successful (S23 "YES"), it automatically disconnects the connected wireless communication in the HFP (S24).

[0170] Next, the control unit 120 judges whether or not security that prohibits or limits the transfer of history data or phone book data is set in the mobile phone 2 (S25). In this example, the control unit 120 judges whether or not security that prohibits or limits the transfer of history data and phone book data is set in the mobile phone 2. This judgment may be performed, for example, by the data transfer control unit 122, or may be performed by another function of the control unit 120. An example of security that prohibits or limits the transfer of history data and phone book data in the mobile phone 2 is a setting that prohibits access to the memory of the mobile phone 2.

[0171] If the determination result of S25 is positive (S25 "YES"), the control unit 120 (display control unit 123) controls the display unit 15 to display a message indicating that the transfer is NG (S26). This message may include the reason why the transfer is NG. In this way, the user can know the reason why the history data or phone book data cannot be downloaded, thereby improving user convenience. In addition, the owner of the mobile phone 2 can rest assured that the history data or phone book data in the mobile phone 2 will not be transferred unintentionally to the in-vehicle hands-free device 1A. After that, the process proceeds to S45 described later.

[0172] In this example, the control unit 120 performs control to display a message when security that prohibits or limits the transfer of history data and phone book data is set in the mobile phone 2, but is not limited to this. For example, the control unit 120 may perform control to display a message indicating that the transfer of one of the history data and the phone book data is not allowed when security that prohibits or limits the transfer of the one of the history data and the phone book data is set in the mobile phone 2.

[0173] If the determination result in S25 is negative (S25 "No"), the control unit 120 (data transfer control unit 122) automatically establishes wireless communication via PBAP with the mobile phone 2 with which the wireless communication connection via HFP has been successful (S27).

[0174] Next, the control unit 120 (data transfer control unit 122) transmits a history data transfer request to the mobile phone 2 to start the transfer process of the history data (in this example, outgoing call history data, incoming call history data, and missed call history data) (S28).

[0175] Upon receiving the history data transfer request, the mobile phone 2 transfers the history data to the in-vehicle hands-free device 1A by Bluetooth communication conforming to the PBAP. The control unit 120 (data transfer control unit 122) stores the history data transferred (downloaded) from the mobile phone 2 in the working memory 16 or the storage memory 17.

[0176] During the transfer of the history data, the control unit 120 (data transfer control unit 122) judges whether the connection in the PBAP has been interrupted (S29). When the control unit 120 (data transfer control unit 122) judges that the PBAP connection has been interrupted (S29 "YES"), the control unit 120 (data transfer control unit 122) interrupts the transfer of the history data (S30). Then, the control unit 120 (display control unit 123) performs control to display an error and a reconnection screen for receiving an input instructing reconnection in the PBAP on the display unit 15 (S31). For example, the reconnection screen may display an icon or button for receiving an input instructing reconnection. When the icon or the like is pressed and an input instructing reconnection is received (S32 "YES"), the control device 12 (data transfer control unit 122) reconnects the wireless communication with the mobile phone 2 by the PBAP (S33). Then, the control device 12 (data transfer control unit 122) resumes the transfer of the history data (S34). After that, the process from S29 onwards is performed. The history data transfer may be resumed in any manner in S34. For example, the history data transfer may be resumed from where it was interrupted, or the history data transfer may be restarted from the beginning.

[0177] In this way, when the connection in the PBAP is interrupted during the transfer of history data, the control unit 120 displays an error and displays a reconnection screen for receiving an input instructing reconnection in the PBAP. Then, when the control unit 120 receives an input instructing reconnection in the PBAP via the reconnection screen, it executes reconnection in the PBAP. With this configuration, the user can know that the connection in the PBAP has been interrupted midway during the transfer of history data (occurrence of an error), and the user can select whether or not to execute reconnection in the PBAP. This improves user convenience. Also, for example, the reconnection screen may display an icon or the like for receiving an input instructing cancellation of the reconnection, and when an input instructing cancellation of the reconnection is received, the control unit 120 (data transfer control unit 122) may cancel the reconnection in the PBAP.

[0178] In the above S29, when it is determined that the PBAP connection is not interrupted (S29 "No"), the control unit 120 (data transfer control unit 122) determines whether the transfer of the history data is completed (S35). When it is determined that the transfer of the history data is completed (S35 "YES"), the control unit 120 (data transfer control unit 122) transmits a phone book data transfer request to the mobile phone 2 to start the transfer process of the phone book data (S36).

[0179] Upon receiving the request to transfer the phone book data, the mobile phone 2 transfers the phone book data to the in-vehicle hands-free device 1A by Bluetooth communication conforming to the PBAP. The control unit 120 (data transfer control unit 122) stores the phone book data transferred from the mobile phone 2 in the working memory 16 or the storage memory 17.

[0180] During the transfer of the telephone directory data, the control unit 120 (data transfer control unit 122) determines whether the connection in the PBAP has been interrupted (S37). When the control unit 120 (data transfer control unit 122) determines that the PBAP connection has been interrupted (S37 "YES"), it interrupts the transfer of the telephone directory data (S38). Then, the control unit 120 (display control unit 123) performs control to display an error and a reconnection screen for receiving an input instructing reconnection in the PBAP on the display unit 15 (S39). When an input instructing reconnection is received via the reconnection screen (S40 "YES"), the control unit 120 (data transfer control unit 122) reconnects the wireless communication with the mobile phone 2 by the PBAP (S41). Then, the control unit 120 (data transfer control unit 122) resumes the transfer of the telephone directory data (S42). After that, the process from S37 onwards is performed.

[0181] In this way, if the connection in PBAP is interrupted during the transfer of phone book data, the control unit 120 displays an error and displays a reconnection screen for receiving an input instructing reconnection in PBAP. Then, if the control unit 120 receives an input instructing reconnection in PBAP via the reconnection screen, it executes reconnection in PBAP. With this configuration, the user can know that the connection in PBAP was interrupted midway during the transfer of phone book data, and the user can select whether or not to reconnect in PBAP. This improves user convenience.

[0182] In this embodiment, when the connection via PBAP is interrupted during data transfer for both history data and phone book data, a reconnection screen is displayed. However, the present invention is not limited to this. For example, the above control may be performed for only one of the history data and phone book data.

[0183] In the above S37, when it is determined that the PBAP connection is not interrupted (S37 "No"), the control unit 120 (data transfer control unit 122) determines whether or not the transfer of the phone book data is completed (S44). When it is determined that the transfer of the phone book data is completed (S44 "YES"), the control unit 120 (data transfer control unit 122) disconnects the wireless communication with the mobile phone 2 by the PBAP (S44).

[0184] Next, the control unit 120 (data transfer control unit 122) automatically connects the mobile phone 2 to wireless communication using HFP again (S45).

[0185] Then, when HFP wireless communication with the mobile phone 2 is established, the control unit 120 (hands-free call connection control unit 111) transitions to hands-free (HF) standby processing (S46). During the hands-free standby processing, the in-vehicle hands-free device 1A is in a state in which it is possible to make or receive calls via the mobile phone 2. The hands-free standby processing continues until the power supply of the in-vehicle hands-free device 1A is cut off or the HFP wireless communication with the mobile phone 2 is terminated. The HFP wireless communication with the mobile phone 2 is terminated when the user performs a disconnection operation on the in-vehicle hands-free device 1A or the mobile phone 2, or when the mobile phone 2 leaves the Bluetooth communication range of the in-vehicle hands-free device 1A, etc.

[0186] In this manner, in this embodiment, the wireless communication is automatically switched to serial communication in the order of HFP→PBAP→HFP. This makes it possible to reliably and stably perform communication processing for mobile phones of many manufacturers that support wireless communication in HFP and wireless communication in PBAP. In addition, this method can reduce the complexity of software processing in the in-vehicle hands-free device 1A.

[0187] Furthermore, when the control unit 120 (hands-free call connection control unit 111) determines that the wireless communication connection via HFP was not successful (failed) (S23 “No”), it determines whether or not there is a mobile phone 2 with the next highest priority (S227).

[0188] If the control unit 120 (hands-free call connection control unit 111) determines that a mobile phone 2 with the next highest priority exists (S227 "YeS"), it selects the mobile phone 2 with the next highest priority as the wireless communication connection target (S228), returns to S22, and repeats the above-mentioned processing.

[0189] Moreover, when the control unit 120 (hands-free telephone connection control unit 111) determines that there is no mobile phone 2 with the next highest priority (S227 "No"), it ends the process of this flowchart.

[0190] The transfer process of the outgoing call history data, incoming call history data, and missed call history data described above with reference to FIG. 23 etc. is similar to that of the in-car hands-free device 1 of the first embodiment.

[0191] As described above, the in-vehicle hands-free device 1A of this embodiment performs a time-division serial connection between the HFP and the PBAP in order to eliminate simultaneous connections between the HFP and the PBAP as much as possible as a more reliable processing procedure for the HFP and the PBAP. This makes it possible to reliably and stably perform communication processing for mobile phones compatible with the HFP and PBAP of many manufacturers. In addition, it is possible to execute processing between the PBAP and the HFP with simple processing without complicating the processing in the in-vehicle hands-free device 1A.

[0192] Furthermore, when the connection at the PBAP is interrupted during the transfer of history data or phonebook data, the in-vehicle hands-free device 1A of this embodiment displays an error and displays a reconnection screen for receiving an input instructing reconnection at the PBAP. Then, when the in-vehicle hands-free device 1A receives an input instructing reconnection at the PBAP via the reconnection screen, it executes reconnection at the PBAP. With this configuration, the user can know that the connection at the PBAP was interrupted midway during the transfer of history data or phonebook data, and can select whether or not to execute reconnection at the PBAP. This improves user convenience.

[0193] Furthermore, when security that prohibits or limits the transfer of history data or phone book data is set in the mobile phone 2, the in-vehicle hands-free device 1A of this embodiment displays a message indicating that the transfer of history data or phone book data is not possible. This message may include the reason why the transfer is not possible. In this way, the user can know the reason why the history data or phone book data cannot be downloaded, improving user convenience. Furthermore, the owner of the mobile phone 2 can rest assured that the history data or phone book data in the mobile phone 2 will not be transferred unintentionally to the in-vehicle hands-free device 1A.

[0194] (Third embodiment) Next, a third embodiment will be described. In this embodiment, the procedure for generating all the history data is different from that of the first embodiment. More specifically, the control unit 120 (data transfer control unit 122) of this embodiment is different from that of the first embodiment in that, when the mobile phone 2 supports a full history request for transferring the history data all at once, the control unit 120 transfers the history data all at once and displays the transferred history data on the display unit 15. Here, the full history request is an example of a bulk transfer request according to the present disclosure.

[0195] More specifically, when the mobile phone 2 does not support the full history request, the control unit 120 (data transfer control unit 122) transfers a predetermined number of the latest incoming call history data, the latest outgoing call history data, and the latest missed call history data in order from the most recent, and displays the full history data (full outgoing and incoming call history) generated based on the date and time information set in each of the transferred incoming call history data, outgoing call history data, and missed call history data as the above history data on the display unit 15. As described above, the full history data is data that displays the outgoing call history data, incoming call history data, and missed call history data collectively in order of the most recent.

[0196] Furthermore, when the mobile phone 2 does not support the full history request and date and time information is not set in at least one of the incoming call history data, outgoing call history data, and missed call history data included in the history data, the control unit 120 (data transfer control unit 122) transfers a predetermined number of each of the incoming call history data, outgoing call history data, and missed call history data, and displays the full history data generated based on the order of reception of each of the transferred incoming call history data, outgoing call history data, and missed call history data as the above-mentioned history data on the display unit 15. The full history data in this case is data in which the outgoing call history data, incoming call history data, and missed call history data are collected and displayed in the order of reception.

[0197] Fig. 24 is a diagram showing an example of a procedure in which the control device 12 receives history data including outgoing call history data, incoming call history data, and missed call history data, and phone book data from the mobile phone 2 in the in-vehicle hands-free device 1A of this embodiment. The following mainly describes the differences from the first embodiment described above, with reference to Fig. 24. Explanations of parts that overlap with the first embodiment described above will be omitted as appropriate.

[0198] The processing of S401-S404 in Fig. 24 is similar to the processing of S21-S24 in Fig. 23, and therefore description thereof will be omitted. In S405, the control unit 120 (data transfer control unit 122) determines whether the mobile phone 2 supports the full history request.

[0199] If the result of S405 is positive (S405 "YES"), the control unit 120 (data transfer control unit 122) automatically establishes wireless communication via PBAP with the mobile phone 2 with which the wireless communication connection via HFP has been successful (S406).

[0200] Next, the control unit 120 (data transfer control unit 122) transmits a full history request to the mobile phone 2 in order to transfer the history data all at once (S407).

[0201] The mobile phone 2 that has received the full history request transfers the history data collectively to the in-vehicle hands-free device 1A by Bluetooth communication conforming to PBAP. The control unit 120 (data transfer control unit 122) stores the history data transferred from the mobile phone 2 in the working memory 16 or the storage memory 17. Then, the control unit 120 (data transfer control unit 122) generates the full history data (S408). Here, if date and time information is set for each of the incoming call history data, outgoing call history data, and missed call history data included in the history data transferred from the mobile phone 2, the control unit 120 (data transfer control unit 122) generates the full history data that compiles and displays the outgoing call history data, incoming call history data, and missed call history data in the latest time order based on the date and time information. On the other hand, if date and time information is not set for each of the incoming call history data, outgoing call history data, and missed call history data included in the history data transferred from the mobile phone 2, the control unit 120 (data transfer control unit 122) generates the full history data based on the order of reception of each of the incoming call history data, outgoing call history data, and missed call history data. In this case, the total history data is data that displays the outgoing call history data, incoming call history data, and missed call history data in the order in which they were received. The timing for generating the total history data is arbitrary and can be changed as desired according to design conditions, etc. For example, the total history data may be generated after the transfer of the phone book data is completed.

[0202] On the other hand, if the result of S405 is negative (S405 "No"), the control unit 120 (data transfer control unit 122) transmits a history data transfer request to the mobile phone 2 to transfer a predetermined number of each of the outgoing call history data, incoming call history data, and missed call history data (S409). Upon receiving this history data transfer request, the mobile phone 2 transfers a predetermined number of each of the outgoing call history data, incoming call history data, and missed call history data to the in-vehicle hands-free device 1A by Bluetooth communication conforming to PBAP. The control unit 120 (data transfer control unit 122) stores the history data transferred from the mobile phone 2 in the working memory 16 or the storage memory 17. Then, the control unit 120 (data transfer control unit 122) generates all the history data based on the date and time information set in the history data or the order in which the history data was received (S410). More specifically, when date and time information is set for each of the outgoing call history data, incoming call history data, and missed call history data included in the history data transferred from the mobile phone, the control unit 120 (data transfer control unit 122) generates all history data based on the date and time information. The all history data is data for displaying the outgoing call history data, incoming call history data, and missed call history data together in the order of the latest calls. On the other hand, when date and time information is not set for each of the incoming call history data, outgoing call history data, and missed call history data included in the history data transferred from the mobile phone 2, the control unit 120 (data transfer control unit 122) generates all history data based on the order in which the incoming call history data, outgoing call history data, and missed call history data were received.

[0203] That is, according to this embodiment, even if the mobile phone does not support the full history request, the full history data can be generated. Furthermore, even if date and time information is not set in the history data transferred from the mobile phone 2, the full history data can be generated based on the order of reception of the incoming call history data, outgoing call history data, and missed call history data included in the history data. This improves the convenience of the user who uses the in-vehicle hands-free device 1A.

[0204] Next, when the transfer process of the history data is completed, the control unit 120 (data transfer control unit 122) next transmits a telephone directory data transfer request to the mobile phone 2 so as to start the transfer process of the telephone directory data (S411).

[0205] Upon receiving the request to transfer the phone book data, the mobile phone 2 transfers the phone book data to the in-vehicle hands-free device 1A by Bluetooth communication conforming to the PBAP. The control unit 120 (data transfer control unit 122) stores the phone book data transferred from the mobile phone 2 in the working memory 16 or the storage memory 17.

[0206] When the transfer process of the telephone directory data is completed, the control unit 120 (data transfer control unit 122) disconnects the wireless communication with the mobile phone 2 by the PBAP (S412).

[0207] Next, the control unit 120 (hands-free call connection control unit 111) automatically connects wireless communication by HFP to the mobile phone 2 again (S413). Then, when wireless communication by HFP with the mobile phone 2 is established, the control unit 120 (hands-free call connection control unit 111) transitions to hands-free (HF) standby processing (S414).

[0208] The configuration of the first embodiment and the configuration of this embodiment can be arbitrarily combined. For example, the control unit 120 according to this embodiment may be configured to control the display of a reconnection screen on the display unit 15, similarly to the first embodiment.

[0209] (Other embodiments) The present disclosure is not limited to the above-described embodiments, but can be modified or expanded as follows.

[0210] For example, the calling operation screen that allows calling operation based on the calling history of the emergency call described above may display a preregistered telephone number or a registered name as a contact that allows calling operation. For example, after the transfer of the emergency history data described above is completed, the control unit 102 (display control unit 114) may control the display unit 15 to display the calling operation screen shown in FIG. 25B when the control unit 102 receives a press of the "History" button from the screen of FIG. 25A. In the example of FIG. 25B, the preregistered telephone number or registered name is displayed higher than the calling history of the emergency call, but the display mode of the preregistered telephone number or registered name is not limited to this, and any display mode of the preregistered telephone number or registered name may be used. For example, the preregistered telephone number or registered name may be displayed lower than the calling history of the emergency call.

[0211] In addition, in the example of FIG. 25B, the contact information for an insurance company is pre-registered as the contact information for emergencies, but this is not limited to the above, and the phone number or registered name to be pre-registered is arbitrary. For example, the contact information for family members, workplace, school, car manufacturer, police, fire department, etc. may be pre-registered.

[0212] According to the above embodiment, the telephone number or registered name pre-registered as an emergency contact is displayed together with the emergency call history, which has the advantageous effect of facilitating the operation of making a call in an emergency.

[0213] Each of the in-vehicle hands-free device 1 and the in-vehicle hands-free device 1A may be configured as a dedicated hands-free device that mainly realizes the hands-free function, or may be a device equipped with a hands-free function in a vehicle audio device that plays CDs or radio. Also, each of the in-vehicle hands-free device 1 and the in-vehicle hands-free device 1A may be configured to be portable (portable type).

[0214] The configuration between the mobile phone 2 and the in-vehicle hands-free device 1 or the in-vehicle hands-free device 1A is not limited to Bluetooth communication, but may be other short-range wireless communication, or may be wired communication.

[0215] The outgoing call history data, incoming call history data, and phone book data received from the mobile phone 2 may be stored in the storage memory 17, and the outgoing call history data, incoming call history data, and phone book data may be updated and stored every time the outgoing call history data, incoming call history data, and phone book data are received from the mobile phone 2. Alternatively, the outgoing call history data, incoming call history data, and phone book data received from the mobile phone 2 may be stored in both the working memory 16 and the storage memory 17, and the storage memory 17 may be used as a backup memory.

[0216] The number of outgoing call history data and incoming call history data that can be stored in the working memory 16 may be one. In this case, when outgoing call processing or incoming call processing is performed in the in-vehicle hands-free device 1, the outgoing call history data and incoming call history data received through the wireless communication connection in the PBAP are always erased.

[0217] In addition, in each of the in-vehicle hands-free device 1 and the in-vehicle hands-free device 1A, a plurality of outgoing call history data and a plurality of incoming call history data are displayed simultaneously, but they may be displayed one by one. In this case, for example, the latest data may be displayed first, and then the next latest data may be displayed in order by operating the operation unit 14.

[0218] The number of outgoing call history data and incoming call history data that can be stored in the working memory 16 may be one. In this case, when outgoing call processing or incoming call processing is performed in the in-vehicle hands-free device 1, the outgoing call history data and incoming call history data received through the wireless communication connection in the PBAP are always erased.

[0219] When a Bluetooth communication line is established between the mobile phone 2 and the in-car hands-free device 1, the configuration is not limited to automatic transfer of outgoing call history data and incoming call history data, but may be such that outgoing call history data, incoming call history data, and phone book data are transferred on the condition that the user operates the in-car hands-free device 1 or the mobile phone 2.

[0220] When the outgoing call history data, incoming call history data and phone book data received from the mobile phone 2 are stored in the working memory 16 separately for each mobile phone 2, the mobile phone 2 and the data stored in the working memory 16 are not limited to being associated with each other by generating a link key, and the two may be associated with each other by other methods. [Explanation of symbols]

[0221] 1,1A In-vehicle hands-free device 2. Mobile Phones 3. Vehicle 12 Control device 13 Bluetooth Communication Department 14 Control section 15 Display section 16 Working Memory 17 Storage Memory 18 Microphones 19 Speaker 40 base station 101 Reception 102,120 Control section 103 Data receiving unit 104 Storage section 111 Hands-free call connection control unit 112,122 Data transfer control section 114,123 Display control unit

Claims

1. A vehicle-mounted hands-free device that enables hands-free conversation by wirelessly connecting to a mobile phone that stores call history data indicating incoming call telephone numbers that are call origins and outgoing call history data indicating outgoing call telephone numbers that are call destinations, as well as telephone numbers and telephone directory data in which names corresponding to the telephone numbers are registered, a control unit that performs control related to data transfer in a transfer protocol for transferring history data, including the incoming call history data and the outgoing call history data, and the phone book data, stored in the mobile phone when the mobile phone is present in a wireless connection area; a data receiving unit that receives the history data and the phone book data from the mobile phone through communication using the transfer protocol; a data storage unit that stores the received history data and the received telephone directory data, the control unit controls the history data to be transferred before the phone book data, and when the mobile phone is set to prohibit or limit the transfer of the history data or the phone book data, causes a display unit to display information indicating that the history data or the phone book data cannot be transferred. Hands-free devices.

2. The mobile phone further includes a hands-free call protocol connection means for connecting a hands-free call protocol for implementing a hands-free call by the mobile phone to the mobile phone, and the control unit, when the hands-free call protocol connection means is in a hands-free call protocol connection state and in an incoming call state, receives outgoing call history data from the mobile phone using the transfer protocol when the incoming call state ends and transitions to a communication state different from the incoming call state.

2. The hands-free device of claim 1.

3. The control unit, when an emergency call sending condition is satisfied, causes the mobile phone to send the emergency call to a destination, and when the hands-free telephone protocol connection means is in a hands-free telephone protocol connection state and in an incoming call state, when the incoming call state ends and a communication state different from the incoming call state is entered, the outgoing call history data from the mobile phone is received by the transfer protocol; A hands-free device according to claim 2.

4. The call history data from the mobile phone includes a telephone number of the destination of the emergency call or identification information of the destination. A hands-free device according to claim 3.

5. After receiving the call history data from the mobile phone, the control unit causes the display unit to display a call operation screen on which a call can be made based on the call history in response to a user operation. A hands-free device according to claim 4.

6. The call operation screen displays pre-registered telephone numbers or registered names as contacts that can be used to make calls. A hands-free device according to claim 5.

7. The transfer protocol is PBAP (Phone Book Access SS Profile), the control unit, when the connection via the PBAP is interrupted during the transfer of the history data or the telephone directory data, displays an error and causes a reconnection screen for receiving an input instructing reconnection via the PBAP to be displayed on the display unit, and, when the input instructing reconnection via the PBAP is received via the reconnection screen, executes reconnection via the PBAP.

2. The hands-free device of claim 1.

8. The control unit is When displaying the history data on a display unit, the outgoing call date and time included in the outgoing call history data is compared with the incoming call date and time included in the incoming call history data, and the one with the latest date and time is displayed on the display unit as the latest data; When the outgoing call date and time are the same as the incoming call date and time, the outgoing call is displayed on the display unit as being more recent than the incoming call, or the incoming call is displayed on the display unit as being more recent than the outgoing call. A hands-free device according to claim 1 or 7.

9. the control unit, when the mobile phone supports a batch transfer request for transferring the history data in a batch, causes the mobile phone to transfer the history data in a batch and causes the display unit to display the transferred history data. A hands-free device according to claim 7 or 8.

10. when the mobile phone does not support the batch transfer request, the control unit transfers a predetermined number of the latest incoming call history data, the latest outgoing call history data, and the latest missed call history data in order from the latest, displaying, on the display unit, as the history data, all outgoing and incoming call histories generated based on date and time information set in each of the transferred incoming call history data, outgoing call history data, and missed call history data; 10. A hands-free device according to claim 9.

11. when the mobile phone does not support the batch transfer request and date and time information is not set in at least one of the incoming call history data, the outgoing call history data, and the missed call history data included in the history data, the control unit transfers a predetermined number of each of the incoming call history data, the outgoing call history data, and the missed call history data, displaying, on the display unit, as the history data, an entire call history generated based on the order of reception of the transferred incoming call history data, outgoing call history data, and missed call history data; A hands-free device according to claim 9 or 10.

12. A hands-free system that enables hands-free conversation by wirelessly connecting to a mobile phone that stores call history data indicating incoming call telephone numbers that are call origins and outgoing call history data indicating outgoing call destination telephone numbers, and telephone numbers and telephone directory data in which names corresponding to the telephone numbers are registered, a control unit that performs control related to data transfer in a transfer protocol for realizing the transfer of the incoming call history data, the outgoing call history data, and the phone book data stored in the mobile phone when the mobile phone is present in a wireless connection area; a data receiving unit that receives call history data, call history data, and phone book data from the mobile phone through communication using the transfer protocol; a data storage unit for storing the received outgoing call history data, incoming call history data, and phone book data; the control unit controls the history data including the outgoing call history data and the incoming call history data to be transferred before the phone book data, and when the mobile phone is set to prohibit or limit the transfer of the history data or the phone book data, causes the display unit to display information indicating that the transfer of the history data or the phone book data is not possible. Hands-free system.

13. A data transfer method executed in a hands-free device that enables hands-free conversation by wirelessly connecting to a mobile phone that stores call history data indicating incoming call telephone numbers that are incoming calls and outgoing call history data indicating outgoing call telephone numbers that are outgoing calls, telephone numbers, and telephone directory data in which names corresponding to the telephone numbers are registered, comprising: a first step of controlling data transfer using a transfer protocol for realizing the transfer of the incoming call history data, the outgoing call history data, and the phone book data stored in the mobile phone when the mobile phone is present in a wireless connection area; a second step of receiving call history data, call history data, and phone book data from the mobile phone through communication using the transfer protocol; a third step of storing the received outgoing call history data, incoming call history data, and telephone directory data in a data storage unit; In the first step, the history data including the outgoing call history data and the incoming call history data is transferred before the phone book data, and when the mobile phone is set to prohibit or limit the transfer of the history data or the phone book data, information indicating that the transfer of the history data or the phone book data is not possible is displayed on a display unit. Data transfer methods.

Citation Information

Patent Citations

  • Telephone system

    JP1999220522A

  • On-vehicle hands free system and its portable terminal

    JP2002193046A

  • Radio communication apparatus

    JP2006109292A

  • In-vehicle communication system

    JP2006287321A

  • In-vehicle hands-free device and data transfer method

    JP2009081824A