Reservation management device and reservation management method

Abstract

To provide a mechanism which can accept a reservation of a charging space while providing the charging space to a vehicle having no reservation.SOLUTION: A reservation management device includes: a status acquisition unit for acquiring information on the presence or absence of a vehicle in a charging space; a reservation management unit for determining whether a use state of the charging space is a reservable state on the basis of the information acquired by the status acquisition unit and accepting a reservation of the charging space if the use state is the reservable state; and a regulation unit for bringing a regulation device provided in the charging space into a state of regulating the use of the charging space when the reservation management unit has accepted the reservation.SELECTED DRAWING: Figure 14

Description

[Technical Field]

[0001] The present invention relates to a reservation management device and a reservation management method. [Background technology]

[0002] Background art in this technical field is found in Japanese Patent No. 7046407 (Patent Document 1), which states that "the reservation system includes a reservation processing unit that reserves a shared facility including an electric vehicle and at least one parking area where a charger capable of charging the battery of the electric vehicle is installed, and the maximum number of reservations for the shared facility is set to the number of at least one parking area. The reservation system further includes a reservation price determination unit that determines a reservation price for the electric vehicle, the electric vehicle being one of a plurality of electric vehicles managed, and the reservation price determination unit may determine the reservation price for the electric vehicle based on the number of unreserved electric vehicles among the plurality of electric vehicles" (see abstract). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7046407 Summary of the Invention [Problem to be solved by the invention]

[0004] According to the reservation system 10 described in Patent Document 1, it is possible to reserve not only electric vehicles but also shared facilities including parking areas equipped with chargers capable of charging the batteries of electric vehicles (paragraph 0015). Furthermore, the shared facility database 122 includes a facility management number, facility location information, the maximum number of reservations, and the number of reservations available for each date (or the number of unreserved reservations) (paragraph 0036). However, Patent Document 1 does not consider a mechanism for accepting reservations while providing parking areas equipped with chargers to vehicles that have not made reservations. Therefore, the present invention provides a system that can accept reservations for charging spaces while providing charging spaces to vehicles that have not made reservations. [Means for solving the problem]

[0005] In order to solve the above problems, for example, the configurations described in the claims are adopted. The present application includes multiple means for solving the above-mentioned problems, and one example is a reservation management device that includes a status acquisition unit that acquires information regarding the presence or absence of a vehicle in a charging space, a reservation management unit that determines whether the usage status of the charging space is available for reservation based on the information acquired by the status acquisition unit and accepts a reservation for the charging space if it is available for reservation, and a regulation unit that, when the reservation is accepted by the reservation management unit, sets a regulation device installed in the charging space to a state that regulates the use of the charging space. [Effects of the Invention]

[0006] According to the present invention, it is possible to provide a system that can accept reservations for charging spaces while providing charging spaces to vehicles that have not reserved them. As a result, the use of charging spaces is guaranteed for vehicles that have made reservations, while vacant charging spaces can be used by vehicles that have not made reservations. This ultimately increases the utilization rate of charging spaces. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 shows an example of the overall configuration of a reservation management system 100. [Figure 2] FIG. 2 shows an example of the hardware configuration of the charging space management device 101. [Figure 3] FIG. 3 shows an example of the hardware configuration of the management server 102. [Figure 4]FIG. 4 shows an example of the hardware configuration of the user terminal 103. [Figure 5] FIG. 5 is an example of user information 500. [Figure 6] FIG. 6 is an example of parking lot management information 600. [Figure 7] FIG. 7 is an example of detailed parking lot information 700. [Figure 8] FIG. 8 is an example of reservation information 800. [Figure 9] FIG. 9 is an example of a state representation 900 of a charging space. [Figure 10] FIG. 10 is an example of state information 1000. [Figure 11] FIG. 11 is an example of telemetry information 1100. [Figure 12] FIG. 12 is an example of command information 1200. [Figure 13] FIG. 13 is an example of the configuration information 1300. [Figure 14] FIG. 14 is an example of a plan view of a charging space 1400. [Figure 15] FIG. 15 is a schematic diagram illustrating a regulating device according to one embodiment in (A) a non-regulating state and (B) a regulating state. [Figure 16] FIG. 16 is an example of a reservation management flow 1600. [Figure 17] FIG. 17 shows an example of a reservation acceptance flow 1700. [Figure 18] FIG. 18 shows an example of a warehousing process flow 1800. [Figure 19] FIG. 19 shows an example of a charging / retrieval process / reservation completion flow 1900. [Figure 20] FIG. 20 shows another example of a reservation acceptance flow 2000. [Figure 21] FIG. 21 shows another example of the charging / retrieval process / reservation completion flow 2100. [Figure 22] 22(A) to 22(C) are examples of screens on the touch panel display of the charger 2. FIG. [Figure 23] FIG. 23 is an example of a state transition diagram 2300. [Figure 24] FIG. 24 is an example of a state management flow 2400. [Figure 25] FIG. 25 is an example of a state management flow 2500. [Figure 26] FIG. 26 is an example of a time-based billing flow 2600. [Figure 27] FIG. 27 is an example of a reservation screen 2700. [Figure 28] FIG. 28 is an example of a reservation screen 2800. [Figure 29] FIG. 29 is an example of a reservation screen 2900. [Figure 30] FIG. 30 shows an example of a reservation mode selection acceptance screen 3000. [Figure 31] FIG. 31 is an example of a confirmation screen 3100. [Figure 32] FIG. 32 is an example of a reservation confirmation screen 3200. [Figure 33] FIG. 33 is an example of a reservation screen 3300. [Figure 34] FIG. 34 is an example of a charging status display screen 3400. [Figure 35] FIG. 35 shows an example of a temporary exit status display screen 3500. [Figure 36] FIG. 36 shows an example of a usage completion screen 3600. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, embodiments will be described with reference to the drawings. In each drawing, components having the same functions may be designated by reference numerals and may not be described in detail. [Example]

[0009] [Reservation Management System] FIG. 1 is a diagram illustrating an example of a configuration of a reservation management system 100 according to an embodiment. The reservation management system 100 according to the present technology is a system that manages reservations (hereinafter simply referred to as "reservations") for parking spaces (i.e., charging spaces) where chargers for electric vehicles such as electric vehicles (EVs) and plug-in hybrid vehicles (PHVs) are installed.

[0010] The reservation management system 100 includes one or more charging space management devices 101, one or more management servers 102, and one or more user terminals 103. The management server 102 is an example of a reservation management device in the present technology. The one or more charging space management devices 101 and the one or more user terminals 103 are each configured to be connectable to the one or more management servers 102 via a network. The network may be wired or wireless, and each terminal can send and receive information via the network.

[0011] The charging space management device 101, management server 102, and user terminal 103 of the reservation management system 100 may each be, for example, a portable terminal (mobile terminal) such as a smartphone, tablet, mobile phone, or personal digital assistant (PDA), or a wearable terminal such as glasses, a head-mounted terminal, a wristwatch, or clothing. These may also be stationary or portable computers, or servers located on the cloud or a network. In terms of functionality, they may also be VR (Virtual Reality) terminals, AR (Augmented Reality) terminals, or MR (Mixed Reality) terminals. Alternatively, they may be a combination of multiple of these terminals. For example, a combination of one smartphone and one wearable terminal may logically function as a single terminal. Other information processing terminals may also be used.

[0012] Each terminal of the reservation management system 100 includes a processor that executes an operating system, applications, programs, etc.; a main storage device such as RAM (Random Access Memory); an auxiliary storage device such as an IC card, hard disk drive, SSD (Solid State Drive), or flash memory; a communication control unit such as a network card, wireless communication module, or mobile communication module; input devices such as a touch panel, keyboard, mouse, audio input device, or input device that detects motion by capturing images from a camera; and output devices such as a monitor, display, printer, audio output device, or oscillator. The input devices may include sensors such as GPS, gyro sensors, and acceleration sensors. The output devices may also be devices or terminals that transmit information to be output to external monitors, displays, printers, or equipment.

[0013] The main memory stores various programs and applications (software modules), and the processor executes these programs and applications to realize each functional element of the overall system. Each module may be an independent program or application, or may be implemented as a subprogram or function within a single integrated program or application. Each module may also be implemented as hardware (hardware modules) by integrating circuits or using a microcomputer. Furthermore, each module may be located on a single terminal (including a management server) or may be distributed across two or more terminals (including management servers) connected to each other via a network.

[0014] In this specification, each module is described as a subject that performs processing, but in reality, the processing is carried out by a processor that processes various programs, applications, etc.

[0015] The auxiliary storage device stores various databases (DB). A "database" is a set of data that has been organized and collected so that it can accommodate any data manipulation (e.g., extraction, addition, deletion, overwriting, etc.) from a processor or an external computer. The auxiliary storage device is a functional element (storage unit) that stores one or more sets of data. There are no limitations on how the database is implemented; for example, it may be a database management system, spreadsheet software, or a text file such as XML or JSON.

[0016] [Charging space management device] FIG. 2 illustrates an example of the hardware configuration of the charging space management device 101. The charging space management device 101 is an element that manages the usage status of a charging space. The charging space management device 101 can be configured, for example, by a microcomputer. The charging space management device 101 includes a main storage device 201 and an auxiliary storage device 202. The charging space management device 101 also includes the processor 203, input device 204, output device 205, camera 206, and communication control unit 207 as described above.

[0017] The main memory device 201 stores programs and applications such as a charging space management module 211, a charging space status acquisition module 212, and a charging space regulation module 213. Each functional element of the charging space management device 101 is realized by the processor 203 executing these programs and applications stored in the main memory device 201.

[0018] The auxiliary storage device 202 stores information necessary for the operation of the reservation management system 100. For example, the auxiliary storage device 202 stores user information 500, parking lot detailed information 700, reservation information 800, etc. Details of this information will be described later. This information may be some or all of the information related to the charging space management device 101 out of the user information 500, parking lot detailed information 700, reservation information 800, etc. stored in the management server 102.

[0019] Each functional element of the charging space management device 101 will be described together with the configuration of the charging space 1400.

