JP2019034684A - In-vehicle device control system, management server, in-vehicle communication device, computer program, and in-vehicle device control method - Google Patents

Abstract

An in-vehicle device control system capable of driving a changed vehicle with good operability even when a user changes the vehicle to be driven.
An in-vehicle device control system 1 acquires first setting information, which is setting information indicating control contents of an in-vehicle device mounted in a first vehicle, and transmits a management server 30 that acquires the acquired first setting information. The first setting information is received from the management server 30, and the received first setting information is set in an in-vehicle device mounted in the second vehicle 2. The in-vehicle communication device disposed in the second vehicle 2 is provided.
[Selection] Figure 1

Description

  The present invention relates to an in-vehicle device control system, a management server, an in-vehicle communication device, a computer program, and an in-vehicle device control method, and in particular, an in-vehicle device control system, a management server, an in-vehicle communication device for setting setting information in an in-vehicle device, The present invention relates to a computer program and an in-vehicle device control method.

  In recent years, car sharing in which a vehicle such as one automobile is shared by a plurality of users has become widespread (for example, see Patent Document 1). In the car sharing system, the user can use the vehicle for a short time and the usage fee is also easy. For this reason, opportunities to use car sharing are increasing not only for users who do not own vehicles but also for users who own vehicles.

  For example, when you want to enjoy a short drive while traveling by train, car sharing, which allows you to apply for use with a relatively simple procedure, is suitable. Thereby, the user can enjoy driving easily.

JP 2017-068449 A

  However, from the viewpoint of a user who owns a vehicle, the user drives a vehicle that is different from the vehicle owned by the user who normally operates the vehicle. For this reason, since the setting of the vehicle such as the position of the seat and the position of the mirror is different from that of the owned vehicle, it must be reset before driving the vehicle, which is troublesome.

  The present invention has been made to solve such a problem, and even when a user changes a vehicle to be driven, an in-vehicle device control system capable of driving the changed vehicle with good operability. An object is to provide a management server, an in-vehicle communication device, a computer program, and an in-vehicle device control method.

  (1) In order to achieve the above object, an in-vehicle device control system according to an embodiment of the present invention acquires first setting information which is setting information indicating control contents of an in-vehicle device mounted on a first vehicle. A management server for transmitting the acquired first setting information; receiving the first setting information from the management server; and setting the received first setting information in an in-vehicle device mounted on a second vehicle. An in-vehicle communication device disposed in the second vehicle.

  (9) A management server according to another embodiment of the present invention obtains setting information indicating the control content of the in-vehicle device mounted in the first vehicle from the in-vehicle communication device arranged in the first vehicle. An acquisition unit; and a setting information providing unit that provides the setting information acquired by the setting information acquisition unit to an in-vehicle communication device arranged in a second vehicle.

  (10) The in-vehicle communication device according to another embodiment of the present invention is an in-vehicle communication device arranged in the second vehicle, and is a setting indicating a setting content of the in-vehicle device mounted in the first vehicle from the management server. A setting information acquisition unit that acquires information; and a setting information setting unit that sets the setting information acquired by the setting information acquisition unit in an in-vehicle device mounted on the second vehicle.

  (11) A computer program according to another embodiment of the present invention obtains setting information indicating control contents of an in-vehicle device mounted on the first vehicle from an in-vehicle communication device disposed in the first vehicle. And a setting information providing unit that provides the setting information acquired by the setting information acquiring unit to the in-vehicle communication device arranged in the second vehicle.

  (12) A computer program according to another embodiment of the present invention is a computer program for causing a computer to function as an in-vehicle communication device disposed in a second vehicle. A setting information acquisition unit that acquires setting information indicating the setting content of the in-vehicle device mounted on the vehicle, and a setting that sets the setting information acquired by the setting information acquisition unit in the in-vehicle device mounted on the second vehicle It functions as an information setting unit.

  (13) In the in-vehicle device control method according to another embodiment of the present invention, the management server acquires and acquires first setting information that is setting information indicating the control content of the in-vehicle device mounted on the first vehicle. The step of transmitting the first setting information, and the in-vehicle communication device arranged in the second vehicle receive the first setting information from the management server, and the received first setting information to the second vehicle. And setting to the on-vehicle device mounted.

  According to the present invention, even if the user changes the vehicle to be driven, the changed vehicle can be driven with good operability.

It is a figure which shows the structure and data flow of the car sharing system which concern on embodiment of this invention. It is a block diagram which shows the structure of a management server. It is a figure which shows an example of the setting information and software information which are memorize | stored in the memory | storage device of a management server. It is a block diagram which shows the main structures of a sharing car. It is a figure for demonstrating the setting information set to the software which operates on the controller of a sharing car, and a controller. It is a block diagram which shows the structure of the vehicle-mounted communication apparatus arrange | positioned at a sharing car. It is a sequence diagram which shows the flow of a process of the car sharing system at the time of user information registration. It is a figure which shows an example of the user information registered into the agent server. It is a sequence diagram which shows the flow of a process of the car sharing system at the time of setting information registration of my car. It is a sequence diagram which shows the flow of a process of the car sharing system at the time of use application and at the time of confirmation of a sharing car. It is a sequence diagram which shows the flow of a process of the car sharing system at the time of boarding a sharing car. It is a sequence diagram which shows the flow of a process of the car sharing system at the time of completion | finish of car sharing. It is a figure which shows the flow of the service and expense delivered between the company which operates a car sharing system, and the user who uses the car sharing system. It is a figure which shows the structure and data flow of the car sharing system which concern on a modification.

