Telecommunication Industry Association
TR-45.7 Sub-committee
Houston, TX
TR-45.7/99.02.23.09R1
CONTRIBUTION
TITLE:
Stage II – Section 4, Architecture
SOURCE:
CONTACTS:
Robert Patzer
Phone: (847) 632-2594
Mail stop: IL27, 2-D5
FAX: (847) –632-6999
Email: [email protected]
ABSTRACT: This contribution provides revisions to Stage II – Section 4, Architecture,
which were requested at the last TR-45.7 meeting 1/26-28/99.
RECOMMENDATION: TR-45.7 review the attached and recommend it for inclusion
into the Stage II document.
NOTICE:
This contributor grants a free, irrevocable license to the Telecommunications Industry Association (TIA) to
incorporate text contained in this contribution and any modification thereof in the creation of a TIA
standards publication; to copyright in TIA’s name any TIA standards publication even though it may
include portions of this contribution; and at TIA’s sole discretion to permit others to reproduce in whole or
in part the resulting TIA standards publication.
This contribution is a working document and was prepared to assist the standards committee. It is offered
to the committee as a basis for further discussion and as such must not be considered a binding proposal
on Motorola who specifically reserves the right to modify the statements contained herein.
4.
Architecture
4.1
Wireless Network Management Architecture
As shown in the TR-45 Network Reference Model (Figure 4-1), the O interface
point exists between an Operations System (OS) and any Mobile Network Entity
(MNE). A MNE represents “A wireless Entity within the collective entity that is
managed by the OS”. or any specific network entity having OS wireless
management needs, including another OS”. The O interface corresponds to the q
or x reference point defined within the TMN functional architecture shown in
Figure 4-2. (The following is hidden text: The x reference point is excluded but
may be included in a future stage II version.)
IP
T3
T7
SCP
SN
T8
T5
T9
T1
T2
T6
TA
T4
R
TE2
MT0
MS
EIR
Sm
ISDN
S
Di
MT1
E
TE1
TE1
F
BS
Um
BTS
Abis
BSC
A
Ai
MSC
PSTN
W
DCE
Rv
TE2
Rm
TAm
C
B
Pi
TE2
PPDN
Rx
TE2
AC
H
HLR
D
VLR
Q1
Q
R
m
MT2
N1
N
D1
Pi
G
TE2
SME
M1
OTAF
MC
M2
M3
V
MNE
CDIS
IAP
O
I
d
OS
CDGP
J
CDCP
DF
Key
Specif ic Network Entity
Composite Entity
Collectiv e Entity
H
x
Interf ace Ref erence Point
Interf ace to Another Instance
of Same Network Entity
Line Intersection
K
CDRP
Y
WNE
e
CF
X
CSC
IWF
Figure 4-1 TR45 Reference Model
Reference points (denoted in lower case) are conceptual points of information exchange
between non-overlapping management function blocks. In other words, they denote a
logical “connection” whereas interfaces denote a physical “connection”. As shown in
Figure 4-2, the q reference points serve to delineate a logical part of the information
exchange between function blocks as defined by the information model mutually
supported by these functions. The scope of the information model for the q reference
points involve aspects of Recommendation M.3100. Function blocks communicating at
the q reference points may not support the full scope of the information model. When
there is a discrepancy between the scope of the information model supported at either
side of the reference point, then mediation, described later, must be used to compensate.
To non-TMN
managed entities
m
QAF
q
To human users
NEF
q
MF
q
OSF
f
WSF
g
Fig 4-2. q-reference points in the TMN
As shown in Figure 4-2 above, the q reference points are located between the function
blocks NEF and OSF, NEF and MF, MF and MF, QAF and MF, MF and OSF, QAF and
OSF, and OSF and OSF either directly or via the DCF (not shown).
The Q Adapter Function (QAF) block is used to connect as part of the TMN those nonTMN entities which are NEF-like and OSF –like. The responsibility of the QAF is to
translate between a TMN reference point and a non-TMN (e.g., proprietary) reference
point and hence a portion of this function block is shown outside the TMN boundary.
The Network Element Function (NEF) block communicates with the TMN for the
purpose of being monitored and/or controlled. The NEF provides the telecommunications
and support functions which are required by the telecommunications network being
managed.
The Mediation Function (MF) block acts on information passing between an OSF and
NEF (or QAF) to ensure that the information conforms to the expectations of the function
blocks attached to the MF. This may be necessary as the scope of the information
supported by different communicating function blocks at the same reference point can
differ. Mediation function blocks may store, adapt, filter, threshold and condense
information.
The Operations systems function (OSF) processes information related to the
telecommunications management for the purpose of monitoring/coordinating and/or
controlling telecommunication functions including management functions (i.e., the TMN
itself).
4.2.
TMN Architecture
The principles of TMN provide for management through the definition of a
management information model (Managed Objects) which is operated on over
standardized interfaces. The goal of an interface specification is to ensure
compatibility between interconnected devices to accomplish a given TMN
application function independent of the type of device or supplier. This requires
compatible communication protocols and a compatible data representation
method for the messages.
An interface specification consists of communication protocols and an
information model. The information model defines the management information
which may be (used or permissible) carried by the common protocols Section 3
5 of this document addresses the communication protocols while section 7 9
defines the level version of the information models.
Note: should this document be an ISO (X.731) as defined in ITU-T M.3010
The following are three important aspects of the TMN architecture which can be
applied to managing wireless networks.
• A Functional Architecture which defines functional blocks (OSF, MF,
WSF, NEF and QAF), connectivity and reference points, shown in
Figure 4-3
WSF
WSF
f
f
f
f
q3
MF
qx
OSF
qx
x
x
q3
qx
NEF
QAF
q3
QAF
q3
MF
OSF
q3
qx
q3
NEF
Fig 4-3 Example TMN Functional Architecture
•
A Logical Layered Architecture that has five layers: Business
Management Layer (BML), Service Management Layer (SML), Network
Management Layer (NML), Element Management Layer (EML) and
Network Element Layer (NEL), shown in Figure 4-4.
TMN Functional Areas
Fault
Configuration Accounting
Performance
Security
Management Management Management Management Management
TMN Management Layers
BML
SML
NML
EML
NEL
Fig 4-4. Logical Layered Architecture
•
A Physical Architecture that defines management roles for operations
systems, communication networks and network elements, shown in
Figure 4-5. It is the Physical architecture that is used in tracing system
faults in the fault management functional area.
Management capabilities supported by the O-interface can be further
decomposed into five categories: fault management, performance management,
configuration management, accounting management and security management,
shown in Figure 4-4. The remainder of this document provides the interface
specification which addresses the network management layer and element
management layer for a portion of fault, configuration, and performance
capabilities as shown by the shaded areas in Figure 4-4.
OS
X/F/Q3
X
F
DCN
WS
Q3/F
Q3
Q3
MD
Qx
DCN
Qx
QA
NE
Qx
QA
NE
OS - Operations System
DCN - Data Communication Network
WS - Workstation
MD - Mediation device
QA - Q Adapter
NE - Network Element
Fig 4-5. Example of Physical Architecture for a TMN
4.3
Manager and Agent Relationship
The interoperability between two management systems (i.e., the manager - agent
relationship) is obtained by the definition of a unique message set derived from
an agreed information model and for an agreed management context.
The environment being managed can be scaled and distributed. This involves the
exchange of management information between management processes for the
purpose of monitoring and controlling the various physical and logical networking
resources. Management activities are effected through the manipulation of
managed objects. For the purpose of network management, management
processes are categorized either as managing processes or agent processes.
The two roles that management systems play are defined in ITU M.3010
(Figure 4-6)
Manager role: the part of the distributed application that issues management
operation directives and receives notifications.
1. Agent role: the part of the application process that manages the
associated managed objects. The role of the agent is to respond to
directives issued by a manager. It also reflects to the manager a view of
these objects, and emits notifications reflecting the behavior of the
objects.
Managed open system
Managing
open system
Communicating
Performing management
operations
Management operations
Agent
Manager
Role
Role
Notifications emitted Managed
Notifications
Local system environment
objects
Figure 4-6 Manager and Agent Interaction
One manager may be involved in an information exchange with several agents.
In this case it contains several manger roles interacting with their associated
agents roles. One agent may be involved in an information exchange with
several managers. In this case it contains several agent roles interacting with
their associated manager roles.
From the distributed application perspective, the agents provide for greater
network scalability as more of the functionality for management can be placed at
the network element level. The network can expand without making heavy
processing demands on the network management center. Another side benefit is
the reduced traffic overhead as many of the management operations can be
performed at the network element level: e.g. event filtering, alarm thresholding,
usage summarization, event logging, etc.
From the element management layer, agents are associated with element
managers. Usually, there will be one agent per managed network element,
although in some cases there may be multiple ones. In the latter case, each
agent would have a different functional responsibility, e.g., a dedicated agent for
a HLR that administers subscriber data.
One function of the agent is to translate between the o-reference point and the
possibly proprietary reference point at the network element layer. In other
words, it will reflect to the manager a view of the managed resources and emit
notifications reflecting the behavior of these resources. In addition, an agent can
perform mediation functions such as store, adapt, filter, threshold, and condense
information.