A system, method, and computer program for using a target device in a billing service.

Abstract

In addition to the ability of the terminal device to remotely control the target device, it is also desirable that the payment process related to the use of this target device be carried out efficiently. [Solution] An embodiment of the present invention provides a system for using a target device in a billing service, comprising: a server device for managing the billing service; a target device that presents or outputs target device identification information for identifying the target device; and a user terminal device that acquires the target device identification information from the target device, and transmits the target device identification information, a user identifier for identifying the user, and information regarding the user's payment to the server device. The server device associates the target device identification information and the user identifier to permit the user to use the target device, and while permitted, can wait to receive information from the terminal device regarding operations used to operate the target device.

Description

Technical Field

[0004] , , , , , , , ,

[0005]

[0001] The present invention relates to a system, method, and computer program for allowing a target device to be used in a charging service.

Background Art

[0002] [[ID=|12]]Currently, so-called charging services (for example, car rental services, equipment usage services by subscription, electric vehicle charging services, and smartphone charging services, etc.), which are services that allow a device not owned by the user (target device) to be used by paying a predetermined fee, are frequently used. Also, due to the progress of information processing technology, there are systems in which a user can remotely control a remote device via Internet communication or the like (for example, a system in which an air conditioning device at home can be started in advance from a remote location so that the user can enter the home at a comfortable temperature and humidity).

[0003] [[ID=1|6]]Patent Document 1 discloses a configuration in which, after a user's terminal device starts charging the battery of an electric vehicle, a vehicle power supply equipment (Electric Vehicle Supply Equipment, EVSE) that the user does not own and that charges the battery of the electric vehicle is remotely controlled (paragraphs (0060), (0061), etc.).

[0004] [[ID=2|0]]However, Patent Document 1 does not disclose a configuration in which a user's terminal device realizes control related to settlement in order to start using a remote target device (for example, an electric vehicle supply device (EVSE)). Control related to settlement can include, but is not limited to the following, for example, control such as starting settlement, control of settlement for extending the use of the target device, and changing the settlement method.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

[0006] In addition to the ability of the terminal device to remotely control the target device, it is also desirable that the payment process related to the use of this target device be carried out efficiently. [Means for solving the problem]

[0007] An embodiment of the present invention provides a system for using a target device in a billing service, comprising: a server device for managing the billing service; a target device that presents or outputs target device identification information for identifying the target device; and a user terminal device that acquires the target device identification information from the target device, and transmits the target device identification information, a user identifier for identifying the user, and information regarding the user's payment to the server device, wherein the server device associates the target device identification information and the user identifier to permit the user to use the target device, and while permitted, can wait to receive information from the terminal device regarding operations used to operate the target device.

[0008] The server device, which is an embodiment of the present invention, can settle a first fee for using the target device based on the payment information.

[0009] In an embodiment of the present invention, the server device, upon receiving information regarding the operation from the terminal device, can settle the difference between the first fee and the second fee (which is the changed fee), or refund the first fee and settle the second fee, if the fee for using the target device changes from the first fee.

[0010] In an embodiment of the present invention, the server device, upon receiving information regarding the operation from the terminal device, can transmit to the terminal device or the target device, if the fee for using the target device changes from the first fee, information indicating that the settled usage fee has changed, or information indicating that the changed usage fee is the second fee.

[0011] In an embodiment of the present invention, the server device can settle the difference between the second fee and the first fee, or refund the first fee and settle the second fee, upon receiving confirmation from the terminal device or the target device that the user accepts the difference between the second fee and the first fee.

[0012] An embodiment of the present invention, a server device that manages a billing service enabling the use of a target device, receives target device identification information for identifying the target device, a user identifier for identifying a user of the billing service, and information regarding the user's payment. Furthermore, it associates the target device identification information and the user identifier to authorize the user to use the target device, and while authorized, waits to receive information from the user's terminal device regarding operations used to operate the target device.

[0013] In an embodiment of the present invention, a terminal device used by a user to operate a target device in a billing service is configured to obtain target device identification information from the target device to identify the target device, transmit the target device identification information, a user identifier to identify the user, and information regarding the user's payment to a server device, and, upon receiving information regarding the status of the target device from the server device, transmit to the server device information regarding the operation used to operate the target device.

[0014] An embodiment of the present invention, comprising a server device, a target device, and a terminal device, and a method executed by a system that allows the use of the target device in a billing service, may include the steps of: the target device presenting and outputting target device identification information for identifying the target device; the terminal device obtaining the target device identification information from the target device and transmitting the target device identification information, a user identifier for identifying the user, and information regarding the user's payment to the server device; and the server device associating the target device identification information and the user identifier to permit the user to use the target device, and waiting to receive from the terminal device information regarding operations used to operate the target device while permitted.

[0015] An embodiment of the present invention, a method performed by a server device managing a billing service that enables the use of a target device, may include the steps of: the server device receiving target device identification information for identifying the target device, a user identifier for identifying a user of the billing service, and information regarding the user's payment; and the server device associating the target device identification information and the user identifier to permit the user to use the target device, and waiting to receive information from the user's terminal device regarding operations used to operate the target device while permitted.

[0016] An embodiment of the present invention, a method executed by a terminal device of a user operating a target device in a billing service, may include the steps of: the terminal device obtaining target device identification information from the target device for identifying the target device; the terminal device transmitting the target device identification information, a user identifier for identifying the user, and information regarding the user's payment to a server device; and the terminal device transmitting to the server device information regarding an operation used to operate the target device, in response to receiving information regarding the status of the target device from the server device.

[0017] An embodiment of the present invention, comprising a server device, a target device, and a terminal device, wherein a system that allows the use of the target device in a billing service executes a computer program that includes the steps of: the target device presenting and outputting target device identification information for identifying the target device; the terminal device obtaining the target device identification information from the target device and transmitting the target device identification information, a user identifier for identifying the user, and information regarding the user's payment to the server device; and the server device associating the target device identification information and the user identifier to permit the user to use the target device, and waiting to receive from the terminal device information regarding operations used to operate the target device while permitted.

