ISO/IEC 15429:2003

Information technology - Telecommunications and information exchange between systems - Private Integrated Services Network - Inter-exchange signalling protocol - Wireless Terminal Location Registration supplementary service and Wireless Terminal Information exchange additional network feature

ISO/IEC 15429:2003 specifies the signalling protocol for the support of the Wireless Terminal Location Registration supplementary service (SS-WTLR) and the Wireless Terminal Information exchange additional network feature (ANF-WTINFO) at the Q reference point between Private Integrated services Network eXchanges (PINXs) connected together within a Private Integrated Services Network (PISN). SS-WTLR is a supplementary service which enables a WTM user to register at, or deregister from, the current location within the PISN. The ability to register at different locations in the PISN at different times enables the WTM user to maintain the provided services (including the ability to make and receive calls) at different access points. Deregistration is used to inform the PISN that the WTM user is temporarily unable to make use of the provided services (including the receipt of calls). ANF-WTINFO is an additional network feature which enables transfer of restriction information between Home PINX and Visitor PINX. ANF-WTINFO also enables the Visitor PINX or Home PINX to initiate a check of the current location information. The Q reference point is defined in ISO/IEC 11579-1. Supplementary Service specifications and Additional Network Feature 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 15428. The signalling protocol for SS-WTLR and ANF-WTINFO uses certain aspects of the generic procedures for the control of supplementary services specified in ISO/IEC 11582. ISO/IEC 15429:2003 also specifies additional signalling protocol requirements for the support of interactions at the Q reference point between SS-WTLR and other supplementary services and ANFs. ISO/IEC 15429: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 — Service supplémentaire d'enregistrement de localisation de terminal sans fil et caractéristiques de réseau additionnelles pour l'échange d'information de terminal sans fil

General Information

• Status: Published
• Publication Date: 07-Apr-2003
• ICS: 33.040.35 - Telephone networks
• Technical Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Drafting Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Current Stage: 9093 - International Standard confirmed
• Start Date: 23-May-2025
• Completion Date: 30-Oct-2025

Relations

• Revises: ISO/IEC 15429:1999 - Information technology - Telecommunications and information exchange between systems - Private Integrated Services Network - Inter-exchange signalling protocol - Wireless Terminal Location Registration supplementary service and Wireless Terminal Information exchange additional network feature
• Effective Date: 15-Apr-2008

Overview

ISO/IEC 15429:2003 specifies the signalling protocol used at the Q reference point (QSIG/PSS1) to support two Wireless Terminal Mobility functions in a Private Integrated Services Network (PISN): the Wireless Terminal Location Registration supplementary service (SS‑WTLR) and the Wireless Terminal Information exchange additional network feature (ANF‑WTINFO). This stage‑3 international standard defines message formats, state machines, operational requirements and protocol interactions required for Private Integrated services Network eXchanges (PINXs) that interconnect to form a PISN.

Key topics and technical requirements

• Scope & conformance
  • Stage‑3 signalling protocol for SS‑WTLR and ANF‑WTINFO at the Q reference point.
  • Conformance demonstrated using the Protocol Implementation Conformance Statement (PICS) proforma (Annex A).
• Operational roles
  • Requirements and actions for Visitor PINX, Home PINX, Transit PINX and Directory PINX during registration, deregistration and information transfer.
• Procedures and state definitions
  • Detailed signalling procedures for location registration, location deregistration, transfer of restriction information, and location checks.
  • State machines for visitor/home/directory PINXs and timers (T1–T6) governing protocol behavior.
• Coding and transport
  • Message structures, information elements and ASN.1 definitions (Annex B & E).
  • Examples of message sequences and SDL representations (Annexes C & D).
• Protocol interactions
  • Defined interactions with many supplementary services and ANFs (e.g., call forwarding, message waiting indication, authentication, call transfer, call offer) to ensure correct multi‑service behaviour.
• Interworking
  • Considerations for interworking with public ISDNs and non‑ISDN networks.

Applications and who uses this standard

• Telecom equipment vendors building PINX/PISN systems and QSIG/PSS1‑compatible PBX interconnects.
• Network architects and operators deploying corporate private networks that support wireless terminal mobility (allowing a wireless terminal to register and receive services across different access points).
• Protocol implementers and firmware developers responsible for message encoding (ASN.1), state machines and timer handling.
• Test labs and certification bodies using the PICS proforma and example sequences for interoperability testing.
• Standards and compliance teams validating interactions between supplementary services in multi‑vendor PISNs.

Related standards

• ISO/IEC 11579‑1 (PINX reference configuration), ISO/IEC 11582 (generic supplementary service protocol), ISO/IEC 15428 (stage‑1/2 WTM service definitions), plus relevant ITU‑T recommendations (e.g., I.130, Q.950).

Keywords: ISO/IEC 15429:2003, SS‑WTLR, ANF‑WTINFO, Wireless Terminal Location Registration, PISN, PINX, Q reference point, QSIG, PSS1, ASN.1, PICS.

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 15429
Second edition
2003-04-01
Information technology —
Telecommunications and information
exchange between systems —
Private Integrated Services Network —
Inter-exchange signalling protocol —
Wireless Terminal Location Registration
supplementary service and Wireless
Terminal Information exchange additional
network feature
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 — Service
supplémentaire d'enregistrement de localisation de terminal sans fil et
caractéristiques de réseau additionnelles pour l'échange d'information
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 [e-mail]
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 WTM user 3
5 Symbols and abbreviated terms 3
6 Signalling protocol for the support of SS-WTLR 3
6.1 SS-WTLR description 3
6.2 SS-WTLR operational requirements 3
6.2.1 Requirements on the Visitor PINX 3
6.2.2 Requirements on the Home PINX 3
6.2.3 Requirements on a Transit PINX 3
6.2.4 Requirements on the Directory PINX 4
6.3 SS-WTLR coding requirements 4
6.3.1 Operations 4
6.3.2 Information elements 7
6.3.3 Messages 7
6.4 SS-WTLR state definitions 7
6.4.1 States at the Visitor PINX 7
6.4.2 States at the Home PINX 7
6.4.3 States at the Directory PINX 7
6.5 SS-WTLR Signalling procedures for location registration 7
6.5.1 Actions at the Visitor PINX for location registration 7
6.5.2 Additional actions at the Visitor PINX for enquiry to the previous Visitor PINX 8
6.5.3 Additional actions at the Visitor PINX for enquiry to a Directory PINX 9
6.5.4 Actions at the Home PINX for location registration 9
6.5.5 Actions at a Transit PINX for location registration 10
6.5.6 Actions at the previous Visitor PINX for location registration 10
6.5.7 Additional actions at the previous Visitor PINX for enquiry from the Visitor PINX 10
6.5.8 Actions at the Directory PINX for enquiry from the Visitor PINX 10
6.6 SS-WTLR signalling procedures for location deregistration 11
6.6.1 Actions at the Visitor PINX for location deregistration 11
6.6.2 Actions at the Home PINX for location deregistration 11
6.6.3 Actions at a Transit PINX for location deregistration 12
6.7 SS-WTLR Impact of interworking with public ISDNs 12
6.8 SS-WTLR Impact of interworking with non-ISDNs 12
6.9 Protocol interactions between SS-WTLR and other supplementary services and ANFs 12
© ISO/IEC 2003 – All rights reserved iii

6.9.1 Interaction with Calling Name Identification Presentation (SS-CNIP) 12
6.9.2 Interaction with Connected Name Identification Presentation (SS-CONP) 12
6.9.3 Interaction with Completion of Calls to Busy Subscriber (SS-CCBS) 12
6.9.4 Interaction with Completion of Calls on No Reply (SS-CCNR) 12
6.9.5 Interaction with Call Transfer (SS-CT) 12
6.9.6 Interaction with Call Forwarding Unconditional (SS-CFU) 12
6.9.7 Interaction with Call Forwarding Busy (SS-CFB) 12
6.9.8 Interaction with Call Forwarding No Reply (SS-CFNR) 12
6.9.9 Interaction with Call Deflection (SS-CD) 12
6.9.10 Interaction with Path Replacement (ANF-PR) 12
6.9.11 Interaction with Call Offer (SS-CO) 12
6.9.12 Interaction with Call Intrusion (SS-CI) 12
6.9.13 Interaction with Do Not Disturb (SS-DND) 12
6.9.14 Interaction with Do Not Disturb Override (SS-DNDO) 13
6.9.15 Interaction with Advice Of Charge (SS-AOC) 13
6.9.16 Interaction with Recall (SS-RE) 13
6.9.17 Interaction with Call Interception (ANF-CINT) 13
6.9.18 Interaction with Transit Counter (ANF-TC) 13
6.9.19 Interaction with Route Restriction Class (ANF-RRC) 13
6.9.20 Interaction with Message Waiting Indication (SS-MWI) 13
6.9.21 Interaction with Wireless Terminal information exchange (ANF-WTINFO) 13
6.9.22 Interaction with Wireless Terminal Incoming Call (SS-WTMI) 13
6.9.23 Interaction with Wireless Terminal Outgoing Call (SS-WTMO) 13
6.9.24 Interaction with Wireless Terminal Authentication of Terminal (SS-WTAT) 13
6.9.25 Interaction with Wireless Terminal Authentication of Network (SS-WTAN) 13
6.10 SS-WTLR parameter values (timers) 13
6.10.1 Timer T1 13
6.10.2 Timer T2 13
6.10.3 Timer T3 13
6.10.4 Timer T4 14
7 Signalling protocol for the support of ANF-WTINFO 14
7.1 ANF-WTINFO description 14
7.2 ANF-WTINFO operational requirements 14
7.2.1 Requirements on the Visitor PINX 14
7.2.2 Requirements on the Home PINX 14
7.2.3 Requirements on a Transit PINX 14
7.3 ANF-WTINFO coding requirements 14
7.3.1 Operations 14
7.3.2 Information elements 14
7.3.3 Messages 14
7.4 ANF-WTINFO state definitions 14
7.4.1 States at the Visitor PINX 14
7.4.2 States at the Home PINX 15
7.5 ANF-WTINFO signalling procedures for transfer of restriction information 15
7.5.1 Actions at the Visitor PINX for transfer of restriction information 15
7.5.2 Actions at the Home PINX for transfer of restriction information 15
7.6 ANF-WTINFO signalling procedures for check of location data 15
7.6.1 Actions at the Visitor PINX for check of location data 16
7.6.2 Actions at the Home PINX for check of location data 16
7.6.3 Actions at a Transit PINX for support of ANF-WTINFO 17
iv © ISO/IEC 2003 – All rights reserved

7.7 ANF-WTINFO Impact of interworking with public ISDNs 17
7.8 ANF-WTINFO Impact of interworking with non-ISDNs 17
7.9 Protocol interactions between ANF-WTINFO and other supplementary services and ANFs 17
7.9.1 Interaction with Calling Name Identification Presentation (SS-CNIP) 17
7.9.2 Interaction with Connected Name Identification Presentation (SS-CONP) 17
7.9.3 Interaction with Completion of Calls to Busy Subscriber (SS-CCBS) 17
7.9.4 Interaction with Completion of Calls on No Reply (SS-CCNR) 17
7.9.5 Interaction with Call Transfer (SS-CT) 17
7.9.6 Interaction with Call Forwarding Unconditional (SS-CFU) 17
7.9.7 Interaction with Call Forwarding Busy (SS-CFB) 17
7.9.8 Interaction with Call Forwarding No Reply (SS-CFNR) 17
7.9.9 Interaction with Call Deflection (SS-CD) 17
7.9.10 Interaction with Path Replacement (ANF-PR) 17
7.9.11 Interaction with Call Offer (SS-CO) 17
7.9.12 Interaction with Call Intrusion (SS-CI) 18
7.9.13 Interaction with Do Not Disturb (SS-DND) 18
7.9.14 Interaction with Do Not Disturb Override (SS-DNDO) 18
7.9.15 Interaction with Advice Of Charge (SS-AOC) 18
7.9.16 Interaction with Recall (SS-RE) 18
7.9.17 Interaction with Call Interception (ANF-CINT) 18
7.9.18 Interaction with Transit Counter (ANF-TC) 18
7.9.19 Interaction with Route Restriction Class (ANF-RRC) 18
7.9.20 Interaction with Message Waiting Indication (SS-MWI) 18
7.9.21 Interaction with Wireless Terminal Location Registration (SS-WTLR) 18
7.9.22 Interaction with Wireless Terminal Incoming Call (SS-WTMI) 18
7.9.23 Interaction with Wireless Terminal Outgoing Call (SS-WTMO) 18
7.9.24 Interaction with Wireless Terminal Authentication of Terminal (SS-WTAT) 18
7.9.25 Interaction with Wireless Terminal Authentication of Network (SS-WTAN) 18
7.10 ANF-WTINFO parameter values (timers) 18
7.10.1 Timer T5 18
7.10.2 Timer T6 19
Annexes
A - Protocol Implementation Conformance Statement (PICS) proforma 20
B - Imported ASN.1 definitions 28
C - Examples of message sequences 29
D - Specification and Description Language (SDL) representation of procedures 35
E - ASN.1 definitions according to ITU-T Recs. X.208 / X.209 43

© 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 15429 was prepared by ECMA (as ECMA-302) 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 15429: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 WTM Wireless
Terminal Location Registration supplementary service and the Wireless Terminal Information Exchange 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 15429:2003(E)

Information technology — Telecommunications and information
exchange between systems — Private Integrated Services Network —
Inter-exchange signalling protocol — Wireless Terminal Location
Registration supplementary service and Wireless Terminal
Information exchange additional network feature

1Scope
This International Standard specifies the signalling protocol for the support of the Wireless Terminal Location Registration
supplementary service (SS-WTLR) and the Wireless Terminal Information exchange additional network feature (ANF-
WTINFO) at the Q reference point between Private Integrated services Network eXchanges (PINXs) connected together within
a Private Integrated Services Network (PISN).
SS-WTLR is a supplementary service which enables a WTM user to register at, or deregister from, the current location within
the PISN. The ability to register at different locations in the PISN at different times enables the WTM user to maintain the
provided services (including the ability to make and receive calls) at different access points. Deregistration is used to inform the
PISN that the WTM user is temporarily unable to make use of the provided services (including the receipt of calls).
ANF-WTINFO is an additional network feature which enables transfer of restriction information between Home PINX and
Visitor PINX. ANF-WTINFO also enables the Visitor PINX or Home PINX to initiate a check of the current location
information.
The Q reference point is defined in ISO/IEC 11579-1.
Supplementary Service specifications and Additional Network Feature 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 15428.
The signalling protocol for SS-WTLR and ANF-WTINFO 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 SS-WTLR 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 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 13873:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Call Diversion supplementary services
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
ISO/IEC 15428:1999, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Specification, functional model and information flows - Wireless Terminal Location Registration
supplementary service and Wireless Terminal Information Exchange additional network feature
ISO/IEC 15433:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Wireless Terminal Aauthentication supplementary services
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.950:2000, Supplementary services protocols, structure and general principles
ITU-T Rec. Z.100:2002, 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:
– Application Protocol Data Unit (APDU) (ISO/IEC 11582)
– Basic Service (ITU-T Rec. I.210)
– Call, Basic Call (ISO/IEC 11582)
– Complete Number (ISO/IEC 11571)
– Co-ordination Function (ISO/IEC 11582)
– Directory PINX (ISO/IEC 15428)
– End PINX (ISO/IEC 11582)
– Home PINX (ISO/IEC 15428)
– Home data base (HDB) (ISO/IEC 15428)

– Interpretation APDU (ISO/IEC 11582)
– Location Area (LA) (ISO/IEC 15428)
– Network Facility Extension (NFE) (ISO/IEC 11582)
– Originating PINX (ISO/IEC 11582)
– PISN Number (ISO/IEC 11571)
– Private Integrated Services Network (PISN) (ISO/IEC 11579-1)
– Private Integrated services Network eXchange (PINX) (ISO/IEC 11579-1)
– Signalling (ITU-T Rec. I.112)
– Supplementary Service (ITU-T Rec. I.210)
– Supplementary Services Control Entity (ISO/IEC 11582)
– Terminating PINX (ISO/IEC 11582)
– Transit PINX (ISO/IEC 11582)
2 © ISO/IEC 2003 – All rights reserved

– User (ISO/IEC 11574)
– Visitor area (ISO/IEC 15428)
– Visitor data base (VDB) (ISO/IEC 15428)
– Visitor PINX (ISO/IEC 15428)
– Wireless Terminal Mobility (WTM) (ISO/IEC 15428)
– WTM user’s identity (ISO/IEC 15428)
4.2 Other definitions
4.2.1 WTM user
The user of SS-WTLR or other WTM services.
5 Symbols and abbreviated terms
ANF Additional Network Feature
ANF-WTINFO Wireless Terminal Information exchange
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-MWI Message Waiting Indication supplementary service
SS-WTLR Wireless Terminal Location Registration supplementary service
VDB Visitor Data Base
WTM Wireless Terminal Mobility
6 Signalling protocol for the support of SS-WTLR
6.1 SS-WTLR description
SS-WTLR is a supplementary service which makes the location of a WTM user known to the PISN. By updating location
information in the PISN, incoming calls can be routed to a WTM user, and the WTM user can access the PISN services from
the current location area. SS-WTLR also enables a WTM user to inform the PISN that the current location area is no longer to
be used to make and receive calls.
6.2 SS-WTLR operational requirements
6.2.1 Requirements on the Visitor PINX
Generic procedures for the call independent control (connection oriented) of supplementary services, as specified in
ISO/IEC 11582 for an Originating and Terminating PINX, shall apply.
6.2.2 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 and an Originating PINX, shall apply.
6.2.3 Requirements on a Transit PINX
Generic procedures for the 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 3

6.2.4 Requirements on the Directory 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.3 SS-WTLR 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 SS-WTLR and ANF-WTINFO
WTM-Location-Registration-Operations-asn1-97
{iso standard pss1-location-registration (15429) wtlr-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 standard
pss1-generic-procedures (11582) msi-class-asn1-97(11)}
notAvailable, invalidServedUserNr
FROM General-Errors-List
{ccitt recommendation q 950 general-error-list (1)}
PartyNumber FROM Addressing-Data-Elements-asn1-97
{iso(1) standard(0) pss1-generic-procedures(11582)
addressing-data-elements-asn1-97(20)}
BasicService FROM Call-Diversion-Operations-asn1-97
{ iso (1) standard (0) pss1-call-diversion (13873)
call-diversion-operations-asn1-97 (1) };
WTMLR-Operations OPERATION ::= {locUpdate | locDelete | locDeReg | pisnEnquiry | getRRCInf | locInfoCheck}
locUpdate OPERATION ::={
-- Sent from the Visitor PINX to the Home PINX.
ARGUMENT LocUpdArg
RESULT DummyRes
ERRORS { invalidServedUserNr | notAuthorized | unspecified }
CODE local: 50}
4 © ISO/IEC 2003 – All rights reserved

