SIST ETS 300 364 E1:2005

• Abstract:

  Do not disturb and do not disturb override supplementary services at Q. See DTR/ECMA-0002 (ECMA-TR/SVC) for service description. See ENV41005 for definition of stage 3. See ENV41004 for definition of Q reference point. To contain PICS proforma.

• Status: Published
• Publication Date: 30-Apr-2005
• ICS: 33.040.35 - Telephone networks
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-May-2005
• Due Date: 01-May-2005
• Completion Date: 01-May-2005
• Mandate: T-75C.3
• Ref Project: ETSI ETS 300 364 ed.1 (1994-11) - Private Telecommunication Network (PTN); Inter-exchange signalling protocol; Do not disturb and do not disturb override supplementary services

SIST ETS 300 364 E1:2005 is the Slovenian adoption of ETS 300 364 Edition 1. It specifies the Q reference point signalling protocol for the Do Not Disturb (DND) and Do Not Disturb Override (DNDO) supplementary services in Private Telecommunication Networks (PTNs). It is written for PTNX implementations that need to support call rejection, override, remote control, and conformance checking.

What does SIST ETS 300 364 E1:2005 specify?

SIST ETS 300 364 E1:2005 specifies how PTNXs signal SS-DND and SS-DNDO at the Q reference point within a PTN. In practice, it tells implementers how a call is rejected when DND is active, how override can be attempted, and how remote activation, deactivation, and interrogation are carried out.

The scope is limited to the signalling protocol and its operation on top of basic circuit switched call control. The document states that interactions with other supplementary services are outside its scope, while path retention for DNDO is handled in a normative annex.

The document is organized into six main clauses and five annexes.

Annex	What it covers
Annex A	Normative path retention mechanism used for SS-DNDO with retained connections
Annex B	Normative Protocol Implementation Conformance Statement (PICS) proforma
Annex C	Informative imported ASN.1 definitions relating to numbers
Annex D	Informative examples of message sequences
Annex E	Informative SDL representations of procedures

What are the key requirements of SIST ETS 300 364 E1:2005?

The standard’s core requirements are in Clause 6 and Annex A. They define what each PTNX role does, how the protocol is coded, which timers apply, and when DND may be overridden.

SS-DND behaviour at the terminating side

SS-DND lets a served user cause the PTN to reject incoming calls addressed to the served user’s PTN number, either for all subscribed basic services or only some of them. The calling user receives an indication, and the served user’s outgoing service is not affected.

At the Terminating PTNX, the standard allows two visible outcomes: the call can be cleared with a rejection cause, or an in-band tone or announcement can be connected before release. In practice, this means the terminating node must be able to reject the call cleanly and optionally give the caller a local announcement.

SS-DNDO depends on protection and capability levels

SS-DNDO allows a calling user to override active SS-DND if the served user’s protection level allows it. The decision is based on comparing the served user’s DND protection level (DNDPL) with the calling side’s DNDO capability level (DNDOCL).

For SS-DND, the subscription parameter DNDPL ranges from 0 to 3, with 0 meaning no protection and 3 meaning total protection against DNDO. For SS-DNDO, DNDOCL ranges from 1 to 3. In practice, an implementation must expose the configured level and apply it consistently when a call encounters DND.

Provisioning is per PTN number and per basic service

Both SS-DND and SS-DNDO are provided or withdrawn after agreement with the service provider. They are subscribed per PTN number and per basic service, and the subscription parameters may apply either per service or across all subscribed services.

This matters because the same user number can have different DND or DNDO behaviour for different basic services. A system integrator or operator therefore has to provision the service at the right service granularity.

Call-independent control uses defined PTNX roles and states

The standard distinguishes terminating, originating, activating, deactivating, interrogating, served user, and transit PTNX behaviour. Remote activation, deactivation, and interrogation use call-independent signalling connections, while the served user PTNX validates the request and returns a result or an error.

Clause 6 also defines the operational states for these procedures, such as DND-aWait, DND-dWait, DND-iWait, and DND-sIdle. In practice, these states guide implementation logic, timer handling, and error recovery.

Coding is through Facility and Notification indicator information elements

Clause 6.3 requires the operations to be coded as ASN.1 and carried in the Facility information element. The notification is coded in the Notification indicator information element, and the message handling follows ETS 300 239 and ETS 300 172.

The implementation must also use the correct NFE destinationEntity value for invoke APDUs, and it must apply the specified Interpretation APDU rules. For implementers, this is the part that determines interoperability on the wire.

Timers protect unanswered operations

Clause 6.9 defines timer protection for unanswered requests. T1, T2, T3, and T4 all have a minimum value of 15 s, each associated with a different activation, deactivation, interrogation, or DNDO execution step.

Annex A adds timer PRT1 for path retention, with a minimum value of 60 s. These timers prevent the protocol from waiting indefinitely when a remote PTNX does not respond.

Path retention supports DNDO without a new call setup

Annex A defines path retention as a generic mechanism that keeps the network connection available so that a supplementary service can be invoked later in the same call flow. For SS-DNDO, the Originating PTNX can request retention with pathRetain, and the Terminating PTNX later reports availability with serviceAvailable.