[Outline of Embodiment of the Present Invention]
First, the outline of the embodiment of the present invention will be listed and described.
(1) The vehicle equipment control system which concerns on one Embodiment of this invention acquires the 1st setting information which is the setting information which shows the control content of the vehicle equipment mounted in the 1st vehicle, The acquired said 1st setting information And a management server that transmits the first setting information received from the management server, and the received first setting information is set in an in-vehicle device mounted on the second vehicle. An in-vehicle communication device.

  According to this structure, the 1st setting information which is the setting information of the vehicle equipment of a 1st vehicle can be succeeded to a 2nd vehicle by setting to the vehicle equipment mounted in the 2nd vehicle. Thereby, even if it is a case where the vehicle which a user drives is changed from the 1st vehicle to the 2nd vehicle, the 2nd vehicle after a change can be driven with sufficient operativity.

  (2) Preferably, the first setting information is associated with a user identifier, and the management server further receives the user identifier from the in-vehicle communication device and corresponds to the received user identifier. The attached setting information is transmitted to the in-vehicle communication device which is a transmission source of the identifier of the user, and the in-vehicle communication device transmits the identifier of the user of the first vehicle to the management server, The first setting information associated with the identifier of the user of the first vehicle is received.

  According to this configuration, the setting information is associated with the user identifier. For this reason, the vehicle-mounted communication apparatus arrange | positioned at the 2nd vehicle can acquire the setting information of the vehicle equipment of a 1st vehicle from a management server by transmitting the identifier of the user of a 1st vehicle to a management server. Thereby, 1st setting information can be set to the vehicle equipment of a 2nd vehicle.

  (3) Further, the management server further transmits at least one of software for operating the in-vehicle device mounted on the first vehicle and acquisition destination information of the software to the in-vehicle communication device, and the in-vehicle communication The apparatus may further acquire the software as an installation target on the second vehicle from at least one of the acquisition destination indicated by the management server and the acquisition destination information.

  According to this configuration, the in-vehicle communication device acquires the software used by the user in the first vehicle in addition to the setting information from the management server or the acquisition source indicated by the acquisition source information, and installs it in the second vehicle. be able to. Thereby, the user can use the same software as that used in the first vehicle even in the second vehicle.

  (4) Moreover, the said vehicle-mounted communication apparatus may perform the acquired said software on a virtualization layer.

  According to this configuration, the same software can be executed on both the first vehicle and the second vehicle having different environments such as hardware and an in-vehicle network.

  (5) Further, the second vehicle may be a shared vehicle that is a vehicle used by a plurality of users.

  According to this configuration, vehicle setting information held by the user can be taken over by a vehicle (sharing car) used in the car sharing system or a shared vehicle such as a rental car. Thereby, the user can drive a sharing car or a rental car with good operability.

  (6) Moreover, the said vehicle equipment control system is further provided with the operation server which operates the said share vehicle, The said operation server transmits the identifier of the user who uses the said share vehicle with respect to the said vehicle-mounted communication apparatus. And the said vehicle-mounted communication apparatus may receive the said user's identifier from the said operation server, and may receive the said setting information matched with the received said user's identifier from the said management server.

  According to this configuration, a user who is permitted to use a shared vehicle such as a sharing car or a rental car from the operation server can transfer the setting information to the shared vehicle.

  (7) The in-vehicle device control system further includes an agent server that mediates the shared vehicle. The agent server receives a request for the shared vehicle from a user of the first vehicle and matches the request. The identifier of the user of the first vehicle may be transmitted to the operation server that operates the shared vehicle.

  According to this configuration, the identifier of the user who uses the shared vehicle can be notified to the operation server of the shared vehicle that matches the user's desire. Accordingly, the operation server that has received the notification can perform processing for issuing electronic key information for allowing the user to use the share vehicle.

  (8) Moreover, the said vehicle-mounted communication apparatus transmits the setting information of the said vehicle-mounted apparatus mounted in the said 2nd vehicle to the said management server, The said management server is the said setting information received from the said vehicle-mounted communication apparatus. The first setting information may be updated.

  According to this configuration, setting information when the user uses the second vehicle can be stored in the management server. Thereby, when a user uses another vehicle after that, he can take over and use the setting information at the time of using a 2nd vehicle.

  (9) The management server according to another embodiment of the present invention acquires setting information indicating the control content of the in-vehicle device mounted in the first vehicle from the in-vehicle communication device arranged in the first vehicle. An acquisition unit; and a setting information providing unit that provides the setting information acquired by the setting information acquisition unit to an in-vehicle communication device arranged in a second vehicle.

  According to this structure, the 1st setting information which is the setting information of the vehicle equipment of a 1st vehicle can be taken over to a 2nd vehicle by providing to the vehicle-mounted communication apparatus arrange | positioned at the 2nd vehicle. Thereby, even if it is a case where the vehicle which a user drives is changed from the 1st vehicle to the 2nd vehicle, the 2nd vehicle after a change can be driven with sufficient operativity.

  (10) An in-vehicle communication device according to another embodiment of the present invention is an in-vehicle communication device arranged in a second vehicle, and a setting indicating the setting content of the in-vehicle device mounted in the first vehicle from the management server. A setting information acquisition unit that acquires information; and a setting information setting unit that sets the setting information acquired by the setting information acquisition unit in an in-vehicle device mounted on the second vehicle.

  According to this configuration, the in-vehicle communication device acquires the first setting information, which is the setting information of the in-vehicle device of the first vehicle, from the management server, and sets the first setting information in the in-vehicle device mounted on the second vehicle. Information can be passed on to the second vehicle. Thereby, even if it is a case where the vehicle which a user drives is changed from the 1st vehicle to the 2nd vehicle, the 2nd vehicle after a change can be driven with sufficient operativity.

  (11) A computer program according to another embodiment of the present invention obtains setting information indicating control contents of an in-vehicle device mounted on the first vehicle from an in-vehicle communication device arranged in the first vehicle. And a setting information providing unit that provides the setting information acquired by the setting information acquiring unit to the in-vehicle communication device arranged in the second vehicle.

  According to this configuration, the computer can function as the above-described management server. For this reason, there can exist an effect | action and effect similar to the above-mentioned management server.

  (12) A computer program according to another embodiment of the present invention is a computer program for causing a computer to function as an in-vehicle communication device disposed in a second vehicle. A setting information acquisition unit that acquires setting information indicating the setting content of the in-vehicle device mounted on the vehicle, and a setting that sets the setting information acquired by the setting information acquisition unit in the in-vehicle device mounted on the second vehicle It functions as an information setting unit.

  According to this configuration, the computer can function as the above-described in-vehicle communication device. For this reason, there can exist an effect | action and effect similar to the above-mentioned vehicle-mounted communication apparatus.

  (13) In the in-vehicle device control method according to another embodiment of the present invention, the management server acquires and acquires first setting information that is setting information indicating the control content of the in-vehicle device mounted on the first vehicle. The step of transmitting the first setting information, and the in-vehicle communication device arranged in the second vehicle receive the first setting information from the management server, and the received first setting information to the second vehicle. And setting to the on-vehicle device mounted.

  This configuration includes steps corresponding to the processing of the components of the above-described in-vehicle device control system. For this reason, there can exist an effect | action and effect similar to the above-mentioned vehicle equipment control system.

[Details of the embodiment of the present invention]
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. Each of the embodiments described below shows a preferred specific example of the present invention. Numerical values, shapes, components, arrangement positions and connection forms of components, steps, order of steps, and the like shown in the following embodiments are merely examples, and are not intended to limit the present invention. The invention is specified by the claims. Therefore, among the constituent elements in the following embodiments, constituent elements that are not described in the independent claims indicating the highest concept of the present invention are not necessarily required to achieve the object of the present invention. It will be described as constituting a preferred form.

<Overall configuration of car sharing system>
FIG. 1 is a diagram showing a configuration and data flow of a car sharing system according to an embodiment of the present invention.

  Referring to FIG. 1, a car sharing system 1 is a system for determining a sharing car that matches a user's desired conditions and providing it to the user. The terminal device 10, the management server 30, and the agent server 40 are provided. A plurality of operation servers 50 and a sharing car 2.

  The terminal device 10 is a device having a communication function such as a smartphone, a tablet terminal, or a laptop computer possessed by the user, communicates with an agent server 40 described later, and uses the sharing car 2 as a second vehicle. Perform procedural processing.

  In addition, the terminal device 10 includes, from a vehicle such as an automobile normally used by a user as the first vehicle (hereinafter also referred to as “my car”), setting information indicating the control content of the in-vehicle device mounted on the vehicle, Information on software for operating the in-vehicle device is extracted, and the extracted setting information and software information are transmitted to the management server 30 described later. For example, when the in-vehicle device is an ECU (Electronic Control Unit) for adjusting the angle of the door mirror, the setting information of the in-vehicle device includes information on the angle of the door mirror. In addition, when the in-vehicle device is a car navigation system, the software information of the in-vehicle device includes information (software name, model number, version, etc.) for specifying software that operates on the car navigation system, The in-vehicle device setting information includes information such as destination information set in the car navigation system and voice guidance volume.

  Furthermore, the terminal device 10 is also used as an electronic key for unlocking the door of the sharing car 2. The operation server 50 of the operating company that operates the sharing car 2 distributes electronic key information in advance to users who are permitted to use the sharing car 2 and the sharing car 2. When the user brings the terminal device 10 close to a predetermined position of the sharing car 2, authentication processing is performed between the terminal device 10 and the sharing car 2, and when the authentication is successful, the door of the sharing car 2. Is unlocked.

  The management server 30 manages, for each user, control information and software information of in-vehicle devices mounted on vehicles used by the user. The management server 30 is a server operated by a management company that manages control information and software information. However, the management server 30 may be operated by an agent company that operates an agent server 40 described later.

  The management server 30 receives control information and software information corresponding to the user's own car from the terminal device 10, and manages them in association with the user ID (user identifier) of the user. Further, the management server 30 receives the user ID of the user who uses the sharing car 2 from the sharing car 2 and transmits control information and software information associated with the user ID to the sharing car 2. Thereby, the control information and software information of the in-vehicle device mounted on the car can be taken over by the sharing car 2.

  The agent server 40 is a server that enters between a plurality of operating companies that provide car sharing services and the user, and provides a service for mediating the optimum sharing car 2 to the user. The agent server 40 is a server operated by an agent company that mediates the sharing car 2.

  The agent server 40 receives the desired condition of the sharing car 2 from the terminal device 10, selects an operating company that possesses the sharing car 2 that matches the condition, and transmits the selection result to the terminal device 10. In addition, the agent server 40 requests car sharing to the operation server 50 of the selected operation company.

  The operation server 50 is a server operated by each operation company that provides the car sharing service. Here, it is assumed that operation servers A to C are operated by operation companies A to C, respectively.

  The operation server 50 receives the desired condition of the sharing car 2 from the agent server 40 and notifies the operation server 50 of the presence or absence of the sharing car 2 that matches the condition. When the operation server 50 receives a request for car sharing from the agent server 40, the operation server 50 unlocks the door of the sharing car 2 to both the sharing car 2 and the user who uses the sharing car 2. Send electronic key information.

<Configuration of management server>
FIG. 2 is a block diagram showing the configuration of the management server 30. As shown in FIG.
The management server 30 is a computer including a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a HDD (Hard Disk Drive), a communication I / F (Interface), and the like. A setting information acquisition unit 32, a storage device 33, a user ID acquisition unit 34, and a setting information provision unit 35.

  The setting information acquisition unit 32, the user ID acquisition unit 34, and the setting information provision unit 35 are functional components realized by reading a computer program stored in an HDD or a ROM into a RAM and executing it on the CPU. It is.

  The communication unit 31 includes a communication I / F, and performs communication with the terminal device 10, the agent server 40, or the sharing car 2.

  The storage device 33 is a device for storing various information, and is configured by an HDD, a RAM, or the like.

  The user ID acquisition unit 34 acquires the user ID of the user who applied for the use of the car sharing service from the agent server 40 via the communication unit 31 and writes the acquired user ID in the storage device 33.

  The setting information acquisition unit 32 acquires the user's own car setting information and software information and the user ID from the terminal device 10 via the communication unit 31 and stores them in the storage device 33.

  FIG. 3 is a diagram illustrating an example of setting information and software information stored in the storage device 33 of the management server 30.

  Referring to FIG. 3, the storage device 33 of the management server 30 stores a user ID, software information (basic software and application), and setting information as a set. For example, the basic software used by the user with the user ID “U001” is “h1, h2, h3”, the application is “hp1, hp2”, and the setting information is “hpd1, hpd2, hpd3, hpd4” It is shown.

  The basic software (BSW) refers to a software module corresponding to an OS (Operating System), a driver, and middleware necessary for operating an in-vehicle device mounted on the vehicle.

  An application refers to an application program for operating an in-vehicle device. For example, this includes car navigation system software and video content playback software.

  The setting information is information indicating the control contents of the in-vehicle device, and includes a setting value set in the in-vehicle device and an application setting value. Examples of setting values set for in-vehicle devices include door mirror angle information, seat position information, accelerator brake response (light / heavy) information, air conditioner temperature setting information, air conditioner wind outlet Includes angle information. Further, the set value of the application includes, for example, information such as destination information set in the car navigation system and a volume of voice guidance.

  It is assumed that software corresponding to the software information is also stored in the storage device 33 in advance. That is, the basic software and application program data shown in FIG. 3 are stored in the storage device 33 in advance.

  Referring to FIG. 2 again, the user ID acquisition unit 34 further acquires a user ID from the sharing car 2 and outputs the acquired user ID to the setting information providing unit 35.

  The setting information providing unit 35 receives the user ID from the user ID acquisition unit 34 and reads software information and setting information corresponding to the user ID from the storage device 33. The setting information providing unit 35 further reads a program corresponding to the read software information from the storage device 33. The setting information providing unit 35 transmits the software and setting information read from the storage device 33 to the sharing car 2 via the communication unit 31.

<Configuration of sharing car>
FIG. 4 is a block diagram showing a main configuration of the sharing car 2. FIG. 4 shows only the configuration related to the present embodiment, and the configuration not related to the present embodiment such as the configuration related to the traveling system is not shown.
The sharing car 2 includes hardware 70A to 70C, a controller 60, and the in-vehicle communication device 20.

  The hardware 70 </ b> A to 70 </ b> C is a general-purpose ECU, and can perform a function corresponding to software executed on the controller 60. Thereby, hardware 70A-70C functions as in-vehicle equipment. For example, when an application for controlling an air conditioner is executed on the controller 60, any one of the hardware 70A to 70C functions as a body system ECU for controlling the air conditioner. Further, when executing the application of the car navigation system on the controller 60, any of the hardware 70A to 70C functions as a multimedia system ECU for realizing the car navigation system. Hereinafter, the hardware 70 </ b> A to 70 </ b> C will be referred to as the hardware 70 when they are not distinguished. Further, the number of hardware 70 is not limited to three, but may be other numbers.

  The controller 60 controls the hardware 70. For example, the controller 60 is a gateway ECU, for example, and has a function of executing software for controlling the hardware 70 on the virtualization layer.

  The in-vehicle communication device 20 is an in-vehicle communication unit for communicating with an external server such as the management server 30 and the operation server 50 and the terminal device 10, and is composed of, for example, a TCU (Telematics Communication Unit). The in-vehicle communication device 20 is close to the terminal device 10 according to standards such as NFC (Near Field Communication), Bluetooth (registered trademark), and ZigBee (registered trademark), in addition to a function of communicating with a server according to a communication standard such as 3G or 4G. It has a function to perform distance wireless communication.

  The in-vehicle communication device 20, the controller 60, and the hardware 70A to 70C may be connected according to a communication standard such as CAN (Controller Area Network) or LIN (Local Interconnect Network), or MOST (Media Oriented Systems Transport). ) And other appropriate communication protocols such as FlexRay (registered trademark).

  FIG. 5 is a diagram for explaining software operating on the controller 60 of the sharing car 2 and setting information set in the controller 60.

  It is assumed that software for realizing virtualization called a virtualization layer 61 is executed on the controller 60.

  The controller 60 realizes virtualization by executing the basic software 62 on the virtualization layer 61. For example, the controller 60 executes basic software h <b> 1 to h <b> 3 on the virtualization layer 61.

  Further, the controller 60 executes the application 63 on the basic software 62. For example, the controller 60 executes the application hp1 on the basic software h1, and executes the application hp2 on the basic software h2. The application hp1 is, for example, software for causing the hardware 70A to function as a body system ECU that controls an air conditioner, and the application hp2 is, for example, the function of the hardware 70B as a multimedia system ECU that implements a car navigation system. It is software to make it.

  Moreover, the controller 60 sets the setting information 64 in the application, or sets the setting information 64 in the hardware 70 that functions as an in-vehicle device.

  For example, the controller 60 sets the set temperature setting information hpd1 in the app hp1 for controlling the air conditioner, or sets the destination setting information pd2 in the app hp2 of the car navigation system. Thereby, the application hp1 can set the set temperature indicated by the setting information in the hardware 70A that controls the air conditioner. Further, the application hp2 can set a destination in the hardware 70B that realizes the car navigation system.

  If the basic software h3 is software for causing the hardware 70C to function as an ECU for adjusting the angle of the door mirror, the controller 60 sets the basic software h3 to indicate the angle of the left door mirror. Information pd3 and setting information pd4 indicating the angle of the right door mirror are set. Thereby, the basic software h3 sets the angle of the door mirror indicated by the setting information pd3 and pd4 in the hardware 70C that controls the door mirror, and the hardware 70C adjusts the angle of the door mirror so as to be equal to the angle. be able to.

  However, some of the hardware 70A to 70C may be dedicated hardware. For example, the hardware 70C that controls the door mirror may be a dedicated ECU.

<Configuration of in-vehicle communication device 20>
FIG. 6 is a block diagram showing a configuration of the in-vehicle communication device 20 arranged in the sharing car 2.

  The in-vehicle communication device 20 includes a communication unit 21, a user ID acquisition unit 22, a storage device 23, a user ID transmission unit 24, a setting information acquisition unit 25, a setting information setting unit 26, and an electronic key information acquisition unit 27. And a setting information transmission unit 28.

  The components excluding the communication unit 21 and the storage device 23 are functional components realized by executing a computer program on a CPU included in the in-vehicle communication device 20.

  The communication unit 21 communicates with a server according to a communication standard such as 3G or 4G, and short-range wireless communication with the terminal device 10 according to a standard such as NFC, Bluetooth (registered trademark), or ZigBee (registered trademark). The communication I / F is configured to perform.

  The user ID acquisition unit 22 acquires the user ID of the user who uses the sharing car 2 from the operation server 50 via the communication unit 21 and stores it in the storage device 23.

  The storage device 23 includes a nonvolatile memory such as a flash memory or an EEPROM (Electrically Erasable Programmable Read-Only Memory) or a volatile memory such as a DRAM (Dynamic Random Access Memory), and temporarily stores various data.

  The user ID transmission unit 24 reads the user ID stored in the storage device 23 and transmits the read user ID to the management server 30 via the communication unit 21.

  The setting information acquisition unit 25 acquires setting information and software corresponding to the user ID transmitted by the user ID transmission unit 24 to the management server 30 from the management server 30 via the communication unit 21.

  The setting information setting unit 26 installs the software in the controller 60 by outputting the setting information and software acquired by the setting information acquisition unit 25 to the controller 60, and installs the software in the sharing car 2 (hardware 70). ) To set the setting information. That is, the controller 60 installs the software (the basic software 62 and the application 63 shown in FIG. 5) received from the setting information acquisition unit 25 on the virtualization layer 61. Further, the controller 60 sets the setting information (setting information 64 shown in FIG. 5) received from the setting information acquisition unit 25 in the software (basic software 62 and application 63 shown in FIG. 5) installed on the virtualization layer 61. To do. As a result, the software sets the setting information in the hardware 70.

  The setting information setting unit 26 may output a part of the setting information or the software among the setting information and software acquired by the setting information acquisition unit 25 to the controller 60. Thereby, a part of software can be installed in the controller 60 and a part of setting information can be set in the hardware 70. For example, the setting information setting unit 26 inquires of the user about the software to be installed and the setting information to be set, and outputs the software and setting information designated by the user to the controller 60, respectively, so that the installation and setting can be performed. Good. Thereby, only the software or setting information that the user wants to use in the sharing car 2 can be installed or set, and unnecessary software or unnecessary setting information can be prevented from being installed or set.

  The electronic key information acquisition unit 27 acquires the electronic key information for the sharing car 2 and information on the validity period of the electronic key information from the operation server 50 via the communication unit 21, and acquires the acquired electronic key information and the valid The period information is output to the controller 60. The electronic key information for the sharing car 2 is paired with the electronic key information for the user separately transmitted from the operation server 50 to the terminal device 10 and used for the user authentication process. The controller 60 sets the electronic key information and validity period information for the sharing car 2 received from the electronic key information acquisition unit 27 in the hardware 70 that performs the authentication process. In the case where the sharing car 2 is equipped with hardware such as a dedicated ECU for performing authentication processing, the electronic key information acquisition unit 27 is connected to the hardware directly or via the controller 60. The valid period information may be output.

  The setting information transmission unit 28 acquires setting information set in the software by the controller 60 from the controller 60 when the use of the sharing car 2 is completed. The setting information transmission unit 28 transmits the acquired setting information to the management server 30 via the communication unit 21 together with the user ID stored in the storage device 23. Thereby, the management server 30 can receive the user ID and the setting information, and can update the setting information for each user ID stored in the management server 30.

<Flow of car sharing>
Next, with reference to FIG. 1 and FIGS. 7 to 12, the flow of car sharing for the user to use the sharing car 2 will be described along with the flow of information between the devices.

  The following is the general process flow of car sharing: “User information registration”, “My car setting information registration”, “Usage application and confirmation of sharing car”, “Ride in sharing car”, “Car sharing” The description will be made in the order of “End”.

(User information registration)
FIG. 7 is a sequence diagram showing a processing flow of the car sharing system 1 at the time of user information registration.

  The user registers user information for using the car sharing service. That is, when the user operates the terminal device 10 to input user information including the user's name, telephone number, email address, payment method, etc., the terminal device 10 receives the user information input to the agent server 40. (S1, (1) user information in FIG. 1).

  The agent server 40 that has received the user information assigns a user ID to the user information and registers it in its own storage device (S2). As a result, the user information of the user who wishes to use the car sharing service is registered in the agent server 40.

FIG. 8 is a diagram illustrating an example of user information registered in the agent server 40.
The user information includes information such as a user ID, name, telephone number, e-mail address, and payment method. For example, the name of the user with the user ID “U001” is “A”, the telephone number is “xxx-xxxx”, the mail address is “aaa @ bbb”, and the payment method is “credit card” Is shown in the user information.

  Referring to FIG. 7 again, the agent server 40 transmits the user ID assigned to the user information received from the terminal device 10 to the management server 30 (S3, (2) user ID in FIG. 1). For example, the agent server 40 transmits the user ID “U001” to the management server 30. As a result, the agent server 40 can notify the management server 30 that a user with the user ID “U001” has been newly registered.

  The management server 30 receives the user ID from the agent server 40 and registers it in its own storage device (S4). For example, the management server 30 receives the user ID “U001” and registers it in its own storage device. Thereby, the management server 30 can manage the user ID “U001” of the newly registered user.

  Further, the agent server 40 transmits the user ID assigned to the user information received from the terminal device 10 to the terminal device 10 (S5, (3) user ID in FIG. 1). For example, the agent server 40 transmits the user ID “U001” to the terminal device 10.

  The terminal device 10 receives the user ID from the agent server 40 and registers it in its own storage device (S6). For example, the terminal device 10 receives the user ID “U001” from the agent server 40 and registers it in its own storage device. Thereby, the user who uses the terminal device 10 can know that his / her user ID is “U001”.

(My car setting information registration)
Next, a process for registering setting information and software information of the in-vehicle device mounted on the car in the management server 30 will be described.

  FIG. 9 is a sequence diagram showing a processing flow of the car sharing system 1 when registering the setting information of the car.

  The user operates the terminal device 10 to transmit the setting information and software information of the private car to the management server 30 as a set with the user ID (S11, (4) User ID / own vehicle setting information and software in FIG. information). For example, setting information and software information are transmitted as a set with the user ID “U001”.

  The management server 30 registers the received information in its own storage device (S12). That is, the management server 30 registers the user ID, setting information, and software information (basic software, application) as a set in the storage device as shown in FIG. Thereby, the management server 30 can manage the setting information and software information which a user usually uses for every user.

  In addition, the user's setting information and software information may be manually input by the user operating the terminal device 10. Further, by connecting the terminal device 10 and the gateway ECU that controls the in-vehicle device of the car, by executing software on the terminal device 10 to extract setting information from the vehicle provided from the agent server 40 or the like, The terminal device 10 may acquire such information from the gateway ECU.

(Use application and sharing car confirmation)
Next, a car sharing use application process by the user will be described.
FIG. 10 is a sequence diagram showing a flow of processing of the car sharing system 1 at the time of application for use and at the time of confirmation of the sharing car.

  The user operates the terminal device 10 and makes a use application to the agent server 40 (S21, (5) use application in FIG. 1). Specifically, the user inputs desired conditions such as the usage location, usage date, usage period, desired fee, and desired vehicle type of the sharing car that the user wishes to board into the terminal device 10. The terminal device 10 makes an application for sharing car use by transmitting the input information on the desired conditions to the agent server 40.

  The agent server 40 that has received the use application transmits the desired condition information received from the terminal device 10 to each of the operation servers A to C, thereby presenting the user's desired conditions to each operation company (S22A). To S22C ((6) Desired conditions in FIG. 1).

  Each of the operation servers A to C receives the information on the desired conditions, and transmits the information of the sharing car 2 closest to the user's desired conditions to the agent server 40 as result information (S23A to S23C, (7 in FIG. 1). )result).

  The agent server 40 collects the result information from the operation servers A to C, and selects the sharing car 2 that is closest to the user's desired conditions (S24). In addition, since the selection process of the sharing car 2 by the agent server 40 and the operation server 50 is not the main point of the present application, detailed description thereof is omitted. For example, you may make it select the sharing car 2 which satisfy | fills all the user's desired conditions, prioritize the desired conditions, and preferentially select the sharing car 2 that satisfies the higher priority desired conditions. You may make it do.

  The agent server 40 transmits the selection result information of the sharing car 2 to the terminal device 10 (S25, (8) selection result in FIG. 1). In the following description, it is assumed that the sharing car 2 of the operation server A is closest to the user's desired conditions. The number of sharing cars 2 indicated by the selection result information is not limited to one. For example, information on a predetermined number of sharing cars 2 that are closest to the desired condition may be included in the selection result information.

  The terminal device 10 presents the selection result information received from the agent server 40 to the user by displaying it on the display device. The user operates the terminal device 10 to input whether to request use of the sharing car 2 indicated in the presented selection result information. When the user requests to use the sharing car 2, the terminal device 10 transmits request information for using the sharing car 2 to the agent server 40 (S26, (9) request in FIG. 1).

  The agent server 40 receives request information for using the sharing car 2 from the terminal device 10, and transmits information for requesting car sharing to the operation server A according to the request information. At the same time, the agent server 40 notifies the operation server A of the user ID and mail address of the user who wants to use the sharing car 2 (S27, (10) car sharing request / user ID / mail address in FIG. 1). ). For example, the agent server 40 notifies the operation server A of the user ID “U001” and the mail address “aaa @ bbb”.

(Ride in a sharing car)
FIG. 11 is a sequence diagram showing the flow of processing of the car sharing system 1 when riding in the sharing car 2.

  When the operation server A receives the car sharing request information, the user ID, and the e-mail address from the agent server 40, the operation server A has a pair of electronic key information for unlocking the door of the sharing car 2 (an electronic key for the sharing car 2). Information and electronic key information for the user) are created (S31).

  The operation server A sends the electronic key information (authentication key information) for the user and the identifier of the sharing car 2 (vehicle registration of the sharing car 2) to the received user's email address (for example, “aaa @ bbb”). E-mail including the number (number of the license plate)) is transmitted (S32, (11) Electronic key information in FIG. 1). Thereby, the user who received the e-mail can specify the sharing car 2 to be used. When the operation server A knows the communication address of the terminal device 10 in advance, the electronic key information for the user and the identifier of the sharing car 2 are directly transmitted to the terminal device 10. May be.

  The operation server A transmits the electronic key information for the sharing car 2 and information on the validity period of the electronic key information to the sharing car 2 used by the user (S33, (12) electronic in FIG. Key information).

  The sharing car 2 sets the electronic key information received from the operation server A in the hardware 70 that performs the authentication process (S34).

  Further, the sharing car 2 sets the validity period information of the electronic key information received from the operation server A in the same hardware 70 as the electronic key information is set (S35). Thereby, the validity period of the electronic key information is set.

  The operation server A transmits the user ID of the user who uses the sharing car 2 to the sharing car 2 (S36, (13) user ID in FIG. 1). For example, the operation server A transmits the user ID “U001” to the sharing car 2.

  The sharing car 2 transmits the user ID received from the operation server A to the management server 30 (S37, (14) user ID in FIG. 1). For example, the sharing car 2 transmits the user ID “U001” to the management server 30.

  Based on the user ID received from the sharing car 2, the management server 30 reads the software information and setting information stored in association with the user ID. Also, the management server 30 transmits the software indicated by the software information and the setting information to the sharing car 2 (S38, (15) setting information / software in FIG. 1). For example, referring to FIG. 3, the management server 30 shares basic software h1, h2, h3, apps hp1, hp2 and setting information hpd1, hdd2, hdd3, and hdd4 associated with the user ID “U001”. Send to car 2.

  The sharing car 2 receives the software and setting information from the management server 30, installs the received software in the sharing car 2 (S39), and sets the received setting information in the installed software (S40). As a result, the basic software 62 and the application 63 are executed on the virtualization layer 61 as shown in FIG. 5, and the setting information 64 is set.

  The user goes to the designated place within the usage period and transmits the user's electronic key information to the sharing car 2 by bringing the terminal device 10 close to a predetermined position of the sharing car 2 (S41, (16) in FIG. 1). Electronic key information). The sharing car 2 usage period is usually the same as the validity period of the electronic key information.

  The sharing car 2 performs an authentication process using the electronic key information of the user received from the terminal device 10 and the electronic key information stored by the self-confidence (S42), and if the authentication is successful, the door of the sharing car 2 Is unlocked (S43). Thereafter, the sharing car 2 starts the engine (S44).

  Thereby, the user can use the sharing car 2 during a use period. In FIG. 11 and FIG. 12 to be described later, the use period is shown in a hatched area 80.

(End of car sharing)
FIG. 12 is a sequence diagram illustrating a processing flow of the car sharing system 1 at the end of car sharing.

  The operation server A notifies the terminal device 10 that the use end time is approaching a predetermined time before the end of the use period (S51).

  When the user finishes using the sharing car 2 and returns the sharing car 2 to a predetermined location, the sharing car 2 transmits the setting information set in the sharing car 2 to the management server 30 together with the user ID ( S52, (17) setting information / user ID in FIG. Thereby, the management server 30 updates the user setting information stored in the management server 30 (S53). By updating the setting information, the user can use the same setting information the next time the sharing car 2 is used. However, the update of the setting information is an arbitrary process, and if the user does not wish to update, the setting information may not be updated.

  The sharing car 2 uninstalls the software installed in the sharing car 2 and clears the setting information set in the sharing car 2 (S54). As a result, it is possible to prevent other users who use the sharing car 2 next from being notified of the software and setting information used.

  When the user requests to extend the usage period of the sharing car 2, the terminal device 10 transmits extension request information to the operation server A. The operation server A that has decided to extend rewrites the validity period of the electronic information key of the sharing car 2 and transmits the rewritten electronic information key to the sharing car 2. Thereby, the sharing car 2 can reset the effective period of electronic key information, and the user can use the sharing car 2 until the effective period after resetting expires.

<Service and cost flow>
FIG. 13 is a diagram illustrating a flow of services and expenses transferred between a company operating the car sharing system 1 and a user using the car sharing system 1.

  The agent 400 that operates the agent server 40 provides a contract sharing service for car sharing to the user 100 and also provides an information providing service for the sharing car 2 associated with the contract proxy service. On the other hand, the user 100 pays a car sharing fee to the agent 400. Note that the user 100 may pay a fee for services provided from the agent 400.

  The agent 400 provides a car sharing contract agency service to the car sharing operation company 500 that operates the operation server 50 and the sharing car 2. Further, the agent 400 pays the car sharing cost deposited from the user 100 to the car sharing operation company 500 when the contract with the user is established. On the other hand, the car sharing operation company 500 pays the registration fee of the Web site to the agent server 40 and the license cost of the management server 30 paid to the management server operation company 300.

  A management server operating company 300 that operates the management server 30 provides a service for managing setting information to the agent 400. In response to this, the agent 400 pays the management server operation company 300 the license cost of the management server 30 deposited from the car sharing operation company 500.

<Effect of Embodiment>
As described above, according to the embodiment of the present invention, the setting information of the in-vehicle device of the car is set in the hardware 70 as the in-vehicle device mounted on the sharing car 2, so that the sharing car 2 Can take over. Thereby, even if it is a case where the vehicle which a user drives is changed from my car to the sharing car 2, the user can drive the sharing car 2 with good operativity.

  The setting information is managed by the management server 30 in association with the user ID. For this reason, the vehicle-mounted communication apparatus 20 arrange | positioned at the sharing car 2 acquires the setting information of the vehicle-mounted apparatus of a car from the management server 30 by transmitting the user ID of the user who uses a car to the management server 30. Can do. Thereby, the setting information of the own car can be easily set in the in-vehicle device of the sharing car 2.

  In addition to the setting information, the in-vehicle communication device 20 can acquire the software used by the user in the car from the management server 30 and install it on the controller 60 of the sharing car 2. As a result, the user can use the same software as that used in the personal car in the sharing car 2.

  Further, since the controller 60 executes the software on the virtual layer, the same software can be executed by both the personal car and the sharing car 2 having different environments such as hardware and in-vehicle network.

  Further, the operation server 50 transmits the user ID of the user who uses the sharing car 2 to the in-vehicle communication device 20 of the sharing car 2, and the in-vehicle communication device 20 is set from the management server 30 based on the user ID. Obtaining information and software. Therefore, a user who is permitted to use the sharing car 2 from the operation server 50 can take over the setting information to the sharing car 2.

  Further, the agent server 40 notifies the user ID to the operation server 50 of the sharing car 2 that matches the user's desire. Accordingly, the operation server 50 that has received the notification can perform processing for issuing electronic key information for allowing the user to use the sharing car 2.

  In addition, when the car sharing ends, the in-vehicle communication device 20 transmits setting information to the management server 30. That is, the setting information when the user uses the sharing car 2 can be stored in the management server 30. Thereby, the user can take over and use the setting information at the time of using the sharing car 2, when using another vehicle after that.

<Modification>
In the above-described embodiment, the management server 30 provides software to the sharing car 2, but software acquisition destination information may be provided. The software acquisition destination information is, for example, URL (Uniform Resource Locator) information of a software download server.

FIG. 14 is a diagram illustrating a configuration and data flow of a car sharing system according to a modification.
Referring to FIG. 14, car sharing system 1 </ b> A includes DL (download) server 90 in addition to the configuration of car sharing system 1 shown in FIG. 1.

  The DL server 90 is a server for providing software, and stores software installed in the vehicle. That is, the DL server 90 stores the basic software h1, h2,..., The applications hp1, hp2,.

  In the above-described embodiment, the management server 30 provides software to the in-vehicle communication device 20 of the sharing car 2 together with setting information ((15) setting information / software in FIG. 1). The management server 30 provides the URL information of the DL server 90 together with the setting information ((15) Setting information / URL in FIG. 14).

  The in-vehicle communication device 20 accesses the URL indicated by the URL information provided from the management server 30 ((15 ′) URL in FIG. 14), and downloads the software from the DL server 90 ((15 ″) in FIG. 14). software).

