SIST ETS 300 196-5:1998

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Integrated Services Digital Network (ISDN); Generic functional protocol for the support of supplementary services; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:ETS 300 196-5 E13SIST ETS 300 196-5:1998en01-DSULO-19983SIST ETS 300 196-5:1998SLOVENSKI
STANDARD



SIST ETS 300 196-5:1998



EUROPEANETS 300 196-5TELECOMMUNICATIONJanuary 1997STANDARDSource: ETSI TC-SPSReference: DE/SPS-05005-5ICS:33.020Key words:ISDN, DSS1, supplementary service, testing, TSS&TP, networkIntegrated Services Digital Network (ISDN);Generic functional protocol for the support ofsupplementary services;Digital Subscriber Signalling System No. one (DSS1) protocol;Part 5: Test Suite Structure and Test Purposes (TSS&TP)specification for the networkETSIEuropean 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 4 92 94 42 00 - Fax: +33 4 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 1997. All rights reserved.SIST ETS 300 196-5:1998



Page 2ETS 300 196-5: January 1997Whilst 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.SIST ETS 300 196-5:1998



Page 3ETS 300 196-5: January 1997ContentsForeword.71Scope.92Normative references.93Definitions.103.1Definitions related to conformance testing.103.2Definitions related to ETS 300 196-1.104Abbreviations.115General Test Suite Structure (TSS).116TSS&TP.126.1Introduction.126.1.1TP naming convention.126.1.2Source of TP definition.126.1.3TP structure.126.1.4Test strategy.136.1.5Test of call states.136.2Network TSS&TP for the generic functional protocol.146.2.1TSS&TP for clauses 1 to 6.146.2.2TSS&TP for clause 7.146.2.2.1TSS for clause 7.146.2.2.2TPs for clause 7.146.2.2.2.1Auxiliary states.146.2.2.2.1.1Hold Request.146.2.2.2.1.2Retrieve Request.156.2.2.2.1.3Hold Indication.156.2.2.2.1.4Retrieve Indication.156.2.2.2.1.5Call Held.166.2.2.2.2Hold function.166.2.2.2.2.1Initiating entity.166.2.2.2.2.2Responding entity.186.2.2.2.3Retrieve function.216.2.2.2.3.1Initiating entity.216.2.2.2.3.2Responding entity.236.2.2.2.4Clearing of a held call.276.2.3TSS&TP for clause 8.286.2.3.1TSS for clause 8.286.2.3.2TPs for clause 8.286.2.3.2.1Introduction.286.2.3.2.2Application of operations(subclause 8.2).296.2.3.2.2.1Invocation (subclause 8.2.2.1).296.2.3.2.2.2Return result (subclause 8.2.2.2).296.2.3.2.2.3Return error (subclause 8.2.2.3).306.2.3.2.2.4Reject (subclause 8.2.2.4).306.2.3.2.3Transport of components(subclause 8.3).316.2.3.2.3.1Bearer related transport(subclause 8.3.1).316.2.3.2.3.2Bearer independent transport(subclause 8.3.2).316.2.3.2.3.2.1Connection-oriented(subclause 8.3.2.1).31SIST ETS 300 196-5:1998



Page 4ETS 300 196-5: January 19976.2.3.2.3.2.2Connectionless (subclauses 8.3.2.2and 8.3.2.4).346.2.3.2.4Error procedures (subclause 8.4).346.2.4TSS&TP for clause 9.356.2.4.1TSS for clause 9.356.2.4.2TPs for clause 9.356.2.4.2.1Introduction.356.2.4.2.2Bearer-related notifications.356.2.4.2.3Bearer-independent notifications(subclause 9.4).376.2.5TSS&TP for clause 10.386.2.5.1TSS for clause 10.386.2.5.2TPs for clause 10.396.2.5.2.1Network-side channel reservationfunction.396.2.5.2.1.1Implicit reservation.396.2.5.2.1.1.1Implicit reservation creation.396.2.5.2.1.1.1.1Channel reserved.396.2.5.2.1.1.1.2Receipt of HOLD ACKNOWLEDGE.396.2.5.2.1.1.1.3Sending of HOLD ACKNOWLEDGE.406.2.5.2.1.1.1.4Receipt of RELEASE COMPLETE.406.2.5.2.1.1.1.4.1Call Held auxiliary state.406.2.5.2.1.1.1.4.2Retrieve Request auxiliary state.426.2.5.2.1.1.1.4.3Retrieve Indication auxiliary state.436.2.5.2.1.1.1.5Sending of RELEASE COMPLETE.446.2.5.2.1.1.1.5.1Call Held auxiliary state.446.2.5.2.1.1.1.5.2Retrieve Request auxiliary state.456.2.5.2.1.1.1.5.3Retrieve Indication auxiliary state.466.2.5.2.1.1.1.6Sending of SUSPENDACKNOWLEDGE.476.2.5.2.1.1.1.6.1Call Held auxiliary state.476.2.5.2.1.1.1.6.2Retrieve Request auxiliary state.486.2.5.2.1.1.1.6.3Retrieve Indication auxiliary state.496.2.5.2.1.1.1.7Sending of RESTARTACKNOWLEDGE.506.2.5.2.1.1.1.8Receipt of RESTARTACKNOWLEDGE.506.2.5.2.1.1.2Implicit reservation use.516.2.5.2.1.1.3Implicit reservation cancellation.526.2.5.2.1.2Explicit reservation.536.2.5.2.1.2.1Explicit reservation control.536.2.5.2.1.2.1.1Invocation.536.2.5.2.1.2.1.1.1With reservation indicator.536.2.5.2.1.2.1.1.2Without reservation indicator.546.2.5.2.1.2.1.1.3No reservation required.566.2.5.2.1.2.1.2Return error.576.2.5.2.1.2.2Explicit reservation management.576.2.5.2.1.2.2.1Absence of invoke.576.2.5.2.1.2.2.2Presence of invoke.586.2.5.2.1.2.2.3Return error.586.2.5.2.1.2.3Explicit reservation cancellation.596.2.5.2.1.2.3.1Invocation.596.2.5.2.1.2.3.2Return error.606.2.5.2.1.2.3.3Other.606.2.5.2.2Generic procedures for supplementaryservice management.616.2.5.2.2.1Activation.616.2.5.2.2.2Deactivation.626.2.5.2.2.3Interrogation.626.2.5.2.3Generic status request procedure.63SIST ETS 300 196-5:1998



Page 5ETS 300 196-5: January 19976.2.6TSS&TP for clause 11.646.2.6.1TSS for clause 11.646.2.6.2TPs for clause 11.646.2.6.2.1Facility information element.646.2.6.2.2Extended facility information element.646.2.7TSS&TP for annex D.656.2.7.1TSS for annex D.656.2.7.2TPs for annex D.656.2.7.2.1Definition of Q.931 informationelements.657Compliance.658Requirements for a comprehensive testing service.65History.66SIST ETS 300 196-5:1998



Page 6ETS 300 196-5: January 1997Blank pageSIST ETS 300 196-5:1998



Page 7ETS 300 196-5: January 1997ForewordThis 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 5 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".Transposition datesDate of adoption8 November 1996Date of latest announcement of this ETS (doa):30 April 1997Date of latest publication of new National Standardor endorsement of this ETS (dop/e):31 October 1997Date of withdrawal of any conflicting National Standard (dow):31 October 1997SIST ETS 300 196-5:1998



Page 8ETS 300 196-5: January 1997Blank pageSIST ETS 300 196-5:1998



Page 9ETS 300 196-5: January 19971ScopeThis fifth part of ETS 300 196 specifies the Test Suite Structure and Test Purposes (TSS&TP) for theNetwork side of the T reference point or coincident S and T reference point (as defined in ITU-TRecommendation I.411 [6]) of implementations conforming to the stage three standard for the genericfunctional protocol for the support of supplementary services for the pan-European Integrated ServicesDigital Network (ISDN) by means of the Digital Subscriber Signalling System No. one (DSS1) protocol,ETS 300 196-1 [1].A further part of this ETS specifies the Abstract Test Suite (ATS) and partial Protocol ImplementationeXtra Information for Testing (PIXIT) proforma based on this ETS. Other parts specify the TSS&TP andthe ATS and partial PIXIT proforma for the User side of the T reference point or coincident S andT reference point of implementations conforming to ETS 300 196-1 [1].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 196-1: "Integrated Services Digital Network (ISDN); Generic functionalprotocol for the support of supplementary services; Digital Subscriber SignallingSystem No. one (DSS1) protocol; Part 1: Protocol specification".[2]ETS 300 196-2: "Integrated Services Digital Network (ISDN); Generic functionalprotocol for the support of supplementary services; Digital Subscriber SignallingSystem No. one (DSS1) protocol; Part 2: Protocol Implementation ConformanceStatement (PICS) proforma specification".[3]ISO/IEC 9646-1: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 1: General Concepts".[4]ISO/IEC 9646-2: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 2: Abstract Test Suite specification".[5]ISO/IEC 9646-3: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 3: The Tree and Tabular CombinedNotation".[6]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -Reference configurations".[7]ETS 300 102-1: "Integrated Services Digital Network (ISDN); User-networkinterface layer 3; Specifications for basic call control".[8]ITU-T Recommendation I.112 (1993): "Vocabulary and terms for ISDNs".[9]CCITT Recommendation E.164 (1991): "Numbering plan for the ISDN era".[10]ITU-T Recommendation I.210 (1993): "Principles of the telecommunicationservices supported by an ISDN and the means to describe them".[11]I-ETS 300 316: "Integrated Services Digital Network (ISDN); Digital SubscriberSignalling System No. one (DSS1); Protocol Implementation ConformanceStatement (PICS) proforma specification for signalling network layer protocol forcircuit-mode basic call control (basic access, network)".[12]CCITT Recommendation X.209 (1988): "Specification of Basic Encoding Rulesfor Abstract Syntax Notation One (ASN.1)".SIST ETS 300 196-5:1998



Page 10ETS 300 196-5: January 19973DefinitionsFor the purposes of this ETS, the following definitions apply:3.1Definitions related to conformance testingabstract test case: Refer to ISO/IEC 9646-1 [3].Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [3].active test: A test case where the IUT is required to send a particular message, but not in reaction to areceived message. This would usually involve the use of PIXIT information to see how this message canbe generated and quite often is specified in an ATS using an implicit send event.Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [3].implicit send event: Refer to ISO/IEC 9646-3 [5].lower tester: Refer to ISO/IEC 9646-1 [3].passive test: A test case where the IUT is required to respond to a protocol event (e.g. receivedmessage) with another protocol event (sends message) and normally does not require any specialoperator intervention such as is associated with the implicit send event.point of control and observation: Refer to ISO/IEC 9646-1 [3].Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [3].PICS proforma: Refer to ISO/IEC 9646-1 [3].Protocol Implementation eXtra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 [3].PIXIT proforma: Refer to ISO/IEC 9646-1 [3].system under test: Refer to ISO/IEC 9646-1 [3].Test Purpose (TP): Refer to ISO/IEC 9646-1 [3].3.2Definitions related to ETS 300 196-1call held auxiliary state: See ETS 300 196-1 [1], subclause 7.1.2.call reference: See ETS 300 102-1 [7], subclause 4.3.called user: The user at the origination side of the call.calling user: The user at the destination side of the call.component: See ETS 300 196-1 [1], subclause 11.2.2.1.hold requested auxiliary state: See ETS 300 196-1 [1], subclause 7.1.2.idle auxiliary state: See ETS 300 196-1 [1], subclause 7.1.2.Integrated Services Digital Network (ISDN): See ITU-T Recommendation I.112 [8], definition 308.ISDN number: A number conforming to the numbering and structure specified in CCITTRecommendation E.164 [9].invoke component: See ETS 300 196-1 [1], subclause 11.2.2.1.SIST ETS 300 196-5:1998



Page 11ETS 300 196-5: January 1997network: The DSS1 protocol entity at the Network side of the user-network interface where a T referencepoint or coincident S and T reference point applies.network (S/T): The DSS1 protocol entity at the network side of the user-network interface where acoincident S and T reference point applies.network (T): The DSS1 protocol entity at the Network side of the user-network interface where aT reference point applies (Network connected to Private ISDN).retrieve requested auxiliary state: See ETS 300 196-1 [1], subclause 7.1.2.return error component: See ETS 300 196-1 [1], subclause 11.2.2.1.return result component: See ETS 300 196-1 [1], subclause 11.2.2.1.service; telecommunication service: See ITU-T Recommendation I.112 [8], definition 201.supplementary service: See ITU-T Recommendation I.210 [10], subclause 2.4.4AbbreviationsFor the purposes of this ETS, the following abbreviations apply:ATMAbstract Test MethodATSAbstract Test SuiteCRCall ReferenceDSS1Digital Subscriber Signalling System No. oneGFPGeneric Functional ProtocolISDNIntegrated Services Digital NetworkIUTImplementation Under TestN00Null call stateN03Outgoing Call Proceeding call stateN04Call Delivered call stateN07Call Received call stateN08Connect Request call stateN09Incoming Call Proceeding call stateN10Active call stateN12Disconnect Indication call stateN19Release Request call stateN25Overlap Receiving call statePICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingTPTest PurposeTSSTest Suite StructureUIUnnumbered Information5General Test Suite Structure (TSS)Generic Functional Protocol - NetworkClauses 1-6Clause 7Clause 8Clause 9Clause 10Clause 11Annex DFigure 1: Test suite structureMore detailed TSS for each group (branch) are contained in separate subclauses.SIST ETS 300 196-5:1998



Page 12ETS 300 196-5: January 19976TSS&TP6.1IntroductionFor each test requirement a TP is defined.6.1.1TP naming conventionTPs are numbered, starting at 001, within each group. Groups are organized according to the TSS.Additional references are added to identify the actual test suite and whether it applies to the network or theuser (see table 1).Table 1: TP identifier naming convention schemeIdentifier:___=supplementary service:e.g. "GFP"=type of IUT:UUserNNetwork=clause1 or 2 character field representing a clause number fromETS 300 196-1 [1]=group2 digit field representing group reference according to TSS=sequential number(001-999)6.1.2Source of TP definitionThe TPs are based on ETS 300 196-1 [1].6.1.3TP structureEach TP has been written in a manner which is consistent with all other TPs. The intention of this is tomake the TPs more readable and checkable. A particular structure has been used and this is illustrated intable 2. This table should be read in conjunction with any TP, i.e. use a TP as an example to fullyunderstand the table.SIST ETS 300 196-5:1998



Page 13ETS 300 196-5: January 1997Table 2: Structure of a single TPTP partTextExampleHeader tabsee table 1 tabsubclause 0.0.0 CRvalid, invalid, inopportuneStimulusEnsure that the IUT in theN10, N10, etc. see below for message structurereceiving a XXXX messageor to request a .Reactionsends, saves, does, etc.using en-bloc sending, .if the action is sending
see below for message structure, etc.and remains in the same stateor and enters state Messagestructuremessage containing aSETUP, FACILITY, CONNECT, .a) information element withb) a encoded as or including and back to a or b,Bearer capability, Facility, .NOTE:Text in italics will not appear in TPs and text between <> is filled in for each TP and maydiffer from one TP to the next.6.1.4Test strategyAs the base standard ETS 300 196-1 [1] contains no explicit requirements for testing, the TPs weregenerated as a result of an analysis of the base standard and the PICS specification ETS 300 196-2 [2].The criteria applied include the following:-only the requirements from the point of view of the T or coincident S and T reference point areconsidered;-whether or not a test case can be built from the TP is not considered.6.1.5Test of call statesMany TPs include a reference to the IUT's final call state after the realization of the TP. In these cases theTP includes the requirement to ensure that the IUT has entered this particular final call state. Ensuringthat the IUT is in a particular call state shall be realized by following the procedures described insubclause 5.8.10 of ETS 300 102-1 [7]. According to these procedures, the IUT on receipt of a STATUSENQUIRY message, shall respond with a STATUS message indicating, in the third octet of the Call stateinformation element, the current call state of the IUT. This exchange of messages is not mentionedexplicitly in each TP but is considered to be implicit in the reference to the final call state. This way ofphrasing the TPs has been used to avoid over-complicating the text and structure of the TPs and toimprove the readability.SIST ETS 300 196-5:1998



