1 / 13

Performance Evaluation of the CPE WAN Management Protocol

Performance Evaluation of the CPE WAN Management Protocol. Serafeim Papastefanos NTUA. Outline. Introduction to CWMP Advantages / disadvantages of CWMP Performance metrics Improvements Results Implementation details Conclusions. The CPE WAN Management Protocol (TR-69).

gratia
Download Presentation

Performance Evaluation of the CPE WAN Management Protocol

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Performance Evaluation of the CPE WAN Management Protocol Serafeim Papastefanos NTUA

  2. Outline • Introduction to CWMP • Advantages / disadvantages of CWMP • Performance metrics • Improvements • Results • Implementation details • Conclusions

  3. The CPE WAN Management Protocol (TR-69)

  4. Advantages of CWMP • Usage of TCP • Reliability • No problem transferring bulk data • Passing through firewalls as HTTP traffic • Avoidance of persistent connections • Usage of XML • Extensibility • Lots of tools

  5. Disadvantages of CWMP • Usage of XML • Increased requirements in bandwidth • Increased requirements in resources • Especially in TR069 clients which are embedded devices • Single ACS • This may be an issue in a multi-provider environment

  6. Performance Metrics • Processing time • Decoding and encoding of messages • Management process • Network delay • Memory requirements • Bandwidth requirements • GetParameterValues and GetParameterValuesResponse messages will be used for measurements

  7. Improvements • Generic parsers • DOM • Can also be used for encoding or messages • SAX • Encoding has to be done “by hand” • Easy to use – more resource requirements • Non-generic parsers • Harder to use – less resource requirements • Compression • We reduce the bandwidth requirements but increase the processing time.

  8. Memory requirements

  9. Encoding / decoding time

  10. Compression sizes

  11. Time needed for management

  12. Implementation details • A mini-ITX with a 600 MHz CPU was used. • CWMP client build in C • Intel’s IXML library used for DOM parsing • Our implementation of non-generic parser • mallinfo() to measure the DOM tree memory requirements • minilzo library to implement compression • gettimeofday() used to measure time

  13. Conclusions • TR069 has many advantages over NETCONF and SNMP • TR069 benefits from compression of messages, even in high network links • Using SAX or even better non-generic parsers instead of DOM optimizes resource usage and speed

More Related