SIST EN 300 196-1 V1.3.2:2004

• Abstract:

  Provide the necessary enhancements to support the addressing of network functionality for CTM and IN/ISDN requirements In order to support these applications, hooks will be made to the generic functional transport control protocol

• Status: Published
• Publication Date: 31-Mar-2004
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Apr-2004
• Due Date: 01-Apr-2004
• Completion Date: 01-Apr-2004
• Ref Project: ETSI EN 300 196-1 V1.3.2 (2001-06) - Integrated Services Digital Network (ISDN); Generic functional protocol for the support of supplementary services; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 1: Protocol specification

SIST EN 300 196-1 V1.3.2:2004 is the Slovenian adoption of ETSI EN 300 196-1 for the ISDN generic functional protocol that supports supplementary services. It specifies how DSS1 protocol elements are used to address network functionality for supplementary services at the T reference point, or coincident S and T reference point, on public ISDN access. The standard is for equipment and implementations that need to control, signal, or test supplementary services over ISDN.

What does SIST EN 300 196-1 V1.3.2:2004 specify?

SIST EN 300 196-1 V1.3.2:2004 specifies the functional protocol for supplementary services in pan-European ISDN. It is symmetrical, applies to both basic and primary rate access, and is based on the Facility information element, the FACILITY message, and other function-specific messages.

The scope covers activation and deactivation, invocation and operation, interrogation, status request, status notification, and the generic channel reservation function. It also covers delivery of notifications at the user-network interface. The application to individual supplementary services is defined in the separate standards for those services.

The document is organized into clauses 1 to 11, followed by annexes A to K. Clauses 5 to 10 explain how the generic protocol works in practice, and clause 11 defines the coding rules for the protocol elements.

Annex	What it covers
A	Dynamic descriptions of the main protocol state machines
B	Guidelines for designing individual supplementary services
C	ASN.1 subtypes and proposed future enhancements
D	Formal data type definitions using ITU-T Recommendation X.208
E	Formal data type definitions using ITU-T Recommendation X.680
F	Remote operations notation using ITU-T Recommendation X.208
G	Remote operations notation using ITU-T Recommendation X.680
H	Coding examples
I	Object identifier values
J	Changes from EN 300 196-1 Version 1.2.2
K	Bibliography

What are the key requirements of SIST EN 300 196-1 V1.3.2:2004?

SIST EN 300 196-1 V1.3.2:2004 defines two control styles for supplementary services - the separate message approach and the common information element approach. In practice, this means implementers must choose the right signaling model depending on whether the service needs resource synchronization with the call or can be handled as a request-response operation.

Co-existence and service selection

Clause 5 allows a network to support more than one generic protocol for supplementary services, such as the keypad protocol and the functional protocol. Users are informed at subscription time which services and protocols are available on their access, so the terminal can use the correct signaling method.

Separate message approach

Clause 7 uses dedicated messages for functions such as HOLD and RETRIEVE. This approach includes a two-dimensional state model with a call state and an auxiliary state, which matters because hold and retrieve actions must stay synchronized with the ongoing call.

Common information element approach

Clause 8 uses the Facility information element, and where needed the Extended facility information element, to carry remote-operations components. This approach is for supplementary services that do not need resource synchronization between the user and the network, so the implementation must track operation, return result, return error, and reject handling.

Transport mechanisms

Clause 8.3 defines bearer-related and bearer-independent transport. The standard distinguishes point-to-point and broadcast transport, and also separates local signalling from general signalling. This matters because the same Facility content may be carried in different message types depending on whether the operation is tied to a call or independent of it.

NCICS and GAT

Clause 8.3.2.5 defines Networked Call Independent, Connection-oriented Signalling (NCICS) for the Generic Addressing and Transport (GAT) protocol. It uses call-control style messages such as SETUP, CALL PROCEEDING, CONNECT, RELEASE, and RELEASE COMPLETE, so implementers must follow the stated state transitions and timer behavior.

Management and reservations

Clause 10 covers the network-side channel reservation function and generic supplementary-service management. That includes implicit and explicit reservation, activation, deactivation, interrogation, status notification, and status request, which are the functions operators use to control service availability.

Coding and error handling

Clause 11 defines the required message contents and information-element coding, including the Facility information element, Notification indicator, Call state, Extended facility information element, Bearer capability, and Channel identification. This is the part that test teams use to verify that a terminal or network encodes the protocol exactly as expected.

What terms does SIST EN 300 196-1 V1.3.2:2004 define?

• functional protocol - A sequence of functional information elements that needs intelligent processing by the terminal when generating or analyzing messages.
• call reference - The identifier for a signaling transaction; it can be bearer-related or bearer-independent.
• CEI (ConnectionEndpointIdentifier) - The identifier a layer 3 protocol entity uses to address its peer entity.
• bearer-related transport mechanism - A transport method tied to a basic call control connection, used when the supplementary service must follow the call.
• bearer-independent transport mechanism - A transport method not tied to a call, used when the service is handled independently of a connection.
• GAT protocol (Generic Addressing and Transport) - The addressing and transport method used for general signalling in this standard.
• NCICS (Networked Call Independent, Connection-oriented Signalling) - The connection-oriented transport used for bearer-unrelated general signalling.

Who uses SIST EN 300 196-1 V1.3.2:2004?

SIST EN 300 196-1 V1.3.2:2004 is used by public telecommunications operators, terminal equipment vendors, network equipment vendors, and test laboratories. Engineers use it to implement DSS1 signaling for supplementary services, quality teams use it to verify protocol behavior, and buyers use it to check whether a product supports the required ISDN supplementary-service control.

It is also relevant for systems that interact with corporate telecommunication networks, PINX equipment, NT2, and other ISDN access equipment.

What changed in SIST EN 300 196-1 V1.3.2:2004 from the previous edition?

SIST EN 300 196-1 V1.3.2:2004 is identified as an extended and updated version of EN 300 196-1 Version 1.2.2. Annex J lists editorial changes and technical changes, including ASN.1 definitions aligned with ITU-T Recommendations X.680 and X.880, a new bearer-independent connection-oriented transport mechanism for general signalling, GAT-related updates, and clarifications.

Which standards are used with SIST EN 300 196-1 V1.3.2:2004?

The standard relies on EN 300 403-1 for basic call control and call-state procedures, and on ETS 300 402-2 for data link layer services. It also uses EN 301 813-1 for the Generic Addressing and Transport protocol.

For coding and notation, it refers to ITU-T Recommendations X.208, X.209, X.219, X.229, X.680, X.690, and X.880. For ISDN vocabulary and reference configurations, it uses ITU-T Recommendations I.112, I.210, I.411, and Q.9.

What does the SIST EN 300 196-1 V1.3.2:2004 document contain?

The document contains the protocol rules for Hold and Retrieve, remote-operations handling through the Facility information element, transport rules for bearer-related and bearer-independent procedures, and the general signalling procedures for NCICS. It also includes dynamic SDL-style descriptions in Annex A, implementation guidance in Annex B, and formal datatype definitions in Annexes D and E.

Annex H gives coding examples, Annex I lists object identifier assignments, and Annex J summarizes the differences from the earlier version. Clause 11 provides the practical coding details that implementers and test teams need when building or checking message formats.

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 1: Protocol specification33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 300 196-1 Version 1.3.2SIST EN 300 196-1 V1.3.2:2004en01-april-2004SIST EN 300 196-1 V1.3.2:2004SLOVENSKI
STANDARD
ETSIEN300196-1V1.3.2(2001-06)EuropeanStandard(Telecommunicationsseries)IntegratedServicesDigitalNetwork(ISDN);Genericfunctionalprotocolforthesupportofsupplementaryservices;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part1:ProtocolspecificationSIST EN 300 196-1 V1.3.2:2004

ETSIETSIEN300196-1V1.3.2(2001-06)2ReferenceREN/SPAN-05135-1Keywordsaddressing,DSS1,functional,generic,ISDN,SDL,supplementaryservice,transportETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:[phone]Fax:[phone]SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:[e-mail]opartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2001.Allrightsreserved.SIST EN 300 196-1 V1.3.2:2004

