.rs
.\" Troff code generated by TPS Convert from ITU Original Files
.\"                 Not Copyright ( c) 1991 
.\"
.\" Assumes tbl, eqn, MS macros, and lots of luck.
.TA 1c 2c 3c 4c 5c 6c 7c 8c
.ds CH
.ds CF
.EQ
delim @@
.EN
.nr LL 40.5P
.nr ll 40.5P
.nr HM 3P
.nr FM 6P
.nr PO 4P
.nr PD 9p
.po 4P

.rs
\v | 5i'
.sp 2P
.LP
\fBRecommendation\ Z.337\fR 
.RT
.sp 2P
.sp 1P
.ce 1000
\fBNETWORK MANAGEMENT ADMINISTRATION\fR 
.EF '%	Fascicle\ X.7\ \(em\ Rec.\ Z.337''
.OF '''Fascicle\ X.7\ \(em\ Rec.\ Z.337	%'
.ce 0
.sp 1P
.LP
\fB1\fR 	\fBGeneral\fR 
.sp 1P
.RT
.PP
This Recommendation has been developed in accordance with the
methodology defined in Recommendations\ Z.332 and\ Z.333.
.PP
The main part of this Recommendation deals with the model of the
Network Management Administration. A glossary of the terms used is also
included.
.PP
The list of operator jobs and the list of system functions to be
controlled are contained in Annex\ A.
.PP
For each system function to be controlled by means of MML, one or more 
MML functions can be derived and each of them can be described using the 
metalanguage defined in Recommendation\ Z.333, in order to detail the relevant 
information structure. 
.PP
Annex\ B contains guidelines for the definition of the list of MML
functions and the information structure diagrams associated to each of 
them to be used as guidelines. 
.RT
.sp 2P
.LP
\fB2\fR 	\fBIntroduction\fR 
.sp 1P
.RT
.PP
Network management is the function of supervising the network and taking 
action to control the flow of traffic so as to ensure the maximum 
utilization of the network in all situations. The objective is to enable as
many calls as possible to be successfully completed. In its current scope,
Network Management doesn't address the aspects of managing traffic on portions 
of the network that are leased or under the control of network customers. 
.PP
According to CCITT Recommendations\ E.410 through\ E.414, E.502, Q.542 
and\ Q.544, Network Management requires the performance of a certain number 
of activities to detect abnormal network conditions and to initiate the 
execution of corrective actions and/or controls. The general scenario of 
Network 
Management activities can be described through the involved information 
flow as depicted in Figure\ 1/Z.337. Network Raw Data related to traffic 
parameters and the status (i.e.\ level of overload, out of service conditions,\ 
etc.) of the 
Network Elements can be processed to provide Network Management Parameters,
using the Network Reference Data which are necessary to calculate Network
Management Parameters. The Network Raw Data are produced from Network
Management Elements.
.PP
Network Management Parameters, describing the current network status and 
performance, can be related to some threshold values (representing the 
boundary between normal and abnormal behaviour) in order to detect abnormal
conditions.
.PP
Abnormal Condition Reports, Network Management Parameters and other
information (from telephone operators, work centres, news media, etc.) 
are used to identify the origin of the problem and, as a consequence, to 
decide the 
proper actions to be taken or the most suitable controls to be activated.
.PP
Network problem identification and consequent corrective actions can be 
handled manually or automatically by an \*Qexpert\*U system which is capable 
of performing the functions of abnormal condition detection, problem analysis 
and problem solving. All the activities carried out for Network Management 
can be handled by the operator supervision. 
.PP
Furthermore, for cooperation, coordination and planning purposes,
Network Management Reports could be distributed to other operating centres, 
to higher authorities,\ etc. 
.PP
Depending on each Administration and network organization, Network
Management activities can be partially or totally performed at exchange 
level or concentrated in one or more Network Management Centres. 
.PP
Figure 2/Z.337 contains an example of how the general scenario can be applied 
to a particular operating organization. In this example, the functions 
shown for the Network Element and Network Management Operations System 
are 
performed by the system under operator control.
.bp
.PP
Considering the Network Management scenario and the operator
activities (listed in Annex\ A to this Recommendation) three different 
sub\(hyareas can be recognized: 
.RT
.LP
	\(em
	Network Management Data administration;
.LP
	\(em
	Network Management Controls administration;
.LP
	\(em
	Network Management Data Distribution administration.
.PP
Only the sub\(hyareas for Network Management Data administration is covered 
by the present Recommendation. The remaining two sub\(hyareas, namely 
Network Management Controls administration and Network Management Data
Distribution administration are left for further study.
.LP
.rs
.sp 40P
.ad r
\fBFigure 1/Z.337, p.1\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 2/Z.337, p.2\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 2P
.LP
\fB3\fR 	\fBNetwork Management Models\fR 
.sp 1P
.RT
.sp 1P
.LP
3.1
	\fIIntroduction\fR 
.sp 9p
.RT
.PP
According to the division of Network Management activities in three sub\(hyareas 
as stated in \(sc\ 2, three different models, as indicated in the 
following, have to be developed:
.RT
.LP
	\(em
	Network Management Data administration model;
.LP
	\(em
	Network Management Controls administration model;
.LP
	\(em
	Network Management Data Distribution administration
model.
.sp 1P
.LP
3.2
	\fINetwork Management Data administration model\fR 
.sp 9p
.RT
.PP
Network Management Data administration sub\(hyarea concerns the
operator activities for managing the set of information necessary to monitor
the network status and performance. This information can be routed toward
proper display and/or storage devices in the Network Management Centre or
passed to remote Administrations under operator control.
.PP
Data administration is applied to the following data:
.RT
.LP
	\(em
	Network Raw Data;
.LP
	\(em
	Network Management Parameters;
.LP
	\(em
	Network Management Indicators;
.LP
	\(em
	Network Reference Data.
.sp 1P
.LP
3.2.1
	\fINetwork Raw Data\fR 
.sp 9p
.RT
.PP
Network Raw Data describe, for each network management element, the current 
operating conditions (e.g.\ exchange load, number of in\(hyservice 
circuits,\ etc.) and traffic behaviour (e.g.\ number of seizures for circuits
sub\(hygroup).
.PP
Network Raw Data are administered by the MML functions for Traffic
Measurements Administration, therefore they are not considered in the Network 
Management functional area. 
.RT
.sp 1P
.LP
3.2.2
	\fINetwork Management Parameters\fR 
.sp 9p
.RT
.PP
Network Management Parameters describe the network status and
performance in terms of entities (as indicated in Recommendation\ E.411) and
Network Management Objects.
.PP
Network Management Objects are the set of Network Elements subject to measurement 
for Network Management purposes. 
.PP
One or more Network Management Objects can be grouped as origin and/or 
destination objects to define traffic flow; the Network Management Objects 
are hierarchically presented below: 
.RT
.LP
	\(em
	network group;
.LP
	\(em
	network;
.LP
	\(em
	exchange group;
.LP
	\(em
	exchange;
.LP
	\(em
	circuit group;
.LP
	\(em
	circuit sub\(hygroup.
.PP
Network management monitoring and control of circuit groups and
circuit sub\(hygroups can only be performed via an exchange.
.PP
In Figure 3/Z.337 is represented, as an example, a Network Management Parameter 
in terms of the entity \*Qanswer/seizure ratio\*U for traffic handled by 
a circuit sub\(hygroup and forwarded to a set of exchanges characterized 
by the 
same destination code.
.bp
.RT
.LP
.rs
.sp 22P
.ad r
\fBFigure 3/Z.337, p.\fR 
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
3.2.3
	\fINetwork Management Indicators\fR 
.sp 9p
.RT
.PP
Network Management Indicators represent the logical results
(e.g.\ yes or\ no) obtained from the comparison of Network Management Parameters 
against a predefined set of numerical values (thresholds). 
.PP
Numerical values associated with thresholds can be time\(hydependent
(e.g.\ morning/afternoon hours, holidays,\ etc.).
.RT
.sp 1P
.LP
3.2.4
	\fINetwork Reference Data\fR 
.sp 9p
.RT
.PP
Network Reference Data can be administered by the MML functions
which are appropriate for each type of reference data, therefore they are 
not considered in the network management functional area. 
.RT
.sp 1P
.LP
3.3
	\fINetwork management control administration model\fR 
.sp 9p
.RT
.PP
To be developed.
.RT
.sp 1P
.LP
3.4
	\fINetwork management data distribution administration model\fR 
.sp 9p
.RT
.PP
To be developed.
.RT
.sp 2P
.LP
\fB4\fR 	\fBGlossary of terms\fR 
.sp 1P
.RT
.sp 1P
.LP
	\fBabnormal Condition Report\fR 
.sp 9p
.RT
.PP
Information produced in the Network Management Centre after
detection of abnormal network status or performance.
.RT
.sp 1P
.LP
	\fBcircuit group\fR 
.sp 9p
.RT
.PP
The set of all switched circuits which directly interconnect one exchange 
with another. 
.bp
.RT
.sp 1P
.LP
	\fBcircuit sub\(hygroup\fR 
.sp 9p
.RT
.PP
A group of circuits within a circuit group which are uniquely
identifiable for operational or technical reasons. A circuit group may 
consist of one or more circuit sub\(hygroups. 
.RT
.sp 1P
.LP
	\fBexchange group\fR 
.sp 9p
.RT
.PP
A set of exchanges which handles traffic forwarded to or coming
from a specific geographical area (e.g.\ area code, switching
centre,\ etc.).
.RT
.sp 1P
.LP
	\fBnetwork\fR 
.sp 9p
.RT
.PP
All the exchanges which are relevant to the service standpoint
operated by a company in a country.
.RT
.sp 1P
.LP
	\fBnetwork Element\fR 
.sp 9p
.RT
.PP
Telecommunication equipment which may perform signalling,
switching and transmission functions.
.RT
.sp 1P
.LP
	\fBnetwork group\fR 
.sp 9p
.RT
.PP
A group of telecommunication networks relevant to the service
standpoint (e.g.\ different operating companies offering the same service 
in the same country). 
.RT
.sp 1P
.LP
	\fBnetwork management action\fR 
.sp 9p
.RT
.PP
The activity performed, not necessarily in the network elements, to regulate 
traffic flow. 
.RT
.sp 1P
.LP
	\fBnetwork Management Centre\fR 
.sp 9p
.RT
.PP
A centre where network management functions are performed (e.g.\ O and\ 
M centre, switching centre). 
.RT
.sp 1P
.LP
	\fBnetwork Management Control\fR 
.sp 9p
.RT
.PP
The capabilities in network elements to regulate traffic flow and network 
operation in order to insure the maximum utilization of the network 
capacity in all situations of traffic overload and network element
failure.
.RT
.sp 1P
.LP
	\fBnetwork Management Data\fR 
.sp 9p
.RT
.PP
The set of information necessary to monitor, detect and identify a network 
problem. 
.RT
.sp 1P
.LP
	\fBnetwork Management Indicator\fR 
.sp 9p
.RT
.PP
A logical result of comparison of Network Management Parameters
and thresholds comparison.
.RT
.sp 1P
.LP
	\fBnetwork Management Information\fR 
.sp 9p
.RT
.PP
The set of information produced in the Network Management Centre describing 
the network status and performance, the abnormal conditions 
detected, the problems identity and the active network management
controls.
.RT
.sp 1P
.LP
	\fBnetwork Management Object\fR 
.sp 9p
.RT
.PP
A set of network elements under control of network management
functions and/or subject to measurement for network management purposes.
.RT
.sp 1P
.LP
	\fBnetwork Management Parameters\fR 
.sp 9p
.RT
.PP
Information produced in the Network Management Centre to be used for the 
production of abnormal condition report and for display on alerting 
devices.
.bp
.RT
.sp 1P
.LP
	\fBnetwork Management System\fR 
.sp 9p
.RT
.PP
A system which performs Network Management functions.
.RT
.sp 1P
.LP
	\fBnetwork Problem Identity\fR 
.sp 9p
.RT
.PP
Information produced in the Network Management Centre to indicate the type 
of problem detected and the portion of the network and/or services 
affected.
.RT
.sp 1P
.LP
	\fBnetwork Raw Data\fR 
.sp 9p
.RT
.PP
Network information provided by network elements and used for the production 
of Network Management Parameters and for display on alerting 
devices.
.RT
.sp 1P
.LP
	\fBnetwork Reference Data\fR 
.sp 9p
.RT
.PP
Information on the network elements and structure (e.g.\ circuit
groups, number of circuits in a circuit group, routing information, type and
quantity of switching system components).
\v'1P'
.RT
.ce 1000
ANNEX\ A
.ce 0
.ce 1000
(To Recommendation Z.337)
.sp 9p
.RT
.ce 0
.ce 1000
\fBList of system functions to be controlled by means of MML\fR 
.sp 1P
.RT
.ce 0
.ce 1000
\fBand list of jobs\fR 
.ce 0
.LP
A.1
	\fIList of system functions to be controlled by means of MML\fR 
.sp 1P
.RT
.PP
Network Management functions include:
.RT
.LP
	\(em
	performing measurements of network status and performance;
.LP
	\(em
	performing Network Management Actions;
.LP
	\(em
	performing Network Management information distribution.
.sp 1P
.LP
A.2
	\fIList of jobs\fR 
.sp 9p
.RT
.PP
The jobs are supposed to be performed at Network Management Centre level 
(i.e.\ any centre which performs network management functions). 
.RT
.sp 1P
.LP
A.2.1
	\fITo determine the appropriate Network Raw Data to be collected\fR 
.sp 9p
.RT
.LP
	\(em
	 the purpose of this job is to select the appropriate sets of Network 
Raw Data for the evaluation of the network elements and traffic 
monitoring;
.LP
	\(em
	the Network Raw Data are defined for each specific network
element. The operator is supposed to select the consistent subset of
information necessary for monitoring purposes;
.LP
	\(em
	the complexity of the job is medium;
.LP
	\(em
	the frequency of the job is low.
.sp 1P
.LP
A.2.2
	\fITo collect appropriate Network Raw Data\fR 
.sp 9p
.RT
.LP
	\(em
	the purpose of this job is to schedule the collection of
Network Raw Data from network elements:
.LP
	\(em
	 the operator is supposed to schedule selected sets of Network Raw Data 
for collection; 
.LP
	\(em
	the complexity of the job is medium;
.LP
	\(em
	the frequency of the job is low.
.bp
.sp 1P
.LP
A.2.3
	 \fITo define the appropriate parameters to be used for the network\fR 
\fIand traffic monitoring\fR 
.sp 9p
.RT
.LP
	\(em
	the purpose of this job is the definition of the Network
Management Parameters for the evaluation of the network status and traffic
performance. The Network Management Parameters are derived from the available 
set of Network Raw Data; 
.LP
	\(em
	the operator is supposed to define the set of information
necessary for Network Management Parameters production;
.LP
	\(em
	the complexity of the job is medium;
.LP
	\(em
	the frequency of the job is low.
.sp 1P
.LP
A.2.4
	 \fITo choose the Network Management Parameters with which to monitor\fR 
\fInetwork status and performance\fR 
.sp 9p
.RT
.LP
	\(em
	the purpose of this job is to choose, from defined Network
Management Parameters, a subset for the evaluation of network status and
performance;
.LP
	\(em
	the operator is supposed to choose the Network Management
Parameters necessary for network monitoring;
.LP
	\(em
	the complexity of the job is medium;
.LP
	\(em
	the frequency of the job is low.
.sp 1P
.LP
A.2.5
	 \fITo activate and deactivate the production of Network Management\fR 
\fIParameters\fR 
.sp 9p
.RT
.LP
	\(em
	 the purpose of this job is to control the production of any Specific 
Network Management Parameter; 
.LP
	\(em
	the system is supposed to store the Network Management
Parameters produced;
.LP
	\(em
	the complexity of the job is low;
.LP
	\(em
	the frequency of the job is low.
.sp 1P
.LP
A.2.6
	 \fITo assemble appropriate reference data to characterize traffic\fR 
\fIbehaviour of network elements\fR 
.sp 9p
.RT
.LP
	\(em
	the purpose of this job is to obtain appropriate reference
data describing network behaviour to be used in the analysis of the network
problems;
.LP
	\(em
	 the operator is supposed to determine what reference data is to be collected 
and stored; 
.LP
	\(em
	data items characterizing the network elements and their
interrelationships are supposed to be collected and stored in the Network
Management Centre;
.LP
	\(em
	the complexity of the job is medium;
.LP
	\(em
	the frequency of the job is low.
.sp 1P
.LP
A.2.7
	\fITo define or change the thresholds for the network status and\fR 
\fIperformance monitoring\fR 
.sp 9p
.RT
.LP
	\(em
	the purpose of this job is to define a specific set of
thresholds to which Network Management Parameters will be compared;
.LP
	\(em
	 the operator is supposed to define, for the selected Network Management 
Parameters, the numerical values to be used as thresholds; 
.LP
	\(em
	the complexity of the job may be medium depending on the
number of thresholds to be defined;
.LP
	\(em
	the frequency of the job is low.
.sp 1P
.LP
A.2.8
	\fITo associate Network Management Parameters with selected\fR 
\fIthresholds\fR 
.sp 9p
.RT
.LP
	\(em
	 the purpose of this job is to associate selected thresholds with Network 
Management Parameters; 
.LP
	\(em
	the operator is supposed to select the Network Management
Parameters which are to be compared against selected thresholds;
.LP
	\(em
	Network Management Parameters are supposed to be compared by  the system;
.LP
	\(em
	the complexity of the job is medium;
.LP
	\(em
	the frequency of the job is low.
.bp
.sp 1P
.LP
A.2.9
	\fITo display appropriate exception conditions\fR 
.sp 9p
.RT
.LP
	\(em
	the purpose of this job is to control the display of the
results derived from the comparison of Network Management Parameters against
established thresholds so as to alert the operator;
.LP
	\(em
	exception conditions may be displayed on a number of
different devices so as to best serve the network management operator. The
operator is supposed to select the devices on which exceptions are to be
displayed;
.LP
	\(em
	the complexity of the job is medium;
.LP
	\(em
	the frequency of the job is medium.
.sp 1P
.LP
A.2.10
	 \fITo request appropriate additional data displays to characterize\fR 
\fInetwork problems\fR 
.sp 9p
.RT
.LP
	\(em
	the purpose of this job is to request the display of
reference data and Network Management Parameters not otherwise automatically
displayed. These data elements provide the operator with additional information 
on which to base his determination of network problems; 
.LP
	\(em
	the operator is supposed to determine what additional
information is to be displayed;
.LP
	\(em
	the complexity of the job is high;
.LP
	\(em
	the frequency of the job is high.
.sp 1P
.LP
A.2.11
	 \fITo request appropriate data displays to characterize possible\fR \fInetwork 
management actions\fR 
.sp 9p
.RT
.LP
	\(em
	the purpose of this job is to request the display of
reference data and Network Management Parameters not otherwise automatically
displayed. These data elements provide the operator with additional information 
on which to base his determination of possible Network Management 
Actions;
.LP
	\(em
	the operator is supposed to determine what additional
information is to be displayed;
.LP
	\(em
	the complexity of the job is high;
.LP
	\(em
	the frequency of the job is high.
.sp 1P
.LP
A.2.12
	\fITo request additional data analysis for determining actions\fR 
\fIto be taken\fR 
.sp 9p
.RT
.LP
	\(em
	the purpose of this job is to request additional data
analysis to assist the operator in determining the correct Network Management 
Actions to be taken (e.g.\ equipment operating conditions, active Network 
Management Controls,\ etc.);
.LP
	\(em
	 the operator is supposed to request additional data analysis as to determine 
alternatives for the implementation of network management 
controls;
.LP
	\(em
	the complexity of the job is high;
.LP
	\(em
	the frequency of the job is high.
.sp 1P
.LP
A.2.13
	\fITo choose appropriate Network Management Controls\fR 
.sp 9p
.RT
.LP
	\(em
	 the purpose of this job is to choose the appropriate Network Management 
Controls to be applied as solutions to network problems; 
.LP
	\(em
	 the operator is supposed to choose the appropriate controls to correct 
problems in the network; 
.LP
	\(em
	the complexity of the job is high;
.LP
	\(em
	the frequency of the job is high.
.sp 1P
.LP
A.2.14
	\fITo administer automatic Network Management Controls\fR 
.sp 9p
.RT
.LP
	\(em
	the purpose of this job is to administer the
thresholds/tables used by network elements to implement automatic control in
the network;
.LP
	\(em
	the operator is supposed to create, change and delete data
from tables used by network elements to implement automatic network management 
controls; 
.LP
	\(em
	the complexity of the job is high;
.LP
	\(em
	the frequency of the job is low.
.bp
.sp 1P
.LP
A.2.15
	\fITo choose appropriate Network Management Control parameters\fR 
.sp 9p
.RT
.LP
	\(em
	the purpose of this job is to choose the appropriate
parameters to be used in the application of network management controls;
.LP
	\(em
	the operator is supposed to select the appropriate control
parameters to correct network problems;
.LP
	\(em
	the complexity of the job is high;
.LP
	\(em
	the frequency of the job is high.
.sp 1P
.LP
A.2.16
	\fITo activate/deactivate Network Management Controls\fR 
.sp 9p
.RT
.LP
	\(em
	the purpose of this job is to implement Network Management
Controls. Implementation may include all types of controls;
.LP
	\(em
	the operator is supposed to implement Network Management
Controls;
.LP
	\(em
	the complexity of the job is high;
.LP
	\(em
	the frequency of the job is high.
.sp 1P
.LP
A.2.17
	\fITo monitor known problems and adjust Network Management\fR 
\fIControls\fR 
.sp 9p
.RT
.LP
	\(em
	the purpose of this job is to provide for iterative
adjustment to the network management process. It requires as a minimum 
that the operator repeat the necessary jobs to insure that actions taken 
to relieve a 
particular problem had the optimum effect;
.LP
	\(em
	the operator is supposed to repeat necessary jobs;
.LP
	\(em
	the complexity of the job is high;
.LP
	\(em
	the frequency of the job is high.
.sp 1P
.LP
A.2.18
	\fITo administer Network Management Information distribution\fR 
\fIcharacteristics\fR 
.sp 9p
.RT
.LP
	\(em
	 the purpose of this job is to set up the required parameters for data 
distribution in and/or outside the Network Management Centre; 
.LP
	\(em
	 the operator is supposed to define the parameters necessary for display, 
record and delivery of the Network Management Information; 
.LP
	\(em
	the complexity of the job is medium;
.LP
	\(em
	the frequency of the job is low.
.sp 1P
.LP
A.2.19
	\fITo activate and deactivate Network Management Information\fR 
\fIDistribution\fR 
.sp 9p
.RT
.LP
	\(em
	the purpose of this job is to control the distribution of
Network Management Information in and/or outside the Network Management
Centre;
.LP
	\(em
	 the operator is supposed to activate/deactivate automatic and manual 
Network Management Information Distribution; 
.LP
	\(em
	the complexity of the job is medium;
.LP
	\(em
	the frequency of the job is high.
\v'1P'
.ce 1000
ANNEX\ B
.ce 0
.ce 1000
(To Recommendation Z.337)
.sp 9p
.RT
.ce 0
.ce 1000
\fBGuidelines for the list of MML functions and\fR 
.sp 1P
.RT
.ce 0
.ce 1000
\fBassociated information structure diagrams\fR 
.ce 0
.LP
B.1
	\fIIntroduction\fR 
.sp 1P
.RT
.PP
This annex contains guidelines for the list of MML functions and
associated information structure diagrams related to the Network Management
administration model defined in Recommendation\ Z.337\ \(em\ Section\ 3.
.RT
.sp 1P
.LP
B.2
	\fIList of MML functions\fR 
.sp 9p
.RT
.PP
The list contains possible MML functions for Network Management
administration.
.bp
.PP
This list is not mandatory nor complete, it may vary according to
administration needs, telecommunication network levels, regulatory needs,\ etc.
.PP
These MML functions do not represent the actual command structure of any 
real implementation of the man\(hymachine interface. Each of the MML functions 
identified can be implemented by providing one or more separate distinctive 
commands or several MML functions could be implemented by using a single
command.
.RT
.sp 1P
.LP
B.2.1
	\fIList of MML functions for Network Management Data administration\fR 
.sp 9p
.RT
.LP
	1)
	\fICreation\fR 
.LP
	\(em
	create a Network Management Object;
.LP
	\(em
	create a Network Management Parameter;
.LP
	\(em
	create a Network Management Indicator.
.LP
	2)
	\fIActivation\fR 
.LP
	\(em
	activate a Network Management Parameter;
.LP
	\(em
	activate a Network Management Indicator.
.LP
	3)
	\fIDeactivation\fR 
.LP
	\(em
	deactivate a Network Management Parameter;
.LP
	\(em
	deactivate a Network Management Indicator.
.LP
	4)
	\fIInterrogation\fR 
.LP
	\(em
	interrogate a Network Management Object;
.LP
	\(em
	interrogate a Network Management Parameter;
.LP
	\(em
	interrogate a Network Management Indicator.
.LP
	5)
	\fIDeletion\fR 
.LP
	\(em
	delete a Network Management Object;
.LP
	\(em
	delete a Network Management Parameter;
.LP
	\(em
	delete a Network Management Indicator.
.LP
	6)
	\fIChanging\fR 
.LP
	\(em
	change a Network Management Object;
.LP
	\(em
	change a Network Management Parameter;
.LP
	\(em
	change a Network Management Indicator.
.sp 1P
.LP
B.2.2
	\fIList of MML functions for Network Management Controls\fR 
\fIadministration\fR 
.sp 9p
.RT
.PP
To be developed.
.RT
.sp 1P
.LP
B.2.3
	 \fIList of MML functions for Network Management Data Distribution\fR 
\fIadministration\fR 
.sp 9p
.RT
.PP
To be developed.
.RT
.sp 1P
.LP
B.3
	\fIInformation structure diagrams\fR 
.sp 9p
.RT
.PP
Only the information entities needed for the MML functions
previously defined have been identified and are reported in the present 
section by means of diagrams representing the information structure of 
each MML 
function.
.bp
.RT
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy1/Z.337, p.4\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy2/Z.337, p.5\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 29P
.ad r
\fBFigure B\(hy3/Z.337, p.6\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 18P
.ad r
\fBFigure B\(hy4/Z.337, p.7\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 16P
.ad r
\fBFigure B\(hy5/Z.337, p.8\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 16P
.ad r
\fBFigure B\(hy6/Z.337, p.9\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 16P
.ad r
\fBFigure B\(hy7/Z.337, p.10\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy8/Z.337, p.11\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy9/Z.337, p.12\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 29P
.ad r
\fBFigure B\(hy10/Z.337, p.13\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 18P
.ad r
\fBFigure B\(hy11/Z.337, p.14\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 21P
.ad r
\fBFigure B\(hy12/Z.337, p.15\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 26P
.ad r
\fBFigure B\(hy13/Z.337, p.16\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy14/Z.337, p.17\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy15/Z.337 (feuillet 1 sur 2), p.18\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy15/Z.337 (feuillet 2 sur 2), p.19\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy16/Z.337, p.20\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp