ETSI ETS 300 196-2 ed.1 (1996-06)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.RIRUPQDVSHFLILNDFLMDIntegrated Services Digital Network (ISDN); Generic functional protocol for the support of supplementary services; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:ETS 300 196-2 Edition 1PSIST ETS 300 196-2:1996en01-oktober-1996PSIST ETS 300 196-2:1996SLOVENSKI
STANDARD
PSIST ETS 300 196-2:1996
EUROPEANETS 300 196-2TELECOMMUNICATIONJune 1996STANDARDSource: ETSI TC-SPSReference: DE/SPS-05039ICS:33.080Key words:ISDN, supplementary service, PICSIntegrated Services Digital Network (ISDN);Generic functional protocol for the support ofsupplementary services;Digital Subscriber Signalling System No. one (DSS1) protocol;Part 2: Protocol Implementation Conformance Statement (PICS)proforma specificationETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1996. All rights reserved.PSIST ETS 300 196-2:1996*

Page 2ETS 300 196-2: June 1996Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.PSIST ETS 300 196-2:1996

Page 3ETS 300 196-2: June 1996ContentsForeword.51Scope.72Normative references.73Definitions.84Abbreviations.85Conformance.9Annex A (normative):PICS proforma.10A.1Instructions for completing the PICS proforma.10A.1.1Identification of the implementation.10A.1.2Global statement of conformance.10A.1.3Explanation of PICS proforma subclauses.10A.1.4Symbols, abbreviations and terms.11A.2Identification of the implementation.11A.2.1Implementation Under Test (IUT) identification.11A.2.2System Under Test (SUT) identification.11A.2.3Product supplier.12A.2.4Client.12A.2.5PICS contact person.13A.3PICS/System Conformance Statement (SCS).13A.4Identification of the protocol.13A.5Global statement of conformance.14A.6Roles.14A.7User.15A.7.1Major capabilities.15A.7.2Subsidiary capabilities.16A.7.3Protocol data units.17A.7.4Protocol data unit parameters.18A.7.4.1Protocol data unit parameters received.18A.7.4.2Protocol data unit parameters transmitted.27A.7.5Timers.35A.7.6Call states.36A.8Network.37A.8.1Major capabilities.37A.8.2Subsidiary capabilities.38A.8.3Protocol data units.39A.8.4Protocol data unit parameters.40A.8.4.1Protocol data unit parameters received.40A.8.4.2Protocol data unit parameters transmitted.48A.8.5Timers.57A.8.6Call states.58PSIST ETS 300 196-2:1996

Page 4ETS 300 196-2: June 1996Annex B (normative):Requirements list.59B.1User.59B.2Network.60History.61PSIST ETS 300 196-2:1996

Page 5ETS 300 196-2: June 1996ForewordThis European Telecommunication Standard (ETS) has been produced by the Signalling Protocols andSwitching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).This ETS is part 2 of a multi-part standard covering the Digital Subscriber Signalling System No. one(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) generic functionalprotocol for the support of supplementary services, as described below:Part 1:"Protocol specification";Part 2:"Protocol Implementation Conformance Statement (PICS) proforma specification";Part 3:"Test Suite Structure and Test Purposes (TSS&TP) specification for the user";Part 4:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing(PIXIT) proforma specification for the user";Part 5:"TSS&TP specification for the network";Part 6:"ATS and partial PIXIT proforma specification for the network".To evaluate conformance of a particular implementation, it is necessary to have a statement of whichcapabilities and options have been implemented for a given Open Systems Interconnection (OSI)protocol. Such a statement is called a Protocol Implementation Conformance Statement (PICS).Transposition datesDate of adoption of this ETS:14 June 1996Date of latest announcement of this ETS (doa):30 September 1996Date of latest publication of new National Standardor endorsement of this ETS (dop/e):31 March 1997Date of withdrawal of any conflicting National Standard (dow):31 March 1997PSIST ETS 300 196-2:1996

Page 6ETS 300 196-2: June 1996Blank pagePSIST ETS 300 196-2:1996

Page 7ETS 300 196-2: June 19961ScopeThis second part of ETS 300 196 is applicable to the generic functional protocol for the support ofsupplementary services for the pan-European Integrated Services Digital Network (ISDN) as provided byEuropean public telecommunications operators at the T reference point or coincident S and T referencepoint (as defined in ITU-T Recommendation I.411 [10]) by means of the Digital Subscriber SignallingSystem No. one (DSS1) protocol.This ETS provides the Protocol Implementation Conformance Statement (PICS) proforma for the ISDNDSS1 generic functional protocol for the support of supplementary services as specified inETS 300 196-1 [2] in compliance with the relevant requirements and in accordance with the relevantguidance given in ISO/IEC 9646-7 [8].The supplier of a protocol implementation which is claimed to conform to ETS 300 196-1 [2] is required tocomplete a copy of the PICS proforma provided in annex A of this ETS and is required to provide theinformation necessary to identify both the supplier and the implementation.2Normative referencesThis ETS incorporates by dated and undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this ETS only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to applies.[1]ETS 300 102-1: "Integrated Services Digital Network (ISDN); User-networkinterface layer 3; Specifications for basic call control".[2]ETS 300 196-1 (1993): "Integrated Services Digital Network (ISDN); Genericfunctional protocol for the support of supplementary services; Digital SubscriberSignalling System No. one (DSS1) protocol; Part 1: Protocol specification".[3]I-ETS 300 314: "Integrated Services Digital Network (ISDN); Digital SubscriberSignalling System No. one (DSS1); Protocol Implementation ConformanceStatement (PICS) proforma specification for the network layer signalling protocolfor circuit-mode basic call control (basic access, user)".[4]I-ETS 300 315: "Integrated Services Digital Network (ISDN); Digital SubscriberSignalling System No. one (DSS1); Protocol Implementation ConformanceStatement (PICS) proforma specification for the network layer signalling protocolfor circuit-mode basic call control (primary rate access, user)".[5]I-ETS 300 316: "Integrated Services Digital Network (ISDN); Digital SubscriberSignalling System No. one (DSS1); Protocol Implementation ConformanceStatement (PICS) proforma specification for the network layer signalling protocolfor circuit-mode basic call control (basic access, network)".[6]I-ETS 300 317: "Integrated Services Digital Network (ISDN); Digital SubscriberSignalling System No. one (DSS1); Protocol Implementation ConformanceStatement (PICS) proforma specification for the network layer signalling protocolfor circuit-mode basic call control (primary rate access, network)".[7]ISO/IEC 9646-1: "Information technology - Open systems interconnection -Conformance testing methodology and framework - Part 1: General concepts".[8]ISO/IEC 9646-7: "Information technology - Open systems interconnection -Conformance testing methodology and framework - Part 7: ImplementationConformance Statements".[9]CCITT Recommendation I.330 (1988): "ISDN numbering and addressingprinciples".PSIST ETS 300 196-2:1996

Page 8ETS 300 196-2: June 1996[10]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -referenceconfigurations".3DefinitionsFor the purposes of this ETS, the following definitions apply, in addition to those given inETS 300 196-1 [2]:Protocol Implementation Conformance Statement (PICS): A statement made by the supplier of anOpen Systems Interconnection (OSI) implementation or system, stating which capabilities have beenimplemented for a given OSI protocol (see ISO/IEC 9646-1 [7]).PICS proforma: A document, in the form of a questionnaire, designed by the protocol specifier orconformance test suite specifier, which, when completed for an OSI implementation or system becomesthe PICS (see ISO/IEC 9646-1 [7]).static conformance review: A review of the extent to which the static conformance requirements are metby the IUT, accomplished by comparing the PICS with the static conformance requirements expressed inthe relevant standard(s) (see ISO/IEC 9646-1 [7]).subaddress: See CCITT Recommendation I.330 [9], subclause 5.4.4AbbreviationsFor the purposes of this ETS, the following abbreviations apply:ANDBoolean "and'"ASAuxiliary StatesCConditional requirement (to be observed if the relevant conditions apply)DSS1Digital Subscriber Signalling System No. oneGFPGeneric Functional ProtocolIERInformation Elements ReceivedIETInformation Elements TransmittedISDNIntegrated Services Digital NetworkIUTImplementation Under TestMMandatory requirement (to be observed in all cases)MCMajor CapabilitiesMRMessages ReceivedMTMessages TransmittedN/ANot applicable, not supported or the conditions for status are not metNonot supportedNOTBoolean "not"OOption (may be selected to suit the implementation, provided that anyrequirements applicable to the option are observed)O.nOptions, but support required for either at least one or only one of the options inthe group labelled with the same numeral "n"ORBoolean "or"OSIOpen Systems InterconnectionPICSProtocol Implementation Conformance StatementRRoleRLRequirements ListSCSubsidiary CapabilitiesSCSSystem Conformance StatementSUTSystem Under TestTMPrefix for index numbers for the timers groupYessupportedPSIST ETS 300 196-2:1996

Page 9ETS 300 196-2: June 19965ConformanceA PICS proforma which conforms to this PICS proforma specification shall be technically equivalent toannex A, and shall 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 ETS 300 196-1 [2];b)be a conforming ICS proforma which has been completed in accordance with the instructions forcompletion given in clause A.1;c)include the information necessary to uniquely identify both the supplier and the implementation.PSIST ETS 300 196-2:1996

