JP2009087123A - Remote control by use of onboard device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problem that access (illegal access) to equipment outside a vehicle from an unauthorized person is permitted. <P>SOLUTION: A remote control system 1 includes an onboard device 2, a communication device 3, an authentication device 4, and the device 5 outside the vehicle, and remotely controls the device 5 outside the vehicle from the onboard device 2. Remote control can be executed only when Bluetooth communication is performed between the onboard device 2 and a communication device 3a. No remote control is performed even if Bluetooth communication is performed between the onboard device 2 and the communication device 3b. The communication device 3a is owned by a person having a right for remotely controlling the device 4 outside the vehicle. The communication device 3b is owned by a person having no right for remotely controlling the device 4 outside the vehicle. More specifically, the communication device 3 functions as an authentication key for remote control. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a technique for remotely controlling an electronic device.

  Commercialized in-vehicle devices employ short-range wireless communication such as Bluetooth (registered trademark). Applications of this communication are mainly for taking in music from an acoustic device to a vehicle-mounted device and for hands-free calling via a mobile phone. Moreover, the user can freely change the target of the short-range wireless communication (such as an acoustic device or a mobile phone) (Non-Patent Document 1).

The user demands the expansion of the aforementioned applications. In other words, future in-vehicle devices are required to realize remote control of electronic devices. Known are a network (Patent Document 1) between an in-vehicle device, a mobile phone, and a server (Patent Document 1), and a network (Patent Document 2) between a mobile phone, a server, and a home electronic device (home appliance). These technologies enable networking between in-vehicle devices, mobile phones, servers, and external devices.
Panasonic HDD Car Navigation Station CN-HDS965TD / CN-HDS945TD / CN-HDS915TD Instruction Manual JP-T-2006-523416 JP 2007-4579 A

  Background art permits access (unauthorized access) to an external device by a person who does not have a legitimate access right. For example, a person who steals an in-vehicle device can illegally operate another person's device from the in-vehicle device via his / her mobile phone. This is because the object of short-range wireless communication can be changed freely.

  The present invention provides the following in-vehicle device and a program for realizing the in-vehicle device. The processing device included in the in-vehicle device includes an authenticator (this column) to be transmitted to the authentication device when a communication device (in this column, simply referred to as a communication device) to be used for connection to the authentication device is registered. Then, it is simply for registering an authenticator. The authentication device is connected to a communication line (network) and confirms the validity of the connection request (identity confirmation). The connection request is preferably made when the external device is remotely controlled by the in-vehicle device. The external device is connected to a communication line. The off-vehicle device may include an authentication device. The communication device performs short-range communication and network communication. The short distance is a distance that enables communication in the passenger compartment.

  The processing device is connected to the output device and causes the output device to output a second request as the output device outputs the first request. The first request requests registration of the communication device. The second request requests registration of an authenticator. The processing device causes the output device to output the first request after the output of the second request.

  When the output device is a display device, conditions for the processing device to display a registration screen on the display device are registration of an identifier to be transmitted to the authentication device and registration of an authenticator. The registration screen is for registering a communication device. The second registration screen that the processing device displays on the display device includes a registration field for registering the authenticator. The registration field does not display the authenticator registered before the second registration screen is displayed.

  The processing device is connected to the near field communication device and controls the near field communication device to realize near field communication with the communication device. This near field communication enables communication between the in-vehicle device and the outside device or the authentication device via the communication device. The communication device transmits the authenticator received by the short-range communication to the authentication device at the time of registration or remote control. In addition, the communication device may transmit the registered authenticator to the authentication device as the device identifier of the in-vehicle device is transmitted to the authentication device. In this case, what the communication device transmits to the authentication device during remote control is the device identifier authenticated by the authentication device.

It should be noted that the present invention is not limited to the in-vehicle device but widely used for information processing devices (for example,
Node computers and desktop computers).

  The present invention prevents spoofing by treating a communication device as an authentication key. A person who does not know the authenticator is forced to register an inappropriate authenticator as an authenticator to be transmitted to the authentication device when the communication device to be used for connection to the authentication device is registered. is there.

  1 to 7 show the best mode for carrying out the present invention (hereinafter referred to as the present embodiment).

  <Outline of Remote Control System> FIG. 1 shows an outline of the remote control system 1. The remote control system 1 includes an in-vehicle device 2, a communication device 3, an authentication device 4, and an external device 5, and aims to remotely control the external device 5 from the in-vehicle device 2. In the present embodiment, the communication device 3 and the external device 5 are a mobile phone and a household electronic device (for example, a recorder, a monitoring camera, a room light, an air conditioner, a microwave oven, a water heater, etc.).

  Remote control is performed via a network (for example, the Internet) 6. Communication between the in-vehicle device 2 and the communication device 3 is realized by a short-range communication technique. The short-range communication employed by the present embodiment is Bluetooth (registered trademark) communication. Communication between the communication device 3 and the authentication device 4 is realized by Internet technology. Communication between the authentication device 4 and the vehicle exterior device 5 is also realized by Internet technology.

  The remote control according to the present embodiment is executed only when the Bluetooth communication is performed between the in-vehicle device 2 and the communication device 3a. In other words, even if the Bluetooth communication is performed between the in-vehicle device 2 and the communication device 3b, the remote control is not executed. Here, the communication device 3a is owned by a person (for example, a person who knows the identifier and the authenticator) who has the authority to remotely control the vehicle exterior device 4. The communication device 3b is owned by a person who does not have the authority to remotely control the external device 4 (for example, a person who has stolen the in-vehicle device 2). That is, the communication device 3 functions as an authentication key for remote control. This function is realized by the following technology.

  In addition, the provider who provides the remote control service passes a regular identifier and an authenticator necessary for remote control to a regular user before starting the service.

  <Display Example> FIG. 2 shows a registration screen 10 for registering the communication device 3 to be used for connection to the authentication device 4. The registration screen 10 includes one or more option switches 11, a “BACK” switch 12, and an “OK” switch 13. The option switch 11 represents a candidate for the communication device 3 to be used for connection to the authentication device 4. The pairing between the candidate communication device 3 and the in-vehicle device 2 (communication device registration work for using the candidate communication device 3 in the in-vehicle device 2) is completed before the registration screen 10 is displayed. That is, the in-vehicle device 2 registers the communication device 3 to be used for connection to the authentication device 4 when the specific option switch 11 and the “OK” switch 13 are selected.

  FIG. 3 shows a second registration screen 14 for registering an identifier to be transmitted to the authentication device 4 and an authenticator to be transmitted to the authentication device 4. The second registration screen 14 is displayed before the registration screen 10 is displayed. The second registration screen 14 includes two registration fields 15 a and 15 b, a “BACK” switch 16 and an “OK” switch 17. The identifier and the authenticator displayed in the registration field 15 are input while the second registration screen 14 is displayed. In other words, the identifier and the authenticator registered before the second registration screen 14 is displayed are not displayed in the registration field 15. That is, the in-vehicle device 2 registers the identifier to be transmitted to the authentication device 4 and the authenticator to be transmitted to the authentication device 4 when the registration field 15 is filled and the “OK” switch 17 is selected. It is.

  <Event Flow> FIG. 4 shows an event flow of the remote control system 1. After registration (S1) of the identifier (ID), the authenticator (AC) and the communication device (CDID) 3, the user requests remote control of the external device 5 from the in-vehicle device 2 (RCRQ) (S2). ). After this request, the communication device (registered communication device) 3 registered on the in-vehicle device 2 and the registration screen 10 exchanges the link key in order to establish Bluetooth communication (S3, S4). If the communication device 3 around the in-vehicle device 2 is not registered on the registration screen 10, communication between the in-vehicle device 2 and the authentication device 4 is not performed. After the establishment of Bluetooth communication, the in-vehicle device 2 transmits to the registered communication device 3 the identifier (ID, registered identifier) registered on the second registration screen 14 and the authenticator registered on the second registration screen 14. (AC, registered authenticator) (S5). That is, the registered identifier (ID) and the registered authenticator (AC) are transmitted to the authentication device 4 through the registered communication device 3. The authentication device 4 transmits the authentication result (RE) via the registered communication device 3 (S6). When the authentication is successful, the in-vehicle device 2 transmits a remote control request (RCRQ) to the authentication device 4 via the registered communication device 3 (S7). On the other hand, when the authentication fails, the in-vehicle device 2 does not transmit a remote control request (RCRQ) to the authentication device 4 via the registered communication device 3. After transmitting the remote control request (RCRQ), the authentication device 4 transmits a control command (CMND) corresponding to the remote control request (RCRQ) to the vehicle exterior device 5. After the transmission of the control command (CMND), what is transmitted by the authentication device 4 via the registered communication device 3 is a control result (RE2). The control result (RE2) indicates the success or failure of the control. After the transmission of the control result (RE2), the in-vehicle device 2 indicates the success or failure of the control.

  <Hardware of In-vehicle Device> FIG. 5 shows the hardware of the in-vehicle device 2. The in-vehicle device 2 includes a processing device 20. The processing device 20 is connected to the input device 21, the secondary storage device 22, the short-range communication device 23, and the output device 24.

  The processing device 20 includes the basic elements of a computer. The basic elements are I / O, ROM, CPU, RAM, and the like.

  The program stored in the ROM is an OS (for example, Windows (registered trademark) CE) or an application. The internal data stored in the ROM is a background image, a switch image, and the like.

  FIG. 6 shows RAM area allocation. The RAM 30 has an area 31 for holding a program and internal data, an area 32 for holding an identifier, an area 33 for holding an authenticator, an area 34 for holding an identifier of the communication device 3, An area 35 for holding a link key and a work area 36.

  The input device 21 is embodied by a touch panel and an infrared remote controller. The secondary storage device 22 is embodied by an SD (registered trademark) memory or a hard disk drive (HDD). The short-range communication device 23 is embodied as a Bluetooth (registered trademark) communication unit. The embodiment of the output device 24 is a liquid crystal display device.

  <Registration Process> The registration process is realized by the CPU executing the aforementioned program. FIG. 7 shows the flow of registration processing.

  The registration of the identifier and the authenticator is requested by displaying the second registration screen 14 (S11). The input identifier and the input authenticator are held in the area 32 and the area 33 of the RAM 30, respectively.

  Whether or not the registration is complete depends on whether or not the “OK” switch 17 is selected (S12). That is, whether or not the registration is complete is determined based on the display coordinate value of the “OK” switch 17 and the input value by the input device 21. These values are held in the work area 36 of the RAM 30.

  When the registration is completed (“y” in S12), the input identifier and the input authenticator are transferred from the RAM 30 to the secondary storage device 22. That is, the in-vehicle device 2 registers an identifier to be transmitted to the authentication device 4 and an authenticator to be transmitted to the authentication device 4. Moreover, the registration of the communication device 21 is requested by displaying the registration screen 10 (S13). The specified device identifier of the communication device 3 is held in the area 34 of the RAM 30.

  Whether or not the registration is complete depends on whether or not the “OK” switch 17 is selected (S14). That is, whether or not the registration is complete is determined based on the display coordinate value of the “OK” switch 14 and the input value by the input device 21. These values are held in the work area 36 of the RAM 30.

  If registration is complete (“y” in S14), the registration process ends. At this time, the device identifier of the designated communication device 3 is transferred from the RAM 30 to the secondary storage device 22. That is, the in-vehicle device 2 registers the device identifier of the communication device 3 to be used for connection to the authentication device 4.

  If registration has not been completed (“n” in S12, “n” in S14), whether or not to cancel the registration process is determined based on the display coordinate values of the “BACK” buttons 12 and 16 and the input value by the input device 21. Based. The determination may be based on display times of the registration screen 10 and the second registration screen 14. For example, the registration process is stopped when the display time exceeds 30 seconds.

  <Communication processing> Communication processing during remote control follows a dial-up network profile (DUN). This profile refers to the device identifier and link key of the communication device 3 registered on the registration screen 10.

  The identifier and the authenticator registered on the registration screen 14 are stored based on a cache function of a browser (for example, NetFront (registered trademark)). Of course, the identifier and the authenticator may be read from the storage device 22 into the login API and transmitted to the authentication device 4 without being limited to the browser cache function.

  Regarding the other technical matters, the present specification incorporates the contents of “Specification of the Bluetooth System” and the contents of Japanese Patent Application Laid-Open No. 2007-4579.

  <Effects of the Present Embodiment> The present embodiment enables the communication device 3 to be treated as an authentication key and prevents spoofing during remote control. That is, the authorized user can prevent a third party such as a person who has stolen the in-vehicle device 2 from remotely operating the out-of-vehicle device 5. This is because a person who does not know the authenticator must register an inappropriate authenticator as an authenticator to be transmitted to the authenticating device 4 in order to use his / her communication device 3b for remote control.

  This embodiment makes it possible to save the trouble of inputting an identifier and an authenticator each time remote control is performed. In other words, it is sufficient for a legitimate user to use his / her communication device 3a as an authentication key. This is because the identifier and authenticator registered on the second registration screen 14 are stored in the in-vehicle device 2.

  What this embodiment makes possible is to more reliably prevent spoofing. That is, the input of the identifier and the authenticator is omitted when transmitting the identifier and the authenticator to the authentication device 4, not when registering the communication device 3. This is because the identifier and authenticator registered before the display of the second registration screen 14 are not displayed in the registration field 15.

  <Modification 1> FIG. 8 shows a screen according to Modification 1. This screen 40 includes a column 41 for displaying the communication device 3 to be used for connection to the authentication device 4, a “REF” button 42 and a “NEW” button 43 for designating the communication device 3. A column 44 for inputting an identifier to be transmitted to the authentication device 4, a column 45 for inputting an authenticator to be transmitted to the authentication device 4, a “BACK” switch 46 and an “OK” switch 47. Even with this screen 40, the user needs to register an authenticator to be transmitted to the authentication device 4 with registration of the communication device 3 to be used for connection to the authentication device 4.

  <Modification 2> FIG. 9 shows an event flow according to Modification 2. A feature of Modification 2 is that authentication processing by the authentication device 4 is requested upon registration (S31 to S35). That is, the reason why the device identifier of the in-vehicle device 2 is transmitted to the authentication device 4 together with the identifier and authenticator registered on the registration screen 14 is to enable authentication by the device identifier of the in-vehicle device 2. After authentication by the authentication device 4, the registered identifier and the registered authenticator are deleted. Moreover, what the in-vehicle device 2 transmits to the authentication device 4 via the communication device 3 registered on the registration screen 10 is the device identifier of the in-vehicle device 2 (S39). In this modification, the display of the registration screen 10 and the registration screen 14 is realized by a browser (for example, NetFront). Of course, the registration screen 10 and the registration screen 14 may be displayed by a function other than the browser. The other steps are as described in the best embodiment.

  <Modification 3> This embodiment can employ biometric authentication such as iris authentication and vein authentication in addition to knowledge authentication such as password authentication. When the speaker outputs a request for registration, the registration operation may be realized by a voice recognition technique.

  The present invention is useful for a car navigation device, a car audio device, and the like.

