Content for  TS 32.102  Word version:  17.0.0

The new requirement on a 3GPP system TMN will imply a focus change from network element management towards management of information "information management". Network and service providers make use of different information in several different ways which also may vary from network to network and from time to time. Basic information such as alarms is of course essential information for localising faults but may also be the key information to be able to set up a service with a service level agreement. Numerous different interfaces can be identified in a PLMN network in the areas of network element management, network management and service management. The most important and complex of these interfaces will be standardised but many interfaces of less importance are unlikely to be fully standardised and will be up to the individual operator and vendor to develop. To adopt mainstream computing technologies, re-use widely used protocols, standards and an open system architecture will be essential to secure interworking between all physical entities in a PLMN. Low-cost and general access to management systems information will be needed. Obviously this is the critical issue and challenging task in the heterogeneous, distributed and complex network of a PLMN.

A PLMN will consist of many different types of components based on different types of technologies. There will be access-, core-, transmission- and service node networks and many of the components have already been the targets for Telecom Management standardisation at different levels. Many of these standards will be reused and the management domain of a PLMN will thereby consist of many TMNs. The architecture of PLMN TMNs should support distributed TMNs and TMN-interworking on peer-to-peer basis. The Telecom Management Architecture can vary greatly in scope and detail, because of scale of operation and that different organisations may take different roles in a PLMN (see clause 5). The architecture of PLMN TMNs should provide a high degree of flexibility to meet the various topological conditions as the physical distribution and the number of NEs. Flexibility is also required to allow high degree of centralisation of personnel and the administrative practices as well as allowing dispersion to administrative domains. The 3GPP Telecom Management architecture should be such that the NEs will operate in the same way, independently of the OS architecture. Figure 7.3.2.1 illustrates the basic domains in a 3GPP system (identified in 3GPP Technical Specifications [12], [13]), related management functional areas and introduces Interface-N (Itf-N).

Itf-N between the NE OSFs and NM/SM OSFs could be used by the network- and service management systems to transfer management messages, notifications and service management requests via the NE OSF to the Network Elements (NEs). This interface shall be open and the information models standardised. Telecom management interfaces may be considered from two perspectives:

1. the management information model;
2. the management information exchange.

The management information models will be standardised in other 3GPP documents but the management information exchange will be further described in this architectural standard. The management task will vary greatly between different network elements in a PLMN. Some NEs are of high complexity e.g. a RNC, while others such as border gateways is of less complexity. Different application protocols can be chosen to best suite the management requirements of the different Network Elements and the technology used. Application protocols can be categorised out of many capabilities as:

• Functionality;
• Implementation complexity;
• Processor requirements;
• Cost efficiency;
• Market acceptance, availability of "off the shelf commercial systems and software".

For each Telecom Management interface that will be standardised by 3GPP at least one of the accepted protocols will be recommended. Accepted application protocols (e.g. SNMP, CORBA IIOP) are defined in TS 32.101, Annex A. Figure 7.3.2.2 below illustrates the basic domains in a 3GPP system (identified in 3GPP Technical Specifications [12], [13]), related management functional areas and introduces Interface-P (Itf-P2P).

Itf-P2P between two NE OSFs (or NE Management as shown in the above figure) could be used to transfer network management information such as network configuration management information The information model and the protocols used shall be those defined for Itf-P2P. They are listed in Annex E of [2].