For a 3GPP entity (management system or NE) to be compliant to a given management interface, all the following conditions shall be satisfied:
-
It implements the management functionality specified in the relevant IRP Information Service specifications.
-
It provides at least one of the IRP Solution Sets (were available) related to the valid Application Protocols specified by 3GPP Application Protocols for that interface, [2] Annex C.
-
It provides at least one standard networking protocol.
-
In case the entity does not offer the management interface on its own, a Q Adapter shall be provided. This Q Adapter shall be provided independently of any other NE and/or management system.
-
Support for Bulk Transfer Application Protocols specified by the relevant 3GPP management interface specifications applicable to that interface.
Figure 8.2 shows two possible options for management interface from the OS upper layers to NE. Option 1, provides access to the NE via element manager, and Option 2, provides a direct access. It is sufficient to provide one or the other.
Figure 8.2 does not imply and limit the realisation of any OS physical block (e.g. E-OS, N-OS) to just one logical layer. OS physical blocks may span more than one logical layer (ITU-T Recommendation M.3010 [1]). Different types of network elements, different functional areas, operator and vendor preferences etc will put different constraints on the physical realisation of the OSFs. See further
clause 9.
For a 3GPP entity (Network Element or management system) to be compliant to a given management interface the following conditions shall all be satisfied:
(Example 3GPP RNC / NodeB)
An important special case of the network element management architecture is where one type of network element such as the RNC will need management information for co-ordination of a subnetwork of other types of network elements such as NodeB.
This management information shared between the RNC and NodeB will not reach the operators and is not considered to be a part of the 3GPP TMN. All other management information related to NodeB will transparently be transferred by the RNC towards the 3GPP TMN.
The same compliance conditions apply for the subnetwork management architecture as for the network element management architecture (see
clause 8.2).
Interoperability between operations systems is an important issue in a 3GPP system. Different organisations may take different roles in a 3GPP system. The need to share information across corporate boundaries will be a consequence of this.
The heterogeneous, distributed and complex network of a 3GPP system will be a market for many different vendors. All operations systems have to interoperate and shall be able to share information. This is a critical issue in the management of third generation systems.
For a Operations System to be 3GPP TMN compliant the following conditions shall all be satisfied:
OS-QInternal indicates an internal flow and is not standardised.
OS-QExternal indicates an external flow and shall to be compliant to a given 3GPP Management Interface satisfy the following conditions:
The business enterprise layer has in the second-generation systems a very low degree of standardisation. Operators have legacy systems or more IT influenced systems often adopted to every organisations different needs. Enterprise management systems are not a part of a 3GPP TMN.
OS-QExteral indicates an external flow and shall to be compliant to a given 3GPP management interface satisfy the following conditions:
IFX indicates an external flow and shall to be compliant to a given 3GPP management interface satisfy the following condition: