SIST ETS 300 237 E1:2005

• Abstract:

  Contains stage 1 and stage 2 description of the calling name id sup service, the connected name id sup service & the call/connected name id restriction sup service. See ECMA DTR/ECMA-0002 (ECMA-TR/SVC) for a description of these supplementary services. See ENV 41 005 for definition of stage 1 and 2

• 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
• Ref Project: ETSI ETS 300 237 ed.1 (1993-06) - Private Telecommunication Network (PTN); Specification, functional models and information flows; Name identification supplementary service

SIST ETS 300 237 E1:2005 is a SIST standard for Private Telecommunication Networks (PTNs) that specifies the Name identification supplementary service. It covers the stage 1 and stage 2 descriptions of Calling Name Identification Presentation (SS-CNIP), Connected Name Identification Presentation (SS-CONP), and Calling/Connected Name Identification Restriction (SS-CNIR) for PTN users and the network functions that support them.

What does SIST ETS 300 237 E1:2005 specify?

SIST ETS 300 237 E1:2005 specifies how PTNs present and restrict user names during calls. It describes the user-facing service behaviour in stage 1 and the functional entities and information flows in stage 2, while the provision of the user’s name to the PTN remains outside its scope.

The standard applies to various basic telecommunication services supported by PTNs. In practice, that means the name services are defined as supplementary behaviour on top of basic calling and call-control functions, not as standalone services.

The document is organized into the following main clauses and one normative annex:

Part	What it covers
Clauses 1-5	Scope, conformance, references, definitions, acronyms
Clause 6	SS-CNIP stage 1 description
Clause 7	SS-CONP stage 1 description
Clause 8	SS-CNIR stage 1 description
Clause 9	SS-CNIP stage 2 description
Clause 10	SS-CONP stage 2 description
Clause 11	SS-CNIR stage 2 description
Annex A	Structure and content of a PTN Name

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

SIST ETS 300 237 E1:2005 defines three related name services and ties each one to the basic call so that name information appears at the right point in call handling. It also defines how restriction, override profiles, and interworking with other networks affect whether a name is shown.

Stage 1 service behaviour

• SS-CNIP in clause 6 presents the calling party name to the called user when an incoming call is presented. This matters because the called user sees who is calling at the same time as the call indication.
• SS-CONP in clause 7 presents the connected party name to the calling user when the call is answered, and may also present the called party name while alerting or the busy party name when the destination is busy. In practice, the caller can see who actually answered, who is being alerted, or why the call failed.
• SS-CNIR in clause 8 restricts presentation of a user’s name to other users. It can operate in permanent mode or temporary mode, with default behaviour set either to presentation restricted or presentation not restricted, so administrators and users can choose how much control they need.

Presentation, restriction, and overrides

• Clauses 6 to 8 require the PTN to indicate when a name is unavailable or when presentation is restricted. That means the network must not silently omit information; it must tell the receiving user why the name is absent.
• Clauses 6 and 7 allow some users to have a service profile that overrides restriction, such as emergency stations or PTN operators. This is important for service policies where selected users must still see identity information.
• Clause 8 says SS-CNIR is activated on provision and deactivated on withdrawal, with no registration or interrogation. In practice, restriction is managed through service profile settings and call-time requests, not through stored user data.

Interworking and call timing

• Clauses 6 and 7 define interworking with other networks for incoming and outgoing calls. If the other network provides the name or a restriction indication, the PTN passes that information on; if not, it presents the appropriate unavailable or restricted indication.
• Clauses 6, 7, and 10 link the supplementary-service information to the basic call events such as SETUP, REPORT, RELEASE, and DISCONNECT. That timing matters because the name must appear with the call event that a user sees, not later or earlier.

Stage 2 functional model

• Clause 9 defines SS-CNIP with functional entities FE1 CNIP Provision, FE2 CNIP Presentation, and FE3 CNIP Reception, and INFORMATION flows INFORM 1 and INFORM 2.
• Clause 10 defines SS-CONP with FE4 CONP Provision, FE5 CONP Presentation, and FE6 CONP Reception, and INFORMATION flows INFORM 3 to INFORM 8.
• Clause 11 defines SS-CNIR with FE7 Restriction Request and FE8 Restriction Control, and the RESTRICT information flow.

In practical terms, these stage 2 clauses tell implementers where the name is generated, where restriction is applied, and where the final presentation to the user occurs.

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

