JP2015018351A - Billing device having network print function for battery charger and server - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a network print function for allowing a user who has performed cash settlement with a billing device for a battery charger not having a print function to obtain a voucher.SOLUTION: A server comprises: means for receiving billing information and charging start information from a billing device; means for storing use history including the billing information in association with voucher identification information in a battery charger use information database; means for, when receiving a voucher request from a user terminal, comparing a reception time of the billing information or a reception time of the charging start information with a reception time of the voucher request to determine whether the difference of the times is within a predetermined setting value; means for, when the difference is within the predetermined setting value, transmitting a voucher URL together with the voucher identification information to the user terminal; and means for, when receiving a connection request using the voucher URL and the voucher identification information from the user terminal, acquiring corresponding use history to generate a voucher and transmit the voucher to the user terminal.

Description

  The present invention relates to a billing apparatus with a network print function and a server connected to or built in a charger for charging an external device such as an electric vehicle.

  EVs (Electric Vehicles) and PHEVs (Plug-in Hybrid Electric Vehicles) are attracting attention again due to environmental problems, soaring crude oil prices, and technological advances in lithium-ion batteries. EVs and PHEVs (both of which are referred to as “electric vehicles” in this specification) are equipped with a large-capacity battery and can be charged from a charger. Chargers used for charging are easier to install than gasoline metering machines used for refueling cars, so there were no refueling facilities for cars such as homes, retail stores, card dealers, and government offices. Installation is progressing to the place.

  The charging amount of the charger is about 3kWh per hour with a normal charger and over 20kWh in 30 minutes with a quick charger, so charging is performed until the remaining battery level reaches 0% to 100%. Then, an electricity bill of several hundred yen is generated. In addition, since a running cost such as a maintenance cost and a contract power charge is also required, an appropriate charging means is important for a charger installation company.

  Solutions that can address these issues are presented. For example, Patent Document 1 discloses a charger capable of inserting coins. In this method, it is possible to charge for charging. Patent Document 2 discloses a coin parking device with a wheel stopper. In this method, pay-as-you-go after charging is possible. Patent Document 3 discloses an EV charge display device. In this method, pay-as-you-go based on the amount of power is possible. Patent Document 4 discloses a charger that operates in conjunction with a parking lot adjustment machine. In this method, when it is difficult to charge a plurality of vehicles at the same time due to the amount of contracted electric power or the like, it is possible to charge in the order of entering the parking lot.

JP 11-161846 A JP 2011-43041 A JP 2011-244514 A JP 2011-244630 A

  When cash settlement is performed with a charging device built in or near the charger, a receipt may be requested. However, in order to issue a receipt, maintenance measures such as an increase in cost due to the built-in printer in the billing device, replenishment of paper, and handling of paper jams are required. The problem to be solved by the present invention is to provide a function that allows a user of a charger to obtain a receipt without adding a receipt issuing function to the charging apparatus.

In order to achieve the above object, the present invention provides the following configurations.
A server according to the present invention is a server that is connected to a charging device that is connected to or built in a charger that charges an external device via a network and that can be connected to a user terminal via a network,
Means for receiving charging information indicating completion of charging operation in the charging device and charging start information indicating charging start in the charger from the charging device;
Means for storing a usage history including at least the billing information in a charger usage information database in association with receipt specifying information for specifying the usage history;
When a receipt request for issuing a receipt is received from a user terminal for sending a receipt request, the reception time of the charging information or the reception time of the charging start information and the reception time of the receipt request Means for determining whether or not a predetermined setting condition is satisfied by comparing; and
When the predetermined setting condition is satisfied, means for transmitting electronic information necessary for obtaining the receipt together with the receipt specifying information to the user terminal for sending the receipt request;
When the connection request using the electronic information necessary for obtaining the receipt and the receipt specifying information are received from the user terminal for receiving the receipt, the charger usage information database based on the receipt specifying information A means of obtaining a corresponding usage history from the URL and generating a receipt,
Means for transmitting the generated receipt to the user terminal for receiving the receipt.
In one aspect of the server, the charging information reception time is a transmission time of the charging information.
In one aspect of the server, the reception time of the charging start information is a transmission time of the charging start information.
In one aspect of the server, the receipt request reception time is a transmission time of the receipt request.
In one aspect of the server, the means for determining whether or not a predetermined set value condition is satisfied is that a difference between the respective times is within a predetermined set value.
In one aspect of the server, the electronic information necessary for obtaining the receipt is a URI (Uniform Resource Identifier) indicating a home page for issuing the receipt.

