METHODS AND APPARATUS TO CHANGE A FEATURE SET ON DATA COLLECTION DEVICES

• US 20090044003A1
• Filed: 08/09/2007
• Published: 02/12/2009
• Est. Priority Date: 08/09/2007
• Status: Active Grant

• Current Assignee: Hand Held Products Incorporated (Honeywell International Inc.)
• Original Assignee: Hand Held Products Incorporated (Honeywell International Inc.)
• Inventors: Stewart, James W., Berthiaume, Guy H., Havens, William H., Wang, Ynjiun P., Yeakley, Daniel D., Caballero, Aldo M., Koziol, Thomas J., Cairns, James A.
• Granted Patent: US 8,635,309 B2
• Time in Patent Office: Days
• US Class Current: 713/100
• CPC Class Codes: G06F 16/17 Details of further file system functions
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: G06F 16/9554 by using bar codes
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities

Abstract

Methods and apparatus for modifying the feature set of data collection devices are disclosed. Requests are receiving at a computer system different from the data collection device for a new configuration of the data collection device, the request including an identifier for the data collection device, identification of one or more features, and for each identified feature, an indication to modify the operation of a feature. The identifier may comprise an identifier that is unique for a particular data collection device or an indication of a group of devices. e.g. a model number. Prior to authorizing the new configuration, a determination may be made as to whether the identified data collection device(s) are suitable for the new configuration by consulting a configuration database. To implement the new configuration, an encoded authorization file is generated based on the requested configuration and the identifier of the data collection device(s). The encoded authorization file is transmitted to one or more data collection devices. Each data collection device that receives an encoded authorization file attempts to decode of the license using its identifier(s). If the authorization file is successfully decoded, a license key on that device is updated to implement the new configuration.

Claims

1. A method for changing a configuration of a remote data collection device, the method comprising:

maintaining a first data structure on the remote data collection device that stores values describing the operation of features of the data collection;

receiving at a computer system different from the remote data collection device a request for a new configuration of the data collection device, the request including an identifier for the data collection device, identification of one or more features, and for each identified feature, an indication to modify the operation of the feature;

using the computer system, generating a second data structure to update the first data structure in accordance with the request;

transmitting the second data structure to the data collection device; and

updating the first data structure based on the second data structure.

2. A method, as set forth in claim 1, wherein the identifier is a group identifier.

3. A method, as set forth in claim 2, wherein the group identifier is a model number.

4. A method, as set forth in claim 1, further comprising:

maintaining a record of the current configuration of the data collection device;

maintaining a database indicating suitable configurations of data collection devices;

when a request is received, identifying whether the data collection device is suitable for the new configuration; and

wherein the steps of generating, transmitting and updating are contingent upon the data collection device being suitable for the new configuration.

5. A method, as set forth in claim 1, further comprising:

wherein the steps of generating, transmitting and updating are contingent upon the receipt of payment.

6. A method, as set forth in claim 4, further comprising:

wherein the steps of generating, transmitting and updating are contingent upon the receipt of payment.

7. A method, as set forth in claim 1, wherein the second data structure is encrypted, and wherein the step of updating is contingent upon successfully decrypting the encrypted data structure.

8. A method, as set forth in claim 7, wherein the second data structure is encrypted using the identifier of the data collection device.

9. A method, as set forth in claim 7, wherein the second data structure is encrypted using a symmetric key.

10. A method, as set forth in claim 7, wherein the second data structure is encrypted in accordance with a PKI methodology.

11. A method, as set forth in claim 7, wherein the second data structure is encrypted using an asymmetric key.

12. A method, as set forth in claim 1, wherein the step of transmitting the second data structure to the data collection device comprises generating a text message bearing the second data structure and transmitting the text message to the data collection device using a cellular network.

13. A method, as set forth in claim 1, wherein the step of transmitting the second data structure to the data collection device comprises generating a dataform bearing the second data structure and scanning the dataform with the data collection device.

14. A method, as set forth in claim 1, wherein the step of transmitting the second data structure to the data collection device comprises transmitting the second data structure to an intermediate device and subsequently transmitting the second data structure to the data collection device.

15. A method, as set forth in claim 1, wherein the step of transmitting the second data structure to the data collection device comprises transmitting a location from which the second data structure may be downloaded.

16. A method, as set forth in claim 1, wherein the second data structure further includes files necessary to implement the requested changes.

17. A method, as set forth in claim 1, further comprising:

transmitting to the data collection device files necessary to enable features enabled by the second data structure.

18. A method, as set forth in claim 17, wherein the files are encrypted.

19. A method, as set forth in claim 1, further comprising:

transmitting to the data collection device a location to download files necessary to enable features enabled by the second data structure.

20. A method, as set forth in claim 1, wherein the identifier comprises a serial number.

21. A method, as set forth in claim 1, wherein the identifier comprises a SKU.

22. A method, as set forth in claim 1, wherein the identifier comprises a model number.

23. A method, as set forth in claim 1, wherein the values in the first data structure include an indication to enable or disable the operation of a feature.

24. A method, as set forth in claim 1 wherein the values in the first data structure include an indication to enable the operation of a feature for a period of time.

25. A method, as set forth in claim 1, wherein the values in the first data structure include an indication to enable the operation of a feature for a predetermined number of operations.

