ISO/IEC 13868:1995

Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Inter-exchange signalling protocol — Name identification supplementary services

Is one of a series of standards defining services and signalling protocols applicable to Private Services Networks (PISN). The Series uses ISDN concepts as developed by ITU-T and conforms to the framework of Standards for Open Systems Interconnections as defined by ISO/IEC. Specifies the Stage 3, signalling protocols for use at the Q reference point in support of the following name identification supplementary services CNIP and CONP.

Technologies de l'information — Télécommunications et échange d'information entre systèmes — Réseau privé à intégration de services — Protocole de signalisation d'interéchange — Services supplémentaires d'identification de nom

General Information

• Status: Withdrawn
• Publication Date: 08-Nov-1995
• Withdrawal Date: 08-Nov-1995
• ICS: 33.040.35 - Telephone networks
• Technical Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Drafting Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 21-Mar-2003

Relations

• Parent: ISO/IEC 13868:1995/Amd 1:2001 - Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Inter-exchange signalling protocol — Name identification supplementary services — Amendment 1: Additional character sets for European languages
• Effective Date: 15-Apr-2008
• Revised: ISO/IEC 13868:2003 - Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Inter-exchange signalling protocol — Name identification supplementary services
• Effective Date: 15-Apr-2008
• Amended By: ISO/IEC 13868:1995/Amd 1:2001 - Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Inter-exchange signalling protocol — Name identification supplementary services — Amendment 1: Additional character sets for European languages
• Effective Date: 06-Jun-2022

Standards Content (Sample)

INTERNATIONAL
ISO/IEC
STANDARD 13868
First edition
1995-11-15
Information technology -
Telecommunications and information
exchange between Systems - Private
Integrated Services Network -
Inter-exchange signalling protocol -
Name identification supplementary
Services
Technologies de I’informa tion - TMcommunications et kchange
- Mseau privk a in tegration de
d ‘in forma tion en tre systemes
Services - Protocole de signalisation d’in terkhange - Services
supplkmen taires d ‘iden tifica tion de nom
Reference number
ISO/1 EC 13868: 1995(E)

---------------------- Page: 1 ----------------------
ISO/IEC 13868:1995(E)
Contents
1 Scope 1
2 1
Conformance
3 Normative References 1
4 Def initions 2
4.1 Extemal Definitions
4.2 Name 3
_.
5 List of Acronyms
3
6 SS-CNIP and SS-CONP Coding Requirements 4
61 . Operations
62 . Information Elements
63 .
Messages
7
Signalling Protocol for the Support of SS-CNIP
7.1
SS-CNIP Description
7.2 S S-CNIP Operational Requiremen ts
7.2.1 Requirements on the Originating PINX and thc Incoming Gateway PINX
Requirements on the Terminating PINX and the Outgoing Gatcway PINX 6
7.2.2
Requirements on a Transit PINX
7.2.3
6
7.3 SS-CNIP State Definitions
7.4 SS-CNIP Signalling Procedures for Invocation and Operation
Actions at the Originating PINX
7.4.1 7
7.4.1.1 Normal proccdurcs
7.4.1.2 Exceptional proccdures
7.4.2 Actions at the Terminating PINX
Normal proccdures 7
7.4.2.1
7
7.4.2.2 Exceptional proccdurcs
7.4.3 Actions at a Transit PINX 7
7.5 SS-CNIP Impact of Interworking with Public ISDNs or with Non-ISDNs 7
7.5.1 Actions at the Incoming Gateway PINX 7
8
7.5.2 Actions at the Outgoing Gatcway PINX
8
7.6 Protocol interactions between SS-CNIP and othcr supplementary scrviccs and ANFs
8 Signalling Protocol for the Support of SS-CONP 9
81 . SS-CONP General Description
82 . SS-CONP Operational Requirements
Requirements on the Terminating PINX and the Outgoing Gateway PINX
8.2.1
8.2.2 Requirements on the Originating PINX and the Incoming Gateway PINX
8.2.3 Requirements on a Transit PINX 10
0 ISO/IEC 1995
All rights reserved. Unless otherwise specified, no part of this publication may be
reproduced or utilized in any form or by any means, electronie or mechanical, including
photocopying and microfilm, without Permission in writing from the publisher.
ISO/IEC Copyright Office l Case postale 56 l CH-121 1 Geneve 20 l Switzerland
Printed in S witzerland
ii