[0018] An embodiment of the present invention, a computer program executed by a server device that manages a billing service enabling the use of a target device, may include the steps of: the server device receiving target device identification information for identifying the target device, a user identifier for identifying a user of the billing service, and information regarding the user's payment; and the server device associating the target device identification information and the user identifier to permit the user to use the target device, and waiting to receive information from the user's terminal device regarding operations used to operate the target device while permitted.

[0019] A computer program executed by a terminal device of a user operating a target device in a billing service may include the steps of: the terminal device obtaining target device identification information from the target device to identify the target device; the terminal device transmitting the target device identification information, a user identifier to identify the user, and information regarding the user's payment to a server device; and the terminal device transmitting information regarding the operation used to operate the target device to the server device in response to receiving information regarding the status of the target device from the server device. [Brief explanation of the drawing]

[0020] [Figure 1] Shows a system according to an embodiment of the present invention. [Figure 2] Shows the hardware configurations of one or more terminal devices, server devices, one or more target devices, and payment devices included in the system according to an embodiment of the present invention. [Figure 3] Shows a processing flow based on the first embodiment of the present invention, in which payment is made after using the target device. [Figure 4] Shows a processing flow based on the second embodiment of the present invention, in which payment is made before using the target device. [Figure 5] Shows a processing flow based on the third embodiment of the present invention, in which payment is made before using the target device and then payment is made again. [Mode for Carrying Out the Invention]

[0021] Embodiments of the present invention will be described below, but the present invention is not limited to the following embodiments. The present invention may include technologies that can be understood by those skilled in the art based on the following descriptions, common technical knowledge, and technologies well-known at the time of filing.

[0022] In the following description, for reference strings specified in figures and the like, unless otherwise specified, the same reference strings indicate the same elements.

[0023] [System Overview]

[0024] [System Overview] Figure 1 shows a system according to an embodiment of the present invention. System 100 includes one or more terminal devices 110, a server device 115, one or more target devices 120, a payment device 125, and a network 150. The one or more terminal devices 110, the server device 115, the one or more target devices 120, and the payment device 125 are each connected to each other via the network 150 so as to be able to communicate.

[0025] One or more terminal devices 110 are devices owned by or available to the user of this system. The terminal devices 110 may include, but are not limited to, mobile phones, smartphones, watches, smartwatches, tablets, laptop computers, and the like. Typically, the terminal device 110 may be a smartphone.

[0026] One or more target devices 120 are devices used by users through a billing service and are controllable or operable by the user when in use. One or more target devices 120 are devices that become available upon request from the user. One or more target devices 120 may include, but are not limited to, electric vehicles, smartphone chargers, air conditioning units for rental offices, rental devices, subscription devices, etc.

[0027] The server device 115 can manage one or more target devices 120. Before using a target device 120 for the first time, a user can register information about themselves (for example, user identifier, user name, address, gender, age, or contact information, user payment method (credit card number, bank account number, etc.)) with the server device 115 using the terminal device 110. This allows the server device 115 to manage information about the user. By managing information about one or more target devices 120 and information about the user, the server device 115 can manage the billing service.

[0028] The server device 115 can receive information from the terminal device 110 and / or the target device 120, and can also transmit information to the terminal device 110 and / or the target device 120, or to other terminal devices 110 and / or target devices 120. This allows the terminal device 110 to control the target device 120 or other terminal devices 110 via the server device 115, and the target device 120 to control the terminal device 110 or other target devices 120 via the server device 115. The server device 115 may include one or more computers. If the server device 115 includes two or more computers, the two or more computers may be located in the same location or in different locations. These different locations may be in different countries. For example, the first computer may be located in Japan and the second computer in the United States, or vice versa. The server device 115 may be located in a country or region other than the country or region where the terminal devices 110 and / or the target devices 120 are located.

[0029] The payment device 125 can receive information from the terminal device 110, the server device 115, and / or the target device 120, and perform payment. In one embodiment, the payment device 125 may be included in the server device 115. The payment device 125 may include one or more computers. If the payment device 125 includes two or more computers, the two or more computers may be located in the same location or in different locations. The different locations may be in different countries. For example, the first computer may be located in Japan and the second computer may be located in the United States, or vice versa. The server device 115 and the payment device 125 may be located in the same location or in different locations. The different locations may be in different countries or regions. For example, the server device 115 may be located in Japan and the payment device 125 may be located in the United States, or vice versa.

[0030] Network 150 may be implemented using any communication protocol and network topology. Typically, Network 150 can be a network implemented by the Internet Protocol. However, Network 150 may also be implemented by a wired public telephone network, a wireless public telephone network, or other communication networks.

[0031] [Hardware configuration] Figure 2 shows the hardware configuration of one or more terminal devices 110, a server device 115, one or more target devices 120, and a payment device 125 included in system 100. One or more terminal devices 110, a server device 115, one or more target devices 120, and a payment device 125 may be equipped with a processor 205, memory 210, storage 215, input / output devices 220, and communication devices 225. In one or more terminal devices 110, a server device 115, one or more target devices 120, and a payment device 125, the processor 205 loads a computer program stored in the storage 215 into the memory 210 and executes it. The input / output devices 220 include a touch panel on a display, a keyboard, a mouse, and a display device. Users can input information into the computer using a keyboard or touch panel and confirm the information output to the display device. One or more terminal devices 110, a server device 115, one or more target devices 120, and a payment device 125 can communicate with at least one of the other devices via a communication device 225 and send and receive data with them. In other embodiments, one or more terminal devices 110, a server device 115, one or more target devices 120, and a payment device 125 may not have some of the hardware components shown in Figure 2, and / or may have components other than the hardware components shown in Figure 2.

[0032] [System Operation Overview] One or more target devices 120 can provide target device identification information to a user for identifying the target device 120. The target device identification information may be provided in the form of information that can be read by a camera. The target device 120 can display the target device identification information dynamically or statically. For example, by displaying the target device identification information on a sticker or display device, the target device identification information is displayed statically (the target device identification information is always displayed in the same form). By changing the target device identification information displayed on the display device according to the current time, the date of the day, random numbers, or other information that changes according to conditions, the target device identification information is displayed dynamically (the target device identification information is displayed in different forms depending on the situation). When the target device identification information is displayed dynamically, the form in which the target device identification information is displayed changes. Dynamic display of target device identification information contributes to improved security because the same form is not used under different conditions.

[0033] Regarding information that can be read by the camera, codes such as 2D barcodes and 3D codes may be used as camera-readable information. In other embodiments, the camera-readable information may include any information that can represent identification information other than codes (for example, information in the form of a string).

[0034] In other embodiments, the target device identification information may be provided by information other than information readable by the camera. That is, the target device 120 can not only dynamically or statically display the target device identification information, but also output the target device identification information. The output may include a display, but may also be implemented by, for example, sensor-readable information that cannot be seen (e.g., information that can be communicated wirelessly or infrared) or sound.

[0035] The user can acquire target device identification information provided by the target device 120 using the terminal device 110. If the target device identification information is information that can be read by a camera, the camera on the terminal device 110 can acquire it by capturing an image of the target device identification information. If the target device identification information is not information that can be read by a camera, it is acquired by a function on the terminal device 110. For example, if the target device identification information is in audio format, the microphone on the terminal device 110 acquires the target device identification information. In other embodiments, the function on the terminal device 110 acquires the target device identification information depending on the information format of the target device identification information. For example, if the target device identification information is transmitted in the form of wireless communication such as Bluetooth, the Bluetooth transmit / receive function of the terminal device 110 acquires the target device identification information. In other embodiments, if the target device 120 provides the target device identification information in a format that can be read by the user (for example, a string of a predetermined length or a number), the user can read the target device identification information and input it using the keyboard or voice input function of the terminal device 110.

[0036] When terminal device 110 obtains target device identification information from target device 120, it can transmit the target device identification information, a user identifier pre-stored in terminal device 110 to the server device 115, and payment information used for settling the billing service of target device 120. When server device 115 receives the payment information, it cooperates with payment device 125 to perform or prepare to perform payment. In this embodiment, the user identifier can refer to information that can identify a specific user. Furthermore, the user identifier does not necessarily have to directly identify an individual user and can be an anonymous or pseudonymous identifier. In addition, the user identifier may be an identifier assigned by technical means, such as a transaction ID in communication or a random string, and can be directly or indirectly associated with a user.

[0037] Payment information may include, but is not limited to, payment method identification information, which includes information that identifies the user's credit card (such as a credit card number), information that identifies the user's bank account (such as an account number), and other information necessary to perform online payments (such as QR code payments) (such as information that identifies the user in online payments), and payment request information, which includes information indicating the user's intention to make a payment, or both.

[0038] If the payment information includes payment method identification information, when the server device 115 receives the payment information, it can cooperate with the payment device 125 to perform a payment or prepare to perform a payment based on the payment method identification information contained in the payment information. In another embodiment, if the payment information includes payment request information but does not include payment method identification information, when the server device 115 receives the payment request information contained in the payment information, it can cooperate with the payment device 125 to perform a payment or prepare to perform a payment based on the payment method identification information that the server device 115 and / or the payment device 125 have previously stored in association with the user identifier.

[0039] In the server device 115 and / or the payment device 125, the server device 115 may permit the terminal device 110 to use the target device 120 when payment or preparation for payment is completed. Once permission to use the target device 120 is granted, the terminal device 110 or the user can begin using the target device 120. While permission to use the target device 120 is granted, the terminal device 110 can control and / or operate the target device 120. In one embodiment, if the terminal device 110 is located remotely from the target device 120 (for example, the terminal device 110 and the target device 120 are far apart but located in the same ward or town in Tokyo, or the terminal device 110 is in Tokyo and the target device 120 is in Hokkaido), the terminal device 110 can remotely control the target device 120. The server device 115 may revoke permission for the terminal device 110 to use the target device 120 when certain conditions are met. If the permission is revoked, terminal device 110 will no longer be able to use target device 120. The prescribed conditions are not limited to the following, but examples include the revocation of permission to use after 30 minutes have elapsed since the start of use, or, if target device 120 is a charging device, the revocation of permission to use when charging is complete.

[0040] [First Embodiment] Figure 3 shows a processing flow based on a first embodiment of the present invention, in which payment is made after using the target device. The target device 120 presents or outputs target device identification information (step 305). Regarding presentation, a sticker attached to the target device 120 provides the target device identification information to the user. Alternatively, the target device identification information may be written directly on the outside of the target device 120. Regarding output, the display device, communication device, speaker, etc. of the target device 120 can output the target device identification information. In other embodiments, other devices associated with the target device 120 may present or output the target device identification information. For example, a single display device connected to one or more target devices 120 can identify one target device 120 by user operation on the target device 120 or the display device, and output the target device identification information of that target device 120.

[0041] The terminal device 110 acquires target device identification information from the target device 120 (step 308). The user reads the target device identification information and inputs it into the user's terminal device 110, thereby enabling the terminal device 110 to acquire the target device identification information. In one embodiment, the user can acquire the target device identification information by capturing an image of the target device identification information using the camera of the target device 120, which enables the terminal device 110 to acquire the target device identification information. In another embodiment, the terminal device 110 may acquire the target device identification information by acquiring it using the functions of the target device 120 (for example, a communication function or a microphone).

[0042] In other embodiments, the user may operate the terminal device 110 to display one or more target devices 120 on a map or the like, and then select a target device 120 to obtain target device identification information for that target device 120. This allows the user to obtain target device identification information even when they are located far from the target device 120.

