Signalling System Number 7 (SS7) Signalling Connection Control Part (SCCP)

Transcription

1 Secretariat Alliance for Telecommunications Industry Solutions ANSI T Revision of ANSI T American National Standard for Telecommunications Signalling System Number 7 (SS7) Signalling Connection Control Part (SCCP) Approved (date to be inserted) American National Standards Institute, Inc. Abstract This recommendation contains a general description of the services provided from the Message Transfer Part (MTP) of Signalling System Number 7, the functions within the Signalling Connection Control Part (SCCP), and the resultant services provided for the users of the SCCP. Table of Contents ANSI T Chapter Foreword T T T T T T Page...ii Functional Description of the Signalling Connection Control Part... T Definitions and Functions of the Signalling Connection Control Part... T Signalling Connection Control Part Formats and Codes... T Signalling Connection Control Part Procedures... T Signalling Connection Control Part Performances... T Signalling Connection Control Part Users Guide... T (NOTE A detailed table of contents is provided at the end of the Foreword for all the above chapters of SCCP. A detailed table of contents for each chapter is also at the beginning of each chapter.)

2 ANSI T Foreword (This foreword is not part of American National Standard T1.112.) This document is entitled American National Standard for Telecommunications Signalling System Number 7 (SS7) Signalling Connection Control Part. It was originally based on the 1988 Blue Book specification of Signalling System No. 7 (SS#7)) for international use, issued by the CCITT Study Group XI (Vol. VI, Fascicles VI.7 and VI.8) and is intended to be generally compatible with that standard and its successors. It has been appropriately modified for use within and between U.S. networks to meet the anticipated needs and applications of such entities. These modifications are the result of extensive work by the members of the T1S1.3 (formerly T1X1.1) Working Group on U.S. Standards for Common Channel Signalling. In general, these modifications fall into two categories: ii 1) The specification of options designated by the ITU-T (formerly CCITT) for national use, 2) Extensions to the 1996 protocol to provide for new applications of the SS7 protocol. This is in accordance with current and projected ITU-T activity. A vertical bar () in the right-hand margin indicates a change from the previous issue of this standard. This standard contains the following five chapters: T , T , T , T , T , T , Functional Description of the Signalling Connection Control Part; Definitions and Functions of Signalling Connection Control Part Messages; Signalling Connection Control Part Formats and Codes; Signalling Connection Control Part Procedures; Signalling Connection Control Part Performances; SCCP Users Guide (I nformative) Changes and additions incorporated into these specifications consist of the following: - Additions and Modifications to Translation Type Code Assignments - Long Messaging Capabilities - Intermediate Network Selection Capability - Message Change Procedures - Alignment of Subsystem Number Values with ITU - Compatibility Test - Subsystem Status Management Changes in a Load-Shared Environment - Changes to Connection Oriented Procedures to Align with ITU-T The overall and detailed organization of these specifications parallels that used in the equivalent ITU-T recommendations. Thus T through T of this standard correspond to Recommendations Q.711 through Q.714 and Q.716 of the ITU-T specification. T corresponds to Q.715. This standard is intended for use in conjunction with American National Standard for Telecommunications - Signalling System Number 7 (SS7) - General information, ANSI T1.110, which includes an overview of SS7, a glossary, and a chapter on abbreviations. Information contained in a Normative Annex in these specifications is considered part of this standard. Information contained in an Informative Annex in these specifications is not considered part of this standard but is rather auxiliary to the standard. Similarly, footnotes are not part of this official standard. Caution should be exercised in using the Specification and Description Language (SDL) diagrams to interpret the standard; Please note that the text always takes precedence over the SDL. Future control of this document will reside with Accredited Standards Committee on Telecommunications, T1. This control of additions to the specification, such as ongoing protocol evolution, new applications and operational requirements, will permit compatibility among U. S. networks. Such additions will be incorporated in an orderly manner with due consideration to the ITU-T layered model principles, conventions, and functional boundaries. Suggestions for improvement of this standard will be welcome. They should be sent to the Alliance for Telecommunications Industry Solutions, 1200 G Street, NW, Suite 500, Washington, DC This standard was processed and approved for submittal to ANSI by the Accredited Standards Committee on Telecommunications, T1. Committee approval of this standard does not necessarily imply that all committee

3 ANSI T members voted for its approval. At the time it approved this standard, the T1 committee had the following members: G.H. Peterson, Chairman Ray Hapeman, Vice-Chairman, Secretary (Membership to be provided by the Secretariat) At the time it approved this standard, the Technical Subcommittee T1S1 on Service, Architecture, and Signaling had the following members: (Membership to be provided by the Secretariat) Working Group T1S1.3, which developed this standard, had the following participants: Wesley Downum, Chairman Brian Foster, Chairman Stu Goldman, Vice-Chairman Doris Lebovits, Vice-Chairman Anne Marie Livingstone, Vice-Chairman Dana Shillingburg, Vice-Chairman Jeffrey D. Copley, SCCP Chairman, Senior Technical Editor Koan S. Chong, Technical Editor Ray P. Singh, Technical Editor Participants list: Bjorn Ahle Nick Andre Shridharan Balachardran Ronald Bell James Calme Angelise Carter Thomas Casey Janey Cheu Don Conrad Darryl DeBault Carol DeFazio Ranga Dendi Amar Deol Patricia Dinh Martin C. Dolly Wesley Downum Richard Ejzak Christopher Fisher Paul Garvey Rakesh Gupta Bob Hall Doug Hedger Rich Hemmeter Andrew Jacob Bill Krehl Jim LaFave Ceyan Lennon Douglas Lin Jan Lindquist Michael Liu Virgil Long Jim Lord Mike Matz Mike McGrew Don Mickel Stewart Patch Yatendra K. Pathak Terry Reese Doug Rollender John Rollins John Roquet N. Sandasara John Schantz Arnette Schultz Greg Sidebottom Dave Signaigo Karl Stanek Walt Subora Alan Varney Stan Wainberg Terry Watts Volnie Whyte Felix J. Zamora Yi Zhao iii

4 ANSI T Table of Contents Chapters T through T The Tables of Content for each of the six chapters of SCCP are provided below: Chapter T Functional Description of the Signalling Connection Control Part 1. SCOPE, PURPOSE, AND APPLICATION General Objectives General Characteristic SERVICES PROVIDED BY THE SCCP Connection-Oriented Services Connectionless Services SCCP Management SERVICES ASSUMED FROM THE MTP Description Primitives and Parameters FUNCTIONS PROVIDED BY THE SCCP Connection-Oriented Functions Connectionless Service Functions...17 Tables Table 1/T Network Service Primitives for Connection-Oriented Services...18 Table 2/T Parameters of the Primitive N-CONNECT...19 Table 3/T Parameters of the Primitive N-DATA...20 Table 4/T Parameters of the Primitive N-EXPEDITED DATA...20 Table 5/T Parameters of the Primitive N-RESET...21 Table 6/T Parameters of the Primitive N-DISCONNECT...21 Table 6A/T Parameters of the Primitive N-INFORM...22 Table 7/T Primitives for the Data Transfer on Permanent Connections...22 Table 8/T Primitives and Parameters of the Connectionless Service...23 Table 8A/T Parameters of the Primitive N-UNITDATA...23 Table 8B/T Parameters of the Primitive N-NOTICE...24 Table 8C/T Primitives and Parameters of the SCCP Management...24 Table 8D/T Parameters of the Primitive N-COORD...25 Table 8E/T Parameters of the Primitive N-STATE...25 Table 8F/T Parameters of the Primitive N-TRAFFIC...26 Table 8G/T Parameters of the Primitive N-PCSTATE...26 Table 9/T Message Transfer Part Service Primitives...26 Figures Figure 1/T Functional Diagram for the Common Channel Signalling System...27 Figure 2/T Relationship between the SCCP Protocol and Adjacent Services...28 Figure 3/T Service Primitives...28 Figure 4/T Specific Names of Service Primitives and Peer-to-Peer Communication...28 Figure 5/T Model for the Internode Communication within the SCCP (Connection-Oriented Service)...29 Figure 6/T State Transition Diagram for the Sequence of Primitives at a Connection Endpoint (Basic Transitions) 30 Annex - Network Layer Services A1. Glossary...31 A2. Relationship Among the Terms "Layer", "Entity", "Layer Service", "Layer Boundary", "Layer Service Primitive", and "Peer Protocol"...31 A3. Data Transport...31 A4. Flow Control...32 A5. Sequencing...32 iv

5 ANSI T A6. Acknowledgment...32 A7. Reset...32 A8. Restart...32 A9. Expedited Data...32 A10. Routing...32 Figures Figure A-1/T Layer and Peer Relationships...33 Figure A-2/T Relation between NSDU and Message with Neither Segmenting nor Blocking33 Figure A-3/T Segmenting...34 Contents Chapter T Definitions and Functions of Signalling Connection Control Part Messages 1. SCOPE, PURPOSE AND APPLICATION SIGNALLING CONNECTION CONTROL PART MESSAGES Connection Confirm (CC) Connection Request (CR) Connection Refused (CREF) Data Acknowledgment (AK) Data Form 1 (DT1) Data Form 2 (DT2) Expedited Data (ED) Expedited Data Acknowledgment (EA) Inactivity Test (IT) Protocol Data Unit Error (ERR) Released (RLSD) Release Complete (RLC) Reset Confirmation (RSC) Reset Request (RSR) Unitdata (UDT) A. Extended Unitdata (XUDT) B. Long UnitData (LUDT) Unitdata Service (UDTS) A. Extended Unitdata Service (XUDTS) B. Long UnitData Service (LUDTS) MESSAGES FOR SCCP SUBSYSTEM MANAGEMENT Subsystem-Allowed (SSA) Subsystem-Prohibited (SSP) Subsystem-Status-Test (SST) Subsystem-Out-of-Service-Request (SOR) Subsystem-Out-of-Service-Grant (SOG) Subsystem-Backup-Routing (SBR) (Optional) Subsystem-Normal-Routing (SNR) (Optional) Subsystem-Routing-Status-Test (SRT) (Optional) SCCP PARAMETERS Calling/called party address Credit Data Diagnostic End of optional parameters Error cause Local reference number (source/destination) Message type code Protocol class Receive sequence number Refusal cause Release cause....6 v

6 ANSI T Reset cause Return cause Segmenting/reassembling Sequencing/segmenting SCCP hop counter Segmentation Intermediate Signalling Network Identification (ISNI) Long Data Intermediate Network Selection (INS) Message Type Interworking (MTI) PARAMETERS FOR SCCP SUBSYSTEM MANAGEMENT Affected subsystem number Affected point code Subsystem multiplicity indicator INCLUSION OF FIELDS IN THE MESSAGES...7 Tables 1/T Inclusion of Fields in Messages (Sheet 1 of 3)...8 1/T Inclusion of Fields in Messages (Sheet 2 of 3)...9 1/T Inclusion of Fields in Messages (Sheet 3 of 3) /T SCCP Management Messages...11 Chapter T Signalling Connection Control Part Formats and Codes 1. SCOPE, PURPOSE AND APPLICATIONS Routing label Message type code Formatting principles Mandatory fixed part Mandatory variable part Optional part End of optional parameters octet Order of transmission Coding of spare bits National message types and parameters CODING OF THE GENERAL PARTS Coding of the message type Coding of the length indicator Coding of the pointers SCCP PARAMETERS End of optional parameters Destination local reference Source local reference Called party address Calling party address Protocol class Segmenting/reassembling Receive sequence number Sequencing/segmenting Credit Release cause Return cause (formerly Diagnostic) Reset cause Error cause Refusal cause Data SCCP Hop Counter Segmentation Intermediate Signaling Network Identification (ISNI)...14 vi

7 ANSI T Long Data Intermediate Network Selection Message Type Interworking SCCP MESSAGES AND CODES General Connection Request (CR) Connection Confirm (CC) Connection Refused (CREF) Released (RLSD) Release Complete (RLC) Data Form 1 (DT1) Data Form 2 (DT2) Data Acknowledgment (AK) Unitdata (UDT) A Extended Unitdata (XUDT) B Long Unitdata (LUDT) Unitdata Service (UDTS) A Extended Unitdata Service (XUDTS) B Long Unitdata Service (LUDTS) Expedited Data (ED) Expedited Data Acknowledgment (EA) Reset Request (RSR) Reset Confirmation (RSC) Protocol Data Unit Error (ERR) Inactivity Test (IT) SCCP MANAGEMENT MESSAGES AND CODES General SCMG Message Parameters SCMG Messages Figures 1/T General layout /T General SCCP Message Format /T Called, Calling Party Address /T Address indicator encoding a/T Ordering of Address Elements /T Signalling point code encoding /T Global title format for indicator a/T Global title format for indicator b/T Global title address information /T Segmenting/reassembling parameter field /T Receive sequence number /T Sequencing/segmenting parameter field /T Subsystem Multiplicity Indicator Format /T SCCP Hop Counter Format /T Segmentation Parameter Format /T ISNI Parameter Format A/T ISNI Routing Control Octets Format...23 Tables 1/T SCCP Message Types /T SCCP Parameter Name Codes /T Connection Request Message /T Connection Confirm Message /T Connection Refused Message /T Released Message /T Release Complete Message /T Data Form 1 Message /T Data Form 2 Message /T Data Acknowledgment Message /T Unitdata Message A/T Extended Unitdata Message...30 vii

8 ANSI T /T Unitdata Service Message A/T Extended Unitdata Service Message A/T Extended Unitdata Service Message /T Expedited Data Message /T Expedited Data Acknowledgment Message /T Reset Request Message /T Reset Confirmation Message /T Error Message /T Inactivity Test Message /T SCCP Management Message Format /T SCMG Format Identifiers /T SCMG Parameter Name Codes /T SCMG Message...35 A Guidelines and Procedures for Assigning Internetwork Translation Type Code Values...36 B Mapping for Cause Parameter Values Chapter T Signalling Connection Control Part Procedures 1. SCOPE, PURPOSE, AND APPLICATION General Characteristics of Signalling Connection Control Procedures Overview of Procedures for Connection-Oriented Services Overview of Procedures for Connectionless Services Structure of the SCCP and Contents of Specification ADDRESSING AND ROUTING SCCP Addressing SCCP Routing Principles SCCP Routing Routing Failures Compatibility test CONNECTION-ORIENTED PROCEDURES Connection Establishment Connection Refusal Connection Release Inactivity Control Data Transfer Expedited Data Transfer Reset Restart Permanent Signalling Connections Abnormalities CONNECTIONLESS PROCEDURES Data Transfer Syntax Error SCCP MANAGEMENT PROCEDURES General Signalling Point Status Management Subsystem Status Management Traffic Information Management (Optional) SCCP Flow Control (Optional) SCCP Restart STATE TRANSITION DIAGRAMS General Drafting Conventions SCCP Routing SCCP Connection-Oriented Control SCCP Connectionless Control SCCP Management Architecture Dependent Functions Abbreviations and Timers viii

9 ANSI T ANNEX A...94 A.1 Introduction...94 A.2 Symbol Definition of the State Diagrams at the Message Interface between Two Nodes (Signaling Points: X and Y)...94 A.3 Order Definition of the State Diagrams...95 ANNEX B...99 B.1 ntroduction...99 B.2 Symbol Definition of the Action Tables...99 B.3 Table of Contents...99 ANNEX C C.1 Introduction C.2 Simple Global Title Translation C.3 Routing with Distributed Translation Load C.4 Routing with Multiple Translation ANNEX D ANNEX E ANNEX F F.1 Example of Constrained Routing Only F.2 Example of Identification Only F.3 Unconstrained Query with Identification, Constrained Reply F.4 Constrained Query with Identification, Constrained Reply F.5 An Example of an Undeliverable Message, XUDTS Message Return ANNEX G G.1 Introduction G.2 Formats of the Optional SCCP INS Parameter G.3 Procedures for Routing Using the INS Capability G.3.1 Actions at the Origination SEP G.3.2 Actions at the INS Capable SCCP Relay Node G Invocation of the INS Function G.3.3 Actions at a Non-INS-Capable SCCP Relay Node G.3.4 Actions at the Destination SEP G.3.5 Abnormal Procedures G Actions at a INS-Capable SCCP Relay Node G.3.6 Error Conditions G.4 Error Handling Procedures G.5 Procedures for Deriving the XUDTS G.6 SDL List of Figures. Figure A-1/T Symbol Definition of the State Diagram...94 Figure A-2/T Primitive and Protocol Interface...95 Figure A-3/T State Transition Diagram for Sequences of Messages during Connection Establishment 96 Figure A-4/T State Transition Diagram for Sequence of Messages during Connection Release 97 Figure A-5/T State Transition Diagram for the Transfer of Reset Messages within the Data Transfer (c4) State 97 Figure A-6/T State Transition Diagram for the Transfer of Data, Expedited Data and Flow Control within the Data Transfer (c4) State...98 Figure C-1/T Routing Model for Simple Translation Figure C-2/T Routing Problem at STP Figure C-3/T Routing Problem at Terminating Node Figure C-4/T Routing Model for Distributed Translation Figure C-5/T Routing Model for Multiple Translations Figure C-6/T Routing Problem at Second Translation Point Figure E-1/T ISNI SDL (Sheet 1 of 5) Figure E-1/T ISNI SDL (Sheet 2 of 5) Figure E-1/T ISNI SDL (Sheet 3 of 5) Figure E-1/T ISNI SDL (Sheet 4 of 5) ix

10 ANSI T Figure E-1/T ISNI SDL (Sheet 5 of 5) Figure F-1/T Reference ISNI Message Path Figure G-2/T INS Parameter Figure G-3/T SDL of INS Figure G-4/T SDL of INS Figure G-5/T SDL of INS Figure G-6/T SDL of INS List of Tables. Table B-1/T Table B-2/T Table B-3/T Table B-4/T Table B-5/T Table F-1/T Constrained Routing Only Table F-2/T Identification Only Table F-3/T Query With Identification Only Table F-4/T Reply With Constrained Routing Only Table F-5/T Query With Constrained Routing and Identification Table F-6/T Reply With Constrained Routing Only Table F-7/T Query Encountering Problems with Constrained Routing and Identification. 124 Table F-8/T XUDTS Message Returned with Constrained Routing Chapter T SIGNALLING CONNECTION CONTROL PART PERFORMANCES 1. SCOPE, PURPOSE AND APPLICATION Overview Definitions DEFINITION OF PERFORMANCE PARAMETERS Performance Parameters for the Connectionless Classes Performance Parameters for the Connection-Oriented Classes Correspondence between the QOS Parameters and the Class SPECIFIED VALUES FOR INTERNAL PARAMETERS Internal Parameters for Classes 0 and Internal Parameters for Classes 2 and Chapter T (Informative) Signalling Connection Control Part Users Guide 1. SCOPE COMPATIBILITY ISSUES Differences between T and T Encoding for Global Title Indicator (GTI) = Segmentation Parameter Intermediate Signaling Network Identification (ISNI) Parameter Return Cause Parameter Refusal Cause Parameter SCCP Flow Control (as a part of SCCP management procedures) SCCP Restart Segmentation/Reassembly (for connectionless procedures) Compatibility and handling of Unrecognized messages Connection Refusal (in connection-oriented procedures) SCCP Reaction to Local MTP Restart SCCP Accessible and Inaccessible Extended Unitdata Message (XUDT) and Extended Unitdata Service Message (XUDTS) Annexes in T Protocol Class x

11 ANSI T Replicated Nodes/Subsystems Differences between T and T Support of Long Message (LUDT) Capability Compatibility test Segmentation Coordinated State Change procedures SCCP Loadsharing Interworking between T and T Support of Long Message (LUDT) Capability USE OF ADDRESSING PARAMETER Scope and Purpose Description of addressing parameters Subsystem Number The Global Title SCCP NETWORKING ASPECTS Scope and Purpose Network Structures in view of SCCP management capabilities Configurations of subsystems/nodes SCCP Management Procedures Coordinated State Change Traffic Information Management Application of Connectionless Services Connectionless Segmentation/Reassembly Message Change Message Return Maximal Length supported by SCCP connectionless segmentation/reassembly Support of SAAL capabilities Protocol Architecture Interworking...19 List Of Figures Figure 1 Global Title format for indicator 0001 (GTI = 1)...7 Figure 2 Global Title format for indicator 0010 (GTI = 2)...8 Figure 3 Solitary Node/Subsystem...8 Figure 4 Primary/Backup configuration...10 Figure 5 Centralized Backup configuration...11 Figure 6 Primary/Primary pair configuration...11 Figure 7 Decentralized Backup configuration...12 Figure 8 Multiple Prioritized configuration...13 Figure 9 SCCP Loadsharing Between N Nodes/Subsystems...13 Figure 10 SCCP Overview for connectionless services...15 Figure 11 Separate MTP networks for broadband and narrowband...18 Figure 12 Mixed broadband and narrowband network...19 Figure 13 Protocol stacks for different interworking scenarios...21 xi

12 ANSI T Chapter T Functional Description of the Signalling Connection Control Part Contents Section Page T Scope, Purpose, and Application General Objectives General Characteristic 1 2. Services Provided by the SCCP Connection-Oriented Services Connectionless Services SCCP Management Services Assumed from the MTP Description Primitives and Parameters Functions Provided by the SCCP Connection-Oriented Functions Connectionless Service Functions 17 Tables Table 1/T Network Service Primitives for Connection-Oriented 18 Services Table 2/T Parameters of the Primitive N-CONNECT 19 Table 3/T Parameters of the Primitive N-DATA 20 Table 4/T Parameters of the Primitive N-EXPEDITED DATA 20 Table 5/T Parameters of the Primitive N-RESET 21 Table 6/T Parameters of the Primitive N-DISCONNECT 21 Table 6A/T Parameters of the Primitive N-INFORM 22 Table 7/T Primitives for the Data Transfer on Permanent 22 Connections Table 8/T Primitives and Parameters of the Connectionless Service 23 Table 8A/T Parameters of the Primitive N-UNITDATA 23 Contents T i

13 ANSI T Section Page T Table 8B/T Parameters of the Primitive N-NOTICE 24 Table 8C/T Primitives and Parameters of the SCCP Management 24 Table 8D/T Parameters of the Primitive N-COORD 25 Table 8E/T Parameters of the Primitive N-STATE 25 Table 8F/T Parameters of the Primitive N-TRAFFIC 26 Table 8G/T Parameters of the Primitive N-PCSTATE 26 Table 9/T Message Transfer Part Service Primitives 26 Figures Figure 1/T Functional Diagram for the Common Channel Signalling 27 System Figure 2/T Relationship between the SCCP Protocol and Adjacent 28 Services Figure 3/T Service Primitives 28 Figure 4/T Specific Names of Service Primitives and Peer-to-Peer 28 Communication Figure 5/T Model for the Internode Communication within the SCCP 29 (Connection-Oriented Service) Figure 6/T State Transition Diagram for the Sequence of Primitives at a Connection Endpoint (Basic Transitions) 30 Annex - Network Layer Services A1. Glossary 31 A2. Relationship Among the Terms "Layer", "Entity", "Layer Service", "Layer 31 Boundary", "Layer Service Primitive", and "Peer Protocol" A3. Data Transport 31 A4. Flow Control 32 A5. Sequencing 32 A6. Acknowledgment 32 A7. Reset 32 A8. Restart 32 A9. Expedited Data 32 A10. Routing 32 Figures Figure A-1/T Layer and Peer Relationships 33 Figure A-2/T Relation between NSDU and Message with Neither 33 Segmenting nor Blocking Figure A-3/T Segmenting 34 T ii

14 ANSI T Chapter T Functional Description of the Signalling Connection Control Part 1. Scope, Purpose, and Application 1.1 General. The Signalling Connection Control Part (SCCP) provides additional functions to the Message Transfer Part (MTP) to provide both connectionless as well as connection-oriented network services to transfer circuit-related and non circuit-related signalling information and other types of information between exchanges and specialized centers in telecommunication networks (e.g., for management and maintenance purposes) via a Signalling System No. 7 (SS7) network. A functional block situated above the MTP, [See American National Standard for Telecommunications - Signalling System Number 7 (SS7) - General Information, ANSI T1.110], performs the functions and procedures of the SCCP. The SCCP is capable of using the services of the MTP as described in T to T The combination of the MTP and the SCCP is called the Network Service Part (NSP). 1.2 Objectives. The overall objectives of the SCCP are to provide the means for: (1) Logical signalling connections within the Common Channel Signalling Network (2) A transfer capability for signalling data units with or without the use of logical signalling connections. Functions of the SCCP are used for the transfer of circuit related and non circuitrelated signalling information of the ISDN User Part with or without setup of end-to-end signalling connections. These functions are described in T and T Figure 1/T illustrates the embedding of the SCCP within the common-channel signalling system. 1.3 General Characteristic Technique of Description. The SCCP is described in terms of: (1) Services provided by the SCCP (2) Services assumed from the MTP (3) Functions of the SCCP. The functions of the SCCP are performed by means of the SCCP protocol between two systems which provide the SCCP service to the user located above the SCCP layer. The service interfaces to the upper layers and to the MTP are described by means of primitives and parameters. Figure 2/T illustrates the relationship between the SCCP protocol and the adjacent services Primitives. Primitives consist of commands and their respective responses associated with the services requested of the SCCP and of the MTP, see Figure 3/T The general syntax of a primitive is shown below: T

15 ANSI T X Generic Name Specific Name Parameters (1) "X" designates the functional block providing the service ("MTP" for MTP, "N" for SCCP) (2) "Generic Name" describes the action that should be performed by the addressed layer (3) "Specific Name" indicates the direction of the primitive flow (4) "Parameters" are the elements of information which are to be transmitted between layers. Four Specific Names exist in general, see Figure 4/T : Request Indication Response Confirm Not all four Specific Names are associated with Generic Names (see Table 1/T and Table 8/T ) Peer-to-Peer Communication. Exchange of information between two peers of the SCCP is performed by means of a protocol. The protocol is a set of rules and formats by which the control information (and user data) is exchanged between the two peers. The protocol provides for: (1) The setup of logical signalling connections (2) The release of logical signalling connections (3) The transfer of data with or without logical signalling connections. A signalling connection is modeled in the abstract by a pair of queues. The protocol elements are objects on that queue added by the origination SCCP user and removed by the destination SCCP user. Each queue represents a flow control function. Figure 5/T illustrates the modes described above. (Model for the connectionless service is for further study.) Contents of ANSI T Chapter 1 contains a general description of the services provided by the MTP, the services provided by the SCCP and the functions within the SCCP. Chapter 2 defines the set of protocol elements and their embedding into messages. Chapter 3 describes the formats and codes used for the SCCP messages. Chapter 4 is a detailed description of the SCCP procedures as a protocol specification. Chapter 5 provides the performance requirements for the SCCP. Chapter 6 provides the SCCP Users Guide (Informative). 2. SERVICES PROVIDED BY THE SCCP The overall set of services is grouped into: (1) Connection-oriented services T

16 (2) Connectionless services. Four classes of services are provided by the SCCP protocol, two for connectionless services and two for connection-oriented services. The four classes are: 0 Basic connectionless class. 1 In-sequence delivery connectionless class. 2 Basic connection-oriented class. 3 Flow control connection-oriented class. In the tables defining individual primitives, the notations given below are used: M indicates a mandatory parameter; O indicates an SCCP implementation option; C indicates that the parameter is conditional; U indicates a user option; = indicates the parameter must have the same value in the indication primitive, or confirm primitive as provided in the corresponding request primitive, or response primitive, respectively. ANSI T Connection-Oriented Services. A distinction has to be made between: (1) Temporary signalling connections (2) Permanent signalling connections. Temporary signalling connection establishment is initiated and controlled by the SCCP user. Temporary signalling connections are comparable with dialed telephone connections. Permanent signalling connections are established and released by Management and are provided to the SCCP user on a semi-permanent basis (comparable with leased telephone lines), while data including reset is under control of the SCCP user. Further details are given in Temporary Signalling Connections Description. The control of a signalling connection is divided into the following phases: (1) Connection establishment phase (2) Data transfer phase (3) Connection release phase. T

17 ANSI T Connection Establishment Phase. Connection establishment procedures provide the mechanism for establishing temporary signalling connections between users of the SCCP. A signalling connection between two SCCP users may consist of one or more connection sections. A signalling connection between two SCCP users in the same node is considered an implementation dependant matter. During connection establishment, routing functions are provided by the SCCP, in addition to those provided by the MTP. At intermediate nodes, SCCP routing determines whether a signalling connection should be realized by one connection section or several concatenated connection sections. The criteria for deciding on several concatenated connection sections are implementation dependant. For Connection establishment there are two alternative boundaries between SCCP and SCCP user with different procedures; - The X.213-like boundry that is described further in , - The ISUP-embedded boundary that is described further in The X.213-like boundary requires that establishment procedures are performed by SCCP while in the case of ISUP-embedded boundary the ISUP provides the outing of the request for the set-up of a connection section. The connection refusal procedure is invoked if the SCCP or the SCCP user is unable to establish a signalling connection Data Transfer Phase. The data transfer service provides for an exchange of user data, called Network Service Data Units (NSDU), in either direction or in both directions simultaneously on a signalling connection. Each NSDU is characterized by a connection identification which allocates the message to a certain signalling connection. The data transfer service provides for segmenting of messages, concatenation of messages, flow control, error detection, sequence control and others, depending on the quality of service required by the SCCP user (two different classes of the connectionoriented service are provided by the protocol, see Chapter T ) Connection Release Phase. Connection release procedures provide the mechanism for releasing temporary signalling connections between users of the SCCP. The signalling connection may be released by either or both of the SCCP users. The signalling connection may also be released by the SCCP if the connection can not be maintained Network Service Primitives and Parameters Applicable To The X.213-Like Connection-Oriented Boundary Overview. Table 1/T gives an overview of the primitives to the upper layers and the corresponding parameters for the (temporary) connection-oriented network service. Figure 6/T shows an overview state transition diagram for the sequence of primitives at a connection endpoint. A more detailed description for the primitives and their parameters is given in the following chapters. T

18 ANSI T Connection Establishment Phase. A network service user (calling user) initiates the setup of the connection by means of the primitive "N-CONNECT request" to the SCCP. The SCCP entity evaluates the primitive and adds the protocol control information. The SCCP message [consisting of the protocol control information (PCI) and possibly an NSDU] is transmitted by means of the MTP-services to the remote peer entity of the SCCP. It evaluates and strips the PCI and sends a primitive "N-CONNECT indication" to the local network service user. On both ends of the connection the status "pending" is assumed. The called SCCP user answers with the primitive "N-CONNECT response" to the local SCCP, which sends the response SCCP message, including PCI, to the calling SCCP. The calling SCCP sends the primitive "N-CONNECT confirmation" to the calling SCCP user. The connection is now ready for data transfer. The four types of N-CONNECT applicable to the X.213-like boundary, the "request", the "indication", the "response" and the "confirmation", may or may not contain the parameters as shown in Table 2/T The parameters "called address" and "calling address" convey addresses identifying the destination/source of a communication. There are three types of addresses: (1) Global Title (2) Subsystem Number (3) Signalling Point Code The Global Title is an address such as dialed digits which does not explicitly contain information that would allow routing in the signalling network, i.e., a translation function is required. The Subsystem Number is an identification of a specific user function within a certain Signalling Point like the ISDN-User Part, the SCCP-Management, etc. The parameter "responding address" indicates to which destination the connection has been established or refused. The Responding Address parameter in the N-CONNECT confirmation primitive conveys the address of the service access point to which the signalling connection has been established. Under certain circumstances (e.g., call redirection, generic addressing), the value of this parameter may be different from the called address in the corresponding N-CONNECT request. The Responding Address parameter is present in the N-DISCONNECT primitive only in the case where the primitive is used to indicate rejection of a signalling connection establishment attempt by an SCCP user function. This parameter conveys the address of the service access point from which the N-DISCONNECT request was issued and, under circumstances like that mentioned above, the Responding Address may be different from the Called Address in the corresponding N-CONNECT request primitive. The parameter "expedited data selection" may be used to indicate during setup whether expedited data can be transferred via the connection. A negotiation will be performed between SCCP and NSP user, local and remote. The quality of service parameters are used during call setup to negotiate the protocol class for the connection and, if applicable, the flow control window size. The N-CONNECT primitives may or may not contain user data. T

19 ANSI T The parameters "source local reference" and "destination local reference" are used to allocate a primitive to a certain connection by the user and network respectively. In principle, the connection establishment has to be completed (i.e., data transfer status has to be reached) before sending or receiving data messages. If data messages arrive at the calling user before the connection establishment is finished, these data messages are discarded. In addition, user data can also be transferred to/from the SCCP within the primitives N-CONNECT and N-DISCONNECT Data Transfer Phase. During this phase, four different primitives may occur: (1) N-DATA (Table 3/T ) (2) N-EXPEDITED DATA (Table 4/T ) (3) N-RESET (Table 5/T ) The primitive "N-DATA" exists only as a "request", i.e., from the SCCP user to the local SCCP, and as an "indication" at the remote end of the connection, i.e., from the SCCP to the local SCCP user. N-DATA can occur bi-directionally, i.e., from the calling to called user or the called to calling user of the SCCP-connection. The primitive "N-EXPEDITED DATA" may only be used by the SCCP user in case of protocol class 3 connections. The primitive "N-RESET" (Table 5/T ) can occur in the data transfer state of a connection with a protocol class including flow control. N-RESET overrides all other activities and causes the SCCP to start a re-initialization procedure for sequence numbering. N-RESET appears as a "request", an "indication", a "response" and a "confirmation". After reception of an N-RESET request and before the sending of an N- RESET confirm, all NSDUs are discarded. The parameter "originator" indicates the source of the reset and can be any of the following: the "network service provider" (network originated), the "network service user" (user originated), or "undefined". The parameter "reason" indicates "network service provider congestion" or "reason unspecified" for a user originated reset. The "reason" parameter is "undefined" when the "originator" parameter is "undefined" Release Phase. The primitives for the release phase are "N-DISCONNECT request" and "N-DISCONNECT indication". These primitives are also used for the connection refusal during the connection establishment phase. Parameters are included to notify the reason for connection release/refusal and the initiator of the connection release/refusal procedure. User data may be added (see Table 6/T ). The parameter "originator" indicates the initiator of the connection release or the connection refusal. It may assume the following values: the network service provider the network service user undefined The parameter "reason" gives information about the cause of the connection release or the connection refusal. It may assume any of the following values in accordance with the value of the "originator": T

20 ANSI T (1) When the "originator" parameter indicates the "network service provider": (a) disconnection abnormal condition of non-transient nature 1 (b) disconnection abnormal condition of transient nature (c) disconnection invalid state 1 (d) disconnection release in progress 1 (e) disconnection subsystem failure (f) disconnection network failure (g) disconnection network congestion (h) connection refusal - destination address unknown (non-transient condition) ( i ) connection refusal - destination inaccessible/non-transient condition 1 ( j ) connection refusal - destination inaccessible/transient condition (k ) connection refusal - QOS not available/non-transient condition ( l ) connection refusal - QOS not available/transient condition (m) connection refusal - reason unspecified/non-transient condition (n) connection refusal - reason unspecified/transient condition (o) connection refusal - local error 1 (p) connection refusal - invalid state 1 (q) connection refusal - no translation 1 (r ) connection refusal - in restart phase 1 (s ) connection refusal - hop counter violation (t) connection refusal - subsystem failure (2) When the "originator" parameter indicates the "network service user": (a) disconnection normal condition (b) disconnection abnormal condition (c) disconnection - end user congestion (d) disconnection - end user failure (e) disconnection SCCP user originated (f ) disconnection - access congestion (g) disconnection - access failure (h) disconnection - subsystem congestion ( i ) connection refusal - non-transient condition ( j ) connection refusal - transient condition (k) connection refusal - incompatible information in NSDUs ( l ) connection refusal - end user originated (m) connection refusal - end user congestion (n) connection refusal - end user failure (o) connection refusal - SCCP user originated (p) connection refusal - access congestion (q) connection refusal - subsystem congestion (3) When the "originator" parameter is "undefined", then the "reason" parameter is also "undefined". 1) These values may be used locally at the originating/initiating node as an implementation option. T

