WO2015103475A1

WO2015103475A1 - Code enabled service device

Info

Publication number: WO2015103475A1
Application number: PCT/US2015/010040
Authority: WO
Inventors: Michael T. LIN; Andrew M. BOICE; Paul J. JEHLEN; G. WARSHAWSKY Brian
Original assignee: Fenix International Inc.
Priority date: 2014-01-02
Filing date: 2015-01-02
Publication date: 2015-07-09

Abstract

A method and apparatus for digitally enabled payments are described herein. A device for providing a service to a customer includes a communicator for receiving an encrypted code including an instruction for configuring the device. The device also includes a microcontroller for decrypting the code received by the communicator, analyzing the decrypted code to identify the instruction therein, and configuring the system according to the instruction of the decrypted code.

Description

CODE ENABLED SERVICE DEVICE

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Patent Application No. 61/923,014, filed on January 2, 2014, entitled Digital Payment Enabled Control System, which is incorporated herein by reference.

BACKGROUND OF THE INVENTION

[0002] The subject matter disclosed herein relates to digital payment enabled systems with control feedback to provide access to physical or virtual goods, services and utilities.

[0003] Four billion people live at the base of the economic pyramid and earn less than 10 USD per day, frequently facing challenges such as seasonal or irregular income. As a result, it is often difficult, if not impossible, to access energy, water, nutrition, healthcare, education, transportation, communication, finance, and other goods, services, and utilities due to their cost.

[0004] For example, one in five people globally (more than 1.3 billion people) do not have access to electricity and an additional 1 billion people struggle with unreliable electricity that is frequently plagued by outages as well as spikes and surges. Centralized power generation and grid distribution is failing to meet need for electricity. New power plant installations and grid expansion are slow and near nonexistent due to cost, corruption, and theft (e.g., power transmission wires are often stolen for scrap metal value and oil is often drained from transformers for fuel). Even alternatives such as petrol-powered generators and solar photovoltaic systems experience only limited success because of cost and reliability issues. A small percentage of the world's poor have re-appropriated 12 volt lead-acid car batteries as a power source. However, the reliability and safety of these re-appropriated batteries leave much to be desired, often resulting in damaged appliances, sparks, fires, acid burns, and even electrocution.

[0005] Water treatment centers, pumps, and distribution are also costly to build and expand. Beyond the infrastructure itself, water metering, billing, and payment collection are costly and difficult to manage, greatly limiting access. The only alternative is to collect water from lakes, rivers, and springs, which are often contaminated. Fetching water can also require considerable time and energy, particularly when the water source is far away from the point of use. This task of fetching water is often culturally defined as a role for women and, as a result, frequently has the effect of limiting access to education for young women.

[0006] Access to other goods and services, whether physical or virtual, such as television, internet, streaming video, or micro-cell mobile phone service are limited to the poor living at the base of the economic pyramid because of their upfront cost as well as the challenges of metering service, payment collection, and a control system.

[0007] The discussion above is merely provided for general background information and is not intended to be used as an aid in determining the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE INVENTION

[0008] In one embodiment of the invention, a device for providing a service to a customer is disclosed. The device includes a communicator for receiving an encrypted code including an instruction for configuring the device. The device also includes a microcontroller for decrypting the code received by the communicator, analyzing the decrypted code to identify the instruction therein, and configuring the system according to the instruction of the decrypted code.

[0009] In another embodiment of the invention, a method for configuring a service device is disclosed herein. The service device includes a communicator and a microcontroller. The method includes receiving an encrypted code in the communicator and transferring the encrypted code to the microcontroller. The method also includes decrypting the encrypted code into plain text in the microcontroller. The decrypted code includes a plurality of fields to instruct the microcontroller to configure the digital payment enabled device. The method further includes analyzing the decrypted code to determine an instruction therein and configuring the digital payment enabled system as per the instruction of the decrypted code. [0010] This brief description of the invention is intended only to provide a brief overview of subject matter disclosed herein according to one or more illustrative embodiments, and does not serve as a guide to interpreting the claims or to define or limit the scope of the invention, which is defined only by the appended claims. This brief description is provided to introduce an illustrative selection of concepts in a simplified form that are further described below in the detailed description. This brief description is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. The claimed subject matter is not limited to implementations that solve any or all disadvantages noted in the background.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] So that the manner in which the features of the invention can be understood, a detailed description of the invention may be had by reference to certain embodiments, some of which are illustrated in the accompanying drawings. It is to be noted, however, that the drawings illustrate only certain embodiments of this invention and are therefore not to be considered limiting of its scope, for the scope of the invention encompasses other equally effective embodiments. The drawings are not necessarily to scale, emphasis generally being placed upon illustrating the features of certain embodiments of invention. Thus, for further understanding of the invention, reference can be made to the following detailed description, read in connection with the drawings in which:

