THOMSON TR-069 - STS Files

E-DOC-CTC-20071119-0003 v1.0
44
3| Firmware Upgrade
and Configuration Upda
te
3.2.2 STS Files
Why STS files?
A new file format, an STS (SpeedTouch Script) file, is introduced for two reasons:
 An STS file can be used to make specific configuration changes and still preserve the value of other
configuration parameters. A configuration file (user.ini) contains also authentication parameters, for
example PPP username and password, WLAN SSID and WEP keys... A configuration update using such a
configuration file overrides the original value of these parameters, even if you do not want to change
them.
 A TR-069 file download of an STS file allows the configuration of parameters that are not (yet)
implemented in the supported IGD data model.
STS file format
An STS file is a text file containing CLI commands that can be executed on the Thomson Gateway.
The main differences between a configuration file and an STS file are listed in following table:
Valid STS file
The CPE is able to identify a valid STS file, taking following aspects into account:
 File name extension:
The FileType argument of the Download RPC has value “3 Vendor Configuration File”. This file type is
used for both complete configuration files and STS files. An STS file is identified by its “.STS” file name
extension.
If the file name has no extension or a extension that differs from “.ini” and “.STS”, the TargetFileName
argument of the Download RPC should contain a file name with the correct extension.
 Header line:
An STS file contains a header line with following two space-separated fields:
 TPVERSION=x: this is the tag-parser version. It indicates the CLI syntax version. The tag-parser
version is checked for exact match against the tag-parser environment variable.
If the execution of CLI commands in an STS file results in errors, these errors are not reported
to the ACS. Hence, the use of CWMP RPCs (e.g. the SetParameterValues RPC) is preferred if the
parameters are implemented in the IGD data model.
Configuration file (user.ini) STS file
CLI commands are bundled per block. Flat list of CLI commands.
No well ordered sequence of blocks. Ordered sequence of CLI commands. The CLI
commands are executed in sequence.
Relative commands within a single block, typically
corresponding to a CLI command group.
Absolute commands. This means that commands
include the complete path.
Downloaded files not having the specific “.STS” file name extension are assumed to be
complete configuration files (user.ini).