<Appendix>
The car sharing system 1 according to the embodiment of the present invention has been described above, but the present invention is not limited to this embodiment.

  For example, in the above-described embodiment, the car sharing system 1 that provides the user with the sharing car 2 has been described. However, the above-described embodiment can also be applied to a rental car system that provides the user with a rental car. . That is, the above-described embodiment can be applied to a share vehicle that is a vehicle used by a plurality of users.

  The present invention can also be configured as a system including the second vehicle including the in-vehicle communication device 20, the terminal device 10, and the management server 30. In this system, the terminal device 10 registers the setting information of the in-vehicle device mounted on the first vehicle such as a personal car in the management server 30 together with the user ID. Moreover, the vehicle-mounted communication apparatus 20 of a 2nd vehicle acquires setting information from the management server 30 by transmitting user ID to the management server 30, and registers it with the vehicle-mounted apparatus of a 2nd vehicle. Thereby, for example, common setting information can be taken over between two private cars owned by the user. In addition, the setting information of the first car owned by the first user can be taken over by the second car owned by the second user.

  In the above-described embodiment, the setting information and software information are managed for each user. However, the setting information and software information may be managed for each vehicle. That is, in the car sharing system 1, the vehicle ID for identifying the vehicle may be used instead of the user ID, and the vehicle ID may be associated with the setting information and software information and registered in the management server 30. . For example, the in-vehicle communication device 20 notifies the management server 30 of the vehicle ID, and acquires setting information and software corresponding to the vehicle ID from the management server 30.

  Note that some or all of the components constituting each of the above-described devices may be configured by a single system LSI. The system LSI is an ultra-multifunctional LSI manufactured by integrating a plurality of components on a single chip, and specifically, a computer system including a microprocessor, ROM, RAM, and the like. . A computer program is stored in the RAM. The system LSI achieves its functions by the microprocessor operating according to the computer program.

  Further, the present invention may be the method described above. Further, the present invention may be a computer program that realizes these methods by a computer.

  Furthermore, the present invention may be a computer-readable non-transitory recording medium such as an HDD, a CD-ROM, or a semiconductor memory.

In the present invention, the computer program or the digital signal may be transmitted via an electric communication line, a wireless or wired communication line, a network represented by the Internet, a data broadcast, or the like.
Each of the above devices may be realized by a plurality of computers.

  The embodiment disclosed this time should be considered as illustrative in all points and not restrictive. The scope of the present invention is defined by the terms of the claims, rather than the meanings described above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims.

DESCRIPTION OF SYMBOLS 1 Car sharing system 1A Car sharing system 2 Sharing car 10 Terminal device 20 In-vehicle communication device 21 Communication part 22 User ID acquisition part 23 Storage device 24 User ID transmission part 25 Setting information acquisition part 26 Setting information setting part 27 Electronic key information acquisition Unit 28 setting information transmission unit 30 management server 31 communication unit 32 setting information acquisition unit 33 storage device 34 user ID acquisition unit 35 setting information provision unit 40 agent server 50 operation server 60 controller 61 virtualization layer 62 basic software 63 application 64 setting information 70 hardware 70A hardware 70B hardware 70C hardware 80 area 90 DL server 100 user 300 management server operating company 400 agent 500 car sharing operating company

Claims (13)

A management server that acquires first setting information, which is setting information indicating the control content of the in-vehicle device mounted on the first vehicle, and transmits the acquired first setting information;
An in-vehicle communication device disposed in the second vehicle that receives the first setting information from the management server and sets the received first setting information in an in-vehicle device mounted in the second vehicle. In-vehicle device control system. The first setting information is associated with a user identifier,
The management server further receives a user identifier from the in-vehicle communication device, and transmits the setting information associated with the received user identifier to the in-vehicle communication device that is a transmission source of the user identifier. And
The in-vehicle communication device transmits an identifier of a user of the first vehicle to the management server, and receives the first setting information associated with the identifier of the user of the first vehicle from the management server. The in-vehicle device control system according to 1. The management server further transmits at least one of software for operating the in-vehicle device mounted on the first vehicle and acquisition destination information of the software to the in-vehicle communication device,
The said vehicle-mounted communication apparatus further acquires the said software as an installation object in the said 2nd vehicle from at least one of the acquisition destination which the said management server and the said acquisition destination information show. In-vehicle device control system.   The in-vehicle device control system according to claim 3, wherein the in-vehicle communication device causes the acquired software to be executed on a virtualization layer.   The in-vehicle device control system according to any one of claims 1 to 4, wherein the second vehicle is a share vehicle that is a vehicle used by a plurality of users. The in-vehicle device control system further includes an operation server that operates the share vehicle,
The operation server transmits an identifier of a user who uses the share vehicle to the in-vehicle communication device,
The in-vehicle device control system according to claim 5, wherein the in-vehicle communication device receives the user identifier from the operation server, and receives the setting information associated with the received user identifier from the management server. . The in-vehicle device control system further includes an agent server that mediates the share vehicle,
The agent server receives a request for the share vehicle from a user of the first vehicle, and transmits an identifier of the user of the first vehicle to the operation server that operates the share vehicle that matches the request. The in-vehicle device control system according to claim 6. The in-vehicle communication device transmits setting information of the in-vehicle device mounted on the second vehicle to the management server,
The in-vehicle device control system according to claim 1, wherein the management server updates the first setting information with the setting information received from the in-vehicle communication device. A setting information acquisition unit that acquires setting information indicating the control content of the in-vehicle device mounted in the first vehicle from the in-vehicle communication device disposed in the first vehicle;
A management server comprising: a setting information providing unit that provides the setting information acquired by the setting information acquiring unit to an in-vehicle communication device disposed in a second vehicle. An in-vehicle communication device arranged in the second vehicle,
A setting information acquisition unit that acquires setting information indicating the setting contents of the in-vehicle device mounted on the first vehicle from the management server;
An in-vehicle communication device comprising: a setting information setting unit that sets the setting information acquired by the setting information acquisition unit in an in-vehicle device mounted on the second vehicle. Computer
A setting information acquisition unit that acquires setting information indicating the control content of the in-vehicle device mounted in the first vehicle from the in-vehicle communication device disposed in the first vehicle;
The computer program for functioning as the setting information provision part which provides the said setting information which the said setting information acquisition part acquired to the vehicle-mounted communication apparatus arrange | positioned at the 2nd vehicle. A computer program for causing a computer to function as an in-vehicle communication device arranged in a second vehicle,
The computer,
A setting information acquisition unit that acquires setting information indicating the setting contents of the in-vehicle device mounted on the first vehicle from the management server;
A computer program for causing the setting information acquired by the setting information acquiring unit to function as a setting information setting unit that sets an in-vehicle device mounted on the second vehicle. A management server acquiring first setting information which is setting information indicating control contents of the in-vehicle device mounted on the first vehicle, and transmitting the acquired first setting information;
An in-vehicle communication device disposed in a second vehicle receives the first setting information from the management server, and sets the received first setting information in an in-vehicle device mounted in the second vehicle; In-vehicle device control method including

Images