Page 14ETS 300 196-5: January 19976.2Network TSS&TP for the generic functional protocol6.2.1TSS&TP for clauses 1 to 6None identified.6.2.2TSS&TP for clause 76.2.2.1TSS for clause 7GFP - clause 7Auxiliary statesHoldRetrieveClearing(10)HoldRequest(01)RetrieveRequest(02)HoldIndication(03)RetrieveIndication(04)Call Held(05)Initiatingentity(06)Respondingentity(07)Initiatingentity(08)Respondingentity(09)Figure 2: TSS6.2.2.2TPs for clause 7Selection:IUT supports the functional protocol for the control of supplementary services.PICS: MCn 1.6.2.2.2.1Auxiliary states6.2.2.2.1.1Hold RequestSelection:IUT supports the functions of an initiating entity. PICS: R 5.1.GFP_N7_01_001subclause 7.1.2, 3rd paragraphinopportuneEnsure that IUT, while in the Active call state N10 and Hold Request auxiliary state, entering the Null callstate N00,enters the Idle auxiliary state.GFP_N7_01_002subclause 7.1.2, 3rd paragraphinopportuneEnsure that IUT, while in the Active call state N10 and Hold Request auxiliary state, entering theDisconnect Request call state N11,enters the Idle auxiliary state.GFP_N7_01_003subclause 7.1.2, 3rd paragraphinopportuneEnsure that if the network, while in the Outgoing Call Proceeding call state N03 and Hold Requestauxiliary state, enters the Release Request call state N19,enters the Idle auxiliary state.GFP_N7_01_004subclause 7.1.2, 4th paragraphinopportuneEnsure that IUT, while in the Active call state N10 and Hold Request auxiliary state, entering theDisconnect Indication call state N12,enters the Idle auxiliary state.SIST ETS 300 196-5:1998



