Management system and management method

Abstract

To improve convenience for sharing users in a car sharing service between individuals.SOLUTION: A management system for managing the rental of a vehicle owned by an individual owner to a sharing user, comprises: a share information storage unit for storing a specific service related to the vehicle to which the owner subscribes; a key generation unit for generating key information for the sharing user to use the vehicle in response to a usage request for allowing the sharing user to use the vehicle; a service collaboration unit for generating collaboration information for the sharing user to use the specific service in response to the usage request for allowing the sharing user to use the vehicle; and a distribution unit for distributing the key information and the collaboration information.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a management system and a management method.

Background Art

[0002] There is a peer-to-peer car-sharing service in which an individual owner temporarily lends out the vehicle owned by the individual owner in response to the demand of a share user. Further spread of peer-to-peer car-sharing is desired from the viewpoint of alleviating traffic congestion due to a decrease in the number of vehicles. Patent Document 1 discloses a technique applicable to a car-sharing service for a vehicle owned by an individual.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, Patent Document 1 does not consider the convenience of share users. In order to promote further spread of car-sharing, it would be better if the convenience of share users could be improved.

[0005] The present invention has been made in view of such a situation, and an object thereof is to provide a management system and a management method capable of improving the convenience of share users in a peer-to-peer car-sharing service.

Means for Solving the Problems

[0006] The management system of the present invention is a management system for managing the lending of a vehicle owned by an individual owner to a shared user, and includes a share information storage unit that stores specific services related to the vehicle to which the owner subscribes, a key generation unit that generates key information for the shared user to use the vehicle in response to a use request for the shared user to use the vehicle, a service cooperation unit that generates cooperation information for the shared user to use the specific service in response to a use request for the shared user to use the vehicle, and a distribution unit that distributes the key information and the cooperation information.

[0007] The management method of the present invention is used in a management system for managing the lending of a vehicle owned by an individual owner to a shared user, and is a management method performed by a computer including a share information storage unit that stores specific services related to the vehicle to which the owner subscribes. In response to a use request for the shared user to use the vehicle, key information for the shared user to use the vehicle is generated, cooperation information for the shared user to use the specific service is generated in response to a use request for the shared user to use the vehicle, and the key information and the cooperation information are distributed.

Advantages of the Invention

[0008] According to the present invention, the convenience of shared users can be improved in the personal car-sharing service.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Mode for Carrying Out the Invention

[0010] Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0011] (Regarding the management system 1) The management system 1 is a system for managing peer-to-peer carsharing. In the management system 1, a peer-to-peer carsharing service is provided in which vehicles owned by individual owners are temporarily lent out in response to the requests of share users. Hereinafter, the case where the vehicle owned by the owner is an electric vehicle will be exemplified and described.

[0012] FIG. 1 is a block diagram showing a configuration example of the management system 1 in the embodiment. The management system 1 includes, for example, a key distribution server 10, a vehicle owner terminal 20, a share user terminal 30, a vehicle 40, a charging service membership server 50, a settlement server 60, and a charging device 70.

[0013] The components of the management system 1, that is, the key distribution server 10, the vehicle owner terminal 20, the share user terminal 30, the vehicle 40, the charging service membership server 50, and the settlement server 60 are communicably connected via a communication network NW such as the Internet. In addition, the vehicle owner terminal 20 and the vehicle 40, and the share user terminal 30 and the vehicle 40 are communicably connected via short-range wireless communication such as RFID (Radio Frequency Identification), BLE (Bluetooth (registered trademark) Low Energy), WiFi (Wi-Fi), and NFC (Near field communication). In addition, the vehicle 40 and the charging device 70 are communicably connected via short-range wireless communication such as RFID, BL, WiFi, and NFC.

[0014] The key distribution server 10 is a computer that manages the lending and borrowing of vehicles owned by individual owners. As the key distribution server 10, a server device, a cloud, a PC (personal computer), etc. can be applied. The key distribution server 10 issues key information for using the vehicle 40 in response to a request from the vehicle owner terminal 20. The key information is encrypted information used to unlock or start the vehicle 40. The key distribution server 10 distributes the issued key information to the vehicle owner terminal 20 and the vehicle 40.

[0015] The vehicle owner terminal 20 is a computer operated by the owner. As the vehicle owner terminal 20, a smartphone, a tablet terminal, a PC, etc. can be applied. An application program (vehicle operation app) for operating the vehicle is installed in the vehicle owner terminal 20. The vehicle owner terminal 20 requests key information for using the vehicle 40 from the key distribution server 10 via the vehicle operation app, and stores the key information obtained in response to the request. The owner unlocks or starts the vehicle 40 by operating the vehicle owner terminal 20 to start the vehicle operation app and operating the screen displayed on the vehicle operation app.

[0016] The share user terminal 30 is a computer operated by the share user. As the share user terminal 30, a smartphone, a tablet terminal, a PC, etc. can be applied. Similar to the vehicle owner terminal 20, a vehicle operation app is installed in the share user terminal 30.

[0017] For example, when a shared user shares a vehicle owned by the owner, the vehicle owner terminal 20 requests the key distribution server 10 to issue key information (shared key) used by the shared user. The shared user terminal 30 obtains the shared key via the vehicle operation application and stores the obtained shared key. The shared user operates the shared user terminal 30 to start the vehicle operation application and operates the screen displayed on the vehicle operation application to unlock or start the vehicle 40.

[0018] The vehicle 40 is an electric vehicle. The vehicle 40 includes a vehicle control unit 41 and a vehicle storage unit 42. The vehicle control unit 41 is a computer that controls the vehicle 40. The vehicle control unit 41 is configured to be communicable with an operation terminal (here, the vehicle owner terminal 20 or the shared user terminal 30). The vehicle control unit 41 controls the vehicle 40 by unlocking the vehicle door of the vehicle 40 or starting the engine of the vehicle 40 according to the operation signal received from the operation terminal. The vehicle storage unit 42 stores the key information generated by the key distribution server 10.

[0019] When the vehicle control unit 41 operates the vehicle 40 according to the operation signal, it authenticates the user (here, the owner or the shared user) operating the operation terminal. The authentication is to determine whether the operator operating the operation terminal that sent the operation signal is a user who has the right to use the vehicle 40. The vehicle control unit 41 includes, for example, a dedicated IC chip that performs processing specialized in authentication processing and encryption / decryption processing called SE (Secure Element), and performs authentication by this SE. As a result of the authentication, if it is determined that the operator is a user who has the right to use the vehicle 40, the vehicle control unit 41 follows the operation signal. The vehicle control unit 41 may store the key information in a secure memory area provided in the SE.

[0020] The charging service member server 50 is a computer that manages the charging device 70 and provides a charging service to charging service members who use the charging device 70. In the charging service, charging of an electric vehicle is performed using a charging card. The charging card is a card issued to smoothly perform authentication and charging by allowing credit card information etc. to be registered in advance.

[0021] For example, when the owner registers for use in the charging service of the operator who operates the charging service member server 50, a charging card is issued to the owner by that operator. The charging card has registered thereon the charging plan joined by the owner and authentication information for authenticating the owner as a member of the charging service. The owner registers credit card information etc. for settling the membership fee and charging fee of the charging card in advance, and then charges at the charging facility using the charging card. The charging service member server 50 authenticates that the owner is a member of the charging service using the information registered on the charging card and then allows charging.

[0022] Here, while the owner tends to use the charging service using a charging card, the share user tends not to have a charging card. Since the share user uses the vehicle only when necessary by carsharing, charging is not often performed. For the share user, it is troublesome to issue a charging card only for using the vehicle by carsharing. Also, while having a charging card allows charging at a lower cost than the guest fee, fixed costs such as membership fees are incurred. For this reason, many share users who do not have a charging card think that using only at the guest fee when necessary can suppress the total expenses. Share users who do not have a charging card have to charge at a high guest fee when using the vehicle by carsharing, making it difficult to use carsharing.

[0023] On the other hand, in the management system 1 of the present embodiment, share users who use the vehicles owned by the owner are enabled to receive a charging service equivalent to the charging card held by the owner. As a result, even share users who do not have a charging card can easily use carsharing, improving the convenience for share users.

[0024] The charging service membership server 50 includes, for example, a charging authority management unit 51, a charging authority distribution unit 52, and a membership information storage unit 53. The charging authority management unit 51 manages charging authorities for charging service members, such as the type of charging plan to which the owner subscribes and whether to allow share users to use the charging plan to which the owner subscribes. The charging authority management unit 51 issues authentication information for the owner to use the charging service as a charging service member in response to a request from the vehicle owner terminal 20. The authentication information is information indicating that the owner of the vehicle 40 is a charging service member and is used for authentication performed between the vehicle 40 and the charging device 70 during charging. The charging authority distribution unit 52 distributes the authentication information issued by the charging authority management unit 51 to the vehicle 40 and the charging device 70. The membership information storage unit 53 stores the membership information of charging service members.

[0025] The settlement server 60 is a computer that settles charging fees. When charging using a charging card is performed, the settlement server 60 receives the charging fee corresponding to the charging from the charging device 70. The settlement server 60 makes a claim to the user (here, the owner or share user) via the charging service membership server 50 or the like based on the received charging fee and accepts payment from the user.

[0026] The charging device 70 is a device that supplies power to the vehicle 40. The charging device 70 includes a charging permission determination unit 71, a charging fee management unit 72, and a charging control unit 73. The charging permission determination unit 71 receives a charging request from the vehicle 40 and determines whether to charge the vehicle 40 based on the received charging request. For example, when the charging permission determination unit 71 receives authentication information issued by the charging service membership server 50 from the vehicle 40, it determines to charge the vehicle 40. The charging fee management unit 72 calculates a charging fee corresponding to the charging when the vehicle 40 is charged. The charging control unit 73 controls the charging device 70 and charges the vehicle 40 for which the charging permission determination unit 71 has determined to perform charging.

[0027] (Regarding the key distribution server 10) The key distribution server 10 includes, for example, a key generation unit 11, a distribution unit 12, a service cooperation unit 13, and a shared information storage unit 14. The key generation unit 11 generates key information for the owner to use the vehicle 40 in response to a usage request from the vehicle owner terminal 20. The key information here is encryption information included in an operation signal for operating the vehicle, and is encryption information used for authentication to determine whether the operator who sent the operation signal is a user who has the right to use the vehicle 40. As the encryption information used here, any information may be used. For example, electronic certificates and key pairs used for mutual authentication or one-way authentication, common keys used for encrypted communication, passwords, etc. can be applied. In addition, the key generation unit 11 issues key information for the shared user to use the vehicle 40 in response to a usage request from the vehicle owner terminal 20. The distribution unit 12 distributes the key information generated by the key generation unit 11. The distribution unit 12 distributes the key information for the owner to use the vehicle 40 by transmitting the key information to the vehicle owner terminal 20 and the vehicle 40. In addition, the distribution unit 12 distributes the key information for the shared user to use the vehicle 40 by transmitting the key information to the shared user terminal 30 and the vehicle 40.