[0012] FIG. 1 illustrates a digital payment enabled system in an exemplary embodiment of the invention;

[0013] FIG. 2 is a block diagram of a digital payment enabled electricity access system in an exemplary embodiment of the invention;

[0014] FIG. 3 is a flow diagram for configuring a service access device in one exemplary embodiment of the invention; and

[0015] FIG. 4 is a flow diagram for configuring a service access device in one exemplary embodiment of the invention. DETAILED DESCRIPTION OF THE INVENTION

[0016] FIG. 1 illustrates a digital payment enabled system in an exemplary embodiment of the invention. The digital payment enabled system 100 includes an electricity access device 102. The electricity access device 102 is an electricity generation, storage, and distribution device that provides a customer with access to electricity upon the receipt of an authorization generated upon notification of a digital payment and disallows access to electricity upon the expiration of the authorized period of service.

[0017] The electricity access device 102 includes a user interface 104 in an exemplary embodiment of the invention. The user interface 104 can include a plurality of elements designed to convey information about the electricity access device 102 to the user (e.g., state of charge of the electricity access device 102, whether the battery of the electricity access device 102 is charging or discharging, the rate of charging or discharging of the battery, whether maintenance is required, whether an error or fault has occurred, that the user has access to the device 102, i.e., whether the device is locked and waiting for a code or unlocked and able to provide electricity access, etc.).

[0018] As shown in FIG. 1, the state/rate of charge indicator 110 can be a funnel or inverted cone shaped display of a plurality of LEDs or other visual indicators. LEDs can be used based on their reliability and long life as well as their low power consumption. The brightness and related current draw of the each of the LEDs can be controlled by selecting an appropriate series resister (e.g., 330 ohms). In one embodiment, the state/rate of charge indicator 110 can include a red first (low) state/rate LED 112, an amber second state/rate LED 114, an amber third state/rate LED 116, and an amber or green fourth state/rate LED 118 to provide the required information. For example, if the red first (low) state/rate LED 112 were continuously illuminated, that would

communicate to a user that the battery of the electricity access device 102 has 25% or less of full capacity charge remaining, while if all four LEDs 112, 114, 116, 118 were continuously illuminated, including the amber fourth state/rate LED 118, that would communicate to the user that the electricity access device 102 has more than 75% of full capacity charge remaining. While the LEDs have been described here as being of a particular color, it is to be understood that the LEDs can be of any suitable color.

[0019] When the electricity access device 102 is charging/discharging, as indicated by the amber charge/discharge LED 120 (e.g., illuminated only when the battery is charging and turned off when the battery is not charging), the particular percentage range of remaining battery charge at that moment (e.g., 50% to 75%) can be communicated by flashing the corresponding charge/discharge LED (e.g., amber third state/rate LED 116) during charging/discharging. In addition, the rate of flashing of the corresponding charge/discharge LED can be determined by the rate of charging/discharging of the battery (e.g., the faster the rate of charging/discharging, the higher the frequency of flashing of the LED). In an alternative embodiment, the charge/discharge LEDs 112, 114, 116, 118 can be illuminated in a cascading or rippling fashion to indicate charging or discharging of the battery of the electricity access device 102.

[0020] The need for maintenance of the electricity access device 102 can be communicated to the user by the red maintenance LED 122, which can be illuminated to, e.g., indicate to the user that a full charge of the battery is required to optimize battery performance and life. In the event of a fault or other error, all of the LEDs can flash for a predetermined amount of time to alert the user of the existence of the error or fault, and that the outputs 106, 108 have been disconnected. In the event of a fault or other error, the multi-function pushbutton 124 can be pressed to reset the electricity access device 102 to reactivate the outputs 106, 108 or to accept an energy source. In addition, the multi-function pushbutton 124 can be pressed during normal conditions to display the state of charge on the state/rate of charge indicator 110. If the electricity access device 102 is off, the multi-function pushbutton 124 can be pressed to energize the electricity access device 102.

[0021] In addition to the information about the electricity access device 102 conveyed to the user by the user interface 104, the electricity access device 102 can also include an audible device to provide information and feedback. For example, a buzzer can be used that can play several different notes based on the switching frequency to provide audible notification when a particular event occurs (e.g., a positive sound to indicate the beginning of charging/discharging, a positive sound to indicate the completion of 1 watt-hour of charging, a negative sound if voltage is approaching dangerous levels, a beeping negative sound to indicate the presence of a fault, a continuous negative sound to indicate the use of an improper input device).

