Conceptio › Archive › ECMA International

ECMA Internationalopen access

ECMA-304 — Private Integrated Services Network (PISN) - Inter-exchange signalling protocol - Wireless Terminal Call Handling additional network features (QSIG-WTMCH) (December 2001)

ECMA International · ECMA International

ECMA International · Standards · License: Open Access

additional ecma ecmainternational exchange features integrated inter network

ecma, standard, ecma international, specification, ecma-304, ecma 304, 304, private, integrated, services, network, pisn, inter-exchange, signalling, protocol, wireless, terminal, call, handling, additional, features, qsig-wtmch

S tandard ECMA-304

2nd Edition - December 2001

Standardizing Information

and

Communication

Systems

Private Integrated Services Network (PISN) Inter-Exchange Signalling Protocol Wireless Terminal 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-304

2nd Edition - December 2001

Standardizing

Information

and

Communication

Systems

Private Integrated Services Network (PISN) Inter-Exchange Signalling Protocol Wireless Terminal Call Handling Additional Network Features (QSIG-WTMCH)

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

Ecma-304.doc

15-01-02 08,50

Brief History

This Standard is one of a series of ECMA Standards defining Wireless Terminal Mobility (WTM) 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 International Standards for Open Systems Interconnection as defined by ISO/IEC. This particular Standard specifies the signalling protocol for use at the Q reference point in support of the Wireless Terminal Call Handling additional network feature. The protocol defined in this Standard forms part of the PSS1 protocol (informally known as QSIG). 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-304 (published by ECMA in June 2000), this 2nd Edition incorporates migration to ASN.1 version 1997.

Adopted as 2nd Edition of Standard ECMA-304 by the General Assembly of December 2001.

- i -

Table of contents 1

Scope

Conformance

References (normative)

Terms and definitions 4 . 1 E x te r n a l d e f in itio n s 4 . 2 O th e r d e f in itio n s 4.2.1 Alternative identifier 4.2.2 H o me d a t a b a s e ( H D B ) 4.2.3 H o me P I N X 4.2.4 Re r o u te in g P I N X 4.2.5 Visitor data base (VDB) 4.2.6 Visitor PINX 4.2.7 WTMI-detect PINX

2 2 3 3 3 3 3 3 3 4

5 6

Symbols and abbreviated terms Signalling protocol for the support of ANF-WTMI 6 . 1 A N F - W T MI d e s c r i p t i o n 6 . 2 A N F - W T 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 W T 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 - W T 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 - W T MI s t a t e d e f i n i t i o n s 6.4.1 States at the Rerouteing PINX 6.4.2 States at the WTMI-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 - W T 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 WTMI-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

4 4 4 5 5 5 5 5 5 6 6 9 9 9 9 9 9 9 10 10 10 12 13 13 13

- ii -

6.6 6.7 6.8

A N F - W T 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 13 A N F - W T 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 13 P r o to c o l in te r a c tio n s b e tw e e n A N F - W T MI 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 13 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 ) 13 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 ) 14 6.8.5 Interaction with Call Transfer (SS-CT) 14 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 ) 14 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 ) 14 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) 14 6.8.9 Interaction with Call Deflection (SS-CD) 14 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 ) 14 6.8.11 Interaction with Call Offer (SS-CO) 14 6.8.12 Interaction with Call Intrusion (SS-CI) 14 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) 15 6.8.16 Interaction with Recall (SS-RE) 15 6.8.17 Interaction with Call Interception (ANF-CINT) 15 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) 15 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 ) 15 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 ) 15 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 ) 16 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 na l I n f o r ma t i o n ( A N F - W T I N F O ) 16 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 ) 16 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 ) 16 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 ) 16 6 . 9 A N F - W T MI p a r a me t e r v a l u e s ( t i me r s ) 16 6.9.1 T i me r T 1 16 6.9.2 T i me r T 2 17 7

Signalling protocol for the support of ANF-WTMO 7 . 1 A N F - W T MO d e s c r ip tio n 7 . 2 A N F - W T 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 - W T 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 - W T MO s ta te d e f in itio n s 7.4.1 States at the Originating PINX 7.4.2 S t a t e s a t t h e H o me P I N X

17 17 17 17 17 17 17 17 17 18 18 18 18

- iii -

7 . 5 A N F - W T MO s ig n a llin g p r o c e d u r e s 18 7.5.1 Actions at the Originating PINX 18 7.5.2 A c t i o n s a t t h e H o me P I N X 18 7.5.3 Actions at the Transit PINX 19 7 . 6 A N F - W T 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 19 7 . 7 A N F - W T 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 19 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 - W T 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 19 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 ) 20 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 ) 20 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 ) 20 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 ) 20 7.8.5 Interaction with Call Transfer (SS-CT) 20 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 ) 20 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 ) 20 7.8.8 Interaction with Call Offer (SS-CO) 20 7.8.9 Interaction with Call Intrusion (SS-CI) 20 7.8.10 Interaction with Do Not Disturb (SS-DND) 20 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 ) 20 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) 20 7.8.13 Interaction with Recall (SS-RE) 20 7.8.14 Interaction with Call Interception (ANF-CINT) 20 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) 20 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 ) 21 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 ) 21 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 ) 21 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 na l I n f o r ma t i o n ( A N F - W T I N F O ) 21 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 I n c o min g C a l l ( A N F - W T MI ) 21 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 ) 21 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 ) 21 7 . 9 P a r a me t e r v a l u e s ( t i me r s ) 21 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 21 7.9.2 T i me r s a t t h e H o me P I N X 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

Annex B - Imported ASN.1 definitions

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

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