[0043] In step 308, the target device 120 presents or displays to the user the amount required to use the target device 120 (for example, an hourly usage fee). In one embodiment, the target device 120 transmits the amount information to the terminal device 110 via or without the server device 115, and the terminal device 110 can display the amount on its display device. The user can then find out the amount required to use the target device 120. If the user accepts the amount, they can continue the process in step 311, which will be described later. If the user does not accept the amount, they can interrupt the process in step 311. In another embodiment, use of the target device 120 may be initiated not by monetary payment, but by payment in the form of points or other values ​​that replace money.

[0044] The terminal device 110 transmits the acquired target device identification information, the user identifier (which is information that identifies the user), and payment-related information to the server device 115 (step 311). The terminal device 110 can notify the server device 115 of the user identifier in advance and can also store it in the terminal device 110 itself.

[0045] Payment information includes at least one of payment method identification information and payment request information. Payment information may include usage fees. If usage fees are determined based on usage time, payment information may include usage start time and / or end time in addition to the usage fee.

[0046] If the payment information includes payment method identification information, the terminal device 110 can pre-store the payment method identification information, such as a credit card number. The terminal device 110 transmits the pre-stored payment method identification information to the server device 115 as payment information. In this embodiment, the transmission of the payment method identification information may be considered equivalent to the transmission of payment request information.

[0047] If the payment information does not include payment method identification information but includes payment request information, the terminal device 110 transmits the payment request information as payment information. When the server device 115 receives the payment request information, it may obtain the payment method identification information that has been previously stored in the server device 115 and / or payment device 125 in association with the user identifier, based on the user identifier transmitted together with the payment information. In other embodiments, the transmission of the user identifier may be considered as the transmission of payment information.

[0048] In other embodiments, the terminal device 110 may transmit at least one of the following to the server device 115 via the target device 120: target device identification information, user identifier, and payment information.

[0049] When the server device 115 receives target device identification information, a user identifier, and / or payment information, it associates the target device identification information and the user identifier (step 314). Depending on the reception of the user identifier and / or payment information, the server device 115 may permit the user associated with the user identifier to use the target device associated with the target device identification information. By associating the user identifier with the target device identification information, the server device 115 can identify that this user is using this target device. The server device 115 can store the association between the target device identification information and the user identifier.

[0050] In other embodiments, the server device 115 may calculate and determine the usage fee for the target device 120 upon receiving the target device identification information and the user identifier, and transmit the usage fee to the terminal device 110 and / or the target device 120. This allows the terminal device 110 and / or the target device 120 to output (e.g., display) the usage fee to the user. After transmitting the target device identification information and the user identifier, the user may use the terminal device 110 and / or the target device 120 to confirm the usage fee transmitted from the server device 115 and transmit payment-related information (e.g., at least payment request information) to the server device 115 (steps 311 and 314).

[0051] In other embodiments, the server device 115 may, upon receiving payment information and / or a user identifier, make a credit decision based on that information, that is, it may determine whether or not the user has the ability to pay the usage fee for the target device 120.

[0052] The server device 115 authorizes the use of the target device 120 identified by the received target device identification information and enables the use of the target device 120 (step 317). The server device 115 may transmit a control signal to the target device 120 to enable the use of the target device 120. After enabling the use of the target device 120, the server device 115 may wait to receive information from the terminal device 110 regarding the operations used to operate the target device 120. In another embodiment, the server device 115 may authorize the user to use the target device 120 if it determines that the user has the ability to pay the usage fee for the target device 120.

[0053] In one embodiment, the server device 115 may, before enabling the use of the target device 120, acquire location information such as a global positioning system (GPS) for both the terminal device 110 and the target device 120, and determine whether the terminal device 110 and the target device 120 are located within a predetermined range (for example, the terminal device 110 and the target device 120 are located within a radius of 10m), and then decide to enable the use of the target device 120.

[0054] In other embodiments, the target device 120 generates unique information such as a password, presents or outputs this unique information to the terminal device 110, and further transmits this unique information to the server device 115. The terminal device 110 may also obtain the unique information from the target device 120 by means similar to that used for the target device identification information and transmit it to the server device 115. The server device 115 may compare the unique information transmitted from the terminal device 110 with the unique information transmitted from the target device 120 and, upon determining that the two pieces of unique information are the same, decide to enable the use of the target device 120. This allows the server device to assume that the user is near the target device 120. In one embodiment, if the unique information is a one-time password that is valid for a predetermined period, the server device can determine that the user was near the target device 120 during the predetermined period in which the one-time password was valid.

[0055] When the target device 120 receives a control signal from the server device 115 to enable its use, it waits in a ready state, and the user starts using the target device 120 (step 320). The user may start using the target device 120 by operating the target device 120 itself. Alternatively, the user may start using the target device 120 by operating the terminal device 110 and based on the information obtained from that operation. In this case, the terminal device 110 can transmit the information obtained from the operation via the server device 115 or without going through the server device 115.

[0056] In one embodiment, the user may start using the target device 120 by operating the terminal device 110 and transmitting the information of that operation to the target device 120 via the server device 115. In this case, the user can start using the target device 120 from a location away from the target device 120.

[0057] The target device 120 notifies the server device 115 of information regarding the status of the target device 120 (step 323). The status of the target device 120 may include, but are not limited to, information indicating that the use of the target device 120 has started, been interrupted, or stopped; information indicating that the permitted period of use has elapsed (for example, if the use of the target device 120 is permitted for 30 minutes, information indicating that 30 minutes have elapsed since the start of use); and information indicating the operational status of the target device 120.

[0058] If the target device 120 is an air conditioner, the information indicating the operating status of the target device 120 may include the temperature, humidity, airflow, and operating time acquired by the target device 120. If the target device 120 is a television installed in a hotel room (for example, a television available for use upon payment), the information indicating the operating status of the target device 120 may include the channel being watched, the volume, and the operating time. If the target device 120 is a charger for an electric vehicle, the information indicating the operating status of the target device 120 may include the charging start time, charging end time, charging in progress, charging complete, charge amount, charging speed, average charging speed over a predetermined period, and operating time.

[0059] Notification is achieved when the target device 120 sends status information to the server device 115. The target device 120 can send status information to the server device 115 periodically (for example, every 30 seconds). In another embodiment, the target device 120 may send status information to the server device 115 in response to a change in status. This allows the server device 115 to obtain real-time status information of the target device 120. In yet another embodiment, the target device 120 may send status information to the server device 115 upon request from the server device 115. This allows the server device 115 to obtain the latest status information of the target device 120 when needed. Furthermore, since the server device 115 does not send or receive information unless requested, the amount of data sent and received can be reduced, contributing to the efficient use of computer resources.

[0060] When the server device 115 receives status information, it determines whether the use of the target device 120 has ended based on the received status (step 326). For example, if the server device 115 detects that the use of the target device 120 has been discontinued or that the permitted time for use of the target device 120 has elapsed, the server device 115 determines that the use of the target device 120 has ended. In other cases, the server device 115 determines that the use of the target device 120 has not ended. Determining whether the use of the target device 120 has ended may include determination methods other than those described above. In other embodiments, if the target device 120 is a charger for an electric vehicle, the server device 115 may determine that the use of the target device 120 has ended if the status indicates that charging is complete. If the target device 120 is an air conditioner, the server device 115 may determine that the use of the target device 120 has been interrupted or discontinued if the status indicates that a preset temperature has been reached.

[0061] If it is determined that the use of the target device 120 has not ended (i.e., No is determined in step 326), the server device 115 manages the status of the target device 120 (step 329). The server device 115 may send confirmation information to the target device 120 indicating that it has successfully received the status information. In response to receiving this confirmation information, the target device 120 may send new status information to the server device 115.

[0062] In other embodiments, the target device 120 may periodically or when there is a change in status, without waiting for confirmation information, to send status information to the server device 115. In this case, the server device 115 does not need to send confirmation information to the target device 120.

[0063] The server device 115 transmits information regarding the status of the target device 120 to the terminal device 110, and the terminal device 110 receives the status information (step 332). Based on the status information, the terminal device 110 can display the status of the target device 120. For example, the terminal device 110 can display whether the use of the target device 120 is permitted or the remaining time that the target device 120 can be used. This allows users to check the status of the target device 120 via the terminal device 110. Since users do not need to check the target device 120 itself but only need to check the terminal device 110 when checking the status of the target device 120, users can check the status of the target device 120 via the terminal device 110 even in remote locations far from the target device 120.

[0064] The terminal device 110 may, but is not limited to, display the following examples of operating status of the target device 120: if the target device 120 is an air conditioner, the operating status of the target device 120 will display the temperature, humidity, airflow, and operating time acquired by the target device 120; if the target device 120 is a television, the operating status of the target device 120 will display the channel being watched, volume, and operating time; and if the target device 120 is a charger for an electric vehicle, the operating status of the target device 120 may display the charging start time, charging end time, charging in progress, charging complete, charge amount, charging speed, average charging speed over a predetermined period, and operating time.

[0065] In other embodiments, information regarding the status of the target device 120 may be transmitted from the target device 120 to the terminal device 110 via a network 150 such as a short-range communication network or the Internet, rather than from the server device 115.

[0066] After confirming the status of the target device 120, the user can operate the target device 120 (step 335). For example, the terminal device 110 can receive input from the user and transmit operation information for operating the target device 120 based on that input to the server device 115. This allows the user to interrupt, cancel, or extend the use of the target device 120, or to operate the target device 120.

[0067] When the server device 115 receives operation information, it converts the operation information into a control signal and transmits the operation information to the target device 120 (step 338). In one embodiment, when the server device 115 receives operation information, it may transmit that operation information to the target device. In this case, the operation information is converted into a control signal in the target device 120. Hereafter, unless otherwise specified, operation information and control signals will be referred to as information relating to the operation.

[0068] In other embodiments, the terminal device 110 may receive input from a user and transmit operation information for operating the target device 120 based on that input to the target device 120 via a network 150 such as a short-range communication network or the Internet, rather than via the server device 115.

[0069] When the target device 120 receives information regarding operation from the server device 115 (step 338) or from the terminal device 110 (step 335), it controls or operates itself according to the information regarding operation or control signals (step 341). For example, the target device 120 can interrupt, suspend, or extend its use based on the information regarding operation or control signals. Since the terminal device 110 can operate the target device 120, even if the terminal device 110 is located remotely from the target device 120, the terminal device 110 can operate the target device 120 remotely, either via the server device 115 or without the server device 115.

[0070] In one embodiment, the server device 115 can change the usage fee for the target device 120 depending on whether the use of the target device 120 is interrupted, suspended, or extended. For example, if the use of the target device 120 is suspended, the server device 115 may calculate the usage fee based on the time from the start time to the time the use was suspended, rather than from the original start time to the end time. Also, if the use of the target device 120 is extended, the server device 115 may calculate the usage fee based on the time from the start time to the time the use was postponed, rather than from the original start time to the end time.

[0071] In other embodiments, the target device 120 may, but is not limited to, change the temperature, humidity, and airflow when the target device 120 is an air conditioner, change the channel being watched and the volume when the target device 120 is a television, or change the charging end time, charging amount, charging speed, or charging speed during a predetermined period, or set additional charging when the target device 120 is a charger for an electric vehicle or the like.

[0072] If the target device 120 is a charger for electric vehicles, etc., the charging amount and / or charging speed may be recalculated and changed based on the changed charging completion time by changing the charging completion time. Conversely, if the charging amount and / or charging speed is changed, the charging completion time may be recalculated based on the changed charging amount and / or charging speed. If the target device 120 is a charger for electric vehicles, etc., the charge fee for using the charger may be determined based on the charging amount and / or charging speed, so the ability to remotely change the charging amount and / or charging speed contributes to providing users with a more flexible and attractive charging service. For example, if normal charging starts at the beginning of charging, and fast charging becomes necessary after the user starts using the charger, the user can remotely change the charging method from normal charging to fast charging by paying an additional fee. As will be described later, payment of the additional fee may be realized in steps 346 and 349, etc.

