Firmware Server and Configuration File Server
24
If the firmware version is 1.0.3.73 or later than 1.0.3.73, the firmware BASIC NAME as follows:
fw924.rom
Service provider can use “hl_” as prefix, and “_1.0.3.73” as postfix, the above files will be changed to:
hl_ fw924.rom _1.0.3.73
In this way, all of the firmware with different version could be stored in one single directory, and they
could be differentiated by using prefix or postfix, i.e., all files with a postfix of “_1.0.3.73” belong to the
firmware version 1.0.3.73.
Same rule applies to configur
ation files, i.e., for configuration file named “cfg001fc1001708”, there could
be 3 versions: “hl_ cfg001fc1001708_cfg001”, “hl_ cfg001fc1001708_cfg002”, and “hl_
cfg001fc1001708_cfg003”. The BASIC NAME of the configuration file is “cfg001fc1001708”, but there
are 3 different versions, the one that will be accepted is the one with matching prefix and postfix specified
in the current configuration.
11. Firmware Server and Configuration File Server
Beside the Prefix and Postfix for firmware and configuration files, different server paths for firmware
upgrade or Configuration File Server can be specified in different FQDN, i.e.:
The parameters are P192 and P237 for Firmware and Config Server
12. Manage Firmware and Download Configuration File
When parameter P194 (Auto Upgrade) is set to 1, Service Provider can use P193 (Auto Check Interval) to
have the devices periodically check with either Firmware Server or Config Server, whenever they are
defined. This allows the device periodically check if there are any new changes need to be taken on a
scheduled time. By defining different intervals in P193 for different devices, Service Provider can
distribute the Firmware or Configuration File download schedule to reduce the Firmware or Provisioning
Server load at any given time.