---------------------- Page: 2 ----------------------
o ISO/IEC
ISO/IEC 13868:1995(E)
10
83 . SS-CONP State Definitions
10
84 . SS-CONP Signahing Procedures f’or Invocation and Operation
10
8.4.1 Actions at the Terminating PINX
10
8.4.1.1 Normal procedures
11
8.4.1.2 Exceptional procedures
11
8.4.2 Actions at the Originating PINX
11
8.4.2.1 Normal procedures
12
8.4.2.2 Exccp tional procedures
12
8.4.3 Actions at a Transit PINX
12
85 . SS-CONP Impact of Interworking with Public ISDNs or with Non-ISDNs
12
8.5.1 Actions at the Outgoing Gateway PINX
12
8.5.2 Actions at the Incoming Gatcway PINX
12
86 . Protocol Interaction between SS-CONP and other supplementary Service and ANFs
14
Annex A: Protocol Implementation Conformance Statement (PICS) Proforma
14
A.l Introduction
PILS prol’orma 14
A.2 Instructions for completing the
A.2.1 General structure of thc PICS prof’orma 14
A.2.2 Additional Information 15
15
A.2.3 Exception Information
16
A.3 PICS Proforma
16
A.3.1 Implementation identification
A.3.2 Protocol Summary 16
A.3.3 Supplementary Services 17
17
A.3.4 Procedures for SS-CNIP
17
A.3.5 Procedures for SS-CONP
19
Annex B: Specification and Description Language (SDL) Representation
19
B.l SDL Representation of SS-CNIP
22
B.2 SDL Representation of SS-CONP
. . .
111

---------------------- Page: 3 ----------------------
ISO/IEC 13868:1995(E) o ISO/IEC
Foreword
ISO (the International Organization for Standardization) and IEC (the international Electrotechnical
Commission) form the specialized System for woridwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take patt in the work.
In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC
JTCl. Draft International Standards adopted by the joint technical committee are circulated to the national
bodies for voting. Publication as an International Standard requires approval by at least 75% of the national
bodies casting a vote.
Annex A forms an integral part of this International Standard. Annex B is for information only.
IV

---------------------- Page: 4 ----------------------
o ISO/IEC
ISO/IEC 13868: 1995(E)
Introduction
This International Standard is one of a series of International Standards defining Services and signaling
protocols applicable to Private Integrated Services Networks (PISNs). The series uses ISDN concepts as
developed by ITU-T and conforms to the framework of International Standards for Open Systems
Interconnection as defined by ISOAEC.
This particular International Standard specifies the Stage 3, signalling protocols for use at the Q reference
Point in support of the following name identification supplementary Services:
0
Calling Name Identification Presentation (CNIP)
l
Connected Name Identification Presentation (CONP)

---------------------- Page: 5 ----------------------
This page intentionally left blank