[0028] When the key generation unit 11 generates key information for a shared user to use the vehicle 40, the service cooperation unit 13 refers to the share information storage unit 14 in response to a usage request, and determines whether there is a specific service related to the vehicle 40 (hereinafter referred to as vehicle service) (for example, a charging service) subscribed by the owner. If there is a vehicle service subscribed by the owner, and the owner permits to lend (share) the vehicle service to the shared user, the service cooperation unit 13 generates cooperation information. The cooperation information is information for realizing shared usage in which the shared user uses the vehicle service with owner authority. Here, the shared usage means that the shared user uses the vehicle service by applying the usage plan contracted by the owner for the vehicle service. For example, when the owner subscribes to the charging service, the shared user uses the charging plan contracted for the charging service.

[0029] In this embodiment, it is assumed that the vehicle service is a service provided via an application program (vehicle service usage application) for using the vehicle service. The cooperation information includes link information for linking the vehicle operation application and the vehicle service usage application via an API (Application Programming Interface). This link information includes information for realizing shared usage in the vehicle service usage application, for example, information for logging in to the vehicle service usage application with the account of the shared user, information of the owner of the vehicle to be shared, the usage period during which the shared user uses the vehicle by sharing, the type and usage plan of the vehicle service that can be shared, link information for issuing authentication information for shared usage or for transitioning to a page for registering settlement information for shared usage.

[0030] The distribution unit 12 transmits the cooperation information to the shared user terminal 30. Also, the distribution unit 12 transmits the cooperation information to a computer (here, the charging service member server 50) managed by an operator providing the specific service. Thereby, the distribution unit 12 distributes the cooperation information.

[0031] When the key information and the cooperation information are distributed by the distribution unit 12, the shared user terminal 30 receives the key information and the cooperation information, and stores the received key information and cooperation information in the vehicle operation application.

[0032] In this case, for example, when the vehicle operation application is started on the shared user terminal 30 in response to an operation by the shared user, a first operation column for operating the vehicle based on the key information and a second operation column for using the vehicle service based on the cooperation information are displayed in the vehicle operation application. When the shared user operates the first operation column, an operation signal for unlocking the vehicle 40 is transmitted from the shared user terminal 30, and communication with the vehicle 40 is performed, such as transmitting the key information in response to a request from the vehicle 40.

[0033] Also, when the shared user operates the second operation column, the screen transitions to the vehicle service use application, and a screen for issuing authentication information for sharing use is displayed. The shared user, according to the display of the issuance screen, for example, "You are permitted to share the charging service from the owner. However, the billing destination in the case of sharing the charging service is the shared user. If the shared user registers payment information such as a credit card in the vehicle service use application, the charging service can be used. Do you wish to share the use of the charging service?" In response to a question text such as this, a response column provided with operation buttons indicating "Yes" and "No" is displayed. When the shared user clicks the operation button indicating "Yes" or otherwise wishes to share the use of the vehicle service, a registration screen for registering payment information is displayed in the vehicle service use application. The shared user registers the payment information by inputting the credit card number or the like according to the display of the registration screen. When the payment information is registered, authentication information for sharing the use of the vehicle service is generated, and the generated authentication information is transmitted to the vehicle 40 and the charging device 70 by the charging service membership server 50. The vehicle 40 stores the authentication information transmitted from the charging service membership server 50 via the vehicle operation application. Also, the charging device 70 stores the authentication information transmitted from the charging service membership server 50 via the vehicle operation application.

[0034] This enables the claim for the vehicle service using the share to be settled by the share user. In this case, the owner may be notified that a claim has been made against the share user, so that the owner can also grasp the share usage situation even when no claim for share usage is made against the owner.

[0035] In addition, the share user terminal 30 may transition to the vehicle service use application via the cooperation information in response to an operation by the share user, and display information provided by the vehicle service use application, such as guidance on a nearby charging device and the availability of the charging device. As a result, the share user can confirm guidance on a nearby charging device and the availability of the charging device.

[0036] The share information storage unit 14 manages share information. The share information includes information indicating a specific service (here, a charging service) related to the vehicle 40 that the share user can use with the owner's authority when the owner lends the vehicle 40 to the share user.

[0037] The storage unit (including the share information storage unit 14) provided in the key distribution server 10 is composed of a storage medium such as an HDD (Hard Disk Drive), a flash memory, an EEPROM (Electrically Erasable Programmable Read Only Memory), a RAM (Random Access read / write Memory), a ROM (Read Only Memory), or a combination thereof. The storage unit provided in the key distribution server 10 stores a program for executing various processes in the key distribution server 10 and temporary data used when performing various processes. In addition, the functional units (the key generation unit 11, the distribution unit 12, and the service cooperation unit 13) provided in the key distribution server 10 are realized by causing the CPU (Central Processing Unit) provided in the key distribution server 10 as hardware to execute a program.

[0038] (Regarding the information stored in the sharing information storage unit 14) FIG. 2 is a diagram showing an example of information stored in the sharing information storage unit 14 in the embodiment. The sharing information storage unit 14 stores information associated with each item of a vehicle and vehicle services, for example. In the item of the vehicle, information regarding the vehicle for which key information is generated by the key distribution server 10 is stored. In the item of the vehicle service, information regarding a service subscribed by the owner of the vehicle for which key information is generated, for example, a charging service, is stored.

[0039] In the item of the vehicle, information regarding each of vehicle ID, vehicle information, owner information, owner key information, share flag, shared user information, and shared user key information is stored. The vehicle ID is identification information for identifying the vehicle. In the vehicle information, basic information of the vehicle, such as vehicle type, vehicle name, model, and vehicle body number, is stored. In the owner information, attribute information of the owner of the vehicle, such as name, telephone number, and address, is stored. In the owner key information, key information issued for the owner to use the vehicle is stored. The share flag determines whether the owner permits (shares) the vehicle to be lent to a shared user. In the example of this figure, if the owner permits the vehicle to be lent to a shared user, 1 is set in the share flag. On the other hand, if the owner does not permit the vehicle to be lent to a shared user, 0 (zero) is set in the share flag. In the shared user information, attribute information of the shared user when the owner lends the vehicle to the shared user, such as name, telephone number, and address, is stored. In the shared user key information, key information issued for the shared user to use the vehicle is stored.

