In Charging Communication Networks, 1999
The Telecommunications Management Network (TMN)
structure
The TMN architecture is orientated to the management
of network sources via predefined interfaces. The TMN - Logical Layered
Architecture (TMN-LLA) uses a hierarchical approach for the modelling of the
deployment of sources and management entities in the system. The report
“Principles for a Telecommunications Management Network” identifies the
decomposition of the TMN functions to the following management layers:@ Raed More webtechnologymedia
Element control layer offers with the lower stage
network assets (e.G. The switching structures), and it depends on the technical
characteristics of the controlled gadget. Performance monitoring, manipulate,
and collection of secretarial metrics are among the duties that keep in touch
to this control layer.
Network control layer affords a much wider view of the
community inside which the connections are deployed and managed. The
hierarchical grouping of switching structures may be used for the definition of
layer-networks, wherein companies of nodes at one layer appear as a unmarried
node for the higher layer.
Service management layer is the surroundings in which
the carrier logic is carried out and the community assets are utilised for
providing services. The carrier manipulate and control mechanisms are deployed
thru interfaces that facilitate conversation with adjoining administrative
domain names and management structures.
Business control layer offers with the
enterprise-oriented relationships among stakeholders and proprietors of various
quantities of the infrastructure. This layer is not strictly defined because it
is meant to accommodate capabilities that correspond to the enterprise
components of service deployment.
Arun Handa, in arrangement Engineering For IMS
Networks, 2009
2.9 Network Management
The control of wi-fi telecommunication networks these
days uses a combination of the Telecommunication Management Network (TMN) and
OSI standards. The OSI version is well popular in coping with maximum IP-based
totally community factors. The TMN version provides the primary set of concepts
for a layered structure and the control functional regions. The OSI version
affords the management framework for the handling gadget and the control
device.
TMN defines a layered architecture, which accommodates
four fundamental layers:
Element Management Layer This layer offers with the
management of the functions of a community detail. Examples of these functions
are detection of device mistakes, environmental conditions which includes
energy intake and temperature, resource dimension inclusive of CPU, disk, and
message queue usage, and software program enhancements.
Network Management Layer This layer specializes in the
interplay of the network factors and the topology of the network. Examples of
the function of this sediment are to configure the network topology, establish
routing and signaling paths, and aggregating fault and measurement situations
across the community.
Service Management Layer This layer is worried with
the aspects of the community that can be experienced via the users of the
network. Examples of those network factors are the Quality of Service
(QoS)/Quality of Experience (QoE), accounting, user management, and so forth.
Business Management Layer This layer focuses on the
overall strategic control increase and evolution of the network.
The managing structures function inside the network
management layer, and the controlled systems are a part of the detail
management layer. The purposeful areas that are required to be supported via
this framework are the subsequent. These are also referred to as the FCAPS.
There aren't any unique standards for IMS community
management. IMS network factors are anticipated with the intention to assist
this general method.
Olivier Courtois, Caroline Bardelay-Guyot, in Undersea
Fiber Communication Systems (Second Edition), 2016
nine.4.1 Academic outline
A telecommunication control community (TMN, ITU-T
M.3000) introduces a logical layered structure as shown in Figure 9.21. It
divides the management location into layers:
network element control,
Each layer includes out its procedure to get control
statistics from the lower layer management machine.
Nine.4.1.1 Element control layer
The element management layer (EML) is undertaken by an
detail manager (EM) and the EM manages the operation of network factors (NEs)
inclusive of the following:
NE fault control that retrieves, shops and
presentations all kinds of alarm, occasion and system messages forwarded
through NEs.@ Read More foxconnblog
NE overall performance management that retrieves,
shops, displays, and measures transmission best information, along with
historical past block errors (BBE), errored seconds (ES), severely errored
seconds (SES), and unavailable seconds (UAS).
NE configuration management, which consists of adding
and putting off device in NE which include circuit packs, shelves and racks.
Nine.4.1.2 Network control layer
The community control layer (NML) is undertaken via a
network manager (NM) and the NM manages community operation consisting of the
subsequent:
Network configuration to manage an stop-to-end path
putting the usage of records forwarded with the aid of EMs.
Network fault to control all forms of alarm, occasion,
and machine messages forwarded by using EMs. The NM displays this data on a
network topological map with severity.
Network overall performance to manage transmission
nice information forwarded by means of EMs in view of network. The NM displays
this facts on a network topological map. The operator can reveal in which
overall performance is degraded in the community.
Nine.Four.1.3 Service management layer
The carrier management layer (SML) is undertaken
through a service manager (SM) and the SM manages ordering, hassle-handling,
credit tests of clients, and so on.
Nine.Four.1.Four Business management layer
The enterprise control layer (BML) is undertaken by a
business manager (BM) and the BM manages billing, trouble notification from
clients, and so on.
Michael Stal, in Agile Software Architecture, 2014
3.Eleven.1 Breaking dependency cycles
In a telecommunication control community, centralized
video display units allow operators to retrieve the current country of hardware
and software device. On every observed community node, agent additives display
and manipulate the underlying system. Agents document troubles using
event-based communication. One vital constituent of those occasion messages is
a time stamp. But how can dealers assign particular time stamps to their
occasions, considering the asynchrony of clocks in a dispensed environment? Unfortunately,
the venture architects decided to move the duty of producing time stamps to the
monitors (see Figure three.7), introducing a dependency cycle.@ Read More informationtechweb
This trouble can be solved in numerous approaches. For
instance, architects ought to try to invert one (or extra) of the dependencies.
They can also introduce dependency injection mechanisms. Another demonstrated
answer is to reassign obligations via adding additional structure additives,
like the committed date aspect in the instance.
A patlet is introduced in Figure three.Eight.
Network Environments, Managing
Ray Hunt, John Vargo, in Encyclopedia of Information
Systems, 2003
IV.E. Telecommunications Information Networking
Architecture
TINA includes the philosophies of TMN inside an in
depth structure designed to address the disbursed nature of present day
telecommunications networks. Like TMN, TINA makes a speciality of:
An item-orientated layout which modularizes structures
into workable additives
A allotted community of software components that may
accommodate site visitors float, traffic load, and reliability requirements
Like TMN, TINA is an architecture which helps
interoperability, portability, and reuse of software mechanism, as well as self-government
from precise technology. It specifies a layered architecture which separates
packages, services, sources, and factors using nicely-defined interfaces. TINA
adds to TMN by means of detailing the distributed processing environment (DPE).
Figure 14 represents the TINA DPE as a layer among
programs and network hardware. The DPE presents programs with an interface to
various services. The capability at the back of this interface is transparently
carried out on one or extra structures. Each implementation then communicates
with network hardware thru a kernel delivery community (e.G., TCP/IP). Key
advantages of the DPE include design portability and interoperability. TINA
programs may be supported via any compliant DPE platform, and applications
walking on exclusive DPE structures are capable of communicate through a
preferred mechanism. Thus, the DPE is a effective abstraction layer that
advantages from the disbursed processing and item orientation paradigms to
remedy the issues of heterogeneity and distribution.@ Raed More clubhitech
.jpg)