• Private Telecommunication Network (PTN) - A private network environment in which the supplementary services in this standard are used.
• Private Telecommunication Network Exchange (PTNX) - A network exchange within the PTN model used to place functional entities at originating, destination, gateway, or other network locations.
• Calling Name Identification Presentation (SS-CNIP) - The supplementary service that provides the calling user’s name to the called user.
• Connected Name Identification Presentation (SS-CONP) - The supplementary service that provides the connected user’s name, and optionally the called or busy party name, to the calling user.
• Calling/Connected Name Identification Restriction (SS-CNIR) - The supplementary service that limits presentation of a user’s name to other users.
• Application Identifier - Manufacturer-specific information that can accompany a name and indicate how the name is structured.
• Busy - A condition in which an ISDN destination is treated as busy because of network-determined or user-determined busy status.
• Name - A character string used for name identification of a PTN user in a call, with its structure defined in Annex A.

Who uses SIST ETS 300 237 E1:2005?

SIST ETS 300 237 E1:2005 is used by PTN network operators, system integrators, and equipment vendors who need to implement name display and name restriction services. It is also relevant to service managers who define user profiles, default restriction behaviour, and override rights.

Test and interoperability teams use it to check that name information appears with the correct basic-call events and that restricted or unavailable names are handled properly. Buyers and technical specifiers use it when they need PTN equipment to support CNIP, CONP, or CNIR in a controlled way.

What changed in SIST ETS 300 237 E1:2005 from the previous edition?

SIST ETS 300 237 E1:2005 corresponds to ETS 300 237 Edition 1. The document history identifies this as the first edition, published in June 1993.

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

Standard	What it contributes
ENV 41005	The method for specifying basic and supplementary services of PTNs, including the stage 1 and stage 2 approach
ENV 41007	Definitions of PTN terms used by the standard
ETS 300 171	The basic call model, basic services, user definition, call control entities, and the basic call information flows used for conformance and stage 2 references
ISO 8859-1	One of the character sets allowed for PTN names
CCITT Rec. I.112	Vocabulary for ISDN terms such as connection and signalling
CCITT Rec. I.210	Principles for telecommunication services and the meaning of supplementary service
CCITT Rec. T.61	Another allowed character repertoire for PTN names
CCITT Rec. Z.100	The SDL notation used for the overall service behaviour and functional entity behaviour
ECMA DTR/ECMA-0002 (ECMA-TR/SVC)	Background description of the supplementary services covered by this standard

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

SIST ETS 300 237 E1:2005 contains stage 1 user descriptions, stage 2 functional models, information flows, and SDL-based behaviour descriptions for the three name-related supplementary services. It also includes the interactions with other supplementary services such as CNIP, CONP, CNIR, CLIP, COLP, and CLIR, together with interworking considerations for incoming and outgoing calls.

The stage 2 clauses define the information flows INFORM 1 to INFORM 8 and RESTRICT, and they show how those flows align with basic call events such as SETUP, REPORT, RELEASE, and DISCONNECT. The document also gives allocation tables for placing the functional entities at physical locations in different call scenarios.

Annex A provides the structure and content of a PTN Name. It states that a name is accompanied by the character set indication and optionally by an Application Identifier, and it points to ISO 8859-1 and T.61 as supported character sets.

SLOVENSKI STANDARD
01-maj-2005
Zasebno telekomunikacijsko omrežje (PTN) – Specifikacija, funkcijski modeli in
informacijski pretoki - Dopolnilna storitev: razpoznavanje imena
Private Telecommunication Network (PTN); Specification, functional models and
information flows; Name identification supplementary service
Ta slovenski standard je istoveten z: ETS 300 237 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 237
TELECOMMUNICATION June 1993
STANDARD
Source: ETSI TC-ECMA Reference: DE/ECMA-0005
ICS: 33.080
PTN, NISD, ECMA-163
Key words:
Private Telecommunication Network (PTN);
Specification, functional models and information flows
Name identification supplementary services
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - [e-mail]
X.400: Internet:
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 1993. All rights reserved.
New presentation - see History box

Page 2
ETS 300 237: June 1993
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 237: June 1993
Contents
Foreword .7
1 Scope .9
2 Conformance.9
3 References.9
4 Definitions.10
4.1 External Definitions.10
4.2 Additional Network Feature.10
4.3 Application Identifier.10
4.4 Busy .11
4.5 Busy party name .11
4.6 Call, Basic Call.11
4.7 Calling party name .11
4.8 Connected party name.11
4.9 Called party name.11
4.10 Name .11
5 List of acronyms .11
6 SS-CNIP Stage 1 Description .11
6.1 Description.11
6.1.1 General Description.11
6.1.2 Qualifications on Applicability to Telecommunication Services.12
6.2 Procedures.12
6.2.1 Provision/Withdrawal.12
6.2.2 Normal Procedures .12
6.2.2.1 Activation/Deactivation/Registration/Interrogation.12
6.2.2.2 Invocation and Operation.12
6.2.3 Exceptional Procedures .12
6.2.3.1 Invocation and Operation.12
6.3 Interactions with other Supplementary Services.12
6.3.1 Connected Name Identification Presentation (CONP) .12
6.3.2 Calling/Connected Name Identification Restriction (CNIR).12
6.3.3 Calling Line Identification Presentation (CLIP).13
6.3.4 Connected Line Identification Presentation (COLP).13
6.3.5 Calling/Connected Line Identification Restriction (CLIR) .13
6.4 Interworking Considerations .13
6.4.1 Incoming Calls.13
6.4.2 Outgoing Calls.13
6.5 Overall SDL.13
7 SS-CONP Stage 1 Description.14
7.1 Description.14
7.1.1 General Description.14
7.1.2 Qualifications on Applicability to Telecommunication Services.15
7.2 Procedures.15
7.2.1 Provision/Withdrawal.15
7.2.2 Normal Procedures .15
7.2.2.1 Activation/Deactivation/Registration/Interrogation.15
7.2.2.2 Invocation and Operation.15
7.2.3 Exceptional Procedures .15
7.2.3.1 Invocation and Operation.15
7.3 Interactions with other Supplementary Services.15
7.3.1 Calling Name Identification Presentation (CNIP) .16

Page 4
ETS 300 237: June 1993
7.3.2 Calling/Connected Name Identification Restriction (CNIR) . 16
7.3.3 Calling Line Identification Presentation (CLIP) . 16
7.3.4 Connected Line Identification Presentation (COLP). 16
7.3.5 Calling/Connected Line Identification Restriction (CLIR). 16
7.4 Interworking Considerations. 16
7.4.1 Outgoing Calls . 16
7.4.2 Incoming Calls . 16
7.5 Overall SDL. 16
8 SS-CNIR Stage 1 Description. 17
8.1 Description . 17
8.1.1 General Description. 17
8.1.2 Qualifications on applicability to Telecommunication Services. 17
8.2 Procedures. 18
8.2.1 Provision/Withdrawal . 18
8.2.2 Normal Procedures. 18
8.2.2.1 Activation/Deactivation/Registration/Interrogation . 18
8.2.2.2 Invocation and Operation. 18
8.2.3 Exceptional Procedures. 18
8.2.3.1 Invocation and Operation. 18
8.3 Interactions with other Supplementary Services . 18
8.3.1 Calling Name Identification Presentation (CNIP). 19
8.3.2 Connected Name Identification Presentation (CONP) . 19
8.3.3 Calling Line Identification Presentation (CLIP) . 19
8.3.4 Connected Line Identification Presentation (COLP). 19
8.3.5 Calling/Connected Line Identification Restriction (CLIR). 19
8.4 Interworking Considerations. 19
8.4.1 Incoming Calls . 19
8.4.2 Outgoing Calls . 19
8.5 Overall SDL. 19
9 SS-CNIP Stage 2 Description. 21
9.1 Functional Model. 21
9.1.1 Functional Model Description . 21
9.1.2 Description of the Functional Entities . 21
9.1.3 Relationship of Functional Model to Basic Call Functional Model . 21
9.2 Information Flows. 21
9.2.1 Definition of Information Flows . 21
9.2.1.1 INFORM 1. 22
9.2.1.2 INFORM 2. 22
9.2.2 Relationship of Information Flows to Basic Call Information Flows. 22
9.2.3 Information Flow Sequences . 22
9.3 The Functional Entity Actions. 23
9.4 Functional Entity Behaviour. 23
9.5 Allocation of Functional Entities to Physical Locations. 26
10 SS-CONP Stage 2 Description. 27
10.1 Functional Model. 27
10.1.1 Functional Model Description . 27
10.1.2 Description of the Functional Entities . 27
10.1.3 Relationship of Functional Model to Basic Call Functional Model . 27
10.2 Information Flows. 27
10.2.1 Definition of Information Flows . 27
10.2.1.1 INFORM 3. 28
10.2.1.2 INFORM 4. 28
10.2.1.3 INFORM 5. 28
10.2.1.4 INFORM 6. 29
10.2.1.5 INFORM 7. 29
10.2.1.6 INFORM 8. 29
10.2.2 Relationship of Information Flows to Basic Call Information Flows. 29
10.2.3 Information Flow Sequences . 30
10.3 Functional Entity Actions . 31
10.4 Functional Entity Behaviour. 31

