Software-delivered dynamic persistent data
First Claim
1. A method to provide for rollback to a previous software load on a mobile device, the method comprising the steps of:
- creating, by a processor of the mobile device, non-volatile memory items for a software load;
preventing, by the processor of the mobile device, deletion of any non-volatile memory items once the non-volatile memory items are created;
adding, by the processor of the mobile device, when upgrading to a new software load, a new non-volatile memory item rather than replacing a value in an existing non-volatile memory item when the new non-volatile memory item corresponds to the existing non-volatile memory item; and
mapping, by the processor of the mobile device, the existing non-volatile memory item to the new non-volatile memory item so that requests for a non-volatile memory item are mapped to a correct non-volatile memory item;
wherein the adding step and the preventing step allow utilization of non-volatile memory items and non-volatile memory item values from the previous software load when rolling back to the previous software load.
3 Assignments
0 Petitions
Accused Products
Abstract
A method and apparatus for dynamically managing non-volatile memory items in a wireless device, the method comprising the steps of: checking the non-volatile memory items for a unique identifier item; if the unique identifier item exists, comparing an identifier stored within the unique identifier item with a software identifier located in software on the wireless device; and if the unique identifier item does not exist or if the identifier is different from the software identifier, performing the steps of: updating the non-volatile memory items; and writing the software identifier to the unique identifier item. The method may further include a rollback scheme for previous software versions.
-
Citations
12 Claims
-
1. A method to provide for rollback to a previous software load on a mobile device, the method comprising the steps of:
-
creating, by a processor of the mobile device, non-volatile memory items for a software load; preventing, by the processor of the mobile device, deletion of any non-volatile memory items once the non-volatile memory items are created; adding, by the processor of the mobile device, when upgrading to a new software load, a new non-volatile memory item rather than replacing a value in an existing non-volatile memory item when the new non-volatile memory item corresponds to the existing non-volatile memory item; and mapping, by the processor of the mobile device, the existing non-volatile memory item to the new non-volatile memory item so that requests for a non-volatile memory item are mapped to a correct non-volatile memory item; wherein the adding step and the preventing step allow utilization of non-volatile memory items and non-volatile memory item values from the previous software load when rolling back to the previous software load. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A wireless communications device comprising:
-
a receiver configured to receive signals; a transmitter configured to transmit signals; a digital signal processor configured to process signals to be transmitted on the transmitter and received on the receiver; a processor configured to communicate with the digital signal processor; a non-volatile memory having program storages and non-volatile memory items, wherein the non-volatile memory is configured to communicate with the processor; and input and output subsystems configured to interact with the processor, wherein the processor includes; means for creating non-volatile memory items for a software load; means for preventing deletion of any non-volatile memory items once the non-volatile memory items are created; means for adding, when upgrading to a new software load, a new non-volatile memory item rather than replacing a value in an existing non-volatile memory item when the new non-volatile memory item corresponds to the existing non-volatile memory item; and a map adapted to map the existing non-volatile memory item to the new volatile non-volatile memory item so that requests for a non-volatile memory item are mapped to a correct non-volatile memory item; wherein the means for adding and the means for preventing are configured to allow utilization of non-volatile memory items and non-volatile memory item values from a previous software load when rolling back to the previous software load. - View Dependent Claims (8, 9, 10, 11, 12)
-
Specification