.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'
.LP
\s9\fBMONTAGE:\fR \ REC.\ Z.333 EN TETE DE CETTE PAGE
.RT
.LP
\v'23P'
\fBRecommendation\ Z.334\fR 
.sp 1P
.ce 1000
\fBSUBSCRIBER\ ADMINISTRATION\fR 
.EF '%	Fascicle\ X.7\ \(em\ Rec.\ Z.334''
.OF '''Fascicle\ X.7\ \(em\ Rec.\ Z.334	%'
.ce 0
.sp 1P
.LP
1.
	\fIGeneral\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
subscriber Administration. A glossary of the terms used is also included. 
The list of functions to be controlled by means of MML is contained in 
Annex\ A. For each of these functions 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 a 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 	\fIIntroduction\fR 
.sp 1P
.RT
.PP
The scope of this Recommendation is the operational aspect of the functional 
area of subscriber administration. 
.PP
It has been recognized that subscriber Administration is related
to various administrative procedures, belonging to other functional areas,
which have to be carried out prior to or in functional relationship to 
the jobs to be controlled by MML. 
.bp
.PP
Such administrative procedures are Administration dependent with
different degrees of data processing support.
.PP
They can be considered as the administrative environment.
.RT
.sp 2P
.LP
\fB3\fR 	\fBSubscriber administration model\fR 
.sp 1P
.RT
.sp 1P
.LP
3.1
	\fIIntroduction\fR 
.sp 9p
.RT
.PP
The model is applicable to subscribers to whom normal telephone
services (POTS: Plan of Telephone Services) are offered.
.PP
For the representation of the model the metalanguage defined in
Recommendation\ Z.333 has been used.
.PP
For the purposes of this Recommendation subscribers have been
divided into the following two classes (see Figures\ B\(hy1/Z.334, B\(hy2/Z.334 
and 
B\(hy3/Z.334 :
.RT
.LP
	\(em
	single\(hyline subscribers, comprising single\(hyparty and
multi\(hyparty lines;
.LP
	\(em
	multi\(hyline subscribers, comprising PBX (without direct
inward dialling), PABX (with direct inward dialling) and subscriber line
groups.
.PP
Both single\(hyline and multi\(hyline subscribers are embedded in an
administrative environment. This environment may comprise all data relevant 
for administering the various types of subscribers. Examples for such data 
are 
addresses of subscribers and subscribers' features. The administrative
environment aspects are not considered in detail in this model.
.sp 2P
.LP
3.2
	\fIDescription of model\fR 
.sp 1P
.RT
.sp 1P
.LP
3.2.1
	\fIGeneral\fR 
.sp 9p
.RT
.PP
Subscribers are distinguished by the data describing the way in
which they are connected to and managed by the public exchange, including 
data related to the associated hardware equipment in the exchange. Examples 
are two party lines, ordinary subscriber lines, PABXs multi\(hyparty lines. 
.PP
From the Administration view every subscriber falls into one of
the two main types identified in the model, single\(hy or multi\(hyline 
subscribers. Due to the different association of information entities needed 
for the 
representation of these two main types, two different sets of MML functions 
are felt to be appropriate. The relevant information entities defined in 
the model are described in the following sections. 
.RT
.sp 1P
.LP
3.2.2
	\fILine characteristics\fR 
.sp 9p
.RT
.PP
Line characteristics are described by their attributes which may
include information about class of line, kind of signalling, attenuation
equalization, traffic directions,\ etc.
.RT
.sp 1P
.LP
3.2.3
	\fILine group characteristics\fR 
.sp 9p
.RT
.PP
Line group characteristics are described by their attributes which may 
include information about kind of signalling, class of line, traffic 
directions etc., associated to all lines forming the group.
.RT
.sp 1P
.LP
3.2.4
	\fIFacility characteristics\fR 
.sp 9p
.RT
.PP
Facility characteristics are described by their attributes. They
include all information about supplementary services which can be assigned 
to a given subscriber. Examples are abbreviated dialling, do not disturb 
service, 
wake\(hyup service, charging information like normal charging or free of 
charge. 
.PP
There are attributes which can only be controlled by the
Administration while others are primarily controlled by the subscribers
themselves. However, it has been recognized that in the latter case these
attributes can also be controlled by the Administration.
.RT
.sp 1P
.LP
3.2.5
	\fIRestriction characteristics\fR 
.sp 9p
.RT
.PP
Restriction characteristics include information which indicate the limitations 
on the regular operational mode, e.g., traffic restrictions for 
originating calls.
.bp
.RT
.sp 1P
.LP
3.2.6
	\fIMonitoring characteristics\fR 
.sp 9p
.RT
.PP
Monitoring characteristics are related to particular monitoring
actions, which are carried out by the system. The monitoring actions are
mainly of a temporary nature and comprise subscriber Administration functions 
carried out to obtain data related to calls. Examples are malicious call 
tracing and charging observation. Monitoring actions are activated on
subscriber's or Administration's request and are described by their attributes, 
e.g.\ duration of monitoring, starting time. 
.RT
.sp 1P
.LP
3.2.7
	\fISingle\(hyline subscriber identity\fR 
.sp 9p
.RT
.PP
Single\(hyline subscriber identity allows the unambiguous
identification of a single\(hyline subscriber, normally by its directory
number.
.RT
.sp 1P
.LP
3.2.8
	\fIMulti\(hyline subscriber identity\fR 
.sp 9p
.RT
.PP
Multi\(hyline subscriber identity allows the unambiguous
identification of a multi\(hyline subscriber, normally by its directory
numbers.
.RT
.sp 1P
.LP
3.2.9
	\fIEquipment identity\fR 
.sp 9p
.RT
.PP
Equipment identity allows the unambiguous identification of the
device to which a subscriber line is connected.
.RT
.sp 1P
.LP
3.2.10
	\fILine number\fR 
.sp 9p
.RT
.PP
A line number allows the unambiguous identification of a line
within a line group.
.RT
.sp 1P
.LP
3.2.11
	\fIAssociated directory number\fR 
.sp 9p
.RT
.PP
An associated directory number may be entered for lines that are
members of a multi\(hyline subscriber and that need to have associated 
with them a directory number other than the multi\(hyline subscriber identity. 
Examples 
include the night service number for a member of a PBX or the directory 
number of a directly dialable member of a multi\(hyline hunt group. 
.RT
.sp 1P
.LP
3.2.12
	\fIState\fR 
.sp 9p
.RT
.PP
The state of a subscriber line identifies the current operational mode 
in an unique way. It may be possible to interrogate the state of a 
subscriber line.
.RT
.sp 2P
.LP
\fB4\fR 	\fIGlossary of terms\fR 
.sp 1P
.RT
.sp 1P
.LP
	\fBsingle\(hyline subscriber line\fR 
.sp 9p
.RT
.PP
A line between a public exchange and a subscriber set.
.RT
.sp 1P
.LP
	\fBmulti\(hyline subscriber line\fR 
.sp 9p
.RT
.PP
A line between a public exchange and a P(A)BX or a line between a public 
exchange and a subscriber set belonging to a subscriber line 
group.
.RT
.sp 1P
.LP
	\fBline group\fR 
.sp 9p
.RT
.PP
A line group is a group of lines of a multi\(hyline subscriber with some 
common line characteristics, e.g.\ incoming, outgoing, bothway. 
.RT
.sp 1P
.LP
	\fBsubscriber line group\fR 
.sp 9p
.RT
.PP
A group of line groups which are recognized and managed by a
public exchange as a logical group.
.bp
.RT
.ce 1000
ANNEX\ A
.ce 0
.ce 1000
(to Recommendation Z.334)
.sp 9p
.RT
.ce 0
.ce 1000
\fBList of\fR 
\fBsystem functions to be controlled\fR  |
\fBby MML and list of jobs\fR 
.sp 1P
.RT
.ce 0
.LP
A.1
	\fIList of functions to be controlled by MML\fR 
.sp 1P
.RT
.LP
	1)
	administering subscriber lines and related data;
.LP
	2)
	tracing malicious calls;
.LP
	3)
	retrieving subscriber charging information;
.LP
	4)
	observing subscriber charging.
.sp 2P
.LP
A.2
	\fIList of jobs\fR 
.sp 1P
.RT
.sp 1P
.LP
A.2.1
	\fIGeneral\fR 
.sp 9p
.RT
.PP
The jobs considered hereafter can be performed either at the
exchange level or at Operation and Maintenance Centre (OMC) level, or both.
.PP
The description of each job should include the following general
characteristics.
.RT
.LP
	\(em
	 The operator is supposed to input all data relevant for the job to be 
performed. 
.LP
	\(em
	The system is supposed to check the input data for formal
correctness and logical plausibility and to output an error message in 
the case of syntax/semantic errors and incomplete insertions, and to prompt 
for further input. 
.LP
	\(em
	 The system should update the data in its database according to the requirements 
of the performed job, e.g.\ to store, to delete data in its database. 
.sp 2P
.LP
A.2.2
	\fIList of jobs\fR 
.sp 1P
.RT
.sp 1P
.LP
A.2.2.1
	\fITo create a\fR 
\fIsingle\(hyline subscriber\fR 
.sp 9p
.RT
.LP
	\(em
	 The purpose of the job is to define an association between an equipment 
identity, subscriber identity, line, facility, restriction and 
monitoring characteristics.
.LP
	\(em
	The complexity of the job is medium.
.LP
	\(em
	 The frequency of the job is high. In local exchanges the job is expected 
to be one of the most frequent. 
.LP
	\(em
	The job is performed at the request of the subscriber, in
accordance with the availability of required equipment, directory
numbers,\ etc.
.sp 1P
.LP
A.2.2.2
	\fITo create a\fR 
\fImulti\(hyline subscriber\fR \fI, a new line group\fR \fIof a multi\(hyline 
subscriber, or a new line of a multi\(hyline subscriber\fR 
.sp 9p
.RT
.LP
	\(em
	 The purpose of the job is to create a multi\(hyline subscriber, a new 
line group of a multi\(hyline subscriber, or a new line of a multi\(hyline 
subscriber, and to define an association between multi\(hyline subscriber
identity, line group identity, line numbers, equipment identities, line,
facility, restriction and monitoring characteristics.
.LP
	\(em
	The complexity of the job is medium.
.LP
	\(em
	The frequency of the job is low.
.LP
	\(em
	The job is performed at the request of the subscriber, in
accordance with the availability of required equipment, directory
numbers,\ etc.
.sp 1P
.LP
A.2.2.3
	\fITo change single\(hyline subscriber related data\fR 
.sp 9p
.RT
.LP
	\(em
	 The purpose of this job is to change single\(hyline subscriber related 
data, i.e.\ the line and/or facility and/or the restriction and/or the 
monitoring characteristics. 
.LP
	\(em
	The complexity of the job depends on the number of the
changes and assignments.
.LP
	\(em
	The frequency of the job is medium.
.LP
	\(em
	 The job is performed at the request of the subscriber or of the Administration. 
.bp
.sp 1P
.LP
A.2.2.4
	\fITo change multi\(hyline subscriber related data\fR 
.sp 9p
.RT
.LP
	\(em
	The purpose of the job is to change multi\(hyline subscriber
related data, i.e.\ the facility and/or line and/or restriction and/or
monitoring characteristics and/or associated directory number.
.LP
	\(em
	The complexity of the job depends on the number of the
changes and assignments.
.LP
	\(em
	The frequency of the job is low;
.LP
	\(em
	 The job is performed at the request of the subscriber or of the Administration. 
.sp 1P
.LP
A.2.2.5
	\fITo delete a single\(hyline subscriber\fR 
.sp 9p
.RT
.LP
	\(em
	 The purpose of the job is to delete all data, i.e., equipment identity, 
subscriber identity and characteristics, related to a certain 
single\(hyline subscriber.
.LP
	\(em
	The complexity of the job is low depending on system
checks.
.LP
	\(em
	The frequency of the job is medium.
.LP
	\(em
	The job is performed on request of the subscriber or of the   Administration.
.sp 1P
.LP
A.2.2.6
	\fITo delete a multi\(hyline subscriber, line groups of a\fR 
\fImulti\(hyline subscriber, or lines of a multi\(hyline subscriber\fR 
.sp 9p
.RT
.LP
\fR 	\(em
	 The purpose of the job is to delete a multi\(hyline subscriber, line 
groups of a multi\(hyline subscriber or lines of a multi\(hyline 
subscriber.
.LP
	\(em
	The compexity of the job is medium depending on system
checks.
.LP
	\(em
	The frequency of the job is low.
.LP
	\(em
	 The job is performed at the request of the subscriber or of the Administration. 
.sp 1P
.LP
A.2.2.7
	\fITo interrogate single\(hyline or multi\(hyline subscriber related\fR 
\fIdata\fR 
.sp 9p
.RT
.LP
	\(em
	The purpose of the job is to interrogate single\(hyline or
multi\(hyline subscriber, line related data, according to selection criteria,
e.g.\ single\(hyline/multi\(hyline subscriber identity, all charge free
lines.
.LP
	\(em
	The system is supposed to display the desired data on an
output device at the operator's request.
.LP
	\(em
	The complexity of the job is low.
.LP
	\(em
	The frequency of the job is high when the selection
criterion is subscriber identity and low when other selection criteria are
used.
.LP
	\(em
	The job is performed at the request of the
Administration.
.sp 1P
.LP
A.2.2.8
	\fITo retrieve charging information for a single\(hyline or\fR 
\fIa multi\(hyline subscriber\fR 
.sp 9p
.RT
.LP
	\(em
	The purpose of the job is to retrieve charging information
for a single\(hyline or a multi\(hyline subscriber in case of the pulse
metering.
.LP
	\(em
	The system is supposed to provide subscribers' charging
information on an output device at the operators' request.
.LP
	\(em
	The complexity of the job is low.
.LP
	\(em
	The frequency of the job is low.
.LP
	\(em
	The job is performed for administrative reasons.
.sp 1P
.LP
A.2.2.9
	\fITo block/unblock a single\(hyline subscriber\fR 
.sp 9p
.RT
.LP
	\(em
	The purpose of the job is to make a single\(hyline subscriber
unavailable/available to traffic.
.LP
	\(em
	The system is supposed to block/unblock a single\(hyline
subscriber to originating and/or terminating traffic.
.LP
	\(em
	The compexity of the job is low.
.LP
	\(em
	The frequency of the job is medium.
.LP
	\(em
	The job is performed for administrative reasons.
.bp
.sp 1P
.LP
A.2.2.10
	\fITo block/unblock a multi\(hyline subscriber\fR 
.sp 9p
.RT
.LP
	\(em
	The purpose of the job is to make a multi\(hyline subscriber,
line groups of a multi\(hyline subscriber or lines of a multi\(hyline subscriber 
unavailable/available to traffic.
.LP
	\(em
	The system is supposed to block/unblock a multi\(hyline
subscriber, line groups of a multi\(hyline subscriber or lines of a multi\(hyline 
subscriber to originating and/or terminating traffic.
.LP
	\(em
	The complexity of the job is low.
.LP
	\(em
	The frequency of the job is low.
.LP
	\(em
	The job is performed for administrative reasons.
.sp 1P
.LP
A.2.2.11
	\fITo activate/deactivate malicious all tracing for a\fR 
\fIsingle\(hyline or a multi\(hyline subscriber\fR 
.sp 9p
.RT
.LP
	\(em
	The purpose of the job is to enable/disable malicious call
tracing for a single\(hyline subscriber, a multi\(hyline subscriber, or 
line groups of a multi\(hyline subscriber. 
.LP
	\(em
	 The system is supposed to collect the malicious call tracing data, to 
store it and to display it on operator's request. 
.LP
	\(em
	The complexity of the job is low.
.LP
	\(em
	The frequency of the job is low.
.LP
	\(em
	The job is performed at the request of the subscriber.
.sp 1P
.LP
A.2.2.12
	\fITo activate/deactivate a single\(hyline or a multi\(hyline\fR 
\fIsubscriber\fR 
.sp 9p
.RT
.LP
	\(em
	The purpose of the job is to put into or to take out of
service a single\(hyline subscriber, a multi\(hyline subscriber, line groups 
of a 
multi\(hyline subscriber or lines of a multi\(hyline subscriber previously 
defined in the system. The activation function may be implied in the corresponding 
creation function.
.LP
	\(em
	The complexity of the job is low.
.LP
	\(em
	The frequency of the job is high.
.LP
	\(em
	The job is performed at the request of the subscriber.
.sp 1P
.LP
A.2.2.13
	\fITo activate/deactivate single\(hyline or multi\(hyline\fR 
\fIsubscriber charging observation\fR 
.sp 9p
.RT
.LP
	\(em
	 The purpose of the job is to start/stop charging observation for a single\(hyline 
or multi\(hyline subscriber for a stated duration. 
.LP
	\(em
	The system is supposed to collect the charging information
data, to store it and to output it on operator's request.
.LP
	\(em
	The complexity of the job is low.
.LP
	\(em
	The frequency of the job is low.
.LP
	\(em
	The job is performed at the request of the
Administration.
\v'1P'
.ce 1000
ANNEX\ B
.ce 0
.ce 1000
(to Recommendation Z.334)
.sp 9p
.RT
.ce 0
.ce 1000
\fIGuidelines for the list of MML functions and\fR 
.sp 1P
.RT
.ce 0
.ce 1000
\fIassociated 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 subscriber
administration model defined in this Recommendation\ Z.334, \(sc\ 3.
.RT
.sp 1P
.LP
B.2
	\fIList of MML functions\fR 
.sp 9p
.RT
.PP
The list contains possible MML functions for subscriber
administration.
.PP
This list is not mandatory or complete.  It may vary according to
administrative needs, telecommunication network levels, regulatory
needs,\ etc.
.bp
.RT
.LP
	1)
	\fICreation\fR 
.LP
	\(em
	create a single\(hyline subscriber;
.LP
	\(em
	 create a multi\(hyline subscriber, a new line group of a multi\(hyline 
subscriber, or a new line of a multi\(hyline subscriber. 
.LP
	2)
	\fIChange\fR 
.LP
	\(em
	change single\(hyline subscriber related data;
.LP
	\(em
	change multi\(hyline subscriber related data.
.LP
	3)
	\fIDeletion\fR 
.LP
	\(em
	delete a single\(hyline subscriber;
.LP
	\(em
	delete a multi\(hyline subscriber, line groups of a
multi\(hyline subscriber or lines of a multi\(hyline subscriber.
.LP
	4)
	\fIInterrogation\fR 
.LP
	\(em
	interrogate single\(hy or multi\(hyline subscriber related
data.
.LP
	5)
	\fIRetrieval\fR 
.LP
	\(em
	retrieve charging information for a single\(hyline or a
multi\(hyline subscriber.
.LP
	6)
	\fIBlock/unblock\fR 
.LP
	\(em
	block/unblock a single\(hyline subscriber;
.LP
	\(em
	block/unblock a multi\(hyline subscriber.
.LP
	7)
	\fIActivation/deactivation\fR 
.LP
	\(em
	activate/deactivate malicious call tracing for a
single\(hyline subscriber;
.LP
	\(em
	activate/deactivate malicious call tracing for a
multi\(hyline subscriber;
.LP
	\(em
	activate/deactivate single\(hyline subscriber charging
observation;
.LP
	\(em
	activate/deactivate multi\(hyline subscriber charging
observation;
.LP
	\(em
	activate/deactivate a single\(hyline subscriber;
.LP
	\(em
	activate/deactivate a multi\(hyline subscriber.
.sp 1P
.LP
B.3
	\fIInformation structure diagrams\fR 
.sp 9p
.RT
.PP
The information structure entities needed for the MML functions
listed in \(sc\ B.2 are reported in this section by means of diagrams
representing each MML function information structure (Figures from B\(hy4/Z.334 
to B\(hy23/Z.334). They are not intended to constrain in any way the enhancement 
of these functions in the light of technological advances or special 
Administrations or regulatory requirements.
.PP
The metalanguage used is described in Recommendation Z.333. In
accordance with the model for single\(hyline types (Figure\ B\(hy2/Z.334) and
multi\(hyline types (Figure\ B\(hy3/Z.334), the characteristics of the 
distinct line types can be divided into characteristics assigned lines/group 
of lines and 
characteristics assigned to subscribers. Examples for the first case are 
line attenuation, kind of signalling, and for the latter case abbreviated 
dialling, wake\(hyup service, restrictions of the regular operation mode, 
etc. 
.PP
In respect of these two classes of characteristics a function may
require a division into two sub\(hyfunctions or not, depending on system
implementations and administrative needs.
.PP
Figures B\(hy5/Z.334 to B\(hy6/Z.334 provide an example of how this division 
can be accomplished, whereas the function \*Qcreate a single\(hyline subscriber\*U 
is depicted in Figure\ B\(hy4/Z.334. For all the after functions this division 
is not covered in this annex. 
.bp
.RT
.LP
.rs
.sp 24P
.ad r
\fBFigure B\(hy1/Z.334, p.1\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 23P
.ad r
\fBFigure B\(hy2/Z.334, p.2\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy3/Z.334 (feuillet 1 sur 2), p.3\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 30P
.ad r
\fBFigure B\(hy3/Z.334 (feuillet 2 sur 2), p.4\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 18P
.ad r
\fBFigure B\(hy4/Z.334, p.5\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 24P
.ad r
\fBFigure B\(hy5/Z.334, p.6\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 23P
.ad r
\fBFigure B\(hy6/Z.334, p.7\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy7/Z.334 (feuillet 1 sur 2), p.8\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 25P
.ad r
\fBFigure B\(hy7/Z.334 (feuillet 2 sur 2), p.9\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 23P
.ad r
\fBFigure B\(hy8/Z.334, p.10\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy9/Z.334 (feuillet 1 sur 2), p.11\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 14P
.ad r
\fBFigure B\(hy9/Z.334 (feuillet 2 sur 2), p.12\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 10P
.ad r
\fBFigure B\(hy10/Z.334, p.13\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 23P
.ad r
\fBFigure B\(hy11/Z.334, p.14\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 28P
.ad r
\fBFigure B\(hy12/Z.334, p.15\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 19P
.ad r
\fBFigure B\(hy13/Z.334, p.16\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 27P
.ad r
\fBFigure B\(hy14/Z.334, p.17\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 20P
.ad r
\fBFigure B\(hy15/Z.334, p.18\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 16P
.ad r
\fBFigure B\(hy16/Z.334, p.19\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 31P
.ad r
\fBFigure B\(hy17/Z.334, p.20\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 17P
.ad r
\fBFigure B\(hy18/Z.334, p.21\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 30P
.ad r
\fBFigure B\(hy19/Z.334, p.22\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 18P
.ad r
\fBFigure B\(hy20/Z.334, p.23\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 29P
.ad r
\fBFigure B\(hy21/Z.334, p.24\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 19P
.ad r
\fBFigure B\(hy22/Z.334, p.25\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 28P
.ad r
\fBFigure B\(hy23/Z.334, p.26\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp