THOMSON TR-069 Configuration Manual page 49

3|
Message flow
The message flow between the CPE and ACS is identical for configuration files and script files.
Following illustration shows the message flow for the "Configuration Update" use case (we assume that the
MaxEnvelopes argument of the first Inform RPC has value 2):
File Server
9) HTTP GET
10) 401 Unauthorized (Challenge)
11) HTTP GET
with authentication info
12) 200 OK File Transfer
13) Config validation and upgrade
Configuration versions
It is the responsibility of the configuration file editors to implement configuration version management. For
example, the downloaded file includes the CLI command
value=1.1.1.
The ACS can retrieve the "InternetGatewayDevice.DeviceInfo.VendorConfigFile.{i}.Version" parameter from
the IGD data model to learn which configuration version is applied on the CPE.
No reboot
No intentional reboot is done after downloading and loading a configuration file or script file. Although, it is
:system reboot
possible that a
reboot is required, it is recommended to use the Reboot RPC instead.
E-DOC-CTC-20071119-0003 v1.0
Firmware Upgrade and Configuration Update
CPE
3) 401 Unauthorized (Challenge)
Download
6) DownloadResponse (Status = 1)
8 ) Close connection
14) Inform (Event Transfer Complete,
15) 401 Unauthorized (Challenge)
16) Inform (Event Transfer Complete,
18) TransferComplete
19) TransferCompleteResponse
22) Close connection
CLI command is present in the downloaded file. However, if an intentional
ACS
2) Inform (Event Periodic)
NoMoreRequests = 1
4) Inform (Event Periodic)
NoMoreRequests = 1
with authentication info
5) InformResponse,
(CommandKey, Vendor
Configuration File, File URL)
7) 200 OK (Empty)
Value Change, M Download)
Value Change, M Download)
with authentication info
17) InfomResponse
(CommandKey)
NoMoreRequests = 1
20) HTTP POST (Empty)
21) 200 OK (Empty)
:env set var=CONF_VERSION
1) Schedule configuration update
43