Vehicle management device, vehicle management system, vehicle management method, and program

The vehicle management system addresses high implementation costs by collectively managing vehicle keys and limiting usage to two times within a reserved time, enhancing cost-effectiveness and accuracy in tracking vehicle reservations and usage.

JP7896336B2Active Publication Date: 2026-07-29RICOH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
RICOH CO LTD
Filing Date
2022-05-09
Publication Date
2026-07-29

AI Technical Summary

Technical Problem

Existing vehicle management systems require costly key storage devices that can independently control the locking and unlocking of each vehicle, leading to high implementation costs for companies with multiple vehicles and employees.

Method used

A vehicle management system that includes a terminal device, key box, and cloud storage, allowing collective management of vehicle keys and limiting key usage to a predetermined number of times within a reserved time frame, eliminating the need for individual key storage devices.

Benefits of technology

Enables cost-effective management of vehicle reservations and usage status by limiting key usage to two times within a reserved time, reducing system costs and improving accuracy in tracking vehicle usage.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007896336000001
    Figure 0007896336000001
  • Figure 0007896336000002
    Figure 0007896336000002
  • Figure 0007896336000003
    Figure 0007896336000003
Patent Text Reader

Abstract

To manage a reservation status, a usage status or the like of a vehicle shared by a plurality of users at a lower cost.SOLUTION: A vehicle management apparatus comprises: a communication unit for communicating with a terminal apparatus and a key management apparatus that manages keys of a plurality of vehicles via a communication network; an information management unit for managing a reservation schedule including a user ID that identifies a user and a reservation time for the user to use the vehicle based on reservation information received from the terminal apparatus; and a usage control unit for permitting usage of the key management apparatus if receiving a request for usage of the key management apparatus including the user ID from the key management apparatus at the reservation time when the user uses the vehicle, wherein the usage control unit limits the number of times the key management apparatus can be used by the user ID during the reservation time.SELECTED DRAWING: Figure 5
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a vehicle management device, a vehicle management system, a vehicle management method, and a program.

Background Art

[0002] There is known a vehicle management system for managing reservations, rentals, etc. of vehicles shared by multiple users. For example, there is a system provided with a key storage device that acquires vehicle borrower information by means of personal authentication, inputs vehicle borrowing information and vehicle return information by means of an input means, and unlocks the key of the borrowed vehicle based on the authentication of the vehicle borrower and the vehicle borrower information (see, for example, Patent Document 1).

Summary of the Invention

Problems to be Solved by the Invention

[0003] For example, in a company or the like that has a plurality of company-owned vehicles and a plurality of employees belong to it, there is a demand to manage the reservation status, usage status, etc. of the company-owned vehicles at low cost.

[0004] However, in the conventional technology as shown in Patent Document 1, since a key storage that can independently control the locking and unlocking of the keys of each vehicle is required, there is a problem that a large amount of cost is required for the introduction of the system.

[0005] One embodiment of the present invention has been made in view of the above problems, and enables the reservation status, usage status, etc. of vehicles shared by multiple users to be managed at a lower cost.

Means for Solving the Problems

[0006] In order to solve the above problems, a vehicle management device according to an embodiment includes a terminal device and keys of a plurality of vehicles StoreA communication unit that communicates with a key management device via a communication network, an information management unit that manages a reservation schedule including a user ID that identifies the user based on the reservation information received from the terminal device, and the key management device receiving a request to use the key management device, including the user ID, at the time the user is scheduled to use the vehicle. Sometimes , the key management device Unlock A user control unit and and , has Furthermore, the usage control unit limits the number of times the key management device is unlocked with the user ID during the reserved time to a predetermined number of times corresponding to the acquisition and return of the vehicle key. When the usage request including the user ID is received from the key management device, if the number of times the key management device has been unlocked with the user ID during the reserved time is equal to or greater than the predetermined number, the key management device is not unlocked. [Effects of the Invention]

[0007] According to one embodiment of the present invention, the reservation status and usage status of vehicles shared by multiple users can be managed at a lower cost. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows an example of the system configuration of a vehicle management system according to one embodiment. [Figure 2] This figure shows an example of a computer hardware configuration according to one embodiment. [Figure 3] This figure shows an example of the hardware configuration of a terminal device according to one embodiment. [Figure 4] This figure shows an example of the functional configuration of a key box according to one embodiment. [Figure 5] This figure shows an example of the functional configuration of a vehicle management system according to one embodiment. [Figure 6] This is a sequence diagram showing an example of a reservation process according to one embodiment. [Figure 7] This figure shows an example of a menu screen according to one embodiment. [Figure 8] This figure shows an example of a new reservation screen according to one embodiment. [Figure 9] This is a sequence diagram showing an example of the key box usage process according to the first embodiment. [Figure 10]This is a sequence diagram showing an example of delay processing and utilization processing according to the second embodiment. [Figure 11] This figure shows an example of a reservation schedule according to the second embodiment. [Figure 12] This is a sequence diagram showing an example of usage processing by another user according to the second embodiment. [Figure 13] This is a sequence diagram showing an example of a reservation change process according to one embodiment. [Figure 14] This figure shows an example of a reservation change screen according to one embodiment. [Modes for carrying out the invention]

[0009] Embodiments of the present invention will be described in detail below with reference to the drawings. <System Configuration> Figure 1 shows an example of the system configuration of a vehicle management system according to one embodiment. The vehicle management system 1 is a system that manages the reservation and rental of vehicles shared by multiple users. Here, as a specific example, the following explanation will be given assuming that the vehicle management system 1 manages the reservation and rental of company vehicles 20a, 20b, ... shared by multiple employees 10.

[0010] The vehicle management system 1 includes, for example, a vehicle management device 100, a key box 110, a terminal device 120, and cloud storage 130, which are connected to each other via a communication network N such as the Internet and a LAN (Local Area Network).

[0011] The vehicle management device 100 is an information processing device having a computer configuration, or a system including multiple computers. The vehicle management device 100 manages the reservations and rentals of company-owned vehicles (examples of vehicles) 20a, 20b, ... shared by multiple employees (examples of users) 10 by executing a predetermined program on the computer. In the following description, "company-owned vehicle 20" will be used to refer to any of the company-owned vehicles 20a, 20b, ...

