SIST EN 301 060-3:2000

• Abstract:

  Test specification for DE/SPS-05109-1

• 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
• Mandate: BC-T-338
• Ref Project: ETSI EN 301 060-3 V1.1.3 (1998-11) - Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Basic call control; Enhancement at the b service entry point for Virtual Private Network (VPN) applications; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user

SIST EN 301 060-3:2000 is the Slovenian adoption of ETSI EN 301 060-3 for ISDN DSS1 basic call control enhancements at the "b" service entry point for VPN applications. It specifies the Test Suite Structure and Test Purposes (TSS&TP) for the user side, so it tells testers what to check on an Implementation Under Test (IUT) and how to group those checks by call state and behavior. In practice, it is a conformance testing document for user-side implementations that need to support the VPN call-control procedures defined in the related protocol parts.

What does SIST EN 301 060-3:2000 specify?

SIST EN 301 060-3:2000 specifies the user-side TSS&TP for the ISDN DSS1 protocol enhancements used for Virtual Private Network (VPN) applications at the T reference point. The scope is conformance-oriented: it gives the test purposes for checking protocol procedures and switching functions against EN 301 060-1 and related testing guidance.

The document is organized into seven clauses:

• Clause 1 - Scope
• Clause 2 - Normative references
• Clause 3 - Definitions and abbreviations
• Clause 4 - Test Suite Structure (TSS)
• Clause 5 - Test Purposes (TP)
• Clause 6 - Compliance
• Clause 7 - Requirements for a comprehensive testing service

Clause 4 groups the tests by call state and behavior. Clause 5 expands those groups into individual test purposes for valid, inopportune, syntactically invalid, and active behavior.

What are the key requirements of SIST EN 301 060-3:2000?

The document structures tests by call state and stimulus type

SIST EN 301 060-3:2000 organizes its test purposes around call states such as U00, U01, U02, U03, U04, U07, U08, U09, U10, U11, U12, U19, U25, R00 and R01, plus the message segmentation procedure. Each state is split into valid, inopportune, syntactically invalid, and active groups where applicable. In practice, this lets a tester pick the right checks for the exact state an IUT should be in.

Test purpose identifiers are structured and traceable

Clause 5.1 defines the TP identifier format as a layered code that includes the layer, IUT type, state, group, and sequence number. The group codes are V, I, S, and A for valid, inopportune, syntactically invalid, and active test cases. This matters because each TP can be traced to its state, behavior class, and origin.

The test strategy is black-box and based on observable behavior

Clause 5.1.4 states that the TPs are built from the base protocol and the PICS specification, and that they focus on externally observable behavior. The tests are limited to realistic situations an implementation is likely to face. For a reader, this means the document is meant for conformance testing of what the equipment does on the wire, not for internal design checks.

State testing uses explicit status verification

Clause 5.1.5 explains that when a TP refers to a final call state, the IUT state is verified through the STATUS ENQUIRY and STATUS exchange defined in the base protocol. The STATUS message carries the current call state in the Call state information element. In practice, the implementation must be able to report and confirm its call state during testing.

Error handling is tested in detail

Clause 5.1.6 and the state-specific TP groups check how the IUT handles invalid call references, dummy and global call references, short messages, wrong protocol discriminators, missing or malformed information elements, and duplicated Display information elements. The expected reactions include no response, STATUS, RELEASE, or RELEASE COMPLETE, depending on the case. This is important because VPN call control must remain stable and predictable when messages are wrong or out of sequence.

Timers and call control actions are part of the scope

The TP groups include timer-driven behavior for T303, T304, T310, and T313, plus call-control actions such as SETUP, CALL PROCEEDING, ALERTING, CONNECT, DISCONNECT, RELEASE, INFORMATION, PROGRESS, and STATUS ENQUIRY. These tests show whether an implementation changes state and sends the right message when a timer expires or a peer message arrives.

What terms does SIST EN 301 060-3:2000 define?

• Implementation Under Test (IUT) - the equipment or protocol stack being checked for conformance.
• Protocol Implementation Conformance Statement (PICS) - the implementer’s statement of which protocol options and features are supported.
• Protocol Implementation eXtra Information for Testing (PIXIT) - the extra implementation details needed to run certain tests.
• Test Purpose (TP) - a single test objective that states the stimulus and the expected reaction.
• Test Suite Structure (TSS) - the way the test purposes are grouped, here mainly by call state and behavior type.
• Abstract Test Suite (ATS) - the abstract test cases derived from the test purposes for conformance testing.

Who uses SIST EN 301 060-3:2000?

SIST EN 301 060-3:2000 is used by protocol implementers, conformance test labs, quality teams, and buyers who need to verify ISDN DSS1 VPN user-side behavior. It is relevant for equipment that performs basic call control over public ISDN access, especially where VPN call handling must match the specified procedures. Test engineers use it to derive test cases, and quality managers use it to check that declared features match the selected PICS items.

Which standards are used with SIST EN 301 060-3:2000?

• EN 301 060-1 and EN 301 060-2 - define the protocol behavior and the PICS proforma that this TSS&TP checks.
• EN 300 403-1, ETS 300 403-2, EN 300 403-3, and ETS 300 403-5 - provide the base DSS1 basic call control protocol, SDL diagrams, PICS proforma, and ATS context.
• ETS 300 406 - gives the standardization methodology for protocol conformance testing.
• ISO/IEC 9646-1, ISO/IEC 9646-3, and ISO/IEC 9646-7 - provide the conformance testing framework, TTCN, and implementation conformance statement rules.
• CCITT Recommendation I.130, ITU-T Recommendation E.164, ITU-T Recommendation I.112, ITU-T Recommendation I.210, and ITU-T Recommendation I.411 - provide the service characterization, numbering, ISDN vocabulary, service principles, and reference configurations used by the document.

What does the SIST EN 301 060-3:2000 document contain?

Table 1 gives the TP identifier naming convention, and Table 2 gives the structure of a single TP. The main body then lists test purposes by call state and by behavior class, with detailed cases for message handling, call-state transitions, error handling, and timer expiry. The TP catalogue covers the user-side behavior for SETUP, CALL PROCEEDING, ALERTING, CONNECT, DISCONNECT, RELEASE, STATUS, STATUS ENQUIRY, INFORMATION, and PROGRESS procedures. Clause 6 adds compliance material, and clause 7 gives requirements for a comprehensive testing service.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.JUDGEDIntegrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Basic call control; Enhancement at the b service entry point for Virtual Private Network (VPN) applications; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 301 060-3 V1.1.33SIST EN 301 060-3:en01-december-3SIST EN 301 060-3:SLOVENSKI
STANDARD
EN 301 060-3 V1.1.3 (1998-11)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Digital Subscriber Signalling System No. one (DSS1) protocol;Basic call control;Enhancement at the "b" service entry point forVirtual Private Network (VPN) applications;Part 3: Test Suite Structure and Test Purposes (TSS&TP)specification for the userSIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)2ReferenceDEN/SPS-05109-3 (9tcr0ie0.PDF)KeywordsISDN, DSS1, basic, VPN, TSS&TP, userETSIPostal 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] copies of this ETSI deliverablecan be downloaded fromhttp://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 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)3ContentsIntellectual Property Rights.6Foreword.61Scope.72Normative references.73Definitions and abbreviations.83.1Definitions.83.1.1Definitions related to conformance testing.83.1.2Definitions related to EN 301 060-1.93.2Abbreviations.94Test Suite Structure (TSS).95Test Purposes (TP).115.1Introduction.115.1.1TP naming convention.115.1.2Source of TP definition.115.1.3TP structure.125.1.4Test strategy.125.1.5Test of call states.135.1.6Test of inopportune and syntactically invalid behaviour.135.2TPs for the basic call control VPN, layer 3, user.135.2.1Null call state U00.135.2.1.1Valid.135.2.1.2Inopportune.155.2.1.3Syntactically invalid.165.2.1.4Active.175.2.2Call Initiated call state U01.185.2.2.1Valid.185.2.2.2Inopportune.185.2.2.3Syntactically invalid.195.2.2.4Active.205.2.3Overlap sending call state U02.205.2.3.1Valid.205.2.3.2Inopportune.205.2.3.3Syntactically invalid.215.2.3.4Active.225.2.4Outgoing call proceeding call state U03.225.2.4.1Valid.225.2.4.2Inopportune.235.2.4.3Syntactically invalid.245.2.4.4Active.245.2.5Call delivered call state U04.255.2.5.1Valid.255.2.5.2Inopportune.255.2.5.3Syntactically invalid.265.2.5.4Active.275.2.6Call received call state U07.275.2.6.1Valid.275.2.6.2Inopportune.275.2.6.3Syntactically invalid.285.2.6.4Active.295.2.7Connect request call state U08.295.2.7.1Valid.295.2.7.2Inopportune.305.2.7.3Syntactically invalid.30SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)45.2.7.4Active.315.2.8Incoming call proceeding call state U09.315.2.8.1Valid.315.2.8.2Inopportune.325.2.8.3Syntactically invalid.335.2.8.4Active.335.2.9Active call state U10 (incoming call).345.2.9.1Valid.345.2.9.2Inopportune.355.2.9.3Syntactically invalid.365.2.9.4Active.365.2.10Active call state U10 (outgoing call).375.2.10.1Valid.375.2.10.2Inopportune.385.2.10.3Syntactically invalid.385.2.10.4Active.395.2.11Disconnect request call state U11 (incoming call).395.2.11.1Valid.395.2.11.2Inopportune.405.2.11.3Syntactically invalid.415.2.11.4Active.415.2.12Disconnect request call state U11 (outgoing call).425.2.12.1Valid.425.2.12.2Inopportune.425.2.12.3Syntactically invalid.435.2.12.4Active.435.2.13Disconnect indication call state U12 (incoming call).445.2.13.1Valid.445.2.13.2Inopportune.445.2.13.3Syntactically invalid.455.2.13.4Active.455.2.14Disconnect indication call state U12 (outgoing call).465.2.14.1Valid.465.2.14.2Inopportune.465.2.14.3Syntactically invalid.475.2.14.4Active.475.2.15Release request call state U19 (incoming call).475.2.15.1Valid.475.2.15.2Inopportune.485.2.15.3Syntactically invalid.495.2.15.4Active.495.2.16Release request call state U19 (outgoing call).495.2.16.1Valid.495.2.16.2Inopportune.505.2.16.3Syntactically invalid.505.2.16.4Active.515.2.17Overlap receiving call state U25.515.2.17.1Valid.515.2.17.2Inopportune.525.2.17.3Syntactically invalid.525.2.17.4Active.535.2.18Restart null call state R00 (incoming call).545.2.18.1Valid.545.2.18.2Inopportune.545.2.18.3Syntactically invalid.555.2.18.4Active.565.2.19Restart null call state R00 (outgoing call).565.2.19.1Valid.565.2.19.2Inopportune.575.2.19.3Syntactically invalid.57SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)55.2.19.4Active.585.2.20Restart request call state R01.585.2.20.1Valid.585.2.20.2Inopportune.585.2.20.3Syntactically invalid.595.2.20.4Active.605.2.21Message segmentation procedure.605.2.21.1Valid.605.2.21.2Inopportune.605.2.21.3Syntactically invalid.615.2.21.4Active.616Compliance.617Requirements for a comprehensive testing service.61History.62SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)6Intellectual 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 SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on theETSI Web server (http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)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).The present document is part 3 of a multi-part standard covering the Digital Subscriber Signalling System No. one(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) basic call control extensions at the"b" service entry point for VPN applications, as identified below:Part 1:"Protocol specification";Part 2:"Protocol Implementation Conformance Statement (PICS) proforma specification";Part 3:"Test Suite Structure and Test Purposes (TSS&TP) specification for the user";Part 4:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)proforma specification for the user";Part 5:"Test Suite Structure and Test Purposes (TSS&TP) specification for the network";Part 6:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)proforma specification for the network".National transposition datesDate of adoption of this EN:20 November 1998Date of latest announcement of this EN (doa):28 February 1999Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 August 1999Date of withdrawal of any conflicting National Standard (dow):31 August 1999SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)71ScopeThe third part of EN 301 060 is applicable to the basic call control extensions at the "b" service entry point for VirtualPrivate Network (VPN) applications for the pan-European Integrated Services Digital Network (ISDN) as provided byEuropean public telecommunications operators at the T reference point (as defined in ITU-T RecommendationI.411 [15]) by means of the Digital Subscriber Signalling System No. one (DSS1) protocol. Stage three identifies theprotocol procedures and switching functions needed to support a telecommunications service (see CCITTRecommendation I.130 [11]).The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) for the user side for theISDN DSS1 basic call control extensions at the "b" service entry point for VPN applications as specified inEN 301 060-1 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given inISO/IEC 9646-7 [10].2Normative referencesReferences may be made to:a)specific versions of publications (identified by date of publication, edition number, version number, etc.), inwhich case, subsequent revisions to the referenced document do not apply; orb)all versions up to and including the identified version (identified by "up to and including" before the versionidentity); orc)all versions subsequent to and including the identified version (identified by "onwards" following the versionidentity); ord)publications without mention of a specific version, in which case the latest version applies.A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.[1]EN 301 060-1 (V1.2): "Integrated Services Digital Network (ISDN); Digital Subscriber SignallingSystem No. one (DSS1) protocol; Basic call control; Enhancement at the "b" service entry pointfor Virtual Private Network (VPN) applications; Part 1: Protocol specification".[2]EN 301 060-2 (V1.1): "Integrated Services Digital Network (ISDN); Digital Subscriber SignallingSystem No. one (DSS1) protocol; Basic call control; Enhancement at the "b" service entry pointfor Virtual Private Network (VPN) applications; Part 2: Protocol implementation ConformanceStatement (PICS) proforma specification".[3]EN 300 403-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control;Part 1: Protocol specification [ITU-T Recommendation Q.931 (1993), modified]".[4]ETS 300 403-2: "Integrated Services Digital Network (ISDN); Digital Subscriber SignallingSystem No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control;Part 2: Specification and Description Language (SDL) diagrams".[5]EN 300 403-3: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control;Part 3: Protocol Implementation Conformance Statement (PICS) proforma specification".[6]ETS 300 403-5: "Integrated Services Digital Network (ISDN); Digital Subscriber SignallingSystem No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control;Part 5: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information forTesting (PIXIT) proforma specification for the user".[7]ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol and profileconformance testing specifications; Standardization methodology".SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)8[8]ISO/IEC 9646-1: "Information technology; Open systems interconnection; Conformance testingmethodology and framework; Part 1: General concepts".[9]ISO/IEC 9646-3: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 3: The Tree and Tabular Combined Notation (TTCN)".[10]ISO/IEC 9646-7: "Information technology; Open systems interconnection; Conformance testingmethodology and framework; Part 7: Implementation Conformance Statements".[11]CCITT Recommendation I.130 (1988): "Method for the characterization of telecommunicationservices supported by an ISDN and network capabilities of an ISDN".[12]ITU-T Recommendation E.164: "The international public telecommunication numbering plan".[13]ITU-T Recommendation I.112: "Vocabulary of terms for ISDNs".[14]ITU-T Recommendation I.210: "Principles of telecommunication services supported by an ISDNand the means to describe them".[15]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - Reference configurations".3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the following definitions apply:3.1.1Definitions related to conformance testingabstract test case: refer to ISO/IEC 9646-1 [8].Abstract Test Suite (ATS): refer to ISO/IEC 9646-1 [8].active test: a test case where the IUT is required to send a particular message, but not in reaction to a received message.This would usually involve the use of PIXIT information to see how this message can be generated and quite often isspecified in an ATS using an implicit send event.Implementation Under Test (IUT): refer to ISO/IEC 9646-1 [8].implicit send event: refer to ISO/IEC 9646-3 [16].lower tester: refer to ISO/IEC 9646-1 [8].passive test: a test case where the IUT is required to respond to a protocol event (e.g. received message) with anotherprotocol event (e.g. send message) which normally does not require any special operator intervention as associated withthe implicit send event.point of control and observation: refer to ISO/IEC 9646-1 [8].Protocol Implementation Conformance Statement (PICS): refer to ISO/IEC 9646-1 [8].PICS proforma: refer to ISO/IEC 9646-1 [8].Protocol Implementation eXtra Information for Testing (PIXIT): refer to ISO/IEC 9646-1 [8].PIXIT proforma: refer to ISO/IEC 9646-1 [8].system under test: refer to ISO/IEC 9646-1 [8].Test Purpose (TP): refer to ISO/IEC 9646-1 [8].SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)93.1.2Definitions related to EN 301 060-1Dummy call reference: see EN 300 403-1 [3], subclause 4.3.Integrated Services Digital Network (ISDN): see ITU-T Recommendation I.112 [13], definition 308.ISDN number: a number conforming to the numbering and structure specified in CCITT Recommendation E.164 [12].service; telecommunication service: see ITU-T Recommendation I.112 [13], definition 201.supplementary service: see ITU-T Recommendation I.210 [14], subclause 2.4.T: the DSS1 protocol entity at the User side of the user-network interface where a T reference point applies (User is aPrivate ISDN).3.2AbbreviationsFor the purposes of the present document, the following abbreviations apply:ATMAbstract Test MethodATSAbstract Test SuiteISDNIntegrated Services Digital NetworkIUTImplementation Under TestPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingTPTest PurposeTSSTest Suite StructureVPNVirtual Private Network4Test Suite Structure (TSS)· Null call state U00· Valid· Inopportune· Syntactically invalid· Active· Call Initiated call state U01· Valid· Inopportune· Syntactically invalid· Active· Overlap Sending call state U02· Valid· Inopportune· Syntactically invalid· Active· Outgoing Call Proceeding call state U03· Valid· Inopportune· Syntactically invalid· Active· Call Delivered call state U04· Valid· Inopportune· Syntactically invalid· ActiveSIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)10· Call Received call state U07· Valid· Inopportune· Syntactically invalid· Active· Connect Request call state U08· Valid· Inopportune· Syntactically invalid· Active· Incoming Call Proceeding call state U09· Valid· Inopportune· Syntactically invalid· Active· Active call state U10 (Incoming call)· Valid· Inopportune· Syntactically invalid· Active· Active call state U10 (Outgoing call)· Valid· Inopportune· Syntactically invalid· Active· Disconnect Request call state U11 (Incoming call)· Valid· Inopportune· Syntactically invalid· Active· Disconnect Request call state U11 (Outgoing call)· Valid· Inopportune· Syntactically invalid· Active· Disconnect Indication call state U12 (Incoming call)· Valid· Inopportune· Syntactically invalid· Active· Disconnect Indication call state U12 (Outgoing call)· Valid· Inopportune· Syntactically invalid· Active· Release Request call state U19 (Incoming call)· Valid· Inopportune· Syntactically invalid· Release Request call state U19 (Outgoing call)· Valid· Inopportune· Syntactically invalidSIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)11· Overlap Receiving call state U25· Valid· Inopportune· Syntactically invalid· Active· Restart null call state R00 (Incoming call)· Valid· Inopportune· Syntactically invalid· Active· Restart null call state R00 (Outgoing call)· Valid· Inopportune· Syntactically invalid· Active· Restart Request call state R01· Valid· Inopportune· Syntactically invalid· Message segmentation procedure· Valid· Inopportune· Syntactically invalid· Active5Test Purposes (TP)5.1IntroductionFor each test requirement, a TP is defined.5.1.1TP naming conventionTPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional referencesare added to identify the actual test suite and whether it applies to the network or the user (see table 1).Table 1: TP Identifier naming convention schemeIdentifier:___=layer + type of IUT:e.g. "L3U" for layer 3, IUT = user=call state:e.g. U10 for Active call state=group:one character field representing the group referenceaccording to TSSV:Valid stimulusI: Inopportune stimulusS:Syntactically invalid stimulusA:Active test case=sequential number:(001-999)5.1.2Source of TP definitionThe TPs are based on EN 300 403-1 [3], ETS 300 403-2 [4], EN 301 060-1 [1], and EN 301 060-2 [2].SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)125.1.3TP structureEach TP has been written in a manner which is consistent with all other TPs. The intention of this is to make the TPsmore readable and checkable. A particular structure has been used which is illustrated in table 2. This table should beread in conjunction with any TP, i.e. please use a TP as an example to facilitate the full comprehension of table 2.Table 2: Structure of a single TPTP partTextExampleHeader tabsee table 1 tabsubclause 2.3.4, subclause 9.3.1.1[17] (see note 4)VPNxxx (see note 2)StimulusEnsure that the IUT in theU00, U10, etc. see below for message structureon receipt of a XXXX message (seenote 3)or to request a .Reactionsends, saves, does, etc.using en bloc sending, etc.if the action is sendingsee below for message structure, etc.and remains in the same stateor and enters state MessagestructuremessageSETUP, FACILITY, CONNECT, etc.(see note 3)a) with a information elementb) indicating in the and back to a) or b)Bearer capability, Facility, etc.NOTE 1:Text in italics will not appear in TPs and text between <> is filled in for each TP and may differ from oneTP to the next.NOTE 2:VPNxxx indicates the origin of the test purpose.VPNMOD: indicates that the test purpose was taken from ETS 300 403-5 [6] and modified in accordancewith the VPN context.VPNNEW: indicates that the test purpose did not exist in ETS 300 403-5 [6] and was created to cover aVPN specific procedure.No indication is used when the test purpose was directly taken from ETS 300 403-5 [6] withoutmodifications.NOTE 3:All messages shall be considered as "valid and compatible" unless otherwise specified in the testpurpose.NOTE 4:the subclause indicated there refers directly to the EN 300 403-1 [3] unless otherwise specified, i.e.subclause 9.3.1.1 [6] refers directly to EN 301 060-1 [6].5.1.4Test strategyAs the base standard EN 300 403-1 [3] contains no explicit requirements for testing, the TPs were generated as a resultof an analysis of the base standard and the PICS specification EN 300 403-3 [5].The TPs are only based on conformance requirements related to the externally observable behaviour of the IUT, and arelimited to conceivable situations to which a real implementation is likely to be faced (ETS 300 406 [7]).SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)135.1.5Test of call statesMany TPs include a reference to the IUT's final call state after the realization of the TP. In these cases the TP includesthe requirement to ensure that the IUT has entered this particular final call state. Ensuring that the IUT is in a particularcall state shall be realized by following the procedures described in subclause 5.8.10 of EN 300 403-1 [3]. According tothese procedures, the IUT on receipt of a STATUS ENQUIRY message, shall respond with a STATUS messageindicating, in the third octet of the Call state information element, the current call state of the IUT. This exchange ofmessages is not mentioned explicitly in each TP but is considered to be implicit in the reference to the final call state.This way of phrasing the TPs has been used to avoid over-complicating the text and structure of the TPs and to improvethe readability.The call state being reached by the IUT in the following test purpose is intended for a call in a VPN context.5.1.6Test of inopportune and syntactically invalid behaviourIn the test groups for inopportune and syntactically invalid behaviour the procedures as described in subclause 5.8 ofEN 300 403-1 [3] are tested. This is done in each call state with one message for each of the described error cases.Messages have been chosen that are, if they are received without the inopportune or erroneous coding, expectedmessages in the call states under test.Test purposes for inopportune behaviour that is described outside the subclause 5.8 of EN 300 403-1 [3] are found inthe valid test groups. This was done, as these procedures are seen more as a part of the basic call procedures than as apart of the error handling procedures.5.2TPs for the basic call control VPN, layer 3, userAll PICS items referred to in this subclause are as specified in ETS 301 060-2 [2] unless indicated otherwise by anothernumbered reference.5.2.1Null call state U005.2.1.1ValidSelection:IUT supports incoming calls. PICS: MCu 2. [18]L3U_U00_V_001subclauses 5.2.1, 5.2.4, 5.2.5.1VPNMODEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message in a VPN context without theSending complete information element, sends any of a SETUP ACKNOWLEDGE, CALL PROCEEDING, ALERTINGor CONNECT message and enters the relevant call state Overlap Receiving U25, Incoming Call Proceeding U09, CallReceived U07 or Connect Request U08.Selection:IUT supports overlap receiving. PICS: MCu 2.2. [19]L3U_U00_V_002subclauses 5.2.1, 5.2.5.1VPNMODEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message in a VPN context with the Sendingcomplete information element, sends any of a CALL PROCEEDING, ALERTING or CONNECT message and entersthe relevant call state Incoming Call Proceeding U09, Call Received U07 or Connect Request U08.L3U_U00_V_003subclause 5.2.3.1VPNMODEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message in a VPN context (delivered via thepoint-to-point data link) with the Channel identification information element indicating a B-channel that is not availableand indicating in the preferred / exclusive bit "indicated channel is preferred", sends any of a SETUPACKNOWLEDGE, CALL PROCEEDING, ALERTING or CONNECT message with the Channel identificationinformation element indicating a B-channel that is available and indicating in the preferred / exclusive bit "exclusive:only the indicated channel is acceptable" and enters the relevant call state Overlap Receiving U25, Incoming CallProceeding U09, Call Received U07 or Connect Request U08.Selection:IUT supports point-to-point configuration. PICS: R 7.1.SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)14L3U_U00_V_004subclause 5.2.3.1VPNMODEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message in a VPN context (delivered via thepoint-to-point data link) with the Channel identification information element indicating a B-channel that is not availableand indicating in the preferred / exclusive bit "exclusive: only the indicated channel is acceptable", sends a RELEASECOMPLETE message with a Cause information element indicating the cause value 44 "requestedcircuit / channel / channel not available" and remains in the Null call state.Selection:IUT supports point-to-point configuration. PICS: R 7.1.L3U_U00_V_005subclause 5.2.3.1VPNMODEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message in a VPN context (delivered via thepoint-to-point data link) with the Channel identification information element indicating a B-channel and indicating in thepreferred / exclusive bit "indicated channel is preferred", when no B-channel is available, sends a RELEASECOMPLETE message with a Cause information element indicating the cause value 34 "no circuit / channel available"and remains in the Null call state.Selection:IUT supports point-to-point configuration. PICS: R 7.1.L3U_U00_V_006subclause 5.2.3.1VPNMODEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message in a VPN context (delivered via thepoint-to-point data link) with the Channel identification information element indicating in the channel selection "anychannel", when no B-channel is available, sends a RELEASE COMPLETE message with a Cause information elementindicating the cause value 34 "no circuit / channel available" and remains in the Null call state.Selection:IUT supports point-to-point configuration. PICS: R 7.1.L3U_U00_V_008annex BVPNMODEnsure that the IUT in the Null call state U00, on receipt of a SETUP message in a VPN context without the Sendingcomplete information element and with the Called party number information element containing mismatching numberdigits, sends no message and remains in the Null call state U00.L3U_U00_V_009annex BVPNMODEnsure that the IUT in the Null call state U00, on receipt of a SETUP message in a VPN context without the Sendingcomplete information element and with the Called subaddress information element containing mismatching subaddressdigits, sends no message and remains in the Null call state U00.L3U_U00_V_010subclause 5.2.5.1VPNMODEnsure that the busy IUT in the Null call state U00, on receipt of a SETUP message in a VPN context with the Sendingcomplete information element, sends a RELEASE COMPLETE message with a Cause information element indicatingthe cause value 17 "user busy" and remains in the Null call state U00.L3U_U00_V_011subclause 5.2.5.1VPNMODEnsure that the IUT in the Null call state U00, on receipt of a SETUP message in a VPN context with the SendingComplete information element, to refuse the call, sends a RELEASE COMPLETE message with a Cause informationelement indicating the cause value 21 "call rejected" and remains in the Null call state U00.L3U_U00_V_012subclause 5.2.6, annex BVPNMODEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message in a VPN context without High andLow layer compatibility information elements but with a Progress indicator information element indicating the progressdescription 1 "call is not end-to-end ISDN", modifies its compatibility checking and accepts the call on the basis of acompatible Bearer capability information element.Selection:IUT supports compatibility checking of the higher layers. PICS: SCu 8[20] ANDIUT supports compatibility checking of the lower layers. PICS: SCu 6. [21]L3U_U00_V_014subclauses 5.2.2, 5.2.5.1, annex BVPNMODEnsure that the IUT in the Null call state U00, on receipt of a SETUP message in a VPN context (delivered via thepoint-to-point data link) containing an incompatible Bearer capability information element, sends a RELEASECOMPLETE message with the Cause information element indicating cause value 88 "incompatible destination" andremains in the Null call state U00.Selection:IUT supports point-to-point configuration. PICS: R 7.1.SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)15L3U_U00_V_016subclauses 5.2.2, 5.2.5.1, annex BVPNMODEnsure that the IUT in the Null call state U00, on receipt of a SETUP message in a VPN context (delivered via thepoint-to-point data link) containing an incompatible High layer compatibility information element, sends a RELEASECOMPLETE message with the Cause information element indicatin
...

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.JUDGEDIntegrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Basic call control; Enhancement at the b service entry point for Virtual Private Network (VPN) applications; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 301 060-3 Version 1.1.3SIST EN 301 060-3:2000en01-december-2000SIST EN 301 060-3:2000SLOVENSKI
STANDARD
EN 301 060-3 V1.1.3 (1998-11)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Digital Subscriber Signalling System No. one (DSS1) protocol;Basic call control;Enhancement at the "b" service entry point forVirtual Private Network (VPN) applications;Part 3: Test Suite Structure and Test Purposes (TSS&TP)specification for the userSIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)2ReferenceDEN/SPS-05109-3 (9tcr0ie0.PDF)KeywordsISDN, DSS1, basic, VPN, TSS&TP, userETSIPostal 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] copies of this ETSI deliverablecan be downloaded fromhttp://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 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)3ContentsIntellectual Property Rights.6Foreword.61Scope.72Normative references.73Definitions and abbreviations.83.1Definitions.83.1.1Definitions related to conformance testing.83.1.2Definitions related to EN 301 060-1.93.2Abbreviations.94Test Suite Structure (TSS).95Test Purposes (TP).115.1Introduction.115.1.1TP naming convention.115.1.2Source of TP definition.115.1.3TP structure.125.1.4Test strategy.125.1.5Test of call states.135.1.6Test of inopportune and syntactically invalid behaviour.135.2TPs for the basic call control VPN, layer 3, user.135.2.1Null call state U00.135.2.1.1Valid.135.2.1.2Inopportune.155.2.1.3Syntactically invalid.165.2.1.4Active.175.2.2Call Initiated call state U01.185.2.2.1Valid.185.2.2.2Inopportune.185.2.2.3Syntactically invalid.195.2.2.4Active.205.2.3Overlap sending call state U02.205.2.3.1Valid.205.2.3.2Inopportune.205.2.3.3Syntactically invalid.215.2.3.4Active.225.2.4Outgoing call proceeding call state U03.225.2.4.1Valid.225.2.4.2Inopportune.235.2.4.3Syntactically invalid.245.2.4.4Active.245.2.5Call delivered call state U04.255.2.5.1Valid.255.2.5.2Inopportune.255.2.5.3Syntactically invalid.265.2.5.4Active.275.2.6Call received call state U07.275.2.6.1Valid.275.2.6.2Inopportune.275.2.6.3Syntactically invalid.285.2.6.4Active.295.2.7Connect request call state U08.295.2.7.1Valid.295.2.7.2Inopportune.305.2.7.3Syntactically invalid.30SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)45.2.7.4Active.315.2.8Incoming call proceeding call state U09.315.2.8.1Valid.315.2.8.2Inopportune.325.2.8.3Syntactically invalid.335.2.8.4Active.335.2.9Active call state U10 (incoming call).345.2.9.1Valid.345.2.9.2Inopportune.355.2.9.3Syntactically invalid.365.2.9.4Active.365.2.10Active call state U10 (outgoing call).375.2.10.1Valid.375.2.10.2Inopportune.385.2.10.3Syntactically invalid.385.2.10.4Active.395.2.11Disconnect request call state U11 (incoming call).395.2.11.1Valid.395.2.11.2Inopportune.405.2.11.3Syntactically invalid.415.2.11.4Active.415.2.12Disconnect request call state U11 (outgoing call).425.2.12.1Valid.425.2.12.2Inopportune.425.2.12.3Syntactically invalid.435.2.12.4Active.435.2.13Disconnect indication call state U12 (incoming call).445.2.13.1Valid.445.2.13.2Inopportune.445.2.13.3Syntactically invalid.455.2.13.4Active.455.2.14Disconnect indication call state U12 (outgoing call).465.2.14.1Valid.465.2.14.2Inopportune.465.2.14.3Syntactically invalid.475.2.14.4Active.475.2.15Release request call state U19 (incoming call).475.2.15.1Valid.475.2.15.2Inopportune.485.2.15.3Syntactically invalid.495.2.15.4Active.495.2.16Release request call state U19 (outgoing call).495.2.16.1Valid.495.2.16.2Inopportune.505.2.16.3Syntactically invalid.505.2.16.4Active.515.2.17Overlap receiving call state U25.515.2.17.1Valid.515.2.17.2Inopportune.525.2.17.3Syntactically invalid.525.2.17.4Active.535.2.18Restart null call state R00 (incoming call).545.2.18.1Valid.545.2.18.2Inopportune.545.2.18.3Syntactically invalid.555.2.18.4Active.565.2.19Restart null call state R00 (outgoing call).565.2.19.1Valid.565.2.19.2Inopportune.575.2.19.3Syntactically invalid.57SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)55.2.19.4Active.585.2.20Restart request call state R01.585.2.20.1Valid.585.2.20.2Inopportune.585.2.20.3Syntactically invalid.595.2.20.4Active.605.2.21Message segmentation procedure.605.2.21.1Valid.605.2.21.2Inopportune.605.2.21.3Syntactically invalid.615.2.21.4Active.616Compliance.617Requirements for a comprehensive testing service.61History.62SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)6Intellectual 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 SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on theETSI Web server (http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)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).The present document is part 3 of a multi-part standard covering the Digital Subscriber Signalling System No. one(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) basic call control extensions at the"b" service entry point for VPN applications, as identified below:Part 1:"Protocol specification";Part 2:"Protocol Implementation Conformance Statement (PICS) proforma specification";Part 3:"Test Suite Structure and Test Purposes (TSS&TP) specification for the user";Part 4:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)proforma specification for the user";Part 5:"Test Suite Structure and Test Purposes (TSS&TP) specification for the network";Part 6:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)proforma specification for the network".National transposition datesDate of adoption of this EN:20 November 1998Date of latest announcement of this EN (doa):28 February 1999Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 August 1999Date of withdrawal of any conflicting National Standard (dow):31 August 1999SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)71ScopeThe third part of EN 301 060 is applicable to the basic call control extensions at the "b" service entry point for VirtualPrivate Network (VPN) applications for the pan-European Integrated Services Digital Network (ISDN) as provided byEuropean public telecommunications operators at the T reference point (as defined in ITU-T RecommendationI.411 [15]) by means of the Digital Subscriber Signalling System No. one (DSS1) protocol. Stage three identifies theprotocol procedures and switching functions needed to support a telecommunications service (see CCITTRecommendation I.130 [11]).The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) for the user side for theISDN DSS1 basic call control extensions at the "b" service entry point for VPN applications as specified inEN 301 060-1 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given inISO/IEC 9646-7 [10].2Normative referencesReferences may be made to:a)specific versions of publications (identified by date of publication, edition number, version number, etc.), inwhich case, subsequent revisions to the referenced document do not apply; orb)all versions up to and including the identified version (identified by "up to and including" before the versionidentity); orc)all versions subsequent to and including the identified version (identified by "onwards" following the versionidentity); ord)publications without mention of a specific version, in which case the latest version applies.A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.[1]EN 301 060-1 (V1.2): "Integrated Services Digital Network (ISDN); Digital Subscriber SignallingSystem No. one (DSS1) protocol; Basic call control; Enhancement at the "b" service entry pointfor Virtual Private Network (VPN) applications; Part 1: Protocol specification".[2]EN 301 060-2 (V1.1): "Integrated Services Digital Network (ISDN); Digital Subscriber SignallingSystem No. one (DSS1) protocol; Basic call control; Enhancement at the "b" service entry pointfor Virtual Private Network (VPN) applications; Part 2: Protocol implementation ConformanceStatement (PICS) proforma specification".[3]EN 300 403-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control;Part 1: Protocol specification [ITU-T Recommendation Q.931 (1993), modified]".[4]ETS 300 403-2: "Integrated Services Digital Network (ISDN); Digital Subscriber SignallingSystem No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control;Part 2: Specification and Description Language (SDL) diagrams".[5]EN 300 403-3: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control;Part 3: Protocol Implementation Conformance Statement (PICS) proforma specification".[6]ETS 300 403-5: "Integrated Services Digital Network (ISDN); Digital Subscriber SignallingSystem No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control;Part 5: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information forTesting (PIXIT) proforma specification for the user".[7]ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol and profileconformance testing specifications; Standardization methodology".SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)8[8]ISO/IEC 9646-1: "Information technology; Open systems interconnection; Conformance testingmethodology and framework; Part 1: General concepts".[9]ISO/IEC 9646-3: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 3: The Tree and Tabular Combined Notation (TTCN)".[10]ISO/IEC 9646-7: "Information technology; Open systems interconnection; Conformance testingmethodology and framework; Part 7: Implementation Conformance Statements".[11]CCITT Recommendation I.130 (1988): "Method for the characterization of telecommunicationservices supported by an ISDN and network capabilities of an ISDN".[12]ITU-T Recommendation E.164: "The international public telecommunication numbering plan".[13]ITU-T Recommendation I.112: "Vocabulary of terms for ISDNs".[14]ITU-T Recommendation I.210: "Principles of telecommunication services supported by an ISDNand the means to describe them".[15]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - Reference configurations".3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the following definitions apply:3.1.1Definitions related to conformance testingabstract test case: refer to ISO/IEC 9646-1 [8].Abstract Test Suite (ATS): refer to ISO/IEC 9646-1 [8].active test: a test case where the IUT is required to send a particular message, but not in reaction to a received message.This would usually involve the use of PIXIT information to see how this message can be generated and quite often isspecified in an ATS using an implicit send event.Implementation Under Test (IUT): refer to ISO/IEC 9646-1 [8].implicit send event: refer to ISO/IEC 9646-3 [16].lower tester: refer to ISO/IEC 9646-1 [8].passive test: a test case where the IUT is required to respond to a protocol event (e.g. received message) with anotherprotocol event (e.g. send message) which normally does not require any special operator intervention as associated withthe implicit send event.point of control and observation: refer to ISO/IEC 9646-1 [8].Protocol Implementation Conformance Statement (PICS): refer to ISO/IEC 9646-1 [8].PICS proforma: refer to ISO/IEC 9646-1 [8].Protocol Implementation eXtra Information for Testing (PIXIT): refer to ISO/IEC 9646-1 [8].PIXIT proforma: refer to ISO/IEC 9646-1 [8].system under test: refer to ISO/IEC 9646-1 [8].Test Purpose (TP): refer to ISO/IEC 9646-1 [8].SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)93.1.2Definitions related to EN 301 060-1Dummy call reference: see EN 300 403-1 [3], subclause 4.3.Integrated Services Digital Network (ISDN): see ITU-T Recommendation I.112 [13], definition 308.ISDN number: a number conforming to the numbering and structure specified in CCITT Recommendation E.164 [12].service; telecommunication service: see ITU-T Recommendation I.112 [13], definition 201.supplementary service: see ITU-T Recommendation I.210 [14], subclause 2.4.T: the DSS1 protocol entity at the User side of the user-network interface where a T reference point applies (User is aPrivate ISDN).3.2AbbreviationsFor the purposes of the present document, the following abbreviations apply:ATMAbstract Test MethodATSAbstract Test SuiteISDNIntegrated Services Digital NetworkIUTImplementation Under TestPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingTPTest PurposeTSSTest Suite StructureVPNVirtual Private Network4Test Suite Structure (TSS)· Null call state U00· Valid· Inopportune· Syntactically invalid· Active· Call Initiated call state U01· Valid· Inopportune· Syntactically invalid· Active· Overlap Sending call state U02· Valid· Inopportune· Syntactically invalid· Active· Outgoing Call Proceeding call state U03· Valid· Inopportune· Syntactically invalid· Active· Call Delivered call state U04· Valid· Inopportune· Syntactically invalid· ActiveSIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)10· Call Received call state U07· Valid· Inopportune· Syntactically invalid· Active· Connect Request call state U08· Valid· Inopportune· Syntactically invalid· Active· Incoming Call Proceeding call state U09· Valid· Inopportune· Syntactically invalid· Active· Active call state U10 (Incoming call)· Valid· Inopportune· Syntactically invalid· Active· Active call state U10 (Outgoing call)· Valid· Inopportune· Syntactically invalid· Active· Disconnect Request call state U11 (Incoming call)· Valid· Inopportune· Syntactically invalid· Active· Disconnect Request call state U11 (Outgoing call)· Valid· Inopportune· Syntactically invalid· Active· Disconnect Indication call state U12 (Incoming call)· Valid· Inopportune· Syntactically invalid· Active· Disconnect Indication call state U12 (Outgoing call)· Valid· Inopportune· Syntactically invalid· Active· Release Request call state U19 (Incoming call)· Valid· Inopportune· Syntactically invalid· Release Request call state U19 (Outgoing call)· Valid· Inopportune· Syntactically invalidSIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)11· Overlap Receiving call state U25· Valid· Inopportune· Syntactically invalid· Active· Restart null call state R00 (Incoming call)· Valid· Inopportune· Syntactically invalid· Active· Restart null call state R00 (Outgoing call)· Valid· Inopportune· Syntactically invalid· Active· Restart Request call state R01· Valid· Inopportune· Syntactically invalid· Message segmentation procedure· Valid· Inopportune· Syntactically invalid· Active5Test Purposes (TP)5.1IntroductionFor each test requirement, a TP is defined.5.1.1TP naming conventionTPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional referencesare added to identify the actual test suite and whether it applies to the network or the user (see table 1).Table 1: TP Identifier naming convention schemeIdentifier:___=layer + type of IUT:e.g. "L3U" for layer 3, IUT = user=call state:e.g. U10 for Active call state=group:one character field representing the group referenceaccording to TSSV:Valid stimulusI: Inopportune stimulusS:Syntactically invalid stimulusA:Active test case=sequential number:(001-999)5.1.2Source of TP definitionThe TPs are based on EN 300 403-1 [3], ETS 300 403-2 [4], EN 301 060-1 [1], and EN 301 060-2 [2].SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)125.1.3TP structureEach TP has been written in a manner which is consistent with all other TPs. The intention of this is to make the TPsmore readable and checkable. A particular structure has been used which is illustrated in table 2. This table should beread in conjunction with any TP, i.e. please use a TP as an example to facilitate the full comprehension of table 2.Table 2: Structure of a single TPTP partTextExampleHeader tabsee table 1 tabsubclause 2.3.4, subclause 9.3.1.1[17] (see note 4)VPNxxx (see note 2)StimulusEnsure that the IUT in theU00, U10, etc. see below for message structureon receipt of a XXXX message (seenote 3)or to request a .Reactionsends, saves, does, etc.using en bloc sending, etc.if the action is sendingsee below for message structure, etc.and remains in the same stateor and enters state MessagestructuremessageSETUP, FACILITY, CONNECT, etc.(see note 3)a) with a information elementb) indicating in the and back to a) or b)Bearer capability, Facility, etc.NOTE 1:Text in italics will not appear in TPs and text between <> is filled in for each TP and may differ from oneTP to the next.NOTE 2:VPNxxx indicates the origin of the test purpose.VPNMOD: indicates that the test purpose was taken from ETS 300 403-5 [6] and modified in accordancewith the VPN context.VPNNEW: indicates that the test purpose did not exist in ETS 300 403-5 [6] and was created to cover aVPN specific procedure.No indication is used when the test purpose was directly taken from ETS 300 403-5 [6] withoutmodifications.NOTE 3:All messages shall be considered as "valid and compatible" unless otherwise specified in the testpurpose.NOTE 4:the subclause indicated there refers directly to the EN 300 403-1 [3] unless otherwise specified, i.e.subclause 9.3.1.1 [6] refers directly to EN 301 060-1 [6].5.1.4Test strategyAs the base standard EN 300 403-1 [3] contains no explicit requirements for testing, the TPs were generated as a resultof an analysis of the base standard and the PICS specification EN 300 403-3 [5].The TPs are only based on conformance requirements related to the externally observable behaviour of the IUT, and arelimited to conceivable situations to which a real implementation is likely to be faced (ETS 300 406 [7]).SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)135.1.5Test of call statesMany TPs include a reference to the IUT's final call state after the realization of the TP. In these cases the TP includesthe requirement to ensure that the IUT has entered this particular final call state. Ensuring that the IUT is in a particularcall state shall be realized by following the procedures described in subclause 5.8.10 of EN 300 403-1 [3]. According tothese procedures, the IUT on receipt of a STATUS ENQUIRY message, shall respond with a STATUS messageindicating, in the third octet of the Call state information element, the current call state of the IUT. This exchange ofmessages is not mentioned explicitly in each TP but is considered to be implicit in the reference to the final call state.This way of phrasing the TPs has been used to avoid over-complicating the text and structure of the TPs and to improvethe readability.The call state being reached by the IUT in the following test purpose is intended for a call in a VPN context.5.1.6Test of inopportune and syntactically invalid behaviourIn the test groups for inopportune and syntactically invalid behaviour the procedures as described in subclause 5.8 ofEN 300 403-1 [3] are tested. This is done in each call state with one message for each of the described error cases.Messages have been chosen that are, if they are received without the inopportune or erroneous coding, expectedmessages in the call states under test.Test purposes for inopportune behaviour that is described outside the subclause 5.8 of EN 300 403-1 [3] are found inthe valid test groups. This was done, as these procedures are seen more as a part of the basic call procedures than as apart of the error handling procedures.5.2TPs for the basic call control VPN, layer 3, userAll PICS items referred to in this subclause are as specified in ETS 301 060-2 [2] unless indicated otherwise by anothernumbered reference.5.2.1Null call state U005.2.1.1ValidSelection:IUT supports incoming calls. PICS: MCu 2. [18]L3U_U00_V_001subclauses 5.2.1, 5.2.4, 5.2.5.1VPNMODEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message in a VPN context without theSending complete information element, sends any of a SETUP ACKNOWLEDGE, CALL PROCEEDING, ALERTINGor CONNECT message and enters the relevant call state Overlap Receiving U25, Incoming Call Proceeding U09, CallReceived U07 or Connect Request U08.Selection:IUT supports overlap receiving. PICS: MCu 2.2. [19]L3U_U00_V_002subclauses 5.2.1, 5.2.5.1VPNMODEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message in a VPN context with the Sendingcomplete information element, sends any of a CALL PROCEEDING, ALERTING or CONNECT message and entersthe relevant call state Incoming Call Proceeding U09, Call Received U07 or Connect Request U08.L3U_U00_V_003subclause 5.2.3.1VPNMODEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message in a VPN context (delivered via thepoint-to-point data link) with the Channel identification information element indicating a B-channel that is not availableand indicating in the preferred / exclusive bit "indicated channel is preferred", sends any of a SETUPACKNOWLEDGE, CALL PROCEEDING, ALERTING or CONNECT message with the Channel identificationinformation element indicating a B-channel that is available and indicating in the preferred / exclusive bit "exclusive:only the indicated channel is acceptable" and enters the relevant call state Overlap Receiving U25, Incoming CallProceeding U09, Call Received U07 or Connect Request U08.Selection:IUT supports point-to-point configuration. PICS: R 7.1.SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)14L3U_U00_V_004subclause 5.2.3.1VPNMODEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message in a VPN context (delivered via thepoint-to-point data link) with the Channel identification information element indicating a B-channel that is not availableand indicating in the preferred / exclusive bit "exclusive: only the indicated channel is acceptable", sends a RELEASECOMPLETE message with a Cause information element indicating the cause value 44 "requestedcircuit / channel / channel not available" and remains in the Null call state.Selection:IUT supports point-to-point configuration. PICS: R 7.1.L3U_U00_V_005subclause 5.2.3.1VPNMODEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message in a VPN context (delivered via thepoint-to-point data link) with the Channel identification information element indicating a B-channel and indicating in thepreferred / exclusive bit "indicated channel is preferred", when no B-channel is available, sends a RELEASECOMPLETE message with a Cause information element indicating the cause value 34 "no circuit / channel available"and remains in the Null call state.Selection:IUT supports point-to-point configuration. PICS: R 7.1.L3U_U00_V_006subclause 5.2.3.1VPNMODEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message in a VPN context (delivered via thepoint-to-point data link) with the Channel identification information element indicating in the channel selection "anychannel", when no B-channel is available, sends a RELEASE COMPLETE message with a Cause information elementindicating the cause value 34 "no circuit / channel available" and remains in the Null call state.Selection:IUT supports point-to-point configuration. PICS: R 7.1.L3U_U00_V_008annex BVPNMODEnsure that the IUT in the Null call state U00, on receipt of a SETUP message in a VPN context without the Sendingcomplete information element and with the Called party number information element containing mismatching numberdigits, sends no message and remains in the Null call state U00.L3U_U00_V_009annex BVPNMODEnsure that the IUT in the Null call state U00, on receipt of a SETUP message in a VPN context without the Sendingcomplete information element and with the Called subaddress information element containing mismatching subaddressdigits, sends no message and remains in the Null call state U00.L3U_U00_V_010subclause 5.2.5.1VPNMODEnsure that the busy IUT in the Null call state U00, on receipt of a SETUP message in a VPN context with the Sendingcomplete information element, sends a RELEASE COMPLETE message with a Cause information element indicatingthe cause value 17 "user busy" and remains in the Null call state U00.L3U_U00_V_011subclause 5.2.5.1VPNMODEnsure that the IUT in the Null call state U00, on receipt of a SETUP message in a VPN context with the SendingComplete information element, to refuse the call, sends a RELEASE COMPLETE message with a Cause informationelement indicating the cause value 21 "call rejected" and remains in the Null call state U00.L3U_U00_V_012subclause 5.2.6, annex BVPNMODEnsure that the IUT in the Null call state U00, on receipt of a valid SETUP message in a VPN context without High andLow layer compatibility information elements but with a Progress indicator information element indicating the progressdescription 1 "call is not end-to-end ISDN", modifies its compatibility checking and accepts the call on the basis of acompatible Bearer capability information element.Selection:IUT supports compatibility checking of the higher layers. PICS: SCu 8[20] ANDIUT supports compatibility checking of the lower layers. PICS: SCu 6. [21]L3U_U00_V_014subclauses 5.2.2, 5.2.5.1, annex BVPNMODEnsure that the IUT in the Null call state U00, on receipt of a SETUP message in a VPN context (delivered via thepoint-to-point data link) containing an incompatible Bearer capability information element, sends a RELEASECOMPLETE message with the Cause information element indicating cause value 88 "incompatible destination" andremains in the Null call state U00.Selection:IUT supports point-to-point configuration. PICS: R 7.1.SIST EN 301 060-3:2000

ETSIEN 301 060-3 V1.1.3 (1998-11)15L3U_U00_V_016subclauses 5.2.2, 5.2.5.1, annex BVPNMODEnsure that the IUT in the Null call state U00, on receipt of a SETUP message in a VPN context (delivered via thepoint-to-point data link) containing an incompatible High layer compatibility information element, sends a RELEASECOMPLETE message with the Cause information
...