Page 10ETS 300 196-2: June 1996Annex A (normative):PICS proformaNotwithstanding the provisions of the copyright clause related to the text of this ETS, ETSI grants thatusers of this ETS may freely reproduce the PICS proforma in this annex so that it can be used for itsintended purposes and may further publish the completed PICS.A.1Instructions for completing the PICS proformaA.1.1Identification of the implementationIdentification of the Implementation Under Test (IUT) and the system in which it resides (the SystemUnder Test (SUT)) should be filled in so as to provide as much detail as possible regarding versionnumbers 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 thecontact person.The SCS as defined in ISO/IEC 9646-1 [7] is a document supplied by the client or product supplier thatsummarizes which OSI International Standards, ITU-T (CCITT) Recommendations, ETSs or otherstandards are implemented and to which conformance is claimed. The PICS/SCS subclause shoulddescribe the relationship 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 completedto facilitate selection of test cases for optional functions.If the answer to the statement in this subclause is "No", all subsequent subclauses should be completed,and all non-supported mandatory capabilities should be identified and explained. Explanations may beentered in the comments field 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 andnetwork) with the following 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 networkimplementations) while the Network clause shall only be completed for network implementations. TheRoles subclause shall be completed for all implementations.The relationship between this PICS proforma and other related PICS proforma (e.g. the basic call PICSproforma) is expressed in the Requirements List (RL) contained in annex B. This provides the additionalrestrictions placed on the related proforma (different conditions, different status, etc.).PSIST ETS 300 196-2:1996

Page 11ETS 300 196-2: June 1996A.1.4Symbols, abbreviations and termsThe PICS proforma contained in this annex is comprised of information in tabular form in accordance withthe guidelines presented in ISO/IEC 9646-7 [8].The reference column contained in the tables gives reference to the appropriate part(s) ofETS 300 196-1 [2] describing the particular item. Note, however, that a reference merely indicates theplace the core of a description of an item can be found. Any additional information contained inETS 300 196-1 [2] has to be taken into account when making a statement about the conformance of thatparticular item.The following common notations, defined in ISO/IEC 9646-7 [8], are used for the status column:MmandatoryOoptionalN/Anot applicableO.for mutually exclusive or selectable options from a setThe following common notations, defined in ISO/IEC 9646-7 [8], are used for the support column:Yfor supported/implementedNfor not supported/not implementedA.2Identification of the implementationA.2.1Implementation Under Test (IUT) identificationIUT name:.IUT version:.A.2.2System Under Test (SUT) identificationSUT name:.Hardware configuration:.Operating system:.PSIST ETS 300 196-2:1996

Page 12ETS 300 196-2: June 1996A.2.3Product supplierName:.Address:.Telephone number:.Facsimile number:.Additional information:.A.2.4ClientName:.Address:.Telephone number:.Facsimile number:.Additional information:.PSIST ETS 300 196-2:1996

Page 13ETS 300 196-2: June 1996A.2.5PICS 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 standards:ETS 300 196-1 (1993): "Integrated Services Digital Network (ISDN); Generic functional protocol for thesupport of supplementary services; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 1:Protocol specification".NOTE:ETS 300 196-1 (1993) was initially published as ETS 300 196 (1993).PSIST ETS 300 196-2:1996

Page 14ETS 300 196-2: June 1996A.5Global statement of conformanceThe implementation described in this PICS meets all the mandatory requirements of the referencedstandard?[
] Yes[
] NoNOTE:Answering "No" to this question indicates non-conformance to the protocolspecification. Non-supported mandatory capabilities are to be identified in the PICS,with an explanation of why the implementation is non-conforming. Explanations maybe entered in the comments field at the bottom of each table or on attached sheets ofpaper.In the tabulations which follow, all references are to ETS 300 196-1 [2] unless another numberedreference is explicitly indicated.A.6RolesTable A.1: Type of implementationItemMajor role:Does the implementation.Conditions forstatusStatusReferenceSupportType of implementationR 1not usedR 2.1support user requirements?O.17, 8, 9, 10[ ]Yes [ ]NoR 2.2support network requirements?O.17, 8, 9, 10[ ]Yes [ ]NoR 3not usedR 4not usedR 5.1support the functions of an initiating entity?O.27, 8, 9, 10[ ]Yes [ ]NoR 5.2support the functions of a responding entity?O.27, 8, 9, 10[ ]Yes [ ]NoO.1Support of one and only one of these options is required.O.2Support of at least one of these options is required.Comments:PSIST ETS 300 196-2:1996