[0073] Before, after, or at the time of transmitting information regarding the operation to the target device 120 (step 338), the server device 115 returns to step 326 (step 344).

[0074] If it is determined that the use of the target device 120 has ended (if "Yes" is determined in step 326), the server device 115 instructs the execution of payment (step 346). The server device 115 can calculate the usage fee for the target device 120. If the usage fee for the target device 120 changes depending on the usage time, the usage fee may be determined based on the start time and end time of use. If the use is interrupted, canceled, or extended, the server device 115 may set the time determined based on the interruption, cancellation, or extension of use as the end time of use.

[0075] In other embodiments, the server device 115 can set the start time of use as the time when it receives a user identifier (step 314), when it activates the use of the target device 120 (step 317), when it first receives a status notification (during steps 323 to 326), or at any other appropriate time. The server device 115 can also calculate the end time of use from the start time of use and / or the usage fee as the initial end time of use, and then calculate the end time of use based on the operation of the target device 120 in step 335 (e.g., cancellation, interruption, extension of use, etc.) and change the initial end time of use. In one embodiment, if the device is interrupted, the end time of use may be set by excluding the time the device is interrupted, treating the target device 120 as not being used.

[0076] Once the usage fee is determined, the server device 115 can transmit information regarding the usage fee to the terminal device 110 and / or the target device 120. At least one of the terminal device 110 and / or the target device 120 outputs (for example, displays) the usage fee to the user based on the information regarding the usage fee. In one embodiment, at least one of the terminal device 110 and / or the target device 120 may prompt the user to input information indicating that they have approved the usage fee, and transmit the input approval information to the server device 115.

[0077] When the server device 115 calculates the usage fee for the target device 120, it sends a payment execution request to the payment device 125 based on the usage fee and the payment information received in steps 311 to 314. In one embodiment, the server device 115 may send a payment execution request to the payment device 125 in response to receiving approval information from at least one of the terminal device 110 and / or the target device 120. The payment execution request may include the usage fee and / or payment information.

[0078] In the above embodiment, the server device 115 calculated the usage fee (step 346). However, in other embodiments, the target device 120 may calculate the usage fee and transmit the usage fee and a payment execution request to the payment device 125, either via the server device 115 or without going through the server device 115. In this case, the target device 120 may obtain payment information and / or the user identifier from the terminal device 110 or the server device 115 before step 346, and in addition to the usage fee and payment execution request, it may transmit payment information and / or the user identifier to the payment device 125, either via the server device 115 or without going through the server device 115.

[0079] In yet another embodiment, if the server device 115 transmits information regarding usage fees to the terminal device 110, the terminal device 110 may transmit the payment execution request and usage fees, as well as payment information and / or user identifiers to the payment device 125, either via the target device 120 and / or the server device 115, or without going through the target device 120 and / or the server device 115.

[0080] When the payment device 125 receives a payment execution request, it executes the payment based on the received usage fee, payment information, and / or the user's identifier (step 349). If the payment device 125 does not receive payment information, it can obtain payment information that is pre-associated with and stored in the payment device 125 based on the received user's identifier.

[0081] In other executions, if the payment device 125 receives a user identifier in step 349 but does not receive payment information, the payment device 125 can request at least one of the terminal device 110 and server device 115, which have pre-stored payment information associated with the user identifier, to return payment information based on the user identifier by transmitting the user identifier to at least one of the terminal device 110 and server device 115. This allows the payment device 125 to obtain payment information based on the user identifier from at least one of the terminal device 110 and server device 115.

[0082] After executing the payment, the payment device 125 may send payment completion information to the server device 115 indicating that the payment has been completed.

[0083] In step 346, the server device 115 can send a payment execution request to the payment device 125, and then send payment completion information to at least one of the terminal device 110 and the target device 120.

[0084] In other embodiments, the server device 115 may transmit payment completion information to at least one of the terminal device 110 and the target device 120 upon receiving payment completion information from the payment device 125.

[0085] At least one of the terminal device 110 and the target device 120 can output (for example, display) to the user that the payment has been completed upon receiving payment completion information.

[0086] In other embodiments, the server device 115 may include the functions of a payment device 125. This allows the server device 115 to perform payments using its own functions.

[0087] In one embodiment, once payment is completed, the server device 115 may terminate the use of the target device. For example, the server device 115 may send a control signal to disable the target device 120. This controls the target device 120 so that the user cannot use it. The server device 115 may also notify the terminal device 110 that the use of the target device 120 has ended. The terminal device 110 and / or the target device 120 will output (for example, display) that the use of the target device has ended, and the user can find out that the use of the target device has ended by checking the target device 120 and / or the terminal device 110. Since the user can find out that the use of the target device has ended by checking the terminal device 110, the status of the target device 120 can be checked from a location away from the target device 120.

[0088] In other embodiments, if the server device 115 notifies the terminal device 110 that the use of the target device 120 has ended, the terminal device 110 may be configured to operate in a way that prevents it from controlling or operating the target device 120 upon receiving the notification. For example, with respect to the user interface displayed on the terminal device 110, control may be implemented by not displaying a user interface that allows operation of the target device 120, or by displaying a user interface but disabling the operation buttons.

[0089] [Second Example] Figure 4 shows a processing flow based on a second embodiment of the present invention, in which payment is made before using the target device. The second embodiment differs from the first embodiment, in that payment is made after using the target device, in that payment is made before using the target device. In this embodiment, the steps that differ from the first embodiment are mainly steps 405, 408, and 411.