The figure which shows the outline of the remote control system which concerns on this Embodiment The figure which shows the structure of the registration screen which concerns on this Embodiment The figure which shows the structure of the 2nd registration screen which concerns on this Embodiment. The figure which shows the remote control event which concerns on this Embodiment The figure which shows the hardware of the vehicle-mounted apparatus which concerns on this Embodiment The figure which shows the area allocation (memory map) of RAM which concerns on this Embodiment The figure which shows the flow of the registration process which concerns on this Embodiment The figure which shows the structure of the screen which concerns on the modification 1. The figure which shows the remote control event which concerns on the modification 2.

Explanation of symbols

1 Remote control system 2 In-vehicle device (or information processing device)
DESCRIPTION OF SYMBOLS 3 Communication apparatus 4 Authentication apparatus 5 Outside-vehicle apparatus 11 Registration screen 14 2nd registration screen 15 Registration column 20 Processing apparatus 23 Short-distance communication apparatus 24 Output apparatus

Claims (14)

Programs identified by:
The function that this program implements in the in-vehicle device is to register an authenticator to be transmitted to the authentication device as the communication device to be used for connection to the authentication device is registered. The program of Claim 1 specified by the following matters.
The function that this program realizes in the in-vehicle device is to perform near field communication with the communication device and transmit the authenticator to the authentication device. The program of Claim 2 specified by the following matters.
The function that this program realizes in the in-vehicle device is to transmit the authenticator to the authentication device during remote control. The program of Claim 2 specified by the following matters.
The function that this program realizes in the in-vehicle device is:
Transmitting the registered authenticator to the authentication device as the device identifier of the in-vehicle device is transmitted to the authentication device; and remotely transmitting the device identifier authenticated by the authentication device to the authentication device It is transmitted at the time of control. In-vehicle devices specified by:
The function included in this in-vehicle device registers an authenticator to be transmitted to the authentication device as a communication device to be used for connection to the authentication device is registered. The in-vehicle device according to claim 5 specified by the following matters.
The function included in the in-vehicle device is to perform near field communication with the communication device and transmit the authenticator to the authentication device. The in-vehicle device according to claim 6 specified by the following matters.
The function included in this in-vehicle device is to transmit the authenticator to the authentication device during remote control. The in-vehicle device according to claim 6 specified by the following matters.
The functions included in this in-vehicle device
Transmitting the registered authenticator to the authentication device as the device identifier of the in-vehicle device is transmitted to the authentication device; and remotely transmitting the device identifier authenticated by the authentication device to the authentication device It is transmitted at the time of control. In-vehicle devices specified by:
The processing device included in this in-vehicle device is
Connected to the output device,
In response to outputting the first request to the output device, causing the output device to output a second request,
The first request requests registration of a communication device to be used for connection to an authentication device;
The second request requests registration of an authenticator to be transmitted to the authentication device. The in-vehicle device according to claim 9 specified by the following matters.
It is after the output of the second request that the processing device causes the output device to output the first request. The in-vehicle device according to claim 9 or 10 specified by the following matters.
The processor is
Connected to a near field communication device,
Causing the short-range communication device to perform short-range communication with the communication device;
The communication device transmits the authenticator from the short-range communication device to the authentication device. In-vehicle devices specified by:
The processing device included in this in-vehicle device is
Connected to the display device,
Conditions for displaying a registration screen on the display device are registration of an identifier to be transmitted to the authentication device and registration of an authenticator to be transmitted to the authentication device,
The registration screen is for registering a communication device used for connection to the authentication device. The in-vehicle device according to claim 13 specified by the following matters.
The second registration screen that the processing device displays on the display device includes a registration field for registering the authenticator,
The registration field does not display the authenticator registered before the second registration screen is displayed. The in-vehicle device according to claim 13 or 14 specified by the following matters.
The processor is
Connected to a near field communication device,
Causing the short-range communication device to perform short-range communication with the communication device;
The communication device transmits the authenticator from the short-range communication device to the authentication device.

Images