A charging device with a network print function according to the present invention is a charging device connected to or built in a charger for charging an external device connected to the server,
Means for transmitting the charging information and the charging start information to the server.
In one aspect of the accounting apparatus, there is provided means for receiving and displaying a password described in the receipt request from the server.
In one aspect of the billing device, the user terminal for sending the receipt request comprises means for receiving and displaying an email address for sending the receipt request to the server from the server. Yes.

  According to the accounting apparatus and server with a network print function according to the present invention, a cash settlement receipt relating to charging for charging of an external device such as an electric vehicle is issued to a user without including a printer in the accounting apparatus. be able to.

FIG. 1 is an overall configuration diagram of the present invention. FIG. 2 is a sequence diagram showing an outline of the present invention. FIG. 3 is a sequence diagram for obtaining a receipt from the network. FIG. 4 is a diagram illustrating an example of a data structure of charger usage information. FIG. 5 is a diagram illustrating an example of a data structure of billing information. FIG. 6 is a diagram illustrating an example of a data structure of the charging start permission information. FIG. 7 is a diagram illustrating an example of a data structure of the charging start information. FIG. 8 is a diagram showing an example of the data structure of the receipt request information. FIG. 9 shows an example of the data structure of receipt URI (Uniform Resource Identifier) information. FIG. 10 is a diagram illustrating an example of a data structure of the charging end information. FIG. 11 is an example of a receipt display screen.

  The present invention attaches a network printing function to a charging device for a charger for an external device such as an electric vehicle and a server connected thereto, and a user obtains a receipt based on the usage record of the charger from the server. The mechanism is realized with the minimum hardware configuration. Hereinafter, an electric vehicle will be described as an example of a typical external device. However, the present invention can be similarly applied to a vehicle or a machine that is charged for charging from a charger other than the electric vehicle. Moreover, although the case where an electric vehicle is EV is described as an example, PHEV can be similarly realized.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a diagram illustrating a configuration example of an entire system including a charging device with a network print function for a charger and a server according to an embodiment of the present invention.

  100 indicates a charger. Reference numeral 101 denotes a user interface attached to the charger, which includes a screen and input buttons. The user inputs an instruction to start charging from this interface. Reference numeral 102 denotes a charge control unit that controls electric power output to the EV. A charging device communication unit 103 communicates with the charging device 110 connected to the charger 100. Control information and the like from charging device 110 are input to charging control unit 102. A charging gun 104 is connected to the EV for charging.

  Reference numeral 110 denotes a charging device. Reference numeral 111 denotes a user interface attached to the billing apparatus, which includes a screen and input buttons. From this interface, the user inputs the operation to the billing device, displays the input amount, and displays the remaining time until charging is completed. A charging control unit 112 permits or prohibits the insertion of coins and banknotes, calculates the amount of money to be inserted, and the like. A server communication unit 113 is connected to the server 130 via the Internet 120. A charger communication unit 114 communicates with the charger 100 connected to the charging apparatus 110.

  Reference numeral 130 denotes a server. A user terminal communication unit 131 communicates with the user terminal 140 such as a PC or a mobile phone via the Internet or the like. 132 is a receipt creation unit, which generates a receipt using the charger usage information of 134, etc., and transmits the receipt as electronic data to the user terminal 140 via the user terminal communication unit 131. Issue. A charging device communication unit 133 connects to the charging device 110 via the Internet 120. Reference numeral 134 denotes a charger usage information database, which holds the date and time when the charger was used, the date and time when the charger was charged, and a random character string created when permitting receipt issuance as a database. With the configuration described above, the user of the charger 100 can use the charging device 110 to pay cash, perform charging, and obtain a receipt from the user terminal 140.

  FIG. 2 is an overall sequence diagram of the present invention. Sequences S201 to S216 indicate the user sequence, sequences S221 to S236 indicate the sequence of the charger 110, sequences S241 to S256 indicate the sequence of the charging device 120, and sequences S261 to S276 indicate the sequence of the server 130. In the initial state of this sequence, the user starts a charging operation, and the charger is waiting for input of the operation. The accounting device is waiting for input of an operation, and the server is waiting for receiving information.

  The outline of this sequence is that when the user starts the charging operation, the charger is instructed to start and the cash is charged into the charging apparatus. Subsequently, the charger starts charging, and at the same time, the user requests the server to issue a receipt by e-mail or the like. Then, the server returns a mail containing a URI that can issue a receipt. When the user accesses the URI that issues a receipt after charging is complete, the receipt screen can be obtained.

  Hereinafter, each step will be described in detail. First, when the user starts the charging operation (S201), the user inputs a charging start request to the charger (S202). In this process, for example, an operation of pressing a “charge start” button displayed on the touch panel screen is performed. The user's operation is input to the charger as a charge start request input (S222). The user sees a screen such as “Please insert the charging gun” after S202, and connects the charging gun to the car (S203).

  The charger transmits a request for charging before starting charging (S223). When the charging device receives the charging request (S243), the charging device sets the charging device in a chargeable state. The billable state is, for example, accepting a coin or banknote and allowing it. The user performs a charging operation, for example, by confirming a display saying “Please insert money” on the charging device (S204). The charging operation is to insert coins or bills into the charging device. The billing apparatus accepts the inserted cash for the set amount (S244). For example, if the set amount is 500 yen, the charging step 244 is completed when it reaches 500 yen.

  Next, the billing apparatus transmits billing information (S245). The server receives the billing information and accumulates a usage history including at least the billing information in the charger usage information database (S265). The charging device transmits a charging start permission to the charger when the set amount of cash is inserted (S246). The charger receives the charging start permission (S226), and starts charging the vehicle (S227). Subsequently, the charger transmits charging start information to inform the server that charging has started (S228). When the charging device receives the charging start information (S248), it transmits the charging start information to the server (S249), and the server receives the charging start information (S269).

  After performing the charging operation S204, the user performs processing according to the method of obtaining a receipt displayed or posted on the charger or the charging device. For example, if you want to obtain a receipt, please send an e-mail to the e-mail address on the charger within 5 minutes after the start of charging. Enter the e-mail address in the terminal (user terminal for sending receipt request) and send the e-mail. At this time, a password or the like displayed on the charger or the billing device may be entered in the body of the email. When a receipt request is transmitted from the user terminal (S210), the server receives the receipt request (S270).

  When the server receives the receipt request, the server compares the reception times (S271). The comparison of the reception time is to compare whether the charging information reception (S265) or charging start information reception (S269) time and the receipt request reception (S270) time, and determine whether or not a predetermined setting condition is satisfied. . For example, it is a process of confirming whether the difference is within a set value. For example, when the set value is 3 minutes, it is confirmed whether or not a receipt request is transmitted from the user within 3 minutes from the start of charging. Charging is usually about 15 to 30 minutes with a quick charger, and it is normal to charge for about 1 to 8 hours with a normal charger. Even if you send a receipt request suddenly, there is a possibility that it is the timing when charging started Low. For this reason, in order to obtain a receipt in a situation where it is not actually used, it is necessary to send a receipt request many times, and a receipt request from the same email address in a time slot that is not clearly used If you receive an email, reject the receipt request for a certain period of time, or send an email such as “This email address is no longer available due to an incorrect receipt request” by sending a receipt URI (S272). May be. If the received time is within the set value, the server sends a receipt URI to the user terminal for sending the receipt request (S272), and the user terminal for sending the receipt request sends the receipt URI. Is received (S212). The receipt URI is an example of electronic information necessary for obtaining a receipt. The receipt URI includes receipt specifying information for specifying the usage history accumulated in the charger usage information database. The receipt specifying information is, for example, a character string.

  When charging is completed (S233), the charger transmits charging completion information to the charging device (S254). The charging device transmits the charging end information to the server (S255), and the server receives the charging end information (S275). The series of processes is thus completed, the user ends the charging operation (S216), and the charger is on standby (S236). Similarly, the charging device is also waiting for operation (S256), and the server is waiting for reception (S276).

  FIG. 3 is a sequence for obtaining a receipt via the network. When the user starts a receipt acquisition process using a user terminal (receipt receiving user terminal) such as a PC (S301), a receipt URI connection request is transmitted (S302). This process is a process in which the user accesses the homepage in S212 using the URI acquired by the user terminal for sending the receipt request on the Web browser of the user terminal for receiving receipts such as a PC. is there. Note that the user terminal for sending a receipt request in S212 and the user terminal for receiving a receipt in S302 may be the same terminal or different terminals. The URI contains a character string that cannot normally be inferred, such as a random character string, and being able to connect to the URI proves that the user has the right to obtain a receipt. This character string may also serve as receipt specifying information. If you want to prove that you are a user who uses the charger more reliably, after S265, the server will send the password to the billing device, display the password on the billing device, and let the user enter the password in the email. The password may be transmitted in S210 and the password issued in S271 may be verified. The password may be a password generated after S265 or a fixed password.

  Upon receiving the connection request (S312), the server refers to the charger usage information database based on the receipt specifying information such as a character string included in the URI, and specifies and acquires the corresponding usage history (S313). As a usage history specifying method, the usage history may be specified from the charger usage information by including a character string 406 as receipt specifying information in the URI. When the usage history is acquired, a receipt screen is generated from the acquired usage history (S314). An example of the generated screen is shown in FIG. 1101 is a screen of a PC or the like, and a receipt is 1102. The amount, date of use, and usage time are obtained from the charger usage information database. Further, the issuer 1103 of the receipt may be described from separately provided charger management information. The generated screen is transmitted to the user terminal for receipt receipt (S305). The user prints out the screen and uses it as a receipt.

  FIG. 4 is an example of charger usage information stored in the charger usage information database 134. The charger usage information is a history for each usage of the charger. 401 is an ID for identifying the charger. Reference numeral 402 indicates the date and time when the charge was made. Reference numeral 403 indicates the date and time when charging was started. 404 indicates the date and time when the charging is completed. Reference numeral 405 denotes a charge amount, which corresponds to the amount paid by the user. 406 is a receipt specifying character string as the receipt specifying information, and uses a random character string that can uniquely specify each usage history of the charger usage information and cannot be easily conceived. As the charger usage information, the charger ID 401, the charging date and time 402, and the charging amount 405 are input in S265, the charging start date and time 403 is input in S269, and the charging end date and time 404 is input in S275. The receipt specifying character string is input between S265 and S272.

  FIG. 5 is an example of the billing information transmitted in S245. The billing information is information that allows the billing amount to be determined by specifying the charger and date and time. Reference numeral 501 denotes an ID for identifying the charger. Reference numeral 502 denotes the date and time when the charge was made. Reference numeral 503 indicates a charge amount.

  FIG. 6 is an example of the charging start permission information transmitted in S246. The charging start permission information is information that allows the charger to start charging. Reference numeral 601 is an ID for identifying the charger. A command 602 instructs the charger to permit charging start.

  FIG. 7 is an example of charging start information transmitted in S228 or S249. The charging start information is information including a date and a state when the charger starts charging. Reference numeral 701 denotes an ID for identifying the charger. 702 is the date and time when charging was started. Reference numeral 703 denotes information indicating the state of the charger when the charging start information is transmitted.

  FIG. 8 is an example of the receipt request information transmitted in S210. Receipt request information is information transmitted when a user requests a receipt. Reference numeral 801 denotes an ID for identifying the charger. 802 is the date and time when this request is transmitted. 803 is a password displayed on the charger or the billing device, and is transmitted from the server to the charger via the billing device or the billing device after S265 only when the password is used. Reference numeral 804 denotes a mail transmission source address. Note that 804 may use information described in a mail header or the like.

  FIG. 9 is an example of the receipt URI information transmitted in S272. Receipt URI information is information including the address of a homepage that issues a receipt. 901 is a URI of a homepage or the like that issues a receipt. The URI includes a receipt specifying character string 406 as receipt specifying information. Note that the receipt specifying character string 406 does not necessarily need to be included in the URI, as long as it can be delivered to the server by some means after connecting to a homepage that issues the receipt. Reference numeral 902 denotes a charging start date and time. Reference numeral 903 denotes the mail address of the user terminal for sending the receipt request that has sent the receipt request information.

  FIG. 10 is an example of the charging end information transmitted in S234 or S255. 1001 is an ID for identifying the charger. 1002 is the date and time when charging is finished. Reference numeral 1003 denotes information indicating the state of the charger when the charging end information is transmitted.

DESCRIPTION OF SYMBOLS 100 Charger 101 Charger user interface 102 Charging control part 103 Charging apparatus communication part 104 Charging gun 110 Charging apparatus 111 Charging apparatus user interface 112 Charging control part 113 Server communication part 114 Charger communication part 120 Internet 130 Server 131 User terminal communication Part 132 Receipt Creation Part 133 Charge Device Communication Part 134 Charger Usage Information Database 140 User Terminal (PC etc.)

Claims (9)

A server that is connected to a charger for charging an external device or connected to a built-in charging device via a network and is connectable to a user terminal via a network,
Means for receiving charging information indicating completion of charging operation in the charging device and charging start information indicating charging start in the charger from the charging device;
Means for storing a usage history including at least the billing information in a charger usage information database in association with receipt specifying information for specifying the usage history;
When a receipt request for issuing a receipt is received from a user terminal for sending a receipt request, the reception time of the charging information or the reception time of the charging start information and the reception time of the receipt request Means for determining whether or not a predetermined setting condition is satisfied by comparing; and
When the predetermined setting condition is satisfied, means for transmitting electronic information necessary for obtaining the receipt together with the receipt specifying information to the user terminal for sending the receipt request;
When the connection request using the electronic information necessary for obtaining the receipt and the receipt specifying information are received from the user terminal for receiving the receipt, the charger usage information database based on the receipt specifying information A means of obtaining a corresponding usage history from the URL and generating a receipt,
Means for transmitting the generated receipt to the user terminal for receiving the receipt.   The server according to claim 1, wherein the reception time of the charging information is a transmission time of the charging information.   The server according to claim 1, wherein the reception time of the charging start information is a transmission time of the charging start information.   The server according to claim 1, 2 or 3, wherein the receipt time of the receipt request is a transmission time of the receipt request.   5. The server according to claim 1, 2, 3, or 4, wherein the means for determining whether or not the predetermined setting condition is satisfied has a difference between the respective times within a predetermined setting value.   6. The server according to claim 1, wherein the electronic information necessary for obtaining the receipt is a URI (Uniform Resource Identifier) indicating a homepage for issuing the receipt. A charging device connected to or built in a charger for charging an external device connected to the server according to claim 1, 2, 3, 4, 5 or 6,
Means for transmitting the charging information and the charging start information to the server, and a charging device with a network print function.   8. A charging apparatus with a network print function according to claim 7, further comprising means for receiving and displaying a password described in the receipt request from the server.   8. The means for receiving a receipt request from the server and displaying a mail address for sending the receipt request to the server by the user terminal for sending the receipt request. 9. A charging apparatus with a network print function according to 8.

Images