21 ANSI T Notice Service. The primitive N-INFORM (Table 6A/T ) is used during data transfer to convey relevant network/user information. The primitive N-INFORM will contain the parameters "reason", "source local reference", and "quality of service (QOS) parameter set". The primitive "N-INFORM request" is provided to inform the SCCP of the connection user failure/congestion, or anticipated QOS changes. A further primitive "N-INFORM indication" is provided to indicate actual failures of the SCCP to the SCCP user functions or anticipated QOS changes or other indications to the SCCP user functions. The parameter "reason" contains the network/user information to be conveyed. It may assume the following values: (1) network service provider failure (2) network service provider congestion (3) network service provider QOS change (4) Network service user failure (5) network service user congestion (6) network service user QOS change (7) unspecified Network Service Primitives, Interface Elements And Parameters Applicable To The ISUP-Embedded Connection-Oriented Boundary Overview Table 6B/T gives an overview of the primitives to the SCCP user layer and the corresponding parameters for the (temporary) ISUP-embedded connection-oriented network service. The state transition diagram for the sequences of the primitives at a connection endpoint is left for further study Connection establishment making use of the ISUP-embedded procedures An SCCP user (calling user) may, instead of using the N-CONNECT.request thereby requesting SCCP to transmit appropriate PDU, use the REQUEST to solicit the SCCP to provide in the REPLY information relevant for connection establishment. The forward direction of the connection is established hop-by-hop making use of PDUs of SIUP thereby is embedded in the forward call set-up. In the backward direction, normal SCCP PDUd are used. The N-CONNECT.request is replaced at the origin by the two interface elements REQUEST type 1 and REPLY. Within intermediate nodes the two interface elements REQUEST type 2 and REPLY are required. The three types of N-CONNECT applicable to the ISUP embedded boundary, the indication, the response, and the confirm contain the parameters as shown in Table6C/T Three interface elements are defined for the information flow between the SCCP and ISDN-User Part: (1) REQUEST to the SCCP, Type 1 (2) REQUEST to the SCCP, Type 2 (3) REPLY from the SCCP The REQUEST Type 1, which requests connection establishment information for an outgoing connection section from the SCCP originating node, contains the following parameters: (1) Connection identification (O) T

