ECMA Internationalopen access

ECMA-284 — Private Integrated Services Network (PISN) - Inter-exchange signalling protocol - Private User Mobility (PUM) - Call handling additional network features (QSIG-PUMCH) (December 2001)

S tandard ECMA-284

3rd Edition - December 2001

Standardizing Information

and

Communication

Systems

Private Integrated Services Network (PISN) Inter-Exchange Signalling Protocol Private User Mobility (PUM) Call Handling Additional Network Features

Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http://www.ecma.ch - Internet: [email protected]

.

S tandard ECMA-284

3rd Edition - December 2001

Standardizing

Information

and

Communication

Systems

Private Integrated Services Network (PISN) Inter-Exchange Signalling Protocol Private User Mobility (PUM) Call Handling Additional Network Features (QSIG-PUMCH)

Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http://www.ecma.ch - Internet: [email protected] IW

Ecma-284.doc

14-01-02 10,31

.

Brief History

This Standard is one of a series of standards defining services and signalling protocols applicable to Private Integrated Services Networks (PISNs). The series uses ISDN concepts as developed by ITU-T and conforms to the framework of standards for Open Systems Interconnection as defined by ISO/IEC. This Standard specifies the signalling protocol for use at the Q reference point for Private User Mobility call handling additional network features ANF-PUMI and ANF-PUMO. This Standard is based upon the practical experience of ECMA member companies and the results of their active and continuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI and other international and national standardization bodies. It represents a pragmatic and widely based consensus. Compared to the 1st Edition of Standard ECMA-284 (published by ECMA in December 1998), the 2nd Edition incorporates changes to achieve complete alignment with International Standard ISO/IEC 17878:2000(E) published by ISO/IEC in April 2000. Compared to the 2nd edition of Standard ECMA-284 (published by ECMA in June 2000), this 3rd Edition incorporates migration to ASN.1 version 1997.

Adopted as 3rd Edition of Standard ECMA-284 by the General Assembly of December 2001.

.

- i -

Table of contents 1

Scope

1

2

Conformance

1

3

References (normative)

1

Definitions E x te r n a l d e f in itio n s Alternative identifier H o me d a t a b a s e ( H D B ) Re r o u te in g P I N X PUMI-detect PINX T e r min a l e q u ip me n t ( T E ) Visitor data base (VDB)

3 3 4 4 4 4 4 4

List of acronyms

4

4 4.1 4.2 4.3 4.4 4.5 4.6 4.7 5 6

Signalling protocol for the support of ANF-PUMI 6 . 1 A N F - P U MI d e s c r i p t i o n 6 . 2 A N F - P U MI o p e r a tio n a l r e q u ir e me n ts 6.2.1 Re q u ir e me n ts o n th e Re r o u te in g P I N X 6.2.2 Re q u ir e me n ts o n th e P U MI - d e te c t P I N X 6.2.3 Re q u ir e me n ts o n th e H o me P I N X 6.2.4 Re q u ir e me n ts o n th e V is ito r P I N X 6.2.5 Re q u ir e me n ts o n a T r a n s it P I N X 6 . 3 A N F - P U MI c o d in g r e q u ir e me n ts 6.3.1 Operations 6.3.2 I n f o r ma t i o n e l e me n t s 6.3.3 Messages 6 . 4 A N F - P U MI s ta te d e f in itio n s 6.4.1 States at the Rerouteing PINX 6.4.2 States at the PUMI-detect PINX 6.4.3 S t a t e s a t t h e H o me P I N X 6.4.4 States at the Visitor PINX 6 . 5 A N F - P U MI s ig n a llin g p r o c e d u r e s f o r in v o c a tio n a n d o p e r a tio n 6.5.1 A c tio n s a t th e Re r o u te in g P I N X 6.5.2 Actions at the PUMI-detect PINX 6.5.3 A c t i o n s a t t h e H o me P I N X 6.5.4 Actions at the Visitor PINX 6.5.5 Actions at a Transit PINX 6.5.6 Actions at an Originating PINX 6 . 6 A N F - P U MI imp a c t o f in te r w o r k in g w ith p u b lic I S D N s 6 . 7 A N F - P U MI imp a c t o f in te r w o r k in g w ith n o n - I S D N s

5 5 5 5 5 5 5 6 7 7 9 10 10 10 10 10 10 10 10 11 13 13 14 14 14 14

- ii -

6 . 8 P r o to c o l in te r a c tio n s b e tw e e n A N F - P U MI an d o th e r s u p p le me n ta r y s e r v ic e s a n d A N F s 1 4 6.8.1 I n t e r a c t i o n w i t h C a l l i n g N a me I d e n t i f i c a t i o n P r e s e n t a t i o n ( S S - C N I P ) 14 6.8.2 I n t e r a c t i o n w i t h C o n n e c t e d N a me I d e n t i f i c a t i o n P r e s e n t a t i o n ( S S - C O N P ) 14 6.8.3 I n t e r a c t i o n w i t h C a l l C o mp l e t i o n t o B u s y S u b s c r i b e r ( S S - C C B S ) 14 6.8.4 I n t e r a c t i o n w i t h C a l l C o mp l e t i o n o n N o R e p ly ( S S - C C N R ) 15 6.8.5 Interaction with Call Transfer (SS-CT) 15 6.8.6 I n te r a c tio n w ith Ca ll F o r w a r d in g U n c o n d itio n a l ( S S - CF U ) 15 6.8.7 I n t e r a c t i o n w i t h C a l l F o r w a r d in g B u s y ( S S - C F B ) 15 6.8.8 I n te r a c tio n w ith Ca ll F o r w a r d in g N o Re p ly ( S S - CF N R) 15 6.8.9 Interaction with Call Deflection (SS-CD) 15 6.8.10 I n t e r a c t i o n w i t h P a t h R e p l a c e me n t ( A N F - P R ) 15 6.8.11 Interaction with Call Offer (SS-CO) 15 6.8.12 Interaction with Call Intrusion (SS-CI) 15 6.8.13 Interaction with Do Not Disturb (SS-DND) 15 6.8.14 I n t e r a c t i o n w i t h D o N o t D is t u r b O v e r r i d e ( S S - D N D O ) 15 6.8.15 I n te r a c tio n w ith A d v ic e O f Ch a r g e ( S S - A O C) 16 6.8.16 Interaction with Recall (SS-RE) 16 6.8.17 Interaction with Call Interception (ANF-CINT) 16 6.8.18 I n te r a c tio n w ith T r a n s it Co u n te r ( A N F - T C) 16 6.8.19 I n t e r a c t i o n w i t h R o u te R e s t r i c t i o n C l a s s ( A N F - R R C ) 16 6.8.20 I n te r a c tio n w ith Me s s a g e W a itin g I n d ic a tio n ( S S - MW I ) 17 6.8.21 I n t e r a c t i o n w i t h W ir e l e s s T e r mi n a l L o c a t i o n R e g is t r a t i o n ( S S - W T L R ) 17 6.8.22 I n t e r a c t i o n w i t h W ir e l e s s T e r mi n a l I n c o min g C a l l ( A N F - W T MI ) 17 6.8.23 I n t e r a c t i o n w i t h W ir e l e s s T e r mi n a l O u t g o in g C a l l ( A N F - W T M O ) 18 6.8.24 I n t e r a c t i o n w i t h W ir e l e s s T e r mi n a l A u t h e n t i c a t i o n o f t h e T e r mi n a l ( S S - W T A T ) 18 6.8.25 I n t e r a c t i o n w i t h W ir e l e s s T e r mi n a l A u t h e n t i c a t i o n o f t h e N e t w o r k ( S S - W T A N ) 18 6.8.26 I n t e r a c t i o n w i t h P r i v a t e U s e r M o b i l i t y R e g is t r a t i o n ( A N F - P U M R ) 18 6.8.27 I n t e r a c t i o n w i t h P r i v a t e U s e r M o b i l i t y O u t g o in g C a l l ( A N F - P U M O ) 18 6.8.28 I n t e r a c t i o n s w i t h C o mmo n I n f o r ma t i o n ( A N F - C MN ) 18 6.8.29 Interaction with Call Priority Interruption (Protection) (SS-CPI(P)) 18 6 . 9 A N F - P U MI p a r a me t e r v a l u e s ( t i me r s ) 18 6.9.1 T i me r T 1 18 6.9.2 T i me r T 2 18 7

Signalling protocol for the support of ANF-PUMO 7 . 1 A N F - P U MO d e s c r ip tio n 7 . 2 A N F - P U MO o p e r a tio n a l r e q u ir e me n ts 7.2.1 Re q u ir e me n ts o n th e O r ig in a tin g P I N X 7.2.2 Re q u ir e me n ts o n th e H o me P I N X 7.2.3 Re q u ir e me n ts o n a T r a n s it P I N X 7 . 3 A N F - P U MO c o d in g r e q u ir e me n ts 7.3.1 Operations 7.3.2 I n f o r ma t i o n e l e me n t s 7.3.3 Messages 7 . 4 A N F - P U MO S ta te d e f in itio n s 7.4.1 States at the Originating PINX

19 19 19 19 19 19 19 19 19 19 20 20

- iii -

7.4.2 S t a t e s a t t h e H o me P I N X 7 . 5 A N F - P U MO s ig n a llin g p r o c e d u r e s 7.5.1 Actions at the Originating PINX 7.5.2 A c t i o n s a t t h e H o me P I N X 7.5.3 Actions at the Transit PINX 7 . 6 A N F - P U MO imp a c t o f in te r w o r k in g w ith p u b lic I S D N s 7 . 7 A N F - P U MO imp a c t o f in te r w o r k in g w ith n o n - I S D N s 7 . 8 P r o to c o l in te r a c tio n s b e tw e e n A N F - P U MO a n d o th e r s u p p le me n ta r y s e r v ic e s a n d ANFs 7.8.1 I n t e r a c t i o n w i t h C a l l i n g N a me I d e n t i f i c a t i o n P r e s e n t a t i o n ( S S - C N I P ) 7.8.2 I n t e r a c t i o n w i t h C o n n e c t e d N a me I d e n t i f i c a t i o n P r e s e n t a t i o n ( S S - C O N P ) 7.8.3 I n t e r a c t i o n w i t h C a l l C o mp l e t i o n t o B u s y S u b s c r i b e r ( S S - C C B S ) 7.8.4 I n t e r a c t i o n w i t h C a l l C o mp l e t i o n o n N o R e p ly ( S S - C C N R ) 7.8.5 Interaction with Call Transfer (SS-WT) 7.8.6 I n t e r a c t i o n w i t h C a l l D i v e r s i o n (S S - C F U , S S - C F B , S S - C F N R , S S - C D ) 7.8.7 I n t e r a c t i o n w i t h P a t h R e p l a c e me n t ( A N F - P R ) 7.8.8 Interaction with Call Offer (SS-CO) 7.8.9 Interaction with Call Intrusion (SS-CI) 7.8.10 Interaction with Do Not Disturb (SS-DND) 7.8.11 I n t e r a c t i o n w i t h D o N o t D is t u r b O v e r r i d e ( S S - D N D O ) 7.8.12 I n te r a c tio n w ith A d v ic e o f Ch a r g e ( S S - A O C) 7.8.13 Interaction with Recall (SS-RE) 7.8.14 Interaction with Call Interception (ANF-CINT) 7.8.15 I n te r a c tio n w ith T r a n s it Co u n te r ( A N F - T C) 7.8.16 I n t e r a c t i o n w i t h R o u te R e s t r i c t i o n C l a s s ( A N F - R R C ) 7.8.17 I n te r a c tio n w ith Me s s a g e W a itin g I n d ic a tio n ( S S - MW I ) 7.8.18 I n t e r a c t i o n w i t h W ir e l e s s T e r mi n a l L o c a t i o n R e g is t r a t i o n ( S S - W T L R ) 7.8.19 I n t e r a c t i o n w i t h W ir e l e s s T e r mi n a l I n c o min g C a l l ( A N F - W T MI ) 7.8.20 I n t e r a c t i o n w i t h W ir e l e s s T e r mi n a l O u t g o in g C a l l ( A N F - W T M O ) 7.8.21 I n t e r a c t i o n w i t h W ir e l e s s T e r mi n a l A u t h e n t i c a t i o n o f t h e T e r mi n a l ( S S - W T A T ) 7.8.22 I n t e r a c t i o n w i t h W ir e l e s s T e r mi n a l A u t h e n t i c a t i o n o f t h e N e t w o r k ( S S - W T A N ) 7.8.23 I n t e r a c t i o n w i t h P r i v a t e U s e r M o b i l i t y R e g is t r a t i o n ( A N F - P U M R ) 7.8.24 I n t e r a c t i o n w i t h P r i v a t e U s e r M o b i l i t y I n c o min g C a l l ( A N F - P U M I ) 7.8.25 I n t e r a c t i o n w i t h C o mmo n I n f o r ma t i o n ( A N F - C MN ) 7.8.26 Interaction with Call Priority Interruption (Protection) (SS-CPI(P)) 7 . 9 P a r a me t e r v a l u e s ( t i me r s ) 7.9.1 T i me r s a t t h e O r i g i n a t i n g P I N X 7.9.2 T i me r s a t t h e H o me P I N X

20 20 20 20 21 21 21

A n n e x A - P r o t o c o l I m p l e m e n t a t i o n C o n fo r m a n c e S t a t e m e n t ( P I C S ) p r o f o r m a

25

Annex B - Imported ASN.1 definitions

37

A n n e x C - Ex a m p le s o f M e s s a g e S e q u e n c e s

39

A n n e x D - S p e c i f i c a t i o n a n d D e s c r i p t i o n L a n gu a g e ( S D L ) r e p r e s e n t a t i o n o f p r o c e d u r e s

45

21 22 22 22 22 22 22 22 22 22 22 22 22 22 22 22 23 23 23 23 23 23 23 23 23 23 23 23 23 23

- iv -

Annex E - Additional feature identifier in module Common-Information-Operations

53

A n n e x F - A S N . 1 d e f in it io n s a c c o r d in g t o I TU - T R e c s . X . 2 0 8 / X . 2 0 9