[0020] FIG. 14 is an example of a plan view of a charging space 1400. As shown in FIGS. 1, 2, and 14, the charging space 1400 is equipped with a parking area 150 for parking electric vehicles, a charging space management device 101, a charger 110, a detection device 120, a regulation device 130, and an alarm device 140. In this example, the charger 110 has a built-in power meter 111 and is connected to an external power source 112 via the power meter 111. The charging space management device 101 is connected to each of the charger 110, the detection device 120, the regulation device 130, and the alarm device 140 by wire or wirelessly, and is configured to be able to send and receive information to and from each of these devices.

[0021] As the charger 110, various types of chargers capable of supplying power to an electric vehicle (more specifically, a power source for driving an electric vehicle) can be used without any particular restrictions. For example, the charger 110 may be a normal charger with a rated output of less than approximately 10 kW (e.g., 3 to 6 kW), or a rapid charger with a rated output of approximately 10 kW or more (e.g., 50 kW). The charger 110 in this example is configured to be switchable between a chargeable state and an unchargeable state when the main power supply is turned on. A configuration (e.g., a selector switch) that switches the state of this charger 110 between a chargeable state and an unchargeable state can be an example of a regulating device that regulates the use of a charging space.

[0022] The detection device 120 detects the presence or absence of a vehicle in the parking area 150. The detection device 120 may be, for example, any one of various vehicle detectors, such as an infrared sensor, an ultrasonic sensor, a loop coil sensor, or a vehicle recognition imaging system, used alone or in combination of two or more. FIG. 14 shows an example in which the detection device 120 is an infrared sensor that can be easily retrofitted to an existing charging space. The detection device 120 detects the presence or absence of a vehicle in the parking area 150, for example, at predetermined time intervals (typically every 1 to 60 seconds, depending on the detection mechanism, for example, every 10 seconds). The detection result by the detection device 120 is acquired by the status acquisition module 312 of the charging space management device 101, or the detection device 120 transmits the result to the charging space management device 101. Although Figure 14 shows an example in which the detection device 120 is installed at the back of the parking area 150, it may also be installed at the entrance side, side, above, below (including within the slab) of the parking area 150 depending on the detection characteristics of the detection device 120, etc.

[0023] The regulating device 130 is an element that regulates the entry of vehicles into the parking area 150. FIG. 15 is a schematic diagram of the regulating device 130 according to one embodiment. The regulating device 130 includes a main body 132 and a plate-shaped regulating member 134 pivotally supported by the main body, and the regulating member 134 is configured to rotate about an axis X along the plate surface. The regulating device 130 is disposed on the entrance side of the parking area 150, and in the (A) unrestricted state, the regulating member 134 is in a horizontal position, allowing vehicles to enter the parking area 150. In the (B) restricted state, the regulating member 134 stands up, allowing the entry of vehicles into the parking area 150 to be restricted.

[0024] The notification device 140 is an additional component of the reservation management system 100 and is an element that notifies the usage status of a charging space. The notification device 140 may be a display device such as a display, LED lamp, or flip-flap display that can visually notify the usage status, or an audio notification device such as a speaker that can audibly notify the usage status, or both. The notification device 140 in this example is an LED display device that is configured to display various usage statuses by, for example, the LED's light color (here, red or green), light emission mode (e.g., on, off, flashing, etc.), text display, etc.

[0025] The charging space status acquisition module 212 of the charging space management device 101 acquires information indicating the presence or absence of a vehicle detected by the detection device 120 at a predetermined interval (for example, every 100 to 500 milliseconds). The charging space status acquisition module 212 stores the information indicating the presence or absence of a vehicle acquired from the detection device 120 in the auxiliary storage device 202.

[0026] The charging space management module 211 transmits information regarding the presence or absence of a vehicle, which is acquired by the charging space status acquisition unit, to the management server 102 at a predetermined cycle (for example, every several tens of seconds). Furthermore, the charging space management module 211 can transmit information to the management server 102 when the management server 102 requests information regarding the usage status of the charging space. Furthermore, when the charging space management module 211 receives an instruction from the management server 102 regarding the content to be reported by the notification device 140 (typically, a notification of the usage status of the charging space), the charging space management module 211 outputs information (instructions) regarding the notification content to the notification device 140.

[0027] The charging space regulation module 213 puts the regulation device 130 installed in the charging space into a state that regulates or cancels the regulation of the use of the charging space. For example, the charging space regulation module 213 outputs information (instructions) to the regulation device 130 to put it into a state (A) that allows vehicle entry or a state (B) that regulates vehicle entry. The charging space regulation module 213 can also output information (instructions) to the charger 110 to switch between a chargeable state and a non-chargeable state.

[0028] 14, the notification device 140 is provided integrally with the charging space management device 101. However, the notification device 140 may be provided integrally with the charger 110 or the regulating device 130, for example, or may be provided independently in a position that is easily visible to a user, such as near the entrance or above the back of the parking area 150. Furthermore, the charging space management device 101, the charger 110, the detection device 120, the regulating device 130, and the notification device 140 may each be provided independently, or two or more of them may be provided integrally.

[0029] [Administration Server] FIG. 3 illustrates an example of the hardware configuration of the management server 102. The management server 102 is an element that manages the reservation management system 100 of this embodiment. The management server 102 is configured, for example, by a server deployed on a cloud. The management server 102 includes a main storage device 301 and an auxiliary storage device 302. The management server 102 also includes the processor 303, input device 304, output device 305, and communication control unit 306 as described above.

[0030] The main memory device 301 stores programs and applications such as a user terminal management module 311, a status acquisition module 312, a reservation management module 313, and a regulation module 314. Each functional element of the management server 102 is realized by the processor 303 executing these programs and applications stored in the main memory device 301.

[0031] The auxiliary storage device 302 stores information necessary for the operation of the reservation management system 100. The auxiliary storage device 302 stores, for example, user information 500, parking lot management information 600, parking lot detailed information 700, reservation information 800, etc. Details of this information will be described later.

[0032] Each functional element of the management server 102 will now be described. The user terminal management module 311 manages the operation of the user terminal 103. The user terminal management module 311 cooperates with the user execution module 411 of the user terminal 103 to control the basic operations for reserving and using a charging space, which are executed in the user terminal 103 using the reservation management system 100.

[0033] For example, the user terminal management module 311 cooperates with the user execution module 411 to output (display) a login page for accessing a charging space reservation site provided by the management server 102, a user information management page, etc., on an output device 405 such as a display of the user terminal 103. The user terminal management module 311 also cooperates with the user execution module 411 of the user terminal 103, for example, to acquire input information entered from the user terminal 103 via these pages. The user terminal management module 311, for example, operates based on the acquired information (various types of information, instructions, etc.), and outputs (stores) the acquired information to the auxiliary storage device 302 as user information 500, etc.

[0034] The status acquisition module 312 acquires information regarding the presence or absence of a vehicle in the charging space. The status acquisition module 312 typically acquires information indicating the presence or absence of a vehicle sent from the charging space status acquisition module 212 of the charging space management device 101. In other words, the status acquisition module 312 monitors information regarding the presence or absence of a vehicle in the charging space via the charging space management device 101 (and the detection device 120). The acquired information is stored in, for example, the auxiliary storage device 302.

[0035] The reservation management module 313 is an element that accepts reservations for charging spaces depending on the usage status of the charging spaces. The reservation management module 313 determines whether the usage status of the charging spaces is available for reservation based on information acquired by the status acquisition module 312 from the user terminal 103, and if the usage status is available for reservation, the reservation management module 313 accepts a reservation for the charging space. The specific operation of the reservation management module 313 will be described later.

[0036] In this specification, the "reservable" state is expressed as "reservable" from the perspective of accepting reservations, but it is the same as the "available" state described below. For example, "available" can be read as "reservable."

[0037] The regulation module 314 manages the usage status of the charging space. When a reservation for a charging space is accepted by the reservation management module 313, the regulation module 314 sets the regulation device 130 installed in the charging space to a state in which the use of the charging space is restricted. The regulation module 314 controls the state of the regulation device 130 via, for example, the charging space management module 211. The specific operation of the regulation module 314 will be described later.

[0038] [User device] 4 shows an example of the hardware configuration of the user terminal 103. The user terminal 103 is a terminal operated by a user who uses the reservation management system 100, and is configured as a terminal such as a smartphone, tablet, laptop PC, or desktop PC. The user terminal 103 includes a main memory device 401 and an auxiliary memory device 402. The user terminal 103 also includes the processor 403, input device 404, output device 405, camera 406, and communication control unit 407 as described above.

[0039] The main memory device 401 stores programs and applications such as a user execution module 411 and a user reservation management module 412, and the processor 403 executes these programs and applications to realize each functional element of the user terminal 103.

[0040] The user execution module 411 controls the basic operations of the user terminal 103 when using the reservation management system 100. The user execution module 411, for example, works in cooperation with the user terminal management module 311 of the management server 102 to control the basic operations for reserving and using a charging space using the reservation management system 100.

[0041] For example, the user execution module 411 cooperates with the user terminal management module 311 of the management server 102 to output (display) a predetermined display screen such as a login page for a charging space reservation application (hereinafter, sometimes simply referred to as "app") or a map of the surrounding area of ​​the current location on an output device 305 such as a display of the user terminal 103.

[0042] The user reservation management module 412 accepts input from users regarding the reservation and use of charging spaces. For example, the user reservation management module 412 cooperates with the user terminal management module 311 of the management server 102 to send to the management server 102 input information, such as the charging space to be reserved, input by the user via the display screen or input device 304.

[0043] The auxiliary storage device 402 stores information necessary for the operation of the user terminal 103. For example, the auxiliary storage device 402 stores user information 500, reservation information 800, etc. This information may be part or all of the information related to the user terminal 103 from the user information 500, reservation information 800, etc. stored in the management server 102.

[0044] 5 to 8 show various types of information stored in the management server 102. Although not limited to this, it is assumed that some or all of this information is stored in a JSON format file. Some or all of this information may be configured to be stored in a relational database or a non-relational database.

[0045] FIG. 5 is an example of user information 500. The user information 500 is information about a user who uses the reservation management system 100. The user information 500 includes, for example, authentication information such as a user ID, a user display ID, a user name, an address, payment information, password information, and a login ID, and values ​​such as those shown as sample values ​​520 are entered for each field name 510.

[0046] The user ID is a symbol assigned to each user to identify them, and is automatically generated as a hash value or the like. Information about each user is basically linked to this user ID. The user display ID is a display ID for the user that is displayed on the screen of the management server 102, user terminal 103, etc., and can be set arbitrarily. The user name, address, and payment information are the name or title, address or location, and fee payment information for the user (including natural persons and corporations; the same applies below). The authentication information is authentication information for logging in to the reservation app to reserve and use a charging space and for user identity verification, and is not limited to password information, login ID, etc.

[0047] FIG. 6 is an example of parking lot management information 600. The parking lot management information 600 is information used to search for charging spaces (which may be charging parking lots with one or more charging spaces) registered in the reservation management system 100. The parking lot management information 600 includes, for example, a charging parking lot ID and information such as latitude and longitude as location information of the charging parking lot, with values ​​such as those shown in sample values ​​620 being entered for each field name 610. The charging parking lot ID is a symbol assigned to each charging parking lot to identify the charging parking lot, and is automatically generated as a hash value or the like. The location information is information that indicates the location of the charging parking lot, and typically includes information related to latitude and longitude. The location information may include other information such as altitude, and may be displayed in other formats such as simplified location information or relative location information.

[0048] FIG. 7 is an example of detailed parking lot information 700. The parking lot detail information 700 includes detailed information about charging parking lots registered in the reservation management system 100, and is associated with the parking lot management information 600 by the charging parking lot ID. The parking lot detail information 700 includes, for example, the charging parking lot ID, charging parking lot name, charging parking lot address, business hours, fees, number of charging spaces, charger type, number of available reservations, whether daily reservations are possible, daily reservation fees, website URL, charging space ID, and usage status, and values ​​such as those shown as sample values ​​720 are entered for each field name 710.

[0049] The number of charging spaces is the total number of charging spaces available in each charging parking lot. The charger type, number of charging spaces, and number of available reservations are the types of chargers installed in the charging spaces of each charging parking lot, the number of chargers installed, and the number of available reservations. The number of available reservations can be understood as the number of available (X1) charging spaces, which is the usage status of the charging spaces for each charging parking lot (described later). Charger types are typically rapid chargers or standard chargers, and information on the total number of installed chargers and the number of available reservations is included for each type. The daily reservation availability and daily reservation fee indicate whether reservations can be made on a daily basis and the reservation fee. The charging space ID is an ID used to identify each charging space in each charging parking lot and is automatically generated according to the information on the number of charging spaces. The usage status is information that indicates the usage status of each charging space and is determined and recorded sequentially by the reservation management module 313 based on information about the charging spaces acquired by the management server 102.

[0050] FIG. 8 is an example of reservation information 800. The reservation information 800 is information related to the reservation of a charging space accepted by the management server 102. The reservation information 800 includes, for example, a reservation ID, a parking lot ID, a parking space ID, a reserving user ID, a reservation type, whether charging is required, a charging type, a parking reservation date and time, a charging reservation date and time, and a reservation acceptance date and time, and values ​​such as those shown as sample values ​​820 are entered for each field name 810.

[0051] The reservation ID is a symbol assigned to each reservation to identify the reservation details. It is automatically generated as a hash value or the like and serves as a primary key referenced from other information. The parking lot ID indicates the reserved charging parking lot. The parking space ID indicates the reserved charging space in the charging parking lot and is determined by the management server at the time of reservation. The reservation user ID is the user ID of the user who made the reservation. The reservation type indicates the reservation format for the charging space in the reservation service. In this example, a "one-day reservation," which reserves a space on a one-day basis, or a "reservation," which reserves a space for up to one hour, can be selected. The reservation time can be set to a relatively short time, for example, 30 minutes to 3 hours. Charging necessity is information on whether a charger will be used (or whether its use is permitted) in the charging space, and the charging type is the type of charger 110 to be used if a charger is used. The charging type can be selected when both a standard charger and a rapid charger are installed in a charging parking lot. When only one of a standard charger or a rapid charger is installed in a charging parking lot, the type of the installed charger is automatically recorded or does not need to be recorded. The parking reservation date and time is information relating to the reservation date and time of the charging space, the charging reservation date is information relating to the reservation date and time of the charger, and the reservation acceptance date and time is information relating to the date and time when the management server 102 accepted the reservation.

[0052] Hereinafter, a method for reserving a charging space in a charging parking lot using the reservation management system 100 will be described. The charging parking lot to be reserved is, for example, a charging parking lot attached to a public facility such as a shopping mall or a sports facility. There are two ways to use the charging space: "on-the-spot use," which uses the charging space without a reservation using a reservation app provided by the reservation management system 100, and "reserved use," which uses the charging space after making a reservation. The reservation type can be selected, for example, from a "one-day reservation" that makes a reservation on a one-day basis, to a "hold" that reserves the space for up to one hour. Making a "hold" reservation allows, for example, a user to reserve a charging space at a nearby sports facility from the comfort of their own home, thereby securing a parking space when visiting the sports facility and charging their vehicle while using the sports facility. With "on-the-spot use," which does not require a reservation, a vehicle without a reservation can immediately enter an unreserved charging space at the charging parking lot, park, and charge. In this embodiment, charging using a quick charger is charged by the hour.

[0053] 16 is an example of a reservation management flow 1600. The reservation management system 100 typically reserves and manages charging spaces in accordance with each step (steps 1610 to 1660) of the reservation management flow 1600. Hereinafter, for example, "step 1610" will be indicated as "S1610."

[0054] [Charging space status detection (S1610)] FIG. 17 shows an example of a reservation acceptance flow 1700. In the first embodiment, the regulating device 130 installed in each charging space enters a regulated state in which it restricts vehicle entry when no reservation has been made (S1702), and the notification device 140 indicates that the charging space is available (S1704). Furthermore, in each charging space, the detection device 120 detects the presence or absence of a vehicle in the charging space at predetermined intervals. The charging space status acquisition module 212 acquires, for example, information regarding the presence or absence of a vehicle from the detection device 120 at predetermined intervals (S1706). The charging space management module 211 transmits the information acquired by the charging space status acquisition module 212 to the management server 102 at predetermined intervals (for example, every 20 seconds) (S1708). The status acquisition module 312 of the management server 102 acquires the information regarding the presence or absence of a vehicle and records it in, for example, the auxiliary storage device 302. This allows the reservation management module 313 to determine whether a vehicle is present in each charging space. The detection of the usage status by the status acquisition module 312 can be performed, for example, during the business hours of each charging parking lot. The usage status will be described in detail later.

[0055] [Reservations (S1620)] A user who wants to reserve a charging space first launches the reservation app on the user terminal 103 (S1710). This causes the user execution module 411 of the user terminal 103 to connect to the management server 102. The user terminal management module 311 of the management server 102 cooperates with the user execution module 411 of the user terminal 103 and the like to execute processes such as user login.

[0056] There are various conceivable methods for reserving a charging parking lot. For example, a reservable charging parking lot can be specified from among charging parking lots close to the current location of the user terminal 103. Then, the user execution module 411 transmits current location information of the user terminal 103 to the management server 102 (S1712). As a result, the reservation management module 313 of the management server 102 displays, on the output device 405 such as a display of the user terminal 103, map information about the area around the current location, as well as information about reservable charging parking lots that exist on the map. A reservable charging parking lot is a charging parking lot for which, at the time of display, it is determined that the number of reservable charging parking lots exceeds zero because the detection device 120 has acquired information indicating that there are no vehicles there (S1714, 1716). Management of the number of reservable charging parking lots will be described later.

[0057] FIG. 27 shows an example of a reservation screen 2700. Round marks (charging parking lot marks) displayed on the map of the reservation screen 2700 indicate the locations of charging parking lots that can be reserved. For example, the user terminal management module 311 displays a lightning bolt mark within the charging parking lot mark for charging parking lots equipped with quick chargers. The user terminal management module 311 also accepts the selection of a charging parking lot mark displayed on the display via the user terminal 103. As a result, a simple information window 2810 for the selected charging parking lot is displayed overlaid on a surrounding map, as shown in FIG. 28, for example. The simple information window 2810 displays, for example, the selected charging parking lot as well as simple information about nearby charging parking lots. This makes it easy to obtain information about nearby charging parking lots, for example, when the conditions of the selected charging parking lot do not meet the user's needs. When the user terminal management module 311 accepts the selection of a charging parking lot that the user wishes to reserve from among the charging parking lots displayed in the simple information window 2810, the user terminal 103 displays a reservation screen 2900 for the selected charging parking lot, as shown in FIG. 29.

[0058] The user terminal management module 311 displays, for example, a charging type selection button 2910, a reservation button 2920, and a start charging button 2930 on a reservation screen 2900. The user selects the reservation button 2920 when making a reservation for a charging parking space, and selects the start charging button 2930 when charging immediately without making a reservation. When the user terminal management module 311 accepts the selection of the charging type and the selection of the reservation button 2920 via the user terminal 103, the user terminal management module 311 then displays, for example, a reservation mode selection acceptance screen 3000 shown in FIG. 30 on the user terminal 103. The user terminal management module 311 displays a one-day reservation selection button 3010 and a reservation selection button 3020 on the reservation mode selection acceptance screen 3000. Then, by accepting the selection of either of these buttons 3010 or 3020, the user terminal management module 311 displays a reservation application content confirmation screen 3100 as shown in FIG. 31. When the confirmation screen 3100 in FIG. 31 is scrolled down, the reservation button is displayed. For example, by accepting the selection of this reservation button, the user terminal management module 311 accepts a reservation application for the selected charging parking lot with the selected charging type and reservation mode (S1720). In this example, a reservation application for quick charging is accepted.

[0059] Here, if the number of available reservations for the charging parking lot exceeds zero at the time the reservation application is accepted, the reservation is confirmed, and the reservation management module 313 transmits information indicating the confirmation of the reservation to the user terminal 103 (S1722). The reservation management module 313 outputs, for example, a reservation confirmation screen 3200 as shown in FIG. 32 to the user terminal 103. As a result, the reserved charging space is reserved from the start of the reservation until the reservation limit time (for example, 60 minutes from 16:57 to 17:57), as shown in FIG. 32, for example. The user terminal management module 311 displays, for example, the reservation end time (here, "17:57") on the reservation confirmation screen 3200.