Page 5
ETS 300 237: June 1993
10.5 Allocation of Functional Entities to Physical Locations .34
11 SS-CNIR Stage 2 Description .34
11.1 Functional Model.34
11.1.1 Functional Model Description .34
11.1.2 Description of the Functional Entities.35
11.1.3 Relationship of Functional Model to Basic Call Functional Model.35
11.2 Information Flows .35
11.2.1 Definition of Information Flows.35
11.2.2 Relationship of Information Flows to Basic Call Information Flows.35
11.2.3 Information Flow Sequences.36
11.3 Functional Entity Actions.36
11.4 Functional Entity Behaviour .36
11.5 Allocation of Functional Entities to Physical Locations .38
Annex A (normative): Structure and Content of a PTN Name .40
History.41

Page 6
ETS 300 237: June 1993
Blank page
Page 7
ETS 300 237: June 1993
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 supplementary services applicable to Private
Telecommunication Networks (PTNs) incorporating one or more interconnected exchanges. This
particular ETS deals with Calling Name Identification Presentation (SS-CNIP), Connected Name
Identification Presentation (SS-CONP) and Calling/Connected Name Identification Restriction (SS-CNIR).
This ETS was produced by ECMA using the ECMA guidelines for the production of ETSs and using the
ECMA stylesheet. In order to avoid undue delays in the publication of this ETS, it has been agreed that
this ETS will not be converted to the ETSI stylesheet.

