SCCP ANSI/ITU/TTC/CHINESE China 1994.10

1	General
1.1	Introduction
1.2	Terms
1.3	Concept
1.4	History
2	Compliance Lists
2.1	Comparison with Q.711, Functional Description of SCCP
2.2	Comparison with Q.712, Definition and Function of SCCP MESSAGES
2.3	Comparison with Q.713, SCCP Formats and Codes
2.4	Comparison with Q.714, SCCP Procedures
3	Notes
Reference List

1 General

1.1 Introduction

This document describes to what extent this version of the Ericsson SCCP signaling component compiles with the standard Reference [1].

1.2 Terms

DPC		Destination Point Code.

EIN		Ericsson Infotech AB.

GT		Global Title.

GTT		Global Title Translation.

ISDN-UP		Integrated Services Digital Network-User Part.

ITU		International Telecommunication Union.

ITU-T		Telecommunication Standardization sector of ITU.

LUDT		Long Unitdata message.

LUDTS		Long Unitdata Service message.

MTP		Message Transfer Part.

MTP-SAP		SAP to access the services provided by MTP.

NSDU		Network Service Data Unit.

PC		Point code.

SAP		Service Access Point

SCCP		Signaling Connection Control Part.

SCMG		SCCP Management.

SMI		Subsystem Multiplicity Indicator.

SOG		Subsystem Out of service Grant.

SOR		Subsystem Out of service Request.

SS7		Signaling Subsystem No.7.

SSN		SubSystem Number.

UDT		Unitdata message.

UDTS		Unitdata Service message.

XUDT		Extended Unitdata message.

XUDTS		Extended Unitdata Service message.

1.3 Concept

The terms that are used are:

C		The Ericsson signaling component complies with the specified section in the standard.

N		The Ericsson signaling component does not comply with the specified section in the standard.

P		The Ericsson signaling component complies partly with the specified section in the standard.

-		There is nothing to implement in the referred section (always placed in column C).

1.4 History

Table 1 Revision history
Status	Revision	Date	Author	Comment
-	A	01-02-27	Adele McKeown	Based on document 1/174 02 CAA 901 437 Uen Rev A. First version for Chinese SCCP R7.
-	B	01-05-31	Jose Pousa	New template used. The following functionality is included in this version of the document: SCCP signaling relay point for connectionless messages, SCCP load sharing.
-	C	02-08-20	Antonio Quintanilla	Frozen local reference number added.
-	D	02-12-12	Karl-Johan Grinnemo	Updated according to inspection 117402-CAA901437Uen.
-	E	03-06-30	Stefan Henrikson	Updated for release R10. Removed note on relay node.
-	E1	03-12-08	Peter Svensson	Added note 23.
-	E2	04-07-20	Peter Svensson	Changed 1.1.4.5 "Handling of gaps" in Q.714 from C to P. Added note 24.
-	E3	05–01–28	Denis Petrov	Entry 4.1.1.1.1 of Q.714 table was changed from fully compliant to partially compliant; added Note 25.
TAPP	F	05-04-19	xtskarl	General updates and improvements of the compliance statements before the R11 release. The most important changes are: Usage N_STATE_ind instead of N_PCSTATE_ind. Note 20, 21, 22, 23 Walk through of all compliances with a comment note. Due to this some chapters now are partly compliant and some notes where removed that was unnecessary. Clearification and more descriptive comment for the following notes: 5, 9, 15, 16, 19, 27. Added compliance note 18 for concerned subsystem support Mapped TR4123 from SCCP R9: Changed items 5.3.6.4 - 5.3.6.6 for Q.714, added note 24
-	G	07–02–26	XMRALBA	Converted to XML format (FM2XML feature)
-	H	08–03–13	XMRKISH	Changed reference style (FM2XML feature). Replaced from “signalling” to “signaling”. Corrected spelling errors. Updated after PC review: changed copyright from 2007 to 2008.

2 Compliance Lists

2.1 Comparison with Q.711, Functional Description of SCCP

Table 2 Functional Description of the signaling Connection Control Part
References		C	N	P	Comments
1.	Introduction	-
1.1	General	-
1.2	Objectives	-
1.3	General Characteristic	-
1.3.1	Technique of Description	X
1.3.2	Primitives	X
1.3.3	Peer-to-Peer Communication	X
1.3.4	Contents of Q.71x — Series Recommendation	X
2.	Services Provided by The SCCP			X	Note 1
2.1	Connection-Oriented Services	X			Note 24
2.1.1	Temporary signaling Connections	-
2.1.1.1	Description	X
2.1.1.1.1	Connection Establishment Phase			X	Note 11
2.1.1.1.2	Data Transfer Phase			X	Note 1
2.1.1.1.3	Connection Release Phase	X
2.1.1.2	Network Service Primitives and Parameters	-
2.1.1.2.1	Overview	X			Note 2, Note 3
2.1.1.2.2	Connection Establishment Phase			X	Note 3
2.1.1.2.3	Data Transfer Phase			X	Note 2
2.1.1.2.4	Release Phase	X
2.1.1.3	Additional SCCP primitives and interface elements		X
2.1.1.3.1	Notice Service		X
2.1.1.3.2	Connection establishment interface elements		X
2.1.2	Permanent signaling Connections	-
2.1.2.1	Description		X
2.1.2.2	Primitives and Parameters		X
2.2	Connectionless Service	X
2.2.1	Description	X
2.2.2	Primitives and Parameters of the Connectionless Service	-
2.2.2.1	Overview	X
2.2.2.2	Parameters	-
2.2.2.2.1	Address	X
2.2.2.2.2	Sequence Control	X
2.2.2.2.3	Return Options	X
2.2.2.2.4	Reason for Return	X
2.2.2.2.5	User Data	X
2.2.2.3	Primitives	-
2.2.2.3.1	UNITDATA	X
2.2.2.3.2	NOTICE	X
2.3	SCCP Management	-
2.3.1	Description	X
2.3.2	Primitives and Parameters of the SCCP Management	-
2.3.2.1	Overview			X	Note 4, Note 17
2.3.2.2	Parameters	-
2.3.2.2.1	Address	-
2.3.2.2.2	Affected subsystems			X	Note 6
2.3.2.2.3	User Status	X
2.3.2.2.4	Subsystem Multiplicity Indicator			X	Note 5
2.3.2.2.5	Affected DPC			X	Note 4, Note 18
2.3.2.2.6	Signaling Point Status			X	Note 4, Note 19
2.3.2.2.7	Remote SCCP status			X	Note 4, Note 20
2.3.2.7	Primitives	-
2.3.2.3.1	COORD		X
2.3.2.3.2	STATE			X	Note 17
2.3.2.3.4	PCSTATE			X	Note 4
3.	Services Assumed from the MTP	-
3.1	Description	X
3.2	Primitives and Parameters	X
3.2.1	TRANSFER	X
3.2.2	PAUSE	X
3.2.3	RESUME	X
3.2.4	STATUS	X
3.2.5	MTP Restart	X
4.	Functions Provided by the SCCP	X
4.1	Connection Oriented Functions	-
4.1.1	Functions for Temporary signaling Connections	-
4.1.1.1	Connection Establishment Functions			X	Note 1
4.1.1.2	Data Transfer Phase Functions			X	Note 7
4.1.1.3	Release Phase Functions	X
4.1.2	Functions for Permanent signaling Connections	-			Note 24
4.1.2.1	Connection Establishment Phase and Connection Release Phase functions	-
4.1.2.2	Data Transfer Phase Functions	-
4.2	Connectionless Service Functions	X
4.3	Management functions			X	Note 8
4.4	Routing and translation functions	X

2.2 Comparison with Q.712, Definition and Function of SCCP MESSAGES

Table 3 Comparison with Q.712, Definition and Function of SCCP MESSAGES
References		C	N	P	Comments
1.	Signaling Connection Control Part Messages	X
1.1	Connection Confirm (CC)	X
1.2	Connection Request (CR)	X
1.3	Connection Refused (CREF)	X
1.4	Data Acknowledgement (AK)		X
1.5	Data Form 1 (DT1)	X
1.6	Data Form 2 (DT2)		X
1.7	Expedited Data (ED)		X
1.8	Expedited Data Acknowledgement (EA)		X
1.9	Inactivity Test (IT)	X
1.10	Protocol Data Unit Error (ERR)	X
1.11	Released (RLSD)	X
1.12	Release Complete (RLC)	X
1.13	Reset Confirm (RSC)		X
1.14	Reset Request (RSR)		X
1.15	Subsystem-Allowed (SSA)	X
1.16	Subsystem-out-of-Service-Grant (SOG)		X
1.17	Subsystem-out-of-Service-Request (SOR)		X
1.18	Subsystem-Prohibited (SSP)	X
1.19	Subsystem-Status-Test (SST)	X
1.20	Unitdata (UDT)	X
1.21	Unitdata Service (UDTS)	X
1.22	Extended Unitdata (XUDT)	X
1.23	Extended Unitdata Service (XUDTS)	X
2.	SCCP Parameter	-
2.1	Affected Point Code	X
2.2	Affected Subsystem Number	X
2.3	Calling/Called Party Address	X
2.4	Credit			X	Note 10
2.5	Data	X
2.6	Diagnostic	-
2.7	Error Cause	X
2.8	End of Optional Parameters	X
2.9	Local Reference Number (Source/Destination)	X
2.10	Protocol Class	X
2.11	Receive Sequence Number		X
2.12	Refusal Cause	X
2.13	Release Cause	X
2.14	Reset Cause		X
2.15	Return Cause	X
2.16	Segmenting/Reassembling	X
2.17	Sequencing/Segmenting		X
2.18	Subsystem Multiplicity Indicator	X
2.19	Hop Counter	X
2.10	Segmentation			X
3.	Inclusion of Fields in the Messages			X	Note 22

2.3 Comparison with Q.713, SCCP Formats and Codes

Table 4 SCCP Formats and Codes
References		C	N	P	Comments
1.	General	X
1.1	Message type code	X
1.2	Formatting principles	X
1.3	Mandatory fixed part	X
1.4	Mandatory variable part	X
1.5	Optional part	X
1.6	End of optional parameters octet	X
1.7	Order of transmission	X
1.8	Coding of spare bits	X
1.9	National message types and parameters	X
1.10	International message types and parameters	X
2.	Coding of the general parts	-
2.1	Coding of the message type			X	Note 1
2.2	Coding of the length indicator	X
2.3	Coding of the pointers	X
3.	SCCP parameters	-
3.1	End of optional parameters	X
3.2	Destination local reference	X
3.3	Source local reference	X
3.4	Called party address	X
3.4.1	Address indicator	X
3.4.2	Address	X
3.4.2.1	Signaling point code	X
3.4.2.2	Subsystem number	X
3.4.2.3	Global title	X
3.4.2.3.1	Global title indicator = 0001	X
3.4.2.3.2	Global title indicator = 0010	X
3.4.2.3.3	Global title indicator = 0011	X
3.4.2.3.4	Global title indicator = 0100	X
3.5	Calling party address	X
3.6	Protocol class			X	Note 1
3.7	Segmenting/reassembling	X
3.8	Receive sequence number		X
3.9	Sequencing/segmenting		X
3.10	Credit			X	Note 10
3.11	Release cause	X
3.12	Return cause	X
3.13	Reset cause		X
3.14	Error cause	X
3.15	Refusal cause	X
3.16	Data	X
3.17	Segmentation	X
3.18	Hop counter	X
4.	SCCP messages and codes	-
4.1	General	-
4.1.1		-
4.1.2		-
4.1.3		-
4.1.4		-
4.2	Connection request (CR)	X
4.3	Connection confirm (CC)	X
4.4	Connection refused (CREF)	X
4.5	Released (RLSD)	X
4.6	Release complete (RLC)	X
4.7	Data form 1 (DT1)	X
4.8	Data form 2 (DT2)		X
4.9	Data acknowledgement (AK)		X
4.10	Unitdata (UDT)	X
4.11	Unitdata service (UDTS)	X
4.12	Expedited data (ED)		X
4.13	Expedited data acknowledgement (EA)		X
4.14	Reset request (RSR)		X
4.15	Reset confirm (RSC)		X
4.16	Protocol data unit error (ERR)	X
4.17	Inactivity test (IT)	X
4.18	Extended unitdata (XUDT)	X
4.19	Extended unitdata service (XUDTS)	X
5.	SCCP Management messages and codes	-
5.1	General	X
5.1.1	SCMG format identifier			X	Note 9
5.1.2	Formatting principles	X
5.2	SCMG message parameters	X
5.2.1	End of optional parameters	X
5.2.2	Affected SSN	X
5.2.3	Affected PC	X
5.2.4	Subsystem multiplicity indicator	-			Note 5
Annex A (Mapping for cause parameter values):		-
A.1 Introduction				X	Note 2
A.2 Connection refusal		X
A.3 Connection release		X
A.4 Connection reset			X

