E-DOC-CTC-20071119-0003 v1.0
33
3|
Firmware Upgrade and Configuration Update
3.1.1
General Firmware Upgrade Mechanism
Why firmware upgrade?
New firmware images are capable of loading older configuration files for backwards compatibility. However,
older firmware images cannot be guaranteed to properly load new configuration files of more recent
firmware versions. The main reason is that new configuration files can contain new commands, which were
introduced for the support of new features.
Firmware images
For a
remote
firmware upgrade, one of the following file types can be used:
*.os
(in case of RTEMS)
*.rbi
(in case of GoLinux)
Description
This use case mainly covers the automatic remote upgrade of a firmware image. At any point in time, the
ACS can trigger the CPE to upgrade its firmware image. The ACS sends an asynchronous connection request
triggering the CPE to establish a transaction session to receive a Download method to upgrade its firmware.
ACS
: the ACS is only responsible for:
Sending the Download RPC.
Retrieving the TransferComplete RPC.
CPE
: the actions taken by the CPE itself depend on the firmware upgrade mechanism, which is
not
defined by TR-069. This is indicated by the “CPE firmware upgrade process” in following illustration. The
different firmware upgrade mechanisms are described in different subsections.
For a
local
firmware upgrade,
*.bli
files are used.
Содержание TR-069
Страница 2: ......
Страница 3: ...Thomson Gateway TR 069 Configuration Guide R7 4 and higher ...
Страница 18: ...E DOC CTC 20071119 0003 v1 0 12 1 Introduction ...
Страница 36: ...E DOC CTC 20071119 0003 v1 0 30 2 Configuring CWMP on the Thomson Gateway ...
Страница 74: ...E DOC CTC 20071119 0003 v1 0 68 5 WAN Connections ...
Страница 106: ...E DOC CTC 20071119 0003 v1 0 100 6 Service Provisioning ...
Страница 109: ......