This mechanism matters when DNDO is negotiated after call setup rather than immediately. It allows the network to pause call progress, decide whether override is allowed, and then continue or fall back to DND handling.

What terms does SIST ETS 300 364 E1:2005 define?

• PTNX - A Private Telecommunication Network Exchange, the switching node used within a PTN.
• SS-DND - Supplementary Service Do Not Disturb, which lets the served user block incoming calls to the PTN number.
• SS-DNDO - Supplementary Service Do Not Disturb Override, which lets a call proceed despite active SS-DND if the levels permit it.
• DNDPL - DND protection level, the subscription parameter that sets how strongly a user is protected against override.
• DNDOCL - DNDO capability level, the subscription parameter that states what override capability the calling side has.
• Path retention - The mechanism that keeps the connection available so a supplementary service can be invoked without a fresh connection setup.
• PICS - Protocol Implementation Conformance Statement, the checklist used to declare which protocol options an implementation supports.

Who uses SIST ETS 300 364 E1:2005?

PTN equipment vendors use this standard when they implement signalling in PTNXs. It is also used by protocol engineers, system integrators, and gateway designers who need SS-DND and SS-DNDO to work across interconnected nodes.

Quality managers, buyers, and testers use Annex B because it turns the specification into a conformance checklist. Service providers use it when they provision DND and DNDO behaviour per number and per basic service, and when they assess interoperability with public ISDNs or non-ISDN networks.

Which standards are used with SIST ETS 300 364 E1:2005?

Standard	What it contributes
DTR/ECMA-0002 (ECMA-TR/SVC)	Service description for the supplementary service set referenced in the scope
ENV 41005	Definition of stage 3 used to frame this specification
ENV 41004	Definition of the Q reference point
IS 11579	Reference configuration for PISN exchanges and the Q reference point context
ETS 300 172	Basic circuit mode call control and basic call messages
ETS 300 239	Generic supplementary service control procedures, coding rules, notifications, and call-independent signalling
ETS 300 363	Stage 1 and stage 2 service specification for SS-DND and SS-DNDO
ETS 300 387	Method used for specifying basic and supplementary services
ETS 300 196-1	Source for imported ASN.1 elements such as errors, BasicService, and PartyNumber
ENV 41007-1	Definitions for PTN terms such as PTNX, terminal, user, and public ISDN
CCITT Rec. I.112	Vocabulary for signalling
CCITT Rec. I.210	Supplementary service terminology and principles
CCITT Rec. Z.100	Specification and Description Language (SDL) used in the annex diagrams

What does the SIST ETS 300 364 E1:2005 document contain?

The document contains ASN.1 definitions for SS-DND and SS-DNDO operations and notifications in Clause 6.3, including the coded arguments, results, and enumerations used on the network. It also contains state definitions and signalling procedures for each PTNX role, which are the main implementation guide for real protocol behaviour.

Annex A provides the path retention mechanism, including its states, procedures, timer, and interworking notes. Annex B gives a full PICS proforma for SS-DND and SS-DNDO, which is what suppliers use to declare conformance and what testers use to plan checks.

Annex C lists imported ASN.1 number-related definitions, Annex D shows typical message sequences, and Annex E gives SDL representations of the procedures. Together, these annexes support design, implementation, interoperability testing, and conformance assessment.

SLOVENSKI STANDARD
01-maj-2005
Zasebno telekomunikacijsko omrežje (PTN) – Medcentralni signalizacijski protokol
- Dopolnilna storitev: ne moti in razveljavi storitev ne moti
Private Telecommunication Network (PTN); Inter-exchange signalling protocol; Do not
disturb and do not disturb override supplementary services
Ta slovenski standard je istoveten z: ETS 300 364 Edition 1
ICS:
33.040.35 Telefonska omrežja Telephone networks
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 364
TELECOMMUNICATION November 1994
STANDARD
Source: ETSI TC-ECMA Reference: DE/ECMA-00054
UDC: 33.080
Key words: CCS, DND, PTN, QSIG, stage 3, supplementary service, ECMA-194
Private Telecommunication Network (PTN);
Inter-exchange signalling protocol
Do not disturb and do not disturb override
supplementary services
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail]
Tel.: [phone] - Fax: [phone]
Copyright Notification: No 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 1994. All rights reserved.
New presentation - see History box

Page 2
ETS 300 364: November 1994
Whilst 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.

Page 3
ETS 300 364: November 1994
Contents
Foreword.7
1 Scope .9
2 Conformance .9
3 References .9
4 Definitions .10
4.1 External definitions.10
4.2 Activating PTNX.10
4.3 Deactivating PTNX .11
4.4 Inter-PTNX link.11
4.5 Interrogating PTNX.11
4.6 Path retention.11
4.7 Served user PTNX.11
5 List of acronyms .11
6 Signalling protocol for the support of SS-DND and SS-DNDO.11
6.1 SS-DND and SS-DNDO description .11
6.2 SS-DND and SS-DNDO operational requirements .12
6.2.1 Provision/withdrawal .12
6.2.1.1 Provision/withdrawal of SS-DND.12
6.2.1.2 Provision/withdrawal of SS-DNDO.12
6.2.2 Requirements on the Terminating PTNX.12
6.2.3 Requirements on the Originating PTNX .12
6.2.4 Requirements on the Activating PTNX.13
6.2.5 Requirements on the Deactivating PTNX .13
6.2.6 Requirements on the Interrogating PTNX.13
6.2.7 Requirements on a SS-DND Served User PTNX.13
6.2.8 Requirements on a Transit PTNX .13
6.3 SS-DND and SS-DNDO coding requirements .13
6.3.1 Operations.13
6.3.2 Notifications.18
6.3.3 Information elements.19
6.3.3.1 Facility information element .19
6.3.3.2 Notification indicator information element .19
6.3.3.3 Other information elements.19
6.3.4 Messages .19
6.4 SS-DND and SS-DNDO state definitions.19
6.4.1 State at the Terminating PTNX.19
6.4.1.1 DND-tIdle .19
6.4.2 States at the Originating PTNX.19
6.4.2.1 DNDO-oIdle .19
6.4.2.2 DNDO-oAwaitExecResult .20
6.4.3 States at the Activating PTNX .20
6.4.3.1 DND-aIdle .20
6.4.3.2 DND-aWait.20
6.4.4 States at the Deactivating PTNX.20

Page 4
ETS 300 364: November 1994
6.4.4.1 DND-dIdle . 20
6.4.4.2 DND-dWait. 20
6.4.5 States at the Interrogating PTNX. 20
6.4.5.1 DND-iIdle . 20
6.4.5.2 DND-iWait. 20
6.4.6 State at the SS-DND Served User PTNX. 20
6.4.6.1 DND-sIdle. 21
6.5 SS-DND signalling procedures. 21
6.5.1 Actions at the Terminating PTNX. 21
6.5.1.1 Normal procedures . 21
6.5.1.2 Exceptional procedures . 21
6.5.2 Actions at the Originating PTNX . 22
6.5.2.1 Normal procedures . 22
6.5.2.2 Exceptional procedures . 22
6.5.3 Actions at the Activating PTNX. 22
6.5.3.1 Normal procedures . 22
6.5.3.2 Exceptional procedures . 22
6.5.4 Actions at the Deactivating PTNX . 22
6.5.4.1 Normal procedures . 23
6.5.4.2 Exceptional procedures . 23
6.5.5 Actions at the Interrogating PTNX. 23
6.5.5.1 Normal procedures . 23
6.5.5.2 Exceptional procedures . 24
6.5.6 Actions at the Served User PTNX. 24
6.5.6.1 Normal procedures . 24
6.5.6.1.1 Remote activation. 24
6.5.6.1.2 Remote deactivation . 24
6.5.6.1.3 Remote interrogation . 24
6.5.6.2 Exceptional procedures . 24
6.5.6.2.1 Remote activation of SS-DND . 24
6.5.6.2.2 Remote deactivation of SS-DND. 25
6.5.6.2.3 Remote interrogation of SS-DND. 25
6.5.7 Actions at a Transit PTNX . 25
6.6 SS-DNDO signalling procedures . 25
6.6.1 Actions at the Terminating PTNX. 25
6.6.1.1 Normal procedures . 25
6.6.1.2 Exceptional procedures . 26
6.6.2 Actions at the Originating PTNX . 26
6.6.2.1 Normal procedures . 26
6.6.2.1.1 Without path retention. 26
6.6.2.1.2 With path retention. 26
6.6.2.2 Exceptional procedures . 27
6.6.3 Actions at a Transit PTNX . 27
6.7 Impact of interworking with public ISDNs . 27
6.7.1 SS-DND . 27
6.7.1.1 Incoming calls . 27
6.7.1.2 Outgoing calls . 27
6.7.2 SS-DNDO. 27
6.7.2.1 Incoming calls . 27
6.7.2.2 Outgoing calls . 27
6.8 Impact of interworking with non-ISDNs. 28
6.8.1 SS-DND . 28
6.8.2 SS-DNDO. 28
6.9 SS-DND and SS-DNDO parameter values (timers). 28
6.9.1 Timer T1. 28
6.9.2 Timer T2. 28

