Share car management server, share car management program, and share car management method

Abstract

The goal is to improve vehicle utilization rates while minimizing restrictions on vehicle use by primary users. [Solution] The server obtains a reference calendar in which either a first specific day or a second specific day is specified. Based on the reference calendar, the server generates a first calendar in which the first specific day is a day when the vehicle can be used by the first user. Based on the reference calendar, the server generates a second calendar in which the second specific day is a day when the vehicle can be used by the second user. When the server receives a request for reservation management information from the personal terminal by the first user, it sends the first calendar to the personal terminal (S54). When the server receives a request for reservation management information from the personal terminal by the second user, it sends the second calendar to the personal terminal (S54). The server accepts reservations for vehicle use from the personal terminal for a date and time selected from either the first calendar or the second calendar (S56, S57).

Description

Technical Field

[0001] The present invention relates to a car-sharing management server, a car-sharing management program, and a car-sharing management method.

Background Art

[0002] The car-sharing management system of Patent Document 1 includes a vehicle, a personal terminal, and a management server. The vehicle is provided for a car-sharing service. That is, the vehicle is shared by users who use the car-sharing service. The personal terminal is a terminal operated by a user of the car-sharing service. The management server can communicate with the personal terminal. The management server accepts a reservation for using the vehicle from the personal terminal. As a result, the user of the car-sharing service can use the reserved vehicle.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] As a vehicle provided for a car-sharing service such as that of Patent Document 1, for example, a business vehicle managed by a company can be used. In this case, an improvement in the utilization rate of the business vehicle managed by the company can be expected. However, in the above configuration, for example, due to the use of the vehicle by a general user who does not belong to the company among the users of the car-sharing service, the use of the vehicle by a corporate user who belongs to the company may be restricted. Here, although the use of the vehicle by corporate users and general users has been described as an example, it is not limited to the above example, and it is not preferable that the use of the vehicle by a user who belongs to a specific group is restricted due to the use of the vehicle by a user who does not belong to the specific group. [Means for solving the problem]

[0005] To solve the above problem, the shared car management server is capable of communicating with a personal terminal (300) operated by a user for a car-sharing service targeting vehicles managed by a vehicle provider, and when a user belonging to a specific group is designated as the first user and a user not belonging to the specific group is designated as the second user, the server performs the following processes: (S32) acquiring a predetermined standard calendar (CS) on a daily or hourly basis for either the first specific day or the second specific day; (S33) generating a first calendar (C1) based on the standard calendar, in which at least the first specific days included in the standard calendar are designated as days on which the vehicle can be used by the first user; and (S33) generating the standard calendar based on the standard calendar The process (S34) is performed to generate a second calendar (C2) in which the second specific date included in the first calendar is set as a date on which the vehicle can be used by the second user; when a request for reservation management information is received from the personal terminal, the process (S53) is performed to determine whether the request is from the first user or the second user; if it is determined to be a request from the first user, the process (S54) is performed to send the first calendar to the personal terminal; if it is determined to be a request from the second user, the process (S54) is performed to send the second calendar to the personal terminal; and the process (S56, S57) is performed to receive a reservation from the personal terminal for the date and time of use of the vehicle selected from either the first calendar or the second calendar.

[0006] The shared car management program for solving the above problem is applied to a shared car management server that can communicate with a personal terminal operated by a user for a car sharing service targeting vehicles managed by a vehicle provider. When a user belonging to a specific group is designated as the first user and a user not belonging to the specific group is designated as the second user, the shared car management server performs the following processes: acquiring a standard calendar in which either the first specific day or the second specific day is predetermined on a daily or hourly basis; generating a first calendar based on the standard calendar in which at least the first specific day included in the standard calendar is designated as a day on which the vehicle can be used by the first user; and the standard The system is configured to perform the following processes: generate a second calendar based on the calendar, where the second specific date included in the standard calendar is designated as a date on which the vehicle can be used by the second user; determine whether the request for reservation management information from the personal terminal is from the first user or the second user; send the first calendar to the personal terminal if it is determined to be a request from the first user; send the second calendar to the personal terminal if it is determined to be a request from the second user; and accept a reservation from the personal terminal for the use of the vehicle on a date and time selected from either the first or second calendar.

[0007] A car-sharing management method for solving the above problems is applied to a car-sharing management server that can communicate with a personal terminal operated by a user for a car-sharing service targeting vehicles managed by a vehicle provider. When a user belonging to a specific group is designated as the first user and a user not belonging to the specific group is designated as the second user, the car-sharing management server performs the following processes: acquiring a predetermined standard calendar in which either the first specific day or the second specific day is determined on a daily or hourly basis; generating a first calendar based on the standard calendar in which at least the first specific day included in the standard calendar is designated as a day on which the vehicle can be used by the first user; and the standard Based on the render, the system performs the following processes: generating a second calendar in which the second specific date included in the standard calendar is set as the date on which the vehicle can be used by the second user; determining whether the request for reservation management information is from the first user or the second user when a request for reservation management information is received from the personal terminal; sending the first calendar to the personal terminal if it is determined to be a request from the first user; sending the second calendar to the personal terminal if it is determined to be a request from the second user; and receiving a reservation from the personal terminal for the date and time selected from either the first calendar or the second calendar to use the vehicle.

[0008] With the above configuration, the second user can use the vehicle for a date and time selected from the second calendar, i.e., a date and time selected from the second specified date. This prevents the first user's vehicle use from being restricted on the first specified date due to the second user's use of the vehicle. As a result, the vehicle utilization rate can be improved by allowing the second user to use the vehicle while suppressing restrictions on the first user's vehicle use. [Brief explanation of the drawing]

[0009] [Figure 1] Figure 1 is a schematic diagram of the shared car management system. [Figure 2] Figure 2 is a sequence diagram showing the registration control process. [Figure 3] Figure 3 is a sequence diagram showing the generation control. [Figure 4] Figure 4 is a sequence diagram showing reservation control. [Modes for carrying out the invention]

[0010] <Outline of the shared car management system> Embodiments of the present invention will be described below with reference to Figures 1 to 4. First, the general configuration of the shared car management system MS will be described. The shared car management system MS is a system for providing a car-sharing service for vehicles managed by a vehicle provider. Here, an example of a vehicle provider is a predetermined company K. An example of a vehicle managed by a vehicle provider is a commercial vehicle managed by company K. In this embodiment, the vehicle provider provides multiple vehicles to be used for the sharing service.

[0011] As shown in Figure 1, the car share management system MS includes a corporate terminal 100. An example of the corporate terminal 100 is a personal computer owned by company K. The corporate terminal 100 includes an execution device 110, a storage device 120, and a communication device 130. The communication device 130 can communicate with devices outside the corporate terminal 100 via a communication network NW. An example of the execution device 110 is a CPU. The storage device 120 includes a read-only ROM, a read and write volatile RAM, and a read and write non-volatile storage. The storage device 120 pre-stores various programs and various data. Specifically, the storage device 120 pre-stores a control program 121 as one of the various programs. The execution device 110 executes various processes described later by executing the control program 121. The storage device 120 can also store a reference calendar CS as one of the various data. The reference calendar CS is stored in the storage device 120 after being created, for example, by an employee of company K. The standard calendar CS is one in which either working days or non-working days for company K are predetermined for each day. Here, an example of a working day for company K is Monday, Tuesday, Wednesday, Thursday, and Friday. An example of a non-working day for company K is Saturday and Sunday. In this embodiment, a working day for company K is an example of a first specified day. A non-working day for company K is an example of a second specified day. Working days may also be referred to as business days, and non-working days may also be referred to as non-business days.

[0012] As shown in Figure 1, the car-sharing management system MS includes a server 200. The server 200 includes an execution unit 210, a storage device 220, and a communication device 230. The communication device 230 can communicate with devices outside the server 200 via a communication network NW. Therefore, the server 200 can communicate with the corporate terminal 100. The server 200 can also communicate with the personal terminal 300, which will be described later.

[0013] The storage device 220 includes a read-only ROM, a read-and-write volatile RAM, and a read-and-write non-volatile storage. The storage device 220 pre-stores various programs and various data. Specifically, the storage device 220 pre-stores a control program 221 as one of the various programs. An example of the execution device 210 is a CPU. The execution device 210 executes various processes described later by executing the control program 221. In this embodiment, the control program 221 is an example of a shared car management program. Furthermore, the execution device 210 executes various processes related to the shared car management method by executing the control program 221. In addition, the server 200 is an example of a shared car management server.

[0014] As shown in Figure 1, the car-sharing management system MS is equipped with multiple personal terminals 300. In this embodiment, the personal terminals 300 are terminals operated by users of the car-sharing service. Here, an example of a personal terminal 300 is a so-called smartphone. Note that in Figure 1, only one personal terminal 300 is shown as a representative example.

[0015] The personal terminal 300 includes an execution device 310, a storage device 320, a communication device 330, and a display 340. The communication device 330 can communicate with devices outside the personal terminal 300 via the communication network NW. An example of the execution device 310 is a CPU. The storage device 320 includes a read-only ROM, a read and write volatile RAM, and a read and write non-volatile storage. The storage device 320 pre-stores various programs and various data. Specifically, the storage device 320 pre-stores a control program 321 as one of the various programs. The execution device 310 executes various processes described later by executing the control program 321.

[0016] The display 340 can display various types of information. The display 340 is a so-called touch panel display. Therefore, the user of the personal terminal 300 can input various types of information via the display 340. That is, the display 340 functions as both an output device that outputs information to the user and an input device that receives information from the user.

[0017] <Registration control> Next, referring to FIG. 2, the registration control executed by the server 200 and the personal terminal 300 will be described. This registration control is control regarding the registration of a user for using a car-sharing service. Note that the registration control is executed by the cooperation of each of the plurality of personal terminals 300 and the server 200. In the present embodiment, when the execution device 310 of the personal terminal 300 starts an operation for a user of the personal terminal 300 to perform registration via the display 340, the registration control is started.

[0018] As shown in FIG. 2, when the execution device 310 of the personal terminal 300 starts the registration control, it executes the process of step S11. In step S11, the execution device 310 receives an input of necessary information, which is information necessary for registration by the user of the personal terminal 300. Here, the necessary information includes, for example, information on the user name, information on whether the user belongs to company K, and the like. Note that the user of the personal terminal 300 can input the necessary information via the display 340. When the execution device 310 acquires the necessary information input by the user of the personal terminal 300, the execution device 310 advances the process to step S12.

[0019] In step S12, the execution device 310 of the personal terminal 300 transmits a request signal for requesting registration and the necessary information of step S11 to the server 200. When the server 200 receives the request signal and the necessary information, the execution device 210 of the server 200 advances the process to step S13.

[0020] In step S13, the execution device 210 of the server 200 executes user registration. Specifically, based on the necessary information of the user received in step S12, the execution device 210 generates ID information for the user to use the car-sharing service. Then, the execution device 210 stores the generated ID information in the storage device 220. At this time, the execution device 210 stores the ID information and the necessary information in step S11 in the storage device 220 in association with each other. Therefore, the execution device 210 can determine whether the user targeted by the ID information belongs to company K based on the ID information. In other words, the execution device 210 can determine whether the user targeted by the ID information is a corporate user belonging to company K or a general user not belonging to company K based on the ID information. Note that an example of the ID information is a number of a dozen or so digits. In this embodiment, company K is an example of a specific group. Also, corporate users are an example of the first user. Furthermore, general users are an example of the second user. After step S13, the execution device 210 advances the process to step S14.

[0021] In step S14, the execution device 210 of the server 200 transmits the ID information generated in step S13 to the personal terminal 300. When the personal terminal 300 receives the ID information, the execution device 310 of the personal terminal 300 outputs a control signal to the display 340 to display the ID information on the display 340. As a result, the user of the personal terminal 300 can grasp the ID information by visually recognizing the image displayed on the display 340. After step S14, the execution device 310 of the personal terminal 300 ends the current registration control.

[0022] <Generation Control> Next, with reference to Figure 3, the generation control performed by the corporate terminal 100 and the server 200 will be described. This generation control is for generating a first calendar C1 used by corporate users when making vehicle reservations, and a second calendar C2 used by general users when making vehicle reservations. In this embodiment, the execution device 110 of the corporate terminal 100 starts generation control when an employee of company K requests generation control via an input device such as a keyboard connected to the corporate terminal 100. For example, an employee of company K may request generation control when they create a new standard calendar CS.

[0023] As shown in Figure 3, when the execution device 210 of the server 200 starts generation control, it executes the process in step S32. In step S32, the execution device 110 of the enterprise terminal 100 sends a reference calendar CS to the server 200. When the server 200 receives the reference calendar CS, the execution device 210 of the server 200 proceeds to step S33. In this embodiment, the process in step S32 is an example of the process of acquiring a reference calendar CS.

[0024] In step S33, the execution device 210 of the server 200 generates a first calendar C1 based on a reference calendar CS, in which the working days of company K included in the reference calendar CS are the days on which company users can use their vehicles. As described above, in this embodiment, the working days of company K are Monday, Tuesday, Wednesday, Thursday, and Friday. Therefore, the available days in the first calendar C1 are Monday, Tuesday, Wednesday, Thursday, and Friday. In this embodiment, the processing in step S33 is an example of the process of generating the first calendar C1. After step S33, the execution device 210 proceeds to step S34.

[0025] In step S34, the execution device 210 of the server 200 generates a second calendar C2 based on the reference calendar CS, in which the non-working days of company K included in the reference calendar CS are the days on which vehicles can be used by general users. As described above, the non-working days of company K are Saturday and Sunday. Therefore, the available days in the second calendar C2 are Saturday and Sunday. In this embodiment, the processing in step S34 is an example of the process for generating the second calendar C2. After step S34, the execution device 210 terminates the generation control for this time.

[0026] <Reservation Control> Next, with reference to Figure 4, the reservation control performed by the server 200 and the personal terminal 300 will be described. This reservation control is for corporate users and general users to make vehicle reservations. The reservation control is performed by the cooperation of each of the multiple personal terminals 300 and the server 200. In this embodiment, the execution device 310 of the personal terminal 300 starts the reservation control each time the user of the personal terminal 300 starts an operation to make a reservation via the display 340.

[0027] As shown in Figure 4, when the execution device 310 of the personal terminal 300 starts reservation control, it executes the process in step S51. In step S51, the execution device 310 accepts the input of ID information obtained by the user through registration control. When the execution device 310 has acquired the ID information entered by the user of the personal terminal 300, the execution device 310 proceeds to step S52.

[0028] In step S52, the execution device 310 of the personal terminal 300 sends a request signal to the server 200 to request reservation management information, and the ID information from step S51. When the server 200 receives the request signal and the ID information, the execution device 210 of the server 200 proceeds to step S53.

[0029] In step S53, the execution device 210 of the server 200 determines, based on the ID information, whether the user targeted by the ID information is a corporate user belonging to company K or a general user not belonging to company K. In this embodiment, the processing in step S53 is one example of determining whether the request for reservation management information from the personal terminal 300 is from the first user or the second user. After step S53, the execution device 210 proceeds to step S54.

[0030] In step S54, the execution device 210 of the server 200 sends either the first calendar C1 or the second calendar C2 as reservation management information to the personal terminal 300. Specifically, if the execution device 210 determines in step S53 that the request is from a corporate user, it sends the first calendar C1 to the personal terminal 300. If the execution device 210 determines in step S53 that the request is from a general user, it sends the second calendar C2 to the personal terminal 300. When the personal terminal 300 receives either the first calendar C1 or the second calendar C2, the execution device 310 of the personal terminal 300 proceeds to step S55.

[0031] In step S55, the execution device 310 of the personal terminal 300 generates reservation request information to request a reservation for the use of a vehicle. Specifically, based on one of the first calendar C1 and the second calendar C2 received in step S54, the execution device 310 displays on the display 340 the date and time when the user can use each vehicle. Subsequently, the execution device 310 receives user operations on the personal terminal 300 via the display 340. Then, the execution device 310 generates reservation request information in response to the received operations. For example, the reservation request information includes information indicating one vehicle selected by the user from among multiple vehicles, and information indicating the planned date and time when the user will use that vehicle. After step S55, the execution device 310 proceeds to step S56.

[0032] In step S56, the execution device 310 of the personal terminal 300 sends the reservation request information generated in step S55 to the server 200. When the server 200 receives the reservation request information, the execution device 210 of the server 200 proceeds to step S57.

[0033] In step S57, the execution device 210 of the server 200 updates the reservation management information based on the reservation request information. Specifically, if the server 200's execution device 210 transmits the first calendar C1 in step S54, it updates the first calendar C1 in step S57. At this time, the execution device 210 stores in the storage device 220 information as information for the first calendar C1 regarding the vehicle selected by the corporate user for the date and time selected by the corporate user. Also, if the server 200's execution device 210 transmits the second calendar C2 in step S54, it updates the second calendar C2 in step S57. At this time, the execution device 210 stores in the storage device 220 information as information for the second calendar C2 regarding the vehicle selected by the general user for the date and time selected by the general user. In this embodiment, the processing in steps S56 and S57 is an example of the process of receiving a reservation for the use of a vehicle for a date and time selected from either the first calendar C1 or the second calendar C2 from the personal terminal 300. After step S57, the execution device 210 of the server 200 terminates the current reservation control.

[0034] <Operation of this embodiment> As shown in Figure 4, the server 200 and the personal terminal 300 perform reservation control. In step S53, the execution device 210 of the server 200 determines, based on the ID information, whether the user targeted by the ID information is a corporate user belonging to company K or a general user not belonging to company K.

[0035] In step S54, if the execution device 210 of the server 200 determines in step S53 that the request is from a corporate user, it sends the first calendar C1 to the personal terminal 300. In this case, in step S55, the user of the personal terminal 300 can reserve the use of a vehicle for a date and time selected from the first calendar C1. That is, a corporate user can reserve a date and time to use a vehicle from among the working days of company K included in the first calendar C1.

[0036] On the other hand, in step S54, if the execution device 210 of the server 200 determines in step S53 that the request is from a general user, it sends the second calendar C2 to the personal terminal 300. In this case, in step S55, the user of the personal terminal 300 can reserve the use of the vehicle for a date and time selected from the second calendar C2. That is, a general user can reserve a date and time to use the vehicle from among the non-working days of company K included in the second calendar C2.

[0037] <Effects of this embodiment> (1) In this embodiment, general users can use the vehicle on dates and times selected from the second calendar C2, i.e., on dates and times selected from the non-working days of company K. On the other hand, general users cannot use the vehicle on dates and times not included in the second calendar C2, i.e., on dates and times selected from the working days of company K. This prevents restrictions on vehicle use by company users on company K's working days due to vehicle use by general users. As a result, the vehicle utilization rate can be improved by allowing general users to use the vehicle while preventing restrictions on vehicle use by company users. In other words, the vehicle utilization rate can be improved by allowing second users who do not belong to a specific group to use the vehicle while preventing restrictions on vehicle use by first users who belong to a specific group.

[0038] (2) Generally, on a business day of company K, there is a high probability that corporate users belonging to company K will request the use of a vehicle. In this embodiment, the specific group is company K. Furthermore, the first specific day predetermined in the standard calendar CS is a business day of company K. Furthermore, the second specific day predetermined in the standard calendar CS is a non-business day of company K. Therefore, it is possible to suppress the restriction of vehicle use by corporate users on a business day of company K, that is, in situations where corporate users are likely to request the use of a vehicle, due to vehicle use by general users not belonging to company K.