Page 8
ETS 300 237: June 1993
Blank Page
Page 9
ETS 300 237: June 1993
1 Scope
This Standard specifies the supplementary services Calling Name Identification Presentation (SS-CNIP),
Connected Name Identification Presentation (SS-CONP) and Calling/Connected Name Identification
Restriction (SS-CNIR), which are applicable to various basic services supported by Private
Telecommunication Networks (PTNs). Basic services are specified in ETS 300 171.
Calling Name Identification Presentation (SS-CNIP) is a supplementary service which is offered to the
called user and which provides the name of the calling user (calling party name) to the called user.
Connected Name Identification Presentation (SS-CONP) is a supplementary service which is offered to
the calling user and which provides to the calling user the following:
- the name of the user who answers the call (connected party name),
- optionally the name of the alerting user (called party name),
- optionally the name of the called user who cannot be reached (busy party name).
Calling/connected Name Identification Restriction (SS-CNIR) is a supplementary service which is offered
to a user to restrict presentation of that user's name to another user.
Provision of a user's name to the PTN is outside the scope of this Standard.
Service specifications are produced in three stages, according to the method described in ENV 41005.
This Standard contains the stage 1 and 2 specifications of the Name Identification supplementary
services. The stage 1 specifications specify the supplementary services as seen by users of PTNs. The
stage 2 specifications identify the functional entities involved in the supplementary services and the
information flows between them.
2 Conformance
A stage 3 Standard shall be in conformance with this Standard if the signalling protocols and equipment
behaviour specified in the stage 3 Standard are capable of being used in a PTN which supports the
supplementary service specified in this Standard. This means that a stage 3 Standard shall be adequate
for the support of those aspects of the stage 1 and stage 2 clauses for that supplementary service which
are relevant to the interface or equipment to which the stage 3 Standard applies.
The stage 1 and stage 2 clauses which a stage 3 Standard for the Calling Name Identification
Presentation supplementary service shall support are clauses 6 and 9 respectively.
The stage 1 and stage 2 clauses which a stage 3 Standard for the Connected Name Identification
Presentation supplementary service shall support are clauses 7 and 10 respectively.
The stage 1 and stage 2 clauses which a stage 3 Standard for the Calling/Connected Name Identification
Restriction supplementary service shall support are clauses 8 and 11 respectively.
3 References
ENV 41005 (1990) Method for the Specification of Basic and Supplementary Services of
Private Telecommunication Networks
ENV 41007 (1989) Definitions of Terms in Private Telecommunication Networks
ETS 300 171 (1992) Private Telecommunication Networks (PTN) - Specification, Functional
Model and Information Flows - Control Aspects of Circuit Mode Basic
Services
ISO 8859-1 (1987) Information processing - 8-bit single-byte coded graphic character sets -
Part 1: Latin alphabet No. 1
Page 10
ETS 300 237: June 1993
CCITT Rec. I.112 (1988) Vocabulary of terms for ISDNs
CCITT Rec. I.210 (1988) Principles of telecommunication services supported by an ISDN and the
means to describe them
CCITT Rec. T.61 (1988) Character repertoire and coded character sets for the international teletex
service
CCITT Rec. Z.100 (1988) Specification and description language
4 Definitions
For the purpose of this Standard the following definitions apply.
4.1 External Definitions
This Standard uses the following terms defined in other documents:
- Basic Service (CCITT Rec. I.210)
- Connection (CCITT Rec. I.112)
- Integrated Services Digital Networks (CCITT Rec. I.112)
- Private (ENV 41007)
- Private Telecommunication Network Exchange (ENV 41007)
- Public (ENV 41007)
- Public ISDN (ENV 41007)
- Service (CCITT Rec. I.112)
- Signalling (CCITT Rec. I.112)
- Supplementary Service (CCITT Rec. I.210)
- Telecommunication Network (ENV 41007)
- Terminal, Terminal equipment (ENV 41007)
- User (ETS 300 171)
This Standard refers to the following basic call functional entities defined in ETS 300 171:
- Call Control
- Call Control Agent
This Standard refers to the following basic call inter-FE relationships defined in ETS 300 171:
-r1
-r2
This Standard refers to the following basic call information flows defined in ETS 300 171:
- DISCONNECT request/indication
- REPORT request/indication
- RELEASE request/indication
- SETUP request/indication
- SETUP response/confirmation
- SETUP REJECT request/indication
4.2 Additional Network Feature
A capability, over and above that of a basic service, provided by a PTN, but not directly to a PTN user.
4.3 Application Identifier
Manufacturer specific information that can accompany a name and imply the structure of the name (see
annex A).
Page 11
ETS 300 237: June 1993
4.4 Busy
An ISDN destination is considered to be busy if either a "network determined user busy" or a "user
determined user busy" conditions occurs.
4.5 Busy party name
The name of the called user who cannot be reached because of a busy condition.
4.6 Call, Basic Call
An instance of the use of a basic service.
4.7 Calling party name
The name of the calling user.
4.8 Connected party name
The name of the user who answers the call.
4.9 Called party name
The name of the alerting user.
4.10 Name
A string of maximum 50 characters which is used for the name identification of the PTN user of a call.
NOTE 1 The structure and content of a name are defined in annex A.
5 List of acronyms
CC Call Control (functional entity)
CCA Call Control Agent (functional entity)
CONP Connected Name Identification Presentation
CNIP Calling Name Identification Presentation
CNIR Calling/Connected Name Identification Restriction
FE Functional Entity
ISDN Integrated Services Digital Network
PTN Private Telecommunication Network
PTNX Private Telecommunication Network Exchange
SDL Specification and Description Language
SS-CONP Connected Name Identification Presentation supplementary service
SS-CNIP Calling Name Identification Presentation supplementary service
SS-CNIR Calling/Connected Name Identification Restriction supplementary service
TE Terminal Equipment
6 SS-CNIP Stage 1 Description
6.1 Description
6.1.1 General Description
Calling Name Identification Presentation (SS-CNIP) is a supplementary service which is offered to the
called user and which provides the name of the calling user (calling party name) to the called user.
The PTN provides the calling party name to the called user when an incoming call is presented.
The possible provision of the calling party name by the calling user to the PTN is outside the scope of this
Standard.
Page 12
ETS 300 237: June 1993
6.1.2 Qualifications on Applicability to Telecommunication Services
This supplementary service is applicable to all basic telecommunication services.
6.2 Procedures
6.2.1 Provision/Withdrawal
SS-CNIP shall be generally available. There is no need for service profile control.
Some users may have a service profile which permits the override of calling name identification restriction.
6.2.2 Normal Procedures
6.2.2.1 Activation/Deactivation/Registration/Interrogation
SS-CNIP shall be permanently activated. No information needs to be registered with the PTN for this
supplementary service, and therefore interrogation is not applicable.
6.2.2.2 Invocation and Operation
The PTN shall provide the called user with the calling party name at the same time as indicating an
incoming call.
The method by which the PTN obtains the name information is implementation dependent and outside the
scope of this Standard. The management of the PTN name directory system is also outside the scope of
this Standard.
6.2.3 Exceptional Procedures
6.2.3.1 Invocation and Operation
There are two exceptions when the calling party name shall not be presented to the called user:
- when the calling name identification restriction has been invoked (see definition of the
Calling/Connected Name Identification Restriction), and
- when the calling party name is not available, e.g. due to interworking with another network or when
no name is registered against the calling PTN user.
In such cases the called user shall receive an indication of the situation.
In some cases where calling name identification restriction has been invoked, there may be certain
categories of called user that have the service profile to override this restriction and have the calling party
name presented, e.g. emergency stations, PTN operators. In these circumstances, presentation shall
include an indication that restriction has been invoked.
6.3 Interactions with other Supplementary Services
This clause specifies interactions with other supplementary services for which PTN Standards were
available at the time of publication of this Standard.
6.3.1 Connected Name Identification Presentation (CONP)
No interactions.
6.3.2 Calling/Connected Name Identification Restriction (CNIR)
The calling party name shall not be presented if calling name identification restriction has been invoked at
the calling user, unless the called user has the service profile to override this restriction.

Page 13
ETS 300 237: June 1993
6.3.3 Calling Line Identification Presentation (CLIP)
No interactions.
6.3.4 Connected Line Identification Presentation (COLP)
No interactions.
6.3.5 Calling/Connected Line Identification Restriction (CLIR)
No interactions.
6.4 Interworking Considerations
6.4.1 Incoming Calls
On calls incoming from another network, the calling party name shall be obtained from the other network if
available. Where no name is provided by the other network, the called PTN user shall be given an
indication "name unavailable" or "presentation restricted", as appropriate.
6.4.2 Outgoing Calls
On outgoing calls to another network, the PTN shall provide the calling party name to the other network if
this network supports an equivalent supplementary service and if the name is available and presentation
not restricted.
6.5 Overall SDL
Figure 1 contains the dynamic description of SS-CNIP using the SDL defined in CCITT Rec. Z.100. The
SDL process represents the behaviour of the network in providing SS-CNIP. The relationship to the basic
call process is indicated in the annotations.
Output signals to the right represent primitives to the called PTN user. Input signals from the left represent
internal stimuli.
Page 14
ETS 300 237: June 1993
Idle
CNIP is invoked at the same time as
CNIP
the basic call SETUP_indication is sent
required
to the caller user
include indication
whether presentation
restriction applies
N
presentation
restricted?
Y
N
override?
Y
include name.
if available. in
CNIP indication
CNIP
indication
Idle
Figure 1 - SS-CNIP Overall SDL
7 SS-CONP Stage 1 Description
7.1 Description
7.1.1 General Description
Connected Name Identification Presentation (SS-CONP) is a supplementary service which is offered to
the calling user and which provides to the calling user the following:
- the name of the user who answers the call (connected party name),
- optionally the name of the alerting user (called party name),
- optionally the name of the called user who cannot be reached (busy party name).
The PTN provides the connected party name to the calling user when the called user connects to the
incoming call. The PTN optionally provides the busy party name to the calling user when the called user is
busy. The PTN optionally provides the called party name to the calling user when the called user is
alerting.
Page 15
ETS 300 237: June 1993
NOTE 2 Interactions with certain supplementary services may cause the connected party name
to differ from the called party name.
The possible provision of the connected party name by the connected user to the PTN is outside the
scope of this Standard.
7.1.2 Qualifications on Applicability to Telecommunication Services
This supplementary service is applicable to all basic telecommunication services.
7.2 Procedures
7.2.1 Provision/Withdrawal
SS-CONP shall be generally available. There is no need for service profile control.
Some users may have a service profile which permits the override of connected/called/busy name
identification restriction.
7.2.2 Normal Procedures
7.2.2.1 Activation/Deactivation/Registration/Interrogation
SS-CONP shall be permanently activated. No information needs to be registered with the PTN for this
supplementary service, and therefore interrogation is not applicable.
7.2.2.2 Invocation and Operation
The PTN shall provide the calling user with the connected party name at the same time as indicating that
call establishment is complete. The PTN may provide the calling user with the busy party name at the
same time as indicating that call establishment is unsuccessful. The PTN may provide the calling user
with the called party name at the same time as indicating that the call is alerting.
The method by which the PTN obtains the name information is implementation dependent and outside the
scope of this Standard. The management of the PTN name directory system is also outside the scope of
this Standard.
7.2.3 Exceptional Procedures
7.2.3.1 Invocation and Operation
There are two exceptions when the connected/called/busy party name shall not be presented to the calling
user:
- when the connected/called/busy/ name identification restriction has been invoked (see
definition of Calling/Connected Name Identification Restriction), and
- when the connected/called/busy party name is not available, e.g. due to interworking
with another network or when no name is registered against the destination PTN user.
In such cases the calling user shall receive an indication of the situation.
In some cases where Connected Name Identification Restriction has been invoked, there may be certain
categories of calling user that have the service profile to override this restriction and have the
connected/called/busy party name presented, e.g. emergency stations, PTN operators. In these
circumstances, presentation shall include an indication that restriction has been invoked.
7.3 Interactions with other Supplementary Services
This clause specifies interactions with other supplementary services for which PTN Standards were
available at the same time of publication of this Standard.