[0060] When the reservation is established, the reservation management module 313 records that the usage status of the charging space, which will be described later, has changed from reservable (X1) to reserved (X6). The reservation management module 313 also transmits information indicating that the notification device 140 has registered the reserved (X6) status for the charging space to the charging space management device 101 (S1724). Here, because the regulating device 130 is in a regulated state, instructions from the management server 102 to the regulating device are unnecessary and can be omitted. On the other hand, for example, to check the operation of the regulating device 130, the regulation module 314 may output information to the charging space management device 101 corresponding to the charging space in the reserved charging parking lot that the regulating device 130 will enter a regulated state (B) in which the regulating device 130 will regulate the use of the charging space. This initiates a reservation operation for the requested charging space (S1726). The charging space regulation module 213 outputs information indicating that the regulating device 130 will enter a regulated state in which the use of the charging space will be regulated to the regulating device 130 (S1728). Furthermore, the charging space management module 211 outputs information indicating that the usage status of the charging space has become reserved to the notification device 140 (S1730). Accordingly, the notification device 140 outputs information indicating that the charging space has become reserved (S1732).

[0061] On the other hand, if the number of available reservations for the charging parking lot is zero at the time of acceptance, the reservation is not made, and the reservation management module 313 transmits information indicating that the reservation has been rejected to the user terminal 103. A reservation may be rejected, for example, when another user makes a reservation for the charging parking lot, or when the charging parking lot begins to be used without a reservation, causing the number of available reservations to drop to zero. In this case, the reservation management module 313 accepts a reservation request for another charging parking lot from the user by, for example, displaying the reservation screen 2700 or 2800 again.

[0062] [Determining usage status] The reservation management module 313 of the management server 102 manages the usage status of each charging space (charging space ID) in each charging parking lot in approximately real time. FIG. 9 shows an example of a status representation 900 for each charging space in a charging parking lot. The status representation 900 also shows the status of the regulating device 130 and the notification device 140. The management server 102 manages the usage status of each charging space, for example, as 11 different states, X1 to X11, as shown in FIG. 9. Each usage status is represented by an example in the "Summary" column 930 in relation to the "No." column 910 and the "Status Description" column 920. The usage status of a charging space can change, for example, as shown in the state transition diagram 2300 in FIG. 23. The management server 102 manages the real-time usage status of an operating charging space, for example, as nine different states, X1, X3 to X10, as shown in FIG. 23.

[0063] The usage status of the charging space can be determined, for example, according to flows 2400, 2500, and 2600 shown in FIGS. 24 to 26. When accepting a reservation, the reservation management module 313 checks the usage status for each charging space in the charging parking lot for which a reservation has been requested, in a predetermined order, according to the status management flows 2400, 2500, and 2600. This makes it possible to determine whether or not a reservation for a charging space can be accepted for that charging parking lot. The order in which the usage status of each charging space in the charging parking lot is checked can be arbitrary, and can be, for example, from the earliest charging space in the sequence (permutation) of IDs (for example, from the smallest ID number).

[0064] When determining the usage status of the charging space, the reservation management module 313 first determines whether the current time is within business hours (S2410), as shown in the status management flow 2400. If the current time is not within business hours (N in S2410), the reservation management module 313 records that the charging space in the charging parking lot is "outside business hours (NOT BUSINESS HOURS)" (X2). Next, the reservation management module 313 determines whether the type of charger for which a reservation has been requested is a rapid charger (S2420). If the reservation type for the charger 110 is a rapid charger (Y in S2420), the reservation management module 313 records that when the charging space is used, it is necessary to determine whether or not to perform time-based charging according to the time-based charging flow shown in FIG. 26 (S2430).

[0065] Next, the reservation management module 313 determines whether there is a vehicle in the charging space (S2440). If there is no vehicle (N in S2440), the reservation management module 313 next determines whether the vehicle is temporarily leaving (S2450). If the vehicle is temporarily leaving (Y in S2450), the reservation management module 313 records the usage status as "temporarily leaving (LEAVING)" (X9). If the vehicle is not temporarily leaving (N in S2450), the reservation management module 313 next determines whether the vehicle has checked in (S2460). Checking in means that use of the charger 110 installed in the charging space is permitted, and the vehicle can check in by performing the check-in operation described below. If the vehicle has checked in (Y in S2460), the usage status is recorded as "checked in (CHECKED IN)" (X5).

[0066] If the user has not checked in (N in S2460), the reservation management module 313 then determines whether the reservation count exceeds 0 (S2470). The reservation count is the number of reservations currently applied for this charging parking lot. If the reservation count exceeds 0, it means that a reservation has been applied for this charging parking lot. If the reservation count is 0, no reservation has been applied for this charging parking lot and the charging space is available, so the reservation management module 313 records that the usage status of this charging space is "available (IDLE)" (X1). If the reservation count exceeds 0 (i.e., at the time of reservation acceptance), the reservation management module 313 accepts a reservation for this currently available charging space and decrements the reservation count for the charging parking lot (or quick charger) by one (S2480). For example, if the reservation count is 2, the reservation count is decremented by one and stored as 1. Additionally, the reservation management module 313 records that the usage status of this charging space is "RESERVED" (X6).

[0067] This reservation count is carried over when determining the usage status of the next charging space. Therefore, by repeating the above usage status determination until the reservation count reaches zero, the reservation management module 313 can accept reservations for charging spaces while determining the usage status for each charging space. In addition, by checking the usage status of all charging spaces in each charging parking lot, the number of available charging spaces in each charging parking lot (i.e., the number of charging spaces whose usage status is "available (IDLE)" (X1)) can be obtained. For charging parking lots that are equipped with both rapid chargers and normal chargers, it is recommended to determine the usage status for each type of charger 110.

[0068] Furthermore, when determining whether or not a vehicle is present in the charging space (S2420), if there is no vehicle (N in S2420), the reservation management module 313 determines whether or not the vehicle is temporarily leaving, as shown in FIG. 25 (S2510). If the vehicle is temporarily leaving (Y in S2510), the reservation management module 313 records that the usage status is "preparing to leave (LEAVING AND OCCUPIED)" (X10). If the vehicle is not temporarily leaving (N in S2510), the reservation management module 313 then determines whether or not the vehicle has checked in (S2520). If the vehicle has checked in (Y in S2520), the reservation management module 313 records that the usage status is "OCCUPIED" (X4).

[0069] Furthermore, when charging using a rapid charger (Y in S2410), the reservation management module 313 measures the charging time using the rapid charger. The reservation management module 313 then determines whether the charging time using the rapid charger is within a predetermined time limit (S2620) in accordance with the time-based charging flow shown in FIG. 26. If it is within the time limit (Y in S2620), the reservation management module 313 monitors the charging time until rapid charging is completed (Y in S2610). The usage status is recorded as "OCCUPIED" (X4). If the charging time using the rapid charger exceeds the predetermined time limit (N in S2620), the reservation management module 313 next determines whether the charging time is within the charging start time at which charging begins (S2630). If it is within the charging start time (Y in S2630), the reservation management module 313 records the usage status as "CHARGING TIME OUT" (X7). If it is not within the charging start time (N in S2630), the reservation management module 313 records that the usage status is "Charging (SURCHARGING)" (X4).

[0070] When the reservation management module 313 receives information indicating that some abnormality has occurred in a charging space, it records that the usage status is "Other (UNKNOWN)" (X11). Through the above procedure, the reservation management module 313 can distinguish between 11 usage statuses, X1 to X11, for each charging space. When the reservation management module 313 receives information indicating that the status of each charging space has changed, it sequentially records (rewrites) the usage status of each charging space after the change, for example, according to the transition diagram in FIG. 23.

[0071] 9 includes a charging availability column 940, a regulating device column 950, and an alarm device column 960. The charging availability column 940 shows an example of control as to whether the charger is in a charging availability state when the charging space is in the state shown in the state display column 920. The regulating device column 950 shows an example of control as to whether the regulating device 130 is in a regulated state when the charging space is in the state shown in the state display column 920. The alarm device column 960 shows the LED light color and light emission mode (in parentheses) when the charging space is in the state shown in the state display column 920. Note that a column that does not state (flashing) as the light emission mode means that the LED is lit. However, the control modes of the charger, regulating device 130, and alarm device 140 are not limited to this.

[0072] [Transmission information] 10 to 13 show information transmitted and received between the management server 102 and the charging space management device 101. FIG. 10 is an example of state information 1000. The state information is information related to the configuration of the charging space management device 101, and is transmitted from the charging space management module 211 of the charging space management device 101 to the management server 102 at predetermined intervals (e.g., every 20 seconds). The state information includes information shown in a key field (KEY) 1010, and information as shown in a description field (DESCRIPTION) 1040 is entered in the format shown in an "M / O" field 1220 and a "T" field 1230. Note that "M" in the "M / O" field 1220 indicates required data, and "O" indicates optional data. Furthermore, "T" in the "T" field indicates a data type, and the value of this field, "O", indicates an object type, "S" a string type, "N" a number type, "NA" a number array type, and "B" a Boolean type.

[0073] 11 is an example of telemetry information 1100. The telemetry information 1100 is information relating to the status of the charging space, etc., and is sent (updated) from the charging space management module 211 of the charging space management device 101 to the management server 102 (1) when a connection between them is established, or (2) when there is a change in the content. The state information includes information shown in a key column (KEY) 1110, and information of the content shown in a description column (DESCRIPTION) 1140 is entered in the format shown in an "M / O" column 1220 and a "T" column 1230.

