Element management requirements for evolving access networks

Abstract

Access Networks (ANs) cover that part of a network which exists between customers and exchanges. Increasingly not only are ANs becoming more sophisticated but they are also tending to combine features of both exchanges and transmission systems. In order to cope with this evolution a new type of TMN Q3 interface [1] is required to convey management information to and from the associated Operations Systems (OSs). To avoid different interfaces to the many and varied ANs being deployed, the new interface needs to be technology and implementation independent. This is best achieved by a common management interface between the network operators' OSs and the suppliers equipment. This type of interface would be terminated by an Element Manager (EM) that translates between the generic interface to an OS and the application specific communication within the AN. The need to accommodate different architecture's within a common interface cannot be met by the existing generic (object model) CCITT framework, and an approach being developed by the ETSI NA4 Sub-Technical Committee seems more appropriate. The common interface must also be capable of handling the on-going build and evolution of the AN. This can be modelled by making use of a logical parallel with test management. In the longer term, Access Networks will evolve and become responsible for services. This has management implications which are revolutionary and still to be fully worked out.