.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
.rs
.sp 47P
.EF '%	Fascicle\ VI.7\ \(em\ Rec.\ Q.714''
.OF '''Fascicle\ VI.7\ \(em\ Rec.\ Q.714	%'
.ad r
\fBFigure C\(hy8/Q.714 (sheet 1 of 4), p. 1\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure C\(hy8/Q.714 (sheet 2 of 4), p. 2\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure C\(hy8/Q.714 (sheet 3 of 4), p. 3\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure C\(hy8/Q.714 (sheet 4 of 4), p. 4\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure C\(hy9/Q.714, p. 5\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure C\(hy10/Q.714 (sheet 1 of 4), p. 6\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure C\(hy10/Q.714 (sheet 2 of 4), p. 7\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure C\(hy10/Q.714 (sheet 3 of 4), p. 8\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure C\(hy10/Q.714 (sheet 4 of 4), p. 9\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure C\(hy11/Q.714, p. 10\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure C\(hy12/Q.714, p. 11\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.ce 1000
ANNEX\ D
.ce 0
.ce 1000
(to Recommendation Q.714)
.sp 9p
.RT
.ce 0
.ce 1000
\fBState transition diagrams (STD) for SCCP management control\fR 
.sp 1P
.RT
.ce 0
.LP
D.1
	\fIGeneral\fR 
.sp 1P
.RT
.PP
This Annex contains the description of the SCCP management (SCMG) function 
according to the CCITT Specification and Description Language\ (SDL). 
.PP
For the SCCP management function, Figure\ D\(hy1/Q.714 illustrates a
subdivision into functional blocks, showing their functional interactions as
well as the functional interactions with the other major functions (e.g.\ 
SCCP connectionless control (SCLC)). This is followed by Figures\ D\(hy2/Q.714 
to\ D\(hy10/Q.714 showing state transition diagrams for each of the functional
blocks.
.PP
The detailed functional breakdown shown in the following diagrams is intended 
to illustrate a reference model, and to assist interpretation of the text 
of the SCCP management procedures. The state transition diagrams are 
intended to show precisely the behaviour of the signalling system under 
normal and abnormal conditions as viewed from a remote location. It must 
be emphasized that the functional partitioning shown in the following diagrams 
is used only to facilitate understanding of the system behaviour, and is 
not intended to 
specify the functional partitioning to be adopted in a practical implementation 
of the signalling system. 
.RT
.sp 1P
.LP
D.2
	\fIDrafting conventions\fR 
.sp 9p
.RT
.PP
Each major function is designated by its acronym (e.g. SCMG\ =\ SCCP management). 
.PP
Each functional block is also designated by an acronym which
identifies it (e.g.\ SSAC\ =\ Sub\(hySystem Allowed Control).
.PP
External inputs and outputs are used for interactions between
different functional blocks. Included within each input and output symbol in
the state transition diagrams are acronyms which identify the functional 
blocks which are the source and the destination of the message,\ e.g.: 
.RT
.LP
	SSAC\ \(ra\ SSTC
	indicates that the message is sent from Sub\(hySystem
Allowed Control to Sub\(hySystem Test Control.
.PP
Internal inputs and outputs are only used to indicate control of   timers.
.sp 1P
.LP
D.3
	\fIFigures\fR 
.sp 9p
.RT
.PP
Figure D\(hy1/Q.714 shows a subdivision of the SCCP management
function (SCMG) into smaller functional blocks, and also shows the functional 
interactions between them. Each of these functional blocks is described 
in 
detail in a state transition diagram as follows:
.RT
.LP
	a)
	Signalling Point Prohibited Control (SPPC) is shown in
Figure\ D\(hy2/Q.714;
.LP
	b)
	Signalling Point Allowed Control (SPAC) is shown in
Figure\ D\(hy3/Q.714;
.LP
	c)
	Signalling Point Congested Control (SPCC) is shown in
Figure\ D\(hy4/Q.714;
.LP
	d)
	Sub\(hySystem Prohibited Control (SSPC) is shown in
Figure\ D\(hy5/Q.714;
.LP
	e)
	Sub\(hySystem Allowed Control (SSAC) is shown in
Figure\ D\(hy6/Q.714;
.LP
	f
)
	Sub\(hySystem Status Test Control (SSTC) is shown in
Figure\ D\(hy7/Q.714;
.LP
	g)
	Coordinated State Change Control (CSCC) is shown in
Figure\ D\(hy8/Q.714;
.LP
	h)
	Local Broadcast (LBCS) is shown in Figure\ D\(hy9/Q.714;
.LP
	i)
	Broadcast (BCST) is shown in Figure\ D\(hy10/Q.714.
.sp 1P
.LP
D.4
	\fIAbbreviations and timers\fR 
.sp 9p
.RT
.PP
Abbreviations and timers used in Figures D\(hy1/Q.714 to D\(hy10/Q.714
are listed below.
.RT
.sp 1P
.LP
	\fIAbbreviations\fR 
.sp 9p
.RT
.LP
	BCST
	Broadcast
.LP
	CSCC
	Cooordinated State Change Control
.LP
	DPC
	Destination Point Code
.LP
	LBCS
	Local Broadcast
.LP
	MSG
	Message
.LP
	MTP
	Message Transfer Part
.LP
	SCCP
	Signalling Connection Control Part
.bp
.LP
	SCLC
	SCCP Connectionless Control
.LP
	SCMG
	SCCP Management
.LP
	SCOC
	SCCP Connection\(hyOriented Control
.LP
	SCRC
	SCCP Routing Control
.LP
	SOG
	Sub\(hySystem Out of Service Grant
.LP
	SOR
	Sub\(hySystem Out of Service Request
.LP
	SP
	Signalling Point
.LP
	SPAC
	Signalling Point Allowed Control
.LP
	SPCC
	Signalling Point Congested Control
.LP
	SPPC
	Signalling Point Prohibited Control
.LP
	SS
	Sub\(hySystem
.LP
	SSA
	Sub\(hySystem Allowed
.LP
	SSAC
	Sub\(hySystem Allowed Control
.LP
	SSP
	Sub\(hySystem Prohibited
.LP
	SSPC
	Sub\(hySystem Prohibited Control
.LP
	SST
	Sub\(hySystem Status Test
.LP
	SSTC
	Sub\(hySystem Status Test Control
.LP
	UIS
	User In Service
.LP
	UOS
	User Out of Service
.sp 1P
.LP
	\fITimers\fR 
.sp 9p
.RT
.LP
	T(stat.\ info.)
	Delay between requests for sub\(hysystem status
information
.LP
	T(coord.\ chg.)
	Waiting for grant for sub\(hysystem to go out of
service
.LP
	T(ignore\ SST)
	Delay for sub\(hysystem between receiving grant to
go out of service and actually going out of service
.LP
.rs
.sp 21P
.ad r
Blanc
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure D\(hy1/Q.714, p. 12\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure D\(hy2/Q.714, p. 13\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure D\(hy3/Q.714, p. 14\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure D\(hy4/Q.714, p. 15\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure D\(hy5/Q.714 (sheet 1 of 2), p. 16\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure D\(hy5/Q.714 (sheet 2 of 2), p. 17\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure D\(hy6/Q.714 (sheet 1 of 2), p. 18\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure D\(hy6/Q.714 (sheet 2 of 2), p. 19\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure D\(hy7/Q.714, p. 20\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure D\(hy8/Q.714 (sheet 1 of 2), p. 21\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure D\(hy8/Q.714 (sheet 2 of 2), p. 22\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure D\(hy9/Q.714 (sheet 1 of 2), p. 23\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure D\(hy9/Q.714 (sheet 2 of 2), p. 24\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure D\(hy10/Q.714, p. 25\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 2P
.LP
\fBRecommendation Q.716\fR 
.RT
.sp 2P
.ce 1000
\fBSIGNALLIG\ CONNECTION\ CONTROL\ PART\fR 
.EF '%	Fascicle\ VI.7\ \(em\ Rec.\ Q.716''
.OF '''Fascicle\ VI.7\ \(em\ Rec.\ Q.716	%'
.ce 0
.sp 1P
.ce 1000
\fB(SCCP) PERFORMANCES\fR 
.ce 0
.sp 1P
.LP
\fB1\fR 	\fBGeneral\fR 
.sp 1P
.RT
.sp 1P
.LP
1.1
	\fIOverview\fR 
.sp 9p
.RT
.PP
The Signalling Connection Control Part (SCCP) of Signalling
System\ No.\ 7 is designed as a general message transport system common to the
various sub\(hysystems which are using its services.
.PP
SCCP must satisfy the requirements of these various sub\(hysystems and
therefore the most stringent sub\(hysystem requirements are considered when
defining a value for a performance parameter (most stringent at the time 
of the specification). To this end, the requirements of ISDN\(hyUP, the 
OMAP, the 
dialogue between an exchange and a Service Control Point (using the Transaction 
Capabilities), in particular, were investigated. It is assumed that a SCCP 
which satisfies the requirements of these users mentioned above will also 
meet those of future users. 
.PP
SCCP performances are defined by parameters of two kinds:
.RT
.LP
	\(em
	quality of service parameters as seen by a user of the SCCP;
.LP
	\(em
	internal parameters which are not seen by the user but which
contribute to a quality of service parameter: for example the
transfer delay in a relay point which contributes to the total
transit delay of messages as seen by the user.
.PP
The definitions of all these parameters are presented in Section 2 of this 
Recommendation. Then the values allowed for the internal parameters are 
defined in Section\ 3. Values for the quality of service parameters are 
given in Recommendation\ Q.709 which deals with HSRCs. 
.sp 1P
.LP
1.2
	\fIDefinitions\fR 
.sp 9p
.RT
.PP
Two concepts must be defined when dealig with SCCP performances:
SCCP route and SCCP relation. These concepts are similar to the one defined 
for the MTP (i.e.\ signalling route and signalling relation). They are 
defined as 
follows:
.RT
.LP
	\(em
	\fBSCCP route\fR : A SCCP route is composed of an ordered list
of nodes where the SCCP is used (origin, relay(s), destination)
for the transfer of SCCP messages from an originating SCCP user
to the destination SCCP user.
.LP
	\(em
	\fBSCCP relation\fR : A SCCP relation is a relation between two
SCCP users which allows them to exchange data over it. A SCCP
relation can consist of one or several SCCP routes.
.PP
Five types of nodes where SCCP functions are involved are
defined as follows:
.LP
	\(em
	\fBoriginating node\fR (origin of a UDT message or of a
signalling connection).
.LP
	\(em
	\fBdestination node\fR (destination of a UDT message
or of a signalling connection).
.LP
	\(em
	\fBrelay point\fR : signalling point where the
translation functions of the SCCP for connectionless
classes are implemented.
.LP
	\(em
	\fBrelay point without coupling\fR : signalling point where
the relay functions of the SCCP connection oriented classes, but
without the coupling of signalling connection sections function,
are implemented.
.LP
	\(em
	\fBrelay point with coupling\fR : signalling point where the
relay functions of the SCCP connection oriented classes,
including the coupling of signalling connection sections
function, are implemented.
.bp
.sp 2P
.LP
\fB2\fR 	\fBDefinition of performance parameters\fR 
.sp 1P
.RT
.PP
Some parameters which are defined in this section cannot be
measured from the outside of a signalling point and therefore no values are
attributed to them in Section\ 3 where only measurable values are given. 
This is true for some internal parameters such as for example the transit 
time of a 
CR\ message for the relay function at a relay point without coupling: this
parameter does not include in its definition the time due to the MTP and
therefore in Section\ 3 values are given to the transit time at a relay point
which icludes both the time spent in the SCCP and the\ MTP.
.PP
In networks containing implementations from a number of different
vendors, it may be necessary where a parameter has a send and receive component 
to specify that parameter on such a basis. This will then ensure that the 
overall requirement is satisfied.
.RT
.sp 2P
.LP
2.1
	\fIPerformance parameters for the connectionless classes\fR 
.sp 1P
.RT
.sp 1P
.LP
2.1.1
	\fIQuality of service parameters\fR 
.sp 9p
.RT
.PP
The following parameters define the quality of service as seen by a user 
of the connectionless classes of the SCCP: 
.RT
.LP
	\(em
	\fBundetected errors\fR 
.LP
	This parameter gives the probability that a UDT message is
delivered with user data which is defective.
.LP
	\(em
	\fBresidual error probability\fR 
.LP
	This parameter gives the probability that a UDT message is
lost, duplicated or delivered incorrectly by the set constituted
of SCCP and the MTP (called Network Service Part or NSP). An
incorrectly delivered UDT is one in which the user data are
delivered in a corrupted condition (see undetected errors
above), or the user data are delivered to an incorrect NSAP.
.LP
	For class 1 only, a UDT message is considered as incorrectly
delivered if it is delivered out of sequence by the\ NSP.
.LP
	\(em
	\fBout of sequence probability\fR 
.LP
	This parameter gives the probability that UDT messages are
delivered out of sequence to the user by the\ NSP.
.LP
	\fINote\fR \ \(em\ This parameter is relevant only for class\ 1.
.LP
	\(em
	\fBtotal transit delay of a UDT message\fR 
.LP
	This parameter is the elapsed time between a N\(hyUNITDATA
request issued by a SCCP user at the originating node and the
correponding N\(hyUNIDATA indication issued to the SCCP user at the
destination node.
.LP
	This parameter is composed of several internal parameters:
.LP
	\(em
	sending time of a UDT message by the SCCP
.LP
	\(em
	MTP overall transfer time
.LP
	\(em
	transit time of a UDT message for the relay function at
a relay point
.LP
	\(em
	receiving time of a UDT message by the SCCP
.LP
	Depending on the configuration, the second parameter could
appear one or several times and the third parameter could appear
zero, one or several times. This is illustrated in
Figure\ 1/Q.716.
.LP
	A probabilistic approach has to be taken to give values to
this parameter, considering the various possible SCCP routes and
the existence of queues at several points.
.LP
	\(em
	\fBunavailability of a SCCP relation\fR 
.LP
	This parameter characterizes the inability for two SCCP
users to communicate via the\ NSP.
.LP
	This parameter is determined by the unavailability of the
individual components of a SCCP relation: SCCP at the two
endpoints, one or several signalling relations and zero, one or
several relay points.
.LP
	This unavailability can be reduced by the duplication of
routes at the SCCP level.
.bp
.LP
.rs
.sp 23P
.ad r
\fBFigure 1/Q.716, p. 26\fR 
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
2.1.2
	\fIInternal parameters\fR 
.sp 9p
.RT
.PP
The following parameters are internal to the network service but
they contribute to the quality of service as components of a parameter 
of the previous section for connectionless classes of the\ SCCP. 
.RT
.LP
	\(em
	\fBsending time of a UDT message by the SCCP\fR 
.LP
	This parameter is the elapsed time between a N\(hyUNIDATA
request and the corresponding MTP\(hyTRANSFER request at the
originating node.
.LP
	\fINote\fR \ \(em\ The value of this parameter may differ
substantially depending whether or not a translation function is
used in the\ SCCP.
.LP
	\(em
	\fBMTP overall transfer time\fR 
.LP
\fB
	This parameter is already defined in Recommendation\ Q.706
as parameter T0 in \(sc\ 4.3.3.
.LP
	\(em
	\fBtransit time of a UDT message for the relay function at a relay point\fR 
.LP
	This parameter is the elapsed time between a MTP\(hyTRANSFER
indication primitive corresponding to an incoming UDT message at
a relay point (i.e.\ a signalling point where are implemented the
SCCP translation functions), and the associated MTP\(hyTRANSFER
request primitive corresponding to the outgoing UDT message
(which may differ from the incoming one by the called party
address).
.LP
	A probabilistic approach has to be taken to give values to
this parameter, considering the existence of queues and that it
is possible for the translation functions to be congested.
.LP
	\(em
	\fBreceiving time of a UDT message by the SCCP\fR 
.LP
	This parameter is the elapsed time between a MTP\(hyTRANSFER
indication and the corresponding N\(hyUNIDATA indication at the
destination node.
.LP
	\(em
	\fBunavailability of a relay point\fR 
.LP
	This parameter characterizes the unavailability of the
translation functions of the SCCP at a relay point.
.bp
.sp 2P
.LP
2.2
	\fIPerformance parameters for the connection oriented classes\fR 
.sp 1P
.RT
.sp 1P
.LP
2.2.1
	\fIQuality of service parameters\fR 
.sp 9p
.RT
.PP
The following parameters define the quality of service as seen by a user 
of the connection oriented classes of the\ SCCP. 
.RT
.LP
	\(em
	\fBsignalling connection establishment time\fR 
.LP
	This parameter is the elapsed time between a N\(hyCONNECT
request and the corresponding 
N\(hyCONNECT confirmation
primitive for a successful signalling connection establishment.
.LP
	This delay is composed of two parameters: one which depends
of the user at the destination node and one which depends of the
NSP. The first one which is the elapsed time between a N\(hyCONNECT
indication and response at the destination will be specified for
each user. The second one is an internal parameter of the SCCP
and will be called SCCP component of the signalling connection
establishment time. It will be specified in this SCCP
performances Recommendation.
.LP
	Moreover it is possible to specify here the maximum
signalling connection establishment time. It is equal to the
connection establishment timer (see Recommendation\ Q.714).
.LP
	\(em
	\fBsignalling connection establishment failure
probability\fR 
.LP
	A signalling connection establishment failure is defined as
a connection refusal or a time\(hyout for the connection
establishment timer coming from the SCCP.
.LP
	The dimensioning of the SCCP regarding the number of local
reference numbers will impact this signalling connection
establishment failure probability. The unavailability of
a SCCP relation is also an internal parameter impacting this
probability.
.LP
	The connection refusals coming from the called user must not
be taken into account. This also applies for the time\(hyout coming
from this called user.
.LP
	\fINote\fR \ \(em\ It is possible for the connection refusals to
distinguish between the one coming from the user and the one
coming from the SCCP, but that is impossible for the time\(hyout of
the connection establishment timer.
.LP
	\(em
	\fBthroughput\fR 
.LP
	This parameter is specified independently for each
direction of transmission and corresponds to a number of octets
of user data (contained in NSDU) transferred per second on a
signalling connection.
.LP
	\fINote\fR \ \(em\ Only successfully transferred user data are taken
into account; that means: to the correct destination, error\(hyfree
and without missequencing.
.LP
	\(em
	\fBoverall transit time of DT messages\fR 
.LP
	This parameter is the elapsed time between a N\(hyDATA request
and the corresponding N\(hyDATA indication.
.LP
	This parameter is composed of several internal parameters:
.LP
	\(em
	sending time of a DT message by the SCCP,
.LP
	\(em
	MTP overall transfer time,
.LP
	\(em
	transit time of a DT message for the relay function at
a relay point with coupling,
.LP
	\(em
	receiving time of a DT message by the SCCP.
.LP
	Depending of the configuration of the signalling connection,
the second parameter could appear one or several times and the
third parameter could appear zero, one or several times (see
Figure\ 1/Q.716).
.LP
	A probabilistic approach has to be taken to give values to
this parameter, considering the various possible SCCP routes and
the existence of queues at several points.
.LP
	\(em
	\fBundetected errors\fR 
.LP
	This parameter gives the probability that a DT message is
delivered with user data which is defective.
.LP
	\(em
	\fBresidual error rate for DT messages\fR 
.LP
	This parameter gives the probability that a DT message is
lost, duplicated, missequenced or incorrectly delivered by
the\ NSP.
.LP
	A DT message is incorrectly delivered if user data is
delivered in a corrupted condition (see undetected errors
above), or the user data are delivered to an incorrect\ NSAP.
.bp
.LP
	\(em
	\fBout of sequence probability for DT messages\fR 
.LP
	This parameter gives the probability that DT messages are
delivered out of sequence to the user by the\ NSP.
.LP
	\(em
	\fBsignalling connection unsolicited reset and premature
release probability\fR 
.LP
	This parameter gives the probability that a connection
release or reinitialization due to the SCCP occurs on a
signalling connection during a given time.
.LP
	The unavailability of a SCCP relation is an internal
parameter to be considered when calculating the probability of a
connection release occurence due to the\ SCCP.
.LP
	\(em
	\fBsignalling connection reset delay\fR 
.LP
	This parameter is the elapsed time between a N\(hyRESET
request and the corresponding N\(hyRESET confirmation primitive for
a successful signalling connection reset.
.sp 1P
.LP
2.2.2
	\fIInternal parameters\fR 
.sp 9p
.RT
.PP
The following parameters are internal to the network service but
they contribute to the quality of service as components of a parameter 
of the previous section for connection oriented classes of the\ SCCP. 
.RT
.LP
	\(em
	\fBSCCP component of the signalling connection
establishment time\fR 
.LP
	This parameter is composed of two times:
.LP
	\(em
	the elapsed time between a N\(hyCONNECT request primitive
at the origin node and the corresponding N\(hyCONNECT
indication primitive at the destination node.
.LP
	\(em
	the elapsed time between a N\(hyCONNECT response primitive
at the destination node and the corresponding N\(hyCONNECT
confirmation primitive at the origin node.
.LP
	It is composed of several internal parameters:
.LP
	\(em
	Sending time of a CR message by the SCCP
.LP
	\(em
	MTP overall transfer time
.LP
	\(em
	Transit time of a CR message for the relay function at
a relay point without coupling
.LP
	\(em
	Transit time of a CR message for the relay function at
a relay point with coupling
.LP
	\(em
	Receiving time of a CR message by the SCCP
.LP
	\(em
	Sending time of a CC message by the SCCP
.LP
	\(em
	Transit time of a CC message for the relay function at
a relay point with coupling
.LP
	\(em
	Receiving time of a CC message by the SCCP
.LP
	Depending on the configuration these parameters can appear
zero, one or several times.
.LP
	A probabilistic approach has to be taken to give values to
this parameter, considering the various possible configurations
and the existence of queues at several points.
.LP
	\(em
	\fBsending time of a CR message by the SCCP\fR 
.LP
	This parameter is the elapsed time between the N\(hyCONNECT
request primitive and the corresponding MTP\(hyTRANSFER request
primitive (for the transfer of the CR\ message).
.LP
	\fINote\fR \ \(em\ The value of this parameter may differ
substantially depending wether or not a translation function is
used in the\ SCCP.
.LP
	\(em
	\fBMTP overall transfer time\fR 
.LP
	This parameter is already defined in Recommendation Q.706
as parameter T0 in \(sc\ 4.3.3.
.LP
	\(em
	\fBtransit time of a CR message for the relay function at
a relay point without coupling\fR 
.LP
	This parameter is the elapsed time between a MTP\(hyTRANSFER
indication primitive corresponding to an incoming CR message at
a relay point without coupling, and the associated MTP\(hyTRANSFER
request primitive corresponding to the outgoing CR\ message.
.LP
	\(em
	\fBtransit time of a CR message for the relay function at
a relay point with coupling\fR 
.LP
	This parameter is the elapsed time between a MTP\(hyTRANSFER
indication primitive corresponding to an incoming CR\ message at
a relay point with coupling, and the associated MTP\(hyTRANSFER
request primitive corresponding to the outgoing CR\ message
(which may differ from the incoming one only by the called party
address).
.bp
.LP
	\(em
	\fBreceiving time of a CR message by the SCCP\fR 
.LP
	This parameter is the elapsed time between a MTP\(hyTRANSFER
indication primitive (for an incoming CR\ message), and the
corresponding N\(hyCONNECT indication primitive.
.LP
	\(em
	\fBsending time of a CC message by the SCCP\fR 
.LP
	This parameter is the elapsed time between a N\(hyCONNECT
respose primitive and the corresponding MTP\(hyTRANSFER request
primitive (for the transfer of the CC\ message).
.LP
	\(em
	\fBtransit time of a CC message for the relay function at
a relay point with coupling\fR 
.LP
	This parameter is the elapsed time between a MTP\(hyTRANSFER
indication primitive corresponding to an incoming CC\ message at
a relay point with coupling, and the associated MTP\(hyTRANSFER
request primitive corresponding to the outgoing CR\ message.
.LP
	\(em
	\fBreceiving time of a CC message by the SCCP\fR 
.LP
	This parameter is the elapsed time between a MTP\(hyTRANSFER
indication primitive (for an incoming CC\ message), and the
corresponding N\(hyCONNECT confirmation primitive.
.LP
	\(em
	\fBunavailability of a SCCP relation\fR 
.LP
	This parameter characterizes the inability for two SCCP
users to communicate via the\ NSP.
.LP
	This parameter is determined by the unavailability of the
individual components of a SCCP relation: SCCP at the two
endpoints, one or several signalling relations and zero, one
or several relay points with coupling and without coupling.
.LP
	The unavailability can be reduced by the duplication of
routes at the SCCP level.
.LP
	\(em
	\fBunavailability of a relay point\fR 
.LP
	This parameter characterizes the unavailability of the SCCP
at a relay point.
.LP
	\(em
	\fBsending time of a DT message by the SCCP\fR 
.LP
	This parameter is the elapsed time between a N\(hyDATA request
primitive and the corresponding MTP\(hyTRANSFER request primitive
(for the transfer of a DT\ message).
.LP
	\(em
	\fBtransit time of a DT message for the relay function at
a relay point with coupling\fR 
.LP
	This parameter is the elapsed time between a MTP\(hyTRANSFER
indication primitive corresponding to an incoming DT message at
a relay point with coupling, and the associated MTP\(hyTRANSFER
request primitive corresponding to the outgoing DT\ message.
.LP
	\(em
	\fBreceiving time of a DT message by the SCCP\fR 
.LP
	This parameter is the elapsed time between a MTP\(hyTRANSFER
indication primitive (for an incoming DT\ message), and the
corresponding N\(hyDATA indication primitive.
.sp 1P
.LP
2.3
	\fICorrespondence between the QOS parameters and the class\fR 
.sp 9p
.RT
.PP
The correspondence between the quality of service parameters
defined in \(sc\(sc\ 2.1.1 and\ 2.2.1 above and their applicability to 
the various 
classes of the SCCP are illustrated in Table\ 1/Q.716 below.
.RT
.LP
\fB3\fR 	\fBSpecified values for internal parameters\fR 
.sp 1P
.RT
.sp 2P
.LP
3.1
	\fIInternal parameters for classes 0 and 1\fR 
.sp 1P
.RT
.sp 1P
.LP
	\fITransit time of a UDT message in a relay point\fR 
.sp 9p
.RT
.PP
The transit time of a UDT message in a relay point is composed of the transit 
time of a UDT message for the relay function in a relay point and of the 
time elapsed in the MTP at this relay point for the UDT message: it is 
measurable externally. It is described in Figure\ 2/Q.716 and it should 
not 
exceed the values given in Table\ 2/Q.716.
.bp
.RT
.LP
.rs
.sp 25P
.ad r
\fBCuadro 1/Q.716 [T1.716], p. 27\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 5
.rs
.sp 14P
.ad r
\fBFigura 2/Q.716, p. 28\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 12P
.ad r
\fBCuadro 2/Q.716 [T2.716], p. 29\fR 
.sp 1P
.RT
.ad b
.RT
.PP
The normal traffic load for the translation function is the load for which 
the point is dimensioned. 
.PP
These figures assume a message length distribution as given in
Table\ 2/Q.706 (short messages with a mean message length of 120\ bits). 
For long messages (272\ octets of SIF) it is necessary to add about 30\ 
ms to each figure, to take into account the emitting time at 64\ kbit/s 
much longer for long 
messages than for short messages.
.RT
.sp 1P
.LP
	\fIUnavailability of a relay point\fR 
.sp 9p
.RT
.PP
The unavailability of a relay point should not
exceed\ 10\uD\dlF261\u4\d.
.RT
.sp 2P
.LP
3.2
	\fIInternal parameters for classes 2 and 3\fR 
.sp 1P
.RT
.sp 1P
.LP
	\fITransit time of a CR message at a relay point without\fR 
\fIcoupling\fR 
.sp 9p
.RT
.PP
The transit time of a CR message at a relay point without coupling is composed 
of the transit time of a CR\ message for the relay function in a 
relay point without coupling and of the time elapsed in the MTP at this 
relay point without coupling for the CR\ message: it is measurable externally. 
It 
should not exceed the values given in Table\ 3/Q.716.
.RT
.ce
\fBH.T. [T3.716]\fR 
.ce
TABLE\ 3/Q.716
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(54p) | cw(54p) sw(54p) , ^  | c | c.
 {
Traffic load for the
relay function
 }	 {
Transit time of a CR message
in a relay point
without coupling (in\ ms)
 }
	Mean	95%
_
.T&
cw(54p) | cw(54p) | cw(54p) .
Normal	\ 50 | (hy | 55	100 | (hy | 10
.T&
cw(54p) | cw(54p) | cw(54p) .
+15%	100 | (hy | 33	200 | (hy | 65
.T&
cw(54p) | cw(54p) | cw(54p) .
+30%	250 | (hy | 88	500 | (hy | 75
.TE
.LP
\fINote\fR
\ \(em\ All values are provisional.
.nr PS 9
.RT
.ad r
\fBTable 3/Q.716 [T3.716], p. 30\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.PP
The normal traffic load for the relay function is the load for
which the point is dimensioned.
.PP
These figures assume a message length distribution as given in
Table\ 2/Q.706 (short messages with a mean message length of 120\ bits). 
For long messages (128\ octets of SCCP user data) it is necessary to add 
about 15\ ms to each figure, to take into account the emitting time at 
64\ kbit/s much longer 
for long messages than for short messages.
.RT
.sp 1P
.LP
	\fITransit time of a CR message in a relay point with coupling\fR 
.sp 9p
.RT
.PP
The transit time of a CR message at a relay point with coupling is composed 
of the transit time of a CR\ message for the relay function in a relay 
point with coupling and of the time elapsed in the MTP at this relay point 
with coupling for the CR\ message: it is measurable externally. It should not
exceed the values given in Table\ 4/Q.716.
.RT
.ce
\fBH.T. [T4.716]\fR 
.ce
TABLE\ 4/Q.716
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(54p) | cw(54p) sw(54p) , ^  | c | c.
 {
Traffic load for the
relay function
 }	 {
Transit time of a CR message
in a relay point
with coupling (in\ ms)
 }
	Mean	95%
_
.T&
cw(54p) | cw(54p) | cw(54p) .
Normal	\ 75 | (hy | 80	150 | (hy | 60
.T&
cw(54p) | cw(54p) | cw(54p) .
+15%	150 | (hy | 70	300 | (hy | 40
.T&
cw(54p) | cw(54p) | cw(54p) .
+30%	375 | (hy | 50	750 | (hy | 00
.TE
.LP
\fINote\fR
\ \(em\ All values are provisional.
.nr PS 9
.RT
.ad r
\fBTable 4/Q.716 [T4.716], p. 31\fR 
.sp 1P
.RT
.ad b
.RT
.PP
The normal traffic load for the relay function is the load for
which the point is dimensioned.
.PP
These figures assume a message length distribution as given in
Table\ 2/Q.706 (short messages with a mean message length of 120\ bits). 
For long messages (128\ octets of SCCP user data) it is necessary to add 
about 15\ ms to each figure, to take into account the emitting time at 
64\ kbit/s much longer 
for long messages than for short messages.
.RT
.sp 1P
.LP
	\fITransit time of a CC message in a relay point with coupling\fR 
.sp 9p
.RT
.PP
The transit time of a CC message at a relay point with coupling is composed 
of the transit time of a CC\ message for the relay function in a relay 
point with coupling and of the time elapsed in the MTP at this relay point 
with coupling for the CC\ message: it is measurable externally. It should not
exceed the values given in Table\ 5/Q.716.
.RT
.ce
\fBH.T. [T5.716]\fR 
.ce
TABLE\ 5/Q.716
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(54p) | cw(54p) sw(54p) , ^  | c | c.
 {
Traffic load for the
relay function
 }	 {
Transit time of a CC message
in a relay point
with coupling (in\ ms)
 }
	Mean	95%
_
.T&
cw(54p) | cw(54p) | cw(54p) .
Normal	\ 30 | (hy | 10	\ 60 | (hy | 20
.T&
cw(54p) | cw(54p) | cw(54p) .
+15%	\ 60 | (hy | 65	120 | (hy | 30
.T&
cw(54p) | cw(54p) | cw(54p) .
+30%	150 | (hy | 75	300 | (hy | 50
.TE
.LP
\fINote\fR
\ \(em\ All values are provisional.
.nr PS 9
.RT
.ad r
\fBTable 5/Q.716 [T5.716], p. 32\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.PP
The normal traffic load for the relay function is the load for
which the point is dimensioned.
.PP
These figures assume a message length distribution as given in
Table\ 2/Q.706 (short messages with a mean message length of 120\ bits). 
For long messages (128\ octets of SCCP user data) it is necessary to add 
about 15\ ms to each figure, to take into account the emitting time at 
64\ kbit/s much longer 
for long messages than for short messages.
.RT
.sp 1P
.LP
	\fITransit time of a DT message in a relay point with coupling\fR 
.sp 9p
.RT
.PP
The transit time of a DT message (DT1 or DT2) at a relay point with coupling 
is composed of the transit time of a DT\ message for the relay function 
in a relay point with coupling and of the time elapsed in the MTP at this 
relay point with coupling for the DT\ message: it is measurable externally. 
It should not exceed the values given in Table\ 6/Q.716. 
.RT
.LP
.sp 1
.ce
\fBH.T. [T6.716]\fR 
.ce
TABLE\ 6/Q.716
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(54p) | cw(54p) sw(54p) , ^  | c | c.
 {
Traffic load for the
relay function
 }	 {
Transit time of a DT message
in a relay point
with coupling (in\ ms)
 }
	Mean	95%
_
.T&
cw(54p) | cw(54p) | cw(54p) .
Normal	\ 30 | (hy | 10	\ 60 | (hy | 20
.T&
cw(54p) | cw(54p) | cw(54p) .
+15%	\ 60 | (hy | 65	120 | (hy | 30
.T&
cw(54p) | cw(54p) | cw(54p) .
+30%	150 | (hy | 75	300 | (hy | 50
.TE
.LP
\fINote\fR
\ \(em\ All values are provisional.
.nr PS 9
.RT
.ad r
\fBTable 6/Q.716 [T6.716], p. 33\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 2
.PP
The normal traffic load for the relay function is the load for
which the point is dimensioned.
.PP
These figures assume a message length distribution as given in
Table\ 2/Q.706 (short messages with a mean message length of 120\ bits). 
For long messages (255\ octets of SCCP user data) it is necessary to add 
about 30\ ms to each figure, to take into account the emitting time at 
64\ kbit/s much longer 
for long messages than for short messages.
.RT
.sp 1P
.LP
	\fIUnavailability of a relay point without coupling\fR 
.sp 9p
.RT
.PP
The unavailability of a relay point without coupling should not
exceed\ 10\uD\dlF261\u4\d.
.RT
.sp 1P
.LP
	\fIUnavailability of a relay point with coupling\fR 
.sp 9p
.RT
.PP
The unavailability of a relay point with coupling is for further
study.
.RT
.LP
.rs
.sp 8P
.ad r
Blanc
.ad b
.RT
.LP
.bp