B). OMAP ("operations, maintenance, and administration part") is an ITU-T man- agement framework defined for SS7 management. This framework comprises management methods and functions specifically for measurement initiations and data collection, and for initiation of tests. It extends the TMN approach by defin- ing a separate management system inside an SS7 network. This system may be connected to an TMN management system as well, in order to allow operators to Note that specifications that are identified by ASN.1 object identifiers are not necessarily MOs. Any ASN.1-based specification can be identified in this way. Organizations that want to make their specifications publicly available have to request that from an ISO authority who creates a new organization code in the object identifier tree. CORBA is developed for being a general platform for distributed OO software applications, i.e., not only for MOs. 5 Management and Traffic Systems initiate testing activities from a central point, for example. The OMAP system will then act as an AF in some mpCPs, defining MOs the TMN way. Internally, however, communication between OMAP elements is by operations only (sup- ported by TACP), which is equivalent to an OMAP actor handling a single MO (since TCAP does not support an object identifier). Thus, OMAP does not rely on MOs inside an SS7 network. 5.3.3 Connectivity Structures for mpCP Management plane control points exist, e.g., in network interfaces between a traffic system and a management system, which require the support of a connectivity stra- tum. This stratum may be completely separated from any traffic-system stratum, or it may be a stratum that is also used by traffic system layers. Using a separate stratum (in TMN called the "TMN data communication net- work") is typical for circuit-switching traffic systems. The solution is to install a LAN in a network element and to allocate its AF in a special server on that LAN. This server may then be connected to a (remote) node in the management system over some data 