Page 5
ETS 300 364: November 1994
6.9.3 Timer T3 .28
6.9.4 Timer T4 .28
Annex A (normative): Signalling protocol for the support of path retention .29
A.1 Path Retention description.29
A.2 Path Retention operational requirements .29
A.2.1 Requirements on the Originating PTNX .29
A.2.2 Requirements on the Terminating PTNX.29
A.2.3 Requirements on a Transit PTNX .29
A.3 Path Retention coding requirements .29
A.3.1 Operations.29
A.3.2 Information elements.30
A.3.3 Messages .30
A.4 Path Retention state definitions .30
A.4.1 States at the Originating PTNX.30
A.4.1.1 PRTO-Idle.30
A.4.1.2 PRTO-Requested .30
A.4.1.3 PRTO-Retained.30
A.4.1.4 PRTO-Invoking.30
A.4.2 States at the Terminating PTNX .30
A.4.2.1 PRTT-Idle.30
A.4.2.2 PRTT-Requested.30
A.4.2.3 PRTT-Retained .31
A.4.2.4 PRTT-Invoking.31
A.5 Path Retention signalling procedures for invocation and operation.31
A.5.1 Actions at the Originating PTNX.31
A.5.2 Actions at the Terminating PTNX.31
A.5.3 Actions at a Transit PTNX.32
A.6 Path Retention impact of interworking with public ISDNs.32
A.7 Path Retention impact of interworking with non-ISDNs .33
A.8 Path Retention parameter values (timers) .33
A.9 Specification and Description Language (SDL) - Representation of procedures (informative).34
A.9.1 SDL representation of Path Retention at the Originating PTNX.35
A.9.2 SDL representation of Path Retention at the Terminating PTNX .37
Annex B (normative): Protocol Implementation Conformance Statement (PICS) proforma.39
B.1 Introduction .39
B.2 Instructions for completing the PICS proforma.39
B.2.1 General structure of the PICS proforma.39
B.2.2 Additional information.40
B.2.3 Exception information.40
B.3 PICS proforma for SS-DND of ETS 300 364.40
B.3.1 Implementation identification .40
B.3.2 Protocol summary .41
B.3.3 General.41
B.3.4 Procedures.42
B.3.5 Coding.43
B.3.6 Timers .43
B.4 PICS proforma for SS-DNDO of ETS 300 364.44
B.4.1 Implementation identification .44
B.4.2 Protocol summary .44
B.4.3 General.45
B.4.4 Procedures.45
B.4.5 Coding.46
B.4.6 Timers .46

Page 6
ETS 300 364: November 1994
Annex C (informative): Imported ASN.1 definitions relating to numbers . 47
Annex D (informative): Examples of message sequences . 49
Annex E (informative): Specification and Description Language (SDL) representation of procedures. 54
E.1 SDL representation of SS-DND and SS-DNDO at a Terminating PTNX . 55
E.2 SDL representation of SS-DNDO at an Originating PTNX. 56
E.3 SDL representation of SS-DND at an Activating PTNX . 57
E.4 SDL representation of SS-DND at a Deactivating PTNX. 58
E.5 SDL representation of SS-DND at an Interrogating PTNX . 59
E.6 SDL representation of SS-DND at a Served User PTNX . 60
History . 61

Page 7
ETS 300 364: November 1994
Foreword
This European Telecommunication Standard (ETS) has been produced by the European Computer Manufacturers
Association (ECMA) on behalf of its members and those of the European Telecommunications Standards Institute
(ETSI).
This ETS is one of a series of standards defining services and signalling protocols applicable to Private
Telecommunication Networks (PTNs). The series uses the ISDN concepts as developed by the ITU-T (formerly CCITT)
and is also within the framework of standards for open systems interconnection as defined by ISO.
This ETS specifies the signalling protocol for use at the Q reference point in support of the Do Not Disturb (DND) and
Do Not Disturb Override (DNDO) supplementary services.
The ETS is based upon the practical experience of ECMA member companies and the results of their active and
continuous participation in the work of ISO, ITU-T (formerly CCITT), ETSI and other international and national
standardisation bodies. It represents a pragmatic and widely based consensus.
This ETS was produced by ECMA using the ECMA guidelines for the production of standards and using the ECMA
stylesheet. In order to avoid undue delays in the approval process for this ETS it has been agreed that this ETS will not
be converted to the ETSI stylesheet.
Transposition dates
Date of latest announcement of this ETS (doa): 28 February 1995
Date of latest publication of new National Standard 31 August 1995
or endorsement of this ETS (dop/e):
Date of withdrawal of any conflicting National Standard (dow): 31 August 1995

Page 8
ETS 300 364: November 1994
Blank page
Page 9
ETS 300 364: November 1994
1 Scope
This European Telecommunication Standard (ETS) specifies the signalling protocol for the support of the Do
Not Disturb and Do Not Disturb Override supplementary services (SS-DND and SS-DNDO) at the Q reference
point between Private Telecommunication Network Exchanges (PTNXs) connected together within a Private
Telecommunication Network (PTN).
SS-DND is a supplementary service which enables a served user to cause the PTN to reject any calls, or just
those associated with a specified basic service, addressed to the served user's PTN number. The calling user is
given an indication. Incoming calls are rejected as long as the service is active. The served user's outgoing
service is unaffected.
SS-DNDO is a supplementary service which enables a served user to override SS-DND at a called number; that
is, to allow the call to proceed as if the called user had not activated SS-DND.
The Q reference point is defined in IS 11579.
Service specifications are produced in three stages and according to the method specified in ETS 300 387. This
ETS contains the stage 3 specification for the Q reference point and satisfies the requirements identified by the
stage 1 and stage 2 specifications in ETS 300 363.
The signalling protocols for SS-DND(O) operate on top of the signalling protocol for basic circuit switched call
control, as specified in ETS 300 172, and use certain aspects of the generic procedures for the control of
supplementary services specified in ETS 300 239.
The impact on the protocol of interactions between SS-DND and other supplementary services and SS-DNDO
and other supplementary services is outside the scope of this ETS.
This ETS is applicable to PTNXs which can interconnect to form a PTN.
2 Conformance
In order to conform to this ETS, a PTNX shall satisfy the requirements identified in the Protocol
Implementation Conformance Statement (PICS) proforma in annex B applies.
3 References
IS 11579 Information Technology - Telecommunications and Information Exchange Between Systems
- Private Integrated Services Network - Reference Configurations for PISN Exchanges
(1993).
ETS 300 171 Private Telecommunication Network (PTN); Specification, functional model and
information flows, Control aspects of circuit mode basic services (1993).
ETS 300 172 Private Telecommunication Network (PTN); Inter-exchange signalling protocol, Circuit
mode basic services (1993).
ETS 300 196-1 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 (1993).
ETS 300 239 Private Telecommunication Network (PTN); Inter-exchange signalling, Generic functional
protocol for the support of supplementary services (1993).
ETS 300 363 Private Telecommunication Network (PTN); Specification, functional model and
information flows, Do not disturb and do not disturb override supplementary services
(1994).
Page 10
ETS 300 364: November 1994
ETS 300 387 Private Telecommunication Network (PTN); Method for the specification of basic and
supplementary services (1994).
ENV 41007-1 Definition of terms in private telecommunication networks (1989).
CCITT Rec. I.112 Vocabulary of terms for ISDNs (1988).
CCITT Rec. I.210 Principles of telecommunication services supported by an ISDN and the means to describe
them (1988).
CCITT Rec. Z.100 Specification and description language (1988).
4 Definitions
For the purpose of this ETS the following definitions apply.
4.1 External definitions
This ETS uses the following terms defined in other documents:
− Application Protocol Data Unit (APDU) (ETS 300 239);
− Basic Service (CCITT Recommendation I.210);
− Coordination Function (ETS 300 239);
− End PTNX (ETS 300 239);
− Gateway PTNX (ETS 300 172);
− Interpretation APDU (ETS 300 239);
− Network Facility Extension (NFE) (ETS 300 239);
− Originating PTNX (ETS 300 239);
− Private (ENV 41007-1);
− Private Telecommunication Network Exchange (PTNX) (ENV 41007-1);
− Public ISDN (ENV 41007-1);
− Served user (ETS 300 363)
− Signalling (CCITT Recommendation I.112);
− Supplementary Service (CCITT Recommendation I.210);
− Supplementary Service Control Entity (ETS 300 239);
− Telecommunication Network (ENV 41007-1);
− Terminal (ENV 41007-1);
− Terminating PTNX (ETS 300 239);
− Transit PTNX (ETS 300 239);
− User (ETS 300 171).
4.2 Activating PTNX
The PTNX serving the activating user.

Page 11
ETS 300 364: November 1994
4.3 Deactivating PTNX
The PTNX serving the deactivating user.
4.4 Inter-PTNX link
The totality of a signalling channel and a number of information channels at the Q reference point.
4.5 Interrogating PTNX
The PTNX serving the interrogating user.
4.6 Path retention
The retaining of the network connection between the Originating PTNX and the Terminating PTNX so that a
supplementary service (such as SS-DNDO) can be invoked without establishing a new connection.
4.7 Served user PTNX
The PTNX serving the served user.
5 List of acronyms
APDU Application Protocol Data Unit
ASN.1 Abstract Syntax Notation no. 1
DNDOCL DNDO Capability Level
DNDPL DND Protection Level
ISDN Integrated Services Digital Network
NFE Network Facility Extension
PICS Protocol Implementation Conformance Statement
PTN Private Telecommunication Network
PTNX Private Telecommunication Network Exchange
SDL Specification and Description Language
SS-DND Supplementary Service Do Not Disturb
SS-DNDO Supplementary Service Do Not Disturb Override
TE Terminal Equipment
6 Signalling protocol for the support of SS-DND and SS-DNDO
6.1 SS-DND and SS-DNDO description
SS-DND is a supplementary service which enables a served user to cause the PTN to reject any calls, or just
those associated with a specified basic service, addressed to the served user's PTN number. The calling user
is given an appropriate indication. Incoming calls are rejected as long as the service is active. The served
user's outgoing service is unaffected.
SS-DNDO is a supplementary service which enables a calling user to override SS-DND at a called user
allowing the call to proceed as if the called user had not activated SS-DND.
Both SS-DND and SS-DNDO are applicable to all circuit mode basic services defined in ETS 300 171.