---------------------- Page: 6 ----------------------
INTERNATIONAL STANDARD @ ISO/IEC
ISO/IEC 13868: 1995(ET)
Information technology - Telecommunications and
information exchange between Systems - Private
Integrated Services Network - Inter-exchange
signalling protocol - Name identification supplementary
Services
1 Scope
This International Standard specifies the signalling protocol for the support of name identification
supplementary Services at the Q reference Point between Private Integrated Services Network Exchanges
(PINXs) connected together within a Private Integrated Services Network (PISN). The name identification
supplementary Services are Calling Name Identification Presentation’ (SS-CNIP) and Connected Name
Identification Presentation (SS-CONP).
Calling Name Identification Presentation (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 (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 supplementary Service Calling/connected Name Identification Restriction (CNIR) has no impact on the
signalling at Q reference Point.
Provision of a user’s name to the PISN is outside the scope of this International Standard.
The Q reference Point is defined in ISO/IEC 11579-1
Service specifications are produced in three stages according to the method specified in CCITT
Recommendation 1.130. This International Standard contains the Stage 3 specification for the Q reference
Point and satisfies the requirements identified by the Stage 1 and Stage 2 specifications in ISO/IEC 13864.
The signalling protocol for SS-CNIP and SS-CONP operates on top of the signalling protocol for basic
circuit switched call control, as specified in ISO/IEC 11572, and uses certain aspects of the generic
procedures for the control of supplementary Services specified in ISO/IEC 11582.
This International Standard also specifies additional signalling protocol requirements for the support of
interactions at Q reference Point between name identification supplementary Services and other
supplementary Services and ANFs.
This International Standard is applicable to PINXs which tan be interconnected to form a PISN.
2 Conformance
In Order to conform to this International Standard, a PINX shall satisfy the requirements identified in the
Protocol Implementation Conformance Statement (PICS) proforma in annex A.
3 Normative References
The following Standards contain provisions which, through reference in this text, constitute provisions of
this International Standard. At the time of publication, the editions indicated were valid. All Standards are
subject to revision, and Parties to agreements based on this International Standard are encouraged to
1

---------------------- Page: 7 ----------------------
ISO/IEC 13868:1995(E) o ISO/IEC
investigate the possibility of applying the most recent editions of the Standards indicated below. Members
of IEC and ISO maintain registers of currently valid International Standards.
ISO/IEC 11572:1994, Information technology - Telecommunications and information exchange between
Systems - Private Integrated Services Network - Circuit-mode bearer Services - Inter-exchange signalfing
procedures and protocol.
ISO/IEC 11574:1994, Information technology - Telecommunications and information exchange between
Systems - Private lntegrated Services Network - Circuit-mode 64 kbit/s bearer Services - Service
description, functional capabilities and information flo ws.
ISO/1 EC 11579-1:1994, Information technology - Telecommunications and information exchange
between Systems - Private integrated Services network - Part 1: ßeference configuration for PISN
Exchanges (PINX).
ISO/IEC 11582:1995, Information technology - Teiecommunications and information exchange between
Systems - Private In tegra ted Services Network - Generic functional protocol for the support of
supplementary Services - Inter-exchange signalling procedures and protocol.
ISOAEC 13864: 1995, Information technofogy - Telecommunica tions and in forma tion exchange between
s ystems - Private lntegrated Services Network - Specifica tion, functional model and in forma tion flo ws -
Name iden tifica tion supplemen tary Services.
ISO 8859-1:1987, Information processing - 8-bit Single-byte coded graphic Character sets - Part I-- Latin
alphabet No. 1.
CCITT Rec. 1.112 (1988), Vocabulary of terms for ISDNs ( Blue Book).
CCITT Rec. 1.130 (1988), Method for the characterization of telecommunication Services supported by an
ISDN and network capabilities of an ISDN (Blue Book).
CCITT Rec. 1.210 (1988), Principles of telecommunications Services supported by an ISDN and the means
to describe them (Blue Book).
CCITT Rec.Z.100 (1988), Specification and Description Language (B/ue Book).
Character repertoire and coded Character sets for the international teletex Service
CCITT Rec. T.61 (1988),
(Blue Book).
4
Definitions
For the purposes of this International Standard, the following definitions apply.
4.1 External Definitions
This International Standard uses the following terms defined in other documents:
Application Protocol Data Unit (APDU) (ISO/1 EC 11582)
(CCITT Rec. 1.210)
Basic Service
Call, Basic Call (ISOAEC 11582)
Coordination Function (ISO/IEC 11582)
Incoming Gateway PINX (lSO/lEC 11572)
(CCITT Rec. 1.112)
Integrated Services Digital Network
Originating PINX (ISO/lEC 11572)
Outgoing Gateway PINX (lSO/lEC 11572)
Private Integrated Services Network (PISN) (ISO/IEC 11579-1)
- Private Integrated Services Network Exchange (PINX) (ISO/IEC 11579-1)
- Signalling (CCITT Rec. 1.112)
(CCITT Rec. 1.210)
- Supplementary Service

---------------------- Page: 8 ----------------------
o ISO/IEC
ISO/IEC 13868:1995(E)
- Supplementary Service Control Entity (ISOAEC 11582)
- Terminating PINX (ISOAEC 11572)
- Transit PINX (ISO/IEC 11572)
(ISO/IEC 11574)
- User
4.2 Name: A string of maximum 50 characters which is used for the name identification of the PISN
user of a call.
5 List of Acronyms
APDU Application Protocol Data Unit
ASN.l Abstract Syntax Notation One
ISDN Integrated Services Digital Network
Network Facility Extension
NFE
Protocol Implementation Conformance Statement
PICS
PISN Private Integrated Services Network
PINX Private Integrated Services Network Exchange
Specif ication and Description Language
SDL
Supplementary Service Control Entity
SSCE
SS-CNIP Calling Name Identification Presentation supplementary Service
Connected Name Identification Presentation supplementary Service
SS-CONP
3

---------------------- Page: 9 ----------------------
o ISO/IEC
ISO/IEC 13868:1995(E)
6 SS-CNIP and SS-CONP Coding Requirements
6.1 Operations
The operations defined in ASN.l in table 1 shall apply.
Table 1 - Operations in Support of SS-CNIP and SS-CONP
Name-Operations
{ iso ( 1) Standard ( 0)
pssl -name (13868) name
operations( 0) }
DEFINITIONS ::=
BEGIN
IMPORTS
Remote-Operation-Notation
OPERATION, ERROR FROM
1
joint-iso-ccitt( 2) remote-operations( 4
>
notation( 0)
.
)
Extension FROM M’anufacturer-specific-service-
extension-definition
1
iso Standard
pssl -generic-procedures (11582)
msi-definition ( 0)
.
1
EXPORTS Name, NameSet; ’
CallingName OPERATION
ARGUMENT CHOICE
Name, SEQUENCE {Name, CHOKE {
1
[5] IMPLICIT Extension,
[6] IMPLICIT SEQUENCE OF Extension } OPTIONAL }
>
CalledName OPERATION
ARGUMENT CHOICE
Name, SEQUENCE {Name, CHOICE {
1
[5] IMPLICIT Extension,
[6] IMPLICIT SEQUENCE OF Extension } OPTIONAL >>
ConnectedName OPERATION
ARGUMENT CHOICE
Name, SEQUENCE {Name, CHOICE (
1
[5] IMPLICIT Extension,
[6] IMPLICIT SEQUENCE OF Extension } OPTIONAL }
BusyName OPERATION
ARGUMENT CHOICE
Name, SEQUENCE {Name, CHOICE {
1
[5] IMPLICIT Extension,
[6] IMPLICIT SEQUENCE OF Extension } OPTIONAL }}
Name ::= CHOICE
NamePresentationAllowed,
1
NamePresentationRestricted,
NameNotAvailable }

---------------------- Page: 10 ----------------------
o ISO/IEC
ISO/IEC 13868:1995(E)
Table 1 - Operations in Support of SS-CNIP and SS-CONP (cont’d)
NamePresentationAllowed
::= CHOICE
namePresentationAllowedSimple (01 IMPLICIT NameData,
1
namePresentationAllowedExtended [l] IMPLICIT NameSet }
--
iso8859-1 is implied in namePresentationAllowedSimple.
NamePresentationRestricted
::= CHOICE
namePresentationRestrictedSimple [Z] IMPLICIT NameData,
1
namePresentationRestrictedExtended [3] IMPLICIT NameSet,
namePresentationRestrictedNuII [7]IMPLICIT NULL}
--
iso8859-1 is implied in namePresentationRestrictedSimple.
BS
namePresentationRestrictedNuII shall only be used in the
--
case of interworking where the other network provides an
sm
indication that the name is restricted without the name itself.
NameNotAvailable
::= [4] IMPLICIT NULL
NameData ::= OCTET STRING (SIZE (1.50))
-- The maximum allowed size of the name field is 50 octets.
-- The minimum required size of the name field is 1 octet.
NameSet ::= SEQUENCE
nameData NameData,
1
characterset CharacterSet OPTIONAL }
-- If characterset is not included, iso8859-1 is implied.
CharacterSet ::= INTEGER
unknown (0),
1
iso8859- 1 (1 ),
t-61 (2) } (0.255)
-- The Character set “iso8859-1” is specified in International
-- Standard ISO 8859-1 [8].
-- The Character set ‘7-61” is specified
SB
in CCIIT recommendation T.61.
-- Other Character sets might be added in further editions of
-- this Standard.
calling Name CallingName ::=0
calledName CalledName ::=l
connectedName ConnectedName ::=2
busyName BusyName ::=3
--
END of name operations