22 ANSI T (2) Expedited data selection (U) (4) Quality of service parameter set (U) REQUEST type 2, contains the following parameters: (1) Quality of service parameter set (U) (2) Connection identification (O) (3) Source local reference (M) (4) Originating Signalling Point Code (M) (5) Reply request (U) (6) Refusal indicator (U) The REPLY contains the following parameters: (1) Source Local reference (M) (2) Quality of service parameter set (M) (3) Connection identification (O) Permanent Signalling Connections Description. The setup/release service is controlled by the Administration (e.g., O&M application). The functions for setup and release may be similar to those provided for temporary signalling connections. The classes of service are the same. Permanently established signalling connections may require additional safeguarding mechanisms within the endpoints (relay points) of the connection in order to guarantee their re-establishment in the case of a processor outage followed by a recovery Primitives and Parameters. The primitives and their parameters are listed in Table 7/T Their content and functionality correspond to the description within Connectionless Service. The SCCP provides the SCCP user with the ability to transfer signalling messages via the signalling network without setup of a signalling connection. In addition to the MTP-capability, a "Routing" function is provided within the SCCP which maps the called address (and any optional routing parameters) to the Signalling Point Codes of the MTP-Service. This mapping function may be provided within each node or might be distributed over the network or could be provided in some special translation centers. Under certain conditions, e.g., congestion and unavailability of subsystems and/or signalling points, connectionless messages could be discarded instead of being delivered. If the SCCP user wishes to be informed of the non-delivery of messages, the parameter "Return Option" must be set to "return message on error" in the primitive to the SCCP Description. There are two possibilities to transfer data without a connection setup with regard to the sequence control mechanisms provided by the MTP. T

