ETSI EN 300 356-33 V3.2.2 (2001-09)
Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 33: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for basic services
Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 33: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for basic services
REN/SPAN-01037-3
Digitalno omrežje z integriranimi storitvami (ISDN) – Signalizacija št. 7 (SS7) – Tretja različica ISDN-uporabniškega dela (ISUP) za mednarodni vmesnik – 33. del: Abstraktni preskušalni niz (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) – Proforma specifikacija za osnovne storitve
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.SUHVNXãDQMHULWYHIntegrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 33: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for basic services33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 300 356-33 Version 3.2.2SIST EN 300 356-33 V3.2.2:2003en01-december-2003SIST EN 300 356-33 V3.2.2:2003SLOVENSKI
STANDARD
ETSI ETSI EN 300 356-33 V3.2.2 (2001-09)2
Reference REN/SPAN-01037-3 Keywords ATS, ISDN, ISUP, PIXIT, SS7, testing ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16
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
Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: editor@etsi.fr 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 2001. All rights reserved.
ETSI ETSI EN 300 356-33 V3.2.2 (2001-09)3 Contents Intellectual Property Rights.5 Foreword.5 1 Scope.7 2 References.7 3 Definitions and abbreviations.8 3.1 Definitions.8 3.2 Abbreviations.9 4 Implementation under test and test methods.10 4.1 Identification of the system and implementation under test.10 4.2 ATM and testing configuration for ISUP '92.11 4.2.1 Intermediate exchanges.11 4.2.2 Local exchanges.13 4.2.3 Master-slave aspects in the test configuration.14 5 Conventions used within the ATS.15 5.1 Test suite parameters, constants and variables.15 5.2 Test case variables.15 5.3 ASP constraints.15 5.4 Timers.15 5.5 Test suite operations.15 5.6 Aliases.15 5.7 Test case and step identifiers.16 5.8 Constraints.16 5.9 Dynamic behaviour part.16 5.10 Pre-test conditions.17 6 Test Suite Structure (TSS).18 7 Test Purposes (TP).20 7.1 Introduction.20 7.1.1 Test Purpose (TP) naming convention.20 7.1.2 Source of test purpose definition.21 7.1.3 Test Purpose structure.21 7.2 Test Purposes for the Basic Call.21 7.2.1 CSSV Circuit supervision and signalling supervision.21 7.2.2 NCS Normal call setup ordinary speech calls.47 7.2.3 NCR Normal call release.53 7.2.4 UCS Unsuccessful call setup.54 7.2.5 AS Abnormal situations.55 7.2.6 SCS Special call setup.57 7.2.7 BS Bearer services.62 7.2.8 CUF Congestion and user flow control.67 7.2.9 EC Echo control.68 7.2.10 TAR Temporary alternate routing.73 7.2.11 Hop Counter Procedure (HOP).73 7.2.12 Call Collect Request Procedure (CALLCOL).74 7.2.13 N × 64 kbit/s connection type (N × 64 k).74 8 Test coverage.83 8.1 General remarks.83 9 Conformance to the PICS proforma specification.83 Annex A (informative): Protocol Conformance Test Report (PCTR) Proforma for ISDN User Part (ISUP) v3.84 SIST EN 300 356-33 V3.2.2:2003
ETSI ETSI EN 300 356-33 V3.2.2 (2001-09)4 A.1 Identification summary.84 A.1.1 Protocol conformance test report.84 A.1.2 IUT identification.84 A.1.3 Testing environment.84 A.1.4 Limits and reservation.85 A.1.5 Comments.85 A.2 IUT Conformance status.85 A.3 Static conformance summary.85 A.4 Dynamic conformance summary.85 A.5 Static conformance review report.86 A.6 Test campaign report.86 A.7 Observations.95 Annex B (informative): PIXIT proforma for ISDN User Part (ISUP) v3 basic call.96 B.1 Identification summary.96 B.2 Abstract test suite summary.96 B.3 Test laboratory.96 B.4 Client identification.96 B.5 System under test.97 B.6 Ancillary protocols.97 B.7 Protocol information for ISUP.97 B.7.1 Protocol identification.97 B.7.2 IUT information - PIXIT proforma tables.97 B.7.2.1 General configuration.97 B.7.2.2 Parameter values.99 B.7.2.3 Timer values.99 B.7.2.4 Procedural information.100 Annex C (normative): ATS for ISDN User Part (ISUP) v3 basic call control procedures.101 C.1 The TTCN Graphical form (TTCN.GR).101 C.2 The TTCN Machine Processable form (TTCN.MP).101 Annex D (informative): Bibliography.102 History.103
ETSI ETSI EN 300 356-33 V3.2.2 (2001-09)5 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 ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http://www.etsi.org/legal/home.htm). Pursuant to the ETSI 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 ETSI SR 000 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 Services and Protocols for Advanced Networks (SPAN). The present document is part 33 of a multi-part deliverable covering the ISDN User Part (ISUP) version 3 for the international interface, as identified below: Part 1: "Basic services [ITU-T Recommendations Q.761 to Q.764 (1999) modified]"; Part 2: "ISDN supplementary service [ITU-T Recommendation Q.730 (1999) modified]"; Part 3: "Calling Line Identification Presentation (CLIP) supplementary service [ITU-T Recommendation Q.731, clause 3 (1993) modified]"; Part 4: "Calling Line Identification Restriction (CLIR) supplementary service [ITU-T Recommendation Q.731, clause 4 (1993) modified]"; Part 5: "Connected Line Identification Presentation (COLP) supplementary service [ITU-T Recommendation Q.731, clause 5 (1993) modified]"; Part 6: "Connected Line Identification Restriction (COLR) supplementary service [ITU-T Recommendation Q.731, clause 6 (1993) modified]"; Part 7: "Terminal Portability (TP) supplementary service [ITU-T Recommendation Q.733, clause 4 (1993) modified]"; Part 8: "User-to-User Signalling (UUS) supplementary service [ITU-T Recommendation Q.737, clause 1 (1997) modified]"; Part 9: "Closed User Group (CUG) supplementary service [ITU-T Recommendation Q.735, clause 1 (1993) modified]"; Part 10: "Subaddressing (SUB) supplementary service [ITU-T Recommendation Q.731, clause 8 (1992) modified]"; Part 11: "Malicious Call Identification (MCID) supplementary service [ITU-T Recommendation Q.731,
clause 7 (1997) modified]"; Part 12: "Conference Call, add-on (CONF) supplementary service [ITU-T Recommendation Q.734,
clause 1 (1993) and implementors guide (1998) modified]"; Part 14: "Explicit Call Transfer (ECT) supplementary service [ITU-T Recommendation Q.732, clause 7 (1996) and implementors guide (1998) modified]"; Part 15: "Diversion supplementary service [ITU-T Recommendation Q.732, clauses 2 to 5 (1999) modified]"; Part 16: "Call Hold (HOLD) supplementary service [ITU-T Recommendation Q.733, clause 2 (1993) modified]"; Part 17: "Call Waiting (CW) supplementary service [ITU-T Recommendation Q.733, clause 1 (1992) modified]"; SIST EN 300 356-33 V3.2.2:2003
ETSI ETSI EN 300 356-33 V3.2.2 (2001-09)6 Part 18: "Completion of Calls to Busy Subscriber (CCBS) supplementary service [ITU-T Recommendation Q.733, clause 3 (1997) modified]"; Part 19: "Three-Party (3PTY) supplementary service [ITU-T Recommendation Q.734, clause 2 (1996) and implementors guide (1998) modified]"; Part 20: "Completion of Calls on No Reply (CCNR) supplementary service [ITU-T Recommendation Q.733, clause 5 (1999) modified]"; Part 21: "Anonymous Call Rejection (ACR) supplementary service [ITU-T Recommendation Q.731, clause 4 (1993)]"; Part 31: "Protocol Implementation Conformance Statement (PICS) proforma specification for basic services"; Part 32: "Test Suite Structure and Test Purposes (TSS&TP) specification for basic services"; Part 33: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for basic services"; Part 34: "Protocol Implementation Conformance Statement (PICS) proforma specification for supplementary services"; Part 35: "Test Suite Structure and Test Purposes (TSS&TP) specification for supplementary services"; Part 36: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for supplementary services". NOTE: Parts 13 and 22 to 30 have not been issued.
National transposition dates Date of adoption of this EN: 21 September 2001 Date of latest announcement of this EN (doa): 31 December 2001 Date of latest publication of new National Standard or endorsement of this EN (dop/e):
30 June 2002 Date of withdrawal of any conflicting National Standard (dow): 30 June 2002
ETSI ETSI EN 300 356-33 V3.2.2 (2001-09)7 1 Scope The present document contains the validation (conformance) test specification for ISUP v3 basic call control and signalling procedures defined in ITU-T Recommendation Q.764 [13] as endorsed by EN 300 356-1 [1]. The present document applies only to exchanges having implemented the ISUP v3 protocol specification. It is applicable for validation testing of all types of exchanges as defined in the ISUP v3 protocol specification. NOTE: The compatibility tests are covered by ITU-T Recommendation Q.784.1 [9]. 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, the latest version applies. [1] ETSI EN 300 356-1 (V3.2.2): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 1: Basic services [ITU-T Recommendations Q.761 to Q.764 (1997), modified]". [2] ISO/IEC 9646-1 (1994): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". [3] ISO/IEC 9646-3: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)". [4] ISO/IEC 9646-5 (1994): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 5: Requirements on test laboratories and clients for the conformance assessment process". [5] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [6] ITU-T Recommendation E.164 (1997): "The international public telecommunication numbering plan". [7] ITU-T Recommendation Q.701 (1993): "Functional description of the message transfer part (MTP) of Signalling System No. 7". [8] ITU-T Recommendation Q.707 (1988): "Testing and maintenance". [9] ITU-T Recommendation Q.784.1 (1996): "Validation and compatibility for ISUP'92 and Q.767 protocols". [10] ITU-T Recommendation Q.784.2 (1997): "Abstract test suite for ISUP'92 basic call control procedures". [11] ITU-T Recommendation Q.784.3 (1999): "ISUP '97 basic call control procedures - Test suite structure and test purposes (TSS&TP)". [12] ITU-T Recommendation Q.761 (1997): "Signalling System No. 7 - ISDN User Part functional description". [13] ITU-T Recommendation Q.764 (1997): "Signalling System No. 7 - ISDN user part signalling procedures". [14] ITU-T Recommendation Q.730: "ISDN user part supplementary services". SIST EN 300 356-33 V3.2.2:2003
ETSI ETSI EN 300 356-33 V3.2.2 (2001-09)8 [15] ITU-T Recommendation Q.731: "Stage 3 description for number identification supplementary services using Signalling System No. 7". [16] ITU-T Recommendation Q.733: "Stage 3 description for call completion supplementary services using Signalling System No. 7". [17] ITU-T Recommendation Q.737: "Stage 3 description for additional information transfer supplementary services using Signalling System No. 7". [18] ITU-T Recommendation Q.735: "Stage 3 description for community of interest supplementary services using Signalling System No. 7". [19] ITU-T Recommendation Q.734 (1993): "Stage 3 description for multiparty supplementary services using Signalling System No. 7". [20] ITU-T Recommendation Q.732: "Stage 3 description for call offering supplementary services using Signalling System No. 7". [21] ITU-T Recommendation Q.762 (1997): "Signalling System No. 7 - ISDN User Part general functions of messages and signals". [22] ITU-T Recommendation Q.763 (1997): "Signalling System No. 7 - ISDN User Part formats and codes". [23] ITU-T Recommendation Q.767 (1991): "Application of the ISDN user part of CCITT signalling system No. 7 for international ISDN interconnections". [24] ITU-T Recommendation Q.724 (1988): "Telephone user part signalling procedures". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: • terms defined in ISDN User Part (ISUP) reference specification ITU-T Recommendations Q.761 [12], Q.762 [21], Q.763 [22] and Q.764 [13] as endorsed by EN 300 356-1 [1]; • terms defined in ISO/IEC 9646-1 [2], ISO/IEC 9646-3 [3] and in ISO/IEC 9646-7 [5]. In particular, the following terms apply: Abstract Test Case (ATC): complete and independent specification of the actions required to achieve a specific test purpose, defined at the level of abstraction of a particular Abstract Test Method, starting in a stable testing state and ending in a stable testing state (see ISO/IEC 9646-1, clause 3.3.3) Abstract Test Method (ATM): description of how an IUT is to be tested, given at an appropriate level of abstraction to make the description independent of any particular realization of a Means of Testing, but with enough detail to enable abstract test cases to be specified for this method (see ISO/IEC 9646-1, clause 3.3.5) Abstract Test Suite (ATS): test suite composed of abstract test cases (see ISO/IEC 9646-1, clause 3.3.6) Implementation Under Test (IUT): implementation of one or more OSI protocols in an adjacent user/provider relationship, being part of a real open system which is to be studied by testing (see ISO/IEC 9646-1, clause 3.3.43) ISDN number: number conforming to the numbering and structure specified in ITU-T Recommendation E.164 Means of Testing (MOT): combination of equipment and procedures that can perform the derivation, selection, parameterization and execution of test cases, in conformance with a reference standardized ATS, and can produce a conformance log (see ISO/IEC 9646-1, clause 3.3.54) PICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system becomes the PICS SIST EN 300 356-33 V3.2.2:2003
ETSI ETSI EN 300 356-33 V3.2.2 (2001-09)9 PIXIT proforma: document, in the form of a questionnaire, which when completed for the IUT becomes the PIXIT Point of Control and Observation: point within a testing environment where the occurrence of test events is to be controlled and observed, as defined in an Abstract Test Method (see ISO/IEC 9646-1, clause 3.3.64) Pre-test condition: setting or state in the IUT which cannot be achieved by providing stimulus from the test environment Protocol Implementation Conformance Statement (PICS): statement made by the supplier of a protocol claimed to conform to a given specification, stating which capabilities have been implemented (see ISO/IEC 9646-1, clause 3.3.39 and clause 3.3.80) Protocol Implementation eXtra Information for Testing (PIXIT): statement made by a supplier or implementor of an IUT (protocol) which contains or references all of the information related to the IUT and its testing environment, which will enable the test laboratory to run an appropriate test suite against the IUT (see ISO/IEC 9646-1, clause 3.3.41 and clause 3.3.81) System Under Test (SUT): real open system in which the IUT resides (see ISO/IEC 9646-1, clause 3.3.103) User: access protocol entity at the User side of the user-network interface where a T reference point or coincident S and T reference point applies 3.2 Abbreviations The ISUP message acronyms can be found in table 2 of ITU-T Recommendation Q.762 [21] as endorsed by EN 300 356-1 [1]. For the purposes of the present document, the following abbreviations apply: ACH Access signalling PCO - (D-channel) APH Access physical circuit PCO - (B-channel) ASP Abstract Service Primitive ATC Abstract Test Case ATM Abstract Test Method ATS Abstract Test Suite CAB PCO for AB circuits CAC PCO for AC circuits CIC Circuit Identification Code DLE Destination Local Exchange DSS1 Digital Subscriber System No. one ISDN Integrated Services Digital Network ISUP ISDN User Part
IncIE Incoming International Exchange. ITE International Transit Exchange.
IUT Implementation Under Test LAB PCO for signalling link AB LAC PCO for signalling link AC LT Lower Tester MMI Man Machine Interface MNT Maintenance PCO MOT Means Of Testing MTC Main Test Component NTE National Transit Exchange OLE Originating Local Exchange OPR Operator PCO OutIE Outgoing International Exchange PCO Point of Control and Observation PCTR Protocol Conformance Test Report PICS Protocol Implementation Conformance Statement PIXIT Protocol Implementation eXtra Information for Testing PTC Parallel Test Component SCS System Conformance Statement SIST EN 300 356-33 V3.2.2:2003
ETSI ETSI EN 300 356-33 V3.2.2 (2001-09)10 SP Signalling Point SUT System Under Test TP Test Purpose TCP Test Coordination Procedures TSS Test Suite Structure TSS&TP Test Suite Structure and Test Purposes TTCN Tree and Tabular Combined Notation UNI User-Network Interface UT Upper Tester 4 Implementation under test and test methods 4.1 Identification of the system and implementation under test The system under test (SUT) is an exchange. SUT Exchange MMI capabilities and functions ISUP Access ISUP ISUP '92 IUT
Figure 1/ITU-T Recommendation Q.784.2 [10]: Exchange as SUT The implementation under test (IUT) is the ISUP '97 implementation in this exchange, as shown in figure 1/ITU-T Recommendation Q.784.2 [10]. The aim of the ISUP implementation is to assure capabilities and functions for circuit and signalling supervision on one hand and for call handling on the other. Circuit supervision is done mainly through the MMI (man machine interface) of the exchange. The MMI interface is implementation dependent and thus not standardized. The effects of signalling procedures of the ISDN User Part can be observed on the NNI (network-network interface), on the circuits controlled by the ISUP. The ISUP signalling protocol can be observed on the SS7 link on the NNI. The ISUP implementation will in some exchanges have to interwork with the access signalling system on the UNI (user-network interface) and involve call handling in order to establish end-to-end connections. From the ISUP reference standard several types of exchanges (or roles) can be identified as presented in figure 2/ITU-T Recommendation Q.784.2 [10]. SIST EN 300 356-33 V3.2.2:2003
ETSI ETSI EN 300 356-33 V3.2.2 (2001-09)11 Access Access intermediate local local Transit NTE Gateway OutIE Transit ITE Gateway IncIE national network international network national network DLE OLE
Figure 2/ITU-T Recommendation Q.784.2 [10]: Roles of exchanges The exchanges can be divided in two main groups according to their functionality: local exchanges, where calls originate and terminate, and intermediate exchanges, with transit functionality. Local exchanges are national, i.e. belong to a national network. Intermediate exchanges are national or international. The international intermediate exchanges which permit access to the international network are the gateway exchanges (incoming and outgoing), also called ISCs - international switching centres. The roles of the exchanges are summarized in table 1/ITU-T Recommendation Q.784.2 [10]. Table 1/ITU-T Recommendation Q.784.2 [10]: Roles of exchanges
Local Intermediate Exchange
Exchange National International Originating Local Exchange TypeA OLE
Transit Exchange TypeB
NTE ITE Incoming/Gateway Exchange TypeA
IncIE Outgoing/Gateway Exchange TypeA
OutIE Destination Local Exchange TypeA DLE
4.2 ATM and testing configuration for ISUP '92 The Abstract Test Method (ATM) chosen for the ISUP '97 testing specification is the distributed multiparty test method. The ATM is defined at an appropriate level of abstraction so that the test cases may be specified appropriately, without adding restrictions to the implementation under test. The testing architectures are described in the following clauses. The ATS is written in concurrent TTCN. 4.2.1 Intermediate exchanges The configuration proposed for testing intermediate exchanges is shown in figure 3/ITU-T Recommendation Q.784.2 [10]. In order to test the protocol and functionality of transit and gateway exchanges one needs to consider the incoming and outgoing side of the SUT. SIST EN 300 356-33 V3.2.2:2003
ETSI ETSI EN 300 356-33 V3.2.2 (2001-09)12 SP A SP B IUT TCP MNT CAB LAB LT ISUP link Circuits TCP LT LT Physical aspects Circuits ISUP link SP C CAC LAC UT Maintenance Network service provider Network service provider LT
Figure 3/ITU-T Recommendation Q.784.2 [10]: ISUP test method for intermediate exchanges The IUT is observed and controlled from two ISUP links with associated circuits. The points of control and observation (PCO) are labelled LAB and CAB on one side, and LAC and CAC on the other.
The LAB and LAC PCOs are used by the lower testers (LT) for controlling the ISUP signalling link, whereas the CAB and CAC PCOs are used by the lower testers for observing circuit related events, such as connectivity, echo control check, alerting tone, etc. The ISUP PDUs to be sent and observed on the LAB PCO side allow for PDU constraints to be specified and coded down to the bit-level. The MNT PCO is used by the upper tester (UT) to control and observe the maintenance functions of the exchange. The underlying network service provider is the Message Transfer Part (MTP) protocol as specified in ITU-T Recommendation Q.701 [7] to ITU-T Recommendation Q.707 [8]. Figure 4/ITU-T Recommendation Q.784.3 [11] shows the actual used configuration for intermediate exchanges, with a main testing component (MTC), responsible for the A-B interface and a slave parallel testing component (PTC), responsible for the C-A interface. The maintenance PCO (MNT) and the operator PCO (OPR), needed for a limited number of test cases are integrated in the MTC, for simplifying reasons. The test coordination procedures (TCP) allow for communication between the testers. The test components are mostly implicitly coordinated (asynchronously); the TCPs are only used when it is necessary to obtain the verdict from the parallel test component. TCP
PTC
MTC
Maintenance
operator
ISUP
signalling,
circuits
MNT
OPR
ISUP
signalling,
circuits
IUT
SP C
SP B
CAB
LAB
CAC
LAC
SP A
Network service provider
Network service provider
Figure 4/ITU-T Recommendation Q.784.2 [10]: ISUP test configuration for intermediate exchanges SIST EN 300 356-33 V3.2.2:2003
ETSI ETSI EN 300 356-33 V3.2.2 (2001-09)13 4.2.2 Local exchanges When testing a local exchange as specified in the reference standard, it is difficult, if not impossible, to observe only ISUP PDUs, if functionality such as connectivity, tones and announcements etc. associated with protocol events is to be considered and used to assign verdicts. The reference standard often refers to actions or events initiated by or to be observed by the calling or called user. A Point of Control of Observation (PCO) from ISUP (IUT) to the access side is needed, e.g. for stimulating the local exchange to originate a call (send an IAM). Another PCO is needed to check connectivity or to check tones generated etc. by the local exchange. There is no exposed interface from ISUP (the IUT) towards the access side. For practical testing purposes the natural choice is the access interface. It is therefore reasonable to make use of the access interface (e.g. the user access interface DSS1) as a PCO and to use existing naming conventions for the abstract service primitives (ASPs) to be used on this PCO. Figure 5/ITU-T Recommendation Q.784.3 [11] presents a multiparty testing configuration for local exchanges. In this figure each tester has a single PCO. The PCO for the access uses the underlying access service provider (e.g. LAPD, in case of DSS1) for observing access events and stimulating the ISUP via the access. The ISUP implementation (IUT) cannot be tested without involving the user-network interface (UNI). SP A SP B IUT TCP MNT CAB LAB TCP ACH Access service provider Physical aspects APH UNI LT Announcements tones, etc. UT Maintenance LT Call handling LT Circuits LT ISUP link Network service provider
Figure 5/ITU-T Recommendation Q.784.2 [10]: ISUP test method
for originating/destination exchanges On the right side there are two PCOs as in the test configuration presented in the previous clause. The LAB PCO is used by the LT controlling the ISUP signalling link, whereas the CAB PCO is used by another LT controlling the traffic channels (for observing circuit related events, such as connectivity, echo control check, alerting tone, etc.). The ISUP PDUs to be sent and observed on the LAB PCO side allow for PDU constraints to be specified and coded down to the bit level. The MNT PCO is used by the Upper Tester to control and observe the maintenance functions of the exchange. On the access side there are two PCOs and two LTs similar to the ones on network side. The ACH PCO is used to observe and control the Call Handling events, whereas the APH is used to control and observe physical aspects (e.g. tones and announcements). The access PDUs to be sent and observed on the ACH PCO are chosen at an appropriate level of abstraction. For the access ASPs DSS1-like primitive names have been used, whereas access PDU constraints have not been coded to the bit level. The access aspects cannot be left out for local exchanges, widening in this respect to some extent the scope of the ISUP testing. SIST EN 300 356-33 V3.2.2:2003
ETSI ETSI EN 300 356-33 V3.2.2 (2001-09)14 Figure 6/ITU-T Recommendation Q.784.3 [11] shows the actual used configuration for local exchanges, with a master testing component (MTC), responsible for the A-B interface and a slave parallel testing component (PTC), responsible for the UNI access interface. The maintenance PCO is integrated in the MTC, for simplifying reasons. CAB LAB TCP PTC IUT MNT Maintenance SP B MTC ACH Call handling APH UNI SP A Access service provider Network service provider ISUP signalling, circuits
Figure 6/ITU-T Recommendation Q.784.2 [10]: ISUP test configuration for local exchanges 4.2.3 Master-slave aspects in the test configuration Figures 4/ITU-T Recommendation Q.784.3 [11] and 6/ITU-T Recommendation Q.784.3 [11] show the logical test components of the adopted test configuration. The main test component is located on the right side of the IUT, whereas on the left side there are different parallel test components: ISUP (see figure 4/ITU-T Recommendation Q.784.2 [10]) and access (see figure 6/ITU-T Recommendation Q.784.2 [10]). The ATS is written so that the appropriate configuration is chosen - depending on the exchange's role to be tested. The right side main test component may be international or national ISUP and is configurable so that any two of these may be run - based on the answers given to PIXIT questions. The left side parallel test component may be of any kind: it may be international or national ISUP, an access signalling system or a non-ISUP user part. At test execution exactly one of these configurations will be chosen - based on the information provided in the PICS and PIXIT. For the gateway exchanges it is assumed by default that the call is set up from the left PTC to the right MTC. In some test cases the call set up is done in the reverse direction. These test cases are marked in the ATS with the configuration field set to "reversed". They have to be executed with a different set of PIXIT settings. The message flow in the test cases is designed in such a way that the verdict is assigned based on observing the behaviour on the right side. The left side will in this case mainly act as a slave stimulus/acceptor. There are, however, test cases where the expected behaviour of both sides is needed to assign the verdict. An example of such a test case is the release on both sides after T7 (waiting for ACM) expiry, where the final verdict has to be based on the verdicts assigned on both the AB and the AC interfaces. SIST EN 300 356-33 V3.2.2:2003
ETSI ETSI EN 300 356-33 V3.2.2 (2001-09)15 5 Conventions used within the ATS Abbreviations for ISUP messages and parameters are used consistently throughout the present document. Abbreviations for the signalling information of ISUP as defined in ITU-T Recommendation Q.762 [21] endorsed by EN 300 356-1 [1] are consistently used within the ATS and are useful for understanding and/or maintaining the coding detail level. 5.1 Test suite parameters, constants and variables Most test suite parameters are named using the pattern: TSP_Xxx Most test suite variables are named using the pattern: TSV_Xxx All test suite constants are named using the pattern: TSC_Xxx 5.2 Test case variables Most test case variables are named using the pattern: TCV_Xxx 5.3 ASP constraints The naming scheme for ASP constraints is: PDU_XY_more_specific Where PDU indicates the PDU type included, XY indicates the direction and more_specific (if any) describes the constraint with abbreviated naming convention. EXAMPLE: IAM_BA_PDC - indicates an IAM sent from SP B to SP A, with a propagation delay counter. 5.4 Timers All timers are named using the pattern: TN[_min or _max]
EXAMPLE: T7, T7_min, T7_max. 5.5 Test suite operations Most names for test suite operations follow the scheme: TSO_TestSuiteOperationName The TSO functions are specified using the syntax of C programming language. 5.6 Aliases Aliases are extensively used instead of cumbersome names for ASP primitives (like MTP TRANSFER_IND). They are named using the scheme: - S_XXX for the sending of an ISUP message XXX which resolves to the MTP TRANSFER_REQ primitive; - R_XXX for the receipt of an ISUP message XXX which is resolved to the MTP TRANSFER_IND primitive. SIST EN 300 356-33 V3.2.2:2003
ETSI ETSI EN 300 356-33 V3.2.2 (2001-09)16 5.7 Test case and step identifiers The general naming convention for the test cases is: ISB_{X}_n_n_n._{a}_{n_a} - where × is either: V - valid stimulus, I - inopportune stimulus or S - syntactically invalid stimulus; n is a one or two digit test case number aligned with ITU-T Recommendation Q.784.1 [9] and a is a lowercase letter to distinguish between tests in case of variants. The last number plus lower case letter is sometimes used to further distinguish between test cases. The general naming convention for the dispatcher test steps is: S_n_n_n - where the n-s are the same as the test case to which they relate. The dispatched "slaves" are named as follows: - ISUP slave: I_n_n_n. - access slave: A_n_n_n. - non-ISUP slave: T_n_n_n. Some generic steps with appropriate names, e.g. to complete the call-setup (+S_ACM_etc_BA, +R_ACM_etc_AC) are also used. 5.8 Constraints The constraints visible on the test case level are all ASP constraints. The ASPs are chained to PDU constraints every time an ISUP message is involved. This allows for a higher level of abstraction on the test case level and hides the information in the ASP constraint part. In the case of access PDUs, no further PDU constraints are defined. Generally derived PDU constraints are avoided for simplicity reasons. 5.9 Dynamic behaviour part The general scheme of running a test case can be described shortly as follows: - firstly, the control is given to the main test component, which starts executing. This main test component controls and observes the IUT on the AB signalling link; - secondly after possibly initializing some data the main test component creates the corresponding parallel test component. This component is the slave process and it is located in a separate test step. It is dispatched using a parameter derived from the role of the exchange to be tested. For each test case exactly one concurrent "slave" parallel test component, either ISUP, or access, or non-ISUP is created. For example if the test configuration requires an ISUP tester on the left side, then the ISUP parallel test component is created, a.s.o; - the main (right) and the parallel (left) test components will then cooperate, most of the time asynchronously driven by the received messages, until the test purpose is achieved and the verdict is set; - the behaviour description is kept on an abstract level, hiding whenever it is possible programming details in the underlying test steps. Test steps are used whenever this saves code without decreasing the readability of the test case. Often functionally related test steps are grouped together using local trees; - the comment fields are extensively used. The message sequence chart for the chosen testing configuration is provided at test case level to quickly give an overview of the expected behaviour. For optimal readability a non-proportional font is used for printing the arrow diagrams. SIST EN 300 356-33 V3.2.2:2003
ETSI ETSI EN 300 356-33 V3.2.2 (2001-09)17 5.10 Pre-test conditions For each test it is assumed that the circuits are unblocked from both sides and idle. Some particular test cases need special pre-test conditions. These are presented in the table 2/ITU-T Recommendation Q.784.3 [11]. Table 2/ITU-T Recommendation Q.784.3: Special pre-test conditions Pre-test condition Test case Arrange the data in the IUT su
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...