[0022] In addition to the notifications, visual and audible, described above, the electricity access device 102 can also include a notification to indicate when an authorized period of service is approaching expiration and/or has expired. The notification can be any suitable type of notification, such as an audible notification or a visual notification, such as an LED. For example, the maintenance LED 122 can act as a "lock light". In this example, the maintenance LED 122 can indicate if the device is locked (LED illuminated) or unlocked (LED off), in addition to indicating if maintenance is required.

[0023] The electricity access device 102 can also include a plastic enclosure with a dimple (not shown) on the underside of the unit at its center of gravity, shaped appropriately to rest on the top of a user's head during transport.

[0024] Additionally, the electricity access device 102 includes a code communicator 126. The code communicator receives a unique, encrypted code. The code includes instructions to direct the configuring of the electricity access device 102. The code is unique to the electricity access device 102 and is generated upon receipt of a digital payment. The code includes a configuration instruction for the electricity access device 102. In addition, the code can act as authorization for services.

[0025] The digital payment enabled system 100 includes a remote 128. The remote is a user interface, designed to allow a customer to input the code to the electricity access device 102. By transmitting the code to the customer and allowing the customer to input the code, a customer is able to use the device 102 in a remote area. While the device 102 is not connected to a network, and thus is not in communication with the service provider, the customer is able to travel to an area with communication access to receive the code, then travel back to the device and input the code to configure the device 102. [0026] The remote includes a remote user interface 130, such as a numeric keypad, to allow the user to input the code. After the code is input, the code is transmitted by a code transmitter 132 of the remote 128 to the code communicator 126 of the electricity access device 102. The code transmitter 132 can be any suitable type of transmitter. For example, the code transmitter 132 can be an infrared transmitter, a DTMF (touch tone) transmitter, an audible transmitter, Bluetooth transmitter, or any other suitable type of transmitter. In addition, while the remote user interface 130 is described as a physical keypad, the remote user interface 130 can be any suitable type of input device, such as a touchscreen. In another embodiment, the remote 128 can be a mobile device, such as a cellular phone, that has been configured to interact with the electricity access device 102 to input the code. Further, while the digital payment enabled system 100 is described here as including a remote 128 to input the code, in an embodiment, the code can be transmitted directly from a service provider to the electricity access device 102, using any suitable method.

[0027] While this embodiment describes a remote acting as the user interface, any other suitable type of user interface can be used to input the code in the electricity access device 102. For example, rather than a remote, the user interface 104 of the device 102 can include a keypad, or other input device, for inputting the code to the device 102. Further, if the device 102 is connected to a communication network, the code can be transmitted directly to the device 102, rather than being sent to a customer. In addition, while the device 102 is described here as an electricity access device, the digital payment enabled system may be employed to provide access to any suitable type of physical or virtual goods, services and utilities.

[0028] FIG. 2 is a block diagram of a digital payment enabled electricity access system 200 in one exemplary embodiment of the invention. The digital payment enabled electricity access system 200 includes an electricity access device 202. The electricity access device 202 includes a battery 204, which can be a sealed, maintenance free 12V DC lead-acid battery. The electricity access device 202 can include a microcontroller unit (MCU) 206 powered by the battery 204 (e.g., at 5V DC or 3.3V DC) that communicates relevant information about the electricity access device 202 to the user through the user interface 104 discussed previously. For example, the MCU 206 can be directly connected to power the LEDs 112, 114, 116, 118, 120, 122 of the user interface 104 through a resistor without the need for driver circuitry. The MCU 206 is a processor, which can be a microprocessor, a microcontroller, an application specific integrated circuit ("ASIC"), a mixed signal processor ("MSP"), a field programmable gate array ("FPGA"), or a combination thereof, among others.

[0029] The MCU 206 can also control the operation and interaction of the other components of the electricity access device 202 to manage power measurements, and control the inputs 218 and outputs 214 to the electricity access device 202 to optimize battery performance and life. The MCU 206 dynamically controls the charge circuit 208, which is responsible for receiving power from a plurality of different types of energy sources attached to the input terminals 218 and using that power to charge the battery 204 in a safe and efficient way. The MCU 206 also dynamically controls the discharge circuit 210, which supplies power to and monitors the outputs 214 to prevent the user from drawing power out of the battery 204 in a manner that might damage the battery 204.

[0030] The electricity access device 202 can include a charge input protection circuit 208 for protecting the electricity access device 202 from being damaged by certain harmful or inappropriate energy sources connected to the input terminals 218. A charge input switch 209 (provided hardware (mechanical (e.g., relay) or electrical (e.g.,

MOSFET)) or software) located after the charge input protection circuit 208 can isolate the energy sources from the electricity access device 202 by serving as a gatekeeper to allow current (closed state) or block current (open state) from the sources from flowing into the remainder of electricity access device 202 depending on whether those sources have been approved by the MCU 206. A conventional buck regulator 219 can be used to step down source voltages for correct charging of the battery 204 and to modulate any excess power when the battery 204 charge is near full. The MCU 206 can use current and voltage sensor readings to identify the particular energy source attached to the input terminals 218. Once the particular energy source has been identified, a charging mode tailored to the particular energy source connected can be used to charge the battery 204. In one embodiment, the electricity access device 202 can accommodate charging voltages from 16V DC (minimum) to 30V DC (maximum) and charge the battery 204 at up to 4 A or 50W depending on the available input power from the energy source. Other embodiments could include different ranges for charging voltages, currents, and wattages.

[0031] Turning first to the protection offered by the charge circuit of the electricity access device 202, in one embodiment, the electricity access device 202 should be able to withstand energy source voltages of up to 300V, alternating current (AC) sources, and inadvertent connections to the input terminals 218 with reverse polarity without damaging the electricity access device 202. In order to accomplish this protection, the charge input protection circuit 208 can include a conventional full bridge rectifier on the input terminals 218 that allows the MCU 206 to read input voltage safely in the case of an AC energy source. The charge input protection circuit 208 can also include a conventional rectifier diode, rated up to 300V, so that if energy source is inadvertently connected with reverse polarity to the input terminals 218, no voltage will be sensed by the MCU 206. The rectifier diode can be used in addition to the full bridge rectifier since the full bridge rectifier would make a energy source connected with reverse polarity to the input terminals 218 appear positive. The charge input protection circuit 208 can also include a voltage divider to scale down voltages of up to 300V. If the energy source connected to the input terminals 218 is determined to be safe, the current from the energy source will bypass the full bridge rectifier and rectifier diode so as not to incur any substantial power losses across those components. Protected by the full bridge rectifier, rectifier diode, and/or voltage divider, the MCU 206 can safely detect overvoltage and AC inputs of up to 300V.

[0032] Energy can be transferred from the battery 204 to the output terminals 214 for charging electronic devices. The electricity access device 202 can include an output protection circuit 210 to protect the electricity access device 202 from additional charge. The electricity access device 202 also includes a charge output switch 211 located after the charge output protection circuit 210 to isolate the energy sources from the electricity access device 202 by serving as a gatekeeper to allow current (closed state) or block current (open state) from the sources from flowing into the remainder of electricity access device 202 depending on whether those sources have been approved by the MCU 206.

[0033] The electricity access device 202 is enabled by control software and hardware that is either built-in or removable and reusable. This control system has the ability to receive commands to enable or disable access to electricity. When a customer makes a digital payment, notification of this payment is received and acknowledged by a centralized, server-based software system of a service provider 224. A code generator 226 of the service provider 224 generates an encrypted code that is unique to the electricity device with the ability to affect the device with a certain behavior, i.e., to instruct the MCU 206 in configuring the electricity access device 202.

[0034] The code generator 226 can transmit the encrypted code digitally to the code communicator 220 of the electricity access device 202 in a variety of ways. The code communicator 220 can be a built-in hardware component of the device 202. In another example, the communicator 220 can be a removable hardware component. For example, when a customer pays off the cost of the device 202, the communicator 220 can be removed from the device and returned to the service provider. The returned

communicator 220 may be incorporated in a new device 202.

[0035] In an example, the code generator 226 can transmit the code via a network 222. The network 222 can be a wired network or a wireless network and can be any suitable type of network. For example, the code can be transmitted via a radio frequency, dual-tone multi-frequency signaling, a cellular network, or the Internet, among others. When the code is received in the electricity access device 202, the device reacts and exhibits the behavior commanded by the code.

[0036] In another example, the code generator 226 can transmit the code to a customer, who inputs the code to the code communicator 220 of the electricity access device 202. For example, the code generator can send the code to a customer's cellular phone, such as in the form of a short message service (SMS) message, a phone call, or an email. The customer can input the code in a variety of ways, such as with the remote 128 illustrated in FIG. 1. When the customer enters the code into the electricity access device 202, the device 202 reacts and exhibits the behavior commanded by the code.