[0012] The key box (key management device) 110 is an example of a key management device that manages the keys 111a, 111b,... of company-owned vehicles 20a, 20b,.... For example, the keys 111a, 111b,... can be stored. In the following description, when referring to any one of the keys 111a, 111b,..., "key 111" is used.

[0013] The key box 110 has a function of reading identification information (hereinafter referred to as user ID) for identifying the employee 10 from the ID card 11 of the employee 10 and transmitting the read user ID to the vehicle management device 100. Further, the key box 110 has a function of locking and unlocking the key box 110 according to the control from the vehicle management device 100. Note that the key management device according to the present embodiment only needs to be able to collectively store a plurality of keys and perform locking and unlocking of the keys, and does not necessarily have to be in the shape of a box.

[0014] The terminal device 120 is an information terminal such as a smartphone, a tablet terminal, or a PC (Personal Computer), for example. The employee 10 can access the vehicle management device 100 through a web browser provided in the terminal device 120 or an application program (hereinafter referred to as an app) for the vehicle management system 1 installed in the terminal device 120, and make a reservation for the company-owned vehicle 20 or the like.

[0015] The cloud storage 130 is an external storage provided by a cloud service or the like on the communication network N, and is an example of a storage means for the vehicle management device 100 to store information such as a reservation schedule. Note that the storage means for the vehicle management device 100 to store information such as a reservation schedule may be a storage device provided in the vehicle management device 100 or a storage server in the vehicle management system 1.

[0016] In the above configuration, for example, when employee 10 uses a company car 20a, employee 10 logs into the vehicle management system 100 using the terminal device 120 and reserves the company car 20a in advance. As a result, the vehicle management system 100 stores and manages the reservation schedule for the company car 20a, including identification information that identifies employee 10 (hereinafter referred to as the user ID) and the reservation time, etc., in the cloud storage 130 or the like.

[0017] Furthermore, when the reserved time arrives, employee 10 can unlock the key box 110 by having it read employee 10's ID card 11, and retrieve the key 111a for the company vehicle 20a. For example, the key box 110 transmits employee 10's user ID, read from employee 10's ID card 11, to the vehicle management device 100. The vehicle management device 100 then retrieves the reserved time corresponding to the user ID received from the key box 110 from cloud storage 130, etc., and unlocks the key box 110 if the current time is within the reserved time. On the other hand, the vehicle management device 100 does not unlock the key box 110 if the current time is not within the reserved time.

[0018] Similarly, after using the company vehicle 20a, employee 10 can unlock the key box 110 by having employee 10's ID card 11 read by the key box 110, and return the key 111a of the company vehicle 20a to the key box 110.

[0019] Preferably, the vehicle management device 100 allows the use (unlocking) of the key box 110 up to two times within the reserved time corresponding to the user ID, and refuses use (unlocking) a third time or more. This allows the vehicle management device 100 to manage the first use of the key box 110 by employee 10's user ID within the reserved time as a key loan, and the second loan by employee 10's user ID as a key return. This is because if unlocking a third time or more is permitted, it becomes difficult to determine when the key was loaned out and when it was returned.

[0020] However, the above method is a basic processing method, and various modifications and applications are possible for the specific processing method. For example, in the above explanation, the vehicle management device 100 unlocked the key box 110 only during the reserved time corresponding to the user ID received from the key box 110. However, the vehicle management device 100 may be set to unlock the key box 110 from a predetermined time before the reserved time (for example, 10 minutes before). In this case, the vehicle management device 100 only needs to manage the reserved time and the predetermined time before the reserved time as the actual reserved time.

[0021] Furthermore, while the above explanation states that the vehicle management device 100 allowed unlocking the key box 110 up to twice within the reserved time, it is also possible to have a system that allows unlocking again within a predetermined time period (e.g., 5 minutes) after unlocking. This would allow for situations such as when employee 10 mistakenly takes out the key for another company vehicle 20b, or when they accidentally close the key box 110 before returning the key. In this case, the vehicle management device 100 can manage the system so that unlocking within the predetermined time period after unlocking is not counted as an actual number of unlocks.

[0022] Thus, when the vehicle management device 100 receives a request from the key box 110 to use the key box 110, including the user ID of employee 10, during the reserved time when employee 10 is to use the company vehicle 20a, it permits the use of the key box 110 (unlocks it). The vehicle management device 100 also limits the number of times employee 10 can use the key box 110 with their user ID during the reserved time.

[0023] Preferably, the vehicle management device 100 limits the number of times (or the actual number of times) that employee 10 can use the key box 110 with their user ID during the reserved time (or the actual reserved time) to two. This allows the vehicle management device 100 to manage the first use of the key box 110 by employee 10's user ID within the reserved time as a key loan, and the second loan by employee 10's user ID as a key return.

[0024] Furthermore, in this embodiment, a key storage unit that can independently control the locking and unlocking of each vehicle's key is not necessary, as in the technology disclosed in Patent Document 1, for example. Instead, a key box 110 that can lock and unlock multiple keys together can be applied.

[0025] Based on the above, this embodiment makes it possible to manage the reservation status and usage status of vehicles shared by multiple users at a lower cost.

[0026] <Hardware Configuration> (Hardware configuration of the vehicle management system) The vehicle management system 100 has a hardware configuration of a computer 200, for example, as shown in Figure 2. Alternatively, the vehicle management system 100 is composed of multiple computers 200.

[0027] Figure 2 shows an example of the hardware configuration of a computer according to one embodiment. The computer 200 includes, for example, a CPU (Central Processing Unit) 201, ROM (Read Only Memory) 202, RAM (Random Access Memory) 203, HD (Hard Disk) 204, HDD (Hard Disk Drive) controller 205, display 206, external device connection I / F (Interface) 207, network I / F 208, keyboard 209, pointing device 210, DVD-RW (Digital Versatile Disk Rewritable) drive 212, media I / F 214, and bus line 215, as shown in Figure 2.