55

1

Scope This Standard specifies the signalling protocol for the support of the Private User Mobility call handling additional network features (ANF-PUMI and ANF-PUMO) at the Q reference point between Private Integrated services Network eXchanges (PINX) connected together within a Private Integrated Services Network (PISN). ANF-PUMI is a feature that directs incoming calls to a PUM user within the PISN regardless of the PUM user’s geographical location within the PISN, provided that the PUM user’s location is known. ANF-PUMO permits the PISN to process call requests from a PUM user at the home location, if required. The Q reference point is defined in ECMA-133. Service specifications are produced in three stages and according to the method specified in ITU-T Rec. I.130. This 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 ECMA-283. The signalling protocol for ANF-PUMI and ANF-PUMO operates on top of the signalling protocol for basic circuit switched call control, as specified in ECMA-143, and uses certain aspects of the generic procedures for the control of supplementary services specified in ECMA-165. This Standard also specifies additional signalling protocol requirements for the support of interactions at the Q reference point between ANF-PUMI / ANF-PUMO and other supplementary services and ANFs. This Standard is applicable to PINXs which can interconnect to form a PISN.

2

Conformance In order to conform to this Standard, a PINX shall satisfy the requirements identified in the Protocol Implementation Conformance Statement (PICS) proforma in annex A.

3

References (normative) The following standards contain provisions which, through reference in this text, constitute provision of this Standard. All standards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. In the case of references to ECMA Standards that are aligned with ISO/IEC International Standards, the number of the appropriate ISO/IEC International Standard is given in brackets after the ECMA reference. ECMA-133

Private Integrated Services Network (PISN) - Reference Configuration for PISN Exchanges (PINX) (International Standard ISO/IEC 11579-1)

ECMA-142

Private Integrated Services Network (PISN) - Circuit Mode 64kbit/s Bearer Services Service Description, Functional Capabilities and Information Flows (International Standard ISO/IEC 11574)

ECMA-143

Private Integrated Services Network (PISN) - Circuit Mode Bearer Services - InterExchange Signalling Procedures and Protocol (International Standard ISO/IEC 11572)

ECMA-155

Private Integrated ISO/IEC 11571)

ECMA-164

Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol - Name Identification Supplementary Services (International Standard ISO/IEC 13868)

ECMA-165

Private Integrated Services Network (PISN) - Generic Functional Protocol for the Support of Supplementary Services - Inter-Exchange Signalling Procedures and Protocol (International Standard ISO/IEC 11582)

ECMA-174

Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol - Call Diversion Supplementary Services (International Standard ISO/IEC 13873)

Services

Networks

-

Addressing

