DOCSIS TLV43

This paper is trying to help you know the work-flow of getting DOCSIS TLV43 config file and downloading the gateway config file according to the DOCSIS TLV43's configuration parameters.The high level architecture is as following fig1.

Fig1.

ARMis responsible for DOCSIS online and ATOM (IntelPUMA 7) takes responsibility of running gateway. The aim of the design is usedto make full use of these two CPUs, which is more efficient than running alltasks in one CPU.

NOTE: After ARM DOCSIS online,  use the ncp( or use other RPC) command to transfer the Docsis.cfg which contains the configuration parameters of TLV43 to ATOM.

the work flow of ATOM:

1.      Initialize system.db in ATOM which contains some parameters stored in NVRAM.

Command: syscfg unset PARAMETER_NAME

2.      Pad Docsis.cfg, and remove the useless part that you do not need them, like the head & end tag.

3.      Parse the Docsis.cfg to get the TLV43 configuration parameters.

4.      When parsing the Docsis.cfg, we can save the parameters according to it in ATOM.

Command: syscfg set PARAMETER_NAME PARAMETER_VALUE

5.      Find the time point when ATOM online (There is always having the signal indicate the ATOM online), which is because the ATOM’s ability to access WAN after ARM’s DOCSIS online and download config file depends on it.(When ATOM can access WAN it will send a separate signal to ARM.)

Command: syscfg get PARAMETER_NAME

6.      Download the gateway.cfg according to the parameters stored in NVRAM and set by command syscfg. When download the gateway.cfg, it can refer to thePARAMETER_NAME and PARAMETER_VALUE.

For example:

PARAMETER_NAME	PARAMETER_VALUE
TFTP SERVER	192.168.0.10
FILE_NAME	gateway.cfg
…	…

 

7.      After getting the gateway.cfg file, judge whether to restore by comparing the latest downloaded file’s name (or usingother tags) to the previous name saved in NVRAM.
*Different: 1. restore (which is a command used to reconfigure the parameters of gateway.) 
                     2. Then reboot.
*same: skip.