ISO/IEC 15431:2003
(Main)Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Inter-exchange signalling protocol — Wireless terminal call handling additional network features
Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Inter-exchange signalling protocol — Wireless terminal call handling additional network features
ISO/IEC 15431:2003 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 International 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 ISO/IEC 11579-1. Service specifications are produced in three stages and according to the method specified in ITU-T Rec. I.130. This International Standard contains the stage 3 specification for the Q reference point and satisfies the requirements identified by the stage 1 and stage 2 specifications in ISO/IEC 15430. 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 ISO/IEC 11572, and uses certain aspects of the generic procedures for the control of supplementary services specified in ISO/IEC 11582. ISO/IEC 15431:2003 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. ISO/IEC 15431:2003 is applicable to PINXs which can interconnect to form a PISN.
Technologies de l'information — Télécommunications et échange d'information entre systèmes — Réseau privé à intégration de services - Protocole de signalement d'interéchange — Caractéristiques de réseau additionnelles pour le traîtement d'appel de terminal sans fil
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 15431
Second edition
2003-04-01
Information technology —
Telecommunications and information
exchange between systems — Private
Integrated Services Network —
Inter-exchange signalling protocol —
Wireless terminal call handling additional
network features
Technologies de l'information — Télécommunications et échange
d'information entre systèmes — Réseau privé à intégration de
services — Protocole de signalement d'interéchange — Caractéristiques
de réseau additionnelles pour le traitement d'appel de terminal sans fil
Reference number
©
ISO/IEC 2003
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO/IEC 2003
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2003 — All rights reserved
Contents
Foreword vi
Introduction vii
1 Scope 1
2 Conformance 1
3 Normative references 1
4 Terms and definitions 2
4.1 External definitions 2
4.2 Other definitions 3
4.2.1 Alternative identifier 3
4.2.2 Home data base (HDB) 3
4.2.3 Home PINX 3
4.2.4 Rerouteing PINX 3
4.2.5 Visitor data base (VDB) 3
4.2.6 Visitor PINX 3
4.2.7 WTMI-detect PINX 3
5 Symbols and abbreviated terms 4
Signalling protocol for the support of ANF-WTMI
6 4
6.1 ANF-WTMI description 4
6.2 ANF-WTMI operational requirements 5
6.2.1 Requirements on the Rerouteing PINX 5
6.2.2 Requirements on the WTMI-detect PINX 5
6.2.3 Requirements on the Home PINX 5
6.2.4 Requirements on the Visitor PINX 5
6.2.5 Requirements on a Transit PINX 5
ANF-WTMI coding requirements
6.3 6
6.3.1 Operations 6
6.3.2 Information elements 8
6.3.3 Messages 9
6.4 ANF-WTMI state definitions 9
6.4.1 States at the Rerouteing PINX 9
6.4.2 States at the WTMI-detect PINX 9
6.4.3 States at the Home PINX 9
6.4.4 States at the Visitor PINX 9
6.5 ANF-WTMI signalling procedures for invocation and operation 9
6.5.1 Actions at the Rerouteing PINX 9
6.5.2 Actions at the WTMI-detect PINX 10
6.5.3 Actions at the Home PINX 11
6.5.4 Actions at the Visitor PINX 12
6.5.5 Actions at a Transit PINX 12
6.5.6 Actions at an Originating PINX 12
6.6 ANF-WTMI impact of interworking with public ISDNs 12
ANF-WTMI impact of interworking with non-ISDNs
6.7 13
6.8 Protocol interactions between ANF-WTMI and other supplementary services and ANFs 13
© ISO/IEC 2003 – All rights reserved iii
6.8.1 Interaction with Calling Name Identification Presentation (SS-CNIP) 13
6.8.2 Interaction with Connected Name Identification Presentation (SS-CONP) 13
6.8.3 Interaction with Call Completion to Busy Subscriber (SS-CCBS) 13
6.8.4 Interaction with Call Completion on No Reply (SS-CCNR) 13
6.8.5 Interaction with Call Transfer (SS-CT) 13
6.8.6 Interaction with Call Forwarding Unconditional (SS-CFU) 13
6.8.7 Interaction with Call Forwarding Busy (SS-CFB) 13
6.8.8 Interaction with Call Forwarding No Reply (SS-CFNR) 13
6.8.9 Interaction with Call Deflection (SS-CD) 13
6.8.10 Interaction with Path Replacement (ANF-PR) 13
6.8.11 Interaction with Call Offer (SS-CO) 13
6.8.12 Interaction with Call Intrusion (SS-CI) 14
Interaction with Do Not Disturb (SS-DND)
6.8.13 14
6.8.14 Interaction with Do Not Disturb Override (SS-DNDO) 14
6.8.15 Interaction with Advice Of Charge (SS-AOC) 14
6.8.16 Interaction with Recall (SS-RE) 14
6.8.17 Interaction with Call Interception (ANF-CINT) 14
6.8.18 Interaction with Transit Counter (ANF-TC) 14
6.8.19 Interaction with Route Restriction Class (ANF-RRC) 14
6.8.20 Interaction with Message Waiting Indication (SS-MWI) 15
Interaction with Wireless Terminal Location Registration (SS-WTLR)
6.8.21 15
6.8.22 Interaction with Wireless Terminal Information (ANF-WTINFO) 15
6.8.23 Interaction with Wireless Terminal Outgoing Call (ANF-WTMO) 15
6.8.24 Interaction with Wireless Terminal Authentication of the Terminal (SS-WTAT) 15
6.8.25 Interaction with Wireless Terminal Authentication of the Network (SS-WTAN) 15
6.9 ANF-WTMI parameter values (timers) 16
6.9.1 Timer T1 16
6.9.2 Timer T2 16
7 Signalling protocol for the support of ANF-WTMO 16
7.1 ANF-WTMO description 16
7.2 ANF-WTMO operational requirements 16
7.2.1 Requirements on the Originating PINX 16
7.2.2 Requirements on the Home PINX 16
7.2.3 Requirements on a Transit PINX 16
7.3 ANF-WTMO coding requirements 16
7.3.1 Operations 16
7.3.2 Information elements 16
Messages
7.3.3 16
7.4 ANF-WTMO state definitions 17
7.4.1 States at the Originating PINX 17
7.4.2 States at the Home PINX 17
7.5 ANF-WTMO signalling procedures 17
7.5.1 Actions at the Originating PINX 17
7.5.2 Actions at the Home PINX 17
7.5.3 Actions at the Transit PINX 18
ANF-WTMO impact of interworking with public ISDNs
7.6 18
7.7 ANF-WTMO impact of interworking with non-ISDNs 18
7.8 Protocol interactions between ANF-WTMO and other supplementary services and ANFs 18
7.8.1 Interaction with Calling Name Identification Presentation (SS-CNIP) 18
7.8.2 Interaction with Connected Name Identification Presentation (SS-CONP) 18
iv © ISO/IEC 2003 – All rights reserved
7.8.3 Interaction with Call Completion to Busy Subscriber (SS-CCBS) 18
7.8.4 Interaction with Call Completion on No Reply (SS-CCNR) 18
7.8.5 Interaction with Call Transfer (SS-CT) 18
7.8.6 Interaction with Call Diversion (SS-CFU, SS-CFB, SS-CFNR, SS-CD) 18
7.8.7 Interaction with Path Replacement (ANF-PR) 19
7.8.8 Interaction with Call Offer (SS-CO) 19
7.8.9 Interaction with Call Intrusion (SS-CI) 19
7.8.10 Interaction with Do Not Disturb (SS-DND) 19
7.8.11 Interaction with Do Not Disturb Override (SS-DNDO) 19
7.8.12 Interaction with Advice of Charge (SS-AOC) 19
7.8.13 Interaction with Recall (SS-RE) 19
7.8.14 Interaction with Call Interception (ANF-CINT) 19
Interaction with Transit Counter (ANF-TC)
7.8.15 19
7.8.16 Interaction with Route Restriction Class (ANF-RRC) 19
7.8.17 Interaction with Message Waiting Indication (SS-MWI) 19
7.8.18 Interaction with Wireless Terminal Location Registration (SS-WTLR) 19
7.8.19 Interaction with Wireless Terminal Information (ANF-WTINFO) 19
7.8.20 Interaction with Wireless Terminal Incoming Call (ANF-WTMI) 19
7.8.21 Interaction with Wireless Terminal Authentication of the Terminal (SS-WTAT) 19
7.8.22 Interaction with Wireless Terminal Authentication of the Network (SS-WTAN) 20
Parameter values (timers)
7.9 20
7.9.1 Timers at the Originating PINX 20
7.9.2 Timers at the Home PINX 20
Annexes
A - Protocol Implementation Conformance Statement (PICS) proforma 21
B - Imported ASN.1 definitions 31
C - Examples of Message Sequences 32
D - Specification and Description Language (SDL) representation of procedures 37
E - ASN.1 definitions according to ITU-T Recs. X.208 / X.209 45
© ISO/IEC 2003 – All rights reserved v
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the
specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the
development of International Standards through technical committees established by the respective organization to deal with
particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the
field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by
the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires
approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC
shall not be held responsible for identifying any or all such patent rights.
ISO/IEC 15431 was prepared by ECMA (as ECMA-304) and was adopted, under a special “fast-track procedure”, by Joint
Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its approval by national bodies of ISO and IEC.
This second edition cancels and replaces the first edition (ISO/IEC 15431:1999), which has been technically revised.
vi © ISO/IEC 2003 – All rights reserved
Introduction
This International Standard is one of a series of 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 International 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 International Standard forms part of the PSS1 protocol
(informally known as QSIG).
This International 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 JTC 1, ITU-T, ETSI and other international and national standardization
bodies. It represents a pragmatic and widely based consensus.
© ISO/IEC 2003 – All rights reserved vii
INTERNATIONAL STANDARD ISO/IEC 15431:2003(E)
Information technology — Telecommunications and information
exchange between systems — Private Integrated Services Network —
Inter-exchange signalling protocol — Wireless terminal call handling
additional network features
1Scope
This International 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 International 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 ISO/IEC 11579-1.
Service specifications are produced in three stages and according to the method specified in ITU-T Rec. I.130. This
International Standard contains the stage 3 specification for the Q reference point and satisfies the requirements identified by
the stage 1 and stage 2 specifications in ISO/IEC 15430.
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 ISO/IEC 11572, and uses certain aspects of the generic procedures for the control of supplementary
services specified in ISO/IEC 11582.
This International Standard also specifies additional signalling protocol requirements for the support of interactions at the Q
reference point between ANF-WTMI / ANF-WTMO and other supplementary services and ANFs.
This International Standard is applicable to PINXs which can interconnect to form a PISN.
2 Conformance
In order to conform to this International Standard, a PINX shall satisfy the requirements identified in the Protocol
Implementation Conformance Statement (PICS) proforma in annex A.
3 Normative references
The following referenced documents are indispensable for the application of this document. For dated references, only the
edition cited applies. For undated references, the latest edition of the referenced document (including any amendments)
applies.
ISO/IEC 11571:1998, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Networks - Addressing
ISO/IEC 11572:2000, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Circuit mode bearer services - Inter-exchange signalling procedures and protocol
ISO/IEC 11574:2000, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Circuit-mode 64 kbit/s bearer services - Service description, functional capabilities and
information flows
ISO/IEC 11579-1:1994, Information technology - Telecommunications and information exchange between systems - Private
integrated services network - Part 1: Reference configuration for PISN Exchanges (PINX)
ISO/IEC 11582:2002, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Generic functional protocol for the support of supplementary services - Inter-exchange
signalling procedures and protocol
© ISO/IEC 2003 – All rights reserved 1
ISO/IEC 13241:1997, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Route Restriction Class additional network feature
ISO/IEC 13868:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Name identification supplementary services
ISO/IEC 13873:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Call Diversion supplementary services
ISO/IEC 13874:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Path Replacement additional network feature
ISO/IEC 14843:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Call Offer supplementary service
ISO/IEC 14844:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Do Not Disturb and Do Not Disturb Override supplementary
services
ISO/IEC 14846:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Call Intrusion supplementary service
ISO/IEC 15050:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Advice Of Charge supplementary services
ISO/IEC 15054:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Call Interception additional network feature
ISO/IEC 15056:1997, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Transit counter additional network feature
ISO/IEC 15430:1999, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Specification, functional model and information flows - Wireless terminal call handling
additional network features
ISO/IEC 15506:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Message Waiting Indication supplementary service
ITU-T Rec. I.112:1993, Vocabulary of terms for ISDNs
ITU-T Rec. I.130:1988, Method for the characterization of telecommunication services supported by an ISDN and network
capabilities of an ISDN (Blue Book)
ITU-T Rec. I.210:1993, Principles of telecommunication services supported by an ISDN and the means to describe them
ITU-T Rec. Q.850:1993, Use of cause and location in the digital subscriber Signalling System No. 1 and the Signalling
System No. 7 ISDN user part
ITU-T Rec. Q.950:2000, Supplementary services protocols, structure and general principles
ITU-T Rec. Z.100:1999, Specification and description language (SDL)
4 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
4.1 External definitions
This International Standard uses the following terms defined in other documents:
– Additional Network Feature (ANF) (ISO/IEC 11582)
– Application Protocol Data Unit (APDU) (ISO/IEC 11582)
– Basic service (ITU-T Rec. I.210)
– Call, Basic call (ISO/IEC 11582)
– Call independent (ISO/IEC 11582)
– Call independent signalling connection (ISO/IEC 11582)
2 © ISO/IEC 2003 – All rights reserved
– Call related (ISO/IEC 11582)
– Complete number (ISO/IEC 11571)
– Co-ordination function (ISO/IEC 11582)
– End PINX (ISO/IEC 11582)
– Incoming Gateway PINX (ISO/IEC 11572)
– Incoming WTM call (ISO/IEC 15430)
– Interpretation APDU (ISO/IEC 11582)
– Network Facility Extension (NFE) (ISO/IEC 11582)
– Originating PINX (ISO/IEC 11572)
– Private Integrated Services Network (PISN) (ISO/IEC 11579-1)
– Private Integrated services Network eXchange (PINX) (ISO/IEC 11579-1)
– PISN number (ISO/IEC 11571)
– Signalling (ITU-T Rec. I.112)
– Supplementary service (ITU-T Rec. I.210)
– Supplementary Service Control Entity (ISO/IEC 11582)
– Subsequent PINX (ISO/IEC 11572)
– Terminating PINX (ISO/IEC 11572)
– Transit PINX (ISO/IEC 11572)
– User (ISO/IEC 11574)
– WTMI user (ISO/IEC 15430)
– WTMO user (ISO/IEC 15430)
4.2 Other definitions
4.2.1 Alternative identifier
An identifier, other than the PISN number, which identifies the WTMI user uniquely.
4.2.2 Home data base (HDB)
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 Rerouteing PINX
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 Visitor PINX
The PINX which has direct access to the VDB entry for a particular WTMI or WTMO user.
4.2.7 WTMI-detect PINX
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.
© ISO/IEC 2003 – All rights reserved 3
5 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
6 Signalling protocol for the support of ANF-WTMI
6.1 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.
4 © ISO/IEC 2003 – All rights reserved
6.2 ANF-WTMI operational requirements
6.2.1 Requirements on the Rerouteing PINX
ISO/IEC 11572 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. ISO/IEC 11572 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 ISO/IEC 11582 for an End PINX,
shall apply.
6.2.2 Requirements on the WTMI-detect PINX
ISO/IEC 11572 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. ISO/IEC 11572 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 ISO/IEC 11582 for an End PINX,
shall apply.
Generic procedures for the call independent control (connection oriented) of supplementary services, as specified in
ISO/IEC 11582 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
ISO/IEC 11582 for a Terminating PINX, shall apply.
6.2.4 Requirements on the Visitor PINX
ISO/IEC 11572 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 ISO/IEC 11582 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 ISO/IEC 11572, shall apply.
Generic procedures for the call related control and call independent control (connection oriented) of supplementary services, as
specified in ISO/IEC 11582 for a Transit PINX, shall apply.
© ISO/IEC 2003 – All rights reserved 5
6.3 ANF-WTMI coding requirements
6.3.1 Operations
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}
6 © ISO/IEC 2003 – All rights reserved
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 { 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 }
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 [ 1 ] IMPLICIT CurrLocation,
cfuActivated [ 2 ] IMPLICIT 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 }
© ISO/IEC 2003 – All rights reserved 7
Table 1 - Operations in support of call handling additional network features (concluded)
CfuActivated ::= SEQUENCE { divToAddress Address,
divOptions SubscriptionOption,
wtmName [ 1 ] Name OPTIONAL,
argExtension WtmiExtension OPTIONAL }
SubscriptionOption ::= ENUMERATED { noNotification (0),
notificationWithoutDivertedToNr (1),
notificationWithDivertedToNr (2) }
DummyRes ::= CHOICE { null NULL,
extension [ 1 ] IMPLICIT Extension{{WTMCHExtSet}},
sequOfExtn [ 2 ] IMPLICIT SEQUENCE OF
Extension{{WTMCHExtSet}} }
WtmiExtension ::= CHOICE { extension [ 4 ] IMPLICIT Extension{{WTMCHExtSet}},
sequOfExtn [ 5 ] IMPLICIT SEQUENCE OF
Extension{{WTMCHExtSet}} }
WtmIdentity ::= CHOICE { pisnNumber PartyNumber,
alternativeId [ 10 ] IMPLICIT AlternativeId,
both [ 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 [0] PartyNumber OPTIONAL,
sendingComplete [1] IMPLICIT NULL OPTIONAL,
extension CHOICE
{single [2] IMPLICIT Extension{{WTMCHExtSet}},
multiple [3] IMPLICIT SEQUENCE OF
Extension{{WTMCHExtSet}}
} OPTIONAL
}
WTMCHExtSet EXTENSION ::= {.}
unspecified ERROR ::= {
PARAMETER Extension{{WTMCHExtSet}}
CODE local: 1008}
locationNotKnown ERROR ::= { CODE local: 1015}
END -- of Wireless-Terminal-Call-Handling-Operations-asn1-97
6.3.2 Information elements
6.3.2.1 Facility information element
The operations defined in 6.3.1 shall be coded in the Facility information element in accordance with ISO/IEC 11582.
8 © ISO/IEC 2003 – All rights reserved
When conveying the invoke APDU of operations defined in 6.3.1 the destinationEntity data element of the NFE shall contain
value endPINX.
When conveying the invoke APDU of operations defined in 6.3.1, the Interpretation APDU shall either be omitted or be
included with value rejectAnyUnrecognisedInvokePdu.
6.3.2.2 Other information elements
Any other information elements (e.g. Calling party number, Called party number) shall be coded in accordance with the rules of
ISO/IEC 11572 and ISO/IEC 11582.
6.3.3 Messages
The Facility information element shall be conveyed in the messages as specified in clause 10 of ISO/IEC 11582.
Messages used for call establishment shall be as specified in ISO/IEC 11572.
6.4 ANF-WTMI state definitions
6.4.1 States at the Rerouteing PINX
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.
6.4.1.1 State ExecIdle
Ready for receipt of a wtmiDivert APDU.
6.4.2 States at the WTMI-detect PINX
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 State WTMI-Idle
ANF-WTMI is not operating.
6.4.2.2 State WTMI-Detected
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 State WTMI-Divert
The current location of the WTMI user is known and a wtmiDivert invoke APDU has been sent to the Rerouteing PINX.
6.4.3 States at the Home PINX
The procedures for the Home PINX are written in terms of the following conceptual states existing within the ANF-WTMI
Supplementary Service Control entity.
6.4.3.1 State HomeIdle
Ready for receipt of a wtmiEnquiry APDU.
6.4.4 States at the Visitor PINX
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.
6.4.4.1 State VisitIdle
Ready for receipt of a wtmiInform APDU.
6.5 ANF-WTMI signalling procedures for invocation and operation
Examples of message sequences are shown in annex C.
6.5.1 Actions at the Rerouteing PINX
The SDL representation of procedures at the Rerouteing PINX is shown in D.1 of annex D.
6.5.1.1 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
© ISO/IEC 2003 – All rights reserved 9
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 Exceptional procedures
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.
6.5.2 Actions at the WTMI-detect PINX
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 WTMI-detect 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 ISO/IEC 11582. 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 International Standard. It can, for example, be the Called party number information element
received in the incoming SETUP message.
The following data elements shall be included in the argument of the 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 WTMI-Divert.
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;
10 © ISO/IEC 2003 – All rights reserved
− 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 Exceptional procedures
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.
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 Actions at the Home PINX
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
© ISO/IEC 2003 – All rights reserved 11
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 ISO/IEC 11582), 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 Exceptional procedures
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.
6.5.3.3 Additional procedures for Call Forwarding Unconditional
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.
6.5.4 Actions at the Visitor PINX
The SDL representation of procedures at the Visitor PINX is shown in D.4 of annex D.
6.5.4.1 Normal procedures
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...