---------------------- Page: 11 ----------------------
ISO/IEC 13868: 1995(E) o ISO/IEC
6.2 Information Elements
The operations defined in 6.1 for the support of SS-CNIP and SS-CONP shall be coded in the
Facility information element in accordance with ISO/IEC 11582.
When conveying the invoke APDU of the operations defined in 6.1, the destinationEntity data
element of the NFE shall contain value endPINX. The Interpretation APDU in the Facility
information element shall be included shall have the value
and
“discardAny UnrecognisedInvokeAPDU (0)“.
6.3 Messages
Basic call messages ALERTING, CONNECT, DISCONNECT,FACILITY, RELEASE, RELEASE
COMPLETE, PROGRESS and SETUP shall be used for conveying the Facility information
element in support of SS-CNIP and SS-CONP as specified in ISO/IEC 11582.
7 Signaiiing Protocoi for the Support of SS-CNIP
7.1 SS-CNIP 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 to the called User.
The PISN provides the calling user’s name and delivers the calling user’s name to the called user
whenever an incoming call is presented.
The presentation of the calling user’s name may be restricted as specified in SS-CNIR. Some
users may have a Service Profile which permits the override of calling name identification
restriction.
This supplementary Service is applicable to all basic Services, defined in lSO/lEC 11574.
7.2 SS-CNIP Operational Requirements
7.2.1 Requirements on the Originating PINX and the Incoming Gateway PINX
Call establishment procedures, as specified in ISO/IEC 11572, shall apply. Additionally, these
PINXs shall be responsible for obtaining the name information. An Originating PINX may limit,
to less than 50, the number of characters that tan be registered against a User.
Generic procedures for the call related control of supplementary Services, as specified in
ISO/IEC 11582 for a Source PINX, shall apply.
7.2.2 Requirements on the Terminating PINX and the Outgoing Gateway
PINX
Call establishment procedures, as specified in ISO/IEC 11572, shall apply. Additionally, these
PINXs shall be responsible for delivering the name information to the user or to the other
network.
Generic procedures for the call related control of supplementary Services, as specified in
ISO/IEC 11582 for a Destination PINX, shall apply.
7.2.3 Requirements on a Transit PINX
Call establishment procedures, as specified in ISO/IEC 11572, shall apply.
Generic procedures for the call related control of supplementary Services, as specified in
ISO/IEC11582 for a Transit PINX, shall apply.
7.3 SS-CNIP State Definitions
No specific state definitions are required.

