SIST EN 301 061-3:2001
(Main)Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Generic functional protocol for the support of supplementary services 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
Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Generic functional protocol for the support of supplementary services 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
Test specification for DE/SPS-05110-1
Digitalno omrežje z integriranimi storitvami (ISDN) - Protokol digitalne naročniške signalizacije št. 1 (DSS1) - Generični funkcijski protokol za podporo dopolnilnih storitev v storitveni-vstopni točki b za navidezno zasebne omrežne (VPN) aplikacije - 3. del: Zgradba preskušalnega niza in namen preskušanja (TSS&TP) - Specifikacija za uporabnika
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Generic functional protocol for the support of supplementary services 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 061-3 Version 1.1.33SIST EN 301 061-3:2001en01-IHEUXDU-20013SIST EN 301 061-3:2001SLOVENSKI
STANDARD
SIST EN 301 061-3:2001
EN 301 061-3 V1.1.3 (1998-10)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Digital Subscriber Signalling System No. one (DSS1) protocol;Generic functional protocol for the support ofsupplementary services 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 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)2ReferenceDEN/SPS-05110-3 (9tor0ie0.PDF)KeywordsDSS1, generic, ISDN, supplementary service,VPN, TSS&TP, userETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frhttp://www.etsi.orgCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1998.All rights reserved.SIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)3ContentsIntellectual Property Rights.4Foreword.41Scope.52Normative references.53Definitions and abbreviations.63.1Definitions.63.1.1Definitions related to conformance testing.63.1.2Definitions related to EN 301 061-1.63.2Abbreviations.64Test Suite Structure (TSS).75Test Purposes (TP).85.1Introduction.85.1.1TP naming convention.85.1.2Source of TP definition.85.1.3TP structure.85.1.4Test strategy.95.2User TPs for VPN-GFP.95.2.1Common IE approach.95.2.1.1Bearer related transport mechanism.105.2.1.1.1Protocol control.105.2.1.1.1.1Incoming call.105.2.1.1.1.2Outgoing call.105.2.1.1.2GFT-Control.115.2.1.2Connection oriented bearer independent transport mechanism.145.2.1.2.1Protocol control.145.2.1.2.1.1Originating interface.145.2.1.2.1.2Destination interface.145.2.1.2.1.3Connection clearing.145.2.1.2.1.4Interaction.145.2.1.2.1.5Handling of error conditions.155.2.1.2.1.6Timers.165.2.1.2.1.7Exchange of FACILITY messages.165.2.1.2.2GFT-Control.175.2.1.2.2.1Control of the Facility IE.175.2.1.2.2.2Control of the NCICS connection.195.2.1.2.2.2ATransit PINX.195.2.2Generic notification procedures.205.2.2.1Protocol control.205.2.2.2GFT-control.215.2.3Co-ordination function.215.2.4ROSE requirements.226Compliance.237Requirements for a comprehensive testing service.23History.24SIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)4Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin 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 European Standard (Telecommunications series) covering the IntegratedServices Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Generic functionalprotocol for the support of supplementary services at the "b" service entry point for Virtual Private Network (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), user";Part 5: "Test Suite Structure and Test Purposes (TSS&TP), specification for the network";Part 6: "Abstract Test Suite (ATS), network".National transposition datesDate of adoption of this EN: 30 October 1998Date of latest announcement of this EN (doa): 31 January 1999Date of latest publication of new National Standardor endorsement of this EN (dop/e): 31 July 1999Date of withdrawal of any conflicting National Standard (dow): 31 July 1999SIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)51ScopeThis third part of EN 301 061 specifies the Test Suite Structure and Test Purposes (TSS&TP) for the user side of theT reference point (as defined in ITU-T Recommendation I.411 [10]) of implementations conforming to the stage threestandard for the generic functional protocol for the support of supplementary services for Virtual Private Network(VPN) applications for the pan-European Integrated Services Digital Network (ISDN) by means of the DigitalSubscriber Signalling System No. one (DSS1) protocol, EN 301 061-1 [2].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 300 196-1 (V1.2): "Integrated Services Digital Network (ISDN); Generic functional protocolfor the support of supplementary services; Digital Subscriber Signalling System No. one (DSS1)protocol; Part 1: Protocol specification".[2]EN 301 061-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Generic functional protocol for the support of supplementary services atthe "b" service entry point for Virtual Private Network (VPN) applications; Part 1: Protocolspecification".[3]EN 301 061-2: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Generic functional protocol for the support of supplementary services atthe "b" service entry point for Virtual Private Network (VPN) applications; Part 2: ProtocolImplementation Conformance Statement (PICS) proforma specification".[4]ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol and profileconformance testing specifications; Standardization methodology".[5]ISO/IEC 9646-1 (1994): "Information technology; Open Systems Interconnection; Conformancetesting methodology and framework; Part 1: General concepts".[6]ISO/IEC 9646-2 (1994): "Information technology; Open Systems Interconnection; Conformancetesting methodology and framework; Part 2: Abstract Test Suite specification".[7]Void.[8]ISO/IEC 11582 (1995): "Information technology; Telecommunications and information exchangebetween systems; Private Integrated Services Network; Generic functional protocol for the supportof supplementary services; Inter-exchange signalling procedures and protocol".[9]ITU-T Recommendation I.112 (1993): "Vocabulary and terms for ISDNs".[10]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces; reference configurations".SIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)63Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the following definitions apply:3.1.1Definitions related to conformance testingAbstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [5].Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [5].PICS proforma: Refer to ISO/IEC 9646-1 [5].Protocol Implementation eXtra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 [5].PIXIT proforma: Refer to ISO/IEC 9646-1 [5].Test Purpose (TP): Refer to ISO/IEC 9646-1 [5].3.1.2Definitions related to EN 301 061-1component: See EN 300 196-1 [1], subclause 11.2.2.1.invoke component: See EN 300 196-1 [1], subclause 11.2.2.1.return error component: See EN 300 196-1 [1], subclause 11.2.2.1.return result component: See EN 300 196-1 [1], subclause 11.2.2.1.service; telecommunication service: See ITU-T Recommendation I.112 [9], definition 201.3.2AbbreviationsFor the purposes of the present document, the following abbreviations apply:APDUApplication Protocol Data UnitATMAbstract Test MethodATSAbstract Test SuiteGFTGeneric Functional TransportIEInformation ElementISDNIntegrated Services Digital NetworkIUTImplementation Under TestNCICSNetworked Call Independent Connection oriented SignallingPICSProtocol Implementation Conformance StatementPINXPrivate Integrated services Network eXchangePIXITProtocol Implementation eXtra Information for TestingROSERemote Operations Service ElementTPTest PurposeTSSTest Suite StructureVPNVirtual Private NetworkVPN-GFPGeneric Functional Protocol for the support of supplementary services for VPNSIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)74Test Suite Structure (TSS)group5.2.1. Common Information Element (IE) approach5.2.1.1. Bearer related transport mechanism5.2.1.1.1. Protocol control5.2.1.1.1.1. Outgoing callU015.2.1.1.1.2. Incoming callU025.2.1.1.2. GFT-controlU035.2.1.2. Connection oriented Bearer bearer independent transport mechanism5.2.1.2.1. Protocol control5.2.1.2.1.1. Originating interfaceU045.2.1.2.1.2. Destination interfaceU055.2.1.2.1.3. Connection clearingU065.2.1.2.1.4. InteractionU075.2.1.2.1.5. Handling of error conditionsU085.2.1.2.1.6. TimersU095.2.1.2.1.7. Exchange of FACILITY messagesU105.2.1.2.2. GFT-controlU115.2.2. Generic notification procedure5.2.2.1. Protocol controlU135.2.2.2. GFT-controlU145.2.3. Co-ordination functionU155.2.4. ROSE requirementU16Figure 1: Test suite structureSIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)85Test 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:__=protocol specification: "GFP"=type of IUT:UUserNNetwork=group2 digit field representing group reference according to TSS=sequential number(001-999)5.1.2Source of TP definitionThe TPs are based on EN 301 061-1 [2].5.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 and this is illustrated in table 2. This table should beread in conjunction with any TP, i.e. use a TP as an example to fully understand the table.SIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)9Table 2: Structure of a single TP for Generic Functional Protocol for the supportof supplementary services for VPN (VPN-GFP)TP partTextExampleHeader tabsee table 1 tabsubclause 0.0.0StimulusEnsure that the IUT in the .N10 etc. see below for message structurereceiving a XXXX messageor to request a .Reactionsends, saves, does, etc.using en bloc sending, .if the action is sendingsee below for message structure, etc.and remains in the same stateor and enters state Messagestructuremessage containing aSETUP, FACILITY, CONNECT, .a) IE withb) a encoded as or including and back to a or b,Bearer capability, Facility, .NOTE 1:TP are always applicable. Optional TPs are applicable according to the configuration options of the IUT. Ifthe configuration option is covered by a Protocol Implementation Conformance Statement (PICS) item, aselection criteria is indicated, else the selection of the corresponding test cases will depend on test suiteparameters Protocol Implementation eXtra Information for Testing (PIXIT) in the Abstract Test Suite(ATS).NOTE 2: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.5.1.4Test strategyAs the base standard EN 301 061-1 [2] contains no explicit requirements for testing, the TPs were generated as a resultof an analysis of the base standard and the PICS specification EN 301 061-2 [3].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 [4]).5.2User TPs for VPN-GFPAll PICS items referred to in this subclause are as specified in EN 301 061-2 [3] unless indicated otherwise by anothernumbered reference.Unless specified, the messages and IEs indicated are valid and contain at least the mandatory parameters and possiblyoptional parameters.5.2.1Common IE approachSelection:IUT supports the common IE category. PICS: MCu 1.The following TPs are testing the procedures associated with the transport of components using the messages for theestablishment and clearing of calls.The primitive exchanged between the different entities are not observable. Only the PDU exchanged between peerimplementations can be observed.So to check that the component is properly transmitted to the Generic Functional Transport (GFT) entity, it shallprovoke a reaction from Remote Operations Service Element (ROSE) entity that will request the transmission of thecorresponding component response. This component will be transmitted in a call related message with the same callreference, which is observable.SIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)10To provoke a reaction from the ROSE entity, a return result component, with an invokeID not related to a currentlyactive invocation, can be sent.5.2.1.1Bearer related transport mechanismSelection:IUT supports the bearer related transport mechanism. PICS: MCu 1.1.In all the TPs of this subclause, the call reference is in a Virtual Private Network (VPN) context.5.2.1.1.1Protocol controlIn the TPs of this subclause, no NFE shall be included so that the Private Integrated services Network eXchange (PINX)entity will be the addressed PINX and can treat the received component.5.2.1.1.1.1Incoming callGFP_U01_001subclause 7.2.1.1.1Ensure that the IUT in the call state U0, on receipt of a SETUP message containing a VPN indicator IE and a Facility IEwith a component requiring an answer, sends a Facility IE with a component, included in a SETUP ACKNOWLEDGE,CALL PROCEEDING or FACILITY message and enters respectively the U25, U9 or U6 call state.GFP_U01_002subclause 7.2.1.1.1Ensure that the IUT in the call state U8 , having sent a CONNECT messages, on receipt of a CONNECTACKNOWLEDGE message containing a Facility IE with a component requiring an answer, sends a FACILITYmessage containing a Facility IE with a component and enters the call state U10.GFP_U01_003subclause 7.2.1.1.1Ensure that the IUT in the call state U10 , on receipt of a DISCONNECT message containing a Facility IE with acomponent requiring an answer, sends a Facility IE with a component included in the RELEASE or a FACILITYmessage and enters the call state U19.GFP_U01_004subclause 7.2.1.1.1Ensure that the IUT in the call state U11 , on receipt of a RELEASE message containing a Facility IE with a componentrequiring an answer, sends a Facility IE with a component included in the RELEASE COMPLETE or a FACILITYmessage and enters the call state U0.5.2.1.1.1.2Outgoing callGFP_U02_001subclause 7.2.1.1.1Ensure that the IUT in the call state U0, in order to transmit a component during the establishment of a bearer relatedcall , sends a SETUP message containing a VPN indicator IE and a Facility IE with a component and enters the call stateU1.GFP_U02_002subclause 7.2.1.1.1Ensure that the IUT in the call state U1 , on receipt of a CALL PROCEEDING message containing a Facility IE with acomponent requiring an answer, sends a FACILITY message containing a Facility IE with a component and enters thecall state U3.GFP_U02_003subclause 7.2.1.1.1Ensure that the IUT in the call state U1 , on receipt of an ALERTING message containing a Facility IE with acomponent requiring an answer, sends a FACILITY message containing a Facility IE with a component and enters thecall state U4.GFP_U02_004subclause 7.2.1.1.1Ensure that the IUT in the call state U1 , on receipt of a CONNECT message containing a Facility IE with a componentrequiring an answer, sends a Facility IE with a component in the CONNECT ACKNOWLEDGE or a FACILITYmessage, and enters the call state U10.SIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)11GFP_U02_005subclause 7.2.1.1.1Ensure that the IUT in the call state U10 , on receipt of a DISCONNECT message containing a Facility IE with acomponent requiring an answer, sends a Facility IE with a component included in the RELEASE or a FACILITYmessage and enters the call state U19.GFP_U02_006subclause 7.2.1.1.1Ensure that the IUT in the call state U11 , on receipt of a RELEASE message containing a Facility IE with a componentrequiring an answer, sends a Facility IE with a component included in the RELEASE COMPLETE or a FACILITYmessage and enters the call state U0.5.2.1.1.2GFT-ControlSelection:IUT supports the termination of the GFT-Control protocol. PICS: MCu 1.1.2.The TPs in this subclause refer to ISO/IEC 11582 [8], subclause 7.1.2, as referenced by subclause 7.2.1.1.2 ofEN 301 061-1 [2].GFP_U03_001subclause 7.1.2.2Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, not including a NFE, sends a FACILITY message containing a Facility IE with a component andremains in the call state U10.NOTE 1:The PINX entity becomes the destination entity for that Facility IE.GFP_U03_002subclause 7.1.2.2.1Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "endPINX" and with nodestinationEntityAddress element, sends a FACILITY message containing a Facility IE with a component and remainsin the call state U10.NOTE 2:The PINX entity becomes the destination entity for that Facility IE.Selection:PICS: IUT supports End PINX functionalities: TIu 1 OR TIu 2 [15].GFP_U03_003subclause 7.1.2.2.2Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "endPINX" and with nodestinationEntityAddress element, sends a FACILITY message containing the same Facility IE at the interface to thenext PINX, and remains in the call state U10.NOTE 3:The PINX entity becomes the destination entity for that Facility IE.Selection:PICS: IUT supports Transit PINX functionalities: TIu 3 [15].GFP_U03_004subclause 7.1.2.2.1Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "anyTypeOfPINX" and with nodestinationEntityAddress element, sends a FACILITY message containing a Facility IE with a component and remainsin the call state U10.NOTE 4:The PINX entity becomes the destination entity for that Facility IE.Selection:PICS: IUT supports End PINX functionalities: TIu 1 OR TIu 2 [15].SIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)12GFP_U03_005subclause 7.1.2.2.2Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "anyTypeOfPINX" and with nodestinationEntityAddress element, either sends a FACILITY message containing a Facility IE with a component,or sends a FACILITY message containing the same Facility IE at the interface to the next PINX,and remains in the call state U10.NOTE 5:The PINX entity passes the Facility IE to the next PINX.Selection:PICS: IUT supports Transit PINX functionalities: TIu 3 [15].GFP_U03_006subclause 7.1.2.2Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "anyTypeOfPINX" and with adestinationEntityAddress element matching the IUT address, sends a FACILITY message containing a Facility IE with acomponent and remains in the call state U10.NOTE 6:The PINX entity becomes the destination entity for that Facility IE.GFP_U03_007subclause 7.1.2.2.1Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "endPINX" and with adestinationEntityAddress element matching the IUT address, sends a FACILITY message containing a Facility IE with acomponent and remains in the call state U10.NOTE 7:The PINX entity becomes the destination entity for that Facility IE.Selection:PICS: IUT supports End PINX functionalities: TIu 1 OR TIu 2 [15].GFP_U03_008subclause 7.1.2.2.2Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "endPINX" and with adestinationEntityAddress element matching the IUT address, sends a FACILITY message containing the same FacilityIE at the interface to the next PINX and remains in the call state U10.NOTE 8:The PINX entity passes the Facility IE to the next PINX.Selection:PICS: IUT supports Transit PINX functionalities: TIu 3 [15].GFP_U03_009subclause 7.1.2.2.1Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "endPINX" and with adestinationEntityAddress element not matching the IUT address, sends a FACILITY message containing a Facility IEwith a component and remains in the call state U10.NOTE 9:The PINX entity becomes the destination entity for that Facility IE.Selection:PICS: IUT supports End PINX functionalities: TIu 1 OR TIu 2 [15].GFP_U03_010subclause 7.1.2.2.2Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "endPINX" and with adestinationEntityAddress element not matching the IUT address, sends a FACILITY message containing the sameFacility IE at the interface to the next PINX and remains in the call state U10.NOTE 10:The PINX entity passes the Facility IE to the next PINX.Selection:PICS: IUT supports Transit PINX functionalities: TIu 3 [15].SIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)13GFP_U03_011subclause 7.1.2.2.1Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "anyTypeOfPINX" and with adestinationEntityAddress element not matching the IUT address, sends no message and remains in the call state U10.NOTE
...
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Generic functional protocol for the support of supplementary services 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 061-3 Version 1.1.3SIST EN 301 061-3:2001en01-september-2001SIST EN 301 061-3:2001SLOVENSKI
STANDARD
SIST EN 301 061-3:2001
EN 301 061-3 V1.1.3 (1998-10)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Digital Subscriber Signalling System No. one (DSS1) protocol;Generic functional protocol for the support ofsupplementary services 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 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)2ReferenceDEN/SPS-05110-3 (9tor0ie0.PDF)KeywordsDSS1, generic, ISDN, supplementary service,VPN, TSS&TP, userETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frhttp://www.etsi.orgCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1998.All rights reserved.SIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)3ContentsIntellectual Property Rights.4Foreword.41Scope.52Normative references.53Definitions and abbreviations.63.1Definitions.63.1.1Definitions related to conformance testing.63.1.2Definitions related to EN 301 061-1.63.2Abbreviations.64Test Suite Structure (TSS).75Test Purposes (TP).85.1Introduction.85.1.1TP naming convention.85.1.2Source of TP definition.85.1.3TP structure.85.1.4Test strategy.95.2User TPs for VPN-GFP.95.2.1Common IE approach.95.2.1.1Bearer related transport mechanism.105.2.1.1.1Protocol control.105.2.1.1.1.1Incoming call.105.2.1.1.1.2Outgoing call.105.2.1.1.2GFT-Control.115.2.1.2Connection oriented bearer independent transport mechanism.145.2.1.2.1Protocol control.145.2.1.2.1.1Originating interface.145.2.1.2.1.2Destination interface.145.2.1.2.1.3Connection clearing.145.2.1.2.1.4Interaction.145.2.1.2.1.5Handling of error conditions.155.2.1.2.1.6Timers.165.2.1.2.1.7Exchange of FACILITY messages.165.2.1.2.2GFT-Control.175.2.1.2.2.1Control of the Facility IE.175.2.1.2.2.2Control of the NCICS connection.195.2.1.2.2.2ATransit PINX.195.2.2Generic notification procedures.205.2.2.1Protocol control.205.2.2.2GFT-control.215.2.3Co-ordination function.215.2.4ROSE requirements.226Compliance.237Requirements for a comprehensive testing service.23History.24SIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)4Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin 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 European Standard (Telecommunications series) covering the IntegratedServices Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Generic functionalprotocol for the support of supplementary services at the "b" service entry point for Virtual Private Network (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), user";Part 5: "Test Suite Structure and Test Purposes (TSS&TP), specification for the network";Part 6: "Abstract Test Suite (ATS), network".National transposition datesDate of adoption of this EN: 30 October 1998Date of latest announcement of this EN (doa): 31 January 1999Date of latest publication of new National Standardor endorsement of this EN (dop/e): 31 July 1999Date of withdrawal of any conflicting National Standard (dow): 31 July 1999SIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)51ScopeThis third part of EN 301 061 specifies the Test Suite Structure and Test Purposes (TSS&TP) for the user side of theT reference point (as defined in ITU-T Recommendation I.411 [10]) of implementations conforming to the stage threestandard for the generic functional protocol for the support of supplementary services for Virtual Private Network(VPN) applications for the pan-European Integrated Services Digital Network (ISDN) by means of the DigitalSubscriber Signalling System No. one (DSS1) protocol, EN 301 061-1 [2].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 300 196-1 (V1.2): "Integrated Services Digital Network (ISDN); Generic functional protocolfor the support of supplementary services; Digital Subscriber Signalling System No. one (DSS1)protocol; Part 1: Protocol specification".[2]EN 301 061-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Generic functional protocol for the support of supplementary services atthe "b" service entry point for Virtual Private Network (VPN) applications; Part 1: Protocolspecification".[3]EN 301 061-2: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Generic functional protocol for the support of supplementary services atthe "b" service entry point for Virtual Private Network (VPN) applications; Part 2: ProtocolImplementation Conformance Statement (PICS) proforma specification".[4]ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol and profileconformance testing specifications; Standardization methodology".[5]ISO/IEC 9646-1 (1994): "Information technology; Open Systems Interconnection; Conformancetesting methodology and framework; Part 1: General concepts".[6]ISO/IEC 9646-2 (1994): "Information technology; Open Systems Interconnection; Conformancetesting methodology and framework; Part 2: Abstract Test Suite specification".[7]Void.[8]ISO/IEC 11582 (1995): "Information technology; Telecommunications and information exchangebetween systems; Private Integrated Services Network; Generic functional protocol for the supportof supplementary services; Inter-exchange signalling procedures and protocol".[9]ITU-T Recommendation I.112 (1993): "Vocabulary and terms for ISDNs".[10]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces; reference configurations".SIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)63Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the following definitions apply:3.1.1Definitions related to conformance testingAbstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [5].Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [5].PICS proforma: Refer to ISO/IEC 9646-1 [5].Protocol Implementation eXtra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 [5].PIXIT proforma: Refer to ISO/IEC 9646-1 [5].Test Purpose (TP): Refer to ISO/IEC 9646-1 [5].3.1.2Definitions related to EN 301 061-1component: See EN 300 196-1 [1], subclause 11.2.2.1.invoke component: See EN 300 196-1 [1], subclause 11.2.2.1.return error component: See EN 300 196-1 [1], subclause 11.2.2.1.return result component: See EN 300 196-1 [1], subclause 11.2.2.1.service; telecommunication service: See ITU-T Recommendation I.112 [9], definition 201.3.2AbbreviationsFor the purposes of the present document, the following abbreviations apply:APDUApplication Protocol Data UnitATMAbstract Test MethodATSAbstract Test SuiteGFTGeneric Functional TransportIEInformation ElementISDNIntegrated Services Digital NetworkIUTImplementation Under TestNCICSNetworked Call Independent Connection oriented SignallingPICSProtocol Implementation Conformance StatementPINXPrivate Integrated services Network eXchangePIXITProtocol Implementation eXtra Information for TestingROSERemote Operations Service ElementTPTest PurposeTSSTest Suite StructureVPNVirtual Private NetworkVPN-GFPGeneric Functional Protocol for the support of supplementary services for VPNSIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)74Test Suite Structure (TSS)group5.2.1. Common Information Element (IE) approach5.2.1.1. Bearer related transport mechanism5.2.1.1.1. Protocol control5.2.1.1.1.1. Outgoing callU015.2.1.1.1.2. Incoming callU025.2.1.1.2. GFT-controlU035.2.1.2. Connection oriented Bearer bearer independent transport mechanism5.2.1.2.1. Protocol control5.2.1.2.1.1. Originating interfaceU045.2.1.2.1.2. Destination interfaceU055.2.1.2.1.3. Connection clearingU065.2.1.2.1.4. InteractionU075.2.1.2.1.5. Handling of error conditionsU085.2.1.2.1.6. TimersU095.2.1.2.1.7. Exchange of FACILITY messagesU105.2.1.2.2. GFT-controlU115.2.2. Generic notification procedure5.2.2.1. Protocol controlU135.2.2.2. GFT-controlU145.2.3. Co-ordination functionU155.2.4. ROSE requirementU16Figure 1: Test suite structureSIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)85Test 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:__=protocol specification: "GFP"=type of IUT:UUserNNetwork=group2 digit field representing group reference according to TSS=sequential number(001-999)5.1.2Source of TP definitionThe TPs are based on EN 301 061-1 [2].5.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 and this is illustrated in table 2. This table should beread in conjunction with any TP, i.e. use a TP as an example to fully understand the table.SIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)9Table 2: Structure of a single TP for Generic Functional Protocol for the supportof supplementary services for VPN (VPN-GFP)TP partTextExampleHeader tabsee table 1 tabsubclause 0.0.0StimulusEnsure that the IUT in the .N10 etc. see below for message structurereceiving a XXXX messageor to request a .Reactionsends, saves, does, etc.using en bloc sending, .if the action is sendingsee below for message structure, etc.and remains in the same stateor and enters state Messagestructuremessage containing aSETUP, FACILITY, CONNECT, .a) IE withb) a encoded as or including and back to a or b,Bearer capability, Facility, .NOTE 1:TP are always applicable. Optional TPs are applicable according to the configuration options of the IUT. Ifthe configuration option is covered by a Protocol Implementation Conformance Statement (PICS) item, aselection criteria is indicated, else the selection of the corresponding test cases will depend on test suiteparameters Protocol Implementation eXtra Information for Testing (PIXIT) in the Abstract Test Suite(ATS).NOTE 2: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.5.1.4Test strategyAs the base standard EN 301 061-1 [2] contains no explicit requirements for testing, the TPs were generated as a resultof an analysis of the base standard and the PICS specification EN 301 061-2 [3].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 [4]).5.2User TPs for VPN-GFPAll PICS items referred to in this subclause are as specified in EN 301 061-2 [3] unless indicated otherwise by anothernumbered reference.Unless specified, the messages and IEs indicated are valid and contain at least the mandatory parameters and possiblyoptional parameters.5.2.1Common IE approachSelection:IUT supports the common IE category. PICS: MCu 1.The following TPs are testing the procedures associated with the transport of components using the messages for theestablishment and clearing of calls.The primitive exchanged between the different entities are not observable. Only the PDU exchanged between peerimplementations can be observed.So to check that the component is properly transmitted to the Generic Functional Transport (GFT) entity, it shallprovoke a reaction from Remote Operations Service Element (ROSE) entity that will request the transmission of thecorresponding component response. This component will be transmitted in a call related message with the same callreference, which is observable.SIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)10To provoke a reaction from the ROSE entity, a return result component, with an invokeID not related to a currentlyactive invocation, can be sent.5.2.1.1Bearer related transport mechanismSelection:IUT supports the bearer related transport mechanism. PICS: MCu 1.1.In all the TPs of this subclause, the call reference is in a Virtual Private Network (VPN) context.5.2.1.1.1Protocol controlIn the TPs of this subclause, no NFE shall be included so that the Private Integrated services Network eXchange (PINX)entity will be the addressed PINX and can treat the received component.5.2.1.1.1.1Incoming callGFP_U01_001subclause 7.2.1.1.1Ensure that the IUT in the call state U0, on receipt of a SETUP message containing a VPN indicator IE and a Facility IEwith a component requiring an answer, sends a Facility IE with a component, included in a SETUP ACKNOWLEDGE,CALL PROCEEDING or FACILITY message and enters respectively the U25, U9 or U6 call state.GFP_U01_002subclause 7.2.1.1.1Ensure that the IUT in the call state U8 , having sent a CONNECT messages, on receipt of a CONNECTACKNOWLEDGE message containing a Facility IE with a component requiring an answer, sends a FACILITYmessage containing a Facility IE with a component and enters the call state U10.GFP_U01_003subclause 7.2.1.1.1Ensure that the IUT in the call state U10 , on receipt of a DISCONNECT message containing a Facility IE with acomponent requiring an answer, sends a Facility IE with a component included in the RELEASE or a FACILITYmessage and enters the call state U19.GFP_U01_004subclause 7.2.1.1.1Ensure that the IUT in the call state U11 , on receipt of a RELEASE message containing a Facility IE with a componentrequiring an answer, sends a Facility IE with a component included in the RELEASE COMPLETE or a FACILITYmessage and enters the call state U0.5.2.1.1.1.2Outgoing callGFP_U02_001subclause 7.2.1.1.1Ensure that the IUT in the call state U0, in order to transmit a component during the establishment of a bearer relatedcall , sends a SETUP message containing a VPN indicator IE and a Facility IE with a component and enters the call stateU1.GFP_U02_002subclause 7.2.1.1.1Ensure that the IUT in the call state U1 , on receipt of a CALL PROCEEDING message containing a Facility IE with acomponent requiring an answer, sends a FACILITY message containing a Facility IE with a component and enters thecall state U3.GFP_U02_003subclause 7.2.1.1.1Ensure that the IUT in the call state U1 , on receipt of an ALERTING message containing a Facility IE with acomponent requiring an answer, sends a FACILITY message containing a Facility IE with a component and enters thecall state U4.GFP_U02_004subclause 7.2.1.1.1Ensure that the IUT in the call state U1 , on receipt of a CONNECT message containing a Facility IE with a componentrequiring an answer, sends a Facility IE with a component in the CONNECT ACKNOWLEDGE or a FACILITYmessage, and enters the call state U10.SIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)11GFP_U02_005subclause 7.2.1.1.1Ensure that the IUT in the call state U10 , on receipt of a DISCONNECT message containing a Facility IE with acomponent requiring an answer, sends a Facility IE with a component included in the RELEASE or a FACILITYmessage and enters the call state U19.GFP_U02_006subclause 7.2.1.1.1Ensure that the IUT in the call state U11 , on receipt of a RELEASE message containing a Facility IE with a componentrequiring an answer, sends a Facility IE with a component included in the RELEASE COMPLETE or a FACILITYmessage and enters the call state U0.5.2.1.1.2GFT-ControlSelection:IUT supports the termination of the GFT-Control protocol. PICS: MCu 1.1.2.The TPs in this subclause refer to ISO/IEC 11582 [8], subclause 7.1.2, as referenced by subclause 7.2.1.1.2 ofEN 301 061-1 [2].GFP_U03_001subclause 7.1.2.2Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, not including a NFE, sends a FACILITY message containing a Facility IE with a component andremains in the call state U10.NOTE 1:The PINX entity becomes the destination entity for that Facility IE.GFP_U03_002subclause 7.1.2.2.1Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "endPINX" and with nodestinationEntityAddress element, sends a FACILITY message containing a Facility IE with a component and remainsin the call state U10.NOTE 2:The PINX entity becomes the destination entity for that Facility IE.Selection:PICS: IUT supports End PINX functionalities: TIu 1 OR TIu 2 [15].GFP_U03_003subclause 7.1.2.2.2Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "endPINX" and with nodestinationEntityAddress element, sends a FACILITY message containing the same Facility IE at the interface to thenext PINX, and remains in the call state U10.NOTE 3:The PINX entity becomes the destination entity for that Facility IE.Selection:PICS: IUT supports Transit PINX functionalities: TIu 3 [15].GFP_U03_004subclause 7.1.2.2.1Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "anyTypeOfPINX" and with nodestinationEntityAddress element, sends a FACILITY message containing a Facility IE with a component and remainsin the call state U10.NOTE 4:The PINX entity becomes the destination entity for that Facility IE.Selection:PICS: IUT supports End PINX functionalities: TIu 1 OR TIu 2 [15].SIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)12GFP_U03_005subclause 7.1.2.2.2Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "anyTypeOfPINX" and with nodestinationEntityAddress element, either sends a FACILITY message containing a Facility IE with a component,or sends a FACILITY message containing the same Facility IE at the interface to the next PINX,and remains in the call state U10.NOTE 5:The PINX entity passes the Facility IE to the next PINX.Selection:PICS: IUT supports Transit PINX functionalities: TIu 3 [15].GFP_U03_006subclause 7.1.2.2Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "anyTypeOfPINX" and with adestinationEntityAddress element matching the IUT address, sends a FACILITY message containing a Facility IE with acomponent and remains in the call state U10.NOTE 6:The PINX entity becomes the destination entity for that Facility IE.GFP_U03_007subclause 7.1.2.2.1Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "endPINX" and with adestinationEntityAddress element matching the IUT address, sends a FACILITY message containing a Facility IE with acomponent and remains in the call state U10.NOTE 7:The PINX entity becomes the destination entity for that Facility IE.Selection:PICS: IUT supports End PINX functionalities: TIu 1 OR TIu 2 [15].GFP_U03_008subclause 7.1.2.2.2Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "endPINX" and with adestinationEntityAddress element matching the IUT address, sends a FACILITY message containing the same FacilityIE at the interface to the next PINX and remains in the call state U10.NOTE 8:The PINX entity passes the Facility IE to the next PINX.Selection:PICS: IUT supports Transit PINX functionalities: TIu 3 [15].GFP_U03_009subclause 7.1.2.2.1Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "endPINX" and with adestinationEntityAddress element not matching the IUT address, sends a FACILITY message containing a Facility IEwith a component and remains in the call state U10.NOTE 9:The PINX entity becomes the destination entity for that Facility IE.Selection:PICS: IUT supports End PINX functionalities: TIu 1 OR TIu 2 [15].GFP_U03_010subclause 7.1.2.2.2Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "endPINX" and with adestinationEntityAddress element not matching the IUT address, sends a FACILITY message containing the sameFacility IE at the interface to the next PINX and remains in the call state U10.NOTE 10:The PINX entity passes the Facility IE to the next PINX.Selection:PICS: IUT supports Transit PINX functionalities: TIu 3 [15].SIST EN 301 061-3:2001
ETSIEN 301 061-3 V1.1.3 (1998-10)13GFP_U03_011subclause 7.1.2.2.1Ensure that the IUT in the call state U10, on receipt of a FACILITY message containing a Facility IE with a componentrequiring an answer, including a NFE with a destinationEntity element indicating "anyTypeOfPINX" and with adestinationEntityAddress element not matching the IUT address, sends no message and remains in the call state U10.NOTE
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.