Table 1 - Operations in support of SS-WTLR and ANF-WTINFO (continued)
locDelete OPERATION ::= {
-- Sent from the Home PINX to the previous Visitor PINX.
ARGUMENT LocDelArg
RESULT DummyRes
ERRORS { temporarilyUnavailable | unspecified }
CODE local: 51}
locDeReg OPERATION ::= {
-- Sent from the Visitor PINX to the Home PINX.
ARGUMENT LocDeRegArg
RESULT DummyRes
ERRORS { notAvailable | unspecified }
CODE local: 52}
pisnEnquiry OPERATION ::= {
-- Sent from the Visitor PINX to the previous Visitor PINX or a Directory PINX.
ARGUMENT PisnEnqArg
RESULT PisnEnqRes
ERRORS { invalidServedUserNr | unspecified}
CODE local: 53}
getRRCInf OPERATION ::= {
-- Sent from the Visitor PINX to the Home PINX.
ARGUMENT GetRRCInfArg
RESULT GetRRCInfRes
ERRORS { notAvailable | unspecified }
CODE local: 97}
locInfoCheck OPERATION ::= {
-- Sent from the Visitor PINX to the Home PINX or vice versa.
ARGUMENT LocInfoCheckArg
RESULT LocInfoCheckRes
ERRORS { notAvailable | unspecified }
CODE local: 98}
LocUpdArg ::= SEQUENCE { wtmUserId WtmUserId,
basicServiceBasicService DEFAULT allServices,
visitPINX PartyNumber,
-- The pisnNumber of the Visitor PINX,
-- always a Complete Number.
argExtension LrExtension OPTIONAL }
DummyRes ::= CHOICE { null NULL,
extension [ 1 ] IMPLICIT Extension{{WTMLRExtSet}},
sequOfExtn [ 2 ] IMPLICIT SEQUENCE OF
Extension{{WTMLRExtSet}} }
LocDelArg ::= SEQUENCE { wtmUserId WtmUserId,
basicServiceBasicService DEFAULT allServices,
argExtension LrExtension OPTIONAL }
LocDeRegArg ::= SEQUENCE { wtmUserId WtmUserId,
basicServiceBasicService DEFAULT allServices,
argExtension LrExtension OPTIONAL }
© ISO/IEC 2003 – All rights reserved 5

Table 1 - Operations in support of SS-WTLR and ANF-WTINFO (concluded)
PisnEnqArg ::= SEQUENCE { alternativeId AlternativeId,
-- Can be a temporary identifier, e.g. Network Assigned
-- Identity structure, or a fixed handset identifier.
argExtension LrExtension OPTIONAL }
PisnEnqRes ::= SEQUENCE { wtmUserId WtmUserId,
resExtension LrExtension OPTIONAL }
GetRRCInfArg ::= SEQUENCE { wtmUserId WtmUserId,
basicServiceBasicService DEFAULT allServices,
argExtension LrExtension OPTIONAL }
GetRRCInfRes ::= SEQUENCE { alternativeId AlternativeId OPTIONAL,
rrClass RRClass OPTIONAL,
argExtension LrExtension OPTIONAL }
LocInfoCheckArg ::= SEQUENCE { wtmUserId WtmUserId,
basicServiceBasicService DEFAULT allServices,
visitPINX PartyNumber,
-- The PISN number of the Visitor PINX,
-- always a Complete Number.
argExtension LrExtension OPTIONAL }
LocInfoCheckRes ::= SEQUENCE { checkResult CheckResult,
argExtension LrExtension OPTIONAL }
WtmUserId ::= CHOICE { pisnNumber PartyNumber,
-- The PISN number of the WTM user,
-- always a Complete Number.
alternativeId AlternativeId }
AlternativeId ::= OCTET STRING(SIZE(1.20))
LrExtension ::= CHOICE { extension [ 1 ] IMPLICIT Extension{{WTMLRExtSet}},
sequOfExtn [ 2 ] IMPLICIT SEQUENCE OF
Extension{{WTMLRExtSet}} }
RRClass ::= INTEGER (0.99)
CheckResult ::= ENUMERATED { locInfChk-correct (0),
locInfChk-incorrect (1) }
WTMLRExtSet EXTENSION ::= {.}
notAuthorized ERROR ::= {CODE local: 1007}
temporarilyUnavailable ERROR ::= {CODE local: 1000}
unspecified ERROR ::={
PARAMETER Extension{{WTMLRExtSet}}
CODE local: 1008}
END -- of WTM-Location-Registration-Operations-asn1-97
NOTE
Element visitPINX in LocUpdArg can either be a roaming number for the individual WTLR user or a single number for all WTLR
users currently registered in this PINX. In the latter case the individual WTLR users are distinguished by their own WtmUserId.
6 © ISO/IEC 2003 – All rights reserved