[0028] Of these components, the CPU 201 controls the overall operation of the computer 200. The ROM 202 stores programs and data used to start the computer 200, such as boot files. The RAM 203 is used, for example, as a work area for the CPU 201. The HD 204 stores programs such as the OS (Operating System), applications, and device drivers, as well as various data. The HDD controller 205 controls the reading or writing of various data to the HD 204, for example, according to the control of the CPU 201.

[0029] Display 206 displays various information, such as a cursor, menu, window, text, or image. Note that Display 206 may be located outside the computer 200. External device connection I / F 207 is an interface for connecting various external devices to the computer 200, such as external memory. Network I / F 208 is an interface for data communication using, for example, a communication network N.

[0030] The keyboard 209 is a type of input device equipped with multiple keys for inputting characters, numbers, and various instructions. The pointing device 210 is a type of input device for selecting and executing various instructions, selecting processing targets, moving the cursor, etc. Note that the keyboard 209 and the pointing device 210 may be located outside the computer 200.

[0031] The DVD-RW drive 212 controls the reading or writing of various data to the DVD-RW 211, which is an example of a removable recording medium. Note that the DVD-RW 211 is not limited to DVD-RW; it may be any other removable recording medium. The media interface 214 controls the reading or writing (storage) of data to the media 213, such as flash memory. The bus line 215 includes an address bus, a data bus, and various control signals for electrically connecting the above components.

[0032] Note that the configuration of computer 200 shown in Figure 2 is just one example. Computer 200 can have any other configuration as long as it has, for example, a CPU 201, ROM 202, RAM 203, and a network I / F 208.

[0033] (Terminal device hardware configuration) As an example, terminal device 120 may have a hardware configuration as shown in Figure 3. Alternatively, as another example, terminal device 120 may have a computer 200 hardware configuration as shown in Figure 2.

[0034] Figure 3 shows an example of the hardware configuration of a terminal device according to one embodiment. As shown in Figure 3, the terminal device 120 includes a CPU 301, ROM 302, RAM 303, storage device 304, CMOS (Complementary Metal Oxide Semiconductor) sensor 305, image sensor I / F 306, acceleration / direction sensor 307, media I / F 309, and GPS (Global Positioning System) receiver 310.

[0035] Of these, the CPU 301 controls the operation of the entire terminal device 120 by executing a predetermined program. The ROM 302 stores programs used to start the CPU 301, such as an IPL. The RAM 303 is used as the work area for the CPU 301. The storage device 304 is a large-capacity storage device that stores programs such as the OS and applications, and various data, and is implemented by, for example, an SSD (Solid State Drive) or flash ROM.

[0036] The CMOS sensor 305 is a type of built-in imaging means that captures an image of a subject (mainly a self-portrait) and obtains image data according to the control of the CPU 301. The terminal device 120 may have an imaging means such as a CCD (Charge Coupled Device) sensor instead of the CMOS sensor 305. The image sensor interface 306 is a circuit that controls the driving of the CMOS sensor 305. The acceleration / direction sensor 307 is a type of sensor such as an electronic magnetic compass, gyrocompass, or acceleration sensor that detects the Earth's magnetic field. The media interface 309 controls the reading or writing (storage) of data to or from the media (storage medium) 308, such as flash memory. The GPS receiver 310 receives GPS signals (positioning signals) from GPS satellites.

[0037] Furthermore, the terminal device 120 includes a long-range communication circuit 311, an antenna 311a for the long-range communication circuit 311, a CMOS sensor 312, an image sensor interface 313, a microphone 314, a speaker 315, an audio input / output interface 316, a display 317, an external device connection interface 318, a short-range communication circuit 319, an antenna 319a for the short-range communication circuit 319, and a touch panel 320.

[0038] Of these, the long-distance communication circuit 311 is a circuit that communicates with other devices, for example, via a communication network. The CMOS sensor 312 is a type of built-in imaging means that captures an image of a subject and obtains image data according to the control of the CPU 301. The image sensor interface 313 is a circuit that controls the driving of the CMOS sensor 312. The microphone 314 is a built-in circuit that converts sound into electrical signals. The speaker 315 is a built-in circuit that converts electrical signals into physical vibrations to produce sound such as music and speech. The sound input / output interface 316 is a circuit that processes the input and output of sound wave signals between the microphone 314 and the speaker 315 according to the control of the CPU 301.

[0039] The display 317 is a type of display means, such as a liquid crystal or organic EL (electroluminescence), that displays images of the subject and various icons. The external device connection I / F 318 is an interface for connecting various external devices. The short-range communication circuit 319 includes a circuit for performing short-range wireless communication. The touch panel 320 is a type of input means that allows the user to operate the terminal device 120 by pressing the display 317.

[0040] Furthermore, the terminal device 120 is equipped with a bus line 321. The bus line 321 includes an address bus, a data bus, and the like for electrically connecting each component, such as the CPU 301 shown in Figure 3.

[0041] (Key box hardware configuration) Figure 4 shows an example of the hardware configuration of a key box according to one embodiment. The key box 110 includes, for example, a CPU 401, memory 402, storage device 403, communication device 404, reading device 405, input / output device 406, locking device 407, and bus 408.

[0042] The CPU 401 is a processor that controls the entire key box 110 by executing programs stored, for example, in a storage device 403 or memory 402. The memory 402 includes, for example, RAM used as a work area for the CPU 401, and ROM that pre-stores programs for starting the CPU 401. The storage device 403 is, for example, a large-capacity, non-volatile storage device such as an SSD or HDD.

[0043] The communication device 404 is, for example, a communication interface that connects the key box to the communication network N. The reading device 405 is, for example, a card reader that reads IDs such as user ID, employee ID, and card ID from the ID card 11. The input / output device 406 includes, for example, one or more input devices such as a touch panel or input buttons, and output devices such as a display, speaker, or lamp.

[0044] The locking device 407 is a device that locks or unlocks the key box 110 according to a control signal from the CPU 401, for example. Locking the key box 110 means controlling it so that the keys 111 for the company vehicles 20 stored in the key box 110 cannot be taken out or returned. Unlocking the key box 110 means controlling it so that the keys 111 for the company vehicles 20 stored in the key box 110 can be taken out or returned. The bus 408 is connected in common to all of the above components and transmits, for example, address signals, data signals, and various control signals.

[0045] <Functional Configuration> Figure 5 shows an example of the functional configuration of a vehicle management system according to one embodiment.

[0046] (Functional configuration of the vehicle management system) The vehicle management device 100 implements the communication unit 501, information management unit 502, usage control unit 503, and storage unit 504, etc., by having one or more computers 200 equipped in the vehicle management device 100 execute predetermined programs stored in a storage medium. At least some of the above functional configurations may be implemented by hardware.

[0047] The communication unit 501 connects the vehicle management device 100 to the communication network N using the network I / F 208, etc., and performs communication processing to communicate with other devices such as the key box 110, terminal device 120, and cloud storage 130.

[0048] The Information Management Unit 502 performs information management processing based on reservation information received from terminal devices, which includes a user ID to identify employee (user) 10 and a reservation schedule that includes the reservation time for employee 10 to use the company vehicle 20. For example, the Information Management Unit 502 functions as a web server that provides a web page to display a reservation screen for reserving the company vehicle 20, and stores and manages the reservation schedule entered on the reservation screen in cloud storage 130 or the like.

[0049] When the usage control unit 503 receives a request from the key box 110 containing the user ID of employee 10 to use the key box 110 during the reserved time when employee 10 is using the company vehicle 20, it executes usage control processing to permit the use of the key box 110. In addition, the usage control unit 503 limits the number of times employee 10 can use the key box 110 with the user ID of employee 10 during the reserved time when employee 10 is using the company vehicle 20.

[0050] For example, when the usage control unit 503 receives a usage request including a user ID from the key box 110, it determines whether it is a reserved time for employee 10 to use the company car 20, and whether the user ID has used the key box 110 less than two times during the reserved time. The usage control unit 503 also determines whether it is a reserved time for employee 10 to use the company car 20, and whether the user ID has used the key box 110 less than two times during the reserved time, and permits the use of the key box 110 (unlocks the key box 110). On the other hand, if it is not a reserved time for employee 10 to use the company car 20, or if the user ID has used the key box 110 two or more times during the reserved time, the usage control unit 503 does not permit the use of the key box 110 (does not unlock the key box 110).

[0051] The memory unit 504 is implemented by, for example, a program executed by the CPU 201, HD 204, and HDD controller 205, and stores various information, data, and programs, such as login information for employees 10, information on web pages provided to terminal devices 120, and information on the key box 110.

[0052] Note that the functional configuration of the vehicle management device 100 shown in Figure 5 is just one example. For example, the functional configuration of the vehicle management device 100 may be distributed across multiple computers 200.

[0053] (Key box functional configuration) The key box (key management device) 110 implements the communication unit 511, request unit 512, key management unit 513, etc., by having the CPU 401 execute a predetermined program stored in a storage medium. At least some of the above functional configurations may be implemented by hardware.

[0054] The communication unit 511, for example, uses a communication device 404 to connect the key box 110 to the communication network N and performs communication processing to communicate with other devices such as the vehicle management device 100.

[0055] The request unit 512 reads the user ID, etc., from the ID card 11 using, for example, a reader 405, and performs request processing to send a request to the vehicle management device 100 to use the key box 110, which includes the read user ID, etc.

[0056] For example, when the key management unit 513 receives permission information from the vehicle management device 100 to allow the use of the key box 110, it executes key management processing that enables the employee 10 to obtain or return the key 111 for the company vehicle 20. For example, the key management unit 513 controls the locking device 407 to lock the door of the key box 110, and when it receives permission information from the vehicle management device 100, it temporarily unlocks the door of the key box 110.

[0057] (Functional configuration of terminal devices) The terminal device 120 implements the communication unit 521, display control unit 522, operation reception unit 523, and storage unit 524, etc., by executing predetermined programs such as an OS (Operating System) and a web browser using the CPU 301 (or CPU 201). At least some of the above functional configurations may be implemented by hardware.

[0058] The communication unit 521 connects the terminal device 120 to the communication network N using the long-distance communication circuit 311 (or network I / F 208), and performs communication processing to communicate with external devices such as the vehicle management device 100.

[0059] The display control unit 522 connects to a web server provided by the vehicle management device 100, for example, and displays various display screens provided by the vehicle management device 100, such as a new reservation screen or a reservation change screen, on the display 317 (or display 206), etc.

[0060] The operation reception unit 523 accepts user (e.g., employee 10) input operations for various display screens displayed by the display control unit 522, for example, using a touch panel 320 (or keyboard 209).

[0061] The memory unit 524 is implemented, for example, by a program executed by the CPU 301 and a storage device 304, and stores various information, data, and programs.

[0062] (Cloud storage functionality configuration) The cloud storage 130 is assumed to be a storage service provided by an external vendor, and can have any configuration as long as it can write and read predetermined information in accordance with the control from the vehicle management device 100.

[0063] <Processing flow> Next, the processing flow of the vehicle management method according to this embodiment will be described.

[0064] [First Embodiment] (Reservation processing) Figure 6 is a sequence diagram showing an example of a reservation process according to one embodiment. This process shows an example of the process executed by the vehicle management system 1 when employee A reserves company vehicle A using terminal device 120. At the start of the process shown in Figure 6, it is assumed that employee A has already logged into the vehicle management system 100 using terminal device 120.

[0065] In step S601, when employee A performs the operation to display the new reservation screen on the terminal device 120, the vehicle management system 1 executes the processes in steps S602 to S605. Employee A can perform the operation to display the new reservation screen by selecting the "New Reservation" button 701 on the menu screen 700 displayed by the terminal device 120, for example, as shown in Figure 7.

[0066] In step S602, when the operation reception unit 523 of the terminal device 120 receives an operation to display the new reservation screen, it sends a request to the vehicle management device 100 to display the new reservation screen. This display request includes, for example, the user ID of employee A.

[0067] In step S603, when the information management unit 502 of the vehicle management device 100 receives a request from the terminal device 120 to display a new reservation screen, it retrieves the reservation schedules of all company vehicles from the cloud storage 130.

[0068] In step S604, the information management unit 502 of the vehicle management device 100 creates a new reservation screen 800, for example, as shown in Figure 8, and sends it to the requesting terminal device 120. As a result, in step S605, the display control unit 522 of the terminal device 120 displays the new reservation screen 800 on a display unit, for example, the display 317.

[0069] Figure 8 shows an example of a new reservation screen according to the first embodiment. On the new reservation screen 800, for example, if a date is entered in the date setting field 801, the reservation schedule 805 displays the reservation status of multiple company vehicles for the entered date. Employee A can make a new reservation by setting the company vehicle to be used (for example, company vehicle A) in the vehicle setting field 803, setting the start time and end time of use in the time setting field 802, and selecting the "Reserve" button 804.

[0070] In step S606 of Figure 6, when employee A makes a new reservation, the vehicle management system 1 executes the processes from step S607 onwards.

[0071] In step S607, when the operation reception unit 523 of the terminal device 120 receives a new reservation operation, it transmits the received reservation information to the vehicle management device 100. This reservation information includes, for example, the user ID of employee A, information about the vehicle to be reserved (for example, company car A), and reservation time (start time and end time).

[0072] In step S608, when the information management unit 502 of the vehicle management device 100 receives reservation information from the terminal device 120, it checks whether the received reservation information overlaps with other reservations. For example, if there are reservations with overlapping reservation times corresponding to the same user ID (multiple reservations), the information management unit 502 determines that the reservations are duplicates.

[0073] If there are no overlapping reservations, the information management unit 502 updates the reservation schedule stored in the cloud storage 130 in step S609. For example, the information management unit 502 stores the user ID, vehicle information, reservation time, and the number of openings / closings ("0") included in the reservation information in the reservation schedule.

[0074] On the other hand, if there is a reservation conflict, the information management unit 502 sends an error notification (reservation conflict) to the requesting terminal device 120 in step S611. As a result, in step S612, the display control unit 522 of the terminal device 120 displays an error message indicating that the reservation failed on a display unit such as the display 317.

[0075] Thus, the information management unit 502 according to this embodiment has a function to reject (or ignore) multiple reservations corresponding to the same user ID. As a result, the information management system 1 can suppress proxy reservations, etc., in which an employee 10 who does not actually use the company car 20 reserves the company car 20 on behalf of another employee, and can grasp the usage status of the company car 20 more accurately.

[0076] (Key box usage process) Figure 9 is a sequence diagram showing an example of the key box usage process according to the first embodiment. This process shows an example of the key box usage process executed by the vehicle management system 1 when employee A, who has reserved a company vehicle (for example, company vehicle A) in the reservation process described in Figure 6, uses the key box 110 within the reserved time to obtain or return the key to company vehicle A.

[0077] In step S901, when employee A performs a read operation on the ID card 11, for example, on the key box 110, to read the user ID stored on the ID card 11, the vehicle management system 1 executes the processes from step S902 onwards.

[0078] In step S902, the request unit 512 of the key box 110 reads employee A's user ID from employee A's ID card 11 and sends a request to use the key box 110, including employee A's user ID, to the vehicle management device 100.

[0079] In step S903, when the information management unit 502 of the vehicle management device 100 receives a usage request from the key box 110, it uses the user ID of employee A included in the usage request to obtain information such as employee A's reservation time and the number of times the door has been opened and closed from the cloud storage 130. If the current time is within employee A's reservation time and the number of times the door has been opened and closed is less than two, the usage control unit 503 of the vehicle management device 100 executes the processes in steps S904 to S906.

[0080] On the other hand, if the current time is not within employee A's reserved time, or if the number of times the lock has been opened and closed is two or more, the usage control unit 503 of the vehicle management device 100 transmits a usage refusal to the key box 110 in step S911. Alternatively, the usage control unit 503 may ignore the usage request from the key box 110.

[0081] In step S904, the usage control unit 503 of the vehicle management device 100 transmits a usage permission to the key box 110 requesting its unlocking. In response, in step S905, the key management unit 513 of the key box 110 unlocks the key box 110. This allows employee A to retrieve the key to company vehicle A that was reserved from the key box 110, or to return the key to company vehicle A to the key box 110.

[0082] In step S906, the information management unit 502 of the vehicle management device 100 adds 1 to the number of times employee A has opened and closed the door during the reserved time.

[0083] As described above, the vehicle management device 100 according to the first embodiment limits the number of times employee A can use the key box 110 within the reserved time slot to (effectively) two times. Therefore, the first use of the key box 110 by employee A is considered to be for obtaining the key to company vehicle A, and the second use of the key box 110 is considered to be for returning the key to company vehicle A, thereby enabling the management of the usage status of multiple company vehicles.

[0084] Preferably, when employee A reserves a company vehicle, the vehicle management device 100 rejects multiple reservations that overlap reservation times for the same user ID. This allows the vehicle management device 100 to suppress inappropriate operations such as proxy reservations where one employee reserves a company vehicle on behalf of another employee, and to more accurately understand the usage status of company vehicles.

[0085] [Second Embodiment] In the second embodiment, for example, an example of how to handle a situation where employee A, who is using company-owned vehicle A, is unable to return to the company within the reserved time will be described. Note that the functional configuration of the vehicle management system 1 according to the second embodiment may be the same as in the first embodiment.

[0086] <Processing flow> (Delayed processing and usage processing) Figure 10 is a sequence diagram showing an example of delay processing and utilization processing according to the second embodiment. The information management unit 502 of the vehicle management device 100 according to the second embodiment repeatedly performs delay processing, such as that shown in steps S1001 and S1002 of Figure 10, at predetermined time intervals (for example, intervals of 1 to 5 minutes).

[0087] In step S1001, the information management unit 502 of the vehicle management device 100 retrieves reservation schedules stored in the cloud storage 130 that have been opened and closed only once and whose reservation time (end time) has elapsed.

[0088] In step S1002, the information management unit 502 of the vehicle management device 100 updates the reservation schedule stored in the cloud storage 130, taking the time that has elapsed since the reservation time as the delay time in the acquired reservation schedule.

[0089] Figure 11 shows an image of a reservation schedule according to the second embodiment. In the example in Figure 11, the reservation schedule 1100 stores the reservation time and delay time reserved by the employee for each company vehicle.

[0090] For example, in Figure 11, the reservation schedule 1110 for company car A has employee A's reservation time 1101 registered from 10:00 to 12:00, and employee B's reservation time 1102 registered from 15:00 to 17:00.

[0091] For example, suppose that due to an accident or other reason, employee A is delayed in returning to the office, and the key to company vehicle A has not been returned to the key box 110 by 4 PM. In this case, the information management department 502 manages the period from 12 PM to 4 PM, during which the key return is delayed, as employee A's delay time 1103 in the reservation schedule 1110 for company vehicle A.

[0092] In this state, for example, if employee A performs a user ID reading operation in step S1011 after the reservation time has elapsed, the vehicle management system 1 executes the processes from step S1012 onwards.

[0093] In step S1012, the request unit 512 of the key box 110 reads employee A's user ID from employee A's ID card 11 and sends a request to use the key box 110, including employee A's user ID, to the vehicle management device 100.

[0094] In step S1013, when the information management unit 502 of the vehicle management device 100 receives a usage request, it uses the user ID of employee A included in the usage request to obtain information such as employee A's reservation time, delay time, and number of times the gate has been opened and closed from the cloud storage 130. If the current time is within employee A's reservation time + delay time and the number of times the gate has been opened and closed is 1, the usage control unit 503 of the vehicle management device 100 executes the processes in steps S1014 to S1016.

[0095] On the other hand, if the current time is not within the period of employee A's reservation time plus the delay time, or if the number of times the lock has been opened and closed is two or more, the usage control unit 503 of the vehicle management device 100 transmits a usage refusal to the key box 110 in step S1021. Alternatively, the usage control unit 503 may ignore the usage request from the key box 110.

[0096] In step S1014, the usage control unit 503 of the vehicle management device 100 transmits a usage permission to the key box 110 requesting its unlocking. In response, in step S1015, the key management unit 513 of the key box 110 unlocks the key box 110. This allows employee A to return the key to company vehicle A to the key box 110.

[0097] In step S1016, the information management unit 502 of the vehicle management device 100 adds 1 to the number of times employee A has opened and closed the door during the reserved time.

