SIST EN 301 061-2: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 2: Protocol Implementation Conformace Statement (PICS) proforma specification
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 2: Protocol Implementation Conformace Statement (PICS) proforma specification
PICS 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 vstopni točki "b" storitve za aplikacije navideznega zasebnega omrežja (VPN) - 2. del: Izjava o skladnosti izvedbe protokola (PICS) - Proforma specifikacije
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 2: Protocol Implementation Conformace Statement (PICS) proforma specification33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 301 061-2 V.1.33SIST EN 301 061-2:en01-GHFHPEHU3SIST EN 301 061-2:SLOVENSKI
STANDARD
EN 301 061-2 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 2: Protocol Implementation ConformanceStatement (PICS) proforma specificationSIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)2ReferenceDEN/SPS-05110-2 (9toi0ie0.PDF)KeywordsISDN, DSS1, generic, supplementary service,VPN, PICSETSIPostal 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-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)3ContentsIntellectual Property Rights.5Foreword.51Scope.62Normative references.63Definitions.74Abbreviations.75Conformance.8Annex A (normative):PICS proforma.9A.1Instructions for completing the PICS proforma.9A.1.1Identification of the implementation.9A.1.2Global statement of conformance.9A.1.3Explanation of PICS proforma subclauses.9A.1.4Symbols, abbreviations and terms.10A.2Identification of the implementation.10A.2.1Date of the statement.10A.2.2Implementation Under Test (IUT) identification.10A.2.3System Under Test (SUT) identification.10A.2.4Product supplier.11A.2.5Client.11A.2.6PICS contact person.12A.3PICS / System Conformance Statement (SCS).12A.4Identification of the protocol.12A.5Global statement of conformance.12A.6Roles.13A.7User.13A.7.1Major capabilities.14A.7.2Subsidiary capabilities.15A.7.3Protocol data units for the bearer-related transport mechanism (VPN context).15A.7.4Protocol data units for the connection-oriented bearer independent transport mechanism (VPN context).16A.7.5Protocol data unit parameters for the bearer-related transport mechanism (VPN context).17A.7.5.1Protocol data unit parameters received.17A.7.5.2Protocol data unit parameters transmitted.22A.7.6Protocol data unit parameters for the connection-oriented bearer independent transport mechanism(VPN context).27A.7.6.1Protocol data unit parameters received.27A.7.6.2Protocol data unit parameters transmitted.31A.7.7Timers (VPN context).35A.7.8Call states.35A.8Network.35A.8.1Major capabilities.36A.8.2Subsidiary capabilities.37A.8.3Protocol data units for the bearer-related transport mechanism (VPN context).37A.8.4Protocol data units for the connection-oriented bearer independent transport mechanism (VPN context).38A.8.5Protocol data unit parameters for the bearer-related transport mechanism (VPN context).39A.8.5.1Protocol data unit parameters received.39A.8.5.2Protocol data unit parameters transmitted.44SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)4A.8.6Protocol data unit parameters for the connection-oriented bearer independent transport mechanism(VPN context).49A.8.6.1Protocol data unit parameters received.49A.8.6.2Protocol data unit parameters transmitted.53A.8.7Timers.57A.8.8Call states.57Annex B (normative):Requirements list.58B.1User.58B.1ARequirements on items used in the basic call PICS.58B.2Network.58B.2ARequirements on items used in the basic call PICS.58History.59SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)5Intellectual 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 2 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-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)61ScopeThis second part of EN 301 061 is applicable to the generic functional protocol for the support of supplementaryservices for Virtual Private Network (VPN) applications for the pan-European Integrated Services Digital Network(ISDN) as provided by European public telecommunications operators at the "b service entry point" (as defined inEN 301 060-1 [2]) by means of the DSS1 protocol.The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for the ISDNDSS1 generic functional protocol for VPN applications as specified in EN 301 061-1 [4] in compliance with therelevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [6].The supplier of a protocol implementation which is claimed to conform to EN 301 061-1 [4] is required to complete acopy of the PICS proforma provided in annex A of the present document and is required to provide the informationnecessary to identify both the supplier and the implementation.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 403-3: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Signalling network layer for the circuit-mode basic call control; Part 3:Protocol Implementation Conformance Statement (PICS) proforma specification".[2]EN 301 060-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Basic call applications; Enhancement at the "b" service entry point forVirtual Private Network (VPN) applications; Part 1: Protocol specification".[3]EN 301 060-2: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Basic call applications; Enhancement at the "b" service entry point forVirtual Private Network (VPN) applications; Part 2: Protocol Implementation ConformanceStatement (PICS) proforma specification".[4]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".[5]ISO/IEC 9646-1 (1994): "Information technology; Open systems interconnection; Conformancetesting methodology and framework; Part 1: General concepts".[6]ISO/IEC 9646-7 (1995): "Information technology; Open systems interconnection; Conformancetesting methodology and framework; Part 7: Implementation Conformance Statements".[7]ISO/IEC 15056 (1997): "Information technology; Telecommunications and information exchangebetween systems; Private Integrate Service Network; Inter-exchange signalling protocol; Transitcounter additional network feature".SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)73DefinitionsFor the purposes of the present document, the following definitions apply, in addition to those given inEN 301 061-1 [4]:Protocol Implementation Conformance Statement (PICS): A statement made by the supplier of an OSIimplementation or system, stating which capabilities have been implemented for a given OSI protocol(see ISO/IEC 9646-1 [5]).PICS proforma: A document, in the form of a questionnaire, designed by the protocol specifier or conformance testsuite specifier, which, when completed for an OSI implementation or system becomes the PICS(see ISO/IEC 9646-1 [5]).static conformance review: A review of the extent to which the static conformance requirements are met by theImplementation Under Test (IUT), accomplished by comparing the PICS with the static conformance requirementsexpressed in the relevant standard(s) (see ISO/IEC 9646-1 [5]).4AbbreviationsFor the purposes of the present document, the abbreviations given in EN 301 061-1 [4] and the following apply:ANDBoolean "and"CConditional requirement (to be observed if the relevant conditions apply)DSS1Digital Subscriber Signalling System No. oneIERInformation Elements ReceivedIETInformation Elements TransmittedISDNIntegrated Services Digital NetworkIUTImplementation Under TestMMandatory requirement (to be observed in all cases)MCMajor CapabilitiesN/ANot applicable, not supported or the conditions for status are not metNonot supportedNOTBoolean "not"OOption (may be selected to suit the implementation, provided that any requirements applicable tothe option are observed)O.nOptions, but support required for either at least one or only one of the options in the group labelledwith the same numeral "n"ORBoolean "or"OSIOpen Systems InterconnectionPParametersPICSProtocol Implementation Conformance StatementRRoleSCSubsidiary CapabilitiesSCSSystem Conformance StatementSUTSystem Under TestVPNVirtual Private NetworkYessupportedSIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)85ConformanceA PICS proforma which conforms to this PICS proforma specification shall be technically equivalent to annex A, andshall preserve the numbering and ordering of the items in annex A.A PICS which conforms to this PICS proforma specification shall:a)describe an implementation which claims to conform to EN 301 061-1 [4];b)be a conforming ICS proforma which has been completed in accordance with the instructions for completiongiven in annex A, clause A.1;c)include the information necessary to uniquely identify both the supplier and the implementation.SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)9Annex A (normative):PICS proformaNotwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that usersof the present document may freely reproduce the PICS proforma in this annex so that it can be used for its intendedpurposes and may further publish the completed PICS.A.1Instructions for completing the PICS proformaA.1.1Identification of the implementationIdentification of the IUT and the system in which it resides (the System Under Test (SUT)) should be filled in so as toprovide as much detail as possible regarding version numbers and configuration options.The product supplier information and client information should both be filled in if they are different.A person who can answer queries regarding information supplied in the PICS should be named as the contact person.The System Conformance Statement (SCS) as defined in ISO/IEC 9646-1 [5] is a document supplied by the client orproduct supplier that summarizes which OSI International Standards, ITU-T (CCITT) Recommendations, ENs or otherstandards are implemented and to which conformance is claimed. The PICS/SCS subclause should describe therelationship of the PICS to the SCS.A.1.2Global statement of conformanceIf the answer to the statement in this subclause is "Yes", all subsequent subclauses should be completed to facilitateselection of test cases for optional functions.If the answer to the statement in this subclause is "No", all subsequent subclauses should be completed, and allnon-supported mandatory capabilities should be identified and explained. Explanations may be entered in the commentsfield at the bottom of each table or on attached sheets of paper.A.1.3Explanation of PICS proforma subclausesThe PICS proforma contains a Roles clause and thereafter is presented in two parts (for user and network) with thefollowing subclauses, as required:-major capabilities;-subsidiary capabilities;-protocol data unit support;-protocol data unit parameters;-timers;-call states.The User clause shall only be completed for user implementations (including private network implementations) whilethe Network clause shall only be completed for network implementations. The Roles subclause shall be completed forall implementations.The relationship between this PICS proforma and other related PICS proforma (e.g. the basic call PICS proforma) isexpressed in the requirements list contained in annex B. This provides the additional restrictions placed on the relatedproforma (different conditions, different status, etc.).SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)10A.1.4Symbols, abbreviations and termsThe PICS proforma contained in this annex is comprised of information in tabular form in accordance with theguidelines presented in ISO/IEC 9646-7 [6].The reference column contained in the tables gives reference to the appropriate part(s) of EN 301 061-1 [4] describingthe particular item. Note, however, that a reference merely indicates the place where the core of a description of an itemcan be found. Any additional information contained in EN 301 061-1 [4] has to be taken into account when making astatement about the conformance of that particular item.The following common notations, defined in ISO/IEC 9646-7 [6] are used for the status column:Mmandatory;Ooptional;N/Anot applicable;O.for mutually exclusive or selectable options from a set.The following common notations, defined in ISO/IEC 9646-7 [6] are used for the support column:Yfor supported / implemented;Nfor not supported / not implemented.A.2Identification of the implementationA.2.1Date of the statement.A.2.2Implementation Under Test (IUT) identificationIUT name:.IUT version:.A.2.3System Under Test (SUT) identificationSUT name:.Hardware configuration:.SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)11Operating system:.A.2.4Product supplierName:.Address:.Telephone number:.Facsimile number:.Additional information:.A.2.5ClientName:.Address:.Telephone number:.Facsimile number:.Additional information:.SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)12A.2.6PICS contact personName:.Address:.Telephone number:.Facsimile number:.Additional information:.A.3PICS / System Conformance Statement (SCS)Provide the relationship of the PICS with the SCS for the system:.A.4Identification of the protocolThis PICS proforma applies to the following standard:EN 301 061-1 (V1.2): "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 forVirtual Private Network (VPN) applications; Part 1: Protocol specification".A.5Global statement of conformanceThe implementation described in this PICS meets all the mandatory requirements of the referenced standard?[
] Yes[
] NoSIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)13NOTE:Answering "No" to this question indicates non-conformance to the protocol specification. Non-supportedmandatory capabilities are to be identified in the PICS, with an explanation of why the implementation isnon-conforming. Explanations may be entered in the comments field at the bottom of each table or onattached pages.In the tabulations which follow, all references are to EN 301 061-1 [4] unless another numbered reference is explicitlyindicated.A.6RolesTable A.1: RolesItemMajor role:Does the implementation.Conditions forstatusStatusReferenceSupportType of implementationR 1not usedR 2.1support user requirements?O.11.9, 1.10[ ]Yes [ ]NoR 2.2support network requirements?O.11.9, 1.10[ ]Yes [ ]NoR 3not usedR 4not usedR 5not usedO.1Support of one and only one of these options is required.Comments:A.7UserThe tables provided in this clause need only to be completed for user implementations, where item R 2.1 in table A.1 issupported.SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)14A.7.1Major capabilitiesTable A.2: Major capabilities - userItemMajor capability:Does the implementation support.Conditions forstatusStatusReferenceSupportMCu 1the functional protocol (common informationelement category) for the control ofsupplementary services?O.27[ ]Yes [ ]NoMCu 1.1the bearer related transport mechanism?MCu 1NOT MCu 1O.3N/A7.2.1.1[ ]Yes [ ]No[ ] N/AMCu 1.1.1Protocol control requirements?MCu 1.1NOT MCu 1.1MN/A7.2.1.1.1[ ]Yes [ ]No[ ] N/AMCu 1.1.2the termination of the GFT-Control protocol?MCu 1.1NOT MCu 1.1ON/A7.2.1.1.2[ ]Yes [ ]No[ ] N/AMCu 1.2the connection-oriented bearer independenttransport mechanism?MCu 1NOT MCu 1O.3N/A7.2.1.2[ ]Yes [ ]No[ ] N/AMCu 1.2.1Protocol control requirements?MCu 1.2NOT MCu 1.2MN/A7.2.1.2.1[ ]Yes [ ]No[ ] N/AMCu 1.2.2the termination of the GFT-Control protocol?MCu 1.2NOT MCu 1.2ON/A7.2.1.2.2[ ]Yes [ ]No[ ] N/AMCu 2generic notification procedures?O.28[ ]Yes [ ]NoMCu 2.1Protocol control requirements?MCu 2NOT MCu 2MN/A8.1.3[ ]Yes [ ]No[ ] N/AMCu 2.2the termination of the GFT-Control protocol?MCu 2NOT MCu 2ON/A8.1.4[ ]Yes [ ]No[ ] N/AMCu 3Application layer requirements?MCu 1.1.2 ORMCu 1.2.2 ORMCu 2.2NOT (MCu 1.1.2ORMCu 1.2.2 ORMCu 2.2)MN/A9[ ]Yes [ ]No[ ] N/AMCu 4Flow control?N/AAnnex CN/AMCu 5the co-existence of the public networkcontext and the VPN context on the sameaccess?O1[ ]Yes [ ]NoMCu 6the transit counter additional networkfeature?O[8][ ]Yes [ ]NoO.2O.3Support of at least one of these options is required.Support of at least one of these options is required.Comments:SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)15A.7.2Subsidiary capabilitiesTable A.3: Subsidiary capabilities - userItemSubsidiary capability:Does the implementation support.Conditions forstatusStatusReferenceSupportSCu 1Notification proceduresSCu 1.1the transport of integer coded notificationinformation in octet 3 of the Notificationindicator information element?MCu 2NOT MCu 2ON/A8.1[ ]Yes [ ]No[ ] N/ASCu 1.2the transport of ASN.1 notificationinformation in octet 4 of the Notificationindicator information element, using thecodepoint 'Discriminator for BER encodednotification extension' in octet 3?MCu 2NOT MCu 2ON/A8.1[ ]Yes [ ]No[ ] N/ASCu 1.3the transport of ASN.1 notificationinformation in octet 4 of the Notificationindicator information element, using thecodepoint 'discriminator for extension to ISOdefined ASN.1 encoded notification structure'in octet 3?MCu 2NOT MCu 2ON/A8.1[ ]Yes [ ]No[ ] N/ASCu 1.4the generation of notification information?MCu 2NOT MCu 2ON/A7.4.3.1[ ]Yes [ ]No[ ] N/ASCu 1.5the actions at a transit PINX regardingnotifications?MCu 2NOT MCu 2MN/A7.4.3.2[ ]Yes [ ]No[ ] N/ASCu 1.5the actions at a receiving end PINXregarding notifications?MCu 2NOT MCu 2MN/A7.4.3.3[ ]Yes [ ]No[ ] N/ASCu 2Control of supplementary services using the common information element approachSCu 2.1the generation of APDUs (as a sourcePINX)?MCu 1.1.2NOT MCu 1.1.2ON/A7.1.2.1[ ]Yes [ ]No[ ] N/ASCu 2.2the actions at a receiving PINX regarding theFacility information element?MCu 1.1.2NOT MCu 1.1.2MN/A7.1.2.2[ ]Yes [ ]No[ ] N/AComments:A.7.3Protocol data units for the bearer-related transportmechanism (VPN context)Table A.4: Messages received (VPN context) - userItemMessage (VPN context):Does the implementation support theinterpretation of .Conditions forstatusStatusReferenceSupportMRu 26FACILITY?MCu 1.1NOT MCu 1.1MN/A11.1[ ]Yes [ ]No[ ] N/AComments:SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)16Table A.5: Messages transmitted (VPN context) - userItemMessage (VPN context):Does the implementation support theinclusion of .Conditions forstatusStatusReferenceSupportMTu 26FACILITY?MCu 1.1NOT MCu 1.1ON/A11.1[ ]Yes [ ]No[ ] N/AComments:A.7.4Protocol data units for the connection-oriented bearerindependent transport mechanism (VPN context)Table A.6: Messages received (VPN context) - userItemMessage (VPN context):Does the implementation support theinterpretation of .Conditions forstatusStatusReferenceSupportMRu 1FACILITY?MCu 1NOT MCu 1MN/A11.1[ ]Yes [ ]No[ ] N/AMRu 2CALL PROCEEDING?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMRu 3CONNECT?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMRu 4CONNECT ACKNOWLEDGE?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMRu 5RELEASE?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMRu 6RELEASE COMPLETE?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMRu 7SETUP?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AComments:SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)17Table A.7: Messages transmitted (VPN context) - userItemMessage (VPN context):Does the implementation support theinclusion of .Conditions forstatusStatusReferenceSupportMTu 1FACILITY?MCu 1NOT MCu 1ON/A11.1[ ]Yes [ ]No[ ] N/AMTu 2CALL PROCEEDING?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMTu 3CONNECT?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMTu 4CONNECT ACKNOWLEDGE?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMTu 5RELEASE?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMTu 6RELEASE COMPLETE?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMTu 7SETUP?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AComments:A.7.5Protocol data unit parameters for the bearer-relatedtransport mechanism (VPN context)A.7.5.1Protocol data unit parameters receivedTable A.8: FACILITY PDU parameters received by the userItemFACILITY PDU parameters (VPN context):Does the implementation support theinformation element.Conditions forstatusStatusReferenceSupportIERu 26.1Protocol discriminator?MRu 26NOT MRu 26MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 26.2Call reference?MRu 26NOT MRu 26MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 26.3Message type?MRu 26NOT MRu 26MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 26.4Facility?MRu 26NOT MRu 26MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 26.5Notification indicator?MRu 26 ANDMCu 2NOT (MRu 26AND MCu2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)18Table A.9: ALERTING PDU parameters received by the userItemALERTING PDU parameters (VPNcontext): Does the implementationsupport the information element.Conditions forstatusStatusReferenceSupportIERu 1.1Facility?[1] MRu 1NOT [1] MRu 1MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 1.2Notification indicator?[1] MRu 1 ANDMCu 2NOT ([1] MRu 1AND MCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:Table A.10: CALL PROCEEDING PDU parameters received by the userItemCALL PROCEEDING PDU parameters(VPN context): Does the implementationsupport the information element.Conditions forstatusStatusReferenceSupportIERu 2.1Facility?[1] MRu 2NOT [1] MRu 2MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 2.2Notification indicator?[1] MRu 2 ANDMCu 2NOT ([1] MRu 2AND MCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:Table A.11: CONNECT PDU parameters received by the userItemCONNECT PDU parameters (VPNcontext): Does the implementationsupport the information element.Conditions forstatusStatusReferenceSupportIERu 4.1Facility?[1] MRu 4NOT [1] MRu 4MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 4.2Notification indicator?[1] MRu 4 ANDMCu 2NOT ([1] MRu 4AND MCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)19Table A.12: CONNECT ACKNOWLDEGE PDU parameters received by the userItemCONNECT ACKNOWLEDGE PDUparameters (VPN context): Does theimplementation support the informationelement.Conditions forstatusStatusReferenceSupportIERu 5.1Facility?[1] MRu 5NOT [1] MRu 5MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 5.2Notification indicator?[1] MRu 5 ANDMCu 2NOT ([1] MRu 5AND MCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:Table A.13: DISCONNECT PDU parameters received by the userItemDISCONNECT PDU parameters (VPNcontext): Does the implementationsupport the information element.Conditions forstatusStatusReferenceSupportIERu 6.1Facility?[1] MRu 6NOT [1] MRu 6MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 6.2Notification indicator?[1] MRu 6 ANDMCu 2NOT ([1] MRu 6AND MCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:Table A.14: INFORMATION PDU parameters received by the userItemINFORMATION PDU parameters (VPNcontext): Does the implementationsupport the information element.Conditions forstatusStatusReferenceSupportIERu 8.1Facility?[1] MRu 8NOT [1] MRu 8MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 8.2Notification indicator?[1] MRu 8 ANDMCu 2NOT ([1] MRu 8AND MCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)20Table A.15: PROGRESS PDU parameters received by the userItemPROGRESS PDU parameters (VPNcontext): Does the implementationsupport the information element.Conditions forstatusStatusReferenceSupportIERu 10.1Facility?[1] MRu 10NOT [1] MRu 10MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 10.2Notification indicator?[1] MRu 10 ANDMCu 2NOT ([1]MRu 10 ANDMCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:Table A.16: RELEASE PDU parameters received by the userItemRELEASE PDU parameters (VPN context):Does the implementation support theinformation element.Conditions forstatusStatusReferenceSupportIERu 11.1Facility?[1] MRu 11NOT [1] MRu 11MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 11.2Notification indicator?[1] MRu 11 ANDMCu 2NOT ([1]MRu 11 ANDMCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:Table A.17: RELEASE COMPLETE PDU parameters received by the userItemRELEASE COMPLETE PDU parameters(VPN context): Does the implementationsupport the information element .Conditions forstatusStatusReferenceSupportIERu 12.1Facility?[1] MRu 12NOT [1] MRu 12MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 12.2Notification indicator?[1] MRu 12 ANDMCu 2NOT ([1]MRu 12 ANDMCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)21Table A.18: SETUP PDU parameters received by the userItemSETUP PDU parameters (VPN context):Does the implementation support theinformation element.Conditions forstatusStatusReferenceSupportIERu 19.1Facility?[1] MRu 19NOT [1] MRu 19MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 19.2Notification indicator?[1] MRu 19 ANDMCu 2NOT ([1]MRu 19 ANDMCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:Table A.19: SETUP ACKNOWLEDGE PDU parameters received by the userItemSETUP ACKNOWLEDGE PDU parameters(VPN context): Does the implementationsupport the information element.Conditions forstatusStatusReferenceSupportIERu 20.1Facility?[1] MRu 20NOT [1] MRu 20MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 20.2Notification indicator?[1] MRu 20 ANDMCu 2NOT ([1]MRu 20 ANDMCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)22Table A.20: Facility Information element contents received by the userItemDoes the implementation support theinformation element field and valuesConditions forstatusStatusReferenceSupportIERu 1.4.1Network Facility Extension (octet 3.1)MCu 1 ANDMCu 1.1.2MCu 1 AND(NOTMCu 1.1.2)NOT MCu 1MM (note)N/A11.2.1[ ]Yes [ ]No[ ]Yes [ ]No[ ]N/AIERu 1.4.2Network Protocol Profile (octet 3.2)MCu 1 ANDMCu 3MCu 1 AND(NOT MCu 3)NOT MCu 1MM (note)N/A11.2.1[ ]Yes [ ]No[ ]Yes [ ]No[ ]N/AIERu 1.4.3Interpretation Component (octet 3.3)MCu 1 ANDMCu 3MCu 1 AND(NOT MCu3)NOT MCu 1MM (note)N/A11.2.1[ ]Yes [ ]No[ ]Yes [ ]No[ ]N/ANOTE:The support of this field implies the ability to pass this field transparently to the next entity.Comments:A.7.5.2Protocol data unit parameters transmittedTable A.21: FACILITY PDU parameters transmitted by the userItemFACILITY PDU parameters (VPN context):Does the implementation support theinformation element.Conditions forstatusStatusReferenceSupportIETu 26.1Protocol discriminator?MTu 26NOT MTu 26MN/A11.1[ ]Yes [ ]No[ ] N/AIETu 26.2Call reference?MTu 26NOT MTu 26MN/A11.1[ ]Yes [ ]No[ ] N/AIETu 26.3Message type?MTu 26NOT MTu 26MN/A11.1[ ]Yes [ ]No[ ] N/AIETu 26.4Facility?MTu 26NOT MTu 26MN/A11.1[ ]Yes [ ]No[ ] N/AIETu 26.5Notification indicator?MTu 26 ANDMCu 2NOT (MTu 26AND MCu2)ON/A11.1[ ]Yes [ ]No[ ] N/AComments:SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)23Table A.22: ALERTING PDU parameters transmitted by the userItemCALL PROCEEDING PDU parameters(VPN context): Does the implementationsupport the information element.Conditions forstatusStatusReferenceSupportIETu 1.1Facility?[1] MTu 1NOT [1] MTu 1ON/A11.1[ ]Yes [ ]No[ ] N/AIETu 1.2Notification indicator?[1] MTu 1 ANDMCu 2NOT ([1] MTu 1AND MCu 2)ON/A11.1[ ]Yes [ ]No[ ] N/AComments:Table A.23: CALL PROCEEDING PDU parameters transmitted by the userItemCALL PROCEEDING PDU parameters(VPN context): Does the implementationsupport the information element.Conditions forstatusStatusReferenceSupportIETu 2.1Facility?[1] MTu 2NOT [1] MTu 2ON/A11.1[ ]Yes [ ]No[ ] N/AIETu 2.2Notification indicator?[1] MTu 2 ANDMCu 2NOT ([1] MTu 2AND MCu 2)ON/A11.1[ ]Yes [ ]No[ ] N/AC
...
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 2: Protocol Implementation Conformace Statement (PICS) proforma specification33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 301 061-2 Version 1.1.3SIST EN 301 061-2:2001en01-februar-2001SIST EN 301 061-2:2001SLOVENSKI
STANDARD
EN 301 061-2 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 2: Protocol Implementation ConformanceStatement (PICS) proforma specificationSIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)2ReferenceDEN/SPS-05110-2 (9toi0ie0.PDF)KeywordsISDN, DSS1, generic, supplementary service,VPN, PICSETSIPostal 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-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)3ContentsIntellectual Property Rights.5Foreword.51Scope.62Normative references.63Definitions.74Abbreviations.75Conformance.8Annex A (normative):PICS proforma.9A.1Instructions for completing the PICS proforma.9A.1.1Identification of the implementation.9A.1.2Global statement of conformance.9A.1.3Explanation of PICS proforma subclauses.9A.1.4Symbols, abbreviations and terms.10A.2Identification of the implementation.10A.2.1Date of the statement.10A.2.2Implementation Under Test (IUT) identification.10A.2.3System Under Test (SUT) identification.10A.2.4Product supplier.11A.2.5Client.11A.2.6PICS contact person.12A.3PICS / System Conformance Statement (SCS).12A.4Identification of the protocol.12A.5Global statement of conformance.12A.6Roles.13A.7User.13A.7.1Major capabilities.14A.7.2Subsidiary capabilities.15A.7.3Protocol data units for the bearer-related transport mechanism (VPN context).15A.7.4Protocol data units for the connection-oriented bearer independent transport mechanism (VPN context).16A.7.5Protocol data unit parameters for the bearer-related transport mechanism (VPN context).17A.7.5.1Protocol data unit parameters received.17A.7.5.2Protocol data unit parameters transmitted.22A.7.6Protocol data unit parameters for the connection-oriented bearer independent transport mechanism(VPN context).27A.7.6.1Protocol data unit parameters received.27A.7.6.2Protocol data unit parameters transmitted.31A.7.7Timers (VPN context).35A.7.8Call states.35A.8Network.35A.8.1Major capabilities.36A.8.2Subsidiary capabilities.37A.8.3Protocol data units for the bearer-related transport mechanism (VPN context).37A.8.4Protocol data units for the connection-oriented bearer independent transport mechanism (VPN context).38A.8.5Protocol data unit parameters for the bearer-related transport mechanism (VPN context).39A.8.5.1Protocol data unit parameters received.39A.8.5.2Protocol data unit parameters transmitted.44SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)4A.8.6Protocol data unit parameters for the connection-oriented bearer independent transport mechanism(VPN context).49A.8.6.1Protocol data unit parameters received.49A.8.6.2Protocol data unit parameters transmitted.53A.8.7Timers.57A.8.8Call states.57Annex B (normative):Requirements list.58B.1User.58B.1ARequirements on items used in the basic call PICS.58B.2Network.58B.2ARequirements on items used in the basic call PICS.58History.59SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)5Intellectual 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 2 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-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)61ScopeThis second part of EN 301 061 is applicable to the generic functional protocol for the support of supplementaryservices for Virtual Private Network (VPN) applications for the pan-European Integrated Services Digital Network(ISDN) as provided by European public telecommunications operators at the "b service entry point" (as defined inEN 301 060-1 [2]) by means of the DSS1 protocol.The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for the ISDNDSS1 generic functional protocol for VPN applications as specified in EN 301 061-1 [4] in compliance with therelevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [6].The supplier of a protocol implementation which is claimed to conform to EN 301 061-1 [4] is required to complete acopy of the PICS proforma provided in annex A of the present document and is required to provide the informationnecessary to identify both the supplier and the implementation.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 403-3: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Signalling network layer for the circuit-mode basic call control; Part 3:Protocol Implementation Conformance Statement (PICS) proforma specification".[2]EN 301 060-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Basic call applications; Enhancement at the "b" service entry point forVirtual Private Network (VPN) applications; Part 1: Protocol specification".[3]EN 301 060-2: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Basic call applications; Enhancement at the "b" service entry point forVirtual Private Network (VPN) applications; Part 2: Protocol Implementation ConformanceStatement (PICS) proforma specification".[4]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".[5]ISO/IEC 9646-1 (1994): "Information technology; Open systems interconnection; Conformancetesting methodology and framework; Part 1: General concepts".[6]ISO/IEC 9646-7 (1995): "Information technology; Open systems interconnection; Conformancetesting methodology and framework; Part 7: Implementation Conformance Statements".[7]ISO/IEC 15056 (1997): "Information technology; Telecommunications and information exchangebetween systems; Private Integrate Service Network; Inter-exchange signalling protocol; Transitcounter additional network feature".SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)73DefinitionsFor the purposes of the present document, the following definitions apply, in addition to those given inEN 301 061-1 [4]:Protocol Implementation Conformance Statement (PICS): A statement made by the supplier of an OSIimplementation or system, stating which capabilities have been implemented for a given OSI protocol(see ISO/IEC 9646-1 [5]).PICS proforma: A document, in the form of a questionnaire, designed by the protocol specifier or conformance testsuite specifier, which, when completed for an OSI implementation or system becomes the PICS(see ISO/IEC 9646-1 [5]).static conformance review: A review of the extent to which the static conformance requirements are met by theImplementation Under Test (IUT), accomplished by comparing the PICS with the static conformance requirementsexpressed in the relevant standard(s) (see ISO/IEC 9646-1 [5]).4AbbreviationsFor the purposes of the present document, the abbreviations given in EN 301 061-1 [4] and the following apply:ANDBoolean "and"CConditional requirement (to be observed if the relevant conditions apply)DSS1Digital Subscriber Signalling System No. oneIERInformation Elements ReceivedIETInformation Elements TransmittedISDNIntegrated Services Digital NetworkIUTImplementation Under TestMMandatory requirement (to be observed in all cases)MCMajor CapabilitiesN/ANot applicable, not supported or the conditions for status are not metNonot supportedNOTBoolean "not"OOption (may be selected to suit the implementation, provided that any requirements applicable tothe option are observed)O.nOptions, but support required for either at least one or only one of the options in the group labelledwith the same numeral "n"ORBoolean "or"OSIOpen Systems InterconnectionPParametersPICSProtocol Implementation Conformance StatementRRoleSCSubsidiary CapabilitiesSCSSystem Conformance StatementSUTSystem Under TestVPNVirtual Private NetworkYessupportedSIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)85ConformanceA PICS proforma which conforms to this PICS proforma specification shall be technically equivalent to annex A, andshall preserve the numbering and ordering of the items in annex A.A PICS which conforms to this PICS proforma specification shall:a)describe an implementation which claims to conform to EN 301 061-1 [4];b)be a conforming ICS proforma which has been completed in accordance with the instructions for completiongiven in annex A, clause A.1;c)include the information necessary to uniquely identify both the supplier and the implementation.SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)9Annex A (normative):PICS proformaNotwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that usersof the present document may freely reproduce the PICS proforma in this annex so that it can be used for its intendedpurposes and may further publish the completed PICS.A.1Instructions for completing the PICS proformaA.1.1Identification of the implementationIdentification of the IUT and the system in which it resides (the System Under Test (SUT)) should be filled in so as toprovide as much detail as possible regarding version numbers and configuration options.The product supplier information and client information should both be filled in if they are different.A person who can answer queries regarding information supplied in the PICS should be named as the contact person.The System Conformance Statement (SCS) as defined in ISO/IEC 9646-1 [5] is a document supplied by the client orproduct supplier that summarizes which OSI International Standards, ITU-T (CCITT) Recommendations, ENs or otherstandards are implemented and to which conformance is claimed. The PICS/SCS subclause should describe therelationship of the PICS to the SCS.A.1.2Global statement of conformanceIf the answer to the statement in this subclause is "Yes", all subsequent subclauses should be completed to facilitateselection of test cases for optional functions.If the answer to the statement in this subclause is "No", all subsequent subclauses should be completed, and allnon-supported mandatory capabilities should be identified and explained. Explanations may be entered in the commentsfield at the bottom of each table or on attached sheets of paper.A.1.3Explanation of PICS proforma subclausesThe PICS proforma contains a Roles clause and thereafter is presented in two parts (for user and network) with thefollowing subclauses, as required:-major capabilities;-subsidiary capabilities;-protocol data unit support;-protocol data unit parameters;-timers;-call states.The User clause shall only be completed for user implementations (including private network implementations) whilethe Network clause shall only be completed for network implementations. The Roles subclause shall be completed forall implementations.The relationship between this PICS proforma and other related PICS proforma (e.g. the basic call PICS proforma) isexpressed in the requirements list contained in annex B. This provides the additional restrictions placed on the relatedproforma (different conditions, different status, etc.).SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)10A.1.4Symbols, abbreviations and termsThe PICS proforma contained in this annex is comprised of information in tabular form in accordance with theguidelines presented in ISO/IEC 9646-7 [6].The reference column contained in the tables gives reference to the appropriate part(s) of EN 301 061-1 [4] describingthe particular item. Note, however, that a reference merely indicates the place where the core of a description of an itemcan be found. Any additional information contained in EN 301 061-1 [4] has to be taken into account when making astatement about the conformance of that particular item.The following common notations, defined in ISO/IEC 9646-7 [6] are used for the status column:Mmandatory;Ooptional;N/Anot applicable;O.for mutually exclusive or selectable options from a set.The following common notations, defined in ISO/IEC 9646-7 [6] are used for the support column:Yfor supported / implemented;Nfor not supported / not implemented.A.2Identification of the implementationA.2.1Date of the statement.A.2.2Implementation Under Test (IUT) identificationIUT name:.IUT version:.A.2.3System Under Test (SUT) identificationSUT name:.Hardware configuration:.SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)11Operating system:.A.2.4Product supplierName:.Address:.Telephone number:.Facsimile number:.Additional information:.A.2.5ClientName:.Address:.Telephone number:.Facsimile number:.Additional information:.SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)12A.2.6PICS contact personName:.Address:.Telephone number:.Facsimile number:.Additional information:.A.3PICS / System Conformance Statement (SCS)Provide the relationship of the PICS with the SCS for the system:.A.4Identification of the protocolThis PICS proforma applies to the following standard:EN 301 061-1 (V1.2): "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 forVirtual Private Network (VPN) applications; Part 1: Protocol specification".A.5Global statement of conformanceThe implementation described in this PICS meets all the mandatory requirements of the referenced standard?[
] Yes[
] NoSIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)13NOTE:Answering "No" to this question indicates non-conformance to the protocol specification. Non-supportedmandatory capabilities are to be identified in the PICS, with an explanation of why the implementation isnon-conforming. Explanations may be entered in the comments field at the bottom of each table or onattached pages.In the tabulations which follow, all references are to EN 301 061-1 [4] unless another numbered reference is explicitlyindicated.A.6RolesTable A.1: RolesItemMajor role:Does the implementation.Conditions forstatusStatusReferenceSupportType of implementationR 1not usedR 2.1support user requirements?O.11.9, 1.10[ ]Yes [ ]NoR 2.2support network requirements?O.11.9, 1.10[ ]Yes [ ]NoR 3not usedR 4not usedR 5not usedO.1Support of one and only one of these options is required.Comments:A.7UserThe tables provided in this clause need only to be completed for user implementations, where item R 2.1 in table A.1 issupported.SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)14A.7.1Major capabilitiesTable A.2: Major capabilities - userItemMajor capability:Does the implementation support.Conditions forstatusStatusReferenceSupportMCu 1the functional protocol (common informationelement category) for the control ofsupplementary services?O.27[ ]Yes [ ]NoMCu 1.1the bearer related transport mechanism?MCu 1NOT MCu 1O.3N/A7.2.1.1[ ]Yes [ ]No[ ] N/AMCu 1.1.1Protocol control requirements?MCu 1.1NOT MCu 1.1MN/A7.2.1.1.1[ ]Yes [ ]No[ ] N/AMCu 1.1.2the termination of the GFT-Control protocol?MCu 1.1NOT MCu 1.1ON/A7.2.1.1.2[ ]Yes [ ]No[ ] N/AMCu 1.2the connection-oriented bearer independenttransport mechanism?MCu 1NOT MCu 1O.3N/A7.2.1.2[ ]Yes [ ]No[ ] N/AMCu 1.2.1Protocol control requirements?MCu 1.2NOT MCu 1.2MN/A7.2.1.2.1[ ]Yes [ ]No[ ] N/AMCu 1.2.2the termination of the GFT-Control protocol?MCu 1.2NOT MCu 1.2ON/A7.2.1.2.2[ ]Yes [ ]No[ ] N/AMCu 2generic notification procedures?O.28[ ]Yes [ ]NoMCu 2.1Protocol control requirements?MCu 2NOT MCu 2MN/A8.1.3[ ]Yes [ ]No[ ] N/AMCu 2.2the termination of the GFT-Control protocol?MCu 2NOT MCu 2ON/A8.1.4[ ]Yes [ ]No[ ] N/AMCu 3Application layer requirements?MCu 1.1.2 ORMCu 1.2.2 ORMCu 2.2NOT (MCu 1.1.2ORMCu 1.2.2 ORMCu 2.2)MN/A9[ ]Yes [ ]No[ ] N/AMCu 4Flow control?N/AAnnex CN/AMCu 5the co-existence of the public networkcontext and the VPN context on the sameaccess?O1[ ]Yes [ ]NoMCu 6the transit counter additional networkfeature?O[8][ ]Yes [ ]NoO.2O.3Support of at least one of these options is required.Support of at least one of these options is required.Comments:SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)15A.7.2Subsidiary capabilitiesTable A.3: Subsidiary capabilities - userItemSubsidiary capability:Does the implementation support.Conditions forstatusStatusReferenceSupportSCu 1Notification proceduresSCu 1.1the transport of integer coded notificationinformation in octet 3 of the Notificationindicator information element?MCu 2NOT MCu 2ON/A8.1[ ]Yes [ ]No[ ] N/ASCu 1.2the transport of ASN.1 notificationinformation in octet 4 of the Notificationindicator information element, using thecodepoint 'Discriminator for BER encodednotification extension' in octet 3?MCu 2NOT MCu 2ON/A8.1[ ]Yes [ ]No[ ] N/ASCu 1.3the transport of ASN.1 notificationinformation in octet 4 of the Notificationindicator information element, using thecodepoint 'discriminator for extension to ISOdefined ASN.1 encoded notification structure'in octet 3?MCu 2NOT MCu 2ON/A8.1[ ]Yes [ ]No[ ] N/ASCu 1.4the generation of notification information?MCu 2NOT MCu 2ON/A7.4.3.1[ ]Yes [ ]No[ ] N/ASCu 1.5the actions at a transit PINX regardingnotifications?MCu 2NOT MCu 2MN/A7.4.3.2[ ]Yes [ ]No[ ] N/ASCu 1.5the actions at a receiving end PINXregarding notifications?MCu 2NOT MCu 2MN/A7.4.3.3[ ]Yes [ ]No[ ] N/ASCu 2Control of supplementary services using the common information element approachSCu 2.1the generation of APDUs (as a sourcePINX)?MCu 1.1.2NOT MCu 1.1.2ON/A7.1.2.1[ ]Yes [ ]No[ ] N/ASCu 2.2the actions at a receiving PINX regarding theFacility information element?MCu 1.1.2NOT MCu 1.1.2MN/A7.1.2.2[ ]Yes [ ]No[ ] N/AComments:A.7.3Protocol data units for the bearer-related transportmechanism (VPN context)Table A.4: Messages received (VPN context) - userItemMessage (VPN context):Does the implementation support theinterpretation of .Conditions forstatusStatusReferenceSupportMRu 26FACILITY?MCu 1.1NOT MCu 1.1MN/A11.1[ ]Yes [ ]No[ ] N/AComments:SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)16Table A.5: Messages transmitted (VPN context) - userItemMessage (VPN context):Does the implementation support theinclusion of .Conditions forstatusStatusReferenceSupportMTu 26FACILITY?MCu 1.1NOT MCu 1.1ON/A11.1[ ]Yes [ ]No[ ] N/AComments:A.7.4Protocol data units for the connection-oriented bearerindependent transport mechanism (VPN context)Table A.6: Messages received (VPN context) - userItemMessage (VPN context):Does the implementation support theinterpretation of .Conditions forstatusStatusReferenceSupportMRu 1FACILITY?MCu 1NOT MCu 1MN/A11.1[ ]Yes [ ]No[ ] N/AMRu 2CALL PROCEEDING?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMRu 3CONNECT?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMRu 4CONNECT ACKNOWLEDGE?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMRu 5RELEASE?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMRu 6RELEASE COMPLETE?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMRu 7SETUP?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AComments:SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)17Table A.7: Messages transmitted (VPN context) - userItemMessage (VPN context):Does the implementation support theinclusion of .Conditions forstatusStatusReferenceSupportMTu 1FACILITY?MCu 1NOT MCu 1ON/A11.1[ ]Yes [ ]No[ ] N/AMTu 2CALL PROCEEDING?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMTu 3CONNECT?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMTu 4CONNECT ACKNOWLEDGE?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMTu 5RELEASE?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMTu 6RELEASE COMPLETE?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AMTu 7SETUP?MCu 1.2NOT MCu 1.2MN/A11.1[ ]Yes [ ]No[ ] N/AComments:A.7.5Protocol data unit parameters for the bearer-relatedtransport mechanism (VPN context)A.7.5.1Protocol data unit parameters receivedTable A.8: FACILITY PDU parameters received by the userItemFACILITY PDU parameters (VPN context):Does the implementation support theinformation element.Conditions forstatusStatusReferenceSupportIERu 26.1Protocol discriminator?MRu 26NOT MRu 26MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 26.2Call reference?MRu 26NOT MRu 26MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 26.3Message type?MRu 26NOT MRu 26MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 26.4Facility?MRu 26NOT MRu 26MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 26.5Notification indicator?MRu 26 ANDMCu 2NOT (MRu 26AND MCu2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)18Table A.9: ALERTING PDU parameters received by the userItemALERTING PDU parameters (VPNcontext): Does the implementationsupport the information element.Conditions forstatusStatusReferenceSupportIERu 1.1Facility?[1] MRu 1NOT [1] MRu 1MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 1.2Notification indicator?[1] MRu 1 ANDMCu 2NOT ([1] MRu 1AND MCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:Table A.10: CALL PROCEEDING PDU parameters received by the userItemCALL PROCEEDING PDU parameters(VPN context): Does the implementationsupport the information element.Conditions forstatusStatusReferenceSupportIERu 2.1Facility?[1] MRu 2NOT [1] MRu 2MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 2.2Notification indicator?[1] MRu 2 ANDMCu 2NOT ([1] MRu 2AND MCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:Table A.11: CONNECT PDU parameters received by the userItemCONNECT PDU parameters (VPNcontext): Does the implementationsupport the information element.Conditions forstatusStatusReferenceSupportIERu 4.1Facility?[1] MRu 4NOT [1] MRu 4MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 4.2Notification indicator?[1] MRu 4 ANDMCu 2NOT ([1] MRu 4AND MCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)19Table A.12: CONNECT ACKNOWLDEGE PDU parameters received by the userItemCONNECT ACKNOWLEDGE PDUparameters (VPN context): Does theimplementation support the informationelement.Conditions forstatusStatusReferenceSupportIERu 5.1Facility?[1] MRu 5NOT [1] MRu 5MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 5.2Notification indicator?[1] MRu 5 ANDMCu 2NOT ([1] MRu 5AND MCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:Table A.13: DISCONNECT PDU parameters received by the userItemDISCONNECT PDU parameters (VPNcontext): Does the implementationsupport the information element.Conditions forstatusStatusReferenceSupportIERu 6.1Facility?[1] MRu 6NOT [1] MRu 6MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 6.2Notification indicator?[1] MRu 6 ANDMCu 2NOT ([1] MRu 6AND MCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:Table A.14: INFORMATION PDU parameters received by the userItemINFORMATION PDU parameters (VPNcontext): Does the implementationsupport the information element.Conditions forstatusStatusReferenceSupportIERu 8.1Facility?[1] MRu 8NOT [1] MRu 8MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 8.2Notification indicator?[1] MRu 8 ANDMCu 2NOT ([1] MRu 8AND MCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)20Table A.15: PROGRESS PDU parameters received by the userItemPROGRESS PDU parameters (VPNcontext): Does the implementationsupport the information element.Conditions forstatusStatusReferenceSupportIERu 10.1Facility?[1] MRu 10NOT [1] MRu 10MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 10.2Notification indicator?[1] MRu 10 ANDMCu 2NOT ([1]MRu 10 ANDMCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:Table A.16: RELEASE PDU parameters received by the userItemRELEASE PDU parameters (VPN context):Does the implementation support theinformation element.Conditions forstatusStatusReferenceSupportIERu 11.1Facility?[1] MRu 11NOT [1] MRu 11MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 11.2Notification indicator?[1] MRu 11 ANDMCu 2NOT ([1]MRu 11 ANDMCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:Table A.17: RELEASE COMPLETE PDU parameters received by the userItemRELEASE COMPLETE PDU parameters(VPN context): Does the implementationsupport the information element .Conditions forstatusStatusReferenceSupportIERu 12.1Facility?[1] MRu 12NOT [1] MRu 12MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 12.2Notification indicator?[1] MRu 12 ANDMCu 2NOT ([1]MRu 12 ANDMCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)21Table A.18: SETUP PDU parameters received by the userItemSETUP PDU parameters (VPN context):Does the implementation support theinformation element.Conditions forstatusStatusReferenceSupportIERu 19.1Facility?[1] MRu 19NOT [1] MRu 19MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 19.2Notification indicator?[1] MRu 19 ANDMCu 2NOT ([1]MRu 19 ANDMCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:Table A.19: SETUP ACKNOWLEDGE PDU parameters received by the userItemSETUP ACKNOWLEDGE PDU parameters(VPN context): Does the implementationsupport the information element.Conditions forstatusStatusReferenceSupportIERu 20.1Facility?[1] MRu 20NOT [1] MRu 20MN/A11.1[ ]Yes [ ]No[ ] N/AIERu 20.2Notification indicator?[1] MRu 20 ANDMCu 2NOT ([1]MRu 20 ANDMCu 2)MN/A11.1[ ]Yes [ ]No[ ] N/AComments:SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)22Table A.20: Facility Information element contents received by the userItemDoes the implementation support theinformation element field and valuesConditions forstatusStatusReferenceSupportIERu 1.4.1Network Facility Extension (octet 3.1)MCu 1 ANDMCu 1.1.2MCu 1 AND(NOTMCu 1.1.2)NOT MCu 1MM (note)N/A11.2.1[ ]Yes [ ]No[ ]Yes [ ]No[ ]N/AIERu 1.4.2Network Protocol Profile (octet 3.2)MCu 1 ANDMCu 3MCu 1 AND(NOT MCu 3)NOT MCu 1MM (note)N/A11.2.1[ ]Yes [ ]No[ ]Yes [ ]No[ ]N/AIERu 1.4.3Interpretation Component (octet 3.3)MCu 1 ANDMCu 3MCu 1 AND(NOT MCu3)NOT MCu 1MM (note)N/A11.2.1[ ]Yes [ ]No[ ]Yes [ ]No[ ]N/ANOTE:The support of this field implies the ability to pass this field transparently to the next entity.Comments:A.7.5.2Protocol data unit parameters transmittedTable A.21: FACILITY PDU parameters transmitted by the userItemFACILITY PDU parameters (VPN context):Does the implementation support theinformation element.Conditions forstatusStatusReferenceSupportIETu 26.1Protocol discriminator?MTu 26NOT MTu 26MN/A11.1[ ]Yes [ ]No[ ] N/AIETu 26.2Call reference?MTu 26NOT MTu 26MN/A11.1[ ]Yes [ ]No[ ] N/AIETu 26.3Message type?MTu 26NOT MTu 26MN/A11.1[ ]Yes [ ]No[ ] N/AIETu 26.4Facility?MTu 26NOT MTu 26MN/A11.1[ ]Yes [ ]No[ ] N/AIETu 26.5Notification indicator?MTu 26 ANDMCu 2NOT (MTu 26AND MCu2)ON/A11.1[ ]Yes [ ]No[ ] N/AComments:SIST EN 301 061-2:2001
ETSIEN 301 061-2 V1.1.3 (1998-10)23Table A.22: ALERTING PDU parameters transmitted by the userItemCALL PROCEEDING PDU parameters(VPN context): Does the implementationsupport the information element.Conditions forstatusStatusReferenceSupportIETu 1.1Facility?[1] MTu 1NOT [1] MTu 1ON/A11.1[ ]Yes [ ]No[ ] N/AIETu 1.2Notification indicator?[1] MTu 1 ANDMCu 2NOT ([1] MTu 1AND MCu 2)ON/A11.1[ ]Yes [ ]No[ ] N/AComments:Table A.23: CALL PROCEEDING PDU parameters transmitted by the userItemCALL PROCEEDING PDU parameters(VPN context): Does the implementationsupport the information element.Conditions forstatusStatusReferenceSupportIETu 2.1Facility?[1] MTu 2NOT [1] MTu 2ON/A11.1[ ]Yes [ ]No[ ] N/AIETu 2.2Notification indicator?[1] MTu 2 ANDMCu 2NOT ([1] MTu 2AND MCu 2)ON/A11.1[
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...