6.3.2 Information elements
6.3.2.1 Facility information element
APDUs of the operations defined in 6.3.1 shall be coded in the Facility information element in accordance with
ISO/IEC 11582.
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 11582.
6.3.3 Messages
The Facility information element shall be conveyed in the messages as specified in clause 10 of ISO/IEC 11582.
6.4 SS-WTLR state definitions
6.4.1 States at the Visitor PINX
The procedures for the Visitor PINX are written in terms of the following conceptual states existing within the SS-WTLR
Supplementary Service Control entity in that PINX in association with a particular location handling request.
6.4.1.1 State VisitIdle
SS-WTLR is not operating.
6.4.1.2 State VisitUpdate
A locUpdate invoke APDU has been sent.
6.4.1.3 State VisitEnquiry
A pisnEnquiry invoke APDU has been sent.
6.4.1.4 State VisitDeReg
A locDeReg invoke APDU has been sent.
6.4.2 States at the Home PINX
The procedures for the Home PINX are written in terms of the following conceptual states existing within the SS-WTLR
Supplementary Service Control entity in that PINX in association with a particular location handling request.
6.4.2.1 State HomeIdle
Ready for receipt of a locUpdate or locDeReg APDU.
6.4.2.2 State HomeDelete
A locDelete invoke APDU has been sent.
6.4.3 States at the Directory PINX
The procedures for the Directory PINX are written in terms of the following conceptual states existing within the SS-WTLR
Supplementary Service Control entity in that PINX in association with a particular location handling request.
6.4.3.1 State DirectoryIdle
Ready for receipt of a pisnEnquiry APDU.
6.5 SS-WTLR Signalling procedures for location registration
Examples of message sequences are shown in annex C.
6.5.1 Actions at the Visitor PINX for location registration
The SDL representation of procedures at the Visitor PINX is shown in D.1 of annex D.
© ISO/IEC 2003 – All rights reserved 7

6.5.1.1 Normal procedures
On receipt of a valid location registration request from a WTM user that is not already registered in the Visitor area, and if the
Visitor PINX possesses sufficient addressing information to make a location registration request to the Home PINX, the Visitor
PINX shall send a locUpdate invoke APDU to the Home PINX 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. Within the argument of the invoke APDU, the
WTM user’s identity shall be included in element wtmUserId, the basic service for which the WTM user is to be registered may
be included in element basicService, and a PISN number identifying the Visitor PINX shall be included in element visitPINX.
This PISN number shall be suitable for use in the Called party number information element of a call or call independent
signalling connection that is to be routed to the Visitor PINX. The Visitor PINX shall enter state VisitUpdate and start timer
T1.
NOTE 1 - Validation of the registration request can involve authentication of the WTM user.
NOTE 2 - In the absence of sufficient addressing information, the Visitor PINX can, before sending a locUpdate invoke APDU, use the
procedures of 6.5.2 to make an enquiry to the previous Visitor PINX or the procedures of 6.5.3 to make an enquiry to a Directory PINX in
order to translate an identifier provided by the WTM user in the registration request into a PISN number.
NOTE 3 - The number to be used in the Called party number information element when establishing the call independent signalling
connection to the Home PINX is outside the scope of this International Standard. It can, for example, be a PISN number provided by the
WTM user in the location registration request or optionally the PISN number provided by the previous Visitor PINX or Directory PINX.
On receipt of the locUpdate return result APDU, the Visitor PINX shall stop timer T1, update the information in the VDB,
revert to state VisitIdle and indicate acceptance to the WTM user.
The Visitor 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.5.1.2 Exceptional procedures
On receipt of a locUpdate return error or reject APDU from the Home PINX, the Visitor PINX shall stop timer T1, revert to
state VisitIdle and indicate rejection to the WTM user.
If timer T1 expires (i.e. the locUpdate invoke APDU is not answered by the Home PINX), the Visitor PINX shall indicate
rejection to the WTM user and enter state VisitIdle.
The Visitor 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 or on expiry of timer T1. Alternatively, the signalling connection may be
retained for other applications, if appropriate.
6.5.2 Additional actions at the Visitor PINX for enquiry to the previous Visitor PINX
The SDL representation of procedures at the Visitor PINX is shown in D.1 of annex D.
6.5.2.1 Normal procedures
In order to make an enquiry to the previous Visitor PINX to translate an identifier provided by the WTM user in the location
registration request into a WTM user’s identity, the Visitor PINX may send a pisnEnquiry invoke APDU to the previous Visitor
PINX 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. Within the argument of the invoke APDU, element alternativeId shall contain the identifier provided by the
WTM user. The Visitor PINX shall enter state VisitEnquiry and start timer T2.
NOTE 4 - The number to be used in the Called party number information element when establishing the call independent signalling
connection to the previous Visitor PINX is outside the scope of this International Standard. It can, for example, be derived from the identifier
provided by the WTM user.
On receipt of the pisnEnquiry return result APDU, the Visitor PINX shall stop timer T2. The WTM user’s identity received in
the pisnEnquiry return result APDU can be used for location registration.
The Visitor PINX is responsible for clearing the call independent signalling connection towards the previous Visitor PINX.
This may occur on receipt of a return result APDU. Alternatively, the signalling connection may be retained for other
applications, if appropriate.
8 © ISO/IEC 2003 – All rights reserved

6.5.2.2 Exceptional procedures
On receipt of a pisnEnquiry return error or reject APDU from the previous Visitor PINX, the Visitor PINX shall stop timer T2
and enter state VisitIdle. If timer T2 expires, the Visitor PINX shall enter state VisitIdle.
NOTE 5 - In any of these situations the Visitor PINX will be unable to proceed with location registration and should indicate rejection to the
WTM user, unless there is another means available for obtaining the WTM user’s identity of the WTM user.
The Visitor PINX is responsible for clearing the call independent signalling connection towards the previous Visitor PINX.
This may occur on receipt of a return error or reject APDU or on expiry of timer T2. Alternatively, the signalling connection
may be retained for other applications, if appropriate.
6.5.3 Additional actions at the Visitor PINX for enquiry to a Directory PINX
The SDL representation of procedures at the Visitor PINX is shown in D.1 of annex D.
6.5.3.1 Normal procedures
In order to make an enquiry to a Directory PINX to translate an identifier provided by the WTM user in the location
registration request into a WTM user’s identity, the Visitor PINX may send a pisnEnquiry invoke APDU to the Directory PINX
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. Within the argument of the invoke APDU, element alternativeId shall contain the identifier provided by the
WTM user. The Visitor PINX shall enter state VisitEnquiry and start timer T2.
NOTE 6 - The number to be used in the Called party number information element when establishing the call independent signalling
connection to the Directory PINX is outside the scope of this International Standard.
On receipt of the pisnEnquiry return result APDU, the Visitor PINX shall stop timer T2. The WTM user’s identity received in
the pisnEnquiry return result APDU can be used for location registration.
The Visitor PINX is responsible for clearing the call independent signalling connection towards the Directory PINX. This may
occur on receipt of a return result APDU. Alternatively, the signalling connection may be retained for other applications, if
appropriate.
6.5.3.2 Exceptional procedures
On receipt of a pisnEnquiry return error or reject APDU from the Directory PINX, the Visitor PINX shall stop timer T2 and
enter state VisitIdle. If timer T2 expires, the Visitor PINX shall enter state VisitIdle.
NOTE 7 - In any of these situations the Visitor PINX will be unable to proceed with location registration and should indicate rejection to the
WTM user, unless there is another means available for obtaining the WTM user’s identity of the WTM user.
The Visitor PINX is responsible for clearing the call independent signalling connection towards the Directory PINX. This may
occur on receipt of a return error or reject APDU or on expiry of timer T2. Alternatively, the signalling connection may be
retained for other applications, if appropriate.
6.5.4 Actions at the Home PINX for location registration
The SDL representation of procedures at the Home PINX is shown in D.2 of annex D.
6.5.4.1 Normal procedures
On receipt of a locUpdate 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 the received WTM user’s identity (element wtmUserId), and may check the
requested basic service (element basicService) to verify that the WTM user may update the location information.
If the WTM user may update the location information, the Home PINX shall update the location information in the HDB using
the Visitor PINX number received in element visitPINX and answer the locUpdate invoke APDU with a return result APDU. If
the Visitor area has changed (i.e. the PISN number of the Visitor PINX optionally related to a basic service has changed), the
Home PINX shall send a locDelete invoke APDU to the previous Visitor PINX 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. Within the argument of the invoke
APDU, the WTM user’s identity shall be included in element wtmUserId and the basic service for which the WTM user has
registered may be included in element basicService. The Home PINX shall enter state HomeDelete and start timer T4.
On receipt of the locDelete return result APDU, the Home PINX shall stop timer T4 and enter state HomeIdle.
© ISO/IEC 2003 – All rights reserved 9