23 ANSI T (1) The MTP guarantees (to a high degree of probability) an in-sequence delivery of messages which contain the same Signalling Link Selection (SLS) code. The SCCP user can demand this MTP-service by allocating a parameter "sequence control" into the primitive to the SCCP. The SCCP will put the same SLS code into the primitive to the MTP for all primitives from the SCCP user with the same sequence control parameter. (2) If the in-sequence delivery is not required, the SCCP can insert SLS codes randomly or with respect to appropriate load sharing within the signalling network Primitives and Parameters of the Connectionless Service Overview. Table 8/T gives an overview of the primitives to the upper layers and the corresponding parameters for the connectionless service Parameters Address. The parameters "called address" and "calling address" serve to identify the destination and origination respectively, of the connectionless message. These parameters may contain some combination global titles, subsystem numbers, and signalling point codes Quality of service parameter set. The quality of service parameter set contains the following parameters: sequence control, return option and message priority. (1) Sequence Control. The parameter "sequence control" indicates to the SCCP whether the user wishes the service "sequence guaranteed" or the service "sequence not guaranteed". In the case of sequence guaranteed service, this parameter is an indication to the SCCP that a given stream of messages with the same called address has to be delivered in sequence by making use of the features of the MTP. In addition, this parameter is also used to distinguish between different streams of messages such that an even distribution of SLS codes will result. (2) Return Option. The parameter "return option" is used to determine the handling of messages encountering transport problems. "Return option" may assume the following values: (a) Discard message on error (b) Return message on error (3) Message priority. The general message priority guidelines and the priority assignments for SCCP messages are provided in T Appendix B, Section B.3 and Table 4, respectively Reason for Return. The parameter "reason for return" identifies the reason why a message was not able to be delivered to its final destination. See T , 3.12, Return cause (formerly Diagnostic) for the values that may be assumed User Data. The parameter "user data" contains information that is to be transferred transparently between SCCP users Primitives T