JP2022155629A - Hands-free device and control method thereof - Google Patents

Abstract

To improve the convenience of a hands-free device and ensure security.SOLUTION: A hands-free device according to the present disclosure that enables hands-free calling by being wirelessly connected to a mobile phone that stores telephone numbers and telephone directory data in which registered names are registered corresponding to the telephone numbers includes a determination unit that determines, when an application operable on the hands-free device requests access to the telephone directory data, whether the application requesting access has already been confirmed by a user as to whether the access request is permitted, and an inquiry unit that inquires of the user whether to permit access when confirmation by the user has not yet been made.SELECTED DRAWING: Figure 1

Description

The present disclosure relates to hands-free devices and methods of controlling hands-free devices.

As a configuration in which a mobile phone automatically transfers phone book data representing correspondence between a phone number and a registered name to a hands-free device, for example, a user carries a mobile phone and gets into a vehicle, and the mobile phone is a hands-free device for short-distance communication. In some cases, when the mobile phone enters the area, a communication line is established between the mobile phone and the hands-free device, and the mobile phone automatically transfers phone book data to the hands-free device. According to this device, a user can select a desired telephone number from the telephone directory data of the mobile telephone and make a call by operating the hands-free device (see, for example, Patent Document 1). In addition, there have been proposed techniques for improving user convenience in a system in which an in-vehicle device and a mobile device are connected (see, for example, Patent Documents 2 and 3).

JP 2002-193046 A WO2014/050459 JP-A-2006-109292

However, it is desired to further improve the convenience and ensure the security of hands-free devices that enable hands-free communication.

An object of the present disclosure is to improve the convenience of a hands-free device while ensuring security.

A hands-free device according to the present disclosure enables hands-free calling by being wirelessly connected to a mobile phone that stores incoming history data, outgoing history data, phone numbers, and phone book data. It comprises a receiver and a data storage. The control unit implements a transfer protocol for transferring history data, including incoming history data and outgoing history data, and telephone book data stored in the mobile phone when the mobile phone is in a wireless connection area. Controls data transfer in The data receiving unit receives history data and phonebook data from the mobile phone through communication using the transfer protocol. The data storage unit stores history data and telephone directory data received by the data reception unit. The control unit performs control to transfer history data before telephone directory data.

According to the hands-free device according to the present disclosure, it is possible to both improve the convenience of the hands-free device and ensure security.

FIG. 1 is a diagram showing an example of usage of a hands-free device according to the first embodiment. FIG. 2 is a diagram illustrating an example of the hardware configuration of the hands-free device according to the first embodiment; FIG. 3 is a functional block diagram of the hands-free device according to this embodiment. FIG. 4 is a processing flowchart of the first embodiment. FIG. 5 is an explanatory diagram of an example of an inquiry screen. FIG. 6 is a diagram showing an example of correspondence between call history data and phonebook data according to the first embodiment. FIG. 7 is a diagram showing an example of correspondence between incoming call history data and telephone directory data according to the first embodiment. FIG. 8 is a diagram showing an example of correspondence between missed call history data and telephone directory data according to the first embodiment. FIG. 9 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. FIG. 10 is a diagram showing an example of the flow of processing for making a call using outgoing call history data, incoming call history data, and phonebook data executed by the hands-free device of the first embodiment. FIG. 11 is a diagram showing an example of the flow of processing for making a call using outgoing call history data, incoming call history data, and phonebook data executed by the hands-free device of the first embodiment. FIG. 12 is a diagram showing an example of outgoing call history data according to the first embodiment. FIG. 13 is a diagram showing an example of incoming call history data according to the first embodiment. FIG. 14 is a diagram illustrating an example of transition of display screens when the user performs a call operation from the call history according to the first embodiment. FIG. 15 is a diagram illustrating an example of transition of display screens when the user performs a call operation from the incoming call history according to the first embodiment. 16A and 16B are diagrams illustrating an example of transition of display screens when the user performs a call operation from the telephone directory according to the first embodiment. FIG. 17 is a diagram showing an example of telephone directory data according to the first embodiment. FIG. 18 is a flowchart showing details of the flow of HFP processing according to the first embodiment. FIG. 19 is a diagram illustrating another example of transition of display screens when the user performs a call operation from the incoming call history according to the first embodiment. FIG. 20 is a diagram for explaining an example of item data constituting telephone directory data. FIG. 21 is a processing flowchart of the second embodiment. FIG. 22 is a processing flowchart of specific item target processing. FIG. 23 is an explanatory diagram of an example of an inquiry screen.

Embodiments of a hands-free device, a hands-free system, and a data transfer method according to the present disclosure will be described below with reference to the drawings.

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

A hands-free device 1 connects to a mobile phone network via a mobile phone 2 . Thereby, for example, the driver of the vehicle 3 can make and receive calls by operating the hands-free device 1 without operating the mobile phone 2 . The hands-free device 1 may be implemented as one function of a hands-free device mounted on the vehicle 3, for example.

FIG. 2 is a diagram showing an example of the hardware configuration of the hands-free device 1 according to this embodiment. The hands-free device 1 of this embodiment is, for example, a hands-free device with a hands-free function. The hands-free device 1 includes a control device 12 , a Bluetooth communication section 13 , an operation section 14 , a display section 15 , a working memory 16 , a storage memory 17 , a microphone 18 and a speaker 19 .

The control device 12 controls overall operations of the hands-free device 1, such as communication operations and data management operations. The control device 12 is, for example, a processor such as a CPU (Central Processing Unit). The control device 12 includes control means, determination means, display control means, transfer protocol control means, transfer protocol disconnection means, hands-free protocol control means, initial hands-free protocol communication means, communication maintenance means, telephone directory transfer setting means, and data transfer. It is an example of designating means and manual transfer protocol designating means.

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 existing within the Bluetooth wireless communication range, and complies with the Bluetooth communication standard. Communicate compliantly. In this case, it is assumed that the mobile phone 2 has a Bluetooth communication function and is within the Bluetooth wireless communication range of the hands-free device 1 .

The Bluetooth communication unit 13 in this example includes a well-known HFP (Hands Free Profile) for making hands-free calls, and a PBAP (Phone Book Access Profile) for transferring phone book data and incoming/outgoing call history data. corresponds to These profiles mean communication protocols defined for each function. The Bluetooth communication unit 13 is an example of outgoing history data receiving means, incoming 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.

As is well known, the mobile phone 2 establishes a mobile phone line with a base station 40 of the mobile phone network and makes calls independently (in a state in which the HFP is not connected to the hands-free device 1, which is a hands-free device). It is configured such that outgoing call processing and incoming call processing can be performed independently. In this case, in the mobile phone 2, for example, the user operates a dial key (numerical keys "0" to "9") (not shown) to enter the telephone number of the destination, and then makes a call. By operating a key (not shown), it is possible to make a call to the phone number as a destination, and to make a call with the mobile phone of the destination.

In addition, when the mobile phone 2 receives an incoming call signal from the base station 40 in response to the call originating mobile phone making a call to the mobile phone 2 as a call destination, the mobile phone 2 receives an incoming call signal from the base station 40. is received as the incoming phone number, and when the user operates the answer key (not shown), the caller's mobile phone can be answered and a call can be made with the caller's mobile phone. It becomes possible.

In addition, the mobile phone 2 has a clock unit (not shown) for keeping date and time (date and time). A plurality of outgoing call history data are stored and held as data corresponding to the outgoing date and time based on the data for one case. In addition, the cellular phone 2 stores a plurality of incoming call histories as data for one case of the correspondence between the incoming call number received from the base station 40 in the incoming call processing and the incoming date and time based on the date and time kept by the clock unit. data is stored.

In addition, the cellular phone 2 stores a plurality of correspondences between the incoming call number received from the base station 40 when no response is made to the incoming call and the incoming date and time based on the date and time kept by the clock unit as data for one case. Missed call history data for each item is stored. Furthermore, the mobile phone 2 holds telephone directory data for a plurality of cases, with correspondence between telephone numbers and registered names as data for one case. The telephone directory data is data in which a user inputs a telephone number and a registered name, and these telephone numbers and registered names are associated with each other, for example, about 500 items, and stored in a non-volatile memory (not shown). .

When the mobile phone 2 has telephone directory data, the outgoing call history data and the incoming call history data include the registered name. Specifically, it checks whether the incoming telephone number received from the base station 40 is a telephone number registered in the telephone directory data, and whether or not the registered name of this telephone number is registered in the telephone directory data. , the incoming call history data consists of a telephone number, an incoming call date and time, and a registered name. Missed call history data is also processed in a similar manner and consists of a telephone number, the date and time of the call, and its registered name. For outgoing call history data, it is checked whether the phone number called in the outgoing call process is a phone number registered in the phone book data. Configured.

By reading out the telephone directory data, selecting one telephone number, and making a call, the user can make a call with a simple operation without having to input all the numeric keys corresponding to the numbers constituting the telephone number one by one. can do. The mobile phone 2 can store, for example, the latest 20 records of outgoing call history data, incoming call history data, and missed call history data. and update outgoing call history data, incoming call history data, and missed call history data. The mobile phone 2 is compatible with well-known HFP for hands-free communication and PBAP for transferring phone book data and incoming/outgoing call history data.

