A new generation of multi-service access networks: results of MUSE phase I
AcessNets '06 Proceedings of the 1st international conference on Access networks
Information modeling and autonomic configuration management of femto network
WiCOM'09 Proceedings of the 5th International Conference on Wireless communications, networking and mobile computing
Performance improvement methods for NETCONF-Based configuration management
APNOMS'06 Proceedings of the 9th Asia-Pacific international conference on Network Operations and Management: management of Convergence Networks and Services
Outsourced management of home and SOHO windows desktops
Proceedings of the 7th International Conference on Network and Services Management
A traffic management scheme using multi-channel sniffer for secure wireless networks
Proceedings of the 6th International Conference on Ubiquitous Information Management and Communication
Towards low-latency model-oriented distributed systems management
APNOMS'07 Proceedings of the 10th Asia-Pacific conference on Network Operations and Management Symposium: managing next generation networks and services
Hi-index | 0.25 |
XML technology is penetrating the network management in the IETF, UPnP, and DSL forum suite of standards and protocols. The advantages of XML are offered at the cost of long byte streams due to XML's inherently verbose nature. The increase in packet size for remote configuration and management can pose problems, if executed in a point-to-multipoint arrangement comprising one automatic configuration server and thousands of home gateways and multimedia devices. We investigate and exploit the repetitive nature of text patterns in typical XML documents as produced by the configuration and management tasks and as coded in SOAP RPCs. The solution mainly comes from application of the Lempel-Ziv compression algorithm, with minimal additions in the proposed DSL Forum standard. Numerical and experimental results support the applicability and advantages of the proposed approach and provide insight on how these are attributable to different layers of the employed protocol stack.