[0090] The server device 115, upon receiving the user identifier, target device identification information, and / or payment information, instructs the execution of the payment (step 405). The processing content in step 405 can be the same as in step 346 of the first embodiment.

[0091] When the payment device 125 receives a payment execution request, it executes the payment based on the received usage fee, payment information, and / or user identifier (step 408). The processing content in step 408 can be the same as in step 349 of the first embodiment.

[0092] In this embodiment, if it is determined that the use of the target device 120 has ended (i.e., if "Yes" is determined in step 326), the server device 115 terminates the use of the target device. The process for terminating the use of the target device can be the same as the process in the first embodiment.

[0093] In this embodiment, payment is completed before the target device 120 is used. After payment is completed, even if the usage fee decreases or increases due to the user interrupting, canceling, or extending the use of the target device 120, the usage fee can be kept unchanged.

[0094] In other embodiments, the terminal device 110, the target device 120, and / or the server device 115 may be controlled in such a way that the usage fee does not change by prohibiting the user from interrupting, canceling, or extending the use of the target device 120. This allows the system 100 to provide the user with a simple fee structure for the use of the target device 120. In this case, the user may use the terminal device 110 to instruct the target device 120 to perform only operations that do not affect the usage fee for the target device 120. For example, the terminal device 110, the target device 120, and / or the server device 115 may be configured to display a user interface on at least one of the display devices of the terminal device 110 and the target device 120 that allows the user to perform only operations that do not affect the usage fee.

[0095] [Third embodiment] Figure 5 shows a processing flow based on a third embodiment of the present invention, in which payment is made before using the target device and then again thereafter. The third embodiment differs from the first embodiment, in that payment is made after using the target device, and also differs from the second embodiment, in that payment is made before using the target device, in that payment is made both before and after using the target device. In this embodiment, the steps that differ from the first and second embodiments are mainly steps 505 and 508.

[0096] In the second embodiment, payment was made before using the target device 120. However, in the second embodiment, after the user started using the target device 120, it was difficult to change the usage fee if the user performed an operation that would change the usage fee for the target device 120 (for example, canceling, interrupting, or extending the use of the target device 120).

[0097] In this embodiment, since payment is made again after the use of the target device 120 is completed (steps 505 and 506), even if there is a change in the usage fee that has already been paid in steps 405 and 408, the usage fee can be recalculated and the difference between the paid usage fee and the recalculated usage fee can be paid. As a result, the system 100 can collect the fee when the use of the target device 120 begins, and furthermore, even if there is a change in the usage fee after use has begun, it can collect the correct fee according to the usage. In other embodiments, the system 100 may operate the terminal device 110, the target device 120, the server device 115, and / or the payment device 125 to pay the deposit, or the deposit and usage fee, in the payment in steps 405 and 408, and then pay the deposit back in the payment in steps 505 and 506. This can prevent theft of the target device 120.

[0098] In this embodiment, when there is a difference between the settled usage fee and the recalculated usage fee, the system 100 can operate the terminal device 110, the target device 120, the server device 115, and / or the settlement device 125 to settle the amount equivalent to the difference. For example, if the settled usage fee is less than the recalculated usage fee, the system 100 may settle an additional amount equivalent to the difference. If the settled usage fee is greater than the recalculated usage fee, the system 100 may settle by refunding the amount equivalent to the difference. Alternatively, the system 100 may refund the entire settled usage fee and then settle again with the recalculated usage fee. The settlement process may be implemented by the server device 115 and / or the settlement device 125. In this case, the server device 115 and / or the payment device 125 may cooperate in executing the payment by causing the terminal device 110 and / or the target device 120 to display a confirmation prompt, etc.

[0099] In this embodiment, if there is a difference between the paid usage fee and the recalculated usage fee, the server device 115 may transmit to at least one of the terminal device 110 and the target device 120 that there is a difference in the usage fee, that is, that the paid usage fee has changed. This allows at least one of the terminal device 110 and the target device 120 to notify the user that the paid usage fee has changed.

[0100] In one embodiment, at least one of the terminal device 110 and the target device 120, and the server device 115 may be configured to present the difference in usage fees to the user and to obtain confirmation from the user that they accept the difference. For example, the server device 115 can transmit information regarding the difference in usage fees to at least one of the terminal device 110 and the target device 120. The display device of at least one of the terminal device 110 and the target device 120 may output (e.g., display) information regarding the difference in usage fees to the user. At least one of the terminal device 110 and the target device 120 may be configured to prompt the user to input information confirming acceptance of the difference and to transmit that information to the server device 115. The server device 115 may perform the settlement in steps 505 and 506 in response to receiving confirmation of acceptance of the difference from at least one of the terminal device 110 and the target device 120 (i.e., from the user).

[0101] [Differentiation] The target device 120 includes electric vehicle chargers, and may also include, but is not limited to, chargers for mobile phones, watches, computers, bicycles, motorcycles, personal mobility vehicles (PMVs), etc.

[0102] If the target device 120 is a charger for electric vehicles, bicycles, motorcycles, and PMVs, which occupy space during storage, the usage time of the target device 120 can be considered as space occupancy time, such as the parking time of an electric vehicle (for example, parking time for a car). In this case, the system 100 may operate the terminal device 110, the target device 120, the server device 115, and / or the payment device 125 to calculate a space occupancy fee (for example, a parking fee for a car) based on the space occupancy time corresponding to the usage time of the target device 120, and settle the space occupancy fee together with the usage fee for the target device 120. In other embodiments, the system 100 may calculate the space occupancy time using or without the usage time of the target device 120. For example, if a user uses a service that charges 300 yen per hour for charging and 140 yen per hour for parking for two hours, the system 100 may be configured to request the user to pay a total of 880 yen, consisting of 600 yen for charging and 280 yen for parking.

[0103] [others] In each of the embodiments described above, the terminal device 110, the target device 120, the server device 115, and the payment device 125 may be implemented as separate hardware, or some or all of them may be implemented as a single piece of hardware.