2.4 Comparison with Q.714, SCCP Procedures

Table 5 SCCP Procedures
References		C	N	P	Comments
1.	Introduction	-
1.1	General characteristics of signaling connection control procedures	-
1.1.1	Purpose	X
1.1.2	Protocol classes			X	Note 1
1.1.2.1	Protocol class 0	X
1.1.2.2	Protocol class 1	X
1.1.2.3	Protocol class 2	X
1.1.2.4	Protocol class 3		X
1.1.3	Signaling connections			X	Note 23
1.1.4	Compatibility and handling of unrecognized information	-
1.1.4.1	Rules for forward compatibility	X
1.1.4.2	Handling of unrecognized messages or parameters	X
1.2	Overview of procedures for connection-oriented services	-			Note 1
1.2.1	Connection establishment			X	Note 23
1.2.2	Data transfer			X	Note 1
1.2.3	Connection release	X
1.3	Overview of procedures for connectionless services	-
1.3.1	General	X
1.3.2	Segmentation and reassembly	X
1.4	Structure of the SCCP and contents of specification			X	Note 1, Note 2, Note 4, Note 9, Note 11
2.	Addressing and routing	-
2.1	SCCP addressing	X
2.2	SCCP routing principles	X
2.2.1	Receipt of SCCP message transferred by a MTP	X
2.2.2	Messages from connection-oriented or connectionless control to SCCP routing control	X
2.2.2.1	DPC present	X
2.2.2.2	DPC not present	X
2.3	SCCP routing	X
2.3.1	Receipt of SCCP message transferred by the MTP			X	Note 23
2.3.2	Messages from connectionless or connection-oriented control to SCCP routing control	X
2.4	Routing failures	X
3.	Connection-oriented procedures	-
3.1	Connection establishment	-
3.1.1	General			X	Note 11
3.1.2	Local reference numbers	X
3.1.3	Negotiation procedures	-
3.1.3.1	Protocol class negotiation	X
3.1.3.2	Flow control credit negotiation		X
3.1.4	Actions at the origination node	-
3.1.4.1	Initial actions			X	Note 1, Note 11
3.1.4.2	Subsequent actions			X	Note 1, Note 10
3.1.5	Actions at an intermediate node	-
3.1.5.1	Initial actions			X	Note 1, Note 11
3.1.5.2	Subsequent actions			X	Note 1, Note 10
3.1.6	Actions at destination node	-
3.1.6.1	Initial actions			X	Note 1, Note 11
3.1.6.2	Subsequent actions			X	Note 1, Note 10
3.2	Connection refusal	-
3.2.1	Actions at node initiating connection refusal			X	Note 11
3.2.2	Actions at relay node not initiating connection refusal			X	Note 11
3.2.3	Actions at the origination node not initiating connection refusal	X
3.3	Connection release	-
3.3.1	General	X
3.3.2	Frozen reference	X
3.3.3	Actions at an end node initiating connection release	-
3.3.3.1	Initial actions	X
3.3.3.2	Subsequent actions			X	Note 12
3.3.4	Actions at a intermediate node	X
3.3.4.1	Initial actions			X	Note 11
3.3.4.2	Subsequent actions			X	Note 12
3.3.5	Actions at an end node not initiating connection release	X
3.4	Inactivity control	X			Note 24
3.5	Data transfer	-
3.5.1	General	X			Note 24
3.5.1.1	Actions at the originating node			X	Note 1
3.5.1.2	Actions at a relay node			X	Note 1
3.5.1.3	Actions at the destination node			X	Note 1
3.5.2	Flow control	-
3.5.2.1	General		X
3.5.2.2	Sequence numbering		X
3.5.2.3	Flow control window		X
3.5.2.4	Flow control procedures	-
3.5.2.4.1	Transfer of Data messages		X
3.5.2.4.2	Transfer of AK messages		X
3.5.2.4.3	Reception of a Data or AK message		X
3.5.3	Segmenting and reassembly	X
3.6	Expedited data transfer	-
3.6.1	General		X
3.6.2	Actions at the originating node		X
3.6.3	Actions at a relay node		X
3.6.4	Actions at destination node		X
3.7	Reset	-
3.7.1	General		X
3.7.2	Action at the initiating node	-
3.7.2.1	Initial actions		X
3.7.2.2	Subsequent actions		X
3.7.3	Actions at the intermediate node	-
3.7.3.1	Initial actions		X
3.7.3.2	Subsequent actions		X
3.7.4	Actions at an end node not initiating the reset procedure		X
3.7.5	Handling of messages during the reset procedures		X
3.8	Restart	-
3.8.1	General	X
3.8.2	Actions at the recovered node	-
3.8.2.1	Initial actions	X			Note 13, Note 24
3.8.2.2	Subsequent actions	X			Note 13
3.8.3	Actions at the non-failed far end node	X
3.9	Permanent signaling connections	-			Note 24
3.10	Abnormalities	-
3.10.1	General	X
3.10.2	Action tables			X	Note 1
3.10.3	Actions upon the reception of an ERR message	X
4.	Connectionless procedures	X
4.1	Data transfer	X
4.1.1	Segmentation/reassembly	-
4.1.1.1	Segmentation	-
4.1.1.1.1	General	X
4.1.1.1.2	Normal procedures	X
4.1.1.1.3	Return on error procedure	X
4.1.1.2	Reassembly	-
4.1.1.2.1	General	X
4.1.1.2.2	Normal procedures	X
4.1.1.2.3	Return on error procedure	X
4.2	Message return procedure	X
4.3	Syntax error	X
5.	SCCP management procedures	-
5.1	General	X
5.2	Signaling point status management	-
5.2.1	General	X
5.2.2	Signaling point prohibited	X
5.2.3	Signaling point allowed	X			Note 25
5.2.4	Signaling point congested	X
5.2.5	Local MTP network availability	X			Note 25
5.3	Subsystem status management	-
5.3.1	General	X
5.3.2	Subsystem prohibited	X
5.3.2.1	Receipt of messages for a prohibited subsystem (response method)	X
5.3.2.2	Receipt of subsystem prohibited message or N-STATE REQUEST primitive or local user failed			X	Note 17
5.3.3	Subsystem allowed			X	Note 17
5.3.4	Subsystem status test	-
5.3.4.1	General	X
5.3.4.2	Actions at the initiating node	X
5.3.4.3	Actions at the receiving node	X
5.3.5	Coordinated state change	-
5.3.5.1	General		X
5.3.5.2	Actions at the requesting node		X
5.3.5.3	Actions at the requested node		X
5.3.6	Local broadcast	-
5.3.6.1	General			X	Note 16
5.3.6.2	User-out-of-service			X	Note 16, Note 17
5.3.6.3	User-in-service			X	Note 16, Note 17
5.3.6.4	Signaling point inaccessible			X	Note 16, Note 19, Note 20
5.3.6.5	Signaling point remote SCCP accessible			X	Note 16, Note 19, Note 20
5.3.6.6	Signaling point congested			X	Note 16, Note 21
5.3.7	Broadcast	-
5.3.7.1	General	X
5.3.7.2	Subsystem prohibited			X	Note 17
5.3.7.3	Subsystem allowed			X	Note 17
5.4	MTP/SCMG restart	X			Note 25
Annex A (State diagrams for the signaling connection control part of signaling System No. 7)		-
A.1	Introduction	-
A.2	Symbol definition of the state diagrams at the message interface	-
A.3	Order definitions of the state diagrams			X	Note1, Note 11
Annex B (Action tables for the signaling connection control part of signaling System No. 7)		-
B.1	Introduction	-
B.2	Symbol definition of the action tables	X
B.3	Table of contents			X	Note1, Note 11
Annex C (State transition diagrams (STD) for the signaling connection control part of signaling System No. 7)		-
C.1	General	-
C.2	Drafting conventions	-
C.3	Figures	-
C.4	Abbreviations and timers			X	Note 12, Note 14
Annex D (State transition diagrams (STD) for SCCP management control)		-
D.1	General	-
D.2	Drafting conventions	-
D.3	Figures	-
D.4	Abbreviations and timers			X	Note 14
Annex E (Guidelines for the use of the address information elements in the international network)		X			Note 15