[0074] The telemetry information 1100 includes error information for the regulating device 130, the detecting device 120, etc. In the following cases, for example, if the charging space is already reserved, the management server 102 notifies the user that the reservation is canceled and performs the cancellation process described below. When the regulating device 130 is instructed to enter the regulated state, an abnormality occurs in which the regulating member 134 does not enter the correct regulated state (the raising operation of the regulating member 134 does not complete) due to, for example, the regulating member 134 coming into contact with an obstacle. When the regulating device 130 was instructed to enter the regulated state or the released state, the completion of the operation was confirmed, but the result was not the expected state (the regulating member 134 was not in the raised state). When the regulating device 130 is instructed to enter a regulated state or a deregulated state, the management server 102 does not receive a notification that the regulating device 130 has completed its operation within 10 seconds or 30 seconds, respectively (in this case, a malfunction of the communication control unit 207 is suspected). When the management server 102 receives information informing the user of an abnormality caused by a person who has confirmed that the detection device 120, the regulation device 130, the alarm device 140, etc., is malfunctioning, However, the conditions for performing the cancellation process are not limited to the above example.

[0075] 12 is an example of command information 1200. The command information 1200 is information sent from the management server 102 to the charging space management device 101 when necessary, and is information that instructs the operation of the charging space management device 101 and each device installed in the charging space. The command information includes information shown in a key column (KEY) 1210, in the format shown in an "M / O" column 1220 and a "T" column 1230, and has information of the content shown in a description column (DESCRIPTION) 1240 entered therein.

[0076] FIG. 13 shows an example of configuration information 1300. The configuration information 1300 is setting information for the charging space management device 101 and is sent from the management server 102 to the charging space management device 101. The configuration information 1300 is recorded in the auxiliary storage device 302 of the management server 102 and can be actively acquired from the charging space management device 101. The charging space management device 101 also records the acquired configuration information 1300 in the auxiliary storage device 202. When the configuration information 1300 is changed, the charging space management device 101 updates the setting values ​​by, for example, restarting the device as necessary. The configuration information 1300 includes information shown in a key column (KEY) 1310, and has information of the content shown in a description column (DESCRIPTION) 1340 entered in the format shown in an "M / O" column 1320 and a "T" column 1330.

[0077] [Warehouse Receipt Processing (S1630)] FIG. 18 shows an example of a warehousing process flow 1800. A user who has reserved a charging space drives their vehicle to the reserved charging space in the charging parking lot by the end of the reservation period. During this reservation period, the regulating device 130 maintains a state in which use of the charging space is restricted (S1802), and the notification device 140 displays that the charging space has been reserved (S1804). The detection device 120 also detects whether a vehicle is present in the charging space at predetermined intervals, and the charging space status acquisition module 212 acquires the result (S1806). The charging space management device 101 also transmits information regarding the presence or absence of a vehicle acquired by the charging space status acquisition module 212 to the management server 102 (S1808).

[0078] When the user arrives at the reserved charging parking lot by vehicle (S1810), the user selects the arrival notification button 3210 displayed on the reservation confirmation screen 3200 (see FIG. 32) and transmits arrival information to the management server 102 (S1812). When the user terminal management module 311 of the management server 102 acquires the arrival information from the user terminal 103, the user terminal management module 311 displays information about the reserved charging spaces on the display of the user terminal 103 (S1814). The user terminal management module 311 displays information about the reserved charging spaces to the user by displaying a check-in screen 3300, for example, as shown in FIG. 33, on the user terminal. In this embodiment, for example, three charging spaces, charging space Nos. 1 to 3, are in a reserved (X5) state, and the user can select and use any one of these three charging spaces.

[0079] The user moves to one of the reserved charging spaces based on the information displayed on the check-in screen 3300 and checks in via the user terminal 103. For example, the check-in screen 3300 allows the user to select the number of one of three reserved charging spaces using a select box 3310. The user selects the number of the charging space they wish to use and selects the send button 3320. This allows the check-in information for the charging space to be sent to the management server 102 (S1822). Note that at this time, for example, by sending the check-in information together with a user ID, the user terminal management module 311 can authenticate whether the user is the same user who reserved the charging space (S1824). In this way, when there are multiple reserved charging spaces, allowing the user to select the charging space to use allows the user to select a charging space that is convenient for parking their vehicle, for example, thereby increasing user satisfaction.

[0080] The user terminal management module 311 accepts input from the user via the user terminal 103, and can confirm that the user is the reserving user if the check-in information accepted from the user matches the check-in information transmitted to the charging space management device 101 (S1824). This allows the user to use the charging space, and check-in is completed. The user terminal management module 311 records that the usage status of the charging space has changed from reserved (X6) to checked-in (X5). However, the method of user authentication is not limited to this, and may be, for example, authentication between the user terminal 103 and the charging space management device 101 (e.g., authentication using a QR code (registered trademark)).

[0081] Various methods of user authentication can be considered. As another example, the user terminal management module 311 transmits check-in information (e.g., the number of any one of the charging spaces to be used by the user) to the charging space management device 101 (S1816). Next, the charging space management module 211 transmits the received check-in information to a display (an example of the notification device 140) of the charging space management device 101 for display (S1818, S1820). The user visually confirms the check-in information displayed on the display, and then inputs or selects the check-in information on the user terminal 103 and transmits it to the management server 102 (S1822). The management server 102 can also perform user authentication if the check-in information transmitted to the charging space management device 101 matches the check-in information received from the user terminal 104. According to this method, a charging space to be used is designated for each user. Therefore, in the unlikely event that two or more reserved users arrive at a charging parking lot at the same time, it is possible to avoid a situation where the charging spaces they want to use overlap.

[0082] When the user has completed check-in, the restriction module 314 outputs information to the charging space management device 101 to lift the restriction on use of the charging space (S1826). When the charging space management device 101 receives information regarding the lifting of the restriction on use of the charging space, the charging space restriction module 213 transmits information to the restriction device 130 to lift the restriction (S1828), and the restriction device 130 enters a restriction-lifting state (A) (S1830). In addition, the reservation management module 313 outputs information indicating that the charging space is in a checked-in state to the charging space management device 101 (S1826). Then, the charging space management module 211 transmits information indicating that the charging space is in a checked-in state to the notification device 140 (S1832), and the notification device 140 displays the checked-in state (S1834). This allows the user to park the vehicle in the charging space.

[0083] When the user parks the vehicle in the charging space (S1836), the detection device 120 detects that there is a vehicle in the charging space. Then, the charging space status acquisition module 212 acquires information indicating that there is a vehicle in the charging space from the detection device 120 (S1838), and the charging space management module 211 sends the acquired information to the management server 102 (S1840). Upon acquiring the information indicating the presence of a vehicle, the user terminal management module 311 of the management server 102 records that the usage status of the charging space has changed from the checked-in (X5) status to the chargeable (X6) status. This completes the parking process (S1842).

[0084] [Charging (S1640)] FIG. 19 shows an example of a charging / retrieval process / reservation completion flow 1900. When the usage status of the charging space becomes the chargeable (X6) status, the regulation module 314 transmits information indicating that the charger is enabled to supply power to the vehicle to the charging space management device 101 (S1902). The charging space regulation module 213 transmits the acquired information enabling the charger to supply power to the charger 110 (S1904), and the charger 110 is enabled to supply power to the vehicle (S1906). For example, if the charging connector of the charger 110 is equipped with a locking mechanism, the charging space regulation module 213 releases the locking mechanism only when the charger is in the chargeable (X6) status. Furthermore, for example, if the charger 110 has a sleep mode that suspends power supply, the charging space regulation module 213 releases the sleep mode when the charger is in the chargeable (X6) status.

[0085] Furthermore, the user terminal management module 311 transmits information indicating that the usage status of the charging space has become a charging-enabled (X6) status to the charging space management device 101 (S1902). The charging space regulation module 213 transmits the acquired information enabling the charger to supply power to the notification device 140 (S1908), and the notification device 140 displays that the charger is in a charging-enabled status (S1910). This allows the user to know that charging to the vehicle is now possible, and to charge as needed (S1912).

[0086] 22(A) to 22(C) are examples of screens on the touch panel display of the charger 110. FIG. When charging, the user can, for example, directly operate the charging space management device 101. For example, FIG. 22(A) shows the initial screen of the charger 110, and the charging operation can be started by selecting the charging button. FIG. 22(B) shows an operation guide screen of the charger 110. Following the operation guide, the user removes the charging connector from the charger 110 and attaches it to the charging port of the vehicle. Charging then begins by pressing the start button on the guide screen. FIG. 22(C) shows a guide screen of the charger 110 during charging. Generally, charging using the charger 110 automatically stops when the battery is fully charged or when a predetermined charging time has elapsed. If the user wishes to stop charging midway, the user can press the stop button on the guide screen to stop charging before the battery is fully charged or the predetermined charging time has elapsed. After charging, the charging connector is removed from the charging port of the vehicle and attached to the charging connector holder of the charger 110.

[0087] [Outbound Processing (S1650)] When the user has finished using the charging space, the user causes the vehicle to leave (exit) the charging space (S1914). The detection device 120 then detects that there is no vehicle in the charging space. The charging space status acquisition module 212 acquires information indicating that there is no vehicle from the detection device 120 (S1916) and sends this information to the status acquisition module 312 (S1918). Upon acquiring the information indicating that there is no vehicle, the user terminal management module 311 records that the usage status of the charging space has changed from a charging available (X6) status to a reservation available (X1) status. Accordingly, the user terminal management module 311 increases the number of reservations available for the rapid chargers in this charging parking lot by one.

[0088] Furthermore, the regulation module 314 transmits information to the charging space management device 101 to place the regulating device 130 in a regulated state (S1920). When the charging space regulation module 213 receives the information to place the regulating device 130 in a regulated state, it transmits information to place the regulating device 130 in a regulated state (S1922), and the regulating device 130 enters a regulated state (B) (S1924). Furthermore, the regulation module 314 transmits information indicating that power supply from the charger to the charging space management device 101 is enabled (S1920). The charging space regulation module 213 transmits the acquired information to the charger 110 to disable power supply from the charger, and regulates power supply from the charger 110 to the vehicle.

[0089] Furthermore, the user terminal management module 311 transmits information to the notification device 140 of the charging space management device 101 indicating that the charging space is available for use (S1920). The charging space management module 211 transmits the received information to the notification device 140 (S1926), and the notification device 140 displays that the charging space is available for use (S1928).