A n n e x E - 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

- iv -

Scope This Standard specifies the signalling protocol for the support of the Wireless terminal call handling additional network features (ANF-WTMI and ANF-WTMO) at the Q reference point between Private Integrated services Network eXchanges (PINX) connected together within a Private Integrated Services Network (PISN). ANF-WTMI is a feature that directs incoming calls to a WTMI user within the PISN regardless of the WTMI user’s geographical location within the PISN, provided that the WTMI user’s location is known. Roaming outside the PISN is outside the scope of this edition of this Standard. ANF-WTMO permits the PISN to process call requests from a WTMO 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-303. The signalling protocol for ANF-WTMI and ANF-WTMO 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-WTMI / ANF-WTMO and other supplementary services and ANFs. This Standard is applicable to PINXs which can interconnect to form a PISN.

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.

References (normative) The following standards contain provisions which, through reference in this text, constitute provisions 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 Services Networks - Addressing (International Standard 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)

- 2 -

ECMA-174

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

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-303

Private Integrated Services Network (PISN) - Specification, Functional Model and Information Flows - Wireless Terminal Call Handling Additional Network Features (International Standard ISO/IEC 15430)

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)

ITU-T Rec. I.112

Vocabulary of terms for ISDNs (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 (1993)

ITU-T Rec. Q.950

Supplementary services protocols, structure and general principles (2000)

ITU-T Rec. Z.100

Specification and description language (1999)

Terms and definitions For the purposes 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)

– Application Protocol Data Unit (APDU)

(ECMA-165)

– Basic service

(ITU-T Rec. I.210)

– Call, Basic call

(ECMA-165)

– Call independent

(ECMA-165)

- 3 -

4.2

– Call independent signalling connection

(ECMA-165)

– Call related

(ECMA-165)

– Complete number

(ECMA-155)

– Co-ordination function

(ECMA-165)

– End PINX

(ECMA-165)

– Incoming Gateway PINX

(ECMA-143)

– Incoming WTM call

(ECMA-303)

– Interpretation APDU

(ECMA-165)

– 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)

– WTMI user

(ECMA-303)

– WTMO user

(ECMA-303)

Other definitions

4.2.1

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

4.2.2

H o m e d a t a b a s e ( H D B) The data base in which the current location and all associated parameters of a wireless terminal are stored.

4.2.3

Home PINX The PINX which has direct access to the HDB entry for a particular WTMI or WTMO user.

4.2.4

R e r o u t e in g P I N X The PINX which executes the rerouteing of the incoming WTM call to the current Visitor PINX. NOTE 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 WTMI-detect PINX.

4.2.5

Visitor data base (VDB) The data base in which all relevant parameters concerning a wireless terminal are stored for as long as it is located in an area controlled by this data base.

4.2.6

V is it o r P I N X The PINX which has direct access to the VDB entry for a particular WTMI or WTMO user.

- 4 -

4.2.7

W TM I - d e t e c t P I N X The PINX which detects that an incoming call is to a WTMI user. NOTE The WTMI-detect PINX is either the Home PINX, a Transit PINX, the Incoming Gateway PINX or the Originating PINX.

6 6.1

Symbols and abbreviated terms ANF

Additional Network Feature

ANF-CINT

Call Interception additional network feature

ANF-PR

Path Replacement additional network feature

ANF-RRC

Route Restriction Class additional network feature

ANF-TC

Transit counter additional network feature

(ANF-)WTMI

Wireless Terminal Incoming Call (additional network feature)

(ANF-)WTMO

Wireless Terminal Outgoing Call (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

SDL

Specification and Description Language

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-DNDO

Do Not Disturb Override supplementary service

SS-MWI

Message Waiting Indication supplementary service

VDB

Visitor Data Base

WTM

Wireless Terminal Mobility

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

- 5 -

6.2 6.2.1

ANF-WTMI 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 WTMI-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 WTMI-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.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.

- 6 -

6.3

ANF-WTMI 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 E. Table 1 - Operations in support of call handling additional network features

Wireless-Terminal-Call-Handling-Operations-asn1-97 { iso (1) standard (0) pss1-wtm-call-handling (15431) 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 (0) recommendation (0) 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) };

-- Operations for ANF-WTMI: -WTMCH-Operations OPERATION ::= {wtmiEnquiry | wtmiDivert | wtmiInform| wtmoCall} wtmiEnquiry

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

- 7 -

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

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

wtmiInform

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

EnquiryArg ::=

SEQUENCE

{ pisnNumber PartyNumber, -- The PISN number of the WTMI 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 WtmiExtension OPTIONAL }

DivertArg ::=

SEQUENCE

InformArg ::=

SEQUENCE

{ wtmIdentity WtmIdentity, -- The PISN number (always a Complete Number) -- and/or an alternative identifier of the WTMI user. argExtension WtmiExtension OPTIONAL }

EnquiryRes ::=

CHOICE

{ currLocation cfuActivated

CurrLocation ::=

SEQUENCE

{ visitPINX PartyNumber, -- The PISN number of the Visitor PINX, -- always a Complete Number. wtmIdentity WtmIdentity, -- The PISN number (always a Complete Number) -- and/or an alternative identifier of the WTMI user argExtension WtmiExtension OPTIONAL }

{ visitPINX PartyNumber, -- The PISN number of the Visitor PINX, -- always a Complete Number. callingNumber PresentedNumberScreened, wtmIdentity WtmIdentity, -- The PISN number (always a Complete Number) -- and/or an alternative identifier of the WTMI 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, callingName [ 2 ] Name OPTIONAL, wtmUserSub [ 3 ] PartySubaddress OPTIONAL, argExtension WtmiExtension OPTIONAL }

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

- 8 -

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

SEQUENCE

{ divToAddress divOptions wtmName argExtension

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

SubscriptionOption ::=

ENUMERATED

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

DummyRes ::=

CHOICE

{ null extension sequOfExtn

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

WtmiExtension ::=

CHOICE

{ extension sequOfExtn

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

WtmIdentity ::=

CHOICE

{ pisnNumber alternativeId both

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

AlternativeId ::=

OCTET STRING(SIZE(1..20))

-- Operation for ANF-WTMO -wtmoCall

OPERATION ::= { ARGUMENT WtmoArg RETURN RESULT FALSE ALWAYS RESPONDS FALSE CODE local: 71}

WtmoArg ::= SEQUENCE { destinationNumber sendingComplete extension

[0] PartyNumber OPTIONAL, [1] IMPLICIT NULL OPTIONAL, CHOICE {single [2] IMPLICIT Extension{{WTMCHExtSet}}, multiple [3] IMPLICIT SEQUENCE OF Extension{{WTMCHExtSet}} } OPTIONAL

} WTMCHExtSet EXTENSION ::= {...} unspecified

ERROR ::= { PARAMETER CODE

Extension{{WTMCHExtSet}} local: 1008}

locationNotKnown

ERROR ::= { CODE

local: 1015}

END

-- of Wireless-Terminal-Call-Handling-Operations-asn1-97

- 9 -

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

6.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. Messages used for call establishment shall be as specified in ECMA-143.

6.4

ANF-WTMI state definitions

6.4.1

6.4.1.1 6.4.2

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-WTMI Supplementary Service Control entity in that PINX in association with a particular call. S t a t e Ex e c I d le Ready for receipt of a wtmiDivert APDU. S t a t e s a t t h e W TM I - d e t e c t P I N X The procedures for the WTMI-detect PINX are written in terms of the following conceptual states existing within the ANF-WTMI Supplementary Service Control entity in that PINX in association with a particular call.

6.4.2.1

S t a t e W TM I - I d le ANF-WTMI is not operating.

6.4.2.2

S t a t e W TM I - D e t e c t e d A call to a WTMI user has been detected and a wtmiEnquiry invoke APDU requesting the current location of the WTMI user has been sent to the Home PINX.

6.4.2.3

S t a t e W TM I - D iv e r t The current location of the WTMI user is known and a wtmiDivert invoke APDU has been sent to the Rerouteing PINX.

6.4.3

6.4.3.1 6.4.4

6.4.4.1

States at the Home PINX The procedures for the Home PINX are written in terms of the following conceptual states existing within the ANF-WTMI Supplementary Service Control entity. S t a t e H o m e I d le Ready for receipt of a wtmiEnquiry APDU. 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-WTMI Supplementary Service Control entity in that PINX in association with a particular call. S t a t e V is it I d le Ready for receipt of a wtmiInform APDU.

- 10 -

6.5

ANF-WTMI 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 wtmiDivert 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-WTMI. If so, it shall initiate a new call establishment to the Visitor PINX and release the leg towards the WTMI-detect PINX by sending a DISCONNECT message containing a wtmiDivert return result APDU. The SETUP message for the new call establishment shall include a wtmiInform invoke APDU. The following specific basic call information elements shall be included in the SETUP message: − Called party number, containing the number received in the visitPINX data element within the wtmiDivert invoke APDU; − Called party subaddress, containing the subaddress received in the wtmUserSub data element within the wtmiDivert invoke APDU (optional); − Calling party number, containing the number received in the callingNumber data element within the wtmiDivert invoke APDU; − Calling party subaddress, containing the subaddress received in the callingUserSub data element within the wtmiDivert invoke APDU (optional); − Bearer capability information element as received in embedded form within the wtmiDivert 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 wtmiInform invoke APDU shall contain the data element wtmIdentity with the same contents as the corresponding data element in the argument of the received wtmiDivert 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-WTMI, it shall answer the wtmiDivert invoke APDU with a return error APDU containing the error notAvailable. A c t io n s a t t h e W TM I - d e t e c t P I N X The SDL representation of procedures at the WTMI-detect PINX is shown in D.2 of annex D. When a WTMI-detect PINX also provides Rerouteing PINX functionality, in support of ANF-WTMI by forward switching, the joint requirements of 6.5.1 (for a Rerouteing PINX) and 6.5.2 (for a WTMIdetect PINX) shall apply, with the exception that any communication between the WTMI-detect PINX functionality and the Rerouteing PINX functionality will be an intra-PINX matter. The messages specified for sending from the WTMI-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-WTMI is to be invoked following the arrival of an incoming call, the WTMI-detect PINX shall send a wtmiEnquiry invoke APDU to the Home PINX of the called WTMI 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 WTMI-detect PINX shall enter state WTMI-Detected and start timer T1. NOTE 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.

- 11 -

The following data elements shall be included in the argument of the wtmiEnquiry 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 wtmiEnquiry return result APDU containing choice currLocation, the WTMI-detect PINX shall stop timer T1, send a wtmiDivert invoke APDU in a FACILITY message to the Rerouteing PINX using the call reference of the incoming call, start timer T2 and enter state WTMIDivert. The following data elements shall be included in the argument of the wtmiDivert invoke APDU: − element visitPINX as received in the wtmiEnquiry return result APDU; − element callingNumber as received in the incoming SETUP message in the Calling party number information element; − element wtmIdentity as received in the wtmiEnquiry 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 wtmUserSub, if a Called party subaddress information element was received in the incoming SETUP message. On receipt of a wtmiEnquiry return result APDU containing choice cfuActivated, if the WTMI-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 WTMI-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 wtmiDivert return result APDU, the WTMI-detect PINX shall stop timer T2 and enter state WTMI-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 wtmiEnquiry return error APDU from the Home PINX indicating ‘invalidServedUserNr’, the WTMI-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 WTMI-Idle. On receipt of a wtmiEnquiry return error APDU from the Home PINX indicating ‘locationNotKnown’, the WTMI-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 WTMI-Idle. On receipt of a wtmiEnquiry return error APDU from the Home PINX indicating ‘notAvailable’, the WTMI-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 WTMI-Idle. On receipt of a wtmiEnquiry return error APDU from the Home PINX indicating ‘basicServiceNotProvided’, the WTMI-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 WTMI-Idle.

- 12 -

On receipt of a wtmiEnquiry reject APDU from the Home PINX, the WTMI-detect PINX shall stop timer T1, enter state WTMI-Idle, and continue with normal basic call procedures. If timer T1 expires (i.e. the wtmiEnquiry invoke APDU is not answered by the Home PINX), the WTMI-detect PINX shall enter state WTMI-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 WTMI-Detected, the WTMI-detect PINX shall stop timer T1 and enter state WTMI-Idle. On receipt of a wtmiDivert return error or reject APDU from the Rerouteing PINX, the WTMI-detect PINX shall stop timer T2, enter state WTMI-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 wtmiDivert invoke APDU is not answered by the Rerouteing PINX), the WTMI-detect PINX shall enter state WTMI-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 WTMI-Divert, the WTMI-detect PINX shall stop timer T2 and enter state WTMI-Idle. The WTMI-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 WTMI-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 WTMI-detect PINX functionality, in support of ANF-WTMI, the joint requirements of 6.5.2 (for a WTMI-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 WTMI-detect PINX functionality will be an intra-PINX matter. The messages specified for sending from the Home PINX towards the WTMI-detect PINX or vice versa will not appear on any inter-PINX link.

6.5.3.1

Normal procedures On receipt of a wtmiEnquiry 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 WTMI 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 WTMI user is defined in the HDB, and the current location of the WTMI user is known for the basic service concerned, then the Home PINX shall answer the wtmiEnquiry invoke APDU with a return result APDU containing choice currLocation. Element visitPINX shall contain the PISN number of the Visitor PINX and element wtmIdentity shall contain the PISN number and/or an alternative identifier of the WTMI 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 WTMI user is not found in the HDB, the Home PINX shall answer the wtmiEnquiry invoke APDU with a return error APDU containing the error invalidServedUserNr. If the WTMI user has deregistered, the Home PINX shall answer the wtmiEnquiry invoke APDU with a return error APDU containing the error notAvailable. If the current location of the WTMI user is unknown, the Home PINX shall answer the wtmiEnquiry 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 wtmiEnquiry invoke APDU with a return error APDU containing the error basicServiceNotProvided.

- 13 -

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 wtmiEnquiry invoke APDU, if the WTMI user is defined in the HDB and SS-CFU is active, the Home PINX shall answer the wtmiEnquiry 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.

6.5.4.1

Normal procedures On receipt of a wtmiInform invoke APDU in a SETUP message, the Visitor PINX shall check that there is an entry in the VDB for the WTMI user, as indicated by the PISN number or alternative identifier in element wtmIdentity, for the basic service indicated by basic call information elements, and that the WTMI user is accessible. If so, the Visitor PINX shall attempt to establish the call to the PISN access indicated by the VDB entry. NOTE On receipt of an incoming call authentication of the WTMI user can be performed.

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 WTMI user is not found in the VDB, the Visitor PINX shall initiate call clearing according to the procedures in ECMA-143 with cause value #41 ‘Temporary failure’. If the WTMI user is not accessible, the Visitor PINX shall initiate call clearing according to the procedures in ECMA-143 with cause value #18 ‘No user responding’.

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-WTMI.

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 WTMI-detect PINX.

6.6

ANF-WTMI 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-WTMI within the PISN, except where Rerouteing PINX functionality is provided at a separate WTMI-detect PINX.

6.7

ANF-WTMI 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-WTMI within the PISN, except where Rerouteing PINX functionality is provided at a separate WTMI-detect PINX.

6.8

Protocol interactions between ANF-WTMI 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 1 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 2 Simultaneous conveyance of APDUs for ANF-WTMI 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

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

- 14 -

6.8.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 When executing ANF-WTMI, 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 WTMI-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.

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 W TM I - d e t e c t P I N X On receipt of a wtmiEnquiry return result APDU containing choice cfuActivated, the WTMI-detect PINX shall stop timer T1 and act as the Served User PINX for SS-CFU in accordance with 6.5.3 of ECMA-174. The WTMI-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-WTMI, 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 WTMI-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 WTMI-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-WTMI, 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 WTMI-detect PINX;

- 15 -

− 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 WTMIdetect 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.

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-WTMI, 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 WTMI-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 WTMI-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 e in g P I N X When executing ANF-WTMI, 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 WTMI-detect PINX.

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-WTMI, 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-WTMI, 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 WTMI-detect PINX. The element rac shall be the Route Access Class of either the calling user or the WTMI user.

6.8.19.2

A c t io n s a t t h e W TM I - d e t e c t P I N X The WTMI-detect PINX may include a routeRestrictionClass invoke APDU, with element rac containing the Route Access Class of the WTMI user, together with the wtmiDivert 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 WTMI user, together with the wtmiEnquiry return result APDU in the message to the WTMI-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 if SS-MWI is supported in accordance with ECMA-242.

- 16 -

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 wtmiDivert 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 W TM 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 WTMI-detect PINX shall 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.

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 FACILITY message using the call reference of a call independent signalling connection and containing a mwiActivate or mwiDeactivate invoke APDU, the Home PINX shall 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 Other actions, e.g. recording the status of SS-MWI for the WTMI 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 WTMI user which is also a served user of SS-MWI. NOTE A message waiting indication may be lost if the WTMI 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 f o r m a t i o n ( A N F - W T I N F O ) No protocol interaction.

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 ) The following interaction shall apply if ANF-WTMO is supported in accordance with clause 7.

6.8.23.1

A c t io n s a t t h e W TM I - d e t e c t P I N X If a SETUP message contains a wtmoCall invoke APDU then ANF-WTMI shall not be invoked on this call.

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.9 6.9.1

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

- 17 -

6.9.2

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

Signalling protocol for the support of ANF-WTMO

7.1

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

7.2

ANF-WTMO 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-WTMO coding requirements

7.3.1

O p e r a t io n s The operation wtmoCall 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 wtmoCall invoke APDU shall also contain an Interpretation APDU with value clearCallIfAnyInvokePduNotRecognised, if sent in a SETUP message. If sent in a FACILITY message, the Interpretation APDU shall either be omitted or included with value rejectAnyUnrecognisedInvokePdu. 7.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.

- 18 -

7.3.3

7.4

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

ANF-WTMO 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-WTMO Supplementary Service Control entity in that PINX in association with a particular WTMO Request.

7.4.1.1 7.4.2

W TM O - I d le ANF-WTMO 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-WTMO Supplementary Service Control entity in that PINX in association with a particular WTMO Request.

7.4.2.1

W TM O - I d le Ready for receipt of a wtmoCall invoke APDU.

7.4.2.2

W TM O - A wa it - I n f o Further address information can be received in overlap mode.

7.5

ANF-WTMO 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 WTMO user, the Originating PINX shall send a SETUP message according to ECMA-143 to the Home PINX. The SETUP message shall contain a wtmoCall invoke APDU, in the Calling party number information element the number of the WTMO user, and in the Called party number information element a number sufficient to route to the WTMO user's Home PINX. 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 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 WTMO user. Subsequently, if the destination number sent in the SETUP message was not complete, additional address information from the WTMO user shall be included in the argument of wtmoCall 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 wtmoCall 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

- 19 -

join the two call legs. If the destination number is not complete, the Home PINX shall enter state WTMO-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 WTMO-Idle. NOTE 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 WTMO-Await-Info, additional number information received as argument of wtmoCall 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 WTMO-Idle. Otherwise it shall restart timer T3 and stay in state WTMO-Await-Info. If a sendingComplete element is contained in a wtmoCall invoke APDU received while in state WTMO-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 WTMO-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 WTMO-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 wtmoCall invoke APDU received in a FACILITY message while in state WTMO-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-WTMO.

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

7.7

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

7.8

Protocol interactions between ANF-WTMO 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 1 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 2 Simultaneous conveyance of APDUs for ANF-WTMO 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 3 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.

- 20 -

NOTE 4 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 WTMO 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 - C 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.

- 21 -

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-WTMO, 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-WTMO, the Home PINX may include a routeRestrictionClass invoke APDU in the SETUP message, indicating the Route Access Class of the WTMO 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 f o r m a t i o n ( A N F - W T I N F O ) 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 I n c o m i n g C a l l ( A N F - W T M I ) This interaction is specified in 6.8.23.1.

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.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 wtmoCall invoke APDU with incomplete number information, restarted on receipt of a further wtmoCall invoke APDU with incomplete number information, and stopped when a wtmoCall invoke APDU containing final number information or an element sendingComplete is received. 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.

- 22 -

- 23 -

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);

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;

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).

- 24 -

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.

- 25 -

A.3

PICS proforma for ANF-WTMI

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 No [ ] Yes [ ] (see A.2.3) ? (The answer YES means that the implementation does not conform to this Standard)

Date of Statement

- 26 -

A.3.3 Item

General Question/feature

References

Status

N/A

Support

Support of ANF-WTMI, call rerouteing

o.1

Yes [ ] No [ ]

Support of ANF-WTMI, forward switching

o.1

Yes [ ] No [ ]

Behaviour as WTMI-detect PINX

o.2

Yes [ ] No [ ]

Behaviour as Home PINX for ANF-WTMI

o.2

Yes [ ] No [ ]

Behaviour as Visitor PINX for ANF-WTMI

o.2

Yes [ ] No [ ]

Behaviour as Originating PINX for ANF-WTMI

o.2

Yes [ ] No [ ]

Behaviour as Incoming Gateway PINX

o.2

Yes [ ] No [ ]

Behaviour as Rerouteing PINX

c.1

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

6.2

[]

m: Yes [ ] Yes [ ]

c1: 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

Signalling procedures at a Rerouteing PINX

6.5.1

A8:m

[]

m: Yes [ ]

Signalling procedures at a WTMI-detect PINX

6.5.2

A3:m

[]

m: Yes [ ]

Signalling procedures at a Home PINX

6.5.3.1 6.5.3.2

A4:m

[]

m: Yes [ ]

Signalling procedures at a Visitor PINX

6.5.4

A5:m

[]

m: Yes [ ]

Additional procedures at a Home PINX for Call Forwarding Unconditional

6.5.3.3

A4:o

[]

o: Yes [ ] No [ ]

- 27 -

A.3.5

Coding

Item

Question/feature

References

Status

N/A

Support

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

6.3

c.1

[]

m: Yes [ ]

Sending of wtmiInform invoke APDU

6.3

A8:m

[]

m: Yes [ ]

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

6.3

A3:m

[]

m: Yes [ ]

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

6.3

c.2

[]

m: Yes [ ]

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

6.3

A4:m

[]

m: Yes [ ]

Receipt of wtmiInform 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

Support of Timer T1

6.9.1

A3:m

[]

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

Support of Timer T2

6.9.2

c.1

[]

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

References

Status

N/A

Support

ECMA-164

6.8.1.1

c.1

[]

References

Status

N/A

ECMA-174

6.8.6.1

c.1

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

A.3.7 Item

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

Support of SS-CNIP

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-WTMI and SS-CFU Question/feature

Support of SS-CFU

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

Support Yes [ ] No [ ]

[]

m: Yes [ ]

- 28 -

A.3.9

Interactions between ANF-WTMI and SS-CO

Item

Question/feature

Support of SS-CO

Interactions at Rerouteing PINX

References

Status

N/A

ECMA-192

6.8.11.1

c.1

[]

References

Status

N/A

ECMA-203

6.8.12.1

c.1

[]

References

Status

N/A

ECMA-194

6.8.14.1

c.1

[]

References

Status

N/A

ECMA-212

6.8.15.1

c.1

[]

References

Status

N/A

ECMA-225

6.8.18.1

c.1

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

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

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

Question/feature

Support of SS-CI

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-WTMI and SS-DNDO Item

Question/feature

Support of SS-DNDO

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-WTMI and SS-AOC Item

Question/feature

Support of SS-AOC

Interactions at Rerouteing PINX

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

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

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

Question/feature

Support of ANF-TC

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

Support Yes [ ] No [ ]

[]

o: Yes [ ] No [ ]

- 29 -

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

Question/feature

References

Status

ISO/IEC 13241

N/A

Support

Support of ANF-RRC

Yes [ ] No [ ]

Interactions at Rerouteing PINX

6.8.19.1

c.1

[]

m: Yes [ ]

Interactions at WTMI-detect PINX

6.8.19.2

c.2

[]

o: Yes [ ] No [ ]

Interactions at Home PINX

6.8.19.3

c.3

[]

o: Yes [ ] No [ ]

References

Status

N/A

ECMA-242

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-WTMI and SS-MWI Item

Question / feature

Support

Support of SS-MWI

Yes [ ] No [ ]

Interactions at Rerouteing PINX

6.8.20.1

c.1

[]

m: Yes [ ]

Interactions at WTMI-detect PINX

6.8.20.2

c.2

[]

m: Yes [ ]

Interactions at Home PINX

6.8.20.3

c.3

[]

m: Yes [ ]

Interactions at Visitor PINX

6.8.20.4

c.4

[]

m: Yes [ ]

References

Status

N/A

6.8.23.1

c.1

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

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

Question / feature

Support of ANF-WTMO

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

Support Yes [ ] No [ ]

[]

m: Yes [ ]

- 30 -

A.4

PICS proforma for ANF-WTMO

A.4.1

Implementation identification

A.4.2

Protocol summary

Protocol Version

1.0

Date of Statement

- 31 -

A.4.3

General

Item

Question/feature

References

Status

N/A

Support

Behaviour as Originating PINX for ANF-WTMO

o.1

Yes [ ] No [ ]

Behaviour as Home PINX for ANF-WTMO

o.1

Yes [ ] No [ ]

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

7.2

Yes [ ]

A.4.4

Procedures References

Status

N/A

Item

Question / feature

Support

WTMO procedures at Originating PINX

7.5.1

A1:m

[]

m: Yes [ ]

WTMO procedures at Home PINX

7.5.2

A2:m

[]

m: Yes [ ]

A.4.5

Coding References

Status

N/A

Item

Question / feature

Sending of wtmoCall invoke APDU

7.3.1

A1:m

[]

m: Yes [ ]

Receipt of wtmoCall invoke APDU

7.3.1

A2:m

[]

m: Yes [ ]

A.4.6

Timers References

Status

N/A

7.9.2

A2:m

[]

Item D1

Question / feature Support of timer T3

Support

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

A.4.7 Item

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

Support of SS-CNIP

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

References

Status

ECMA-164

7.8.1.1

c.1

N/A

Support Yes [ ] No [ ]

[]

o: Yes [ ] No [ ]

- 32 -

A.4.8

Interactions between ANF-WTMO and Call Diversion

Item

Question / feature

References

Status

N/A

Support

Support of SS-CFU/CFB/CFNR/CD

ECMA-174

Home PINX acts as Rerouting PINX

7.8.6.1

c.1

[]

o: Yes [ ] No [ ]

References

Status

N/A

Support

ECMA-176

7.8.7.1

c.1

[]

o: Yes [ ] No [ ]

References

Status

N/A

Support

ECMA-221

7.8.14.1

c.1

[]

o: Yes [ ] No [ ]

References

Status

N/A

Support

ECMA-225

7.8.15.1

c.1

[]

o:Yes [ ] No [ ]

References

Status

N/A

Support

ISO/IEC 13241

7.8.16.1

c.1

Yes [ ] No []

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

A.4.9 Item

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

Support of ANF-PR

Home PINX acts as Cooperating PINX

Yes [ ] No [ ]

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

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

Question / feature

Support of ANF-CINT

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-WTMO and ANF-TC Item

Question/feature

Support of ANF-TC

Interactions at Home PINX

Yes [ ] No [ ]

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

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

Question/feature

Support of ANF-RRC

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

Yes [ ] No [ ] []

o:Yes [ ] No [ ]

- 33 -

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.

- 34 -

- 35 -

Annex C ( in f o r ma tiv e )

Examples of Message Sequences

This annex describes some typical message flows for ANF-WTMI and ANF-WTMO. The following conventions are used in the figures of this annex: 1. The following notation is used: Basic call message containing ANF-WTMI / ANF-WTMO information Basic call message without ANF-WTMI / ANF-WTMO information Call indepenent signalling connection message containing ANF-WTMI information Call indepenent signalling connection message without ANF-WTMI 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-WTMI / ANF-WTMO. Only messages relevant to ANF-WTMI / ANF-WTMO 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-WTMI / ANF-WTMO is not shown.

C.1

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

- 36 -

Rerouting PINX

WTMI detect PINX

Transit PINX SETUP

SETUP

CALL PROCEEDING

Transit PINX

SETUP wtmiEnquiry.inv

CALL PROCEEDING

SETUP wtmiEnquiry.inv

CALL PROCEEDING

CALL PROCEEDING CONNECT wtmiEnquiry.res

CONNECT wtmiEnquiry.res

FACILITY wtmiDivert.inv

RELEASE

DISCONNECT wtmiDivert.res

DISCONNECT wtmiDivert.res Transit PINX

SETUP wtmiInform.inv

Home PINX

RELEASE

RELEASE COMPLETE

Visitor PINX SETUP wtmiInform.inv

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 - W TM I Figure C.2 shows an example of ANF-WTMI when the Rerouteing fails and the WTMI-detect PINX performs forward switching to the Visitor PINX. Rerouting PINX

Transit PINX SETUP

CALL PROCEEDING

Transit PINX

WTMI detect PINX SETUP CALL PROCEEDING

SETUP wtmiEnquiry.inv

CALL PROCEEDING

FACILITY wtmiDivert.inv FACILITY wtmiDivert.err

FACILITY wtmiDivert.inv

CALL PROCEEDING CONNECT wtmiEnquiry.res

CONNECT wtmiEnquiry.res RELEASE

FACILITY wtmiDivert.err

Home PINX

RELEASE

RELEASE COMPLETE

Transit PINX SETUP wtmiInform.inv CALL PROCEEDING

Visitor PINX SETUP wtmiInform.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 W T M I - d e t e c t P I N X

- 37 -

C.2

Examples of unsuccessful operation of ANF-WTMI

C.2.1

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

Transit PINX SETUP

SETUP

CALL PROCEEDING

Transit PINX

WTMI detect PINX

CALL PROCEEDING

SETUP wtmiEnquiry.inv

CALL PROCEEDING

DISCONNECT cause = 1

CALL PROCEEDING CONNECT wtmiEnquiry.err

CONNECT wtmiEnquiry.err RELEASE

RELEASE

RELEASE COMPLETE

Home PINX

RELEASE

RELEASE COMPLETE

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

C.2.2

WTMI user’s location not known in Home PINX Figure C.4 shows an example of unsuccessful operation of ANF-WTMI due to WTMI user’s location not known. Rerouting PINX

Transit PINX SETUP

CALL PROCEEDING

WTMI detect PINX SETUP CALL PROCEEDING

Transit PINX

SETUP wtmiEnquiry.inv CALL PROCEEDING

DISCONNECT cause = 3 RELEASE RELEASE COMPLETE

DISCONNECT cause = 3

CONNECT wtmiEnquiry.err RELEASE

RELEASE RELEASE COMPLETE

RELEASE COMPLETE

Home PINX

SETUP wtmiEnquiry.inv CALL PROCEEDING CONNECT wtmiEnquiry.err

RELEASE RELEASE COMPLETE

F ig u r e C . 4 - Ex a m p le o f A N F - W TM I f a ilu r e d u e t o W T M I u s e r ’ s l o c a t i o n n o t k n o wn

- 38 -

C.2.3

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

Transit PINX SETUP

SETUP

CALL PROCEEDING

Transit PINX

WTMI detect PINX

SETUP wtmiEnquiry.inv

CALL PROCEEDING

FACILITY wtmiDivert.inv

RELEASE

DISCONNECT wtmiDivert.res

Transit PINX

SETUP wtmiInform.inv CALL PROCEEDING DISCONNECT cause = 41

CONNECT wtmiEnquiry.res

FACILITY wtmiDivert.inv

SETUP wtmiInform.inv

SETUP wtmiEnquiry.inv CALL PROCEEDING CONNECT wtmiEnquiry.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 locDelete.res

SETUP locDelete.inv RELEASE COMPLETE

CALL PROCEEDING DISCONNECT cause = 41

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

- 39 -

C.3

Successful invocation of ANF-WTMO

C.3.1

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

Originating PINX

Transit PINX SETUP

Home PINX

Subsequent PINX

SETUP

wtmoCall.inv CALL PROCEEDING

PROGRESS

FACILITY

wtmoCall.inv

FACILITY

wtmoCall.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 - W TM 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-WTMO where the whole destination number is sent in the first message. Originating PINX

Transit PINX SETUP

wtmoCall.inv CALL PROCEEDING

Home PINX

Subsequent PINX

SETUP wtmoCall.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 - W TM O wit h e n - b lo c o p e r a t io n

- 40 -

- 41 -

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-WTMI / ANF-WTMO 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

- 42 -

D.1

SDL representation of ANF-WTMI at the Rerouteing PINX Figure D.1 shows the behaviour of an ANF-WTMI 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 wtmiDivert.inv

WTMI possible?

Yes

Stimulate release of basic call to WTMI-detect PINX

DISCONNECT wtmiDivert.res

FACILITY wtmiDivert.err

Stimulate establishment of basic call to Visitor PINX

SETUP wtmiInform.inv

ExecIdle

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

- 43 -

D.2

SDL representation of ANF-WTMI at the WTMI-detect PINX Figure D.2 shows the behaviour of an ANF-WTMI entity within the WTMI-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.

WTMI-Idle

WTMI-Divert

WTMI call detected

Call cleared

DISCONNECT wtmiDivert.res

Message with wtmiEnquiry.inv to Home PINX

FACILITY wtmiDivert.err

Stop T2

Start T1

Forward switching supported No

Stimulate release of basic call

WTMI-Detected

Message with wtmiEnquiry.res

T1 Expiry

Stop T1

CFU activated ?

T2 Expiry

Message with wtmiEnquiry.err or reject

Call cleared

Stop T1

Yes

Do forward switching to the Visitor PINX

Yes

Stimulate release of basic call

FACILITY wtmiDivert.inv to Rerouteing PINX

Invoke CFU if supported by the PINX

Start T2

WTMI-Divert

WTMI-Idle

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

- 44 -

D.3

SDL representation of ANF-WTMI at the Home PINX Figure D.3 shows the behaviour of an ANF-WTMI 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 wtmiEnquiry.inv

Retrieve information from HDB

User found?

Yes

Return error invalidServedUserNumber

Service provided ?

Yes

Return error basicServiceNotProvided

WTM user registered?

Yes

Return error notAvailable

Location known?

Yes

Return error locationNotKnown

SS-CFU activated ?

Yes

Insert diverted-to address and PUM user name into response

Message with wtmiEnquiry.err

Message with wtmiEnquiry.res

HomeIdle

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

Insert hosting number into response

- 45 -

D.4

SDL representation of ANF-WTMI at the Visitor PINX Figure D.4 shows the behaviour of an ANF-WTMI 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 wtmiInform.inv

Access VDB

User found?

Yes

Attempt establishment of basic call to WTM user

Stimulate release of basic call

V isitIdle

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

- 46 -

D.5

Behaviour of the Originating PINX for ANF-WTMO 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).

CTMO-Idle

basic call request

SETUP ctmoCall.inv

information request

FACILITY ctmoCall.inv

CTMO-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

- 47 -

D.6

Behaviour of the Home PINX for ANF-WTMO 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.

CTMO Idle

SETUP ctmoCall.inv

information indication

route on?

yes

extend call

number complete?

yes

no start T3

CTMO-AwaitInfo

CTMO 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 )

- 48 -

CTMO-AwaitInfo

FACILITY ctmoCall.inv

T3 expiry

information indication

number complete?

yes route on?

clear call

yes

CTMO Idle

extend call call extended?

number complete?

yes

no re-start T3

CTMO-AwaitInfo

stop T3

CTMO Idle

CTMO 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

- 49 -

Annex E ( 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 first edition of ECMA-304, i.e. based on ITU-T Recommendations X.208 / X.209. Starting with the second edition the ASN.1 modules within ECMA-304 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 E.1 - Wireless-Terminal-Call-Handling-Operations – based on ITU-T Recs. X.208 / X.209 Wireless-Terminal-Call-Handling-Operations { iso (1) standard (0) pss1-wtm-call-handling (15431) 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-WTMI: -WtmiEnquiry ::=

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

WtmiDivert ::=

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

- 50 -

Table E.1 - Wireless-Terminal-Call-Handling-Operations – based on ITU-T Recs. X.208 / X.209 (continued) WtmiInform ::=

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

EnquiryArg ::=

SEQUENCE

DivertArg ::=

SEQUENCE

InformArg ::=

SEQUENCE

{ wtmIdentity WtmIdentity, -- The PISN number (always a Complete Number) -- and/or an alternative identifier of the WTMI user. argExtension WtmiExtension OPTIONAL }

EnquiryRes ::=

CHOICE

{ currLocation cfuActivated

CurrLocation ::=

SEQUENCE

CfuActivated ::=

SEQUENCE

{ divToAddress divOptions wtmName argExtension

SubscriptionOption ::=

ENUMERATED

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

DummyRes ::=

CHOICE

{ null extension sequOfExtn

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

WtmiExtension ::=

CHOICE

{ extension sequOfExtn

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

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

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

- 51 -

Table E.1 - Wireless-Terminal-Call-Handling-Operations – based on ITU-T Recs. X.208 / X.209 (concluded) WtmIdentity ::=

CHOICE

{ pisnNumber alternativeId both

AlternativeId ::=

OCTET STRING(SIZE(1..20))

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

-- Operation for ANF-WTMO -WtmoCall ::=

OPERATION ARGUMENT

WtmoArg ::= SEQUENCE { destinationNumber sendingComplete extension }

WtmoArg [0] PartyNumber OPTIONAL, [1] IMPLICIT NULL OPTIONAL, CHOICE {single [2] IMPLICIT Extension, multiple [3] IMPLICIT SEQUENCE OF Extension OPTIONAL }

wtmiEnquiry wtmiDivert wtmiInform

WtmiEnquiry WtmiDivert WtmiInform

::= ::= ::=

localValue 54 localValue 55 localValue 56

wtmoCall

WtmoCall

::=

localValue 71

locationNotKnown unspecified

ERROR Unspecified

::= ::=

localValue 1015 localValue 1008

ERROR

PARAMETER Extension

Unspecified

::=

END

-- of Wireless-Terminal-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.

ECMA-304 — Private Integrated Services Network (PISN) - Inter-exchange signalling protocol - Wireless Terminal Call Handling additional network features (QSIG-WTMCH) (December 2001)

Related documents