3 Notes

Note 1		Class 3 is not supported (flow-controlled connection-oriented class).

Note 2		N-EXPEDITED-DATA, N-DATA-ACKNOWLEDGE and N-RESET primitives are not supported.

Note 3		The parameter “Expedited data selection” and “Receipt confirmation selection” of primitive N-CONNECT is not supported.

Note 4		N-COORD and N-PCSTATE are not supported. Parts of the N-PCSTATE functionality is implemented using the N-STATE Indication. For compliance refer to the following sub-clauses.

Note 5		The SMI is a configurable parameter in the SCCP configuration file.

Note 6		The parameter "Affected subsystem " does not support the global title portion of the Called/Calling Address.

Note 7		Flow control, NSDU delimiting, Expedited data, Missequence detection, Reset, and Receipt confirmation not supported.

Note 8		Functions to permit coordinated state change of replicated SCCP subsystems are not supported.

Note 9		The SCMG messages SOR and SOG are not supported.

Note 10		Credit negotiation is not supported. If received, the credit parameter is ignored.

Note 11		ISDN-UP connections are not supported.

Note 12		The timers T(int) and T(repeat rel) are not supported.

Note 13		The usage of the T(guard) timer is a configurable option. If T(guard) is used it will not be started if the functionality to set connection state upon node recovery is used. As a recommended alternative to the timer a restart counter has been implemented that assures that local reference numbers are not reused after a node recovery. The restart counter does not have the time penalty inherent with T(guard) upon a node recovery.