If the mobile phone 2 is compatible with PBAP, which defines automatic transfer of incoming/outgoing call history data, PBAP is connected immediately after establishing a communication line with the Bluetooth communication unit 13. To automatically transfer stored telephone directory data, and to automatically transfer outgoing call history data, incoming call history data, and missed call history data stored at that time. As a result, when the hands-free device 1 exists within the Bluetooth communication range, the mobile phone 2 can store up to 20 outgoing call history data that has been independently processed and stored in the past. Incoming call history data for up to 20 cases stored by performing incoming call processing and missed call history data for up to 20 cases stored by independently performing missed call processing in the past are automatically transferred to a hands-free device 1. - 特許庁

In this embodiment, when collectively referring to outgoing call history data, incoming call history data, and missed call history data, it may simply be called history data. Here, the history data includes at least outgoing call history data and incoming call history data. The history data may be in the form of outgoing call history data and incoming call history data, or may be in the form of outgoing call history data, incoming call history data and missed call history data.

Also, the mobile phone 2 stores a voice message left by the caller in a non-volatile memory (not shown) when the call is not answered. The voice message is also called a message memo, for example, and the user of the mobile phone 2 can reproduce and listen to the content.

The operation unit 14 is operation means for user operation in the present embodiment, and includes, for example, touch keys formed on the display unit 15. The operation unit 14 detects user operations and outputs operation signals representing the operation contents. to the control device 12 . The display unit 15 is the display means referred to in this embodiment, and when a display signal is input from the control device 12, a display screen is displayed based on the input display signal. , a display screen on which dial keys corresponding to "0" to "9" are arranged is displayed.

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

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 be a writable storage medium such as an HDD (Hard Disk Drive) or flash memory.

In this case, when the user makes a display request for the outgoing call history data using the operation unit 14, the control device 12 causes the display unit 15 to display the outgoing call history data stored in the working memory 16, and the user can display the incoming call history data. When the operation unit 14 makes a display request, the incoming call history data stored in the work memory 16 is displayed on the display unit 15. When the user makes a display request for the telephone directory data through the operation unit 14, the work memory 16 display the telephone directory data stored in the display unit 15. In the hands-free device 1 of the present embodiment, as described above, the working memory 16 stores 5 outgoing call history data and 5 incoming call history data, respectively, and the maximum number of items displayed on the display unit 15 is 5 each. matter. The number of data items stored in the working memory 16 is an example, and the number of data items is not limited to the above example.

The microphone 18 is voice input means for inputting voice, and inputs the voice uttered by the user when performing a hands-free call using the mobile phone 2. The speaker 19 is voice output means, and is used for the mobile phone. When a hands-free call is made using the telephone set 2, the received voice of the other party is output. That is, when a Bluetooth communication line is established between the Bluetooth communication unit 13 and the mobile phone 2 to connect wireless communication by HFP, the control device 12 transmits the voice input by the microphone 18 from the Bluetooth communication unit 13 to the mobile phone 2. , and the voice received by the mobile phone 2 from the mobile phone network is received by the Bluetooth communication unit 13 from the mobile phone 2 and output from the speaker 19 .

In addition to the illustrated functional blocks, the hands-free device 1 includes a GPS device as a current position detection unit for detecting the current position of the vehicle, a route search unit for searching for a route from the current position to the destination, A map data reading unit that reads map data from a recording medium in which map data is recorded, a VICS information receiving unit that receives VICS information distributed from the VICS (registered trademark) center, and a voice recognition unit that recognizes the voice uttered by the user. It may also be configured to include functional blocks necessary for navigation operations such as. In this case, the hands-free device 1 may acquire the date and time by extracting the GPS date and time information from the GPS radio signal received by the GPS device from the GPS satellites, and use the acquired date and time as the date and time of call origination and the date and time of call reception.

The hands-free device 1 described above is configured to start and stop in conjunction with on/off of an ACC switch (switch for turning on/off power supply to vehicle equipment). For example, when the ACC switch is switched from on to off in response to a user's operation, the hands-free device 1 stops power supply, and as a result, the device power transitions from on to off. In this case, the various data stored in the storage memory 17 immediately before that are not erased (although they are stored), but the call history data, incoming history data, and missed call history stored in the working memory 16 immediately before Data and phone book data are configured to be erased.

Next, the details of the functions of the hands-free device 1 of this embodiment will be described.
FIG. 3 is a functional block diagram of the hands-free device according to this embodiment.
Note that the functions of the hands-free device 1 are not limited to the example shown in FIG. 3, and may have other functions.
In the example of FIG. 3 , the hands-free device 1 of this embodiment includes a determination unit 101 , an inquiry unit 102 , an inquiry screen display unit 103 , an instruction input unit 104 and a situation storage unit 105 .

In this embodiment, the functions of the determination unit 101 and the inquiry unit 102 are realized by the control device 12 reading out a program from the storage memory 17 and executing it. However, not limited to this, for example, some or all of the functions of the determination unit 101 and the inquiry unit 102 may be realized by a dedicated hardware circuit.
Further, the inquiry screen display unit 103 is realized by the display unit 15, for example.
Also, the instruction input unit 104 is realized by the operation unit 14, for example.
Further, the inquiry screen display unit 103 is realized by the display unit 15, for example.
The status storage unit 105 is realized by the storage memory 17, for example.

In this case, the operation unit 14 and the display unit 15 are, for example, integrated as a touch panel display, and the user operates the operation unit 14 based on the content displayed on the display unit 15 to input instructions. .
More specifically, the control device 12 functioning as the inquiry unit 102 performs an instruction operation ( For example, an operation of pressing an icon, etc.) is accepted.

In the present embodiment, various functions of the hands-free device 1 are realized by one device, but the invention is not limited to this. It may be in a form dispersed in. In other words, various functions of the hands-free device 1 may be realized by a system (hands-free system) composed of a plurality of devices.

Next, the operation of the configuration described above will be described. In the present embodiment, the mobile phone 2 stores 20 maximum storable outgoing history data, 20 maximum storable incoming history data, 20 maximum storable incoming history data, and 20 maximum storable incoming history data. Missed call history data has already been held (stored), and in this state, the user carrying the mobile phone 2 approaches the vehicle 3 and gets into the vehicle, turning on the ACC switch, thereby causing the mobile phone 2 to go into the handshake state. Description will be made on the assumption that the free device 1 has entered the Bluetooth communication range.

FIG. 4 is a processing flowchart of the first embodiment.
First, in the hands-free device 1, a procedure for receiving outgoing call history data, incoming call history data, missed call history data, and telephone directory data from the cellular phone 2 by the control device 12 will be described with reference to FIG. It should be noted that the user has previously registered the mobile phone 2 as a partner of the Bluetooth communication in the hands-free device 1 .

For example, the user inputs a 4-digit password into the hands-free device 1 for each mobile phone 2 at the time of initial communication setup. The hands-free device 1 and the mobile phone 2 generate a link key used for mutual connection and hold the link key. The 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, HFP communication connection and PBAP communication connection are not established between the hands-free device 1 and an unregistered mobile phone. Basically, the mobile phone 2 of the owner of the vehicle 3 is registered in advance, and Bluetooth communication is performed between the mobile phone 2 and the hands-free device 1 . Note that the above-described method for pre-registering the mobile phone 2 to be communicated with by the hands-free device 1 is merely an example, and is not limited to this.

In this example, it is assumed that a plurality of mobile phones 2 to be connected for communication are registered in the hands-free device 1 . For example, the user operates the operation unit 14 to preset priorities for the plurality of mobile phones 2, and the work memory 16 or the storage memory 17 stores the priorities. For example, since some drivers may own a plurality of mobile phones 2, the hands-free device 1 can register a plurality of mobile phones 2 in this manner.

As a premise of this example, the Bluetooth communication unit 13 of the hands-free device 1 supports both HFP wireless communication and PBAP wireless communication protocols, and simultaneously connects these two profiles (multi-profile connection). can be connected to However, this simultaneous connection processing is intentionally avoided. There are mainly the following three reasons for this.

(1) Like the hands-free device 1, the mobile phone 2, which is the communication partner, supports wireless communication in HFP and wireless communication in PBAP, but may not support simultaneous connection. to be.

(2) The mobile phone 2, which is the communication partner, may support both HFP wireless communication and PBAP wireless communication, and may also support simultaneous connection. 2) The software processing of the Bluetooth communication unit 13 of the hands-free device 1 becomes complicated, and the stability of the communication connection is uncertain.

(3) Mobile phones 2 are manufactured by many manufacturers around the world, and the hands-free device 1 is required to be connected to all mobile phones compatible with HFP wireless communication and PBAP wireless communication. to be

For the above reasons, the hands-free device 1 in this example performs wireless communication in HFP and wireless communication in PBAP as a more reliable processing procedure for wireless communication in HFP and wireless communication in PBAP. In order to eliminate simultaneous connections as much as possible, HFP wireless communication and PBAP wireless communication are serially connected in a time-divided manner.

Returning to the description, the control device 12 selects the mobile phone 2 with the higher priority as a communication connection target in wireless communication by HFP (S1).
Here, in this example, the communication connection is not first established by PBAP, but the initial communication by HFP is automatically attempted and the connection is started.
The reason for this will be described later.

Next, the control device 12 executes a process of automatically connecting the selected mobile phone 2 for initial HFP communication (S2).
Subsequently, the control device 12 determines whether or not the wireless communication connection in the HFP has succeeded (S3).

When the control device 12 determines that the wireless communication connection in the HFP is successful (S3 "YES"), the control device 12 automatically disconnects the wireless communication in the connected HFP, and the control device 12 restarts the wireless communication in the HFP. PBAP wireless communication is automatically connected to the mobile phone 2 that has succeeded in connection (S4).

Next, control device 12 transmits a history data transfer request to mobile phone 10 so as to start transfer processing of outgoing call history data, incoming call history data, and missed call history data. is performed, and the in-vehicle hands-free device 1 receives these history data (S5).

When the history data transfer process is completed, the control device 12 next requests the mobile phone 10 to transfer the phone book data, and the in-vehicle hands-free device 1 receives the phone book data ( S6). Then, the control device 12 stores the phonebook data transferred from the mobile phone 2 in the working memory 16 or the storage memory 17 .

After that, when the control device 12 (determining unit 101) accesses the phone book data of the mobile phone 2 from an application (Display Audio application: hereinafter referred to as a DA application) running on the in-vehicle hands-free device 1 (S7 ), it is determined whether or not the user has confirmed whether or not access is permitted by the time of the previous access (S8).

If the control device 12 (determining unit 101) determines that the user's access permission has been confirmed by the time of the previous access (S8 "permission confirmed"), the control device 12 permits the DA application to access the telephone directory data. (S11), the control is returned to the DA application and the process is terminated (S12).

Further, when the control device 12 (determination unit 101) determines that the user has not confirmed whether or not access is permitted by the time of the previous access (S8 “unconfirmed”), the control device 12 (inquiry unit 102) displays the display unit 15 (inquiry screen display unit 103) to that effect is notified (S9).

FIG. 5 is an explanatory diagram of an example of an inquiry screen.
A dialog box 111 as an inquiry screen is displayed on the display screen 15A of the display unit 15 to display an inquiry message "Do you want to allow application X to access the phonebook data?" A check box 112 for instructing whether or not to confirm whether or not to confirm whether or not access is permitted to the user when an access request is made by the current DA application, a permission instruction button 113 for inputting an instruction to grant permission for the access request by the current DA application, and the current DA application. A rejection instruction button 114 is displayed for inputting an instruction to reject an access request from an application.

In the above configuration, in the example of FIG. 5, "application X" is the DA application name for the user to specify the DA application.
Also, the check box 112 toggles between a checked state and a non-checked state every time the user touches it.

When the user touches the permission instruction button 113, if the check box 112 is checked, the DA application is permitted to access the telephone book data from now onwards. Instructions are entered.

If the check box 112 is unchecked, the DA application is permitted to access the phonebook data this time, but next time, when the DA application requests access again, the user will be asked to confirm whether or not access is permitted. Instructions are entered.

When the user touches the refusal instruction button 114, the controller 12 is instructed to deny access to the telephone directory data for the DA application from now onwards if the check box 112 is checked. is entered.

If the check box 112 is unchecked, access to the telephone directory data for the DA application is denied this time, but next time, when the DA application requests access again, the user will be confirmed as to whether or not access is permitted. Instructions are entered.

Subsequently, the control device 12 determines whether or not the DA application that requested the access is permitted to access the telephone directory data based on the input of the user's instruction (S10).

When the control device 12 (determining unit 101) determines that the DA application that has issued the access request is permitted to access the telephone directory data ("YES" in S10), the access to the telephone directory data by the DA application is permitted. is permitted (S11), the control is returned to the DA application, and the process is terminated (S12).

If the control device 12 (determining unit 101) determines that the DA application that requested access has been denied access to the telephone directory data (S10 "NO"), the access to the Tonomachi data by the DA application is determined. is rejected (S13), the control is returned to the D application, and the process is terminated (S12).

On the other hand, when the control device 12 (determining unit 101) determines that access denial by the user has been confirmed by the time of the previous access (S8 "denial confirmed"), access to the Tonomachi data by the DA application is prohibited. Refusal (S13), control is returned to the D application, and the process ends (S12).

In this way, every time a DA application issues an access request to the telephone directory data of the mobile phone 2, the control device 12 determines whether the permission has been confirmed, the refusal has been confirmed, or the access has not been confirmed. If it is determined that the confirmation has not been completed by the time of the previous access request, it will prompt the confirmation again, and if it has been confirmed by the time of the previous access request, it will automatically process according to the contents of the confirmation. Therefore, it is possible to easily achieve both convenience improvement and security assurance.

According to the above configuration, unless the user explicitly permits each DA application to access the telephone directory data, an unspecified DA application may access the telephone directory data from a location unknown to the user. Therefore, it is possible to eliminate user's concerns about security.

Next, the process of transferring the outgoing call history data, the incoming call history data, and the missed call history data described above with reference to FIG. 4 and the like will be described more specifically.

FIG. 6 is a diagram showing an example of correspondence between call history data and phonebook data according to the present embodiment. More specifically, FIG. 6A is an example of outgoing call history data saved in the mobile phone 2 . FIG. 6B is an example of phone book data stored in the mobile phone 2. As shown in FIG. FIG. 6C is an example of outgoing call history data saved or displayed on the hands-free device 1. As shown in FIG.

Also, FIG. 7 is a diagram showing an example of correspondence between incoming call history data and telephone directory data according to the present embodiment. More specifically, FIG. 7A is an example of incoming call history data saved in the mobile phone 2 . FIG. 7B is an example of phonebook data stored in the mobile phone 2. As shown in FIG. FIG. 7(c) is an example of incoming history data stored or displayed on the hands-free device 1. As shown in FIG.

FIG. 8 is a diagram showing an example of correspondence between missed call history data and telephone directory data according to the present embodiment. More specifically, FIG. 8A is an example of missed call history data saved in the mobile phone 2. FIG. FIG. 8(b) is an example of phonebook data stored in the mobile phone 2. As shown in FIG. FIG. 8C is an example of missed call history data saved or displayed on the hands-free device 1 .

The control device 12 receives call history data including the registered name, caller telephone number, and call date and time shown in FIG.

Also, the control device 12 receives incoming call history data including the registered name, the incoming telephone number, and the incoming date and time shown in FIG.

The control device 12 also receives missed call history data including the registered name, missed call telephone number, and missed call date and time shown in FIG.

Further, when the registered name is not included in the incoming call history data, outgoing call history data, and missed call history data in the mobile phone 2, the control device 12 controls the call history data included in the incoming call history data, outgoing call history data, and missed call history data By associating the number with the registered name associated with the telephone number in the telephone directory data, the registered name is added to the incoming call history data, the outgoing call history data, and the missed call history data, and stored in the working memory 16 or the storage memory. 17 may be stored. When there is a request to display outgoing call history data, incoming call history data, and missed call history data, control device 12 displays outgoing call history data, incoming call history data, and missed call history data stored in working memory 16 or storage memory 17. is displayed on the display unit 15 . In other words, control device 12 can display the registered name transferred from mobile phone 2 on display unit 15 without reading the registered name from the telephone directory data stored in working memory 16 or storage memory 17. .

Incoming call history data, outgoing call history data, and missed call history data may be stored in working memory 16 or storage memory 17 without including the registered name. In this case, the control device 12 associates the telephone number included in the incoming call history data, the outgoing call history data, and the missed call history data with the registered name associated with the telephone number in the telephone directory data, and displays it on the display unit 15. to display.

When the control device 12 completes the HFP connection processing described in S25 of FIG. 5, the user can operate the operation unit 14 on the hands-free device 1 side to perform call origination processing and call reception processing. .

Further, after the control device 12 receives the outgoing call history data, the incoming call history data, and the missed call history data from the mobile phone 2 by the initial connection processing with the mobile phone 2 described in FIG. , new outgoing call processing, new incoming call processing, or new missed call processing may be executed. Thereafter, when the user operates the operation unit 14 to request display of outgoing call history data, incoming call history data, or missed call history data, the control device 12 performs new outgoing call processing, incoming call processing, or missed call processing. 6(c), 7(c) and 8 ( The registered name is displayed on the display unit 15 as shown in c).

In more detail, it is assumed that the control device 12 has processed a call to the telephone number of "Ichiro Kato" as a new call process. In this case, if the registered name of "Ichiro Kato" is registered in the telephone directory data, the controller 12 reads out the registered name of "Ichiro Kato" from the telephone directory data as shown in FIG. Displayed on the display unit 15 . In addition, as a new incoming call processing, when there is a call from the telephone number of "Ichiro Yoshimoto", the control device 12, if this incoming telephone number is registered in the telephone directory data, performs the processing shown in FIG. Thus, the registered name of "Ichiro Yoshimoto" is read out from the telephone directory data and displayed on the display unit 15. FIG. Further, when there is a new missed call from the telephone number of "Saburo Watanabe", the control device 12 reads out and displays the registered name of "Saburo Watanabe" from the telephone directory data as shown in FIG. 8(c). display on the part 15.

Further, when control device 12 receives a display request for all history data (all outgoing/incoming call history), in which outgoing call history data, incoming call history data, and missed call history data are collectively displayed according to the latest time order, control device 12 displays incoming call history data and missed call history data. Regarding the incoming call history data, regardless of whether the incoming telephone number or the missed call telephone number is the same (overlapping), the incoming call history data and the missed call history data with the newer incoming date and time or missed call date and time are all included. A predetermined number of them are selected and displayed. Further, the control device 12 selects and displays only the latest transmission history data among the transmission history data having the same (overlapping) transmission telephone number as the transmission history data.

FIG. 9 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 present embodiment. In the example shown in FIG. 9, the calling telephone number of "Taro Abe" is duplicated. In this case, the control device 12 displays only the call history with the latest call date and time (the call call history data with the call date and time of August 10, 12:15) among the call history of “Taro Abe”, and displays the call history with the latest call date and time. Do not display call history that is not.

Next, in the hands-free device 1, the control device 12 receives and stores outgoing call history data, incoming call history data, missed call history data and telephone directory data from the mobile phone 2, and the stored outgoing call history data and incoming call history data. A procedure for making a call using history data and missed call history data will be described. Although the outgoing call history data and the incoming call history data will be described here, the same applies to the missed call history data.

10 and 11 are diagrams showing an example of the flow of processing for making a call using outgoing call history data, incoming call history data, and telephone directory data executed by the hands-free device 1 of the present embodiment. The processing executed by the control device 12 in FIGS. 10 and 11 is, for example, the processing realized by the control device 12 and the like described in FIG.

Here, FIG. 12 described in FIGS. 10 and 11 is a diagram showing an example of outgoing call history data according to the present embodiment. FIG. 13 is a diagram showing an example of incoming call history data according to this embodiment. Also, FIG. 14 is a diagram showing an example of transition of display screens when the user performs a call operation from the call history according to the present embodiment. Further, FIG. 15 is a diagram showing an example of transition of display screens when the user performs a calling operation from the incoming call history according to the present embodiment. FIG. 16 is a diagram showing an example of transition of display screens when the user makes a call from the phonebook according to the present embodiment. FIG. 17 is a diagram showing an example of telephone directory data according to this embodiment.

Returning to the flowchart of FIG. 10 , first, the controller 12 of the hands-free device 1 determines that the mobile phone 2 exists within the Bluetooth communication range of the hands-free device 1 and the Bluetooth communication unit 13 communicates with the mobile phone 2. If it is determined that the line has been established ("Yes" at S121), automatic transfer of outgoing call history data, incoming call history data, and telephone directory data from mobile phone 2 to Bluetooth communication section 13 is waited (S122).

Then, when the controller 12 determines that the outgoing call history data, the incoming call history data and the phonebook data have been automatically transferred from the mobile phone 2 (S122 "Yes"), the outgoing call history data automatically transferred from the mobile phone 2 , the incoming history data and the telephone directory data are stored in the working memory 16 or the storage memory 17 (S123).

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 20, respectively. It is also assumed that the number of outgoing call history data and incoming call history data that can be stored in the work memory 16 is five, for example. That is, the number of outgoing call history data and incoming call history data that can be stored in the work memory 16 is smaller than the number of outgoing call history data and incoming call history data automatically transferred from the mobile phone 2 .

In this case, the control device 12, for example, discards the outgoing call history data with the old outgoing date and time among the outgoing call history data automatically transferred from the mobile phone 2, and discards the outgoing call history data for 20 cases automatically transferred from the mobile phone 2. Among them, the five transmission history data with the newest transmission date and time are preferentially stored in the work memory 16 as the portable side transmission history data. In addition, the control device 12 discards the incoming call history data with the old incoming date and time among the incoming call history data, and discards the incoming call history data with the new incoming date and time among the 20 incoming call history data automatically transferred from the mobile phone 2. The data is preferentially stored in the working memory 16 as the mobile-side incoming call history data.

Immediately after the call history data is automatically transferred from the mobile phone 2, the control device 12 holds the call history data shown in FIG. Further, when the user performs an operation to display the call history data from this state, the control device 12 causes the display section 15 to display the display screen shown in FIG. 14(b). 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. When an operation for displaying incoming call history data is performed, the display screen shown in FIG. 15B is displayed on the display unit 15 .

Thus, when the mobile phone 2 and the hands-free device 1 establish a Bluetooth communication line, the outgoing call history data and the incoming call history data stored before the mobile phone 2 establishes the Bluetooth communication line are transferred to the hands-free device. 1, the mobile phone 2 and the hands-free device 1 constitute one telephone system, and this telephone system enables hands-free communication. After the cellular phone 2 and the hands-free device 1 form one telephone system in this way, the user can perform a call operation by dial key input, a call operation by call history, a call operation by call history, and a telephone directory. It is possible to perform a call operation by selecting one of the call operations by , and it is possible to wait for an incoming call from the mobile phone network.

Here, in the present embodiment, as a procedure for Bluetooth communication, after establishing wireless communication connection by PBAP in S7 shown in the flowchart of FIG. Serial profile switching is performed by connecting. Therefore, when a new incoming call is received to the mobile phone 2 after the wireless communication connection is established in S25, or when a new outgoing call process is performed by the operation unit 14, the mobile phone 2 Incoming call history data and outgoing call history data including the incoming call and outgoing call are, after all, own history data, so they are held in their own memory. Therefore, the control device 12 of the hands-free device 1 again performs PBAP wireless communication (simultaneous connection) during HFP wireless communication in order to acquire the latest incoming/outgoing call history data from the mobile phone 2 again. is also possible.

However, if simultaneous connections are to be avoided as much as possible, if the HFP wireless communication connection is disconnected and the PBAP wireless communication connection is established in the serial connection, one telephone system will be used for hands-free communication during that time. The cellular phone 2 and the hands-free device 1, which constitute the device, are substantially separated, and a state occurs in which hands-free communication cannot be performed. Therefore, in the present embodiment, when the HFP wireless communication connection is established in S25, the hands-free device 1 acquires the latest outgoing/incoming call history data by itself and self-manages it only by the HFP wireless communication connection thereafter. I am trying to This will be explained below.

Returning to the flowchart of FIG. 10, the control device 12 determines whether or not the user has performed a call origination operation by dial key input (S124), and determines whether or not the user has performed a call origination operation using the call history (S125). . Here, following the flowchart of FIG. 11, the control device 12 determines whether or not the user has made a call using the incoming call history (S126), and determines whether or not the user has made a call using the telephone directory ( S127), and it is determined whether or not there is an incoming call from the mobile phone network (S128).

Here, when the control device 12 determines that the user has made a call by dial key input ("YES" in S124), the control device 12 carries out call processing for making a call using the telephone number entered by the user with the dial key as the originating telephone number. (S129). Then, when the control device 12 completes the call processing by dial key input, as shown in FIG. The history data is erased (S130), and the latest call history data of the own device representing the call made by the dial key input is additionally stored in the work memory 16 as self call history data (S131).

That is, when the user operates the dial keys to input, for example, the telephone number "09000000100" and performs an operation to transmit the telephone number "09000000100" as the originating telephone number, the control device 12 is shown in FIG. 12(b). Thus, call history data representing the telephone number "09000000100" is additionally stored in the work memory 16 as self-call history data. In this case, the control device 12 stores the date and time acquired by the GPS device of the hands-free device 1 as the date and time of transmission corresponding to the telephone number "09000000100" as a time stamp. In other words, in FIG. 12B, the date and time of calling the latest telephone number “09000000100” is the date and time acquired by the GPS device of the hands-free device 1, and the date and time of calling the remaining four telephone numbers are the clocks of the mobile phone 2. It is the date and time that the department acquired. When the user performs an operation to display the call history data in this state, the control device 12 causes the display section 15 to display the display screen shown in FIG. 14(c).

Further, when the control device 12 determines that the user has pressed the "history button" 4a and then pressed the "transmission history button" 4b to perform a transmission operation based on the transmission history (S125 "YES"). , with reference to the origination history data stored in the work memory 16 (S132), with reference to the telephone directory data stored in the work memory 16 (S133), and as shown in FIGS. , the call operation screen based on the call history is displayed on the display unit 15 (S134). In this case, if the originating telephone number of the originating history data is registered in the telephone directory data, the control device 12 causes the display unit 15 to display the registered name corresponding to the telephone number. If the number is not registered in the telephone directory data, the telephone number is displayed on the display section 15. - 特許庁

Next, the control device 12 performs a calling process of calling the phone number selected by the user as the calling phone number (S135). Then, when the call processing based on the call history is completed, the control device 12 also deletes the call history data with the oldest call date and time among the call history data stored in the work memory 16 at that time (S130). ), and additionally stores the latest call history data of the own device representing the call made by the call history as self call history data in the work memory 16 (S131). Also in this case, the control device 12 stores the date and time acquired by the GPS device of the hands-free device 1 as the date and time of transmission corresponding to the calling telephone number as a time stamp.

Further, when the control device 12 determines that the user has pressed the "history button" 4a and then pressed the "incoming call history button" 4c, and thus determined that a calling operation based on the incoming call history has been performed (S126 "YES"). , the incoming call history data stored in the work memory 16 is referred to (S136), the telephone directory data stored in the work memory 16 is referred to (S137), and as shown in FIGS. Then, the display unit 15 displays the outgoing call operation screen based on the incoming call history (S138). In this case, if the originating telephone number of the incoming history data is registered in the telephone directory data, the control device 12 causes the display unit 15 to display the registered name corresponding to the telephone number. If the number is not registered in the telephone directory data, the telephone number is displayed on the display section 15. - 特許庁

Next, the control device 12 performs a calling process of calling the phone number selected by the user as the calling phone number (S139). Then, when the outgoing call processing based on the incoming call history is finished, the control device 12 also deletes the outgoing call history data with the oldest outgoing date and time among the outgoing call history data stored in the work memory 16 at that time (S130). ), and additionally stores the latest call history data of the own device representing call origination based on the call history in the working memory 16 as self call history data (S131). Also in this case, the control device 12 stores the date and time acquired by the GPS device of the hands-free device 1 as the date and time of transmission corresponding to the calling telephone number as a time stamp.

Further, when the control device 12 determines that the user has pressed the "phone book button" 4d to make a call using the phone book (S127 "YES"), the phone book stored in the work memory 16 The data is referred to (S140), and as shown in FIG. 16(b), the call operation screen based on the telephone directory is displayed on the display unit 15 (S141). Next, the control device 12 performs a calling process of calling the phone number selected by the user from among them as the calling phone number (S142). Then, when the call processing by the telephone directory is completed, the control device 12 also deletes 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). ), the latest call history data of the own device representing the call made by the telephone directory is additionally stored in the work memory 16 as self call history data (S131). Also in this case, the control device 12 stores the date and time acquired by the GPS device of the hands-free device 1 as the date and time of transmission corresponding to the calling telephone number as a time stamp.

Further, when the control device 12 determines that an incoming call has been received from the mobile phone network via the Bluetooth communication unit 13 from the mobile phone 2 ("YES" in S128), it performs incoming call processing such as announcing the incoming call (S143). ), when the incoming call processing is completed, the incoming call history data with the oldest incoming date and time among the incoming call history data stored in the work memory 16 at that time is erased (S144), and the latest incoming call of the own device representing the incoming call is erased (S144). The history data is additionally stored in the work memory 16 as self-incoming call history data (S145).

That is, when the control device 12 receives the telephone number “09000000200” as the incoming telephone number from the mobile phone network via the Bluetooth communication unit 13, it stores the incoming call history data representing the telephone number “09000000200” in the working memory 16. It is additionally stored as data.

By doing so, after the wireless communication connection by HFP in S25, even if the wireless communication connection by PBAP is not performed, if there is a new incoming call processing and outgoing call processing after S1, the own incoming/outgoing call history Data can be added and displayed on the display unit 15 . As a result, it is not necessary to connect HFP and PBAP at the same time. It is possible to prevent the cellular phone 2 and the hands-free device 1, which have become a single telephone system, from being substantially separated.

Next, description will be given of display processing of outgoing/incoming call history data received by wireless communication in PBAP, outgoing call processing generated after S25, and outgoing call/incoming call history data generated in incoming call processing.

In S25, in the HFP wireless connection state, the mobile phone 2 transmits the incoming call telephone number to the hands-free device 1 when receiving an incoming call, but does not transmit incoming call date and time information at this time. Therefore, the control device 12 stores the date and time obtained by the GPS device of the hands-free device 1 as a time stamp as the incoming date and time corresponding to the telephone number "09000000200". In other words, in FIG. 13(b), the latest call date and time of the phone number "09000000200" is the date and time acquired by the GPS device of the hands-free device 1, and the call arrival dates and times of the remaining four phone numbers are the clock of the mobile phone 2. It is the date and time that the department acquired. When the user performs an operation to display incoming call history data in this state, the control device 12 causes the display section 15 to display the display screen shown in FIG. 15(c).

It should be noted that the above is the case where the number of outgoing call history data and incoming call history data that can be stored in the work 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 mobile phone 2 automatically Out of the transferred outgoing call history data and incoming call history data, the outgoing call history data and incoming call history data with old outgoing date and time and incoming call history data are discarded, and the outgoing call history data and incoming call history data automatically transferred from the mobile phone 2 are discarded. Although the case of preferentially storing outgoing call history data and incoming call history data with a newer incoming date and time in the working memory 16 has been described, the hands-free device 1 automatically transfers data to the mobile phone 2 when connecting wireless communication by PBAP. It is also possible to specify the number of cases (in this embodiment, five cases) to be stored in the work memory 16, and preferentially store outgoing history data and incoming history data with new outgoing date and time and incoming date and time.

In addition, in the above-described configuration, when a new outgoing call process or a new incoming call process is performed in the hands-free device 1, the oldest outgoing call history data or incoming call history data stored in the work memory 16 is displayed. Although the case of erasing the data and the oldest incoming call history data has been described, from the user's point of view, there are the following requests, so the control device 12 may perform the following alternative processing. This processing is necessary when wireless communication connection by PBAP is not performed after S25, as in this example.

That is, when comparing the date and time kept by the clock unit of the mobile phone 2 and the date and time acquired by the GPS device of the hands-free device 1, the date and time kept by the clock unit of the mobile phone 2 are compared with the date and time acquired by the GPS device. It may be inaccurate due to many errors and can be set arbitrarily by the user. Therefore, the user intentionally sets it ahead of a predetermined time (for example, 10 minutes) or sets it behind it. Sometimes.

Therefore, if the user has set the date and time of the mobile phone 2 ahead by a predetermined amount of time, and the hands-free device 1 has stored the advanced date and time in the working memory 16, the mobile phone can be set from this state. 2 and the call history data and incoming call history data of the hands-free device 1 are rearranged according to date and time. Incoming call history data and incoming call history data that have undergone such incoming processing are not displayed in the top column on the list display screen even though they are the latest on the time axis, and are displayed in columns other than the top column (for example, the second or third column). In this case, the time axis stored by the user and the time axis displayed by the display unit 15 are out of alignment, and the user feels uncomfortable.

In order to deal with such a problem, the control device 12 arranges the outgoing call history data and the incoming call history data automatically transferred from the mobile phone 2 in order of date and time in columns other than the highest column within the range of only them. The new outgoing history data and new incoming history data of the own device are displayed in the top column. Thereby, it is possible to display in harmony with the time axis memorized by the user, so that the user does not feel uncomfortable.

When the control device 12 arranges and displays the outgoing call history data and the incoming call history data automatically transferred from the mobile phone 2 in order of date and time, the control device 12 does not sort by the date and time data included in the outgoing call history data and the incoming call history data. In both cases, if the outgoing call history data and the incoming call history data contain call order data representing the calling order and incoming order data representing the incoming order, the outgoing call history data is based on the outgoing call order data and the incoming call order data. and incoming history data may be displayed side by side.

Also, even if the outgoing order data and the incoming order data are not explicitly included, the data is received from the mobile phone 2 in a list format as shown in FIGS. When the data is transmitted and received by the hands-free device 1, it may be displayed based on the rule that the higher the data is, the more recent the data is. In other words, the mobile phone 2 transmits data in a format that enables the hands-free device 1 to identify the actual calling order and incoming call order.

In this case, for example, depending on the mobile phone 2, if there is an incoming call from Mr. A at 12:00:00 and Mr. B receives an incoming call at 12:00:30, the time stamp is set to minutes instead of seconds. Then, the time is exactly the same 12:00, which is stored as the incoming call history data of the mobile phone 2. FIG. Even if this data is received by the hands-free device 1 and rearranged in chronological order, the order cannot be determined. It is convenient if you send it in the form. Thereby, it is possible to display in harmony with the time axis memorized by the user, so that the user does not feel uncomfortable.

In these cases, the date and time data included in the outgoing call history data and the incoming call history data are ancillary data, and the call order data and call arrival order data become the user's actual order of call arrival and call. In addition, the mobile phone 2 repeats incoming call processing and outgoing call processing in its independent operation. It is possible to manage Therefore, regardless of the date and time of call origination and the date and time of call arrival by its own clock unit, call order data and call order data are attached to each call and each call, and transmitted to the hands-free device 1, and the hands-free device 1 receives the call. Based on the order data and call order data, the incoming/outgoing call history data are arranged. Alternatively, the mobile phone 2 determines the actual calling order and incoming order without assigning the outgoing order data and the incoming order data, and transmits the list to the hands-free device 1, and the hands-free device 1 follows the above rule. According to the above, the call is arranged in the order of actual call origination and call arrival.

In this way, if the clock of the mobile phone 2 is set to advance or slow down at a certain timing, immediately after that, if an outgoing call or an incoming call occurs, the outgoing call history display and incoming call history display on the mobile phone 2 will be , are displayed in the actual order. Therefore, if the hands-free device 1 rearranges such outgoing/incoming call history data on the basis of the outgoing date/time and the incoming/outgoing date/time, the data is displayed in an order different from the actual order. For this reason, it can be said that the method of calling order data, the calling order data, or the list format method is convenient in comparison with the actual calling order.

As a result, the control device 12 can display the data on the display unit 15 according to the actual calling order and the receiving order of the mobile phone 2 . After performing such data processing, the hands-free device 1 performs call processing using its own dial key input, call processing using the call history, call processing using the incoming call history, and call processing using telephone directory data, as described above. In this case, out of the call history data stored in the working memory 16 at that time, the call history data whose call order data is the oldest or the call call history data considered to be the oldest is erased, and the call made by that call record is indicated. The latest transmission history data of the own device is additionally stored in the working memory 16 as self transmission history data. On the other hand, when a new incoming call process occurs, the control device 12 selects the oldest incoming call history data among the incoming call history data stored in the work memory 16 at that time, or the incoming call data considered to be the oldest. The history data is erased, and the latest incoming call history data of the own device representing incoming calls based on the incoming call history is additionally stored in the working memory 16 as own incoming call history data.

In the case of these outgoing call processing and incoming call processing, the control device 12 stores the date and time obtained by the GPS device of the hands-free device 1 as time stamps as the outgoing date and time corresponding to the outgoing telephone number and the incoming date and time corresponding to the incoming telephone number. . In this way, it is possible to display in harmony with the time axis memorized by the user, so that the user does not feel uncomfortable.

In addition, when there is a display request for all history data, which collectively displays the outgoing call history data and the incoming call history data, the control device 12 displays only the outgoing call history data and the incoming call history data. of sorting is required. In other words, as described above, the incoming call history data and outgoing call history data are transmitted along the actual time axis from the mobile phone 2 so that the latest order including the outgoing call order data and incoming call order data can be understood, and these data are included. If the data is sent in the above list format, the hands-free device 1 displays the received data in the order of notification without reference to the date and time of call and date and time of call reception contained in the received data as described above. However, in the case of only displaying the incoming call history, they are displayed according to the display order on the mobile phone 2 .

Here, when displaying all history data, the hands-free device 1 can grasp the latest data of the outgoing history data and the latest data of the incoming history data. can be difficult to identify. Therefore, in this example, when displaying all history data, the control device 12 compares the outgoing date and time included in outgoing call history data with the incoming date and time included in incoming call history data, and selects the one with the latest date and time as the latest data. display as For example, in the case of five records of incoming call history data and five records of outgoing call history data, the control device 12 sorts ten records in order of date and time and displays them in this order. As a result, in most cases, it is possible to display outgoing call history data and incoming call history data in order along the user's actual time axis. However, if the time stamp function of the mobile phone 2 is up to "minutes", if Mr. A receives a call at 12:00:00 and calls Mr. B at 12:00:30, the date and time of the call will be Since the date and time of the incoming call is exactly the same as 12:00, the control device 12 performs a predetermined rearrangement process such as displaying the outgoing call as the newest than the incoming call, or vice versa.

Also, if the latest order of the three incoming call history data (A to C) received by wireless communication with PBAP can be grasped as described above, and the latest order of outgoing call history data (D to F) received by PBAP can be grasped. , the control device 12 performs rearrangement processing by comparing the dates and times of the originating history data and the receiving history data as follows.

First, the controller 12 compares the dates and times of A and D, making the newest first (eg A), then comparing B and D and making the newest second (eg B). Next, compare C and D and make the newest third (eg D), then compare the dates and times of C and E and make the newest fourth (eg C). Next, for the remaining E and F, since E is the latest, the control device 12 assigns E to the fifth and F to the sixth. If the compared dates and times are the same, the control device 12 sorts them according to a predetermined sorting rule such that outgoing calls are prioritized over incoming calls, or vice versa.

In addition, in the mobile phone 2, when transferring phone book data, it is necessary to convert the data format of the phone book data into the data format of "vCard" defined by the Bluetooth communication standard and transfer it. There is a circumstance that book data is generally updated less frequently than outgoing call history data and incoming call history data. Therefore, even if the control device 12 receives the outgoing call history data and the incoming call history data from the mobile phone 2 by the Bluetooth communication unit 13 first, and then receives the phonebook data from the mobile phone 2 by the Bluetooth communication unit 13. good. Further, the control device 12 receives call history data and incoming call history data from the mobile phone 2 by the Bluetooth communication unit 13, and thereafter, only when the user performs a predetermined operation on the operation unit 14, the call is received from the mobile phone 2. The book data may be received by the Bluetooth communication unit 13 .

Further, whether the telephone book data is to be transferred or automatically transferred by such user operation is set by the user by selecting manual transfer or automatic transfer in the hands-free device 1, and transfer processing is performed according to this setting. may be performed. With the automatic transfer setting set to "do not transfer", the user can perform a manual transfer operation after the HFP wireless connection in S9 to transfer only the phonebook data. However, due to this manual transfer operation, the wireless communication connection by HFP in S9 is disconnected, and the wireless communication connection by PBAP is established. to connect to wireless communication and enable hands-free calling.

If you set this "Do not transfer", you can receive the outgoing call history data and incoming call history data, which are frequently updated, with priority over the phone book data, which is less frequently updated. Although data conversion is not required to transfer incoming call history data, data conversion is required to transfer phone book data. It can be received with priority over data. 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 using the transfer protocol can be performed early, and subsequent communication using the hands protocol can be performed early, so when the mobile phone is brought into the vehicle, the time required to make a hands-free call can be shortened. . Furthermore, it is possible to select whether or not to receive telephone directory data whose data update frequency is low and whose transfer time is long, as required, thereby enhancing convenience.

When phone book data is transferred as necessary by the above manual transfer operation of the user, communication using the Humphrey protocol is automatically executed when the transfer is completed. , it is possible to make a hands-free call, which improves convenience. Furthermore, when the telephone directory data is transferred by the manual transfer operation, only the telephone directory data is stored in the non-volatile storage memory 17, and the stored data is transferred to the hands-free device 1 next time. It is preferable to read out from the storage memory 17 at startup and use it as telephone directory data.

Further, the control device 12 may store the outgoing history data, the incoming history data, and the phone book data received from the mobile phone 2 in the working memory 16 by 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 outgoing call history data, incoming call history data, and phonebook data received from the mobile phone 2 in the work memory 16, the mobile phone ID individually assigned to the mobile phone 2 received from the mobile phone 2 and A link key is generated based on the device ID individually given to the hands-free device 1, and the generated link key and various data are associated with each other and stored in the work memory 16.例文帳に追加After that, when the control device 12 receives the mobile phone ID from the mobile phone 2, it regenerates the link key based on the received mobile phone ID and the device ID, and associates it with the generated link key. Various data stored in the working memory 16 are updated.

Next, the HFP processing of S2 in the above-described flowchart of FIG. 4 will be described in detail. FIG. 18 is a flowchart showing details of the flow of HFP processing according to this embodiment.

When the control device 12 determines that a communication line has been established with the mobile phone 2 existing within the Bluetooth communication range, it connects (activates) wireless communication by HFP (S151), and the mobile phone 2 is in communication. (S152). Whether the mobile phone 2 is on call or on standby is notified by HFP wireless communication, received by the hands-free device 1, and determined based on the received communication state. Incidentally, S151 corresponds to the processing of S2.

Here, when the control device 12 determines that the mobile phone 2 is not on the phone, that is, is on standby waiting for an incoming call (S152 "No"), it disconnects the wireless communication with the connected HFP. (End) (S154), and the control device 12 connects wireless communication by PBAP (S155). In other words, if the mobile phone 2 is not in a call, the control device 12 immediately and automatically disconnects the connected wireless communication by HFP and automatically connects the wireless communication by PBAP, thereby enabling the transmission from the mobile phone 2. The Bluetooth communication unit 13 receives the outgoing call history data, incoming call history data, and telephone directory data.

Further, when the control device 12 determines that the mobile phone 2 is in the middle of a call (S152 "YES"), the control device 12 determines that the call may be executed as a hands-free call using the hands-free device 1. maintain radio communications. Whether or not this call is executed basically depends on the mobile phone 2. When the mobile phone 2 establishes wireless communication connection in HFP during a call, the received voice is automatically sent to the Bluetooth communication unit 13. , and on the other hand, there are cases where the reception voice is transmitted to the Bluetooth communication unit 13 by operating the mobile phone 2 .

Then, the control device 12 determines whether or not the mobile phone 2 has ended the call (S153), and when it determines that the mobile phone 2 has ended the call (S153 "Yes"), (S154 "No"), and the control device 12 connects the wireless communication by PBAP (S155). That is, if the mobile phone 2 is in a call, the control device 12 disconnects the connected wireless communication by HFP after the end of the call and connects the wireless communication by PBAP so that the user can make a hands-free call. , the Bluetooth communication unit 13 receives the outgoing call history data, the incoming call history data, and the phonebook data transmitted from the mobile phone 2 . Incidentally, S152 and S153 correspond to the processing between S3 and S4.

When the mobile phone 2 is connected to the hands-free device 1 in this way, the hands-free device 1 determines whether the mobile phone 2 is busy, and if so, switches to wireless communication connection using PBAP. Then, since it is impossible to shift to a hands-free call, the HFP wireless communication is maintained, and the PBAP wireless communication connection is not performed during the call. Then, when it is determined that the call has ended, the HFP wireless communication is disconnected, and the PBAP wireless communication connection is established. As a result, when the mobile phone 2 is talking alone, it is possible to smoothly switch to a hands-free call.

Further, the control device 12 may receive and store, as incoming call history data, a history of received calls and a history of unanswered calls (missed calls) separately from the cellular phone 2 .
FIG. 19 is a diagram showing another example of transition of display screens when the user performs a call operation from the incoming call history according to the present embodiment. When the control device 12 determines that the user has pressed the "history button" 4a and then the "incoming call history button" 4c to make a call based on the incoming call history, it is stored in the work memory 16. 19(b) and 19(c), by referring to the incoming call history data stored in the work memory 16 and by referring to the telephone directory data stored in the working memory 16, and causing the display unit 15 to display the outgoing call operation screen based on the incoming call history as shown in FIGS. is an icon that indicates an incoming call that has been answered (a combination of a handset and an arrow), and an icon that indicates an incoming call that has not been answered (missed call) (a combination of a handset and an X mark). ) are displayed for each data.

In this embodiment, the case where outgoing call history data, incoming call history data, and phone book data transferred from the mobile phone 2 are stored in the work memory 16, and the case where the phone book data is stored in the storage memory 17 will be described. However, the configuration may be such that the outgoing call history data, the incoming call history data, and the telephone directory data transferred from the mobile phone 2 are stored in the storage memory 17 . With such a configuration, even when the hands-free device 1 is powered off, the outgoing call history data, incoming call history data, and phonebook data stored in the storage memory 17 are retained.

As described above, the hands-free device 1 of the present embodiment eliminates simultaneous connections between HFP and PBAP as much as possible as a more reliable processing procedure for HFP and PBAP. Make a split serial connection. As a result, communication processing can be reliably and stably performed for mobile phones compatible with HFP and PBAP of many manufacturers. In addition, it is possible to perform PBAP and HFP processing with simple processing without complicating the processing in the hands-free device 1 .

Further, when the hands-free device 1 of the present embodiment determines that confirmation has not been completed by the time of the previous access request, it prompts the user to confirm again. Since processing is automatically performed according to the confirmed contents, it is possible to easily improve convenience and ensure security.

In addition, the hands-free device 1 of the present embodiment can access the phonebook data by an unspecified DA application at a location unknown to the user, unless the user explicitly permits each DA application to access the phonebook data. is not accessed, it is possible to eliminate user's concerns about security.

In addition, the hands-free device 1 of the present embodiment, when making a call to the mobile phone network or receiving a call from the mobile phone network while connecting to the wireless communication by the HFP after disconnecting the wireless communication by the PBAP, performs the work at that time. Out of the outgoing history data and the incoming history data stored in the memory 6, the outgoing history data and the incoming history data with the oldest outgoing date and time and incoming date and time are erased, and the outgoing history data and the incoming history data of the device are stored in the working memory 6. store in addition to As a result, the latest outgoing call history data and incoming call history data of the own device can be stored each time a call is made to the mobile phone network or an incoming call is made from the mobile phone network.

Further, after establishing a communication line with the mobile phone 2, the hands-free device 1 of the present embodiment determines whether or not the mobile phone 2 is busy after connecting the HFP in S2, When the mobile phone 2 is in a call, after the call ends, PBAP wireless communication is connected to receive call history data, incoming call history data and telephone directory data from the mobile phone 2 . As a result, a hands-free call can be made without being affected by the transfer of outgoing call history data, incoming call history data, and phone book data from the mobile phone 2. FIG.

In addition, the hands-free device 1 of the present embodiment establishes a Bluetooth communication line with the mobile phone 2, and stores outgoing call history data and incoming call history data stored before the mobile phone 2 establishes the Bluetooth communication line. When it is received from the mobile phone 2, its outgoing history data and incoming history data are stored in the work memory 16 in the same way as the outgoing history data and incoming history data of its own device. Allows outgoing call operation based on history data. As a result, it is possible to make a call by selecting a desired telephone number from among outgoing call history data and incoming call history data automatically transferred from the mobile phone 2, and to make a call from the outgoing call history data and incoming call history data of the own device. A desired telephone number can be selected and dialed, and convenience can be improved.

Further, when a display request for outgoing call history data or incoming call history data is generated, the hands-free device 1 according to the present embodiment displays the same telephone number as the incoming and outgoing telephone numbers stored as outgoing call history data or incoming call history data in the work memory 16 . is stored, the registered name corresponding to the telephone number is displayed. As a result, the outgoing call history data and the incoming call history data received from the mobile phone 2 can be displayed using the registered names stored in the phonebook data.

In addition, the hands-free device 1 of the present embodiment displays the call history data of its own device as the latest call date and time on the display screen displaying a list of the call history data each time the call processing is performed. In addition, the hands-free device 1 of the present embodiment displays the incoming call history data of the own device as the incoming call history data with the latest incoming call date and time on the display screen displaying the list of incoming call history data each time the hands-free device 1 of the present embodiment performs incoming call processing. As a result, the date and time acquired by the mobile phone 2 and the date and time acquired by the hands-free device 1 do not match, and the outgoing date and time of the outgoing call history data automatically transferred from the mobile phone 2 and the incoming date and time of the incoming call history data automatically match. To prevent a user from having a sense of incongruity due to a difference in date and time between devices, even when the date and time of transmission of outgoing history data and the date and time of reception of incoming history data of a device do not match on the time axis. be able to.

In addition, the hands-free device 1 of the present embodiment stores outgoing call history data, incoming call history data, and phonebook data in the work memory 16 by distinguishing them for each mobile phone 2 . As a result, outgoing call history data, incoming call history data and phone book data can be managed for each mobile phone 2 . In addition, the hands-free device 1 of the present 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 . As a result, there is no need to receive the phone book data from the mobile phone 2 each time the device power is turned on, and the user can quickly use the phone book data stored in correspondence with his/her own mobile phone 2. It is possible to greatly improve convenience when using the phone book function.

Furthermore, when the hands-free device 1 of the present embodiment collectively displays the outgoing call history data, the incoming call history data, and the missed call history data as all history data, displays only the phone number with the most recent call date and time. Thereby, history information can be increased.

(Second embodiment)
Next, a second embodiment will be described.
In the first embodiment, access to the entire telephone directory data is controlled for each DA application. This is an embodiment for controlling permission.

In this case, the specific item refers to each of a plurality of item data constituting the telephone directory data, and individual item data corresponding to a plurality of item data belonging to a predetermined group. There is a case to say.

FIG. 20 is a diagram for explaining an example of item data constituting telephone directory data.
As shown in FIG. 20, the telephone directory data DPH includes first item data D1 to sixth item data D6, which are a plurality of item data, and group data DG.

More specifically, the first item data D1 stores a name corresponding to the item name, the second item data D2 stores an address, and the third item data D3 stores a telephone number. The fourth item data D4 stores the date of birth, the fifth item data D5 stores the first mail address (for example, the carrier mail address of the mobile phone 2), and the sixth item data D6 stores a second mail address (for example, an e-mail address).

Also, the group data DG can store a plurality of group names (for example, a "local" group and a "family" group) specifying groups to which corresponding first item data D1 to sixth item data D6 belong.

FIG. 21 is a processing flowchart of the second embodiment.
In FIG. 21, the same reference numerals are given to the same parts as in the first embodiment of FIG.
In FIG. 21, the difference from FIG. 4 is that a specific item target process (S20) for a specific item is performed after the process of step S12.

The processing from step S1 to step S15 is the same as that of the first embodiment, so the detailed description thereof will be used.

In a state in which the processing up to step S12 has been completed and whether or not the DA application can access the entire telephone directory data DPH at that point in time has been determined, when the DA application issues an access request to the telephone directory data DPH, the controller 12 , the process proceeds to the specific item target process (S20).

FIG. 22 is a processing flowchart of specific item target processing.
First, the control device 12 determines whether or not access to the telephone directory data DPH is permitted (S21).
If access to the DA application is denied at that time (S21 "No"), the control device 12 returns control to the D application for processing because there is no access to the specific item in the first place. is ended (S27).

If access to the DA application is permitted at this point in time (S21 "Yes") and access to a specific item is requested by the DA application (S22 ), it is determined whether or not the user has confirmed whether or not access to the specific item is permitted by the time of the previous access (S23).

If the control device 12 (determining unit 101) determines that the user's access permission for the specific item has been confirmed by the time of the previous access (S23 "permission confirmed"), the telephone directory data DPH is processed by the DA application. Access to the specific item is permitted (S26), control is returned to the DA application concerned, and the process ends (S27).

If the control device 12 (determining unit 101) determines that the confirmation of whether or not the user can access the specific item has not been confirmed by the time of the previous access (S23 “unconfirmed”), the control device 12 (inquiry unit 102) , the display screen of the display unit 15 (inquiry screen display unit 103) notifies to that effect (S24).

FIG. 23 is an explanatory diagram of an example of an inquiry screen.
FIG. 23A is an example of an inquiry screen when requesting access to Mr. A's address (second item data D2 in the above example) as a specific item.

As shown in FIG. 23A, a dialog box 121 as an inquiry screen is displayed on the display screen 15A of the display unit 15, and "App X is permitted to access Mr. A's address in the phone book data." Are you sure?" is displayed, along with a check box 122 for instructing whether or not to confirm whether or not to confirm the user's access permission when the next access request is made by the DA application. and a rejection button 124 for inputting an instruction to deny the current access request by the DA application are displayed.

In the above configuration, in the example of FIG. 23A, "application X" is the DA application name for the user to specify the DA application.
Also, the check box 122 toggles between a checked state and a non-checked state every time the user touches it.

In addition, when the user touches the permission instruction button 123, if the check box 112 is checked, the control device 12 is notified that the address of Mr. A in the telephone book data will be sent to the address of Mr. A in the telephone book data for the DA application from this time onward as well. is entered.

If the check box 112 is unchecked, the DA application is permitted to access Mr. A's address in the telephone directory data this time. An instruction to confirm access permission is input.

Also, when the user touches the refusal instruction button 114, if the check box 112 is checked, the control device 12 is notified that the address of Mr. A in the telephone book data will be sent to the address of Mr. A in the telephone book data for the DA application in the next time as well as this time. is entered to deny access to

If the check box 112 is unchecked, access to Mr. A's address in the telephone book data for the DA application is denied this time, but next time the access is requested again by the DA application, the user An instruction to confirm access permission is input.

Subsequently, the control device 12 determines whether or not the DA application that requested the access is permitted to access Mr. A's address in the telephone directory data based on the input of the user's instruction ( S25).

When the control device 12 determines that the DA application that requested the access is permitted to access Mr. A's address in the telephone directory data (S25 "YES"), the DA application in the telephone directory data access to the address of Mr. A (S26), control is returned to the DA application, and the process is terminated (S27).

Further, when the control device 12 determines that the DA application that made the access request is denied access to the address of Mr. A in the telephone directory data (S25 "NO"), Access is denied (S28), control is returned to the D application, and processing is terminated (S27).