Page 15ETS 300 196-2: June 1996A.7UserThe tables provided in this clause need only to be completed for user implementations, where item R 2.1in table A.1 is supported.A.7.1Major capabilitiesTable A.2: Major capabilities - userItemMajor capability:Does the implementation.Conditions forstatusStatusReferenceSupportMCu 1support the functional protocol (separate messagecategory) for the control of supplementaryservices?O.36.3, 7[ ]Yes [ ]NoMCu 2support the functional protocol (commoninformation element category) for the control ofsupplementary services?O.36.3, 8[ ]Yes [ ]NoMCu 2.1support bearer related supplementary servicesprocedure?MCu 2NOT MCu 2O.4N/A8.3.1[ ]Yes [ ]No[ ]N/AMCu 2.2support bearer independent supplementaryservices procedure?MCu 2NOT MCu 2O.4N/A8.3.2[ ]Yes [ ]No[ ]N/AMCu 2.3support point-to-point (bearer related) transportmechanism?MCu 2.1NOT MCu 2.1MN/A8.3.1, 8.3.1.1[ ]Yes [ ]No[ ]N/AMCu 2.4support broadcast (bearer related) transportmechanism?MCu 2.1NOT MCu 2.1ON/A8.3.1, 8.3.1.2[ ]Yes [ ]No[ ]N/AMCu 2.5support point-to-point (bearer independent)connection-oriented transport mechanism?MCu 2.2NOT MCu 2.2O.5N/A8.3.2, 8.3.2.1[ ]Yes [ ]No[ ]N/AMCu 2.6support point-to-point (bearer independent)connectionless transport mechanism?MCu 2.2NOT MCu 2.2O.5N/A8.3.2, 8.3.2.2[ ]Yes [ ]No[ ]N/AMCu 2.7support broadcast (bearer independent)connectionless transport mechanism?MCu 2.2NOT MCu 2.2O.5N/A8.3.2, 8.3.2.4[ ]Yes [ ]No[ ]N/AMCu 3support notification category procedures?O.39[ ]Yes [ ]NoMCu 3.1support transport of bearer-related notifications?MCu 3NOT MCu 3O.6N/A9.3[ ]Yes [ ]No[ ]N/AMCu 3.2support transport of bearer-independentnotifications?MCu 3NOT MCu 3O.6N/A9.4[ ]Yes [ ]No[ ]N/AMCu 4support the network-side channel reservation?O.310.1[ ]Yes [ ]No[ ]N/AMCu 4.1support implicit reservation?MCu 4NOT MCu 4O.7N/A10.1.1[ ]Yes [ ]No[ ]N/AMCu 4.2support explicit reservation?MCu 4NOT MCu 4O.7N/A10.1.2[ ]Yes [ ]No[ ]N/AMCu 5support generic procedures for the supplementaryservices management?O.310.2[ ]Yes [ ]NoMCu 5.1support activation?MCu 5 ANDMCu 2.6NOT (MCu 5 ANDMCu 2.6)O.8N/A10.2.2[ ]Yes [ ]No[ ]N/AMCu 5.2support deactivation?MCu 5 ANDMCu 2.6NOT (MCu 5 ANDMCu 2.6)O.8N/A10.2.3[ ]Yes [ ]No[ ]N/AMCu 5.3support interrogation?MCu 5 ANDMCu 2.6NOT (MCu 5 ANDMCu 2.6)O.8N/A10.2.4[ ]Yes [ ]No[ ]N/AMCu 5.4support status notification? (note)MCu 5 ANDMCu 2.7NOT (MCu 5 ANDMCu 2.7)O.8N/A10.2.5[ ]Yes [ ]No[ ]N/A(continued)PSIST ETS 300 196-2:1996

Page 16ETS 300 196-2: June 1996Table A.2 (concluded): Major capabilities - userItemMajor capability:Does the implementation.Conditions forstatusStatusReferenceSupportMCu 6support generic status request procedure?MCu 2.6 ORMCu 2.7NOT (MCu 2.6 ORMCu 2.7)O.3N/A10.3[ ]Yes [ ]No[ ]N/AO.3Support of at least one of these options is required.O.4Support of at least one of these options is required.O.5Support of at least one of these options is required.O.6Support of at least one of these options is required.O.7Support of at least one of these options is required.O.8Support of at least one of these options is required.NOTE:This major capability can be supported even if neither MCu 5.1 nor MCu 5.2 are supported.Comments:A.7.2Subsidiary capabilitiesTable A.3: Subsidiary capabilities - userItemCapability:Does the implementation.Conditions forstatusStatusReferenceSupportSCu 1Separate message categorySCu 1.1support the Hold procedures?MCu 1NOT MCu 1MN/A7.1, 7.2[ ]Yes [ ]No[ ]N/ASCu 1.2support the Retrieve procedures?MCu 1NOT MCu 1MN/A7.1, 7.4[ ]Yes [ ]No[ ]N/ASCu 3Notification proceduresSCu 3.1support the transport of notification information insimple notification "indicators"?MCu 3NOT MCu 3O.10N/A9.2[ ]Yes [ ]No[ ]N/ASCu 3.2support the transport of notification information innotification "parameters"?MCu 3NOT MCu 3O.10N/A9.2[ ]Yes [ ]No[ ]N/ASCu 3.3support the transport of notification information innotification "indicators" and "parameters" using anextension codepoint in octet 3 of the Notificationindicator information element?MCu 3NOT MCu 3O.10N/A9.2[ ]Yes [ ]No[ ]N/ASCu 4ReservationSCu 4.1support interaction between explicit and implicitchannel reservation?MCu 4.1 ANDMCu 4.2NOT (MCu 4.1 ANDMCu 4.2)MN/A10.1.2.5[ ]Yes [ ]No[ ]N/AO.10Support of at least one of these options is required.Comments:PSIST ETS 300 196-2:1996

Page 17ETS 300 196-2: June 1996A.7.3Protocol data unitsTable A.4: Messages received - userItemMessage:Does the implementationsupport theinterpretation of.Conditions for statusStatusReferenceSupportMRu 1FACILITY?MCu 2NOT MCu 2MN/A8.3, 11.1.1.1,11.1.2.1, 11.1.3.1[ ]Yes [ ]No[ ]N/AMRu 2HOLD?SCu 1.1 AND R 5.2NOT (SCu 1.1 AND R 5.2)MN/A 7.2, 11.1.1.2[ ]Yes [ ]No[ ]N/AMRu 3HOLD ACKNOWLEDGE?SCu 1.1 AND R 5.1NOT (SCu 1.1 AND R 5.1)MN/A7.2, 11.1.1.3[ ]Yes [ ]No[ ]N/AMRu 4HOLD REJECT?SCu 1.1 AND R 5.1NOT (SCu 1.1 AND R 5.1)MN/A7.2, 11.1.1.4[ ]Yes [ ]No[ ]N/AMRu 5REGISTER?MCu 2.5 AND R 5.2NOT (MCu 2.5 AND R 5.2)MN/A8.3.2.1.1, 11.1.2.2[ ]Yes [ ]No[ ]N/AMRu 6RETRIEVE?SCu 1.2 AND R 5.2NOT (SCu 1.2 AND R 5.2)MN/A7.4, 11.1.1.5[ ]Yes [ ]No[ ]N/AMRu 7RETRIEVEACKNOWLEDGE?SCu 1.2 AND R 5.1NOT (SCu 1.2 AND R 5.1)MN/A7.4, 11.1.1.6[ ]Yes [ ]No[ ]N/AMRu 8RETRIEVE REJECT?SCu 1.2 AND R 5.1NOT (SCu 1.2 AND R 5.1)MN/A7.4, 11.1.1.7[ ]Yes [ ]No[ ]N/AComments:Table A.5: Messages transmitted - userItemMessage:Does the implementationsupport the inclusionof.Conditions for statusStatusReferenceSupportMTu 1FACILITY?MCu 2.6(NOT MCu 2.6) AND MCu 2NOT MCu 2MON/A8.3, 11.1.1.1,11.1.2.1, 11.1.3.1[ ]Yes [ ]No[ ]N/AMTu 2HOLD?SCu 1.1 AND R 5.1NOT (SCu 1.1 AND R 5.1)MN/A7.2, 11.1.1.2[ ]Yes [ ]No[ ]N/AMTu 3HOLD ACKNOWLEDGE?SCu 1.1 AND R 5.2NOT (SCu 1.1 AND R 5.2)MN/A7.2, 11.1.1.3[ ]Yes [ ]No[ ]N/AMTu 4HOLD REJECT?SCu 1.1 AND R 5.2NOT (SCu 1.1 AND R 5.2)MN/A7.2, 11.1.1.4[ ]Yes [ ]No[ ]N/AMTu 5REGISTER?MCu 2.5 AND R 5.1NOT (MCu 2.5 AND R 5.1)MN/A8.3.2.1.1, 11.1.2.2[ ]Yes [ ]No[ ]N/AMTu 6RETRIEVE?SCu 1.2 AND R 5.1NOT (SCu 1.2 AND R 5.1)MN/A7.4, 11.1.1.5[ ]Yes [ ]No[ ]N/AMTu 7RETRIEVEACKNOWLEDGE?SCu 1.2 AND R 5.2NOT (SCu 1.2 AND R 5.2)MN/A7.4, 11.1.1.6[ ]Yes [ ]No[ ]N/AMTu 8RETRIEVE REJECT?SCu 1.2 AND R 5.2NOT (SCu 1.2 AND R 5.2)MN/A7.4, 11.1.1.7[ ]Yes [ ]No[ ]N/AComments:PSIST ETS 300 196-2:1996

Page 18ETS 300 196-2: June 1996A.7.4Protocol data unit parametersA.7.4.1Protocol data unit parameters receivedTable A.6: FACILITY PDU parameters received - userItemFACILITY PDUparameters:Does the implementationsupport the .Conditions for statusStatusReferenceSupportIERu 1.1Protocol discriminator?MRu 1NOT MRu1MN/A[1] 4.2[ ]Yes [ ]No[ ]N/AIERu 1.2Call reference?MRu 1NOT MRu 1MN/A[1] 4.3[ ]Yes [ ]No[ ]N/AIERu 1.3Message type?MRu 1NOT MRu 1MN/A11.2.1[ ]Yes [ ]No[ ]N/AIERu 1.4Facility?MRu 1NOT MRu 1MN/A11.2.2.1[ ]Yes [ ]No[ ]N/AIERu 1.5Called party number?(note 1)MRu 1 AND (MCu 2.6 OR MCu 2.7)NOT (MRu 1 OR (MCu 2.6 OR MCu 2.7))ON/A[1] 4.5[ ]Yes [ ]No[ ]N/AIERu 1.6Called party subaddress?(note 2)MRu 1 AND (MCu 2.6 OR MCu 2.7)NOT (MRu 1 OR (MCu 2.6 OR MCu 2.7))ON/A[1] 4.5[ ]Yes [ ]No[ ]N/AIERu 1.7Notification indicator?MRu 1 AND MCu 3.1NOT (MRu 1 AND MCu 3.1)MN/A11.2.2.2[ ]Yes [ ]No[ ]N/AIERu 1.8Display?MRu 1NOT MRu 1MN/A[1] 4.5[ ]Yes [ ]No[ ]N/ANOTE 1:Only applicable in conjunction with the Multiple subscriber number supplementary service.NOTE 2:Only applicable in conjunction with the Subaddressing supplementary service.Comments:Table A.7: HOLD PDU parameters received - userItemHOLD PDU parameters:Does the implementationsupport the .Conditions for statusStatusReferenceSupportIERu 2.1Protocol discriminator?MRu 2NOT MRu 2MN/A[1] 4.2[ ]Yes [ ]No[ ]N/AIERu 2.2Call reference?MRu 2NOT MRu 2MN/A[1] 4.3[ ]Yes [ ]No[ ]N/AIERu 2.3Message type?MRu 2NOT MRu 2MN/A11.2.1[ ]Yes [ ]No[ ]N/AIERu 2.4Facility?MRu 2 AND MCu 2.1NOT (MRu 2 AND MCu 2.1)MN/A11.2.2.1[ ]Yes [ ]No[ ]N/AIERu 2.5Notification indicator?MRu 2 AND MCu 3.1NOT (MRu 2 AND MCu 3.1)MN/A11.2.2.2[ ]Yes [ ]No[ ]N/AIERu 2.6Display?MRu 2NOT MRu 2MN/A[1] 4.5[ ]Yes [ ]No[ ]N/AComments:PSIST ETS 300 196-2:1996

Page 19ETS 300 196-2: June 1996Table A.8: HOLD ACKNOWLEDGE PDU parameters received - userItemHOLD ACKNOWLEDGEPDU parameters:Does the implementationsupport the .Conditions for statusStatusReferenceSupportIERu 3.1Protocol discriminator?MRu 3NOT MRu 3MN/A[1] 4.2[ ]Yes [ ]No[ ]N/AIERu 3.2Call reference?MRu 3NOT MRu 3MN/A[1] 4.3[ ]Yes [ ]No[ ]N/AIERu 3.3Message type?MRu 3NOT MRu 3MN/A11.2.1[ ]Yes [ ]No[ ]N/AIERu 3.4Facility?MRu 3AND MCu 2.1NOT (MRu 3 AND MCu 2.1)MN/A11.2.2.1[ ]Yes [ ]No[ ]N/AIERu 3.5Notification indicator?MRu 3 AND MCu 3.1NOT (MRu 3 AND MCu 3.1)MN/A11.2.2.2[ ]Yes [ ]No[ ]N/AIERu 3.6Display?MRu 3NOT MRu 3MN/A[1] 4.5[ ]Yes [ ]No[ ]N/AComments:Table A.9: HOLD REJECT PDU parameters received - userItemHOLD REJECT PDUparameters:Does the implementationsupport the .Conditions for statusStatusReferenceSupportIERu 4.1Protocol discriminator?MRu 4NOT MRu 4MN/A[1] 4.2[ ]Yes [ ]No[ ]N/AIERu 4.2Call reference?MRu 4NOT MRu 4MN/A[1] 4.3[ ]Yes [ ]No[ ]N/AIERu 4.3Message type?MRu 4NOT MRu 4MN/A11.2.1[ ]Yes [ ]No[ ]N/AIERu 4.4Cause?MRu 4NOT MRu 4MN/A[1] 4.5[ ]Yes [ ]No[ ]N/AIERu 4.5Facility?MRu 4 AND MCu 2.1NOT (MRu 4 AND MCu 2.1)MN/A11.2.2.1[ ]Yes [ ]No[ ]N/AIERu 4.5Notification indicator?MRu 4 AND MCu 3.1NOT (MRu 4 AND MCu 3.1)MN/A11.2.2.2[ ]Yes [ ]No[ ]N/AIERu 4.6Display?MRu 4NOT MRu 4MN/A[1] 4.5[ ]Yes [ ]No[ ]N/AComments:PSIST ETS 300 196-2:1996

Page 20ETS 300 196-2: June 1996Table A.10: REGISTER PDU parameters received - userItemREGISTER PDUparameters:Does the implementationsupport the .Conditions for statusStatusReferenceSupportIERu 5.1Protocol discriminator?MRu 5NOT MRu 5MN/A[1] 4.2[ ]Yes [ ]No[ ]N/AIERu 5.2Call reference?MRu 5NOT MRu 5MN/A[1] 4.3[ ]Yes [ ]No[ ]N/AIERu 5.3Message type?MRu 5NOT MRu 5MN/A11.2.1[ ]Yes [ ]No[ ]N/AIERu 5.4Facility?MRu 5NOT MRu 5MN/A11.2.2.1[ ]Yes [ ]No[ ]N/AIERu 5.5Display?MRu 5NOT MRu 5MN/A[1] 4.5[ ]Yes [ ]No[ ]N/AComments:Table A.11: RETRIEVE PDU parameters received - userItemRETRIEVE PDUparameters:Does the implementationsupport the .Conditions for statusStatusReferenceSupportIERu 6.1Protocol discriminator?MRu 6NOT MRu 6MN/A[1] 4.2[ ]Yes [ ]No[ ]N/AIERu 6.2Call reference?MRu 6NOT MRu 6MN/A[1] 4.3[ ]Yes [ ]No[ ]N/AIERu 6.3Message type?MRu 6NOT MRu 6MN/A11.2.1[ ]Yes [ ]No[ ]N/AIERu 6.4Channel identification?MRu 6NOT MRu 6MN/A[1] 4.5[ ]Yes [ ]No[ ]N/AIERu 6.5Facility?MRu 6 AND MCu 2.1NOT (MRu 6 AND MCu 2.1)MN/A11.2.2.1[ ]Yes [ ]No[ ]N/AIERu 6.6Notification indicator?MRu 6 AND MCu 3.1NOT (MRu 6 AND MCu 3.1)MN/A11.2.2.2[ ]Yes [ ]No[ ]N/AIERu 6.7Display?MRu 6NOT MRu 6MN/A[1] 4.5[ ]Yes [ ]No[ ]N/AComments:PSIST ETS 300 196-2:1996

Page 21ETS 300 196-2: June 1996Table A.12: RETRIEVE ACKNOWLEDGE PDU parameters received - userItemRETRIEVEACKNOWLEDGE PDUparameters:Does the implementationsupport the .Conditions for statusStatusReferenceSupportIERu 7.1Protocol discriminator?MRu 7NOT MRu 7MN/A[1] 4.2[ ]Yes [ ]No[ ]N/AIERu 7.2Call reference?MRu 7NOT MRu 7MN/A[1] 4.3[ ]Yes [ ]No[ ]N/AIERu 7.3Message type?MRu 7NOT MRu 7MN/A11.2.1[ ]Yes [ ]No[ ]N/AIERu 7.4Channel identification?MRu 7NOT MRu 7MN/A[1] 4.5[ ]Yes [ ]No[ ]N/AIERu 7.5Facility?MRu 7 AND MCu 2.1NOT (MRu 7 AND MCu 2.1)MN/A11.2.2.1[ ]Yes [ ]No[ ]N/AIERu 7.6Notification indicator?MRu 7 AND MCu 3.1NOT (MRu 7 AND MCu 3.1)MN/A11.2.2.2[ ]Yes [ ]No[ ]N/AIERu 7.7Display?MRu 7NOT MRu 7MN/A[1] 4.5[ ]Yes [ ]No[ ]N/AComments:Table A.13: RETRIEVE REJECT PDU parameters received - userItemRETRIEVE REJECT PDUparameters:Does the implementationsupport the .Conditions for statusStatusReferenceSupportIERu 8.1Protocol discriminator?MRu 8NOT MRu 8MN/A[1] 4.2[ ]Yes [ ]No[ ]N/AIERu 8.2Call reference?MRu 8NOT MRu 8MN/A[1] 4.3[ ]Yes [ ]No[ ]N/AIERu 8.3Message type?MRu 8NOT MRu 8MN/A11.2.1[ ]Yes [ ]No[ ]N/AIERu 8.4Cause?MRu 8NOT MRu 8MN/A[1] 4.5[ ]Yes [ ]No[ ]N/AIERu 8.5Facility?MRu 8 AND MCu 2.1NOT (MRu 8 AND MCu 2.1)MN/A11.2.2.1[ ]Yes [ ]No[ ]N/AIERu 8.6Notification indicator?MRu 8 AND MCu 3.1NOT (MRu 8 AND MCu 3.1)MN/A11.2.2.2[ ]Yes [ ]No[ ]N/AIERu 8.7Display?MRu 8NOT MRu 8MN/A[1] 4.5[ ]Yes [ ]No[ ]N/AComments:PSIST ETS 300 196-2:1996

