[go: up one dir, main page]

WO2015174932A1 - Procédé et système destinés à l'opération d'un dispositif sans connexion intégré à faible coût fondé sur la répartition avec une interface utilisateur - Google Patents

Procédé et système destinés à l'opération d'un dispositif sans connexion intégré à faible coût fondé sur la répartition avec une interface utilisateur Download PDF

Info

Publication number
WO2015174932A1
WO2015174932A1 PCT/SG2015/050115 SG2015050115W WO2015174932A1 WO 2015174932 A1 WO2015174932 A1 WO 2015174932A1 SG 2015050115 W SG2015050115 W SG 2015050115W WO 2015174932 A1 WO2015174932 A1 WO 2015174932A1
Authority
WO
WIPO (PCT)
Prior art keywords
activation
codes
code
activation code
activating
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/SG2015/050115
Other languages
English (en)
Inventor
Vladimir PERVOUCHINE
Karl Heinz REMMERS
Sebastian Franz Ludwig HAENDEL
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Publication of WO2015174932A1 publication Critical patent/WO2015174932A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2137—Time limited access, e.g. to a computer or data

Definitions

  • the present disclosure relates to the activation of a non-network enabled device.
  • Such devices may be particularly suited to use in remote and third world countries, but are not limited to such use.
  • PAYG pay-as you-go
  • the PAYG device should only be useable when the user has paid for that usage.
  • One such method involves using a cellular network to connect to a main station for payment verification.
  • the Indigo devices by Azuri Technologies Ltd use such a technology. These methods require the devices to be network-enabled (i.e. to be capable of communicating over a network) so that payment verification can be sent to the device to activate the device.
  • Network connectivity entails hardware and software complexity, and associated expense. A large amount of software code is also required to support the various network communication protocols and a multitude of available prepaid cards.
  • a further method uses cryptographically protected activation keys that the user enters into the device.
  • the device deciphers the keys and activates the device.
  • Such a method is described in patent WO2011149644 A3, entitled “Techniques for progressive purchasing”.
  • the activation keys are necessarily long so as to contain a protected authorization token, and proper cryptography algorithms require considerable computing power to manage such activation keys.
  • Low-end, simple controllers are typically not capable of operating with such cryptography.
  • the inventors have realized the need to service remote and third world areas, among others, to ensure consistent access to basic utilities such as electricity.
  • methods and systems e.g. solar panels
  • the present disclosure provides a method for controlling activation of a non-network enabled device, the device having a memory and an activation interface through which new activation codes can be entered for activating the device, the method comprising the steps of: receiving a first system activation code through the activation interface; comparing the first system activation code to one or more device activation codes from a group of predetermined device activation codes stored in the memory of the device; activating the device for a predetermined period if the system activation code corresponds to the one device activation code of the one or more device activation codes; deactivating the device when the predetermined period expires; and repeating the receiving, comparing, activating and deactivation steps with a second system activation code that is different from the first system activation code.
  • the present disclosure provides a method for controlling activation of at least one non-network enabled device, the method being performed between at least one device and a computing system, each device having a unique device identifier and comprising: an activation interface through which new activation codes can be entered for activating the device; and a memory, the computing system comprising: a processor; and memory, the method comprising the steps of: receiving, at the computing system, activation request information including the unique device identifier or information from which the unique device identifier is derivable, and information confirming receipt of a payment for activating the device; locating, using the unique device identifier, a first system activation code from a group of predetermined system activation codes stored in the memory of the computing system; receiving the first system activation code through the activation interface; comparing the first system activation code to one or more device activation codes from a group of predetermined device activation codes stored in the memory of the respective device; activating the device for a predetermined period if the system new activation code corresponds to one device
  • the present disclosure provides a non-network enabled device having one or more functions that can be activated, the device comprising: an activation interface through which system activation codes can be entered for activating the device; a memory for storing a group of predetermined device activation codes; a processor for: comparing system activation codes, received through the activation interface, to one or more device activation codes from the group of predetermined device activation codes stored in the memory; activating the device for a predetermined period when a system activation code, received through the activation interface, corresponds to one device activation code of the one or more device activation codes; deactivating the device when the predetermined period expires; and repeating the comparing, activating and deactivation steps once a second system activation code, that is different from the first system activation code, is received through the activation interface.
  • Some embodiments may provide a system and method for low-cost, connectionless (i.e. non-network enabled), PAYG device payments.
  • a method for controlling activation of a device may be performed between two or more devices and a computing system.
  • the computing system may comprise a central server for providing PAYG services for a multitude of devices.
  • Figure 1 illustrates an example of a full cycle of coordination between server, user and electronic device with integrated PAYG verification according to present teachings.
  • Figure 2 Depicts an example of a server operation diagram according to present teachings.
  • Figure 3 Shows an example of an integrated PAYG device operation diagram according to present teachings.
  • Figure 4 Illustrates an example of an integrated 3 button user interface layout for entering activation codes according to present teachings.
  • Figure 5 Depicts an example of the assignment of an individual list of activation codes to the device by the server according to present teachings.
  • Figure 6 Depicts an example of a block diagram of a server which may be used in the system or standalone according to present teachings.
  • Figure 1 illustrates an example of a full cycle of coordination between a computing system (presently a server), user and non-network enabled device (e.g. an electronic device such as a radio, stereo, solar panel, heater and so forth) with integrated PAYG verification.
  • non-network enabled device e.g. an electronic device such as a radio, stereo, solar panel, heater and so forth
  • the non-network enabled device may instead be a non-telephonic device.
  • Devices such as solar panels contemplated herein, are capable of use without connection to an electricity grid of telecommunications network. They are thus suitable for use in remote and third world areas.
  • the user may need to make a payment.
  • the portable device may operate without limitation (Rent-to-own model). Ensuring the user pays for usage allows the device to be paid off over time, thus avoiding the upfront capital cost of the device itself.
  • Payment for the device may be made, for example, via a paid SMS, phone call, through an authorized distributor, or any other payment means. Payment may be payment for the device only. Alternatively, payment may be payment for the device and for some usage of the device.
  • the computing system may be arranged to receive such payment information without involvement of cryptography or online data verification.
  • Each non-network enabled device is associated with a unique device identifier such that, once the user makes payment for the device, the relevant device can be identified 101 by the computing system.
  • the computing system will typically receive an activation request comprising activation request information including payment information or payment confirmation information.
  • the computing system may receive the unique device identifier as part of the activation request information.
  • the computing system may derive the unique device identifier either from the activation request information.
  • the activation request information may comprise a phone number associated with a person (e.g. device user) who is also associated with the device.
  • the unique device identifier may be derivable from the device user bank account details, address details, or email address, or unique mobile telephone identification information (e.g.
  • the unique device identifier may be a unique identifier of the user (i.e. a personal detail or personal details of the user).
  • the computing system sends the unique device identifier to activation code selection 102.
  • the unique device identifier is used to generate an activation code based on a list of predetermined system activation codes stored in memory of the computing system, where the predetermined system activation codes correspond to the unique device identifier.
  • the system activation codes are “predetermined” in that they are loaded into the system before payment is made by the user for the device or for usage of the device. Each time a payments is made by the user for the device or for usage of the device (subject to any minimum payment criteria), the next activation code in the list of predetermined activation codes is sent by the system (e.g. to the user).
  • the computing system stores a number (e.g. one or more lists) of such system activation codes for activating the device.
  • a number e.g. one or more lists
  • the first system activation code from the respective list of system activation codes is sent back to the user.
  • the next system activation code i.e. next down on the list
  • the next system activation code is selected from the list of predetermined system activation codes corresponding to the unique device identifier.
  • the new system activation code Upon selection of a new system activation code from memory of the computing system, the new system activation code is sent to the user.
  • the user inputs the activation code into the device 103 which compares the system activation code to a list of device activation codes 104 stored in memory of the device. If the system activation code corresponds to (e.g. exactly matches) a relevant one or ones of the device activation codes, the device or desired device function is activated 105.
  • each system activation code may be paired with a respective device activation code.
  • the system activation code is verified or compared against one or more device activation codes from the list or group of predetermined device activation codes stored in memory of the device. If the system activation code corresponds to one of the relevant device activation codes (e.g. there is an exact match or the two codes comply with a relationship by which one is identifiable with the other) the device or a device function is activated or unlocked (105).
  • the predetermined device activation codes may be loaded into the device before initial purchase, during manufacture or at any time before the user receives the first system activation code for entry into the activation interface of the device.
  • the device activation codes are “predetermined” in the sense that they are known by the device – and not by the user – in advance of any system activation codes being entered into the activation interface.
  • the system activation codes may similarly be loaded into memory of the system in advance of any activation request information being received.
  • repeated incorrect activation code entries may block (i.e. deactivate) the device or a device function for a period of time.
  • a system activation code may be accidentally or inadvertently entered.
  • the device may determine if the system activation code was entered intentionally and disregard it if not. For example, the device may measure the time between successive button activations (e.g. button presses) on an activation interface and disregard the button activations if the time therebetween is sufficiently long.
  • FIG. 2 shows an illustrative example of server operation.
  • a payment 201 is received.
  • the payment 201 can be made via paid SMS, paid phone line, operator, or any other means providing the computing system (e.g. a remote server) with information comprising unique device identifier, or information from which the unique device identifier can be derived, and desired device function(s).
  • the computing system e.g. a remote server
  • information comprising unique device identifier, or information from which the unique device identifier can be derived, and desired device function(s).
  • the computing system keeps a group (hereinafter referred to as a list) of predetermined activation codes for every device (see 202 in Figure 2).
  • the list of predetermined activation codes stored in the computing system may be an exact copy of the list or group of predetermined device activation codes stored in the respective device.
  • the computing system may also store the current system activation code position in the respective list(s) of system activation codes for each device (see 203 in Figure 2).
  • the computing system From the unique device identifier, the computing system consults the list of predetermined system activation codes for the device, and the current system activation code position in the list of predetermined system activation codes (see 204 in Figure 2). The current system activation code is sent back to the user. The computing system then increments the current system activation code position to be the next position in the list of predetermined system activation codes.
  • the user may be delivered the activation code in a number of ways including via email, SMS or postal mail.
  • the user paid via mobile phone the user could receive the system activation code either via SMS reply from the computing system, via voice generated reply or other means by which the user can receive a response from the computer system at the mobile phone through which the payment was made.
  • a list of predetermined system activation codes may be maintained for each function.
  • the activation request information received by the computing system may include information on the function or functions the user wishes to activate.
  • the corresponding list of predetermined system activation codes for the desired function or combination of functions is selected and the system activation code at the current position in that list of predetermined system activation codes is sent to the user.
  • the computing system updates the current system activation code position in the list of predetermined system activation codes – in other words, the current activation code position in the list of activation codes is incremented (see 205 in Figure 2).
  • a current activation code or expected activation code
  • the current activation code for each list is at a particular position in the respective list.
  • a different current activation code and its position in each list may be stored in memory of the device.
  • the same current activation code position in all relevant lists may be used and thus only one position needs to be stored by the device for all lists of predetermined device activation codes.
  • each system and device activation code may be a number formulaically set, each system and device activation code may comprise a random number. Since each system activation code is paired with a respective device activation code, the one of the system activation code and device activation code will be the random number, and the other of the system activation code and device activation code will be made to match or appropriately pair to that random number.
  • Figure 3 shows an example of an integrated PAYG device operation diagram according to various embodiments described herein.
  • the user enters the system activation code into the device 301, it is compared with the device activation code in the next position 302 in the list of predetermined device activation codes 303. If the entered system activation code corresponds to the device activation code the corresponding purchased device function is activated 304.
  • a system activation code may be lost.
  • the device may check more than one activation code when determining whether a match or appropriate correspondence exists.
  • the expected device activation code i.e. the code the device expects to receive, or the code in the list of predetermined device activation code immediately after the most recently received device activation code with which a positive match was found
  • the device may check the device activation code at the next (i.e. immediately after the current activation being that which was most recently matched with an inputted system activation code) position in the list of predetermined device activation codes and, if no correspondence (e.g. match) is found, check one or more subsequent positions in the list of predetermined device activation codes as shown at 307 and 305 in Figure 3.
  • the device upon receipt of a system activation code the device, the operation of which is illustrated by Figure 3, compares the activation code in the next position (i.e. current position in the list + 1) and, if necessary, several device activation codes 305 that follow in the list of predetermined device activation codes to determine the actual current device activation code position.
  • the desired device function may be enabled 304 and the current device activation code position may be set to device activation code with which a match was found. This way the current device activation code position in the device and the current system activation code position in the computing system are once again matched.
  • the device may be blocked 306 for a period of time to discourage code guessing.
  • the device may be a multifunction device.
  • the device will be capable of performing several functions.
  • the device may provide cellphone charging, lighting, sound recording, radio playing or other functions.
  • a multifunction device may be activated in its entirety – in other words, upon activation of the device, all of its functions may be activated.
  • each function of the device may be activated separately or a subset of the functions may be activated (e.g. for a device providing clock, radio and CD-player functions, two of the three functions may be activated).
  • payment can be made such that each function can be paid for and activated separately from other functions.
  • SMS payment When making payment, the user can choose the specific function desired to the activated. Where SMS payment is afforded such selective function activation may be achieved, for example, using different server SMS numbers (i.e. a number associated with the computing system, or server, that debits payment from the user’s account) or different SMS content.
  • server SMS numbers i.e. a number associated with the computing system, or server, that debits payment from the user’s account
  • SMS content i.e. a number associated with the computing system, or server, that debits payment from the user’s account
  • the server will respond with a system activation code for activating the desired function(s).
  • the device may store a plurality of lists of predetermined device activation codes in memory (e.g. one list of activation codes per function). Each list of predetermined device activation codes may correspond to a respective one of the functions of the device. Alternatively, one or more lists of predetermined device activation codes may correspond with one or more of the functions of the device. Corresponding identical lists of predetermined device activation codes are located on the computing system. The computing system may store the corresponding unique device identifier for each list of predetermined device activation codes.
  • the server stores list of predetermined system activation codes that correspond to the lists of predetermined device activation codes stored in memory of the device.
  • the correspondence between the codes in the respective lists may be that the system activation code is the same (i.e. exactly matches) the respective device activation code.
  • the correspondence may be that the system activation codes at the server have a predetermined relationship with the device activation codes at the device (e.g. one can be transformed into the other through a known algorithm).
  • the server returns a corresponding system activation code from the corresponding stored list of predetermined system activation codes 203 for the device and/or the desired function.
  • the system activation code is entered into the activation interface and the device then compares the entered system activation code 303 with activation codes from the lists of predetermined device activation codes for each device function. Once a corresponding code is found (i.e. the comparison is successful) the function corresponding to the list of predetermined device activation codes that contained the successfully compared device activation code is enabled 304.
  • the current device activation code is set to the device activation code with which the match was made. It will be appreciated that it is simple to rely on the “expected” activation code (i.e. the activation code that is next expected to be received through the activation interface) rather than the current activation code, and all such alternative implementations of the present concepts are intended to fall within the scope of the present disclosure.
  • the expected activation code can be useful since the expected activation code will be null when the final payment has been made for the device. Thus, setting the expected activation code to a null activation code will indicate to the device that the device has been fully paid for.
  • the expected or current activation code in each list may be at a different location in the respective list or may be incremented independently of the expected activation codes in the other lists.
  • the expected activation code in each list may be concurrently updated for each time a successful comparison is made. In the latter case, it may be easier to monitor when a PAYG rent-to-own process (i.e.
  • the position of the expected activation code for all lists of predetermined device activation codes is common and is incremented for every list of predetermined device activation codes with every successful match 307.
  • the maximum number of activation codes required before the user has paid in full for the device, and the device is no longer deactivated is equal to the value of the device divided by the minimum payment amount for activating one or more functions of the device.
  • the current activation code position may be incremented for all lists for the particular device when a system activation code from any one of the lists is sent to the user.
  • the current system activation code position in each list for the particular device may be incremented independently of the current system activation code positions in the other lists.
  • Figure 4 is a partial illustration of a device having one or more functions that can be activated.
  • the device comprises an activation interface through which system activation codes can be entered for activating the device.
  • the device comprises an integrated 3-button activation interface layout for entering system activation codes.
  • the simplicity of the activation interface does not deprive the device from being secure.
  • the system activation code may in fact be of any desired length.
  • the system activation code simply comprises a sequence of button activations of buttons (A, B, #) in Figure 4.
  • the system and device activation codes may have a length of one byte. In such cases, the need for 10-button code entry keypad (i.e. activation interface) is removed and the interface itself can be greatly simplified as shown. This may result in a lowering of internal circuit complexity in the device.
  • buttons A, B, # of the activation interface of Figure 4 there may be two code entry buttons (e.g. A and B) and an activation code send button (e.g. #).
  • a new activation code can be entered by activating the code entry buttons A, B in a particular sequence.
  • the system activation code will then be compared – against the device activation codes – by the processor when the activation code send button # is activated.
  • the activation interface comprises three buttons and receiving a new system activation code through the activation interface comprises receiving a signal corresponding to a sequence of activations of the three buttons. Where only two of the three buttons are used to enter a new system activation code, receiving a signal corresponding to a sequence of activations of the three buttons may include receiving a signal the end of which is indicated by activation of a particular one of the three buttons.
  • a 2-button interface may also be used – for example, the #-button may be omitted.
  • Such an interface may be particularly suitable in cases where the device activation codes have a common length of X-digits – where “X” is an integer number.
  • the device may accept that last sequence of X-button presses when determining if a correct system activation code (i.e. one that can be matched with a corresponding device activation code) has been entered on the activation interface. It will be appreciated that a device having an interface with 4 or more buttons may also be used while making use of some of the present teachings.
  • buttons should include in its scope physical and virtual buttons, slidebars, and other physical and virtual features by which a user can interact with a device.
  • the activation interface may comprise buttons that, when the device is activated, are assigned an operation for controlling at least one of the one or more functions.
  • buttons A and B may in fact be the volume “+” and “-“ buttons of a stereo.
  • the server may convey the system activation code by sending the user a particular sequence of key presses required for entry of the system activation code.
  • This sequence may be represented by symbols, letters or numbers, for example A and B as per the button labels 401. This may reduce the number of additional buttons on the device from traditional 10-digit keypads to less than 10 digits.
  • existing buttons on the electronic device otherwise used in the functional operation of the device, can be re-programmed to be used for system activation code entry as discussed in relation to the volume adjustment “+” and “-“ buttons.
  • the system activation code is received by the activation interface it is compared to one or more device activation codes from a group of predetermined device activation codes stored in the memory of the device.
  • the comparison is performed by a processor that also activates the device for a predetermined period when an accepted correlation (e.g. an exact match) is found between a new activation code, received through the activation interface, and one device activation code of the one or more device activation codes that are stored in the memory of the device.
  • the processor is also capable of deactivating the device when the predetermined period expires.
  • a second new activation code is received through the activation interface, compared with relevant predetermined device activation codes, the device is activated if a corresponding device activation code is found and the device is deactivated after a predetermined period.
  • the processor ensures that the device remains active provided there is an activation code that states the device should remain active (e.g. the activation code relates to a particular payment amount associated with a period of use of the device), and the processor otherwise deactivates the device.
  • the predetermined period may be associated with the system activation code.
  • the predetermined period over which the device is activated after entry of one system activation code may be different from the predetermined period over which the device is activated after entry of a different system activation code.
  • the processor is also configured to disable the device in the event that a predetermined number of incorrect system activation codes (i.e. activation codes that do not correspond with respective device action codes stored in memory of the device) are entered into the activation interface.
  • the predetermined number may be 1, 2, 3 or any desired number.
  • the processor may also, or alternatively, be configured to disable the device for a set period of time (e.g. 1 minute, 5 minutes or 15 minutes) in the event that a predetermined number of incorrect attempts are made at entering system activation codes into the activation interface.
  • the user can simply start over from the beginning and only press the activation button when the correct activation code has been entered.
  • the user can simply start over from the beginning and only press the activation button when the correct activation code has been entered.
  • only the last relevant number letters or symbols entered into the activation interface will be considered when verifying the system activation code (i.e. comparing it to the relevant device activation code(s)).
  • the “relevant number” will be understood to be the number of code elements (symbols, digits or letters) equal to the length of the system, and device, activation code.
  • the activation interface also includes an LED 403.
  • the LED informs the user of a successful or unsuccessful code entry result. For example, the LED may remain steady or turn green for a correct system activation code entry, and may flash or turn red for an incorrect system activation code entry.
  • the device logic can be implemented with a very cheap low-end microcontroller, for example Atmel ATtiny13 microcontroller, measuring just 3x3x1 mm in MLF packaging. Any other suitable controller or microcontroller may be used. Additional keyboard controllers may not be required as input and confirmation can be performed with just three buttons (or two, if a 2-button interface is used).
  • the present device is a PAYG device.
  • it is paid off over a period of time by the user of the device making successive payments for use of the device and for the device itself. In some cases, payments will only be made for the device itself.
  • a system activation code will typically be sent each time a payment is made by the user. In a “rent-to-buy” situation, the user will ultimately own the device after having made the relevant number of payments. In this case, once the portable electronic device is paid off in full, it may be activated in perpetuity (i.e. its ongoing operation will not be stopped).
  • Figure 5 depicts an example of a process to distribute lists of activation codes according to various embodiments described herein.
  • the device may be programmed during production (e.g. at the assembly station of the device). This allows the lists of activation codes (system and device activation codes) to be protected from leaks during production, as all lists of activation codes are properly generated by the server and programmed on the devices before shipping to client. At no point do lists of activation codes have to go through a third party.
  • the device may be programmed by exposing ISP contacts of the microcontroller, allowing the device to be attached to the programmer 502.
  • Memory of the device may alternatively be loaded with device activation codes after manufacture.
  • each device can be equipped with a computer readable identification tag – for example an RFID or barcode (e.g. quick response (QR) code) – so that it is read automatically 501 and sent to computing system or server 503.
  • the computing system 503 generates lists of device activation codes for the device 504, sends them (e.g. to a programmer or distributor) for uploading to the device, and stores the corresponding list of system activation codes.
  • the list of activation codes can be obtained from hardware entropy generators, which derive true random information from a stochastic physical process. This makes activation codes unpredictable, so the user is not able to derive next code from previous one.
  • the generated lists of activation codes may be immediately sent back from the server to be uploaded to the device (e.g. by a programmer, a distributor and/or using specialized equipment through which the activation codes can be taken from a network and loaded into memory of the device without human interaction during the loading process).
  • TLS Transport Layer Security
  • Activation code lists will typically be programmed into a microcontroller.
  • the microcontroller can be small.
  • the small size of the microcontroller may allow it to be protected from physical tampering.
  • the microcontroller may be laminated with other essential device electronic components. Therefore accessing the microcontroller is likely to damage essential electronic components of the device. This may discourage tampering.
  • an incorrect code entry causes a significant delay before a new attempt at entering a system activation code can be made.
  • the device may be locked for a period of time.
  • the device 10 may also inform the user that the input is blocked, for example, by a flashing a LED indicator 403, as seen in Figure 4.
  • the computing system would likely be unaware of a guessed system activation code. As such, when a request for an activation code is subsequently made, the computing system will respond with the activation code already guessed by the user since this activation code is the current activation code in the list of predetermined system activation codes for the device or relevant function(s) of the device. Since the system activation code has been previously used it will not activate the device, and the user will have to make another payment to receive a new system activation code to activate the device or desired function(s).
  • FIG. 6 shows an exemplary block diagram illustrating a computing system, comprising a server 600, which may be used in the system 100, in other systems, or standalone.
  • the server 600 may be a digital computer that, in terms of hardware architecture, generally includes a processor 602, input/output (I/O) interfaces 604, a network interface 606, a data store 608, and memory 610.
  • I/O input/output
  • Figure 6 depicts the server 600 in a simplified manner, and a practical embodiment may include additional components and suitably configured processing logic to support known or conventional operating features that are not described in detail herein.
  • the components (602, 604, 606, 608, and 610) are communicatively coupled via a local interface 612.
  • the local interface 612 may be, for example but not limited to, one or more buses or other wired or wireless connections, as is known in the art.
  • the local interface 612 may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers, among many others, to enable communications.
  • the local interface 612 may include address, control, and/or data connections to enable appropriate communications among the aforementioned components.
  • the processor 602 is a hardware device for executing software instructions.
  • the processor 602 may be any custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the server 600, a semiconductor-based microcontroller (in the form of a microchip or chip set), or generally any device for executing software instructions.
  • the processor 602 is configured to execute software stored within the memory 610, to communicate data to and from the memory 610, and to generally control operations of the server 600 pursuant to the software instructions.
  • the I/O interfaces 604 may be used to receive user input from and/or for providing system output to one or more devices or components. User input may be provided via, for example, a keyboard, touch pad, and/or a mouse.
  • I/O interfaces 604 may include, for example, a serial port, a parallel port, a small computer system interface (SCSI), a serial ATA (SATA), a fiber channel, Infiniband, iSCSI, a PCI Express interface (PCI-x), an infrared (IR) interface, a radio frequency (RF) interface, and/or a universal serial bus (USB) interface.
  • SCSI small computer system interface
  • SATA serial ATA
  • PCI-x PCI Express interface
  • IR infrared
  • RF radio frequency
  • USB universal serial bus
  • the network interface 606 may be used to enable the server 600 to communicate on a network, such as the Internet, a wide area network (WAN), a local area network (LAN), and the like, etc.
  • the network interface 606 may include, for example, an Ethernet card or adapter (e.g., 10BaseT, Fast Ethernet, Gigabit Ethernet, 10GbE) or a wireless local area network (WLAN) card or adapter (e.g., 802.11a/b/g/n).
  • the network interface 606 may include address, control, and/or data connections to enable appropriate communications on the network.
  • a data store 608 may be used to store data.
  • the data store 608 may include any of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, and the like)), nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, and the like), and combinations thereof. Moreover, the data store 608 may incorporate electronic, magnetic, optical, and/or other types of storage media. In one example, the data store 608 may be located internal to the server 600 such as, for example, an internal hard drive connected to the local interface 612 in the server 600. Additionally in another embodiment, the data store 608 may be located external to the server 600 such as, for example, an external hard drive connected to the I/O interfaces 604 (e.g., SCSI or USB connection). In a further embodiment, the data store 608 may be connected to the server 600 through a network, such as, for example, a network attached file server.
  • the data in the data store 608 may include personal data of the user, and data relating to the device.
  • the personal data of the user may include the user’s name, phone number, account number, address and other information.
  • the data relating to the device may include the unique device identifier, the type of device, the model number, the serial number and other data.
  • the unique device identifier may be derived from a unique combination of information such as the user’s name and address, where such a combination is indeed unique. In this sense, the unique device identifier may be allocated by the computing system. Alternatively, the unique device identifier may comprise a piece of information or a combination of pieces of information where that information or combination of information is unique to the user of the particular device. If the user has multiple devices and a payment is made in relation to only one of those devices, then information other than that which is common to the user details listed in respect of more than one device may be used to determine which activation codes should be provided to the user.
  • the memory 610 may include any of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)), nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, etc.), and combinations thereof. Moreover, the memory 610 may incorporate electronic, magnetic, optical, and/or other types of storage media. Note that the memory 610 may have a distributed architecture, where various components are situated remotely from one another, but can be accessed by the processor 602.
  • the software in memory 610 may include one or more software programs, each of which includes an ordered listing of executable instructions for implementing logical functions.
  • the software in the memory 610 includes a suitable operating system (O/S) 614 and one or more programs 616.
  • O/S operating system
  • the operating system 614 essentially controls the execution of other computer programs, such as the one or more programs 616, and provides scheduling, input-output control, file and data management, memory management, and communication control and related services.
  • the one or more programs 616 may be configured to implement the various processes, algorithms, methods, techniques, etc. described herein.
  • a skilled person may employ a method for controlling activation of one or more non-network enabled devices, where each device is configured as described herein and is associated with a unique device identifier.
  • the method can be performed between the device or devices and a computing system.
  • each device will include an activation interface (e.g. as shown in Figure 4) through which new system activation codes can be entered for activating the device, and memory.
  • the computing system will include a processor and memory.
  • the resulting method will generally include the steps of: the computing system receiving activation request information including the unique device identifier or information from which the unique device identifier is derivable as described above, and information confirming receipt of a payment for activating the device; using the unique device identifier to locate a first system activation code from a group of predetermined system activation codes (e.g.
  • a list of activation codes stored in the memory of the computing system; receiving the first system activation code through the activation interface; comparing the first system activation code to one or more device activation codes from a group of predetermined device activation codes stored in the memory of the respective device; activating the device for a predetermined period if the system activation code corresponds to one device activation code of the one or more device activation codes; and deactivating the device when the predetermined period expires; and repeating the receiving, comparing, activating and deactivation steps with a second system activation code that is different from the first system activation code.
  • the stored group of predetermined device activation codes may comprise a list of device activation codes.
  • a stored group of predetermined system activation codes i.e. a group of codes stored at the computing system or server rather than at the device
  • comparing the first system activation code to one or more device activation codes may include comparing the first system activation code to two or more device activation codes that are adjacent on the list.
  • adjacent means that the two or more device activation codes are neighbours in the respective list of predetermined device activation codes.
  • the computing system there is a current system activation code being the system activation code that is sent to the device or user upon confirmation of a payment being made.
  • the expected activation code is the system activation code that is next expected to be received through the activation interface.
  • the two or more device activation codes include the expected activation code. Since the activation codes are adjacent in the list, upon activating the device the expected activation code may be updated to be the device activation code listed immediately after the activation code just sent by the computing system and received through the activation interface.
  • FIG. 3 shows an alternative, but functionally similar, embodiment in which the current device activation code is the activation code most recently matched to a corresponding system activation code.
  • the two or more adjacent device activation codes will generally comprise the expected device activation code and one or more activation codes further down the list of device activation codes. This accounts for lost activation codes as discussed above.
  • the device will require a memory for storing a group of predetermined device activation codes, and an activation interface through which new activation codes can be entered for activating the device.
  • the general method of usage will involve: receiving a first system activation code (i.e. an activation code sent by the computing system) through the activation interface; once received, the first system activation code is compared to one or more device activation codes from a group of predetermined device activation codes (e.g.
  • the device is then activated for a predetermined period if the system activation code corresponds to one device activation code of the one or more device activation codes; the device may be deactivated when the predetermined period expires; and the receiving, comparison, activation and deactivation steps can be performed with a second system activation code.
  • Each of the system activation codes is the result of a payment being made for the device or for both the device and use of the device. As such, the user will pay for the device over time.
  • the predetermined period may be a predetermined period of time. That predetermined period of time may be based on time the device is in use. For example, where the device is an air-conditioner, upon receiving payment for 4 hours of use the device may remain active for 4 hours of use even where those 4 hours are distributed over multiple days.
  • the predetermined period may involve activating the device until there has been a predetermined amount of usage of the device.
  • the device is an air-conditioner
  • using the air-conditioner on a low power setting may be considered lower usage than when the air-conditioner is used in a high power setting.
  • the low power setting may take longer to use the entirety of the “predetermined amount of usage” than the high power setting.
  • the “predetermined period” may change, but its expiry can at all times be known in advance since for one power setting it will be longer or shorter by a known amount than for a different power setting, and even where power settings are changed during use the extension or contraction of the predetermined period will be known before expiry of that period.
  • the user may wish to pay in varying amounts for activation of the device.
  • the first system activation code may relate to a particular payment amount paid by a user of the device in exchange for the new activation code
  • the second system activation code may relate to a different payment amount.
  • the device may be activated for a predetermined period dependent on the amount paid by the user.
  • there may be multiple lists of activation codes stored in the computing system and corresponding lists stored in the device, where each list relates to a particular function or functions of the device and the related predetermined period of time over which that function or those functions can be used.
  • the computing system will return a first system activation code for activating the device or the desired function(s) of the device for a first predetermined period of time. If the user pays a second amount greater than the first amount, the computing system will return a different system activation code for activating the device or the desired function(s) of the device for a second predetermined period of time that is greater than the first predetermined period of time.
  • the device may be rendered activate in perpetuity after a predetermined number of system activation codes have been received through the activation interface and have been matched with respective device activation codes in the device.
  • Activation of the device may rely on the security of the system activation codes.
  • distribution of the device e.g. from wholesaler to retailer to consumer
  • security of the activation codes may be critical.
  • the device activation codes may be programmed into the device at various times, including during manufacture and after manufacture (e.g. along the distribution chain from manufacturer to wholesaler to retailer to consumer).
  • the corresponding system activation codes are also sent to a central server for storage.
  • Each device is then associated with a unique device identifier enabling the future activation request information to be linked to an appropriate group of predetermined system activation codes.
  • the identifier may be a barcode, such as a QR-code, RFID tag or other identifier located on the device.
  • the device After the device has been sent down the distribution chain, it will be purchased by a user. Upon initial purchase, the purchaser details (e.g. user’s bank account details) will be associated with the purchase and can thus be used in replacement of the unique device identifier, or to associate the user with the unique device identifier.
  • any subsequent payments made using the same purchaser details will result in a system activation code being sent to the user associated with those purchaser details (e.g. by SMS).
  • the device can be tracked between parties, along the supply chain.
  • payments made for the device can be distributed to the parties along the supply chain.
  • the code can be scanned before, during or after a payment has been made so as to associate the payment with the particular device.
  • scanning the QR-code or similar may result in automatic debiting of an account for making the payment.
  • a distributor may have an account from which all relevant payments can be taken, where each payment is made simply by scanning the QR-code or similar.
  • the apparatus on which the scan was performed may be network-enabled and in connection with the computing system that sends the system activation codes.
  • scanning the QR-code, for example, and making payment may result in the computing system sending a system activation code (e.g. to the user or device).
  • a distributor may also make payments on the device on behalf of one or more purchasers, and seek payment from the one or more purchasers in compensation.
  • the unique device identifier can be used to distinguish the particular device for which the system activation code is desired from all other devices of a similar nature sold by the same distributor.
  • One advantage of programming the device during manufacture is that there is little, or reduced, need to program the device after fabrication.
  • Alternatively to programming the device with activation codes during manufacture is to program the device downstream (e.g. at point of sale).
  • To program the device downstream would require the device to be capable of being programmed to include device activation codes.
  • the distributor would require the distributor to have a system (e.g. an android telephone) capable of sending device activation codes to the device, preferably in a secure manner.
  • a system e.g. an android telephone
  • a group of predetermined device activation codes will be programmed into the device and also sent to a central server (e.g. the computing system as described above) or alternatively held within the distributors system (e.g. their android telephone).
  • a central server e.g. the computing system as described above
  • distributors system e.g. their android telephone
  • system and device activation codes correspond with each other but are not intended to be exact matches
  • the corresponding group of predetermined system activation codes are sent to the central server.
  • subsequent payments made by the user will result in activation codes being sent from the server.
  • subsequent payments made to the distributor will result in the distributor’s system sending activation codes to the user.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Multimedia (AREA)
  • Technology Law (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Telephone Function (AREA)

Abstract

La présente invention concerne un procédé de commande de l'activation d'un dispositif. Le dispositif présente une mémoire destinée à mémoriser une liste de codes d'activation et une interface d'activation, grâce à laquelle de nouveaux codes d'activation peuvent être saisis pour activer le dispositif. Le procédé comprend la réception d'un premier nouveau code d'activation par le biais de l'interface d'activation. Après réception, le premier nouveau code d'activation est comparé à un ou plusieurs codes d'activation de dispositif parmi un groupe de codes d'activation de dispositif mémorisés dans la mémoire du dispositif. S'il existe une corrélation acceptée (par ex. une correspondance) entre le nouveau code d'activation et un code d'activation de dispositif parmi le ou les codes d'activation de dispositif, le dispositif est activé pendant une période prédéfinie. Après expiration de la période prédéfinie, le dispositif est désactivé, à moins qu'un second nouveau code d'activation ne soit reçu par le biais de l'interface d'activation.
PCT/SG2015/050115 2014-05-14 2015-05-14 Procédé et système destinés à l'opération d'un dispositif sans connexion intégré à faible coût fondé sur la répartition avec une interface utilisateur Ceased WO2015174932A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201461993266P 2014-05-14 2014-05-14
US61/993,266 2014-05-14

Publications (1)

Publication Number Publication Date
WO2015174932A1 true WO2015174932A1 (fr) 2015-11-19

Family

ID=54480326

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SG2015/050115 Ceased WO2015174932A1 (fr) 2014-05-14 2015-05-14 Procédé et système destinés à l'opération d'un dispositif sans connexion intégré à faible coût fondé sur la répartition avec une interface utilisateur

Country Status (1)

Country Link
WO (1) WO2015174932A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN119829153A (zh) * 2024-12-24 2025-04-15 珠海格力智能装备有限公司 一种设备锁机的控制方法、装置及计算机设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999010793A1 (fr) * 1997-08-27 1999-03-04 Sonera Oyj Procedure d'acces a un service dans un systeme de communication de donnees, et systeme de communication de donnees
JP2008071199A (ja) * 2006-09-14 2008-03-27 Oki Electric Ind Co Ltd 取引システム、管理情報処理装置、操作情報処理装置、および処理方法
US20130179281A1 (en) * 2012-01-10 2013-07-11 Mocapay, Inc. System and method for offline stand-in of financial payment transactions
WO2014057822A1 (fr) * 2012-10-12 2014-04-17 シチズンホールディングス株式会社 Système et procédé de limitation d'utilisation

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999010793A1 (fr) * 1997-08-27 1999-03-04 Sonera Oyj Procedure d'acces a un service dans un systeme de communication de donnees, et systeme de communication de donnees
JP2008071199A (ja) * 2006-09-14 2008-03-27 Oki Electric Ind Co Ltd 取引システム、管理情報処理装置、操作情報処理装置、および処理方法
US20130179281A1 (en) * 2012-01-10 2013-07-11 Mocapay, Inc. System and method for offline stand-in of financial payment transactions
WO2014057822A1 (fr) * 2012-10-12 2014-04-17 シチズンホールディングス株式会社 Système et procédé de limitation d'utilisation

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN119829153A (zh) * 2024-12-24 2025-04-15 珠海格力智能装备有限公司 一种设备锁机的控制方法、装置及计算机设备

Similar Documents

Publication Publication Date Title
US10491605B2 (en) Secure interface using non-secure element processors
KR101948277B1 (ko) Ip 화이트리스팅을 갖는 근접 기반의 네트워크 보안
CA2882986C (fr) Procede et systeme pour permettre une emission de billet/des paiements sans contact mobile(s) par l'intermediaire d'une application de telephone mobile
US11288659B2 (en) System and method enabling mobile near-field communication to update display on a payment card
EP2901392A1 (fr) Protection de numéros d'identification personnels pour des applications de paiement mobiles par combinaison avec des composantes aléatoires
WO2015179637A1 (fr) Authentification hors ligne
CN112785309B (zh) 支付码生成、移动支付方法、装置及设备
WO2015095771A1 (fr) Procédés et systèmes de transactions en nuage
EP3167417A1 (fr) Communications hors ligne mains-libres
CN105427106B (zh) 电子现金数据的授权处理方法、支付处理方法及虚拟卡
TW201610858A (zh) 多卡合一裝置、系統和卡資訊載入方法
CN104038924A (zh) 实现资源交换信息处理的方法和系统
EP3424230B1 (fr) Interactions de lecteur médial
US20190362345A1 (en) Transaction Processing Method and Apparatus
CN103370713B (zh) 用于编程移动终端设备芯片的方法
EP3528154B1 (fr) Systèmes et procédés de saisie de code d'authentification au moyen de dispositifs électroniques mobiles
WO2015174932A1 (fr) Procédé et système destinés à l'opération d'un dispositif sans connexion intégré à faible coût fondé sur la répartition avec une interface utilisateur
CN113888789A (zh) 一种基于访客管理系统的数据处理方法及装置
US20160300229A1 (en) Method and Device for Utilizing Apparatuses Through a Pre-paid Credit
CN108574572B (zh) 一种卡片洗卡发行的方法及装置
US11695548B1 (en) Systems and methods for network authentication with a shared secret
KR102448378B1 (ko) 임시키 생성장치 및 방법
KR20250152442A (ko) 디지털 자산 거래 시스템 및 그 운영 방법
AU2021302513A1 (en) Method and system for starting up or managing an offline control device
HK40005085A (en) Encryption key exchange process using access device

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15793492

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15793492

Country of ref document: EP

Kind code of ref document: A1