[0040] In the item of the vehicle service, information regarding service name, used application, share flag, cooperation information, billing destination, etc. is stored. In the service name, the name of the vehicle service is stored. In the used application, an application for using the vehicle service, for example, the URL of the vehicle service use application, is stored. The sharing flag determines whether the owner permits the sharing (lending) of the vehicle service to the sharing user. In the example of this figure, if the owner permits the sharing of the vehicle service to the sharing user, the sharing flag is set to 1. On the other hand, if the owner does not permit the sharing of the vehicle service to the sharing user, the sharing flag is set to 0 (zero). The linkage information stores the linkage information for realizing the shared use of the vehicle service when the sharing flag is set to 1, that is, when the owner permits the sharing (lending) of the vehicle service to the sharing user. The billing destination flag stores whether the billing destination for the shared use is the owner or the sharing user. If the owner desires the sharing user as the billing destination for the shared use, the billing destination flag is set to 1. On the other hand, if the owner desires the owner as the billing destination for the shared use, the billing flag is set to 0 (zero).

[0041] For example, when a vehicle operation app is installed on the vehicle owner terminal 20 and an account for the owner to log in to the vehicle operation app is generated, 40 pieces of vehicle information owned by the owner and owner information such as the owner's address and age are registered. Based on the registered information, information is stored in each of "Vehicle ID", "Vehicle Information", and "Owner Information" in the vehicle item of the share information storage unit 14. Also, the key distribution server 10 conducts a hearing via the vehicle operation app to determine, for example, whether to permit sharing of the vehicle 40, and based on the result of the hearing, sets 0 (zero) or 1 in the "Share Flag" in the vehicle item. Further, when the owner permits sharing of the vehicle 40, the key distribution server 10 conducts a hearing via the vehicle operation app to determine whether the vehicle 40 subscribes to available vehicle services, and based on the result of the hearing, stores information corresponding to "Service Name" and "Used App" in the vehicle service item. Also, when the owner subscribes to vehicle services for the vehicle 40, the key distribution server 10 conducts a hearing via the vehicle operation app to determine whether the vehicle 40 subscribes to available vehicle services, and based on the result of the hearing, sets 0 (zero) or 1 in the "Share Flag" in the vehicle service item. Further, when the owner permits use of vehicle services by a shared user, a hearing is conducted to determine whether the billing destination for the use of vehicle services by the shared user is the shared user or the owner, and based on the result of the hearing, 0 (zero) or 1 is set in the "Billing Destination Flag" in the vehicle service item.

[0042] When the key distribution server 10 receives a request from the vehicle owner terminal 20 to generate key information used by the owner himself / herself, it causes the sharing user information such as the name and address of the sharing user, and the period (sharing period) during which the sharing user can borrow the vehicle 40, etc. to be registered, and stores the information in the respective items of "sharing user information" and "sharing period" in the vehicle item. When the key distribution server 10 receives a request from the vehicle owner terminal 20 to generate key information used by the sharing user, it generates the key information and stores the generated key information in the "sharing user key information" in the vehicle item of the share information storage unit 14. Further, when the key distribution server 10 refers to the share information storage unit 14 and the "share flag" in the vehicle service item is set to "1", it generates cooperation information for the sharing user to use the vehicle service with "1" set, and stores it in the "cooperation information" in the vehicle service item. When the key distribution server 10 refers to the share information storage unit 14 and the "billing destination flag" in the vehicle service item is set to "1", if the settlement information is not registered by the sharing user in the cooperation information, it includes information indicating that the sharing user is not allowed to use the vehicle service, for example, includes link information for transitioning to a registration screen for registering the sharing user's settlement information in the vehicle service use application.

[0043] (Regarding the information stored in the vehicle storage unit 42) FIG. 3 is a diagram showing an example of the information stored in the vehicle storage unit 42 in the embodiment. In the vehicle storage unit 42, for example, information corresponding to each item of vehicle key information, vehicle service authentication information, and user flag is stored. In the vehicle key information, as the key information generated by the key generation unit 11, the key information for the owner to use the vehicle and the key information for the sharing user to use the vehicle are stored. In the vehicle service authentication information, as the authentication information for sharing the vehicle service, the authentication information for the owner to use the vehicle service and the authentication information for the sharing user to use the vehicle service, which are issued by the charging service membership server 50, are stored. The driver flag is information indicating whether the user of the vehicle is the owner or the sharing user. The user flag stores information indicating whether the user using the vehicle is the owner or a shared user. When the owner is using the vehicle, 0 (zero) is set in the owner item of the user flag, and 1 is set in the shared user item of the user flag. For example, when the vehicle is unlocked using the key information and is not yet locked, if the key information used to unlock the vehicle is the key information generated for the owner to use the vehicle, the vehicle control unit 41 assumes that the user using the vehicle is the owner, sets 1 in the owner item of the user flag, and sets 0 (zero) in the shared user item of the user flag. On the other hand, when the vehicle is unlocked using the key information and is not yet locked, if the key information used to unlock the vehicle is the key information generated for the shared user to use the vehicle, the vehicle control unit 41 assumes that the user using the vehicle is the shared user, sets 0 (zero) in the owner item of the user flag, and sets 1 in the shared user item of the user flag.