Page 22ETS 300 196-2: June 1996Table A.14: ALERTING PDU parameters received - userItemALERTING PDUparameters:Does the implementationsupport the .Conditions for statusStatusReferenceSupportIERu 9.1Facility?MCu 2.1NOT MCu 2.1MN/A11.2.2.1[ ]Yes [ ]No[ ]N/AIERu 9.2Notification indicator?MCu 3.1NOT MCu 3.1MN/A11.2.2.2[ ]Yes [ ]No[ ]N/ANOTE:These parameters are additional to those required for support of basic call (ETS 300 102-1 [1]).Comments:Table A.15: CALL PROCEEDING PDU parameters received - userItemCALL PROCEEDING PDUparameters:Does the implementationsupport the .Conditions for statusStatusReferenceSupportIERu 10.1Facility?MCu 2.1NOT MCu 2.1MN/A11.2.2.1[ ]Yes [ ]No[ ]N/AIERu 10.2Notification indicator?MCu 3.1NOT MCu 3.1MN/A11.2.2.2[ ]Yes [ ]No[ ]N/ANOTE:These parameters are additional to those required for support of basic call (ETS 300 102-1 [1]).Comments:Table A.16: CONNECT PDU parameters received - userItemCONNECT PDUparameters:Does the implementationsupport the .Conditions for statusStatusReferenceSupportIERu 11.1Facility?MCu 2.1NOT MCu 2.1MN/A11.2.2.1[ ]Yes [ ]No[ ]N/AIERu 11.2Notification indicator?MCu 3.1NOT MCu 3.1MN/A11.2.2.2[ ]Yes [ ]No[ ]N/ANOTE:These parameters are additional to those required for support of basic call (ETS 300 102-1 [1]).Comments:PSIST ETS 300 196-2:1996

Page 23ETS 300 196-2: June 1996Table A.17: CONNECT ACKNOWLEDGE PDU parameters received - userItemCONNECTACKNOWLEDGE PDUparameters:Does the implementationsupport the .Conditions for statusStatusReferenceSupportIERu 12.1Facility?MCu 2.1NOT MCu 2.1MN/A11.2.2.1[ ]Yes [ ]No[ ]N/AIERu 12.2Notification indicator?MCu 3.1NOT MCu 3.1MN/A11.2.2.2[ ]Yes [ ]No[ ]N/ANOTE:These parameters are additional to those required for support of basic call (ETS 300 102-1 [1]).Comments:Table A.18: DISCONNECT PDU parameters received - userItemDISCONNECT PDUparameters:Does the implementationsupport the .Conditions for statusStatusReferenceSupportIERu 13.1Facility?MCu 2.1NOT MCu 2.1MN/A11.2.2.1[ ]Yes [ ]No[ ]N/AIERu 13.2Notification indicator?MCu 3.1NOT MCu 3.1MN/A11.2.2.2[ ]Yes [ ]No[ ]N/ANOTE:These parameters are additional to those required for support of basic call (ETS 300 102-1 [1]).Comments:Table A.19: INFORMATION PDU parameters received - userItemINFORMATION PDUparameters:Does the implementationsupport the .Conditions for statusStatusReferenceSupportIERu 14.1Facility?MCu 2.1NOT MCu 2.1MN/A11.2.2.1[ ]Yes [ ]No[ ]N/AIERu 14.2Notification indicator?MCu 3.1NOT MCu 3.1MN/A11.2.2.2[ ]Yes [ ]No[ ]N/ANOTE:These parameters are additional to those required for support of basic call (ETS 300 102-1 [1]).Comments:PSIST ETS 300 196-2:1996

Page 24ETS 300 196-2: June 1996Table A.20: PROGRESS PDU parameters received - userItemPROGRESS PDUparameters:Does the implementationsupport the .Conditions for statusStatusReferenceSupportIERu 15.1Facility?MCu 2.1NOT MCu 2.1MN/A11.2.2.1[ ]Yes [ ]No[ ]N/AIERu 15.2Notification indicator?MCu 3.1NOT MCu 3.1MN/A11.2.2.2[ ]Yes [ ]No[ ]N/ANOTE:These parameters are additional to those required for support of basic call (ETS 300 102-1 [1]).Comments:Table A.21: RELEASE PDU parameters received - userItemRELEASE PDUparameters:Does the implementationsupport the .Conditions for statusStatusReferenceSupportIERu 16.1Facility?MCu 2.1NOT MCu 2.1MN/A11.2.2.1[ ]Yes [ ]No[ ]N/AIERu 16.2Notification indicator?MCu 3.1NOT MCu 3.1MN/A11.2.2.2[ ]Yes [ ]No[ ]N/ANOTE:These parameters are additional to those required for support of basic call (ETS 300 102-1 [1]).Comments:Table A.22: RELEASE COMPLETE PDU parameters received - userItemRELEASE COMPLETEPDU parameters:Does the implementationsupport the .Conditions for statusStatusReferenceSupportIERu 17.1Facility?MCu 2.1NOT MCu 2.1MN/A11.2.2.1[ ]Yes [ ]No[ ]N/AIERu 17.2Notification indicator?MCu 3.1NOT MCu 3.1MN/A11.2.2.2[ ]Yes [ ]No[ ]N/ANOTE:These parameters are additional to those required for support of basic call (ETS 300 102-1 [1]).Comments:PSIST ETS 300 196-2:1996

Page 25ETS 300 196-2: June 1996Table A.23: RESUME ACKNOWLEDGE PDU parameters received - userI
...