[0104] It will be understood that the functions and steps described in the above embodiments can be implemented as methods, computer programs, machine-readable computer programs, or storage devices or storage media for recording machine-readable computer programs.

[0105] In the above embodiments, it will be understood that some or all of the elements described as being implemented in hardware can be implemented in software, and some or all of the elements described as being implemented in software can be implemented in hardware.

[0106] In the processes or processing order described above, you may freely change the processes or processing order, as long as no inconsistencies arise in the processes or processing order, such as a process using data that should not yet be available in that process.

[0107] Each of the embodiments described above may be implemented as a single embodiment by combining some or all of the embodiments.

[0108] The embodiments described above are illustrative examples for illustrating the present invention, and the present invention is not limited to these embodiments. The present invention can be implemented in various forms without departing from its essence. [Explanation of Symbols]

[0109] 100: System 110: Terminal device 115: Server device 120: Target device 125: Payment device 150: Network 205: Processor 210: Memory 215: Storage 220: Input / Output Devices 225: Communication equipment

Claims

1. A system that allows the use of a target device through a billing service, A server device that manages the aforementioned billing service, The target device presents or outputs target device identification information for identifying the aforementioned target device, A terminal device of a user that acquires the target device identification information from the target device, and transmits the target device identification information, a user identifier that identifies the user, and information regarding the user's payment to the server device, Equipped with, A system in which, upon receiving payment information from the user, the server device associates the target device identification information with the user identifier, permits the user to use the target device, and waits for information from the terminal device regarding operations used to operate the target device while the user is permitted to use the target device.

2. The system according to claim 1, wherein the server device settles a first fee for using the target device based on the payment information.

3. The system according to claim 2, wherein, in response to receiving information regarding the operation from the terminal device, the server device settles the difference between the first fee and the second fee, which is the changed fee, or refunds the first fee and settles the second fee.

4. The system according to claim 2, wherein the server device, upon receiving information relating to the operation from the terminal device, transmits to the terminal device or the target device information indicating that the settled usage fee has changed, or information indicating that the changed usage fee is the second fee, if the fee for using the target device has changed from the first fee.

5. The system according to claim 4, wherein the server device settles the difference, or refunds the first fee and settles the second fee, in response to the user receiving confirmation from the terminal device or the target device that the user accepts the difference between the second fee and the first fee.

6. A server device that manages a billing service that enables the use of the target device, The server device is The system receives target device identification information for identifying the target device, a user identifier for identifying the user of the billing service, and information regarding the user's payment, and further, A server device configured to associate the target device identification information and the user identifier in response to receiving payment information from the user, to authorize the user to use the target device, and to wait for information regarding operations used to operate the target device from the user's terminal device while the authorization is granted.

7. A terminal device used by a user to operate the target device in a billing service, The aforementioned terminal device is A target device identification information for identifying the aforementioned target device is obtained from the aforementioned target device, The target device identification information, the user identifier that identifies the user, and the user's payment information are transmitted to the server device. A terminal device configured to transmit information regarding the user's payment to a server device, and then, upon receiving information regarding the status of the target device from the server device, transmit to the server device information regarding operations used to operate the target device.

8. A method executed by a system that includes a server device, a target device, and a terminal device, and which allows the use of the target device for a billing service, The steps include: the target device presenting and outputting target device identification information for identifying the target device; The terminal device obtains the target device identification information from the target device and transmits the target device identification information, a user identifier that identifies the user, and information regarding the user's payment to the server device. A method comprising the steps of: when the server device receives information regarding the user's payment, associating the target device identification information and the user identifier to authorize the user to use the target device, and waiting for the terminal device to receive information regarding operations used to operate the target device while the authorization is granted.

9. A method executed by a server device that manages a billing service that enables the use of the target device, The server device receives target device identification information for identifying the target device, a user identifier for identifying the user of the billing service, and information regarding the user's payment. A method comprising the steps of: when the server device receives information regarding the user's payment, associating the target device identification information and the user identifier to authorize the user to use the target device, and waiting for information regarding operations used to operate the target device to be received from the user's terminal device while the authorization is granted.

10. A method executed by a user's terminal device that operates the target device in a billing service, The terminal device obtains target device identification information from the target device for identifying the target device, The terminal device transmits the target device identification information, the user identifier that identifies the user, and the user's payment information to the server device. A method comprising the steps of: the terminal device transmitting information relating to the user's payment to the server device, and then, in response to receiving information relating to the status of the target device from the server device, transmitting to the server device information relating to an operation used to operate the target device.

11. A computer program executed by a system that includes a server device, a target device, and a terminal device, and which allows the use of the target device in a billing service, The steps include: the target device presenting and outputting target device identification information for identifying the target device; The terminal device obtains the target device identification information from the target device and transmits the target device identification information, a user identifier that identifies the user, and information regarding the user's payment to the server device. A computer program comprising the steps of: when the server device receives information regarding the user's payment, associating the target device identification information and the user identifier to authorize the user to use the target device, and waiting for information from the terminal device regarding operations used to operate the target device while the authorization is granted.

12. A computer program executed by a server device that manages a billing service that enables the use of the target device, The server device receives target device identification information for identifying the target device, a user identifier for identifying the user of the billing service, and information regarding the user's payment. A computer program comprising the steps of: when the server device receives information regarding the user's payment, associating the target device identification information and the user identifier to authorize the user to use the target device, and waiting for information regarding operations used to operate the target device to be received from the user's terminal device while the authorization is granted.

13. A computer program executed by a terminal device of a user who operates the target device in a billing service, The terminal device obtains target device identification information from the target device for identifying the target device, The terminal device transmits the target device identification information, the user identifier that identifies the user, and the user's payment information to the server device. A computer program comprising the steps of: the terminal device transmitting information relating to the user's payment to the server device, and then, upon receiving information relating to the status of the target device from the server device, transmitting information relating to an operation used to operate the target device to the server device.

Images