JP2021015409A - Service provision system, management server, service provision device, management service provision program, device service provision program, and service provision method - Google Patents

Abstract

To provide a service provision system, management server, service provision device, management service provision program, device service provision program, and service provision method, which can provide services using the service provision device without having the service provision device communicate directly with the management server.SOLUTION: A service provision system 10 comprises a charging device 20 for providing a service, a management server 40 for managing the charging device 20, and a user terminal 30 configured to communicate with the management server 40. A management CPU 42 of the management server 40 performs an authentication signal transmission process for sending authentication information including usage condition information on usage conditions, to the user terminal 30. Upon receipt of the authentication information, the charging device 20 provides a service corresponding to the usage conditions.SELECTED DRAWING: Figure 2

Description

The present invention relates to a service providing system, a management server, a service providing device, a management service providing program, a device service providing program, and a service providing method.

For example, Patent Document 1 describes a charging system as a service providing system including a charging device as a service providing device, a mobile terminal as a user terminal, and a charging management server as a management server for managing the charging device. Is described. In the charging system described in Patent Document 1, the mobile terminal and the charging management server communicate with each other via the first communication network, and the charging device and the charging management server are different from the first communication network. Communication is carried out via the communication network of.

Japanese Unexamined Patent Publication No. 2013-1611107

Here, the mobile terminal and the charge management server communicate with each other via the first communication network, and the charging device and the charge management server communicate with each other via a second communication network different from the first communication network. In the configuration for performing the above, both the communication cost between the mobile terminal and the charge management server and the communication cost between the charging device and the charge management server are incurred. In addition, it is necessary to provide the charging device with a communication device that directly communicates with the charge management server. From these things, there is a concern that the cost will increase.

The present invention has been made in view of the above circumstances, and an object of the present invention is a service providing system capable of providing a service using a service providing device without direct communication between the service providing device and the management server. It is to provide a management server, a service providing device, a management service providing program, a device service providing program, and a service providing method.

A service providing system that achieves the above object includes a service providing device that provides a service, a management server that manages the service providing device, and a user terminal that communicates with the management server. The service providing device is provided with an encryption key transmission unit that transmits an encryption key including the usage condition information which is information on the usage conditions of the service providing device to the user terminal, and the service providing device does not directly communicate with the management server. It is characterized by including a reception unit that accepts the encryption key and a service execution unit that provides a service corresponding to the usage conditions based on the reception unit accepting the encryption key. ..

According to such a configuration, it is possible to provide a service corresponding to the usage conditions without directly communicating with the service providing device and the management server. Further, since the encryption key is transmitted to the user terminal, the user can perform the reception procedure for the reception unit, and the user terminal can perform the reception procedure for the reception unit. As a result, the service providing device and the management server do not directly communicate with each other, and a third party such as an administrator who manages the service providing device does not perform any procedure, and the service providing device can be used to comply with the usage conditions. Can provide services to be provided.

Regarding the service providing system, the service providing device is set by a device operation unit on which an input operation is performed, a condition setting unit that sets the usage conditions based on an input operation to the device operation unit, and the condition setting unit. The user terminal includes a transmission unit that executes a transmission process for transmitting the said usage conditions to the user terminal, and the user terminal is the usage condition information that is information regarding the usage conditions transmitted from the service providing device. It is preferable to include an application signal transmission unit that transmits an application signal including the above to the management server.

According to such a configuration, the user can set the desired usage conditions by performing an input operation on the device operation unit. Further, the set usage conditions are transmitted to the user terminal and transmitted to the management server via the user terminal. As a result, the management server can grasp the user's wishes without directly communicating with the service providing device. Therefore, it is possible to provide the service corresponding to the user's request by transmitting the encryption key in which the usage conditions corresponding to the user's request are set.

Regarding the service providing system, the user terminal includes a terminal operation unit on which an input operation is performed, a condition setting unit that sets the usage conditions of the service providing device based on an input operation to the terminal operation unit, and the conditions. It is preferable to include an application signal transmission unit for transmitting an application signal including the usage condition information, which is information on the usage conditions set by the setting unit, to the management server.

According to such a configuration, usage conditions can be set by an input operation to the terminal operation unit of the user terminal. As a result, the management server can grasp the user's wishes without exchanging information on the usage conditions between the service providing device and the user terminal.

With respect to the service providing system, when the management server receives the application signal from the user terminal, the management server determines whether or not to permit the provision of the service corresponding to the usage conditions. When it is determined by the approval / disapproval determination that the provision of the service corresponding to the usage conditions is permitted, the encryption key is transmitted by the encryption key transmission unit, while the service corresponding to the usage conditions is transmitted by the approval / disapproval determination. When it is determined that the provision is not permitted, it is preferable to include a signal control unit for transmitting an impossible signal indicating that the provision of the service is not permitted to the user terminal.

According to such a configuration, the encryption key is transmitted when the approval / disapproval determination result is a permission determination, and is not transmitted when the approval / disapproval determination result is a disapproval determination. As a result, it is possible to prevent the service from being provided to a user who is not permitted by the management server. Further, when the pass / fail judgment result is the pass / fail judgment, the pass / fail signal is transmitted. As a result, the user terminal can grasp the approval / disapproval determination result.

Regarding the service providing system, the user terminal includes a terminal notification unit that notifies the user and a terminal notification control unit that controls notification of the terminal notification unit, and the terminal notification control unit is the user. When the terminal receives the encryption key, the terminal notification unit may be used to perform encryption key notification to notify the encryption key.

According to such a configuration, the user can recognize the encryption key by the encryption key notification. As a result, the user can accept the encryption key from the reception unit. As a result, the encryption key can be accepted without requiring a third party such as an administrator.

Regarding the service providing system, the user terminal includes a terminal notification unit that notifies a user and a terminal notification control unit that controls notification of the terminal notification unit, and the terminal notification control unit is the user. When the terminal receives the impossible signal, it is preferable to use the terminal notification unit to perform non-notification to notify that the service corresponding to the usage conditions cannot be provided.

According to such a configuration, it is possible for the user to recognize that the service cannot be provided due to the non-notification. In particular, since the non-notification is performed not by the service providing device but by the user terminal held by the user, it is possible to prevent the user from overlooking the non-notification.

Regarding the service providing system, the service providing device has a device short-range communication unit that performs short-range communication, and the user terminal has a terminal short-range communication unit that performs short-range communication with the device short-range communication unit. Then, when the user terminal receives the encryption key, the terminal short-range communication unit transmits the encryption key to the device short-range communication unit, and the reception unit receives the device short-range communication unit. Accepts the encryption key based on the receipt of the encryption key.

According to such a configuration, the user can accept the encryption key to the reception unit without directly inputting the encryption key. As a result, it is possible to simplify the procedure for providing the service.

The management server that achieves the above object has a reception unit that accepts an encryption key including usage condition information that is information on usage conditions of the service providing device, and the usage conditions based on the reception unit accepting the encryption key. It manages the service providing device having the service execution unit that provides the service corresponding to the above, and the management server communicates with the user terminal but does not directly communicate with the service providing device. It is characterized by including an encryption key transmission unit for transmitting the encryption key toward the user terminal.

A service providing device that achieves the above object is managed by a management server having a management communication unit that communicates with a user terminal, and does not directly communicate with the management server, and information on usage conditions of the service providing device. It is provided with a reception unit that accepts an encryption key including usage condition information, and a service execution unit that provides a service corresponding to the usage conditions based on the reception unit accepting the encryption key. It is characterized by.

The management service providing program that achieves the above object is based on a reception unit that accepts an encryption key including usage condition information that is information on usage conditions of the service providing device, and the reception unit that accepts the encryption key. It is for providing a service by using the service execution unit that provides the service corresponding to the usage conditions and the service providing device that is provided and managed by the management server, and communicates with the user terminal. The management server, which does not directly communicate with the service providing device, functions as an encryption key transmission unit for transmitting the encryption key to the user terminal.

The device service providing program that achieves the above object is for providing a service using a service providing device managed by a management server having a management communication unit that communicates with a user terminal, and the management server. The service providing device that does not directly communicate with the service providing device is based on a reception unit that accepts an encryption key including usage condition information that is information on usage conditions of the service providing device, and a reception unit that accepts the encryption key. It is characterized in that it functions as a service execution unit that provides a service corresponding to the above-mentioned usage conditions.

The service providing method that achieves the above object is to provide a service by using a service providing device that is managed by a management server that communicates with the user terminal and does not directly communicate with the management server. A transmission step in which the server transmits an encryption key including usage condition information which is information on usage conditions of the service providing device to the user terminal, a reception step in which the service providing device accepts the encryption key, and the above. The service providing device is characterized by comprising a service execution step of providing a service corresponding to the usage conditions based on the acceptance of the encryption key.