Page 12
ETS 300 364: November 1994
6.2 SS-DND and SS-DNDO operational requirements
6.2.1 Provision/withdrawal
6.2.1.1 Provision/withdrawal of SS-DND
SS-DND is provided or withdrawn after pre-arrangement with the service provider.
SS-DND is provided on a per PTN number basis and per basic service basis. For each PTN number, the
supplementary service can be subscribed to for every basic service subscribed to by that PTN number,
or for only some of the basic services subscribed to by that PTN number.
SS-DND subscription parameters may apply separately to each basic service to which SS-DND is
subscribed, or for all the basic services to which SS-DND is subscribed.
If SS-DNDO is implemented then the subscription parameter "DND protection level" (DNDPL) shall be
provided. The DNDPL has a value in the range 0 to 3 where 0 means no protection against DNDO and 3
means total protection against DNDO. The values 0 and 3 shall be offered. The values 1 and 2 may, as
an implementation option, be offered. The effect of the subscription parameter DNDPL shall be as
described in subclause 6.3.10 of ETS 300 363.
The subscription parameter "Served user notification of SS-DND" may be provided. If it is not
provided, as an implementation option, the network may or may not notify the served user of DND
invocation.
6.2.1.2 Provision/withdrawal of SS-DNDO
SS-DNDO is provided or withdrawn after pre-arrangement with the service provider.
SS-DNDO is provided on a per PTN number basis and per basic service basis. For each PTN number,
the supplementary service can be subscribed to for every basic service subscribed to by that PTN
number, or for only some of the basic services subscribed to by that PTN number.
SS-DNDO subscription parameters may apply separately to each basic service to which SS-DNDO is
subscribed, or for all the basic services to which SS-DNDO is subscribed.
The subscription parameter "DNDO capability level" (DNDOCL) shall be provided. The DNDOCL has
a value in the range 1 (lowest capability) to 3 (highest capability). At least one of the DNDOCL levels
shall be offered. The effect of the subscription parameter "DNDO capability level" shall be as described
in subclause 6.3.10 of ETS 300 363.
6.2.2 Requirements on the Terminating PTNX
Call establishment procedures for the incoming side of an inter-PTNX link and call release procedures, as
specified in ETS 300 172, shall apply.
Generic procedures for the call-related control of supplementary services, as specified in ETS 300 239 for
an End PTNX, shall apply. In addition, the generic procedures for notification, as specified in ETS 300
239 for an End PTNX, shall apply.
6.2.3 Requirements on the Originating PTNX
Call establishment procedures for the outgoing side of an inter-PTNX link and call release procedures, as
specified in ETS 300 172, shall apply.
Generic procedures for the call-related control of supplementary services, as specified in ETS 300 239 for
an End PTNX, shall apply. In addition, the generic procedures for notification, as specified in ETS 300
239 for an End PTNX, shall apply.

Page 13
ETS 300 364: November 1994
6.2.4 Requirements on the Activating PTNX
Generic procedures for the call-independent control (connection oriented) of supplementary services, as
specified in ETS 300 239 for an Originating PTNX, shall apply.
6.2.5 Requirements on the Deactivating PTNX
Generic procedures for the call-independent control (connection oriented) of supplementary services, as
specified in ETS 300 239 for an Originating PTNX, shall apply.
6.2.6 Requirements on the Interrogating PTNX
Generic procedures for the call-independent control (connection oriented) of supplementary services, as
specified in ETS 300 239 for an Originating PTNX, shall apply.
6.2.7 Requirements on a SS-DND Served User PTNX
Generic procedures for the call-independent control (connection oriented) of supplementary services, as
specified in ETS 300 239 for a Terminating PTNX, shall apply.
6.2.8 Requirements on a Transit PTNX
The basic call procedures for call establishment and call clearing at a Transit PTNX, as specified in
ETS 300 172, shall apply.
Generic procedures for the call-related control and call-independent control (connection oriented) of
supplementary services, as specified in ETS 300 239 for a Transit PTNX, shall apply. In addition, the
generic procedures for notification, as specified in ETS 300 239 for a Transit PTNX, shall apply.
6.3 SS-DND and SS-DNDO coding requirements
6.3.1 Operations
The operations defined in Abstract Syntax Notation number 1 (ASN.1) in table 1 shall apply.

