SIST EN 301 008:2000

• Abstract:

  Description of interoperability tests between two or more products having implemented ETS 300 009 to ensure compatibility.

• Status: Published
• Publication Date: 30-Nov-2000
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• Technical Committee: SPS - Signalling protocols and switching
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2000
• Due Date: 01-Dec-2000
• Completion Date: 01-Dec-2000
• Ref Project: ETSI EN 301 008 V1.1.2 (1998-05) - Integrated Services Digital Network (ISDN); Signalling System No.7; Signalling Connection Control Part (SCCP); Interoperability test specification

SIST EN 301 008 is the Slovenian adoption of the European Telecommunications Standard for Integrated Services Digital Network (ISDN) Signalling System No.7 SCCP interoperability testing. It is published by SIST and based on ETSI EN 301 008, with the test content aimed at equipment vendors, network operators, and test labs that need to check whether separate SCCP implementations can interwork.

What does SIST EN 301 008 specify?

SIST EN 301 008 specifies a basic set of interoperability tests for nodes that meet ITU-T Recommendations Q.711 to Q.714 as modified by ETS 300 009-1. The tests are meant to build confidence that different SCCP implementations can communicate correctly, and the document says they may also be applied in national networks and to earlier versions of ETS 300 009 and the ITU-T Recommendations.

The document is organized into a short front matter, Scope, References, Abbreviations, and the main SCCP test specification. The main body then covers the test purpose, network and implementation dependencies, a typical international network configuration, the reference specification, a test list, and detailed test tables for each test.

What are the key requirements of SIST EN 301 008?

Interoperability testing is the focus, not conformance testing

SIST EN 301 008 says that conformance and performance tests are not included. In practice, that means this document is used after SCCP, its applications, and Message Transfer Part (MTP) have already passed their own validation, so the user is checking real interworking rather than basic protocol compliance.

The document also says interoperability tests are for implementations that each conform to ETS 300 009-1. The tests are a basic set only, so specific interconnections may need more testing than the document lists.

Test conditions depend on the network setup

SIST EN 301 008 notes that SCCP applications may be external to the node under test, for example an external tester. This matters because the test setup may not be built entirely from production network elements.

The document also gives practical limits. If the receiving node is a stand-alone SCCP relay, tests that rely on SubSystem Number (SSN) routing are not applicable. If SCCP and MTP availability cannot be separated in the implementation, tests that depend on different availability states cannot be run. If the nodes are in service, it is inadvisable to run tests that require MTP or SCCP to be unavailable.

The test network model uses nodes A, B, and C

SIST EN 301 008 bases all tests on a typical international network scenario with nodes A, B, and C. Node B may be a stand-alone SCCP relay, and the document notes that some relay-related tests can still be applied even when Node B is absent, by relating them to gateway nodes.

This matters in practice because the document is not tied to one exact topology. A tester can map the abstract nodes to real equipment, but the same message logic and checks still apply.

Global Title routing and error handling are the main checks

SIST EN 301 008 gives six Global Title (GT) routing tests. Together they check correct GT translation, correct message forwarding, and correct handling of inaccessible destinations or unavailable SCCP/SSN conditions.

The tests also check how the return on error option affects behavior. When the option is set, the receiving node should generate UDTS for relevant failures or translation problems. When the option is not set, UDTS should not be returned. In practice, this tells the tester whether the node handles routing errors and negative responses the way SCCP expects.

The document checks several specific routing failure cases

SIST EN 301 008 covers these cases in the GT routing tests:

• correct GT translation and a working signalling route
• temporary SCCP unavailability and later recovery
• inaccessible Destination Point Code (DPC) and/or unavailable SSN/SCCP with return on error not set
• the same unavailable conditions with return on error set
• a GT type for which no translation table can be selected
• received Global Title Address Information (GTAI) that is not present in the selected translation table

These cases matter because they separate a healthy route from translation-table problems, destination reachability problems, and SCCP availability problems. A buyer or integrator can use them to confirm that alarms, returns, and message routing behave correctly under failure conditions.

Segmented user data is checked with XUDT

SIST EN 301 008 includes one connectionless protocol class test for segmented user data. The test checks that segmented messages are transferred correctly using Extended Unitdata (XUDT) messages, and it applies only when all nodes in the test support XUDT.

The document checks the segmentation coding and the transfer of each segment, but it says reassembly is outside its scope. In practice, this means the test proves the network can carry segmented SCCP user data correctly, while end-to-end reassembly must be verified elsewhere if needed.

UDT and XUDT are treated as alternative message types where supported

SIST EN 301 008 notes that several tests refer to UnitData (Service) message (UDT(S)) messages, and that XUDT(S) may be used instead when all nodes support it. This gives implementers some flexibility while keeping the test intent the same.

For a test lab, this means the chosen message type should match the capabilities of all nodes involved so that the test remains valid.

What terms does SIST EN 301 008 define?

• Destination Point Code (DPC) - The point code that identifies the destination signalling point for a message.
• Global Title (GT) - An address form used for SCCP routing by translation rather than by direct point code only.
• Global Title Address Information (GTAI) - The address digits or information within the GT that are used for translation.
• Signalling Connection Control Part (SCCP) - The SS7 user part covered by this document and the subject of the interoperability tests.
• UnitData message (UDT) - A connectionless SCCP message used in most of the routing and error-handling tests.
• UnitData Service message (UDTS) - The returned SCCP message used when an error response is expected.
• Extended Unitdata message (XUDT) - The segmented connectionless SCCP message used in the segmented transfer test.
• SubSystem Number (SSN) - The number used to identify a subsystem within SCCP routing and availability checks.

Who uses SIST EN 301 008?

SIST EN 301 008 is used by telecom equipment vendors, signalling system engineers, interoperability test labs, and network operators that deploy SCCP-based SS7 nodes. Quality managers and buyers use it when they want a clear test basis for acceptance or pre-deployment checks.

It is especially relevant for international interconnection work, where nodes from different implementations must exchange SCCP traffic reliably. It can also be used in national networks and in older implementations where bilateral or multilateral test agreements need a common reference.

Which standards are used with SIST EN 301 008?

• ETS 300 009-1 - Provides the SCCP protocol specification that the interoperability tests assume.
• ITU-T Recommendations Q.711 to Q.714 - Provide the base SCCP recommendations that define the functions being tested.
• ITU-T Recommendation Q.786 - Provides related SCCP test specification references that the document cites for several GT routing tests.

What does the SIST EN 301 008 document contain?

SIST EN 301 008 contains a typical international network figure, a numbered test list, and detailed test tables for seven interoperability tests. The tables show message flows between nodes A, B, and C and identify the protocol class, routing indicator, GT details, and response behavior to check.

The detailed test cases cover UDT, UDTS, and XUDT exchanges, including the cases where messages are forwarded, rejected, or returned because of translation or reachability problems. The document also includes notes on SCCP availability, use of a signal monitor, and when XUDT(S) may replace UDT(S).

For practical work, the document is used to set up lab tests, verify interworking, and document whether a signalling node handles GT routing, error returns, and segmented transfer as expected.

SLOVENSKI STANDARD
3SIST EN 301 008:
01-december-
Digitalno omrežje z integriranimi storitvami (ISDN) - Signalizacija št. 7 - Krmilni del
signalizacijske zveze (SCCP) - Preskušalna specifikacija medsebojne
obratovalnosti
Integrated Services Digital Network (ISDN); Signalling System No.7; Signalling
Connection Control Part (SCCP); Interoperability test specification
Ta slovenski standard je istoveten z: EN 301 008 V1.1.2
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
3SIST EN 301 008: en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EN 301 008 V1.1.2 (1998-05)
European Standard (Telecommunications series)
Integrated Services Digital Network (ISDN);
Signalling System No.7;
Signalling Connection Control Part (SCCP);
Interoperability test specification

2 EN 301 008 V1.1.2 (1998-05)
Reference
DEN/SPS-02050 (9c000idc.PDF)
Keywords
ISDN, SS7, SCCP, testing
ETSI
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: [phone]  Fax: [phone]
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Internet
[e-mail]
http://www.etsi.fr
http://www.etsi.org
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1998.
All rights reserved.
ETSI
3 EN 301 008 V1.1.2 (1998-05)
Contents
Intellectual Property Rights.4
Foreword .4
1 Scope.5
2 References.5
2.1 Normative references. 5
2.2 Informative references . 5
3 Abbreviations.6
4 SCCP test specification.6
4.1 Introduction. 6
4.2 Network and implementation dependency considerations . 7
4.3 Test network configuration . 7
4.4 Reference specification. 7
4.5 Test list . 7
4.5.1 GT routing tests. 8
4.5.2 Connectionless protocol class tests . 8
4.6 Test tables. 9
History.24
ETSI
4 EN 301 008 V1.1.2 (1998-05)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETR 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of
ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on the ETSI
Web server (http://www.etsi.fr/ipr or http://www.etsi.org/ipr).
Pursuant to the ETSI Interim IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No
guarantee can be given as to the existence of other IPRs not referenced in ETR 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Signalling
Protocols and Switching (SPS).
National transposition dates
Date of adoption of this EN: 3 April 1998
Date of latest announcement of this EN (doa): 31 August 1998
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 28 february 1999
Date of withdrawal of any conflicting National Standard (dow): 28 February 1999
ETSI
5 EN 301 008 V1.1.2 (1998-05)
1 Scope
The present document specifies interoperability testing between nodes meeting the requirements of ITU-T
Recommendations Q.711 to Q.714 [2] as modified by ETS 300 009-1 [1]. The present document may optionally also be
applied within national networks and implementations of earlier versions of ETS 300 009 and the ITU-T
Recommendations.
The present document is not meant to restrict national networks. The tests in the present document form a basic set of
interoperability tests, and are used in gaining confidence that implementations of the Signalling Connection Control Part
(SCCP) can interwork.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, subsequent revisions do apply.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
2.1 Normative references
[1] ETS 300 009-1 (1996): "Integrated Services Digital Network (ISDN); Signalling System No.7;
Signalling Connection Control Part (SCCP) (connectionless and connection-oriented class 2) to
support international interconnection; Part 1: Protocol specification [ITU-T Recommendations
Q.711 to Q.714 and Q.716 (1993), modified]".
[2] ITU-T Recommendations Q.711 to Q.714 (1993): "Signalling Connection Control Part (SCCP)".
2.2 Informative references
[3] ITU-T Recommendation Q.786 (1993): "SCCP Test Specification".
ETSI
6 EN 301 008 V1.1.2 (1998-05)
3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
DPC Destination Point Code
DT1 Data Form 1 message
GT Global Title
GTAI Global Title Address Information
MTP Message Transfer Part
NI Network Indicator
OPC Origination Point Code
PC Point Code
SCCP Signalling Connection Control Part
SIO Service Information Octet
SP Signalling Point
SSA SubSystem Allowed message
SSN SubSystem Number
SST Subsystem Status Test message
UDT UnitData message
UDTS UnitData Service message
UPU User Part Unavailable
XUDT Extended Unitdata message
XUDTS Extended UnitData Service message
4 SCCP test specification
Conformance and performance tests are not included in the present document.
4.1 Introduction
The function of interoperability testing is to confirm that different implementations, each of which conforms to
ETS 300 009-1 [1], can interwork. These interoperability tests apply in the international network but may also be
applied in national networks. Successful conformance or validation testing of SCCP itself, SCCP applications and
Message Transfer Part (MTP) is a pre-requisite of interoperability testing. It is recommended that interoperability testing
is performed on signalling nodes that are not in service.
Interoperability testing may require the use of a monitor to check the operation of the signalling node(s) under test. The
specification of this monitor is not covered by the present document although the general requirements are that the
equipment is capable of capturing all data on the signalling link, and preferably be able to decode the information
captured into SCCP messages.
The tests in the present document are only a basic set in gaining confidence in the interoperability of SCCP
implementations. Specific interconnections may require more interoperability testing than specified here. The specific
range of tests performed between nodes is subject to bilateral or multilateral agreement and also dependent on the
functionality of the implementations under test. The tests are shown in one direction of testing, thus they should be
repeated in the reverse direction for completeness.
ETSI
7 EN 301 008 V1.1.2 (1998-05)
4.2 Network and implementation dependency considerations
SCCP applications may be external to the nodes under test (e.g. external testers).
Where the receiving node is a stand alone SCCP relay Sub System Number (SSN) routing to it cannot be used. In this
case tests using SSN routing are not applicable.
In some implementations SCCP and MTP availability are inseparable (e.g. in the case where MTP and SCCP are
handled together). In such cases tests that require the availability status of SCCP and MTP to be different cannot be run.
If the nodes under test are in service it is inadvisable to run tests that require the MTP or SCCP to be unavailable.
4.3 Test network configuration
The following network configuration is intended to show a typical international SCCP network scenario and is the basis
of all the tests in the present document. In practice, in some cases, node B (i.e. a "stand alone" SCCP relay node) may
not exist. In these cases the relay functionality part of the tests may still be applied but would relate to international
gateway nodes A and C.
National Network 2
National Network 1 International Network
SCCP Messages SCCP Messages
SCCP SCCP SCCP
MTP MTP
MTP
MTP MTP
(Nat. PC xx) (Int. PC A) (Int. PC B) (Int. PC C) (Nat. PC xx)
International SCCP Relay International G/W
International G/W
(Node B) (Node C)
(Node A)
Figure 1
4.4 Reference specification
The SCCP is described in the ETS 300 009-1 [1].
4.5 Test list
NOTE: A number of the tests given in the present document make reference to UnitData (Service) message
(UDT(S)) messages. Where supported by all the nodes in the test, Extended UnitData (Service) message
(XUDT(S)) messages may be employed as an alternative.
ETSI
8 EN 301 008 V1.1.2 (1998-05)
4.5.1 GT routing tests
Test Number 1
To verify correct Global Title (GT) translation and a correctly functioning signalling route exists between nodes under
test. The primary purpose of this test is to give confidence that a signalling relationship exists between the nodes under
test. Specific signalling functionality is tested by the other tests.
Test Number 2
To verify correct GT translation, message return and SCCP management functionality following temporary SCCP
unavailability.
Test Number 3
To verify that UDTS is not returned when GT translates to an inaccessible Destination Point Code (DPC) and/or
unavailable SSN/SCCP and the return on error option is not set.
Test Number 4
To verify that UDTS is returned when the GT translates to an inaccessible DPC and/or unavailable SSN/SCCP and the
return on error option is set.
Test Number 5
To verify that UDTS is returned when the GT is of a type that cannot be translated and the return on error option is set.
Test Number 6
To verify that UDTS is returned when unknown GT Address digits are received and the return on error option is set.
4.5.2 Connectionless protocol class tests
Test Number 7
To verify that segmented messages are correctly transferred.
ETSI
9 EN 301 008 V1.1.2 (1998-05)
4.6 Test tables
Test Number 1
Reference ITU-T Recommendation Q.714 [2], clause 2, as modified by ETS 300 009-1 [1]
Title GT translation
Subtitle Correct operation of signalling route
Purpose To verify correct Global Title translation and a correctly functioning signalling
route exists between nodes under test
Pre-test Conditions:
1. Arrange the generation of a UDT message from Node A to Node B with:
- SCCP address information:
- GT;
- route on GT.
2. Arrange the SCCP routing control data at Node B as follows:
- GT translated to DPC of Node C.
3. At node B, DPC and SCCP of Node C and, if applicable (i.e. RI Node BfiC = SSN routing), Subsystem all
available.
Expected Message Sequence
NODE A NODE B NODE C
UDT UDT
(continued)
ETSI
10 EN 301 008 V1.1.2 (1998-05)
(Test 1 continued)
Test Description:
1. Arrange Node A to send a UDT message to Node B with a GT to be translated at Node B to PC of Node C.
2. Record the message sequence and parameters using a signal monitor.
3. CHECK A: Was the UDT message correctly forwarded to Node C?
4. CHECK B: Was the message sequence as above?
5. CHECK C: Were the parameter fields set correctly as indicated in the check table below?
Check Table:
UDT (NODE A fi NODE B)
1) Protocol Class : x0000000 (Class 0); or
x0000001 (Class 1).
Called Party Address:
2) Global Title Indicator : 0100.
3) Routing Indicator: 0 (Route on GT).
4) Global Title : Address information, as appropriate.
UDT (NODE B fi NODE C)
5) Protocol Class : Identical to UDT (NODE A fi NODE B).
Called Party Address: As appropriate to addressing scheme used between Node B and Node C.
NOTE: The presence or coding of any address parameters not specifically mentioned are not critical to this test.
ETSI
11 EN 301 008 V1.1.2 (1998-05)
Test Number 2
Reference ITU-T Recommendation Q.714 [2], subclause 5.2, as modified by ETS 300 009 [1]
Title GT translation
Subtitle Updating of translation table status based on information of SCCP temporary
unavailability and subsequent availability
Purpose To verify correct GT translation, message return and SCCP management
functionality followin
...

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digitalno omrežje z integriranimi storitvami (ISDN) - Signalizacija št. 7 - Krmilni del signalizacijske zveze (SCCP) - Preskušalna specifikacija medsebojne obratovalnostiIntegrated Services Digital Network (ISDN); Signalling System No.7; Signalling Connection Control Part (SCCP); Interoperability test specification33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 301 008 Version 1.1.2SIST EN 301 008:2000en01-december-2000SIST EN 301 008:2000SLOVENSKI
STANDARD
EN 301 008 V1.1.2 (1998-05)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Signalling System No.7;Signalling Connection Control Part (SCCP);Interoperability test specificationSIST EN 301 008:2000

ETSIEN 301 008 V1.1.2 (1998-05)2ReferenceDEN/SPS-02050 (9c000idc.PDF)KeywordsISDN, SS7, SCCP, testingETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: [phone]
Fax: [phone]Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/[e-mail]://www.etsi.frhttp://www.etsi.orgCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1998.All rights reserved.SIST EN 301 008:2000

ETSIEN 301 008 V1.1.2 (1998-05)3ContentsIntellectual Property Rights.4Foreword.41Scope.52References.52.1Normative references.52.2Informative references.53Abbreviations.64SCCP test specification.64.1Introduction.64.2Network and implementation dependency considerations.74.3Test network configuration.74.4Reference specification.74.5Test list.74.5.1GT routing tests.84.5.2Connectionless protocol class tests.84.6Test tables.9History.24SIST EN 301 008:2000

ETSIEN 301 008 V1.1.2 (1998-05)4Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin ETR 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect ofETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on the ETSIWeb server (http://www.etsi.fr/ipr or http://www.etsi.org/ipr).Pursuant to the ETSI Interim IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. Noguarantee can be given as to the existence of other IPRs not referenced in ETR 314 (or the updates on the ETSI Webserver) which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical Committee SignallingProtocols and Switching (SPS).National transposition datesDate of adoption of this EN: 3 April 1998Date of latest announcement of this EN (doa): 31 August 1998Date of latest publication of new National Standardor endorsement of this EN (dop/e): 28 february 1999Date of withdrawal of any conflicting National Standard (dow): 28 February 1999SIST EN 301 008:2000

ETSIEN 301 008 V1.1.2 (1998-05)51ScopeThe present document specifies interoperability testing between nodes meeting the requirements of ITU-TRecommendations Q.711 to Q.714 [2] as modified by ETS 300 009-1 [1]. The present document may optionally also beapplied within national networks and implementations of earlier versions of ETS 300 009 and the ITU-TRecommendations.The present document is not meant to restrict national networks. The tests in the present document form a basic set ofinteroperability tests, and are used in gaining confidence that implementations of the Signalling Connection Control Part(SCCP) can interwork.2ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the presentdocument.· References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.· For a specific reference, subsequent revisions do not apply.· For a non-specific reference, subsequent revisions do apply.· A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.2.1Normative references[1]ETS 300 009-1 (1996): "Integrated Services Digital Network (ISDN); Signalling System No.7;Signalling Connection Control Part (SCCP) (connectionless and connection-oriented class 2) tosupport international interconnection; Part 1: Protocol specification [ITU-T RecommendationsQ.711 to Q.714 and Q.716 (1993), modified]".[2]ITU-T Recommendations Q.711 to Q.714 (1993): "Signalling Connection Control Part (SCCP)".2.2Informative references[3]ITU-T Recommendation Q.786 (1993): "SCCP Test Specification".SIST EN 301 008:2000

ETSIEN 301 008 V1.1.2 (1998-05)63AbbreviationsFor the purposes of the present document, the following abbreviations apply:DPCDestination Point CodeDT1Data Form 1 messageGTGlobal TitleGTAIGlobal Title Address InformationMTPMessage Transfer PartNINetwork IndicatorOPCOrigination Point CodePCPoint CodeSCCPSignalling Connection Control PartSIOService Information OctetSPSignalling PointSSASubSystem Allowed messageSSNSubSystem NumberSSTSubsystem Status Test messageUDTUnitData messageUDTSUnitData Service messageUPUUser Part UnavailableXUDTExtended Unitdata messageXUDTSExtended UnitData Service message4SCCP test specificationConformance and performance tests are not included in the present document.4.1IntroductionThe function of interoperability testing is to confirm that different implementations, each of which conforms toETS 300 009-1 [1], can interwork. These interoperability tests apply in the international network but may also beapplied in national networks. Successful conformance or validation testing of SCCP itself, SCCP applications andMessage Transfer Part (MTP) is a pre-requisite of interoperability testing. It is recommended that interoperability testingis performed on signalling nodes that are not in service.Interoperability testing may require the use of a monitor to check the operation of the signalling node(s) under test. Thespecification of this monitor is not covered by the present document although the general requirements are that theequipment is capable of capturing all data on the signalling link, and preferably be able to decode the informationcaptured into SCCP messages.The tests in the present document are only a basic set in gaining confidence in the interoperability of SCCPimplementations. Specific interconnections may require more interoperability testing than specified here. The specificrange of tests performed between nodes is subject to bilateral or multilateral agreement and also dependent on thefunctionality of the implementations under test. The tests are shown in one direction of testing, thus they should berepeated in the reverse direction for completeness.SIST EN 301 008:2000

ETSIEN 301 008 V1.1.2 (1998-05)74.2Network and implementation dependency considerationsSCCP applications may be external to the nodes under test (e.g. external testers).Where the receiving node is a stand alone SCCP relay Sub System Number (SSN) routing to it cannot be used. In thiscase tests using SSN routing are not applicable.In some implementations SCCP and MTP
availability are inseparable (e.g. in the case where MTP and SCCP arehandled together). In such cases tests that require the availability status of SCCP and MTP to be different cannot be run.If the nodes under test are in service it is inadvisable to run tests that require the MTP or SCCP to be unavailable.4.3Test network configurationThe following network configuration is intended to show a typical international SCCP network scenario and is the basisof all the tests in the present document. In practice, in some cases, node B (i.e. a "stand alone" SCCP relay node) maynot exist. In these cases the relay functionality part of the tests may still be applied but would relate to internationalgateway nodes A and C.SCCP MessagesSCCP MessagesSCCP MTP(Int. PC B)National Network 1National Network 2International NetworkInternational G/W(Node A)International G/W(Node C)International SCCP Relay(Node B)MTP(Nat. PC xx)MTP(Int. PC C)SCCP MTP(Int. PC A)MTP(Nat. PC xx)SCCPFigure 14.4Reference specificationThe SCCP is described in the ETS 300 009-1 [1].4.5Test listNOTE:A number of the tests given in the present document make reference to UnitData (Service) message(UDT(S)) messages. Where supported by all the nodes in the test, Extended UnitData (Service) message(XUDT(S)) messages may be employed as an alternative.SIST EN 301 008:2000

ETSIEN 301 008 V1.1.2 (1998-05)84.5.1GT routing testsTest Number 1To verify correct Global Title (GT) translation and a correctly functioning signalling route exists between nodes undertest. The primary purpose of this test is to give confidence that a signalling relationship exists between the nodes undertest. Specific signalling functionality is tested by the other tests.Test Number 2To verify correct GT translation, message return and SCCP management functionality following temporary SCCPunavailability.Test Number 3To verify that UDTS is not returned when GT translates to an inaccessible Destination Point Code (DPC) and/orunavailable SSN/SCCP and the return on error option is not set.Test Number 4To verify that UDTS is returned when the GT translates to an inaccessible DPC and/or unavailable SSN/SCCP and thereturn on error option is set.Test Number 5To verify that UDTS is returned when the GT is of a type that cannot be translated and the return on error option is set.Test Number 6To verify that UDTS is returned when unknown GT Address digits are received and the return on error option is set.4.5.2Connectionless protocol class testsTest Number 7To verify that segmented messages are correctly transferred.SIST EN 301 008:2000

ETSIEN 301 008 V1.1.2 (1998-05)94.6Test tablesTest Number1ReferenceITU-T Recommendation Q.714 [2], clause 2, as modified by ETS 300 009-1 [1]TitleGT translationSubtitleCorrect operation of signalling routePurposeTo verify correct Global Title translation and a correctly functioning signallingroute exists between nodes under testPre-test Conditions:1.Arrange the generation of a UDT message from Node A to Node B with:- SCCP address information:- GT;- route on GT.2.Arrange the SCCP routing control data at Node B as follows:- GT translated to DPC of Node C.3.At node B, DPC and SCCP of Node C and, if applicable (i.e. RI Node B®C = SSN routing), Subsystem allavailable.Expected Message SequenceNODE AUDT NODE BUDT NODE C(continued)SIST EN 301 008:2000

ETSIEN 301 008 V1.1.2 (1998-05)10(Test 1 continued)Test Description:1. Arrange Node A to send a UDT message to Node B with a GT to be translated at Node B to PC of Node C.2. Record the message sequence and parameters using a signal monitor.3. CHECK A: Was the UDT message correctly forwarded to Node C?4. CHECK B: Was the message sequence as above?5. CHECK C: Were the parameter fields set correctly as indicated in the check table below?Check Table:UDT (NODE A ® NODE B)1)Protocol Class:x0000000 (Class 0); orx0000001 (Class 1).Called Party Address:2)Global Title Indicator:0100.3)Routing Indicator:0 (Route on GT).4)Global Title:Address information, as appropriate.UDT (NODE B ® NODE C)5)Protocol Class:Identical to UDT (NODE A ® NODE B).Called Party Address:As appropriate to addressing scheme used between Node B and Node C.NOTE:The presence or coding of any address parameters not specifically mentioned are not critical to this test.SIST EN 301 008:2000

ETSIEN 301 008 V1.1.2 (1998-05)11Test Number2ReferenceITU-T Recommendation Q.714 [2], subclause 5.2, as modified by ETS 300 009 [1]TitleGT translationSubtitleUpdating of trans
...