[0037] The code is a unique code that is generated by a service provider and transmitted to a communicator 220 of the electricity access device 202. The code is unique to the device 202 and can be valid for only one use. In an example, the digital payment enabled control system, including the communicator 220, can be built-in hardware of the electricity access device 202. In this example, if a customer is granted ownership of the device, the digital payment enabled control system can be reactivated should the customer want to add a new feature, product, or service to the device, refinance the loan to purchase the device, or use the device as collateral for a loan for another purpose which does not have a control system embedded within (e.g., a loan to purchase livestock which does not have a control system). In another example, the digital payment enabled control system can be removable and/or reusable. For example, the digital payment enabled control system can be a USB dongle that can be removed from the electricity access device 202. In another example, the digital payment enabled control system can be connected within the device 202 via a data cable to a "daughter card" (a separate PCBA with the digital payment enabled control system). In yet another example, the digital payment enabled control system can be an external device that communicates wirelessly to the device 202, such as via near field communication (NFC), Bluetooth, Wi-Fi, etc. In an example, the digital payment enabled control system can be removed when a customer has repaid the cost of the device. A removed digital payment enabled control system can be reset to factory condition and installed in a new electricity access device.

[0038] The code is created based on the serial number of the device 202 and information stored by the service provider under that serial number. A customer's cellular phone can be associated with the serial number of the device 202 for ease of payments. The serial number of the device 202 has a set of keys associated with the serial number that are used to generate the code and to encrypt and decrypt the code. The keys are unique to the device 202 and are loaded onto the device 202 during the manufacturing process and stored in a service provider's database during the

manufacturing process. In an example, the device 202 includes six random keys.

[0039] Each code is encrypted before being transmitted to the customer/device 202. Upon being received in the communicator 220, the code is transmitted to the MCU 206, where the code is decrypted. The code includes a plurality of fields, the fields providing configuration instructions to the MCU 206. The MCU 206 analyzes the code to identify these instructions and configures the electricity access device 202 based on these instructions.

[0040] The code is a numeric code and can include any suitable number of digits. In an embodiment, the code can be an eight (8) digit code. Each code includes four fields which, together, represent a configuration instruction to the device 202. The first digit of the code represents a command type. The command type determines what action the device shall perform upon receiving the message and how the command parameter is interpreted by the unit. The second and third digits of the code represent the command parameter. The command parameter contains the two-digit data payload. Depending on the command, the value of this parameter may have different meanings. For example, the command parameter may indicate a number of days of service to be added, or the command parameter may indicate reconfiguration of the device 202. The fourth, fifth, and sixth digits of the code represent the sequence number. This element is critical in ensuring that commands cannot be reused. When creating a new base command, the sequence number of the last command generated for the device 202 is referenced. The previous sequence number is incremented by one (1) to determine the next sequence number. If the new sequence number exceeds the maximum value of 999, then numbering rolls over to 000. The seventh and eighth digits of the code represent the checksum. The checksum is the two-digit sum of the six digits preceding it in the code. This effectively gives the checksum a minimum value of 00 when the six preceding digits are 000000 and a maximum value of 54 when all six preceding digits are 999999. This calculation does not overflow and there is exactly one and only one valid checksum for a given 6 digit code.

[0041] The command types of the code are broken down into type classifications based on their treatment of the sequence number field of the command. For example, the command types can be broken down into override commands and value adding/changing commands. Override commands are intended to allow a service provider to clear and reset certain device parameters remotely. The use of override commands is intended to be infrequent. Primarily, override commands provide a mechanism to return the device to a known state for service and support purposes. All override commands expect a particular command parameter. If the command parameter is not as expected, the command is rejected. This requirement is imposed to minimize the valid code space. When a device receives an override code, the device goes to a known state and the device is re-keyed in a known way. For example, one key value is indexed by adding 1. The database updates key records using the same method when an override code is issued so that future codes are generated using updated key values as stored on the device. As a result of this re-keying process, all previously issued codes are invalidated as they were encrypted with an out of date set of keys.

[0042] Value adding/changing commands allow additional value units, such as time, energy, etc., to be credited to the device. To prevent the same credit from being applied multiple times, the device 202 tracts and stored in non-volatile memory (not shown) the sequence numbers of the last ten valid commands. Any received command whose sequence number is more than ten counts above or below the highest recorded sequence number or that is still contained in the history list is considered invalid.

[0043] Value adding/changing commands can be used to change a variety of values, such as the operating parameters of the device. For example, unlocking the electricity access device 202 to provide the customer with electricity either metered by time (limit upon the expiration of a certain period of time), energy (limit upon the consumption of a certain amount of energy), power (limit at a maximum power), a combination thereof, or some other behavior. Examples of other operating parameters that can be modified include setting voltage thresholds, tracking fuel gauge/state of charge and setting the threshold, limiting the input charge rate, and limiting the maximum output rate, among others.

[0044] The usage of electricity is monitored or metered by the device 202. When the limits determined by the code are triggered, the device 202 reacts appropriately. For example, the device 202 may react by disabling the output of electricity when a period of time elapses. When the limit is triggered, the charge output relay 316 can be deactivated to prevent electricity from being transferred to a customer, effectively locking the device 202. The action of locking the output serves as feedback and motivation to the customer that another payment is due. The transmission and receipt of a subsequent digital payment to the service provider results in the generation of another code that unlocks the device 202 for the appropriate metric, re-enabling output of electricity until the limits are triggered again.

[0045] In another example, the code can upgrade the device 202. Should a customer want to upgrade or add a new feature, product, or service, an adjustment can be made to change the amount due and the resulting effect on the device 202. For example, should a customer want to upgrade to a larger electrical output, a code can be generated. Upon being received and decrypted in the MCU 206, the threshold of the output switch 316 can be increased. Alternatively, the battery 204 can include a charging threshold, limiting the amount of charge the battery 204 can hold. Upon receiving a code upgrading the device 202, the charging threshold of the battery 204 can be increased.

[0046] Should a customer want to downgrade or remove a new feature, product or service to the device, an adjustment could be made to change the amount due and the resulting effect on the device. For example, upon receipt of a downgrade code, the threshold of the output switch 316 or the charging threshold of the battery 204 can be decreased.

[0047] FIG. 3 is a flow diagram for configuring a digital payment enabled service access device in one exemplary embodiment of the invention. The method 300 for configuring the digital payment enabled service access device, such as the electricity access device 102, 202 described with reference to FIGs. 1-2, at block 302, an encrypted code is received in a service access device. The code is received in a code

communicator, such as the communicators described with reference to FIGs. 1-2. The code can be transmitted in any suitable way. In an example, the code is transmitted to a customer and is input in the device by the customer. In another example, the code is transmitted directly from a service provider to the device.

[0048] Upon being received in thee communicator, the code is transferred from the communicator to the microcontroller/processor. At block 304, the code is decrypted by the microcontroller. The microcontroller employs the keys preloaded on the device during manufacturing to decrypt the code.

[0049] At block 306, the microcontroller analyzes the decrypted code to identify the configuration instructions contained therein. As described above with respect to FIG. 2, the code contains a plurality of fields, directing the microcontroller to configure the service access device. For example, as discussed above, the code can include an override command or a value adding/changing command. At block 308, the microcontroller configures the device as instructed by the decrypted code.

[0050] FIG. 4 is a flow diagram of a method 400 for configuring a digital payment enabled service access device in one exemplary embodiment of the invention. The service access device can control access to a variety of products or services, whether real or virtual. Examples of these services include electricity, water (metering by time of water access, total amount of water, or by rate), weather information access (metering by time of weather information access or total amount of weather information access), and GSM/CDMA wireless micro-cell signal repeater access (metering by time of network access, total amount of network access, or by rate). Additional examples of services include radio or audio content, television or audio and visual content, video game content, streaming media content, and internet data content, metering by time of service access or total service access.

[0051] A sales person can introduce the customer to the device and the service(s) and gauge the customer's interest. If a device has not received a valid code since having been locked (fresh from the factory), a demo code may be entered to provide a predetermined timed period of service (e.g., 45 seconds), for sales, demo, or training purposes. Upon purchasing the device, a customer account is created in the service provider's system. The serial number of the device is registered to the customer's account.

[0052] At block 402, notification of a customer payment is received at a service provider. The payment can be made by the customer or, alternatively, by a third party on behalf of the customer. The payment can be for services and/or a payment on the cost of the device. In another example, the payment can be for a service/device upgrade or downgrade. In another example, the service provider can receive a service request, such as a reset request, rather than a payment notification. The service provider can be notified of the payment and the payment is credited to the customer's account.

[0053] At block 404, the payment is validated. If the payment is not valid, a notice is sent to the customer at block 406. If the payment is valid, the service provider generates a unique code at block 408. As discussed above, the code is unique to the device and includes configuration instructions for the service access device. The code is encrypted after the code is generated.

[0054] At block 410, the encrypted code is transmitted. In an embodiment, the code is transmitted to the customer to be input in the communicator of the device. For example, the code can be transmitted to a customer's cell phone, via an SMS message, phone call, or other suitable method. The customer can input the encrypted code in any suitable manner. For example, the code can be entered using an infrared (IR) keypad and an IR receiver. In another embodiment, the encrypted code can be transmitted directly from the service provider to the service device.

