Firmware management and updates - Data plane Control Management

Data plane Control Management

8.6.7 Firmware management and updates

N°

Requirement

R214.

The HG MUST support software and firmware upgrades from the RMS. The main components to be updated are:

• Operating system and gateway firmware. This includes complete firmware updates or upgradeable modules.

• Module additions or removals, in the case of a modular gateway. For example, when a new hardware module is added or removed, the drivers and associated services enablers are included.

DSL-Forum TR-069 provides mechanisms for firmware upgrades. However, some additional 4

mechanisms and specifications are needed. These add-ons are described in the following sections. 5

8.6.7.1 General 6

N°

Requirement

R215.

TR-069 Appendix A [1] MUST be supported for software management and updates. This applies to the firmware of the HG.

This requirement emphasizes current TR-069 functionality

R216.

It MUST be possible to support software modules that can be upgraded remotely. Therefore, the TR-098 data model should be extended with the information included in the following table. The table describes the parameters that MUST be manageable by the RMS for remote software module management. The names of the parameters are descriptive and left to the DSL Forum to be further defined.

Argument Description

Module.{i}. Object for installed module description.

Identifier Description / Identification of the modules, which MUST be consistent with the list of modules attribute. SoftwareVersion A string identifying the software module version currently installed in the HG.

To allow version comparisons, this element SHOULD be in the form of dot-delimited integers, where each successive integer represents a more minor category of variation. For example, a version number can be 3.0.21 where the components mean: Major.Minor.Build.

Home Gateway Technical Requirements: Residential Profile

Argument Description

EnabledOptions Comma-separated list of the option names of each. Option that is currently enabled in the HG. The mechanism is identical to the one defined for CPE firmware in the DSL Forum TR-069.

N°

Requirement

R217.

If software modules are supported, the TR-069 firmware upgrading mechanism MUST also be fully supported for software management and updates: The “DOWNLOAD” procedure will include a “FileType” that specifies the vendor and the module upgrade.

S 2 8.6.7.2 Firmware upgrades 3

N°

Requirement

R218. The HG MUST support RMS initiated firmware upgrades according to TR-069.

This requirement emphasizes current TR-069 functionality.

R219. It MUST be possible to read the current HG firmware version via CWMP.

This requirement emphasizes current TR-069 functionality.

R220. The HG SHOULD control the firmware integrity (for example MD5 checksum) and

authenticate the signature prior to the flashing procedure.

R221.

Normal operation (last good state of network provisioning and configuration) of the HG MUST be re-established in terms of provisioning and configuration when the HG itself comes back after a power failure.

R222.

The HG MUST provide a mechanism that guarantees that the basic functionality and connectivity to the RMS can be recovered in the case of a failure of a software upgrade or installation of new software.

R223.

The HG MUST provide a bootloader that works independently of the rest of the software. For recovery the following mechanisms are possible (one or the other):

• There is always (but maybe limited) default software together with a default configuration stored on the HG. If software upgrade fails (e.g. the HG is not booting anymore, incompatibilities with hardware are found, mismatch between software and configuration, etc.), the HG automatically loads his default software and configuration. Active notification to the RMS is necessary.

• The HG has enough resources to always keep the latest running software and configuration. If a software upgrade fails the HG automatically reboots with the last good software and configuration. Notification to the RMS is necessary.

R224.

When upgrading the safe boot loader, the old version MUST NOT be overwritten but maintained in the HG memory until the integrity check of the new version has been successfully completed.

Home Gateway Technical Requirements: Residential Profile

N°

Requirement

R225. The HG MUST have a factory-default configuration. S

R226. The HG factory-default configuration MUST work with any software/firmware and

hardware and in particular MUST be able to establish connectivity to the RMS.

R227.

The HG MUST be able to be reset to the factory-default either by the LM Remote UI or by the reset button that SHOULD be present.

There MUST be two levels for the reset: • Reset to factory default configuration

• Reset to last running software and configuration

Note: this requirement is for the exceptional case when the HG is not accessible from the RMS.

R228.

The HG MUST be able to provide the current configuration parameters to the RMS e.g. to allow the configuration to be periodically stored in a remote database.

Note: This can be implemented using the TR-069 Upload method and the configuration file will be coded in a vendor specific format.

R229.

The HG MUST provide a function that allows the restoration of the configuration parameters stored in the RMS. Such events are RMS initiated.

This can be implemented using the TR-069 Download method, using the “FileType” attribute to “3 Vendor Configuration File”.

8.6.7.4 Application Layer Gateway Management 3

N°

Requirement

R230. The ALG list (see Section 8.8.1) stored in the HG MUST be remotely accessible by the

RMS.

R231.

The HG MUST allow the RMS to enable or disable the ALGs. These changes can be made either by the RMS or by the user through the local management interface (some restrictions may apply in the latter case).

R232.

The HG MUST support a data model object required for the ALG management as described in the table below. The table describes the parameters that MUST be manageable by the RMS for remote ALG management. The names of the parameters are descriptive and left to DSL Forum to be further defined.

4 5

Name Description

ALG ALG table object

Home Gateway Technical Requirements: Residential Profile

Name Description

ALG.Info.{i} Each instance contains objects associated a given ALG

Enable Enables or disables this ALG

Status Indicates the status of the ALG entry. Enumeration of:

“Enabled” “Disabled”

Name Name of the ALG

Version A string identifying the ALG version currently used in the HG

Description A description of the ALG

8.6.8 Multi-service provider management

In document Home Gateway Technical Requirements: Residential Profile (Page 79-82)