Back to results
US 8,527,613 B2Granted
Provisioned firmware updates using object identifiers
AssigneeAssa Abloy AB
InventorsMichael William Malone, Yoong-Goog Cho, Thad Smith, Ryan Milbrandt
Life of this patent
Estimating the term…
Abstract
Methods, devices, and systems are provided for remotely updating provisioning data in devices or a population of devices. An update message is generated that includes an Object Identifier (OID) that uniquely identifies eligible devices or components for the provisioning data update. If an eligible device receives the update message, then the new provisioning data is loaded on the device, thereby replacing the old provisioning data on the device.
Claims32
A method, comprising:
- receiving, from a requestor, an update request;
- generating an update file that includes provisioning data as well as an object identifier which identifies an object authorized to receive the provisioning data, wherein the object identifier comprises at least five bytes, wherein a first of the at least five bytes uniquely defines an entity associated with the object authorized to receive the provisioning data update, wherein a second of the at least five bytes uniquely defines a subclass of device associated with the entity, wherein a third of the at least five bytes uniquely defines a platform associated with the device, wherein a fourth of the at least five bytes uniquely defines a behavior associated with the platform, and wherein a fifth of the at least five bytes uniquely defines a version associated with the behavior;
- and
- transmitting the update file to the requestor.
1 more element
A method, comprising:
- receiving an update file;
- extracting an object identifier from the update file, wherein the object identifier comprises at least five bytes, wherein a first of the at least five bytes uniquely defines an entity associated with the object authorized to receive the provisioning data update, wherein a second of the at least five bytes uniquely defines a subclass of device associated with the entity, wherein a third of the at least five bytes uniquely defines a platform associated with the device, wherein a fourth of the at least five bytes uniquely defines a behavior associated with the platform, and wherein a fifth of the at least five bytes uniquely defines a version associated with the behavior;
- and
- determining whether an object is allowed to receive a provisioning data update based on the object identifier.
1 more element
An electronic device, comprising:
- memory that stores at least one version of provisioning data and an object identifier, wherein the object identifier is used to determine whether the at least one version of provisioning data can be replaced with a new version of provisioning data based on a comparison of the object identifier to an object identifier associated with the new version of provisioning data, wherein the object identifier further comprises at least five bytes, wherein a first of the at least five bytes uniquely defines an entity associated with the object authorized to receive the provisioning data update, wherein a second of the at least five bytes uniquely defines a subclass of device associated with the entity, wherein a third of the at least five bytes uniquely defines a platform associated with the device, wherein a fourth of the at least five bytes uniquely defines a behavior associated with the platform, and wherein a fifth of the at least five bytes uniquely defines a version associated with the behavior.
A non-transitory computer-readable medium, comprising:
- provisioning data;
- and
- an object identifier used to determine whether the provisioning data is allowed to be boot loaded, wherein the object identifier further comprises at least five bytes, wherein a first of the at least five bytes uniquely defines an entity associated with the object authorized to receive the provisioning data update, wherein a second of the at least five bytes uniquely defines a subclass of device associated with the entity, wherein a third of the at least five bytes uniquely defines a platform associated with the device, wherein a fourth of the at least five bytes uniquely defines a behavior associated with the platform, and wherein a fifth of the at least five bytes uniquely defines a version associated with the behavior.
Dependencies are inferred from the claim text.