JP2019175185A - Data structure, vehicle-mounted terminal, information communication method, program, and storage medium - Google Patents

Abstract

To allow for providing various services to a shared self-driving car.SOLUTION: Transmission data is transmitted from a vehicle-mounted terminal in a vehicle used by a user to a server device configured to collect information from vehicles. A data structure of the transmission data comprises a user ID of the user for a service provider who provides services associated with vehicles, and a vehicle ID for identifying the vehicle having the vehicle-mounted terminal installed therein. The transmission data is used by the server device of the service provider for user authentication.SELECTED DRAWING: Figure 9

Description

  The present invention relates to a technique for providing various services related to an autonomous driving vehicle that is car-shared.

  If self-driving cars become widespread, it is considered that car sharing will develop in addition to possessing them as private cars. Patent Document 1 describes a technique related to car sharing of an autonomous vehicle.

JP-A-2006-57946

  The autonomous driving vehicle transmits various information such as the position and route where the vehicle is traveling and information on surrounding objects detected by the sensor to a server that manages the autonomous driving vehicle. A company that provides various services related to an autonomous vehicle needs various information related to the autonomous vehicle in order to provide the service. Consider a case where a user receives a service related to an autonomous vehicle, for example, a service provided by an insurance company. In this case, it is desirable that the server managing the autonomous driving vehicle provides only the information requested by the insurance company among the information acquired from the autonomous driving vehicle to the insurance company. Therefore, there is a need for a mechanism for a server that manages an autonomous driving vehicle to select information obtained from the autonomous driving vehicle and provide it to a company that provides the service.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to provide various services to an autonomous driving vehicle that is car-shared.

  The invention according to claim 1 is a data structure of transmission data transmitted from an in-vehicle terminal mounted on a vehicle used by a user to a server device that collects information from the vehicle, and provides a service related to the vehicle. Including a user ID of the user for a service provider and a vehicle ID for identifying a vehicle on which the in-vehicle terminal is mounted, and based on the user ID and the vehicle ID by the server device of the service provider, Used for user authentication.

  The invention according to claim 2 is an in-vehicle terminal mounted on a vehicle used by a user, and receives from the user terminal device the user ID of the user for a service provider that provides a service related to the vehicle. And a transmission unit that transmits data including a user ID and a vehicle ID that identifies a vehicle on which the in-vehicle terminal is mounted to a server device that collects information from the vehicle.

  The invention according to claim 5 is an information communication method executed by an in-vehicle terminal mounted on a vehicle used by a user, wherein the user with respect to a service providing company that provides a service related to the vehicle from a user terminal device A receiving step of receiving the user ID, a transmitting step of transmitting data including the user ID and a vehicle ID for identifying the vehicle on which the in-vehicle terminal is mounted to a server device that collects information from the vehicle, Is provided.

  The invention according to claim 6 is a program that includes a computer and is executed by an in-vehicle terminal mounted on a vehicle used by a user, and is provided to a service provider that provides a service related to the vehicle from the user's terminal device. A receiving unit that receives the user ID of the user, a transmitting unit that transmits data including the user ID and a vehicle ID that identifies a vehicle on which the in-vehicle terminal is mounted, to a server device that collects information from the vehicle; To make the computer function.

1 shows a schematic configuration of a car sharing system according to an embodiment. It is a block diagram which shows the internal structure of a user terminal. It is a block diagram which shows the internal structure of a vehicle-mounted terminal. It is a block diagram which shows the internal structure of a vehicle cloud server and a service cloud server. An example of service information is shown. It is a flowchart of a service information registration process. An example of service information transmitted from the in-vehicle terminal to the vehicle cloud is shown. It is a flowchart of the 1st example of a use start process. It is a flowchart of the 2nd example of a use start process. It is a flowchart of the information provision process to a service cloud server. It is a flowchart of a use end process of a share car. It is a flowchart of a history deletion process. An authentication method using biometric information is schematically shown. It is a flowchart which shows the authentication process at the time of the utilization start using biometric information. It is a flowchart of the authentication process in using the share car.

  One preferred embodiment of the present invention is a data structure of transmission data transmitted from an in-vehicle terminal mounted on a vehicle used by a user to a server device that collects information from the vehicle. Including a user ID of the user for the service provider to be provided and a vehicle ID for identifying a vehicle on which the in-vehicle terminal is mounted, and based on the user ID and the vehicle ID by the server device of the service provider , Used to authenticate the user.

  The transmission data is transmitted from an in-vehicle terminal mounted on a vehicle used by a user to a server device that collects information from the vehicle. The data structure includes a user ID of the user for a service provider that provides a service related to the vehicle, and a vehicle ID that identifies the vehicle on which the in-vehicle terminal is mounted. This transmission data is used for user authentication by the server device of the service providing company.

  In another preferred embodiment of the present invention, an in-vehicle terminal mounted on a vehicle used by a user receives the user ID of the user from a user terminal device for a service provider that provides a service related to the vehicle. And a transmission unit that transmits data including a user ID and a vehicle ID that identifies a vehicle on which the in-vehicle terminal is mounted to a server device that collects information from the vehicle.

  The in-vehicle terminal receives the user ID of the user for the service provider that provides the service related to the vehicle from the user terminal device. And the data containing user ID and vehicle ID which specifies the vehicle by which a vehicle-mounted terminal device is mounted are transmitted to the server apparatus which collects information from a vehicle. Thereby, the user is authenticated by the server device of the service providing company.

  In one aspect of the in-vehicle terminal, the receiving unit receives a result of authentication performed by the service providing company based on the user ID. Thereby, the in-vehicle terminal can transmit the authentication result to the user.

  In another aspect of the in-vehicle terminal described above, the transmission unit provides information to be provided to the server device of the service providing company out of information collected from the vehicle when the successful authentication is received. The service information that is included is transmitted to the server device that collects information from the vehicle.

  In the other one aspect | mode of said vehicle-mounted terminal device, the said transmission part transmits the result of the said authentication to the said user's terminal device. Thereby, a user's terminal device can tell an authentication result to a user.

  In another preferred embodiment of the present invention, an information communication method executed by an in-vehicle terminal mounted on a vehicle used by a user is the user for a service providing company that provides a service related to the vehicle from the user terminal device. A receiving step of receiving the user ID, a transmitting step of transmitting data including the user ID and a vehicle ID for identifying the vehicle on which the in-vehicle terminal is mounted to a server device that collects information from the vehicle, Is provided. Thereby, the user is authenticated by the server device of the service providing company.

  Another preferred embodiment of the present invention includes a computer, and a program executed by an in-vehicle terminal mounted on a vehicle used by a user is provided to a service provider that provides a service related to the vehicle from the user's terminal device. A receiving unit that receives the user ID of the user, a transmitting unit that transmits data including the user ID and a vehicle ID that identifies a vehicle on which the in-vehicle terminal is mounted, to a server device that collects information from the vehicle; To make the computer function. By executing this program on a computer, the above-described in-vehicle terminal can be realized. This program can be stored in a storage medium and handled.

Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings.
[Car sharing system]
(overall structure)
FIG. 1 shows a schematic configuration of a car sharing system according to an embodiment. The car sharing system includes a user terminal 10 used by a user, a share car V, a vehicle (VEHICLE) cloud server 30, and a service cloud server 40.

  The user terminal 10 is a terminal device used by a user who uses a share car, and is typically a user's smartphone or the like. The share car V is an autonomous driving vehicle provided to the user. The share car V is equipped with an in-vehicle terminal 20, and the user terminal 10 and the in-vehicle terminal 20 can transmit and receive data by wireless communication.

  The vehicle cloud server 30 is a server device that constitutes a vehicle cloud. The vehicle cloud is a cloud operated by an information collection company that manages an autonomous driving vehicle provided to a user and collects various types of information from the autonomous driving vehicle. The information gathering company is operated by the manufacturer of self-driving cars. For example, if there are three companies, A, B, and C, as automakers for self-driving cars, the information collection company operated by company A, the information collection company operated by company B, and the information collection operated by company C There are separate companies, and each information gathering company collects various information from self-driving cars manufactured by the automakers they operate.

  The service cloud server 40 is a server device that constitutes a service cloud. A service cloud is a cloud operated by a service provider that provides services related to autonomous vehicles. Service providers include insurance companies that provide insurance services, map service companies that provide map services, parking service companies that provide parking services, and route search service companies that provide route search services. Can be mentioned.

  The in-vehicle terminal 20, the vehicle cloud server 30, and the service cloud server 40 mounted on the share car V can communicate with each other through a network 5 by wire or wirelessly.

(User terminal)
Next, the user terminal will be described in detail. FIG. 2 is a block diagram showing an internal configuration of the user terminal 10. The user terminal 10 includes a communication unit 11, a storage unit 12, a control unit 13, a display unit 14, and an input unit 15. These components can communicate with each other through a bus line 19.

  The communication unit 11 communicates with the outside by wireless communication. In the present embodiment, the communication unit 11 mainly performs wireless communication with the in-vehicle terminal 20 of the share car V. The storage unit 12 includes a ROM, a RAM, a flash memory, and the like, and stores programs for various processes executed by the user terminal 10. The storage unit 12 is also used as a working memory when various processes are executed. Further, the storage unit 12 stores service information to be described later.

  The control unit 13 is configured by a computer such as a CPU, and controls the entire user terminal 10. Specifically, the control unit 13 performs various processes by executing various programs stored in the storage unit 12. The display unit 14 is a liquid crystal display device or the like, and displays various types of information. The input unit 15 is a touch panel or the like provided on the display unit 14 and is used when a user inputs an instruction.

(In-vehicle terminal)
Next, the in-vehicle terminal 20 will be described in detail. FIG. 3 is a block diagram showing the internal configuration of the in-vehicle terminal 20. As illustrated, the in-vehicle terminal 20 mainly includes a communication unit 21, a storage unit 22, an input unit 23, a control unit 24, an interface 25, and an output unit 26. Each element in the in-vehicle terminal 20 is connected to each other via a bus line 29. The interface 25 is connected to the sensor unit 27.

  Based on the control of the control unit 24, the communication unit 21 transmits various information acquired by the share car V (hereinafter also referred to as “upload data”) to the vehicle cloud server 30 or updates the map DB. The map data is received from the vehicle cloud server 30. The communication unit 21 communicates with the user terminal 10 by wireless communication. Further, the communication unit 21 may perform a process of transmitting a signal for controlling the vehicle to the vehicle and a process of receiving a signal related to the state of the vehicle from the vehicle. The communication unit 21 is an example of a reception unit and a transmission unit of the present invention.

  The storage unit 22 stores a program executed by the control unit 24 and information necessary for the control unit 24 to execute a predetermined process. In the present embodiment, the storage unit 22 stores a plurality of map DBs, sensor data caches, and vehicle attribute information.

  The map DB is a database including, for example, road data, facility data, and feature data around the road. The road data includes lane network data for route search, road shape data, traffic regulation data, and the like. The feature data includes information such as signs such as road signs, road markings such as stop lines, road lane markings such as center lines, and structures along the road. Further, the feature data may include highly accurate point cloud information of the feature to be used for the vehicle position estimation. In addition, the map DB may store various data necessary for position estimation.

  The sensor data cache is a cache memory that temporarily holds output data of the sensor unit 27. The vehicle attribute information indicates information related to attributes of the share car V on which the in-vehicle terminal 20 is mounted, such as a vehicle type, a vehicle ID, a vehicle length, a vehicle width, a vehicle size such as a vehicle height, and a fuel type of the vehicle.

  The input unit 23 is a button operated by the user, a touch panel, a remote controller, a voice input device, etc., for example, an input for specifying a destination for route search, an input for specifying on / off of automatic driving, and the like And the generated input signal is supplied to the control unit 24. The output unit 26 is, for example, a display or a speaker that performs output based on the control of the control unit 24.

  The interface 25 performs an interface operation for supplying output data of the sensor unit 27 to the control unit 24 and the sensor data cache. The sensor unit 27 includes a plurality of external sensors for recognizing the surrounding environment of the vehicle such as a rider and a camera, and internal sensors such as a GPS receiver, a gyro sensor, a position sensor, and a three-axis sensor. The lidar discretely measures the distance to an object existing in the outside world, recognizes the surface of the object as a three-dimensional point group, and generates point group data. The camera generates image data taken from the vehicle. The position sensor is provided to detect the position of each external sensor, and the triaxial sensor is provided to detect the attitude of each external sensor. Note that the sensor unit 27 may include any external sensor and internal sensor other than the external sensor and the internal sensor illustrated in FIG. 3. For example, the sensor unit 27 may include an ultrasonic sensor, an infrared sensor, a microphone, and the like as an external sensor.

  The control unit 24 includes a CPU that executes a predetermined program on one or more platforms, and controls the entire in-vehicle terminal 20. The control unit 24 functionally includes a position estimation unit, an object detection unit, and an upload data generation unit.

  The position estimation unit estimates the own vehicle position (including the attitude of the vehicle) based on the output data of the sensor unit 27 held in the sensor data cache and the map DB. The position estimation unit can execute various position estimation methods. The position estimation unit, for example, a vehicle position estimation method based on dead reckoning (autonomous navigation) based on outputs of autonomous positioning sensors such as a GPS receiver and a gyro sensor, and a process of further collating road data in the map DB with autonomous navigation ( Vehicle position estimation method for performing map matching, output data of external sensors such as lidars and cameras, and landmark position information indicated by the feature information of the map DB with reference to a predetermined object (landmark) existing around The vehicle position estimation method based on the above is executed. The position estimation unit executes the position estimation method having the highest estimation accuracy among the currently executable position estimation methods, and indicates the own vehicle position obtained based on the executed position estimation method. Information is supplied to the upload data generation unit. The position estimation unit supplies information specifying the executed position estimation method to the upload data generation unit by including in the vehicle position information.

  The object detection unit detects a predetermined object based on point cloud information, image data, audio data, and the like output from the sensor unit 27. In this case, for example, the object detection unit extracts feature data corresponding to the object detected by the sensor unit 27 from the map DB based on the vehicle position estimated by the position estimation unit. The object detection unit corresponds to the map DB when there is a difference between the position and shape of the object detected by the sensor unit 27 and the position and shape of the object indicated by the feature data extracted from the map DB. For example, when there is no feature data to be detected, information related to the object detected by the sensor unit 27 is supplied to the upload data generation unit.

  The upload data generation unit generates upload data based on the vehicle position information supplied from the position estimation unit, the object data supplied from the object detection unit, and the output data of the sensor unit 27 supplied from the sensor data cache. Generate. Then, the upload data generation unit transmits the generated upload data to the vehicle cloud server 30 through the communication unit 21.

(Vehicle cloud server)
Next, the vehicle cloud server 30 will be described in detail. FIG. 4A is a block diagram showing the internal configuration of the vehicle cloud server 30. As illustrated, the vehicle cloud server 30 includes a communication unit 31, a storage unit 32, a control unit 33, a service information DB 34, and a history DB 35. Each element in the vehicle cloud server 30 is connected to each other via a bus line 39.

  The communication unit 31 communicates with the in-vehicle terminal 20 of the share car V and the service cloud server 40 based on the control of the control unit 33. Specifically, the communication unit 31 receives upload data from the in-vehicle terminal 20 or transmits information corresponding to provided information described later to the service cloud server 40.

  The storage unit 32 includes a ROM, a RAM, and the like, and stores programs for various processes executed by the vehicle cloud server 30. The storage unit 32 is also used as a working memory when various processes are executed.

  The control unit 33 is configured by a computer such as a CPU, and controls the entire vehicle cloud server 30. Specifically, the control unit 33 performs various processes by executing various programs stored in the storage unit 32.

  The service information DB 34 stores service information transmitted from the in-vehicle terminal 20. The service information will be described in detail later.

  The history DB 35 stores upload data acquired by the vehicle cloud server 30 from the in-vehicle terminal 20. Specifically, the information received from each in-vehicle terminal 20 is stored in the history DB 35 in association with the vehicle ID of the share car V in which the in-vehicle terminal 20 is mounted, the reception time, and the like. The history DB 35 may store the provision information transmitted from the vehicle cloud server 30 to the service cloud server 40 as a history. In this case, information specifying the service cloud server 40 that has transmitted the provision information is stored in association with the provision information.

(Service cloud server)
Next, the service cloud server 40 will be described in detail. FIG. 4B is a block diagram showing the internal configuration of the service cloud server 40. As illustrated, the service cloud server 40 includes a communication unit 41, a storage unit 42, a control unit 43, a contract information DB 44, and a history DB 45. Each element in the service cloud server 40 is connected to each other via a bus line 49.

  The communication unit 41 communicates with the vehicle cloud server 30 based on the control of the control unit 43. Specifically, the communication unit 41 receives information corresponding to provision information described later from the vehicle cloud server 30.

  The storage unit 42 includes a ROM, a RAM, and the like, and stores programs for various processes executed by the service cloud server 40. The storage unit 42 is also used as a working memory when various processes are executed.

  The control unit 43 is configured by a computer such as a CPU, and controls the entire service cloud server 40. Specifically, the control unit 43 performs various processes by executing various programs stored in the storage unit 42.

  The contract information DB 44 stores contract information. The contract information is information that defines the service content provided by the service provider that operates the service cloud server 40 for users who use the share car V using the car sharing service. For example, when the service providing company is an insurance company, the contract information includes the contents of an insurance contract signed by the user with the insurance company. Further, the contract information includes provision information based on the contract. That is, the contract information includes provision information indicating information that the vehicle cloud server 30 should provide to the service provider based on the contract.

  The history DB 45 stores information acquired by the service cloud server 40 from the vehicle cloud server 30. This information is information transmitted from the vehicle cloud server 30 as corresponding to provision information indicating information requested by the service provider among the information acquired by the vehicle cloud server 30 from the in-vehicle terminal 20. Specifically, the information received from the vehicle cloud server 30 is stored in the history DB 45 in association with the information specifying the vehicle cloud server 30 that transmitted the information, the reception time, and the like.

[Service Information]
Next, service information will be described. The service information is information related to services that a user using the share car V has contracted with various service providers. The service information is stored in the storage unit 12 of the user terminal 10 as shown in FIG.

  FIG. 5 shows an example of service information. As illustrated, the service information includes “share car user ID”, “vehicle cloud”, “service cloud user ID”, “provided information”, and “provided destination address”.

  The “share car user ID” is a user ID for the share car management company. The share car management company is a company that provides the share car V to the user. As described above, the share car V is an autonomous driving vehicle manufactured by a plurality of automobile manufacturers, and the share car management company prepares and purchases the autonomous driving cars of those automobile manufacturers. At this time, the user makes a user contract with the share car management company, and the ID given to the user from the share car management company is the share car user ID.

  “Vehicle cloud” indicates a vehicle cloud contracted by a share car operating company used by a user. In this embodiment, it is assumed that the share car operating company is a company that provides users with a share car V manufactured and managed by company A and company B. In this case, the share car management company purchases auto-driving cars of car manufacturers A and B and provides them to users as a car sharing service, for example, and manages the share car V provided to the users. Ask an information collection company operated by. Therefore, the service information stored in the user terminal 10 stores information related to the vehicle cloud operated by the automobile manufacturers A and B as information collection companies. In the example of FIG. 5, a vehicle cloud “CL001” operated by company A and a vehicle cloud “CL002” operated by company B are stored. When a share car management company signs a contract with a new information collection company, the vehicle cloud is added.

  In addition, while the user is using the share car V provided by the share car management company, the in-vehicle terminal 20 of the share car V transmits various information acquired during traveling to the vehicle cloud server 30 as upload data. To do. For example, when a user receives a share car V of a car maker A from a share car management company, the in-vehicle terminal 20 of the share car V collects information acquired during travel by the car maker A. Upload to the company's vehicle cloud "CL001".

  The “service cloud user ID” is an ID of a user for a service cloud operated by a service provider company contracted by the user. A service cloud user ID is registered for each vehicle cloud operated by an automobile manufacturer. In the example of FIG. 5, the user has contracted with an insurance company, a map service company, a parking lot service company, and a route search service company regarding the vehicle cloud CL001 operated by the automobile manufacturer A. Therefore, the user can receive services from an insurance company, a map service company, a parking lot service company, and a route search service company when using the share car V of the automobile manufacturer A company. Specifically, in the example of FIG. 5, the service cloud user ID for the insurance company is “XXXX1”, the service cloud user ID for the map service company is “ZZZ1”, and the service cloud user ID for the parking lot service company is “ “WWWWW”, and the service cloud user ID for the route search service company is “RRRRRR”.

  Similarly, regarding the vehicle cloud CL002 operated by the automobile manufacturer B, the user contracts with an insurance company and a map service company. Therefore, the user can receive services from the insurance company and the map service company when using the share car V of the automobile manufacturer B company. Specifically, in the example of FIG. 5, the service cloud user ID for the insurance company is “XXXX2”, and the service cloud user ID for the map service company is “ZZZ2”. In some cases, a service provider may provide services to users by using services of another service provider. Specifically, when a route search service company makes a contract with a map service company, the latest map can be provided to the user and a route search service based on the latest map can be provided. Service level can be improved. In this case, the route search service company may receive the service directly from the map service company and obtain the latest map. Alternatively, a service cloud user ID of the map service company may be provided to the user from the route search service company so that the user can receive the service directly from the map service company.

  “Provided information” indicates information to be provided to each service cloud server 40 among various types of information acquired by the vehicle cloud server 30 from the in-vehicle terminal 20. For example, in the example of FIG. 5, “shooting information with N minutes before and after the occurrence of the accident” is defined as provision information for insurance companies. This is, for example, taken outside the vehicle with an in-vehicle camera that is one of the sensors mounted on the share car V, and is useful information for clarifying the situation at the time of the accident and the cause of the self. When an accident occurs in the share car V, the service cloud server 30 uses the information acquired from the vehicle-mounted terminal 20 of the share car V to capture information taken with N minutes of cameras before and after the accident, and the service cloud server 40 of the insurance company. Will be sent to. The insurance company can provide an appropriate insurance service based on the photographing information of the share car V.

  Similarly, for the map service company, “recognized object information” and “movement route information” are defined as provided information. Therefore, the service cloud server 30 transmits the recognition object information and the travel route information among the information acquired from the in-vehicle terminal 20 of the share car V to the service cloud server 40 of the map service company. The map service company can update the map data based on such information. In addition, the map service company can provide a service for supplying the latest map with updated data to the user of the share car V who has contracted.

  For the parking service company, “user destination” is set as provided information. Therefore, the service cloud server 30 transmits the destination set by the user among the information acquired from the in-vehicle terminal 20 of the share car V to the service cloud server 40 of the parking lot service company. The parking lot service company notifies the terminal device 20 via the vehicle cloud server 30 of parking lots where the shared car V can be parked out of the parking lots near the destination. You can park automatically at a nearby parking lot.

  For the route search service company, “departure point / destination / route” and “travel area” are set as provided information. Therefore, the service cloud server 30 uses the service cloud server of the route search service company for the “departure / destination / intermediate” and “travel area” set by the user from the information acquired from the in-vehicle terminal 20 of the share car V. 40 will be transmitted. The route search service company notifies the terminal device 20 via the vehicle cloud server 30 of the travel route according to the user's wish based on the information of “departure point / destination / route” and “travel area”. . As a result, the share car V can reach the destination from the starting point to the destination by an automatic driving by an appropriate route.

  The “providing destination address” indicates a transmission destination address of information corresponding to the providing information, that is, an address of the service cloud. In the example of FIG. 5, when an accident occurs in the share car V, the vehicle cloud server 30 transmits shooting information with N cameras before and after the accident to the address “xxx.xxx.co.jp”.

[Service information registration process]
Next, a process for registering the service information in the user terminal 10 and the in-vehicle terminal 20 will be described. FIG. 6 is a flowchart of the service information registration process. First, after starting an application program on the user terminal 10, the user inputs a share car user ID and a service cloud user ID to the user terminal 10, and the user terminal 10 receives them (step S11). The share car user ID is a user ID assigned to the user by the share car operating company, and the service cloud user ID is a user ID assigned to the user by each service providing company. When the user has contracted with a plurality of service providing companies, the user inputs the service cloud user ID of each service providing company.

  The user terminal 10 transmits the service cloud user ID received in step S11 to the service cloud server 40 operated by the corresponding service provider company (step S12). The service cloud server 40 refers to the contract information DB 44 to obtain provision information corresponding to the contract of the user (step S13), and transmits it to the user terminal 10 together with the provision destination address of the service cloud server 40 (step S14). .

  As described above, there is a case where a service provider company A (for example, a route search service company) to which a user makes a contract provides a service by using a service of another service provider company B (for example, a map service company). is there. When the service provider A provides the user with the service cloud user ID of the service provider B, the user ID of the service provider B is transmitted from the service provider A to the user terminal 10 in step S13 and automatically 10 is preferably registered. In this case, when the user ID of the service providing company B is registered, the user terminal 10 transmits the service cloud user ID to the service cloud server 40 operated by the service providing company B by the process of step S12. Alternatively, the service cloud server 40 of the service provider company A obtains the provision information and the provision destination address from the service cloud server 40 of the service provider company B, and the user terminal together with the service cloud user ID of the service provider company B 10 may be registered.

  The user terminal 10 stores the received provision information and provision destination address in the storage unit 12 as service information in association with the service cloud user ID (step S15). In this way, service information as illustrated in FIG. 5 is stored in the user terminal 10.

  Thereafter, when the user uses the share car V, service information is transmitted from the user terminal 10 to the in-vehicle terminal 20 (step S16). For example, when the user operates the user terminal 10 or the in-vehicle terminal 20, communication between the user terminal 10 and the in-vehicle terminal 20 is established, and service information is transmitted from the user terminal 10 to the in-vehicle terminal 20. When receiving the service information from the user terminal 10, the in-vehicle terminal 20 stores the service information in the service information DB 34 and transmits the service information to the vehicle cloud server 30 (step S17). In this case, the in-vehicle terminal 20 transmits only the information related to the destination vehicle cloud server 30 in the service information. For example, when receiving the service information shown in FIG. 5 from the user terminal 10, the in-vehicle terminal 20 transmits only a portion corresponding to the vehicle cloud CL001 shown in FIG. 7A to the vehicle cloud server 30 of the vehicle cloud CL001. Only the part corresponding to the vehicle cloud CL002 shown in FIG. 7B is transmitted to the vehicle cloud server 30 of the vehicle cloud CL002.

[Use start processing]
Next, a process in which the user starts using the share car V will be described.
(First example)
In the first example, the service cloud server 40 performs user authentication based on the service cloud user ID. FIG. 8 is a flowchart of a first example of the use start process. As a premise, it is assumed that the in-vehicle terminal 20 receives and stores service information from the user terminal 10 as shown in step S16 of FIG.

  First, when the user operates the user terminal 10 and inputs an instruction to start using the share car V, the user terminal 10 transmits a use start request to the in-vehicle terminal 20 (step S20). The in-vehicle terminal 20 refers to the service information of the user, acquires the share car user ID and the service cloud user ID associated with the vehicle cloud for the share car V, and transmits the service cloud user ID to the vehicle cloud server 30 (step S21). .

  The vehicle cloud server 30 performs authentication based on the share car user ID received from the in-vehicle terminal 20 (step S22). That is, the vehicle cloud server 30 determines whether the user has a user contract with the share car operating company. If the authentication is successful, the vehicle cloud server 30 transmits the service cloud user ID to the corresponding service cloud server 40 (step S23). In addition, when authentication fails, the vehicle cloud server 30 transmits that to the vehicle-mounted terminal 20, and a process is complete | finished.

  The service cloud server 40 performs authentication based on the service cloud user ID received from the vehicle cloud server 30 (step S24). Specifically, the service cloud server 40 refers to the contract information DB 44 and determines whether or not a contract corresponding to the service cloud user ID exists effectively. Then, the service cloud server 40 transmits the authentication result to the vehicle cloud server 30 (step S25).

  The vehicle cloud server 30 transmits the authentication result received from the service cloud server 40 to the in-vehicle terminal 20 (step S26). The in-vehicle terminal 20 notifies the user of the authentication result by display by the output unit 26 (step S27). Thus, the process ends.

(Second example)
In the second example, the service cloud server 40 performs user authentication based on the service cloud user ID and the vehicle information. FIG. 9 is a flowchart of a second example of the use start process. As a premise, it is assumed that the in-vehicle terminal 20 receives and stores service information from the user terminal 10 as shown in step S16 of FIG.

  First, when the user operates the user terminal 10 and inputs an instruction to start use, the user terminal 10 transmits a use start request to the in-vehicle terminal 20 (step S30). The in-vehicle terminal 20 refers to the service information of the user, acquires the share car user ID and the service cloud user ID associated with the vehicle cloud for the share car V, and the vehicle of the share car V on which the in-vehicle terminal 20 is mounted. It transmits to vehicle cloud server 30 with ID (step S31).

  The vehicle cloud server 30 performs authentication based on the share car user ID received from the in-vehicle terminal 20 (step S32). That is, the vehicle cloud server 30 determines whether the user has a user contract with the share car operating company. If the authentication is successful, the vehicle cloud server 30 acquires vehicle information (for example, information on the vehicle type of the share car V, information on the travel distance, information on the failure location, etc.) based on the vehicle ID, and the service cloud user ID and the vehicle information. Are transmitted to the service cloud server 40 (step S33). In addition, when authentication fails, the vehicle cloud server 30 transmits that to the vehicle-mounted terminal 20, and a process is complete | finished.

  The service cloud server 40 performs authentication based on the service cloud user ID and vehicle information received from the vehicle cloud server 30 (step S34). Specifically, the service cloud server 40 refers to the contract information DB 44, and whether or not the contract corresponding to the service cloud user ID exists effectively and the vehicle information has the conditions specified in the contract. Determine whether. For example, in the case of the service cloud server 40 of an insurance company, it is determined whether or not the vehicle that the user intends to use matches the vehicle conditions specified in the user's insurance contract. For example, it is assumed that the insurance service is applicable only when the user uses a specific vehicle type. This means that, for example, when using a specific vehicle type with a high accident rate, the insurance contract does not provide insurance services. In this case, when the user uses a different vehicle type, the authentication is not successful. Similarly, if the contents of the insurance contract are those in which the insurance service can be applied only when the travel distance of the vehicle used by the user is within a predetermined range, the user uses a vehicle that has traveled over a predetermined distance. In some cases, authentication is not successful.

  If the contract corresponding to the service cloud user ID exists effectively and the vehicle information has the conditions specified in the contract, the service cloud server 40 makes the authentication successful. Then, the service cloud server 40 transmits the authentication result to the vehicle cloud server 30 (step S35).

  The vehicle cloud server 30 transmits the authentication result received from the service cloud server 40 to the in-vehicle terminal 20 (step S36). The in-vehicle terminal 20 notifies the user of the authentication result by display by the output unit 26 (step S37). Thus, the process ends.

  In the second example, the service cloud server 40 performs authentication by checking not only the service cloud user ID but also the vehicle that the user is trying to use and the vehicle conditions in the user's contract. Even when there are various contract conditions between and the user, the user can be properly authenticated.

  In the above-described embodiment, the vehicle information is described as the condition for providing the insurance service. However, for example, the travel range of the share car V (that is, the region or the route to which the user goes) may be used as the condition for providing the insurance service. Conceivable. This is the case when the user passes through a dangerous area and the contract does not apply the insurance service. In this case, the service cloud 40 receives, from the terminal device 20 via the vehicle cloud 30, information on the user's destination and the travel route to the destination instead of the vehicle information. When the contract corresponding to the service cloud user ID exists effectively and the travel range of the share car V satisfies the conditions specified by the contract, the service cloud server 40 determines that the authentication is successful.

[Provision of information from vehicle cloud server to service cloud server]
Next, a process for providing information from the vehicle cloud server 30 to the service cloud server 40 will be described. The vehicle cloud server 30 is operated by an information collection company, periodically acquires various types of information from the in-vehicle terminal 20 of the share car V, and stores the information in the history DB 35. On the other hand, the service cloud server 40 does not require all information acquired by the vehicle cloud server 30 from the in-vehicle terminal 20, but specific information is necessary for providing a service to the user. From this viewpoint, as described above, information necessary for each service cloud is defined as provision information, and service information including provision information is given to the vehicle cloud server 30. The vehicle cloud server 30 provides only necessary information to the service cloud server 40 in accordance with the provision of provision information.

  In the example of the service information shown in FIG. 5, for example, when an accident occurs in the share car V, the vehicle cloud server 30 uses N cameras before and after the accident occurrence among various information acquired from the in-vehicle terminal 20. Only the photographing information is transmitted to the service cloud server 40 of the insurance company. Further, when the detection result of the object acquired by the sensor unit 27 of the share car V is different from the map information, the object recognition information including the fact and the position information is transmitted to the service cloud server 40 of the map service company. The service cloud server 40 stores the information thus received from the vehicle cloud server 30 in the history DB 45. The vehicle cloud server 30 may store the information transmitted to the service cloud server 40 in the history DB 35.

  FIG. 10 is a flowchart of information providing processing from the vehicle cloud server to the service cloud server. As a premise, it is assumed that the in-vehicle terminal 20 receives and stores service information from the user terminal 10 as shown in step S16 of FIG.

  First, the in-vehicle terminal 20 transmits service information to the vehicle cloud server 30 (step S41). The vehicle cloud server 30 stores the received service information in the service information DB 34 (step S42). As a premise, in step S22 of FIG. 8, the vehicle cloud server 30 performs authentication based on the share car user ID received from the in-vehicle terminal 20, and the in-vehicle terminal 20 is a result of successful authentication in step S27. Is assumed to be received.

  During traveling of the share car V, the in-vehicle terminal 20 transmits various information (hereinafter, referred to as “detection information”) acquired by the sensor unit 27 and the like to the vehicle cloud server 30 (step S43). Stores the received detection information in the history DB 35 (step S44).

  Next, the vehicle cloud server 30 refers to the service information, and transmits, to the service cloud server 40, the detection information corresponding to the provision information defined for each service cloud among the detection information received from the in-vehicle terminal 20. For example, in the example of FIG. 5, the vehicle cloud server 30 of the vehicle cloud CL001 transmits information for N minutes before and after the accident to the service cloud server 40 of the insurance company (providing address “xxx.xxx.co.jp”). . The service cloud server 40 stores the received detection information in the history DB 45.

  Thus, by providing service information including provision information to the vehicle cloud server 30, the vehicle cloud server 30 efficiently uses only the information requested by the service provider out of various types of detection information acquired by the in-vehicle terminal 20. Can be transmitted to the service cloud server 40.

  When the vehicle cloud server 30 transmits the detection information corresponding to the provided information to the service cloud server 40, the history information indicating the detection information transmitted to the service cloud server 40 may also be stored in the history DB 35. preferable.

[Use termination processing]
Next, a process when the user finishes using the share car V will be described. FIG. 11 is a flowchart of the use end process when the user ends the use of the share car V. When the user inputs a usage termination instruction to the user terminal 10, the user terminal 10 transmits a usage termination request to the in-vehicle terminal 20 (step S50). For example, while the user is using the share car V, a button (for example, a “get down” button) for instructing the end of use is displayed on the user terminal 10 and the user presses the button. In addition, it may be determined that an instruction to end use has been input.

  When receiving the usage termination request from the user terminal 10, the in-vehicle terminal 20 transmits the usage termination request to the vehicle cloud server 30 (step S51). When the vehicle cloud server 30 receives the use end request, the vehicle cloud server 30 performs use end processing (step S52). Specifically, the vehicle cloud server 30 cancels registration as a user of the user's share car V, and ends transmission of the detection information to the service cloud server 40. Further, the vehicle cloud server 30 notifies the service cloud server 40 of the end of use of the user (step S53). Thereby, the service cloud server 40 recognizes that the use of the share car V has been completed by the user, that transmission of detection information from the vehicle cloud server 30 is stopped, and the like.

  Further, the vehicle cloud server 30 transmits a use end notification indicating that the use end processing has been performed to the in-vehicle terminal 20 (step S54). When the in-vehicle terminal 20 receives the use end notification from the vehicle cloud server 30, the in-vehicle terminal 20 transmits a use end notification to the user terminal 10 (step S55). The user terminal 10 displays the end of use on the display unit 14 (step S56), and informs the user that the use by the user has ended normally.

[History deletion processing]
Next, a process for deleting history information stored in the vehicle cloud server 30 and the service cloud server 40 will be described. As described above, the vehicle cloud server 30 stores the information acquired from the in-vehicle terminal 20 while the user is using the share car V in the history DB 35. The service cloud server 40 receives detection information corresponding to the provided information from the vehicle cloud server 30 while the share car V is used by the user, and stores the detection information in the history DB 45. These provided information is personal information for the user, and the user does not want the provided information to be continuously recorded in the information collecting company or the service providing company even after the service providing from the service providing company is finished. There is. Therefore, after the user has finished using the share car V, the user can request deletion of the history information. The vehicle cloud server 30 and the service cloud server 40 delete the history information based on the user deletion request.

  FIG. 12 is a flowchart of the history deletion process. First, the user operates the user terminal 10 to transmit a history deletion request to the in-vehicle terminal 20 (step S60). The history deletion request includes the share car user ID of the user. When receiving the history deletion request from the user terminal 10, the in-vehicle terminal 20 transmits the history deletion request to the vehicle cloud server 30 (step S61).

  When the vehicle cloud server 30 receives the history deletion request, the vehicle cloud server 30 deletes the history information corresponding to the share car user ID included in the history deletion request from the history information stored in the history DB 35 (step S62). Furthermore, the vehicle cloud server 30 transmits a history deletion request to the service cloud server 40 (step S63). At that time, the vehicle cloud server 30 refers to the service information and includes the service cloud user ID in the history deletion request and transmits it to the service cloud server 40.

  When receiving the history deletion request, the service cloud server 40 deletes the history information corresponding to the service cloud user ID included in the history deletion request from the history information stored in the history DB 45 (step S64). Then, the service cloud server 40 transmits a deletion completion notification indicating that the history information has been deleted to the vehicle cloud server 30 (step S65).

  When the vehicle cloud server 30 receives the notification of the completion of deletion from the service cloud server 40, the vehicle cloud server 30 transmits a notification of the completion of deletion to the in-vehicle terminal 20 (step S66). This notification indicates that both the history deletion in the vehicle cloud server 30 and the history deletion in the service cloud server 40 have been completed.

  When receiving the notification of the completion of deletion from the vehicle cloud server 30, the in-vehicle terminal 20 transfers the notification of the completion of deletion to the user terminal (step S67). When the user terminal 10 receives the notification of the completion of deletion from the in-vehicle terminal 20, the user terminal 10 displays on the display unit 14 the end of deletion (step S68). As a result, the user can know that the history information has been deleted correctly.

  In the above example, the history deletion request by the user is transmitted to the vehicle cloud server 30 through the in-vehicle terminal 20, but may instead be transmitted directly from the user terminal 20 to the vehicle cloud server 30. Further, the history deletion request may include the range of information for which deletion is requested, for example, according to the date or time when the information is transmitted. In this case, the vehicle cloud server 30 and the service cloud server 40 delete the history information corresponding to the specified date and time. In addition, the vehicle cloud server 30 deletes information (data amount, number of records, etc.) related to the amount of information transmitted to the service cloud server 40 from the service cloud server 40 when stored for each service cloud user ID. Along with the notification of completion, the information regarding the amount of information deleted by the service cloud server 40 is received and collated to confirm that the history information has been securely deleted, and then the deletion completion notification to the in-vehicle terminal 20 May be sent.

[Use of biometric authentication]
Next, a method of using biometric information in user authentication using the share car V will be described. When a user uses a vehicle cloud or a service cloud, it is necessary to prevent spoofing. As an example of impersonation, there is a case where another user Y uses the share car V after the user X completes the authentication for the vehicle cloud and the service cloud. If such a thing is performed, a service provider will provide the service based on the contract with the user X with respect to the user Y who has not contracted. Therefore, authentication using biometric information is performed at the time of use start authentication and during actual use of the share car V.

  FIG. 13 schematically shows an authentication method using biometric information. In the following, fingerprint information is used as biometric information. First, at the start of use authentication, fingerprint authentication is performed by the user terminal 10, and when the authentication is successful, the user terminal 10 transmits fingerprint information to the in-vehicle terminal 20. The in-vehicle terminal 20 stores the received fingerprint information in the storage unit 22 or the like. As described above, the vehicle cloud server 30 and the service cloud server 40 perform authentication for starting use.

  Thereafter, while the user uses the share car V, the in-vehicle terminal 20 periodically performs biometric authentication using the steering of the share car V or the like. For example, a sensor provided in the steering of the share car V detects the user's fingerprint information. The in-vehicle terminal 20 collates the fingerprint information acquired from the user terminal 10 at the start of use with the biometric information acquired from the sensor while using the share car V. If they match, the identity of the user who has authenticated the start of use and the user who uses the share car V is guaranteed. Therefore, the in-vehicle terminal 20 notifies the vehicle cloud server 30 that the user who has authenticated the start of use matches the user who is using the share car V. In addition, the vehicle cloud server 30 notifies the service cloud server 40 that a legitimate user is using the share car V. In this way, impersonation of the user can be detected. In the above example, fingerprint information is used as the biometric information. However, other biometric information may be used, and face authentication may be used.

  FIG. 14 is a flowchart showing an authentication process at the start of use using biometric information. The user performs biometric authentication such as a fingerprint using the user terminal 10 (step S60). If the authentication is successful, the user terminal 10 transmits biometric information to the in-vehicle terminal 20 (step S61). The in-vehicle terminal 20 stores the biological information transmitted from the user terminal 10 (step S62), and transmits an authentication request to the vehicle cloud server 30 (step S63). At this time, as described above, the in-vehicle terminal 20 transmits the share car user ID and the service cloud user ID to the vehicle cloud server 30.

  The vehicle cloud server 30 performs authentication based on the share car user ID (step S64). When the authentication is successful, the vehicle cloud server 30 transmits an authentication request including the service cloud user ID to the service cloud server 40 (step S65). The service cloud server 40 performs authentication based on the service cloud user ID (step S66), and transmits the authentication result to the vehicle cloud server 30 (step S67).

  The vehicle cloud server 30 transmits the authentication result received from the service cloud server 40 to the in-vehicle terminal 20 (step S68), and the in-vehicle terminal 20 transmits the authentication result received from the vehicle cloud server 30 to the user terminal 10 (step S69). ). The user terminal 10 displays the received authentication result on the display unit 14 (step S70). Thus, the authentication process at the start of use ends.

  FIG. 15 is a flowchart of the authentication process during use of the share car V by the user. The in-vehicle terminal 20 periodically detects the user's biometric information with a sensor or the like (step S71), and collates with the biometric information acquired from the user terminal 10 at the start of use (step S72). And the vehicle-mounted terminal 20 transmits a collation result to the vehicle cloud server 30 (step S73). In addition, the vehicle cloud server 30 transmits the received verification result to the service cloud server 40 (step S74). Thereby, in step S72, when the biometric information matches, the vehicle cloud server 30 and the service cloud server 40 are notified that a valid user is using the share car V. On the other hand, if the biometric information does not match in step S72, a matching result indicating that is transmitted to the vehicle cloud server 30 and the service cloud server 40, so that the vehicle cloud and the service cloud can take appropriate measures. .

DESCRIPTION OF SYMBOLS 10 User terminal 20 In-vehicle terminal 27 Sensor part 30 Vehicle cloud server 40 Service cloud server

Claims (8)

A data structure of transmission data transmitted from an in-vehicle terminal mounted on a vehicle used by a user to a server device that collects information from the vehicle,
A user ID of the user for a service provider that provides services related to vehicles;
A vehicle ID for identifying a vehicle on which the in-vehicle terminal is mounted;
Including
A data structure used for authentication of the user based on the user ID and the vehicle ID by the server device of the service providing company. An in-vehicle terminal mounted on a vehicle used by a user,
A receiving unit that receives the user ID of the user for a service provider that provides services related to the vehicle from the user terminal device;
A transmission unit that transmits data including the user ID and a vehicle ID that identifies a vehicle on which the in-vehicle terminal is mounted to a server device that collects information from the vehicle;
In-vehicle terminal equipped with.   The in-vehicle terminal according to claim 2, wherein the receiving unit receives a result of authentication performed by the service providing company based on the user ID.   The transmission unit collects information from the vehicle, including service information including information to be provided to the server device of the service providing company, out of information collected from the vehicle, when the success of the authentication is received. The in-vehicle terminal device according to claim 3 which transmits to a server device.   The in-vehicle terminal according to claim 3, wherein the transmission unit transmits the authentication result to the terminal device of the user. An information communication method executed by an in-vehicle terminal mounted on a vehicle used by a user,
A receiving step of receiving the user ID of the user from a user terminal device for a service provider that provides a service related to the vehicle;
A transmission step of transmitting data including the user ID and a vehicle ID for identifying the vehicle on which the in-vehicle terminal is mounted to a server device that collects information from the vehicle;
An information communication method comprising: A program provided with a computer and executed by an in-vehicle terminal mounted on a vehicle used by a user,
A receiving unit that receives the user ID of the user from a terminal device of the user to a service provider that provides a service related to the vehicle;
A transmission unit that transmits data including the user ID and a vehicle ID that identifies a vehicle on which the in-vehicle terminal is mounted to a server device that collects information from the vehicle;
A program for causing the computer to function as   A storage medium storing the program according to claim 7.