[0044] (Regarding the information stored in the member information storage unit 53) FIG. 4 is a diagram showing an example of information stored in the member information storage unit 53 in the embodiment. The member information storage unit 53 stores information associated with each item of, for example, a user ID, a share user flag, a charging plan, an owner's user ID, authentication information, a usage history, and settlement information. The user ID is identification information for identifying a user of the charging service (charging service member). The share user flag is information indicating whether the user of the charging service (charging service member) is an owner or a share user. The charging plan is information indicating a charging plan available to the user of the charging service (charging service member). The owner's user ID is information set when the user of the charging service (charging service member) is a share user, and indicates the user ID of the owner of the vehicle shared by the share user. The authentication information is authentication information used when using the charging service. The usage history is information indicating the usage history of the charging service. The settlement information is information indicating whether settlement has been made for the use of the charging service.

[0045] (Regarding the processing flow performed by the management system 1) Here, with reference to FIGS. 5 to 7, the processing flow performed by the management system 1 of the embodiment will be described. FIGS. 5 to 7 are sequence diagrams showing the processing flow performed by the management system 1 of the embodiment.

[0046] FIG. 5 shows the flow of each of the processes of issuing key information for the owner to use the vehicle 40 shown in step S100, issuing authentication information for the owner to use the charging service as a vehicle service shown in step S130, issuing key information for the share user to use the vehicle 40 shown in step S170, and issuing authentication information for the share user to use the charging service shown in step S210.

[0047] First, the process flow shown in step S100 will be described. The vehicle owner terminal 20 sends a notification to the key distribution server 10, requesting it to issue key information for the owner to use the vehicle 40 (step S10). In response to the request from the vehicle owner terminal 20, the key distribution server 10 generates key information for the owner to use the vehicle 40 by the key generation unit 11, and transmits the generated key information to the vehicle owner terminal 20 by the distribution unit 12 (step S11). The vehicle owner terminal 20 registers the key information received from the key distribution server 10 in the vehicle operation application. Also, the vehicle owner terminal 20 transmits the key information to the vehicle 40 and stores it in the vehicle storage unit 42 as key information for the owner to use the vehicle 40 (step S12). Here, instead of the vehicle owner terminal 20, the key distribution server 10 may transmit the key information to the vehicle 40 and store it in the vehicle storage unit 42 as key information for the owner to use the vehicle 40.

[0048] Next, the process flow shown in step S130 will be described. The vehicle owner terminal 20 sends a notification to the charging service membership server 50 via the key distribution server 10, requesting it to issue authentication information for the owner to use the charging service (step S13). Here, the vehicle owner terminal 20 may directly send a notification to the charging service membership server 50, requesting it to issue authentication information for the owner to use the charging service, without going through the key distribution server 10. In response to the request from the vehicle owner terminal 20, the charging service membership server 50 generates authentication information for the owner to use the charging service, and transmits the generated authentication information to the charging device 70 (step S14). Also, the charging service membership server 50 transmits the generated authentication information to the vehicle owner terminal 20 via the key distribution server 10 or directly (step S15). Also, the charging service membership server 50 transmits the generated authentication information to the vehicle 40 (step S16).

[0049] Next, the process flow shown in step S170 will be described. The vehicle owner terminal 20 transmits a notification to the key distribution server 10, requesting the key distribution server 10 to issue key information for the shared user to use the vehicle 40 (step S17). In response to the request from the vehicle owner terminal 20, the key distribution server 10 generates key information for the shared user to use the vehicle 40 and transmits the generated key information to the shared user terminal 30 (step S18). The shared user terminal 30 registers the key information received from the key distribution server 10 in the vehicle operation application. Further, the shared user terminal 30 transmits the key information to the vehicle 40 and stores it in the vehicle storage unit 42 as key information for the owner to use the vehicle 40 (step S19). Here, instead of the shared user terminal 30, the key distribution server 10 may transmit the key information to the vehicle 40 and store it in the vehicle storage unit 42 as key information for the shared user to use the vehicle 40. The key distribution server 10 returns a response to the vehicle owner terminal 20 indicating that the issuance of the key information for the shared user to use the vehicle 40 has been completed (step S20).

[0050] Next, the process flow shown in step S210 will be described. The vehicle owner terminal 20 transmits a notification to the charging service membership server 50 via the key distribution server 10, requesting the charging service membership server 50 to issue authentication information for the shared user to use the charging service (step S21).

[0051] For example, when the key distribution server 10 generates key information for a shared user to use the vehicle 40 in response to a request as shown in step S13 from the vehicle owner terminal 20, it refers to the share information storage unit 14 and determines whether there is a vehicle service that the owner has subscribed to. When there is a vehicle service that the owner has subscribed to, the key distribution server 10 determines whether the owner has permitted the shared use of that vehicle service, that is, whether the share flag in the vehicle service of the share information storage unit 14 is set to 1. When the share flag is set to 1, the key distribution server 10 sends a notification to the vehicle owner terminal 20 to inquire whether to permit the shared user to use the vehicle service during the period when the vehicle 40 is lent out. In response to this notification, if the owner permits the shared user to use the vehicle service, the owner sends a notification request to the key distribution server 10 via the vehicle owner terminal 20 to issue cooperation information for the shared user to use the vehicle service.

[0052] In response to a request from the shared user terminal 30, the key distribution server 10 generates cooperation information for the shared user to share and use the charging service, and sends the generated cooperation information to the shared user terminal 30 (step S22). The shared user terminal 30 uses the cooperation information received from the key distribution server 10 to transition from the vehicle operation application to the vehicle service use application, and sends a notification request to issue authentication information for shared use to the charging service member server 50 (step S23). In response to a request from the shared user terminal 30, the charging service member server 50 generates authentication information for shared use and sends the generated authentication information to the charging device 70 (step S24). Also, the charging service member server 50 sends the generated authentication information to the vehicle 40 (step S25). Here, the charging service member server 50 may send a two-dimensional code or barcode embedded with the authentication information to the shared user terminal 30.