[0090] [Reservation completion process (S1660)] FIG. 36 shows an example of a usage completion screen 3600. Once the unloading process is complete, the user terminal management module 311 settles the charging space usage fee. As an example, because regular charging generally employs constant current charging, the time during which the vehicle is in the chargeable (X6) state can be settled as charger usage time. Note that while rapid charging generally employs constant current and constant voltage charging, constant voltage charging is performed after the charging rate has reached a high level. Therefore, the time during which the vehicle is in the chargeable (X6) state can be settled as charger usage time, just like regular charging. Once settlement is complete, the user terminal management module 311 records that the reservation for the charging space has been completed.

[0091] [Cancellation process] Note that a charging space reservation may be canceled due to a change in the user's schedule, etc. It is also possible that the user does not arrive at the reserved charging parking lot within the reserved time due to, for example, a long travel time. If the user terminal management module 311 does not receive at least one of arrival information and check-in information within the reserved time, it determines that the reservation of the charging space has been canceled. Furthermore, a reserved charging space may become unavailable due to, for example, a malfunction of the regulating device 130 or the detection device 120 (see FIG. 11 ). When a reservation cancellation request is received for a reserved charging space or when a reservation is canceled, the user terminal management module 311 records, from the user terminal 103, that the usage status of the charging space has changed from reserved (X6) to available for reservation (X1). Then, the process from S1920 onward in the exit process is executed. The cancellation of the reservation is then recorded.

[0092] [Temporary Exit Processing] After using the charging space, payment is made as necessary when exiting the charging space, for example, as described above. However, the reservation management system 100 may also be configured to allow "temporary exit," which allows a user to temporarily exit from the charging available (X3) state without payment, as shown in FIG. 34. In this case, the charging space reservation status can be maintained even while exiting.

[0093] Note that a vehicle in the chargeable (X3) state can temporarily exit the space without paying. To temporarily exit, the user selects, for example, a temporary exit button 3410 displayed on the charging status display screen 3400. This causes the user terminal 103 to transmit information indicating that the charging space will not be used temporarily to the management server 102. When the management server 102 receives the information indicating that the charging space will not be used temporarily, the user terminal management module 311 records that the usage status of the charging space has changed from chargeable (X3) to ready for temporary exit (X10). The regulation module 314 restricts power supply to the vehicle from the charger. Note that, at this point, the detection device 120 has detected that a vehicle is present in the charging space. Furthermore, the user terminal management module 311 can display, on the user terminal 103, a temporary exit status display screen 3500, such as that shown in FIG. 35 .

[0094] When the vehicle temporarily exits the charging space and the detection device 120 detects that there is no vehicle in the charging space, the detection device 120 transmits information indicating that there is no vehicle to the charging space management device 101. The charging space management module 211 transmits information indicating that there is no vehicle to the management server 102. When the user terminal management module 311 acquires the information indicating that there is no vehicle, it records that the usage status of the charging space has changed from preparing to temporarily exit (X10) to temporarily exiting (X9). In addition, the user terminal management module 311 transmits information indicating that the usage status of the charging space has become temporarily exiting (X9) to the charging space management device 101. When the charging space management device 101 receives the information indicating that the usage status has become temporarily exiting (X9), the charging space regulation module 213 transmits information to the regulating device 130 to change the state to restrict vehicle entry, and the regulating device 130 enters a regulating state (B). Furthermore, the charging space management module 211 transmits information indicating that the charging space is being temporarily vacated to the notification device 140, and the notification device 140 displays the information indicating that the charging space is being temporarily vacated. This allows the charging space to be reserved and restricts the entry of other vehicles even when there is no vehicle in the charging space.

[0095] When returning the vehicle to the charging space, the user selects, for example, the re-entry button 3510 displayed on the temporary exit status display screen 3500. As a result, information indicating that the vehicle will be re-entered into the charging space is sent from the user terminal 103 to the management server 102. When the management server 102 acquires the information indicating re-entry, the user terminal management module 311 records that the usage status of the charging space has changed from temporary exit (X9) to check-in (X5). Therefore, from this point on, the entry process can be performed according to S1826 to S1842 above.

[0096] [Hourly Charge] A quick charger converts power into high-voltage direct current inside the charger and sends it to the vehicle, allowing for full charging in a short time, but the charging time is limited to protect the battery and equipment. Therefore, the reservation management system 100 may be configured to terminate quick charging after a predetermined time (e.g., 60 minutes from the start of charging). Furthermore, if a predetermined exit time (e.g., 75 minutes from the start of charging) is exceeded after quick charging, an overtime fee may be charged for the exceeded time.

[0097] In this case, as already described, the user terminal management module 311 determines the usage status of the charging space according to the billing flow in Fig. 26, and if there is a change in the usage status, records the changed usage status. That is, if the charging time exceeds a predetermined time limit, the usage status is recorded as having changed from available for charging (X3) to occupied (X4), and for example, information indicating occupied (X4) is transmitted to the charging space management device 101, causing the notification device 140 to display that the usage status of the charging space is occupied (X4). Also, if the charging time exceeds a predetermined billing start time, the usage status is recorded as having changed from occupied (X4) to time limit exceeded (X7), and for example, information indicating time limit exceeded (X7) is transmitted to the charging space management device 101, causing the notification device 140 to display that the usage status of the charging space is time limit exceeded (X7).

[0098] [Using charging spaces without reservations 1] In addition to the above-described reservation, charging spaces can also be used without a reservation. In this case, an unreserved user applies for use of the charging parking lot using, for example, an app provided by the reservation management system 100 at the charging parking lot. For example, the unreserved user applies for use by selecting a charger type using the charging type selection button 2910 on the charging parking lot reservation screen 2900 shown in FIG. 29 and then selecting the start charging button 2930. When the user terminal management module 311 accepts a usage application from an unreserved user, it determines an available charging space according to the status management flow 2400 shown in FIG. 24 and notifies (displays) the determined charging space on, for example, the user terminal 103 of the unreserved user. The unreserved user then checks in at the notified charging space. As a result, the user terminal management module 311 determines that the usage status of the charging space by the unreserved user is the same as that of the reserved user (see FIG. 23). Thereafter, the unreserved user can use the charging space in the same way as the reserved user.

[0099] [Using charging spaces without reservations 2] Although the management server 102 monitors the usage status of each charging space at a predetermined interval and timing, an unreserved user may enter a charging space. For example, a reserved user may use a charging space and then exit the charging space at approximately the same time as an unreserved vehicle enters the charging space. In such a case, as indicated by the dotted line in the state transition diagram 2300 in FIG. 23 , the user terminal management module 311 determines that the usage status of the charging space by the unreserved user is occupied. The unreserved user can change the usage status to charging available by checking in with their vehicle parked in the charging space. Therefore, for example, the user terminal management module 311 outputs information to the charging space management device 101 of the occupied charging space, via the notification device 140, to display a message prompting the user to check in. The charging space management module 211 then outputs information prompting the user to check in to the notification device 140, and the notification device 140 displays the message prompting the user to check in. As a result, when the user checks in, the user terminal management module 311 determines that the usage status of the charging space by the unreserved user has changed from occupied (X4) to charging available (X3) (see FIG. 23). Furthermore, the unreserved user can then use the charging space in the same way as the reserved user.

[0100] [Action and effect] The reservation management system 100 according to the present technology determines whether a charging space is available for reservation based on information about the presence or absence of a vehicle in the charging space, and accepts a reservation if the charging space is available for reservation. Furthermore, when a reservation is accepted, a regulating device installed in the charging space is set to a state that restricts use of the charging space. With this configuration, for example, it is possible to accept a reservation for only the charging space without a reservation for an electric vehicle. Furthermore, it is possible to accept a reservation for the charging space while providing the charging space to vehicles that have not made a reservation. As a result, for example, a user can reserve the charging space even when using the charging space with their own electric vehicle. Furthermore, because the availability of a charging space is determined based on information about the presence or absence of a vehicle in the charging space at the time of reservation, it is possible to accept reservations that are not for the entire day, for example, that is, reservations that are intended for use for a short period of time, such as one to several hours, that is shorter than business hours. As a result, it is possible to accept multiple reservations per day for one charging space, thereby increasing the utilization rate of the charging parking lot.

[0101] In the above configuration, a reservation time is set to reserve a charging space for a specified period of time from the reservation time. Furthermore, reservations that do not begin use within the specified reservation time are canceled. This prevents excessive loss of usage opportunities for users who have not made reservations. It also makes it possible to accept more reservations per day for one charging space.

[0102] In the above configuration, charging space reservation is free of charge. This allows the charging space reservation service to be offered at an affordable price, which is expected to attract more users. However, for example, it is also possible to charge for the reservation time. In this case, more opportunities to reserve a charging space can be provided to users who are willing to pay a reservation fee to use the charging space.

[0103] In the above configuration, the management server determines the usage status of the charging space and notifies the notification device 140, for example, that a charging space is available for reservation and that it has already been reserved. This reduces the possibility that a user may mistakenly enter another charging space, thinking it is a reserved or unreserved charging space that the user can use. The management server also determines the usage status of the charging space in detail and notifies the notification device 140 of each usage status. This allows the user to understand the usage status of the charging space and use the charging space safely and with peace of mind.

[0104] In the above configuration, the user terminal management module 311 can identify an occupancy state when an unreserved user enters a charging space before checking in. With this configuration, it is possible to accept reservations for charging spaces while safely providing charging spaces to vehicles that have not made reservations.

[0105] In the above configuration, when check-in information is received and it is confirmed that the charging space is reserved, the restriction device is set to a state where it can release the restriction on use of the charging space. This allows use of the charging space only when the reserved user uses the reserved charging space.

[0106] In the above configuration, the reservation management module 313 receives temporary exit information indicating that a vehicle will temporarily exit, and when the status acquisition module 312 receives information indicating that no vehicle is in the charging space, the restriction module 314 puts the restriction device into a restricted state. As a result, the charging space is immediately put into a restricted state when the vehicle temporarily exits, preventing other vehicles from entering. This allows a vehicle to safely temporarily exit the charging space while maintaining the reserved status, for example, when using the charging space for an extended period of time, such as for overnight stays. [Example]

[0107] FIG. 20 shows another example of a reservation acceptance flow 2000. In the first embodiment, the regulating device 130 is in a state in which it regulates vehicles from entering the charging space when the charging space is available. However, as shown in Fig. 20, in the reservation management system 100 of the second embodiment, the regulating device 130 is in a state in which it does not regulate vehicles from entering the charging space when the charging space is available (see S2002 and S2004). The other configurations and effects may be the same as those of the first embodiment, and therefore will not be described again.

[0108] In such a case, the process from launching the reservation app (S2010) to accepting the reservation request (S2020) can be executed in the same manner as in Example 1. When a reservation request is accepted from the user terminal 103, the user terminal management module 311 checks the usage status of all charging spaces in the charging parking lot for which the reservation has been requested in accordance with the status management flow 2400 (S2022). The charging space status acquisition module 212 of the charging space management device 101 connects to the detection device 120 to acquire information regarding the presence or absence of a vehicle (S2024) and transmits the information to the management server 102 (S2026).

[0109] At this time, if there is a reservable charging space in the charging parking lot, the reservation is established. Therefore, the management server 102 executes the reservation procedure in a manner generally similar to that of the first embodiment. That is, the reservation management module 313 transmits information indicating that the reservation has been established to the user terminal 103 (S2028). Furthermore, the regulation module 314 outputs information indicating that the regulating device 130 enters a regulated state (B) that regulates use of the charging space to the charging space management device 101 corresponding to the reserved charging space in the charging parking lot (S2034), and the reservation management module 313 transmits information indicating that the notification device 140 has reserved the charging space (X6) (S2030). Then, the charging space regulation module 213 of the charging space management device 101 outputs information indicating that the regulating device 130 enters a regulated state that regulates use of the charging space to the regulating device 130 (S2034), and sets the regulating device 130 to the regulated state (S2036). Furthermore, the charging space management module 211 outputs information indicating that the charging space has been reserved to the notification device 140 (S2038), and the notification device 140 outputs information indicating that the charging space has been reserved (S2040).

[0110] On the other hand, if there are no reservable charging spaces in the charging parking lot, it is possible that a vehicle has entered the charging space without making a reservation, or that the detection device 120 has detected that a person or vehicle has temporarily entered the charging space. Therefore, the reservation management module 313 waits for a predetermined waiting time (typically 10 to 30 seconds, e.g., 10 seconds) and then checks the usage status again according to the status management flow 2400 (not shown). At this time, if there is a reservable charging space, the management server 102 completes the reservation and completes the reservation process according to steps S2028 to S2040. However, if there are no reservable charging spaces again, it can be determined that a vehicle has entered the charging space without making a reservation. Therefore, the reservation management module 313 transmits information indicating that the reservation has been unsuccessful to the user terminal 103 and, for example, displays the reservation screen 2700 or 2800 again to accept the user's request for a reservation of another charging parking lot.

[0111] FIG. 21 shows another example of the charging / retrieval process / reservation completion flow 2100. The flow from the completion of reservation until the detection device 120 detects information indicating that the vehicle is not present after leaving the garage (S2118) may be the same as in the first embodiment.

[0112] When the status acquisition module 312 of the management server 102 acquires information indicating that there is no vehicle in the charging space (S2118), the user terminal management module 311 records that the usage status of the charging space has changed from charging possible (X6) to reservation possible (X1). Accordingly, the user terminal management module 311 increases the number of reservations that can be made for the rapid charger in this charging parking lot by one.

[0113] The regulation module 314 also transmits information indicating that power supply to the vehicle by the charger is permitted to the charging space management device 101 (S1920). Here, the regulation module 314 does not transmit information that puts the regulating device into a regulated state. The charging space regulation module 213 transmits the acquired information that disables power supply by the charger to the charger 110, and regulates power supply to the vehicle by the charger 110.

[0114] The user terminal management module 311 transmits information to the notification device 140 of the charging space management device 101 indicating that the charging space is available for use (S1920). The charging space management module 211 transmits the received information to the notification device 140 (S1926), and the notification device 140 displays that the charging space is available for use (S1928).

[0115] [Action and effect] According to the above configuration, the regulating device 130 does not record the entry of a vehicle when a charging space is available, which can motivate users who own electric vehicles to try using the charging space without making a reservation. This can increase the opportunities to use the charging parking lot. Furthermore, whether the regulating device 130 is in a regulated state or a non-regulated state when the charging space is available can be easily selected by a program executed by the management server 102. Therefore, the state of the regulating device 130 when the charging space is available can be determined according to, for example, the number and attributes of users who use each charging parking lot.

[0116] The present invention is not limited to the above-described embodiments and includes various modifications. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those including all of the described configurations. Furthermore, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, it is possible to add, delete, or replace part of the configuration of each embodiment with other configurations.

[0117] (1) In the above embodiment, the management server confirms that the user is the reserving user by obtaining the check-in information transmitted by the management server to the user terminal 103 or the charging space management device from the charging space management device or the user terminal. However, the user authentication method is not limited to this. For example, when the reservation management module 313 confirms that the reservation identification information related to the reservation and the identification information related to the check-in information are the same, the restriction module 314 may set the restriction device 130 to release the restriction on use of the charging space. Specifically, for example, when the reservation management module 313 confirms that the reservation ID notified to the user terminal 103 at the time of reservation and the reservation ID transmitted from the user terminal 103 at the time of check-in are the same, the restriction module 314 may set the restriction device 130 to release the restriction on use of the charging space.

[0118] Furthermore, for example, if the detection device 120 is a vehicle license plate reader, when it is confirmed that the vehicle license plate number of the reserved vehicle registered at the time of reservation is the same as the vehicle license plate number detected by the vehicle license plate reader at check-in, the restriction module 314 may cause the restriction device 130 to release the restriction on use of the charging space. Alternatively, the reservation management module 313 may permit charging. This reduces the burden on the user and enables check-in.

[0119] (2) The usage status management flows in Figures 24 to 26 in the above embodiment can be modified as appropriate depending on the facilities and fee structure of the target charging parking lot. For example, when grasping the usage status of a charging space in a charging parking lot that only has standard chargers or rapid chargers, there is no need to check the charging type, so for example, S2420 can be omitted. Furthermore, it can be determined whether or not to execute the billing flow for the use of all charging spaces. For example, when determining the usage status of a charging space in a charging parking lot that has both standard chargers and rapid chargers, the charging type may be confirmed in S2420, and then different billing flows may be executed depending on the type of charger. In either case, the time at which billing begins and the time at which an overcharge fee is incurred can be set as desired.

[0120] (3) The state transition diagram illustrated in FIG. 23 of the above embodiment does not show a route for transitioning from temporary exit (LEAVING; X9) to preparation for temporary exit (LEAVING_AND_OCCUPIED; X10). However, a charging space does not necessarily need to be provided with a charging space regulating device 130 that regulates vehicle entry. In such cases, the charging space may be configured to be able to transition from temporary exit (X9) to preparation for temporary exit (X10). In this case, the usage status of the charging space can be notified by the display on the notification device 140. Alternatively, the system may be configured to detect a situation in which a special vehicle, such as a vehicle with a high vehicle height, is parked beyond the regulating device 130 even though the regulating device 130 is in a regulated state.

[0121] (4) In the above-described embodiments, all charging spaces are equipped with chargers. However, the reservation management system 100 according to the present technology is not limited to application to a reservation system for charging parking lots that have chargers. For example, the technology can also be applied to a reservation system for charging parking lots that do not have chargers in one or more charging spaces, or for parking lots that do not have chargers at all.

[0122] (5) In the above embodiment, one charger 110 is provided per charging space. However, a charger does not necessarily have to be provided for each charging space. For example, one charger 110 may be provided between two adjacent charging spaces. In such a case, the management server 102 may also accept a reservation for a charging time when accepting a reservation. The management server 102 may be configured to accept a reservation if there is a reservable (available) charging space, provided that there is no vehicle in the charging space and the charging times do not overlap. The availability status may be changed from "charging available" to "charging standby" or the like when the conditions of having checked in and having a vehicle in the charging space are met, and the availability status may be set to "charging available" when the condition of being within the reserved charging time is met.

[0123] (6) In the above embodiment, the restriction device is exemplified as a restricting device having a rotating restriction member that restricts a vehicle from entering the charging space. However, the restriction member is not limited to this example. For example, the shape of the restriction member is not limited to a plate-like member and may be various shapes such as a rod, a mesh, a fence, or a sheet. Furthermore, the operation of switching between the restricted state and the unrestricted state is not particularly limited. For example, the restriction member may be displaced by rotating around a horizontal axis, rotating around a vertical axis, rotating, ascending, descending, or moving horizontally, etc., to switch between the restricted state and the unrestricted state.

[0124] (7) In the above embodiment, data processing by the detection device 120 is not described. However, at least one of the charging space management device 101 and the management server 102 (for example, the charging space management device 101) may organize and use the information regarding the presence or absence of a vehicle acquired by the detection device 120, for example, as follows: For example, the measurement values ​​detected by the detection device may be converted into a binary value indicating whether or not a vehicle is present based on a predetermined threshold value, for example, the measurement values ​​acquired during a predetermined detection period. If the detection device is, for example, an ultrasonic distance sensor, the sampling period (e.g., 300 milliseconds) can be input to the AI, and a moving average can be calculated for a predetermined number of samples (e.g., 30). The presence or absence of a vehicle can be determined based on whether this moving average value is below a predetermined threshold (e.g., 600 to 650 mV) (in this case, a vehicle is present) or below the threshold (in this case, a vehicle is not present). When the detection device is an ultrasonic sensor, the measurement value at the time of sampling can be used as the measurement value. Alternatively, for example, a value after a certain buffer time (for example, 10 seconds) has elapsed since the start of acquisition may be used as the final value. Furthermore, if the detection device is, for example, a loop coil sensor, it is preferable to sequentially acquire data indicating the presence of a vehicle (for example, HI) or data indicating the absence of a vehicle (for example, LO) for each lap. If the regulating device has a rotating regulating member that rotates from a horizontal position to a vertical position to restrict vehicle entry, and is equipped with a detection device that detects the presence or absence of obstacles in the surrounding area (e.g., the periphery of the regulating device or outside the rotation radius) when the regulating member is in the horizontal position, sampling values ​​at a predetermined period (e.g., 10 to 30 seconds) can be used. The value indicating the presence or absence of a vehicle obtained in this manner can be stored and managed in the management server 102, for example.