---------------------- Page: 12 ----------------------
ISO/IEC 13868:1995(E)
o ISO/IEC
7.4 SS-CNIP Signalling Procedures for Invocation and Operation
7.4.1 Actions at the Originating PINX
7.4.1 .l Normal procedures
If the calling user’s name is available and presentation is allowed, the callingName invoke
APDU shall be sent in the SETUP message from the Originating PINX to the Terminating
PINX. Within the argument, the NamePresentationAllowed type shall be Chosen for the
element of type Name.
If the calling user’s name is available and presentation is restricted, the callingName invoke
APDU shall also be sent in the SETUP message from the Originating PINX to the
Terminating PINX. Within the argument, the NamePresentationRestricted type shall be
Chosen for the element of type Name.
If the calling user’s name is not available, the callingName invoke APDU may be sent in the
SETUP message from the Originating PINX to the Terminating PINX. Within the argument,
the NameNotAvailable type shall be Chosen for the element of type Name.
7.4.1.2 Exceptional procedures
Not applicable.
Actions at the Termlnating PINX
7.4.2
7.4.2.1 Normal procedures
If the callingName invoke APDU has been received with an element of type
NamePresentationAIlowed in the argument, the name information including the
presentation indicator shall be delivered to the called user if able and authorized to receive
the calling name information
If the callingName invoke APDU has been received with an element of type
NamePresentationRestricted in the argument, no name information other than the
presentation indictor shall be delivered to the called User, unless the called user has an
override capability.
If either the callingName invoke APDU has not been received or the callingName invoke
APDU has been received with an element of type NameNotAvailable in the argument, no
name information other than the presentation indicator “name not available” shall be
delivered to the called User.
7.4.2.2 Exceptional procedures
Not applicable.
7.4.3 Actions at a Transit PINX
No special actions are required in support of SS-CNIP.
SS-CNIP Impact of Interworking with Public ISDNs or with Non-ISDNs
7.5
7.5.1 Actions at the Incoming Gateway PINX
On calls incoming from another network, if the other network provides the calling user’s name
information, it shall be sent to the Terminating PINX as specified in 7.4.1 (the Incoming
Gateway PINX thereby acting as an Originating PINX). If the other network does not provide
the calling user name, but provide an indication that the calling user name is restricted, the
incoming gateway PINX shall include the callingName invoke APDU in the SETUP message
7

---------------------- Page: 13 ----------------------
o ISO/IE@
ISO/IEC 13868:1995(E)
sent to the Terminating PINX. Within the argument, choice namePresentationRestrictedNul1
of type NamePresentationRestricted -shall be Chosen for the element of type Name.
If the number of characters in the caliing Party name exceeds 50, the PINX shall
truncate the excess characters.
7.5.2 Actions at the Outgoing Gateway PINX
On outgoing calls to another network, the PISN shall deliver the calling user’s name
information to the other network as specified in 7.42 (the Outgoing Gateway PINX thereby
acting as a Terminating PINX), if the other network supports an equivalent supplementary
Service.
7.6 Protocol lnteractions between SS-CNIP and other supplementary
Services and ANFs
interactions with other supplementary Services and ANFs for
This clause specifies protocol
which Stage 3 International Standards had been published at the time of publication of this
International Standard. For interactions with supplementary Services and ANFs for which Stage 3
International Standards are published subsequent to the publication of this International
Standard, see those other Stage 3 International Standards.
NOTES
Service or
1 Simultaneous conveyance of APDUs for SS-CNIP and another supplementary
ANF in the same message, each in accordance with the requirements of its respective Stage
3 Standard, does not, on its own, constitute a protocol interaction.
2 Additional interactions that have no impact on the signalling protocol at the Q reference Point
tan be found in the relevant Stage 1 specifications.
7.6.1 Connected Name Identification Presentation (SS-CONP)
No protocol interaction.
7.6.2 Completlon of Calls to Busy Subscribers (SS-CCBS)
No protocol interaction.
7.6.3
Completion of Calls on No Reply (SS-CCNR)
No protocol interaction.
7.6.4 Call Transfer (SS-CT)
Protocol interactions are specified in ISO/IEC 13860.
7.6.5 Cal1 Forwarding Unconditional (SS-CFU)
Protocol interactions are specified in ISO/IEC 13873.
7.6.6 Call Forwarding Busy (SS-CFB)
Protocol interactions are specified in ISO/IEC 13873.

---------------------- Page: 14 ----------------------
ISOAEC 13868: 1995(E)
o ISOAEC
7.6.7 Cal1 Forwarding No Reply (SS-CFNR)
Protocol interactions are specified in ISO/IEC ‘I 3873.
7.6.8 Cal1 Deflection (SS-CD)
The protocol interactions with Cal1 Deflection Immcdiate shall be as specified in 7.65 for interaction with
SS-CFU.
The protocol interactions with Cal1 Deflection from Alert shall be as specified in 7.67 for interaction with
SS-CFNR.
7.6.9 Path Replacement (ANF-PR)
No protocol interaction.
8 Signalling Protocol for the Support of SS-CONP
8.1 SS-CONP 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 that answers the call;
- optionally the name of the alerting User;
- optionally the name of the called user that cannot be reached.
The PISN provides the connected user’s name and delivers the connected user’s name to the
calling user whenever an incoming cal1 is answered by the called User.
Optionally, the PISN provides the name of the busy user and delivers the name to the calling
user whenever the called user cannot be reached because of a busy condition.
Optionally, the PISN provides the name of the alerted user and delivers the name to the calling
user whenever an incoming call commences alerting at the called User.
The presentation of the connected user’s name, busy user’s name and alerted user’s name
may be restricted as specified in SS-CNIR. Some users may have a Service Profile which permits
the override of connected name identification restriction.
This supplementary Service is applicable to all basic Services defined in ISO/IEC 11574.
8.2 SS-CONP Operational Requirements
8.2.1 Requirements on the Terminating PINX and the Outgoing Gateway
PINX
Call establishment procedures and the cal1 release procedures, as specified in ISOAEC
11572, shall apply. Additionally, these PINXs shall be responsible for obtaining the name
information. A Terminating PINX may limit, to less than 50, the number of characters that tan
be registered against a User.
Generic procedures for the call related control of supplementary Services, as specified in
ISO/IEC 11582 for a Source PINX, shall apply.
8.2.2 Requirements on the Originating PINX and the Incoming Gateway PINX
Call establishment procedures and the cal1 release procedures, as specified in ISOAEC
11572, shall apply. Additionally, these PINXs shall be responsible for delivering the name
information to the user or to the other network.

---------------------- Page: 15 ----------------------
ISO/IEC 13868:1995(E) o ISO/IEC
Generic procedures for the cal1 related control of supplementary Services, as specified in
ISO/IEC 11582 for a Destination PINX, shall apply.
8.2.3 Requirements on a Transit PINX
Cal1 establishment and release procedures, as specified in ISO/IEC 11572, shall apply.
Generic procedures for the call related control of supplementary Services, as specified in
ISO/IEC 11582 for a Transit PINX, shall apply.
8.3 SS-CONP State Definitions
No specific state definitions are required.
8.4 SS-CONP Signalling Procedures for Invocation and Operation
8.4.1
Actions at the Terminating PINX
8.4.1.1
Normal procedures
When an incoming call is answered by the called user and the connected user-3 name is
available and presentation is allowed, the connectedName invoke APDU shall be sent in
the CONNECT message from the Terminating PINX to the Originating PINX. Within the
argument, the NamePresentationAllowed type shall be Chosen for the element of type
Name.
When the called user cannot be reached because of a busy condition and the called
user’s name is available and presentation is allowed, the busyName invoke APDU may be
sent in the message that indicates the busy condition. Within the argument, the
NamePresentationAllowed type shall be Chosen for the element of type Name.
When an incoming call commences alerting at the called user and the called user-3 name is
available and presentation is allowed, the calledName invoke APDU may be sent in the
ALERTING message from the Terminating PINX to the Originating PINX. Within the
argument, the NamePresentationAIlowed type shall be Chosen for the element of type
Name.
When an incoming call is answered by the called user and the connected user’s name is
available and presentation is restricted, the connectedName invoke APDU shall be sent in
the CONNECT message from the Terminating PINX to the Originating PINX. Within the
argument, the NamePresentationRestricted type shall be Chosen for the element of type
Name.
When the called user cannot be reached because of a busy condition and the called
user-3 name is available and presentation is restricted, the busyName invoke APDU may
be sent in the message that indicates the busy condition. Within the argument, the
NamePresentationRestricted type shall be Chosen for the element of type Name.
When an incoming call commences alerting at the called user and the called user’s name is
available and presentation is restricted, the calledName invoke APDU may be sent in the
ALERTING message from the Terminating PINX to the Originating PINX. Within the
argument, the NamePresentationRestricted type shall be Chosen for the element of type
Name.
When an incoming call is answered by the called user and the connected user’s name is
not available, the connectedName invoke APDU may be sent in the CONNECT message
from the Terminating PINX to the Originating PINX. Within the argument, the
NameNotAvailable type shall be Chosen for the element of type Name.
10

---------------------- Page: 16 ----------------------
o ISO/IEC ISO/IEC 13868:1995(E)
When the called user cannot be reached because of a busy condition and the called
user’s name is not available, the busyName invoke APDU may be sent in the message that
indicates the busy condition. Within the argument, the NameNotAvailable type shall be
Chosen for the element of type Name.
When an incoming call commences alerting at the called user and the called user’s name is
not available, the calledName invoke APDU may be sent in the ALERTING message from
the Terminating PINX to the Originating PINX. Within the argument, the NameNotAvailable
type shall be Chosen for the element of type Name.
8.4.1.2 Exceptional procedures
Not applicable.
8.4.2 Actions at the Originating PI
...