According to each of the above configurations, it is possible to provide a service corresponding to the usage conditions without directly communicating with the service providing device and the management server. Further, since the encryption key is transmitted to the user terminal, the user can perform the reception procedure for the reception unit, and the user terminal can perform the reception procedure for the reception unit. As a result, it is possible to provide the service corresponding to the usage conditions without requiring a third party such as an administrator who manages the service providing device.

According to the present invention, the service can be provided by using the service providing device without the service providing device and the management server directly communicating with each other.

Schematic diagram of the service provision system. Block diagram of the service providing system. Flow chart of device service processing, terminal service processing, management service processing, and payment service processing. Flowchart of application processing. Front view of the device touch panel on which the condition selection screen is displayed. Front view of the device touch panel on which the confirmation screen is displayed. Front view of the device touch panel on which the payment selection screen is displayed. Front view of the device touch panel on which the transmission screen is displayed. Flowchart of authentication support processing. Flowchart of charge control processing. Front view of the user terminal with the authentication information displayed on the terminal touch panel. Front view of the device touch panel on which the authentication acceptance screen is displayed. The block diagram of the service providing system of 2nd Embodiment. The flowchart of the application process of the third embodiment. Front view of the device touch panel on which another confirmation screen is displayed.

(First Embodiment)
Hereinafter, the first embodiment of the service providing system, the service providing device, the management server, the management service providing program, the device service providing program, and the service providing method will be described.

As shown in FIGS. 1 and 2, the service providing system 10 includes a charging device 20 as a service providing device, a user terminal 30, and a management server 40.
The charging device 20 is a device that provides a service, for example, a charging service for a power storage device 101 mounted on a vehicle 100. In the present embodiment, charging of the vehicle 100 (specifically, the power storage device 101) by the charging device 20 corresponds to "providing a service".

The charging device 20 has, for example, a rectangular parallelepiped shape that stands up from the ground. The charging device 20 has a charging connector 21, and charging can be performed by connecting the charging connector 21 to the vehicle 100. However, the charging method is not limited to the wired type using the charging connector 21, and a non-contact type charging method using electromagnetic induction, magnetic resonance, or the like may be used.

The vehicle 100 is arbitrary as long as it has a power storage device 101 and a motor that is rotated by the electric power of the power storage device 101, and is, for example, a plug-in hybrid vehicle, an electric vehicle, or the like. The power storage device 101 is arbitrary, for example, a secondary battery or an electric double layer capacitor.

As shown in FIG. 2, the charging device 20 is a device CPU 26 that controls the charging unit 22, the device touch panel 23, the device touch sensor 24, the state detection unit 25, the charging unit 22, and the display control of the device touch panel 23. And the device memory 27.

The charging unit 22 supplies charging power to the vehicle 100 via the charging connector 21. The charging unit 22 includes an AC / DC conversion circuit that converts AC power such as a system power supply into DC power.

As shown in FIG. 1, the device touch panel 23 is formed at a position visible to the user in the charging device 20, and is formed on one side surface of the charging device 20 in the present embodiment. The device touch panel 23 has, for example, a rectangular shape having a longitudinal direction and a lateral direction. By displaying a desired image, the device touch panel 23 transmits information to the user terminal 30 and notifies the user.

Further, the device touch panel 23 is input-operated. The user or administrator can perform an input operation (specifically, a touch operation or a slide operation) on the device touch panel 23.

In the present embodiment, the device touch panel 23 corresponds to the “device operation unit”. The device touch panel 23 can also be said to be a device display unit. Further, paying attention to the fact that the device touch panel 23 is used to perform various notifications to the user, the device touch panel 23 can be said to be a device notification unit.

The device touch sensor 24 detects an input operation on the device touch panel 23, which is a kind of operation on the charging device 20. Specifically, the device touch sensor 24 detects whether or not the finger is in contact with the device touch panel 23, and if the finger contact is detected, detects the position. Then, the device touch sensor 24 outputs the detection result to the device CPU 26. As a result, the device CPU 26 can grasp the input operation for the device touch panel 23. The specific configuration of the device touch sensor 24 is arbitrary, but there are, for example, a capacitance type sensor and a pressure sensor that detect based on a change in capacitance.

The state detection unit 25 detects the state of the charging device 20 including the abnormality of the charging device 20. For example, the state detection unit 25 detects the operation mode of the charging device 20, detects the presence or absence of an abnormality in the charging device 20, and outputs a detection signal in which the detection result is set to the device CPU 26.

The operation mode of the charging device 20 includes, for example, at least one of the voltage or current of the charging power supplied to the power storage device 101 of the vehicle 100 and the temperature of the charging unit 22.
The abnormality of the charging device 20 includes, for example, an abnormality of the charging unit 22 or the device touch panel 23. The abnormalities of the charging unit 22 include, for example, the charging unit 22 does not operate normally and charging cannot be started, an overcurrent abnormality in which a current exceeding the upper limit value flows through the charging unit 22 during charging, and a current in the charging unit 22 during charging. It is conceivable that there is an insulation abnormality in which the current does not flow, a temperature abnormality in which the temperature of the charging unit 22 exceeds the specified temperature during charging, or the charging cannot be stopped. The state detection unit 25 has various sensors for detecting the abnormality of the charging unit 22.

The device CPU 26 executes various processes using various programs stored in the device memory 27. For example, a program related to image control of the device touch panel 23 is stored in the device memory 27, and the device CPU 26 controls the display of the device touch panel 23 by reading and executing the program. In the present embodiment, the device CPU 26 can be said to be a device notification control unit (or device display control unit) that performs notification control (specifically, display control) of the device touch panel 23.

As shown in FIG. 2, the device memory 27 is provided with a maintenance information storage unit 27a in which maintenance information D1 related to maintenance of the charging device 20 is stored.
The maintenance information D1 is information used for maintenance of the charging device 20. For example, the maintenance information D1 includes abnormality information De, which is information regarding an abnormality of the charging device 20. The abnormality information De includes information indicating that an abnormality has been detected by the state detection unit 25. Further, the abnormality information De includes at least one of an abnormality of the charging unit 22, an abnormal operation or abnormal operation performed before or during charging, and a power supply from the outside such as a power failure being stopped. It may be configured.

The device CPU 26 updates the maintenance information D1 stored in the maintenance information storage unit 27a based on the detection signal input from the state detection unit 25, the control mode of the charging unit 22, and the like. For example, when a predetermined abnormality of the charging device 20 is detected by the state detection unit 25, the device CPU 26 performs maintenance information D1 so that the abnormality information De indicating the predetermined abnormality is reflected (in other words, saved). To update.

The user terminal 30 is an operation terminal having a wide area communication function, and communicates with the management server 40 via the wide area communication network. The user terminal 30 is basically a terminal owned by a user who intends to use the service. The user terminal 30 is a general-purpose product such as a smartphone or a tablet terminal.

As shown in FIGS. 1 and 2, the user terminal 30 includes a terminal touch panel 31, a terminal touch sensor 32, a terminal communication unit 33, an acquisition device 34, a terminal CPU 35, and a terminal memory 36. ..

As shown in FIG. 1, the terminal touch panel 31 has a rectangular shape having a longitudinal direction and a lateral direction. In the present embodiment, the terminal touch panel 31 is smaller than the device touch panel 23. The terminal touch panel 31 notifies the user, and in detail, displays a desired image. In the present embodiment, the terminal touch panel 31 corresponds to the "terminal operation unit" and the "terminal notification unit".

The terminal touch sensor 32 detects an input operation (specifically, a touch operation or a slide operation) on the terminal touch panel 31, which is a kind of operation on the user terminal 30. Specifically, the terminal touch sensor 32 detects whether or not the finger is in contact with the terminal touch panel 31, and if the finger contact is detected, detects the position. Then, the terminal touch sensor 32 outputs the detection result to the terminal CPU 35. As a result, the terminal CPU 35 can grasp the input operation for the terminal touch panel 31.

The terminal communication unit 33 is a communication interface for communicating with the management server 40, for example, via the Internet NT1 as a wide area communication network. The terminal communication unit 33 may correspond to a mobile communication system so as to be directly connected to the Internet NT1, or may communicate with a device connected to the Internet NT1.

The wide area communication network is arbitrary, and may be, for example, a telephone line. Further, the wide area communication network may be a dedicated line such as VPN. In this case, it is advisable to pre-register the user terminal 30 to be used in the management server 40.