26. A method, as set forth in claim 1, wherein the values in the first data structure include an indication to enable the operation of a feature and at least one parameter for the operation thereof.

27. A method for changing a configuration of a remote data collection device, the method comprising:

receiving at a computer system different from the remote data collection device a request for software to be installed on the data collection device, the request including an identifier for the data collection device;

using the computer system, encrypting the software with the identifier for the data collection device;

transmitting the encrypted software to a data collection device;

receiving encrypted software at a data collection device;

attempting to decrypt to the received encrypted software on the data collection device using an identifier of the data collection device; and

if the encrypted software is successfully decrypted installing the software on the data collection device.

28. A system comprising:

a plurality of data collection devices, each data collection device operable in accordance with a plurality of features and including a memory with a first data structure that stores values describing the operation of features of the data collection, each data collection device further including an update program to update the first data structure based on a second data structure;

a customer interface system that receives a request to change the configuration of a data collection device, the request including an identifier of the data collection device, identification of one or more features, and for each identified feature an indication to modify the operation of the feature; and

a manager that, responsive to the request received by the customer interface, generates a second data structure to update the first data structure in accordance with the request, and facilitates the transmission of the second data structure to the identified data collection device.

29. A system, as set forth in claim 28, wherein the identifier is a group identifier.

30. A system, as set forth in claim 29, wherein the group identifier is a model number.

31. A system, as set forth in claim 28, further comprising:

a database having records indicating a current configuration of the data collection device;

a database indicating suitable configurations for types of data collection devices;

a process, in communication with the customer interface, for determining whether the identified data collection device is suitable for the new configuration; and

wherein the manager only generates the second data structure if the process determines that the data collection device is suitable for the new configuration.

32. A system, as set forth in claim 28, further comprising:

wherein the manager only generates the second data structure when payment conditions have been satisfied.

33. A system, as set forth in claim 28, wherein the manager encrypts the second data structure;

and

wherein the update program only updates upon successfully decrypting the second data structure.

34. A system, as set forth in claim 33, wherein the second data structure is encrypted using the identifier of the data collection device.

35. A system, as set forth in claim 33, wherein the second data structure is encrypted using a symmetric key.

36. A system, as set forth in claim 33, wherein the second data structure is encrypted in accordance with a PKI methodology.

37. A system, as set forth in claim 33, wherein the second data structure is encrypted using an asymmetric key.

38. A system, as set forth in claim 28, wherein the second data structure is transmitted to the data collection device as a text message using a cellular network.

39. A system, as set forth in claim 28, wherein the second data structure is transmitted to the data collection device by generating a dataform bearing the second data structure and scanning the dataform with the data collection device.

40. A system, as set forth in claim 28, wherein the second data structure is transmitted to the data collection device via an intermediate device.

41. A system, as set forth in claim 28, further comprising:

a data storage device for storing the second data structure and from which the second data structure may be downloaded.

42. A system, as set forth in claim 28, wherein the second data structure further includes files necessary to implement the requested changes.

43. A system, as set forth in claim 28, wherein the second data structure includes files necessary to enable features enabled by the second data structure.

44. A system, as set forth in claim 43, wherein the files are encrypted.

45. A system, as set forth in claim 28, further comprising:

a data storage device for storing files necessary to enable features enabled by the second data structure.

46. A system, as set forth in claim 28, wherein the identifier comprises a serial number.

47. A system, as set forth in claim 28, wherein the identifier comprises a SKU.

48. A system, as set forth in claim 28, wherein the identifier comprises a model number.

49. A system, as set forth in claim 28, wherein the values in the first data structure include an indication to enable or disable the operation of a feature.

50. A system, as set forth in claim 28, wherein the memory is a secondary non-volitle memory physically distinct from a main memory of the data collection device.

51. A system, as set forth in claim 28, wherein the memory is an EEPROM.

52. A system, as set forth in claim 51 wherein the EEPROM is physically distinct from a main memory of the data collection device.

53. A system, as set forth in claim 28 wherein the values in the first data structure include an indication to enable the operation of a feature for a period of time.

54. A system, as set forth in claim 28, wherein the values in the first data structure include an indication to enable the operation of a feature for a predetermined number of operations.

55. A system, as set forth in claim 28, wherein the values in the first data structure include an indication to enable the operation of a feature and at least one parameter for the operation thereof.

56. A method of updating a data collection device comprising:

generating a barcode indicating a server and the name of at least one file to download;

scanning the barcode with the portable data terminal;

initiating communication between the server identified in the bar code and the data collection device; and

transferring the named at least one file from the server to the data collection device.

57. A method of updating, as set forth in claim 57, wherein the barcode further includes an indication of when to initiate communication and wherein the step of initiating the communication is performed on or near the indicated time.

58. A method of updating, as set forth in claim 57, wherein the barcode further includes an authorization string for updating a license key on the data collection device.

59. A method of updating, as set forth in claim 57, wherein the barcode further includes an indication of a backup server, and wherein the step of initiating communication further comprises initiating communication with the backup server if communication with the server fails.

60. A method of updating, as set forth in claim 57, further comprising displaying the bar code on an electronic display in proximity of the data collection device.