[0055] At block 412, the code is received by the device. The code is received in a communicator of a digital payment enabled service device. In an example, the customer can input the encrypted code in the communicator. At block 414, the digital payment enabled system is configured based on the code. Examples of various configuration instructions are described above with reference to FIG. 2. [0056] In an example, upon receiving the code, the microcontroller decrypts the code and analyzes the code to determine the instructions therein. The code contains a configuration instruction. For example, the code can instruct the microcontroller to unlock the device for a predetermined period of time.

[0057] The device tracks time. Upon receiving a code to unlock the device for a period of time, the microcontroller adds the period of time indicated in the code to the current time to create a lock threshold. When the current time reaches the lock threshold, the device locks and service is halted. While the lock threshold is described here in reference to time, the lock threshold can be generated based on a variety of parameters, such as amount of service dispensed or a rate of service dispensed.

[0058] Upon receiving the instruction to unlock the device, the microcontroller determines if the device is currently locked or unlocked. For example, the

microcontroller determines if the current time has exceeded the lock threshold. If the device is unlocked, the microcontroller adds the period of time indicated in the code to the current lock threshold to generate a new lock threshold. The device will not lock until the current time exceeds the new lock threshold. If the device is currently locked, the microcontroller unlocks the device and adds the period of time indicated in the code to the current time to generate a new lock threshold. When the new lock threshold is exceeded, the device locks. Upon receipt of a new payment, the service provider generates a new code and sends the code to the customer. An automated payment reminder can be sent at predetermined times in advance of expiration of the unlocked period.

[0059] While the output is blocked, the input may be enabled, for example, to allow for energy storage to continue. While the device is locked, the device may turn on power briefly to energize the receiver. The receiver will periodically send a command to keep the device energized to facilitate code entry. If the command is not received by the device, the device will power down (e.g., receiver sends commands lx per second for 30 seconds to keep the device active to receive codes) [0060] The digital payment enabled service device can be purchased under a variety of plans/models. Examples of these models include pay-for-utility model, pay-to-own model, and loan model. Under a pay-for-utility model, a customer makes digital payments to receive access to a service. The hardware is never purchased or owned by the customer. The payments due and service provided may be calculated on a pre-paid or a post-paid basis. Payment for access to energy continues in perpetuity.

[0061] Under this model, the customer receives the device, with or without a down payment. Payments are made by the customer and received by a service provider. A code is issued that unlocks the device to provide a service for a period of time or for a metered amount of service appropriate for the amount of the payment. Once the amount of time has elapsed or the metered energy has been dispensed, the device locks until another payment is made and a code is received by the device. The customer continues to make payments in order to receive access to the service. The customer purchases the service and never owns the hardware. Payments take into account hardware

service/replacement costs.

[0062] Under a pay to own (relative timing) model, a customer makes payments and receives service access until a cumulative total predetermined amount of payment is received, at which time the customer is granted ownership of the device and the device is unlocked without any trigger threshold or instruction to return to the locked state.

[0063] Under this model, a customer enters a plan similar to a pre-paid mobile phone plan whereby a customer pays for minutes up front and, once consumed, must top up again in order to use the phone. A down payment may be collected. Payments are made by the customer and received by the service provider. A code is issued that unlocks the device to provide the service for a period of time or a metered amount of the service appropriate for the amount of the payment. Once the amount of time has elapsed or metered energy has been dispensed, the device locks until another payment is made and a code is received by the device. Payments are made until the system is fully paid for and then a "master unlock" code is sent to unlock the system without a time expiration or metered energy threshold. [0064] Under a loan (absolute timing) model, a customer is required to make periodic payments until the device is paid in full, similar to a home mortgage or car loan. If payments are made in the appropriate amount and on time, the device unlocks to provide electricity until the next payment is due. Should a payment not be received on time, or the appropriate amount due, the device will not unlock until the minimum amount due is received. The device will then only remain unlocked until the next payment is due.

When the total amount of payment due on the loan is received, the customer is granted ownership of the device and the device is unlocked without any condition to return it to the locked state.

[0065] Under this model, a customer enters a lease-to-own model, similar to a home mortgage or car loan with a down payment, interest rate, and regular repayment schedule. A down payment is collected, initiating the loan. Payments are made by the customer according to a loan schedule (e.g., monthly on the 1^st of the month) and received by the service provider. A code is issued that unlocks the device to provide power via the outputs for a period of time appropriate for the amount of the payment. Once the amount of time has elapsed, the device locks. Should the customer make a later payment, the device will unlock. However, the device will lock again at the end of the moth, requiring a payment on the regularly scheduled date to unlock the device for the next month. The late payment does not allow for the customer to have access to the service for a full month, only until the next regularly scheduled payment.

[0066] Under any of the models, if payment is received late and/or below the amount due, a fee or penalty may be applied. This penalty may take the form of increasing the total amount due, increasing the tariff for energy (the cost per amount of time, service provided), etc.

