.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\ Q.712\fR 
.RT
.sp 2P
.sp 1P
.ce 1000
\fBDEFINITION\ AND\ FUNCTION\ OF\ SCCP\ MESSAGES\fR 
.EF '%	Fascicle\ VI.7\ \(em\ Rec.\ Q.712''
.OF '''Fascicle\ VI.7\ \(em\ Rec.\ Q.712	%'
.ce 0
.sp 1P
.LP
\fB1\fR 	\fBSignalling connection control part messages\fR 
.sp 1P
.RT
.PP
The signalling connection control part (SCCP) messages are used by the 
peer\(hyto\(hypeer protocol. All messages are uniquely identified by means 
of a message type code, which is to be found in all the messages. The meaning 
and 
definition of the various parameter fields contained in these messages are
specified in \(sc\ 2. The actual inclusion of these parameter fields in a given
message depends on the class of protocol and is specified in \(sc\ 3.
.RT
.sp 1P
.LP
1.1
	\fBConnection Confirm (CC)\fR 
.sp 9p
.RT
.PP
A \fIConnection Confirm\fR  | message is sent by the called SCCP to
indicate to the calling SCCP that it has performed the setup of the signalling 
connection. On reception of a \fIConnection Confirm\fR  | message, the 
calling SCCP completes the setup of the signalling connection, if possible. 
.PP
It is used during connection establishment phase by
connection\(hyoriented protocol class\ 2 or\ 3.
.RT
.sp 1P
.LP
1.2
	\fBConnection Request (CR)\fR 
.sp 9p
.RT
.PP
A \fIConnection Request\fR  | message is sent by a calling SCCP to a
called SCCP to request the setting up of a signalling connection between the
two entities. The required characteristics of the signalling connection are
carried in various parameter fields. On reception of a \fIConnection Request\fR 
 | 
message, the called SCCP initiates the setup of the signalling connection if
possible.
.PP
It is used during connection establishment phase by
connection\(hyoriented protocol class\ 2 or\ 3.
.RT
.sp 1P
.LP
1.3
	\fBConnection Refused (CREF)\fR 
.sp 9p
.RT
.PP
A \fIConnection Refused\fR  | message is sent by the called SCCP or an 
intermediate node SCCP to indicate to the calling SCCP that the setup of 
the 
signalling connection has been refused.
.PP
It is used during connection establishment phase by
connection\(hyoriented protocol class\ 2 or\ 3.
.RT
.sp 1P
.LP
1.4
	\fBData Acknowledgement (AK)\fR 
.sp 9p
.RT
.PP
A \fIData Acknowledgement\fR  | message is used to control the window
flow control mechanism, which has been selected for the data transfer phase.
.PP
It is used during the data transfer phase in protocol class 3.
.RT
.sp 1P
.LP
1.5
	\fBData Form 1 (DT1)\fR 
.sp 9p
.RT
.PP
A \fIData Form 1\fR  | message is sent by either end of a signalling
connection to pass transparently SCCP user data between two SCCP nodes.
.PP
It is used during the data transfer phase in protocol class 2
only.
.RT
.sp 1P
.LP
1.6
	\fBData Form 2 (DT2)\fR 
.sp 9p
.RT
.PP
A \fIData Form 2\fR  | message is sent by either end of a signalling
connection to pass transparently SCCP user data between two SCCP nodes 
and to acknowledge messages flowing in the other direction. 
.PP
It is used during the data transfer phase in protocol class 3
only.
.bp
.RT
.sp 1P
.LP
1.7
	\fBExpedited Data (ED)\fR 
.sp 9p
.RT
.PP
An \fIExpedited Data\fR  | message functions as a \fIData Form 2\fR  | 
message but includes the ability to bypass the flow control mechanism which 
has been 
selected for the data transfer phase. It may be sent by either end of the
signalling connection.
.PP
It is used during the data transfer phase in protocol class 3
only.
.RT
.sp 1P
.LP
1.8
	\fBExpedited Data Acknowledgement (EA)\fR 
.sp 9p
.RT
.PP
An \fIExpedited Data Acknowledgement\fR  | message is used to
acknowledge an \fIExpedited Data\fR  | message. Every ED message has to be
acknowledged by an EA message before another ED message may be sent.
.PP
It is used during the data transfer phase in protocol class 3
only.
.RT
.sp 1P
.LP
1.9
	\fBInactivity Test (IT)\fR 
.sp 9p
.RT
.PP
An \fIInactivity Test\fR  | message may be sent periodically by either
end of a signalling connection to check if this signalling connection is 
active at both ends, and to audit the consistency of connection data at 
both ends. 
.PP
It is used in protocol classes 2 and 3.
.RT
.sp 1P
.LP
1.10
	\fBProtocol Data Unit Error (ERR)\fR 
.sp 9p
.RT
.PP
A \fIProtocol Data Unit Error\fR  | message is sent on detection of any 
protocol errors. 
.PP
It is used during the data transfer phase in protocol classes 2
and\ 3.
.RT
.sp 1P
.LP
1.11
	\fBReleased (RLSD)\fR 
.sp 9p
.RT
.PP
A \fIReleased\fR  | message is sent, in the forward or backward
direction, to indicate that the sending SCCP wants to release a signalling
connection and the associated resources at the sending SCCP have been brought 
into the disconnect pending condition. It also indicates that the receiving 
node should release the connection and any other associated resources as well.
.PP
It is used during connection release phase in protocol classes\ 2
and\ 3.
.RT
.sp 1P
.LP
1.12
	\fBRelease Complete (RLC)\fR 
.sp 9p
.RT
.PP
A \fIRelease Complete\fR  | message is sent in response to the
\fIReleased\fR  | message indicating that the \fIReleased\fR  | message 
has been 
received, and the appropriate procedures has been completed.
.PP
It is used during connection release phase in protocol classes 2
and\ 3.
.RT
.sp 1P
.LP
1.13
	\fBReset Confirm (RSC)\fR 
.sp 9p
.RT
.PP
A \fIReset Confirm\fR  | message is sent in response to a \fIReset\fR 
\fIRequest\fR  | message to indicate that \fIReset Request\fR  | has been 
received and the appropriate procedure has been completed. 
.PP
It is used during the data transfer phase in protocol class 3.
.RT
.sp 1P
.LP
1.14
	\fBReset Request (RSR)\fR 
.sp 9p
.RT
.PP
A \fIReset Request\fR  | message is sent to indicate that the sending
SCCP wants to initiate a reset procedure (re\(hyinitialization of sequence
numbers) with the receiving SCCP.
.PP
It is used during the data transfer phase in protocol class 3.
.RT
.sp 1P
.LP
1.15
	\fBSubsystem\(hyAllowed (SSA)\fR 
.sp 9p
.RT
.PP
A \fISubsystem\(hyAllowed\fR  | message is sent to concerned destinations 
to inform those destinations that a subsystem which was formerly prohibited 
is now allowed. 
.PP
It is used for SCCP subsystem management.
.bp
.RT
.sp 1P
.LP
1.16
	\fBSubsystem\(hyOut\(hyof\(hyService\(hyGrant (SOG)\fR 
.sp 9p
.RT
.PP
A \fISubsystem\(hyOut\(hyof\(hyService\(hyGrant\fR  | message is sent, 
in response to a \fISubsystem\(hyOut\(hyof\(hyService\(hyRequest\fR  | 
message, to the requesting SCCP if 
both the requested SCCP and the backup of the affected subsystem agree 
to the request. 
.PP
It is used for SCCP subsystem management.
.RT
.sp 1P
.LP
1.17
	\fBSubsystem\(hyOut\(hyof\(hyService\(hyRequest (SOR)\fR 
.sp 9p
.RT
.PP
A \fISubsystem\(hyOut\(hyof\(hyService\fR  | message is used to allow subsystems 
to go out\(hyof\(hyservice without degrading performance of the network. 
When a 
subsystem wishes to go out\(hyof\(hyservice, the request is transferred 
by means of a \fISubsystem\(hyOut\(hyof\(hyService\(hyRequest\fR  | message 
between the SCCP at the subsystem's node and the SCCP at the duplicate 
subsystem's node. 
.PP
It is used for SCCP subsystem management.
.RT
.sp 1P
.LP
1.18
	\fBSubsystem\(hyProhibited (SSP)\fR 
.sp 9p
.RT
.PP
A \fISubsystem\(hyProhibited\fR  | message is sent to concerned
destinations to inform SCCP Management (SCMG) at those destinations of the
failure of a subsystem.
.PP
It is used for SCCP subsystem management.
.RT
.sp 1P
.LP
1.19
	\fBSubsystem\(hyStatus\(hyTest (SST)\fR 
.sp 9p
.RT
.PP
A \fISubsystem\(hyStatus\(hyTest\fR  | message is sent to verify the status 
of a subsystem marked prohibited. 
.PP
It is used for SCCP subsystem management.
.RT
.sp 1P
.LP
1.20
	\fBUnitdata (UDT)\fR 
.sp 9p
.RT
.PP
A \fIUnitdata\fR  | message is used by a SCCP wanting to send data in a 
connectionless mode. 
.PP
It is used in connectionless protocol classes 0 and 1.
.RT
.sp 1P
.LP
1.21
	\fBUnitdata Service (UDTS)\fR 
.sp 9p
.RT
.PP
A \fIUnitdata Service\fR  | message is used to indicate to the
originating SCCP that a UDT it sent cannot be delivered to its destination. 
A UDTS message is sent only when the option field in that UDT is set to 
\*Qreturn on error\*U. 
.PP
It is used in connectionless protocol classes 0 and 1.
.RT
.sp 2P
.LP
\fB2\fR 	\fBSCCP parameter\fR 
.sp 1P
.RT
.sp 1P
.LP
2.1
	\fBaffected point code\fR 
.sp 9p
.RT
.PP
The \*Qaffected point code\*U identifies a signalling point where the affected 
subsystem is located. 
.RT
.sp 1P
.LP
2.2
	\fBaffected subsystem number\fR 
.sp 9p
.RT
.PP
The \*Qaffected subystem number\*U parameter field identifies a
subsystem which is failed, withdrawn, congested or allowed. In the case 
of SST messages, it also identifies the subsystem being audited. In the 
case of SOR or SOG messages, it identifies a subsystem requesting to go 
out of service. 
.RT
.sp 1P
.LP
2.3
	\fBcalling/called party address\fR 
.sp 9p
.RT
.PP
The \*Qcalling/called party address\*U parameter field contains enough 
information to uniquely identify the origination/destination signalling 
point and/or the SCCP service access point. 
.bp
.PP
It can be any combination of a global title (dialled digits for
example), a signalling point code, and a subsystem number. The subsystem 
number (SSN) identifies a SCCP user function when provided. 
.PP
In order to allow the interpretation of this address, it begins with an 
address indicator indicating which information elements are present. The 
address indicator also includes a routing indicator specifying if translation
.PP
is required, and a global title indicator specifying global title format.
.PP
The \*Qcalling/called party address\*U parameter field has two different 
meanings depending on whether it is included in a connection\(hyoriented 
or 
connectionless message.
.PP
For a connection\(hyoriented message, the significance of these fields 
is related to the direction of the connection setup (i.e. independent of 
the 
direction the message is going.
.PP
For a connectionless message, the significance of these fields is
dependent on the direction the message is going (just as for OPC and
DPC).
.RT
.sp 1P
.LP
2.4
	\fBcredit\fR 
.sp 9p
.RT
.PP
The \*Qcredit\*U parameter field is used in the acknowledgements to
indicate to the sender how many messages it may send, i.e.,\ window size. 
It is also used in the CR and CC message to indicate the proposed and selected 
credit, and in the IT message to audit the consistency of this connection 
data at both ends of a connection section. 
.RT
.sp 1P
.LP
2.5
	\fBdata\fR 
.sp 9p
.RT
.PP
The \*Qdata\*U parameter field contains information coming from upper layers 
or from SCCP management. 
.PP
In connectionless and connection\(hyoriented messages the data parameter 
field contains information coming from the upper layers. 
.PP
Information coming from SCCP management will be contained in the data parameter 
field of a UDT message. In this case the data parameter field of the UDP 
message will only contain the SCCP management message. 
.RT
.sp 1P
.LP
2.6
	\fBdiagnostic\fR 
.sp 9p
.RT
.PP
The \*Qdiagnostic\*U parameter field is for further study.
.RT
.sp 1P
.LP
2.7
	\fBerror cause\fR 
.sp 9p
.RT
.PP
The \*Qerror cause\*U parameter field is used in the \fIProtocol Data\fR 
\fIUnit Error\fR  | message in order to indicate what is the exact protocol 
error.
.RT
.sp 1P
.LP
2.8
	\fBend of optional parameters\fR 
.sp 9p
.RT
.PP
The \*Qend of optional parameters\*U parameter field is used in any
message containing optional parameters to indicate where the part allocated 
to these optional parameters ends. 
.RT
.sp 1P
.LP
2.9
	\fBlocal reference number (source/destination)\fR 
.sp 9p
.RT
.PP
The \*Qlocal reference number (source/destination)\*U parameter field uniquely 
identifies in a node a signalling connection. It is an internal 
working
number chosen by each node independently from the destination node. At least
.PP
one local reference number is to be found in any message exchanged on a
signalling connection section.
.PP
\fINote\fR \ \(em\ Remote reference number is used to reflect the local
reference number at the remote end of a connection section.
.RT
.sp 1P
.LP
2.10
	\fBprotocol class\fR 
.sp 9p
.RT
.PP
For connection\(hyoriented protocol classes, the \*Qprotocol class\*U
parameter field is used during the connection establishment phase; it is
negotiated between the two end SCCP. It is also used during data transfer 
phase to audit the consistency of this connection data at both ends of 
a connection section. 
.PP
For connectionless protocol classes the \*Qprotocol class\*U parameter
field is used to indicate whether or not a message should be returned on 
error occurence. 
.bp
.RT
.sp 1P
.LP
2.11
	\fBreceive sequence number\fR 
.sp 9p
.RT
.PP
The \*Qreceive sequence number\*U parameter field P(R) is used in the data 
acknowledgement message to indicate the lower edge of the receiving 
window.
.PP
It also indicates that at least all messages numbered up to and
including P(R)\ \(em\ 1 are accepted.
.RT
.sp 1P
.LP
2.12
	\fBrefusal cause\fR 
.sp 9p
.RT
.PP
The \*Qrefusal cause\*U parameter field is used in a \fIConnection\fR 
\fIRefused\fR  | message to indicate the reason why the connection setup 
request 
was refused.
.RT
.sp 1P
.LP
2.13
	\fBrelease cause\fR 
.sp 9p
.RT
.PP
The \*Qrelease cause\*U parameter field is used in a \fIReleased\fR  |
message to indicate the reason of the release.
.RT
.sp 1P
.LP
2.14
	\fBreset cause\fR 
.sp 9p
.RT
.PP
The \*Qreset cause\*U parameter field is used in a \fIReset Request\fR  |
message to indicate the reason why a reset procedure is invoked.
.RT
.sp 1P
.LP
2.15
	\fBreturn cause\fR 
.sp 9p
.RT
.PP
For connectionless protocol classes, the \*Qreturn cause\*U parameter field 
is used to indicate the reason why a message was returned. 
.RT
.sp 1P
.LP
2.16
	\fBsegmenting/reassembling\fR 
.sp 9p
.RT
.PP
The \*Qsegmenting/reassembling\*U parameter field is used in the data message 
for the segmenting and reassembling function. It is the more data 
indicator (M\(hybit). This is used only in connection\(hyoriented messages.
.PP
It is set to one in a data message to indicate that more data will
follow in a subsequent message.
.PP
It is set to zero in a data message to indicate that the data in this message 
forms the end of a complete data sequence. 
.RT
.sp 1P
.LP
2.17
	\fBsequencing/segmenting\fR 
.sp 9p
.RT
.PP
The \*Qsequencing/segmenting\*U parameter field contains the
information necessary for the following functions: sequence numbering, flow
control, segmenting and reassembling.
.RT
.sp 1P
.LP
2.18
	\fBsubsystem multiplicity indicator\fR 
.sp 9p
.RT
.PP
The \*Qsubsystem multiplicity indicator\*U is used in SCCP management messages 
to indicate the number of associated replicated subsystems. 
.RT
.sp 2P
.LP
\fB3\fR 	\fBInclusion of fields in the messages\fR 
.sp 1P
.RT
.PP
The inclusion of the information elements specified in \(sc\ 2 in the various 
messages specified in \(sc\ 1 according to their type depends on the class 
.PP
of protocol. SCCP messages are specified in Table\ 1/Q.712 and SCCP management 
messages are specified in Table\ 2/Q.712. 
.PP
All SCCP management messages are embedded in the \*Qdata\*U parameter of 
the \fIUnitdata\fR  | message. 
.PP
The following applies to Tables 1/Q.712 and 2/Q.712:
.RT
.LP
	m
	mandatory field
.LP
	o
	optional field (which is included in a message when
needed)
.bp
.ce
\fBH.T. [T1.712]\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(342p) .
TABLE\ 1/Q.712
.T&
cw(342p) .
 {
\fBInclusion of fields in messages\fR
 }
.TE
.TS
center box ;
lw(90p) | cw(12p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) .
Messages Parameter field	CR	CC	CREF	RLSD	RLC	DT1	DT2	AK	ED	EA	RSR	RSC	ERR	IT	UDT	UDTS  
_
.T&
lw(90p) | cw(12p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) .
 {
Destination local reference number
 }		m	m	m	m	m	m	m	m	m	m	m	m	m		
_
.T&
lw(90p) | cw(12p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) .
Source local reference number	m	m		m	m						m	m		m		
_
.T&
lw(90p) | cw(12p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) .
Called party address	m	o	o												m	m
_
.T&
lw(90p) | cw(12p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) .
Calling party address	o														m	m
_
.T&
lw(90p) | cw(12p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) .
Protocol class	m	m												m	m	
_
.T&
lw(90p) | cw(12p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) .
Segmenting/Reassembling						m										
_
.T&
lw(90p) | cw(12p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) .
Receive sequence number								m 								
_
.T&
lw(90p) | cw(12p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) .
Sequencing/Segmenting							m							m | ua\d\u)\d		
_
.T&
lw(90p) | cw(12p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) .
Credit	o	o						m						m | ua\d\u)\d		
_
.T&
lw(90p) | cw(12p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) .
Release cause				m												
_
.T&
lw(90p) | cw(12p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) .
Return cause																m
_
.T&
lw(90p) | cw(12p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) .
Reset cause											m					
_
.T&
lw(90p) | cw(12p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) .
Error cause													m 			
_
.T&
lw(90p) | cw(12p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) .
User data	o	o	o	o		m	m		m						m	m 
_
.T&
lw(90p) | cw(12p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) .
Refusal cause			m													
_
.T&
lw(90p) | cw(12p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) | cw(20p) | cw(14p) | cw(14p) .
End of optional parameters	o	o	o	o 
.TE
.LP
\ua\d\u)\d\ Information in these parameter fields are ignored if the protocol
class parameter indicates class\ 2.
.nr PS 9
.RT
.ad r
\fBTableau 1/Q.712 [T1.712] (\*`a l'italienne), p.1\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.ce
\fBH.T. [T2.712]\fR 
.ce
TABLE\ 2/Q.712
.ce
\fBSCCP management messages\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
Messages  Parameter fields	SSA	SSP	SST	SOR	SOG
_
.T&
lw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
SCMG format ID	m	m	m	m	m
_
.T&
lw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
Affected SSN	m	m	m	m	m
_
.T&
lw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
Affected PC	m	m	m	m	m
_
.T&
lw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
 {
Subsystem multiplicity indicator
 }	m	m	m	m	m
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau 2/Q.712 [T2.712], p.2\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 4
.sp 2P
.LP
\fBRecommendation\ Q.713\fR 
.RT
.sp 2P
.sp 1P
.ce 1000
\fBSCCP\ FORMATS\ AND\ CODES\fR 
.EF '%	Fascicle\ VI.7\ \(em\ Rec.\ Q.713''
.OF '''Fascicle\ VI.7\ \(em\ Rec.\ Q.713	%'
.ce 0
.sp 1P
.LP
\fB1\fR 	\fBGeneral\fR 
.sp 1P
.RT
.PP
The Signalling Connection Control Part (SCCP) messages are carried on the 
signalling data link by means of Signal Units the format of which is 
described in Recommendation\ Q.703, \(sc\ 2.2.
.PP
The Service Information Octet format and coding is described in
Recommendation\ Q.704, \(sc\ 14.2. The Service Indicator is coded\ 0011 for
the\ SCCP.
.PP
The Signalling Information Field (SIF) of each Message Signal Unit containing 
an\ SCCP message consists of an integral number of octets. 
.PP
A message consists of the following parts (see
Figure\ 1/Q.713):
.RT
.LP
	\(em
	the routing label;
.LP
	\(em
	the message type code;
.LP
	\(em
	the mandatory fixed part;
.LP
	\(em
	the mandatory variable part;
.LP
	\(em
	the optional part, which may contain fixed length and
variable length fields.
.PP
The description of the various parts is contained in the following sections. 
SCCP Management messages and codes are provided in \(sc\ 5 of this 
Recommendation.
.sp 1P
.LP
1.1
	\fIRouting label\fR 
.sp 9p
.RT
.PP
The standard routing label specified in Recommendation Q.704, \(sc\ 2.2 
is used. The rules for the generation of the signalling link selection 
(SLS) 
code are described in Recommendation\ Q.711, \(sc\ 2.2.1.
.bp
.RT
.LP
.rs
.sp 13P
.ad r
\fBFigure 1/Q.713 [T1.713], p. \ \ 
(\*`a traiter comme tableau MEP)\fR 
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
.sp 1
1.2
	\fIMessage type code\fR 
.sp 9p
.RT
.PP
The message type code consists of a one octet field, and is
mandatory for all messages. The message type code uniquely defines the 
function and format of each SCCP message. The allocation of message type 
codes, with 
reference to the appropriate descriptive section of this Recommendation is
summarized in Table\ 1/Q.713. Table\ 1/Q.713 also contains an indication 
of the applicability of the various message types to the relevant classes 
of 
protocol.
.RT
.sp 1P
.LP
1.3
	\fIFormatting principles\fR 
.sp 9p
.RT
.PP
Each message consists of a number of parameters listed and
described in \(sc\ 3. Each parameter has a \*Qname\*U which is coded as 
a single 
octet (see \(sc\ 3). The length of a parameter may be fixed or variable, and a
\*Qlength indicator\*U of one octet for each parameter may be included 
as described below. 
.PP
The detailed format is uniquely defined for each message type as
described in \(sc\ 4.
.PP
A general SCCP message format is shown in Figure\ 2/Q.713
.
.RT
.sp 1P
.LP
1.4
	\fIMandatory fixed part\fR 
.sp 9p
.RT
.PP
Those parameters that are mandatory and of fixed length for a
particular message type will be contained in the \*Qmandatory fixed part\*U. 
The 
position, length and order of the parameters is uniquely defined by the 
message type. Thus the names of the parameters and the length indicators 
are not 
included in the message.
.RT
.sp 1P
.LP
1.5
	\fIMandatory variable part\fR 
.sp 9p
.RT
.PP
Mandatory parameters of variable length will be included in the
mandatory variable part. The name of each parameter and the order in which
the pointers are sent is implicit in the message type. Parameter names are,
therefore, not included in the message. A pointer is used to indicate the
beginning of each parameter. Because of this, parameters may be sent in an
order different from that of the pointers. Each pointer is encoded as a 
single octet. The details of how pointers are encoded is found in \(sc\ 
2.3. The number of parameters, and thus the number of pointers is uniquely 
defined by the message type. 
.PP
A pointer is also included to indicate the beginning of the
optional part. If the message type indicates that no optional part is allowed, 
then this pointer will not be present. If the message type indicates that 
an 
optional part is possible, but there is no optional part included in this
particular message, then a pointer field containing all zeros will be used.
.PP
All the pointers are sent consecutively at the beginning of the
mandatory variable part. Each parameter contains the parameter length indicator 
followed by the contents of the parameter. 
.bp
.RT
.LP
.rs
.sp 41P
.ad r
\fBFigure 2/Q.713 (CCITT 73070), p.\fR 
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
1.6
	\fIOptional part\fR 
.sp 9p
.RT
.PP
The optional part consists of parameters that may or may not occur in any 
particular message type. Both fixed length and variable length 
parameters may be included. Optional parameters may be transmitted in any
order
.FS
It is for further study if any constraint in the order of
transmission will be introduced.
.FE
. Each optional parameter will include
the parameter name (one octet) and the length indicator (one octet) followed 
by the parameter contents. 
.bp
.RT
.sp 1P
.LP
1.7
	\fIEnd of optional parameters octet\fR 
.sp 9p
.RT
.PP
After all optional parameters have been sent, an end of optional
parameters octet containing all zeroes will be transmitted. This octet 
is only included if optional parameters are present in the message. 
.RT
.sp 1P
.LP
1.8
	\fIOrder of transmission\fR 
.sp 9p
.RT
.PP
Since all the parameters consist of an integral number of octets, the formats 
are presented as a stack of octets. The first octet transmitted is the 
one shown at the top of the stack and the last is the one at the bottom 
(see Figure\ 2/Q.713).
.PP
Within each octet, the bits are transmitted with the least significant 
bit first. 
.RT
.sp 1P
.LP
1.9
	\fICoding of spare bits\fR 
.sp 9p
.RT
.PP
According to the general rules defined in Rec. Q.700, spare bits
are coded 0 unless indicated otherwise at the originating nodes. At
intermediate nodes, they are passed transparently. At destination nodes, 
they need not be examined. 
.RT
.sp 1P
.LP
1.10
	\fINational message types and parameters\fR 
.sp 9p
.RT
.PP
If message type codes and parameter codes are required for national uses, 
it is suggested that the codes be selected from the highest code 
downwards, that is starting at code\ 11111110. Code\ 11111111 is reserved for
future use.
.RT
.sp 2P
.LP
\fB2\fR 	\fBCoding of the general parts\fR 
.sp 1P
.RT
.sp 1P
.LP
2.1
	\fICoding of the message type\fR 
.sp 9p
.RT
.PP
The coding of the message is shown in Table\ 1/Q.713.
.RT
.sp 1P
.LP
2.2
	\fICoding of the length indicator\fR 
.sp 9p
.RT
.PP
The length indicator field is binary coded to indicate the number of octets 
in the parameter content field. The length indicator does not include the 
parameter name octet or the length indicator octet. 
.RT
.sp 1P
.LP
2.3
	\fICoding of the\fR 
\fIpointers\fR 
.sp 9p
.RT
.PP
The pointer value (in binary) gives the number of octets between
the pointer itself (included) and the first octet (not included) of the
parameter associated with that pointer
.FS
For example, a pointer value of
\*Q00000001\*U indicates that the associated parameter begins in the octet
immediately following the pointer. A pointer value of \*Q00001010\*U indicates 
that nine octets of information exist between the pointer octet and the 
first octet of the parameter associated with that pointer. 
.FE
.
.PP
The pointer value all zeros is used to indicate that, in the case of optional 
parameters, no optional parameter is present. 
.RT
.sp 2P
.LP
\fB3\fR 	\fBSCCP parameters\fR 
.sp 1P
.RT
.PP
The parameter name codes are given in Table\ 2/Q.713 with reference to 
the subsections in which they are described. 
.RT
.sp 1P
.LP
3.1
	\fIEnd of optional parameters\fR 
.sp 9p
.RT
.PP
The \*Qend of optional parameters\*U parameter field consists of a
single octet containing all zeros.
.RT
.sp 1P
.LP
3.2
	\fIDestination local reference\fR 
.sp 9p
.RT
.PP
The \*Qdestination local reference\*U parameter field is a three\(hyoctet 
field containing a reference number which, in outgoing messages, has been 
allocated to the connection section by the remote node.
.PP
The coding \*Qall ones\*U is reserved, its use is for further
study.
.bp
.RT
.ce
\fBH.T. [T2.713]\fR 
.ce
TABLE\ 1/Q.713
.ce
\fBSCCP message types\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(96p) | cw(18p) sw(18p) sw(18p) sw(18p) | cw(24p) | cw(36p) , ^  | c | c | c | c | ^ | ^ .
Message type	Classes	\(sc	Code
	0	1	2	3
_
.T&
lw(96p) | lw(18p) | lw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(36p) .
CR Connection Request			X	X	4.2\ 	0000\ 0001
_
.T&
lw(96p) | lw(18p) | lw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(36p) .
CC Connection Confirm			X	X	4.3\ 	0000\ 0010
_
.T&
lw(96p) | lw(18p) | lw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(36p) .
CREF Connection Refused			X	X	4.4\ 	0000\ 0011
_
.T&
lw(96p) | lw(18p) | lw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(36p) .
RLSD Released			X	X	4.5\ 	0000\ 0100
_
.T&
lw(96p) | lw(18p) | lw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(36p) .
RLC Release Complete			X	X	4.6\ 	0000\ 0101
_
.T&
lw(96p) | lw(18p) | lw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(36p) .
DT1 Data Form 1			X		4.7\ 	0000\ 0110
_
.T&
lw(96p) | lw(18p) | lw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(36p) .
DT2 Data Form 2				X	4.8\ 	0000\ 0111
_
.T&
lw(96p) | lw(18p) | lw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(36p) .
AK Data Acknowledgement				X	4.9\ 	0000\ 1000
_
.T&
lw(96p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(36p) .
UDT Unitdata	X	X			4.10	0000\ 1001
_
.T&
lw(96p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(36p) .
UDTS Unitdata Service	X	X			4.11	0000\ 1010
_
.T&
lw(96p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(36p) .
ED Expedited Data				X	4.12	0000\ 1011
_
.T&
lw(96p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(36p) .
 {
EA Expedited Data Acknowledgement
 }				X	4.13	0000\ 1100
_
.T&
lw(96p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(36p) .
RSR Reset Request				X	4.14	0000\ 1101
_
.T&
lw(96p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(36p) .
RSC Reset Confirm				X	4.15	0000\ 1110
_
.T&
lw(96p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(36p) .
ERR Protocol Data Unit Error			X	X	4.16	0000\ 1111
_
.T&
lw(96p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(24p) | cw(36p) .
IT Inactivity Test			X	X	4.17	0001\ 0000
.TE
.LP
X\ Type of message in this protocol class.
.nr PS 9
.RT
.ad r
\fBTableau 1/Q.713 [T2.713], p.5\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 7P
.ad r
Blanc
.ad b
.RT
.LP
.bp
.ce
\fBH.T. [T3.713]\fR 
.ce
TABLE\ 2/Q.713
.ce
\fBSCCP parameter name codes\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(114p) | cw(24p) | cw(42p) .
Parameter name	\(sc	 {
Parameter name code
8765\ 4321
 }
_
.T&
lw(114p) | cw(24p) | cw(42p) .
End of optional parameters	3.1\ 	0000\ 0000
_
.T&
lw(114p) | cw(24p) | cw(42p) .
Destination local reference	3.2\ 	0000\ 0001
_
.T&
lw(114p) | cw(24p) | cw(42p) .
Source local reference	3.3\ 	0000\ 0010
_
.T&
lw(114p) | cw(24p) | cw(42p) .
Called party address	3.4\ 	0000\ 0011
_
.T&
lw(114p) | cw(24p) | cw(42p) .
Calling party address	3.5\ 	0000\ 0100
_
.T&
lw(114p) | cw(24p) | cw(42p) .
Protocol class	3.6\ 	0000\ 0101
_
.T&
lw(114p) | cw(24p) | cw(42p) .
Segmenting/reassembling	3.7\ 	0000\ 0110
_
.T&
lw(114p) | cw(24p) | cw(42p) .
Receive sequence number	3.8\ 	0000\ 0111
_
.T&
lw(114p) | cw(24p) | cw(42p) .
Sequencing/segmenting	3.9\ 	0000\ 1000
_
.T&
lw(114p) | cw(24p) | cw(42p) .
Credit	3.10	0000\ 1001
_
.T&
lw(114p) | cw(24p) | cw(42p) .
Release cause	3.11	0000\ 1010
_
.T&
lw(114p) | cw(24p) | cw(42p) .
Return cause	3.12	0000\ 1011
_
.T&
lw(114p) | cw(24p) | cw(42p) .
Reset cause	3.13	0000\ 1100
_
.T&
lw(114p) | cw(24p) | cw(42p) .
Error cause	3.14	0000\ 1101
_
.T&
lw(114p) | cw(24p) | cw(42p) .
Refusal cause	3.15	0000\ 1110
_
.T&
lw(114p) | cw(24p) | cw(42p) .
Data	3.16	0000\ 1111
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau 2/Q.713 [T3.713], p.6\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 9P
.ad r
Blanc
.ad b
.RT
.LP
.bp
.sp 1P
.LP
3.3
	\fISource local reference\fR 
.sp 9p
.RT
.PP
The \*Qsource local reference\*U parameter field is a three\(hyoctet field 
containing a reference number which is generated and used by the local 
node to identify the connection section. 
.PP
The coding \*Qall ones\*U is reserved, its use is for further study.
.RT
.sp 1P
.LP
3.4
	\fICalled party address\fR 
.sp 9p
.RT
.PP
The \*Qcalled party address\*U is a variable length parameter. Its
structure is shown in Figure\ 3/Q.713.
.RT
.LP
.sp 1
.rs
.sp 15P
.ad r
\fBFigure 3/Q.713 [T4.713], p. \ \ 
(\*`a traiter comme tableau MEP)\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 2
.sp 1P
.LP
3.4.1
	\fIAddress indicator\fR 
.sp 9p
.RT
.PP
The \*Qaddress indicator\*U indicates the type of address information contained 
in the address field (see Figure\ 4/Q.713). The address consists of 
one or any combination of the following elements:
.RT
.LP
	\(em
	signalling point code;
.LP
	\(em
	global title (for instance, dialled digits);
.LP
	\(em
	subsystem number.
.LP
.sp 1
.rs
.sp 8P
.ad r
\fBFigure 4/Q.713 [T5.713], p. \ \ 
(\*`a traiter comme tableau MEP)\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.PP
A \*Q1\*U in bit 1 indicates that the address contains a signalling
point code.
.PP
A \*Q1\*U in bit\ 2 indicates that the address contains a subsystem
number.
.PP
Bits 3\(hy6 of the address indicator octet contain the global title
indicator, which is encoded as follows:
.RT
.LP
Full E.164 numbering plan address is used in these two cases for
Recommendation\ E.164 based global titles.
.FE
	Bits
	6\ 5\ 4\ 3
.LP
	0\ 0\ 0\ 0
	No global title included
.LP
	0\ 0\ 0\ 1
	Global title includes nature of address
indicator only
.LP
	0\ 0\ 1\ 0
	Global title includes translation type
only
.LP
	0\ 0\ 1\ 1
	Global title includes translation type,
numbering plan and encoding scheme
.LP
	0\ 1\ 0\ 0
	Global title includes translation type,
numbering plan, encoding scheme and nature of
address indicator
.LP
	0\ 1\ 0\ 1
	
.LP
	\ \  | o
		spare international
.LP
	0\ 1\ 1\ 1
	
.LP
	1\ 0\ 0\ 0
	
.LP
	\ \  | o
		spare national
.LP
	1\ 1\ 1\ 0
	
.LP
	1\ 1\ 1\ 1
	reserved for extension.
.PP
When a global title is used in the called party address, it is
suggested that the called party address contain a subsystem number. This 
serves to simplify message reformatting following global title translation. 
The 
subsystem number should be encoded \*Q00000000\*U when the subsystem number 
is not known, e.g.,\ before translation. 
.PP
Bit 7 of the address indicator octet contains routing information
identifying which address element should be used for routing.
.PP
A \*Q0\*U in bit 7 indicates that routing should be based on the global
title in the address.
.PP
A \*Q1\*U in bit 7 indicates that routing should be based on the
destination point code in the MTP routing label and the subsystem number
information in the called party address.
.PP
Bit 8 of the address indicator octet is designated for national
use.
.RT
.sp 1P
.LP
3.4.2
	\fIAddress\fR 
.sp 9p
.RT
.PP
The various elements, when provided, occur in the order: point
code, subsystem number, global title, as shown in Figure\ 5/Q.713.
.RT
.LP
.sp 2
.rs
.sp 11P
.ad r
\fBFigure 5/Q.713 [T6.713], p. \ \ 
(\*`a traiter comme tableau MEP)\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 3
.bp
.sp 1P
.LP
3.4.2.1
	\fISignalling point code\fR 
.sp 9p
.RT
.PP
The signalling point code, when provided, is represented by two
octets. Bits\ 7 and\ 8 in the second octet are set to zero (see
Figure\ 6/Q.713).
.RT
.LP
.sp 3
.rs
.sp 9P
.ad r
\fBFigure 6/Q.713 [T7.713], p. \ \ 
(\*`a traiter comme tableau MEP)\fR 
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
.sp 4
3.4.2.2
	\fISubsystem number\fR 
.sp 9p
.RT
.PP
The subsystem number (SSN) identifies an SCCP user function and,
when provided, consists of one octet coded as follows:
.RT
.LP
	Bits
	8\ 7\ 6\ 5\ 4\ 3\ 2\ 1
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 0\ 0
	SSN not known/not used
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 0\ 1
	SCCP management
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 1\ 0
	reserved for CCITT allocation
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 1\ 1
	ISDN user part
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 0\ 0
	OMAP
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 0\ 1
	MAP (Mobile Application Part)
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 1\ 0
	
.LP
	\ \ \ to
		spare
.LP
	1\ 1\ 1\ 1\ 1\ 1\ 1\ 0
	
.LP
	1\ 1\ 1\ 1\ 1\ 1\ 1\ 1
	reserved for expansion.
.PP
Network specific subsystem numbers should be assigned in
descending order starting with\ \*Q11111110\*U.
.sp 1P
.LP
3.4.2.3
	\fIGlobal title\fR  |
.FS
Incorporation of NSAP address in the SCCP
global title is for further study.
.FE
.sp 9p
.RT
.PP
The format of the global title is of variable length.
Figure\ 7/Q.913, Figure\ 9/Q.713, Figure\ 10/Q.713 and\ Figure 11/Q.713 
show four possible formats for global title. 
.RT
.LP
.sp 2
.bp
.sp 1P
.LP
3.4.2.3.1
	\fIGlobal title indicator = 0001\fR 
.sp 9p
.RT
.LP
.rs
.sp 10P
.ad r
\fBFigure 7/Q.713 [T8.713], p. \ \ 
(\*`a traiter comme tableau MEP)\fR 
.sp 1P
.RT
.ad b
.RT
.PP
Bits 1 to 7 of octet 1 contain the nature of address indicator and are 
coded as follows: 
.LP
	Bits
	7\ 6\ 5\ 4\ 3\ 2\ 1
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 0
	spare
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 1
	subscriber number
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 0
	reserved for national use
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 1
	national significant number
.LP
	0\ 0\ 0\ 0\ 1\ 0\ 0
	international number
.LP
	0\ 0\ 0\ 0\ 1\ 0\ 1
	
.LP
	\ \ \ to
		spare
.LP
	1\ 1\ 1\ 1\ 1\ 1\ 1
	
.PP
Bit 8 of octet 1 contains the odd/even indicator and is coded as   follows:
.LP
	Bit
	8
.LP
	0\ even number of address signals
.LP
	1\ odd number of address signals
.PP
The octets 2 and further contain a number of address signals and possibly 
a filler as shown in Figure\ 8/Q.713. 
.LP
.rs
.sp 20P
.ad r
\fBFigure 8/Q.713 [T9.713], p. \ \ 
(\*`a traiter comme tableau MEP)\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.PP
Each address signal is coded as follows:
.LP
The application of these codes in actual networks is for further
study.
.FE
.LP
	0000
	digit 0
.LP
	0001
	digit 1
.LP
	0010
	digit 2
.LP
	0011
	digit 3
.LP
	0100
	digit 4
.LP
	0101
	digit 5
.LP
	0110
	digit 6
.LP
	0111
	digit 7
.LP
	1000
	digit 8
.LP
	1001
	digit 9
.LP
	1010
	spare
.LP
	1011
	code 11
.LP
	1100
	code 12
.LP
	1101
	spare
.LP
	1110
	spare
.LP
	1111
	ST
.PP
In case of an odd number of address signals, a filler code 0000 is inserted 
after the last address signal. 
.sp 1P
.LP
3.4.2.3.2
	\fIGlobal title indicator = 0010\fR 
.sp 9p
.RT
.PP
Figure 9/Q.713 shows the format of the global title, if the global title 
indicator equals\ \*Q0010\*U. 
.RT
.LP
.sp 1
.rs
.sp 9P
.ad r
\fBFigure 9/Q.713 [T10.713], p. \ \ 
(\*`a traiter comme tableau MEP)\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 2
.PP
The translation type is a one\(hyoctet field that is used to direct the 
message to the appropriate global title translation function. 
.FS
A
translation type may for instance imply a specific service to be provided by
the SCCP user, such as free phone number translation, or identify the category 
of service to be provided, for example, dialed number screening, password 
validation or transmission of digits to telephone network address.
.FE
Thus, it may be possible for the address information to be translated into 
different values for and different combinations of DPCs, SSNs and GTs. 
.PP
This octet will be coded \*Q00000000\*U when not used. Translation types 
for internetwork services will be assigned in ascending order starting 
with\ 00000001\*U. Translation types for network specific services will be
assigned in descending order starting with\ \*Q11111110\*U. The code\ \*Q11111111\*U 
is reserved for expansion. However, the exact coding of translation types 
in the international network is for further study. Additional requirements 
may be 
placed on this field as a result of further work on Transaction Capabilities
and the ISDN User Part.
.PP
In the case of this global title format (0010), the translation type may 
also imply the encoding scheme, used to encode the address information, 
and the numbering plan. 
.RT
.LP
.sp 1
.bp
.sp 1P
.LP
3.4.2.3.3
	\fIGlobal title indicator = 0011\fR 
.sp 9p
.RT
.LP
.sp 3
.rs
.sp 12P
.ad r
\fBFigure 10/Q.713 [T11.713], p. \ \ 
(\*`a traiter comme tableau MEP)\fR 
.sp 1P
.RT
.ad b
.RT
.PP
.sp 4
The translation type is as described in \(sc\ 3.4.2.3.2.
.PP
The numbering plan is encoded as follows
.FS
The support of all
numbering plans is not mandatory.
.FE
:
.RT
.LP
	Bits
	8\ 7\ 6\ 5
.LP
	0\ 0\ 0\ 0
	unknown
.LP
	0\ 0\ 0\ 1
	ISDN/Telephony Numbering Plan
(Recommendations\ E.163 and\ E.164)
.LP
	0\ 0\ 1\ 0
	spare
.LP
	0\ 0\ 1\ 1
	Data Numbering Plan (Recommendation\ X.121)
.LP
	0\ 1\ 0\ 0
	Telex Numbering Plan (Recommendation\ F.69)
.LP
	0\ 1\ 0\ 1
	Maritime Mobile Numbering Plan
(Recommendations\ E.210,\ 211)
.LP
	0\ 1\ 1\ 0
	Land Mobile Numbering Plan
(Recommendation\ E.212)
.LP
	0\ 1\ 1\ 1
	ISDN/Mobile numbering plan
(Recommendation\ E.214)
.LP
	1\ 0\ 0\ 0
	
.LP
	\ \  | o
		spare
.LP
	1\ 1\ 1\ 0
	
.LP
	1\ 1\ 1\ 1
	reserved
.PP
The encoding scheme is encoded as follows:
.LP
	Bits
	4\ 3\ 2\ 1
.LP
	0\ 0\ 0\ 0
	unknown
.LP
	0\ 0\ 0\ 1
	BCD, odd number of digits
.LP
	0\ 0\ 1\ 0
	BCD, even number of digits
.LP
	0\ 0\ 1\ 1
	
.LP
	\ \  | o
		spare
.LP
	1\ 1\ 1\ 0
	
.LP
	1\ 1\ 1\ 1
	reserved.
.PP
If the encoding scheme is binary coded decimal, the global title value, 
starting from octet\ 3, is encoded as shown in Figure\ 8/Q.713. 
.LP
.sp 1
.bp
.sp 1P
.LP
3.4.2.3.4
	\fIGlobal title indicator = 0100\fR 
.sp 9p
.RT
.LP
.sp 4
.rs
.sp 14P
.ad r
\fBFigure 11/Q.713 [T12.713], p. \ \ 
(\*`a traiter comme tableau MEP)\fR 
.sp 1P
.RT
.ad b
.RT
.PP
.sp 5
The field \*Qtranslation type\*U is as described in \(sc\ 3.4.2.3.2. The 
fields \*Qnumbering plan\*U and \*Qencoding scheme\*U are as described 
in \(sc\ 3.4.2.3.3. The field \*Qnature of address indicator\*U is as described 
in \(sc\ 3.4.2.3.1. 
.PP
If the encoding scheme is binary coded decimal, the global title
value, starting from octet\ 4, is encoded as shown in Figure\ 8/Q.713.
.RT
.sp 1P
.LP
3.5
	\fICalling party address\fR 
.sp 9p
.RT
.PP
The \*Qcalling party address\*U is a variable length parameter. Its
structure is the same as the \*Qcalled party address\*U.
.PP
When the calling party address is a mandatory parameter but is not
available or must not be sent, the calling party address parameter only
consists of the address indicator octet, where bits\ 1 to\ 7 are coded all
zeros.
.RT
.sp 1P
.LP
3.6
	\fIProtocol class\fR 
.sp 9p
.RT
.PP
The \*Qprotocol class\*U parameter field is a four bit field
containing the protocol class.
.PP
Bits 1\(hy4 are coded as follows:
.RT
.LP
	4321
.LP
	0000
	class 0
.LP
	0001
	class 1
.LP
	0010
	class 2
.LP
	0011
	class 3
.PP
When bits 1\(hy4 are coded to indicate a connection\(hyoriented\(hyprotocol 
class (class\ 2, class\ 3), bits 5\(hy8 are spare. 
.bp
.PP
When bits 1\(hy4 are coded to indicate a connectionless protocol class
(class\ 0, class\ 1), bits 5\(hy8 are used to specify message handling as
follows:
.RT
.LP
	Bits
	8\ 7\ 6\ 5
.LP
	0\ 0\ 0\ 0
	no special options
.LP
	0\ 0\ 0\ 1
	
.LP
	\ \  | o
		spare
.LP
	0\ 1\ 1\ 1
	
.LP
	1\ 0\ 0\ 0
	return message on error
.LP
	1\ 0\ 0\ 1
	
.LP
	\ \  | o
		spare
.LP
	1\ 1\ 1\ 1
	
.sp 1P
.LP
3.7
	\fISegmenting/reassembling\fR 
.sp 9p
.RT
.PP
The \*Qsegmenting/reassembling\*U parameter field is a one octet field 
and is structured as follows: 
.RT
.LP
.sp 2
.ce
\fBH.T. [T13.713]\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(12p) | cw(12p) | cw(12p) | cw(12p) | cw(12p) | cw(12p) | cw(12p) | cw(12p) .
8	7	6	5	4	3	2	1
_
.T&
cw(84p) | cw(12p) .
reserve	M
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau [T13.713], p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 3
	Bits\ 8\(hy2 are spare.
.LP
	Bit\ 1 is used for the More Data indication and is coded as
follows:
.LP
	0\ =\ no more data
.LP
	1\ =\ more data
.sp 1P
.LP
3.8
	\fIReceive sequence number\fR 
.sp 9p
.RT
.PP
The \*Qreceive sequence number\*U parameter field is a one octet field 
and is structured as follows: 
.RT
.LP
.sp 2
.ce
\fBH.T. [T14.713]\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(12p) | cw(12p) | cw(12p) | cw(12p) | cw(12p) | cw(12p) | cw(12p) | cw(12p) .
8	7	6	5	4	3	2	1  
_
.T&
cw(84p) | cw(12p) .
P(R)	/
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau [T14.713], p.\fR 
.sp 1P
.RT
.ad b
.RT
.PP
.sp 5
Bits\ 8\(hy2 contain the receive sequence number\ P(R) used to indicate 
the sequence number of the next expected message. P(R) is binary coded 
and 
bit\ 2 is the\ LSB.
.PP
Bit\ 1 is spare.
.bp
.RT
.sp 1P
.LP
3.9
	\fISequencing/segmenting\fR 
.sp 9p
.RT
.PP
The sequencing/segmenting parameter field consists of two octets
and is structured as follows:
.RT
.ce
\fBH.T. [T15.713]\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(36p) | cw(12p) | cw(12p) | cw(12p) | cw(12p) | cw(12p) | cw(12p) | cw(12p) | lw(12p) .
8  	7	6	5	4	3	2	1  	
_
.T&
cw(36p) | cw(84p) | cw(12p) .
octet 1	P(S)	/
.T&
lw(96p) .
.T&
cw(36p) | cw(84p) | cw(12p) .
octet 2	P(R)	M
.T&
lw(96p) .
.TE
.nr PS 9
.RT
.ad r
\fBTableau [T15.713], p.\fR 
.sp 1P
.RT
.ad b
.RT
.PP
Bits 8\(hy2 of octet 1 are used for indicating the send sequence
number\ P(S). P(S) is binary coded and bit\ 2 is the\ LSB.
.PP
Bit 1 of octet 1 is spare.
.PP
Bits 8\(hy2 of octet 2 are used for indicating the receive sequence
number\ P(R). P(R) is binary coded and bit\ 2 is the\ LSB.
.PP
Bit 1 of octet 2 is used for the More Data indication and is coded
as follows:
.PP
0\ =\ no more data
.PP
1\ =\ more data
.PP
The sequencing/segmenting parameter field is used exclusively in
protocol class\ 3.
.RT
.sp 1P
.LP
3.10
	\fICredit\fR 
.sp 9p
.RT
.PP
The \*Qcredit\*U parameter field is a one\(hyoctet field used in the
protocol classes which include flow control functions. It contains the 
window size value coded in pure binary. 
.RT
.sp 1P
.LP
3.11
	\fIRelease cause\fR 
.sp 9p
.RT
.PP
The release cause parameter field is a one\(hyoctet field containing the 
reason for the release of the connection. 
.PP
The coding of the release cause field is as follows:
.RT
.LP
Subsystem congestion control procedure is for further study.
.FE
	Bits
	8\ 7\ 6\ 5\ 4\ 3\ 2\ 1
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 0\ 0
	end user originated
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 0\ 1
	end user congestion
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 1\ 0
	end user failure
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 1\ 1
	SCCP user originated
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 0\ 0
	remote procedure error
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 0\ 1
	inconsistent connection data
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 1\ 0
	access failure
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 1\ 1
	access congestion
.LP
	0\ 0\ 0\ 0\ 1\ 0\ 0\ 0
	subsystem failure
.LP
	0\ 0\ 0\ 0\ 1\ 0\ 0\ 1
	subsystem congestion
.LP
	0\ 0\ 0\ 0\ 1\ 0\ 1\ 0
	network failure
.LP
	0\ 0\ 0\ 0\ 1\ 0\ 1\ 1
	network congestion
.LP
	0\ 0\ 0\ 0\ 1\ 1\ 0\ 0
	expiration of reset timer
.LP
	0\ 0\ 0\ 0\ 1\ 1\ 0\ 1
	expiration of receive inactivity timer
.LP
	0\ 0\ 0\ 0\ 1\ 1\ 1\ 0
	not obtainable
.LP
	0\ 0\ 0\ 0\ 1\ 1\ 1\ 1
	unqualified
.LP
	0\ 0\ 0\ 1\ 0\ 0\ 0\ 0
	
.LP
	\ \ \ \  | o
		spare
.LP
	1\ 1\ 1\ 1\ 1\ 1\ 1\ 1
	
.PP
\fINote\fR \ \(em\ A more comprehensive list of causes covering X.96 call
progress information is for further study.
.bp
.sp 1P
.LP
3.12
	\fIReturn cause\fR 
.sp 9p
.RT
.PP
In the \fIUnitdata Service\fR message, the <<return cause>> parameter
field is a one octet field containing the reason for message return. Bits\ 
1\(hy8 are coded as follows: 
.RT
.LP
	Bits
	8\ 7\ 6\ 5\ 4\ 3\ 2\ 1
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 0\ 0 
	no translation for an address of such nature
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 0\ 1 
	no translation for this specific address
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 1\ 0 
	subsystem congestion
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 1\ 1 
	subsystem failure
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 0\ 0 
	unequipped user
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 0\ 1 
	network failure
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 1\ 0 
	network congestion
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 1\ 1 
	unqualified
.LP
	0\ 0\ 0\ 0\ 1\ 0\ 0\ 0
	
.LP
	\ \ \ \  | o
		spare
.LP
	1\ 1\ 1\ 1\ 1\ 1\ 1\ 1
	
.sp 1P
.LP
3.13
	\fIReset cause\fR 
.sp 9p
.RT
.PP
The \*Qreset cause\*U parameter field is a one octet field containing the 
reason for the resetting of the connection. 
.PP
The coding of the reset cause field is as follows:
.RT
.LP
	Bits
	8\ 7\ 6\ 5\ 4\ 3\ 2\ 1
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 0\ 0 
	end user originated
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 0\ 1 
	SCCP user originated
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 1\ 0 
	message out of order\ \(em\ incorrect P(S)
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 1\ 1 
	message out of order\ \(em\ incorrect P(R)
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 0\ 0 
	remote procedure error\ \(em\ message out of
window
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 0\ 1 
	remote procedure error\ \(em\ incorrect P(S) after  (re)initialization
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 1\ 0 
	remote procedure error\ \(em\ general
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 1\ 1 
	remote end user operational
.LP
	0\ 0\ 0\ 0\ 1\ 0\ 0\ 0 
	network operational
.LP
	0\ 0\ 0\ 0\ 1\ 0\ 0\ 1 
	access operational
.LP
	0\ 0\ 0\ 0\ 1\ 0\ 1\ 0 
	network congestion
.LP
	0\ 0\ 0\ 0\ 1\ 0\ 1\ 1 
	not obtainable
.LP
	0\ 0\ 0\ 0\ 1\ 1\ 0\ 0 
	unqualified
.LP
	0\ 0\ 0\ 0\ 1\ 1\ 0\ 1
	
.LP
	\ \ \ \  | o
		spare
.LP
	1\ 1\ 1\ 1\ 1\ 1\ 1\ 1
	
.sp 1P
.LP
3.14
	\fIError cause\fR 
.sp 9p
.RT
.PP
The \*Qerror cause\*U parameter field is a one octet field containing the 
indication of the exact protocol error. 
.PP
The coding of the error cause field is as follows:
.RT
.LP
	Bits 
	8\ 7\ 6\ 5\ 4\ 3\ 2\ 1
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 0\ 0 
	local reference number (LRN)
mismatch\ \(em\ unassigned destination LRN
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 0\ 1 
	local reference number (LRN)
mismatch\ \(em\ inconsistent source LRN
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 1\ 0 
	point code mismatch
.FS
National option.
.FE
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 1\ 1 
	service class mismatch
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 0\ 0 
	unqualified
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 0\ 1
	
.LP
	\ \ \ \  | o
		spare
.LP
	1\ 1\ 1\ 1\ 1\ 1\ 1\ 1
	
.LP
.sp 1
.bp
.sp 1P
.LP
3.15
	\fIRefusal cause\fR 
.sp 9p
.RT
.PP
The refusal cause parameter field is a one octet field containing the reason 
for the refusal of the connection. 
.PP
The coding of the refusal cause field is as follows:
.RT
.LP
	Bits 
	8\ 7\ 6\ 5\ 4\ 3\ 2\ 1
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 0\ 0 
	end user originated
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 0\ 1 
	end user congestion
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 1\ 0 
	end user failure
.LP
	0\ 0\ 0\ 0\ 0\ 0\ 1\ 1 
	SCCP user originated
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 0\ 0 
	destination address unknown
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 0\ 1 
	destination inaccessible
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 1\ 0 
	network resource\ \(em\ QOS not
available/non\(hytransient
.LP
	0\ 0\ 0\ 0\ 0\ 1\ 1\ 1 
	network resource\ \(em\ QOS not
available/transient
.LP
	0\ 0\ 0\ 0\ 1\ 0\ 0\ 0 
	access failure
.LP
	0\ 0\ 0\ 0\ 1\ 0\ 0\ 1 
	access congestion
.LP
	0\ 0\ 0\ 0\ 1\ 0\ 1\ 0 
	subsystem failure
.LP
	0\ 0\ 0\ 0\ 1\ 0\ 1\ 1 
	subsystem congestion
.LP
	0\ 0\ 0\ 0\ 1\ 1\ 0\ 0 
	expiration of the connection establishment
timer
.LP
	0\ 0\ 0\ 0\ 1\ 1\ 0\ 1 
	incompatible user data
.LP
	0\ 0\ 0\ 0\ 1\ 1\ 1\ 0 
	not obtainable
.LP
	0\ 0\ 0\ 0\ 1\ 1\ 1\ 1 
	unqualified
.LP
	0\ 0\ 0\ 1\ 0\ 0\ 0\ 0
	
.LP
	\ \ \ \  | o
		spare
.LP
	1\ 1\ 1\ 1\ 1\ 1\ 1\ 1
	
.PP
\fINote\ 1\fR \ \(em\ The inclusion of the routing failure causes as
specified for the \*Qreturn cause\*U parameter in Recommendation\ Q.713, 
\(sc\ 3.12, is for further study. 
.PP
\fINote\ 2\fR \ \(em\ A more comprehensive list of causes covering CCITT
Recommendation\ X.96 call progress information is for further study.
.RT
.sp 1P
.LP
3.16
	\fIData\fR 
.sp 9p
.RT
.PP
The \*Qdata\*U parameter field is a variable length field containing
SCCP\(hyuser data to be transferred transparently between the SCCP user
functions.
.RT
.LP
\fB4\fR 	\fBSCCP messages and codes\fR 
.sp 1P
.RT
.sp 2P
.LP
4.1
	\fIGeneral\fR 
.sp 1P
.RT
.PP
4.1.1
In the following sections, the format and coding of the SCCP
messages is specified.
.sp 9p
.RT
.PP
For each message a list of the relevant parameters is given in a tabular 
form. 
.PP
4.1.2
For each parameter the table also includes:
.sp 9p
.RT
.LP
	\(em
	 \fIa reference\fR  | o the section where the formatting and coding of 
the parameter content is specified; 
.LP
	\(em
	\fIthe type\fR  | f the parameter. The following types are used in the tables:
.LP
	F
	=\ mandatory fixed length parameter;
.LP
	V
	=\ mandatory variable length parameter;
.LP
	O
	=\ optional parameter of fixed or variable length;
.LP
	\(em
	\fIthe length\fR  | f the parameter. The value in the table
includes:
.LP
	\(em
	 \fIfor type F parameters\fR  | he length, in octets, of the parameter 
content; 
.LP
	\(em
	 \fIfor type V parameters\fR  | he length, in octets, of the length indicator 
and of the parameter content; (The minimum and the maximum 
length are indicated.)
.LP
	\(em
	 \fIfor type O parameters\fR  | he length, in octets, of the parameter 
name, length indicator and parameter content. (For variable length 
parameters the minimum and maximum length is indicated.)
.bp
.PP
4.1.3
For each message the number of pointers included is also
specified.
.sp 9p
.RT
.PP
4.1.4
For each message type, type F parameters and the pointers for the type\ 
V parameters must be sent in the order specified in the following 
tables.
.sp 1P
.LP
4.2
	\fIConnection request (CR)\fR 
.sp 9p
.RT
.PP
The CR message contains:
.RT
.LP
	\(em
	the routing label,
.LP
	\(em
	2 pointers,
.LP
	\(em
	the parameters indicated in Table\ 3/Q.713.
.sp 1P
.LP
4.3
	\fIConnection confirm (CC)\fR 
.sp 9p
.RT
.PP
The CC message contains:
.RT
.LP
	\(em
	the routing label,
.LP
	\(em
	1 pointer,
.LP
	\(em
	the parameters indicated in Table\ 4/Q.713.
.sp 1P
.LP
4.4
	\fIConnection refused (CREF)\fR 
.sp 9p
.RT
.PP
The message contains:
.RT
.LP
	\(em
	the routing label,
.LP
	\(em
	1 pointer,
.LP
	\(em
	the parameters indicated in Table\ 5/Q.713.
.sp 1P
.LP
4.5
	\fIReleased (RLSD)\fR 
.sp 9p
.RT
.PP
The RLSD message contains:
.RT
.LP
	\(em
	the routing label,
.LP
	\(em
	1 pointer,
.LP
	\(em
	the parameters indicated in Table\ 6/Q.713.
.sp 1P
.LP
4.6
	\fIRelease complete (RLC)\fR 
.sp 9p
.RT
.PP
The RLC message contains:
.RT
.LP
	\(em
	the routing label,
.LP
	\(em
	no pointers,
.LP
	\(em
	the parameters indicated in Table\ 7/Q.713.
.sp 1P
.LP
4.7
	\fIData form\ 1 (DT1)\fR 
.sp 9p
.RT
.PP
The DT1 message contains:
.RT
.LP
	\(em
	the routing label,
.LP
	\(em
	1 pointer,
.LP
	\(em
	the parameters indicated in Table\ 8/Q.713.
.sp 1P
.LP
4.8
	\fIData form\ 2 (DT2)\fR 
.sp 9p
.RT
.PP
The DT2 message contains:
.RT
.LP
	\(em
	the routing label,
.LP
	\(em
	1 pointer,
.LP
	\(em
	the parameters indicated in Table\ 9/Q.713.
.bp
.ce
\fBH.T. [T16.713]\fR 
.ce
TABLE\ 3/Q.713
.ce
\fBMessage type: Connection request\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(36p) | cw(36p) | cw(36p) .
Parameter	\(sc	Type (F V O)	Length (octets)
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Message type code	2.1\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Source local reference	3.3\ 	F	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Protocol class	3.6\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Called party address	3.4\ 	V	3 minimum
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Credit	3.10	O	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Calling party address	3.5\ 	O	4 minimum
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Data	3.16	O	3 | (hy | 30
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
End of optional parameters	3.1\ 	O	1
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau 3/Q.713 [T16.713], p.19\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 2
.ce
H.T. [T17.713]\fR 
.ce
TABLE\ 4/Q.713
.ce
\fBMessage type: Connection confirm\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(36p) | cw(36p) | cw(36p) .
Parameter	\(sc	Type (F V O)	Length (octets)
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Message type	2.1\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Destination local reference	3.2\ 	F	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Source local reference	3.3\ 	F	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Protocol class	3.6\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Credit	3.10	O	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Called party address	3.4\ 	O	4 minimum
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Data	3.16	O	3 | (hy | 30
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
End of optional parameter	3.1\ 	O	1
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau 4/Q.713 [T17.713], p.20\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.ce
\fBH.T. [T18.713]\fR 
.ce
TABLE\ 5/Q.713
.ce
\fBMessage type: Connection refused\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(36p) | cw(36p) | cw(36p) .
Parameter	\(sc	Type (F V O)	Length (octets)
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Message type	2.1\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Destination local reference	3.2\ 	F	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Refusal cause	3.15	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Called party address	3.4\ 	O	4 minimum
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Data	3.16	O	3 | (hy | 30
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
End of optional parameter	3.1\ 	O	1
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau 5/Q.713 [T18.713], p.21\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 5
.ce
\fBH.T. [T19.713]\fR 
.ce
TABLE\ 6/Q.713
.ce
\fBMessage type: Released\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(36p) | cw(36p) | cw(36p) .
Parameter	\(sc	Type (F V O)	Length (octets)
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Message type	2.1\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Destination local reference	3.2\ 	F	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Source local reference	3.3\ 	F	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Release cause	3.11	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Data	3.16	O	3 | (hy | 30
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
End of optional parameter	3.1\ 	O	1
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau 6/Q.713 [T19.713], p.22\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 5P
.ad r
Blanc
.ad b
.RT
.LP
.bp
.ce
\fBH.T. [T20.713]\fR 
.ce
TABLE\ 7/Q.713
.ce
\fBMessage type: Release complete\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(36p) | cw(36p) | cw(36p) .
Parameter	\(sc	Type (F V O)	Length (octets)
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Message type	2.1	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Destination local reference	3.2	F	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Source local reference	3.3	F	3
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau 7/Q.713 [T20.713], p.23\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 1
.ce
\fBH.T. [T21.713]\fR 
.ce
TABLE\ 8/Q.713
.ce
\fBMessage type: Data form 1\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(36p) | cw(36p) | cw(36p) .
Parameter	\(sc	Type (F V O)	Length (octets)
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Message type	2.1\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Destination local reference	3.2\ 	F	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Segmenting/reassembling	3.7\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Data	3.16	V	2 | (hy | 56
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau 8/Q.713 [T21.713], p.24\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 1
.ce
\fBH.T. [T22.713]\fR 
.ce
TABLE\ 9/Q.713
.ce
\fBMessage type: Data form 2\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(36p) | cw(36p) | cw(36p) .
Parameter	\(sc	Type (F V O)	Length (octets)
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Message type	2.1\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Destination local reference	3.2\ 	F	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Sequencing/Segmenting	3.9\ 	F	2
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Data	3.16	V	2 | (hy | 56
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 9/Q.713 [T22.713], p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
4.9
	\fIData acknowledgement (AK)\fR 
.sp 9p
.RT
.PP
The AK message contains:
.RT
.LP
	\(em
	the routing label,
.LP
	\(em
	no pointers,
.LP
	\(em
	the parameters indicated in Table\ 10/Q.713.
.ce
\fBH.T. [T23.713]\fR 
.ce
TABLE\ 10/Q.713
.ce
\fBMessage type: Data acknowledgement\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(36p) | cw(36p) | cw(36p) .
Parameter	\(sc	Type (F V O)	Length (octets)
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Message type	2.1\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Destination local reference	3.2\ 	F	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Receive sequence number	3.8\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Credit	3.10	F	1
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 10/Q.713 [T23.713], p.\fR 
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
4.10
	\fIUnitdata (UDT)\fR 
.sp 9p
.RT
.PP
The UDT message contains:
.RT
.LP
	\(em
	the routing label,
.LP
	\(em
	3 pointers,
.LP
	\(em
	the parameters indicated in Table\ 11/Q.713.
.ce
\fBH.T. [T24.713]\fR 
.ce
TABLE\ 11/Q.713
.ce
\fBMessage type: Unitdata\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(36p) | cw(36p) | cw(36p) .
Parameter	\(sc	Type (F V O)	Length (octets)
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Message type	2.1\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Protocol class	3.6\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Called party address	3.4\ 	V	3 minimum
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Calling party address	3.5\ 	V	2 minimum
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Data	3.16	V	2 | (hy |  | ua\d\u)\d
.TE
.LP
\ua\d\u)\d
Due to the ongoing studies on the SCCP called and calling party
address, the maximum length of this parameter needs further study. It is also noted that the transfer of up to 255\ octets of user data is allowed when the
SCCP called and calling party address do not include global title.
.nr PS 9
.RT
.ad r
\fBTable 11/Q.713 [T24.713], p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
4.11
	\fIUnitdata service (UDTS)\fR 
.sp 9p
.RT
.PP
The UDTS message contains:
.RT
.LP
	\(em
	the routing label,
.LP
	\(em
	3 pointers,
.LP
	\(em
	the parameters indicated in Table\ 12/Q.713.
.LP
.sp 1
.ce
\fBH.T. [T25.713]\fR 
.ce
TABLE\ 12/Q.713
.ce
\fBMessage type: Unitdata service\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(36p) | cw(36p) | cw(36p) .
Parameter	\(sc	Type (F V O)	Length (octets)
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Message type	2.1\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Return cause	3.12	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Called party address	3.4\ 	V	3 minimum
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Calling party address	3.5\ 	V	2 minimum
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Data	3.16	V	2 | (hy |  | ua\d\u)\d
.TE
.LP
\ua\d\u)\d
See \ua\d\u)\d Table 11/Q.713.
.nr PS 9
.RT
.ad r
\fBTable 12/Q.713 [T25.713], p.\fR 
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
.sp 2
4.12
	\fIExpedited data (ED)\fR 
.sp 9p
.RT
.PP
The ED message contains:
.RT
.LP
	\(em
	the routing label,
.LP
	\(em
	1 pointer,
.LP
	\(em
	the parameters indicated in Table\ 13/Q.713.
.LP
.sp 1
.ce
\fBH.T. [T26.713]\fR 
.ce
TABLE\ 13/Q.713
.ce
\fBMessage type: Expedited data\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(36p) | cw(36p) | cw(36p) .
Parameter	\(sc	Type (F V O)	Length (octets)
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Message type	2.1\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Destination local reference	3.2\ 	F	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Data	3.16	V	2 | (hy | 3
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 13/Q.713 [T26.713], p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
4.13
	\fIExpedited data acknowledgement (EA)\fR 
.sp 9p
.RT
.PP
The EA message contains:
.RT
.LP
	\(em
	the routing label,
.LP
	\(em
	no pointers,
.LP
	\(em
	the parameters indicated in Table\ 14/Q.713.
.LP
.sp 3
.ce
\fBH.T. [T27.713]\fR 
.ce
TABLE\ 14/Q.713
.ce
\fBMessage type: Expedited data acknowledgement\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(36p) | cw(36p) | cw(36p) .
Parameter	\(sc	Type (F V O)	Length (octets)
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Message type	2.1	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Destination local reference	3.2	F	3
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 14/Q.713 [T27.713], p.\fR 
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
.sp 5
4.14
	\fIReset request (RSR)\fR 
.sp 9p
.RT
.PP
The RSR message contains:
.RT
.LP
	\(em
	the routing label,
.LP
	\(em
	1 pointer,
.LP
	\(em
	the parameters indicated in Table\ 15/Q.713.
.LP
.sp 3
.ce
\fBH.T. [T28.713]\fR 
.ce
TABLE\ 15/Q.713
.ce
\fBMessage type: Reset request\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(36p) | cw(36p) | cw(36p) .
Parameter	\(sc	Type (F V O)	Length (octets)
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Message type	2.1\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Destination local reference	3.2\ 	F	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Source local reference	3.3\ 	F	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Reset cause	3.13	F	1
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 15/Q.713 [T28.713], p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
4.15
	\fIReset confirm (RSC)\fR 
.sp 9p
.RT
.PP
The RSC message contains:
.RT
.LP
	\(em
	the routing label,
.LP
	\(em
	no pointers,
.LP
	\(em
	the parameters indicated in Table\ 16/Q.713.
.LP
.sp 3
.ce
\fBH.T. [T29.713]\fR 
.ce
TABLE\ 16/Q.713
.ce
\fBMessage type: Reset confirmation\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(36p) | cw(36p) | cw(36p) .
Parameter	\(sc	Type (F V O)	Length (octets)
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Message type	2.1	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Destination local reference	3.2	F	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Source local reference	3.3	F	3
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 16/Q.713 [T29.713], p.\fR 
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
.sp 4
4.16
	\fIProtocol data unit error (ERR)\fR 
.sp 9p
.RT
.PP
The ERR message contains:
.RT
.LP
	\(em
	the routing label,
.LP
	\(em
	1 pointer,
.LP
	\(em
	the parameters indicated in Table\ 17/Q.713.
.LP
.sp 3
.ce
\fBH.T. [T30.713]\fR 
.ce
TABLE\ 17/Q.713
.ce
\fBMessage type: Protocol data unit error\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(36p) | cw(36p) | cw(36p) .
Parameter	\(sc	Type (F V O)	Length (octets)
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Message type	2.1\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Destination local reference	3.2\ 	F	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Error cause	3.14	F	1  
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 17/Q.713 [T30.713], p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
4.17
	\fIInactivity test (IT)\fR 
.sp 9p
.RT
.PP
The IT message contains:
.RT
.LP
	\(em
	the routing label,
.LP
	\(em
	no pointers,
.LP
	\(em
	the parameters indicated in Table\ 18/Q.713.
.LP
.sp 4
.ce
\fBH.T. [T31.713]\fR 
.ce
TABLE\ 18/Q.713
.ce
\fBMessage type: Inactivity test\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(36p) | cw(36p) | cw(36p) .
Parameter	\(sc	Type (F V O)	Length (octets)
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Message type	2.1\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Destination local reference	3.2\ 	F	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Source local reference	3.3\ 	F	3
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Protocol class	3.6\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
 {
Sequencing/segmenting | ua\d\u)\d
 }	3.9\ 	F	2
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Credit | ua\d\u)\d	3.10	F	1
.TE
.LP
\ua\d\u)\d
Information in these parameter fields reflect those values sent in the last data Form 2 or Data acknowledgement message. They are ignored if the protocol class parameter indicates class\ 2.
.nr PS 9
.RT
.ad r
\fBTable 18/Q.713 [T31.713], p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 5
.sp 2P
.LP
\fB5\fR 	\fBSCCP Management messages and codes\fR 
.sp 1P
.RT
.sp 1P
.LP
5.1
	\fIGeneral\fR 
.sp 9p
.RT
.PP
SCCP Management (SCMG) messages
are carried using the
connectionless service of the SCCP. When transferring SCMG messages, class\ 
0 is requested with the \*Qdiscard message on error\*U option. SCCP management 
message parts are provided in the \*Qdata\*U parameter of the \fIUnitdata 
message\fR . 
.PP
The \fIUnitdata\fR message contains:
.RT
.LP
	\(em
	the routing label,
.LP
	\(em
	3 pointers,
.LP
	\(em
	the parameters indicated in Table 19/Q.713.
.PP
Descriptions of the various parts are contained in the following   sections.
.bp
.ce
\fBH.T. [T32.713]\fR 
.ce
TABLE\ 19/Q.713
.ce
\fBSCCP management message format\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(36p) | cw(36p) | cw(36p) .
Parameter	\(sc	Type (F V O)	Length (octets)
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Message type  (= Unitdata)	2.1\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
 {
Protocol class
(= Class 0, no return)
 }	3.6\ 	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
 {
Called party address
(SSN = SCCP management)
 }	3.4\ 	V	3 minimum
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
 {
Calling party address
(SSN = SCCP management)
 }	3.5\ 	V	3 minimum | ua\d\u)\d
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
 {
Data
(Data consists of an SCMG message with form as in
Table\ 22/Q.713)
 }	3.16	V	6
.TE
.LP
\ua\d\u)\d\ SSN is always present.
.nr PS 9
.RT
.ad r
\fBTable 19/Q.713 [T32.713], p.\fR 
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
.sp 1
5.1.1
	\fISCMG format identifier\fR 
.sp 9p
.RT
.PP
The SCMG format identifier consists of a one\(hyoctet field, which is mandatory 
for all SCMG messages. The SCMG format identifier uniquely defines 
the function and format of each SCMG message. The allocation of SCMG format
identifiers is shown in Table\ 20/Q.713.
.RT
.LP
.sp 1
.ce
\fBH.T. [T33.713]\fR 
.ce
TABLE\ 20/Q.713
.ce
\fBSCMG format identifiers\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(108p) | cw(42p) .
Message	Code  87654321
_
.T&
lw(108p) | cw(42p) .
SSA Subsystem\(hyAllowed	00000001
_
.T&
lw(108p) | cw(42p) .
SSP Subsystem\(hyProhibited	00000010
_
.T&
lw(108p) | cw(42p) .
 {
SST Subsystem\(hyStatus\(hyTest
 }	00000011
_
.T&
lw(108p) | cw(42p) .
 {
SOR Subsystem\(hyOut\(hyof\(hyService\(hyRequest
 }	00000100
_
.T&
lw(108p) | cw(42p) .
 {
SOG Subsystem\(hyOut\(hyof\(hyService\(hyGrant
 }	00000101
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 20/Q.713 [T33.713], p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
5.1.2
	\fIFormatting principles\fR 
.sp 9p
.RT
.PP
The formatting principles used for SCCP messages, as described in \(sc\(sc\ 
1.3, 1.4, 1.5, 1.6, 2.2 and\ 2.3 apply to SCMG messages. 
.RT
.sp 1P
.LP
5.2
	\fISCMG message parameters\fR 
.sp 9p
.RT
.PP
SCMG parameter name codes are given in Table 21/Q.713 with
reference to the subsections in which they are described. Presently, these
parameter name codes are not used since all SCMG messages contain mandatory
fixed parameters only.
.RT
.ce
\fBH.T. [T34.713]\fR 
.ce
TABLE\ 21/Q.713
.ce
\fBSCMG parameter name codes\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(108p) | cw(24p) | cw(48p) .
Parameter name	\(sc	Parameter name code 87654321
_
.T&
lw(108p) | cw(24p) | cw(48p) .
End of optional parameters	5.2.1	00000000
_
.T&
lw(108p) | cw(24p) | cw(48p) .
Affected SSN	5.2.2	00000001
_
.T&
lw(108p) | cw(24p) | cw(48p) .
Affected PC	5.2.3	00000010
_
.T&
lw(108p) | cw(24p) | cw(48p) .
 {
Subsystem multiplicity indicator
 }	5.2.4	00000011
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 21/Q.713 [T34.713], p.\fR 
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
5.2.1
	\fIEnd of optional parameters\fR 
.sp 9p
.RT
.PP
The \*Qend of optional parameters\*U parameter field consists of a
single octet containing all zeros.
.RT
.sp 1P
.LP
5.2.2
	\fIAffected SSN\fR 
.sp 9p
.RT
.PP
The \*Qaffected subsystem number (SSN)\*U parameter field consists of one 
octet coded as directed for the called party address field, 
\(sc\ 3.4.2.1.
.RT
.sp 1P
.LP
5.2.3
	\fIAffected PC\fR 
.sp 9p
.RT
.PP
The \*Qaffected signalling point code (PC)\*U parameter field is
represented by two octets which are coded as directed for the called party
address field, \(sc\ 3.4.2.2.
.RT
.sp 1P
.LP
5.2.4
	\fISubsystem multiplicity indicator\fR 
.sp 9p
.RT
.PP
The \*Qsubsystem multiplicity indicator\*U parameter field consists of 
one octet coded as shown in Figure\ 12/Q.713. 
.RT
.LP
.rs
.sp 7P
.ad r
\fBFigura 12/Q.713 [T35.713], p. \ \ 
(\*`a traiter comme tableau MEP)\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.PP
The coding of the SMI field is as follows:
.LP
	Bits
	21
.LP
	00 
	affected subsystem multiplicity unknown
.LP
	01 
	affected subsystem is solitary
.LP
	10 
	affected subsystem is duplicated
.LP
	11 
	spare
.PP
Bits 3\(hy8 are spare.
.sp 1P
.LP
5.3
	\fISCMG messages\fR 
.sp 9p
.RT
.PP
Presently, all SCMG messages contain mandatory fixed parameters
only. Each SCMG message contains:
.RT
.LP
	\(em
	0 pointers
.LP
	\(em
	the parameters indicated in Table\ 22/Q.713.
.ce
\fBH.T. [T36.713]\fR 
.ce
TABLE\ 22/Q.713
.ce
\fBSCMG Message\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(36p) | cw(36p) | cw(36p) .
Parameter	\(sc	Type (F V O)	Length  (octets)
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
 {
SCMG format identifier
(Message type code)
 }	5.1.1	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Affected SSN	5.2.2	F	1
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
Affected PC	5.2.3	F	2
_
.T&
lw(84p) | cw(36p) | cw(36p) | cw(36p) .
 {
Subsystem multiplicity indicator
 }	5.2.4	F	1
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 22/Q.713 [T36.713], p.\fR 
.sp 1P
.RT
.ad b
.RT
.ce 1000
ANNEX\ A
.ce 0
.ce 1000
(to Recommendation Q.713)
.sp 9p
.RT
.ce 0
.ce 1000
\fBMapping for cause parameter values\fR 
.sp 1P
.RT
.ce 0
.LP
A.1
	\fIIntroduction\fR 
.sp 1P
.RT
.PP
During connection refusal/release/reset, the SCCP and its users
could take necessary corrective actions, if any, only upon relevant information 
available to them. Thus, it would be very helpful if those information 
could be conveyed correctly. 
.PP
During connection release, the \*Qrelease cause\*U parameter in the
\fIReleased\fR (RLSD) message and the N\(hyDISCONNECT primitive (with parameters 
\*Qoriginator\*U and \*Qreason\*U) are used together to convey those information 
on the initiator and the cause of the connection release. In addition, 
the 
N\(hyDISCONNECT primitive is also used together with the \*Qrefusal cause\*U 
parameter 
.PP
in the \fIConnection Refused\fR (CREF) message to convey those information 
during connection refusal. During connection reset, the \*Qreset cause\*U 
parameter in the \fIReset Request\fR (RSR) message and the N\(hyRESET primitive 
(with parameters 
\*Qoriginator\*U and \*Qreason\*U) are used together similarly.
.bp
.PP
In order to convey those information correctly, this Annex provides a guideline 
for the mapping of values between the cause parameters and the 
corresponding N\(hyprimitive parameters during various scenarios.
.RT
.sp 1P
.LP
A.2
	\fIConnection refusal\fR 
.sp 9p
.RT
.PP
Table A\(hy1/Q.713 describes the mapping of values between the
\*Qrefusal cause\*U parameter (\(sc\ 3.15, Rec.\ Q.713) and the \*Qoriginator\*U, 
\*Qreason\*U parameters in the N\(hyDISCONNECT primitive (\(sc\ 2.1.1.2.4, 
Rec.\ Q.711). 
.RT
.sp 1P
.LP
A.3
	\fIConnection release\fR 
.sp 9p
.RT
.PP
Table A\(hy2/Q.713 describes the mapping of values between the
\*Qrelease cause\*U parameter (\(sc\ 3.11, Rec.\ Q.713) and the \*Qoriginator\*U, 
\*Qreason\*U parameters in the N\(hyDISCONNECT primitive (\(sc\ 2.1.1.2.4, 
Rec.\ Q.711). 
.RT
.sp 1P
.LP
A.4
	\fIConnection reset\fR 
.sp 9p
.RT
.PP
Table A\(hy3/Q.713 describes the mapping of values between the \*Qreset 
cause\*U parameter (\(sc\ 3.13, Rec.\ Q.713) and the \*Qoriginator\*U, 
\*Qreason\*U parameters in the N\(hyRESET primitive (\(sc\ 2.1.1.2.3, Rec.\ 
Q.711). 
.RT
.LP
.rs
.sp 33P
.ad r
Blanc
.ad b
.RT
.LP
.bp
.ce
\fBH.T. [T37.713]\fR 
.ce
TABLE\ A\(hy1/Q.713
.ce
\fBMapping during connection refusal\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(30p) sw(84p) | cw(84p) sw(30p) , c | c | c | c.
CREF Message	N\(hyDISCONNECT primitive
Code	Refusal cause	Reason	Originator
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000000	end user originated	 {
connection refusal \(em end user originated
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000001	end user congestion	 {
connection refusal \(em end user congestion
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000010	end user failure	 {
connection refusal \(em end user failure
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000011	SCCP user originated	 {
connection refusal \(em SCCP user originated
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000100	destination address unknown	 {
connection refusal \(em destination address unknown (non\(hytransient
condition)
 }	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000101	destination inaccessible	 {
connection refusal \(em destination inaccessible/transient condition
 }	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000110	 {
network resource \(em QOS unavailable/non\(hytransient
 }	 {
connection refusal \(em QOS unavailable/non\(hytransient condition
 }	NSP | ua\d\u)\d
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000111	 {
network resource \(em QOS unavailable/transient
 }	 {
connection refusal \(em QOS unavailable/transient condition
 }	NSP | ua\d\u)\d
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001000	access failure	 {
connection refusal \(em access failure
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001001	access congestion	 {
connection refusal \(em access congestion
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001010	subsystem failure	 {
connection refusal \(em destination inaccessible/non\(hytransient condition
 }	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001011	subsystem congestion	 {
connection refusal \(em subsystem congestion
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001100	 {
expiration of connection estimated timer
 }	 {
connection refusal \(em reason unspecified/transient
 }	NSP | ua\d\u)\d
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001101	inconsistent user data	 {
connection refusal \(em incompatible information in NSDU
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001110	not obtainable	 {
connection refusal \(em reason unspecified/transient
 }	NSP | ua\d\u)\d
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001110	not obtainable	 {
connection refusal \(em undefined
 }	undefined
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001111	unqualified	 {
connection refusal \(em reason unspecified/transient
 }	NSP | ua\d\u)\d
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001111	unqualified	 {
connection refusal \(em undefined
 }	undefined
.TE
.LP
NSU
Network Service User
.LP
NSP
Network Service Provider
.LP
\ua\d\u)\d
Only those cases will be applicable if the SCCP originates the
refusal procedure in response to REQUEST interface element.
.nr PS 9
.RT
.ad r
\fBTableau A\(hy1/Q.713 [T37.713], p.40\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.ce
\fBH.T. [T38.713]\fR 
.ce
TABLE\ A\(hy2/Q.713
.ce
\fBMapping during connection release\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(30p) sw(84p) | cw(84p) sw(30p) , c | c | c | c.
RLSD Message	N\(hyDISCONNECT primitive
Code	Release cause	Reason	Originator
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000000	end user originated	 {
disconnection \(em normal condition
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000001	end user congestion	 {
disconnection \(em end user congestion
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000010	end user failure	 {
disconnection \(em end user failure
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000011	SCCP user originated	 {
disconnection \(em SCCP user originated
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000100	remote procedure error	 {
disconnection \(em abnormal condition of transient nature
 }	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000101	inconsistent connection data	 {
disconnection \(em abnormal condition of transient nature
 }	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000110	access failure	 {
disconnection \(em access failure
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000111	access congestion	 {
disconnection \(em access congestion
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001000	subsystem failure	 {
disconnection \(em abnormal condition of non\(hytransient nature
 }	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001001	subsystem congestion	 {
disconnection \(em subsystem congestion
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001010	network failure	 {
disconnection \(em abnormal condition of non\(hytransient nature
 }	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001011	network congestion	 {
disconnection \(em abnormal condition of transient nature
 }	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001100	expiration of reset timer	 {
disconnection \(em abnormal condition of transient nature
 }	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001101	 {
expiration of receive inactivity timer
 }	 {
disconnection \(em abnormal condition of transient nature
 }	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001110	not obtainable | ua\d\u)\d	disconnection \(em undefined	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001110	not obtainable | ua\d\u)\d	disconnection \(em undefined	undefined
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001111	unqualified	 {
disconnection \(em abnormal condition
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001111	unqualified	disconnection \(em undefined	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001111	unqualified	disconnection \(em undefined	undefined
.TE
.LP
NSU
Network Service User
.LP
NSP
Network Service Provider
.LP
\ua\d\u)\d
The need for this value is for further study.
.nr PS 9
.RT
.ad r
\fBTableau A\(hy2/Q.713 [T38.713], p.41\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.ce
\fBH.T. [T39.713]\fR 
.ce
TABLE\ A\(hy3/Q.713
.ce
\fBMapping during connection reset\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(30p) sw(84p) | cw(84p) sw(30p) , c | c | c | c.
RSR Message	N\(hyRESET primitive
Code	Reset cause	Reason	Originator
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000000	end user originated	 {
reset \(em user synchronization
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000001	SCCP user originated	 {
reset \(em user synchronization
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000010	 {
message out of order \(em incorrect P(S)
 }	reset \(em unspecified	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000011	 {
message out of order \(em incorrect P(R)
 }	reset \(em unspecified	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000100	 {
remote procedure error \(em message out of window
 }	reset \(em unspecified	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000101	 {
remote procedure error \(em incorrect P(S) after initialization
 }	reset \(em unspecified	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000110	 {
remote procedure error \(em general
 }	reset \(em unspecified	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00000111	remote end user operational	 {
reset \(em user synchronization
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001000	network operational	reset \(em unspecified	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001001	access operational	 {
reset \(em user synchronization
 }	NSU
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001010	network congestion	reset \(em network congestion	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001011	not obtainable | ua\d\u)\d	reset \(em unspecified	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001011	not obtainable | ua\d\u)\d	reset \(em undefined	undefined
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001100	unqualified	reset \(em unspecified	NSP
_
.T&
cw(30p) | lw(84p) | lw(84p) | cw(30p) .
00001100	unqualified	reset \(em undefined	undefined
.TE
.LP
NSU
Network Service User
.LP
NSP
Network Service Provider
.LP
\ua\d\u)\d
The need for this value is for further study.
.nr PS 9
.RT
.ad r
\fBTableau A\(hy3/Q.713 [T39.713], p.42\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp