0 Bewertungen0% fanden dieses Dokument nützlich (0 Abstimmungen)
72 Ansichten5 Seiten
The TMN functional architecture defines five functional blocks: operations systems, network element, mediation, workstation, and Q adapter. Each block contains functions and communicates via standardized interfaces. The physical architecture embodies the functional blocks as physical devices connected by networks and interfaces representing the reference points. Operations systems, network elements, mediation devices, workstations, and Q adapters physically implement the corresponding functional blocks.
The TMN functional architecture defines five functional blocks: operations systems, network element, mediation, workstation, and Q adapter. Each block contains functions and communicates via standardized interfaces. The physical architecture embodies the functional blocks as physical devices connected by networks and interfaces representing the reference points. Operations systems, network elements, mediation devices, workstations, and Q adapters physically implement the corresponding functional blocks.
The TMN functional architecture defines five functional blocks: operations systems, network element, mediation, workstation, and Q adapter. Each block contains functions and communicates via standardized interfaces. The physical architecture embodies the functional blocks as physical devices connected by networks and interfaces representing the reference points. Operations systems, network elements, mediation devices, workstations, and Q adapters physically implement the corresponding functional blocks.
1. The functional architecture identifies functional modules, or blocks, in
the TMN environment, including the reference points between them, and specifies interface requirements. 2. TMN Recommendation M.3010 defines TMN architecture as five function blocks: operations systems, network element, mediation, workstation, and Q adapter, as shown in Figure. 3. Each function block contains a set of functions, and there are multiple instances of each function. Thus, for example, many OSs may be performing various operational functions in the operations systems' function block. Communication between function blocks is itself a function, but not a function block, and is defined as the TMN data communication function (DCF), which supports the standard transport protocols.
4. The TMN operations systems function (OSF) is implemented in
operations systems. Operations systems, such as the network trunk test system OS and traffic measurement OS, help monitor, manage, and control telecommunications networks and services. Network
5.
6.
7.
8.
management, both as manager and agent, is also considered to be an
OS. This system includes the MIB in Internet management and the naming tree in OSI management as a function of the OSE. The TMN network element function (NEF) is concerned with managed network elements. The network elements themselves are not part of TMN, but are supported by TMN over the standard interfaces. Network elements include hardware, software, and systems such as hubs, routers, switches, processes, and the like. The network management agent and the associated MIB are part of the NEE Network elements providing information for management (e.g., packets dropped, collision rate, etc.) are considered to be part of TMN (i.e., NEF). The TMN mediation function (MF) block addresses the operations performed on the information content passing between the network elements and OSs. Such operations include filtering, store and forward, protocol conversion, and threshold detection. A physical entity in which the MF is implemented can be shared between multiple OSs and network elements. The TMN workstation function (WSF) provides an interface between human personnel and TMN activities. More specifically, it addresses the presentation aspect of the system. The function that converts machine readable information to human interpretable format in the presentation function belongs in one of the other three function blocks: the OSF, MF, or Q adapter function. Putting it there would cover presentation functions such as the Graphical User Interface (GUI) and the humanmachine interface of workstations. Communication among the four functional blocksOSF, WSF, MF, and NEFis assumed to be standardized. Of course, that is far from the reality of the situation. Therefore, in order to accommodate legacy functionality as part of TMN, a TMN Q adapter function (QAF) has been defined. It is somewhat similar to a proxy server in SNMP management, where non-SNMP network elements are managed by an SNMP manager via a proxy server. Thus TMN noncompliant devices are connected to a TMN compliant system/network with a Q-adapter interface.
9. Each function in the function block can be considered as
providing a service and each function in the service block as providing a set of services. 10.Function blocks are designed to be nonoverlapping. However, that does not keep different function blocks from using some of the same functions.
11.Notice that the function blocks in Figure 11.7 are
connected with interfaces denoted by x, q3, qx, and f. They are called TMN service interfaces, or simply TMN interfaces. The TMN interface between function blocks, shown in Figure 11.8, is called a TMN reference point. A reference point can be considered to be a conceptual point of information exchange between function blocks. An interface between a management agent embedded in a network element and a network management system is a q3 reference point.
Q2. TMN Physical Architecture.
1. ITU-T recommendation M.3010 presenting a model for the
TMN physical architecture is illustrated in Figure 11.9. A TMN physical block could be an embodiment of one or more blocks, besides its equivalent function block. For example, an OS could have its operation function as well as a mediation device, which filters information. Five types of physical blocks represent the five functions, excluding the TMN data communication function. 2. Operations systems are embodiments of the TMN operations system function. This function is connected to the mediation device, placing the mediation function on a data communication network. The data communication network is the physical implementation of the data communication
function, which, to repeat, is not a function block but a TMN
function, DCF. The network elements, Q adapter, and workstations reflect their respective TMN functions. 3. The Q, F, and X TMN interfaces between the physical devices are also shown in Figure 11.9, representing the physical implementation of the respective TMN reference points. The Q3 interface is used between the OS and an NE or a QA. The Qx interface is used between an MD and a QA or an NE. An example is an MD being a proxy server communicating with legacy systems via a QA interface. The F interface is implemented to connect a workstation to TMN. The X interface is used between OSs belonging to two different TMNs.