[0098] (Processing of other users' usage) Figure 12 is a sequence diagram showing an example of usage processing by another user according to the second embodiment. This process shows an example of the vehicle management system 1's processing for employee B, another user who reserved company car A, when employee A is late in returning the key to company car A, as explained in Figure 10. Here, we will assume that employee A and employee B have reserved company car A, as shown in the reservation schedule 1100 in Figure 11, and will provide the following explanation.

[0099] In step S1201, when employee B performs a user ID reading operation, the vehicle management system 1 executes the processes from step S1202 onwards.

[0100] In step S1202, the request unit 512 of the key box 110 reads employee B's user ID from employee B's ID card 11 and sends a request to use the key box 110, including employee B's user ID, to the vehicle management device 100.

[0101] In step S1203, when the information management unit 502 of the vehicle management device 100 receives a usage request, it uses the user ID of employee B included in the usage request to obtain information such as employee B's reservation time, delay time, and number of openings and closings from the cloud storage 130. If the current time is within employee B's reservation time + delay time and the number of openings and closings is 0, the usage control unit 503 of the vehicle management device 100 executes the processing from step S1204 onwards.

[0102] Furthermore, if the current time is within employee B's reservation time + delay time and the number of times the gate has been opened and closed is 1, the usage control unit 503 executes the same process as in steps S1014 to S1016 in Figure 10. If the current time is outside of employee B's reservation time + delay time, or if the number of times the gate has been opened and closed is 2 or more, the usage control unit 503 executes the process in step S1021 in Figure 10.

[0103] In step S1204, the information management unit 502 of the vehicle management device 100 retrieves the delay time of the vehicle reserved by employee B from the cloud storage 130. For example, in the example of the reservation schedule 1100 shown in Figure 11, the information management unit 502 retrieves the delay time of company vehicle A reserved by user B (employee A's delay time 1103). If the retrieved delay time (employee A's delay time 1103) does not overlap with employee B's reservation time 1102, the vehicle management system 1 executes the processes in steps S1211 to S1213.

[0104] On the other hand, if the acquired delay time (employee A's delay time 1103) overlaps with employee B's reservation time 1102, the usage control unit 503 of the vehicle management device 100 prioritizes the delay time over the reservation time and sends a usage refusal to the key box 110 in step S1221. Alternatively, the usage control unit 503 may ignore the usage request from the key box 110. This is because, for example, if employee B opens the key box 110 when the key for company vehicle A is not stored in the key box 110, the first use of the key box 110 cannot be managed as the acquisition of a key.

[0105] In step S1211, the usage control unit 503 of the vehicle management device 100 transmits a usage permission to the key box 110 requesting its unlocking. In response, in step S1212, the key management unit 513 of the key box 110 unlocks the key box 110. As a result, employee B can obtain the key to company vehicle A from the key box 110.

[0106] In step S1213, the information management unit 502 of the vehicle management device 100 adds 1 to the number of times employee B has opened and closed the door during the reserved time.

[0107] By the processes shown in Figures 10-12, the vehicle management device 100 can prevent employee B from opening the key box 110 when the key for the reserved company vehicle A is not stored in the key box 110.

[0108] Furthermore, if employee B is unable to use the key box 110 at the reserved time, they can reserve a different company vehicle by following the reservation change procedure shown in Figure 13.

[0109] (Reservation change processing) Figure 13 is a sequence diagram showing an example of a reservation change process according to one embodiment. This process shows an example of the process that the vehicle management system 1 executes when a user (for example, employee B) changes a reservation for a company-owned vehicle that has already been reserved. At the start of the process shown in Figure 13, it is assumed that employee B has already logged in to the vehicle management system 100 using the terminal device 120.

[0110] In step S1301, when employee B performs the operation to display the reservation change screen on the terminal device 120, the vehicle management system 1 executes the processes in steps S1302 to S1305. Employee B can perform the operation to display the reservation change screen by selecting the "Change Reservation" button 702 on the menu screen 700 displayed by the terminal device 120, for example, as shown in Figure 7.

[0111] In step S1302, when the operation reception unit 523 of the terminal device 120 receives an operation to display the reservation change screen, it sends a request to the vehicle management device 100 to display the reservation change screen. This display request includes, for example, the user ID of employee B.

[0112] In step S1303, when the information management unit 502 of the vehicle management device 100 receives a request from the terminal device 120 to display the reservation change screen, it retrieves the reservation schedules of all company vehicles from the cloud storage 130.

[0113] In step S1304, the information management unit 502 of the vehicle management device 100 creates a reservation change screen 1400, for example, as shown in Figure 14, and sends it to the requesting terminal device 120. As a result, in step S1305, the display control unit 522 of the terminal device 120 displays the reservation change screen 1400 on a display unit, for example, a display 317.

[0114] Figure 14 shows an example of a reservation change screen according to one embodiment. The reservation change screen 1400 displays, for example, the reservation schedule 1401 obtained in step S1303. In the example in Figure 14, in the reservation schedule 1401, employee B's reservation time 1402 and employee A's delay time 1403 overlap, and at 3pm, employee B is unable to use the company car A that they reserved.

[0115] In such a case, employee B can change the reservation by selecting employee B's reservation time 1402, then setting the new date, time, and vehicle in the fields 1404, and then selecting the "Change" button 1405.

[0116] In step S1306 of Figure 13, when employee B performs a reservation change operation, the vehicle management system 1 executes the processes from step S1307 onwards.

[0117] In step S1307, when the operation reception unit 523 of the terminal device 120 receives a reservation change operation, it transmits the received reservation change information to the vehicle management device 100. This reservation information includes, for example, the user ID of employee B, the vehicle information and reservation time before the change, and the vehicle information and reservation time after the change.

[0118] In step S1308, the information management unit 502 of the vehicle management device 100 updates the reservation schedule stored in the cloud storage 130 according to the reservation change information. At this time, the information management unit 502 may, for example, check for duplicate reservations as shown in steps S608 to S611 of Figure 6, and update the reservation schedule stored in the cloud storage 130 if there are no duplicate reservations. Alternatively, the information management unit 502 may control the reservation change screen 1400 displayed on the terminal device 120 so that duplicate dates, times, or vehicles cannot be selected.

[0119] As a result of the process shown in Figure 13, for example, on the reservation change screen shown in Figure 14, user B can reserve company car B from 15:00 instead of the reservation time 14:02 for employee B of company car A, thereby enabling them to use company car B from 15:00.

[0120] As described above, according to each embodiment of the present invention, the reservation status and usage status of vehicles shared by multiple users can be managed at a lower cost.

[0121] <Supplement> Each function of the embodiments described above can be realized by one or more processing circuits. Hereinafter, "processing circuit" as used herein includes processors programmed to execute each function by software, such as processors implemented by electronic circuits, as well as devices such as ASICs (Application Specific Integrated Circuits), DSPs (digital signal processors), FPGAs (field programmable gate arrays), and conventional circuit modules designed to execute each function described above.

[0122] Furthermore, the apparatus described in the examples represents only one of several computing environments for carrying out the embodiments disclosed herein. In one embodiment, the vehicle management system 100 includes multiple computing devices, such as a server cluster. The multiple computing devices are configured to communicate with each other via any type of communication link, including networks and shared memory, and perform the processing disclosed herein.

[0123] Furthermore, the vehicle management device 100 can be configured to share the disclosed processing steps, such as those shown in Figures 9, 10, 12, and 13, in various combinations. For example, a process performed by a predetermined unit may be performed by the key box 110. Similarly, the functions of a predetermined unit may be performed by the vehicle management device 100. In addition, each functional configuration of the vehicle management device 100 may be combined into a single server device or divided among multiple devices.

[0124] <Note> This specification discloses vehicle management devices, vehicle management systems, vehicle management methods, and programs as described in the following sections. (Section 1) A terminal device, a key management device that manages the keys of multiple vehicles, and a communication unit that communicates with them via a communication network, Based on the reservation information received from the terminal device, a user ID is assigned to identify the user, and an information management unit manages the reservation schedule, including the reservation time for the user to use the vehicle. When the user receives a request from the key management device to use the key management device, including the user ID, during the reserved time for the user to use the vehicle, the usage control unit permits the use of the key management device, and the usage control unit limits the number of times the user ID can use the key management device during the reserved time. A vehicle management device having the following features. (Section 2) The aforementioned usage control unit, When the key management device receives the usage request including the user ID, If the user has a reservation to use the vehicle and the number of times the user ID has used the key management device during that reservation time is less than two, the use of the key management device will be permitted. If the user is not using the vehicle during the reserved time, or if the user has used the key management device with the user ID two or more times during the reserved time, the use of the key management device will not be permitted. The vehicle management device described in paragraph 1. (Section 3) The aforementioned information management department, The first use of the key management device by the aforementioned user ID is managed as the lending of the vehicle key. The second use of the key management device by the aforementioned user ID is managed as the return of the vehicle key. The vehicle management device described in paragraph 2. (Section 4) The aforementioned information management department, If the user ID has used the key management device once during the reserved time, and there is a reserved schedule that has exceeded the reserved time, the elapsed time will be managed as the delay time during which the user used the vehicle. A vehicle management device as described in paragraph 2 or 3. (Section 5) The vehicle management device according to paragraph 4, wherein the usage control unit prioritizes the delay time over the reservation time of other reservation schedules. (Section 6) The key management device is a key box that stores the keys for the plurality of vehicles, The vehicle management device according to any one of paragraphs 1 to 5, wherein the usage control unit unlocks the key box when it permits the use of the key box. (Section 7) The vehicle management device according to any one of paragraphs 1 to 6, wherein the information management unit rejects multiple reservations for the user ID where the reservation time overlaps. (Section 8) A vehicle management system including a key management device for managing the keys of multiple vehicles and a vehicle management device, The aforementioned vehicle management device is A terminal device and a communication unit that communicates with the key management device via a communication network, Based on the reservation information received from the terminal device, a user ID is assigned to identify the user, and an information management unit manages the reservation schedule, including the reservation time for the user to use the vehicle. When the user receives a request from the key management device to use the key management device, including the user ID, during the reserved time for the user to use the vehicle, the usage control unit permits the use of the key management device, and the usage control unit limits the number of times the user ID can use the key management device during the reserved time. It has, The aforementioned key management device is A request unit that obtains the user ID and transmits a request to use the key management device, including the user ID, to the vehicle management device. A key management unit that, upon receiving permission information from the vehicle management device that permits the use of the key management device, enables the user to acquire or return the key, Having, Vehicle management system. (Section 9) The process involves communicating with a terminal device and a key management device that manages the keys of multiple vehicles via a communication network. Based on the reservation information received from the terminal device, a user ID is generated to identify the user, and a process is used to manage the reservation schedule, including the time the user is scheduled to use the vehicle. When the user has a reservation to use the vehicle, the key management device receives a request from the key management device to use the key management device, including the user ID, the key management device is authorized to be used. A process to limit the number of times the user ID can use the key management device at the reserved time, A vehicle management method that is performed by a computer. (Section 10) A program that causes a computer to execute the vehicle management method described in paragraph 9.

[0125] Although embodiments of the present invention have been described above, the present invention is not limited to these specific embodiments, and various modifications and applications are possible within the scope of the gist of the present invention as described in the claims.

[0126] For example, in each of the embodiments described above, the vehicle management system 1 was described as managing company-owned vehicles shared by multiple employees. However, the vehicle management system 1 may also be used to manage vehicles shared by multiple users in various organizations such as medical institutions, educational institutions, disaster prevention centers, or government offices. [Explanation of Symbols]

[0127] 1. Vehicle Management System 20, 20a, 20b Company-owned vehicles (examples of vehicles) 110 Key box (an example of a key management device) 111, 111a, 111b keys 120 Terminal devices 501 Communications Department 502 Information Management Department 503 User Control Unit 512 Request part 513 Key Management Department N Communication Network [Prior art documents] [Patent Documents]

[0128] [Patent Document 1] Japanese Patent Publication No. 2004-259147

Claims

1. A terminal device, a key management device that stores keys for multiple vehicles, and a communication unit that communicates with them via a communication network, Based on the reservation information received from the terminal device, a user ID is used to identify the user, and an information management unit manages the reservation schedule, including the reservation time for the user to use the vehicle. When the user has a reservation to use the vehicle and the key management device receives a request from the key management device to use the key management device, including the user ID, the usage control unit unlocks the key management device. It has, The aforementioned usage control unit, The number of times the key management device is unlocked using the user ID at the reserved time is limited to a predetermined number of times corresponding to the acquisition and return of the vehicle key. When the key management device receives the usage request including the user ID, if the number of times the key management device has been unlocked with the user ID during the reserved time is equal to or greater than the predetermined number, the key management device will not be unlocked. Vehicle management system.

2. The aforementioned usage control unit, When the key management device receives the usage request including the user ID, If the user has a reservation to use the vehicle and the number of times the user ID has unlocked the key management device during that reservation time is less than two, the key management device will be unlocked. If the user is not using the vehicle at the reserved time, or if the user has unlocked the key management device with the user ID two or more times during the reserved time, the key management device will not be unlocked. The vehicle management device according to claim 1.

3. The aforementioned information management department, The first unlocking of the key management device by the user ID is managed as the lending of the vehicle key. The second unlocking of the key management device by the aforementioned user ID is managed as the return of the vehicle key. The vehicle management device according to claim 2.

4. The aforementioned information management department, If the user ID has unlocked the key management device once during the reserved time, and there is a reserved schedule that has exceeded the reserved time, the elapsed time will be managed as the delay time during which the user used the vehicle. The vehicle management device according to claim 2.

5. The vehicle management device according to claim 4, wherein the usage control unit prioritizes the delay time over the reservation time of other reservation schedules.

6. The key management device is a key box that stores the keys for the plurality of vehicles, The vehicle management device according to any one of claims 1 to 5, wherein the usage control unit unlocks the key box when it permits the use of the key box.

7. The vehicle management device according to any one of claims 1 to 5, wherein the information management unit rejects multiple reservations for the user ID where the reservation time overlaps.

8. A vehicle management system including a key management device for storing keys for multiple vehicles and a vehicle management device, The aforementioned vehicle management device is A terminal device and a communication unit that communicates with the key management device via a communication network, Based on the reservation information received from the terminal device, a user ID is used to identify the user, and an information management unit manages the reservation schedule, including the reservation time for the user to use the vehicle. A usage control unit transmits permission information to the key management device that authorizes the unlocking of the key management device when it receives a request from the key management device, including the user ID, at the time the user has reserved to use the vehicle. It has, The aforementioned key management device is A request unit that obtains the user ID and transmits a request to use the key management device, including the user ID, to the vehicle management device. A key management unit, upon receiving permission information from the vehicle management device, unlocks the key management device, enabling the user to acquire or return the key. It has, The aforementioned usage control unit, The number of times the user ID is permitted to unlock the key management device at the reserved time is limited to a predetermined number of times corresponding to the acquisition and return of the vehicle key. When the key management device receives the usage request including the user ID, if the number of times the user ID has been authorized to unlock the key management device during the reserved time is greater than or equal to the predetermined number, the authorization information is not transmitted to the key management device. Vehicle management system.

9. The process involves communicating with a terminal device and a key management device that stores keys for multiple vehicles via a communication network. Based on the reservation information received from the terminal device, a user ID is generated to identify the user, and a process is used to manage the reservation schedule, including the reservation time for the user to use the vehicle. When the user has a reservation to use the vehicle and the key management device receives a request from the key management device to use the key management device, including the user ID, a usage control process is performed to unlock the key management device. The computer executes this, The aforementioned usage control process is: The number of times the key management device is unlocked using the user ID at the reserved time is limited to a predetermined number of times corresponding to the acquisition and return of the vehicle key. When the key management device receives the usage request including the user ID, if the number of times the key management device has been unlocked with the user ID during the reserved time is equal to or greater than the predetermined number, the key management device will not be unlocked. Vehicle management methods.

10. A program that causes a computer to execute the vehicle management method described in claim 9.