[0053] In addition, when settlement information indicating the billing destination when a shared user uses vehicle services is set in the charging service membership server 50, the charging service membership server 50 transmits the settlement information to the settlement server 60 (step S26). Note that if the settlement information of the shared user is registered in advance in the vehicle service use application, the process shown in step S26 may be omitted. The key distribution server 10 returns a response to the vehicle owner terminal 20 indicating that the issuance of authentication information for shared use has been completed (step S27).

[0054] FIG. 6 shows the respective flows of the process of unlocking the vehicle 40 shown in step S280 and the process of using vehicle services shown in step S350.

[0055] First, the flow of the process shown in step S280 will be described. Here, a method in which a shared user operates the shared user terminal 30 to unlock the vehicle 40 will be described, but it can also be applied when the owner operates the vehicle owner terminal 20 to unlock the vehicle 40.

[0056] The shared user terminal 30 transmits an operation signal requesting to unlock the door of the vehicle 40 to the vehicle control unit 41 (step S28). The operation signal includes key information for the shared user to use the vehicle 40, which is generated by the key distribution server 10 and transmitted to the shared user terminal 30. The vehicle control unit 41 refers to the vehicle storage unit 42 to acquire key information for user authentication (steps S29, S30). The key information for user authentication is the key information for the shared user to use the vehicle 40, which is generated by the key distribution server 10 and transmitted to the vehicle 40.

[0057] The vehicle control unit 41 performs authentication. The authentication here only needs to use at least key information as encryption information. For example, if the encryption information is information such as an electronic certificate for mutual authentication or one-way authentication, the vehicle control unit 41 uses the information (encryption information) such as the electronic certificate as authentication to perform mutual authentication or one-way authentication between the shared user terminal 30 and the vehicle 40. If the encryption information is a common key used for encrypted communication, the vehicle control unit 41 decrypts the information (for example, an operation signal for unlocking the door) notified from the shared user terminal 30 using the common key (encryption information) as authentication. If the encryption information is a password, the vehicle control unit 41 compares the password notified from the shared user terminal 30 with the previously notified password (encryption information).

[0058] Here, in step S25, when a two-dimensional code or barcode embedded with authentication information is transmitted to the shared user terminal 30, the charging device 70 may be made to start using the charging device 70 by having the charging device 70 read the two-dimensional code or barcode embedded with the authentication information. In this case, the processes shown in steps S36 to S41 are omitted. Also, in this case, the charging device 70 is provided with a reading device (for example, a scanner). The shared user causes the shared user terminal 30 to display a display screen that displays the authentication information in the vehicle service use application. A two-dimensional code or barcode embedded with the authentication information is displayed on the display screen. The shared user holds the display screen in front of the reading part of the reading device or the like to cause the reading device to read the authentication information. When the charging device 70 reads the authentication information via the reading device, the charging device 70 executes the process shown in step S42.

[0059] When the vehicle control unit 41 determines that the authentication is successful (authentication OK) as a result of the authentication, it determines to follow the operation signal, that is, to unlock the door (step S31). For example, if the encryption information is information used for mutual authentication, the vehicle control unit 41 determines that the authentication is OK when it can mutually determine that both devices are legitimate devices as a result of the mutual authentication. If the encryption information is information used for one-way authentication, the vehicle control unit 41 determines that the authentication is OK when it is determined by the authenticating device that the authenticated device is a legitimate device as a result of the one-way authentication. If the encryption information is a common key, the vehicle control unit 41 determines that the authentication is OK when the operation signal notified from the shared user terminal 30 can be correctly decrypted using the common key. If the encryption information is a password, the vehicle control unit 41 determines that the authentication is OK when the password notified from the shared user terminal 30 matches the previously notified password (encryption information).

[0060] When the vehicle control unit 41 determines that the authentication is successful (authentication OK) as a result of the authentication, it updates the "user flag" in the vehicle storage unit 42 (step S32). If the key information used for authentication is the key information for the shared user to use the vehicle, the vehicle control unit 41 sets a flag indicating that the user is a shared user in the user flag. On the other hand, if the key information used for authentication is the key information for the owner to use the vehicle, the vehicle control unit 41 sets a flag indicating that the user is the owner in the user flag.

[0061] When the vehicle control unit 41 unlocks the door of the vehicle 40 in step S31, it may send a notification to the vehicle owner terminal 20 reporting that the sharing of the vehicle 40 has started (step S33). When the shared user unlocks the door of the vehicle 40, the shared user gets into the vehicle 40 and starts the engine of the vehicle 40 (step S34). For example, the shared user terminal 30 sends an operation signal requesting to start the engine of the vehicle 40 to the vehicle control unit 41, and the vehicle 40 performs authentication in the same way as when the door is unlocked, and starts the engine when the authentication is successful.

[0062] Next, the process flow shown in step S350 will be described. The shared user stops the vehicle 40 beside the charging device 70 and stops the engine in order to supply power to the vehicle 40 (step S35). The vehicle control unit 41 transmits a usage start request indicating a request to charge the vehicle 40 using the charging device 70 to the charging device 70 (step S36). For example, the charging device 70 is provided with a charging port as an outlet to which the charging plug of the vehicle is connected. When the shared user connects the charging plug of the vehicle to the charging port of the charging device 70 and operates the operation panel provided on the charging device 70 to press the usage start button, a usage start request is transmitted from the vehicle 40 to the charging device 70. Alternatively, it may be configured such that when the shared user connects the charging plug of the vehicle to the charging port of the charging device 70, a usage start request is transmitted from the vehicle 40 to the charging device 70.