Page 14
ETS 300 364: November 1994
Table 1 - Operations in support of SS-DND(O)
Do-Not-Disturb-Operations
{iso(1) identified-organization(3) icd-ecma(0012) standard(0)
qsig-do-not-disturb(194) do-not-disturb-operations (0)}
DEFINITIONS EXPLICIT TAGS ::=
BEGIN
IMPORTS OPERATION, ERROR FROM Remote-Operation-Notation
{joint-iso-ccitt(2) remote-operations(4) notation(0) }
Extension FROM ecma-manufacturer-specific-service-extension-definition
{iso(1) identified-organization(3) icd-ecma (0012) standard (0)
qsig-generic-procedures (165) msi-definition(0) }
basicServiceNotProvided, invalidServedUserNr, notAvailable, notSubscribed,
supplementaryServiceInteractionNotAllowed
FROM General-Errors
{ccitt(0) identified-organization(3) etsi (0) 196 general-errors(2) }
notActivated FROM Call-Diversion-Operations
{ccitt(0) identified-organization(3) etsi (0) 207 diversion-operations (1)}
PartyNumber FROM Addressing-Data-Elements { ccitt(0)
identified-organization(3) etsi(0) 196 addressing-data-elements (6)}
-- Note. The definition of PartyNumber is reproduced in annex C
BasicService FROM Basic-Service-Elements
{ ccitt(0) identified-organization(3) etsi(0) 196 basic-service-elements (8) }
-- Note. The definition of BasicService is reproduced in annex C
;
ptn OBJECTIDENTIFIER ::= {iso(1) identified-organization(3) icd-ecma (0012) private-isdn-signalling-domain(9)}
DoNotDisturbActivate ::= OPERATION
ARGUMENT DNDActivateArg
RESULT DNDActivateRes
ERRORS { notSubscribed,
notAvailable,
invalidServedUserNr,
basicServiceNotProvided,
temporarilyUnavailable,
supplementaryServiceInteractionNotAllowed,
unspecified}
Page 15
ETS 300 364: November 1994
DoNotDisturbDeactivate ::= OPERATION
ARGUMENT DNDDeactivateArg
RESULT DummyRes
ERRORS { notSubscribed,
notAvailable,
invalidServedUserNr,
notActivated,
temporarilyUnavailable,
supplementaryServiceInteractionNotAllowed,
unspecified}
DoNotDisturbInterrogate ::= OPERATION
ARGUMENT DNDInterrogateArg
RESULT DNDInterrogateRes
ERRORS { notSubscribed,
notAvailable,
invalidServedUserNr,
temporarilyUnavailable,
supplementaryServiceInteractionNotAllowed,
unspecified}
DoNotDisturbOverride ::= OPERATION
ARGUMENT DNDOverrideArg
PathRetain ::= OPERATION
ARGUMENT PathRetainArg -- this operation may be used by other
-- Supplementary Services using other
-- values of the argument
ServiceAvailable ::= OPERATION
ARGUMENT ServiceAvailableArg -- this operation may be used by other
-- Supplementary Services using other
-- values of the argument
DoNotDisturbOvrExecute ::= OPERATION
ARGUMENT DummyArg
RESULT DummyResult
ERRORS {notAvailable,
temporarilyUnavailable,
supplementaryServiceInteractionNotAllowed,
unspecified}
DummyArg ::= CHOICE {
null NULL,
extension [1] IMPLICIT Extension,
sequenceOfExtn [2] IMPLICIT SEQUENCE OF Extension
}
Page 16
ETS 300 364: November 1994
DummyRes ::= CHOICE {
null NULL,
extension [1] IMPLICIT Extension,
sequenceOfExtn [2] IMPLICIT SEQUENCE OF Extension
}
DNDActivateArg ::= SEQUENCE {
basicService BasicService,
servedUserNr PartyNumber,
argumentExtension CHOICE{
extension [1] IMPLICIT Extension,
sequenceOfExtn [2] IMPLICIT SEQUENCE OF Extension
} OPTIONAL
}
DNDActivateRes ::= SEQUENCE {
status SET OF SEQUENCE{
basicService BasicService,
dndProtectionLevel DNDProtectionLevel OPTIONAL
} OPTIONAL
resultExtension CHOICE{
extension [1] IMPLICIT Extension,
sequenceOfExtn [2] IMPLICIT SEQUENCE OF Extension
} OPTIONAL
}
DNDDeactivateArg ::= SEQUENCE {
basicService BasicService,
servedUserNr PartyNumber,
argumentExtension CHOICE{
extension [1] IMPLICIT Extension,
sequenceOfExtn [2] IMPLICIT SEQUENCE OF Extension
} OPTIONAL
}
DNDInterrogateArg ::= SEQUENCE {
servedUserNr PartyNumber,
argumentExtension CHOICE{
extension [1] IMPLICIT Extension,
sequenceOfExtn [2] IMPLICIT SEQUENCE OF Extension
} OPTIONAL
}
Page 17
ETS 300 364: November 1994
DNDInterrogateRes ::= SEQUENCE {
status SET OF SEQUENCE {
basicService BasicService,
dndProtectionLevel DNDProtectionLevel OPTIONAL
} OPTIONAL
resultExtension CHOICE{
extension [1] IMPLICIT Extension,
sequenceOfExtn [2] IMPLICIT SEQUENCE OF Extension
} OPTIONAL
}
DNDOverrideArg ::= SEQUENCE {
dndoCapabilityLevel DNDOCapabilityLevel,
argumentExtension CHOICE{
extension [1] IMPLICIT Extension,
sequenceOfExtn [2] IMPLICIT SEQUENCE OF Extension
} OPTIONAL
}
PathRetainArg ::= CHOICE {
serviceList ServiceList,
extendedServiceList SEQUENCE {
serviceList ServiceList,
extension Extension
}
}
ServiceAvailableArg ::= CHOICE {
serviceList ServiceList,
extendedServiceList SEQUENCE {
serviceList ServiceList,
extension Extension
}
}
DNDProtectionLevel ::= ENUMERATED {
lowProtection(0),
mediumProtection(1),
highProtection(2),
fullProtection(3)
}
DNDOCapabilityLevel ::= ENUMERATED {
overrideLowProt(1),
overrideMediumProt(2),
overrideHighProt(3)
}
Page 18
ETS 300 364: November 1994
ServiceList ::= BITSTRING (SIZE (1.32))
{ dndo-low(1), dndo-medium(2), dndo-high(3) }
-- bits other than dndo-low, dndo-medium, or dndo-high, are reserved
-- for other Supplementary Services
temporarilyUnavailable ERROR ::= { ptn 1000 }
Unspecified ::= ERROR PARAMETER Extension
unspecified Unspecified ::= {ptn 1008}
doNotDisturbActivateQ DoNotDisturbActivate ::= {ptn dnd-activate-q (35) }
doNotDisturbDeactivateQ DoNotDisturbDeactivate ::= {ptn dnd-deactivate-q (36) }
doNotDisturbInterrogateQ DoNotDisturbInterrogate ::= {ptn dnd-interrogate-q (37) }
doNotDisturbOverrideQ DoNotDisturbOverride ::= {ptn dndo-q (38) }
doNotDisturbOvrExecuteQ DoNotDisturbOvrExecute ::= {ptn dndo-execute-q (39) }
pathRetain PathRetain ::= {ptn pathretain (41) }
serviceAvailable ServiceAvailable ::= {ptn service-available (42) }
END -- of Do-Not-Disturb-Operations
6.3.2 Notifications
The notification defined in Abstract Syntax Notation number 1 (ASN.1) in table 2 shall apply.
Table 2 - Notification in support of SS-DND
Do-Not-Disturb-Notifications
{iso(1) identified-organization(3) icd-ecma(0012) standard(0)
qsig-do-not-disturb(194) do-not-disturb-notifications (1) }
DEFINITIONS ::=
BEGIN
IMPORTS NOTIFICATION FROM Notification-Data-Structure
{ iso(1) identified-organization(3) icd-ecma (0012) standard (0)
qsig-generic-procedures (165) notification-data-structure (7) } ;
DoNotDisturb ::= NOTIFICATION
ARGUMENT NULL
doNotDisturb DoNotDisturb ::=
{ iso(1) identified-organization(3) icd-ecma (0012)
private-isdn-signalling-domain (9) 2002}
END -- of Do-Not-Disturb-Notifications

Page 19
ETS 300 364: November 1994
6.3.3 Information elements
6.3.3.1 Facility information element
The operations defined in subclause 6.3.1 shall be coded in the Facility information element in
accordance with ETS 300 239.
When conveying the invoke APDU of operations defined in subclause 6.3.1, the destinationEntity data
element of the NFE shall contain value endPTNX.
When conveying the invoke APDU of operation doNotDisturbOverrideQ, the Interpretation APDU shall
contain value discardAnyUnrecognisedInvokePdu.
When conveying the invoke APDU of operations doNotDisturbOvrExecuteQ, doNotDisturbActivateQ,
doNotDisturbDeactivateQ or doNotDisturbInterrogateQ, the Interpretation APDU shall be omitted.
NOTE 1
Additional requirements for the conveyance of APDUs of operations pathRetain and serviceAvailable are
given in A.3.2 of annex A.
6.3.3.2 Notification indicator information element
The notification defined in subclause 6.3.2 shall be coded in the Notification indicator information
element in accordance with ETS 300 239.
6.3.3.3 Other information elements
Any other information elements (e.g. Progress indicator) shall be coded in accordance with the rules of
ETS 300 172 and ETS 300 239.
6.3.4 Messages
The Facility information element and the Notification indicator information element shall be conveyed in
the messages as specified in Clause 10 of ETS 300 239.
Messages used for call establishment and release shall be as specified in ETS 300 172.
6.4 SS-DND and SS-DNDO state definitions
6.4.1 State at the Terminating PTNX
The procedures at the Terminating PTNX are written in terms of the following conceptual state existing
within the SS-DND Supplementary Service Control entity in that PTNX in association with a particular
incoming call for the served user.
6.4.1.1 DND-tIdle
SS-DND or SS-DNDO operation is not in progress.
6.4.2 States at the Originating PTNX
The procedures at the Originating PTNX are written in terms of the following conceptual states existing
within the SS-DNDO Supplementary Service Control entity in that PTNX in association with a particular
call of the calling user.
6.4.2.1 DNDO-oIdle
SS-DNDO is not operating.
Page 20
ETS 300 364: November 1994
6.4.2.2 DNDO-oAwaitExecResult
A doNotDisturbOvrExecuteQ invoke APDU has been sent.
6.4.3 States at the Activating PTNX
The procedures at the Activating PTNX for remote activation of SS-DND are written in terms of the
following conceptual states existing within the SS-DND Supplementary Service Control entity in that
PTNX in association with a particular activation request from the activating user.
6.4.3.1 DND-aIdle
Activation not in progress.
6.4.3.2 DND-aWait
A doNotDisturbActivateQ invoke APDU has been sent. The Activating PTNX is waiting for the
response.
6.4.4 States at the Deactivating PTNX
The procedures at the Deactivating PTNX for remote deactivation of SS-DND are written in terms of the
following conceptual states existing within the SS-DND Supplementary Service Control entity in that
PTNX in association
...