On the other hand, if the control device 12 determines that the denial of access by the user has been confirmed by the time of the previous access (S23 "denial confirmed"), it denies access to the telephone directory data by the DA application (S28). , the control is returned to the D application and the process is terminated (S27).

FIG. 23B shows the address of the local group as a specific item (in the case of the above example, the second item data D2 when the group data DG includes "local": more specifically, the loop data DG This is an example of an inquiry screen when requesting access to Mr. A's and Mr. C's addresses including "Local".

As shown in FIG. 23(B), a dialog box 121 as an inquiry screen is displayed on the display screen 15A of the display unit 15, and "App X is permitted to access the address of the local group in the phonebook data." Are you sure?" is displayed, along with a check box 122 for instructing whether or not to confirm whether or not to confirm the user's access permission when the next access request is made by the DA application. and a rejection button 124 for inputting an instruction to deny the current access request by the DA application are displayed.

In the above configuration, also in the example of FIG. 23B, "application X" is the DA application name for the user to specify the DA application.
Also, the check box 122 toggles between a checked state and a non-checked state every time the user touches it.

In addition, when the user touches the permission instruction button 123, if the check box 122 is checked, the control device 12 asks Mr. A's address in the telephone book data for the DA application from this time onwards. is entered.

If the check box 122 is unchecked, the DA application is permitted to access Mr. A's address in the telephone directory data this time. An instruction to confirm access permission is input.

When the user touches the refusal instruction button 124, if the check box 122 is checked, the control device 12 is notified that the DA application belongs to the local group in the telephone book data from now onwards as well. An instruction is entered to deny access to a person's address.

If the check box 122 is unchecked, access to the address of (a person belonging to) a local group in the telephone directory data for the DA application is denied this time, but the next time, the access will be denied by the DA application again. At the time of access request, an instruction is input for confirming whether or not access is permitted for the user.

Subsequently, based on the input of the user's instruction, the control device 12 determines whether or not the DA application that has made the access request is permitted to access the address of (a person belonging to) the local group in the telephone directory data. (S25).

If the control device 12 determines that the DA application that made the access request is permitted to access the address of (a person belonging to) the local group in the telephone directory data (S25 "YES"), the DA application access to Mr. A's address in the telephone directory data (S26), control is returned to the DA application, and the process is terminated (S27).

If the control device 12 determines that the DA application that made the access request is denied access to the address of (a person belonging to) the local group in the telephone directory data (S25 "NO"), the DA application Access to the Tonomachi data by the application is denied (S28), control is returned to the D application, and processing is terminated (S27).
On the other hand, if the control device 12 determines that the denial of access by the user has been confirmed by the time of the previous access (S23 "denial confirmed"), it denies access to the telephone directory data by the DA application (S28). , the control is returned to the D application and the process is terminated (S27).

In this way, every time an access request is made from the DA application to a specific item constituting the phone book data DPH of the mobile phone 2, the control device 12 determines whether permission has been confirmed, refusal has been confirmed, or not. If it is determined that it has not been confirmed by the time of the previous access request, it will prompt you to confirm again, and if it has been confirmed by the time of the previous access request, according to the confirmed contents Since the processing is performed automatically, it is possible to easily achieve both convenience improvement and security assurance.

According to the above configuration, unless the user clearly permits each DA application to access each item data that constitutes the telephone directory data, an unspecified DA application can be used to make a call at a location unknown to the user. Since each item data constituting the book data is not accessed, it is possible to eliminate the user's anxiety about security.

Further, when the hands-free device 1 of the present embodiment determines that confirmation has not been completed by the time of the previous access request, it prompts the user to confirm again. Since processing is automatically performed according to the confirmed contents, it is possible to easily improve convenience and ensure security.

In addition, the hands-free device 1 of the present embodiment is not accessible to the user by an unspecified DA application unless the user clearly permits each DA application to access specific items that make up the telephone directory data. Since there is no access to the specific items that make up the phone book data at the location, it is possible to eliminate the user's concerns about security.

A program executed by the hands-free device 1 of each of the above-described embodiments is pre-installed in a ROM or the like and provided. The program executed by the hands-free device 1 of each embodiment described above is a file in an installable format or an executable format, and can be stored on a CD-ROM, a flexible disk (FD), a CD-R, a DVD (Digital Versatile Disk), or the like. may be configured to be recorded and provided on a computer-readable recording medium.

Furthermore, the programs executed by the hands-free device 1 of each of the above-described 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 program executed by the hands-free device 1 of each of the above-described embodiments may be provided or distributed via a network such as the Internet.

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

The hands-free device 1 may be composed of a dedicated hands-free device that mainly realizes a hands-free function, or may be a vehicle audio device that reproduces CDs or radios with a hands-free function. Also, the hands-free device 1 may be configured to have portability (portable type).

The mobile phone 2 and the hands-free device 1 are not limited to the configuration in which Bluetooth communication is performed, but may be a configuration in which other short-range wireless communication is performed, or a configuration in which wired communication is performed.

The outgoing call history data, the incoming call history data and the phonebook data received from the mobile phone 2 are stored in the storage memory 17, and each time the outgoing call history data, the incoming call history data and the phonebook data are received from the mobile phone 2, The configuration may be such that history data and telephone directory data are updated and stored. Also, the outgoing history data, the incoming history data and the telephone directory 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.

The number of outgoing call history data and incoming call history data that can be stored in the work memory 16 may be one. In this case, when the hands-free device 1 performs outgoing call processing and incoming call processing, the outgoing call history data and incoming call history data received through the wireless communication connection by PBAP are always deleted.

Also, in the hands-free device 1, a plurality of call history data and a plurality of call history data are displayed at the same time, but they may be displayed one by one. In this case, for example, the latest data may be displayed first, and then the latest data may be displayed in order by operating the operation unit 14 .

The number of outgoing call history data and incoming call history data that can be stored in the work memory 16 may be one. In this case, when the hands-free device 1 performs outgoing call processing and incoming call processing, the outgoing call history data and incoming call history data received through the wireless communication connection by PBAP are always deleted.

When a Bluetooth communication line is established between the mobile phone 2 and the hands-free device 1, the user can operate the hands-free device 1 or the mobile phone 2 without being limited to the configuration of automatically transferring outgoing call history data and incoming call history data. The configuration may be such that outgoing call history data, incoming call history data, and telephone directory data are transferred as a condition.

When outgoing call history data, incoming call history data, and phone book data received from the mobile phone 2 are distinguished for each mobile phone 2 and stored in the working memory 16, the mobile phone 2 and the data stored in the working memory 16 are stored in the working memory 16. The configuration is not limited to the configuration in which the two are associated by the method of generating the link key, and a configuration in which the two are associated by another method may be used.

1 hands-free device 2 mobile phone 3 vehicle 12 control device 13 Bluetooth communication unit 14 operation unit 15 display unit 16 work memory 17 storage memory 18 microphone 19 speaker 40 base station 101 determination unit 102 inquiry unit 103 inquiry screen display unit 104 instruction input unit 105 status storage unit

Claims (8)

A hands-free device that enables hands-free calling by being wirelessly connected to a mobile phone that stores phone numbers and phone book data in which registered names are registered corresponding to the phone numbers,
a determination unit that determines, when an application operable on the hands-free device requests access to the telephone directory data, whether or not the user has already confirmed whether or not the application requesting the access has been confirmed as to whether or not the access request is permitted; ,
an inquiry unit that inquires of the user whether or not to permit access when the confirmation by the user has not yet been made;
hands-free device with an inquiry screen display unit for displaying an inquiry screen for inquiring whether or not to permit access to the user;
The inquiry unit causes the inquiry screen display unit to display the inquiry screen,
Hands-free device according to claim 1. Equipped with an instruction input unit for performing instruction input for the inquiry,
A hands-free device according to claim 1 or claim 2. a situation storage unit that associates and stores specific information that specifies the application and situation information that stores the confirmation situation;
The determination unit makes the determination by referring to the situation storage unit.
A hands-free device according to any one of claims 1 to 3. wherein the telephone directory data contains item data for a plurality of items including the registered name in association with the telephone number;
When the application requests access to any of the item data, the determining unit determines whether or not the user has already confirmed whether or not the access request to the item data is permitted for the application requesting the access. ,
The inquiry unit inquires of the user whether or not to permit access to the item data if the confirmation by the user has not yet been made;
A hands-free device according to any one of claims 1 to 4. a status storage unit for storing specific information specifying the application and status information storing status of confirmation for each item data in association with each other;
The determination unit refers to the situation storage unit and performs the determination for each item data.
A hands-free device according to claim 5. In the telephone directory data, one or a plurality of groups to which the item data corresponding to the telephone number belongs can be registered for each telephone number,
When the application requests access to the item data belonging to one of the groups, the determination unit determines whether or not the user has already confirmed whether or not the application requesting access can request access to the group. to determine
The inquiry unit inquires of the user whether or not to permit access to the item data belonging to the group when the confirmation by the user has not yet been made.
A hands-free device according to claim 5 or claim 6. A hands-free device that controls a hands-free device that enables hands-free communication by wirelessly connecting to a mobile phone that stores telephone numbers and telephone directory data in which registered names are registered corresponding to the telephone numbers. A control method comprising:
a step of determining, when an application operable on the hands-free device requests access to the phonebook data, whether or not confirmation by the user has already been made as to whether or not the access request has been made for the application requesting access;
inquiring of a user whether or not to allow access if confirmation by the user has not yet been made;
A method of controlling a hands-free device with

Images