ETSIETSIEN300196-1V1.3.2(2001-06)3ContentsIntellectualPropertyRights.9Foreword.91Scope.102References.103Definitions.123.1Generaldefinitions.123.2Remoteoperationsdefinitions.133.3Definitionofproceduresusingthecommoninformationelementapproach.134Abbreviations.145Co-existenceofgenericprotocolsforthecontrolofsupplementaryservices.145.1Supportofvariousgenericprotocols.145.2Co-existenceofgenericprotocols.145.3Arrangementsbywhichco-existenceofprotocolsmaybesupportedbyanetwork.156Generalprinciplesappliedforthefunctionalcontrolofsupplementaryservices.156.1Introduction.156.2Scopeoftheprocedures.156.3Categoriesofprocedures.156.4Supplementaryservicefunctions.167Controlofsupplementaryservicesusingtheseparatemessageapproach.167.1HoldandRetrievefunctions.167.1.1MessagesfortheHoldandRetrievefunction.167.1.2AuxiliarystatesfortheHoldandRetrievefunction.177.2Holdprocedures.187.2.1Initiatingentity.187.2.1.1Normaloperation.187.2.1.2Exceptionalprocedures.197.2.2Respondingentity.197.2.2.1Normaloperation.197.2.2.2Exceptionalprocedures.197.3CallHeldauxiliarystate.197.4Retrieveprocedure.197.4.1Initiatingentity.207.4.1.1Normaloperation.207.4.1.2Exceptionalprocedures.207.4.2Respondingentity.207.4.2.1Normaloperation.207.4.2.2Exceptionalprocedures.217.5Parametervalues(timers).217.6Clearingofaheldcall.218Controlofsupplementaryservicesusingthecommoninformationelementapproach.228.1General.228.1.1Introduction.228.1.2Scopeoftheprocedures.228.2Applicationofoperations.228.2.1Definitions.228.2.2Proceduresforoperations.228.2.2.1Invocation.238.2.2.2Returnresult.238.2.2.3Returnerror.238.2.2.4Reject.238.2.2.5FormaldefinitionofDataTypes.24SIST EN 300 196-1 V1.3.2:2004

ETSIETSIEN300196-1V1.3.2(2001-06)48.3Transportofcomponents.248.3.1Bearer-relatedtransport.258.3.1.1Point-to-pointtransportmechanism.258.3.1.1.1Normaloperation.258.3.1.1.2Exceptionalprocedures.258.3.1.2Broadcasttransportmechanism.268.3.1.2.1Normaloperation.268.3.1.2.2Exceptionalprocedures.268.3.2Bearer-independenttransport.268.3.2.1Point-to-pointtransportmechanism(connection-oriented)forlocalsignalling.278.3.2.1.1Connectionestablishment.278.3.2.1.2Datatransferphase.288.3.2.1.3Connectionrelease.288.3.2.2Point-to-pointtransportmechanism(connectionless)forlocalsignalling.298.3.2.2.1Normaloperation.298.3.2.2.2Exceptionalprocedures.308.3.2.3Broadcasttransportmechanism(connection-oriented)forlocalsignalling.308.3.2.4Broadcasttransportmechanism(connectionless)forlocalsignalling.308.3.2.4.1Normaloperation.308.3.2.4.2Exceptionalprocedures.308.3.2.5Point-to-pointtransportmechanism(connection-oriented)forgeneralsignalling.318.3.2.5.1Connectionestablishmentattheoriginatinginterface.318.3.2.5.2Connectionestablishmentatthedestinationinterface.338.3.2.5.3Connectionclearing.358.3.2.5.4Interactionwithrestartprocedure.378.3.2.5.5Interactionwithcallrearrangements.378.3.2.5.6Handlingoferrorconditions.378.3.2.5.7Protocoltimervalues.378.3.2.6Broadcasttransportmechanism(connection-oriented)forgeneralsignalling.378.3.3GFT-ControlandGAT-Control.388.3.3.1GFT-Control.388.3.3.1.1Transmissionofgenericfunctionaldata.388.3.3.1.2Receiptofgenericfunctionaldata.388.3.3.2GAT-Control.398.4Errorprocedures.398.4.1Componenterrorhandling.398.4.2Errorhandlingofmistypeddatavalues.398.5Responsetomultiplesupplementaryserviceinvocations.399Genericnotificationprocedures.399.1General.399.2Categoriesofnotificationprocedures.409.3Transportofbearer-relatednotifications.409.3.1Normaloperation.409.3.2Exceptionalprocedures.419.4Transportofbearer-independentnotifications.419.4.1Normaloperation.419.4.2Exceptionalprocedures.4110Othergenericprocedures.4110.1Network-sidechannelreservationfunction.4110.1.1Implicitreservation.4210.1.1.1Implicitreservationcreation.4210.1.1.2Implicitreservationuse.4210.1.1.3Implicitreservationcancellation.4310.1.2Explicitreservation.4310.1.2.1Explicitreservationcontrol.4310.1.2.2Explicitreservationmanagement.4410.1.2.3Explicitreservationcancellation.4510.1.3Effectofreservationonchannelselectionforanewcall.4510.1.4Interactionbetweenimplicitandexplicitnetwork-sidechannelreservationfunctionsonthesameCEI.45SIST EN 300 196-1 V1.3.2:2004

ETSIETSIEN300196-1V1.3.2(2001-06)510.2Genericproceduresforsupplementaryservicemanagement.4610.2.1Introduction.4610.2.2Activation.4710.2.2.1Normaloperation.4710.2.2.2Activationexceptionalprocedures.4710.2.3Deactivation.4810.2.3.1Normaloperation.4810.2.3.2Deactivationexceptionalprocedures.4810.2.4Interrogation.4910.2.4.1Normaloperation.4910.2.4.2Interrogationexceptionalprocedures.4910.2.5Statusnotification.5010.2.5.1Normaloperation.5010.2.5.2Exceptionalprocedures.5010.2.6Statedefinitions.5010.2.7Parametervalues(timers).5010.3Genericstatusrequestprocedure.5110.3.1Introduction.5110.3.2Normaloperation.5110.3.3Exceptionalprocedures.5310.3.4Parametervalues(timers).5311Codingrequirements.5311.1Messagefunctionaldefinitionsandcontent.5311.1.1Additionalmessagesforthebearer-relatedtransportmechanism.5411.1.1.1FACILITY.5411.1.1.2HOLD.5411.1.1.3HOLDACKNOWLEDGE.5411.1.1.4HOLDREJECT.5511.1.1.5RETRIEVE.5511.1.1.6RETRIEVEACKNOWLEDGE.5511.1.1.7RETRIEVEREJECT.5611.1.2Messagesforthebearer-independent(connection-oriented)transportmechanismforlocalsignalling.5611.1.2.1FACILITY.5611.1.2.2REGISTER.5711.1.2.3RELEASE.5711.1.2.4RELEASECOMPLETE.5811.1.2.5STATUS.5811.1.2.6STATUSENQUIRY.5811.1.3Messagesforbearer-independenttransportmechanism(connectionless)forlocalsignalling.5911.1.3.1FACILITY.5911.1.3.2NOTIFY.5911.1.4Messagesforbearer-independent,point-to-pointtransportmechanism(connection-oriented)forgeneralsignalling.5911.1.4.1CALLPROCEEDING.6011.1.4.2CONNECT.6011.1.4.3CONNECTACKNOWLEDGE.6011.1.4.4FACILITY.6011.1.4.5RELEASE.6111.1.4.6RELEASECOMPLETE.6111.1.4.7SETUP.6211.1.4.8STATUS.6211.1.4.9STATUSENQUIRY.6211.1.5AdditionalinformationelementsinEN300403-1messagesforthebearerrelatedtransportmechanism.6211.2Generalmessageformatandinformationelementcoding.6311.2.1Messagetype.6311.2.2Otherinformationelements.6311.2.2.1Facility.6411.2.2.1.1TreatmentofexistingQ.931informationelementsasparameters.6611.2.2.2Notificationindicator.6611.2.2.3Callstate.67SIST EN 300 196-1 V1.3.2:2004

ETSIETSIEN300196-1V1.3.2(2001-06)611.2.2.4Extendedfacilityinformationelement.6711.2.2.5Bearercapability.6811.2.2.6Channelidentification.69AnnexA(normative):Dynamicdescriptions.71A.1DynamicdescriptionoftheHoldandRetrievefunctions.71A.2Dynamicdescriptionofthestatusrequestprocedure.82A.3Dynamicdescriptionofthesupplementaryservicemanagementfunction.86A.4Dynamicdescriptionofthebearer-independentpoint-to-pointtransportmechanism(connection-oriented)forgeneralsignalling.95A.4.1NetworksideSDLprocess.95A.4.1.1Null(N0)state.95A.4.1.2CallInitiated(N1)state.95A.4.1.3OverlapSending(N2)state.95A.4.1.4OutgoingCallProceeding(N3)state.95A.4.1.5CallDelivered(N4)state.95A.4.1.6CallPresent(N6)state.96A.4.1.7CallReceived(N7)state.96A.4.1.8IndividualCallReceived(N7I)state.96A.4.1.9ConnectRequest(N8)state.96A.4.1.10IndividualConnectRequest(N8I)state.96A.4.1.11IncomingCallProceeding(N9)state.96A.4.1.12IndividualIncomingCallProceeding(N9I)state.97A.4.1.13Active(N10)state.97A.4.1.14ReleaseRequest(N19)state.97A.4.1.15IndividualReleaseRequest(N19I)state.97A.4.1.16CallAbort(N22)state.97A.4.1.17OverlapReceiving(N25)state.97A.4.1.18IndividualOverlapReceiving(N25I)state.97A.4.2UsersideSDLprocess.97A.4.2.1Null(U0)state.97A.4.2.2CallInitiated(U1)state.98A.4.2.3OverlapSending(U2)state.98A.4.2.4OutgoingCallProceeding(U3)state.98A.4.2.5CallDelivered(U4)state.98A.4.2.6CallPresent(U6)state.98A.4.2.7CallReceived(U7)state.98A.4.2.8Connectrequest(U8)state.98A.4.2.9IncomingCallProceeding(U9)state.99A.4.2.10Active(U10)state.99A.4.2.11ReleaseRequest(U19)state.99A.4.2.12OverlapReceiving(U25)state.99A.4.3RestartSDLprocess.99A.4.3.1Null(REST0)state.99A.4.3.2RestartRequest(REST1)state.99A.4.3.3Restart(REST2)state.100AnnexB(informative):Guidelinesfortheapplicationofthegenericproceduresforthedesignofindividualsupplementaryservices.101B.1Introduction.101B.2Separatemessagecategory.101B.2.1ApplicationoftheseparatemessagecategoriesfornewservicesdefinedbyITU-T.101B.2.2ApplicationoftheseparatemessagecategoryfornewservicesdefinedbyETSI.101B.2.3Applicationoftheseparatemessagecategoryforsupplementaryservicesdefinedbyotherorganizations.101B.3Commoninformationelementcategory.102B.3.1ApplicationofthecommoninformationelementcategoryforservicesdefinedbyITU-T.102B.3.2ApplicationofthecommoninformationelementcategoryforservicesdefinedbyETSI.102SIST EN 300 196-1 V1.3.2:2004

ETSIETSIEN300196-1V1.3.2(2001-06)7B.3.3Applicationofthecommoninformationelementcategoryforsupplementaryservicesdefinedbyotherorganizations.102B.4Notificationcategory.103B.4.1ApplicationofthenotificationcategoryforservicesdefinedbyITU-T.103B.4.2ApplicationofthenotificationcategoryforservicesdefinedbyETSI.103B.4.3Applicationofthenotificationcategoryforsupplementaryservicesdefinedbyotherorganizations.103AnnexC(informative):ASN.1subtypesandproposedmechanismforenhancementsofthefutureprotocol.104AnnexD(normative):FormaldefinitionofdatatypesusingITU-TRecommendationX.208.106D.1Componenttypes.106D.2Definitionofgenerallyapplicableerrors.108D.3Definitionofaddresstypes.109D.4DefinitionofQ.931informationelements.111D.5Formaldefinitionofbasicservices.111D.6Operationsanderrorsforexplicitchannelreservationcontrol.114D.7Operationforstatusrequestprocedure.115D.8Typesfornotificationprocedures.115AnnexE(normative):FormaldefinitionofdatatypesusingITU-TRecommendationX.680.117E.1Componenttypes.117E.2Definitionofgenerallyapplicableerrors.120E.3Definitionofaddresstypes.121E.4DefinitionofQ.931informationelements.123E.5Formaldefinitionofbasicservices.124E.6Explicitnetworkcontrolledchannelreservation.125E.7Statusrequestprocedure.126E.8ASN.1definitionofthenotificationindicator.127AnnexF(informative):FormaldefinitionofremoteoperationsnotationusingITU-TRecommendationX.208.128AnnexG(informative):FormaldefinitionofremoteoperationsnotationusingITU-TRecommendationX.680.129AnnexH(informative):Codingexamples.131H.1Codingofcomponenttypes.131H.2EmbeddingofexistingQ.931informationelements.133AnnexI(informative):Assignmentofobjectidentifiervalues.134AnnexJ(informative):IdentificationofchangesfromEN300196-1Version1.2.2tothepresentdocument.135J.1Editorialchanges.135J.2Technicalchanges.135J.2.1IntroductionoftheASN.1DefinitionsaccordingtoITU-TRecommendationsX.680andX.880.135J.2.2Newbearer-independentconnection-orientedtransportmechanismforthesupportofgeneralsignalling.136J.2.3GAT.136SIST EN 300 196-1 V1.3.2:2004

ETSIETSIEN300196-1V1.3.2(2001-06)8J.2.4Clarifications.136AnnexK(informative):Bibliography.137History.138SIST EN 300 196-1 V1.3.2:2004

ETSIETSIEN300196-1V1.3.2(2001-06)9IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinETSISR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinETSISR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSITechnicalCommitteeServicesandProtocolsforAdvancedNetworks(SPAN).Thepresentdocumentispart1ofamulti-partdeliverablecoveringtheIntegratedServicesDigitalNetwork(ISDN);Genericfunctionalprotocolforthesupportofsupplementaryservices;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol,asidentifiedbelow:Part1:"Protocolspecification";Part2:"ProtocolImplementationConformanceStatement(PICS)proformaspecification";Part3:"TestSuiteStructureandTestPurposes(TSS&TP)specificationfortheuser";Part4:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationfortheuser";Part5:"TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetwork";Part6:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthenetwork".ThepresentdocumentisanextendedandupdatedversionofETS300196-1(1993)anditsamendmentA1(1995).NationaltranspositiondatesDateofadoptionofthisEN:8June2001DateoflatestannouncementofthisEN(doa):30September2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31March2002DateofwithdrawalofanyconflictingNationalStandard(dow):31March2002SIST EN 300 196-1 V1.3.2:2004

ETSIETSIEN300196-1V1.3.2(2001-06)101ScopeThepresentdocumentspecifiesthefunctionalprotocolforthepan-EuropeanIntegratedServicesDigitalNetwork(ISDN)asprovidedbyEuropeanpublictelecommunicationsoperatorsfortheapplicationtoarangeofsupplementaryservicesattheTreferencepointorcoincidentSandTreferencepoint(asdefinedinITU-TRecommendationI.411[3])bymeansoftheDigitalSubscriberSignallingSystemNo.one(DSS1)protocol.ThefunctionalprotocolisbasedontheuseoftheFacilityinformationelementandtheFACILITYmessage,aswellasonotherspecificfunctionalmessagesspecifiedinclause11.1.Theprotocolissymmetrical,andisapplicabletoboththebasicandprimaryrateaccessstructures.Tobefunctionalthisprotocolrequiresknowledgeofsupplementaryservicessupportedbytheuserequipment.Thisfacilitatesuserequipmentoperationwithouthumaninterventionbydefiningsemanticsfortheprotocolelementswhichuserequipmentcanprocessonitsown.Theproceduresspecifiedinthepresentdocumentcanbeusedfor:-activationanddeactivation;-invocationandoperation;-interrogation;-statusrequest;and-statusnotification,ofsupplementaryservicesinassociationwithexistingcallsoroutsideanyexistingcall.Inaddition,thepresentdocumentspecifiesthegenericproceduresforthechannelreservationfunctionperformedbythenetworkasitisappliedbyseveralsupplementaryservices(e.g.callhold).Furthermore,thefunctionalsignallingproceduresthatsupportthedeliveryofnotificationsattheuser-networkinterfacearecovered.Theapplicationofthepresentdocumenttoindividualsupplementaryservicesisoutsidethescopeofthepresentdocumentandisdefinedinthosestandardswhichspecifytheindividualsupplementaryservices.Furtherpartsofthepresentdocumentspecifythemethodoftestingrequiredtoidentifyconformancetothepresentdocument.Thepresentdocumentisapplicabletoequipment,supportingsupplementaryservicesusingthefunctionalprotocol,tobeattachedateithersideofaTreferencepointorcoincidentSandTreferencepointwhenusedasanaccesstothepublicISDN.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.[1]ITU-TRecommendationI.112(1993):"VocabularyoftermsforISDNs".[2]ITU-TRecommendationI.210(1993):"PrinciplesoftelecommunicationservicessupportedbyanISDNandthemeanstodescribethem".SIST EN 300 196-1 V1.3.2:2004

ETSIETSIEN300196-1V1.3.2(2001-06)11[3]ITU-TRecommendationI.411(1993):"ISDNuser-networkinterfaces-Referenceconfigurations".[4]ITU-TRecommendationQ.9(1988):"Vocabularyofswitchingandsignallingterms".[5]ITU-TRecommendationX.208(1988):"SpecificationofAbstractSyntaxNotationOne(ASN.1)".[6]ITU-TRecommendationX.209(1988):"SpecificationofbasicencodingrulesforAbstractSyntaxNotationOne(ASN.1)".[7]ITU-TRecommendationX.219(1988):"Remoteoperations:Model,notationandservicedefinition".[8]ITU-TRecommendationX.229(1988):"Remoteoperations:Protocolspecification".[9]ITU-TRecommendationZ.100:"Specificationanddescriptionlanguage(SDL)".[10]ETSIEN300052-1:"IntegratedServicesDigitalNetwork(ISDN);
...