[0063] The charging device 70 makes an authentication request to the vehicle 40 (step S37) and requests that authentication information be transmitted to the charging device 70. The vehicle control unit 41 refers to the vehicle storage unit 42 to obtain the user flag and obtain the authentication information corresponding to the user using the vehicle (here, the shared user) (steps S38, S39, S40). The vehicle 40 transmits the authentication information to the charging device 70 (step S41). The charging device 70 performs authentication based on the authentication information received from the vehicle 40 and makes an inquiry regarding settlement to the settlement server 60 (step S42). The authentication here can adopt the same method as the authentication performed when unlocking the door of the vehicle 40. Also, the inquiry to the settlement server 60 here is, for example, an inquiry as to whether the settlement information registered by the user of the charging service (here, the shared user) is valid.

[0064] When there is settlement information registered as the billing destination for the shared user), and the settlement information is valid, for example, when the credit card has not been suspended and the expiration date has not passed, it is determined that the settlement information is valid, and the determination result is transmitted to the charging device 70 as the answer to the inquiry in step S42 (step S43). When the result of authentication using the authentication information received from the vehicle 40 in step S41 is authentication OK, and the answer received from the settlement server 60 in step S43 indicates that the settlement information is valid, the charging device 70 determines to start power supply to the vehicle 40 (step S44). On the other hand, when the result of authentication using the authentication information received from the vehicle 40 in step S41 is not authentication OK, or when the answer received from the settlement server 60 in step S43 does not indicate that the settlement information is valid, the charging device 70 determines not to start power supply to the vehicle 40. When the charging device 70 determines to start power supply to the vehicle 40, it transmits a signal indicating the start of power supply to the vehicle 40 (step S45) and starts power supply to the vehicle 40.

[0065] Figure 7 shows the respective flows of the process of performing settlement for the charging service shown in step S460 and the process of locking the vehicle door shown in step S540.

[0066] First, the process flow shown in step S460 will be described. When the power supply to the vehicle 40 is completed, the charging device 70 transmits a signal indicating the completion of power supply to the vehicle 40 (step S46). When the vehicle 40 receives the signal indicating the completion of power supply from the charging device 70, it starts the engine (step S47). When the power supply is completed, the shared user inserts and removes the charging plug of the vehicle to disconnect the connection between the charging plug and the charging port of the charging device 70. The charging device 70 transmits the charging fee to the settlement server 60 (step S48). The settlement server 60 generates billing information indicating a claim based on the charging fee received from the charging device 70, transmits the generated billing information to the charging service member server 50 (step S49), and transmits the billing information to the shared user terminal 30 via the charging service member server 50 (step S50). Here, the settlement server 60 may directly transmit the billing information to the shared user terminal 30 without going through the charging service member server 50.

[0067] When the shared user terminal 30 receives the billing information generated by the settlement server 60 via the charging service member server 50 or directly, it settles the received billing information, and for example, transmits to the settlement server 60 a notice indicating that a transfer or remittance procedure has been performed (step S51). When the settlement server 60 receives the notice indicating that a transfer or remittance procedure has been performed from the shared user terminal 30, it transmits a notice indicating that the settlement has been completed to the charging service member server 50 (step S52). Here, the charging service member server 50 may transmit the usage status of shared use in the charging service to the vehicle owner terminal 20 (step S53).

[0068] Next, the process flow shown in step S540 will be described. The shared user parks the vehicle 40 at a parking station for return or the like and stops the engine (step S54). The shared user gets out of the vehicle 40 and transmits an operation signal requesting to lock the door of the vehicle 40 to the vehicle control unit 41 (step S55). The operation signal includes the key information generated by the key distribution server 10 and transmitted to the shared user terminal 30 for the shared user to use the vehicle 40. The vehicle control unit 41 refers to the vehicle storage unit 42 and acquires the key information for user authentication (steps S56, S57). The key information for user authentication is the key information generated by the key distribution server 10 and transmitted to the vehicle 40 for the shared user to use the vehicle 40. The vehicle control unit 41 performs authentication. The vehicle control unit 41 performs authentication in the same manner as the authentication performed when unlocking the door of the vehicle 40, and locks the door when the authentication is successful (step S58). When the vehicle control unit 41 locks the door, it discards the key information (the key information for the shared user to use the vehicle) and the authentication information (the authentication information for the shared user to use the charging service) stored in the vehicle storage unit 42 (step S59). When the vehicle control unit 41 discards the key information and the authentication information, it transmits a message indicating that the sharing (use of the vehicle 40 by the shared user) is completed to the key distribution server 10 (step S60). The key distribution server 10 transmits a message indicating that the sharing is completed to the vehicle owner terminal 20 (step S61).

[0069] Note that the vehicle control unit 41 may not execute step S59 when the date and time when the door is locked in step S58 is within the usage period during which the owner has permitted the shared user to use the vehicle 40. In this case, the vehicle control unit 41 executes step S59 when the current date and time has passed the usage period during which the owner has permitted the shared user to use the vehicle 40.

[0070] As described above, the management system 1 of the embodiment is a management system that manages the lending of the vehicle 40 owned by an individual owner to share users. The management system 1 includes a share information storage unit 14, a key generation unit 11, a service cooperation unit 13, and a distribution unit 12. The share information storage unit 14 stores a vehicle service (a specific service related to the vehicle 40) to which the owner subscribes. The key generation unit 11 generates key information for the share user to use the vehicle 40 in response to a use request for allowing the share user to use the vehicle. The service cooperation unit 13 generates cooperation information for the share user to use the vehicle service in response to a use request for allowing the share user to use the vehicle 40. The distribution unit 12 distributes the key information and the cooperation information. For example, the distribution unit 12 transmits the key information and the cooperation information to the share user terminal 30. The distribution unit 12 transmits the key information to the share user terminal 30 and the vehicle 40. Thereby, in the management system 1 of the embodiment, when a share user shares a vehicle, it can be made to cooperate with a vehicle service. For example, during the period when a share user borrows a vehicle, the share user can use the vehicle service to which the owner subscribes. Therefore, the convenience of share users can be improved in the personal car sharing service.