Page 15ETS 300 196-5: January 19976.2.2.2.1.2Retrieve RequestSelection:IUT supports the functions of an initiating entity. PICS: R 5.1.GFP_N7_02_001subclause 7.1.2, 3rd paragraphinopportuneEnsure that IUT, while in the Active call state N10 and Retrieve Request auxiliary state, entering the Nullcall state N00,enters the Idle auxiliary state.GFP_N7_02_002subclause 7.1.2, 3rd paragraphinopportuneEnsure that IUT, while in the Active call state N10 and Retrieve Request auxiliary state, entering theDisconnect Request call state N11,enters the Idle auxiliary state.GFP_N7_02_003subclause 7.1.2, 3rd paragraphinopportuneEnsure that if the network, while in the Outgoing Call Proceeding call state N03 and Retrieve Requestauxiliary state, enters the Release Request call state N19,enters the Idle auxiliary state.GFP_N7_02_004subclause 7.1.2, 4th paragraphinopportuneEnsure that IUT, while in the Active call state N10 and Retrieve Request auxiliary state, entering theDisconnect Indication call state N12,it remains in the same auxiliary state.6.2.2.2.1.3Hold IndicationSelection:IUT supports the functions of an responding entity. PICS: R 5.2.GFP_N7_03_001subclause 7.1.2, 3rd paragraphinopportuneEnsure that IUT, while in the Active call state N10 and Hold Indication auxiliary state, entering the Null callstate N00,enters the Idle auxiliary state.GFP_N7_03_002subclause 7.1.2, 3rd paragraphinopportuneEnsure that IUT, while in the Active call state N10 and Hold Indication auxiliary state, entering theDisconnect Request call state N11,enters the Idle auxiliary state.GFP_N7_03_003subclause 7.1.2, 3rd paragraphinopportuneEnsure that if the network, while in the Outgoing Call Proceeding call state N03 and Hold Indicationauxiliary state, enters the Release Request call state N19,enters the Idle auxiliary state.GFP_N7_03_004subclause 7.1.2, 3rd paragraphinopportuneEnsure that IUT, while in the Active call state N10 and Hold Indication auxiliary state, entering theDisconnect Indication call state N12,enters the Idle auxiliary state.6.2.2.2.1.4Retrieve IndicationSelection:IUT supports the functions of an responding entity. PICS: R 5.2.GFP_N7_04_001subclause 7.1.2, 3rd paragraphinopportuneEnsure that IUT, while in the Active call state N10 and Retrieve Indication auxiliary state, entering the Nullcall state N00,enters the Idle auxiliary state.GFP_N7_04_002subclause 7.1.2, 3rd paragraphinopportuneEnsure that IUT, while in the Active call state N10 and Retrieve Indication auxiliary state, entering theDisconnect Request call state N11,enters the Idle auxiliary state.SIST ETS 300 196-5:1998



Page 16ETS 300 196-5: January 1997GFP_N7_04_003subclause 7.1.2, 3rd paragraphinopportuneEnsure that if the network, while in the Outgoing Call Proceeding call state N03 and Retrieve Indicationauxiliary state, enters the Release Request call state N19,enters the Idle auxiliary state.GFP_N7_04_004subclause 7.1.2, 3rd paragraphinopportuneEnsure that IUT, while in the Active call state N10 and Retrieve Indication auxiliary state, entering theDisconnect Indication call state N12,it remains in the same auxiliary state.6.2.2.2.1.5Call HeldGFP_N7_05_001subclause 7.1.2, 3rd paragraphinopportuneEnsure that IUT, while in the Active call state N10 and Call Held auxiliary state, entering the Null call stateN00,enters the Idle auxiliary state.GFP_N7_05_002subclause 7.1.2, 3rd paragraphinopportuneEnsure that IUT, while in the Active call state N10 and Call Held auxiliary state, entering the DisconnectRequest call state N11,enters the Idle auxiliary state.GFP_N7_05_003subclause 7.1.2, 3rd paragraphinopportuneEnsure that if the network, while in the Outgoing Call Proceeding call state N03 and Call Held auxiliarystate, enters the Release Request call state N19,enters the Idle auxiliary state.GFP_N7_05_004subclause 7.1.2, 3rd paragraphinopportuneEnsure that IUT, while in the Active call state N10 and Call Held auxiliary state, entering the DisconnectIndication call state N12,it remains in the same auxiliary state.6.2.2.2.2Hold function6.2.2.2.2.1Initiating entitySelection:IUT supports the functions of an initiating entity. PICS: R 5.1.GFP_N7_06_001subclause 7.2.1.1validEnsure that the IUT, while in the Outgoing Call Proceeding call state N03 and Idle auxiliary state,is able to transmit a HOLD message and enters the Hold Request auxiliary state.GFP_N7_06_002subclause 7.2.1.1validEnsure that the IUT, while in the Call Delivered call state N04 and Idle auxiliary state,is able to transmit a HOLD message and enters the Hold Request auxiliary state.GFP_N7_06_003subclause 7.2.1.1validEnsure that the IUT, while in the Call Received call state N07 and Idle auxiliary state,is able to transmit a HOLD message and enters the Hold Request auxiliary state.Selection:IUT supports basic access, point-to-point configuration? P
...