[0039] <Example of changes> This embodiment can be implemented with the following modifications. This embodiment and the following modifications can be combined with each other to the extent that they do not contradict each other technically.

[0040] In the above embodiment, the vehicle provider may be changed. For example, the vehicle provider is not limited to company K. Specifically, the vehicle provider could be a different company from company K, or an individual who owns the vehicle. Furthermore, the vehicle provider could be different from a specific group.

[0041] In the above embodiment, the specific group may be changed. For example, the specified group is not limited to company K. Specifically, the specified group could be a department within company K, or an organization separate from company K. Furthermore, for example, the specified group could be different from the vehicle provider.

[0042] In the above embodiment, the reference calendar CS may be changed. For example, the first specified day does not have to be any of the working days of company K, but may be any of the working days of company K. As a specific example, suppose company K's working days are Monday, Tuesday, Wednesday, Thursday, and Friday, and the frequency of vehicle use by company users is low on Wednesday. In this case, the first specified day may be Monday, Tuesday, Thursday, and Friday, excluding Wednesday from company K's working days. In the above case, the second specified day would be Wednesday, Saturday, and Sunday.

[0043] For example, the working days and non-working days of company K may be changed. Specifically, the working days of company K may be Saturday and Sunday. Similarly, the non-working days of company K may be Monday, Tuesday, Wednesday, Thursday, and Friday.

[0044] For example, the first and second specified days may be predetermined hourly in the standard calendar CS. In other words, the term "day" in the first and second specified days is merely a convenient expression and does not necessarily have to be a 24-hour period with midnight as the boundary. For example, the period from 8 AM to 8 PM on that day may be designated as the "first specified day," and the period from 8 PM to 8 AM the following day may be designated as the "second specified day."

[0045] In the above embodiment, the process by which the server 200 obtains the reference calendar CS may be modified. For example, suppose a device other than the enterprise terminal 100 stores the reference calendar CS. In this case, in step S32 of the generation control, the execution device 210 of the server 200 only needs to obtain the reference calendar CS from the other device mentioned above. Note that the other device mentioned above may be a device other than the server 200, or it may be an internal storage area of ​​the server 200.

[0046] In the above embodiment, the process by which the server 200 generates the first calendar C1 may be modified. For example, in step S33 of the generation control, the execution device 210 of the server 200 may generate a first calendar C1 based on a reference calendar CS, in which the working days and non-working days of company K included in the reference calendar CS are the days on which company users can use vehicles. In other words, the execution device 210 of the server 200 may generate a first calendar C1 based on a reference calendar CS, in which, in addition to the working days of company K, the non-working days of company K are the days on which company users can use vehicles. Here, generally speaking, on company K's non-working days, it is unlikely that company users belonging to company K will request to use a vehicle. However, even on company K's non-working days, situations may arise where company users want to use a vehicle. With the above configuration, company users can use vehicles even on company K's non-working days. Furthermore, even with the above configuration, it is possible to suppress the restriction of company users' use of vehicles on company K's working days due to vehicle use by general users.

[0047] In the above embodiment, the configuration of the car share management system MS may be changed. For example, the configuration of server 200 may be changed. Specifically, server 200 may be configured as a circuit including one or more processors that execute various processes according to a computer program (software). Server 200 may also be configured as a circuit including one or more dedicated hardware circuits, such as application-specific integrated circuits (ASICs), or a combination thereof, that execute at least some of the various processes. The processor includes a CPU and memory such as RAM and ROM. Memory stores program code or instructions configured to cause the CPU to execute processes. Memory, i.e., computer-readable media, includes any media accessible by a general-purpose or dedicated computer. Similarly, the configurations of enterprise terminal 100 and personal terminal 300 may be changed. [Explanation of symbols]

[0048] C1…First calendar C2…Second calendar CS…Reference calendar MS…Shared car management system NW…Communication network 100…Enterprise terminal 110…Execution device 120…Storage device 121…Control program 130…Communication device 200…Server 210…Execution device 220…Storage device 221…Control program 230…Communication device 300…Personal terminal 310…Execution device 320…Storage device 321…Control program 330…Communication device 340…Display

Claims

1. It is possible to communicate with a personal terminal (300) operated by a user regarding a car-sharing service that targets vehicles managed by the vehicle provider, When, among the aforementioned users, users belonging to a specific group are designated as the first user, and users not belonging to the aforementioned specific group are designated as the second user, The process (S32) involves obtaining a predetermined standard calendar (CS) on a daily or hourly basis on either the first specified day or the second specified day, A process (S33) to generate a first calendar (C1) based on the aforementioned reference calendar, wherein at least the first specific day included in the reference calendar is set as a day on which the vehicle can be used by the first user, Based on the aforementioned reference calendar, a process (S34) is performed to generate a second calendar (C2) in which the second specific day included in the reference calendar is set as the day on which the vehicle can be used by the second user. When a request for reservation management information is received from the aforementioned personal terminal, the process (S53) determines whether the request is from the first user or the second user. If it is determined that the request is from the first user, the process of sending the first calendar to the personal terminal (S54) If it is determined that the request is from the second user, the process of sending the second calendar to the personal terminal (S54) The process of receiving a reservation for the use of the vehicle for a date and time selected from either the first calendar or the second calendar from the personal terminal (S56, S57), Execute Share car management server.

2. The aforementioned specific group is a company, The aforementioned first specified day is a working day of the company, The second specified day is a non-working day for the company. The car-sharing management server according to claim 1.

3. Based on the aforementioned reference calendar, the process is executed to generate the first calendar, in which the working days and non-working days included in the reference calendar are the days on which the vehicle can be used by the first user. The car share management server according to claim 2.

4. This applies to a car-sharing service that involves vehicles managed by the vehicle provider, and is compatible with a shared car management server that can communicate with the user's personal device. When, among the aforementioned users, users belonging to a specific group are designated as the first user, and users not belonging to the aforementioned specific group are designated as the second user, The aforementioned car share management server, The process involves obtaining a predetermined standard calendar on a daily or hourly basis on either the first specified day or the second specified day, A process to generate a first calendar based on the aforementioned reference calendar, wherein at least the first specific day included in the reference calendar is set as a day on which the vehicle can be used by the first user; A process to generate a second calendar based on the aforementioned standard calendar, wherein the second specific day included in the standard calendar is set as a day on which the vehicle can be used by the second user, When a request for reservation management information is received from the aforementioned personal terminal, the process determines whether the request is from the first user or the second user. If it is determined that the request is from the first user, the process of sending the first calendar to the personal terminal is performed. If it is determined that the request is from the second user, the process of sending the second calendar to the personal terminal is performed. A process for receiving a reservation for the use of the vehicle for a date and time selected from either the first calendar or the second calendar from the personal terminal, Make it run A car-sharing management program.

5. This applies to a car-sharing service that involves vehicles managed by the vehicle provider, and is compatible with a shared car management server that can communicate with the user's personal device. When, among the aforementioned users, users belonging to a specific group are designated as the first user, and users not belonging to the aforementioned specific group are designated as the second user, The aforementioned car share management server The process involves obtaining a predetermined standard calendar on a daily or hourly basis on either the first specified day or the second specified day, A process to generate a first calendar based on the aforementioned reference calendar, wherein at least the first specific day included in the reference calendar is set as a day on which the vehicle can be used by the first user; A process to generate a second calendar based on the aforementioned standard calendar, wherein the second specific day included in the standard calendar is set as a day on which the vehicle can be used by the second user, When a request for reservation management information is received from the aforementioned personal terminal, the process determines whether the request is from the first user or the second user. If it is determined that the request is from the first user, the process of sending the first calendar to the personal terminal is performed. If it is determined that the request is from the second user, the process of sending the second calendar to the personal terminal is performed. A process for receiving a reservation for the use of the vehicle for a date and time selected from either the first calendar or the second calendar from the personal terminal, Execute How to manage a shared car.

Images