[0125] (8) The present technology provides a reservation management method, which is included in the above-described embodiments, that acquires information regarding the presence or absence of a vehicle in a charging space, determines whether the usage status of the charging space is available for reservation based on the acquired information, accepts a reservation for the charging space if it is available for reservation, and, if the reservation is accepted, sets a regulating device installed in the charging space to a state that restricts the use of the charging space.

[0126] The present technology also provides a program for causing a server to execute each step in the reservation management method. This program may consist of a single program, or may consist of two or more subprograms. It may also be a program for causing a server to execute any one or more of the steps.

[0127] (9) The present technology provides a charging space management method, included in the above-described examples, that acquires information regarding the presence or absence of a vehicle in a charging space detected by a detection device installed in the charging space, transmits the information regarding the presence or absence of a vehicle acquired by the charging space status acquisition unit to a reservation management device that manages reservations for the charging space, and acquires information regarding restrictions on use of the charging space from the reservation management device, and, when information restricting use of the charging space is acquired by the charging space management unit, sets a restriction device installed in the charging space to a state that restricts use of the charging space.

[0128] The present technology also provides a program for causing a computer to execute each step in the charging space management method. This program may be composed of a single program, or may be composed of two or more subprograms. It may also be a program for causing a computer to execute any one or more of the steps.

[0129] (10) Furthermore, the above-described configurations, functions, processing units, processing means, etc. may be partially or entirely implemented in hardware, for example, by designing them as integrated circuits. Furthermore, the above-described configurations, functions, etc. may be implemented in software by a processor interpreting and executing a program that implements each function. Information such as the programs, tables, and files that implement each function can be stored in a memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD.

[0130] (11) Also, the control lines and information lines shown are those considered necessary for explanation, and do not necessarily show all the control lines and information lines in the product. In reality, it can be assumed that almost all components are interconnected.

[0131] (12) Furthermore, one or more of the elements of the one or more charging space management devices 101, one or more management servers 102, and one or more user terminals 103 that constitute the reservation management system 100 may be installed in different countries. Furthermore, the management server 102 may be composed of one or more computers, any of which may be installed in different countries. The above-described embodiments disclose at least the configurations described in the claims. [Explanation of symbols]

[0132] 100... reservation management system, 101... charging space management device, 102... management server, 103... user terminal, 110... charger, 111... power meter, 112... external power supply, 120... detection device, 130... regulation device, 132... main body, 134... regulation member, 140... alarm device, 150... parking area, 211... charging space management module, 212... charging space status acquisition module, 213... charging space regulation module, 311... user terminal management module, 312... status acquisition module, 313... reservation management module, 314... regulation module

Claims

1. A reservation management device that manages reservations for multiple charging spaces, a status acquisition unit that acquires information regarding the presence or absence of a vehicle in each of the plurality of charging spaces; a reservation management unit that determines whether the usage status of the charging space is in a reservable state based on the information acquired by the status acquisition unit, and accepts reservations for the charging space if the usage status is in a reservable state, and is configured to manage the number of reservations and / or the number of reservable states for the plurality of charging spaces; a restriction unit that, when the reservation management unit accepts the reservation, causes a restriction device provided in the charging space to enter a state in which use of the charging space is restricted; Equipped with the reservation management unit accepts a reservation when the number of available reservations exceeds zero; the restriction unit outputs information to restriction devices provided in at least the unused charging spaces corresponding to the number of reserved charging spaces, to place the charging spaces in a state in which use of the charging spaces is restricted; When the reservation management unit detects that the reserving person has arrived at the plurality of charging spaces, the reservation management unit extracts one of the unused charging spaces whose use is restricted, and outputs information about the extracted charging space as information about the charging space available to the reserving person. Reservation management device.

2. When the reservation management unit detects that the reservation holder has arrived at the plurality of charging spaces, and there are a plurality of charging spaces whose use is restricted among the unused charging spaces, outputting information about a plurality of unused charging spaces whose use is restricted as information about charging spaces available to the reservation user; and accepting any one charging space selected by the reserver from among the outputted charging spaces available to the reserver as the charging space to be used by the reserver. The reservation management device according to claim 1 .

3. When the reservation management unit determines that the number of available reservations is zero, the status acquisition unit waits for a predetermined waiting time and then again acquires information regarding the presence or absence of vehicles in each charging space, When the reservation management unit determines again that the number of available reservations is zero, it outputs information indicating that the reservation request has been unsuccessful. The reservation management device according to claim 1 .

4. The charging space is provided with an alarm device that outputs a usage status of the charging space, The reservation management unit If it is determined that the charging space is available for reservation, output information indicating that the charging space is available for reservation; When the reservation is accepted, output information indicating that the charging space has been reserved. The reservation management device according to claim 1 .

5. When the charging space is available for reservation and the status acquisition unit acquires information indicating that a vehicle is present in the charging space, the reservation management unit outputs, to the notification device, information indicating that the charging space is occupied. The reservation management device according to claim 4.

6. the reservation management unit is configured to receive check-in information indicating that use of a charger installed in the charging space is permitted; When the charging space is occupied and the reservation management unit receives the check-in information, The regulation unit enables the charger to supply power to the vehicle. The reservation management device according to claim 5 .

7. the reservation management unit is configured to receive check-in information indicating that use of a charger installed in the charging space is permitted; When the charging space is available for reservation and the reservation management unit receives the check-in information, the restriction unit causes the restriction device to release restriction on use of the charging space.

3. The reservation management device according to claim 1 or 2.

8. the reservation management unit is configured to receive check-in information indicating that use of a charger installed in the charging space is permitted; When the charging space is available for reservation, and after the reservation management unit receives the check-in information, the status acquisition unit acquires information indicating that a vehicle is present in the charging space, The regulation unit enables the charger to supply power to the vehicle. The reservation management device according to claim 7.

9. the reservation management unit is configured to receive check-in information indicating that use of a charger installed in the charging space is permitted; When the reservation management unit receives the check-in information and confirms that the charging space is reserved, the restriction unit causes the restriction device to release restriction on use of the charging space.

3. The reservation management device according to claim 1 or 2.

10. When the reservation management unit confirms that the reservation identification information related to the reservation and the identification information related to the check-in information are the same, the restriction unit causes the restriction device to release the restriction on use of the charging space. The reservation management device according to claim 9.

11. the reservation management unit is configured to receive check-in information indicating that use of a charger installed in the charging space is permitted; When the charging space is already reserved and the reservation management unit receives the check-in information, the reservation management unit outputs to a notification device installed in the charging space that the charging space is in a charging-enabled state. The reservation management device according to claim 9.

12. When the charging space is in a charging enabled state and the status acquisition unit acquires information indicating that there is no vehicle in the charging space, the reservation management unit outputs information indicating that the charging space is available for reservation. The reservation management device according to claim 11.

13. the reservation management unit measures a time during which the charging space is in a chargeable state as a charging time; When the status acquisition unit acquires information indicating that there is no vehicle in the charging space, The reservation management unit settles the usage fee based on the charging time. The reservation management device according to claim 11.

14. When the reservation management unit receives temporary exit information indicating that the vehicle will temporarily exit and the status acquisition unit receives information indicating that no vehicle is in the charging space, The restriction unit causes the restriction device to restrict use of the charging space.

3. The reservation management device according to claim 1 or 2.

15. When the reservation management unit is in a temporary exit state where temporary exit information indicating that the charging space will not be used temporarily is received and the status acquisition unit acquires information indicating that the vehicle is present, the restriction unit restricts power supply to the vehicle by the charger.

3. The reservation management device according to claim 1 or 2.

16. When the reservation management unit is in a temporary exit state in which temporary exit information indicating that the charging space will not be used temporarily is received and the status acquisition unit acquires information indicating that the vehicle is not present, The restriction unit causes the restriction device to restrict use of the charging space.

3. The reservation management device according to claim 1 or 2.

17. When the reservation management unit is in a temporary exit state in which temporary exit information indicating that the charging space will not be used temporarily is received, and the reservation management unit receives check-in information indicating that use of a charger installed in the charging space is permitted, The reservation management device according to claim 1 , wherein the regulating unit causes the regulating device to release the restriction on use of the charging space.

18. When the charging space is in a temporary vacant state and the reservation management unit receives check-in information indicating that use of a charger installed in the charging space is permitted, The regulation unit enables the charger to supply power to the vehicle.

3. The reservation management device according to claim 1 or 2.

19. The charging space is provided with a charger for charging the vehicle, the reservation management unit accepts a reservation for using the charger; 3. The reservation management device according to claim 1 or 2.

20. the charging space is provided with a detection device that detects the presence or absence of a vehicle; The detection device is a vehicle number reader that reads the number of a vehicle, The reservation information regarding the reservation includes vehicle number information of the reservation holder, the reservation management unit permits charging when the vehicle number read by the vehicle number reader matches the vehicle number of the reservation user; 3. The reservation management device according to claim 1 or 2.

21. A reservation management method for managing reservations for a plurality of charging spaces, comprising: acquiring information regarding the presence or absence of a vehicle in each of the plurality of charging spaces; determining whether the usage status of the charging space is in a reservable state based on the acquired information, and accepting a reservation for the charging space if the usage status is in a reservable state; managing the number of reservations and / or the number of available reservations for the plurality of charging spaces, and accepting a reservation if the number of available reservations exceeds zero; When the reservation is accepted, output information to regulating devices installed in at least the number of unused charging spaces corresponding to the number of reservations, to cause the regulating devices installed in the charging spaces to enter a state in which use of the charging spaces is regulated; When it is detected that the reservation person has arrived at the plurality of charging spaces, one of the unused charging spaces whose use is restricted is extracted, and information about the extracted charging space is output as information about the charging space available to the reservation person. How to manage reservations.

22. A program for causing a server to execute each step of the reservation management method according to claim 21.

Images