[0071] In the management system 1 of the embodiment, operations of the vehicle are executed from an operation terminal (vehicle owner terminal 20 or shared user terminal 30) using a vehicle operation app. The vehicle operation app is an application program for operating the vehicle 40 and can be used by installing it on the vehicle owner terminal 20 and the shared user terminal 30. Also, using a vehicle service usage app, the usage of vehicle services is executed from the operation terminal. The vehicle service usage app is an application program for using vehicle services and can be used by installing it on the vehicle owner terminal 20 and the shared user terminal 30. The service cooperation unit 13 generates, as cooperation information, information for cooperating the vehicle operation app and the vehicle service usage app via an API or the like. The service cooperation unit 13 generates, as cooperation information, information including link information for the shared user to transition to a page for using vehicle services in the vehicle service usage app from the vehicle operation app. Thereby, in the management system 1 of the embodiment, it becomes possible to notify the shared user that sharing is possible and to smoothly acquire information necessary for registration when wishing to use sharing. For this reason, the procedures when the shared user uses sharing can be smoothly advanced, and the convenience of the shared user can be improved.

[0072] In addition, in the management system 1 of the embodiment, the shared information storage unit 14 stores a billing destination flag. The billing destination flag is information indicating whether the billing destination when the shared user uses the vehicle service is the owner or the shared user. When generating the cooperation information, the service cooperation unit 13 acquires the billing destination flag from the shared information storage unit 14. When "1" is set in the acquired billing destination flag, that is, when it is set that the billing destination is the shared user, the service cooperation unit 13 generates information including link information for transitioning to a registration page for registering settlement information in the vehicle service use application as the cooperation information. The settlement information is information indicating the billing destination when billing the shared user, and includes, for example, information for specifying the credit card of the shared user. In the management system 1, when the settlement information of the shared user is not registered in the vehicle service use application, the shared user is prevented from using the vehicle service. Thereby, in the management system 1 of the embodiment, when the owner sets the billing destination of the shared use as the shared user, if the shared user does not register the settlement information, the shared user can be prevented from using the vehicle service, and troubles such as the shared user being billed to the owner when the shared user uses the shared use can be avoided, and the convenience of the shared user can be improved.

[0073] The management system 1 and all or part of the key distribution server 10 in the above-described embodiment may be realized by a computer. In that case, a program for realizing this function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read into a computer system and executed to realize it. Here, the “computer system” shall include hardware such as an OS and peripheral devices. Further, the “computer-readable recording medium” refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, etc., and a storage device such as a hard disk built into a computer system. Furthermore, the “computer-readable recording medium” also includes, like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, a medium that dynamically holds a program for a short time, and a volatile memory inside a computer system that becomes a server or a client in that case, which holds a program for a certain period of time. Also, the above program may be for realizing a part of the aforementioned functions, and may further be realized in combination with a program already recorded in the computer system for the aforementioned functions, and may also be realized using a programmable logic device such as an FPGA.

[0074] As described above, the embodiments of the present invention have been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and designs and the like within the scope not departing from the gist of the present invention are also included.

[0075] For example, in the above embodiment, the charging service was exemplified and described as a vehicle service, but it is not limited to this. When the vehicle 40 is a gasoline vehicle, instead of the charging service, a refueling service may be applied as the vehicle service in this embodiment. Also, various services related to the vehicle, such as car washing, tire replacement, battery replacement, maintenance, tow truck movement, and other various services may be applied as the vehicle service in this embodiment.

Explanation of Reference Numerals

[0076] 1… Management system 10… Key distribution server 11… Key generation unit 12… Distribution unit 13… Service cooperation unit 20… Vehicle owner terminal 30… Shared user terminal 40… Vehicle 42… Vehicle memory unit 50… Charging service membership server 60… Settlement server

Claims

1. A management system for managing the lending of a vehicle owned by an individual owner to a shared user, comprising: a shared information storage unit that stores specific services related to the vehicle to which the owner subscribes; a key generation unit that generates key information for the shared user to use the vehicle in response to a use request for the shared user to use the vehicle; a service cooperation unit that generates cooperation information for the shared user to use the specific service in response to a use request for the shared user to use the vehicle; a distribution unit that distributes the key information and the cooperation information; A management system comprising:

2. Using a vehicle operation application, which is an application program for operating the vehicle, the operation of the vehicle is executed from an operation terminal. Using a vehicle service use application, which is an application program for using the specific service, the use of the specific service is executed from an operation terminal. The service cooperation unit generates, as the cooperation information, information including link information for transitioning to a page for the shared user to use the specific service in the vehicle service use application from the vehicle operation application. The management system according to Claim 1.

3. The shared information storage unit stores a billing destination flag indicating whether the billing destination when the shared user uses the specific service is the owner or the shared user. When generating the cooperation information, the service cooperation unit acquires the billing destination flag from the shared information storage unit. If it is set that the billing destination is the shared user in the acquired billing destination flag, as the cooperation information, information including link information for transitioning to a registration page for registering settlement information indicating the billing destination in the vehicle service use application is generated. If the settlement information is not registered in the vehicle service use application, the shared user is prevented from using the specific service. The management system according to Claim 2.

4. A management method performed by a computer comprising a shared information storage unit that stores specific services related to a vehicle to which an individual owner subscribes, the management method being used in a management system for managing the lending of a vehicle owned by an individual owner to a shared user, the method comprising: generating key information for the shared user to use the vehicle in response to a use request for the shared user to use the vehicle; In response to a usage request for allowing the shared user to use the vehicle, generate cooperation information for the shared user to use the specific service, distribute the key information and the cooperation information, management method.

Images