E-DOC-CTC-20071119-0003 v1.0
43
3| Firmware Upgrade and Configuration Update
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):
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 :env set var=CONF_VERSION
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
possible that a
:system reboot CLI command is present in the downloaded file. However, if an intentional
reboot is required, it is recommended to use the Reboot RPC instead.
7) 200 OK (Empty)
ACSCPE
8 ) Close connection
2) Inform (Event Periodic)
NoMoreRequests = 1
3) 401 Unauthorized (Challenge)
4) Inform (Event Periodic)
NoMoreRequests = 1
with authentication info
5) InformResponse,
Download (CommandKey, Vendor
Configuration File, File URL)
6) DownloadResponse (Status = 1)
22) Close connection
9) HTTP GET
10) 401 Unauthorized (Challenge)
11) HTTP GET
with authentication info
12) 200 OK File Transfer
File Server
1) Schedule configuration update
19) TransferCompleteResponse
14) Inform (Event Transfer Complete,
Value Change, M Download)
15) 401 Unauthorized (Challenge)
16) Inform (Event Transfer Complete,
Value Change, M Download)
with authentication info
18) TransferComplete (CommandKey)
NoMoreRequests = 1
21) 200 OK (Empty)
20) HTTP POST (Empty)
13) Config validation and upgrade
17) InfomResponse
To Next Page
Loading...