[0067] In either the pay to own model or loan model, if a customer is granted ownership of the device, the digital payment enabled control system may be re-enabled should the customer want to add a new feature, product, or service to the device, refinance the loan, or utilize the device as collateral for a loan for another purpose. A custom code can be transmitted for reconfiguring the device. The custom code alters the key(s) within the device for the purpose of re-enabling the device into a new mode, or to adjust configuration and/or adjust capacity of the device.

[0068] Alternative pricing models and incentives may be applied to the customer's account to encourage a certain behavior, such as on-time payment, size of payment, frequency of payment, etc. The incentive could be in the form of additional credit added to the customer's account, additional time represented in a code, or a combination thereof. Other incentives could include an early-payoff discount, reducing the total balance owed. Additionally, the service device can include a fraud protection system. If the system energizes ten times with no valid code entry, the device locks for thirty minutes. Additionally, past codes are invalidated to prevent reuse of codes. A code can be transmitted to re-key the device, invalidating all past codes and returning the device to a known state.

[0069] Upon a payment rendering the account balance zero, a permanent unlock code can be sent to the customer. The permanent unlock code disables the digital payment system. In an example, the digital payment system can be removed from the device after inputting the permanent unlock code. In another example, the digital payment system can be reactivated after inputting the permanent unlock code, such as when a customer upgrades the service device or uses the device as collateral for a loan.

[0070] An account can be upgraded with more features (e.g., solar power, battery capacity, etc). This upgrade is logged in the service provider's database and payment parameters are defined, enabling the process to continue under new terms. If the device has not been "unlocked", a code is sent instructing the microcontroller to configure the device to include the upgrade. If the device has been "unlocked", a code could be entered to relock the device and initiate the customer's account again under new terms.

[0071] In view of the foregoing, embodiments of the invention describe a code enabled device for providing a service. A technical effect is to allow customers to receive a code in an area with communication service and input the code in a service device located in an area without communication service in order to receive a service provided by the device. [0072] As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method, or computer program product.

Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.), or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "service," "circuit," "circuitry," "module," and/or "system." Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.

[0073] Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0074] Program code and/or executable instructions embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0075] Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one ore more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer (device), partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0076] Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[0077] These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

[0078] The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[0079] This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to practice the invention, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the invention is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal language of the claims.

Claims

What is claimed is:

1. A device for providing a service to a customer, comprising:

a communicator for receiving an encrypted code comprising an instruction for configuring the device; and

a microcontroller for:

decrypting the code received by the communicator;

analyzing the decrypted code to identify the instruction therein; and configuring the system according to the instruction of the decrypted code.

2. The device of claim 1, wherein the decrypted code comprises a plurality of fields, the fields comprising the instruction for configuring the device.

3. The device of claim 2, wherein the plurality of fields comprise command type, command parameter, sequence number, and checksum.

4. The device of claim 1, wherein the encrypted code is generated by a service provider and transmitted to a customer to input in the communicator.

5. The device of claim 1, wherein configuring the device comprises changing an operating parameter of the device.

6. The device of claim 5, wherein changing the operating parameter comprises one of unlocking the device, changing a method by which the service is metered, setting voltage thresholds, tracking a fuel gauge/state of charge, setting a fuel gauge/state of charge threshold, limiting an input charge rate, limiting a maximum output rate, or a combination thereof.

7. The device of claim 1, wherein configuring the device comprises reconfiguring the device to alter a key of the device.

8. The device of claim 1, wherein configuring the device comprises disabling the service.

9. The device of claim 1, wherein the code is invalidated after use.

10. A method for configuring a service device, the service device comprising a communicator and a microcontroller, the method comprising:

receiving an encrypted code in the communicator; transferring the encrypted code to the microcontroller;

decrypting the encrypted code into plain text in the microcontroller, the decrypted code comprising a plurality of fields to instruct the microcontroller to configure the digital payment enabled device;

analyzing the decrypted code to determine an instruction therein; and

configuring the digital payment enabled system as per the instruction of the decrypted code.

11. The method of claim 10, wherein configuring the device comprises changing an operating parameter of the device.

12. The method of claim 11 , wherein changing the operating parameter comprises one of changing a service time threshold, changing an amount of service to be dispensed, and changing a rate of service to be dispensed.

13. The method of claim 10, wherein receiving the code comprises receiving the code as input by a customer.

14. The method of claim 10, further comprising:

receiving a payment from a customer;

generating the code; and

transmitting the code to the customer to input in the communicator.

15. The method of claim 10, wherein configuring the device comprises altering a key of the device.