The Home PINX is responsible for clearing the call independent signalling connection towards the previous Visitor PINX. This
may occur on receipt of a return result APDU. Alternatively, the signalling connection may be retained for other applications, if
appropriate.
6.5.4.2 Exceptional procedures
If the Visitor area optionally related to a basic service is unchanged, the Home PINX shall revert to state HomeIdle after
sending locUpdate return result.
If the WTM user is not found in the HDB, the Home PINX shall answer the locUpdate invoke APDU with a return error APDU
containing the error invalidServedUserNr.
If the WTM user is not allowed to update the location information, the Home PINX shall answer the locUpdate invoke APDU
with a return error APDU containing the error notAuthorized.
On receipt of a locDelete return error or reject APDU from the previous Visitor PINX, the Home PINX shall stop timer T4 and
enter state HomeIdle.
If timer T4 expires (i.e. the locDelete invoke APDU is not answered by the previous Visitor PINX), the Home PINX shall enter
state HomeIdle.
NOTE 8 - Expiry of timer T4 or receipt of a locDelete return error or reject APDU may invoke management actions to correct the VDB data
in the previous Visitor PINX.
6.5.5 Actions at a Transit PINX for location registration
No special actions are required in support of location registration.
6.5.6 Actions at the previous Visitor PINX for location registration
The SDL representation of procedures at the previous Visitor PINX is shown in D.3 of annex D.
6.5.6.1 Normal procedures
On receipt of a locDelete invoke APDU using the call reference of a call independent signalling connection (as specified in 7.3
of ISO/IEC 11582), the previous Visitor PINX shall check the WTM user’s identity (element wtmUserId), the basic service
(element basicService) if received, and delete the corresponding VDB entry for the WTM user and answer the locDelete invoke
APDU with a return result APDU.
6.5.6.2 Exceptional procedures
If the WTM user is not found in the VDB, the previous Visitor PINX shall answer the locDelete invoke APDU with a return
result APDU.
If the VDB is temporarily unavailable, the previous Visitor PINX shall answer the locDelete invoke APDU with a return error
APDU containing the error temporarilyUnavailable.
6.5.7 Additional actions at the previous Visitor PINX for enquiry from the Visitor PINX
The SDL representation of procedures at the previous Visitor PINX is shown in D.3 of annex D.
6.5.7.1 Normal procedures
On receipt of a pisnEnquiry invoke APDU using the call reference of a call independent signalling connection (as specified in
7.3 of ISO/IEC 11582), the previous Visitor PINX shall check if the VDB contains an entry for the WTM user. If there is an
entry, the WTM user’s identity shall be returned in a pisnEnquiry return result APDU.
6.5.7.2 Exceptional procedures
If the WTM user is not found in the VDB, the previous Visitor PINX shall answer the pisnEnquiry invoke APDU with a return
error APDU containing the error invalidServedUserNr.
NOTE 9 - If a PINX that receives a pisnEnquiry invoke APDU is capable of behaving as a Visitor PINX and as a Directory PINX, it should
respond with a return error APDU only if the WTM user is present in neither the VDB nor the directory.
6.5.8 Actions at the Directory PINX for enquiry from the Visitor PINX
The SDL representation of procedures at the Directory PINX is shown in D.4 of annex D.
10 © ISO/IEC 2003 – All rights reserved

6.5.8.1 Normal procedures
On receipt of a pisnEnquiry invoke APDU using the call reference of a call independent signalling connection (as specified in
7.3 of ISO/IEC 11582), the Directory PINX shall attempt to translate the identity received in the pisnEnquiry invoke APDU to
a WTM user’s identity. The WTM user’s identity shall be returned in a pisnEnquiry return result APDU.
6.5.8.2 Exceptional procedures
If the Directory PINX is unable to translate the identity received in the pisnEnquiry invoke APDU, a pisnEnquiry return error
APDU containing the error invalidServedUserNr shall be returned.
NOTE 10 - If a PINX that receives a pisnEnquiry invoke APDU is capable of behaving as a Visitor PINX and as a Directory PINX, it should
respond with a return error APDU only if the WTM user is present in neither the VDB nor the directory.
6.6 SS-WTLR signalling procedures for location deregistration
Examples of message sequences are shown in annex C.
6.6.1 Actions at the Visitor PINX for location deregistration
The SDL representation of procedures at the Visitor PINX is shown in D.1 of annex D.
6.6.1.1 Normal procedures
When a Visitor PINX determines that a WTM user is deregistered or on receipt of a valid location deregistration request from a
WTM user, the Visitor PINX shall send a locDeReg invoke APDU to the Home PINX 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. Within the argument of
the invoke APDU, the WTM user’s identity shall be included in element wtmUserId and the basic service for which the WTM
user has deregistered may be included in element basicService. The Visitor PINX shall enter state VisitDeReg and start timer
T3.
NOTE 11 - Validation of the deregistration request can involve authentication of the WTM user.
On receipt of the locDeReg return result APDU, the Visitor PINX shall stop timer T3, delete the corresponding VDB
information, revert to state VisitIdle and, if applicable, indicate acceptance to the WTM user.
The Visitor 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.
...