The acquisition device 34 is used to acquire information separately from the terminal communication unit 33. In the present embodiment, the acquisition device 34 acquires the information transmitted from the device touch panel 23. For example, the acquisition device 34 reads a code including various information such as a QR code (registered trademark) and a bar code, and is specifically a camera.

The terminal CPU 35 executes various processes using various programs stored in the terminal memory 36. Specifically, a program related to image control of the terminal touch panel 31 is stored in the terminal memory 36, and the terminal CPU 35 controls the display of the terminal touch panel 31 by reading and executing the program. In the present embodiment, it can be said that the terminal CPU 35 is a "terminal notification control unit (or terminal display control unit)" that performs notification control (specifically, display control) using the terminal touch panel 31.

As shown in FIGS. 1 and 2, the management server 40 manages a plurality of charging devices 20. The management server 40 includes a management communication unit 41 that communicates with the user terminal 30 via the Internet NT1. On the other hand, the charging device 20 of the present embodiment does not have a communication unit connected to the Internet NT1. Therefore, the charging device 20 and the management server 40 do not directly communicate with each other. That is, the charging device 20 of the present embodiment is configured so as not to directly communicate with the management server 40.

As shown in FIG. 2, the management server 40 includes a management CPU 42 and a management memory 43.
The management CPU 42 is electrically connected to the management communication unit 41, and various signals from the user terminal 30 are input to the management CPU 42. By executing various programs stored in the management memory 43, the management CPU 42 determines whether or not the charging device 20 can provide the service based on the usage application from the user terminal 30, and manages the charging device 20. Details will be described later.

The management memory 43 is provided with a management information storage unit 43a in which the management information D2, which is information related to the management of the charging device 20, is stored. The management information D2 includes, for example, information indicating the current state such as whether or not the service is being provided, maintenance information D1, and usage record information indicating the charging history and the like. Management information D2 for each charging device 20 is stored in the management memory 43.

As shown in FIGS. 1 and 2, the management server 40 is configured to be able to communicate with the payment server 50 that performs electronic payment. The payment server 50 has a payment CPU 51 and a payment memory 52. The payment memory 52 stores a payment service processing program 52a, which is a program used for performing payment processing, and payment data 52b required for payment processing. The payment data 52b includes personal information necessary for payment processing, for example, credit card number and electronic money balance information.

The management server 40 is configured to make a collation request (in other words, a payment application) to the payment server 50. By executing the payment service process, the payment CPU 51 responds to the collation request from the management server 40 while referring to the payment data 52b.

That is, in the present embodiment, the management server 40 and the payment server 50 are separately provided, and the information required for the payment process is stored in the payment memory 52 instead of the management memory 43. The payment server 50 is not included in the configuration requirements of the service providing system 10. The service providing system 10 only needs to have a management server 40 capable of communicating with the payment server 50 (specifically, collation request / payment result notification reception), and has the payment server 50. No need.

Here, the service providing system 10 is configured to provide a service using the user terminal 30 without direct communication between the charging device 20 which is a service providing device and the management server 40. Hereinafter, a configuration related to service provision by the charging device 20 using the user terminal 30 will be described.

In the service providing system 10 of the present embodiment, whether or not the charging device 20, the user terminal 30, and the management server 40 are allowed to provide the service corresponding to the usage conditions by executing the processing related to the service provision, respectively. It is configured to determine whether or not it is possible and to provide services corresponding to the terms of use.

Specifically, as shown in FIG. 2, the device memory 27 stores a device service processing program 27b for providing services by the charging unit 22. The device service processing program 27b is a program used by the charging device 20 to execute device service processing for providing a service corresponding to the usage conditions. The device CPU 26 reads the device service processing program 27b and executes the device service process to control the charging unit 22 so that the service corresponding to the usage conditions is provided. In the present embodiment, the device service processing program 27b corresponds to the “device service providing program”.

In the present embodiment, the device service process is executed when the charging device 20 is turned on. Further, the device service process ends after executing the process related to the provision of a series of services to one vehicle 100, and is executed again. That is, the device service process is repeatedly executed when the charging device 20 is turned on. As a result, the charging device 20 is basically executing the device service process.

The terminal memory 36 stores a terminal service processing program 36a used by the charging device 20 to execute a terminal service process for providing a service corresponding to the usage conditions. The terminal service processing program 36a is, for example, an application program. The terminal CPU 35 reads the terminal service processing program 36a based on the touch operation of the application icon displayed on the terminal touch panel 31, for example, and executes the terminal service processing to provide a service corresponding to the usage conditions. A usage application is made to the management server 40 so as to be provided, and a notification of the application result is received.

The management service processing program 43b is stored in the management memory 43. The management CPU 42 reads the management service processing program 43b and executes the management service processing to perform a pass / fail determination or the like while communicating with the payment server 50. In the present embodiment, the management service processing program 43b corresponds to the “management service providing program”.

Hereinafter, device service processing, terminal service processing, management service processing, and payment service processing will be described with reference to FIGS. 3 to 12.
As shown in FIG. 3, in the present embodiment, the device CPU 26 and the terminal CPU 35 first execute an application process for making a usage application to the management server 40. The application process will be described with reference to FIG.

As shown in FIG. 4, the device CPU 26 first sets the usage conditions of the charging device 20 based on the input operation from the user in steps S101 to S105, and the usage condition information which is the information regarding the set usage conditions. A process for transmitting D3 to the user terminal 30 is executed. In the present embodiment, the device CPU 26 executes a process for transmitting maintenance information D1 to the user terminal 30 in addition to the usage condition information D3.

Specifically, the apparatus CPU 26 waits until the start operation is performed in step S101. For example, the device CPU 26 displays a screen on which the charging start icon is displayed on the device touch panel 23 after executing the device service process. In this case, the start operation is a touch operation on the charge start icon.

However, the start operation is not limited to this and is arbitrary. For example, when the charging device 20 is provided with a start operation button, the start operation may be performed by operating the start operation button. Further, the start operation may be such that the charging connector 21 is connected to the vehicle 100. Further, if the charging device 20 has a vehicle detection sensor for detecting the surrounding vehicle 100, the start operation is to arrange the vehicle 100 around the charging device 20, that is, the vehicle can be moved by the vehicle detection sensor. It may be detected.

When the start operation is performed, in detail, when the device touch sensor 24 detects the touch operation to the charging start icon, the device CPU 26 performs the usage condition setting process for setting the usage conditions in step S102. Execute. Specifically, the device CPU 26 causes the device touch panel 23 to display a condition selection screen G1 that allows the user to select usage conditions.

As shown in FIG. 5, the condition selection screen G1 is a screen that allows the user to select usage conditions. In this embodiment, the usage period is adopted as the usage condition. A plurality of usage condition icons Ic1 to Ic8 are displayed on the condition selection screen G1. Each usage condition icon Ic1 to Ic8 is an icon indicating that the usage conditions are different. The usage condition icons Ic1 to Ic8 in the present embodiment indicate different usage periods.

The device CPU 26 waits until the usage conditions are selected, and in detail, until a touch operation for any of the usage condition icons Ic1 to Ic8 is performed. Then, the device CPU 26 displays the confirmation screen G2 when any one of the usage condition icons Ic1 to Ic8 is touched.

As shown in FIG. 6, the selected usage period, the confirmation icon Ic11, and the return icon Ic12 are displayed on the confirmation screen G2. When a confirmation operation (for example, a touch operation on the confirmation icon Ic11) is performed, the device CPU 26 sets the usage period selected this time as a usage condition, and proceeds to step S103. On the other hand, when the return icon Ic12 is touched, the device CPU 26 displays the condition selection screen G1 again and waits until the usage conditions are re-entered.

As shown in FIG. 4, in the following step S103, the device CPU 26 executes a payment method setting process for setting a payment method. Specifically, the device CPU 26 causes the user to display a payment selection screen G3 for selecting a payment method.

As shown in FIG. 7, a plurality of payment icons Ic21 to Ic26 are displayed on the payment selection screen G3. The plurality of payment icons Ic21 to Ic26 are icons indicating different payment methods. When a touch operation is performed on any of the payment icons Ic21 to Ic26, the device CPU 26 sets a payment method corresponding to the payment icon for which the touch operation is performed as the payment method this time, and sets the payment method in step S104. move on.

The device CPU 26 may display a confirmation screen based on the touch operation performed on any of the payment icons Ic21 to Ic26. In this case, the device CPU 26 may set the payment method by performing the confirmation operation.

As shown in FIG. 4, in step S104, the apparatus CPU 26 grasps the maintenance information D1 stored in the maintenance information storage unit 27a.
After that, in step S105, the device CPU 26 transmits the usage condition information D3 regarding the usage conditions set in step S102 and the payment method information D4 regarding the payment method set in step S103 to the user terminal 30. Perform the transmission process to do so. In the present embodiment, the device CPU 26 displays a transmission screen G4 on which the usage code C1 in which the usage condition information D3 and the payment method information D4 are set is displayed.

As shown in FIG. 8, the transmission screen G4 displays the usage code C1 and prompts the user to read the usage code C1. The usage code C1 of this embodiment is, for example, a QR code (registered trademark). However, the specific configuration of the usage code C1 is arbitrary, and may be, for example, another two-dimensional code or a one-dimensional code such as a bar code.

Here, the usage code C1 in the present embodiment includes a plurality of information in addition to the usage condition information D3 and the payment method information D4. For example, the usage code C1 includes usage condition information D3, payment method information D4, identification information D5 of the charging device 20, and maintenance information D1. The identification information D5 is information for identifying the charging device 20, for example, information indicating an identification number (in other words, an ID number) assigned to each charging device 20.

In the application process, the terminal CPU 35 acquires information from the charging device 20 and performs a process for making a usage application to the management server 40.
Specifically, as shown in FIG. 4, the terminal CPU 35 executes an acquisition process of acquiring information from the charging device 20 in step S201. Specifically, the terminal CPU 35 uses the acquisition device 34 to acquire various information included in the usage code C1. For example, when the acquisition device 34 is a camera, the terminal CPU 35 waits until the usage code C1 is photographed by the camera, and based on the camera capturing the usage code C1, various information included in the usage code C1. To read.

After that, in step S202, the terminal CPU 35 executes an application signal transmission process for transmitting the application signal SG1 to the management server 40 based on the various information acquired in step S201. The application signal SG1 includes various information read in step S201, specifically, usage condition information D3, payment method information D4, identification information D5, maintenance information D1, and user information D6.

The user information D6 is information for identifying a user who is going to receive the service provided by the charging device 20 this time. The user information D6 of the present embodiment may be any information as long as the payment server 50 performing payment can identify the user, and for example, the identification number of the user or the user terminal 30 registered in the payment server 50 can be considered. The information about the user may be registered at least in the payment server 50, and the management server 40 may or may not be registered.

According to such a configuration, a usage application corresponding to the usage conditions and the payment method selected by the user is made to the management server 40 via the user terminal 30. Further, the maintenance information D1 is transmitted to the management server 40 via the user terminal 30 in accordance with the usage application.

As shown in FIG. 3, in the management service process executed by the management CPU 42 and the payment service process executed by the payment CPU 51, the authentication support process that determines whether or not the management server 40 receives the application signal SG1. Is done. Further, the authentication-corresponding process of the present embodiment includes a process related to maintenance of the charging device 20.

The authentication correspondence process will be described with reference to FIG.
As shown in FIG. 9, the management CPU 42 waits in step S301 until the management server 40 receives the application signal SG1. When the application signal SG1 transmitted from the user terminal 30 via the Internet NT1 is received by the management server 40, the management CPU 42 proceeds to step S302.

In step S302, the management CPU 42 grasps the target charging device 20 and the usage conditions applied for this time from the identification information D5 and the usage condition information D3 included in the application signal SG1.
In the following step S303, the management CPU 42 performs a usage determination for determining whether or not the target charging device 20 is available, as a kind of availability determination.

The usage determination includes, for example, determining whether or not the target charging device 20 has an abnormality. Specifically, the management CPU 42 determines whether or not there is an abnormality in the charging device 20 based on the abnormality information De of the maintenance information D1 included in the application signal SG1 received this time, and determines that the charging device 20 can be used if there is no abnormality. On the other hand, if there is an abnormality, it is judged that it cannot be used.

Further, when the service providing system 10 is configured to be able to make a reservation for the charging device 20, the usage determination includes determining whether or not a usage reservation is made for the target charging device 20. Good. In this case, the management CPU 42 determines that the target charging device 20 can be used when there is no usage reservation or when the usage period applied for this time and the reservation period do not overlap. On the other hand, the management CPU 42 determines that the service cannot be used when at least a part of the reservation period overlaps with the usage period.

When the management CPU 42 determines that the product cannot be used by the usage determination, the management CPU 42 proceeds to step S309 assuming that the availability determination result is the unavailability determination.
On the other hand, when the management CPU 42 determines that the service can be used by the usage determination, the management CPU 42 performs a payment determination in steps S304 to S307 to determine whether or not payment for the service corresponding to the current usage conditions is possible. ..

First, the management CPU 42 calculates the amount of money corresponding to the usage conditions applied for this time in step S304.
The specific configuration for calculating the amount of money is arbitrary, and may be calculated based on, for example, the usage period, or may be calculated based on the amount of charging power. In addition, the amount may be an approximate value rather than an accurate value.

After that, in step S305, the management CPU 42 executes a collation request process for requesting the settlement server 50 for collation. In the collation request process, the management CPU 42 grasps the settlement method set in the settlement method information D4 and transmits the verification request signal SG2 to the settlement server 50 corresponding to the settlement method. The collation request signal SG2 includes the user information D6 included in the application signal SG1 and the amount of money calculated in step S304.

Then, after executing the process of step S305, the settlement CPU 51 waits until the settlement result is received in step S306.
The settlement CPU 51 of the settlement server 50 corresponding to the settlement method selected this time is waiting in step S401 until the verification request signal SG2 is received. When the settlement CPU 51 receives the collation request signal SG2, the settlement CPU 51 proceeds to step S402 and executes the settlement process. Specifically, the payment CPU 51 identifies a user from the user information D6, and withdraws the amount set by the collation request signal SG2 from the payment system such as a credit card or electronic money corresponding to the user.

After that, the settlement CPU 51 notifies the management server 40 of the settlement result in step S403. Specifically, when the payment process in step S402 is normally performed, the payment CPU 51 gives a payment success notification indicating that the payment has been performed normally, while the payment process in step S402 is normally performed. If not, a payment failure notification is sent to indicate that the payment could not be made. The case where the payment process is not performed normally is, for example, the case where the credit card cannot be used, or the case where the balance of electronic money is insufficient.

As shown in FIG. 9, the management CPU 42 proceeds to step S307 based on the notification of the payment result, and determines whether or not the current payment result is successful. If the payment result this time is successful, the management CPU 42 determines that the payment determination result is an affirmative determination (that is, the approval / disapproval determination result is a permission determination), proceeds to step S308, and uses the management communication unit 41 to use the management communication unit 41 to use the user terminal. The authentication signal transmission process for transmitting the authentication signal SG3 toward 30 is executed, and then the process proceeds to step S310.

The authentication signal SG3 is a permission signal indicating that the provision of the service corresponding to the usage conditions is permitted. The authentication signal SG3 includes the authentication information D7. The authentication information D7 of the present embodiment includes, for example, usage condition information D3 which is information regarding usage conditions of the charging device 20. The authentication information D7 of the present embodiment is an encryption key including the usage condition information D3, and is indicated by, for example, an encrypted numerical code associated with the usage condition information D3. However, the present invention is not limited to this, and the authentication information D7 may be an encrypted character code or graphic code.

In the present embodiment, the transmission / reception of the authentication signal SG3 can be said to be the transmission / reception of the encryption key (in other words, the authentication information D7). Further, the authentication signal transmission process corresponds to the "transmission step", and the management CPU 42 that executes the authentication signal transmission process corresponds to the "encryption key transmission unit".

On the other hand, when the payment result is unsuccessful, the management CPU 42 assumes that the payment determination result is a negative determination (that is, the approval / disapproval determination result is an unacceptable determination), and does not execute the authentication signal transmission process in step S308. Proceed to S309. In step S309, the management CPU 42 executes a non-signal transmission process for transmitting a non-signal SG4 indicating that the provision of the service is not permitted (in other words, the service cannot be used), and proceeds to step S310. In other words, the management CPU 42 executes the authentication signal transmission process so that the authentication signal SG3 is not transmitted when the approval / disapproval determination result is the disapproval determination, or in detail, when the usage determination or the payment determination is negatively determined. It can be said that it is prohibited.

That is, the management CPU 42 permits the provision of the service corresponding to the usage conditions when the usage determination result is the affirmative determination and the payment determination result is the affirmative determination (that is, the approval / disapproval determination result is the permission determination). The transmission of the authentication signal SG3 is permitted. On the other hand, when at least one of the usage determination result and the payment determination result is a negative determination, the management CPU 42 does not permit the provision of the service corresponding to the usage condition (that is, the approval / disapproval determination result is the disapproval determination). The signal SG4 is transmitted. As a result, the user terminal 30 can recognize the approval / disapproval determination result by receiving either the authentication signal SG3 or the non-performing signal SG4.

Further, in the present embodiment, whether or not to permit the provision of the service corresponding to the usage conditions is determined by (A) whether or not the target charging device 20 can provide the service corresponding to the usage conditions. And, (B) Includes payment determination as to whether or not payment is possible for the provision of services corresponding to the terms of use. In the present embodiment, the processes of steps S303 to S307 correspond to the "possibility determination step", and the management CPU 42 that executes the processes of steps S303 to S307 corresponds to the "possibility determination unit".

After executing the process of step S308 or step S309, the management CPU 42 executes the maintenance support process related to the maintenance of the charging device 20 in step S310, and ends the authentication support process.

In the maintenance support process, the management CPU 42 updates the management information D2 based on the maintenance information D1 of the application signal SG1 received this time. Specifically, the management CPU 42 updates the management information D2 stored in the management information storage unit 43a so that the maintenance information D1 of the application signal SG1 received this time is reflected. As a result, the maintenance information D1 of the management information D2 is updated to the latest information. Further, the management CPU 42 updates the information indicating the state of the target charging device 20 in the management information D2 to the information indicating that the service is being provided.

As shown in FIG. 3, in steps S203 to S206, the terminal CPU 35 executes the process corresponding to the signal (specifically, the authentication signal SG3 or the non-authentication signal SG4) transmitted from the management server 40 by the authentication correspondence process.

Specifically, first, the terminal CPU 35 determines in step S203 whether or not the authentication signal SG3 is received, and if the authentication signal SG3 is not received, the terminal CPU 35 receives the impossibility signal SG4 in step S204. Judge whether or not. Then, if the terminal CPU 35 has not received the impossibility signal SG4, the terminal CPU 35 returns to step S203. That is, after transmitting the application signal SG1, the terminal CPU 35 waits until it receives either the authentication signal SG3 or the impossibility signal SG4.

When the terminal communication unit 33 receives the authentication signal SG3, the terminal CPU 35 positively determines step S203 and proceeds to step S205 to charge the authentication information D7 (in other words, the encryption key) included in the authentication signal SG3 to the charging device 20. Performs processing to communicate to. Specifically, the terminal CPU 35 uses the terminal touch panel 31 as the terminal notification unit to perform authentication notification for notifying the authentication information D7. Considering that the authentication information D7 is an encryption key, the authentication notification can be said to be an encryption key notification.

In the present embodiment, as shown in FIG. 11, the terminal CPU 35 causes the authentication information D7 to be displayed on the terminal touch panel 31. As described above, since the authentication information D7 of the present embodiment is an encrypted number code, the number code is displayed. As a result, the user can recognize the authentication information D7. After that, the terminal CPU 35 ends the terminal service processing. In the present embodiment, the process of step S205 corresponds to "encryption key notification".

On the other hand, when the terminal communication unit 33 receives the unavailability signal SG4, the terminal CPU 35 positively determines step S204, proceeds to step S206, and executes error processing corresponding to unavailability. The error processing of the present embodiment includes a non-notification that notifies that the service corresponding to the usage conditions cannot be provided. For example, the terminal CPU 35 as the terminal notification control unit causes the terminal touch panel 31 to display that the service corresponding to the usage conditions cannot be provided. That is, the non-notification of the present embodiment is a non-display using the terminal touch panel 31. After that, the terminal CPU 35 ends the terminal service processing.

As shown in FIG. 3, after executing the application process (specifically, the process of step S105), the device CPU 26 provides a service corresponding to the usage conditions based on the reception of the authentication information D7 (in other words, the encryption key). The charge control process for performing (charging the vehicle 100 in the present embodiment) is executed.

The charge control process will be described with reference to FIG.
As shown in FIG. 10, the apparatus CPU 26 first waits in step S106 until the authentication information D7 is accepted.

In the present embodiment, the transmission screen G4 is displayed on the device touch panel 23 by the transmission process in step S105. As shown in FIG. 8, the transmission screen G4 displays a guide icon Ic30 that guides the user to the authentication reception screen G5, which is an input screen for the authentication information D7. When the guide icon Ic30 is touched, the management CPU 42 switches the screen displayed on the device touch panel 23 from the transmission screen G4 to the authentication acceptance screen G5.

As shown in FIG. 12, on the authentication acceptance screen G5, a display area Ic31 in which the input authentication information D7 is displayed and an input icon Ic32 are displayed. The input icon Ic32 corresponds to the format of the authentication information D7. In the present embodiment, the input icon Ic32 is a numeric keypad so that the authentication information D7 is a numeric code. As a result, the user can input the authentication information D7 displayed on the terminal touch panel 31 into the charging device 20 by performing a touch operation on the input icon Ic32. Further, the input information is displayed in the display area Ic31.

In the present embodiment, the device service processing program 27b has a database in which the predetermined correct authentication information D7 is stored. The device CPU 26 determines whether or not the authentication information D7 input to the device touch panel 23 is correct by referring to the above database.

As shown in FIG. 10, when the correct authentication information D7 is input, the apparatus CPU 26 assumes that the authentication information D7 has been accepted, in other words, the acceptance procedure of the authentication information D7 has been completed, and proceeds to steps S107 to S110. And provide services that correspond to the terms of use.

Specifically, the device CPU 26 first grasps the usage conditions in step S107 based on the authentication information D7 input to the device touch panel 23. For example, the device service processing program 27b has a reading program that reads the usage condition information D3 included in the authentication information D7. The apparatus CPU 26 grasps the usage conditions from the authentication information D7 by executing the reading program.

After that, the apparatus CPU 26 starts providing the service in step S108. In the present embodiment, the device CPU 26 confirms that the charging connector 21 is connected to the vehicle 100, and controls the charging unit 22 so that charging of the vehicle 100 is started. Further, the device CPU 26 starts counting the charging period.

In the following step S109, the device CPU 26 determines whether or not the provision of the service corresponding to the usage conditions grasped in step S107 is completed. In the present embodiment, the device CPU 26 determines whether or not the charging period has reached the usage period grasped in step S107. In the present embodiment, the device CPU 26 continues to provide (charge) the service until the provision of the service corresponding to the usage conditions is completed.

The device CPU 26 proceeds to step S110 and executes a process of terminating the service based on the completion of the service corresponding to the usage condition, that is, the charging period has reached the usage period. In the present embodiment, the device CPU 26 controls the charging unit 22 so that the supply of charging power to the vehicle 100 is stopped.

After that, in step S111, the device CPU 26 executes a service end notification process for notifying that the service has been provided, and ends the main charge control process. The service end notification process is, for example, a process of displaying the fact that charging is completed on the device touch panel 23.

In the present embodiment, the device CPU 26 that executes the process of step S106 corresponds to the “reception unit”, and the device CPU 26 that executes the process of steps S107 to S110 corresponds to the “service execution unit”. Further, the device CPU 26 that executes the usage condition setting process in step S102 corresponds to the "condition setting unit", and the device CPU 26 that executes the transmission process in step S105 corresponds to the "transmission unit".

The terminal CPU 35 that executes the application signal transmission process in step S202 corresponds to the “application signal transmission unit”.
The management CPU 42 that executes the processes of steps S303 to S307 corresponds to the “possibility determination unit”. The management CPU 42 that executes the process of affirming step S303 and step S307 and proceeding to step S308, or the process of denying step S303 or step S307 and proceeding to step S309 corresponds to the "signal control unit".

Further, it can be said that the service providing system 10 employs a service providing method of providing a service using the charging device 20 managed by the management server 40 that communicates with the user terminal 30. In this case, the process of step S106 corresponds to the "acceptance step", and the process of steps S107 to S110 corresponds to the "service execution step". Further, the transmission process of step S105 corresponds to the "transmission step", the acquisition process of step S201 corresponds to the "acquisition step", and the application signal transmission process of step S202 corresponds to the "terminal communication control step".

Next, the operation of this embodiment will be described.
Authentication information D7 as an encryption key including usage condition information D3 is transmitted from the management server 40 to the user terminal 30. Then, when the authentication information D7 is input to the device touch panel 23 of the charging device 20, a service corresponding to the usage conditions is provided.

According to the present embodiment described in detail above, the following effects are obtained.
(1-1) The service providing system 10 includes a charging device 20 that provides a service, a management server 40 that manages the charging device 20, and a user terminal 30 that communicates with the management server 40. The management server 40 includes a management CPU 42 that executes management service processing. In the management service process, the management CPU 42 executes an authentication signal transmission process for transmitting the authentication information D7 as an encryption key including the usage condition information D3 which is information on the usage conditions of the charging device 20 to the user terminal 30.

The charging device 20 does not directly communicate with the management server 40, and includes a device CPU 26. The device CPU 26 executes a process of accepting the authentication information D7 (step S106) and a process of providing a service corresponding to the usage conditions based on the acceptance of the authentication information D7 (steps S107 to S110).

According to such a configuration, it is possible to provide a service corresponding to the usage conditions without directly communicating with the charging device 20 and the management server 40. Further, since the authentication information D7 is transmitted to the user terminal 30, the user can input the authentication information D7 to the device touch panel 23 or have the charging device 20 input the authentication information D7 via the user terminal 30. .. As a result, the charging device 20 and the management server 40 do not directly communicate with each other, and a third party such as an administrator who manages the charging device 20 does not perform any procedure. The corresponding service can be provided.

(1-2) The charging device 20 includes a device touch panel 23 as a device operating unit on which an input operation is performed. The device CPU 26 executes a usage condition setting process for setting usage conditions based on an input operation on the device touch panel 23. Then, in step S105, the device CPU 26 executes a transmission process for transmitting the set usage conditions to the user terminal 30. The terminal CPU 35 of the user terminal 30 executes an application signal transmission process for transmitting the application signal SG1 including the usage condition information D3 which is information on the usage conditions transmitted from the charging device 20.

According to such a configuration, the user can set the desired usage conditions by performing an input operation on the device touch panel 23. Further, the set usage conditions are transmitted to the user terminal 30 and transmitted to the management server 40 via the user terminal 30. As a result, the management server 40 can grasp the user's wishes without directly communicating with the charging device 20. Therefore, by transmitting the authentication information D7 in which the usage conditions corresponding to the user's wishes are set, the service corresponding to the user's wishes can be provided.

(1-3) When the management CPU 42 of the management server 40 receives the application signal SG1 from the user terminal 30, in steps S303 to S307, it is determined whether or not to permit the provision of the service corresponding to the usage conditions. Make a pass / fail judgment. The management CPU 42 authenticates that the authentication information D7 as an encryption key is transmitted to the user terminal 30 when the approval / disapproval determination result is an authorization determination, that is, when it is determined that the provision of the service corresponding to the usage conditions is permitted. Execute signal transmission processing. On the other hand, when the approval / disapproval determination result is the disapproval determination, that is, when it is determined that the provision of the service corresponding to the usage conditions is not permitted, the management CPU 42 transmits the disapproval signal SG4 indicating that the service provision is not permitted. Executes the non-signal transmission process.

According to such a configuration, the encryption key is transmitted when the approval / disapproval determination result is a permission determination, and is not transmitted when the approval / disapproval determination result is a disapproval determination. As a result, it is possible to prevent the service from being provided to the user who is not permitted by the management server 40. Further, when the pass / fail determination result is the impossibility determination, the impossibility signal SG4 is transmitted. As a result, the user terminal 30 can grasp the approval / disapproval determination result.

(1-4) The user terminal 30 has a terminal touch panel 31 as a terminal notification unit that notifies the user. When the user terminal 30 receives the authentication information D7 from the management server 40, the terminal CPU 35 uses the terminal touch panel 31 to perform authentication notification as an encryption key notification for notifying the authentication information D7. In the present embodiment, the terminal CPU 35 causes the terminal touch panel 31 to display the authentication information D7.

According to such a configuration, the user can recognize the authentication information D7 by the authentication notification. As a result, the user can perform the procedure for accepting the authentication information D7, so that the procedure for accepting the authentication information D7 can be performed without requiring a third party such as an administrator.

(1-5) When the user terminal 30 receives the impossible signal SG4 from the management server 40, the terminal CPU 35 cannot notify that the service corresponding to the usage conditions cannot be provided by using the terminal touch panel 31. Notify. In the present embodiment, the terminal CPU 35 performs non-display on the terminal touch panel 31.

According to such a configuration, it is possible for the user to recognize that the service cannot be provided due to the non-notification. In particular, since the non-notification is performed not by the charging device 20 but by the user terminal 30 held by the user, it is possible to prevent the user from overlooking the non-notification.

(1-6) In the transmission process of step S105, the device CPU 26 executes a process of displaying the usage code C1 including the usage condition information D3 on the device touch panel 23. The terminal CPU 35 uses the acquisition device 34 to acquire the usage condition information D3 included in the usage code C1.

According to such a configuration, the usage condition information D3 can be easily acquired by using the user terminal 30. In particular, with this configuration, it is not necessary to make a communication connection (pairing) between the charging device 20 and the user terminal 30. This makes it possible to facilitate the transmission of the usage condition information D3.

(1-7) The management server 40 manages the charging device 20 having the device CPU 26. The device CPU 26 executes a process of accepting the authentication information D7 as an encryption key and a process of providing a service corresponding to the usage conditions based on the acceptance of the authentication information D7. The management server 40 communicates with the user terminal 30, but does not directly communicate with the charging device 20, and includes a management CPU 42 that executes an authentication signal transmission process. According to such a configuration, the effect of (1-1) is obtained.

(1-8) The management service processing program 43b as the management service providing program is for providing the service by using the charging device 20 managed by the management server 40 that communicates with the user terminal 30. The charging device 20 includes a device CPU 26, and the device CPU 26 executes a process of accepting the authentication information D7 as an encryption key and a process of providing a service corresponding to the usage conditions based on the acceptance of the authentication information D7. Is what you do. The management service processing program 43b causes the management server 40, which does not directly communicate with the charging device 20, to function as transmitting the authentication information D7 to the user terminal 30. Specifically, the management service processing program 43b causes the management CPU 42 to execute the authentication signal transmission process. According to such a configuration, the effect of (1-1) is obtained.

(1-9) The charging device 20 is managed by a management server 40 having a management communication unit 41 that communicates with the user terminal 30 and a management CPU 42 that executes an authentication signal transmission process. The charging device 20 does not directly communicate with the management server 40. The device CPU 26 of the charging device 20 executes a process of accepting the authentication information D7 as an encryption key and a process of providing a service corresponding to the usage conditions based on the acceptance of the authentication information D7. According to such a configuration, the effect of (1-1) is obtained.

(1-10) The device service processing program 27b is a program for providing a service using the charging device 20 managed by the management server 40. The management server 40 includes a management communication unit 41 and a management CPU 42 that executes an authentication signal transmission process. The device service processing program 27b is based on a process of accepting authentication information D7 as an encryption key for a charging device 20 (specifically, device CPU 26) that does not directly communicate with the management server 40, and receiving authentication information D7. It functions as a process to provide a service corresponding to the terms of use. According to such a configuration, the effect of (1-1) is obtained.

(1-11) The service providing method is to provide the service by using the charging device 20 which is managed by the management server 40 which communicates with the user terminal 30 and does not directly communicate with the management server 40. The service providing method includes step S308 as a transmission step in which the management server 40 transmits the authentication information D7 as an encryption key to the user terminal 30, and step S106 as a reception step in which the charging device 20 receives the authentication information D7. It has. The service providing method includes steps S107 to S110 in which the charging device 20 provides a service corresponding to the usage conditions based on the acceptance of the authentication information D7. According to such a configuration, the effect of (1-1) is obtained.

<Second Embodiment>
As shown in FIG. 13, the service providing system 10 of the present embodiment is configured so that the charging device 20 and the user terminal 30 perform short-range communication.

For example, the charging device 20 includes a device short-range communication unit 111 that supports short-range communication. The user terminal 30 includes a terminal short-range communication unit 112 that performs short-range communication with the device short-range communication unit 111. Both short-range communication units 111 and 112 communicate with each other when the charging device 20 and the user terminal 30 are within the communication range.

By the way, both short-range communication units 111 and 112 are not connected to the Internet NT1. Therefore, the charging device 20 and the management server 40 do not directly communicate with each other.
The device short-range communication unit 111 is electrically connected to the device CPU 26, and the terminal short-range communication unit 112 is electrically connected to the terminal CPU 35. The charging device 20 and the user terminal 30 (specifically, the device CPU 26 and the terminal CPU 35) exchange information with each other via both short-range communication units 111 and 112.

The communication format of both short-range communication units 111 and 112 may be Wi-Fi, Bluetooth (registered trademark), Zigbee (registered trademark) or the like, or communication by a non-contact IC card such as FeliCa (registered trademark). Including the method.

In the present embodiment, instead of displaying the usage code C1 and the authentication information D7, the two short-range communication units 111 and 112 communicate with each other to exchange the maintenance information D1, the usage condition information D3, and the authentication information D7. ..

For example, in step S205, the terminal CPU 35 may execute a process of transmitting the authentication information D7 to the device short-range communication unit 111 by using the terminal short-range communication unit 112. That is, in the present embodiment, when the user terminal 30 receives the authentication signal SG3, the terminal short-range communication unit 112 transmits the authentication information D7 to the device short-range communication unit 111.

In this case, in step S106, the device CPU 26 may wait until the device short-range communication unit 111 receives the authentication information D7. That is, in the present embodiment, the device CPU 26 receives the D7 authentication information based on the device short-range communication unit 111 receiving the authentication information D7. In other words, receiving the authentication information D7 by the device short-range communication unit 111 corresponds to the reception of the authentication information D7 by the reception unit.

According to the present embodiment described in detail above, the following effects are obtained.
(2-1) The charging device 20 includes a device short-range communication unit 111 that performs short-range communication. The user terminal 30 includes a terminal short-range communication unit 112 that performs short-range communication with the device short-range communication unit 111. When the user terminal 30 receives the authentication signal SG3 (specifically, the authentication information D7), the terminal short-range communication unit 112 transmits the authentication information D7 to the device short-range communication unit 111. The device CPU 26 receives the authentication information D7 based on the fact that the device short-range communication unit 111 receives the authentication information D7.

According to such a configuration, the user can perform the procedure for accepting the authentication information D7 in the charging device 20 without directly inputting the authentication information D7. As a result, it is possible to simplify the procedure for providing the service.

<Third Embodiment>
In this embodiment, the application process is different from that in the first embodiment. The differences will be described below.

As shown in FIG. 14, when the start operation is performed in step S101, the apparatus CPU 26 grasps the maintenance information D1 in step S104. Then, in step S105, the device CPU 26 executes a transmission process for transmitting the maintenance information D1 and the identification information D5 to the user terminal 30. Specifically, the device CPU 26 causes the device touch panel 23 to display the usage code C1 including the maintenance information D1 and the identification information D5.

On the other hand, the terminal CPU 35 first executes the usage condition setting process in step S211. After that, the terminal CPU 35 executes the payment method setting process for setting the payment method in step S212.

The specific configurations of the usage condition setting process and the payment method setting process are the usage condition setting process and the payment method setting of the first embodiment, except that the displayed screen is changed from the device touch panel 23 to the terminal touch panel 31. Same as processing.

In the following step S201, the terminal CPU 35 executes an acquisition process for acquiring the maintenance information D1 and the identification information D5 transmitted in step S105. Specifically, the terminal CPU 35 acquires the maintenance information D1 and the identification information D5 from the usage code C1 by using the acquisition device 34 provided in the user terminal 30.

After that, in step S202, the terminal CPU 35 executes an application signal transmission process for transmitting the application signal SG1. The application signal SG1 includes usage condition information D3 and payment method information D4 corresponding to the usage conditions and payment methods set in steps S211 and S212, identification information D5 and maintenance information D1 acquired in step S201. including.

According to the present embodiment described in detail above, the following effects are obtained.
(3-1) The user terminal 30 includes a terminal touch panel 31 on which an input operation is performed, and a terminal CPU 35 that executes a usage condition setting process for setting usage conditions based on an input operation on the terminal touch panel 31. There is. The terminal CPU 35 causes the terminal CPU 35 to transmit the application signal SG1 including the usage condition information D3 regarding the usage conditions set by the usage condition setting process.

According to such a configuration, usage conditions can be set by an input operation on the terminal touch panel 31 of the user terminal 30. As a result, the management server 40 can grasp the user's wishes without exchanging the usage condition information D3 between the charging device 20 and the user terminal 30.

Each of the above embodiments may be modified as follows. In addition, each of the above-described embodiments and the following alternative examples may be combined with each other within a technically consistent range.
○ The charging device 20 as a service providing device may be one that does not directly communicate with the management server 40, and may communicate with the management server 40 via the user terminal 30 or a device having a wide area communication function. .. For example, the charging device 20 may be provided with a connection unit to which a management device having a communication function with the Internet NT1 can be connected. The connection unit may be a connector compatible with a wired connection, a transmission / reception unit compatible with a short-distance wireless connection, or the like. In this case, by connecting the management device to the charging device 20, the charging device 20 and the management server 40 may communicate with each other via the management device. In other words, it can be said that the service providing device that does not directly communicate with the management server 40 cannot be connected to the wide area communication network (Internet NT1) by itself.

○ The service providing device is not limited to the charging device 20, but is arbitrary. For example, a parking lot management device (time parking device) may be adopted as the service providing device. In this case, the use of the parking lot corresponds to the "providing of services". In such a configuration, the usage period of the parking lot corresponds to the "use conditions". That is, the specific content of the service is arbitrary.

○ The usage conditions for charging are not limited to the charging period, but may be arbitrary, for example, the amount of electric power. Further, as a usage condition, a parking period (in other words, a parking space occupancy period) may be set separately from the charging period.

○ The management server 40 may have a configuration in which a usage management server that performs processing corresponding to usage such as approval / disapproval determination and a maintenance management server that manages maintenance may be separately provided. In this case, the usage management server and the maintenance management server may exchange information with each other.

○ The specific mode relating to the transmission of the authentication information D7 (in other words, the authentication notification) is arbitrary. For example, a graphic code such as a bar code or a QR code may be adopted as the code including the authentication information D7. In this case, the terminal CPU 35 may display the graphic code on the terminal touch panel 31. The charging device 20 may have a camera or a scanner that reads a graphic code. In such a configuration, it is preferable that the user brings the graphic code displayed on the terminal touch panel 31 closer to a position where the camera or scanner can read it. As a result, the authentication information D7 is accepted.

Further, voice data may be adopted as the authentication information D7. In this case, the reception unit may receive the authentication information D7 by voice recognition. That is, if the reception unit can acquire the authentication information D7, its specific configuration is arbitrary.

○ The specific configuration of the device notification unit is arbitrary, and is not limited to the display unit such as a touch panel or monitor, for example, it may be a speaker or a light emitting device that emits a plurality of colors, or the display unit and the speaker. It may be a combination.

○ The device operation unit is not limited to the device touch panel 23, and may be any, for example, a dedicated button or a controller. Further, the charging device 20 includes a device touch panel 23 in which a device operation unit and a device notification unit are integrated, but the present invention is not limited to this, and the device operation unit and the device notification unit may be separate bodies.

○ In each embodiment, the terminal touch panel 31 functions as a terminal notification unit and a terminal operation unit, but the present invention is not limited to this, and the terminal notification unit and the terminal operation unit may be separate bodies.
The specific configuration of the transmission process in step S105 is not limited to that of the first embodiment and the second embodiment, and is arbitrary. For example, a password in which the usage condition information D3 and the like are encrypted is displayed on the device touch panel 23. It may be in a mode of notifying the user by causing the user to perform voice guidance.

○ The specific mode of non-notification is arbitrary. For example, a speaker may be adopted as the terminal notification unit, and sound may be used to perform non-notification, or both sound and non-display may be performed.
○ The specific display mode of each screen G1 to G5 is arbitrary.

○ In addition, the input operation mode of the usage conditions and payment method is arbitrary. For example, as an input mode of the usage conditions, an operation of inputting an arbitrary period using, for example, a numeric keypad may be adopted.
-The start operation of step S101 is not essential.

○ There may be only one payment method. In this case, the payment method information D4 may be omitted from the usage code C1 and the application signal SG1.
-In the usage condition setting process of step S211 in the third embodiment, the terminal CPU 35 may execute a process of calculating the amount of money corresponding to the selected usage condition while communicating with the management server 40. In this case, as shown in FIG. 15, the terminal CPU 35 may display the calculated amount of money on the terminal touch panel 31 in addition to the selected usage conditions on the confirmation screen G2.

○ The terminal CPU 35 may be configured to transmit the position information of the user terminal 30 as the identification information D5. In this case, the management CPU 42 may specify the charging device 20 to be used this time from the position information.

In particular, when the present alternative example is adopted in the third embodiment and the transmission and acquisition of the maintenance information D1 is omitted, it is not necessary for the terminal CPU 35 to acquire the information from the charging device 20. Therefore, the processes of steps S105 and S201 can be omitted. As a result, the procedure for application for use can be completed on the user terminal 30.

○ The first embodiment and the third embodiment may be combined. That is, the service providing system 10 may be configured so that the usage conditions can be set by either the input operation to the charging device 20 or the input operation of the user terminal 30.

-In the first embodiment and the second embodiment, the apparatus CPU 26 may separately transmit the usage condition information D3 and the maintenance information D1 to the user terminal 30. Further, the terminal CPU 35 may be configured to transmit a maintenance signal including maintenance information D1 separately from the application signal SG1. In short, the maintenance information D1 does not have to be transmitted together with the usage condition information D3, and may be configured to be independently transmitted to the management server 40 via the user terminal 30.

○ The usage determination is not limited to the configuration performed based on the abnormality information De of the maintenance information D1 included in the application signal SG1 received this time, and is performed based on, for example, the maintenance information D1 of the management information D2 stored in the management server 40. It may be configured. Even in this case, it is possible to suppress the permission to provide the service even though the charging device 20 has an abnormality.

○ The management CPU 42 may execute the maintenance support process before executing the process in step S303. As a result, the management information D2 is updated to the latest information. In this case, the management CPU 42 may make a usage determination in step S303 based on the maintenance information D1 stored in the management information D2. As a result, even when the management information D2 is used, the usage determination based on the latest maintenance information D1 can be performed.

○ Usage judgment may be omitted. That is, the usage judgment is not essential.
○ Payment processing may be omitted. In this case, the application signal SG1 may not include the user information D6. That is, the user information D6 is not essential.

○ The device CPU 26 may suspend the provision of the service if the cancellation condition is satisfied during the provision of the service corresponding to the usage condition. The discontinuation condition is arbitrary, and for example, the discontinuation operation may be performed on the charging device 20 or the user terminal 30 by the user. Further, for example, when the service is provided by charging the power storage device 101, it may be adopted as a cancellation condition that the state of charge (SOC) of the power storage device 101 is 100%.

○ The number of charging devices 20 managed by the management server 40 is arbitrary, and may be one or a plurality.
○ Transmission of maintenance information D1 by the charging device 20 and acquisition of maintenance information D1 by the user terminal 30 are not essential. That is, the processing of steps S104 and S310 may be omitted, and the usage code C1 may be configured not to include the maintenance information D1.

Next, a suitable example that can be grasped from each of the above embodiments and another example will be described below.
(A) The transmission process is a process for transmitting the maintenance information and the identification information of the charging device, and the acquisition unit may acquire the maintenance information and the identification information.

(B) The management server and the user terminal may communicate with each other via the Internet.
(C) A service providing device for providing a service, a management server for managing the service providing device, and a user terminal for communicating with the management server are provided, and the service providing device relates to an abnormality of the service providing device. The user terminal includes a transmission unit that executes a transmission process for transmitting maintenance information including abnormality information to the user terminal, and the user terminal has an acquisition unit that acquires the maintenance information and the maintenance information acquired by the acquisition unit. A service providing system including a terminal communication control unit that transmits a message to the management server.

10 ... Service providing system, 20 ... Charging device (service providing device), 23 ... Device touch panel (device operation unit), 25 ... Status detection unit, 26 ... Device CPU, 27 ... Device memory, 27b ... Device service processing program (device) Service provision program), 30 ... user terminal, 31 ... terminal touch panel (terminal operation unit, terminal notification unit), 34 ... acquisition device, 35 ... terminal CPU, 40 ... management server, 41 ... management communication unit, 42 ... management CPU, 43 ... Management memory, 43b ... Management service processing program, 100 ... Vehicle, 111 ... Device short-range communication unit, 112 ... Terminal short-range communication unit, SG1 ... Application signal, SG3 ... Authentication signal, SG4 ... Impossible signal, C1 ... Use Code, D1 ... Maintenance information, De ... Abnormal information, D2 ... Management information, D3 ... Terms of use information, D7 ... Authentication information (encryption key).

Claims (12)

Service providing equipment that provides services and
A management server that manages the service providing device and
A user terminal that communicates with the management server,
With
The management server includes an encryption key transmission unit that transmits an encryption key including usage condition information which is information on usage conditions of the service providing device to the user terminal.
The service providing device does not directly communicate with the management server.
The reception section that accepts the encryption key and
A service execution unit that provides a service corresponding to the usage conditions based on the reception unit accepting the encryption key.
A service provision system characterized by being equipped with. The service providing device is
The device operation unit where input operations are performed and
A condition setting unit that sets the usage conditions based on an input operation to the device operation unit, and a condition setting unit.
A transmission unit that executes a transmission process for transmitting the usage conditions set by the condition setting unit to the user terminal, and a transmission unit.
With
The user terminal according to claim 1, further comprising an application signal transmission unit for transmitting an application signal including the usage condition information, which is information on the usage conditions transmitted from the service providing device, to the management server. Service provision system. The user terminal is
The terminal operation unit where input operations are performed and
A condition setting unit that sets the usage conditions of the service providing device based on an input operation to the terminal operation unit.
An application signal transmission unit for transmitting an application signal including the usage condition information, which is information about the usage conditions set by the condition setting unit, to the management server.
The service providing system according to claim 1. The management server
When the application signal is received from the user terminal, a propriety determination unit for determining whether or not to permit the provision of a service corresponding to the usage conditions, and a feasibility determination unit.
When it is determined by the approval / disapproval determination that the provision of the service corresponding to the usage conditions is permitted, the encryption key is transmitted by the encryption key transmission unit, while the provision of the service corresponding to the usage conditions is provided by the approval / disapproval determination. When it is determined that the service is not permitted, a signal control unit for transmitting an impossible signal indicating that the provision of the service is not permitted to the user terminal, and
2. The service providing system according to claim 2 or 3. The user terminal is
A terminal notification unit that notifies the user and
A terminal notification control unit that controls notification of the terminal notification unit,
With
The service providing system according to claim 4, wherein the terminal notification control unit uses the terminal notification unit to perform encryption key notification for notifying the encryption key when the user terminal receives the encryption key. The user terminal is
A terminal notification unit that notifies the user and
A terminal notification control unit that controls notification of the terminal notification unit,
With
When the user terminal receives the impossible signal, the terminal notification control unit uses the terminal notification unit to perform non-notification to notify that the service corresponding to the usage conditions cannot be provided. The service providing system according to claim 4 or 5. The service providing device has a device short-range communication unit that performs short-range communication.
The user terminal has a terminal short-range communication unit that performs short-range communication with the device short-range communication unit.
When the user terminal receives the encryption key, the terminal short-range communication unit transmits the encryption key to the device short-range communication unit.
The service providing system according to any one of claims 1 to 4, wherein the reception unit receives the encryption key based on the reception of the encryption key by the device short-range communication unit. A reception unit that accepts an encryption key including usage condition information that is information on usage conditions of a service providing device, and a service execution that provides a service corresponding to the usage conditions based on the reception unit accepting the encryption key. A management server that manages the service providing device having a unit and
The management server communicates with the user terminal, but does not directly communicate with the service providing device, and includes an encryption key transmission unit that transmits the encryption key toward the user terminal. A management server that features. A service providing device that is managed by a management server that has a management communication unit that communicates with the user terminal and does not directly communicate with the management server.
A reception unit that accepts an encryption key including usage condition information, which is information on usage conditions of the service providing device, and
A service execution unit that provides a service corresponding to the usage conditions based on the reception unit accepting the encryption key.
A service providing device characterized by being equipped with. A reception unit that accepts an encryption key including usage condition information that is information on usage conditions of a service providing device, and a service execution that provides a service corresponding to the usage conditions based on the reception unit accepting the encryption key. It is a management service providing program for providing a service by using the service providing device provided with a unit and managed by a management server.
A management service characterized in that the management server that communicates with the user terminal but does not directly communicate with the service providing device functions as an encryption key transmission unit that transmits the encryption key toward the user terminal. Offer program. A device service providing program for providing services using a service providing device managed by a management server having a management communication unit that communicates with a user terminal.
The service providing device that does not directly communicate with the management server
A reception unit that accepts an encryption key including usage condition information, which is information on usage conditions of the service providing device, and
A service execution unit that provides a service corresponding to the usage conditions based on the reception unit accepting the encryption key.
A device service provision program characterized by functioning as. A service providing method in which a service is provided by using a service providing device that is managed by a management server that communicates with a user terminal and does not directly communicate with the management server.
A transmission step in which the management server transmits an encryption key including usage condition information, which is information on usage conditions of the service providing device, to the user terminal.
The reception step in which the service providing device accepts the encryption key, and
A service execution step in which the service providing device provides a service corresponding to the usage conditions based on the acceptance of the encryption key.
A service provision method characterized by having.