|
ATP069 Validation Tool
dBm069-ATP069 is the entry level tool of the dBm069 family. It has been designed with the aim to perform a validation test plan running the tests proposed by the BBF ATP-069. This is the minimum TR-069 requirements that a CPE should PASS to be deployed by an Telecom Operator. No matter if dealing with routers (fiber, VDSL, DSL), or any LAN device.
|
dBm069-ATP069 is intended for all the players who manufacture, sell or deploy CPEs:
- Modems and routers manufacturers as well as OEM suppliers and integrators
- Tier 1 Telecom Operators just as a first step in their validation proccess
- Tier 2 and Tier 3 Telecom Operators should also have it for mandatory use before deploying a single CPE unit
Are you aware about the basic TR-069 issues that can happen and how they can affect your level of service?
An RPC method not implemented correctly can provoque failures such as:
- not allowing remote configuration of the CPE
- mistakes in the remote configuration (like performing partial configurations)
- not allowing the correct update of new firmware versions
Here are a couple of examples that describe basic typical issues related with the TR-069 behavior of a CPE:
dBm069-ATP069 provides its own internal ACS completely TR-069 compliant. Therefore it offers the possibility to check the correct implementation of TR-069 in a CPE without the need of accessing a commercial ACS.
Testing a CPE with dBm-069-ATP069 does not guarantee that the CPE will also pass a final Telecom Operator validation, since although it checks the correct implementation of the TR-069 RPC methods following BBF ATP-069, it does not perform any functional test of the device when it is configured through TR-069, neither validates the Vendor Specific parameters developed by the CPE vendor or implemented by the Operator.
Testing a CPE with dBm-069-ATP069 does not guarantee that the CPE will also pass a final Telecom Operator validation, since although it checks the correct implementation of the TR-069 RPC methods following BBF ATP-069, it does not perform any functional test of the device when it is configured through TR-069, neither validates the Vendor Specific parameters developed by the CPE vendor or implemented by the Operator.
Testing Scenario of dBm069-ATP069
Do you need a complete TR-069 testing solution able to run customized Test Plans according to the specific requests of CPE functionalities (e.g. an ADSL modem, fiber router, STB, video bridge…)? dBm069 can be configured to run a specific Test Plan based on any of BBF data models.
dBm069-ATP069 Delivery
dBm069-ATP069 includes all the elements necesary to make a CPE validation based in ATP069. Here are the items included:
* dBm069-ATP069 can not run any other library out of dBm069-ATP069-Lib, but if you wish to execute other test cases, dBm069-ATP069 can be upgraded to dBm069-Engine when the need arises.
- dBm069-Main Engine (*) - This is the full engine needed to run test cases but limited to work with dBm069-ATP069-Lib
- dBm069-ACS - Propietary full BBF compliant dBm ACS
- dBm069-ATP069-Lib - This is the library that contains the test cases to run for ATP069 validation
* dBm069-ATP069 can not run any other library out of dBm069-ATP069-Lib, but if you wish to execute other test cases, dBm069-ATP069 can be upgraded to dBm069-Engine when the need arises.
Scope of dBm069-ATP069-Lib
This library includes test cases that check if the CPE can communicate properly with the ACS following the protocol requirements, as well as that all mandatory RPC methods are correctly implemented in the CPE.
Here is the list of test cases included in dBm069-ATP069-Lib:
Here is the list of test cases included in dBm069-ATP069-Lib:
|
Group
ACS Connection Authentication Connection Request Diagnostics HTTP HTTP Inform PeriodicInform Manual Reboot RPCs RPCs RPCs RPCs RPCs RPCs RPCs RPCs RPCs RPCs RPCs RPCs RPCs Disable TR069 Session SOAP |
Subgroup
Headers Redirection AddObject DeleteObject Download FactoryReset GetRPCMethods GetParameterAttributes GetParameterNames GetParameterValues Reboot ScheduleInform SetParameterAttributes SetParameterValues Upload |
Nº of test cases
4 3 2 1 1 6 4 4 1 2 2 5 1 1 6 10 10 1 1 8 2 4 1 4 3 |