Note 14		The timers T(coord chg) and T(ignore SST) are not supported.

Note 15		There is nothing in our SCCP signaling component which prohibits someone to follow these guidelines.

Note 16		Concerned subsystems at remote SCCP signaling points are configured per local signaling point, hence all local subsystem at given local SCCP signaling point are considered to be concerned when the local broadcast procedure is initiated.

Note 17		The proprietary N_BIND_req and N_UNBIND_req used to implement behavior of N-STATE Request.

Note 18		The "Affected DPC " is included as a part of the N-STATE which is used instead of the PC-STATE for signaling point status and remote SCCP status. Refer also to Note 19 and Note 20.

Note 19		N_STATE with SSN=1 used instead of N_PCSTATE to inform the upper layer of the "signaling Point Status ".

Note 20		N_STATE with SSN=1 used instead of N_PCSTATE to inform the upper layer of the "Remote SCCP status ". The values remote SCCP unavailable, unequipped and inaccessible are all mapped to a congestion level (value 0-3) that is presented in the User Status parameter of the N_STATE primitive.

Note 21		N_STATE with SSN=1 used instead of N_PCSTATE to inform the upper layer of the congestion level (value 0-3). It is presented in the User status parameter of the N_STATE primitive.

Note 22		The SCCP are only compliant with Table 1 and Table 2 for supported messages and parameters according to this statement of compliance for clause 1 and 2 of Q.712.

Note 23		Connection oriented relay point without coupling is not supported.

Note 24		Permanent connections is excluded in standard Reference [1].

Note 25		It is a configurable option if all remote SSN shall be considered allowed at the reception of a MTP-RESUME indication or if the subsystem shall be marked "prohibited " and subsystem test procedure should be used to audit the remote subsystem state.

Reference List

China Standard
[1] Technical Specification of SCCP, Directorate General of Telecommunication of Ministry of Posts and Telecommunication, P.R.C. 1994:10