Page 16
ETS 300 237: June 1993
7.3.1 Calling Name Identification Presentation (CNIP)
No interactions.
7.3.2 Calling/Connected Name Identification Restriction (CNIR)
The connected/called/busy party name shall not be presented if Connected Name Identification Restriction
has been invoked at the destination user, unless the calling user has the service profile to override this
restriction.
7.3.3 Calling Line Identification Presentation (CLIP)
No interactions
7.3.4 Connected Line Identification Presentation (COLP)
No interactions.
7.3.5 Calling/Connected Line Identification Restriction (CLIR)
No interactions.
7.4 Interworking Considerations
7.4.1 Outgoing Calls
On calls outgoing to another network, the connected/called/busy party name shall be obtained from the
other network if available. Where no name is provided by the other network, the calling PTN user shall be
given an indication "name unavailable" or "presentation restricted", as appropriate.
7.4.2 Incoming Calls
On incoming calls from another network, the PTN shall provide the connected/called/busy party name to
the other network if this network supports an equivalent supplementary service and if the name is
available and presentation not restricted.
7.5 Overall SDL
Figure 2 contains the dynamic description of SS-CONP using the SDL defined in CCITT Rec. Z.100. The
SDL process represents the behaviour of the network in providing SS-CONP. The relationship to the basic
call process is indicated in the annotations.
Output signals to the left represent primitives to the calling PTN user. Input signals from the right
represent internal stimuli.
Page 17
ETS 300 237: June 1993
Idle
CONP is invoked at the same time as
the basic call SETUP_confirmation.
CONP
REPORT_indication or
required
RELEASE_indication
is sent to the caller user
include indication
whether presentation
restriction applies
N
presentation
restricted?
Y
N
override?
Y
include name.
if available. in
CONP indication
CONP
indication
Idle
Figure 2 - SS-CONP Overall SDL
8 SS-CNIR Stage 1 Description
8.1 Description
8.1.1 General Description
Calling/connected Name Identification Restriction (SS-CNIR) is a supplementary service which is offered
to a user to restrict presentation of that user's name to another user.
When SS-CNIR applies to a user, the user's name is normally not presented to any other user.
8.1.2 Qualifications on applicability to Telecommunication Services
The supplementary service is applicable to all basic telecommunication services.

Page 18
ETS 300 237: June 1993
8.2 Procedures
8.2.1 Provision/Withdrawal
SS-CNIR shall be provided on a service profile basis. A PTN may provide one or more of several service
options. The options shall apply separately to each name. The following service profile options are
available.
- SS-CNIR mode:
• permanent (invoked for all calls)
• temporary (specified by user per call)
- Default for temporary mode:
• presentation restricted
• presentation not restricted
8.2.2 Normal Procedures
8.2.2.1 Activation/Deactivation/Registration/Interrogation
SS-CNIR shall be activated on provision and deactivated on withdrawal. This supplementary service
requires no registration and admits no interrogation.
8.2.2.2 Invocation and Operation
If permanent mode is provided, identification restriction shall be invoked automatically for all calls
originating or terminating at the PTN user concerned.
If temporary mode is provided, the called party name and busy name shall not be presented. If temporary
mode with default "presentation restricted" is provided, identification restriction of the calling party name
and connected party name shall be invoked automatically for all calls originating or terminating at the PTN
user concerned, unless requested otherwise by the PTN user at call establishment time. If temporary
mode with default "presentation not restricted" is provided, identification restriction of the calling party
name and connected party name shall not be invoked automatically for calls originating or terminating at
the PTN user concerned, unless requested otherwise by the PTN user at call establishment time.
To override the default for an outgoing call when temporary mode is provided, the calling user makes a
request for restriction or no restriction at the same time as requesting call establishment. To override the
default for an incoming call when temporary mode is provided, the called user makes a request for
restriction or no restriction at the same time as responding to the incoming call indication.
If identification restriction is invoked for an outgoing call, the calling party name shall be marked by the
PTN as "presentation restricted". This prevents presentation to the called user (unless the called user has
an override service profile).
If identification restriction is invoked for an incoming call, the connected/called/busy party name shall be
marked by the PTN as "presentation restricted". This prevents presentation to the calling user (unless the
calling user has an override service profile).
8.2.3 Exceptional Procedures
8.2.3.1 Invocation and Operation
A request from the PTN user for the override of a default shall be ignored if the PTN user is not provided
with the temporary mode.
8.3 Interactions with other Supplementary Services
This clause specifies interactions with other supplementary services for which PTN Standards were
available at the time of publication of this Standard.

Page 19
ETS 300 237: June 1993
8.3.1 Calling Name Identification Presentation (CNIP)
see SS-CNIP clause 6.3.2.
8.3.2 Connected Name Identification Presentation (CONP)
see SS-CONP clause 7.3.2
8.3.3 Calling Line Identification Presentation (CLIP)
No interactions.
8.3.4 Connected Line Identification Presentation (COLP)
No interactions.
8.3.5 Calling/Connected Line Identification Restriction (CLIR)
No interactions.
8.4 Interworking Considerations
8.4.1 Incoming Calls
This PTN supplementary service does not apply to the calling user of an incoming call. The other network
may provide the equivalent service, in which case the PTN may receive an indication that presentation of
the calling party name is restricted. In such a situation the other network may or may not supply the calling
party name to the PTN. If not provided, even a called PTN user with an override service profile will be
given only an indication that presentation is restricted. If the called user has invoked name identification
restriction, the connected/called/busy party name is marked as "presentation restricted". This indication
shall be passed on to the other network.
8.4.2 Outgoing Calls
This PTN supplementary service does not apply to the connected user of an outgoing call. The other
network may provide the equivalent service, in which case the PTN may receive an indication that
presentation of the connected/called/busy party name is restricted. In such a situation the other network
may or may not supply the connected/called/busy party name to the PTN. If not provided, even a calling
PTN user with an override service profile will be given only an indication that presentation is restricted. If
the calling user has invoked name identification restriction, the calling party name shall be marked as
"presentation restricted". This indication shall be passed on to the other network.
8.5 Overall SDL
Figure 3 contains the dynamic description of SS-CNIR using the SDL defined in CCITT Rec. Z.100. The
SDL process represents the behaviour of the network in providing SS-CNIR. The relationship to the basic
call process is indicated in the annotations. Input signals from the left represent primitives from the served
PTN user. Input signals from the right represent internal stimuli.

Page 20
ETS 300 237: June 1993
Idle
CNIR request CNIR request get restriction
restriction on restriction off default
received in conjunction
genarated when no
with basic call
SETUP_request or explicit request for
CNIR is received
SETUP_response
in conjunction with
basic call
Y
N
temporary
temporary
mode?
mode?
Y
N
Has user N
restriction service
profile?
Y
N
temporary
mode?
Y
N
default
restriction
on?
Y N
Y
called or busy
party name
restriction on restriction off
for this call for this call
Idle Idle
Figure 3 - SS-CNIR Overall SDL

Page 21
ETS 300 237: June 1993
9 SS-CNIP Stage 2 Description
9.1 Functional Model
9.1.1 Functional Model Description
The functional model for SS-CNIP shall comprise the FEs "CNIP Provision" (FE1), "CNIP Presentation"
(FE2) and "CNIP Reception" (FE3). A relationship ra shall exist between FE1 and FE2 and relationship rb
shall exist between FE2 and FE3. Figure 4 shows these FEs and relationships.
ra rb
FE1 FE2 FE3
r1 r2 r2 r3
CCA
CC CC CC CCA
Figure 4 - Functional model and relationship to basic call for SS-CNIP
9.1.2 Description of the Functional Entities
The functional entities required by SS-CNIP shall be as follows:
- FE1 CNIP Provision: responsible for provision of the calling party name information and
associated indicators to FE2.
- FE2 CNIP Presentation: responsible for reporting the calling party name information and
associated indicators to FE3.
- FE3 CNIP Reception: responsible for delivery of the calling party name information and
associated indicators to the PTN user.
NOTE 3 The structure of the name information is described in annex A of this Standard.
NOTE 4 The possibility, that the name information is stored in another FE (data base) and
provided to FE1 on request for delivery to FE2 is outside the scope of this Standard.
9.1.3 Relationship of Functional Model to Basic Call Functional Model
Figure 4 also shows the relationship with a basic service for SS-CNIP.
9.2 Information Flows
9.2.1 Definition of Information Flows
The information flows INFORM 1 and INFORM 2 shall apply for SS-CNIP.
In the tables below, the column headed "Request" indicates which of the service elements are mandatory
(M) and which are optional (O) in an request/indication information flow. The column headed "Confirm"
indicates which of the service elements are mandatory (M) and which are optional (O) in a
response/confirmation information flow.

Page 22
ETS 300 237: June 1993
9.2.1.1 INFORM 1
This unconfirmed information flow, which conveys the calling party name, shall be sent over relationship ra
(optional in the case of name unavailable, otherwise mandatory). It shall contain the service elements
listed in table 1:
Table 1 - Content of INFORM 1
Service elements Allowed value Request Confirm
Presentation indicator presentation not restricted M
presentation restricted
calling party name not available
Name O (NOTE)
Type of character set O (NOTE)
Application Identifier O
NOTE 5 The service element shall be present if and only if the name is available.
9.2.1.2 INFORM 2
This unconfirmed information flow, which conveys the calling party name, shall be sent over relationship rb
(optional in the case of name unavailable, otherwise mandatory). It shall contain the service elements
listed in table 2.
Table 2 - Content of INFORM 2
Service elements Allowed value Request Confirm
Presentation indicator presentation not restricted M
presentation restricted
calling party name not ava
...