(International

Standard

- 2 -

ECMA-176

Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol - Path Replacement Additional Network Feature (International Standard ISO/IEC 13874)

ECMA-192

Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol - Call Offer Supplementary Service (International Standard ISO/IEC 14843)

ECMA-194

Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol - Do Not Disturb and Do Not Disturb Override Supplementary Services (International Standard ISO/IEC 14844)

ECMA-203

Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol - Call Intrusion Supplementary Service (International Standard ISO/IEC 14846)

ECMA-212

Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol Advice of Charge Supplementary Services (International Standard ISO/IEC 15050)

ECMA-221

Private integrated services network (PISN) - Inter-Exchange Signalling Protocol - Call Interception Additional Network Feature (International Standard ISO/IEC 15054)

ECMA-225

Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol Transit Counter Additional Network Feature (International Standard ISO/IEC 15056)

ECMA-242

Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol Message Waiting Indication Supplementary Service (International Standard ISO/IEC 15506)

ECMA-251

Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol Common Information Additional Network Feature (International Standard ISO/IEC 15772)

ECMA-264

Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol - Call Priority Interruption and Call Priority Interruption Protection Supplementary Services (International Standard ISO/IEC 15992)

ECMA-281

Private Integrated Services Network (PISN) - Specification, Functional Model and Information Flows - Private User Mobility (PUM) - Registration Supplementary Service (International Standard ISO/IEC 17875)

ECMA-282

Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol Private User Mobility (PUM) - Registration Supplementary Service (International Standard ISO/IEC 17876)

ECMA-283

Private Integrated Services Network (PISN) - Specification, Functional Model and Information Flows - Private User Mobility (PUM) - Call Handling Additional Network Features (International Standard ISO/IEC 17877)

ECMA-304

Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol Wireless Terminal Call Handling Additional Network Features (International Standard ISO/IEC 15431)

ISO/IEC 13241

Information technology - Telecommunications and information exchange between systems - Private Integrated Services Network - Inter-exchange signalling protocol Route restriction class additional network feature (1997)

ETS 300 415

Private Integrated Services Network (PISN); Terms and definitions (1996)

ITU-T Rec. I.112

Vocabulary of terms for ISDN (1993)

ITU-T Rec. I.130

Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN (Blue Book) (1988)

ITU-T Rec. I.210

Principles of telecommunication services supported by an ISDN and the means to describe them (1993)

ITU-T Rec. Q.850

Usage of cause and location in the digital subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN user part (1998)

- 3 -

4

ITU-T Rec. Q.950

Supplementary services protocols, structure and general principles (2000)

ITU-T Rec. Z.100

Specification and description language (1999)

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: − Additional Network Feature (ANF)

(ECMA-165)

− AllCall registration

(ECMA-281)

− Application Protocol Data Unit (APDU)

(ECMA-165)

− Basic service

(ITU-T Rec. I.210)

− Call, Basic call

(ECMA-165)

− Call independent

(ECMA-165)

− Call independent signalling connection

(ECMA-165)

− Call related

(ECMA-165)

− Complete number

(ECMA-155)

− Co-ordination function

(ECMA-165)

− End PINX

(ECMA-165)

− InCall registration

(ECMA-281)

− Incoming Gateway PINX

(ECMA-143)

− Incoming PUM call

(ECMA-283)

− Interpretation APDU

(ECMA-165)

− Home PINX

(ECMA-283)

− Hosting address

(ECMA-283)

− Network Facility Extension (NFE)

(ECMA-165)

− Originating PINX

(ECMA-143)

− Private Integrated Services Network (PISN)

(ECMA-133)

− Private Integrated services Network eXchange (PINX)

(ECMA-133)

− PISN number

(ECMA-155)

− Signalling

(ITU-T Rec. I.112)

− Supplementary service

(ITU-T Rec. I.210)

− Supplementary Service Control Entity

(ECMA-165)

− Subsequent PINX

(ECMA-143)

− Terminating PINX

(ECMA-143)

− Transit PINX

(ECMA-143)

− User

(ECMA-142)

− PUM user

(ECMA-283)

− Visitor PINX

(ECMA-283)

- 4 -

4.2

Alternative identifier An identifier, other than the PISN number, which identifies the PUM user uniquely.

4.3

Home data base (HDB) The database in which the data on the current location and associated parameters of a wireless terminal or a mobile user are stored.

4.4

Rerouteing PINX The PINX which executes the rerouteing of the incoming PUM call to the current Visitor PINX. NOTE 1 In case of rerouteing, the Rerouteing PINX is either the Originating PINX or the Incoming Gateway PINX. In case of forward switching, the Rerouteing PINX is the PUMI-detect PINX.

4.5

PUMI-detect PINX The PINX which detects that an incoming call is to a PUM user. NOTE 2 The PUMI-detect PINX is either the Home PINX, a Transit PINX, the Incoming Gateway PINX or the Originating PINX.

4.6

Terminal equipment (TE) An item of equipment attached to a telecommunication network to provide access for a user to one or more services.

4.7

Visitor data base (VDB) The database in which location information concerning a wireless terminal or a mobile user is stored, as long as the wireless terminal or the mobile user are localized in the corresponding visitor area.

5

List of acronyms ANF

Additional Network Feature

ANF-CINT

Call Interception additional network feature

ANF-CMN

Common Information additional network feature

ANF-WTMI

Wireless Terminal Incoming call additional network feature

ANF-PR

Path Replacement additional network feature

(ANF-)PUMI

Private User Mobility Incoming Call (additional network feature)

(ANF-)PUMO

Private User Mobility Outgoing Call (additional network feature)

ANF-RRC

Route Restriction Class additional network feature

ANF-TC

Transit counter additional network feature

APDU

Application Protocol Data Unit

ASN.1

Abstract Syntax Notation no. 1

HDB

Home Data Base

ISDN

Integrated Services Digital Network

NFE

Network Facility Extension

PICS

Protocol Implementation Conformance Statement

PINX

Private Integrated services Network eXchange

PISN

Private Integrated Services Network

PUM

Private User Mobility

SDL

Specification and Description Language

- 5 -

6

SS-AOC

Advice Of Charge supplementary services

SS-CD

Call Deflection supplementary service

SS-CFB

Call Forwarding Busy supplementary service

SS-CFNR

Call Forwarding No Reply supplementary service

SS-CFU

Call Forwarding Unconditional supplementary service

SS-CI

Call Intrusion supplementary service

SS-CNIP

Calling Name Identification Presentation supplementary service

SS-CO

Call Offer supplementary service

SS-CPI(P)

Call Priority Interruption (Protection) supplementary service

SS-DNDO

Do Not Disturb Override supplementary service

SS-MWI

Message Waiting Indication supplementary service

TE

Terminal Equipment

VDB

Visitor Data Base

Signalling protocol for the support of ANF-PUMI

6.1

ANF-PUMI description ANF-PUMI enables calls to be directed to a PUM user within the PISN. As there is no predetermined PINX for the connection of a PUM user to the PISN, the directing of such calls requires that information regarding the location of the user is available.

6.2 6.2.1

ANF-PUMI operational requirements Requirements on the Rerouteing PINX ECMA-143 protocol control procedures for call establishment at the outgoing side of an inter-PINX link shall apply to the establishment of the connection to the Visitor PINX. ECMA-143 protocol control procedures for call clearing shall apply to the release of the connection to the PUMI-detect PINX. Generic procedures for the call related control of supplementary services, as specified in ECMA-165 for an End PINX, shall apply.

6.2.2

Requirements on the PUMI-detect PINX ECMA-143 protocol control procedures for call establishment at the incoming side of an inter-PINX link shall apply to the establishment of the connection from the Originating or Incoming Gateway PINX. ECMA-143 protocol control procedures for call clearing shall apply to the release of the connection to the Rerouteing PINX. Generic procedures for the call related control of supplementary services, as specified in ECMA-165 for an End PINX, shall apply. Generic procedures for the call independent control (connection oriented) of supplementary services, as specified in ECMA-165 for an Originating PINX, shall apply.

6.2.3

Requirements on the Home PINX Generic procedures for the call independent control (connection oriented) of supplementary services, as specified in ECMA-165 for a Terminating PINX, shall apply.

6.2.4

Requirements on the Visitor PINX ECMA-143 protocol control procedures for call establishment at the incoming side of an inter-PINX link shall apply to the establishment of the connection from the Rerouteing PINX. Generic procedures for the call related control of supplementary services, as specified in ECMA-165 for an End PINX, shall apply.

- 6 -

6.2.5

Requirements on a Transit PINX Basic call procedures for call establishment and call clearing at a Transit PINX, as specified in ECMA-143, shall apply. Generic procedures for the call related control and call independent control (connection oriented) of supplementary services, as specified in ECMA-165 for a Transit PINX, shall apply.

- 7 -

6.3

ANF-PUMI coding requirements

6.3.1

O p e r a t io n s The operations defined in Abstract Syntax Notation number 1 (ASN.1) in table 1 shall apply. The notation is in accordance with ITU-T Rec. X.680 and X.690. The ITU-T Rec. X.208 and X.209 superseded version is in annex F. Table 1 - Operations in support of call handling additional network features

Private-User-Mobility-Call-Handling-Operations-asn1-97 { iso (1) standard (0) pss1-pum-call-handling (17878) pum-call-handling-operations-asn1-97 (1)} DEFINITIONS EXPLICIT TAGS ::= BEGIN IMPORTS

OPERATION, ERROR FROM Remote-Operations-Information-Objects { joint-iso-itu-t remote-operations (4) informationObjects (5) version1 (0) } EXTENSION, Extension{} FROM Manufacturer-specific-service-extension-class-asn1-97 { iso (1) standard (0) pss1-generic-procedures (11582) msi-class-asn1-97(11) } PSS1InformationElement FROM PSS1-Generic-parameters-definition-asn1-97 { iso (1) standard (0) pss1-generic-procedures (11582) pss1-generic-parameters-asn1-97 (17) } Name FROM Name-Operations-asn1-97 { iso (1) standard (0) pss1-name (13868) name-operations-asn1-97 (1) } basicServiceNotProvided, invalidServedUserNr, notAvailable FROM General-Error-List { ccitt recommendation q 950 general-error-list (1) } Address, PartyNumber, PartySubaddress, PresentedNumberScreened FROM Addressing-Data-Elements-asn1-97 { iso (1) standard (0) pss1-generic-procedures (11582) addressing-data-elements-asn1-97 (20) };

Private-User-Mobility-Call-Handling--Operations OPERATION ::= { pumiEnquiry | pumiDivert | pumiInform | pumoCall } -- Operations for ANF-PUMI: -pumiEnquiry

OPERATION ::= { -- Sent from the PUMI-detect PINX to the Home PINX. ARGUMENT EnquiryArg RESULT EnquiryRes ERRORS { invalidServedUserNr | locationNotKnown | notAvailable | basicServiceNotProvided | unspecified } CODE local: 93}

pumiDivert

OPERATION ::= { -- Sent from the PUMI-detect PINX to the Rerouteing PINX. ARGUMENT DivertArg RESULT DummyRes ERRORS { notAvailable | unspecified } CODE local: 94}

- 8 -

Table 1 - Operations in support of call handling additional network features (continued) pumiInform

EnquiryArg ::=

OPERATION ::= { -- Sent from the Rerouteing PINX to the Visitor PINX. ARGUMENT InformArg RETURN RESULT FALSE ALWAYS RESPONDS FALSE CODE local: 95} SEQUENCE

{ pisnNumber PartyNumber, -- The PISN number of the PUM user qSIGInfoElement PSS1InformationElement,

-- The basic call information elements Bearer capability, High layer compatibility, -- Low layer compatibility can be embedded in the qSIGInfoElement -- in accordance with clause 6.5.2.1. argExtension PumiExtension OPTIONAL } DivertArg ::=

SEQUENCE

{ hostingAddr PartyNumber, -- The PISN number of the hosting user, -- always a Complete Number. callingNumber PresentedNumberScreened, pumIdentity PumIdentity, -- The PISN number (always a Complete Number) -- and/or an alternative identifier of the PUM user. qSIGInfoElement PSS1InformationElement, -- The basic call information elements Bearer capability, High layer compatibility, -- Low layer compatibility, and Progress indicator -- can be embedded in the qSIGInfoElement in accordance with clause 6.5.2.1. callingUserSub [ 1 ] PartySubaddress OPTIONAL, callingUserName [ 2 ] Name OPTIONAL, pumUserSub [ 3 ] PartySubaddress OPTIONAL, argExtension PumiExtension OPTIONAL }

InformArg ::=

SEQUENCE

{ pumIdentity PumIdentity, -- The PISN number (always a Complete Number) -- and/or an alternative identifier of the PUM user. argExtension PumiExtension OPTIONAL }

EnquiryRes ::=

CHOICE

{ currLocation cfuActivated

[ 1 ] IMPLICIT CurrLocation, [ 2 ] IMPLICIT CfuActivated }

CurrLocation ::= SEQUENCE

{ hostingAddr PartyNumber, -- The PISN number of the hosting user, -- always a Complete Number. pumIdentity PumIdentity, -- The PISN number (always a Complete Number) -- and/or an alternative identifier of the PUM user. argExtension PumiExtension OPTIONAL }

CfuActivated ::= SEQUENCE

{ divToAddress divOptions pumName argExtension

SubscriptionOption ::=ENUMERATED

{ noNotification (0), notificationWithoutDivertedToNr (1), notificationWithDivertedToNr (2) }

Address, SubscriptionOption, [ 1 ] Name OPTIONAL, PumiExtension OPTIONAL }

- 9 -

Table 1 - Operations in support of call handling additional network features (concluded) DummyRes ::=

CHOICE

{ null extension sequOfExtn

NULL, [ 1 ] IMPLICIT Extension{{PUMCHExtSet}}, [ 2 ] IMPLICIT SEQUENCE OF Extension{{PUMCHExtSet}} }

PumiExtension ::= CHOICE

{ extension sequOfExtn

[ 4 ] IMPLICIT Extension{{PUMCHExtSet}}, [ 5 ] IMPLICIT SEQUENCE OF Extension{{PUMCHExtSet}} }

PumIdentity ::=

CHOICE

{ pisnNumber alternativeId both

PartyNumber, [ 10 ] IMPLICIT AlternativeId, [ 11 ] IMPLICIT SEQUENCE { pisnNumber PartyNumber, alternativeId AlternativeId } }

AlternativeId ::=

OCTET STRING(SIZE(1..20))

-- Operation for ANF-PUMO -pumoCall

OPERATION ::= { ARGUMENT PumoArg ALWAYS RESPONDS FALSE RETURN RESULT FALSE CODE local: 96}

PumoArg ::=

SEQUENCE

{ destinationNumber [0] PartyNumber OPTIONAL, pumIdentity [1] PumIdentity OPTIONAL, -- The PISN number (always a Complete Number) -- and/or an alternative identifier of the PUM user. sendingComplete [2] IMPLICIT NULL OPTIONAL, extension CHOICE {single [3] IMPLICIT Extension{{PUMCHExtSet}}, multiple [4] IMPLICIT SEQUENCE OF Extension{{PUMCHExtSet}} } OPTIONAL }

PUMCHExtSet EXTENSION ::= {...} locationNotKnown unspecified

END

ERROR ERROR

::= ::=

{ {

CODE local: 1015} PARAMETER Extension{{PUMCHExtSet}} CODE local: 1008}

-- of Private-User-Mobility-Call-Handling-Operations-asn1-97

6.3.2 Information elements 6.3.2.1 Facility information element The operations defined in 6.3.1 shall be coded in the Facility information element in accordance with ECMA-165. When conveying the invoke APDU of operations defined in 6.3.1 the destinationEntity data element of the NFE shall contain value endPINX. When conveying the invoke APDU of operations defined in 6.3.1, the Interpretation APDU shall either be omitted or be included with value rejectAnyUnrecognisedInvokePdu. 6.3.2.2

Other information elements Any other information elements (e.g. Calling party number, Called party number) shall be coded in accordance with the rules of ECMA-143 and ECMA-165.

- 10 -

6.3.3

Messages The Facility information element shall be conveyed in the messages as specified in clause 10 of ECMA-165. Messages used for call establishment shall be as specified in ECMA-143.

6.4

ANF-PUMI state definitions

6.4.1

S t a t e s a t t h e R e r o u t e in g P I N X The procedures for the Rerouteing PINX are written in terms of the following conceptual states existing within the ANF-PUMI Supplementary Service Control entity in that PINX in association with a particular call.

6.4.1.1 6.4.2

S t a t e Ex e c I d le Ready for receipt of a pumiDivert APDU. States at the PUMI-detect PINX The procedures for the PUMI-detect PINX are written in terms of the following conceptual states existing within the ANF-PUMI Supplementary Service Control entity in that PINX in association with a particular call.

6.4.2.1

S t a t e P U M I - I d le ANF-PUMI is not operating.

6.4.2.2

State PUMI-Detected A call to a PUM user has been detected and a pumiEnquiry invoke APDU requesting the current location of the PUM user has been sent to the Home PINX.

6.4.2.3

S t a t e P U M I - D iv e r t The current location of the PUM user is known and a pumiDivert invoke APDU has been sent to the Rerouteing PINX.

6.4.3

States at the Home PINX The procedures for the Home PINX are written in terms of the following conceptual states existing within the ANF-PUMI Supplementary Service Control entity.

6.4.3.1 6.4.4

S t a t e s a t t h e V is it o r P I N X The procedures for the Visitor PINX are written in terms of the following conceptual states existing within the ANF-PUMI Supplementary Service Control entity in that PINX in association with a particular call.

6.4.4.1

6.5

S t a t e H o m e I d le Ready for receipt of a pumiEnquiry APDU.

S t a t e V is it I d le Ready for receipt of a pumiInform APDU.

ANF-PUMI signalling procedures for invocation and operation Examples of message sequences are shown in annex C.

6.5.1 6.5.1.1

A c t io n s a t t h e R e r o u t e in g P I N X The SDL representation of procedures at the Rerouteing PINX is shown in D.1 of annex D. Normal procedures On receipt of a pumiDivert invoke APDU in a FACILITY message during basic call protocol control state Outgoing Call Proceeding, the Rerouteing PINX shall determine whether it can proceed with ANF-PUMI. If so, it shall initiate a new call establishment to the Visitor PINX and release the leg towards the PUMI-detect PINX by sending a DISCONNECT message containing a pumiDivert return result APDU. The SETUP message for the new call establishment shall include a pumiInform invoke APDU.

- 11 -

The following specific basic call information elements shall be included in the SETUP message: − Called party number, containing the number received in the hostingAddr data element within the pumiDivert invoke APDU; − Called party subaddress, containing the subaddress received in the pumUserSub data element within the pumiDivert invoke APDU (optional); − Calling party number, containing the number received in the callingNumber data element within the pumiDivert invoke APDU; − Calling party subaddress, containing the subaddress received in the callingUserSub data element within the pumiDivert invoke APDU (optional); − Bearer capability information element as received in embedded form within the pumiDivert invoke APDU, and any of the following information elements which were also received in embedded form in this APDU: High layer compatibility, Low layer compatibility and Progress indicator information elements. The pumiInform invoke APDU shall contain the data element pumIdentity with the same contents as the corresponding data element in the argument of the received pumiDivert invoke APDU. 6.5.1.2

6.5.2

Ex c e p t io n a l p r o c e d u r e s If the Rerouteing PINX can not proceed with ANF-PUMI, it shall answer the pumiDivert invoke APDU with a return error APDU containing the error notAvailable. A c t io n s a t t h e P U M I - d e t e c t P I N X The SDL representation of procedures at the PUMI-detect PINX is shown in D.2 of annex D. When a PUMI-detect PINX also provides Rerouteing PINX functionality, in support of ANF-PUMI by forward switching, the joint requirements of 6.5.1 (for a Rerouteing PINX) and 6.5.2 (for a PUMI-detect PINX) shall apply, with the exception that any communication between the PUMI-detect PINX functionality and the Rerouteing PINX functionality will be an intra-PINX matter. The messages specified for sending from the PUMI-detect PINX towards the Rerouteing PINX or vice versa will not appear on any inter-PINX link.

6.5.2.1

Normal procedures On determining that ANF-PUMI is to be invoked following the arrival of an incoming call, the PUMIdetect PINX shall send a pumiEnquiry invoke APDU to the Home PINX of the called PUM user, using the call reference of a call independent signalling connection. The call independent signalling connection shall be established (or used, if an appropriate connection is already available) in accordance with the procedures specified in 7.3 of ECMA-165. The PUMI-detect PINX shall enter state PUMI-Detected and start timer T1. NOTE 3 The number to be used in the Called party number information element when establishing the call independent signalling connection to the Home PINX is outside the scope of this Standard. It can, for example, be the Called party number information element received in the incoming SETUP message. The following data elements shall be included in the argument of the pumiEnquiry invoke APDU: − element pisnNumber as received in the incoming SETUP message in the Called party number information element; − element qSIGInfoElement containing an embedded Bearer capability information element, as received in the incoming SETUP message, and any of the following information elements which were received in the incoming SETUP message: High layer compatibility and Low layer compatibility. On receipt of the pumiEnquiry return result APDU containing choice currLocation, the PUMI-detect PINX shall stop timer T1, send a pumiDivert invoke APDU in a FACILITY message to the Rerouteing PINX using the call reference of the incoming call, start timer T2 and enter state PUMIDivert.

- 12 -

The following data elements shall be included in the argument of the pumiDivert invoke APDU: − element hostingAddr as received in the pumiEnquiry return result APDU; − element callingNumber as received in the incoming SETUP message in the Calling party number information element; − element pumIdentity as received in the pumiEnquiry return result APDU; − element qSIGInfoElement containing an embedded Bearer capability information element, as received in the incoming SETUP message, and any of the following information elements which were received in the incoming SETUP message: High layer compatibility, Low layer compatibility and Progress indicator; − element callingUserSub, if a Calling party subaddress information element was received in the incoming SETUP message; − element callingUserName, if a callingName invoke APDU was received in the incoming SETUP message as defined in ECMA-164 and if CNIP is supported; − element pumUserSub, if a Called party subaddress information element was received in the incoming SETUP message. On receipt of a pumiEnquiry return result APDU containing choice cfuActivated, if the PUMI-detect PINX does not support the procedures of 6.8.6.1 the actions taken shall be an implementation matter, e.g. route the incoming call onwards to the Home PINX or release the incoming call. The PUMI-detect PINX is responsible for clearing the call independent signalling connection towards the Home PINX. This may occur on receipt of a return result APDU. Alternatively, the signalling connection may be retained for other applications, if appropriate. On receipt of the pumiDivert return result APDU, the PUMI-detect PINX shall stop timer T2 and enter state PUMI-Idle. 6.5.2.2

Ex c e p t io n a l p r o c e d u r e s On receipt of a pumiEnquiry return error APDU from the Home PINX indicating ‘invalidServedUserNr’, the PUMI-detect PINX shall stop timer T1, stimulate the sending of a DISCONNECT message with cause value #1 ‘Unallocated (unassigned) number’ for release of the basic call, and enter state PUMI-Idle. On receipt of a pumiEnquiry return error APDU from the Home PINX indicating ‘locationNotKnown’, the PUMI-detect PINX shall stop timer T1, stimulate the sending of a DISCONNECT message with cause value #3 ‘No route to destination’ for release of the basic call, and enter state PUMI-Idle. On receipt of a pumiEnquiry return error APDU from the Home PINX indicating ‘notAvailable’, the PUMI-detect PINX shall stop timer T1, stimulate the sending of a DISCONNECT message with cause value #20 ‘Subscriber absent’ for release of the basic call, and enter state PUMI-Idle. On receipt of a pumiEnquiry return error APDU from the Home PINX indicating ‘basicServiceNotProvided’, the PUMI-detect PINX shall stop timer T1, stimulate the sending of a DISCONNECT message with cause value #88 ‘Incompatible destination’ for release of the basic call, and enter state PUMI-Idle. On receipt of a pumiEnquiry reject APDU from the Home PINX, the PUMI-detect PINX shall stop timer T1, enter state PUMI-Idle, and continue with normal basic call procedures. If timer T1 expires (i.e. the pumiEnquiry invoke APDU is not answered by the Home PINX), the PUMI-detect PINX shall enter state PUMI-Idle and either stimulate the sending of a DISCONNECT message with cause value #41 ‘Temporary failure’ for release of the basic call, or continue with normal basic call procedures. On call clearing during state PUMI-Detected, the PUMI-detect PINX shall stop timer T1 and enter state PUMI-Idle.

- 13 -

On receipt of a pumiDivert return error or reject APDU from the Rerouteing PINX, the PUMI-detect PINX shall stop timer T2, enter state PUMI-Idle, and either stimulate the sending of a DISCONNECT message for release of the basic call, or provide Rerouteing PINX functionality locally by initiating a new call establishment to the Visitor PINX in accordance with 6.5.1.1. If timer T2 expires (i.e. the pumiDivert invoke APDU is not answered by the Rerouteing PINX), the PUMI-detect PINX shall enter state PUMI-Idle and either stimulate the sending of a DISCONNECT message for release of the basic call, or provide Rerouteing PINX functionality locally by initiating a new call establishment to the Visitor PINX in accordance with 6.5.1.1. On call clearing during state PUMI-Divert, the PUMI-detect PINX shall stop timer T2 and enter state PUMI-Idle. The PUMI-detect PINX is responsible for clearing the call independent signalling connection towards the Home PINX. This may occur on receipt of a return error or reject APDU, on expiry of timer T1 or on call clearing during state PUMI-Detect. Alternatively, the signalling connection may be retained for other applications, if appropriate. 6.5.3

A c t io n s a t t h e H o m e P I N X The SDL representation of procedures at the Home PINX is shown in D.3 of annex D. When a Home PINX also provides PUMI-detect PINX functionality, in support of ANF-PUMI, the joint requirements of 6.5.2 (for a PUMI-detect PINX) and 6.5.3 (for a Home PINX) shall apply, with the exception that any communication between the Home PINX functionality and the PUMI-detect PINX functionality will be an intra-PINX matter. The messages specified for sending from the Home PINX towards the PUMI-detect PINX or vice versa will not appear on any inter-PINX link.

6.5.3.1

Normal procedures On receipt of a pumiEnquiry invoke APDU using the call reference of a call independent signalling connection (as specified in 7.3 of ECMA-165), the Home PINX shall check that the PUM user, as identified by the PISN number in element pisnNumber, is defined in the HDB and that the basic service indicated by the basic call information elements embedded in element qSIGInfoElement is provided to that user. If the PUM user is defined in the HDB, and the current location of the PUM user is known for the basic service concerned, then the Home PINX shall answer the pumiEnquiry invoke APDU with a return result APDU containing choice currLocation. Element hostingAddr shall contain the PISN number of the hosting user and element pumIdentity shall contain the PISN number and/or an alternative identifier of the PUM user. The PISN number, if included, shall be in the form of a complete number even if the PISN number received in the invoke APDU was not a complete number.

6.5.3.2

Ex c e p t io n a l p r o c e d u r e s If the PUM user is not found in the HDB, the Home PINX shall answer the pumiEnquiry invoke APDU with a return error APDU containing the error invalidServedUserNr. If the PUM user has deregistered, the Home PINX shall answer the pumiEnquiry invoke APDU with a return error APDU containing the error notAvailable. If the current location of the PUM user is unknown, the Home PINX shall answer the pumiEnquiry invoke APDU with a return error APDU containing the error locationNotKnown. If the requested basic service is not provided, the Home PINX shall answer the pumiEnquiry invoke APDU with a return error APDU containing the error basicServiceNotProvided.

6.5.3.3

6.5.4

A d d it io n a l p r o c e d u r e s f o r C a ll F o r wa r d in g U n c o n d it io n a l On receipt of a pumiEnquiry invoke APDU, if the PUM user is defined in the HDB and SS-CFU is active, the Home PINX shall answer the pumiEnquiry invoke APDU with a return result APDU containing choice cfuActivated. A c t io n s a t t h e V is it o r P I N X The SDL representation of procedures at the Visitor PINX is shown in D.4 of annex D.

- 14 -

6.5.4.1

Normal procedures On receipt of a pumiInform invoke APDU in a SETUP message, the Visitor PINX may check that there is an entry in the VDB for the PUM user, as indicated by the PISN number or alternative identifier in element pumIdentity, for the basic service indicated by basic call information elements. In any case, the Visitor PINX shall attempt to establish the call to the TE that is indicated by the hosting address contained in the Called party number information element, including the pumIdentity in the call request.

6.5.4.2

Ex c e p t io n a l p r o c e d u r e s If the PUM user is not found in the VDB, the Visitor PINX may initiate call clearing according to the procedures in ECMA-143 with cause value #41 ‘Temporary failure’. All call failure situations shall be handled according to basic call procedures as specified in ECMA-143.

6.5.5

A c t io n s a t a Tr a n s it P I N X There are no special actions required in support of ANF-PUMI.

6.5.6

A c t io n s a t a n O r ig in a t in g P I N X An Originating PINX shall act as the Rerouteing PINX in accordance with 6.5.1, except where Rerouteing PINX functionality is provided at a separate PUMI-detect PINX.

6.6

ANF-PUMI impact of interworking with public ISDNs When interworking with a public ISDN which does not support an equivalent feature, the Incoming Gateway PINX shall act as the Rerouteing PINX in accordance with 6.5.1 in order to perform ANF-PUMI within the PISN, except where Rerouteing PINX functionality is provided at a separate PUMI-detect PINX.

6.7

ANF-PUMI impact of interworking with non-ISDNs When interworking with a non-ISDN which does not support an equivalent feature, the Incoming Gateway PINX shall act as the Rerouteing PINX in accordance with 6.5.1 in order to perform ANF-PUMI within the PISN, except where Rerouteing PINX functionality is provided at a separate PUMI-detect PINX.

6.8

Protocol interactions between ANF-PUMI and other supplementary services and ANFs This clause specifies protocol interactions with other supplementary services and ANFs for which stage 3 standards had been published at the time of publication of this Standard. For interactions with supplementary services and ANFs for which stage 3 standards are published subsequent to the publication of this Standard, see those other stage 3 standards. NOTE 4 Additional interactions that have no impact on the signalling protocol at the Q reference point can be found in the relevant stage 1 specifications. NOTE 5 Simultaneous conveyance of APDUs for ANF-PUMI and other supplementary services or ANFs 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.

6.8.1 6.8.1.1

Interaction with Calling Name Identification Presentation (SS-CNIP) The following interaction shall apply if SS-CNIP is supported in accordance with ECMA-164. A c t io n s a t t h e R e r o u t e in g P I N X When executing ANF-PUMI, the Rerouteing PINX shall include a callingName invoke APDU in the SETUP message to the Visitor PINX if this was included in the original SETUP message to the PUMI-detect PINX.

6.8.2

Interaction with Connected Name Identification Presentation (SS-CONP) No protocol interaction.

6.8.3

Interaction with Call Completion to Busy Subscriber (SS-CCBS) No protocol interaction.

- 15 -

6.8.4

I n t e r a c t i o n wit h C a l l C o m p l e t i o n o n N o R e p l y ( S S - C C N R ) No protocol interaction.

6.8.5

I n t e r a c t io n wit h C a ll Tr a n s f e r ( S S - C T) No protocol interaction.

6.8.6

I n t e r a c t io n wit h C a ll F o r wa r d in g U n c o n d it io n a l ( S S - C F U ) The following interaction shall apply if SS-CFU is supported in accordance with ECMA-174.

6.8.6.1

A c t io n s a t t h e P U M I - d e t e c t P I N X On receipt of a pumiEnquiry return result APDU containing choice cfuActivated, the PUMI-detect PINX shall stop timer T1 and act as the Served User PINX for SS-CFU in accordance with 6.5.4 of ECMA-174. The PUMI-detect PINX is responsible for clearing the call independent signalling connection towards the Home PINX. This may occur on receipt of a return result APDU. Alternatively, the signalling connection may be retained for other applications, if appropriate.

6.8.7

I n t e r a c t io n wit h C a ll F o r wa r d in g Bu s y ( S S - C F B) No protocol interaction.

6.8.8

I n t e r a c t i o n wit h C a l l F o r wa r d i n g N o R e p l y ( S S - C F N R ) No protocol interaction.

6.8.9

Interaction with Call Deflection (SS-CD) No protocol interaction.

6.8.10

Interaction with Path Replacement (ANF-PR) No protocol interaction.

6.8.11

I n t e r a c t i o n wit h C a l l O f f e r ( S S - C O ) The following interaction shall apply if SS-CO is supported in accordance with ECMA-192.

6.8.11.1

A c t io n s a t t h e R e r o u t e in g P I N X When executing ANF-PUMI, the Rerouteing PINX shall act as follows: − include a callOfferRequest invoke APDU in the SETUP message to the Visitor PINX if this was included in the original SETUP message to the PUMI-detect PINX; − include a pathRetain invoke APDU with callOffer bit set to ONE in the SETUP message to the Visitor PINX if this was included in the original SETUP message to the PUMI-detect PINX.

6.8.12

I n t e r a c t i o n wit h C a l l I n t r u s i o n ( S S - C I ) The following interaction shall apply if SS-CI is supported in accordance with ECMA-203.

6.8.12.1

A c t io n s a t t h e R e r o u t e in g P I N X When executing ANF-PUMI, the Rerouteing PINX shall act as follows: − include a callIntrusionRequest invoke APDU in the SETUP message to the Visitor PINX if this was included in the original SETUP message to the PUMI-detect PINX; − include a pathRetain invoke APDU with bit ci-low, ci-medium or ci-high set to ONE in the SETUP message to the Visitor PINX if this was included in the original SETUP message to the PUMI-detect PINX.

6.8.13

I n t e r a c t i o n wit h D o N o t D i s t u r b ( S S - D N D ) No protocol interaction.

6.8.14

Interaction with Do Not Disturb Override (SS-DNDO) The following interaction shall apply if SS-DNDO is supported in accordance with ECMA-194.

- 16 -

6.8.14.1

A c t io n s a t t h e R e r o u t e in g P I N X When executing ANF-PUMI, the Rerouteing PINX shall act as follows: − include a doNotDisturbOverrideQ invoke APDU in the SETUP message to the Visitor PINX if this was included in the original SETUP message to the PUMI-detect PINX; − include a pathRetain invoke APDU with bit dndo-low, dndo-medium or dndo-high set to ONE in the SETUP message to the Visitor PINX if this was included in the original SETUP message to the PUMI-detect PINX.

6.8.15

I n t e r a c t io n wit h A d v ic e O f C h a r g e ( S S - A O C ) The following interaction shall apply if SS-AOC is supported in accordance with ECMA-212.

6.8.15.1

A c t io n s a t t h e R e r o u t in g P I N X When executing ANF-PUMI, the Rerouteing PINX shall include a chargeRequest invoke APDU in the SETUP message to the Visitor PINX if this was included in the original SETUP message to the PUMI-detect PINX. On receipt of a pumiDivert invoke APDU for a call independent signalling connection which conveys an aocFinal invoke APDU, the Rerouteing PINX shall act in accordance to 6.5.1, except that the basic call procedures are replaced by the corresponding procedures for call independent signalling connections as specified in ECMA-165 clause 7.3, and shall include the aocFinal invoke APDU of the original received in the SETUP message sent to the Visitor PINX.

6.8.15.2

A c t io n s a t t h e P U M I - d e t e c t P I N X On receipt of a SETUP message for a call independent signalling connection which conveys an aocFinal invoke APDU, the PUMI-detect PINX shall act in accordance to 6.5.2, except that the basic call procedures are replaced by the corresponding procedures for call independent signalling connections as specified in ECMA-165 clause 7.3.

6.8.15.3

A c t io n s a t t h e V is it o r P I N X On receipt of a SETUP message for a call independent signalling connection which conveys an aocFinal invoke APDU and a pumiInform invoke APDU, the joint requirements of 6.5.4, except that the basic call procedures are replaced by the corresponding procedures for call independent signalling connections as specified in ECMA-165 clause 7.3, and 6.9.3.1 of ECMA-212 for an Originating PINX shall apply.

6.8.16

Interaction with Recall (SS-RE) No protocol interaction.

6.8.17

Interaction with Call Interception (ANF-CINT) No protocol interaction.

6.8.18

I n t e r a c t io n wit h Tr a n s it C o u n t e r ( A N F - TC ) The following interaction shall apply if ANF-TC is supported in accordance with ECMA-225.

6.8.18.1

6.8.19

A c t io n s a t t h e R e r o u t e in g P I N X When executing ANF-PUMI, the Rerouteing PINX may include a Transit counter information element in the SETUP message to the Visitor PINX. The value of the transit count field shall be zero.

I n t e r a c t i o n wit h R o u t e R e s t r i c t i o n C l a s s ( A N F - R R C ) The following interaction shall apply if ANF-RRC is supported in accordance with ISO/IEC 13241.

6.8.19.1

A c t io n s a t t h e R e r o u t e in g P I N X When executing ANF-PUMI, the Rerouteing PINX shall include a routeRestrictionClass invoke APDU in the SETUP message to the Visitor PINX if this was included in the original SETUP message to the PUMI-detect PINX. The element rac shall be the Route Access Class of either the calling user or the PUM user.

- 17 -

6.8.19.2

A c t io n s a t t h e P U M I - d e t e c t P I N X The PUMI-detect PINX may include a routeRestrictionClass invoke APDU received from the Home PINX, with element rac containing the Route Access Class of the PUM user, together with the pumiDivert invoke APDU in the FACILITY message to the Rerouteing PINX.

6.8.19.3

A c t io n s a t t h e H o m e P I N X The Home PINX may include a routeRestrictionClass invoke APDU, with element rac containing the Route Access Class of the PUM user, together with the pumiEnquiry return result APDU in the message to the PUMI-detect PINX.

6.8.20

I n t e r a c t io n wit h M e s s a g e W a it in g I n d ic a t io n ( S S - M W I ) The following interaction shall apply in case of an active InCall or AllCall registration if SS-MWI is supported in accordance with ECMA-242.

6.8.20.1

A c t io n s a t t h e R e r o u t e in g P I N X On receipt of a pumiDivert invoke APDU using the call reference of a call independent signalling connection which conveys a mwiActivate or mwiDeactivate invoke APDU, the Rerouteing PINX shall act in accordance with 6.5.1, except that basic call procedures are replaced by the corresponding procedures for call independent signalling connections as specified in ECMA-165 clause 7.3, and include the mwiActivate / mwiDeactivate invoke APDU in the SETUP message sent to the Visitor PINX.

6.8.20.2

A c t io n s a t t h e P U M I - d e t e c t P I N X On receipt of a SETUP message for a call independent signalling connection containing a mwiActivate or mwiDeactivate invoke APDU the PUMI-detect PINX may act in accordance with 6.5.2, except that basic call procedures are replaced by the corresponding procedures for call independent signalling connections as specified in ECMA-165 clause 7.3. NOTE 6 If the PUMI-detect PINX does not act on an incoming mwiActivate or mwiDeactivate invoke APDU the APDU will pass through to the Home PINX.

6.8.20.3

A c t io n s a t t h e H o m e P I N X On receipt of a SETUP message using the call reference of a call independent signalling connection and containing a mwiActivate or mwiDeactivate invoke APDU, the Home PINX may forward the mwiActivate / mwiDeactivate invoke APDU to the Visitor PINX, using a call independent signalling connection. The Home PINX shall also forward to the Message Centre PINX any mwiActivate / mwiDeactivate return result, return error or reject APDU subsequently returned by the Visitor PINX. NOTE 7 Other actions, e.g. recording the status of SS-MWI for the PUM user, are outside the scope of this Standard.

6.8.20.4

A c t io n s a t t h e V is it o r P I N X The Visitor PINX shall act as the SS-MWI Served User PINX for a visiting PUM user which is also a served user of SS-MWI. NOTE 8 A message waiting indication may be lost if the PUM user moves or has moved to another location.

6.8.21

Interaction with Wireless Terminal Location Registration (SS-WTLR) No protocol interaction.

6.8.22

I n t e r a c t i o n w i t h W i r e l e s s Te r m i n a l I n c o m i n g C a l l ( A N F - W T M I ) The following interaction shall apply if ANF-WTMI is supported in accordance with ECMA-304.

6.8.22.1

A c t io n s a t t h e W TM I R e r o u t e in g P I N X If a call is routed by means of ANF-WTMI and if the received SETUP message contained a pumiInform invoke APDU, the WTMI Rerouteing PINX shall include the pumiInform invoke APDU in the SETUP message to the Visitor PINX, in addition to the wtmiInform invoke APDU.

- 18 -

6.8.22.2

A c t io n s a t t h e V is it o r P I N X In addition to normal ANF-WTMI procedures the Visitor PINX shall include the pumIdentity in the call request to the current access of the PUM/WTM user.

6.8.23

I n t e r a c t i o n w i t h W i r e l e s s Te r m i n a l O u t g o i n g C a l l ( A N F - W T M O ) No protocol interaction.

6.8.24

Interaction with Wireless Terminal Authentication of the Terminal (SS-WTAT) No protocol interaction.

6.8.25

Interaction with Wireless Terminal Authentication of the Network (SS-WTAN) No protocol interaction.

6.8.26

I n t e r a c t i o n w i t h P r i v a t e U s e r M o b i l i t y R e g is t r a t i o n ( A N F - P U M R ) No protocol interaction.

6.8.27

I n t e r a c t i o n w i t h P r i v a t e U s e r M o b i l i t y O u t g o in g C a l l ( A N F - P U M O ) The following interaction shall apply if ANF-PUMO is supported in accordance with clause 7.

6.8.27.1

6.8.28

I n t e r a c t i o n s wit h C o m m o n I n f o r m a t i o n ( A N F - C M N ) The following interaction shall apply if ANF-CMN is supported in accordance with ECMA-251.

6.8.28.1

6.8.29

A c t io n s a t t h e P U M I - d e t e c t P I N X If a SETUP message contains a pumoCall invoke APDU then ANF-PUMI shall not be invoked on this call.

A c t io n s a t t h e R e r o u t e in g P I N X When executing ANF-PUMI, the Rerouteing PINX shall include a cmnRequest invoke APDU (for the ANF-CMN solicited service) or a cmnInform invoke APDU (for the unsolicited service) in the SETUP message to the Visitor PINX if this was included in the SETUP message to the PUMI-detect PINX.

I n t e r a c t io n wit h C a ll P r io r it y I n t e r r u p t i o n ( P r o t e c t i o n ) ( S S - C P I ( P ) ) The following interaction shall apply if SS-CPI(P) is supported in accordance with ECMA-264.

6.8.29.1

A c t io n s a t t h e R e r o u t e in g P I N X On receiving a pumiDivert invoke APDU, the Rerouteing PINX shall include in the SETUP message sent to the Visitor PINX any callInterruptionRequest invoke APDU or callProtectionRequest invoke APDU accompanying the pumiDivert invoke APDU.

6.8.29.2

A c t io n s a t t h e P U M I - d e t e c t P I N X If the incoming call for which ANF-PUMI is to be invoked contains a callInterruptionRequest invoke APDU or a callProtectionRequest invoke APDU, the PUMI-detect PINX shall include these APDUs with the pumiDivert invoke APDU in the FACILITY message sent to the Rerouteing PINX.

6.9 6.9.1

ANF-PUMI parameter values (timers) Timer T1 Timer T1 operates at the PUMI-detect PINX during state PUMI-Detected. Its purpose is to protect against the absence of a response to the pumiEnquiry invoke APDU. Timer T1 shall have a value not less than 15 s.

6.9.2

Timer T2 Timer T2 operates at the PUMI-detect PINX during state PUMI-Divert. Its purpose is to protect against the absence of a response to the pumiDivert invoke APDU. Timer T2 shall have a value not less than 15 s.

- 19 -

7

Signalling protocol for the support of ANF-PUMO

7.1

ANF-PUMO description ANF-PUMO permits the PISN to optionally process call requests from a PUM user at the home location, if required. NOTE 9 Further actions that may be performed at the visited location - verification of the PUM user's identity, local access to the service profile, local call processing - are outside the scope of this Standard.

7.2

ANF-PUMO operational requirements

7.2.1

Requirements on the Originating PINX Call establishment procedures for the outgoing side of an inter-PINX link and call release procedures, as specified in ECMA-143, shall apply. Generic procedures for the call related control of supplementary services, as specified in ECMA-165 for an End PINX, shall apply.

7.2.2

Requirements on the Home PINX Call establishment procedures for the incoming and outgoing side of an inter-PINX link and call release procedures, as specified in ECMA-143, shall apply. Generic procedures for the call related control of supplementary services, as specified in ECMA-165 for an End PINX, shall apply.

7.2.3

Requirements on a Transit PINX Basic call procedures for call establishment and call clearing at a Transit PINX, as specified in ECMA-143, shall apply. Generic procedures for the call related control of supplementary services, as specified in ECMA-165 for a Transit PINX, shall apply.

7.3

ANF-PUMO coding requirements

7.3.1

O p e r a t io n s The operation pumoCall defined in Abstract Syntax Notation number 1 (ASN.1) in 6.3.1, table 1, shall apply.

7.3.2 Information elements 7.3.2.1 Facility information element The operation defined in 7.3.1 shall be coded in the Facility information element in accordance with ECMA-165. The Facility information element shall always contain an NFE with the destinationEntity element having value endPINX. A Facility information element conveying a pumoCall invoke APDU shall also contain an Interpretation APDU with value clearCallIfAnyInvokePduNotRecognised. If sent in a FACILITY message, the Interpretation APDU shall either be omitted or included with value rejectAnyUnrecognisedInvokePdu. 7.3.2.2

7.3.3

Other information elements Any other information elements (e.g. Calling party number, Called party number) shall be coded in accordance with the rules of ECMA-143 and ECMA-165. Messages The Facility information element shall be conveyed in the messages as specified in clause 10 of ECMA-165.

- 20 -

7.4

ANF-PUMO State definitions

7.4.1

S t a t e s a t t h e O r ig in a t in g P I N X The procedures for the Originating PINX are written in terms of the following conceptual states existing within the ANF-PUMO Supplementary Service Control entity in that PINX in association with a particular PUMO Request.

7.4.1.1 7.4.2

P U M O - I d le ANF-PUMO is not operating. States at the Home PINX The procedures for the Home PINX are written in terms of the following conceptual states existing within the ANF-PUMO Supplementary Service Control entity in that PINX in association with a particular PUMO Request.

7.4.2.1

P U M O - I d le Ready for receipt of a pumoCall invoke APDU.

7.4.2.2

P U M O - A wa it - I n f o Further address information can be received in overlap mode.

7.5

ANF-PUMO signalling procedures Examples of message sequences are shown in annex C.

7.5.1 7.5.1.1

A c t io n s a t t h e O r ig in a t in g P I N X The SDL representation of procedures at the Originating PINX is shown in D.5 of annex D. Normal procedures If the Originating PINX decides to pass to the Home PINX for processing a call request that was initiated by the PUM user, the Originating PINX shall send a SETUP message according to ECMA-143 to the Home PINX. The SETUP message shall contain a pumoCall invoke APDU, in the Calling party number information element the number of the PUM user if available, and in the Called party number information element a number sufficient to route to the PUM user's Home PINX. If the PUM user's number is not available, the alternative identifier shall be included in the element pumIdentity of the invoke APDU's argument. If (part of) the intended destination number is already available it shall be included in element destinationNumber of the invoke APDU's argument. If the destination number is complete, element sendingComplete may also be included in the argument. NOTE 10 The number to be used in the Called party number information element is outside the scope of this Standard. It could, for example, be the number of the PUM user. Subsequently, if the destination number sent in the SETUP message was not complete, additional address information from the PUM user shall be included in the argument of pumoCall invoke APDUs, which shall be sent to the Home PINX in FACILITY messages, with the digit(s) encoded in element destinationNumber. The end of number information transmission may be indicated to the Home PINX by means of a sendingComplete element.

7.5.1.2 7.5.2 7.5.2.1

Ex c e p t io n a l p r o c e d u r e s Not applicable. A c t io n s a t t h e H o m e P I N X The SDL representation of procedures at the Home PINX is shown in D.6 of annex D. Normal procedures If on receipt of a SETUP message with a pumoCall invoke APDU enough digits of the destination number are present in the argument of the APDU to select a route for call extension, the Home PINX shall initiate call establishment towards the intended destination in accordance with ECMA-143 and join the two call legs. If the PUM user's number is not included in the Calling Party element of the received SETUP message, the alternative identifier from the element pumIdentity in the invoke APDU argument may be used to determine the PUM user's number before attempting to establish a call

- 21 -

towards the intended destination number. If the destination number is not complete, the Home PINX shall enter state PUMO-Await-Info, optionally send a PROGRESS message with progress description number 8 to the Originating PINX to stop T310 at Transit PINXs, and start timer T3. Otherwise it shall remain in state PUMO-Idle. NOTE 11 The only purpose of this progress description is to stop timer T310. It does not mean that in-band information is necessarily provided. While in state PUMO-Await-Info, additional number information received as argument of pumoCall invoke APDUs in a FACILITY message shall be used to select a route for call extension or, if the call has already been extended, passed on to the Subsequent PINX in accordance with ECMA-143. If the Home PINX regards the number information complete it shall stop timer T3, initiate call establishment towards the intended destination in accordance with ECMA-143 if not already done, join the two call legs, and return to state PUMO-Idle. Otherwise it shall restart timer T3 and stay in state PUMO-Await-Info. If a sendingComplete element is contained in a pumoCall invoke APDU received while in state PUMO-Await-Info, the Home PINX shall process any number information present in the argument, stop timer T3, initiate call establishment towards the intended destination in accordance with ECMA-143 if not already done, join the two call legs, and return to state PUMO-Idle. 7.5.2.2

Ex c e p t io n a l p r o c e d u r e s If timer T3 expires the Home PINX shall return to state PUMO-Idle and − if the number information received so far is considered sufficient, initiate call establishment towards the intended destination in accordance with ECMA-143, if not already done, and join the two call legs; − if the information is not sufficient to proceed, initiate call clearing with an appropriate cause value, e.g. #28 'invalid number format (address incomplete)'. A pumoCall invoke APDU received in a FACILITY message while in state PUMO-Idle shall be ignored.

7.5.3

7.6

A c t io n s a t t h e Tr a n s it P I N X No special actions are required for ANF-PUMO.

ANF-PUMO impact of interworking with public ISDNs Not applicable.

7.7

ANF-PUMO impact of interworking with non-ISDNs Not applicable.

7.8

Protocol interactions between ANF-PUMO and other supplementary services and ANFs This clause specifies protocol interactions with other supplementary services and ANFs for which stage 3 standards had been published at the time of publication of this Standard. For interactions with supplementary services and ANFs for which stage 3 standards are published subsequent to the publication of this Standard, see those other stage 3 standards. NOTE 12 Additional interactions that have no impact on the signalling protocol at the Q reference point can be found in the relevant stage 1 specifications. NOTE 13 Simultaneous conveyance of APDUs for ANF-PUMO and another supplementary service or 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. NOTE 14 The transmission of a Facility information element on one leg as a result of receiving a Facility information element on the other leg does not constitute a protocol interaction.

- 22 -

NOTE 15 If the Home PINX acts as the Originating PINX with regards to supplementary services is outside the scope of this Standard. 7.8.1

Interaction with Calling Name Identification Presentation (SS-CNIP) The following interaction shall apply if SS-CNIP is supported in accordance with ECMA-164.

7.8.1.1

A c t io n s a t t h e H o m e P I N X The Home PINX may include a callingName invoke APDU in the SETUP message, indicating the name of the PUM user.

7.8.2

Interaction with Connected Name Identification Presentation (SS-CONP) No protocol interaction.

7.8.3

Interaction with Call Completion to Busy Subscriber (SS-CCBS) No protocol interaction.

7.8.4

I n t e r a c t i o n wit h C a l l C o m p l e t i o n o n N o R e p l y ( S S - C C N R ) No protocol interaction.

7.8.5

I n t e r a c t io n wit h C a ll Tr a n s f e r ( S S - W T) No protocol interaction.

7.8.6

I n t e r a c t i o n wit h C a l l D i v e r s i o n ( S S - C F U , S S - C F B , S S - C F N R , S S - C D ) The following interaction shall apply if call diversion is supported in accordance with ECMA-174.

7.8.6.1 7.8.7

A c t io n s a t t h e H o m e P I N X On receipt of a callRerouting invoke APDU the Home PINX may act as the Rerouting PINX. Interaction with Path Replacement (ANF-PR) The following interaction shall apply if ANF-PR is supported in accordance with ECMA-176.

7.8.7.1

A c t io n s a t t h e H o m e P I N X The Home PINX may act as the Cooperating PINX when receiving a prPropose invoke APDU from either side.

7.8.8

I n t e r a c t i o n wit h C a l l O f f e r ( S S - C O ) No protocol interaction.

7.8.9

I n t e r a c t i o n wit h C a l l I n t r u s i o n ( S S - C I ) No protocol interaction.

7.8.10

I n t e r a c t i o n wit h D o N o t D i s t u r b ( S S - D N D ) No protocol interaction.

7.8.11

Interaction with Do Not Disturb Override (SS-DNDO) No protocol interaction.

7.8.12

I n t e r a c t io n wit h A d v ic e o f C h a r g e ( S S - A O C ) No protocol interaction.

7.8.13

Interaction with Recall (SS-RE) No protocol interaction.

7.8.14

Interaction with Call Interception (ANF-CINT) The following interaction shall apply if ANF-CINT is supported in accordance with ECMA-221.

7.8.14.1 7.8.15

A c t io n s a t t h e H o m e P I N X The Home PINX may act as Intercepting PINX.

I n t e r a c t io n wit h Tr a n s it C o u n t e r ( A N F - TC ) The following interaction shall apply if ANF-TC is supported in accordance with ECMA-225.

- 23 -

7.8.15.1

7.8.16

A c t io n s a t t h e H o m e P I N X When executing ANF-PUMO, the Home PINX may include a Transit counter information element in the SETUP message.

I n t e r a c t i o n wit h R o u t e R e s t r i c t i o n C l a s s ( A N F - R R C ) The following interaction shall apply if ANF-RRC is supported in accordance with ISO/IEC 13241.

7.8.16.1

A c t io n s a t t h e H o m e P I N X When executing ANF-PUMO, the Home PINX may include a routeRestrictionClass invoke APDU in the SETUP message, indicating the Route Access Class of the PUM user.

7.8.17

I n t e r a c t io n wit h M e s s a g e W a it in g I n d ic a t io n ( S S - M W I ) No protocol interaction.

7.8.18

Interaction with Wireless Terminal Location Registration (SS-WTLR) No protocol interaction.

7.8.19

I n t e r a c t i o n w i t h W i r e l e s s Te r m i n a l I n c o m i n g C a l l ( A N F - W T M I ) No protocol interaction.

7.8.20

I n t e r a c t i o n w i t h W i r e l e s s Te r m i n a l O u t g o i n g C a l l ( A N F - W T M O ) No protocol interaction.

7.8.21

Interaction with Wireless Terminal Authentication of the Terminal (SS-WTAT) No protocol interaction.

7.8.22

Interaction with Wireless Terminal Authentication of the Network (SS-WTAN) No protocol interaction.

7.8.23

I n t e r a c t i o n w i t h P r i v a t e U s e r M o b i l i t y R e g is t r a t i o n ( A N F - P U M R ) No protocol interaction.

7.8.24

Interaction with Private User Mobility Incoming Call (ANF-PUMI) This interaction is specified in 6.8.27.

7.8.25

I n t e r a c t i o n wit h C o m m o n I n f o r m a t i o n ( A N F - C M N ) No protocol interaction.

7.8.26

I n t e r a c t io n wit h C a ll P r io r it y I n t e r r u p t i o n ( P r o t e c t i o n ) ( S S - C P I ( P ) ) No protocol interaction.

7.9

Parameter values (timers)

7.9.1

Timers at the Originating PINX None.

7.9.2

Timers at the Home PINX T3 Information receiving This timer is started on receipt of the first pumoCall invoke APDU with incomplete number information, restarted on receipt of a further pumoCall invoke APDU with incomplete number information, and stopped when a pumoCall invoke APDU containing final number information or an element sendingComplete is received from the Originating PINX or an ALERTING or CONNECT message is received from the Terminating PINX. On expiry of timer T3 the call is either cleared or proceeds as normal basic call. The value of timer T3 should be in the range 14 - 16 seconds.

- 24 -

- 25 -

Annex A ( n o r ma tiv e )

Protocol Implementation Conformance Statement (PICS) proforma

A.1

Introduction The supplier of a protocol implementation which is claimed to conform to this Standard shall complete the following Protocol Implementation Conformance Statement (PICS) proforma. A completed PICS proforma is the PICS for the implementation in question. The PICS is a statement of which capabilities and options of the protocol have been implemented. The PICS can have a number of uses, including use: − by the protocol implementor, as a check list to reduce the risk of failure to conform to the Standard through oversight; − by the supplier and acquirer, or potential acquirer, of the implementation, as a detailed indication of the capabilities of the implementation, stated relative to the common basis for understanding provided by the Standard's PICS proforma; − by the user or potential user of the implementation, as a basis for initially checking the possibility of interworking with another implementation - while interworking can never be guaranteed, failure to interwork can often be predicted from incompatible PICS's. − by a protocol tester, as the basis for selecting appropriate tests against which to assess the claim for conformance of the implementation.

A.2

Instructions for completing the PICS proforma

A.2.1

General structure of the PICS proforma The PICS proforma is a fixed format questionnaire divided into subclauses each containing a group of individual items. Each item is identified by an item number, the name of the item (question to be answered), and the reference(s) to the clause(s) specifying the item in the main body of this Standard. The "Status" column indicates whether an item is applicable and if so whether support is mandatory or optional. The following terms are used: m

mandatory (the capability is required for conformance to the protocol);

o

optional (the capability is not required for conformance to the protocol, but if the capability is implemented it is required to conform to the protocol specifications);

o.<n>

optional, but support of at least one of the group of options labelled by the same numeral <n> is required;

x

prohibited;

c.<cond>

conditional requirement, depending on support for the item or items listed in condition <cond>;

<item>:m

simple conditional requirement, the capability being mandatory if item number <item> is supported, otherwise not applicable;

<item>:o

simple conditional requirement, the capability being optional if item number <item> is supported, otherwise not applicable.

Answers to the questionnaire items are to be provided either in the "Support" column, by simply marking an answer to indicate a restricted choice (Yes or No), or in the "Not Applicable" column (N/A).

- 26 -

A.2.2

Additional information Items of Additional Information allow a supplier to provide further information intended to assist the interpretation of the PICS. It is not intended or expected that a large quantity will be supplied, and a PICS can be considered complete without any such information. Examples might be an outline of the ways in which a (single) implementation can be set up to operate in a variety of environments and configurations. References to items of Additional Information may be entered next to any answer in the questionnaire, and may be included in items of Exception information.

A.2.3

Exception information It may occasionally happen that a supplier will wish to answer an item with mandatory or prohibited status (after any conditions have been applied) in a way that conflicts with the indicated requirement. No pre-printed answer will be found in the Support column for this. Instead, the supplier is required to write into the Support column an x.<i> reference to an item of Exception Information, and to provide the appropriate rationale in the Exception item itself. An implementation for which an Exception item is required in this way does not conform to this Standard. A possible reason for the situation described above is that a defect in the Standard has been reported, a correction for which is expected to change the requirement not met by the implementation.

- 27 -

A.3

PICS proforma for ANF-PUMI

A.3.1

Implementation Identification

Supplier Contact point for queries about the PICS Implementation Name(s) and Version(s) Other information necessary for full identification, e.g., name(s) and version(s) for machines and/or operating systems; system name(s) Only the first three items are required for all implementations; other information may be completed as appropriate in meeting the requirement for full identification. The terms Name and Version should be interpreted appropriately to correspond with a supplier's terminology (e.g., Type, Series, Model).

A.3.2

Protocol Summary

Protocol Version

1.0

Addenda Implemented (if applicable) Amendments Implemented Have any exception items been required (see A.2.3) ?

Date of Statement

No [ ]

Yes [ ]

(The answer YES means that the implementation does not conform to this Standard)

- 28 -

A.3.3

General

Item

Question/feature

References

Status

N/A

Support

A1

Support of ANF-PUMI, call rerouteing

o.1

Yes [ ] No [ ]

A2

Support of ANF-PUMI, forward switching

o.1

Yes [ ] No [ ]

A3

Behaviour as PUMI-detect PINX

c.1

[ ]

o: Yes [ ] No [ ]

A4

Behaviour as Home PINX for ANF-PUMI

c.1

[ ]

o: Yes [ ] No [ ]

A5

Behaviour as Visitor PINX for ANF-PUMI

c.1

[ ]

o: Yes [ ] No [ ]

A6

Behaviour as Originating PINX for ANF-PUMI

c.1

[ ]

o: Yes [ ] No [ ]

A7

Behaviour as Incoming Gateway PINX

c.1

[ ]

o: Yes [ ] No [ ]

A8

Behaviour as Rerouteing PINX

c.2

[ ]

m: Yes [ ]

A9

Support of relevant procedures of ECMA-143 and ECMA-165

6.2

m

Yes [ ]

c.1: if A1 or A2 then o.2 else N/A c.2: if (A1 and (A6 or A7)) or (A2 and A3) then mandatory else N/A

A.3.4 Item

Procedures Question/feature

References

Status

N/A

Support

B1

Signalling procedures at a Rerouteing PINX

6.5.1

A8:m

[]

m: Yes [ ]

B2

Signalling procedures at a PUMI-detect PINX

6.5.2

A3:m

[]

m: Yes [ ]

B3

Signalling procedures at a Home PINX

6.5.3.1 6.5.3.2

A4:m

[]

m: Yes [ ]

B4

Signalling procedures at a Visitor PINX

6.5.4

A5:m

[]

m: Yes [ ]

B5

Additional procedures at a Home PINX for Call Forwarding Unconditional

6.5.3.3

A4:o

[]

o: Yes [ ] No [ ]

- 29 -

A.3.5

Coding

Item

Question/feature

References

Status

N/A

Support

C1

Receipt of pumiDivert invoke APDU and sending of return result and return error APDUs

6.3

c.1

[]

m: Yes [ ]

C2

Sending of pumiInform invoke APDU

6.3

A8:m

[]

m: Yes [ ]

C3

Sending of pumiEnquiry invoke APDU and receipt of return result and return error APDUs

6.3

A3:m

[]

m: Yes [ ]

C4

Sending of pumiDivert invoke APDU and receipt of return result and return error APDUs

6.3

c.2

[]

m: Yes [ ]

C5

Receipt of pumiEnquiry invoke APDU and sending of return result and return error APDUs

6.3

A4:m

[]

m: Yes [ ]

C6

Receipt of pumiInform invoke APDU

6.3

A5:m

[]

m: Yes [ ]

References

Status

N/A

Support

c.1: if A1 and A8 then mandatory else N/A c.2: if A1 and A3 then mandatory else N/A

A.3.6 Item

Timers Question/feature

D1

Support of Timer T1

6.9.1

A3:m

[]

m: Yes [ ] Value [ . . . .]

D2

Support of Timer T2

6.9.2

c.1

[]

m: Yes [ ] Value [ . . . .]

References

Status

N/A

Support

ECMA-164

o

6.8.1.1

c.1

[]

References

Status

N/A

ECMA-174

o

6.8.6.1

c.1

c.1: if A1 and A3 then mandatory else N/A

A.3.7 Item

Interactions between ANF-PUMI and SS-CNIP Question/feature

E1

Support of SS-CNIP

E2

Interactions at Rerouteing PINX

Yes [ ] No [ ] m: Yes [ ]

c.1: if E1 and A8 then mandatory, else N/A

A.3.8 Item

Interactions between ANF-PUMI and SS-CFU Question/feature

F1

Support of SS-CFU

F2

Interactions at PUMI-detect PINX c.1: if F1 and A3 then mandatory, else N/A

Support Yes [ ] No [ ]

[]

m: Yes [ ]

- 30 -

A.3.9 Item

Interactions between ANF-PUMI and SS-CO Question/feature

G1

Support of SS-CO

G2

Interactions at Rerouteing PINX

References

Status

N/A

ECMA-192

o

6.8.11.1

c.1

[]

References

Status

N/A

ECMA-203

o

6.8.12.1

c.1

[]

References

Status

N/A

ECMA-194

o

6.8.14.1

c.1

[]

References

Status

N/A

ECMA-212

o

Support Yes [ ] No [ ] m: Yes [ ]

c.1: if G1 and A8 then mandatory, else N/A

A.3.10 Interactions between ANF-PUMI and SS-CI Item

Question/feature

H1

Support of SS-CI

H2

Interactions at Rerouteing PINX

Support Yes [ ] No [ ] m: Yes [ ]

c.1: if H1 and A8 then mandatory, else N/A

A.3.11 Interactions between ANF-PUMI and SS-DNDO Item

Question/feature

I1

Support of SS-DNDO

I2

Interactions at Rerouteing PINX

Support Yes [ ] No [ ] m: Yes [ ]

c.1: if I1 and A8 then mandatory, else N/A

A.3.12 Interactions between ANF-PUMI and SS-AOC Item

Question/feature

Support

J1

Support of SS-AOC

Yes [ ] No [ ]

J2

Interactions at Rerouteing PINX

6.8.15.1

c.1

[]

m: Yes [ ]

J3

Interactions at PUMI-detect PINX

6.8.15.2

c.2

[]

m Yes [ ]

J4

Interactions at Visitor PINX

6.8.15.3

c.3

[]

m Yes [ ]

References

Status

N/A

ECMA-225

o

6.8.18.1

c.1

c.1: if J1 and A8 then mandatory, else N/A c.2: if J1 and A3 then mandatory, else N/A c.3: if J1 and A5 then mandatory, else N/A

A.3.13 Interactions between ANF-PUMI and ANF-TC Item

Question/feature

K1

Support of ANF-TC

K2

Interactions at Rerouteing PINX c.1: if K1 and A8 then optional, else N/A

Support Yes [ ] No [ ]

[]

o: Yes [ ] No [ ]

- 31 -

A.3.14 Interactions between ANF-PUMI and ANF-RRC Item

Question/feature

References

Status

ISO/IEC 13241

o

N/A

Support

L1

Support of ANF-RRC

Yes [ ] No [ ]

L2

Interactions at Rerouteing PINX

6.8.19.1

c.1

[]

m: Yes [ ]

L3

Interactions at PUMI-detect PINX

6.8.19.2

c.2

[]

o: Yes [ ] No [ ]

L4

Interactions at Home PINX

6.8.19.3

c.3

[]

o: Yes [ ] No [ ]

References

Status

N/A

Support

ECMA-242

o

c.1: if L1 and A8 then mandatory, else N/A c.2: if L1 and A3 then optional, else N/A c.3: if L1 and A4 then optional, else N/A

A.3.15 Interactions between ANF-PUMI and SS-MWI Item

Question / feature

M1

Support of SS-MWI

Yes [ ] No [ ]

M2

Interactions at Rerouteing PINX

6.8.20.1

c.1

[ ]

m: Yes [ ]

M3

Interactions at PUMI-detect PINX

6.8.20.2

c.2

[ ]

o: Yes [ ] No [ ]

M4

Interactions at Home PINX

6.8.20.3

c.3

[ ]

o: Yes [ ] No [ ]

M5

Interactions at Visitor PINX

6.8.20.4

c.4

[ ]

m: Yes [ ]

References

Status

N/A

ECMA-304

o

c.1: if M1 and A8 then mandatory, else N/A c.2: if M1 and A3 then optional, else N/A c.3: if M1 and A4 then optional, else N/A c.4: if M1 and A5 then mandatory, else N/A

A.3.16 Interactions between ANF-PUMI and ANF-WTMI Item

Question / feature

Support

N1

Support of ANF-WTMI

Yes [ ] No [ ]

N2

Interactions at WTMI Rerouteing PINX

6.8.22.1

N1:m

[ ]

m: Yes [ ]

N3

Interactions at Visitor PINX

6.8.22.2

c.1

[ ]

m: Yes [ ]

References

Status

N/A

7

o

6.8.27.1

c.1

c.1: if N1 and A5 then mandatory, else N/A

A.3.17 Interactions between ANF-PUMI and ANF-PUMO Item

Question / feature

O1

Support of ANF-PUMO

O2

Interactions at PUMI-detect PINX c.1: if O1 and A3 then mandatory, else N/A

Support Yes [ ] No [ ]

[ ]

m: Yes [ ]

- 32 -

A.3.18 Interactions between ANF-PUMI and ANF-CMN Item

Question/feature

P1

Support of ANF-CMN

P2

Interactions at Rerouteing PINX

References

Status

N/A

ECMA-251

o

6.8.28.1

c.1

[]

References

Status

N/A

ECMA-264

o

Support Yes [ ] No [ ] m: Yes [ ]

c.1: if P1 and A8 then mandatory, else N/A

A.3.19 Interactions between ANF-PUMI and SS-CPI(P) Item

Question/feature

Support

Q1

Support of SS-CPI(P)

Q2

Interactions at Rerouteing PINX

6.8.29.1

c.1

[]

m: Yes [ ]

Q3

Interactions at PUMI-detect PINX

6.8.29.2

c.2

[]

m: Yes [ ]

c.1: if Q1 and A8 then mandatory, else N/A c.2: if Q1 and A3 then mandatory, else N/A

Yes [ ] No [ ]

- 33 -

A.4

PICS proforma for ANF-PUMO

A.4.1

Implementation Identification

Supplier Contact point for queries about the PICS Implementation Name(s) and Version(s) Other information necessary for full identification, e.g., name(s) and version(s) for machines and/or operating systems; system name(s) Only the first three items are required for all implementations; other information may be completed as appropriate in meeting the requirement for full identification. The terms Name and Version should be interpreted appropriately to correspond with a supplier's terminology (e.g., Type, Series, Model).

A.4.2

Protocol Summary

Protocol Version

1.0

Addenda Implemented (if applicable) Amendments Implemented Have any exception items been required (see A.2.3) ?

Date of Statement

No [ ]

Yes [ ]

(The answer YES means that the implementation does not conform to this Standard)

- 34 -

A.4.3

General

Item

Question/feature

A1

Behaviour as Originating PINX for ANF-PUMO

o.1

Yes [ ] No [ ]

A2

Behaviour as Home PINX for ANF-PUMO

o.1

Yes [ ] No [ ]

A3

Support of relevant procedures of ECMA-143 and ECMA-165

7.2

m

Yes [ ]

References

Status

N/A

A.4.4

References

Status

N/A

Support

Procedures

Item

Question / feature

Support

B1

PUMO procedures at Originating PINX

7.5.1

A1:m

[ ]

m: Yes [ ]

B2

PUMO procedures at Home PINX

7.5.2

A2:m

[ ]

m: Yes [ ]

References

Status

N/A

A.4.5

Coding

Item

Question / feature

C1

Sending of pumoCall invoke APDU

7.3.1

A1:m

[ ]

m: Yes [ ]

C2

Receipt of pumoCall invoke APDU

7.3.1

A2:m

[ ]

m: Yes [ ]

References

Status

N/A

Support

7.9.2

A2:m

[]

m: Yes [ ] Value: .............

References

Status

N/A

Support

ECMA-164

o

7.8.1.1

c.1

A.4.6 Item D1

A.4.7 Item

Support

Timers Question / feature Support of timer T3

Interactions between ANF-PUMO and SS-CNIP Question/feature

E1

Support of SS-CNIP

E2

Interactions at Home PINX

Yes [ ] No [ ] []

o: Yes [ ] No [ ]

N/A

Support

c.1: if E1 and A2 then optional, else N/A

A.4.8 Item

Interactions between ANF-PUMO and Call Diversion Question / feature

References

Status

F1

Support of SS-CFU/CFB/CFNR/CD

ECMA-174

o

F2

Home PINX acts as Rerouting PINX

7.8.6.1

c.1

c.1: if F1 and A2 then optional, else N/A

Yes [ ] No [ ] [ ]

o: Yes [ ] No [ ]

- 35 -

A.4.9 Item

Interactions between ANF-PUMO and ANF-PR Question / feature

G1

Support of ANF-PR

G2

Home PINX acts as Cooperating PINX

References

Status

N/A

Support

ECMA-176

o

7.8.7.1

c.1

[ ]

o: Yes [ ] No [ ]

References

Status

N/A

Support

ECMA-221

o

7.8.14.1

c.1

[ ]

o: Yes [ ] No [ ]

References

Status

N/A

Support

ECMA-225

o

7.8.15.1

c.1

[]

o:Yes [ ] No [ ]

References

Status

N/A

Support

ISO/IEC 13241

o

7.8.16.1

c.1

Yes [ ] No [ ]

c.1: if G1 and A2 then optional, else N/A

A.4.10 Interactions between ANF-PUMO and ANF-CINT Item

Question / feature

H1

Support of ANF-CINT

H2

Home PINX acts as Intercepting PINX

Yes [ ] No [ ]

c.1: if H1 and A2 then optional, else N/A

A.4.11 Interactions between ANF-PUMO and ANF-TC Item

Question/feature

I1

Support of ANF-TC

I2

Interactions at Home PINX

Yes [ ] No [ ]

c.1: if I1 and A2 then optional, else N/A

A.4.12 Interactions between ANF-PUMO and ANF-RRC Item

Question/feature

J1

Support of ANF-RRC

J2

Interactions at Home PINX c.1: if J1 and A2 then optional, else N/A

Yes [ ] No [ ] []

o:Yes [ ] No [ ]

- 36 -

- 37 -

Annex B ( in f o r ma tiv e )

Imported ASN.1 definitions

The content of this annex has been deleted to remove duplicate ASN.1 definitions defined elsewhere.

- 38 -

- 39 -

Annex C ( in f o r ma tiv e )

Examples of Message Sequences

This annex describes some typical message flows for ANF-PUMI and ANF-PUMO. The following conventions are used in the figures of this annex: 1.

The following notation is used: Basic call message containing ANF-PUMI / ANF-PUMO information Basic call message without ANF-PUMI / ANF-PUMO information Call indepenent signalling connection message containing ANF-PUMI information Call indepenent signalling connection message without ANF-PUMI information xxx.inv xxx.res xxx.err

Invoke APDU for operation xxx Return result APDU for operation xxx Return error APDU for operation xxx

2.

The figures show messages exchanged via Protocol Control between PINXs involved in ANF-PUMI / ANFPUMO. Only messages relevant to ANF-PUMI / ANF-PUMO are shown.

3.

Only the relevant information content (e.g. remote operation APDUs, notifications, information elements) is listed below each message name. The Facility information elements containing remote operation APDUs are not explicitly shown. Information with no impact on ANF-PUMI / ANF-PUMO is not shown.

- 40 -

C.1

Example message sequences for normal operation of ANF-PUMI Figure C.1 shows an example of normal operation of ANF-PUMI. Rerouting PINX

PUMI detect PINX

Transit PINX SETUP

SETUP

CALL PROCEEDING

Transit PINX

SETUP pumiEnquiry.inv

CALL PROCEEDING

SETUP pumiEnquiry.inv

CALL PROCEEDING

FACILITY pumiDivert.inv

CALL PROCEEDING CONNECT pumiEnquiry.res

CONNECT pumiEnquiry.res

FACILITY pumiDivert.inv

RELEASE

DISCONNECT pumiDivert.res

Transit PINX SETUP pumiInform.inv

RELEASE

RELEASE COMPLETE

DISCONNECT pumiDivert.res

Home PINX

RELEASE COMPLETE

Visitor PINX SETUP pumiInform.inv

CALL PROCEEDING

CALL PROCEEDING

F ig u r e C . 1 - Ex a m p le o f n o r m a l o p e r a t io n o f A N F - P U M I Figure C.2 shows an example of ANF-PUMI when the Rerouteing fails and the PUMI-detect PINX performs forward switching to the Visitor PINX. Rerouting PINX

Transit PINX SETUP

CALL PROCEEDING

Transit PINX

PUMI detect PINX SETUP CALL PROCEEDING

SETUP pumiEnquiry.inv

SETUP pumiEnquiry.inv

CALL PROCEEDING

FACILITY pumiDivert.inv FACILITY pumiDivert.err

FACILITY pumiDivert.inv

CALL PROCEEDING CONNECT pumiEnquiry.res

CONNECT pumiEnquiry.res RELEASE

FACILITY pumiDivert.err

Home PINX

RELEASE

RELEASE COMPLETE

RELEASE COMPLETE

Transit PINX SETUP pumiInform.inv CALL PROCEEDING

Visitor PINX SETUP pumiInform.inv CALL PROCEEDING

F ig u r e C . 2 - Ex a m p le o f f o r wa r d s w i t c h i n g b y t h e P U M I - d e t e c t P I N X

- 41 -

C.2

Examples of unsuccessful operation of ANF-PUMI

C.2.1

PUM user unknown in Home PINX Figure C.3 shows an example of unsuccessful operation of ANF-PUMI due to PUM user unknown.

Rerouting PINX

Transit PINX SETUP

SETUP

CALL PROCEEDING

Transit PINX

PUMI detect PINX

SETUP pumiEnquiry.inv

CALL PROCEEDING

SETUP pumiEnquiry.inv

CALL PROCEEDING

CALL PROCEEDING CONNECT pumiEnquiry.err

CONNECT pumiEnquiry.err

DISCONNECT cause = 1

DISCONNECT cause = 1

RELEASE

RELEASE

RELEASE

RELEASE COMPLETE

Home PINX

RELEASE

RELEASE COMPLETE

RELEASE COMPLETE

RELEASE COMPLETE

Figure C.3 - Example of ANF-PUMI failure due to PUM user unknown

C.2.2

PUM user has de-registered Figure C.4 shows an example of unsuccessful operation of ANF-PUMI due to the PUM user having deregistered. Rerouting PINX

Transit PINX SETUP

CALL PROCEEDING

PUMI detect PINX SETUP CALL PROCEEDING

Transit PINX

SETUP pumiEnquiry.inv CALL PROCEEDING

DISCONNECT cause = 20 RELEASE RELEASE COMPLETE

DISCONNECT cause = 20

CONNECT pumiEnquiry.err RELEASE

RELEASE RELEASE COMPLETE

RELEASE COMPLETE

Home PINX

SETUP pumiEnquiry.inv CALL PROCEEDING CONNECT pumiEnquiry.err

RELEASE RELEASE COMPLETE

Figure C.4 - Example of ANF-PUMI failure due to PUM user having de-registered

- 42 -

C.2.3

Collision with location update detected by Visitor PINX Figure C.5 shows an example of unsuccessful operation of ANF-PUMI due to collision with location update. Rerouting PINX

Transit PINX SETUP

SETUP

CALL PROCEEDING

Transit PINX

PUMI detect PINX

SETUP pumiEnquiry.inv

CALL PROCEEDING

CALL PROCEEDING

RELEASE

DISCONNECT pumiDivert.res

DISCONNECT pumiDivert.res

Transit PINX

SETUP pumiInform.inv CALL PROCEEDING DISCONNECT cause = 41

CONNECT pumiEnquiry.res

FACILITY pumiDivert.inv

FACILITY pumiDivert.inv

SETUP pumiInform.inv

SETUP pumiEnquiry.inv CALL PROCEEDING CONNECT pumiEnquiry.res RELEASE

RELEASE COMPLETE

Visitor PINX

Home PINX

RELEASE COMPLETE

A location update is performed from a new Visitor location or a location deregistration is performed.

CONNECT pumDelReg.res

SETUP pumDelReg.inv RELEASE COMPLETE

CALL PROCEEDING DISCONNECT cause = 41

Figure C.5 - Example of ANF-PUMI failure due to collision with location update

- 43 -

C.3

Successful invocation of ANF-PUMO

C.3.1

With overlap operation Figure C.6 shows an example of the invocation of ANF-PUMO where the destination number is sent in pieces. Originating PINX

Transit PINX SETUP

Home PINX

Subsequent PINX

SETUP

pumoCall.inv CALL PROCEEDING

pumoCall.inv CALL PROCEEDING

PROGRESS

PROGRESS

FACILITY

FACILITY

pumoCall.inv

pumoCall.inv

FACILITY

FACILITY

pumoCall.inv

pumoCall.inv

SETUP

F ig u r e C . 6 - S u c c e s s f u l in v o c a t io n o f A N F - P U M O wit h o v e r la p o p e r a t io n

C.3.2

With en-bloc operation Figure C.7 shows an example of the invocation of ANF-PUMO where the whole destination number is sent in the first message. Originating PINX

Transit PINX SETUP

pumoCall.inv CALL PROCEEDING

Home PINX

Subsequent PINX

SETUP pumoCall.inv

SETUP

CALL PROCEEDING

F ig u r e C . 7 - S u c c e s s f u l in v o c a t io n o f A N F - P U M O wit h e n - b lo c o p e r a t io n

- 44 -

- 45 -

Annex D ( in f o r ma tiv e )

Specification and Description Language (SDL) representation of procedures

The diagrams in this annex use the Specification and Description Language defined in ITU-T Recommendation Z.100. Each diagram represents the behaviour of an ANF-PUMI / ANF-PUMO Service Control entity at a particular type of PINX. In accordance with the protocol model described in ECMA-165, the Supplementary Service Control entity uses, via the Coordination function, the services of Generic Functional Procedures Control and Basic Call Control. Where an output symbol represents a primitive to the Coordination function, and that primitive results in a message being sent, the output symbol bears the name of the message and any remote operations APDU(s) contained in that message. In the case of a message specified in ECMA-143, basic call actions associated with the sending of that message are deemed to occur. Where an input symbol represents a primitive from the Coordination function, and that primitive is the result of a message being received, the input signal bears the name of the message and any remote operations APDU(s) contained in that message. In the case of a message specified in ECMA-143, basic call actions associated with the receipt of that message are deemed to have occurred. The following abbreviations are used: inv

Invoke APDU

res

Return result APDU

err

Return error APDU

rej

Reject APDU

- 46 -

D.1

SDL representation of ANF-PUMI at the Rerouteing PINX Figure D.1 shows the behaviour of an ANF-PUMI Supplementary Service Control entity within the Rerouteing PINX. Input signals from the right and output signals to the right represent primitives to and from the Co-ordination Function in respect of messages sent and received.

ExecIdle

FACILITY pumiDivert.inv

PUMI possible?

No

Yes

Stimulate release of basic call to PUMI-detect PINX

DISCONNECT pumiDivert.res

FACILITY pumiDivert.err

Stimulate establishment of basic call to Visitor PINX

SETUP pumiInform.inv

ExecIdle

Figure D.1 - SDL representation of ANF-PUMI at the Rerouteing PINX

- 47 -

D.2

SDL representation of ANF-PUMI at the PUMI-detect PINX Figure D.2 shows the behaviour of an ANF-PUMI entity within the PUMI-detect PINX. Input signals from the right and output signals to the right represent primitives to and from the Co-ordination Function in respect of messages sent and received. Also protocol timer expiry is indicated by an input signal from the right. Input signals from the left represent internal stimuli.

PUMI-Idle

PUMI-Divert

PUMI call detected

DISCONNECT pumiDivert.res

Call cleared

Message with pumiEnquiry.inv to Home PINX

FACILITY pumiDivert.err

Stop T2

Stop T2

Start T1

Forward switching supported No

Stimulate release of basic call

PUMI-Detected

Message with pumiEnquiry.res

T1 Expiry

Stop T1

CFU activated ?

T2 Expiry

Message with pumiEnquiry.err or reject

Call cleared

Stop T1

Stop T1

Yes

Do forward switching to the Visitor PINX

Yes

Stimulate release of basic call

No

FACILITY pumiDivert.inv to Rerouteing PINX

Invoke CFU if supported by the PINX

Start T2

PUMI-Divert

PUMI-Idle

Figure D.2 - SDL representation of ANF-PUMI at the PUMI-detect PINX

- 48 -

D.3

SDL representation of ANF-PUMI at the Home PINX Figure D.3 shows the behaviour of an ANF-PUMI entity within the Home PINX. Input signals from the right and output signals to the right represent primitives to and from the Co-ordination Function in respect of messages sent and received.

HomeIdle

Message with pumiEnquiry.inv

Retrieve information from HDB

User found?

Yes

No

Return error invalidServedUserNumber

Service provided ?

Yes

No

Return error basicServiceNotProvided

PUM user registered ?

Yes

No

Return error notAvailable

Location known?

Yes

No

Return error locationNotKnown

SS-CFU activated ?

No

Yes

Insert diverted-to address and PUM user name into response

Message with pumiEnquiry.err

Message with pumiEnquiry.res

HomeIdle

Figure D.3 - SDL representation of ANF-PUMI at the Home PINX

Insert hosting number into response

- 49 -

D.4

SDL representation of ANF-PUMI at the Visitor PINX Figure D.4 shows the behaviour of an ANF-PUMI entity within the Visitor PINX. Input signals from the right and output signals to the right represent primitives to and from the Co-ordination Function in respect of messages sent and received.

VisitIdle

SETUP pumiInform.inv

Access VDB

User found?

No

Yes

Attempt establishment of basic call to PUM user

Stimulate release of basic call

VisitIdle

Figure D.4 - SDL representation of ANF-PUMI at the Visitor PINX

- 50 -

D.5

Behaviour of the Originating PINX for ANF-PUMO Figure D.5 shows the behaviour of the Originating PINX. Input signals from the left represent internal primitives. Output signals to the right represent messages to the peer SS-Control entity (i.e. in the Home PINX).

PUMO-Idle

basic call request

SETUP pumoCall.inv

information request

FACILITY pumoCall.inv

PUMO-Idle F ig u r e D . 5 - O r ig in a t in g P I N X b e h a v io u r

- 51 -

D.6

Behaviour of the Home PINX for ANF-PUMO Figures D.6 and D.7 show the behaviour of the Home PINX. Input signals from the left represent messages from the peer SS-Control entity (i.e. in the Originating PINX). Output signals to the right and input signals from the right represent internal primitives.

PUMO Idle

SETUP pum oCall.inv

inform ation indication

route on?

yes

no

num ber com plete?

extend call

yes

no start T3

PUMO-AwaitInfo

PUMO Idle

F ig u r e D . 6 - H o m e P I N X b e h a v io u r ( p a r t 1 )

- 52 -

PUMO-AwaitInfo

FACILITY pumoCall.inv

T3 expiry

information indication

number complete?

no

yes route on?

clear call

yes

no

PUMO Idle

extend call call extended?

number complete?

no

yes

yes

no re-start T3

PUMO-AwaitInfo

stop T3

PUMO Idle

PUMO Idle F ig u r e D . 7 - H o m e P I N X b e h a v io u r ( p a r t 2 )

extend call

- 53 -

Annex E ( n o r ma tiv e )

Additional feature identifier in module Common-Information-Operations

In ASN.1 module Common-Information-Operations {iso (1) standard (0) pss1-common-information (15772) operations (0)}, specified in 6.3.1 of ECMA-251, bit number 16 of type FeatureIdList shall be interpreted in the following way: anfPUMIreRoutingSupported

(16)

-- Rerouting for -- Incoming PUM calls -- supported

- 54 -

- 55 -

Annex F ( n o r ma tiv e )

ASN.1 definitions according to ITU-T Recs. X.208 / X.209

This annex lists all ASN.1 modules as they were defined in the second edition of ECMA-284, i.e. based on ITU-T Recommendations X.208 / X.209. Starting with the third edition the ASN.1 modules within ECMA-284 comply with ITU-T Recommendations X.680 / X.690. Please note that regardless of which version of these modules is used as a base of a QSIG implementation, the line encoding remains unchanged. Changes in future editions to modules based on X.680 / X.690 ASN.1 are not reflected in the modules in this annex. Table F.1 - Private-User-Mobility-Call-Handling-Operations – based on ITU-T Recs. X.208 / X.209 Private-User-Mobility-Call-Handling-Operations { iso (1) standard (0) pss1-pum-call-handling (17878) pum-call-handling-operations (0)} DEFINITIONS EXPLICIT TAGS ::= BEGIN IMPORTS

OPERATION, ERROR FROM Remote-Operation-Notation { joint-iso-ccitt (2) remote-operations (4) notation (0) } Extension FROM Manufacturer-specific-service-extension-definition { iso (1) standard (0) pss1-generic-procedures (11582) msi-definition (0) } PSS1InformationElement FROM Generic-parameters-definition { iso (1) standard (0) pss1-generic-procedures (11582) pss1-generic-parameters (6) } Name FROM Name-Operations { iso (1) standard (0) pss1-name (13868) name-operations (0) } basicServiceNotProvided, invalidServedUserNumber, notAvailable FROM General-Error-List { ccitt (0) recommendation (0) q (17) 950 general-error-list (1) } Address, PartyNumber, PartySubaddress, PresentedNumberScreened FROM Addressing-Data-Elements { iso (1) standard (0) pss1-generic-procedures (11582) addressing-data-elements (9) };

-- Operations for ANF-PUMI: -PumiEnquiry ::=

OPERATION -- Sent from the PUMI-detect PINX to the Home PINX. ARGUMENT EnquiryArg RESULT EnquiryRes ERRORS { invalidServedUserNumber, locationNotKnown, notAvailable, basicServiceNotProvided, unspecified }

PumiDivert ::=

OPERATION -- Sent from the PUMI-detect PINX to the Rerouteing PINX. ARGUMENT DivertArg RESULT DummyRes ERRORS { notAvailable, unspecified }

- 56 -

Table F.1 - Private-User-Mobility-Call-Handling-Operations – based on ITU-T Recs. X.208 / X . 2 0 9 ( c o n t in u e d ) PumiInform ::=

EnquiryArg ::=

OPERATION -- Sent from the Rerouteing PINX to the Visitor PINX. ARGUMENT InformArg SEQUENCE

{ pisnNumber PartyNumber, -- The PISN number of the PUM user qSIGInfoElement PSS1InformationElement,

-- The basic call information elements Bearer capability, High layer compatibility, -- Low layer compatibility can be embedded in the qSIGInfoElement -- in accordance with clause 6.5.2.1. argExtension PumiExtension OPTIONAL } DivertArg ::=

SEQUENCE

{ hostingAddr PartyNumber, -- The PISN number of the hosting user, -- always a Complete Number. callingNumber PresentedNumberScreened, pumIdentity PumIdentity, -- The PISN number (always a Complete Number) -- and/or an alternative identifier of the PUM user. qSIGInfoElement PSS1InformationElement, -- The basic call information elements Bearer capability, High layer compatibility, -- Low layer compatibility, and Progress indicator -- can be embedded in the qSIGInfoElement in accordance with clause 6.5.2.1. callingUserSub [ 1 ] PartySubaddress OPTIONAL, callingUserName [ 2 ] Name OPTIONAL, pumUserSub [ 3 ] PartySubaddress OPTIONAL, argExtension PumiExtension OPTIONAL }

InformArg ::=

SEQUENCE

{ pumIdentity PumIdentity, -- The PISN number (always a Complete Number) -- and/or an alternative identifier of the PUM user. argExtension PumiExtension OPTIONAL }

EnquiryRes ::=

CHOICE

{ currLocation cfuActivated

[ 1 ] IMPLICIT CurrLocation, [ 2 ] IMPLICIT CfuActivated }

CurrLocation ::= SEQUENCE

{ hostingAddr PartyNumber, -- The PISN number of the hosting user, -- always a Complete Number. PumIdentity PumIdentity, -- The PISN number (always a Complete Number) -- and/or an alternative identifier of the PUM user. argExtension PumiExtension OPTIONAL }

CfuActivated ::= SEQUENCE

{ divToAddress divOptions pumName argExtension

SubscriptionOption ::=ENUMERATED

{ noNotification (0), notificationWithoutDivertedToNr (1), notificationWithDivertedToNr (2) }

DummyRes ::=

CHOICE

{ null extension sequOfExtn

NULL, [ 1 ] IMPLICIT Extension, [ 2 ] IMPLICIT SEQUENCE OF Extension }

PumiExtension ::= CHOICE

{ extension sequOfExtn

[ 4 ] IMPLICIT Extension, [ 5 ] IMPLICIT SEQUENCE OF Extension }

Address, SubscriptionOption, [ 1 ] Name OPTIONAL, PumiExtension OPTIONAL }

- 57 -

Table F.1 - Private-User-Mobility-Call-Handling-Operations – based on ITU-T Recs. X.208 / X . 2 0 9 ( c o n c lu d e d ) PumIdentity ::=

CHOICE

{ pisnNumber alternativeId both

AlternativeId ::=

OCTET STRING(SIZE(1..20))

PartyNumber, [ 10 ] IMPLICIT AlternativeId, [ 11 ] IMPLICIT SEQUENCE { pisnNumber PartyNumber, alternativeId AlternativeId } }

-- Operation for ANF-PUMO -PumoCall ::= PumoArg ::=

OPERATION ARGUMENT SEQUENCE

PumoArg { destinationNumber [0] PartyNumber OPTIONAL, pumIdentity [1] PumIdentity OPTIONAL, -- The PISN number (always a Complete Number) -- and/or an alternative identifier of the PUM user. sendingComplete [2] IMPLICIT NULL OPTIONAL, extension CHOICE {single [3] IMPLICIT Extension, multiple [4] IMPLICIT SEQUENCE OF Extension } OPTIONAL }

pumiEnquiry pumiDivert pumiInform

PumiEnquiry PumiDivert PumiInform

::= ::= ::=

localValue 93 localValue 94 localValue 95

pumoCall

PumoCall

::=

localValue 96

locationNotKnown unspecified

ERROR Unspecified

::= ::=

localValue 1015 localValue 1008

::=

ERROR PARAMETER Extension

Unspecified END

-- of Private-User-Mobility-Call-Handling-Operations

.

.

Free printed copies can be ordered from: ECMA 114 Rue du Rhône CH-1204 Geneva Switzerland Fax: Email:

+41 22 849.60.01 [email protected]

Files of this Standard can be freely downloaded from the ECMA web site (www.ecma.ch). This site gives full information on ECMA, ECMA activities, ECMA Standards and Technical Reports.

ECMA 114 Rue du Rhône CH-1204 Geneva Switzerland See inside cover page for obtaining further soft or hard copies.

Related documents

• ECMA-94 — 8-bit single-byte coded graphic character sets - Latin alphabets No. 1 to No. 4 (June 1986)#600481
• ECMA-74 — Measurement of Airborne Noise emitted by Information Technology and Telecommunications Equipment (December 2025)#600482
• ECMA-48 — Control functions for coded character sets (June 1991)#600483
• ECMA-43 — 8-bit coded character set structure and rules (December 1991)#600484
• ECMA-35 — Character code structure and extension techniques (December 1994)#600485