SIST EN 300 196-1 V1.2.2:2003
(Main)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
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
Amendment to add codepoints for new standardized services
Digitalno omrežje z integriranimi storitvami (ISDN) – Generični funkcijski protokol za podporo dopolnilnim storitvam – Protokol digitalne naročniške signalizacije št. 1 (DSS1) – 1. del: Specifikacija protokola
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); 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.2.2SIST EN 300 196-1 V1.2.2:2003en01-december-2003SIST EN 300 196-1 V1.2.2:2003SLOVENSKI
STANDARD
European Telecommunications Standards InstituteEN 300 196-1 V1.2.2 (1998-04)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Generic functional protocol for the support ofsupplementary services;Digital Subscriber Signalling System No. one (DSS1) protocol;Part 1: Protocol specificationSIST EN 300 196-1 V1.2.2:2003
EN 300 196-1 V1.2.2 (1998-04)2ReferenceREN/SPS-05097-1 (1tc90ipc.PDF)KeywordsISDN, DSS1, supplementary service, functional,generic, protocol, stage 3ETSI SecretariatPostal 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.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 300 196-1 V1.2.2:2003
EN 300 196-1 V1.2.2 (1998-04)3ContentsIntellectual Property Rights.7Foreword.71Scope.82Normative references.93Definitions.103.1General definitions.103.2Remote operations definitions.113.3Definition of procedures using the common information element approach.114Abbreviations.125Co-existence of generic protocols for the control of supplementary services.125.1Support of various generic protocols.125.2Co-existence of generic protocols.125.3Arrangements by which co-existence of protocols may be supported by a network.126General principles applied for the functional control of supplementary services.136.1Introduction.136.2Scope of the procedures.136.3Categories of procedures.136.4Supplementary service functions.137Control of supplementary services using the separate message approach.147.1Hold and Retrieve functions.147.1.1Messages for the Hold and Retrieve function.147.1.2Auxiliary states for the Hold and Retrieve function.147.2Hold procedures.167.2.1Initiating entity.167.2.1.1Normal operation.167.2.1.2Exceptional procedures.167.2.2Responding entity.167.2.2.1Normal operation.167.2.2.2Exceptional procedures.177.3Call Held auxiliary state.177.4Retrieve procedure.177.4.1Initiating entity.177.4.1.1Normal operation.177.4.1.2Exceptional procedures.187.4.2Responding entity.187.4.2.1Normal operation.187.4.2.2Exceptional procedures.187.5Parameter values (timers).197.6Clearing of a held call.198Control of supplementary services using the common information element approach.198.1General.198.1.1Introduction.198.1.2Scope of the procedures.208.2Application of operations.208.2.1Definitions.208.2.2Procedures for operations.208.2.2.1Invocation.208.2.2.2Return result.218.2.2.3Return error.218.2.2.4Reject.218.2.2.5Formal definition of Data Types.22SIST EN 300 196-1 V1.2.2:2003
EN 300 196-1 V1.2.2 (1998-04)48.3Transport of components.228.3.1Bearer-related transport.228.3.1.1Point-to-point transport mechanism.238.3.1.1.1Normal operation.238.3.1.1.2Exceptional procedures.238.3.1.2Broadcast transport mechanism.248.3.1.2.1Normal operation.248.3.1.2.2Exceptional procedures.248.3.2Bearer-independent transport.248.3.2.1Point-to-point transport mechanism (connection-oriented).248.3.2.1.1Connection establishment.258.3.2.1.2Data transfer phase.258.3.2.1.3Connection release.268.3.2.2Point-to-point transport mechanism (connectionless).278.3.2.2.1Normal operation.278.3.2.2.2Exceptional procedures.278.3.2.3Broadcast transport mechanism (connection-oriented).288.3.2.4Broadcast transport mechanism (connectionless).288.3.2.4.1Normal operation.288.3.2.4.2Exceptional procedures.288.4Error procedures.298.4.1Component error handling.298.4.2Error handling of mistyped data values.298.5Response to multiple supplementary service invocations.299Generic notification procedures.299.1General.299.2Categories of notification procedures.309.3Transport of bearer-related notifications.309.3.1Normal operation.309.3.2Exceptional procedures.319.4Transport of bearer-independent notifications.319.4.1Normal operation.319.4.2Exceptional procedures.3110Other generic procedures.3110.1Network-side channel reservation function.3110.1.1Implicit reservation.3210.1.1.1Implicit reservation creation.3210.1.1.2Implicit reservation use.3310.1.1.3Implicit reservation cancellation.3310.1.2Explicit reservation.3310.1.2.1Explicit reservation control.3310.1.2.2Explicit reservation management.3410.1.2.3Explicit reservation cancellation.3510.1.3Effect of reservation on channel selection for a new call.3510.1.4Interaction between implicit and explicit network-side channel reservation functions on the same CEI.3610.2Generic procedures for supplementary service management.3610.2.1Introduction.3610.2.2Activation.3710.2.2.1Normal operation.3710.2.2.2Activation exceptional procedures.3710.2.3Deactivation.3810.2.3.1Normal operation.3810.2.3.2Deactivation exceptional procedures.3810.2.4Interrogation.3910.2.4.1Normal operation.3910.2.4.2Interrogation exceptional procedures.3910.2.5Status notification.4010.2.5.1Normal operation.4010.2.5.2Exceptional procedures.40SIST EN 300 196-1 V1.2.2:2003
EN 300 196-1 V1.2.2 (1998-04)510.2.6State definitions.4010.2.7Parameter values (timers).4010.3Generic status request procedure.4110.3.1Introduction.4110.3.2Normal operation.4110.3.3Exceptional procedures.4310.3.4Parameter values (timers).4311Coding requirements.4311.1Message functional definitions and content.4311.1.1Additional messages for bearer-related supplementary service control.4411.1.1.1FACILITY.4411.1.1.2HOLD.4411.1.1.3HOLD ACKNOWLEDGE.4511.1.1.4HOLD REJECT.4511.1.1.5RETRIEVE.4511.1.1.6RETRIEVE ACKNOWLEDGE.4611.1.1.7RETRIEVE REJECT.4611.1.2Messages for bearer-independent supplementary service control.4611.1.2.1FACILITY.4611.1.2.2REGISTER.4711.1.2.3RELEASE.4711.1.2.4RELEASE COMPLETE.4811.1.2.5STATUS.4811.1.2.6STATUS ENQUIRY.4811.1.3Messages used with the dummy call reference.4911.1.3.1FACILITY.4911.1.3.2NOTIFY.4911.2General message format and information element coding.5011.2.1Message type.5011.2.2Other information elements.5011.2.2.1Facility.5011.2.2.1.1Treatment of existing Q.931 information elements as parameters.5111.2.2.2Notification indicator.5211.2.2.3Call state.5311.2.2.4Extended facility information element.53Annex A (normative):Dynamic descriptions.55A.1Dynamic description of the Hold and Retrieve functions.55A.2Dynamic description of the status request procedure.66A.3Dynamic description of the supplementary service management function.70Annex B (informative):Guidelines for the application of the generic procedures for thedesign of individual supplementary services.79B.1Introduction.79B.2Separate message category.79B.2.1Application of the separate message categories for new services defined by ITU-T.79B.2.2Application of the separate message category for new services defined by ETSI.79B.2.3Application of the separate message category for supplementary services defined by other organizations.79B.3Common information element category.80B.3.1Application of the common information element category for services defined by ITU-T.80B.3.2Application of the common information element category for services defined by ETSI.80B.3.3Application of the common information element category for supplementary services defined by otherorganizations.80B.4Notification category.81B.4.1Application of the notification category for services defined by ITU-T.81B.4.2Application of the notification category for services defined by ETSI.81SIST EN 300 196-1 V1.2.2:2003
EN 300 196-1 V1.2.2 (1998-04)6B.4.3Application of the notification category for supplementary services defined by other organizations.81Annex C (informative):ASN.1 subtypes and proposed mechanism for enhancements of thefuture protocol.82Annex D (normative):Formal definition of data types.83D.1Component types.83D.2Definition of generally applicable errors.85D.3Definition of address types.86D.4Definition of Q.931 information elements.88D.5Formal definition of basic services.88D.6Operations and errors for explicit channel reservation control.91D.7Operation for status request procedure.92D.8Types for notification procedures.93Annex E (informative):Formal definition of remote operations notation.94Annex F (informative):Coding examples.95F.1Coding of component types.95F.2Embedding of existing Q.931 information elements.97Annex G (informative):Assignment of object identifier values.98History.99SIST EN 300 196-1 V1.2.2:2003
EN 300 196-1 V1.2.2 (1998-04)7Intellectual 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 ETR 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect ofETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on the ETSIWeb server (http://www.etsi.fr/ipr).Pursuant to the ETSI Interim IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. Noguarantee can be given as to the existence of other IPRs not referenced in ETR 314 (or the updates onhttp://www.etsi.fr/ipr) 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 1 of a multi-part standard covering the Digital Subscriber Signalling System No. one(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) generic functional protocol for thesupport 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".The present document is an extended and updated version of ETS 300 196-1 (1993) and its amendment A1 (1995).National transposition datesDate of adoption of this EN:3 April 1998Date of latest announcement of this EN (doa):31 July 1998Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 January 1999Date of withdrawal of any conflicting National Standard (dow):31 January 1999SIST EN 300 196-1 V1.2.2:2003
EN 300 196-1 V1.2.2 (1998-04)81ScopeThis first part of EN 300 196 specifies the functional protocol for the pan-European Integrated Services Digital Network(ISDN) as provided by European public telecommunications operators for the application to a range of supplementaryservices at the T reference point or coincident S and T reference point (as defined in ITU-T Recommendation I.411 [3])by means of the Digital Subscriber Signalling System No. one (DSS1) protocol.The functional protocol is based on the use of the Facility information element and the FACILITY message, as well ason other specific functional messages specified in subclause 11.1. The protocol is symmetrical, and is applicable to boththe basic and primary rate access structures.To be functional this protocol requires knowledge of supplementary services supported by the user equipment. Thisfacilitates user equipment operation without human intervention by defining semantics for the protocol elements whichuser equipment can process on its own.The procedures specified in the present document can be used for:-activation and deactivation;-invocation and operation;-interrogation;-status request; and-status notification,of supplementary services in association with existing calls or outside any existing call.In addition, the present document specifies the generic procedures for the channel reservation function performed by thenetwork as it is applied by several supplementary services (e.g. call hold).Furthermore, the functional signalling procedures that support the delivery of notifications at the user-network interfaceare covered.The application of the present document to individual supplementary services is outside the scope of the presentdocument and is defined in those standards which specify the individual supplementary services.Further parts of the present document specify the method of testing required to identify conformance to the presentdocument.The present document is applicable to equipment, supporting supplementary services using the functional protocol, to beattached at either side of a T reference point or coincident S and T reference point when used as an access to the publicISDN.SIST EN 300 196-1 V1.2.2:2003
EN 300 196-1 V1.2.2 (1998-04)92Normative 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]ITU-T Recommendation I.112 (1993): "Vocabulary of terms for ISDNs".[2]ITU-T Recommendation I.210 (1993): "Principles of telecommunication services supported by anISDN and the means used to describe them".[3]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - Reference configurations".[4]CCITT Recommendation Q.9 (1988): "Vocabulary of switching and signalling terms".[5]CCITT Recommendation X.208 (1988): "Specification of Abstract Syntax Notation One(ASN.1)".[6]CCITT Recommendation X.209 (1988): "Specification of basic encoding rules for Abstract SyntaxNotation One (ASN.1)".[7]CCITT Recommendation X.219 (1988): "Remote operations: Model, notation and servicedefinition".[8]CCITT Recommendation X.229 (1988): "Remote operations: Protocol specification".[9]ITU-T Recommendation Z.100: "Specification and Description Language (SDL)".[10]ETS 300 052-1: "Integrated Services Digital Network (ISDN); Multiple Subscriber Number(MSN) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;Part 1: Protocol specification".[11]ETS 300 061-1: "Integrated Services Digital Network (ISDN); Subaddressing (SUB)supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 1:Protocol specification".[12]ETS 300 122-1: "Integrated Services Digital Network (ISDN); Generic keypad protocol for thesupport of supplementary services; Digital Subscriber Signalling System No. one (DSS1) protocol;Part 1: Protocol specification".[13]EN 300 267-1: "Integrated Services Digital Network (ISDN); Telephony 7 kHz, videotelephonyaudiographic conference and videoconference teleservices; Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Part 1: Protocol specification".[14]ETS 300 402-2: "Integrated Services Digital Network (ISDN); Digital Subscriber SignallingSystem No. one (DSS1) protocol; Data link layer; Part 2: General protocol specification".[15]EN 300 403-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 1:Protocol specification".SIST EN 300 196-1 V1.2.2:2003
EN 300 196-1 V1.2.2 (1998-04)103DefinitionsThe following definitions apply:3.1General definitionsall services: If for the control of supplementary services the parameter basic service is set to "all services", then all thebasic services shall be affected that the user is subscribed to, and for which the supplementary service applies and issubscribed to, at the point in time that the request is received.auxiliary state: A state as defined in subclause 7.1.2. An auxiliary state may exist for a call reference in parallel withthe call state.basic access: See CCITT Recommendation Q.9 [4], definition 1551.basic service: A bearer service or teleservice. The terms "bearer service" and "teleservice" are defined in ITU-TRecommendation I.112 [1], definitions 202 and 203.call control message: A message as defined in EN 300 403-1 [15], subclause 3.1, which on sending or receipt causes achange of the call state at either the network or the user. Call control messages also include the INFORMATIONmessage and PROGRESS message.call reference: (excluding dummy call reference) an identifier of a signalling transaction. The signalling transactionmay either be bearer related, in which case the signalling transaction can be used to control that bearer, or bearerindependent, in which case there is no bearer associated with that signalling transaction. Where there is only one bearerrequired for a call, then the call reference of the associated bearer-related signalling transaction may be used to identifythe call.call state: A state as defined in EN 300 403-1 [15], subclause 2.1,for either the user or the network as appropriate. Acall state may exist for each call reference value (and for each additional responding Connection Endpoint Identifier(CEI) in the incoming call states).call: See CCITT Recommendation Q.9 [4], definition 2201.component: Data structure as defined in clause D.1.connection: See CCITT Recommendation Q.9 [4], definition 0011. In the present document the use of this term is takento include a bearer and its associated control signalling.Data Link Connection Endpoint Identifier; Connection Endpoint Identifier (CEI): Identifier used by a layer 3protocol entity to address its peer entity.dummy call reference: A null value indicating that the message is not applicable to an identified signalling transaction.Other rules specify the association of DSS1 protocol entities.functional protocol: A functional protocol consists of a sequence of functional information elements. A functionalinformation element requires a degree of intelligent processing by a terminal in either generation or analysis.initiator: An entity (user or network) requesting establishment of a signalling connection between an initiator and theresponder.Integrated Services Digital Network (ISDN): See ITU-T Recommendation I.112 [1], definition 308.network: The DSS1 protocol entity at the network side of the user-network interface.point-to-point configuration: See EN 300 403-1 [15]point-to-multipoint configuration: See EN 300 403-1 [15]primary rate access: See CCITT Recommendation Q.9 [4], definition 1552.responder: The entity (user or network) responding to a request from an initiator on establishing a signallingconnection.SIST EN 300 196-1 V1.2.2:2003
EN 300 196-1 V1.2.2 (1998-04)11service; telecommunication service: See ITU-T Recommendation I.112 [1], definition 201.signalling connection: An association of DSS1 protocol entities using the bearer-independent supplementary serviceprocedure with the connection-oriented transport mechanism.stimulus protocol: A stimulus protocol consists of a sequence of stimulus information elements. A stimulus informationelement is generated as a result of a single event at the user-network interface or contains a basic instruction from thenetwork to be executed by the user.supplementary service: See ITU-T Recommendation I.210 [2], subclause 2.4.user: The DSS1 protocol entity at the user side of the user-network interface.3.2Remote operations definitionsThe common information element category makes use of the following terms defined in CCITT RecommendationX.219 [7]:-remote operation;-operation;-operation classes (class 1 to class 5);-association (initiator; responder);-invoking (application entity; invoker).invoke component: See subclause 8.2.2.1. Where reference is made to a "xxxx" invoke component, an invokecomponent is meant with its operation value set to the value of the operation "xxxx".return result component: See subclause 8.2.2.2. Where reference is made to a "xxxx" return result component, a returnresult component is meant which is related to a "xxxx" invoke component.return error component: See subclause 8.2.2.3. Where reference is made to a "xxxx" return error component, a returnerror component is meant which is related to a "xxxx" invoke component.reject component: See subclause 8.2.2.4.3.3Definition of procedures using the common informationelement approachbearer-related transport mechanism: A procedure tied to the procedures for basic call control and tied to aconnection in progress, active or in the clearing phase. The call reference used by the basic call control procedure isadopted by the bearer-related service invocations to correlate with the appropriate basic call control transaction.bearer-independent transport mechanism: A procedure independent of the procedures for basic call control and notcorrelated to a connection.connection-oriented transport mechanism: A mechanism requiring the establishment of a data link and a transportassociation between the service requesting entity and the service provider. It provides a facility to access commoninformation element category operations where success and/or failure reporting is required. It provides a call referencewithin the transport association as a means to associate uniquely among the related transport messages.connectionless transport mechanism: A mechanism where no transport association exists but a single transportmessage transfer is provided using the dummy call reference.SIST EN 300 196-1 V1.2.2:2003
EN 300 196-1 V1.2.2 (1998-04)124AbbreviationsThe following abbreviations apply:ASN.1Abstract Syntax Notation OneBERBasic Encoding RulesCEIConnection Endpoint IdentifierDSS1Digital Subscriber Signalling System No. oneISDNIntegrated Services Digital NetworkLSBLeast Significant BitMSBMost Significant BitROSERemote Operations Service ElementSDLSpecification and Description Language5Co-existence of generic protocols for the control ofsupplementary services5.1Support of various generic protocolsNetworks may support more than one generic protocol for the control of supplementary services, e.g. the keypadprotocol and the functional protocol. The support of multiple generic protocols is a network option. Users shall beinformed by the service provider at subscription time of the supplementary services available, and of the genericprotocols supported on their access.5.2Co-existence of generic protocolsAs a general rule, the functional protocol shall be used unless the network specifies the use of a stimulus protocol for thecontrol of certain supplementary services.Networks may support one or more of the generic protocols; it is a network option as to whether one or more genericprotocols are supported on a given access.In general, the keypad protocol, as defined in ETS 300 122-1 [12], has only local significance while the functionalprotocol may have other than local significance.For a given call instance, the protocol applied at a local interface may be different from the one applied at a remoteuser's interface. For example, one of the stimulus protocols may be used at the requesting user's interface, while afunctional protocol may be applied at the remote user's interface.5.3Arrangements by which co-existence of protocols may besupported by a networkSome networks may support only one of the generic protocols per user access for the control of supplementary services.Other networks may choose to support a single generic protocol for the control of supplementary services, depending onthe user-network interface type (e.g. keypad on the basic access, functional on the basic access and primary rate access).This has to be arranged at subscription time.Networks supporting multiple generic protocols per access in the user-to-network direction will implicitly recognize theprotocol option chosen by the user on the basis of the received message type or information element type.Networks supporting multiple generic protocols per access in the network-to-user direction (i.e. at the remote-userinterface) may choose to apply a particular protocol depending on the supplementary services involved.SIST EN 300 196-1 V1.2.2:2003
EN 300 196-1 V1.2.2 (1998-04)136General principles applied for the functional control ofsupplementary services6.1IntroductionThis clause specifies the general pr
...
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...