E-DOC-CTC-20071119-0003 v1.0
34
3| Firmware Upgrade
and Configuration Upda
te
Message flow
The message flow between the CPE and ACS is identical for all firmware upgrade mechanisms.
Following illustration shows the message flow for the “Firmware Upgrade” use case (we assume that the
MaxEnvelopes argument of the first Inform RPC has value 1):
ACSCPE
1) Schedule firmware upgrade
6) Close connection
15) Close connection
5) 200 OK
2) HTTP GET to
ConnectionRequestURL
3) 401 Unauthorized (Challenge)
4) HTTP GET to
ConnectionRequestURL
with authentication info
7) Inform (Event Connection Request)
8) 401 Unauthorized (Challenge)
9) Inform (Event Connection Request)
with authentication info
10) InformResponse
HoldRequests = 1
13) DownloadResponse (Status = 1)
21 ) TransferCompleteResponse
16) Inform (Event Transfer Complete,
Boot, Value Change, M Download)
17) 401 Unauthorized (Challenge)
18) Inform (Event Transfer Complete,
Boot, Value Change, M Download)
with authentication info
19) InformResponse
20) TransferComplete (CommandKey)
23) 200 OK (Empty)
22) HTTP POST (Empty)
24) Close connection
File Server
14) 200 OK (Empty)
CPE Firmware Upgrade Process
12) Download (CommandKey,
Firmware Upgrade Image, File URL)
HoldRequests = 1
11) HTTP POST (Empty)
To Next Page
Loading...
