dBm069-Engine is the platform which runs the whole TR-069 testing process
dBm069- Engine provides all the necesary gadgets to automatically run a Test Plan to validate a CPE in relation to the TR-069 protocol. dBm069-Engine needs to have a Library to run the test cases included in that Library. We provide several Libraries to test devices acording to different TR-069 data models. If you only need to test your CPE acording to BBF ATP069, we have available a low cost solution: dBm069-ATP069, that you can upgrade in the future if your needs change.
dBm069-Engine main functionalities are:
|
Run a manual test step by step
Although the main purpose of dBm069-Engine is to automatically run a Validation Test Plan, sometimes it is necessary to execute a test case step by step to better understand the CPE behavior. This mode is also used for new staff trainning purposes. |
|
|
Automatic execution of a Test Plan
Test Plan execution to validate the TR-069 behavior of a CPE is the main purpose of dBm069 Engine. All information about the execution of the test case is available in real time during its execution step by step: Test case definition; results; ACS logs, failures detected… and everything is shown in a Windows view to better help the user to understand what is happening during execution. |
|
|
Generate/analyze traffic
Traffic generation allows performing functional tests to the CPE. Wired ports, WiFi ports, and many connectivity tasks can be performed sending and receiving real traffic. |
|
|
Use its internal STUN server
The STUN Server provided in dBm069 allows to work with LAN devices connected to the CPE under test. |
|
|
Use its internal HTTP & FTP server
HTTP & FTP servers are used to upload and download files during testing, as for example to update the internal CPE SW. This operation will be of maximal importance to guarrantee remote CPE updates. |
|
|
PASS / FAIL decission
dBm069 will decide if a Test Case result is PASS of FAIL following the Test Case definition. All the sub steps related to a Test Case are analyzed separately. The whole test case will FAIL if a single step failed providing the user with whole visibility of the nature of the failure. |
|
|
Capture TR-069 traffic
By capturing all the messages sent in both ways from ACS to CPE and CPE to ACS, the user can investigate the FAILED cases that have no obvious interpretation, and find out the nature of the failure. All the traffic is captured and recorded in real time including precise time stamp for latter troubleshooting. |
|
|
WireShark connection
dBm069 automatically saves WireShark captures both when testing manually and automatically. When testing automatically WireShark captures of each test case can be accessed independently, being a gold tool for debuggers. |
|
|
Report Generation
Test Reports are generated in an automatic way. All the relevant information is interconnected using hyperlinks. User will find everything fast and clearly. |
|
|
Results comparation
Comparing results of different executions with the same sample before and after debugging, or to compare behaviour of several different models is an excellent tool to get a global vision and verify behavior improvement. |
|
Automation
Most tests cases need no human intervention, meaning that the tool can automatically execute almost 100% of a Test Plan.
What else is necessary to start testing a CPE?
dBm069-Engine + ACS + Library is required to start running a validation process
ACS
|
Use an external ACS (optional)
dBm069 allows working against an external ACS. dBm069-MOT is an interface that connects dBm069-Engine with the Nokia (Motive) ACS via its HDM interface application. Testing your CPE against a real ACS guarantees 100% that there will not have any interoperability issues during CPE deployment. |
|
Libraries
dBm069 Libraries
Test Case Builder (optional)
ALU is the short name of Alcatel-Lucent name. Nokia, ALU and Alcatel-Lucent are registered trade marks that belong to Nokia
