THOMSON TR-069, Configuration Manual

Page: 52 / 110

E-DOC-CTC-20071119-0003 v1.0
46
3| Firmware Upgrade and Configuration Update
3.2.3 Embedded STS (eSTS) Files
Why eSTS files?
An eSTS file has exactly the same file format as an STS file.
By embedding this STS file in a firmware image, the STS file is loaded once after a firmware upgrade. The
use of an explicit STS file download is avoided. This way, a firmware upgrade can be considered as a single
stage process without requiring extra download steps for completing successfully. This makes the upgrade
process more robust, as an explicit STS file download requires a longer time and is more vulnerable to
failures.
How to embed STS files?
The process of embedding an STS file in a software build is executed by Thomson during customization,
prior to delivery.
The use of eSTS files is customizable using the customization wizard and does not require a new software
build:
1 A fixed file name for the eSTS file is used: upgrade.sts .
2 The eSTS file must be embedded in the folder “archive/active/” of the software build.
Flag
An eSTS file is loaded once and only once after the firmware upgrade. To this end a flag is used:
After loading the upgrade.sts file, a flag is written to Flash to indicate that the file was loaded.
A factory reset does not delete the flag.
When the same firmware image is loaded twice, the eSTS file is loaded only once (the first time).
On a firmware upgrade to a new firmware image, the flag is deleted.
Firmware upgrade mechanism with eSTS file
When an eSTS file is embedded in the folder “archive/active/”, the firmware upgrade process is followed by
following steps:
1 The old user.ini file is loaded. This file preserved the user configuration and previous TR-69 configuration.
If no user.ini file exists, the factory defaults are loaded.
2 The upgrade.sts file is loaded if an upgrade.sts file exists and if the flag is not present in Flash.
This corresponds to CLI command
:config load filename=upgrade.sts
.
3 The flag is written to Flash.
4 The configuration is saved (by default), creating a new user.ini file.
This corresponds to CLI command
:saveall
.