Network Inter Working Between GSM MAP and ANSI-41 CDMA

3GPP2 X.
S0023
Version 1.0
Version Date: July, 2004
Network Interworking Between GSM MAP and

TIA-41 MAP – CDMA2000 Support
Revision: B
COPYRIGHT
3GPP2 and its Organizational Partners claim copyright in this document and individual
Organizational Partners may copyright and issue documents or standards publications in
individual Organizational Partner's name based on this document. Requests for
reproduction of this document should be directed to the 3GPP2 Secretariat at
[email protected]. Requests to reproduce individual Organizational Partner's
documents should be directed to that Organizational Partner. See www.3gpp2.org for more
information.
Revision History
Revision Date
Rev. B v1.0 Initial Publication (Note 1) July 2004
Notes
1. The specification is an extract of J-STD-038-B.
X.S0023
1 N
Neettw
woorrkk IInntteerrw
woorrkkiinngg BBeettw
weeeenn G
GSSMMM MAAPP aanndd TTIIA
A--4411 M
MAAP
P;;
2 R
Reevviissiioonn B
B –– C
CD DMMAA22000000 S
Suuppppoorrtt
3 V
Voolluum
mee 00 –– O
Ovveerrvviieew
w aanndd N
Neettw
woorrkk R
Reeffeerreennccee M
Mooddeell
4 ((R
Reevviissiioonn ooff JJ--S
STTD
D--003388--A
AVVoolluum
mee 00))
Digitally signed
by sanket
sanket
DN:
cn=sanket,
o=Reliance,
c=IN
Date:
2006.06.10
0-i Signature 11:24:40 +
Not 05'30'
Verified
X.S0023
1 Abstract
2 This standard addresses the interworking and interoperability between ANSI-41 MAP[2] and GSM
3 MAP[4] based networks in the support of subscribers roaming between networks. The
4 interworking and interoperability functionality of the services, information flows, and message
5 mappings are specified.
6 This standard consists of four volumes:
7 Volume 0 - Overview and Interworking Reference Model
8 Volume 1 - Service Descriptions
9 Volume 2 - Information Flows
10 Volume 3 - Message Mappings
11 This Volume contains an overview of the Interworking and Interoperability Function (IIF) and the
12 associated network reference model.
0-ii
X.S0023
1 Contents
2 Abstract....................................................................................................................................................ii
3 Contents ................................................................................................................................................. iii
4 List of Tables ...........................................................................................................................................v
5 List of Figures.........................................................................................................................................vi
6 Foreword................................................................................................................................................vii
7 1 Introduction ............................................................................................................................... 1
8 1.1 General........................................................................................................................ 1
9 1.2 Purpose ....................................................................................................................... 1
10 1.3 Scope .......................................................................................................................... 1
11 2 References................................................................................................................................ 2
12 3 Definitions and Acronyms ........................................................................................................ 4
13 3.1 Definitions.................................................................................................................... 4
14 3.2 Acronyms .................................................................................................................... 7
15 4 Overview of Internetwork Roaming ....................................................................................... 11
16 5 IIF Reference Model and Description .................................................................................... 12
17 5.1 Reference Model....................................................................................................... 12
18 5.2 Description ................................................................................................................ 12
19 5.2.1 Provisioned Subscriber Data ..................................................................... 13
20 5.3 Interworking for Network Interfaces ......................................................................... 15
21 5.3.1 HLR - VLR Interface................................................................................... 16
22 5.3.2 Originating / Gateway MSC - Serving MSC Interface ............................... 18
23 5.3.3 MC / SMS-SC - Serving MSC Interface .................................................... 19
24 5.3.4 HLR – SGSN Interface................................................................................ 20
0-iii
X.S0023
1 5.4 IIF Implementation Alternatives................................................................................ 21
2 5.4.1 IIF Resides within a GSM Network Entity .................................................. 21
3 5.4.2 IIF Resides within ANSI-41 Network Entity................................................ 21
4 5.4.3 IIF Resides within External Network Element............................................ 22
5 5.4.4 IIF Resides within Both ANSI-41 and GSM Network Entities ................... 22
6
0-iv
X.S0023
1 List of Tables
2 There are no tables in this volume.
0-v
X.S0023
1 List of Figures
2 Figure 1: IIF Reference Model............................................................................................................ 12
3 Figure 2: HLR - VLR Interface ............................................................................................................ 16
4 Figure 3: Originating / Gateway MSC - Serving MSC Interface........................................................ 18
5 Figure 4: MC / SMS-SC - Serving MSC Interface ............................................................................. 19
6 Figure 5: HLR- SGSN Interface.......................................................................................................... 20
7 Figure 6: IIF Resides within GSM Network Element ......................................................................... 21
8 Figure 7: IIF Resides within ANSI-41 Network Element.................................................................... 21
9 Figure 8: IIF Resides within External Network Element .................................................................... 22
10 Figure 9: IIF Resides within both ANSI-41 and GSM Network Elements......................................... 22
11
0-vi
X.S0023
1 Foreword
2 This foreword is not part of this standard.
3 This standard addresses the interworking and interoperability between ANSI-41 MAP and GSM
4 based networks in the support of subscribers roaming between networks. The objective of the
5 standard is to achieve fully automatic, two-way interoperability between the heterogeneous
6 networks. Services supported by this standard are described along with the associated
7 information flows and message mappings. However, not all services and associated capabilities
8 of ANSI-41 MAP and GSM MAP are supported by this standard. In general the attempt has been
9 to focus on the key subscriber services needed in the market.
10 The focus of the first release of this standard was on common GSM and ANSI-136 TDMA
11 services and associated network signaling (i.e. ANSI-41 MAP and GSM MAP). A prerequisite for
12 this interoperability is multi-mode mobile stations with an enhanced SIM card for roaming
13 between ANSI-136, GSM, and AMPS networks.
14 The first release of the standard did not define or require changes to existing ANSI-41 MAP or
15 GSM MAP to achieve the described interworking and interoperability. However, due to
16 differences between the services and associated capabilities of the MAP protocols, complete and
17 fully transparent interoperability may not have been achieved for some services. Future releases
18 of this standard may require changes to ANSI-41 MAP, GSM MAP and the associated services to
19 achieve full transparency while roaming between the different networks.
20 Aspects of TIA/EIA-136 Revision C have been incorporated into the standard.
21 Revision A adds GPRS service capability in GSM Foreign Mode.
22 Revision B adds one-way and two-way roaming between GSM and CDMA systems.
23
0-vii
X.S0023
1 1 Introduction
2 1.1 General
3 When a subscriber to one network type (e.g., ANSI-41) roams to a network of another type (e.g.,
4 GSM), interworking and interoperability functions are required to support roaming and enable
5 service. This standard describes an Interworking and Interoperability Function (IIF) to support this
6 cross-technology roaming between ANSI-41 and GSM networks. The IIF supports a multi-mode
7 mobile station with a removable Subscriber Identity Module (SIM). The standard also defines the
8 required network message mappings between ANSI-41 MAP and GSM MAP to support the
9 mobile terminal and associated services.
10 This standard includes the support of cross-technology roaming from an ANSI-41 based network
11 to a GPRS network. The GPRS network may be coupled with a GSM network. This feature
12 requires enhancement to the Interworking and Interoperability Function (IIF) which supports a
13 multi-mode mobile station and SIM with GPRS functionality.
14 1.2 Purpose
15 The purpose for this standard is to define and describe the functions necessary for roaming
16 between ANSI-41 MAP and GSM MAP based networks in the support of roaming subscribers.
17 This includes a capability to allow a subscriber to an ANSI-41 based network (e.g., a TDMA or
18 CDMA native subscriber) with a mobile terminal supporting GPRS service to roam to a GPRS
19 network in GSM Foreign Mode.
20 1.3 Scope
21 The scope of this standard are the services, information flows and message mappings which
22 require interworking and interoperability functional specifications to support roaming between
23 ANSI-41 MAP and GSM MAP networks.
24 The scope of this volume is to provide a description of interstandard roaming along with an
25 overview and network reference model for the Interworking and Interoperability Function (IIF).
0-1
X.S0023
1 2 References
2 [1] TIA/EIA-136: “TDMA Third Generation Wireless,” March 2000, ANSI.
3 [2] TIA/EIA-41-D: “Cellular Radiotelecommunications Intersystem Operations,” December
4 1997, ANSI.
5 [3] TIA/EIA-553: “Mobile Station – Land Station Compatibility Specification,” September
6 1989, ANSI.
7 [4] GSM 09.02 Version 6.2.0 Release 1997 “Digital cellular telecommunication system
8 (Phase 2+); Mobile Application Part (MAP) specification”, August 1998, ETSI.
9 [5] TIA/EIA/IS-129, “Interworking/Interoperability Between DCS 1900 and IS-41 Based MAPs
10 for 1800 MHz Personal Communications Systems,” Phase 1, July 1996.
11 [6] TIA/EIA/IS-737-A “IS-41 support for data services for digital terminals (TDMA and
12 CDMA)”.
13 [7] TIA/EIA/IS- 735 “IS-41 support for IS-95-A (advanced CDMA)”.
14 [8] TIA/EIA/TSB58-E “Administration of Parameter Value Assignments for TIA/EIA Spread
15 Spectrum Standards”, January 2002.
16 [9] TIA/EIA-95-B “Mobile Station-Base Station Compatibility Standard for Dual-Mode Spread
17 Spectrum Systems”; Published October 1998.
18 [10] “TIA/EIA-IS-2000-A, cdma2000 Series, March 2000, plus addenda” Mobile Station-Base
19 Station Compatibility Standard for Dual-Mode Spread Spectrum Systems.
20 [11] TIA/EIA-868 – ANSI-41-D Network Based Enhancements to support one-way roaming to
21 GSM, in press.
22 [12] “Enhanced Cryptographic Algorithms, Revision B,” TR-45 AHAG, March, 2002.
23 [13] TIA/EIA/IS-751, “TIA/EIA 41-D Modifications to Support IMSI, February 1998”.
24 [14] TIA/EIA/IS-807, “TIA/EIA-41-D Enhancements for Internationalization”; August, 1999.
25 [15] TIA/EIA-664: “Cellular Features Description”, Telecommunications Industry Association;
26 February 2000, ANSI.
27 [16] “Common Cryptographic Algorithms, Revision C,” October 27, 1998, TR-45 AHAG.
28 [17] TIA/EIA-136-510 “Authentication, encryption of signaling information/user data and
29 privacy”.
30 [18] GSM 02.04 version 6.1.1 Release 1997, “General on Supplementary Services”,
31 (Phase 2+), ETSI.
32 [19] GSM 02.09 version 6.1.0 Release 1997, “Digital cellular telecommunications system
33 Security Aspects”, (Phase 2+), ETSI.
34 [20] GSM 02.30 version 6.1.0 Release 1997, “Man-Machine Interface (MMI) of the Mobile
35 Station”, (Phase 2+), ETSI.
36 [21] GSM 02.41 version 6.0.0, Release 1997, "Operator Determined Barring (ODB)",
37 (Phase 2+), ETSI.
38 [22] GSM 02.79 version 6.0.0, Release 1997, “Support of Optimal Routeing (SOR) Service
39 Definition (Stage 1)”, (Phase 2+), ETSI.
0-2
X.S0023
1 [23] GSM 02.81 version 7.0.0 Release 1998, “Line Identification Supplementary Services –
2 Stage 1“ (Phase 2+), ETSI.
3 [24] GSM 02.82 version 6.0.0 Release 1997, “Call Forwarding (CF) Supplementary Services -
4 Stage 1” (Phase 2+), ETSI.
5 [25] GSM 02.83 version 6.0.0 Release 1997, “Call Waiting (CW) and Call Holding (HOLD)
6 Supplementary Services - Stage 1”, (Phase 2+), ETSI.
7 [26] GSM 02.84 version 6.0.0 Release 1997, “MultiParty (MPTY) Supplementary Services –
8 Stage 1”, (Phase 2+), ETSI.
9 [27] GSM 02.85 version 6.0.0 Release 1997, “Closed User Group (CUG) Supplementary
10 Services – Stage 1 ”, (Phase 2+), ETSI.
11 [28] GSM 02.86 version 6.0.0 Release 1997, “Advice of Charge (AOC) Supplementary
12 Services – Stage 1”, (Phase 2+), ETSI.
13 [29] GSM 02.88 version 6.0.0 Release 1997, “Call Barring (CB) Supplementary Services –
14 Stage 1” (Phase 2+), ETSI.
15 [30] GSM 02.60 version 6.3.1 Release 1997 “General Packet Radio Service (GPRS); Service
16 Description, Stage 1.
17 [31] GSM 03.18 Version 6.2.0 Release 1997 “ Digital cellular communication system
18 (Phase 2+); Basic call handling; Technical realisation”, November 1998, ETSI.
19 [32] GSM 03.79 version 6.2.0 Release 1997, “Digital cellular telecommunications system
20 (Phase 2+); Support of Optimal Routeing (SOR) Technical Realisation”.
21 [33] GSM 03.60 version 6.8.0 Release 1997 “General Packet Radio Service (GPRS);
22 Stage 2”.
23 [34] GSM 03.81 version 6.0.0 Release 1997 “Line Identification Supplementary Services;
24 Stage 2”.
25 [35] GSM 03.40 version 6.2.0 Release 1997 “Technical realization of the Short Message
26 Service (SMS)”.
0-3
X.S0023
1 3 Definitions and Acronyms
2 3.1 Definitions
3 AMPS
4 Advanced Mobile Phone Service (AMPS) is the same as EIA/TIA-553 [3], which is an analog air
5 interface protocol standard for mobile stations and their associated base stations. AMPS
6 networks use ANSI-41 for intersystem signaling.
7 ANSI-41
8 ANSI-41, as used in this document, refers to TIA/EIA-41[2] and the modifications and
9 enhancements as noted in IS-751 and IS-807. This is a network protocol standard to support
10 intersystem operation of cellular networks, such as TDMA or CDMA networks. Key intersystem
11 support defined by ANSI-41 includes automatic roaming, intersystem handoff, and intersystem
12 operation, administration, and maintenance. Among other things, ANSI-41 defines the interfaces
13 between MSCs, between the MSC/VLR and the HLR/AC, and between the MSC and the Short
14 Message Service Center (SMS-SC) or Teleservice Server (TS).
15 ANSI-136
16 ANSI-136, as used in this document, refers to TIA/EIA-136[1], which is a TDMA air interface
17 protocol standard for mobile stations and their associated base stations. ANSI-136 is a dual-
18 mode standard that includes digital (TDMA) operation at 800 MHz and 1900 MHz, and analog
19 (AMPS) operation at 800 MHz. ANSI-136 networks use ANSI-41 for intersystem signaling.
20 ANSI-136 Mode
21 ANSI-136 mode indicates the condition or state of a mobile station accessing an ANSI-136
22 network.
23 ANSI-136 Foreign Mode

24 ANSI-136 foreign mode indicates the condition or state of a GSM native subscriber accessing an
25 ANSI-136 network.
26 ANSI-136 Native Mode

27 ANSI-136 native mode indicates the condition or state of an ANSI-136 native subscriber
28 accessing an ANSI-136 network.
29 ANSI-136 Native Subscriber

30 ANSI-136 native subscriber indicates an end user whose primary or home subscription resides in
31 an ANSI-136 network. These subscribers include both home subscribers from the ANSI-136
32 network, as well as roamers from other ANSI-136 networks.

34 ANSI-41 foreign mode indicates the condition or state of a GSM native subscriber accessing an
35 ANSI-41 based network
0-4
X.S0023
1 CDMA
2 CDMA as used in this document, refers to TIA/EIA -95 [9] or TIA/EIA-2000 [10], which is a CDMA
3 air interface protocol standard for mobile stations and their associated base stations. CDMA is a
4 dual-mode standard that includes digital (CDMA) operation and analog (AMPS) operation. CDMA
5 networks use ANSI-41 for intersystem signaling.
6 CDMA Foreign Mode

7 CDMA foreign mode indicates the condition or state of a GSM native subscriber accessing a
8 CDMA network.
9 CDMA Mode
10 CDMA mode indicates the condition or state of a mobile station accessing a CDMA network.
11 CDMA Native Mode

12 CDMA native mode indicates the condition or state of an CDMA native subscriber accessing an
13 CDMA network.
14 CDMA Native Subscriber

15 CDMA native subscriber indicates an end user whose primary or home subscription resides in an
16 CDMA network. These subscribers include both home subscribers from the CDMA network, as
17 well as roamers from other CDMA networks.
18 Class A mobile
19 Class A mobile station is a GSM mobile that can operate in Class A mode: both GSM circuit-
20 switched and GPRS packet services simultaneously.
21 Class B mobile
22 Class B mobile station is a GAIT or GSM mobile that operates in Class B mode: can operate
23 alternatively GSM circuit-switched or GPRS packet services (1 type service at a time). The mobile
24 can be attached to GSM and GPRS networks simultaneously in this case. The subscriber cannot
25 be simultaneously attached to an ANSI-41 MSC.
26 Class C mobile
27 Class C mobile station is a GSM mobile that can only operate in Class C mode: GSM circuit-
28 switched only or GPRS packet services only. The mobile is attached to only one network at a
29 time.
30 GPRS HLR
31 General Packet Radio Service Home Location Register is the HLR responsible for GPRS
32 functions. It interfaces with the SGSN and GGSN and Authentication Center.
33 GPRS in GSM Foreign Mode

34 GPRS in GSM Foreign Mode is a subset of GSM Foreign Mode and indicates the condition or
35 state of an ANSI-41 native subscriber accessing a GPRS network. The GPRS network may be
36 coupled with a GSM network.
37 GSM
38 Global System for Mobile Communications (GSM) defines both air interface and network
39 intersystem protocol standards for mobile stations (MS), base station systems (BSS), and
40 network switching systems (NSS).
0-5
X.S0023
1 GSM CS attached
2 GSM circuit-switched services attached means that the subscriber is attached to a GSM MSC.
3 This is also referred to as IMSI attached
4 GSM CS detached
5 GSM circuit-switched services detached means that the subscriber is detached from a GSM
6 MSC. This is also referred to as IMSI detached.
7 GSM Foreign Mode

8 GSM foreign mode indicates the condition or state of an ANSI-41 native subscriber accessing a
9 GSM network.
10 GSM Mode
11 GSM mode indicates the condition or state of a mobile station accessing a GSM network.
12 GSM Native Mode

13 GSM native mode indicates the condition or state of a GSM native subscriber accessing a GSM
14 network.
15 GSM Native Subscriber

16 GSM native subscriber indicates an end user whose primary or home subscription resides in a
17 GSM network. These subscribers include both home subscribers from the GSM network, as well
18 as roamers from other GSM networks.
19 Late Call Forwarding

20 Call Forwarding invoked after the call has been offered to the terminating VMSC (e.g., CFB,
21 CFNA/CFNRy, CFNRc) .
22 Mobile Equipment
23 The radio transceiver, main processing unit, and man-machine interface necessary to access the
24 radio network.
25 Mobile Station
26 The mobile equipment and the SIM together make up the mobile station, which is the wireless
27 radiotelephone used by the subscriber.
28 Subscriber Identity Module

29 A smart card that plugs into the mobile equipment and that contains the authentication
30 algorithms, and stores service-oriented subscription information.
0-6
X.S0023
1 3.2 Acronyms
2 AC Authentication Center in ANSI TIA/EIA-41 based networks
3 ADN Abbreviated Dialing Numbers
4 AMPS Advanced Mobile Phone Service
5 ANSI American National Standards Institute
6 AuC Authentication Center in GSM networks
7 BAIC Barring of All Incoming Calls
8 BAOC Barring of All Outgoing Calls
9 BIC-Roam Barring of Incoming Calls while Roaming Outside HPLMN Country
10 BMI Base Station, Mobile Switching System, and Interworking Function
11 BOIC Barring of Outgoing International Calls
12 BOIC-exHC Baring of Outgoing International Calls Except to HPLMN Country
13 CDMA Code-Division Multiple Access
14 CFB Call Forwarding Busy
15 CFNA Call Forwarding No Answer
16 CFNRc Call Forwarding Not Reachable
17 CFNRy Call Forwarding No Reply
18 CFU Call Forwarding Unconditional
19 CPHS Common PCN Handset Specification
20 CS Circuit-Switched
21 DCS Data Coding Scheme
22 EDGE Enhanced Data Rates Through Global Evolution
23 EIA Electronics Industries Association
24 ESN Electronic Serial Number
25 ETSI European Telecommunications Standards Institute
0-7
X.S0023
1 EUI ESN Usage Indicator
2 FC Feature Code
3 FDN Fixed Dialing Numbers
4 FSM Forward Short Message
5 GGSN Gateway GPRS Serving Node
6 GGSN Gateway GPRS Serving Node
7 GHOST GSM Hosted SMS Teleservice
8 GMSC Gateway Mobile Switching Center
9 GPRS General Packet Radio Service
10 GSM Global System for Mobile Communications
11 GSM Global System for Mobile Communications
12 HLPI Higher Layer Protocol Indicator
13 HLR Home Location Register
14 HPLMN Home Public Land Mobile Network
15 IIF Interworking and Interoperability Function
16 IMEI International Mobile Equipment Identifier
17 IMSI International Mobile Subscriber Identity
18 Interim OAA Interim Over-the-Air Activation
19 IRDB Intelligent Roaming Database
20 ISUP ISDN User Part
21 ITU International Telecommunications Union
22 MAP Mobile Application Part
23 MC ANSI-41 Message Center (for SMS)
24 MDN Mobile Directory Number
25 ME Mobile Equipment
26 MF Multi-Frequency
0-8
X.S0023
1 MIN Mobile Identification Number
2 MO Mobile Originated
3 MS Mobile Station
4 MSC Mobile Switching Center
5 MSID Mobile Station Identity
6 MSISDN Mobile Subscriber ISDN Number
7 MSRN Mobile Station Routing Number
8 MT Mobile Terminated
9 MWN Message Waiting Notification
10 NAM Numeric Assignment Module
11 NSDB Network Selection Database
12 ODB Operator Determined Barring
13 OR Optimal Routing
14 OTA Over-the-Air Activation
15 PCS Personal Communications Service
16 PDP Packet Data Protocol
17 PDU Packet Data Unit
18 PIN Personal Identification Number
19 PLMN Public Land Mobile Network
20 PRN Provide Roaming Number
21 PSAP Public Safety Access Point
22 SC Service Center
23 SESN SIM Electronic Serial Number
24 SGSN Serving GPRS Support Node
25 SID System Identity
26 SIM Subscriber Identity Module
0-9
X.S0023
1 SMDPP Short Message Delivery Point-to-Point
2 SME Short Message Entity
3 SMS Short Message Service
4 SMS-GMSC GSM Short Message Service Gateway Mobile Switching Center
5 SMS-IWMSC GSM Short Message Service Interworking Mobile Switching Center
6 SMS-SC GSM Short Message Service Center
7 SOC System Operator Code
8 SS7 Signaling System 7
9 TDMA Time Division Multiple Access
10 TIA Telecommunications Industry Association
11 TLDN Temporary Location Directory Number
12 TMSI Temporary Mobile Station Identity
13 TP-FCS TP Failure Cause
14 TS Teleservice Server
15 TSAR Teleservice Segmentation and Reassembly
16 UDH Universal Data Header
17 VLR Visitor Location Register
18 VPLMN Visitor Public Land Mobile Network
19 WAP Wireless Application Protocol
20 WEMT Wireless Enhanced Messaging Teleservices
0-10
X.S0023
1 4 Overview of Internetwork Roaming

2 Commercial mobile radio networks are implemented using several different standards. Some
3 example radio access networks based on different standards include Advanced Mobile Phone
4 Service (AMPS) based on TIA-553, Time Division Multiple Access (TDMA) based on ANSI-136,
5 Code Division Multiple Access (CDMA) based on IS-95 and TDMA based on the Global System
6 for Mobile Communication (GSM) standard. Furthermore, both TDMA and CDMA and GSM uses
7 different network signaling standards.
8 In order to provide greater service ubiquity and flexibility, the need to offer subscribers access to
9 multiple networks based on different standards has been identified. Depending on the types of
10 networks available in the subscriber's location, the subscriber shall access service on a network
11 based on one of several different standards.
12 The type of network provided in the subscriber's home location area is native for this subscriber.
13 When the subscriber accesses any network using this technology or standard, the subscriber is
14 operating in native mode. Conversely, when the subscriber accesses a network using a
15 technology or standard which is different from the home location's network, the subscriber is
16 operating in foreign mode. Interstandard roaming allows the subscriber to seamlessly obtain
17 service in foreign mode.
0-11
X.S0023
1 5 IIF Reference Model and Description

2 5.1 Reference Model
3 The Interworking and Interoperability Function (IIF) provides a signaling control interface between
4 ANSI-41 and GSM network entities. This interface is provided to enable service access when a
5 subscriber operates in a foreign network whose signaling protocol is different from the home
6 network's protocol. Figure 1 below depicts the family of network interfaces provided by the IIF in
7 interconnecting networks.
SMS
MC
SMS -SC
-IWMSC
N
Q
E SMS
AC H HLR E
-GMSC
D
IIF D
D
HLR H AuC
VLR D
E
E
VLR
MSC Gr
MSC
SGSN
TIA/EIA-41
GSM
Network Entities Network Entities
8 Figure 1: IIF Reference Model
9 5.2 Description
10 GSM and ANSI-41 network entities rely on different network signaling protocols to support
11 mobility management and service realization. When a subscriber to a network supported by
12 ANSI-41 network entities (i.e., a native TDMA or CDMA subscriber) accesses a visited GSM
13 network, the visited network uses GSM Mobile Application Part (MAP) signaling, while the
14 controlling home network uses ANSI-41 MAP signaling. Likewise, when a native GSM subscriber
15 accesses a visited ANSI-41 based network, the visited network uses ANSI-41 MAP signaling,
16 while the controlling home network uses GSM MAP signaling.
17 To support “seamless” interoperability of service between GSM and ANSI-41 network entities, an
18 interworking and interoperability function (IIF) or gateway shall map messages between GSM and
19 ANSI-41 MAP. ANSI-41 MAP also supports analog AMPS capability, which is defined as a subset
20 of ANSI-136.
21 In most cases, the IIF interprets a signaling message in one protocol and converts it to the
22 equivalent signaling message in the other network protocol.
0-12
X.S0023
1 5.2.1 Provisioned Subscriber Data

2 The IIF does not duplicate the subscriber’s existing HLR, but provides a gateway to any visited
3 network that uses a foreign MAP protocol. The original source of subscription data remains in the
4 home network’s HLR. Most of this data shall not reside in the IIF, but shall be dynamically
5 converted and translated between GSM and ANSI-41 MAP messages as needed.
6 Nevertheless, some basic subscriber identity information needs to be provisioned in the IIF to
7 support this mapping process, such as:
8 • International Mobile Subscriber Identity (IMSI)
9 • Mobile Identification Number (MIN)
10 • Electronic Serial Number (ESN)
11 • Terminal type
12 • Network Access Mode (non-GPRS, GPRS or both)
13 Authentication and encryption services are critical functions that shall be supported with network
14 interoperability. These capabilities are managed in both GSM and ANSI-41 networks by the
15 Authentication Center (AuC or AC), which can be physically separated from the associated HLR
16 or integrated with it. Different authentication processes and algorithms are defined for GSM and
17 ANSI-41. Therefore, subscriber specific authentication data shall be provisioned and maintained
18 on both a GSM AuC and ANSI-41 AC, in order to support service on either network.
19 Subscriber data that needs to be maintained for ANSI-41 networks includes:
20 • Ki (GSM subscriber authentication key)
21 • Triplets or groups of Kc (cipher key), CKSN (cipher key sequence number), and SRES
22 (signed response) for GSM based authentication and ciphering
23 • A-key (AMPS/ANSI-136 or IS-95 authentication key)
24 • SSD-A (AMPS/ANSI-136 or IS-95 shared secret data for authentication)
25 • SSD-B (AMPS/ANSI-136 or IS-95 shared secret data used for generated signaling
26 message encryption (SME) and voice privacy (VP) masks: the
27 CDMAPrivateLongCodeMask or the TDMA VoicePrivacyMask)
28 The foreign mode Authentication Center can be integrated into the IIF gateway or implemented
29 as a separate network element.
30 Optionally, IIF may support one-way roaming only from CDMA to GSM network. In this case no
31 data is provisioned at IIF level and ANSI-41 HLR/AC must be compliant with TIA/EIA -868 [11].
32 All the changes are made on the assumption the new requirements for UIM/handsets are
33 working.
34
35 The following items are basic assumptions on which the optional one-way roaming scenario is
36 based:
37
38 • The IIF is not provisioned with any subscriber data.
39 • There is no subscriber specific data stored in the IIF.
40 • The Home System is enhanced to support ANSI -41-to-GSM roaming.
0-13
X.S0023
1 • The ANSI-41 Home System has enhanced authentication capabilities to support roaming
2 of subscribers to GSM systems. Subscribers may be using multi-mode mobile stations
3 capable of roaming into a GSM system or UIMs that are inserted into GSM terminal
4 equipment. A valid SSD is generated in the UIM before the user can roam to a GSM
5 system
6 • A valid SSD value must be generated in the UIM (or multi-mode MS) before the
7 subscriber can roam into a GSM system. The IIF functions as a VLR in its interaction with
8 the ANSI -41 Home System
9 • The ANSI-41 AC shares SSD with the IIF for subscribers roaming in a GSM network. The
10 IIF generates the triplets (RAND, XRES, KC) used by the GSM system. The triplet
11 generation function is specified in section 2.2.4.1 of “Enhanced Cryptographic Algorithms,
12 Revision B.”
13 • After the subscriber is registered in a GSM system, the IIF reports authentication failures
14 to the ANSI-41 system using the AuthenticationFailureReport operation. SSD is shared
15 with the IIF until registration in the GSM system is canceled. The ANSI -41 AC/HLR can
16 cancel registration using the RegistrationCancellation operation.
17 • The IIF shall remove the subscriber’s SSD when registration in the GSM system is
18 canceled. SSD Update cannot be performed when the MS is roaming in a GSM system
19 • A new SystemCapabilities parameter value shall be defined to indicate a GSM system
20 • A SystemCapabilities parameter value indicating GSM system shall be used by the IIF to
21 indicate that the Serving network is using GSM authentication and privacy procedures.
22 This indicates that
23 • SSD Update cannot be performed. It also indicates that the ESN sent to the ANSI-41
24 home system was not received from the MS. The IIF functions as a GSM HLR/AC in its
25 interactions with the GSM system
26 • The IIF provides the GSM triplets needed for authentication and privacy in the GSM
27 system. The
28 • IIF generates triplets using the SSD value stored in the UIM (or multi-mode MS).
29 • When roaming in a GSM system, the UIM uses the “authentication” algorithm supported
30 by the IIF
31 • When roaming is a GSM system, the UIM (or multi-mode MS) must use an authentication
32 algorithm supported by the IIF for the computation of the cipher key and the response to
33 the random challenge.
34 • The ANSI-41 home system is expected to update SSD when the MS returns to an
35 ANSI–41 system
36 • The subscriber’s SSD should be updated when the user returns to an ANSI-41 system.
37 • The IIF shall prevent disclosure of SSD values received from ANSI-41 systems
38 • The IIF shall provide a secure method of storing SSD values received from ANSI-41
39 systems.
40 • The SSD values shall not be disclosed nor transmitted to any other network entity.
0-14
X.S0023
1 • The IIF shall be able to request the MS’s ESN in the AuthenticationRequest INVOKE sent
2 to the home ANSI-41 system
3
4 To support GPRS service in GSM Foreign Mode, GPRS specific subscriber data also needs to be
5 provisioned in the IIF such as :
6 • GGSN-list (GGSN Number and optional IP address)
7 • PDP Type
8 • PDP Address (if dynamic addressing is not allowed)
9 • Quality of Service Subscribed
10 5.3 Interworking for Network Interfaces

11 This following describes the individual network interfaces for which interoperability is provided by
12 the IIF. For each particular interoperability function and interface interworking, the IIF
13 simultaneously emulates a network element using foreign protocol messaging and a
14 corresponding network element using native protocol messaging. The emulation functions in the
15 IIF conform to existing ANSI-41 and GSM protocols when communicating over the external
16 interfaces.
17 The following figures depict the emulated network elements within the IIF using dashed lines. The
18 dashed lines connecting emulated network elements within the IIF represent internal, conversion
19 or mapping interfaces. All solid connecting lines depict standard ANSI-41 or GSM interfaces
20 based on existing protocols.
21 The arrow above each figure represents information exchange for the top half of the figure, while
22 the arrow below each figure represents information exchange for the bottom half of the figure.
0-15
X.S0023
1 5.3.1 HLR - VLR Interface

2 The IIF provides an interface between the subscriber's HLR and any VLR which uses a foreign
3 network signaling protocol. This interworking is provided over the interface reference "D" depicted
4 in the network reference model. Figure 2 below depicts the interworking and control interface
5 provided by the IIF in this case.
ANSI-41 subscriber roaming
to GSM network
IIF
ANSI-41 D ANSI-41 GSM D GSM

HLR VLR HLR VLR
ANSI-41 D ANSI-41 GSM D GSM

VLR HLR VLR HLR
GSM subscriber roaming

to ANSI-41 network
TIA/EIA-41 GSM
6
7 Figure 2: HLR - VLR Interface
8 5.3.1.1 ANSI-136 Foreign Mode Implementation for GSM Subscriber
9 When a GSM native subscriber operates in ANSI-136 foreign mode, the mobile station shall use
10 the ANSI-136 air interface. The interoperability gateway or IIF shall provide both ANSI-41 HLR
11 and GSM VLR emulation to allow the subscriber to automatically register and obtain service. To
12 the visited ANSI-41 network, the subscriber appears to register with the IIF, emulating an
13 ANSI-41 HLR. This emulated ANSI-41 HLR acts as a limited proxy for the actual GSM HLR, with
14 the true GSM HLR retaining ultimate control. At the same time, to the home GSM network, the
15 subscriber appears to register from the IIF, emulating a GSM VLR. The IIF links ANSI-41 MAP
16 operations and data to the equivalent GSM MAP operations and data, and vice versa, in order to
17 support interoperability.
18 To support ANSI-136 foreign mode operation, an ANSI-136 Authentication Center (AC) can be
19 integrated into the IIF gateway or implemented as a separate network element.
20 5.3.1.2 GSM Foreign Mode Implementation for ANSI-136 Subscriber
21 Similarly, when an ANSI-136 native subscriber operates in GSM foreign mode, the mobile station
22 shall use the GSM air interface. The interoperability gateway or IIF shall provide both GSM HLR
23 and ANSI-41 VLR emulation to allow the subscriber to automatically register and obtain service.
24 To the visited GSM network, the subscriber appears to register with the IIF, emulating a GSM
25 HLR. This emulated GSM HLR acts as a limited proxy for the actual ANSI-41 HLR, with the true
26 ANSI-41 HLR retaining ultimate control. At the same time, to the home ANSI-136 network, the
27 subscriber appears to register from the IIF, emulating an ANSI-136 VLR. The IIF links GSM MAP
0-16
X.S0023
1 operations and data to the equivalent ANSI-41 MAP operations and data, and vice versa, in order
2 to support interoperability.
3 To support GSM foreign mode operation, a GSM Authentication Center (AuC) can be integrated
4 into the IIF gateway or implemented as a separate network element.
5 5.3.1.3 CDMA Foreign Mode Implementation for GSM Subscriber

6 When a GSM native subscriber operates in IS-95 foreign mode, the mobile station shall use the
7 CDMA air interface. The interoperability gateway or IIF shall provide both ANSI-41 HLR and GSM
8 VLR emulation to allow the subscriber to automatically register and obtain service. To the visited
9 ANSI-41 network, the subscriber appears to register with the IIF, emulating an ANSI-41 HLR.
10 This emulated ANSI-41 HLR acts as a limited proxy for the actual GSM HLR, with the true GSM
11 HLR retaining ultimate control. At the same time, to the home GSM network, the subscriber
12 appears to register from the IIF, emulating a GSM VLR. The IIF links ANSI-41 MAP operations
13 and data to the GSM MAP operations and data, and vice versa, in order to support
14 interoperability.
15 5.3.1.4 GSM Foreign Mode Implementation for CDMA Subscriber

16 Similarly, when an CDMA native subscriber operates in GSM foreign mode, the mobile station
20 HLR. This emulated GSM HLR acts as a limited proxy for the actual ANSI-41 HLR, with the true
21 ANSI-41 HLR retaining ultimate control. At the same time, to the home CDMA network, the
22 subscriber appears to register from the IIF, emulating an CDMA VLR. The IIF links GSM MAP
23 operations and data to the ANSI-41 MAP operations and data, and vice versa, in order to support
0-17
X.S0023
1 5.3.2 Originating / Gateway MSC - Serving MSC Interface

2 The IIF provides a MAP interface between the subscriber's originating or gateway MSC to a
3 serving MSC which uses a foreign network signaling protocol. This interworking is provided over
4 the interface reference "E" depicted in the network reference model. In this case, no ISUP or MF
5 signaling is supported over this interface. Figure 3 below depicts the interworking and control
6 interface provided by the IIF in this case.
7 This interface is key to supporting optimal routing for late call forwarding, where the serving MSC
8 wishes to signal back to the originating or gateway MSC in order to request forwarding of the call.
9 In order to support optimal routing for late call forwarding, the IIF provides originating or gateway
10 MSC emulation.
to GSM network
IIF
ANSI-41 ANSI-41 GSM GSM

Originating E Serving Gateway E Serving
MSC MSC MSC MSC
ANSI-41 ANSI-41 GSM GSM

Serving E E
Originating Serving Gateway
MSC MSC MSC MSC

to ANSI-41 network
TIA/EIA-41 GSM
11
12 Figure 3: Originating / Gateway MSC - Serving MSC Interface
0-18
X.S0023
1 5.3.3 MC / SMS-SC - Serving MSC Interface

2 The IIF provides an interface from the subscriber's short message service message center (MC /
3 SMS-SC) to a serving MSC which uses a foreign network signaling protocol. This interworking is
4 provided over the interface references "Q" and "E" depicted in the network reference model. In
5 the case of ANSI-41 messaging, the MC has a direct "Q" interface to the serving MSC. In the
6 case of GSM messaging, the SMS-SC interfaces with the serving MSC via the SMS Interworking
7 MSC (SMS-IWMSC) or the SMS Gateway MSC (SMS-GMSC) over the "E" interface. Figure 4
8 below depicts the interworking and control interface provided by the IIF in this case.
to GSM network
IIF
GSM GSM
SMS- E Serving
ANSI-41 IWMSC MSC
ANSI-41 GSM
Q Serving E
MC SMS-SC
MSC GSM
GSM
SMS-
SMS-
GMSC
ANSI-41 IWMSC
ANSI-41 E GSM
Serving Q MC SMS-SC
MSC GSM GSM
Serving E SMS-
MSC GMSC

to ANSI-41 network
TIA/EIA-41 GSM
9
10 Figure 4: MC / SMS-SC - Serving MSC Interface
11 5.3.3.1 ANSI-41 Foreign Mode Implementation for GSM Subscriber
12 For short message service (SMS) interoperability, the IIF shall provide ANSI-41 Message Center
13 (MC) emulation, acting as a limited proxy for the subscriber’s GSM Short Message Service
14 Center (SMS-SC). The IIF links GSM MAP operations and data to the equivalent ANSI-41 MAP
15 operations and data, and vice versa.
16 5.3.3.2 GSM Foreign Mode Implementation for ANSI-41 Subscriber
17 For SMS interoperability, the IIF shall provide GSM SMS-SC emulation, as well as SMS-GMSC
18 or SMS-IWMSC emulation, acting as a limited proxy for the subscriber’s ANSI-41 MC. The IIF
19 links ANSI-41 MAP operations and data to the equivalent GSM MAP operations and data, and
20 vice versa. In some cases, the IIF may need to originate short messages in order to support
0-19
X.S0023
1 5.3.4 HLR – SGSN Interface

2 The IIF provides an interface between the subscriber's HLR and any SGSN which uses a foreign
3 network signaling protocol. This interworking is provided over the interface reference "Gr"
4 depicted in the network reference model. Figure 5 below depicts the interworking and control
5 interface provided by the IIF in this case.
ANSI-41 Subscriber roaming

to GPRS network
IIF
ANSI-41 D ANSI-41 GSM Gr

HLR VLR HLR SGSN
TIA/EIA-41 GSM Network

Network Entities Entities
6
7 Figure 5: HLR- SGSN Interface
8 5.3.4.1 GPRS in GSM Foreign Mode Implementation for ANSI-41 Subscriber
9 When an ANSI-41 native subscriber operates GPRS in GSM foreign mode, the mobile station
13 HLR. This emulated GSM HLR acts as a limited proxy for the actual ANSI-41 HLR. At the same
14 time, to the home ANSI-41 network, the subscriber appears to register from the IIF, emulating an
15 ANSI-41 VLR. The IIF links GSM MAP operations and data to the equivalent ANSI-41 MAP
16 operations and data, and vice versa, in order to support interoperability.
17 To support GPRS in GSM foreign mode operation, a GSM Authentication Center (AuC) can be
18 integrated into the IIF gateway or implemented as a separate network element.
0-20
X.S0023
1 5.4 IIF Implementation Alternatives

2 There are four alternatives for the implementation of the IIF functional element with respect to the
3 network reference model and the network entities that are served. See “5 IIF Reference Model
4 and Description” for applicable interfaces.
5 5.4.1 IIF Resides within a GSM Network Entity

6 The IIF may reside entirely inside an existing GSM network entity as a separate functional
7 element. Each of the interfaces can be supported with this implementation alternative.
TIA/EIA-41 GSM
Network Network
Element Element
IIF
9 Figure 6: IIF Resides within GSM Network Element
10 5.4.2 IIF Resides within ANSI-41 Network Entity

11 The IIF may reside entirely inside an existing ANSI-41 network entity as a separate functional
TIA/EIA-41 GSM
Network Network
Element Element
IIF
13
14 Figure 7: IIF Resides within ANSI-41 Network Element
0-21
X.S0023
1 5.4.3 IIF Resides within External Network Element

2 The IIF may reside external to any existing ANSI-41 or GSM network entity as a separate network
External
Network
Element
IIF
TIA/EIA-41 GSM
Network Network
Element Element
5 Figure 8: IIF Resides within External Network Element
6 5.4.4 IIF Resides within Both ANSI-41 and GSM Network Entities
7 Finally, the IIF may reside within both existing ANSI-41 and GSM network entities at the same
8 time. In this case, each individual subscriber is likely to be served by one particular IIF, although
9 the use of multiple IIFs per subscriber is possible. Again, each of the interfaces can be supported
10 with this implementation alternative. While multiple IIFs can support one particular subscriber,
11 each network interworking function would be supported by one specific IIF implementation.
TIA/EIA-41 GSM
Network Network
Element Element
IIF IIF
12
13 Figure 9: IIF Resides within both ANSI-41 and GSM Network Elements
14
0-22
X.S0023
1 N
Neettw
woorrkk IInntteerrw
woorrkkiinngg B
Beettw
weeeenn GGS SM
MMMA
APP aanndd TTIIA
A--4411 M
MAAP
P;;
2 R
Reevviissiioonn B
B –– C CD
DMMA A22000000 S
Suuppppoorrtt
3 V
Voolluum
mee 11 –– S
Seerrvviiccee D
Deessccrriippttiioonnss
4 ((R
STTD
D--003388--A
AVVoolluum
mee 11))
5 Abstract
6 This volume is based on ANSI-664 [15] and GSM stage 1’s (see GSM 02-series e.g., GSM 02.04,
7 etc. in the References section). Some modifications (primarily simplifications) were made for the
8 purpose of specifying the degree of interoperability desired. ANSI-664 services and GSM services do
9 not necessarily align.
1-i
X.S0023
Contents
Abstract........................................................................................................................................................... i
Contents ........................................................................................................................................................ ii
List of Tables .................................................................................................................................................iii
List of Figures............................................................................................................................................... iv
Foreword........................................................................................................................................................ v
1 Introduction ............................................................................................................................................. 1
1.1 General 1
1.2 Purpose 1
1.3 Scope 1
2 Stage 1 Service Descriptions................................................................................................................. 2
2.1 Authentication ........................................................................................................................... 2
2.2 Call Forwarding......................................................................................................................... 8
2.3 Optimal Routing for Late Call Forwarding .............................................................................36
2.4 Call Waiting (CW) ...................................................................................................................40
2.5 Three-Way Calling (3WC) and Multi-Party (MPTY) .............................................................51
2.6 Calling Number / Line Identification Presentation .................................................................63
2.7 Call Barring (CB) and Operator Determined Barring (ODB).................................................68
2.8 Short Message Teleservice Support (ANSI-41 Networks) ...................................................76
2.9 Message Waiting Notification.................................................................................................83
2.10 GPRS in GSM Foreign mode.................................................................................................88
1-ii
X.S0023
List of Tables
Table 1: CW Subscription Options ............................................................................................................. 40
Table 2: 2-Way State for Call Waiting ....................................................................................................... 43
Table 3: 2-Way Notification State for Call Waiting ................................................................................... 44
Table 4: 2-Way CW State for Call Waiting................................................................................................. 45
Table 5: ANSI-41 Foreign Mode Interoperability for Barring of Outgoing Calls ....................................... 69
Table 6: GSM Foreign Mode Interoperability for Outgoing Call Restrictions ........................................... 69
Table 7: Call Barring Activation Options .................................................................................................... 70
Table 8: Call Barring Deactivation Options................................................................................................ 71
1-iii
X.S0023
List of Figures
There are no figures in this volume.
1-iv
X.S0023
1 Foreword
5 standard is to achieve fully automatic, two-way interoperability between the heterogeneous networks.
6 Services supported by this standard are described along with the associated information flows and
7 message mappings. However, not all services and associated capabilities of ANSI-41 MAP and GSM
8 MAP are supported by this standard. In general the attempt has been to focus on the key subscriber
9 services needed in the market.
10 The focus of the first release of this standard was on common GSM and ANSI-136 TDMA services
11 and associated network signaling (i.e. ANSI-41 MAP and GSM MAP). A pre-requisite for this
12 interoperability is multi-mode mobile stations with an enhanced SIM card for roaming between ANSI-
13 136, GSM, and AMPS networks.
14 The first release of the standard did not define or require changes to existing ANSI-41 MAP or GSM
15 MAP to achieve the described interworking and interoperability. However, due to differences between
16 the services and associated capabilities of the MAP protocols, complete and fully transparent
17 interoperability may not have been achieved for some services. Future releases of this standard may
18 require changes to ANSI-41 MAP, GSM MAP and the associated services to achieve full
19 transparency while roaming between the different networks.
20 Aspects of TIA/EIA-136 Rev C have been incorporated into this standard.
21 Revision A adds the capability of getting GPRS services when roaming in GSM Foreign Mode.
22 Revision B adds roaming between GSM and CDMA systems.
1-v
X.S0023
1 1 Introduction
2 1.1 General
4 GSM), interworking and interoperability functions are required to support roaming and enable service.
5 This standard describes an Interworking and Interoperability Function (IIF) to support this cross-
6 technology roaming between ANSI-41 and GSM networks. The IIF supports a multi-mode mobile
7 station with a removable Subscriber Identity Module (SIM). The standard also defines the required
8 network message mappings between ANSI-41 MAP and GSM MAP to support the mobile terminal
9 and associated services.
10 This standard includes the support of cross-technology roaming from an ANSI-41 based network to a
11 GPRS network. The GPRS network may be coupled with a GSM network. This feature requires
12 enhancement to the Interworking and Interoperability Function (IIF) which supports a multi-mode
13 mobile station and Subscriber Identity Module (SIM) with GPRS functionality.
14 1.2 Purpose
15 The purpose for this standard is to define and describe the functions necessary for roaming between
16 ANSI-41 MAP and GSM MAP based networks in the support of roaming subscribers. This includes a
17 capability to allow a subscriber to an ANSI-41 based network (e.g., an ANSI-136 or CDMA native
18 subscriber) with a mobile terminal supporting GPRS service to roam to a GPRS network in GSM
19 Foreign Mode.
20 1.3 Scope
21 The scope of this standard are the services, information flows, and message mappings which require
22 interworking and interoperability functional specifications to support roaming between ANSI-41 MAP
23 and GSM MAP networks.
24 The scope of this volume is a high level (stage 1) description of the services and functionality required
25 to support GSM and ANSI-41 network interoperability. In particular, when in foreign mode (roaming in
26 non-native mode technology), subscribers are able to:
27  roam and register (with authentication);
28  originate and terminate calls;
29  have the following supplementary services operate:
30 - Call Forwarding,
31 - Call Waiting,
32 - Calling Number Identification Presentation - Line Identification Presentation,
33 - Call Barring, and
34 - GSM Multi-Party - ANSI-41 3-way Calling and Conference;
35  have Short Message Service access and Message Waiting Notification;
36  have Late Call Forwarding optimally routed; and
37  have GPRS service in GSM Foreign Mode.
38
1-1
X.S0023
1 2 Stage 1 Service Descriptions

2 When in foreign mode (e.g., GSM or ANSI-41 subscribers accessing respectively ANSI-41 or GSM
3 networks), subscribers are able:
4  to roam and register (with authentication)
5  to originate and terminate calls
6  to have the following supplementary services operate:
7 o Call Forwarding,
8 o Call Waiting, Calling Number/Line Identification Presentation,
9 o Call Barring, and
10 o GSM Multi-Party - ANSI-41 3-way Calling and Conference;
11  to have short message service and Message Waiting Notification; and
12  to have late call forwarding optimally routed.
13 2.1 Authentication
14 Authentication defines the ability for a wireless network to confirm the identity of a mobile station at
15 the time of connection, and to ensure the validity of this identity during the complete connection time.
16 This is achieved through the use of cryptographic schemes based on secret key algorithms.
17 2.1.1 General Description

18 The authentication procedure starts based on network events received by the mobile station. These
19 events include mobile station origination, termination, registration and R-DATA messages in ANSI-41
20 TDMA or CDMA. These events are dependent of the technology used and are different in GSM and
21 ANSI-41. The authentication procedure involves an authentication center on the network side and an
22 authentication module in the mobile station. It is initiated by a random number sent from the
23 authentication center to the authentication module. The authentication module uses this random
24 value and a combination of secret data and internal values to create an authentication value and a
25 key that is optionally used for encryption. This authentication value is sent back to the authentication
26 center, which verifies its validity by computing it again based on the same input. A successful
27 outcome of the authentication process occurs only when it can be demonstrated that the
28 authentication module and the authentication center possess identical sets of secret values.
29 Optionally, IIF may support one-way roaming only from CDMA to GSM network. In this case since no
30 data is provisioned at IIF level, IIF must generate the GSM triplets using as input the authentication
31 parameters returned by ANSI-41 HLR/AC, and ANSI-41 HLR/AC must be compliant with PN-4925 (to
32 be published as TIA/EIA-868 28]. All the changes are made on the assumption the new requirements
33 for UIM/handsets are working.
34 2.1.1.1 Applicability to Telecommunications Services

35 Not identified.
1-2
X.S0023
1 2.1.2 Normal Procedures With Successful Outcome

2 In ANSI-41 native and foreign mode, the authentication procedure is done according to the
3 procedures defined in TIA/EIA-136-510 [17].
4 In GSM native and foreign mode, the authentication procedure is done according to the procedures
5 defined in GSM 02.09 [19].
6 ANSI-136 Mode
7 The ANSI-136 authentication module is defined by the ANSI-136 directory. It holds the secret data
8 and internal values used during the authentication process.
9 The secret data used in the ANSI-136 authentication process is the shared secret data (SSD). The
10 internal values used within the ANSI-136 authentication process are the ESN, the MIN1 and the
11 MIN2.
12 GSM Mode
13 The GSM authentication module is defined by the GSM directory in the SIM. The SIM card can
14 support multiple GSM subscriptions and each one has its own authentication module.
15 The secret data used in the GSM authentication process is the Ki. There is no internal data used in
16 the GSM authentication process.
17 ANSI-41 Mode
18 The ANSI-41 authentication module is defined by the air-interface-specific directory in the mobile
19 station. The data used for authentication is as defined by the Common Cryptographic Algorithm
20 (CAVE) The ANSI-41 mode includes the ANSI-136 Mode described above.
21 2.1.2.1 Authorization (or Provision)

22 In GSM mode, the secret data (Ki) is stored in advance in the network’s Authentication Center (AuC)
23 as well as the SIM’s authentication module at the time of personalization of the SIM. This secret data
24 on the SIM cannot be modified after the issuance of the SIM.
25 In ANSI mode, the secret data (A-key) is stored in advance in the network’s Authentication Center
26 (AC) as well as the mobile’s station authentication module at the time of provisioning. This secret data
27 maybe overwritten with a new value via reprovisioning or over the air parameter administration for
28 CDMA
29 In ANSI-136, the shared secret data (SSD) is generated from a root secret data (A-Key). This root
30 secret data is stored in advance in the authentication module and can be modified after issuance. The
31 generation of the secret data is done by the authentication center issuing an SSD UPDATE request
32 with the appropriate parameters.
33 2.1.2.2 De-Authorization (or Withdrawal)

34 The de-authorization is done at the Authentication Center.
35 2.1.2.3 Registration
36 None identified.
37 2.1.2.4 De-Registration (or Erasure)

38 None identified.
1-3
X.S0023
1 2.1.2.5 Activation
2 Activation is performed by the operator or serving system.
3 2.1.2.6 De-Activation
4 De-activation is performed by the operator or serving system.
5 2.1.2.7 Invocation
6 The authentication function is invoked in the mobile station by selecting the appropriate directory
7 (GSM or ANSI-41) on the authentication module and sending the appropriate command (RUN AUTH
8 ALGO or RUN CAVE), with the appropriate parameters (random value, option flag, internal values).
9 The authentication function is invoked in the network by the receipt of an authentication message
10 from the mobile station.
11 2.1.2.8 Normal Operation with Successful Outcome

12 If the Authentication Signature result calculated by the mobile station and sent to the BMI (Base
13 Station, Mobile Switching Center, Interworking Function) matches the result calculated by the BMI
14 then call processing and feature access is allowed by the BMI.
15 2.1.3 Exception Procedures or Unsuccessful Outcome

16 In the event that the mobile station cannot provide the correct Authentication Signature result to the
17 BMI then call processing and feature access may be denied by the BMI.
19 None identified.
20 2.1.3.2 De-Registration / Erasure

21 None identified.
23 None identified.
25 None identified.
27 None identified.
28 2.1.3.6 Exceptions While Roaming

29 None identified.
30 2.1.3.7 Exceptions During Intersystem Handoff

31 None identified.
32 2.1.4 Alternate Procedures

33 None identified.
1-4
X.S0023
1 2.1.5 Interactions With Other Features and Services

2 2.1.5.1 Advice of charge (AoC)
3 None identified.
4 2.1.5.2 Barring of All Outgoing Calls (BAOC)

5 None identified.
6 2.1.5.3 Barring of Outgoing International Calls (BOIC)

7 None identified.
8 2.1.5.4 Barring of Outgoing International Calls except those directed to the Home PLMN
9 (BOIC-exHC)
10 None identified.
11 2.1.5.5 Barring of All Incoming Calls (BAIC)

12 None identified.
13 2.1.5.6 Barring of Incoming Calls when Roaming Outside the Home PLMN (BIC-Roam)
14 None identified.
15 2.1.5.7 Call Delivery (CD)

16 If the Authentication Signature result at the mobile station does not match that of the BMI then Call
17 Delivery shall not be allowed.
18 2.1.5.8 Call Forwarding—Busy (CFB)

19 None identified.
20 2.1.5.9 Call Forwarding—Default (CFD)

21 None identified.
22 2.1.5.10 Call Forwarding—No Answer / No Reply (CFNA / CFNRy)

23 None identified.
24 2.1.5.11 Call Forwarding—Not Reachable (CFNRc)

25 None identified.
26 2.1.5.12 Call Forwarding—Unconditional (CFU)

27 None identified.
28 2.1.5.13 Call Transfer (CT)

29 None identified.
30 2.1.5.14 Call Waiting / Call Hold (CW / HOLD)

31 None identified.
32 2.1.5.15 Calling Number / Line Identification Presentation (CNIP / CLIP)

33 None identified.
1-5
X.S0023
1 2.1.5.16 Calling Number / Line Identification Restriction (CNIR / CLIR)

2 None identified.
3 2.1.5.17 Calling Name Presentation (CNAP)

4 None identified.
5 2.1.5.18 Calling Name Restriction (CNAR)

6 None identified.
7 2.1.5.19 Closed User Group (CUG)

8 None identified.
9 2.1.5.20 Conference Calling / Multi Party Service (CC / MPTY)

10 A special challenge shall be made to the mobile station by the BMI in order to activate this feature. If
11 the Authentication Signature result at the mobile station does not match that of the BMI then this
12 feature shall not be allowed.
13 2.1.5.21 Do Not Disturb (DND)

14 None identified.
15 2.1.5.22 Emergency Services (Future)

16 None identified.
17 2.1.5.23 Flexible Alerting (FA)

18 None identified.
19 2.1.5.24 Message Waiting Notification (MWN)

20 None identified.
21 2.1.5.25 Mobile Access Hunting (MAH)

22 None identified.
23 2.1.5.26 Password Call Acceptance (PCA)

24 None identified.
25 2.1.5.27 Preferred Language (PL)

26 None identified.
27 2.1.5.28 Priority Access and Channel Assignment (PACA)

28 None identified.
29 2.1.5.29 Remote Feature Control (RFC)

30 None identified.
31 2.1.5.30 Selective Call Acceptance (SCA)

32 None identified.
33 2.1.5.31 Subscriber PIN Access (SPINA)

34 The Authentication Feature shall take precedence over the SPINA feature.
1-6
X.S0023
1 2.1.5.32 Subscriber PIN Intercept (SPINI)

2 The Authentication Feature shall take precedence over the SPINI feature.
3 2.1.5.33 Three-Way Calling / Multi Party Service (3WC / MPTY)

4 A special challenge shall be made to the mobile station by the BMI in order to activate this feature. If
5 the Authentication Signature result at the mobile station does not match that of the BMI then this
6 feature shall not be allowed.
7 2.1.5.34 Voice Message Retrieval (VMR)

8 If this feature requires the mobile station to originate a call from the mobile station and the
9 Authentication Signature result at the mobile station does not match that of the BMI then this feature
10 shall not be allowed.
11 2.1.5.35 Voice Privacy (VP)

12 The Voice Privacy elements (e.g., for ANSI-41 TDMA or CDMA) are derived from the same secret
13 A–Key as for the Authentication algorithm. If the HLR/AC for the mobile subscriber does not have
14 knowledge of this information it shall not be able to activate the Voice Privacy feature.
1-7
X.S0023
1 2.2 Call Forwarding

2

4 Call Forwarding, permits a called subscriber to have the system send incoming calls addressed to the
5 called subscriber’s Directory Number to another Directory Number (forward-to number) under certain
6 conditions (e.g., busy, not reachable, or no reply).
7 GSM 02.82 [24] defines the following call forwarding supplementary services:
8  Call forwarding unconditional (CFU);
9  Call forwarding on mobile subscriber busy (CFB);
10  Call forwarding on no reply (CFNRy);
11  Call forwarding on mobile subscriber not reachable (CFNRc).
12 ANSI-664 [15] defines the following call forwarding supplementary services:
13  Call forwarding – Unconditional (CFU)
14  Call forwarding – Busy (CFB)
15  Call forwarding - No answer (CFNA)
16  Call forwarding – Default (CFD)
1-8
X.S0023
1 2.2.2 Call Forwarding Unconditional (CFU)

2
3 2.2.2.1 General Description

4 Call Forwarding—Unconditional (CFU) permits a called subscriber to send incoming calls addressed
5 to the called subscriber’s Directory Number to another Directory Number (forward-to number) or to
6 the called subscriber’s designated voice mail box.
7 2.2.2.1.1 Applicability to Telecommunications Services
8 CFU is applicable to voice telecommunication services.
9 2.2.2.2 Normal Procedures With Successful Outcome

10
11 2.2.2.2.1 Authorization (or Provision)
12 CFU may be generally available or may be provided after pre-arrangement with the service provider.
13 The authorization (provision) may have subscription options. These options are defined in either GSM
14 02.82 [24] (i.e., GSM native mode subscribers) or ANSI-664 [15] (e.g., ANSI-41 TDMA or CDMA
15 native mode subscribers). Authorization or Provisioning may occur while operating in foreign mode.
16 2.2.2.2.2 De-Authorization (or Withdrawal)
17 CFU may be withdrawn by the service provider, at the subscriber’s request or for administrative
18 reasons. De-authorization or withdrawal may occur while operating in foreign mode.
19 2.2.2.2.3 Registration
20 If the subscriber is authorized for Fixed Registration, the forward-to number shall be registered upon
21 authorization (provision). Mobile stations operating in foreign mode may attempt to perform
22 registration procedures normally supported in native mode.
23 The forward-to-number may be registered by the service provider upon authorization (provision) for
24 Variable Registration subscribers
25 GSM foreign mode: A forward-to-number may be registered by a Variable Registration authorized

26 subscriber specifying the CFU registration feature code and a forward-to number termination address
27 as in:
28 *FC + termination address + SEND .
29 Alternatively, if the mobile station offers menu driven control of registration, the mobile station is
30 expected to generate the equivalent GSM functional signaling towards the network.
31 ANSI-41 foreign mode: Registration can take place with an appropriate control procedure by the
32 subscriber, per GSM 02.30 [20]. In ANSI-41 foreign mode, if the equivalent GSM feature code (MMI)
33 is manually entered by the user, the mobile station is expected to issue the relevant ANSI-41 feature
34 code entry.
36 expected to generate the equivalent ANSI-41 feature code entry and resulting call origination based
37 on the menu driven entry.
38 If the registration is accepted, the system shall indicate success using either GSM or ANSI-41
39 signaling techniques depending on the mode of operation.
1-9
X.S0023
1 2.2.2.2.4 De-Registration (or Erasure)
2 Mobile stations operating in foreign mode may attempt to perform De-Registration or Erasure
3 procedures normally supported in native mode.
4 A forward-to-number may be de-registered upon de-activation (at the home service provider option).
5 GSM foreign mode: If the de-registration is to be separate from de-activation, the de-registration
6 feature code must be distinct from the corresponding de-activation feature code.
7 GSM foreign mode: CFU may be de-registered by a Variable Registration authorized subscriber
8 specifying the CFU de-registration feature code, as in:
9 *FC0 + SEND .
12 ANSI-41 foreign mode: The subscriber can specifically erase a previous registration with an
13 appropriate control procedure, per GSM 02.30 [20]. In ANSI-41 foreign mode, if the equivalent GSM
14 feature code (MMI) is manually entered by the user, the mobile station is expected to issue the
15 necessary ANSI-41 feature code to the network.
16 CFU shall be de-registered upon de-authorization or withdrawal.
17 2.2.2.2.5 Activation
18 Mobile stations operating in foreign mode may attempt to perform Activation procedures normally
19 supported in native mode.
20 If the subscriber is authorized for Permanent Activation, CFU shall be activated upon authorization
21 (provision).
22 CFU may be activated upon authorization or registration for Demand Activation authorized
23 subscribers. CFU may be activated upon registration for Variable Registration authorized subscribers.
24 GSM foreign mode: A previously registered forward-to-number may be activated by a Demand

25 Activation authorized subscriber specifying a CFU activation feature code, as in:
26 *FC + SEND .
27 Alternatively, if the mobile station offers menu driven control of activation, the mobile station is
28 expected to generate the equivalent GSM functional signaling.
29 ANSI-41 foreign mode: The MS shall be allowed to activate CFU by a control procedure (e.g., using
30 the MMI command described in GSM 02.30 [20]). In ANSI-41 foreign mode, if the equivalent GSM
33 If the activation is accepted, the system shall indicate success using either GSM or ANSI-41 signaling
34 techniques depending on the mode of operation.
35 The serving system may provide a courtesy call to the forward-to number shortly after this feature is
36 activated permitting the subscriber to verify the validity of the forward-to-number.
1-10
X.S0023
1 2.2.2.2.6 De-Activation
2 GSM foreign mode: CFU may be de-activated by a Demand Activation authorized subscriber
3 specifying the CFB de-activation feature code, as in:
4 *FC0 + SEND .
5 Alternatively, if the mobile station offers menu driven control of de-activation, the mobile station is
7 ANSI-41 foreign mode: The user may deactivate CFU by means of an appropriate control procedure
8 (e.g., as described in GSM 02.30 [20]). In ANSI-41 foreign mode, if the equivalent GSM feature code
9 (MMI) is manually entered by the user, the mobile station is expected to issue the necessary ANSI-41
10 feature code to the network.
11 If the de-activation is accepted, the system shall indicate success using either GSM or ANSI-41
12 signaling techniques depending on the mode of operation. Registered information shall not be
13 erased.
14 CFU shall be de-activated upon de-authorization (withdrawal) or de-registration (erasure).
15 2.2.2.2.7 Invocation
16 The feature treatment is invoked unconditionally when there is an incoming call and CFU is active.

18 When CFU is active, incoming calls for the subscriber shall be forwarded unconditionally to the
19 forward-to number.
20 GSM Foreign Mode: When an incoming call is forwarded unconditionally the forward-to-party shall
21 receive a notification that the call has been forwarded. The calling party may also receive a
22 notification that the call has been forwarded.
23 ANSI-41 foreign mode: When an incoming call is forwarded unconditionally the served mobile
24 subscriber may receive a notification that the call has been forwarded.
25 2.2.2.3.1 Call Detail Record / Charging Requirements
26 For GSM and ANSI-41 based network interoperability, no new or special recording capabilities are
27 needed.
1-11
X.S0023
1 2.2.2.4 Exception Procedures or Unsuccessful Outcome

2
4 If the system cannot accept a registration request, the served mobile subscriber shall receive a
5 notification that registration of call forwarding unconditional was not successful. Possible causes are:
6  service not subscribed to;
7  forward-to number is invalid directory number;
8  use of an operator access prefix;
9  insufficient information;
10  forward-to number is a special service code (e.g., police);
11  forward-to number is the directory number of the mobile subscriber herself.
12 2.2.2.4.2 De-Registration (Erasure)

13 If the subscriber is not authorized for the request, the system shall apply feature denial treatment
14 when de-registration is attempted.
16 If the subscriber is not authorized for the request, or if a forward-to-number is not properly registered,
17 the system shall apply feature denial treatment when activation is attempted.
20 when de-activation is attempted.
22 If the forwarded call cannot be routed to the forward-to-destination, then the call shall be given the
23 appropriate treatment, such as applying the Special Information Tone for intercept to the calling party.
24 Precautions shall be taken to preclude undesirable looping of forwarded numbers within the MSC or
25 between the MSC and other switching centers. If such looping is detected, the call forwarding shall be
26 given the appropriate treatment, such as applying the Special Information Tone for intercept to the
27 calling party.
28 2.2.2.4.6 Exceptions While Roaming
29 None identified.
30 2.2.2.4.7 Exceptions During Intersystem Handoff

31 None identified.
32 2.2.2.5 Alternate Procedures

33 None identified.
34 2.2.2.6 Interactions With Other Features and Services
35 2.2.2.6.1 Advice of charge (AoC)

36 See GSM 02.86 [28].
1-12
X.S0023
1 2.2.2.6.2 Barring of All Outgoing Calls (BAOC)
2 None identified at this time.
3 2.2.2.6.3 Barring of Outgoing International Calls (BOIC)
5 2.2.2.6.4 Barring of Outgoing International Calls except those directed to the Home PLMN
6 (BOIC-exHC)
8 2.2.2.6.5 Barring of All Incoming Calls (BAIC)
10 2.2.2.6.6 Barring of Incoming Calls when Roaming Outside the Home PLMN (BIC-Roam)
12 2.2.2.6.7 Call Delivery (CD)
13 CFU takes precedence over CD. That is, calls arriving when CFU is active are forwarded
14 unconditionally and not given CD treatment.
15 2.2.2.6.8 Call Forwarding—Busy (CFB)
16 CFU takes precedence over CFB. That is, calls arriving when CFU is active shall be forwarded
17 unconditionally and not given CFB treatment
18 2.2.2.6.9 Call Forwarding—Default (CFD)

19 CFU takes precedence over CFD. That is, calls arriving when CFU is active shall be forwarded
20 unconditionally and not given CFD treatment.
21 2.2.2.6.10 Call Forwarding—No Answer / No Reply /Not Reachable (CFNA / CFNRy/CFNRc)
22 CFU takes precedence over CFNA/CFNRy/CFNRc. That is, an incoming call arriving for a subscriber
23 with both CFU and CFNA/CFNRy/CFNRc active shall be forwarded with CFU.
24 2.2.2.6.11 Call Transfer (CT)
25 None identified.
26 2.2.2.6.12 Call Waiting / Call Hold (CW / HOLD)
27 CFU takes precedence over CW. That is, calls arriving when CFU is active shall be forwarded
28 unconditionally and not given CW treatment.
29 2.2.2.6.13 Calling Number / Line Identification Presentation (CNIP / CLIP)
30 When a call has been forwarded and the forward-to user has been provided with the CNIP / CLIP
31 supplementary service, the forward-to user shall receive the number of the original calling user, if this
32 calling user has not subscribed to or invoked the CNIR / CLIR supplementary service.
33 2.2.2.6.14 Calling Number / Line Identification Restriction (CNIR / CLIR)
34 If the calling number indicates presentation restricted, the calling number shall not be presented to
35 the called party or the forward-to-party.
1-13
X.S0023
1 If the called (redirecting) subscriber has CFU active and CNIR is either Permanently Restricted or the
2 default is Presentation Restricted, the redirecting number shall indicate presentation restricted to
3 prevent presentation to the forward-to-party or to the forward-to station.
4 2.2.2.6.15 Calling Name Presentation (CNAP)
5 When a call has been forwarded and the forward-to-party has been provided with the CNAP
6 supplementary service, the forward-to user shall receive the name of the original calling user, if this
7 calling user has not subscribed to or invoked the CNAR or CNIR / CLIR supplementary service.
8 2.2.2.6.16 Calling Name Restriction (CNAR)
9 If the calling name or number indicates presentation restricted, the calling name or number shall not
10 be presented to the called party or the forward-to-party.
11 If the called (redirecting) subscriber has CFU active and CNAR or CNIR is either Permanently
12 Restricted, or the default is Presentation Restricted, the redirecting name shall indicate presentation
13 restricted to prevent presentation to the forward-to-party.
14 2.2.2.6.17 Closed User Group (CUG)

15 See GSM 02.85 [27].
16 2.2.2.6.18 Conference Calling / Multi Party Service (CC / MPTY)
17 None identified.
18 2.2.2.6.19 Do Not Disturb (DND)
20 2.2.2.6.20 Emergency Services (Future)
22 2.2.2.6.21 Flexible Alerting (FA)
24 2.2.2.6.22 Message Waiting Notification (MWN)
25 None identified.
26 2.2.2.6.23 Mobile Access Hunting (MAH)
28 2.2.2.6.24 Password Call Acceptance (PCA)
30 2.2.2.6.25 Preferred Language (PL)
31 None identified.
32 2.2.2.6.26 Priority Access and Channel Assignment (PACA)

34 2.2.2.6.27 Remote Feature Control (RFC)
35 CFU Registration shall be allowed via RFC in ANSI-41 mode, or via functional messaging in GSM
36 mode.
1-14
X.S0023
1 2.2.2.6.28 Selective Call Acceptance (SCA)
3 2.2.2.6.29 Subscriber PIN Access (SPINA)
5 2.2.2.6.30 Subscriber PIN Intercept (SPINI)
6 None identified.
7 2.2.2.6.31 Three-Way Calling / Multi Party Service (3WC / MPTY)

8 None identified.
9 2.2.2.6.32 Voice Message Retrieval (VMR)
10 None identified.
11 2.2.2.6.33 Voice Privacy (VP)
12 None identified.
1-15
X.S0023
1 2.2.3 Call Forwarding - Busy (CFB)

2

4 Call Forwarding—Busy (CFB) permits a called subscriber to have the system send incoming calls
5 addressed to the called subscriber’s Directory Number to another Directory Number (forward-to
6 number) or to the called subscriber’s designated voice mail box, when the subscriber is engaged in a
7 call or service. CFB does not impact a subscriber’s ability to originate calls.

9 CFB is applicable to voice telecommunications services.

11
13 CFB may be generally available or may be provided after pre-arrangement with the service provider.
14 The authorization (provision) may have the subscription options. These options are defined in either
15 GSM 02.82 [24] (i.e., GSM native mode subscribers) or ANSI-664 [15] (e.g., ANSI-41 native mode
16 subscribers). Authorization or Provisioning may occur while operating in foreign mode.
18 CFB may be withdrawn at the subscriber’s request or for administrative reasons. De-authorization or
19 withdrawal may occur while operating in foreign mode.
22 authorization (provision).
23 The CFB forward-to number may be registered by the service provider upon authorization (provision)
24 for Variable Registration subscribers. Mobile stations operating in foreign mode may attempt to
25 perform registration procedures normally supported in native mode.

27 subscriber specifying the CFB registration feature code and a forward-to number termination address
28 as in:
32 ANSI-41 foreign mode: Registration may take place with an appropriate control procedure by the
33 subscriber, per GSM 02.30 [20]. In ANSI-41 foreign mode, if the equivalent GSM mode feature code
34 (MMI) is manually entered by the user, the mobile station is expected to issue the relevant ANSI-41
35 feature code entry.
1-16
X.S0023
6 Forward-to numbers may be de-registered upon de-activation (at the home service provider option).
9 GSM foreign mode: CFB may be de-registered by a Variable Registration authorized subscriber
10 specifying the CFB de-registration feature code, as in:
11 *FC0 + SEND .
13 expected to generate the GSM functional signaling towards the network.
16 mode feature code is manually entered by the user, the mobile station is expected to issue the
18 CFB shall be de-registered upon de-authorization or withdrawal.
22 If the subscriber is authorized for Permanent Activation, CFB shall be activated upon authorization
23 (provision).
24 CFB may be activated upon registration for Demand Activation authorized subscribers. CFB may be
25 activated upon registration for Variable Registration authorized subscribers.
26 GSM foreign mode: A previously registered forward-to number may be activated by a Demand
27 Activation authorized subscriber specifying a CFB activation feature code, as in:
28 *FC + SEND .
31 ANSI-41 foreign mode: The MS shall be allowed to activate CFB by for example using the MMI
32 command described in GSM 02.30 [20]. In ANSI-41 foreign mode, if the equivalent GSM mode
35 If the activation is accepted, the system shall indicate success with using either GSM or ANSI-41
38 activated permitting the subscriber to verify the validity of the forward-to number.
1-17
X.S0023
2 GSM foreign mode: CFB may be de-activated by a Demand Activation authorized subscriber
3 specifying the CFB de-activation feature code, as in:
4 *FC0 + SEND .
7 ANSI-41 foreign mode: The user may deactivate CFB by means of an appropriate control procedure
8 (e.g., as described in GSM 02.30 [20]). In ANSI-41 foreign mode, if the equivalent GSM mode feature
9 code (MMI) is manually entered by the user, the mobile station is expected to issue the necessary
10 ANSI-41 feature code to the network.
11 If the de-activation is accepted, the system shall indicate success with using either GSM or ANSI-41
13 erased.
14 CFB shall be de-activated upon de-authorization (withdrawal) or de-registration (erasure).
16 The feature treatment is invoked when there is an incoming call while the subscriber is considered to
17 be busy (i.e., in any state other than the idle state) and CFB is active.

19 When CFB is active, incoming calls for the subscriber shall be forwarded to the forward-to number
20 when the subscriber is considered to be busy.
21 GSM Foreign Mode: When an incoming call is forwarded on mobile subscriber busy with the
22 condition network determined user busy (NDUB) the forward-to-party shall receive a notification that
23 the call has been forwarded. The calling party may also receive a notification that the call has been
24 forwarded.
25 ANSI-41 foreign mode: When an incoming call is forwarded due to a busy condition the served
26 mobile subscriber may receive a notification that the call has been forwarded.
29 needed.

31
34 notification that call forwarding on mobile subscriber busy registration was not successful. Possible
35 causes are:
1-18
X.S0023

11 If the subscriber is not authorized for the request, or if a forward-to number is not properly registered,
17 If the forwarded call cannot be routed to the forward-to destination, then the call shall be given the
22 calling party.
24 None identified.
26 None identified.

28 None identified.

30

32 See GSM 02.86 [28].
1-19
X.S0023
4 (BOIC-exHC)

11 CD affects CFB. That is, if CD is inactive while the subscriber is roaming, the subscriber is considered
12 to be inaccessible. Even if the subscriber has CFB active, incoming calls shall be given the subscriber
13 inaccessible treatment.
14 If CD is active and registered for a roaming subscriber, or if the subscriber is at home, CFB works
15 normally.
16 If the call is delivered to the subscriber, the subscriber is busy, and the subscriber has CFB active,
17 the call shall be diverted to the CFB forward-to number.
19 Not applicable.
21 CFB takes precedence over CFD. That is, calls arriving to a busy subscriber with CFB and CFD
22 active shall be forwarded by CFB and not given CFD treatment.
23 2.2.3.6.10 Call Forwarding—No Answer / No Reply (CFNA / CFNRy)
24 CFB is mutually exclusive with CFNA / CFNRy. That is, calls arriving to a busy subscriber with CFB
25 and CFNA / CFNRy active shall be forwarded by CFB and not given CFNA / CFNRy treatment.
26 2.2.3.6.11 Call Forwarding—Not Reachable (CFNRc)

27 CFB is mutually exclusive with CFNRc. That is, calls arriving to a busy subscriber with CFB and
28 CFNRc active shall be forwarded by CFB and not given CFNRc treatment.
29 2.2.3.6.12 Call Forwarding—Unconditional (CFU)

30 CFU takes precedence over CFB. That is, calls arriving when CFU is active shall be forwarded
31 unconditionally and not given CFB treatment.
33 None identified.

35 CW is invoked before CFB. If a call arrives for a busy subscriber able to receive a second call, the
36 called subscriber has both CW and CFB active, and no call is already waiting to be answered; the call
37 is presented to the subscriber with CW notification. If the CW call is not accepted, CFB is not invoked.
1-20
X.S0023
1 If a call arrives for a busy subscriber, the called subscriber has both CW and CFB active, and if the
2 called subscriber is unable to receive a second call or has a call waiting to be answered; the call shall
3 be forwarded immediately by CFB.
10 the called party, the called station, the forward-to party, or the forward-to station.
11 If the called (redirecting) subscriber has CFB invoked and either the CNIR mode is Permanently
12 Restricted or the CNIR Default is Presentation Restricted, the redirecting number shall indicate
13 presentation restricted to prevent presentation to the forward-to party or to the forward-to station.

15 When a call has been forwarded and the forward-to user has been provided with the CNAP
20 be presented to the called party, the called station, the forward-to party, or the forward-to station.
21 If the called (redirecting) subscriber has CFB invoked and either the CNAR or CNIR mode is
22 Permanently Restricted, or the CNAR or CNIR Default is Presentation Restricted, the redirecting
23 name shall indicate presentation restricted to prevent presentation to the forward-to party or to the
24 forward-to station.
26 See GSM 02.85 [27].
28 None identified.
31 2.2.3.6.22 Emergency Services

36 None identified.

1-21
X.S0023
4 None identified.

8 CFB Registration shall be allowed via RFC in ANSI-41 mode, or via functional messaging in GSM
9 mode.

15 None identified.
17 None identified.
19 None identified.
21 None identified.
1-22
X.S0023
1 2.2.4 Call Forwarding No Answer/ No Reply/Not Reachable

2 (CFNA/CFNRy/CFNRc)
3

5 Call Forwarding—No Answer (CFNA) permits a called subscriber to have the system send incoming
6 calls addressed to the called subscriber’s Directory Number to another Directory Number (forward-to
7 number) or to the called subscriber’s designated voice mail box, when the subscriber fails to answer,
8 or is otherwise inaccessible (including no paging response, the subscriber’s location is not known the
9 subscriber is reported as inactive, Call Delivery not active for a roaming subscriber, Do Not Disturb
10 active, etc.).
11 Call Forwarding No Reply (CFNRy) permits a called subscriber to have the system send all incoming
12 calls, or just those associated with a specific Basic service group, addressed to the called mobile
13 subscriber's directory number and which meet no reply to another directory number.
14 Call Forwarding Not Reachable (CFNRc) permits a called subscriber to have the system send all
15 incoming calls, or just those associated with a specific Basic service group, addressed to the called
16 mobile subscriber's directory number and which meet not reachable to another directory number.
18 CFNA/CFNRy/CFNRc is applicable to voice telecommunication services.

20
22 CFNA/CFNRy/CFNRc may be generally available or may be provided after pre-arrangement with the
23 service provider. The authorization (provision) may have subscription options. These options are
24 defined in either GSM 02.82 [24] (i.e., GSM native mode subscribers) or ANSI-664 [15] (e.g., ANSI-41
25 TDMA or CDMA native mode subscribers). Authorization or Provisioning may occur while operating in
26 foreign mode.
28 CFNA/CFNRy/CFNRc may be withdrawn by the service provider, at the subscriber’s request, or for
29 administrative reasons. De-authorization or withdrawal may occur while operating in foreign mode.
1-23
X.S0023

2 subscriber specifying the CFNA registration feature code and a forward-to number termination
3 address as in:
4 *FC + termination address + SEND
7 ANSI-41 foreign mode: Registration can take place with an appropriate control procedure by the
8 subscriber, per GSM 02.30 [20]. In ANSI-41 foreign mode, if the equivalent GSM feature code (MMI)
9 is manually entered by the user, the mobile station is expected to issue the relevant ANSI-41 feature
10 code entry.
22 GSM foreign mode: CFNA may be de-registered by a Variable Registration authorized subscriber
23 specifying the CFNA de-registration feature code, as in:
24 *FC0 + SEND .
31 CFNA/CFNRy/CFNRc shall be de-registered upon de-authorization or withdrawal.
35 If the subscriber is authorized for Permanent Activation, CFNA shall be activated upon authorization
36 (provision).
37 CFNA may be activated upon authorization or registration for Demand Activation authorized
38 subscribers. CFNA may be activated upon registration for Variable Registration authorized
39 subscribers.
1-24
X.S0023

2 Activation authorized subscriber specifying a CFNA activation feature code, as in:
3 *FC + SEND .
6 ANSI-41 foreign mode: The MS shall be allowed to activate CFNRy/CFNRc by using an appropriate
7 control procedure (e.g. using the MMI command described in GSM 02.30 [20]). In ANSI-41 foreign
8 mode, if the equivalent GSM feature code (MMI) is manually entered by the user, the mobile station is
9 expected to issue the necessary ANSI-41 feature code to the network.
10 If the activation is accepted, the system shall indicate success using either GSM or ANSI-41 signaling
11 techniques depending on the mode of operation.
15 GSM foreign mode: CFNA may be de-activated by a Demand Activation authorized subscriber
16 specifying the CFNA de-activation feature code, as in:
17 *FC0 + SEND .
20 ANSI-41 foreign mode: The user may deactivate CFNRy/CFNRc by means of an appropriate control
21 procedure (e.g., as described in GSM 02.30 [20]). In ANSI-41 foreign mode, if the equivalent GSM
24 If the de-activation is accepted, the system shall indicate success using either GSM or ANSI-41
26 erased.
27 CFNA/CFNRy/CFNRc shall be de-activated upon de-authorization (withdrawal) or de-registration

28 (erasure).
30 The feature treatment is invoked when there is an incoming call and either CFNA, CFNRy or CFNRc
31 is active and the necessary conditions have been met – see GSM 02.82 [24] and ANSI-664 [15].

33 When CFNA/CFNRy/CFNRc is active, incoming calls for the subscriber shall be forwarded due to not
34 reachable (e.g., no response to paging) or no reply to the forward-to number.
35 GSM Foreign Mode: When an incoming call is forwarded due to no reply or not reachable, the
36 forward-to-party shall receive a notification that the call has been forwarded. The calling party may
37 also receive a notification that the call has been forwarded.
38 ANSI-41 foreign mode: When an incoming call is forwarded due to no answer the served mobile
39 subscriber may receive a notification that the call has been forwarded.
1-25
X.S0023
3 needed.

5
8 notification that registration of CFNA/CFNRy/CFNRc was not successful. Possible causes are:
30 calling party.

32 None identified.
34 None identified.

36 None identified.
1-26
X.S0023

2
4 See GSM 02.86 [28].
10 (BOIC-exHC)
17 CD affects CFNA. That is, if CD is inactive while the subscriber is roaming, the subscriber is
18 considered to be inaccessible. If the subscriber has CFNA active, incoming calls shall be diverted to
19 the CFNA forward-to number.
20 If CD is active and registered for a roaming subscriber, or if the subscriber is at home, CFNA works
21 normally.
22 If the call is presented to the subscriber, the call is not answered, and the subscriber has CFNA
23 active, the call shall be diverted to the CFNA forward-to number.
25 CFB is mutually exclusive with CFNA/CFNRy/CFNRc. That is, calls arriving to a busy subscriber with
26 CFB and CFNA/CFNRy/CFNRc active shall be forwarded by CFB and not given
27 CFNA/CFNRy/CFNRc treatment.
29 CFNA takes precedence over CFD. That is, an incoming call to an inaccessible or non-answering
30 subscriber with both CFNA and CFD active shall be forwarded using CFNA.
32 None identified.
1-27
X.S0023
2 CW is invoked before CFNA/CFNRy. If a call arrives for a busy subscriber able to receive a second
3 call, the called subscriber has both CW and CFNA/CFNRy active, and no call is waiting to be
4 answered; the call is presented to the subscriber with CW notification. If the call is not answered
5 within a period of time after applying the first CW notification, it shall be given no answer treatment.
6 CFNRc is invoked before CW.

10 calling party has not subscribed to or invoked the CNIR / CLIR supplementary service.
14 If the called (redirecting) subscriber has CFNA/CFNRy/CFNRc active and CNIR is either Permanently
15 Restricted or the default is Presentation Restricted, the redirecting number shall indicate presentation
16 restricted to prevent presentation to the forward-to-party or to the forward-to station.

24 If the called (redirecting) subscriber has CFNA/CFNRy/CFNRc active and CNAR or CNIR is either
25 Permanently Restricted, or the default is Presentation Restricted, the redirecting name shall indicate
26 presentation restricted to prevent presentation to the forward-to-party.
28 See GSM 02.85 [27].
30 None identified.


38 None identified.
1-28
X.S0023
6 None identified.

10 CFNA/CFNRy/CFNRc Registration shall be allowed via RFC in ANSI-41 mode, or via functional
11 messaging in GSM mode.

17 None identified.
19 None identified.
21 None identified.
23 None identified.
1-29
X.S0023
1 2.2.5 Call Forwarding Default

2

4 Call Forwarding—Default (CFD) permits a called subscriber to send incoming calls addressed to the
5 called subscriber’s Directory Number to the subscriber’s designated voice mail box or to another
6 Directory Number (forward-to number), when the subscriber is engaged in a call, does not respond to
7 paging, does not answer the call within a specified period after being alerted or is otherwise
8 inaccessible (including no paging response, the subscriber’s location is not known, the subscriber is
9 reported as inactive, Call Delivery not active for a roaming subscriber, Do Not Disturb active, etc.).
11 CFD is applicable to voice telecommunication services.

13
15 CFD may be generally available or may be provided after pre-arrangement with the service provider.
16 The authorization (provision) may have subscription options. These options are defined in
17 ANSI-664 [15] (e.g., ANSI-41 TDMA or CDMA native mode subscribers). Authorization or
18 Provisioning may occur while operating in foreign mode.
20 CFD may be withdrawn by the service provider, at the subscriber’s request, or for administrative
21 reasons. De-authorization or withdrawal may occur while operating in foreign mode.

29 subscriber specifying the CFD registration feature code and a forward-to number termination address
30 as in:
34 If the registration is accepted, the system shall indicate success using either GSM signaling
35 techniques.
37 Mobile stations operating in foreign mode, may attempt to perform De-Registration or Erasure
1-30
X.S0023
4 GSM foreign mode: CFD may be de-registered by a Variable Registration authorized subscriber
5 specifying the CFD de-registration feature code, as in:
6 *FC0 + SEND .
9 CFD shall be de-registered upon de-authorization or withdrawal.
13 If the subscriber is authorized for Permanent Activation, CFD shall be activated upon authorization
14 (provision).
15 CFD may be activated upon authorization or registration for Demand Activation authorized
16 subscribers. CFD may be activated upon registration for Variable Registration authorized subscribers.

18 Activation authorized subscriber specifying a CFD activation feature code, as in:
19 *FC + SEND .
22 If the activation is accepted, the system shall indicate success using GSM or ANSI-41 signaling
23 techniques.
27 GSM foreign mode: CFD may be de-activated by a Demand Activation authorized subscriber
28 specifying the CFD de-activation feature code, as in:
29 *FC0 + SEND .
32 If the de-activation is accepted, the system shall indicate success using either GSM signaling
33 techniques. Registered information shall not be erased.
34 CFD shall be de-activated upon de-authorization (withdrawal) or de-registration (erasure).
36 The feature treatment is invoked when there is an incoming call, CFD is active and the necessary
37 conditions have been met – See ANSI-664 [15].
1-31
X.S0023

2 When CFD is active, incoming calls for the subscriber shall be forwarded due to not reachable (e.g.,
3 no response to paging), no reply, or busy to the forward-to number.
4 GSM Foreign Mode: When an incoming call is forwarded due to CFD, the forward-to-party shall
5 receive a notification that the call has been forwarded. The calling party may also receive a
6 notification that the call has been forwarded.
9 needed.

11
14 notification that registration of CFD was not successful. Possible causes are:
36 calling party.
1-32
X.S0023
2 None identified.
4 None identified.

6 None identified.
9 CD affects CFD. That is, if CD is inactive while the subscriber is roaming, the subscriber is
10 considered to be inaccessible. If the subscriber has CFD active, incoming calls shall be diverted to
11 the CFD forward-to number.
13 CFB takes precedence over CFD. That is, calls arriving to a busy subscriber with CFB and CFD
14 active shall be forwarded by CFB and not given CFD treatment.
16 None identified.
18 CW is invoked before CFD. If a call arrives for a busy subscriber able to receive a second call, the
19 called subscriber has both CW and CFD active, and no call is waiting to be answered; the call is
20 presented to the subscriber with CW notification. If the call is not answered within a period of time
21 after applying the first CW notification, it shall be given no answer treatment.


29 If the called (redirecting) subscriber has CFD active and CNIR is either Permanently Restricted or the
30 default is Presentation Restricted, the redirecting number shall indicate presentation restricted to
31 prevent presentation to the forward-to-party or to the forward-to station.
1-33
X.S0023
4 If the called (redirecting) subscriber has CFD active and CNAR or CNIR is either Permanently
5 Restricted, or the default is Presentation Restricted, the redirecting name shall indicate presentation
6 restricted to prevent presentation to the forward-to-party.

8 See GSM 02.85 [27].
10 None identified.
18 None identified.
24 None identified.
28 CFD Registration shall be allowed via RFC in ANSI-41 mode, or via functional messaging in GSM
29 mode.

1-34
X.S0023
2 None identified.
4 None identified.
6 None identified.

8 None identified.
1-35
X.S0023
1 2.3 Optimal Routing for Late Call Forwarding

2

4 Optimal Routing for Late Call Forwarding is a network feature which enables calls for a mobile
5 subscriber who is not available to be routed from the called party HPLMN directly to a specified
6 forward-to destination.
7 In GSM Optimal Routing for Late Call Forwarding by the HPLMN is a subset of the capabilities
8 provided in GSM Support for Optimal Routing (SOR) Phase I per GSM 02.79 [22]. With SOR, the
9 interrogating PLMN (IPLMN) decides whether or not to optimize routing by taking into account
10 information provided by the called party HPLMN. The HPLMN can decide, on a call-by-call basis,
11 whether or not to allow OR.
12 GSM SOR provides additional capabilities for OR under other conditions and by systems other than
13 the HPLMN, which are outside the scope of this feature.
14 In ANSI-41 networks Optimal Routing for Late Call Forwarding can be provided automatically for
15 every call by ANSI-41 call delivery procedures, and is not considered a supplementary service.
16 OR is a network feature, and therefore is transparent to the subscriber, except possibly in charging.
17 There is no subscriber initiated registration, activation, or invocation.

19 Optimal Routing for Late Call Forwarding is applicable to all circuit switched Telecommunications
20 Service.
21 2.3.2 Normal Procedures with Successful Outcome

22 Optimal Routing for Late Call Forwarding refers to the scenario in which party A (mobile or wireline)
23 attempts to call mobile subscriber B who may have calls forwarded to party C (mobile or wireline). In
24 GSM, the consideration of whether or not to invoke OR depends upon the relative locations HPLMN-
25 B, VPLMN-B, and HPLMN-C. Both the HPLMN-B and the VPLMN-B must be capable of supporting
26 Optimal Routing for Late Call Forwarding. The VPLMN-B determines if Optimal Routing for Late Call
27 Forwarding is feasible, but the HPLMN-B controls the invocation of this feature.
28 Using GSM terminogy, the interrogating PLMN (IPLMN) in the following scenario is HPLMN-B.
29 Party A originates a call to party B. A may be a fixed or mobile subscriber, and A may be in any
30 country.
31 HPLMN- B acts as the interrogating PLMN, and launches a query to the HLR to determine the
32 location and status of B.
33 If the response from the HLR indicates that B is active and reachable, then HPLMN-B proceeds to
34 initiate call setup to VPLMN-B.
35 Upon receipt of call setup request from HPLMN-B, VPLMN-B proceeds to page B. If call cannot be
36 completed successfully (e.g., Busy, No Page Response or No Answer), and B has call forwarding
37 active, then HPLMN-B proceeds to initiate call forwarding to the forward-to number. Call setup to the
38 forward to party is done directly from HPLMN-B rather than through VPLMN-B. Without optimal
39 routing in GSM call leg would have been setup initially to VPLMN-B, and from there to C.
1-36
X.S0023
1 2.3.2.1 Call Detail Record

3 needed.

5 2.3.3.1 Non-support for OR in the called party HPLMN
6 If the HPLMN of the called party is a GSM system which does not support OR, Optimal Routing for
7 Late Call Forwarding cannot be invoked.
8 2.3.3.2 Non-support for OR in the called party VPLMN

9 If a subscriber whose HPLMN is an ANSI-41 or GSM system that supports OR registers in a VPLMN
10 with a GSM system that does not support OR, then Optimal Routing for Late Call Forwarding cannot
11 be invoked.
12 2.3.3.3 Calls to special mobile network numbers

13 If the called number is a special mobile network number of the HPLMN and the HPLMN is a GSM
14 system, then the HPLMN has to guarantee that the call terminates at the correct destination. This can
15 be achieved by denying OR for this call or by sending an appropriate error cause, or by implementing
16 special handling.
17 2.3.3.4 Exceptions while Roaming

18 None identified.
19 2.3.3.5 Exceptions during Intersystem Handoff

20 None identified.

22 None identified.
23 2.3.5 Interactions with Other Features and Services

24 2.3.5.1 Advice of Charge
25 Depending on the particular call scenario, AoC may not work properly. For example, the subscriber
26 may be charged a rate that is associated with non-optimal routing.

28 None identified.

30 None identified.

32 BAIC takes precedence over Optimal Routing for Late Call Forwarding, and all incoming calls are
33 given denial treatment.
34 Barring of Incoming Calls when Roaming Outside the Home PLMN Country (BIC-Roam)
35 No impact.
1-37
X.S0023
1 2.3.5.5 Call Forwarding Busy (CFB)

2 The interaction between Optimal Routing for Late Call Forwarding and CFB is as described in 2.3.1
3 above. Optimal Routing for Late Call Forwarding does not impact the forwarded number or the
4 ultimate call delivery to the forwarded party – only intermediate routing.
5 2.3.5.6 Call Forwarding Default (CFD)

6 The interaction between Optimal Routing for Late Call Forwarding and CFD is as described in 2.3.1
7 above. Optimal Routing for Late Call Forwarding does not impact the forwarded number or the
8 ultimate call delivery to the forwarded party – only intermediate routing.
9 2.3.5.7 Call Forwarding Busy No Answer / No Reply (CFNA)

10 The interaction between Optimal Routing for Late Call Forwarding and CFNA is as described in 2.3.1.
11 Optimal Routing for Late Call Forwarding does not impact the forwarded number or the ultimate call
12 delivery to the forwarded party – only intermediate routing.

14 There is no interaction between Optimal Routing for Late Call Forwarding and CFU since CFU is
15 invoked in the called party HPLMN before call setup to the serving system is initiated. (ANSI-41: it
16 depends on when paging occurs!).
17 2.3.5.9 Call Forwarding Unconditional (CFU)

18 There is no interaction between Optimal Routing for Late Call Forwarding and CFU since CFU is
19 invoked in the called party HPLMN before call setup to the serving system is initiated.

21 None identified.

23 None identified.

25 None identified.

27 None identified.

29 None identified.

31 None identified.

33 None identified.

35 Same as CFU.
36 2.3.5.18 Emergency Services

37 None identified.
1-38
X.S0023
1 2.3.5.19 Law Enforcement or CALEA

2 None identified.

4 None identified.

6 None identified.

8 Applicable to ANSI-41 networks only. None identified.

10 None identified.



16 Applicable to ANSI-41 networks only. Callers that are not able to provide the correct password are
17 given denial treatment. Calls that are allowed may be subjected to OR treatment.



23 None identified.

25 None identified.
26 2.3.5.31 3-Way Calls or Conference Calls

27 None identified.
28
1-39
X.S0023
1 2.4 Call Waiting (CW)

2

4 Call Waiting (CW) provides notification to a controlling subscriber of an incoming call while the
5 subscriber’s call is in the 2-way state. Subsequently, the controlling subscriber can either answer or
6 ignore the incoming call. If the controlling subscriber answers the second call, it may alternate
7 between the two calls.
8 This service operates when the traffic channel at the controlling subscriber is not available and is
9 engaged in an active or held call. When a third party attempts to connect to that termination, the
10 controlling subscriber is given an appropriate indication of the waiting call. The maximum number of
11 waiting calls at one time per mobile access is one. In ANSI-41 mode, this means that no further calls
12 are offered to the subscriber while a call is waiting. In GSM mode, another call can be offered to the
13 subscriber while a call is waiting, but only one call may be waiting at any time.

15 Call Waiting is applicable to circuit switched voice telecommunications services.
16

18

20 No new authorization procedures are needed for either GSM or ANSI-41 foreign mode operation of
21 call waiting. The following describes authorization procedures for both GSM and ANSI-41 native
22 modes.
23 CW may be generally available or may be provided after pre-arrangement with the service provider.
24 GSM native subscriber: This supplementary service is provisioned for all Basic services subscribed
25 to and to which it is applicable, i.e. not provisioned to any subset of these BS.
26 ANSI-41 native subscriber: CW may be authorized for the following options:
27 Table 1: CW Subscription Options
Subscription Options Values

Temporary Cancellation Demand. The subscriber is authorized to
cancel or de-activate CW for a single call.
Permanent. CW may not be canceled or
de-activated for a single call.
Activation Demand. The subscriber is authorized to
control the activation and de-activation of
CW.
Permanent. CW is active while authorized
(unless canceled).
1-40
X.S0023

3 CW may be withdrawn at the subscriber’s request or for administrative reasons.
5 CW has no registration.

7 CW has no de-registration.
9 In both GSM and ANSI-41 foreign modes, the subscriber shall be provided with menu selections by
10 the mobile station to allow him/or her to activate the call waiting feature. Menu selections shall also be
11 available to the subscriber while in native mode as well. In addition, the user may also be able to
12 activate call waiting (depending on individual service provider’s preference) through the use of the
13 keypad, as follows:
14 ANSI-41 native and foreign modes:
15 CW may be activated upon authorization.
16 CW may be activated by a Demand Activation authorized subscriber specifying a CW activation

17 feature code, as in:
18 *FC + SEND .
19 If the activation is accepted, the system shall indicate success with feature confirmation treatment.
20 GSM native and foreign modes: This supplementary service shall be activated either collectively
21 for all applicable Basic Services or on a Basic Service group basis by the subscriber using a control
22 procedure, as specified in GSM 02.30 [20], or by the service provider. The controlling subscriber shall
23 be informed by the network of the success or otherwise of her action.
25 In both GSM and ANSI-41 foreign modes, the subscriber shall be provided with menu selections by
26 the mobile station to allow him/or her to de-activate the call waiting feature. Menu selections shall
27 also be available to the subscriber while in native mode as well. In addition, the user may also be able
28 to de-activate call waiting (depending on individual service provider’s preference) through the use of
29 the keypad, as follows:
30 ANSI-41 native and foreign mode:
31 CW shall be de-activated upon de-authorization.
32 CW Demand De-Activation:
33 CW may be de-activated by a Demand Activation authorized subscriber specifying a CW

34 de-activation feature code, as in:
35 *FC0 + SEND .
36 If the de-activation is accepted, the system shall indicate success with feature confirmation treatment.
37 Temporary Cancellation During a Call (ANSI-41 Native Mode Only):
1-41
X.S0023
1 CW may be canceled during a single call by a Demand Cancellation authorized subscriber issuing a
2 flash request and then specifying a CCW feature code, as in:
3 *FC0 + SEND .
4 If the cancellation is accepted, the system may indicate success with feature confirmation treatment
5 and then reconnect the call. At the completion of the call, CW shall resume the activation state prior
6 to using the cancel CW feature code.
7 Temporary Cancellation With a Call Setup Request (ANSI-41 Native Mode Only):
8 CW may be canceled for a single call concurrently with a call request by a Demand Cancellation
9 authorized subscriber specifying a CCW feature code and a termination address, as in:
10 *FC0 + # + termination address + SEND .
11 Alternatively:
12 *FC + termination address + SEND
13 is possible, if a fixed length Temporary Cancellation feature code is distinct from the de-activation
14 feature code.
15 If the cancellation is accepted, the system may indicate success with feature confirmation treatment
16 and then the call is allowed to proceed toward the termination address. At the completion of the call,
17 CW shall resume the activation state prior to using the cancel CW feature code.
18 GSM native and foreign mode: The service shall be deactivated either collectively for all applicable
19 Basic Services or on a Basic Service group basis by the subscriber using a control procedure, as
20 specified in GSM 02.30 [20], or by the service provider. The controlling subscriber shall be informed
21 by the network of the success or otherwise of her action.
23 CW is invoked when a incoming call attempt arrives for a subscriber who is already engaged in
24 conversation on a prior call, who does not have another call waiting, and who has CW active.
25 There are functions or actions which exist on GSM (in GSM 02.83 [25]), but do not exist in ANSI-41,
26 and vice versa (see charts below). In order to achieve a seamless user Interface when roaming, it
27 would be better to either provide the menu selections as it is in a GSM handset, or some other
28 mechanism that can achieve the same goal.
1-42
X.S0023
1 2.4.3 Normal Operation with Successful Outcome

2 Menu selections shall be provided by the mobile station, in both foreign and native modes, to allow
3 the subscriber to control the operation of calls involving call waiting. Because, in general, GSM
4 networks provide more capabilities related to call waiting operation, the menu-driven procedures may
5 be different for a given subscriber depending on whether the serving network is GSM or ANSI-41. In
6 addition to the use of menu selections, a subscriber may use the keypad entries (shown in the tables
7 below) to control the operation of calls involving call waiting. Note that the subscriber would need to
8 use different set of keypad entries depending on whether the serving network is GSM or ANSI-41,
9 and thus the use of the shown keypad entries to control the operation of the calls is not encouraged.
10 In general, the menu-driven approach would be preferred instead.
11 The following tables describe the call party actions and system reactions for CW on GSM and
12 ANSI-41.
13 Table 2: 2-Way State for Call Waiting
State: 2-way Condition The controlling subscriber is alerting the

other party, or the controlling subscriber
is in a two-way conversation with the
other party.
GSM Called Party ANSI-41 Called Party System Reaction
Action Action
A call arrives from a A call arrives from a CW notification is applied to the

calling party for a calling party for a controlling subscriber. The CW
controlling subscriber controlling notification is repeated once if the
in a two-way subscriber in a waiting call is not answered.
conversation and with two-way Audible ringing is applied to the
CW active. conversation and calling party until the call is
with CW active. answered or given no answer
treatment. Go to the 2-way CW
notification state.
14
1-43
X.S0023
1 The CW notification may be an audible Call Waiting Tone injected into the voice path, a message on
2 the alphanumeric display, or both.
3 Table 3: 2-Way Notification State for Call Waiting
State: 2-way Condition The controlling subscriber is in a

notification two-way conversation with the other
party and call waiting notification is
applied.
GSM Called Party ANSI-41 Called Party System Reaction
Action Action
The controlling The controlling Remove the call waiting
subscriber signals subscriber signals a notification. Place the other
a flash request by flash request by party on hold. Connect the
pressing 2 + pressing the SEND controlling subscriber and
SEND key . the calling party. Go to the
key without digits.
2-way CW state.
The controlling The controlling Release the other party.
subscriber subscriber requests Remove the call waiting
requests a a disconnect by notification. Apply the
disconnect by pressing the END alerting to the controlling
pressing the END subscriber for the calling
key.
party. Go to the Alerting
key.
state.
The controlling No equivalent Release the other party.
subscriber signals function. Remove the call waiting
a flash request by notification. Connect the
pressing 1 + controlling subscriber and
SEND key . the calling party. Go to the
2-way CW notification state.
The controlling No equivalent Remove the call waiting
subscriber signals function. notification. Place the UDUB
a flash request by condition to the calling party
pressing 0 + for busying treatment. Go to
SEND key . the 2-way CW notification
state.
4
1-44
X.S0023
1 Table 4: 2-Way CW State for Call Waiting
State: 2-way CW Condition The controlling subscriber is in a

two-way conversation with the other
party and a third party is on hold.
GSM Called Party ANSI-41 Called party System Reaction
Action Action
The controlling The controlling Place the other party on

subscriber signals a subscriber signals a hold. Connect the
flash request by flash request by controlling subscriber
pressing 2 + SEND pressing the SEND and the third party.
Remain in the 2-way CW
key. key without digits.
state.
No equivalent The controlling Release the other party.
function. subscriber requests Apply the recall distinctive
a disconnect by alerting for the third party
pressing the END to recall the controlling
subscriber. Optionally
key.
apply audible alerting to
the held party. Go to the
Alerting state.
The controlling No equivalent Release the other party.
subscriber signals a function. Connect the controlling
flash request by subscriber and the held
pressing 1+ SEND party. Go to the 2-way
CW notification state.
key.
The controlling No equivalent The held party is
subscriber signals a function. released. Remain in the
flash request by 2-way CW state.
pressing 0+ SEND
key.
The controlling No equivalent Release all calls.
subscriber requests function.
a disconnect by
pressing the END
key.
2
3 2.4.3.1 Call Detail Record / Charging Requirements

5 needed.
1-45
X.S0023
1 2.4.3.2 Interrogation
2 In foreign modes, the interrogation procedure is not supported.
3 GSM native mode
4 The controlling subscriber may interrogate the network by the use of a control procedure, as specified
5 in GSM 02.30 [20]. The network shall respond with an appropriate indication telling the subscriber
6 whether the service is supported in this network and, if so, provide a list of all Basic Service groups to
7 which the Call waiting supplementary service is active.

9
11 None identified.

13 None identified.
16 when activation is attempted.
18 Demand De-Activation: If the subscriber is not authorized for the request, the system shall apply
19 feature denial treatment when de-activation is attempted.
20 Temporary Cancellation (ANSI-41 native mode only): If the subscriber is not authorized for the
21 request, the system shall apply feature denial treatment when de-activation is attempted.
22 Temporary Cancellation With a Call Setup Request (ANSI-41 native mode only): If the
23 subscriber is not authorized for a Temporary Cancellation request made concurrently with a call setup
24 request, the system shall apply feature denial treatment and the call setup shall be denied.
26 If the controlling subscriber is not authorized, if the controlling subscriber is alerting the other party, or
27 if resources are not available; give the calling party busy treatment. Remain in the 2-way state.

29 None identified.

31 None identified.

33 None identified.
1-46
X.S0023

2

4 None identified.

6 None identified.

8 None identified.
10 (BOIC-exHC)
11 None identified.

13 None identified.
15 None identified.

17 No interactions between CD and CW in foreign mode.
18 While the subscriber is in native mode, CD may affect CW. That is, if CD is inactive while the
19 subscriber is roaming, the subscriber is considered to be inaccessible. Even if the subscriber has CW
20 active, incoming calls shall be given the subscriber inaccessible treatment.
21 If CD is active and registered for a roaming subscriber, or if the subscriber is at home, CW works
22 normally.

24 CW is invoked before CFB. If a call arrives for a busy subscriber able to receive a second call, the
25 called subscriber has both CW and CFB active, and no call is already waiting to be answered; the call
26 is presented to the subscriber with CW notification. If the CW call is not accepted, CFB is not invoked.
27 If a call arrives for a busy subscriber, the called subscriber has both CW and CFB active, and if the
29 be forwarded immediately by CFB.

31 CW is invoked before CFD. If a call arrives for a busy subscriber able to receive a second call, the
32 called subscriber has both CW and CFD active, and no call is waiting to be answered; the call is
35 If a call arrives for a busy subscriber, the called subscriber has both CW and CFD active, and if the
37 be forwarded immediately by CFD.
1-47
X.S0023

2 CW is invoked before CFNA. If a call arrives for a busy subscriber able to receive a second call, the
3 called subscriber has both CW and CFNA active, and no call is waiting to be answered; the call is
6 If a call arrives for a busy subscriber, the called subscriber has both CW and CFNA active, and if the
8 be given busy treatment.

10 None identified.

12 CFU takes precedence over CW. That is, calls arriving when CFU is active are forwarded
13 unconditionally and not given CW treatment.

15 CT and CW are mutually exclusive. A call incoming to a controlling subscriber setting up or engaged
16 in a CT shall be given busy treatment, even if the called subscriber has CW active.

18 Not applicable.

20 If the called subscriber has CNIP and CW active, the CNI shall be presented with the CW notification
21 according to CNIP’s procedures.

23 None identified.

25 None identified.

27 None identified.

29 None identified.

31 CC takes precedence over CW. If CC is invoked, CW shall not be invoked for an incoming call and
32 the subscriber shall be considered to be busy.

34 DND takes precedence over CW. That is, calls arriving for a subscriber with DND and CW active shall
35 be refused and not be given CW treatment.

37 None identified.
1-48
X.S0023

2 CW of the FA Pilot Directory Number shall apply to calls to the Pilot Directory Number when the FA
3 group is considered to be busy, but one or more members that have CW active are able to accept a
4 CW call. CW alerting shall be applied to the members of the FA group able to accept a CW call. If the
5 FA Pilot Directory Number does not have CW active, CW may not apply.

7 MWN pip tone may not be applied if the affected subscriber has requested CW cancellation or has
8 CW de-active.
9 MWN pip tone shall not be applied for the call waiting legs of a call.
10 The CW activation feature code may be the same as the MWN pip tone activation feature code. The
11 CW de-activation feature code may be the same as the MWN pip tone de-activation feature code.
12 The Cancel Call Waiting (CCW) feature code may be the same as the Cancel Message Waiting
13 Notification (CMWN) feature code.

15 Interaction between MAH and CW is beyond the scope of this Standard. The following describes a
16 possible implementation:
17 For a single user MAH group, CW may be applied to a busy MAH member.
18 For a multiple user MAH group, CW of the MAH Pilot Directory Number shall apply to calls to the Pilot
19 Directory Number when the MAH group is considered to be busy, but one or more of the MAH
20 members that have CW active are able to accept a CW call. CW alerting shall be applied to the
21 members of the MAH group able to accept a CW call. If the MAH Pilot Directory Number does not
22 have CW active, CW may not apply.

24 PCA takes precedence over CW. Incoming calls to the subscriber with PCA and CW active shall be
25 screened by the PCA feature before being considered for CW.

27 None identified.

29 PACA has precedence over CW. The CW feature shall not be invoked for incoming calls to a
30 subscriber waiting for a PACA channel, as the subscriber shall be considered to be busy.

32 None identified.

34 SCA takes precedence over CW. Incoming calls to the subscriber with SCA and CW active shall be
35 screened by the SCA feature before being considered for CW.

37 CW feature code requests shall be denied for an MS while SPINA is active.

39 None identified.
1-49
X.S0023

2 3WC and CW are mutually exclusive. A call incoming to a controlling subscriber setting up or
3 engaged in a three-way call shall be given busy treatment, even if the called subscriber has CW
4 active.
5 A flash request from a subscriber authorized for 3WC, while CW alerting is being applied, shall be
6 used to respond to the CW call. If the controlling subscriber still desires a three-way call, it must first
7 dispose of the CW call before requesting a three-way call.

9 None identified.

11 None identified.
12
1-50
X.S0023
1 2.5 Three-Way Calling (3WC) and Multi-Party (MPTY)

2

4 ANSI-41 Mode: Three-Way Calling (3WC) provides the subscriber the capability of adding a third
5 party to an established two-party call, so that all three parties may communicate in a three-way call. If
6 either of the two non-controlling parties to an established three-way call disconnects, the remaining
7 party is re-connected to the controlling subscriber as a normal two-party call. If the controlling
8 subscriber of a three-way call disconnects, the conference circuit and all other parties are released.
9 Digits included with flash requests when a termination address is not expected may be ignored.
10 Native mode user interface capabilities while operating in foreign mode are mobile station dependent.
11 GSM Mode: Once a multi-party call is active, remote parties may be added, disconnected or
12 separated (i.e. removed from the multi-party call but remain connected to the served mobile
13 subscriber). The maximum number of remote parties is 5.

15 3WC/MPTY is applicable to voice telecommunication services.

17

19 GSM native subscribers: This supplementary service is provisioned for all Basic services
20 subscribed to and to which it is applicable, i.e. not provisioned to any subset of these BS. The
21 provision of the Call Hold supplementary service is also required.
22 ANSI-41 native subscribers: 3WC may be generally available or may be provided after pre-
23 arrangement with the service provider.

25 3WC/MPTY may be withdrawn at the subscriber’s request or for administrative reasons.
27 3WC/MPTY has no registration.

29 3WC/MPTY has no de-registration.
31 3WC/MPTY is activated upon authorization.
33 3WC/MPTY shall be de-activated upon de-authorization.
35 ANSI-41 Mode: 3WC is invoked when the appropriate flash request is sent and the feature is
36 authorized.
1-51
X.S0023
1 GSM Mode: Multi-Party service is invoked by the served mobile subscriber by use of a control
2 procedure, as defined in GSM 02.30 [20].

4
5 2.5.3.1 ANSI-41 Mode

6 1. 3WC allows a controlling subscriber to add a third party to an existing two-way call. If necessary,
7 the last party added to a call may be dropped.
8 2. The controlling subscriber presses the SEND key without digits while in a two-way conversation to
9 put the other party on hold.
10  One party is on hold. The system is waiting for the controlling subscriber to enter a feature code
11 or the address of a third party,
12  If the controlling subscriber presses the SEND key without digits, the system reconnects the held
13 party.
14  If the controlling subscriber presses the END key, the system releases the controlling subscriber.
15 Apply distinctive recall alerting to the controlling subscriber to recall the held party.
16  If the controlling subscriber enters termination address + SEND, the system attempts to establish
17 a connection to the third party specified by the termination address allowing the controlling
18 subscriber to hear call progress tones and announcements.
19  If the controlling subscriber enters a feature code, *FC + SEND, the system acts upon the feature
20 code. Apply feature confirmation treatment.
21  If the controlling subscriber enters *FC + # + termination address + SEND, the system acts upon
22 the feature code. Applies feature confirmation treatment. Attempts to establish a connection to
23 the third party specified by the termination address allowing the controlling subscriber to hear call
24 progress tones and announcements.
25  If an incoming call arrives for the controlling subscriber, the system applies busy treatment to the
26 calling party.
27  If the held party disconnects, the system release the held party. The voice channel may be
28 released. Any further action by the subscriber is treated as a new service request.
1-52
X.S0023
1 3. One party is on hold. The controlling subscriber is alerting the other party, or the controlling
2 subscriber is in a two-way conversation with a third party,
3  If the controlling subscriber presses the SEND key without digits, the system connects the
4 controlling, held and third parties into a three-way call.
5  If the controlling subscriber presses the END key, the system releases the controlling subscriber
6 and the third party. Apply distinctive recall alerting to the controlling subscriber to recall the held
7 party.
8  If the controlling subscriber enters digits + SEND key, the system ignores any accompanying
9 digits. Connects the controlling, held and third parties into a three-way call.
10  If the third party answers, the system allows a conversation with the third party.
11  If the third party disconnects, the system releases the third party. Connects the held party.
13 calling party.
14  If the held party disconnects, the system releases the held party.
15 4. A connection is established between the controlling subscriber, a second party and a third party.
16  If the controlling subscriber presses the SEND key without digits, the system releases the third
17 party. Connect the controlling subscriber and the second party.
18  If the controlling subscriber presses the END key, the system releases the controlling subscriber
19 and two other parties.
20  If the controlling subscriber enters digits + SEND key, the system ignores any accompanying
21 digits. Releases the third party. Connect the controlling subscriber and the second party.
22  If the third party answers, the system allows a conversation with the third party.
23  If the third party disconnects, the system releases the third party and connects the controlling
24 subscriber and the second party.
26 calling party.
27  If the second party disconnects, the system releases the second party. Connect the controlling
28 subscriber and the third party.
29 2.5.3.2 GSM Mode

30 Only the served mobile subscriber shall be able to add remote parties to the multi-party call as
31 specified in GSM 02.84 [26].
32 2.5.3.2.1 Beginning the multi-party call
33 When the served mobile subscriber invokes multi-party, the network joins the active call and the call
34 on hold together into a multi-party call in which the served mobile subscriber and the remote parties
35 can all communicate with one another.
1-53
X.S0023
1 2.5.3.2.2 Managing an active multi-party call
2 During an active multi-party call, the served mobile subscriber shall be able to:
3 1. Add another remote party,
4 to which a private communication has been established, if the number of remote parties does not
5 then exceed the maximum number allowed, which results in an active multi-party call.
6 A MPTY invoke notification shall be sent towards all remote parties. A Retrieve notification
7 (according to GSM 02.83 [25]) shall be sent towards all previously held remote parties.
8 2. Put the connection to multi-party call on hold:
9 (i.e., place her connection to the multi-party call on hold (and typically later retrieve it)). The served
10 mobile subscriber may make an enquiry call (e.g., to a potential new remote party) or process a
11 Call Waiting request from this state. While the multi-party call is on hold the remaining remote
12 parties in the multi-party call can have communication with each other.
13 As a result of this scenario, the inquiry call or the accepted waiting call can be added to the multi-
14 party call or released. If the call is released by the served mobile subscriber or by the remote
15 party, the served mobile subscriber is in control of a held multi-party call.
16 A Hold notification (according to GSM 02.83 [25]) shall be sent towards all remote parties.
17 3. Separate a remote party:
18 Explicitly choose one remote party to have a private communication with. This results in that
19 remote party being removed from the multi-party call which is placed on hold, and the conversation
20 between the served mobile subscriber and the designated remote party being a normal active call.
21 The remaining remote parties may have communication with each other in this state.
22 As a result of this scenario the private communication can be added again to the multi-party call or
23 released. If the private call is released by the served mobile subscriber or by the remote party, the
24 served mobile subscriber is in control of a held multi-party call.
25 A Hold notification (according to GSM 02.83 [25]) shall be sent towards all remote parties, except the
26 designated remote party to which a private communication was established.
27 4. Terminate the entire multi-party call.
28 When the served mobile subscriber releases, this is interpreted as a request for termination of the
29 entire multi-party call even if there are calls on hold.
30 No further notification shall be sent.
31 5. Disconnect a remote party:
32 Explicitly release the remote parties on a one at a time basis. In the case when no remote parties
33 remain, the multi-party call is terminated.
34 The notification about the held multiparty call towards the served mobile subscriber is given by the
35 MS, not by the network.
1-54
X.S0023
1 2.5.3.2.3 Managing a held multi-party call
2 During a held multi-party call the served mobile subscriber shall be able to:
3 1. Retrieve the held multi-party call, which results in an active multi-party call.
4 2. Initiate a new call.
5 3. Process a Call Waiting request.
6 4. Disconnect the held multi-party call. All calls belonging to the multi-party call shall be released.
7 5. Disconnect a single remote party.
8 During a held multi-party call the served mobile subscriber shall NOT be able to: Retrieve a single
9 remote party.
10 2.5.3.2.4 Managing a single call and a MPTY
11 a) Single active call
12 If the served mobile subscriber is connected to a single active call (regardless whether it is a private
13 communication or a new initiated call) and has a MPTY on hold, she is able to:
14 1. Disconnect the single active call.
15 2. Disconnect the held MPTY.
16 3. Disconnect both. All calls, even if they are on hold, shall be released.
17 4. Join the single active call and the held MPTY together.
18 This would result in an active MPTY, except if the number of remote parties exceeds the number
19 allowed.
20 A MPTY invoke notification shall be sent towards all remote parties.
21 A Retrieve notification (according to GSM 02.83 [25]) shall be sent towards the previously held
22 remote party.
23 5. Alternate between both calls.
24
25 b) Active MPTY and held call
26 If the served mobile subscriber is connected to a active MPTY and has a single call on hold, she is
27 able to:
28 1. Disconnect the active MPTY.
29 2. Disconnect the single held call.
30 3. Disconnect both. All calls, even if they are on hold, shall be released.
31 4. Join the single held call and the active MPTY together.
32 This would result in an active MPTY, except if the number of remote parties exceeds the number
33 allowed.
34 A MPTY invoke notification shall be sent towards all remote parties. A Retrieve notification
35 (according to GSM 02.83 [25]) shall be sent towards all previously held remote parties.
1-55
X.S0023
1 5. Alternate between both calls.
2 If the served mobile subscriber is connected to an active Multi Party call and has a single call on
3 hold, a request for establishing a private communication shall be rejected by the network. (Because
4 this would lead to an active call and two calls on hold, which is not supported according to the GSM
5 Call Hold Supplementary Service).
6 An indication shall be given to the served mobile subscriber with the reason for failure.
7 2.5.3.2.5 Remote parties in a Multi-Party Call

8 Any of the remote parties shall be able to:
9 1. Put their connection to the multi-party call on hold (and typically later retrieve it). The requirements
10 of the Call Hold service then apply;
11 2. Release from the multi-party call.
12 If a remote party releases and no remote party then remains, the requirements of the normal call
13 release procedures then apply.

16 needed.
18 GSM mode
19 The controlling subscriber may interrogate the network by the use of a control procedure, as specified
20 in GSM 02.30 [20]. The network shall respond with an appropriate indication telling the subscriber
21 whether the service is supported in this network and, if so, provide a list of all Basic Service groups to
22 which the Call waiting supplementary service is active.

24
26 None identified.

28 None identified.
30 None identified.
32 None identified.
1-56
X.S0023
2 ANSI-41 Mode
3 The controlling subscriber is alerting the other party, or the controlling subscriber is in a two-way
4 conversation with the other party, if the controlling subscriber presses the SEND key, the system
5 applies denial treatment. Retain connections.
6 One party is on hold, and the system is waiting for the controlling subscriber to enter a feature code
7 or the address of a third party,
8 • if the controlling subscriber enters the termination address + SEND key, if the subscriber is
9 not authorized for the request, resources are not available, or the termination address was
10 not acceptable; then ignore any accompanying digits and the system applies denial
11 treatment. Retain existing connection to party on hold.
12 • if the controlling subscriber enters *FC + SEND key, if the subscriber is not authorized for the
13 request, resources are not available, or the termination address was not acceptable; then
14 ignore any accompanying digits and the system applies denial treatment. Retain existing
15 connection to party on hold.
16 • if the controlling subscriber enters *FC + # + termination address + SEND key, if the
17 subscriber is not authorized for the request, resources are not available, or the termination
18 address was not acceptable; then ignore any accompanying digits and the system applies
19 denial treatment. Retain existing connection to party on hold.
20 GSM Mode
21 If a served mobile subscriber attempts to invoke multi-party service and the network cannot accept
22 that request, the request shall be rejected and an indication shall be given to the served mobile
23 subscriber with a reason for denial. Some possible reasons for rejection are:
24  service not subscribed;
25  resources cannot be allocated;
26  conflicting situation with other supplementary services;
27  calls are not in appropriate state (e.g., one or more calls are not answered or are in the process
28 of being cleared);
29  service not supported by the local PLMN.
30 If the service provider cannot satisfy the request to add a further remote party (e.g., if the multi-party
31 call has been cleared or if the maximum number of remote parties allowed has already been reached)
32 the served mobile subscriber shall receive an indication that the request is denied, with the reason for
33 failure.
34 If the radio path of the served mobile subscriber is lost permanently for any reason, the multi-party
35 call shall be released.

37 None identified.

39 None identified.
1-57
X.S0023

2 ANSI-41
3 An alternative procedures has been identified for 3WC. This procedure builds upon the normal 3WC
4 procedures.
5 The controlling subscriber is alerting the other party, or the controlling subscriber is in a two-way
6 conversation with the other party:
7  If the controlling subscriber enters a termination address + SEND , the system puts the other
8 party on hold. Atempts to establish a connection to the termination address.
9  If the controlling subscriber enters a termination address + SEND , if the other party is alerting,
10 the controlling subscriber is not authorized for the request, resources are not available, or the
11 termination address was not acceptable; the system applies denial treatment. Reconnects the
12 controlling subscriber and the second party.
13  If the controlling subscriber enters *FC + # + termination address + SEND , the system acts upon
14 the feature code. The system applies feature confirmation treatment. Puts the other party on
15 hold. Attempts to establish a connection to the termination address.
16  If the controlling subscriber enters *FC + # + termination address + SEND , the system acts upon
17 the feature code. If the other party is alerting, the controlling subscriber is not authorized for the
18 request, resources are not available, or the termination address was not acceptable; the system
19 applies for denial treatment. Reconnects the controlling subscriber and the second party.
20
21 GSM Mode
22 None identified.
23

25

27 None identified.

29 None identified.

31 None identified.
33 (BOIC-exHC)
34 None identified.

36 None identified.
1-58
X.S0023
2 None identified.

4 None identified.

6 None identified.

8 None identified.

10 None identified.

12 None identified.

14 None identified.

16 ANSI-41 Mode
17 CT takes precedence over 3WC. When the controlling subscriber disconnects on an active three-way
18 call, and also has CT active, then the disconnect shall be used to transfer the call and the two non-
19 controlling parties remain connected.
20 To avoid a call transfer, the controlling subscriber may force a three-way call to disconnect by
21 sending a flash request to drop the last party added and then disconnecting the remaining party.
22 3WC takes precedence over CT for the interpretation of flash requests. If the controlling subscriber
23 presses SEND in the Holding 2-way state (and both CT and 3WC are active), the result is a
24 conference request rather than a CT drop party request. If the controlling subscriber presses SEND
25 while in the 3-way state, the last party is requested to be dropped.

27 ANSI-41 Mode
28 3WC and CW are mutually exclusive. A call incoming to a controlling subscriber setting up or
29 engaged in a three-way call shall be given busy treatment, even if the called subscriber has CW
30 active.
31 A flash request from a subscriber authorized for 3WC, while CW alerting is being applied, shall be
32 used to respond to the CW call. If the controlling subscriber still desires a three-way call, it must first
33 dispose of the CW call before requesting a three-way call.
34 GSM Mode
35 A user who is active on a multi-party call, either as the served mobile subscriber or as remote party,
36 may receive an indication of a waiting call, provided that the maximum number of calls at the mobile
37 equipment is not exceeded.
1-59
X.S0023
1 After the user has put the multi-party call on hold, the user may accept the waiting call.
2 Any party involved in an active multi-party call may place the connection to the multi-party call on hold
3 and later retrieve it.

5 None identified.

7 ANSI-41 Mode
8 If the 3WC controlling subscriber activates the Temporary CNIR Mode during the setup of a 3WC leg,
9 then the Temporary CNIR activation applies only to that call leg.
10 If the 3WC controlling subscriber de-activates the Temporary CNIR Mode during the setup of a 3WC
11 leg, then the Temporary CNIR de-activation applies only to that call leg.

13 None identified.

15 None identified.

17 None identified.
18 See GSM 02.85 [27], Section 1.6.84.1.

20 ANSI-41 Mode
21 3WC takes precedence over CC. That is, a subscriber cannot add more parties to a 3WC call (in
22 effect trying to convert the 3WC call into a CC call). A 3WC can be converted to a two-way call with a
23 flash request to drop the last party. The two-way call can be converted into a conference call.
24 GSM Mode
25 It shall be possible for any remote party in a multi-party call to alternate between two different multi-
26 party calls.
27 Served Mobile Subscriber:
28 The served mobile subscriber cannot control more than one multi-party call at a time.
29 It shall not be possible to invoke multi-party service if either or both of the initial calls are active parts
30 of one or two other multi-party calls.
31 Multi-Party call controlled by one of the remote parties:
32 The network shall not be required to prevent that a leg to one of the other remote parties can be part
33 of another multi-party call controlled by that remote party.
1-60
X.S0023
1 2.5.6.21 Connected line identification presentation

2 GSM Native Subscriber
3 Remote parties in an existing multi-party call who have subscribed to connected line number
4 identification presentation shall not receive a new remote party’s number whenever a served mobile
5 subscriber adds a new remote party to the multi-party call.

7 None identified.

9 None identified.

11 None identified.

13 MWN pip tone shall only be applied for the first leg of the call.

15 None identified.

17 None identified.

19 None identified.

21 None identified.

23 None identified.

25 None identified.

27 3WC shall not be activated while SPINA is active.

29 The service provider may require the 3WC invoking subscriber (with SPINI active) to enter the SPINI
30 PIN when initiating a three-way call. That is, the subscriber shall be requested to enter the SPINI PIN,
31 if the call leg to the third party meets the call type criteria for SPINI.

33 Not applicable.

35 None identified.
1-61
X.S0023

2 None identified.
1-62
X.S0023
1 2.6 Calling Number / Line Identification Presentation

2

4 Calling Number Identification Presentation (CNIP) or Calling Line Identification Presentation (CLIP)
5 provides the number identification of the calling party to the called subscriber. The terminating
6 network may receive the Calling Number Identification (CNI) as part of basic call setup. CNIP / CLIP
7 does not impact a subscriber's ability to originate calls or to receive calls.

10 For GSM native mode: CLIP applies to all circuit switched telecommunication services.
11 For ANSI native mode: CNIP applies to voice telecommunication services only.
12 2.6.2 GSM and ANSI-41 interoperability Feature Mapping

13 The definition of which feature capabilities are mapped between GSM (in GSM 02.81 [23]) and
14 ANSI-41 modes is described below.
15 2.6.2.1 ANSI-41 foreign mode Capabilities (GSM --> ANSI-41 Feature Mapping)
16 The ability of the subscriber’s serving system to override calling number or line presentation
17 restriction invoked from the calling party’s serving system or PLMN is not supported.
18 Connected Line Identification Presentation and Restriction (COLP / COLR) is not supported.
19 Interrogation of the status of CLIP is not supported.
20 2.6.2.2 GSM Foreign Mode Capabilities (ANSI-41 --> GSM Feature Mapping)
21 The ability to display multiple calling party numbers, a sub-address, or a redirecting number is not
22 explicitly defined.
23 If the called subscriber has call forwarding unconditional active, the ability to present the calling
24 number identification to the subscriber during an abbreviated (or reminder) alert is not supported.

27 CNIP / CLIP shall be generally available after pre-arrangement with the service provider.

29 CNIP / CLIP may be withdrawn at the subscriber’s request or for administrative reasons.
31 CNIP / CLIP has no registration.

33 CNIP / CLIP has no de-registration (or erasure).
1-63
X.S0023
2 CNIP / CLIP shall be activated upon authorization (or provision).
4 CNIP / CLIP shall be de-activated upon de-authorization (or withdrawal).
6 The network automatically invokes CNIP / CLIP upon incoming call set-up when calling number
7 identification is available and presentation is not restricted.

9 If CNIP / CLIP service is authorized and active, and calling number identification is available, the
10 called party’s serving network shall provide the calling number identification during alerting on
11 incoming calls. In addition to or instead of the calling number identification the subscriber shall also
12 be given a Presentation Indicator and Screening Indicator associated with the calling number
13 identification.
14 The originating network shall be capable of transmitting up to 15 digits of calling party number. The
15 subscriber’s serving system must likewise be capable of delivering up to 15 digits of calling party
16 number.
17 If CNIP / CLIP service is not authorized or active, no calling number identification, presentation
18 indicator, or screening indicator shall be delivered to the subscriber, even if it is available to the
19 serving system.

22 needed.
24 GSM mode only: The subscriber can request the status of the CLIP supplementary service.

26
28 None identified.

30 None identified.
32 None identified.
34 None identified.
1-64
X.S0023
2 In some situations with insufficient signaling capability, if the calling party number identification is not
3 available, the called party / subscriber shall receive an indication that calling number identity is not
4 available. This indication may include an alphanumeric display indicatingnumber not available.
5 For an international call with calling party number identification not available, the called party /
6 subscriber shall receive an indication that calling number identity is not available. This indication may
7 include an alphanumeric display indicating number not available.

9 Some serving systems may not offer CNIP / CLIP to any subscriber. In this case, the subscriber shall
10 receive no indication or display during alerting of an incoming call.

12 Some serving systems may not offer CNIP / CLIP to any subscriber. In this case, the subscriber shall
13 receive no indication or display during alerting of an incoming call.

15 None identified.

17

19 None identified.

21 None identified.

23 None identified.
25 (BOIC-exHC)
26 None identified.

28 When BAIC is active, the subscriber shall receive no calling party identification or display.
30 When BIC-Roam is active and invoked, the subscriber shall receive no calling party identification or
31 display.

33 When Call Delivery is not active, the subscriber shall receive no calling party identification or display.

35 None identified.
1-65
X.S0023

2 None identified.

4 None identified.

6 None identified.

8 ANSI-41 mode only: If the called subscriber has CNIP / CLIP active, the calling number
9 identification may be presented to the subscriber during an abbreviated (or reminder) alert in
10 accordance with CNIP / CLIP procedures.

12 None identified.

14 If the called subscriber has CNIP / CLIP active, the calling party identification shall be presented to
15 the subscriber with the call waiting notification.
17 Not applicable.

19 CNIR / CLIR takes precedence over CNIP / CLIP.

21 Authorization and activation of CNAP may be linked to the authorization and activation of CNIP /
22 CLIP.

24 Authorization and activation of CNAR may be linked to the authorization and activation of CNIR /
25 CLIR.

27 None identified.

29 None identified.

31 DND takes precedence over CNIP / CLIP. When DND is active and invoked, the subscriber shall
32 receive no calling party identification or display.

34 None identified.

36 None identified.
1-66
X.S0023

2 None identified.

4 None identified.
5 2.6.7.25 Over the Air Activation (OTA)

6 None identified.

8 None identified.

10 It shall be possible to present information in the subscriber’s preferred language.

12 None identified.

14 None identified.

16 None identified.

18 None identified.

20 None identified.

22 None identified.

24 None identified.

26 None identified.
27
1-67
X.S0023
1 2.7 Call Barring (CB) and Operator Determined Barring (ODB)

2

4 Call Barring (CB) Supplementary service consists of Outgoing Call Barring (OCB) and Incoming Call
5 Barring (ICB). It denies a mobile subscriber the ability to originate/terminate certain types of calls.
6 These can be applied separately per basic service group.
7 Operator Determined Barring (ODB) allows the network operator or service provider to regulate, by
8 means of an exceptional procedure, access by the subscribers to services, by the barring of certain
9 categories of outgoing or incoming calls or of roaming.
10 The purpose of this network feature is to be able to limit the service provider's financial exposure to
11 new subscribers, or to those who have not promptly paid their bills. It may only be applied to the
12 service provider's own subscribers.
13 Application of Operator Determined Barring is controlled by the Service Provider on a subscriber-

14 basis (automatically applies to all basic service groups), by administrative interaction with the HLR;
15 this interface is not standardized.
16 With the exception of the barring of roaming, the HLR effects Operator Determined Barring in a
17 similar manner to Service Provider Call Barring supplementary service. Consequently, the VLR and
18 MSC also execute the relevant Barring Conditions in similar manners. It is noted that there is no
19 password usage. Roaming is barred by the HLR when the MS is in a PLMN other than the Home
20 PLMN or not in the Home PLMN Country as applicable.
21 Operator Determined Barring is a GSM feature. An identical feature does not exist in ANSI-41,
22 although portions of it may be implemented by an operator using ANSI-41. The following sections
23 separately describe the following GSM ODB options for which interoperability can be supported in
24 some form at least (note that the first two are also Call Barring supplementary services):
25  Barring outgoing calls
26  Barring incoming calls
27  Barring of roaming
28  Barring of Supplementary Services Management
29  Barring of registration of call forward-to numbers
30  Barring of invocation of call transfer
31  Description of Barring of Outgoing Calls
32 The operator may select a barring program that prevents certain types of outgoing calls from being
33 originated by the MS.
34 ODB in GSM is documented in GSM 02.41 [21]. Call Barring Supplementary Services in GSM is
35 documented in GSM 02.88 [29].
36 Barring of outgoing calls with a wider range of conditions can be implemented using the ANSI-41
37 Origination Indicator parameter, which is provided by the HLR to the serving MSC/VLR upon
38 subscriber registration, as defined in Chapter 5 of ANSI-41 [2]. The Origination Indicator specifies
39 which types of call originations are permitted, as opposed to which types of call originations are
40 barred or restricted in GSM.
1-68
X.S0023
1 The main problem for roaming interoperability is that for GSM and ANSI-41 the call barring programs
2 are based on different screening criteria. In GSM barring is based on the concept of PLMN, and calls
3 are generally permitted to all terminals within the country of a particular PLMN (i.e., fixed and mobile
4 terminals). ANSI-41 allows more specific barring programs such as ‘local calls only’, or a specific DN.
5 As a result of this conflict, IIF functionality is required to support subscribers using their non-native
6 mode.
7 The mapping of GSM and ANSI-41 outgoing barring conditions may be accomplished as follows:
8 Table 5: ANSI-41 Foreign Mode Interoperability for Barring of Outgoing Calls

GSM Native Mode ANSI-41 Equivalent
Bar all outgoing calls Origination denied
National long distance allowed (which

Bar all outgoing international calls
includes local calls).
Bar all outgoing international calls

National long distance allowed (which
except to HPLMN country (BOIC-
includes local calls).
exHC)
10 Table 6: GSM Foreign Mode Interoperability for Outgoing Call Restrictions

GSM Equivalent (option: either ODB or
ANSI-41 Native Mode
OCB)
Origination denied Bar all outgoing calls (BAOC)
Local Calls Only Allowed Bar all outgoing calls (BAOC)
Selected leading digits of directory Bar all outgoing calls (BAOC)

number allowed
National long distance allowed Bar outgoing international calls (BOIC)
Allow international calls No barring
Allow single directory number only Bar all outgoing calls (BAOC)
(i.e., hotline)
11
12 2.7.1.1 Description of Barring of Incoming Calls

13 Barring of incoming calls takes place at the HLR for native mode and foreign mode. To support
14 interoperability of barring incoming calls when roaming outside the HPLMN country (BIC-Roam), the
15 true serving system identity (SID) must be passed to the HLR upon registration. Otherwise, this
16 feature must be supported from the IIF.
17 2.7.1.2 Description of ODB Barring of Roaming

18 Barring of roaming takes place at the HLR. There is no IIF involvement, beyond the mapping of
19 registration operations between GSM and ANSI-41 based networks. Upon activation of ODB for
20 barring of roaming and ODB Barring of all Outgoing Calls when Roaming Outside the HPLMN
21 country, the HLR can be set to deny registration. The degree of granularity to which roaming can be
22 denied (e.g., roaming outside home PLMN country) shall be determined by the HLR capabilities.
1-69
X.S0023
1 2.7.1.3 Description of ODB Barring of Supplementary Services Management.

2 Barring of supplementary services management takes place at the HLR. There is no IIF involvement
3 (other than transfer of services management requests between GSM and ANSI-41 based networks).
4 Upon activation of ODB for barring of supplementary services management, the HLR can be set to
5 deny these user operations. The degree to which supplementary services management can be
6 denied shall be determined by the HLR capabilities.
7 2.7.1.4 Description of ODB Barring of Registration of Call Forward-to Numbers

8 Barring of registration of call forward-to numbers takes place at the HLR. There is no IIF involvement.
9 Upon activation of ODB for barring of registration of call forward-to numbers, the HLR can be set to
10 deny registration of these numbers. The degree of granularity to which registration can be denied
11 (e.g., Barring of registration of any international call forward-to number) shall be determined by the
12 HLR capabilities.
13 2.7.1.5 Description of ODB Barring of Invocation of Call Transfer

14 Barring of call transfer is possible in ANSI-41 based networks by restriction in the subscriber profile.
15 There is no IIF involvement. It is not possible to conditionally bar call transfer (based on the charging
16 conditions for the various call legs) as described in the GSM ODB Stage 1 description.

18 CB and ODB applies to all telecommunications services except emergency calls and possibly certain
19 outgoing free calls (e.g., calls to customer care).

21 ODB is an administrative feature. There are no user procedures for authorization, de-authorization,
22 registration, or de-registration.
24 Table 7: Call Barring Activation Options

Activation Option Procedure
ODB Service provider controlled activation Determined by the service provider at

provisioning time or at a later date due to
administrative reasons. Cannot be controlled by
the subscriber.
Call Barring Service provider controlled Determined by the service provider at

activation provisioning time or at a later date due to
administrative reasons. Can be controlled by the
subscriber in GSM native mode.
25
1-70
X.S0023
1 2.7.2.2 De-activation
2 Table 8: Call Barring Deactivation Options

De-Activation Option Procedure
ODB Service provider controlled activation Determined by the service provider at

provisioning time or at a later date due to
administrative reasons. Cannot be controlled by
the subscriber.
Call Barring Service provider controlled Determined by the service provider at

activation provisioning time or at a later date due to
administrative reasons. Can be controlled by the
subscriber in GSM native mode.
5 Call Barring and ODB are invoked automatically by the network for subscribers that have it active,
6 upon subscriber or network actions that are barred.

8 A subscriber that attempts to originate a call for which call barring or operator determined barring of
9 outgoing calls has been activated shall receive call denial treatment (e.g., a re-order tone and
10 announcement). Likewise, a caller that attempts to terminate a call for which call barring or operator
11 determined barring of incoming calls has been activated shall receive call denial treatment (e.g., a re-
12 order tone and announcement).
13 A subscriber that attempts to perform other barred operations (e.g., management of supplementary
14 services) shall receive a notification indicating denial of the operation.
15 Call Barring and ODB does not affect the origination of emergency calls.
16 2.7.3.1 Call Detail Record

18 needed.

20
21 2.7.4.1 Provisioning
22 Since GSM PLMNs may not support many of the provisioning criteria in ANSI-41 networks, service
23 provisioning shall revert to the closest available criterion as described above.

25 None identified.

27 None identified.
1-71
X.S0023

2
3 2.7.5.1 Advice of Charge (AoC) or Prepaid Charging (PPC)

4 AoC and PPC take precedence over Call Barring and ODB in the following sense. If service is denied
5 by the AoC or PPC application due to non-payment, then calls shall not be delivered to or sent from
6 the mobile subscriber even if the barring program criteria are met. Whether or not forwarding to the
7 diversion number is done is beyond the scope of this document.
8 2.7.5.2 Barring of Incoming Calls (Call Barring Supplementary Services)

9 Calls shall be denied if either Operator Determined Barring or Barring Of Incoming Calls determine
10 that the call is to be barred.
11 If a call is barred due to both Operator Determined Barring and Barring Of Incoming Calls, then the
12 message or notification returned towards the caller shall be the same as if the barring was due solely
13 to Operator Determined Barring.
14 2.7.5.3 Barring of Outgoing Calls (Call Barring Supplementary Services)

15 Calls shall be denied if either Operator Determined Barring or Barring Of Outgoing Calls determine
16 that the call is to be barred.
17 If a call is barred due to both Operator Determined Barring and Barring Of Outgoing Calls, then the
18 message or notification returned towards the caller shall be the same as if the barring was due solely
19 to Operator Determined Barring.

21 Call Barring and ODB takes precedence over CD. If an incoming call arrives for a subscriber with
22 Barring / ODB and CD active, the call is managed by the barring program first. Only if Call Barring
23 and ODB accepts the call, is CD attempted. If Barring / ODB refuses the call, the call is given barring /
24 ODB refusal treatment.

26 Call Barring (CB)/ODB takes precedence over CFB. If an incoming call arrives for a subscriber with
27 both CB/ODB and CFB active, the call is screened by the CB/ODB program first. If CB and ODB
28 accepts the call, an attempt is made to deliver or terminate the call to the subscriber. If the subscriber
29 is busy, then CFB is invoked.
30 If CFB is in contravention of a Call Barring / Operator Determined Barring Category, when the latter is
31 activated, then the activation shall result in making CFB quiescent. If the subscriber attempts to
32 activate a new CFB program in contravention of a Call Barring / Operator Determined Barring
33 Category, then the activation shall be denied, and the subscriber informed of the denial.
34 2.7.5.6 ANSI-41 Call Forwarding—Default (CFD)

35 CB/ODB takes precedence over CFD. If an incoming call arrives for a subscriber with CB/ODB and
36 CFD active, the call is screened by CB/ODB first. If CB and ODB accepts the call, an attempt is made
37 to deliver or terminate the call to the subscriber. If the subscriber does not or cannot answer the call,
38 then CFD is invoked.
39 If CFD is in contravention of a Call Barring / Operator Determined Barring Category, when the latter is
40 activated, then the activation shall result in making CFD quiescent. If the subscriber attempts to
41 activate a new CFD program in contravention of a Call Barring / Operator Determined Barring
1-72
X.S0023
1 Call Forwarding—No Answer (ANSI-41 CFNA = GSM CF No Reply (CFNRy) and GSM CF Not
2 Reachable (CFNRc))
3 CB/ODB takes precedence over CFNA. If an incoming call arrives for a subscriber with CB/ODB and
4 CFNA active, the call is screened by CB/ODB first. If CB and ODB accepts the call, an attempt is
5 made to deliver or terminate the call to the subscriber. If the subscriber does not or cannot answer the
6 call, then CFNA is invoked.
7 If CFNA is in contravention of a Call Barring / Operator Determined Barring Category, when the latter
8 is activated, then the activation shall result in making CFNA quiescent. If the subscriber attempts to
9 activate a new CFNA program in contravention of a Call Barring / Operator Determined Barring

12 Interaction between ODB and CFU is beyond the scope of this Standard. The following describes a
14 CB/ODB takes precedence over CFU. If an incoming call arrives for a subscriber with CB/ODB and
15 CFU active, incoming calls are denied according to the ODB option, except when Barring of Incoming
16 Calls when Roaming Outside the HPLMN country is active, CFU has precedence).
17 If CFU is in contravention of a Call Barring/ Operator Determined Barring Category, when the latter is
18 activated, then the activation shall result in making CFU quiescent, (except in the case of Barring of
19 Incoming Calls when Roaming outside the HPLMN Country, in which case CFU takes precedence). If
20 the subscriber attempts to activate a new CFU program in contravention of a Call Barring / Operator
21 Determined Barring Category, then the activation shall be denied, and the subscriber informed of the
22 denial.

24 If the subscriber attempts to invoke a call transfer in contravention of a Call Barring / Operator
25 Determined Barring category, then the invocation shall be denied, and the subscriber informed of the
26 denial.
27 2.7.5.9 Call Waiting (CW) or Call Hold (CH)

28 ODB takes precedence over CW. Incoming calls to the subscriber with CB/ODB and CW active shall
29 be screened by the CB/ODB feature before being considered for CW.
30 2.7.5.10 Calling Number/Line Identification Presentation (CNIP/CLIP)

31 None identified.
32 2.7.5.11 Calling Number/Line Identification Restriction (CNIR/CLIR)

33 If the calling number indicatespresentation restricted, the calling number shall not be presented to the
34 called party, the called station, the diversion party, or the diversion station.

36 See GSM 02.85 [27].
37 If a call is barred due to both Call Barring / Operator Determined Barring and CUG restrictions, then
38 the message or notification returned towards the caller shall be the same as if the barring was due
39 solely to Call Barring / Operator Determined Barring.

41 None identified.
1-73
X.S0023

2 Interaction between CB/ODB and DND is beyond the scope of this Standard. The following describes
3 a possible implementation:
4 CB/ODB takes precedence over DND. That is, an incoming call to a subscriber with CB/ODB and
5 DND active is given CB/ODB treatment.

7 Emergency Services takes precedence over CB/ODB. A call to or from an authorized emergency
8 service bureau shall not be refused by CB/ODB.

10 Interaction between FA and CB/ODB is beyond the scope of this Standard. The following describes a
12 CB/ODB on the FA Pilot Directory Number takes precedence over FA. That is, calls to the FA Pilot
13 Directory Number with ODB active are given ODB treatment first. If CB/ODB screening fails, the call
14 is refused. If CB/ODB screening passes, the call is given FA treatment.

16 None identified.

18 Interaction between MAH and CB/ODB is beyond the scope of this Standard. The following describes
19 a possible implementation:
20 CB/ODB of the MAH Pilot Directory Number takes precedence over MAH. That is, calls to the MAH
21 Pilot Directory Number with CB/ODB active are given CB/ODB treatment first. If CB/ODB screening
22 fails, the call is refused. If CB/ODB screening passes, the call is given MAH treatment.
23 2.7.5.19 Password Call Acceptance (BIC)

24 Not applicable.

26 None identified.

28 None identified.

30 TBD.

32 None identified

34 None identified.
35 2.7.5.25 Three-Way Calling (3WC)

36 None identified.
1-74
X.S0023

2 None identified.

4 None identified.
1-75
X.S0023
1 2.8 Short Message Teleservice Support (ANSI-41 Networks)

2

4 A short message teleservice is a mechanism for information delivery end to end between two Short
5 Message Entities (SMEs). The source of the information may be a mobile station or a Teleservice
6 Server (TS). The information may be text based, (e.g., an ANSI-41 Cellular Messaging Teleservice
7 (TDMA or CDMA CMT) message or a GSM short message service (SMS) text message), or it may be
8 coded information destined for the mobile station’s storage and use, (e.g., over the air activation or
9 programming data, or GSM Message Waiting Indication (MWI)). In ANSI-41, unique teleservice
10 formats are defined to deliver different types of information. Conversely, in GSM, both text based and
11 coded information is generically delivered via GSM SMS. The information delivered from the source
12 to the destination is known as user data.
13 SMS teleservices require the use of a Short Message Service Center (SMS-C), also called a
14 Message Center (MC) or Teleservice Server (TS) in ANSI-41, to provide store and forward functions.
15 Thus, an ANSI-41 or GSM network needs to support the transfer of SMS teleservice messages
16 between the SMS-C and the mobile station. For each subscriber, a different SMS-C may be assigned
17 as the home SMS-C for each SMS teleservice. For mobile originated teleservices, the address of the
18 home SMS-C can be provided by the mobile station. The address of the SMS-C would be used for
19 routing purposes in the network when the mobile station originates a SMS teleservice message.
20 Two different categories of point-to-point SMS teleservices have been defined: mobile originated
21 (MO) and mobile terminated (MT). Mobile originated SMS messages shall be transported from a
22 mobile station to the subscriber’s home SMS-C. These may be destined for other mobile users, or for
23 subscribers on a fixed network. Mobile terminated messages shall be transported from the SMS-C to
24 a mobile station. These may be sent to the SMS-C from other mobile users (via a mobile originated
25 SMS teleservice) or from a variety of other sources, (e.g., speech, telex, facsimile, and gateway
26 server).
27 An active mobile station (MS) is allowed to receive an SMS teleservice message at any time it is in
28 service on a GSM or ANSI-41 digital network, independently of whether or not there is a voice or data
29 call in progress. An acknowledgement message shall always be returned to the SMS-C, either
30 confirming that the mobile station has received the teleservice message, or informing the SMS-C that
31 it was impossible to deliver the short message to the mobile station, including the reason why.
32 An active mobile station is allowed to submit a teleservice message at any time it is in service on a
33 GSM or ANSI-41 digital network, independently of whether or not there is a voice or data call in
34 progress. An acknowledgement message shall always be returned to the mobile station, either
35 confirming that the SMS-C has received the teleservice message, or informing the mobile station that
36 it was impossible to deliver the teleservice message to the SMS-C, including the reason why.
37 Both ANSI-41 and GSM native subscribers shall be capable of submitting and receiving SMS
38 teleservice messages in both native and foreign mode. Note that teleservice delivery is not supported
39 in analog AMPS mode.
40 The support of privacy indicators, character sets, validity periods and alert options shall be limited by
41 existing standards.
1-76
X.S0023

2 This section describes the normal procedures that result in a successful outcome.

4 The service is made available to an individual subscriber after necessary arrangements have been
5 made with the home service provider. Authorized service may include:
6  Only mobile originated SMS teleservices
7  Only mobile terminated SMS teleservices
8  Both mobile originated and mobile terminated SMS teleservices

10 The service is removed on an individual basis from subscribers provided with the service after
11 necessary arrangements have been made with the home service provider. Authorized service may
12 include:
13  Only mobile originated SMS teleservices
14  Only mobile terminated SMS teleservices
15  Both mobile originated and mobile terminated SMS teleservices
17 Mobile terminated SMS teleservice registration shall be as a result of Authorization.
18 For mobile originated SMS teleservices the following information shall be registered in the mobile
19 station:
20 SMS-C address(es) as needed for different mobile originated SMS teleservices or applications.

22 Mobile terminated SMS teleservice de-registration shall be as a result of withdrawal.
23 For mobile originated SMS teleservices the following information may be erased in the mobile station:
24 SMS-C address(es) as needed for different mobile originated SMS teleservices or applications.
26 Both mobile originated and mobile terminated SMS teleservices shall be activated as the result of
27 authorization. When operating in GSM or ANSI-41 foreign mode, there is no special activation
28 process required.
30 Both mobile originated and mobile terminated SMS teleservice de-activation shall be the result of de-
31 authorization. When operating in GSM or ANSI-41 foreign mode, there is no special de-activation
32 process required.
1-77
X.S0023
2 Invocation shall be the result of:
3  A mobile station needing to send user data to another Short Message Entity (SME).
4  A SME needing to send user data to a mobile station.
6 Interrogation shall not be possible for mobile terminated SMS teleservices.
7 For mobile originated SMS teleservices, the user shall be able to interrogate if they have any SMS-C
8 addresses registered on their mobile station.

10 For mobile terminated SMS teleservices, the following normal operation applies. Upon receiving a
11 request from an SME, the SMS-C shall:
12  Determine the location of the mobile station
13  Attempt to deliver the user data to the mobile station
14  If notification was requested, an indication shall be passed back to the user.
15 For mobile originated SMS teleservices, the following normal operation applies. The mobile station
16 shall send user data to the network including the following information:
17  Destination address;
18  Home SMS-C address;
19  Originating mobile identifier
20  If notification is required.
21 If notification was requested, an indication shall be passed back to the user.

23 For GSM and ANSI-41 interoperability, no new or special recording capabilities are needed.

25 This section describes abnormal situations not described in “Normal Operation with Successful
26 Outcome”. Procedures on time-outs, unexpected signaling responses, and other such events may be
27 defined.

29 An attempt to re-provision an already provisioned service shall result in an indication to the service
30 provider.
31 2.8.4.2 De-Authorization / Withdrawal

32 An attempt to withdraw a service that has not been provisioned shall result in an indication being
33 provided to the service provider.
1-78
X.S0023
3 2.8.4.4 De-registration / Erasure

4 Not applicable.
6 Not applicable.
8 Not applicable.
10 For mobile terminated teleservices, if the SMS-C attempts to deliver user data to the mobile station
11 and is unsuccessful, an indication shall be presented to the SMS-C. Possible causes may include:
12  insufficient network resources;
13  service not supported;
15  insufficient mobile memory resources;
17  conflicting situation with other supplementary services (e.g., call barring has been activated);
18  subscriber not reachable.
19 For mobile originated teleservices, if the mobile station attempts to deliver user data to the network
20 and is unsuccessful, the user shall be presented with an indication. Possible causes may include:
21  insufficient network resources
22  service not supported
23  service not subscribed to
25  conflicting situation with other supplementary services (e.g., call barring has been activated).
27 Not applicable.

29 None.

31 None Identified

33 None Identified
1-79
X.S0023

2

4 None Identified

6 Per GSM 02.04 [18], BAOC shall inhibit SMS origination, but this interaction is generally not invoked.

8 Per GSM 02.04 [18], BOIC shall inhibit SMS origination, but this interaction is generally not invoked.
10 (BOIC-exHC)
11 Per GSM 02.04 [18], BOIC-exHC shall inhibit SMS origination, but this interaction is generally not
12 invoked.

14 Per GSM 02.04 [18], BAIC shall inhibit SMS delivery, but this interaction is generally not invoked.
16 Per GSM 02.04 [18], BIC-Roam shall inhibit SMS delivery, but this interaction is generally not
17 invoked.

19 None Identified

21 None Identified

23 None Identified

25 None Identified

27 None Identified

29 None Identified

31 None Identified

33 None Identified

35 None Identified
1-80
X.S0023

2 None Identified

4 None Identified

6 None Identified

8 None Identified

10 None Identified

12 None Identified

14 None Identified

16 None Identified

18 None Identified

20 None Identified

22 None Identified

24 None Identified

26 None Identified

28 None Identified

30 None Identified

32 None Identified

34 None Identified
1-81
X.S0023

2 None Identified

4 None Identified

6 None Identified
1-82
X.S0023
1 2.9 Message Waiting Notification

2

4 Message Waiting Notification (MWN) informs authorized and activated subscribers when a voice
5 message is available for retrieval.
6 MWN may use pip tone, alert pip tone, or a MS display indication (including message waiting
7 indication and message waiting count) to inform a subscriber of an unretrieved voice message(s).
8 Once all voice messages have been retrieved, the pip tone, alert pip tone, or a MS display indication
9 must be removed.
10 Pip tone notification provides an audible, stuttered tone to the subscriber in the initial moment of a call
11 origination or termination. Alert pip tone provides an audible alert tone to the subscriber when the MS
12 is idle. MS display indication provides an icon or display text or both indications of the number of
13 unretrieved voice messages (i.e. count).
14 If MS display indication with count is provided, and the number of unretrieved voice messages has
15 increased, the display indication on the MS must be updated.
16 MWN does not impact a subscriber’s ability to originate calls or to receive calls, or to use other
17 features or supplementary services.

19 Message Waiting Notification applies to voice telecommunication services.
20 2.9.1.2 GSM and ANSI-41 interoperability Feature Mapping

21 The definition of which feature capabilities are mapped between GSM and ANSI-41 modes is
22 described below.
23 2.9.1.2.1 ANSI-41 foreign mode Capabilities (GSM --> ANSI-41Feature Mapping)
24 MWN is done via an MS display message waiting indication. An MS display message waiting count is
25 provided to the MS as available. The MS shall be capable of receiving the count.
26 MWN via an MS display indication may be supplemented with audible pip tone alerting.
27 2.9.1.2.2 GSM Foreign Mode Capabilities (ANSI-41--> GSM Feature Mapping)
28 Audible pip tone notification is not supported, but MS display indication shall be provided as required.
29 The ability to activate and de-activate various means of MWN alerting shall not be supported.

32 MWN may be generally available or may be provided after pre-arrangement with the service provider.
33 Pip tone, alert pip tone, or MS display indication (including message waiting indication and message
34 waiting count) are provided at the option of the service provider in ANSI-41mode. Only the MS display
35 indication is provided in GSM mode.
36 Authorization on demand by the subscriber, as described in ANSI-664 [15], shall be optionally

37 supported in ANSI-41native mode only.
1-83
X.S0023

2 MWN may be withdrawn by the service provider.
4 MWN is registered upon authorization.

6 MWN is de-registered upon de-authorization.
8 MWN shall be activated upon authorization. Activation on demand by the subscriber, as described in
9 ANSI-664 [15], shall be optionally supported in ANSI-41native mode only.
11 MWN shall be de-activated upon de-authorization.
13 MWN alert pip tone is invoked when the first voice message is left in a VMS for a particular
14 subscriber. MWN alert pip tone is also invoked upon MS power up and there is one or more
15 unretrieved voice messages in the VMS. Alert pip tone notification is provided when authorized by the
16 service provider in ANSI-41mode only.
17 MWN pip tone is invoked when a voice message is left and remains unretrieved in a Voice Message
18 System (VMS) for a particular subscriber, and the subscriber originates a call or answers an incoming
19 call. Pip tone notification is provided when authorized by the service provider in ANSI-41mode only.
20 MS display indication is invoked when a voice message is left in a VMS for a particular subscriber. It
21 is also invoked when ANSI-41 registration procedures are invoked for a subscriber and there is an
22 unretrieved voice message in the VMS for the subscriber. In ANSI-41mode, the message waiting
23 count indication may be updated each time the number of messages in the VMS changes.

25 Alert pip tone shall be applied when the MS powers up and a voice message remains unretrieved in
26 the VMS. The alert pip tone shall also be applied when the first voice message is left on a VMS and
27 the MS is available and not engaged in a call or service request.
28 Pip tone notification shall be inserted into the voice channel when the subscriber originates a call or
29 answers an incoming call and a voice message is awaiting retrieval.
30 The MS display message waiting indication shall be provided to an MS as long as there is an

31 unretrieved voice message in the VMS. The MS display indication (including message waiting
32 indication and message waiting count) is removed from the MS after the last voice message has been
33 retrieved from the VMS.

36 needed.
38 Not applicable
1-84
X.S0023

2
4 None identified.

6 None identified.
8 None identified.
10 None identified.
12 None identified.

14 None identified.

16 None identified.

18 None identified.

20

22 None identified.

24 None identified.

26 None identified.
28 (BOIC-exHC)
29 None identified.

31 None identified.
1-85
X.S0023
2 None identified.

4 None identified.

6 None identified.

8 None identified.

10 None identified.

12 None identified.

14 None identified.

16 None identified.

18 No pip tone notification shall be provided if call waiting has been deactivated.

20 None identified.

22 None identified.

24 None identified.

26 None identified.

28 None identified.

30 Any pip tone notification shall only be applied to the primary leg of a multiparty call.

32 MWN MS indication, count, and pip tone takes precedence over DND. MWN indication and pip tone
33 may still be applied while DND is active.
1-86
X.S0023
1 DND takes precedence over MWN alert pip tone. That is, while DND is active, alerting shall not be
2 applied.

4 None identified.

6 None identified.

8 Not applicable.

10 None identified.
11 2.9.6.26 Over the Air Activation (OTA)

12 None identified.

14 None identified.

16 None identified.

18 None identified.

20 None identified.

22 None identified.

24 None identified.

26 None identified.

28 Any pip tone notification shall only be applied to the primary leg of a three-way call.

30 None identified.

32 None identified.
1-87
X.S0023
1 2.10 GPRS in GSM Foreign mode

2 GPRS in GSM Foreign mode applies to the case where an ANSI-41ANSI-41 based subscriber (e.g.,
3 an ANSI-41 TDMA or CDMA native subscriber) has registered on a GPRS network [30].
4 GPRS in GSM Foreign Mode allows a subscriber to an ANSI-41 based network (e.g., an ANSI-41
5 TDMA or CDMA native subscriber) to obtain GPRS service (i.e., register for service) in GSM Foreign
6 Mode. There is no impact on ANSI-41 Foreign Mode. There is no communication between a GSM
7 SGSN and an ANSI-41 MSC and a mobile can not operate simultaneously on GPRS and ANSI-41
8 systems.
9 In GSM Foreign Mode it is required that the handset register on a GSM network or a GPRS network
10 to be in GSM Foreign Mode. The GPRS network may be coupled with a GSM network (i.e., one
11 PLMN can provide both GSM circuit-switched and packet service).

13 GPRS is a GSM Bearer Service that provides a packet data transmission scheme within the PLMN.
14 GPRS can also be used as a bearer for SMS teleservices.

16 Subscribers operating GPRS in GSM foreign mode (e.g., ANSI-41 TDMA or CDMA native
17 subscribers) shall be able to send and receive GPRS service packets when attached to a GPRS
18 network.

20 GPRS subscription data must be provisioned and stored on the IIF, acting as the GPRS HLR. It may
21 be possible to provision an ANSI-41 TDMA or CDMA native subscriber with GPRS only service and
22 no GSM CS service.

24 The de-authorization shall be possible at the IIF, acting as the GPRS HLR, as well as at the
25 Authentication Center.
26 2.10.2.3 Authentication
27 The GPRS network shall query the IIF, acting as a GPRS HLR, to verify the authentication
28 parameters. This may occur upon with GPRS attach and GPRS routing area update operations.
29 2.10.2.4 ANSI-41 registration

30 ANSI-41 registration occurs when the subscriber roams into an ANSI-41 network and is:
31  registered on a GSM MSC and a GPRS SGSN; or
32  registered on a GPRS SGSN; or
33  registered on a GSM MSC.
34 ANSI-41 registration in all of these conditions shall result in a cancel location towards one or both of
35 the GSM MSC and GPRS SGSN, if the subscriber is registered to that network element.
1-88
X.S0023
1 2.10.2.5 GPRS Attach

2 The MS shall perform a GPRS attach to access GPRS services. This can be immediately after the
3 MS has been switched on or later as the user decides to use the GPRS service.
4 A successful GPRS attach requires a valid GPRS subscription.
5 The GPRS attach itself may be performed as one of the following:
6  GPRS only attach; or
7  GPRS attach when GSM CS attached; or
8  combined GPRS and GSM CS attach.
9 If one of the above GPRS attaches takes place when previously registered on an ANSI-41 network,
10 normal registration cancellation within the ANSI-41 network shall take place.
11 2.10.2.6 GPRS Detach

12 A GPRS detach allows:
13  an MS to inform the network that it does not want to access GPRS services any longer; and
14  the network to inform the MS that it does not have access to the GPRS services any longer.
15 The GPRS detach itself may be performed as one of the following:
16  GPRS only detach;
17  GPRS detach when GSM CS attached;
18  combined GPRS and GSM CS detach.
19 The MS is detached either explicitly or implicitly as follows:
20  Explicit Detach: the network or the MS explicitly requests detach.
21  Implicit Detach: the network detaches the MS, without notifying the MS.
22 2.10.2.7 GPRS Routing Area Update

23 A routing area update occurs when a GPRS attached MS detects that it has entered a new routing
24 area or when the periodic routing area update timer has expired. These may be combined with GSM
25 CS location area updates depending on the network mode of operation.
26 The following GPRS Routing Area Updates are possible:
27  intra SGSN Routing Area Update.
28  inter SGSN Routing Area Update.
29 The following combined RA and LA updates takes place when an association exists between the
30 SGSN and the MSC [30]:
31  combined Intra SGSN RA and LA update.
32  combined Inter SGSN RA and LA update.
1-89
X.S0023
1 2.10.2.8 SMS Impacts

2 GPRS has the following impacts on SMS:
3  When operating GPRS in GSM Foreign mode, and both GPRS attached and GSM CS
4 attached, the mobile may originate mobile-originated SMS messages either thru the GSM
5 network or the GPRS network. When operating only in GPRS mode, SMS originations thru the
6 GPRS network shall be possible.
7  When operating GPRS in GSM Foreign mode, and both GPRS attached and GSM CS
8 attached, the mobile shall receive mobile-terminated SMS messages either thru the GSM
9 network or the GPRS network. When operating in GPRS only mode, SMS terminations shall be
10 possible.
11 For GSM native subscribers in GSM native mode, the GSM SMS Service Center (i.e., SMSC) queries
12 the combined GSM-GPRS HLR for routing information and the HLR responds with both the SGSN
13 address as well as the GSM MSC address. Then the SMSC decides to send the SMS message to
14 either the GPRS SGSN or the GSM MSC.
15 For GPRS in GSM Foreign Mode the ANSI-41 MC shall query the ANSI-41 HLR for the ANSI-41
16 MSC address and shall be instructed to route the ANSI-41 formatted SMS message to the IIF,
17 emulating both an ANSI-41 MSC and a GSM SMSC, for any of the following conditions:
18  when the subscriber is both GSM CS attached and GPRS attached; or
19  when the subscriber is GPRS only attached; or
20  when the subscriber is GSM CS only attached.
21 The IIF shall then convert the mobile-terminated ANSI-41 SMS message to a GSM-formatted SMS
22 message and, acting like a GSM SMSC, send it to the GSM MSC or the GPRS SGSN. If the MS is
23 reachable a Network option for routing the SMS messages may be as follows:
24  first - send to the GPRS SGSN;
25  second - send to the GSM MSC.

27 In the event that the IIF is not able to authenticate the GPRS subscriber, the GPRS service shall be
28 denied. If the ANSI-41 registration process fails due to location update failure or authentication failure,
29 the MS shall be denied access to the GPRS network.
30 In the event that the IIF receives a mobile terminating ANSI-41 formatted SMS message, and if the
31 IIF detects that the GSM Foreign Mode subscriber is not reachable (for both packet and circuit-
32 switched services), the IIF shall reply to the ANSI-41 Message Center with an error and when the IIF
33 detects that the subscriber is again reachable, either GPRS or non-GPRS, then the IIF shall notify the
34 Message Center to retransmit the ANSI-41 formatted SMS message to the IIF.
35 The SGSN notifies (i.e., alert) the IIF, acting as a GPRS HLR, when the handset has memory
36 available and when the handset is “MS present”.
37 GSM GPRS HLR fault recovery procedures shall also apply to the IIF acting as the GPRS HLR.
38 2.10.3.1 GPRS Attach

39 None identified.
1-90
X.S0023
1 2.10.3.2 GPRS Detach

2 None identified.

4 None identified.

6 None identified.

8 None identified.

10

12 None identified
13 2.10.5.2 Authentication
14 GSM authentication procedures are required to be supported by the IIF in the GPRS home network.
15 For GPRS in GSM Foreign Mode the authentication procedure is done according to the procedures
16 defined in GSM 09.02 [4].

18 ODB_BAOC may be provisioned in the IIF, acting as a GPRS HLR, and it applies to Mobile
19 Originated SMS via the GPRS network.

21 ODB_BOIC may be provisioned in the IIF, emulating a GPRS HLR, and it applies to Mobile
24 (BOIC-exHC)
25 ODB_BOIC-exHC may be provisioned in the IIF, emulating a GPRS HLR, and it applies to Mobile
27 2.10.5.6 Operator Determined Barring PLMN-specific

28 Four ODB PLMN-specific barring programs may be provisioned in the IIF, emulating a GPRS HLR,
29 and each applies to Mobile Originated SMS via the GPRS network.

31 ODB_BAIC may be provisioned in the IIF, emulating a GPRS HLR, and it applies for GPRS and
32 Mobile Terminated SMS deliveries thru the GPRS network.
34 None identified.
1-91
X.S0023

2 When a subscriber receives a call termination attempt when operating in GSM foreign mode (e.g.,
3 ASNI-41 TDMA or CDMAnative subscriber) and connected to a GPRS network, the GSM Circuit-
4 switched paging is sent through the GPRS SGSN and the IIF is not impacted.1
5 Call terminations to the subscriber (e.g., ANSI-41 TDMA or CDMAnative subscriber) operating in
6 GPRS only mode shall not be possible. However, it is possible for the IIF to send a SMS message to
7 the user thru the GPRS network indicating the calling party number of the missed call.

9 None identified.

11 None identified.

13 None identified.

15 None identified.

17 None identified.

19 None identified.

21 None identified.

23 None identified.

25 None identified.

27 None identified.

29 None identified.

31 None identified.
1 The MSC and SGSN are both GSM.
1-92
X.S0023

2 None identified.

4 None identified.
5 2.10.5.24 Emergency Services (Future)

6 None identified.

8 None identified.

10 None identified.

12 None identified.

14 None identified.

16 None identified.

18 None identified.

20 None identified.

22 None identified.

24 None identified.

26 None identified.

28 None Identified.

30 None identified.

32 None identified.
33
1-93
X.S0023
1 N
Neettw
woorrkk IInntteerrw
woorrkkiinngg B
Beettw
weeeenn GGS SM
MMMA
APP aanndd TTIIA
A--4411 M
MAAP
P;;
2 R
Reevviissiioonn B
B –– C CD
DMMA A22000000 S
Suuppppoorrtt
3 V
Voolluum
mee 22 –– IInnffoorrm
maattiioonn FFlloow
wss
4 ((R
STTD
D--003388--A
AVVoolluum
mee 22))
5 Abstract
6 This Volume contains the information flows for GSM MAP/TIA-41 MAP interworking.
2-i
X.S0023
1 Contents
2 Abstract.....................................................................................................................................................i
3 Contents ..................................................................................................................................................ii
4 List of Tables .........................................................................................................................................vii
5 List of Figures....................................................................................................................................... viii
6 Foreword................................................................................................................................................xii
7 1 Introduction ............................................................................................................................... 1
8 1.1 General .................................................................................................................................. 1
9 2 Purpose..................................................................................................................................... 1
10 3 Scope ........................................................................................................................................ 1
11 4 Stage 2 Information Flows ....................................................................................................... 2

12 4.1 Location Registration ............................................................................................................ 2
13 4.1.1 Location Registration in GSM Foreign Mode................................................................ 2
14 4.1.1.1 MS registers in a GSM network when previously registered in an
15 ANSI-41 network........................................................................................ 2
16 4.1.1.2 MS location updates in a different MSC/VLR ........................................... 4
17 4.1.1.3 IMSI Detach ............................................................................................... 5
18 4.1.1.4 IMSI Attach................................................................................................. 6
19 4.1.2 Location Registration in ANSI-41 Foreign Mode .......................................................... 7
20 4.1.2.1 MS registers in an ANSI-41 network when previously registered in
21 a GSM network .......................................................................................... 7
22 4.1.2.2 MS location updates in a different MSC/VLR ........................................... 9
23 4.1.2.3 MS Powers Off......................................................................................... 10
24 4.1.2.4 MS Powers On......................................................................................... 10
25 4.1.3 Location Registration in Native Mode ......................................................................... 11
26 4.1.3.1 MS registers in an ANSI-41 network when previously registered in
27 a GSM network ........................................................................................ 11
28 4.1.3.2 MS registers in a GSM network when previously registered in an
29 ANSI-41 network...................................................................................... 13
30 4.2 Fault Recovery Procedures ................................................................................................ 15
31 4.2.1 Fault Recovery Procedures in GSM Foreign Mode.................................................... 15
32 4.2.1.1 Recovery from Failure at the ANSI-41 HLR ........................................... 15
33 4.2.1.2 Recovery from Failure at the IIF.............................................................. 16
34 4.2.1.3 Recovery from Failure at the serving GSM VLR .................................... 17
35 4.2.2 Fault Recovery Procedures in ANSI-41 Foreign Mode .............................................. 18
36 4.2.2.1 Recovery from Failure at the GSM HLR................................................. 18
37 4.2.2.2 Recovery from Failure at the IIF.............................................................. 19
38 4.2.2.3 Recovery from Data Failure at the ANSI-41 VLR................................... 19
39 4.4 Subscriber Data Management............................................................................................ 20
2-ii
X.S0023
1 4.4.1 Subscriber Data Management Procedures in ANSI-41 Foreign Mode...................... 20

2 4.4.1.1 Subscriber Deletion ................................................................................. 20
3 4.4.1.2 Subscriber Data Modification .................................................................. 21
4 4.4.2 Subscriber Data Management Procedures in GSM Foreign Mode ........................... 24
5 4.4.2.1 Subscriber Deletion ................................................................................. 24
6 4.4.2.2 Modifying Subscriber Data ...................................................................... 25
7 4.5 Automatic Call Delivery....................................................................................................... 26
8 4.5.1 Automatic Call Delivery Activation/Deactivation ......................................................... 26
9 4.5.2 Automatic Call Delivery Invocation.............................................................................. 26
10 4.5.2.1 Call Delivery to ANSI-41Subscriber Roaming in GSM Network............ 26
11 4.5.2.2 Delivery to an ANSI-41Subscriber Roaming in a GSM Network –
12 Unsuccessful Case .................................................................................. 28
13 4.5.2.3 Call Delivery to a GSM Subscriber Roaming in ANSI-41 Network –
14 Successful Case ...................................................................................... 29
15 4.5.2.4 Call Delivery to a GSM Subscriber Roaming in ANSI-41 Network –
16 Unsuccessful Case .................................................................................. 30
17 4.6 Call Forwarding ................................................................................................................... 31
18 4.6.1 Call forwarding scenarios for ANSI-41 foreign mode ................................................. 31
19 4.6.1.1 Call forwarding unconditional (CFU)....................................................... 31
20 4.6.1.2 Call forwarding busy (CFB) ..................................................................... 39
21 4.6.1.3 Call forwarding no reply (CFNRy) ........................................................... 44
22 4.6.1.4 Call forwarding not reachable (CFNRc).................................................. 47
23 4.6.2 Call forwarding scenarios for GSM foreign mode....................................................... 51
24 4.6.2.1 Call forwarding unconditional (CFU)....................................................... 51
25 4.6.2.2 Call forwarding busy (CFB) ..................................................................... 56
26 4.6.2.3 Call forwarding no answer (CFNA) ......................................................... 66
27 4.7 Optimal Routing for Late Call Forwarding.......................................................................... 68
28 4.7.1 ANSI-41 Foreign Mode ................................................................................................ 69
29 4.7.1.1 ANSI-41 Foreign Mode - Success condition .......................................... 69
30 4.7.1.2 ANSI-41 Foreign Mode - Failure condition ............................................. 72
31 4.7.2 GSM Foreign Mode...................................................................................................... 73
32 4.7.2.1 GSM Foreign Mode - Success Case ...................................................... 73
33 4.7.2.2 GSM Foreign Mode - Failure case.......................................................... 75
34 4.8 Call Waiting ......................................................................................................................... 76
35 4.8.1 Call Waiting Activation ................................................................................................. 76
36 4.8.1.1 ANSI-41 Foreign Mode Successful Call Waiting Activation................... 76
37 4.8.1.2 ANSI-41 Foreign Mode Unsuccessful Call Waiting Activation............... 78
38 4.8.1.3 GSM Foreign Mode Feature Activation .................................................. 79
39 4.8.2 Call Waiting Deactivation ............................................................................................. 81
40 4.8.2.1 ANSI-41 Foreign Mode Call Waiting Deactivation ................................. 81
41 4.8.2.2 GSM Foreign Mode Feature Deactivation .............................................. 83
42 4.9 Calling Number / Line Identification Presentation/Restriction........................................... 85
43 4.9.1 Handling of calling number/ line identification presentation ....................................... 85
44 4.9.1.1 GSM Foreign Mode ................................................................................. 85
45 4.9.1.2 ANSI-41 Foreign Mode............................................................................ 87
46 4.9.2 Handling of calling number/ line identification restriction ........................................... 89
2-iii
X.S0023
1 4.9.2.1 General..................................................................................................... 89
2 4.9.2.2 GSM Foreign Mode ................................................................................. 89
4 4.10 Call Barring and Operator Determined Barring ................................................................. 90
5 4.10.1 Activation of Barring at VLR......................................................................................... 90
6 4.10.1.1 Activation of Call Restrictions while in GSM Foreign Mode................... 90
7 4.10.1.2 Activation of Call Barring while in ANSI-41 Foreign Mode..................... 91
8 4.10.2 Invocation of Barring of Incoming Calls....................................................................... 92
9 4.10.2.1 GSM Foreign Mode ................................................................................. 92
11 4.10.3 Invocation of Barring of Roaming ................................................................................ 92
12 4.10.3.1 GSM Foreign Mode ................................................................................. 92
14 4.10.4 Invocation of Barring of Supplementary Services Management................................ 94
15 4.10.4.1 GSM Foreign Mode ................................................................................. 94
17 4.11 Short Message Service....................................................................................................... 96
18 4.11.1 Assumptions ................................................................................................................. 96
19 4.11.2 Mobile Station only Supports GHOST/WEMT ............................................................ 97
20 4.11.2.1 Short Message from CMT Mobile Station to GHOST/WEMT Mobile
21 Station both in Native Mode .................................................................... 97
22 4.11.2.2 Short Message sent from GHOST/WEMT Mobile Station to CMT
23 Mobile Station, both in Native Mode ....................................................... 98
24 4.11.3 Mobile Terminating SMS in GSM Foreign Mode ........................................................ 99
25 4.11.3.1 Successful Mobile Terminating ANSI-41SMS (CMT) mapped to
26 GSM SMS ................................................................................................ 99
27 4.11.3.2 Successful Mobile Terminating ANSI-41SMS (GHOST/WEMT)
28 Mapped to GSM SMS............................................................................ 101
29 4.11.3.3 Unsuccessful Mobile Terminated Delivery (Failure at MSC) ............... 102
30 4.11.3.4 Unsuccessful Mobile Terminated Delivery (Failure at IIF)................... 104
31 4.11.3.5 Alerting for an ANSI-41Subscriber in GSM Foreign Mode .................. 105
32 4.11.4 Mobile Terminated SMS in ANSI-41 Foreign Mode ................................................. 106
33 4.11.4.1 Successful GSM SMS mapped to ANSI-41(CMT) SMS...................... 106
34 4.11.4.2 Successful GSM SMS mapped to ANSI-41(GHOST/WEMT) SMS .... 108
35 4.11.4.3 Unsuccessful GSM SMS mapped to ANSI-41SMS (Failure at MS).... 110
36 4.11.4.4 Unsuccessful Delivery to GSM Subscriber (Postponed at MSC) ........ 112
37 4.11.4.5 Unsuccessful Delivery to GSM Subscriber (Failure at IIF) .................. 114
38 4.11.4.6 Alerting for a GSM Subscriber in ANSI-41 Foreign Mode ................... 115
39 4.11.5 Message Flows for Mobile Originated SMS in GSM Foreign Mode ........................ 116
40 4.11.5.1 Successful Mobile Originated Delivery ................................................. 116
41 4.11.5.2 Unsuccessful Mobile Originated (Failure at MC).................................. 117
42 4.11.5.3 Unsuccessful Mobile Originated (Failure at IIF) ................................... 118
43 4.11.6 Message Flows for Mobile Originated SMS in ANSI-41 Foreign Mode................... 119
44 4.11.6.1 Successful Mobile Originated Delivery ................................................. 119
45 4.11.6.2 Unsuccessful Mobile Originated (Failure at SMSC)............................. 120
46 4.11.6.3 Unsuccessful Mobile Originated (Failure at IIF) ................................... 121
2-iv
X.S0023
1 4.12 Message Waiting Notification ........................................................................................... 122

2 4.12.1 GSM Foreign Mode.................................................................................................... 122
3 4.12.1.1 Indicator in ANSI-41 Registration Notification Return Result
4 mapped to GSM SMS............................................................................ 123
5 4.12.1.2 ANSI-41 Qualification Directive mapped to GSM SMS........................ 125
6 4.12.1.3 Handling when GSM MSC/VLR only supports GSM Phase 1 (MAP
7 V1) .......................................................................................................... 127
8 4.12.1.4 Handling at SMS delivery failure at the IIF ........................................... 129
9 4.12.1.5 Handling at SMS delivery failure at the MSC/VLR or at the Mobile
10 Station .................................................................................................... 130
11 4.12.2 ANSI-41 Foreign Mode .............................................................................................. 132
12 4.12.2.1 GSM SMS mapped to ANSI-41 Qualification Directive........................ 132
13 4.12.2.2 GSM SMS mapped to ANSI-41 SMS using GHOST or WEMT
14 Teleservice............................................................................................. 134
15 4.12.2.3 Clearing of MWN Information after Retrieval of Messages while in
16 ANSI-41 Foreign Mode – QualDir Method............................................ 136
17 4.12.2.4 Handling at SMS delivery failure at the IIF ........................................... 138
18 4.12.2.5 Handling at SMS delivery failure at the MSC/VLR – QualDir
19 Method ................................................................................................... 140
20 4.12.2.6 Handling at SMS delivery failure at the MSC/VLR –
21 GHOST/WEMT SMS Method................................................................ 142
22 4.12.2.7 GSM SMS mapped to ANSI-41 Qualification Directive and to
23 Registration Notification Return Result................................................. 144
24 4.13 GPRS in GSM Foreign Mode ........................................................................................... 147
25 4.13.1 Location Registration Scenarios................................................................................ 148
26 4.13.1.1 GPRS Attach (not currently registered) ................................................ 148
27 GPRS Attach when currently registered in an ANSI-41 network ............................. 152
28 4.13.1.3 Inter-SGSN routing area update ........................................................... 156
29 4.13.1.4 GPRS- Attach when only GSM CS Attached ...................................... 160
30 4.13.1.5 Combined GSM and GPRS attach when not currently registered ...... 162
31 4.13.1.6 Combined Inter-SGSN Routeing Area/Location Area Update............. 169
32 4.13.1.7 Inter-SGSN routing area update when GSM CS and GPRS
33 attached (GSM MSC remains constant)............................................... 172
34 4.13.1.8 Combined Attach When Currently Registered in an ANSI-41 MSC.... 174
35 4.13.1.9 Authentication Failure at the IIF ............................................................ 178
36 4.13.1.10 Registration Failure at the ANSI-41HLR............................................... 178
37 4.13.2 Location Deregistration Scenarios ............................................................................ 179
38 4.13.2.1 GSM CS (IMSI) Detach while GPRS and GSM CS Attached ............. 179
39 4.13.2.2 GPRS Detach While Attached for Both GPRS and GSM CS
40 Services.................................................................................................. 179
41 4.13.2.3 GPRS Detach While Attached for GPRS Services Only ..................... 179
42 4.13.2.4 Combined GPRS Detach and GSM CS (IMSI) Detach ....................... 179
43 4.13.2.5 GPRS Detach Followed By Purge ........................................................ 180
44 4.13.2.6 IIF - Initiated Detach ............................................................................. 181
45 4.13.3 SMS Scenarios........................................................................................................... 182
46 4.13.3.1 SMS Scenarios for Mobile Terminated SMS while GPRS Attached ... 182
2-v
X.S0023
1 4.13.3.1.1 Successful Mobile Terminated ANSI-41SMS (CMT) Mapped to GSM

2 SMS........................................................................................................ 182
3 4.13.3.1.2 Successful Mobile Terminating ANSI-41SMS (GHOST/WEMT)
4 Mapped to GSM SMS............................................................................ 184
5 4.13.3.1.3 Unsuccessful Mobile Terminated Delivery (Failure at SGSN)................ 185
6 4.13.3.1.4 Unsuccessful Mobile Terminated Delivery (Failure at IIF)...................... 187
7 4.13.3.1.5 Alerting for an ANSI-41Subscriber for GPRS in GSM Foreign Mode .... 188
8 4.13.4 Message Flows for Mobile Originated SMS when operating GPRS in GSM Foreign
9 Mode 189
10 4.13.4.1 Successful Mobile Originated SMS to MC ................................................. 189
11 4.13.4.2 Unsuccessful Mobile Originated (Failure at MC)........................................ 190
12 4.13.4.3 Unsuccessful Mobile Originated (Failure at IIF) ......................................... 191
13 4.13.5 Message Waiting Notification while GPRS Attached in GSM Foreign Mode .......... 192
14 4.13.5.1 Indicator in ANSI-41 Registration Notification Return Result mapped to GSM SMS193
15 4.13.5.2 ANSI-41 Qualification Directive mapped to GSM SMS.............................. 195
16 4.13.5.3 Handling at SMS delivery failure at the SGSN or at the Mobile Station ... 197
17 4.13.6. Call Delivery Scenarios............................................................................................. 199
18 4.13.6.1 Call Delivery Scenarios in GSM Foreign Mode while GSM CS and
19 GPRS Attached...................................................................................... 199
20 4.13.6.1.1 Call Delivery to ANSI-41Subscriber Roaming on a GSM/GPRS
21 Network .................................................................................................. 199
22 4.13.6.1.2 Call Delivery to ANSI-41Subscriber Roaming in a GPRS Network
23 (Unsuccessful) ....................................................................................... 201
24 4.13.6.2 Successful Network-Requested PDP Context Activation Procedure.. 203
25 4.13.6.3 Unsuccessful Network-Requested PDP Context Activation
26 Procedure............................................................................................... 204
27 4.13.7 Packet Domain Subscriber Data in the IIF............................................................... 204
28 Annex A (informative) ........................................................................................................................ 205
29 Annex B - CDMA to GSM One-way Roaming Only.......................................................................... 207

30 B.1 Successful Authentication on Initial Access in GSM System.......................................... 207
31 B. 2 Authentication Failure on Initial Access in GSM System ................................................ 209
32 B.3 Authentication Failure on Initial Access in GSM System – Authentication Failure Message
33 Not Supported ................................................................................................................... 211
34 B.4 GSM System Request for Additional Triplets .................................................................. 213
35
36
2-vi
X.S0023
1 List of Tables
2 There are no tables in this volume.
2-vii
X.S0023
1 List of Figures
2 Figure 1: Registration on a GSM Network – GSM Foreign Mode ....................................................... 2
3 Figure 2: Registration in a different MSC/VLR – GSM Foreign Mode................................................. 4
4 Figure 3: Registration on an ANSI-41 network – ANSI-41 Foreign Mode........................................... 7
5 Figure 4: Registration in a different MSC/VLR – ANSI-41 Foreign Mode ........................................... 9
6 Figure 5: Registration in an ANSI-41 Network (Native Mode) ........................................................... 11
7 Figure 6: Registration in a GSM Network (Native Mode) ................................................................... 13
8 Figure 7: Failure at the ANSI-41 HLR (GSM Foreign Mode) ............................................................. 15
9 Figure 8: IIF Failure (GSM Foreign Mode).......................................................................................... 16
10 Figure 9: Terminating Call Flow following a GSM VLR Failure.......................................................... 17
11 Figure 10: Failure at a GSM HLR (ANSI-41 Foreign Mode) .............................................................. 18
12 Figure 25: Subscriber Deletion – ANSI-41 Foreign Mode.................................................................. 20
13 Figure 26: Insert Subscriber Data Procedure ..................................................................................... 21
14 Figure 27: Delete Subscriber Data Procedure.................................................................................... 22
15 Figure 28: Cancel Location Procedure ............................................................................................... 23
16 Figure 29: Subscriber Deletion- GSM Foreign Mode ......................................................................... 24
17 Figure 30: Subscriber Data Modification............................................................................................. 25
18 Figure 31: Call Delivery to ANSI-41 Subscriber Roaming in a GSM Network .................................. 26
19 Figure 32: Unsuccessful Call Delivery to an ANSI-41Subscriber Roaming in a GSM

20 Network......................................................................................................................... 28
21 Figure 33: Call Delivery to GSM Subscriber Roaming in an ANSI-41 Network ................................ 29
22 Figure 34: Unsuccessful Call Delivery to GSM Subscriber Roaming in an ANSI-41 Network ......... 30
23 Figure 35: CFU registration ................................................................................................................. 31
24 Figure 36: CFU deregistration (erasure) ............................................................................................. 33
25 Figure 37: CFU activation .................................................................................................................... 35
26 Figure 38: CFU deactivation................................................................................................................ 37
27 Figure 39: CFU invocation ................................................................................................................... 38
28 Figure 40: CFB invocation (Scenario 1a, “CFB#=MSRN method”) ................................................... 40
29 Figure 41: CFB invocation (Scenario 1b, “AbsentSubscriber method”) ............................................ 42
30 Figure 42: CFB invocation (Scenario 2, without OR) ......................................................................... 43
31 Figure 43: CFNRy invocation (Scenario 1, without OR)..................................................................... 46
32 Figure 44: CFNRc invocation (Scenario 1) ......................................................................................... 48
2-viii
X.S0023
1 Figure 45: CFNRc invocation (Scenario 2, without OR)..................................................................... 49
2 Figure 46: CFU registration ................................................................................................................. 51
3 Figure 47: CFU deregistration (erasure) ............................................................................................. 52
4 Figure 48: CFU activation .................................................................................................................... 53
5 Figure 49: CFU deactivation................................................................................................................ 54
6 Figure 50: CFU invocation ................................................................................................................... 55
7 Figure 51: Obtaining forward-to numbers ........................................................................................... 56
8 Figure 52: CFB registration.................................................................................................................. 57
9 Figure 53: CFB deregistration (erasure) ............................................................................................. 59
10 Figure 54: CFB activation .................................................................................................................... 61
11 Figure 55: CFB deactivation ................................................................................................................ 63
12 Figure 57: CFNA invocation (Scenario 1, without OR)....................................................................... 67
13 Figure 58: Optimal Routing with Late Call Forwarding (ANSI-41 Foreign Mode) Success
14 Case.............................................................................................................................. 69
15 Figure 59: Optimal Routing with Late Call Forwarding (ANSI-41 Foreign Mode) Failure
16 Case.............................................................................................................................. 72
17 Figure 60: Optimal Routing with Late Call Forwarding (GSM Foreign Mode) Success Case.......... 73
18 Figure 61: Optimal Routing with Late Call Forwarding (GSM Foreign Mode) Failure Case ............ 75
19 Figure 62: ANSI-41 Foreign Mode Call Waiting Activation ................................................................ 76
20 Figure 63: ANSI-41 Foreign Mode Unsuccessful Call Waiting Activation ......................................... 78
21 Figure 64: GSM Foreign Mode Call Waiting Activation...................................................................... 79
22 Figure 65: ANSI-41 Foreign Mode Call Waiting Deactivation............................................................ 81
23 Figure 66: GSM Foreign Mode Call Waiting Deactivation ................................................................. 83
24 Figure 67: Calling number/ line identification presentation: mobile station or fixed terminal to
25 mobile station – GSM Foreign Mode........................................................................... 85
26 Figure 68: Calling number/ line identification presentation: mobile station or fixed terminal to
27 mobile station – ANSI-41 Foreign Mode ..................................................................... 87
28 Figure 69: Activation of Call Restriction - GSM Foreign Mode .......................................................... 90
29 Figure 70: Activation of Call Barring – ANSI-41 Foreign Mode ......................................................... 91
30 Figure 71: Invocation of Barring of Roaming – GSM Foreign Mode ................................................ 92
31 Figure 72: Invocation of Barring of Roaming – ANSI-41 Foreign Mode ............................................ 93
32 Figure 73: Invocation of Barring of Supplementary Service Control – GSM Foreign Mode............. 94
33 Figure 74: Invocation of Barring of Supplementary Services Management – ANSI-41

34 Foreign Mode ............................................................................................................... 95
2-ix
X.S0023
1 Figure 75: Short Message from a TDMA or CDMA CMT phone to a GHOST or WEMT
2 mobile station, both in native mode............................................................................. 97
3 Figure 76: Short Message from a GHOST or WEMT mobile station to a TDMA CMT or
4 CDMA CMT Phone, both in native mode.................................................................... 98
5 Figure 77: Successful Mobile Terminating ANSI-41SMS (CMT) mapped to GSM SMS.................. 99
6 Figure 78: Successful Mobile Terminating ANSI-41SMS (GHOST/WEMT) mapped to GSM

7 SMS ............................................................................................................................ 101
8 Figure 79: Unsuccessful Mobile Terminated Delivery (Failure at MSC).......................................... 102
9 Figure 80: Unsuccessful Mobile Terminated Delivery (Failure at IIF) ............................................. 104
10 Figure 81: Alerting for an ANSI-41Subscriber in GSM Foreign Mode............................................. 105
11 Figure 82: Successful GSM SMS mapped to ANSI-41(CMT) SMS ................................................ 106
12 Figure 83: Successful GSM SMS mapped to ANSI-41(GHOST/WEMT) SMS............................... 108
13 Figure 84: Successful GSM SMS mapped to ANSI-41SMS (Failure at MS) .................................. 110
14 Figure 85: Unsuccessful Delivery to GSM Subscriber (Postponed at MSC) .................................. 112
15 Figure 86: Unsuccessful Delivery to GSM Subscriber (Failure at IIF)............................................. 114
16 Figure 87: Alerting for a GSM Subscriber in ANSI-41 Foreign Mode.............................................. 115
17 Figure 88: Successful Mobile Originated Delivery............................................................................ 116
18 Figure 89: Unsuccessful Mobile Originated (Failure at MC) ............................................................ 117
19 Figure 90: Unsuccessful Mobile Originated (Failure at IIF).............................................................. 118
20 Figure 91: Successful Mobile Originated Delivery – ANSI-41 Foreign Mode ................................. 119
21 Figure 92: Successful Mobile Originated (Failure at SMSC) – ANSI-41 Foreign Mode ................. 120
22 Figure 93: Unsuccessful Mobile Originated (Failure at IIF) – ANSI-41 Foreign Mode ................... 121
23 Figure 94: Indicator in ANSI-41 Registration Notification Return Result mapped to GSM
24 SMS ............................................................................................................................ 123
25 Figure 95: ANSI-41 Qualification Directive mapped to GSM SMS ................................................. 125
26 Figure 96: Handling when GSM MSC/VLR only supports GSM Phase 1 (MAP V1) ...................... 127
27 Figure 97: Handling at SMS delivery failure at the IIF..................................................................... 129
28 Figure 98: Handling at SMS delivery failure at the MSC/VLR or at the MS ................................... 130
29 Figure 99: GSM SMS mapped to ANSI-41 Qualification Directive .................................................. 132
30 Figure 100: GSM SMS mapped to ANSI-41 using GHOST/WEMT Teleservice ............................ 134
31 Figure 101: Clearing of MWN Information after Retrieval of Messages while in ANSI-41
32 Foreign mode – Qualdir Method................................................................................ 136
33 Figure 102: Handling at SMS delivery failure at the IIF.................................................................... 138
34 Figure 103: Handling at SMS delivery failure at the MSC/VLR Qualdir Method............................. 140
2-x
X.S0023
1 Figure 104: Handling at SMS delivery failure at the MSC/VLR – GHOST/WEMT SMS
2 Method ........................................................................................................................ 142
3 Figure 105: GSM SMS mapped to ANSI-41 Qualification Directive and to Registration
4 Notification Return Result .......................................................................................... 144
5 Figure 106: GPRS Attach (Option1: with timer)................................................................................ 149
6 Figure 107: GPRS Attach (Option 2: without timer) ......................................................................... 150
7 Figure 108: GPRS Attach when currently registered in ANSI-41 (Option 1: with timer)................. 152
8 Figure 109: GPRS Attach when currently registered in ANSI-41 (Option 2: without timer)............ 154
9 Figure 112: GPRS Attach when GSM CS Attached......................................................................... 160
10 Figure 113: Combined GPRS and GSM attach (Option 1: With timer). .......................................... 162
11 Figure 114: Combined GPRS and GSM attach (Option 2: Without timer and without
12 support for multiple MSCIDs). ................................................................................... 164
13 Figure 115: Combined GPRS and GSM attach (Option 3: IIF supports multiple MSCIDs)............ 166
14 Figure 116: Combined Inter-SGSN RA/LA update........................................................................... 169
15 Figure 117: Inter-SGSN routing area update when GSM CS and GPRS Attached
16 (MSC remains constant) ............................................................................................ 172
17 Figure 118: Combined Attach when registered on a ANSI-41 MSC (Option 1: With timer) ........... 174
18 Figure 119: Combined attach when registered on a ANSI-41 MSC (Option 2: without timer ) ...... 176
19 Figure 120: MS in GSM Foreign Mode Performing GPRS Detach Followed by Purge.................. 180
20 Figure 121: IIF - Initiated Detach....................................................................................................... 181
21 Figure 122: Successful Mobile Terminating ANSI-41SMS (CMT) mapped to GSM SMS............. 182
22 Figure 123: Successful Mobile Terminating ANSI-41SMS (GHOST/WEMT) mapped to

23 GSM SMS................................................................................................................... 184
24 Figure 124: Unsuccessful Mobile Terminated Delivery (Failure at SGSN) ..................................... 185
25 Figure 125: Unsuccessful Mobile Terminated Delivery (Failure at IIF) ........................................... 187
26 Figure 126: Alerting for an ANSI-41Subscriber in GSM Foreign Mode........................................... 188
27 Figure 127: Successful Mobile Originated Delivery......................................................................... 189
28 Figure 128: Unsuccessful Mobile Originated Delivery (Failure at MC)............................................ 190
29 Figure 129: Unsuccessful Mobile Originated (Failure at IIF)............................................................ 191
30 Figure 130: Indicator in ANSI-41 Registration Notification Return Result mapped to GSM
31 SMS ............................................................................................................................ 193
32 Figure 131: ANSI-41 Qualification Directive mapped to GSM SMS ................................................ 195
33 Figure 132: Handling at SMS delivery failure at the SGSN or at the MS ........................................ 197
34 Figure 133: Call Delivery to ANSI-41Subscriber Roaming in GSM/GPRS Network....................... 199
35 Figure 134: MS Notification of a “Missed” Call via SMS .................................................................. 201
2-xi
X.S0023
2 Foreword
4 This standard addresses the interworking and interoperability between TIA/EIA IS41 MAP and GSM
6 standard is to achieve fully automatic, two-way interoperability between the heterogeneous networks.
7 Services supported by this standard are described along with the associated information flows and
8 message mappings. However, not all services and associated capabilities of ANSI-41 MAP and GSM
9 MAP are supported by this standard. In general the attempt has been to focus on the key subscriber
10 services needed in the market.
11 The focus of the first release of this standard was on common GSM and ANSI-136 TDMA services
13 interoperability is multi-mode mobile stations with an enhanced SIM card for roaming between
14 ANSI-136, GSM, and AMPS networks.
16 MAP to achieve the described interworking and interoperability. However, due to differences between
17 the services and associated capabilities of the MAP protocols, complete and fully transparent
18 interoperability may not have been achieved for some services. Future releases of this standard may
19 require changes to ANSI-41 MAP, GSM MAP and the associated services to achieve full
20 transparency while roaming between the different networks.
21 Existing ANSI-41 and GSM standard specifications cover the use and value of timers controlling the
22 various operations. Therefore, these timers are not part of this standard. However, care should be
23 taken when allocating actual timer values in order to support interoperability between ANSI-41 MAP
24 and GSM MAP.
25 Aspects of TIA/EIA-136 Rev C have been incorporated into this standard.
26 Revision A adds GPRS service capability in GSM Foreign Mode.
27 Revison B adds two way roaming between GSM and CDMA systems.
2-xii
X.S0023
1 1 Introduction
2 1.1 General
4 GSM), interworking and interoperability functions are required to support the subscriber and enable
5 service. This standard describes an Interworking and Interoperability Function (IIF) to support this
6 cross-technology roaming between ANSI-41 and GSM networks. The IIF supports a multi-mode
7 mobile station with a removable Subscriber Identity Module (SIM). The standard also defines the
8 required network message mappings between ANSI-41 MAP and GSM MAP to support the mobile
9 terminal and associated services.
10 This standard includes the support of cross-technology roaming from an ANSI-41 based network to
11 a GPRS network. The GPRS network may be coupled with a GSM network. This feature requires
12 enhancement to the Interworking and Interoperability Function (IIF) which supports a multi-mode
13 mobile station and Subscriber Identity Module (SIM) with GPRS functionality.
14 Optionally, the IIF may support one way-roaming only from CDMA to GSM network. In this case
15 since no data is provisioned at the IIF level, it must generate the GSM triplets using as input the
16 authentication parameters returned by the ANSI-41 HLR/AC, and the ANSI-41 HLR/AC must be
17 compliant with PN-4925 (to be published as TIA/EIA-868 [11]). All the changes are made on the
18 assumption the new requirements for UIM/handsets are implemented. (Annex B)
19 2 Purpose
20 The purpose of this standard is to define and describe the functions necessary for roaming between
21 ANSI-41 MAP [2] and GSM MAP [4] based networks in the support of roaming subscribers. This
22 includes a capability to allow a subscriber to an ANSI-41 based network (e.g., an ANSI-41 TDMA or
23 CDMA native subscriber) with a mobile terminal supporting GPRS service to roam to a GPRS
24 network in GSM Foreign Mode.
25 3 Scope
26 The scope of this standard are the services, information flows and message mappings which
28 ANSI-41 MAP and GSM MAP networks.
29 The scope of this volume describes the “Information Flows” and addresses the functionality required
30 to support GSM and ANSI-41 network interoperability.
2-1
X.S0023
1 4 Stage 2 Information Flows

2 4.1 Location Registration
3 4.1.1 Location Registration in GSM Foreign Mode
4 4.1.1.1 MS registers in a GSM network when previously registered in an ANSI-41 network
5 When an ANSI-41subscriber registers in a GSM network, when previously registered in an ANSI-41

6 network, the MS performs a location update using the IMSI as shown in Figure 1. The IIF emulates
7 both a GSM HLR/AuC and an ANSI-41 VLR in this case.
MSC/ HLR MSC/

MS IIF
VLR VLR
Update Location Req
a
(IMSI)
Authentication Info b
Authentication Info Ack
c
Authentication Req
d
Authentication Res e
Update Location Req
f
(IMSI)
REGNOT
g
(MIN/IMSI)
REGCANC h
regcanc
i
regnot j
Insert Sub Data

k
Insert Sub Data Ack

l
Update Location Ack

m
Update Location Ack

n
GSM NETWORK ANSI-41 NETWORK
9 Figure 1: Registration on a GSM Network – GSM Foreign Mode
2-2
X.S0023
1 a. MS powers up and registers in a GSM network. The MS sends an Update Location Request
2 (which includes the IMSI) to the network.
3 b. If the serving VLR does not have authentication information in order to perform
4 authentication i.e. authentication triplets, it requests authentication information from the IIF.
5 The IIF emulates a GSM HLR/AuC in this case.
6 c. The IIF returns the necessary authentication information.
7 d. VLR initiates authentication towards the MS.
8 e. MS responds to the authentication request.
9 f. VLR initiates Location Updating towards the IIF. The Update Location Request contains the
10 IMSI.
11 g. The IIF translates the GSM MAP Update Location Request into an ANSI-41 MAP REGNOT
12 and sends the REGNOT to the subscribers home HLR. The IIF is emulating an ANSI-41
13 VLR when it sends the REGNOT. If necessary, the subscriber IMSI in the Update Location
14 Request is mapped to the associated MIN.
15 If SIM-based roaming is authorized, an initially provisioned, fixed ESN for this subscriber
16 shall be passed in the REGNOT to the subscriber’s HLR. This ESN may not match the
17 currently validated dynamic ESN for this subscriber, but the HLR shall also accept this fixed
18 ESN for this subscriber.
19 h. The HLR updates its location information and deletes the previous VLR record by sending a
20 REGCANC to the previous VLR.
21 i. The VLR acknowledges the REGCANC
22 j. The HLR returns an acknowledgement to the REGNOT (regnot)
23 k. When the IIF receives the regnot, it initiates the GSM MAP Insert Subscriber Data
24 Procedure towards the serving VLR. This procedure is used to download subscriber data to
25 the serving VLR. Multiple Insert Subscriber Data transactions may be necessary to
26 complete the transfer of subscriber data to the VLR.
27 l. The VLR acknowledges the Insert Subscriber Data operation(s).
28 m. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the
29 IIF returns an acknowledgement for the Update Location Request.
2-3
X.S0023
1 4.1.1.2 MS location updates in a different MSC/VLR
2 When an ANSI-41subscriber roams within a GSM PLMN and registers in a different MSC/VLR area,
3 the MS performs a location update using the IMSI as shown in Figure 2.
MSC/ PVLR HLR

MS IIF
VLR
Update Location Req
(IMSI) a
c
Authentication Req
d
Update Location Req
f
(IMSI)
Cancel Location
g
Cancel Location Ack
h
REGNOT
i
regnot
j
Insert Sub Data

k
Insert Sub Data Ack l
Update Location Ack

m
Update Location Ack
n
5 Figure 2: Registration in a different MSC/VLR – GSM Foreign Mode

6 a. MS powers up and registers in a different MSC/VLR in the same GSM network. The MS
7 sends an Update Location Request (which includes the IMSI) to the network.
8
9 b. If the serving VLR does not have authentication information in order to perform authentication
10 i.e. authentication triplets, it requests authentication information from the IIF. The IIF emulates
11 a GSM HLR/AuC in this case.
12
13 c. The IIF returns the necessary authentication information.
14
15 d. VLR initiates authentication towards the MS.
16
18
2-4
X.S0023
1
2 f. VLR initiates Location Updating towards the IIF. The Update Location Request contains the
3 IMSI.
4
5 g. The IIF sends a Cancel Location request to the previous VLR (PVLR) that the subscriber was
6 registered on.
7
8 h. The PVLR deletes the subscriber record and acknowledges the request.
9
10 i. Optionally, the IIF may send a Registration Notification to the HLR to indicate the changed
11 location.
12
13 If SIM-based roaming is authorized, an initially provisioned, fixed ESN for this subscriber shall
14 be passed in the REGNOT to the subscriber’s HLR. This ESN may not match the currently
15 validated dynamic ESN for this subscriber, but the HLR shall also accept this fixed ESN for
16 this subscriber.
17
18 j. The HLR acknowledges the REGNOT.
19
20 k. The IIF initiates the GSM MAP Insert Subscriber Data Procedure towards the serving VLR.
21 This procedure is used to download subscriber data to the new serving VLR. Multiple Insert
22 Subscriber Data transactions may be necessary to complete the transfer of subscriber data to
23 the VLR.
24
25 l. The VLR acknowledges the Insert Subscriber Data operation(s).
26
28 IIF returns an acknowledgement for the Update Location Request.
29
30 n. The new MSC/VLR acknowledges the location update request from the MS.
31 Note: If the MS performs a location update in the same MSC/VLR area, either the IMSI or
32 TIMSI may be used as described in GSM 09.02 [4]. The IIF however, is not informed.
33 4.1.1.3 IMSI Detach
34 If an MS powers off while operating in GSM Foreign mode, and the IMSI Detach procedure is
35 supported, it shall perform an IMSI Detach as described in GSM 09.02 [4]. Neither the IIF or the
36 home HLR is informed.
37 Terminating calls intended for this ANSI-41 subscriber, shall therefore be treated in the home HLR
38 as if that subscriber was available.
39 If the MS remains inactive for an extended period of time (determined by operator), the VLR may
40 delete the subscriber record associated with that MS and shall send an MS PURGE to the IIF. In
41 this case, the IIF shall send an MS INACTIVE towards the ANSI-41 HLR and the ANSI-41 HLR shall
42 follow the procedures outlined in ANSI-41 [2]. Terminating calls intended for this ANSI-41subscriber
43 shall be treated in the home HLR as if that subscriber was not available.
2-5
X.S0023
1 4.1.1.4 IMSI Attach
2 If an MS powers on and registers on the same MSC/VLR (that has not deleted the subscriber
3 record) while operating in GSM Foreign mode and the IMSI Attach procedure is supported, it shall
4 perform an IMSI Attach as described in GSM 09.02 [4]. Neither the IIF or the home HLR is informed.
5 If an MS powers on and registers on the same MSC/VLR (that has deleted the subscriber record),
6 while operating in GSM Foreign mode and the IMSI Attach procedure is supported, it shall perform
7 an IMSI Attach as described in GSM 09.02 [4]. The IIF shall be informed as shown in Section
8 4.1.1.2. (however the IIF shall not send a Cancel Location to the MSC/VLR as it is the same
9 MSC/VLR).
10 If an MS powers on and registers on a different MSC/VLR, while operating in GSM Foreign mode
11 and the IMSI Attach procedure is supported, it shall perform an IMSI Attach as described in GSM
12 09.02 [4]. The IIF shall be informed as shown in Section 4.1.1.2.
2-6
X.S0023
1 4.1.2 Location Registration in ANSI-41 Foreign Mode

2 4.1.2.1 MS registers in an ANSI-41 network when previously registered in a GSM network
3 When a GSM subscriber registers in an ANSI-41 network, when previously registered in a GSM
4 network, the MS performs a location update using an IMSI or MIN as shown in Figure 3. The IIF
5 emulates both an ANSI-41 HLR and a GSM VLR in this case.
MSC/ HLR MSC/

MS IIF
VLR VLR
Registration
a
(MIN/IMSI)
AUTH REQ
b
Auth req
c
REGNOT
d
Update Location Req

e
(IMSI)
Cancel Location
f
Cancel Loc Ack

g
Update Location Ack
h
regnot
i
Reg_ack
j
ANSI-41 NETWORK GSM NETWORK
7 Figure 3: Registration on an ANSI-41 network – ANSI-41 Foreign Mode

8
9 a. Upon MS power up, if global authentication is active, the MS first sends an Authentication
10 message to the network. The MS then sends a Registration message (which includes the
11 IMSI or MIN) to the network.
12
13 b. If global authentication is active upon registration, the serving VLR initiates an AUTHREQ
14 towards the IIF. The IIF emulates an ANSI-41 HLR/AC in this case.
15
16 The reported ESN for this subscriber shall be dynamic to support SIM-based roaming. The
17 IIF shall authenticate the subscriber using this reported ESN.
18
2-7
X.S0023
1 c. The IIF acknowledges the authentication request. If authentication is successful, the IIF shall
2 store the reported ESN as the currently validated dynamic ESN for this subscriber. The
3 currently validated dynamic ESN shall be maintained by the ANSI-41 HLR emulation function
4 in the IIF.
5
6 d. VLR sends a REGNOT message to the IIF.
7
8 e. The IIF translates the ANSI-41 MAP REGNOT into a GSM MAP Update Location Request
9 (which includes the IMSI) and sends the Update Location Request to the subscribers home
10 HLR. The IIF is emulating a GSM VLR when it sends the Update Location Request.
11
12 f. The HLR updates its location information and deletes the previous VLR record by sending a
13 Cancel Location to the previous VLR.
14
15 g. The VLR acknowledges the Cancel Location. Note: The GSM Insert Subscriber data
16 procedure between the HLR and the IIF takes place between steps g and h.
17
18 h. The HLR acknowledges the Update Location Request
19
20 i. The IIF acknowledges the REGNOT. The acknowledgement also contains the subscriber data
21 download to the new serving VLR.
22
23 j. The MSC/VLR acknowledges the Registration message from the MS.
2-8
X.S0023
1 4.1.2.2 MS location updates in a different MSC/VLR
2 When a GSM subscriber roams within an ANSI-41 network and registers in a different MSC/VLR
3 area, the MS performs a location update using an IMSI or MIN as shown in Figure 4.
MSC/ PVLR HLR

MS IIF
VLR
Registration
a
(MIN/IMSI)
AUTH REQ
b
Auth req
c
REGNOT
d
REGCANC
e
(MIN)
regcanc
f
Location Update Req
g
Location Update Ack h
regnot i
Reg_ack j
5 Figure 4: Registration in a different MSC/VLR – ANSI-41 Foreign Mode

6 a. MS powers up and registers in a new MSC/VLR in the same ANSI-41 network. If global
7 authentication is active, the MS sends an Authentication message to the network. The MS
8 also sends a Registration message (which includes the IMSI / MIN) to the network.
9
10 b. If global authentication is active upon registration, the serving VLR initiates an AUTHREQ
11 towards the IIF. The IIF emulates an ANSI-41 HLR/AC in this case.
12
14 IIF shall authenticate the subscriber using this reported ESN.
15
16 c. The IIF acknowledges the authentication request. If authentication is successful, the IIF shall
17 store the reported ESN as the currently validated dynamic ESN for this subscriber.
18
2-9
X.S0023
1 The currently validated dynamic ESN shall be maintained by the ANSI-41 HLR emulation
2 function in the IIF.
3
4 d. VLR sends a REGNOT message to the IIF.
5
6 e. The IIF deletes the subscriber record in the previous VLR (PVLR), by sending a REGCANC to
7 the PVLR.
8
9 f. The PVLR acknowledges the REGCANC.
10
11 g. Optionally, the IIF may send an Update Location Request to the HLR to indicate the changed
12 location.
13
14 h. The HLR acknowledges the update location.
15
16 i. The IIF acknowledges the REGNOT.
17
18 j. The new serving MSC/VLR acknowledges the Registration message from the MS.
19
20 4.1.2.3 MS Powers Off
21 If a mobile station powers off while operating in ANSI-41 Foreign mode, the IIF receives an MS
22 INACTIVE message from the serving VLR. This results in the IIF setting the ‘IMSI Detached’ Flag.
23 If the MS remains inactive for an extended period of time (determined by operator), the IIF may
24 delete the subscriber record associated with that MS and send an MS Purge to the HLR.
25 4.1.2.4 MS Powers On
26 If a mobile station powers on and registers on an MSC/VLR, while operating in ANSI-41 Foreign
27 mode, normal registration procedures apply.
2-10
X.S0023
1 4.1.3 Location Registration in Native Mode

2 4.1.3.1 MS registers in an ANSI-41 network when previously registered in a GSM network
3 When an ANSI subscriber registers in an ANSI-41 network (Native Mode), when previously
4 registered in a GSM Network (Foreign Mode), the MS performs a location update and the temporary
5 subscriber data in the IIF is deleted as shown in figure 5.
MSC/ HLR IIF PVLR

MS
VLR
Registration
(MSID) a
AUTH REQ b
Auth req c
REGNOT d
(MSID)
REGCANC e
(MSID)
Cancel Location f
(IMSI)
Cancel Location Ack g
regcanc h
regnot
i
Reg_ack j
6
7
8 Figure 5: Registration in an ANSI-41 Network (Native Mode)

9 a. MS powers up and registers in a new MSC/VLR in an ANSI-41 network.
10 If global authentication is active upon registration, the serving VLR initiates an AUTHREQ
11 towards the ANSI-41 HLR.
13 HLR shall authenticate the subscriber using this reported ESN.
14
15 c. The HLR acknowledges the authentication request. If authentication is successful, the HLR
16 shall store the reported ESN as the currently validated dynamic ESN for this subscriber.
17
18 d. The serving VLR sends a REGNOT to the HLR.
19
20 e. The HLR sends a REGCANC to the IIF.
2-11
X.S0023
1
2 f. The IIF deletes the temporary subscriber data and sends a Cancel Location to the previous VLR
3 in the GSM network.
4
5 g. The previous VLR deletes the relevant subscriber data and acknowledges the request.
6
7 h. The IIF acknowledges the REGCANC.
8
9 i. HLR updates the new serving VLR.
10
11 j. The VLR acknowledges the update towards the MS.
2-12
X.S0023
1 4.1.3.2 MS registers in a GSM network when previously registered in an ANSI-41 network
2 When a GSM subscriber registers in a GSM network (Native Mode), when previously registered in
3 an ANSI-41 Network (Foreign Mode), the MS performs a location update and the temporary
4 subscriber data in the IIF is deleted as shown in figure 6.
MSC/ PVLR
MS HLR IIF
VLR
Update Location Req

a
(IMSI)
Update Location Req b
(IMSI)
Cancel Location
c
(IMSI)
REGCANC
d
(MSID)
regcanc e
Cancel Location Ack

f
Insert Sub Data

g
Insert Sub Data Ack

h
Update Location Ack

i
Update Location Ack

j
5
6 Figure 6: Registration in a GSM Network (Native Mode)
7 a. MS powers up and registers in a new MSC/VLR in a GSM network.
8
9 b. The serving VLR sends an Update Location Request to the HLR.
10
11 c. The HLR sends a Cancel Location to the IIF.
12
13 d. The IIF deletes the temporary subscriber data and sends a REGCANC to the previous VLR in
14 the ANSI-41 network.
15
16 e. The Previous VLR deletes the relevant subscriber data and acknowledges the request.
17
18 f. The IIF acknowledges the Cancel Location Request.
19
20 g. HLR updates the new serving VLR.
2-13
X.S0023
1
2 h. The VLR acknowledges the update.
3
4 i. The HLR acknowledges the Update Location Request.
5
6 j. The VLR acknowledges the Update Location Request towards the MS.
7
2-14
X.S0023
1 4.2 Fault Recovery Procedures

2 After a fault of a location register, the fault recovery procedures ensure that the subscriber data in
3 the VLR becomes consistent with the subscriber data that are stored in the IIF (emulating an HLR)
4 or that subscriber data in the IIF (emulating a VLR) becomes consistent with the subscriber data
5 that are stored in the HLR for the MS concerned, and that the location information in the IIF
6 (emulating an HLR) and VLR or the HLR and IIF (emulating a VLR) reflect accurately the current
7 location of the MS.
8 Existing fault recovery procedures described in GSM 09.02 [4] or ANSI-41D [2] are directly
9 applicable to the IIF, while the IIF is emulating a GSM or ANSI 41 functional entity.
10 4.2.1 Fault Recovery Procedures in GSM Foreign Mode

11 4.2.1.1 Recovery from Failure at the ANSI-41 HLR
12 When the ANSI-41 HLR returns to a stable state after suffering a failure, it shall send the IIF
13 (emulating an ANSI-41 VLR) an UnreliableRoamerDataDirective message (UNRELDIR) as
14 described in ANSI 41.3 D [2], informing the IIF that it has experienced a failure which has rendered
15 the HLR’s roaming MS data unreliable. Figure 7 below shows the call flow.
16 When the roaming MS next makes radio contact, the serving GSM VLR shall initiate the location
17 updating procedure towards the IIF.
VLR HLR
IIF
UNRELDIR
a
unreldir
b
RESET
c
18
19 Figure 7: Failure at the ANSI-41 HLR (GSM Foreign Mode)

20
21 a. HLR returns to stable state following a failure and sends an UNRELDIR towards the IIF.
22
23 b. The IIF acknowledges the request and removes all the temporary subscriber data of all the MSs
24 associated with that HLR from its memory.
25
26 c. The IIF may reload its data from a non-volatile backup (optional) and shall send a RESET
27 towards each of the serving VLRs. The RESET message contains a unique identity, identifying
28 the ANSI-41 HLR that failed and that is connected to the IIF.
29
2-15
X.S0023
1 When the MS next establishes authenticated radio contact (including a mobile originated call
2 attempt), the VLR initiates location updating towards the IIF (See 4.1.1).
3 4.2.1.2 Recovery from Failure at the IIF
4 If the IIF suffers a failure, it shall follow the recovery procedure described in GSM 09.02 [4] section
5 19.3.2 (i.e. IIF is acting like a GSM HLR). As part of the recovery procedure, the IIF shall send all
6 the serving GSM VLRs a RESET message for each associated ANSI-41 HLR as shown in step a) in
7 Figure 8. The message shall contain a unique identifier for the ANSI-41 HLR. In addition, the IIF
8 shall send a BULKDEREG to all affected ANSI-41 HLRs (i.e. IIF is acting like an ANSI-41 VLR).
VLR HLR
IIF
RESET
a
BULKDEREG
b
bulkdereg
c
9 Figure 8: IIF Failure (GSM Foreign Mode)

10 a. The IIF sends a RESET towards each of the affected VLRs, containing a unique identity,
11 identifying the ANSI-41 HLRs connected to the IIF.
12
13 b. The IIF sends a BULKDEREG towards all the affected ANSI-41 HLRs. On reception of the
14 BULKDEREG the HLR(s) follow(s) the procedures as described in ANSI-41.6D [2].
15
16 c. The ANSI-41 HLR(s) responds with a bulkdereg.
17
19 attempt), the VLR initiates location updating towards the IIF (See 4.1.1).
20
21
2-16
X.S0023
1 4.2.1.3 Recovery from Failure at the serving GSM VLR
2 If the VLR suffers a failure, it shall follow the recovery procedure described in GSM 09.02 [4] section
3 19.3.1. As part of the recovery procedure, when a MS next establishes authenticated radio contact,
4 the VLR shall initiate location updating towards the IIF (See 4.1.1).
5 If the VLR receives a request for a roaming number from the IIF following a failure, the VLR shall
6 send a RESTORE DATA message to the IIF as shown in Figure 9.
VLR HLR
IIF
ROUTREQ
a
PROVIDE ROAMING NO
b
PROVIDE ROAMING NO ACK c
routreq
d
RESTORE DATA e
INSERT SUB DATA
f
INSERT SUB DATA ACK

g
RESTORE DATA ACK

h
ANSI-41 NETWORK
GSM NETWORK
7 Figure 9: Terminating Call Flow following a GSM VLR Failure

8
9 a. Terminating call arrives for MS following a GSM VLR failure.

10
11 b,c,d The IIF follows normal mobile terminated call handling procedures (See 4.5.2.1).
12
13 e. The VLR may request more authentication sets prior to sending Restore Data to the IIF to
14 request subscriber data.
15
16 f. The IIF downloads subscriber data to the VLR.
17 g. The VLR acknowledges the operation.
18 h. The IIF acknowledges the Restore Data Operation.
2-17
X.S0023
1 4.2.2 Fault Recovery Procedures in ANSI-41 Foreign Mode

2 4.2.2.1 Recovery from Failure at the GSM HLR
3 When a GSM HLR undergoes a restart, it shall follow the procedures described in GSM 09.02 [4]
4 section 19.3.2. As part of the recovery procedure, the HLR sends the IIF a RESET message,
5 informing the IIF that it has experienced a failure, which has rendered the HLR’s roaming MS data
6 unreliable. When the roaming MS next makes radio contact, the serving ANSI-41 VLR shall initiate
7 the location updating procedure towards the IIF. Figure 10 below shows the call flow.
HLR IIF VLR
RESET
a
UNRELDIR
b
unreldir
c
ANSI-41 NETWORK
GSM NETWORK
8
9 Figure 10: Failure at a GSM HLR (ANSI-41 Foreign Mode)
10
11 a. The HLR follows the recovery procedures described in GSM 09.02 [4] section 19.3.2. The
12 affected sends a RESET towards the IIF.
13
14 b. The IIF follows the procedures described in GSM 09.02 [4] section 19.3.2 on reception of the
15 RESET and sends an UNRELDIR towards each of the serving ANSI-41 VLRs. The UNRELDIR
16 message contains a unique identity, identifying the affected GSM HLR.
17
18 c. The VLR follows the procedures described in ANSI-41.3 [2] and ANSI-41.6 [2] and
19 acknowledges the UNRELDIR.
20
22 attempt), the VLR initiates location updating towards the IIF (See 4.1.2.1).
23
2-18
X.S0023
1 4.2.2.2 Recovery from Failure at the IIF
2 If the IIF suffers a failure, it shall follow the recovery procedure described in ANSI-41.6 [2] (i.e. IIF is
3 acting like an ANSI HLR). As part of the recovery procedure, the IIF shall send all the serving
4 ANSI-41 VLRs an UNRELDIR message for each associated GSM HLR as shown in steps b and c in
5 Figure 10. The message shall contain a unique identifier for the GSM HLR.
7 attempt), the VLR initiates location updating towards the IIF (See 4.1.2.2).
8 If following an IIF failure, the IIF receives a request for routing information, it shall send a RESTORE
9 DATA towards the requesting GSM HLR.
10 4.2.2.3 Recovery from Data Failure at the ANSI-41 VLR
11 If the ANSI-41 VLR suffers a failure, it shall follow the recovery procedure described in ANSI-41.6
12 [2]. As part of the recovery procedure, when an MS next establishes authenticated radio contact,
13 the VLR shall initiate location updating towards the IIF.
14 Upon receipt of a BULKDEREG, the IIF shall clear the location pointer for those MSs that were
15 registered on that VLR. If following the reception of a BULKDEREG, the IIF receives a request for
16 routing information, the terminating call towards the MS shall not be possible until the MS has
17 performed a successful location registration.
2-19
X.S0023
1 4.4 Subscriber Data Management

2 4.4.1 Subscriber Data Management Procedures in ANSI-41 Foreign Mode
3 Two types of subscriber data management procedures are defined in GSM 09.02 [4]. These
4 procedures impact the GSM subscribers HLR, the IIF and the serving VLR when the subscriber is
5 operating in ANSI-41 Foreign Mode. For these procedures, only modification to temporary
6 subscriber data in the IIF is addressed. The procedures are (1) Subscriber Deletion and (2)
7 Subscriber Data Modification.
8 4.4.1.1 Subscriber Deletion
9 In this procedure, temporary subscriber data shall be removed from the HLR, IIF and the serving
10 MSC/VLR as shown in Figure 25.
MSC/ HLR OMC

IIF
VLR
Delete Subscriber
a
Cancel Location b
REGISTRATION_
CANCELLATION c
Registration_
cancellation
d
Cancel Location Ack

e
Subscriber Deleted
f
GSM NETWORK
ANSI-41 NETWORK
11 Figure 25: Subscriber Deletion – ANSI-41 Foreign Mode
12 a. Operations and Maintenance Center (OMC) initiates a request to delete a subscriber.
13 b. The HLR deletes the subscriber data from the HLR and sends a Cancel Location request to
14 the IIF.
15 c. The IIF deletes the temporary subscriber data from the IIF and sends a Registration
16 Cancellation to the serving MSC/VLR. The CancellationType in this operation shall be set to
17 “Discontinue” to tear down any active call.
18 d. The VLR deletes the subscriber data from the VLR and returns an acknowledgement to the
19 IIF.
2-20
X.S0023
1 e. The IIF acknowledges the cancel location request.
2 f. The HLR acknowledges the delete subscriber request.

3
4 4.4.1.2 Subscriber Data Modification
5 The OMC can modify subscriber data in several different ways e.g. withdrawal of a basic or
6 supplementary service, roaming modifications, data modifications to both HLR and VLR. Depending
7 on the data modification required, one of three MAP procedures is initiated from the HLR towards
8 the IIF. These procedures are described in more detail in GSM 09.02 [4].
9 4.4.1.2.1 Insert Subscriber Data Procedure
10 Where data is required to be modified in the HLR, IIF and the serving VLR, the HLR initiates the
11 Insert Subscriber Data Procedure towards the IIF as shown in Figure 26.
MSC/ HLR OMC

IIF
VLR
Modify Subscriber Data
a
Insert Subscriber Data

b
QUALDIR c
qualdir
d
Insert Subscriber Data Ack

e
Subscriber Data Modified

f
12 Figure 26: Insert Subscriber Data Procedure
13 a. OMC initiates a request to modify subscriber data.
14 b. The HLR modifies the subscriber data in the HLR and initiates the Insert Subscriber Data
15 Operation towards the IIF.
16 c. The IIF modifies the subscriber data in the IIF and sends a QUALDIR to the serving MSC/VLR.
17 There may be some cases where the subscriber data change cannot be mapped to an
18 associated ANSI-41subscriber profile modification. In this case, no QualDir operation shall be
19 initiated.
20 d. The serving MSC/VLR modifies the subscriber data and acknowledges the QUALDIR
2-21
X.S0023
1 e. The IIF acknowledges the Insert Subscriber Data Request.
2 f. The HLR acknowledges the request to modify subscriber data.

3
4 4.4.1.2.2 Delete Subscriber Data Procedure
5 If a basic or supplementary service is withdrawn, which requires a change to VLR data, the HLR
6 initiates the Delete Subscriber Data Procedure towards the IIF as shown in Figure 27.
MSC/ HLR OMC

IIF
VLR
a
Delete Subscriber Data

b
QUALDIR
c
qualdir
d
Delete Subscriber Data Ack

e

f
8 Figure 27: Delete Subscriber Data Procedure
10 b. The HLR deletes the relevant subscriber data in the HLR and initiates the Delete Subscriber
11 Data Operation towards the IIF.
12 c. The IIF deletes the relevant subscriber data in the IIF and sends a QUALDIR to the serving
13 MSC/VLR. There may be some cases where the subscriber data deletion cannot be
14 mapped to an associated ANSI-41subscriber profile modification. In this case, no QualDir
15 operation shall be initiated.
16 d. The serving MSC/VLR deletes the relevant subscriber data and acknowledges the
17 QUALDIR.
18 e. The IIF acknowledges the Delete Subscriber Data Request.
2-22
X.S0023
1 4.4.1.2.3 Cancel Location Procedure
2 If roaming modifications are required, which require the subscriber to be removed from the VLR
3 data, the HLR initiates the Cancel Location Procedure towards the IIF as shown in Figure 28.
MSC/ HLR OMC

IIF
VLR
a
Cancel Location
b
REGISTRATION_
CANCELLATION c
Registration_
cancellation
d
Cancel Location Ack

e

f
GSM NETWORK
ANSI-41 NETWORK
4 Figure 28: Cancel Location Procedure
6 b. The HLR deletes the relevant subscriber data in the HLR and initiates the Cancel Location
7 Operation towards the IIF.
8 c. The IIF deletes the temporary subscriber data in the IIF and sends a REGCANC to the
9 serving MSC/VLR.
10 d. The serving MSC/VLR deletes the relevant subscriber data and acknowledges the
11 REGCANC.
12 e. The IIF acknowledges the Cancel Location Request.
2-23
X.S0023
1 4.4.2 Subscriber Data Management Procedures in GSM Foreign Mode

2 Subscriber data management procedures are defined in ANSI 41-D, Section 6. These procedures
3 impact the ANSI-41subscribers HLR, the IIF and the serving VLR when the subscriber is operating
4 in GSM Foreign Mode. For these procedures, only modification to temporary subscriber data in the
5 IIF is addressed.
6 4.4.2.1 Subscriber Deletion
7 The OMC may request that subscriber data relating to a particular subscriber is removed from the
8 HLR. In this case, subscriber data shall also be removed from the IIF and the serving MSC/VLR as
9 shown in Figure 29.
10
MSC/ HLR OMC

IIF
VLR
Sub Data Delete
a
REGCANC
b
Cancel Location
c
Cancel Location Ack

d
regcanc
e
Sub Data Delete Ack

f
ANSI-41 NETWORK
GSM NETWORK
11 Figure 29: Subscriber Deletion- GSM Foreign Mode

12 a. OMC initiates a request to delete a subscriber
13 b. The HLR deletes the subscriber data from the HLR and sends a REGCANC to the IIF.
14 c. The IIF deletes the temporary subscriber data from the IIF and sends a Cancel Location to the
15 serving VLR.
16 d. The VLR acknowledges the cancel location
17 e. The IIF acknowledges the REGCANC
18 f. The HLR acknowledges the request to delete subscriber data.
2-24
X.S0023
1 4.4.2.2 Modifying Subscriber Data
2 The OMC may request that subscriber data relating to a particular subscriber is modified (e.g., the
3 authorization or de-authorization of a particular feature). In this case, subscriber data may also be
4 required to be modified in the IIF and the serving MSC/VLR as shown in Figure 30.
MSC/ HLR OMC

IIF
VLR
Sub Data Change
a
QUALDIR
b
Insert Sub Data

c
Insert Sub Data Ack

d
qualdir
e
Sub Data Change Ack

f
ANSI-41 NETWORK
GSM NETWORK
6 Figure 30: Subscriber Data Modification

7
8 a. OMC initiates a request to modify subscriber data
9 b. The HLR modifies the subscriber data from the HLR and sends a QUALDIR to the IIF.
10 c. The IIF modifies the temporary subscriber data and sends Insert Subscriber Data to the VLR if
11 for example, a feature has been authorized or activated.
12 Note: The IIF sends a Delete Subscriber Data message if for example, a feature has been
13 de-authorized or de-activated. There may be multiple ISD or DSD operations. There may be
14 some cases where the subscriber data change cannot be mapped to an associated GSM
15 subscriber profile modification. In this case, no ISD or DSD operation shall be initiated.
16 d. The VLR acknowledges the request
17 e. The IIF acknowledges the QUALDIR
18 f. The HLR acknowledges the request to modify subscriber data
19
2-25
X.S0023
1 4.5 Automatic Call Delivery

2 This section depicts the interactions between network entities in various situations related to GSM
3 and ANSI-41 foreign mode operation and automatic call delivery. These scenarios are not meant to
4 be exhaustive.
5 4.5.1 Automatic Call Delivery Activation/Deactivation

6 Activation and deactivation of call delivery is not required to be supported.
7 4.5.2 Automatic Call Delivery Invocation

8 Automatic call delivery is invoked when an incoming call attempt arrives for a subscriber who is
9 roaming. Call delivery scenarios for both the case in which an ANSI-41subscriber is roaming in a
10 GSM network and the case in which a GSM subscriber is roaming in an ANSI-41 network are
11 provided.
12 4.5.2.1 Call Delivery to ANSI-41Subscriber Roaming in GSM Network
Serving System
MSC/ HLR GSM

VLR IIF
MSC/
Incoming Call VLR
From PSTN
a
LOCREQ
b
ROUTREQ c
Provide Roaming No.

d
PRN Ack
e
routreq f
locreq
g
Call setup
h
13
14 Figure 31: Call Delivery to ANSI-41 Subscriber Roaming in a GSM Network
15 a. A call origination and the dialed MS address digits (i.e., directory number) are received by the
16 Originating MSC from the PSTN destined to a subscriber to the ANSI-41 network.
17 b. The Originating MSC sends a LOCREQ to the HLR associated with the called subscriber; this
18 association is made through the dialed MS address digits.
19 c. The HLR sends a ROUTREQ to the IIF emulating the VLR where the MS is registered.
20 d. The IIF forwards a Provide Roaming Number message to the VLR/GSM MSC where the MS is
21 registered. If necessary, mapping from MIN to IMSI is done by the IIF.
22 e. The VLR/GSM MSC returns a Provide Roaming Number Ack message to the IIF that includes
23 an MSRN.
2-26
X.S0023
1 f. The IIF returns a routreq message to the HLR that includes a TLDN (Temporary Local Directory
2 Number), set to the received MSRN, in the Digits (Destination) parameter. Note that the MSRN
3 is always in international format. It is assumed that the gateway MSC on the ANSI-41 side is
4 capable of supporting internationally formatted TLDNs.
5 g. When the routreq is received by the HLR, it returns a locreq to the Originating MSC. The locreq
6 includes routing information in the form of the TerminationList parameter, along with an
7 indication of the reason for extending the incoming call (i.e., for Call Delivery, in this case) in the
8 DMH_RedirectionIndicator parameter.
9 h. Upon receiving the locreq, the Originating MSC sets up a voice path to the Serving GSM MSC
10 (using a protocol such as SS7 ISUP).
2-27
X.S0023
1 4.5.2.2 Delivery to an ANSI-41Subscriber Roaming in a GSM Network – Unsuccessful Case
2 In the following scenario, call delivery to an ANSI-41subscriber roaming in a GSM network fails
3 during the processing of the Provide Roaming Number message (e.g., no roaming number is
4 available, absent subscriber).
ANSI-41 Home System Serving System
MSC/ HLR GSM

VLR IIF
MSC/
Incoming Call VLR
From PSTN
a
LOCREQ
b
ROUTREQ c
Provide Roaming No.

d
PRN Return Error
e
routreq Ret Error f

locreq Ret Error
g
5
6 Figure 32: Unsuccessful Call Delivery to an ANSI-41Subscriber Roaming in a GSM Network
8 Originating ANSI-41 MSC from the PSTN destined to a subscriber to the ANSI-41 network.
9 b. The Originating ANSI-41 MSC sends a LOCREQ message to the ANSI-41 HLR associated with
10 the called subscriber; this association is made through the dialed MS address digits.
11 c. The ANSI-41 HLR sends a ROUTREQ message to the IIF emulating the VLR where the MS is
12 registered. If necessary, mapping from IMSI to MIN is done beforehand by the IIF.
13 d. The IIF forwards a Provide Roaming Number message to the GSM VLR/MSC where the MS is
14 registered.
15 e. The GSM VLR/MSC determines that either no roaming numbers are available or subscriber is
16 not reachable and it replies with a PRN Return Error message.
17 f. The IIF sends a RoutingRequest RETURN ERROR message.
18 g. The ANSI-41 HLR sends a LocationRequest RETURN ERROR message.
2-28
X.S0023
1 4.5.2.3 Call Delivery to a GSM Subscriber Roaming in ANSI-41 Network – Successful Case
GSM Home System ANSI-41 Serving System

GSM
GSM
MSC/ IIF MSC/
HLR
VLR VLR
Incoming Call
From PSTN
a
Send Routing Info
b
Provide Roaming No. c
ROUTREQ
d
routreq
e
PRN Ack f
SRI Ack
g
Call setup
h
2
3 Figure 33: Call Delivery to GSM Subscriber Roaming in an ANSI-41 Network
5 Originating MSC from the PSTN destined to a subscriber to the GSM network.
6 b. The Gateway GSM MSC sends a Send Routing Information message to the GSM HLR
7 associated with the called subscriber; this association is made through the dialed MS address
8 digits.
9 c. The GSM HLR sends a Provide Roaming Number message to the IIF emulating the VLR where
10 the MS is registered. If necessary, mapping from IMSI to MIN is done beforehand by the IIF.
11 d. The IIF forwards a ROUTREQ message to the VLR/MSC where the MS is registered.
12 e. The serving VLR/ MSC returns a routreq message that includes a TLDN to the IIF.
13 f. The IIF returns a Provide Roaming Number Ack message that includes an MSRN (set to the
14 received TLDN) to the GSM HLR. If the TLDN is not received in international format, the IIF
15 shall first convert the TLDN to international format (by prepending the country code associated
16 with the serving system) before setting the MSRN equal to it.
17 g. When the Provide Roaming Number Ack is received by the GSM HLR, it returns a Send
18 Routing Information Ack message to the Gateway GSM MSC.
19 h. Upon receiving the Send Routing Information Ack message, the Gateway GSM MSC sets up a
20 voice path to the Serving MSC (using a protocol such as SS7 ISUP).
2-29
X.S0023
1 4.5.2.4 Call Delivery to a GSM Subscriber Roaming in ANSI-41 Network – Unsuccessful Case
2 In the following scenario, call delivery to a GSM subscriber roaming in an ANSI-41 network fails
3 because the user is either ‘not reachable’ as determined by the IIF or does not answer a page sent
4 by the serving system during the processing of the RouteRequest message, and call forwarding is
5 not active for the subscriber.
GSM Home System ANSI-41 Serving System
GSM GSM
MSC/ IIF MSC/
HLR
VLR VLR
Incoming Call
From PSTN
a
Send Routing Info
b
Provide Roaming No. c
ROUTREQ
d
routreq[ACCDEN]
e
PRN Ret Error f

SRI Ret Error
g
6
7 Figure 34: Unsuccessful Call Delivery to GSM Subscriber Roaming in an ANSI-41 Network
9 Originating MSC from the PSTN destined to a subscriber to the GSM network.
10 b. The Gateway GSM MSC sends a Send Routing Information message to the GSM HLR
11 associated with the called subscriber; this association is made through the dialed MS address
12 digits.
13 c. The GSM HLR sends a Provide Roaming Number message to the IIF emulating the VLR where
14 the MS is registered. If necessary, mapping from IMSI to MIN is done beforehand by the IIF. If
15 the IIF determines that the called subscriber is not reachable, it returns an absent subscriber
16 error as in step f.
17 d. If the IIF determines that the subscriber is reachable, it forwards a ROUTREQ message to the
18 VLR/MSC where the MS is registered.
19 e. The VLR/MSC pages the subscriber does not get a response and returns a routreq message
20 with an AccessDeniedReason parameter set to NoPageResponse.
21 f. The IIF returns a Provide Roaming Number Return Error message with the error code set to
22 Subscriber Absent to the subscriber’s GSM HLR.
23 g. The GSM HLR sends a Send Routing Information Return Error message to the Gateway GSM
24 MSC with the Subscriber Absent error code, and the appropriate treatment (e.g. announcement)
25 is provided to the incoming call by the Gateway GSM MSC.
2-30
X.S0023
1 4.6 Call Forwarding

2 4.6.1 Call forwarding scenarios for ANSI-41 foreign mode
3 The scenarios in this section illustrate the call forwarding information flows applicable to a GSM
4 native subscriber roaming in an ANSI-41 network (i.e., ANSI-41 foreign mode).
5 4.6.1.1 Call forwarding unconditional (CFU)
6 The following scenarios illustrate the call forwarding unconditional (CFU) information flows
7 applicable to ANSI-41 foreign mode operation.
8 4.6.1.1.1 CFU registration
9 This scenario illustrates the CFU registration information flows applicable to ANSI-41 foreign mode
10 operation.
GSM ANSI-41
Home System Serving System Subscriber
IIF
HLR VMSC MS
2
GSM ANSI-41
feature code digits

a
FEATREQ [digits]
b
REG_SS
c
reg_ss
d
featreq [success]
e
feature confirmation
f
ISD
g
isd
h
[TCAP End]
i
QUALDIR
j
qualdir
k
11
12 Figure 35: CFU registration
13
2-31
X.S0023
1 a. The ANSI-41 serving system receives dialed digits from the subscriber’s mobile station (MS).
2 The serving system detects a “*” character as the first dialed digit. This indicates that the dialed
3 digits are a feature code string.1
4
5 b. The serving system sends a FEATREQ message to the IIF, including the digits received from
6 the subscriber.
7
8 c. The IIF parses the received digit string. In this case, the subscriber has requested to register a
9 call forwarding number. The IIF sends a REG_SS message to the GSM HLR.2
10
11 d. The HLR processes the request and returns a reg_ss message to the IIF, indicating operation
12 success.
13
14 e. The IIF sends a featreq message to the serving system, indicating a successful feature control
15 request.
16
17 f. The serving system sends a feature confirmation signal to the subscriber.
18
19 g. The GSM HLR initiates a service profile update by sending an Insert Subscriber Data (ISD)
20 message to the IIF, containing the new or modified profile data (e.g., the new call forward
21 number).
22
23 h. The IIF responds with an ISD acknowledgement message. Note that, if the subscriber’s profile
24 is too large for a single ISD message, then multiple ISD exchanges may be executed between
25 the GSM HLR and the IIF.
26
27 i. The GSM HLR completes the operation by closing the TCAP transaction.
28
29 j. The IIF converts the revised GSM profile data into ANSI-41 equivalents. If this results in a
30 change in the value of the subscriber’s ANSI-41 profile, the IIF includes the revised ANSI-41
31 profile data in a QUALDIR message it sends to the serving system.
32
33 k. The serving system stores the new profile information and responds with a qualdir message.
34
1 Some ANSI-41 serving systems may perform further digit analysis before concluding that the digits
represent a feature code string. This analysis may also include screening for allowable feature code strings
(e.g., cellular A-side codes only). This may limit the ability of the subscriber to control features while
roaming on the ANSI-41 serving system.
2 Because the IIF must provide the new call forwarding number digits in the REG_SS message, these digits
shall be provided by the subscriber (or the subscriber’s mobile station).
2-32
X.S0023
1 4.6.1.1.2 CFU deregistration (erasure)
2 This scenario illustrates the CFU deregistration information flows applicable to ANSI-41 foreign
3 mode operation.
GSM ANSI-41
IIF
HLR VMSC MS
2
GSM ANSI-41
feature code digits

a
FEATREQ [digits]
b
ERASE_SS
c
erase_ss
d
featreq [success]
e
f
ISD
g
isd
h
[TCAP End]
i
QUALDIR
j
qualdir
k
4
5 Figure 36: CFU deregistration (erasure)
8 digits are a feature code string.
9
11 the subscriber.
12
13 c. The IIF parses the received digit string. In this case, the subscriber has requested to erase a
14 call forwarding number. The IIF sends an ERASE_SS message to the GSM HLR.
15
16 d. The HLR processes the request and returns an erase_ss message to the IIF, indicating
17 operation success.
18
19
21 request.
22
2-33
X.S0023
1
3 message to the IIF, containing the new or modified profile data (e.g., the new ss-status value).
4
5
9
11
15
2-34
X.S0023
1
2 4.6.1.1.3 CFU activation
3 This scenario illustrates the CFU activation information flows applicable to ANSI-41 foreign mode
4 operation.
GSM ANSI-41
IIF
HLR VMSC MS
2
GSM ANSI-41
feature code
digits a
FEATREQ [digits]
b
ACT_SS
c
act_ss
d
featreq [success]
e
feature
confirmation f
ISD
g
isd
h
[TCAP End]
i
QUALDIR
j
qualdir
k
5
6 Figure 37: CFU activation
10
12 the subscriber.
13
14 c. The IIF parses the received digit string. In this case, the subscriber has requested to activate
15 call forwarding. The IIF sends an ACT_SS message to the GSM HLR.
16
17 d. The HLR processes the request and returns an act_ss message to the IIF, indicating operation
18 success.
19
21 request.
22
2-35
X.S0023

2
5
9
11
15
17
2-36
X.S0023
1 4.6.1.1.4 CFU deactivation
2 This scenario illustrates the CFU deactivation information flows applicable to ANSI-41 foreign mode
3 operation.
GSM ANSI-41
IIF
HLR VMSC MS
2
GSM ANSI-41
feature code digits

a
FEATREQ [digits]
b
DEACT_SS
c
deact_ss
d
featreq [success]
e
f
ISD
g
isd
h
[TCAP End]
i
QUALDIR
j
qualdir
k
4
5 Figure 38: CFU deactivation
9
11 the subscriber.
12
13 c. The IIF parses the received digit string. In this case, the subscriber has requested to deactivate
14 call forwarding. The IIF sends a DEACT_SS message to the GSM HLR.
15
16 d. The HLR processes the request and returns a deact_ss message to the IIF, indicating operation
17 success.
18
20 request.
21
23
2-37
X.S0023
3
7
9
13
15
16 4.6.1.1.5 CFU Interrogation
17 While in ANSI-41 foreign mode, the GSM subscriber does not have the capability to interrogate the
18 CFU service. An attempt to perform such an operation shall result in an error response
19 4.6.1.1.6 CFU invocation
20 This scenario illustrates the CFU invocation information flows applicable to ANSI-41 foreign mode
21 operation.
GSM GSM ANSI-41

Gateway Home System Serving System
IIF
GMSC HLR VMSC
2
GSM ANSI-41
incoming call
a
SRI
b
sri [CFU#]
c
forward call to CFU #

d
22
23 Figure 39: CFU invocation
24 a. The GSM gateway MSC (GMSC) receives an incoming call for the subscriber.
25
26 b. The GMSC sends a SRI message to the HLR.
27
28 c. The GSM HLR determines that the subscriber has CFU registered and active; therefore, the
29 HLR responds with the subscriber’s CFU forward-to number in the sri message.
30
31 d. The GMSC forwards the call to the CFU forward-to number.
2-38
X.S0023
1 4.6.1.2 Call forwarding busy (CFB)
2
3 The following scenarios illustrate the call forwarding busy (CFB) information flows applicable to
4 ANSI-41 foreign mode operation.
5 4.6.1.2.1 CFB registration
6 See 4.6.1.1.1 for the CFB registration information flows applicable to ANSI-41 foreign mode
7 operation, since they are the same as those for CFU.
8 4.6.1.2.2 CFB deregistration (erasure)
9 See 4.6.1.1.2 for the CFB deregistration information flows applicable to ANSI-41 foreign mode
11 4.6.1.2.3 CFB activation
12 See 4.6.1.1.3 for the CFB activation information flows applicable to ANSI-41 foreign mode
14 4.6.1.2.4 CFB deactivation
15 See 4.6.1.1.4 for the CFB deactivation information flows applicable to ANSI-41 foreign mode
17 4.6.1.2.5 CFB Interrogation
18 While in ANSI-41 foreign mode, the GSM subscriber does not have the capability to interrogate the
19 CFB service. An attempt to perform such an operation shall result in an error response.
2-39
X.S0023
1 4.6.1.2.6 CFB invocation
2 The following scenarios illustrate the CFB invocation information flows applicable to ANSI-41 foreign
3 mode operation.
4 4.6.1.2.6.1 CFB invocation (Scenario 1a, “CFB#=MSRN method”)
5 In this scenario, the busy condition is detected by the ANSI-41 serving system when the
6 RoutingRequest Invoke message is received, and the IIF returns the CFB forward-to number (i.e.,
7 as the MSRN) to the GSM HLR in the ProvideRoamingNumber Return Result message.
GSM GSM ANSI-41
IIF
GMSC HLR VMSC
2
GSM ANSI-41
incoming call
a
SRI
b
PRN
c
ROUTREQ
d
Subscriber is
detected busy e
routreq [Busy]
f
prn [CFB #]
g
sri [CFB #]
h
setup call to MSRN=CFB #

i
8
9 Figure 40: CFB invocation (Scenario 1a, “CFB#=MSRN method”)
10 a. The GSM GMSC receives an incoming call for the subscriber.
11
13
14 c. The HLR sends a PRN message to the current GSM serving system; i.e., the IIF.
15
16 d. The IIF sends a ROUTREQ message to the ANSI-41 serving system.
17
18 e. The serving system determines that the subscriber is busy.
19
20 f. Therefore, the serving system returns a routreq message, containing the AccessDeniedReason
21 parameter set to the value Busy.
22
23 The IIF determines that CFB is active for the subscriber. The IIF sends the subscriber’s CFB
24 forward-to number as the MSRN in the prn message.
25
2-40
X.S0023
1 g. NOTE: From the GSM HLR and GMSC’s perspectives, the call is routed to a MSRN; they are
2 not aware that the call is being forwarded. Therefore, there may be billing issues associated
3 with this handling. Another drawback is that it is not possible to provide the GSM notification of
4 forwarding to the calling party functionality. It is also critical that the GMSC have controls built in
5 to limit the potential for call looping (e.g., if two dual-mode roaming subscribers have forwarded
6 their calls to each other).
7
8 h. The GSM HLR returns an sri message containing the CFB forward-to number as the MSRN to
9 the GMSC.
10
11 i. The GMSC establishes a call to the CFB forward-to number.
12
2-41
X.S0023
1 4.6.1.2.6.2 CFB invocation (Scenario 1b, “AbsentSubscriber method”)
2 In this scenario, the busy condition is detected by the ANSI-41 serving system when the
3 RoutingRequest Invoke message is received, and the IIF returns an AbsentSubscriber error code to
4 the GSM HLR in the ProvideRoamingNumber Return Error message.
GSM GSM ANSI-41
IIF
GMSC HLR VMSC
2
GSM ANSI-41
incoming call
a
SRI
b
PRN
c
ROUTREQ
d
Subscriber is
detected busy e
routreq [Busy]
f
prn_RE
[AbsentSubscriber]
g
sri [CFNRc #]
h
forward call to CFNRc#

i
5
6 Figure 41: CFB invocation (Scenario 1b, “AbsentSubscriber method”)
7
8 a-f. Same as Section 4.6.1.2.6.1, steps a-f.
9
10 g. The IIF determines that CFB is active for the subscriber. The IIF sends the AbsentSubscriber
11 error code in a ProvideRoamingNumber Return Error message.
12
13 NOTE: This directs the GSM HLR to initiate CFNRc processing if this feature is active in the
14 subscriber’s profile. While this handling complies with the GSM MAP Version 2 standard and
15 avoids the potential problems of other approaches, it requires that the CFNRc feature be active
16 and does not allow different handling of busy versus not reachable conditions.
17
18 h. The GSM HLR returns an sri message, directing the GMSC to forward the call to the CFNRc
20
21 i. The GMSC forwards the call to the CFB forward-to number.
22
2-42
X.S0023
1 4.6.1.2.6.3 CFB invocation (Scenario 2, without OR)
2 In this scenario, the busy condition is detected by the ANSI-41 serving system after the
3 RoutingRequest Invoke message is received and while attempting to complete the call to the TLDN,
4 and optimal routing is not invoked.
5
GSM GSM ANSI-41
IIF
GMSC HLR VMSC
2
GSM ANSI-41
incoming call
a
SRI
b
PRN
c
ROUTREQ [BillingID1]
d
routreq [TLDN]
e
prn [MSRN]
f
sri [MSRN]
g
setup call to MSRN

h
Subscriber is
detected busy i
REDREQ [Busy, BillingID1]

j
redreq [reject]
k
TRANUMREQ [Busy]
l
tranumreq [CFB #]
m
forward call to CFB #

n
6
7 Figure 42: CFB invocation (Scenario 2, without OR)
9
11
12 c. The HLR sends a PRN message to the current GSM serving system; i.e., the IIF.
13
14 d. The IIF sends a ROUTREQ message to the ANSI-41 serving system. Note that this message
15 shall contain the MSCID and PC_SSN parameters corresponding to the IIF. The serving system
16 may use this information to route any subsequent REDREQ message, as in step-j.
17
2-43
X.S0023
1 e. The serving system determines that the subscriber is available; therefore, it returns a routreq
2 message, containing a routing number (called a temporary local directory number, or TLDN, in
3 ANSI-41) to the IIF.
4
5 f. The IIF responds to the GSM HLR with a prn message including the MSRN that it derives from
6 the TLDN; i.e., if the received TLDN is not in international format, then the IIF converts the
7 TLDN into international format for use as the MSRN by adding country code digit(s) associated
8 with the country of the serving system.
9
10 g. The GSM HLR returns an sri message containing the MSRN to the GMSC.
11
12 h. The GMSC establishes a call to the MSRN.
13
14 i. The serving system determines that the subscriber is busy. Note: If call waiting (CW) is active,
15 the serving system would normally invoke CW under these circumstances.
16
17 j. The serving system sends a REDREQ message to the IIF (e.g., using the routing information
18 provided in step-d), indicating that call redirection is requested due to a subscriber busy
19 condition.
20
21 k. Since the IIF is not able to redirect the call (i.e., optimal routing is not possible), it rejects the
22 redirection request.
23
24 l. If the serving system is able to redirect the call, it sends a TRANUMREQ message to the IIF,
25 requesting the CFB forward-to number. Note that not all ANSI-41 systems have implemented
26 this redirection capability. Without this capability, the call shall fail, possibly with a tone or
27 announcement to the calling party.
28
29 m. The IIF determines that CFB is active for the subscriber. Therefore, the IIF responds with a
30 tranumreq message including the subscriber’s CFB forward-to number.
31
32 n. The serving system forwards the call to the CFB forward-to number.
33 4.6.1.2.6.4 CFB invocation (Scenario 2, with OR)
34 In this scenario, the busy condition is detected by the ANSI-41 serving system after the
36 and optimal routing is invoked.
37 This scenario is covered in Section 4.7.1.
38 4.6.1.3 Call forwarding no reply (CFNRy)
39 The following scenarios illustrate the call forwarding no reply (CFNRy) information flows applicable
40 to ANSI-41 foreign mode operation.
2-44
X.S0023
1 4.6.1.3.1 CFNRy registration
2 See 4.6.1.1.1 for the CFNRy registration information flows applicable to ANSI-41 foreign mode
3
4 4.6.1.3.2 CFNRy deregistration (erasure)
5 See 4.6.1.1.2 for the CFNRy deregistration information flows applicable to ANSI-41 foreign mode
6 operation, since they are the same as those for CFU.3
7 4.6.1.3.3 CFNRy activation
8 See 4.6.1.1.3 for the CFNRy activation information flows applicable to ANSI-41 foreign mode
9 operation, since they are the same as those for CFU. 3
10 4.6.1.3.4 CFNRy deactivation
11 See 4.6.1.1.4 for the CFNRy deactivation information flows applicable to ANSI-41 foreign mode
12 operation, since they are the same as those for CFU. 3
13 4.6.1.3.5 CFNRy invocation
14 The following scenarios illustrate the CFNRy invocation information flows applicable to ANSI-41
15 foreign mode operation.
3 The ANSI-136 serving system may not directly support CFNRy registration or activation, but only
support registration or activation of call forwarding no answer (CFNA). In this case, CFNA registration or
activation shall result in the registration or activation of both CFNRy and call forwarding not reachable
(CFNRc).
2-45
X.S0023
1 4.6.1.3.5.1 CFNRy invocation (Scenario 1, without OR)
2 In this scenario, the no reply condition is detected by the ANSI-41 serving system while attempting
3 to complete the call to the TLDN, and optimal routing is not invoked.
GSM GSM ANSI-41
IIF
GMSC HLR VMSC
2
GSM ANSI-41
incoming call
a
SRI
b
PRN
c
ROUTREQ [BillingID1]
d
routreq [TLDN]
e
prn [MSRN]
f
sri [MSRN]
g
setup call to MSRN

h
Subscriber does
not answer i
REDREQ [No answer, BillingID1]

j
redreq [reject]
k
TRANUMREQ [No Answer]

l
tranumreq [CFNRy #]
m
forward call to CFNRy #

n
4
5 Figure 43: CFNRy invocation (Scenario 1, without OR)
6
7 a-h. Same as Section 4.6.1.2.6.3, steps a-h.

8
9 i. The serving system determines that the subscriber does not answer the alert.
10
11 j. The serving system sends a REDREQ message to the IIF (e.g., using the routing
12 information provided in step-d), indicating that call redirection is requested due to a subscriber
13 no answer condition.
14
2-46
X.S0023
2 redirection request
3
4 l. If the serving system is able to redirect the call, it sends a TRANUMREQ message to the IIF,
5 requesting the CFNA (i.e., GSM CFNRy) forward-to number. Note that not all ANSI-41 systems
6 have implemented this redirection capability. Without this capability, the call shall fail, possibly
7 with a tone or announcement to the calling party.
8
9 m. The IIF determines that CFNRy is active for the subscriber. Therefore, the IIF responds with a
10 tranumreq message including the subscriber’s CFNRy forward-to number.
11
12 n. The serving system forwards the call to the CFNRy forward-to number.
13 4.6.1.3.5.2. CFNRy invocation (Scenario 1, with OR)
14 In this scenario, the no reply condition is detected by the ANSI-41 serving system while attempting
15 to complete the call to the TLDN, and optimal routing is invoked.
16 This scenario is addressed in Section 4.7.1.
17 4.6.1.4 Call forwarding not reachable (CFNRc)
18 The following scenarios illustrate the call forwarding not reachable (CFNRc) information flows
19 applicable to ANSI-41 foreign mode operation.
20 4.6.1.4.1 CFNRc registration
21 See 4.6.1.1.1 for the CFNRc registration information flows applicable to ANSI-41 foreign mode
22 operation.4
23 4.6.1.4.2 CFNRc deregistration (erasure)
24 See 4.6.1.1.2 for the CFNRc deregistration information flows applicable to ANSI-41 foreign mode
4
26 4.6.1.4.3 CFNRc activation
27 See 4.6.1.1.3 for the CFNRc activation information flows applicable to ANSI-41 foreign mode
4
29 4.6.1.4.4 CFNRc deactivation
30 See 4.6.1.1.4 for the CFNRc deactivation information flows applicable to ANSI-41 foreign mode
4
32 4.6.1.4.5 CFNRc invocation
33 The following scenarios illustrate the CFNRc invocation information flows applicable to ANSI-41
34 foreign mode operation.
35
4 The ANSI-136 serving system may not directly support CFNRc registration or activation,
but only support registration or activation of call forwarding no answer (CFNA). In this
case, CFNA registration or activation shall result in the registration or activation of both
CFNRc and CFNRy.
2-47
X.S0023
1 4.6.1.4.5.1 CFNRc invocation (Scenario 1)
2 In this scenario, the not reachable condition is detected either by the IIF or by the ANSI-41 serving
3 system when the RoutingRequest Invoke message is received.
4
5 Figure 44: CFNRc invocation (Scenario 1)
7
9
10 c. The HLR sends a PRN message to the current GSM serving system (i.e., the IIF).
11
12 d. If the IIF determines that the called subscriber is not reachable, it returns an absent
13 subscriber error, otherwise, the IIF sends a ROUTREQ message to the ANSI-41 serving
14 system.
15
16 e. The serving system determines that the subscriber is no reachable (e.g., does not respond to
17 paging).
18
19 f. Therefore, the serving system returns a routreq message, containing the
20 AccessDeniedReason parameter set to the value No Page Response.
21
22 g. The IIF determines that CFNRc is active for the subscriber. The IIF sends the
23 AbsentSubscriber error code in a ProvideRoamingNumber Return Error message.
24
25 h. The GSM HLR returns a sri message, directing the GMSC to forward the call to the CFNRc
27
28 i. The GMSC forwards the call to the CFB forward-to number.
2-48
X.S0023
1 4.6.1.4.5.2 CFNRc invocation (Scenario 2, without OR)
2 In this scenario, the not reachable condition is detected by the ANSI-41 serving system after the
4 and optimal routing is not invoked.
5
6 Figure 45: CFNRc invocation (Scenario 2, without OR)
7
9
10 i. The serving system determines that the mobile station does not respond to paging.
11
12 j. The serving system sends a REDREQ message to the IIF (e.g., using the routing information
13 provided in step d), indicating that call redirection is requested due to a subscriber no page
14 response condition.
15
2-49
X.S0023
2 redirection request.
3
4 If the serving system is able to redirect the call, it sends a TRANUMREQ message to the
5 IIF, requesting the forward-to number appropriate for the no page response condition. Note
6 that not all ANSI-41 systems have implemented this redirection capability. Without this
7 capability, the call shall fail, possibly with a tone or announcement to the calling party.
8
9 l. The IIF determines that CFNRc is active for the subscriber. Therefore, the IIF responds with a
10 tranumreq message including the subscriber’s CFNRc forward-to number.
11
12 m. The serving system forwards the call to the CFNRc forward-to number.
13 4.6.1.4.5.3 CFNRc invocation (Scenario 2, with OR)
14 In this scenario, the not reachable condition is detected by the ANSI-41 serving system after the
16 and optimal routing is invoked.
2-50
X.S0023
1 4.6.2 Call forwarding scenarios for GSM foreign mode

2 The scenarios in this section illustrate the call forwarding information flows applicable to an
3 ANSI-41native subscriber roaming in a GSM network; i.e., GSM foreign mode.
4 4.6.2.1 Call forwarding unconditional (CFU)
5 The following scenarios illustrate the call forwarding unconditional (CFU) information flows
6 applicable to GSM foreign mode operation.
7 4.6.2.1.1 CFU registration
8 This scenario illustrates the CFU registration information flows applicable to GSM foreign mode
9 operation.
ANSI-41 GSM
IIF
HLR VMSC MS
2
ANSI-41 GSM
A_REG_SS
a
REG_SS
b
FEATREQ [digits]
c
featreq [success]
d
reg_ss
e
a_reg_ss
f
10
11 Figure 46: CFU registration
12
13 a. The GSM serving system receives an A_REG_SS message from the subscriber’s mobile
14 station (MS), indicating that the subscriber wishes to change his CFU forward-to number.
15
16 b. The serving system sends a REG_SS message to the IIF, constructed based on the information
17 received in the A_REG_SS message.
18
19 c. The IIF translates the information received in the REG_SS message into a corresponding digit
20 string (e.g., based on internal tables) and sends this string to the ANSI-41 HLR in a FEATREQ
21 message.
22
23 d. The HLR processes the request and returns a featreq message to the IIF, indicating operation
24 success.
25
26 e. The IIF sends a reg_ss message to the serving system, indicating a successful feature control
27 request.
28
29 f. The serving system sends a registration response message to the subscriber.
30
2-51
X.S0023
1 Note: The process of registering the call forward number may also result in activation of the service.
2 This is based on HLR (i.e., carrier) determined policy.
3 4.6.2.1.2 CFU deregistration (erasure)
4 This scenario illustrates the CFU deregistration information flows applicable to GSM foreign mode
5 operation.
ANSI-41 GSM
IIF
HLR VMSC MS
2
ANSI-41 GSM
A_ERASE_SS
a
ERASE_SS
b
FEATREQ [digits]
c
featreq [success]
d
erase_ss
e
a_erase_ss
f
6
7 Figure 47: CFU deregistration (erasure)
8 a. The GSM serving system receives an A_ERASE_SS message from the subscriber’s mobile
9 station (MS), indicating that the subscriber wishes to deregister the CFU service.
10
11 b. The serving system sends an ERASE_SS message to the IIF, constructed based on the
12 information received in the A_ERASE_SS message.
13
14 c. The IIF translates the information received in the ERASE_SS message into a corresponding
15 digit string (e.g., based on internal tables) and sends this string to the ANSI-41 HLR in a
16 FEATREQ message.
17
19 success.
20
21 e. The IIF sends an erase_ss message to the serving system, indicating a successful feature
22 control request.
23
24 f. The serving system sends a deregistration response message to the subscriber.
25
26 Note: The process of deregistering the call forward service also results in deactivation of the
27 service.
2-52
X.S0023
1 4.6.2.1.3 CFU activation
2 This scenario illustrates the CFU activation information flows applicable to GSM foreign mode
3 operation.
ANSI-41 GSM
IIF
HLR VMSC MS
2
ANSI-41 GSM
A_ACT_SS
a
ACT_SS
b
FEATREQ [digits]
c
featreq [success]
d
act_ss
e
a_act_ss
f
4
5 Figure 48: CFU activation
6 a. The GSM serving system receives an A_ACT_SS message from the subscriber’s mobile station
7 (MS), indicating that the subscriber wishes to activate the CFU service.
8
9 b. The serving system sends an ACT_SS message to the IIF, constructed based on the
10 information received in the A_ACT_SS message.
11
12 c. The IIF translates the information received in the ACT_SS message into a corresponding digit
14 message.
15
17 success.
18
19 e. The IIF sends an act_ss message to the serving system, indicating a successful feature control
20 request.
21
22 f. The serving system sends an activation response message to the subscriber.
2-53
X.S0023
1 4.6.2.1.4 CFU deactivation
2
3 This scenario illustrates the CFU deactivation information flows applicable to GSM foreign mode
4 operation.
5
ANSI-41 GSM
IIF
HLR VMSC MS
2
ANSI-41 GSM
A_DEACT_SS
a
DEACT_SS
b
FEATREQ [digits]
c
featreq [success]
d
deact_ss
e
a_deact_ss
f
6
7 Figure 49: CFU deactivation
8
9 a. The GSM serving system receives an A_DEACT_SS message from the subscriber’s mobile
10 station (MS), indicating that the subscriber wishes to deactivate the CFU service.
11
12 b. The serving system sends a DEACT_SS message to the IIF, constructed based on the
13 information received in the A_DEACT_SS message.
14
15 c. The IIF translates the information received in the DEACT_SS message into a corresponding
17 FEATREQ message.
18
20 success.
21
22 e. The IIF sends a deact_ss message to the serving system, indicating a successful feature
23 control request.
24
25 f. The serving system sends a deactivation response message to the subscriber.
2-54
X.S0023
1 4.6.2.1.5 CFU invocation
2 This scenario illustrates the CFU invocation information flows applicable to GSM foreign mode
3 operation.
4
ANSI-41 ANSI-41 GSM
Originating MSC Home System Serving System
IIF
GMSC HLR VMSC
2
ANSI-41 GSM
incoming call
a
LOCREQ
b
locreq [CFU#]
c
forward call to CFU #

d
5
6 Figure 50: CFU invocation
7 a. The ANSI-41 originating MSC (OMSC) receives an incoming call for the subscriber.
8
9 b. The OMSC sends a LOCREQ message to the HLR.
10
11 c. The HLR determines that the subscriber has CFU registered and active; therefore, the HLR
12 responds with the subscriber’s CFU forward-to number in the locreq message.
13
14 d. The OMSC forwards the call to the CFU forward-to number.
2-55
X.S0023
1 4.6.2.2 Call forwarding busy (CFB)
2 The following scenarios illustrate the call forwarding busy (CFB) information flows applicable to
3 GSM foreign mode operation.
4 Since the ANSI-41 HLR does not provide the CFB forward-to number to the serving system until the
5 feature is actually invoked—versus the GSM method, whereby the HLR provides the forward-to
6 number(s) to the serving system as part of the subscriber’s profile information at registration
7 time—the IIF shall use the ANSI-41 TransferToNumberRequest operation to obtain the CFB
8 forward-to number. This is illustrated in Figure 51.
ANSI-41 GSM
IIF
HLR VMSC MS
2
ANSI-41 GSM
a
Normal registration process
TRANUMREQ
b
tranumreq
c
TRANUMREQ
d
tranumreq
e
ISD
f
isd
g
[TCAP End]
h
9
10 Figure 51: Obtaining forward-to numbers
11 a. The subscriber registers on a GSM serving system using the normal registration signaling
12 process.
13
14 b. If the subscriber’s ANSI-41 profile indicates that CFB is authorized and active, and the IIF
15 determines that it does may not have the current CFB forward-to number, then the IIF sends a
16 TRANUMREQ message to the HLR requesting the CFB forward-to number.
17
18 c. The HLR responds with the CFB forward-to number in the tranumreq message.
19
20 d. If the subscriber’s ANSI-41 profile indicates that CFNA is authorized and active, and the IIF
21 determines that it does may not have the current CFNA forward-to number, then the IIF sends a
22 TRANUMREQ message to the HLR requesting the CFNA forward-to number.
23
24 e. The HLR responds with the CFNA forward-to number in the tranumreq message.
25
26 f-h. If the CFB forward-to number or CFNA forward-to number, or both numbers do not
27 correspond with the numbers previously provided to the GSM serving system, then the IIF
28 sends the modified information to the GSM serving system using the InsertSubscriberData
2-56
X.S0023
1 operation. The CFNA forward-to number shall be populated as both the CFNRc and CFNRy
2 forward-to numbers.
3 4.6.2.2.1 CFB registration
4 This scenario illustrates the CFB registration information flows applicable to GSM foreign mode
5 operation.
ANSI-41 GSM
IIF
HLR VMSC MS
2
ANSI-41 GSM
A_REG_SS
a
REG_SS
b
FEATREQ [digits]
c
featreq [success]
d
reg_ss
e
a_reg_ss
f
QUALDIR
g
qualdir
h
TRANUMREQ
i
tranumreq
j
ISD
k
isd
l
[TCAP End]
m
6
7 Figure 52: CFB registration
8 a. The GSM serving system receives an A_REG_SS message from the subscriber’s mobile
9 station (MS), indicating that the subscriber wishes to change his call forwarding number.
10
11 b. The serving system sends a REG_SS message to the IIF, constructed based on the information
12 received in the A_REG_SS message.
13
14 c. The IIF translates the information received in the REG_SS message into a corresponding digit
16 message.
17
19 success.
2-57
X.S0023
1
2 e. The IIF sends a reg_ss message to the serving system, indicating a successful feature control
3 request.
4
5 f. The serving system sends a registration response message to the subscriber.
6
7 g-h. If the subscriber’s ANSI-41 profile changes as a result of the operation (e.g., the service was
8 previously authorized, but not activated), the HLR sends a QUALDIR message to the IIF,
9 containing the new profile information.
10
11 i. If the IIF determines that the subscriber’s call forwarding number may have changed, it sends a
12 TRANUMREQ message to the HLR to request the new number.
13
14 j. The HLR responds with the subscriber’s call forwarding number in the tranumreq message.
15
16 k-m. If the subscriber’s GSM profile has changed as a result of these operations, then the IIF
17 sends the modified profile information to the serving system via an InsertSubscriberData
18 message exchange.
19
20 Note: The process of registering the call forwarding number may also result in activation of the
21 service. This is based on HLR (i.e., carrier) determined policy.
2-58
X.S0023
1 4.6.2.2.2 CFB deregistration (erasure)
2 This scenario illustrates the CFB deregistration information flows applicable to GSM foreign mode
3 operation.
ANSI-41 GSM
IIF
HLR VMSC MS
2
ANSI-41 GSM
A_ERASE_SS
a
ERASE_SS
b
FEATREQ [digits]
c
featreq [success]
d
erase_ss
e
a_erase_ss
f
QUALDIR
g
qualdir
h
ISD
i
isd
j
[TCAP End]
k
4
5 Figure 53: CFB deregistration (erasure)
6
7 a. The GSM serving system receives an A_ERASE_SS message from the subscriber’s mobile
8 station (MS), indicating that the subscriber wishes to deregister the call forward service.
9
10 b. The serving system sends an ERASE_SS message to the IIF, constructed based on the
11 information received in the A_ERASE_SS message.
12
13 c. The IIF translates the information received in the ERASE_SS message into a corresponding
15 FEATREQ message.
16
18 success.
19
20 e. The IIF sends an erase_ss message to the serving system, indicating a successful feature
21 control request.
22
23 f. The serving system sends a deregistration response message to the subscriber.
2-59
X.S0023
1
3 previously authorized and activated), the HLR sends a QUALDIR message to the IIF, containing
4 the new profile information.
5
6 i-k. If the subscriber’s GSM profile has changed as a result of these operations, then the IIF
8 message exchange.
9
10 Note: The process of deregistering the call forwarding service also results in deactivation of the
11 service.
12
2-60
X.S0023
1 4.6.2.2.3 CFB activation
2 This scenario illustrates the CFB activation information flows applicable to GSM foreign mode
3 operation.
ANSI-41 GSM
IIF
HLR VMSC MS
2
ANSI-41 GSM
A_ACT_SS
a
ACT_SS
b
FEATREQ [digits]
c
featreq [success]
d
act_ss
e
a_act_ss
f
QUALDIR
g
qualdir
h
ISD
i
isd
j
[TCAP End]
k
4
5 Figure 54: CFB activation
6
7 a. The GSM serving system receives an A_ACT_SS message from the subscriber’s mobile station
8 (MS), indicating that the subscriber wishes to activate the call forward service.
9
10 b. The serving system sends an ACT_SS message to the IIF, constructed based on the
11 information received in the A_ACT_SS message.
12
13 c. The IIF translates the information received in the ACT_SS message into a corresponding digit
15 message.
16
18 success.
19
20 e. The IIF sends an act_ss message to the serving system, indicating a successful feature control
21 request.
22
23 f. The serving system sends an activation response message to the subscriber.
2-61
X.S0023
1
3 previously authorized but not active), the HLR sends a QUALDIR message to the IIF, containing
5
8 message exchange.
2-62
X.S0023
1 4.6.2.2.4 CFB deactivation
2 This scenario illustrates the CFB deactivation information flows applicable to GSM foreign mode
3 operation.
ANSI-41 GSM
IIF
HLR VMSC MS
2
ANSI-41 GSM
A_DEACT_SS
a
DEACT_SS
b
FEATREQ [digits]
c
featreq [success]
d
deact_ss
e
a_deact_ss
f
QUALDIR
g
qualdir
h
ISD
i
isd
j
[TCAP End]
k
4
5 Figure 55: CFB deactivation
6
7 a. The GSM serving system receives an A_DEACT_SS message from the subscriber’s mobile
8 station (MS), indicating that the subscriber wishes to deactivate the call forward service.
9
10 b. The serving system sends a DEACT_SS message to the IIF, constructed based on the
11 information received in the A_DEACT_SS message.
12
13 c. The IIF translates the information received in the DEACT_SS message into a corresponding
15 FEATREQ message.
16
18 success.
19
20 e. The IIF sends a deact_ss message to the serving system, indicating a successful feature
21 control request.
22
23 f. The serving system sends a deactivation response message to the subscriber.
24
2-63
X.S0023
2 previously authorized and active), the HLR sends a QUALDIR message to the IIF, containing
4
7 message exchange.
2-64
X.S0023
1 4.6.2.2.5 CFB invocation
2 The following scenarios illustrate the CFB invocation information flows applicable to GSM foreign
3 mode operation.
4 4.6.2.2.5.1 CFB invocation (without OR)
5 In this scenario, the busy condition is detected by the GSM serving system while attempting to
6 complete the call to the TLDN, and optimal routing is not invoked.
ANSI-41 ANSI-41 GSM
IIF
OMSC HLR VMSC
2
ANSI-41 GSM
incoming call
a
LOCREQ
b
ROUTREQ
c
PRN
d
prn [MSRN]
e
routreq [TLDN]
f
locreq [TLDN]
g
setup call to TLDN

h
Subscriber is
detected busy i
forward call to CFB #

j
7
8 Figure 56: CFB invocation (without OR)
9 a. The ANSI-41 originating MSC (OMSC) receives an incoming call for the subscriber.
10
11 b. The OMSC sends a LOCREQ message to the HLR.
12
13 c. The HLR sends a ROUTREQ message to the current serving system; i.e., the IIF.
14
15 d. The IIF sends a PRN message to the GSM serving system.
16
17 e. The serving system returns a prn message, containing a routing number (called a mobile station
18 roaming number, or MSRN, in GSM) to the IIF.
19
20 f. The IIF responds to the HLR with a routreq message including the TLDN that it derives from the
21 MSRN. Note that the TLDN is typically in international format.
22
23 g. The HLR returns a locreq message containing the TLDN to the OMSC.
24
25 h. The OMSC establishes a call to the TLDN.
2-65
X.S0023
1
2 i-j. The serving system determines that the subscriber is busy and forwards the call to the CFB
4 4.6.2.2.5.2 CFB invocation (with OR)
5 In this scenario, the busy condition is detected by the GSM serving system while attempting to
6 complete the call to the TLDN, and optimal routing is invoked.
8 4.6.2.3 Call forwarding no answer (CFNA)
9 The following scenarios illustrate the call forwarding no answer (CFNA) information flows applicable
10 to GSM foreign mode operation.
11 Since the ANSI-41 HLR does not provide the CFNA forward-to number to the serving system until
12 the feature is actually invoked—versus the GSM method, whereby the HLR provides the forward-to
13 number(s) to the serving system as part of the subscriber’s profile information at registration
14 time—the IIF shall use the ANSI-41 TransferToNumberRequest operation to obtain the CFNA
15 forward-to number. This is illustrated in Figure 51 and described in Section 4.6.2.2.
16 Note that ANSI-41, unlike GSM, does not distinguish the “not reachable” condition from the “no
17 reply” condition. Therefore, if ANSI-41 CFNA is activated, then both of the GSM CFNRy and CFNRc
18 services shall be considered activated.
19 4.6.2.3.1 CFNA registration
20 See 4.6.2.2.1 for the CFNA registration information flows applicable to GSM foreign mode
21 operation, since they are the same as those for CFB. Both CFNRy and CFNRc shall be registered
22 in the IIF and GSM VLR.
23 4.6.2.3.2 CFNA deregistration (erasure)
24 See 4.6.2.2.2 for the CFNA deregistration information flows applicable to GSM foreign mode
25 operation, since they are the same as those for CFB. Both CFNRy and CFNRc shall be
26 deregistered in the IIF and GSM VLR.
27 4.6.2.3.3 CFNA activation
28 See 4.6.2.2.3 for the CFNA activation information flows applicable to GSM foreign mode operation,
29 since they are the same as those for CFB. Both CFNRy and CFNRc shall be activated in the IIF and
30 GSM VLR.
31 4.6.2.3.4 CFNA deactivation
32 See 4.6.2.2.4 for the CFNA deactivation information flows applicable to GSM foreign mode
33 operation, since they are the same as those for CFB. Both CFNRy and CFNRc shall be deactivated
34 in the IIF and GSM VLR.
2-66
X.S0023
1 4.6.2.3.5 CFNA invocation
2 The following scenarios illustrate the CFNA invocation information flows applicable to GSM foreign
3 mode operation.
4 4.6.2.3.5.1 CFNA invocation (Scenario 1, without OR)
5 In this scenario, the no reply condition is detected by the GSM serving system while attempting to
6 complete the call to the TLDN, and optimal routing is not invoked.
ANSI-41 ANSI-41 GSM
IIF
OMSC HLR VMSC
2
ANSI-41 GSM
incoming call
a
LOCREQ
b
ROUTREQ
c
PRN
d
prn [MSRN]
e
routreq [TLDN]
f
locreq [TLDN]
g
setup call to TLDN

h
Subscriber does
not answer i
forward call to CFNRy #

j
7
8 Figure 57: CFNA invocation (Scenario 1, without OR)
10
11 i-j. The serving system determines that the subscriber does not answer the alert and forwards
12 the call to the CFNRy forward-to number.
13
14 4.6.2.3.5.2 CFNA invocation (Scenario 1, with OR)
15 In this scenario, the no reply condition is detected by the GSM serving system while attempting to
16 complete the call to the TLDN, and optimal routing is invoked.
17
2-67
X.S0023
1 4.7 Optimal Routing for Late Call Forwarding

2 The following scenarios cover the interoperability to support Optimal Routing for Late Call
3 Forwarding. The signaling is based on ANSI-41 Rev. D [2] and GSM 9.02 [4].
4 From GSM 02.79 [22] and GSM 03.79 [32], Late Call Forwarding is Call Forwarding performed after
5 the call has been extended to the Visited PLMN (VPLMN) of the forwarding subscriber (i.e.,
6 Conditional Call Forwarding on Busy, Conditional Call Forwarding on No Reply, and Conditional
7 Call Forwarding on Not Reachable detected in the VPLMN of the forwarding subscriber). Late Call
8 Forwarding may be invoked in the Interrogating PLMN (IPLMN) or in the VPLMN of the forwarding
9 subscriber.
10 Assumptions:
11 1) The Subscriber has forwarding enabled.
12 2) Optimal Routing is enabled.
13 The following scenarios address the case where the forwarding attempt is done by the IPLMN.
2-68
X.S0023
1 4.7.1 ANSI-41 Foreign Mode

2 4.7.1.1 ANSI-41 Foreign Mode - Success condition
3 Scenario: GSM Subscriber A makes a call origination attempt at GMSC-A to a GSM Subscriber B
4 who is roaming and registered in an ANSI-41 network at MSC-B. Subscriber B has call forwarding
5 set to an address at MSC-C.
GSM GSM ANSI-41

(GMSC-A) (B’s HLR) IIF (MSC-B/VLR) (MSC-C)
Call Origination
a a
Send Routing Info
b b
Provide Roaming Number
c [ORphase, c
GMSC#,CR#, ROUTEREQ [billing ID]
ORinterrog(Opt.)] [GMSC#,CR#,
d ORinterrog(Opt.)] d
Routereq [TLDN]
e e
Provide Roaming NumberAck[MSRN]
f f
Send Routing InfoAck [MSRN, FIR]
g g
h Establish Connection Attempt h
i REDREQ [REDREASON, billing ID] i
j Resume Call Handling [CR#,reason, forwarding#] j
Send Routing Info [forwarding reason]
k k
Send Routing InfoAck [forwarding #]
l l
m Resume Call HandlingAck m
n redreq n
o Connection Release o
p Call Forward Setup p
6
7
8 Figure 58: Optimal Routing with Late Call Forwarding (ANSI-41 Foreign Mode) Success Case
9
10 a. GSM GMSC-A receives a call origination stimulus from Subscriber A.

11
12 b. If GMSC-A recognizes subscriber B's address as belonging to a GSM PLMN, it checks the
13 identity of HPLMN-B and shall follow the following procedures:
14
15 (i) If GMSC-A is in the same PLMN as the HLR-B, GMSC-A sends a request for routing
16 information to Subscriber B's HLR. This GSM-SRI request contains:
17
18 - an indication of the phase of optimal routing supported by the GMSC-A;
19
20 - the E-164 address of GMSC-A;
21
22 - the Call Reference Number.
23
2-69
X.S0023
1 (ii) If GMSC-A is in a different PLMN from HLR-B, it sends a request for routing information to
2 Subscriber B's HLR. This GSM-SRI request contains all parameters as in item (i) above as well
3 as an indication that it is an optimal routing inquiry (OR interrogation indicator).
4
5
6 c. Subscriber B's GSM HLR determines that Subscriber B is roaming at MSC-B and sends a
7 GSM-Provide Roaming Number message, which also contains the GMSC address, the Call
8 Reference Number and the OR interrogation indicator if it was received in the GSM-SRI to an
9 IIF acting on behalf of MSC-B to get a roaming number. The E-164 address of GMSC-A shall be
10 provided in the message, as specified in GSM 03.79.
11
12 d. The IIF relays this request to the ANSI-41 MSC/VLR-B by sending an ANSI-41-Routing Request
13 message. The originating address in this message is provided as a routing address back to the
14 IIF.
15
16 e. The ANSI-41 MSC/VLR-B acknowledges the ANSI-41-Routing Request message with the
17 Temporary Local Directory Number (TLDN).
18
19 f. Upon receipt of the ANSI-41-Routing Request message, the IIF sends an MSRN to Subscriber
20 B's GSM HLR in the GSM-Provide Roaming Number Acknowledgment message.
21
22 g. Subscriber B's GSM HLR relays this information to GMSC-A using the GSM-Send Routing
23 Information Acknowledgment message. This message includes MSRN and optionally a
24 ForwardedInterrogationRequired (FIR) parameter, which indicates whether the GMSC-A shall
25 interrogate the HLR for routing information for late call forwarding.
26
27 h. GMSC-A starts a call setup procedure using the MSRN (TLDN) as Subscriber B's called
28 address at ANSI-41 MSC/VLR-B).
29
30 i. The incoming call at ANSI-41 MSC/VLR-B can not be terminated because of reasons such as
31 No Answer, No Page Response, or Unavailable. An ANSI-41-Redirection Request message
32 with a RedirectionReason parameter is then sent to the IIF based on the originating address
33 received in the ANSI-41-Route Request message at step d.
34
35 j. The IIF sends GSM-Resume Call Handling message to GMSC-A based on the GMSC-A
36 address received in the GSM-Provide Roaming Number. Note that the GSM-Resume Call
37 Handling includes the same Call Reference Number received in the GSM-Provide Roaming
38 Number, the cause for termination failure (forwarding reason) and the forwarding number at
39 MSC-C plus all necessary parameters required for call forwarding.
40
41 k. If the ForwardedInterrogationRequired parameter was received from Subscriber B's GSM HLR
42 in the GSM-Send Routing Information Acknowledgement message at step g, , GMSC-A sends a
43 GSM-Send Routing Information message to Subscriber B's GSM HLR requesting it to send a
44 call forwarding information.
45
46 Otherwise, it is assumed that all forwarding information is ready available at GMSC-A and an
47 acknowledgment of the GSM-Resume Call Handling message is sent to the IIF (step m).
48
49 l. If a corresponding forwarded-to number is available at subscriber B's GSM HLR, GMSC-A
50 receives a GSM-Send Routing Information Acknowledge message with the necessary
51 forwarding information.
52
2-70
X.S0023
1 In case of an error, a GSM-Send Routing Information Error message is sent to GMSC-A and
2 GMSC-A uses the forwarding information from step j.
3
4 m. GMSC-A sends an acknowledgment of the GSM-Resume Call Handling message.
5
6 n. Upon receipt of GSM-Resume Call Handling Acknowledgment message, the IIF acknowledges
7 the ANSI-41-Redirection Request message.
8
9 In case of an error, the IIF rejects the redirection request and the ANSI-MSC-B initiates a call
10 forwarding procedure extend the call to MSC-C. See Section 6.2.
11
12 o. If step n is successful, GMSC-A releases all circuit-associated resources specific to ANSI-41
13 MSC/VLR-B.
14
15 p. GMSC-A starts a call setup procedure using the call forwarded-to number as Subscriber B’s
16 address at ANSI-41 MSC-C.
17
2-71
X.S0023
1 4.7.1.2 ANSI-41 Foreign Mode - Failure condition
2 Scenario: GSM Subscriber A makes a call origination attempt at GMSC-A to GSM Subscriber B
3 roaming and registered in an ANSI-41 network at MSC-B. Subscriber B has call forwarding set to an
4 address at MSC-C. Optimal Routing fails at IPLMN.
GSM GSM ANSI-41

(GMSC-A) (B’s HLR) IIF (MSC-B/VLR) (MSC-C)
Call Origination
a a
b Send Routing Info b
[ORphase,
c GMSC#, CR#, Provide Roaming Number c
ORinterrog(opt.)] [GMSC#,CR#,
ORinterrog(opt.)] ROUTEREQ
d d
Routereq [TLDN]
e e
Provide Roaming NumberAck[MSRN]
f f
Send Routing InfoAck [MSRN, FIR]
g g
i REDREQ [REDREASON] i
j Resume Call Handling [CR#,reason, forwarding #] j
Send Routing Info [forwarding reason]
k k
Send Routing InfoAck [forwarding #]
l l
m Resume Call Handling Error m
redreq (reject)
n n
o TRANUMREQ [REDREASON] o
p tranumreq [TERMLIST, REDIND] p
q Forward Call q
5
6
7 Figure 59: Optimal Routing with Late Call Forwarding (ANSI-41 Foreign Mode) Failure Case
8 a.-l.These steps are the same as the success case.
9
10 m. If GMSC-A determines that it cannot forward the call via an optimal route, it returns a Resume
11 Call Handling error to the IIF.
12
13 n. The redirection request at step i. is rejected.
14
15 o. The ANSI-41 MSC/VLR-B sends an ANSI-41 TransferToNumberRequest message to the IIF
16 with the RedirectionReason parameter.
17
18 p. The IIF returns the ANSI-41 TransferToNumberResponse message to the ANSI-41 MSC/VLR-B
19 with the forward-to number in the TerminationList parameter along with an indication of the
20 reason (DMH_RedirectionIndicator) for extending the incoming call.
21
22 q. The ANSI-41 MSC/VLR-B forwards the incoming call to MSC-C.
2-72
X.S0023
1 4.7.2 GSM Foreign Mode

2 4.7.2.1 GSM Foreign Mode - Success Case
3 Scenario: ANSI-41 Subscriber A makes a call origination attempt at ANSI-41 MSC-A to ANSI-41
4 Subscriber B roaming and registered in a GSM network at MSC-B. Subscriber B has call forwarding
5 set to an address at MSC-C. Subscriber B is not IMSI detached.
ANSI-41 ANSI-41 GSM

(MSC-A) (B’s HLR) IIF (VLR/MSC-B) (MSC-C)
Call Origination
a a
LOCREQ
b b
c ROUTEREQ
c
Provide Roaming Number[GMSC#,CR#]
d d
Provide Roaming NumberAck [MSRN]
e e
Routereq [TLDN]
f f
Locreq [TLDN]
g g
i Resume Call Handling [CR#,reason]
i
j REDREQ [REDREASON]
j
TRANUMREQ [REDREASON]
k k
tranumreq
l l
redreq
m m
Resume Call HandlingAck
n n
o Connection Release o
p Call Forward Setup p
6
7
8 Figure 60: Optimal Routing with Late Call Forwarding (GSM Foreign Mode) Success Case
9 a. ANSI-41 MSC-A receives a call origination stimulus from Subscriber A.
10
11 b. The ANSI-41 MSC-A sends an ANSI-41-Location Request message for routing information to
12 Subscriber B's ANSI-41 HLR with the MSCID address of the originating MSC (ANSI-41 MSC-
13 A).
14
15 c. Subscriber B's ANSI-41 HLR determines that Subscriber B is roaming at MSC-B and sends a
16 ANSI-41-Routing Request message number with the MSCID address of the ANSI-41 MSC-A
17 received in step b. to an IIF acting on behalf of MSC-B to get a roaming number.
18
19 d. The IIF relays this request to GSM MSC/VLR-B by sending a GSM-Provide Roaming Number
20 message. The IIF generates two parameters: the Call Reference number (for the VLR/MSC-B
21 to use in the GSM-RCH) and the GMSC address set to the IIF address, to indicate that the IIF is
22 capable of supporting optimal routing for late call forwarding.
23
24 e. GSM MSC/VLR-B acknowledges the GSM - Provide Roaming Number message with the
25 Mobile Subscriber Roaming Number (MSRN).
2-73
X.S0023
1
2 f. Upon receipt of this message, the IIF sends the TLDN to Subscriber B's ANSI-41 HLR in the
3 ANSI-41-Routing Request message.
4
5 g. Subscriber B's ANSI-41 HLR relays this information to ANSI-41 MSC-A via the ANSI-41-
6 Location Request (Acknowledgment) message.
7
8 h. ANSI-41 MSC starts a call setup procedure using TLDN (MSRN) as Subscriber B's called
9 address at GSM MSC/VLR-B. The incoming call can not be terminated at GSM MSC/VLR-B
10 because of reasons such as Busy, Not Reachable, or No Reply.
11
12 i. Since the GMSC address and the Call Reference Number parameters were present in the
13 GSM-Provide Roaming Number message the GSM MSC-B sends a GSM-Resume Call
14 Handling message to the IIF with the received Call Reference number and all necessary
15 information required for call forwarding.
16
17 If optimal routing is not supported the call is forwarded by GSM MSC-B using the forwarding
18 information available.
19
20 j. When optimal routing is supported and the IIF receives the GSM-Resume Call Handling
21 message, the IIF sends an ANSI-41-Redirecion Request message with the Redirection Reason
22 to the ANSI-41 MSC-A supporting subscriber A's call origination attempt.
23
24 k. The ANSI-41 MSC-A passes this Redirection Reason to the Subscriber B's ANSI-41 HLR in the
25 ANSI-41-Transfer To Number message to get call forwarding number information.
26
27 l. Based on the Redirection Reason, the ANSI-41 HLR returns the corresponding forwarded-to
28 number to ANSI-41 MSC/VLR-A.
29
30 m. If ANSI-41 MSC-A received forwarded-to number from ANSI-41 HLR, it sends
31 ANSI-41-Redirection Request (Acknowledgment) message to the IIF.
32
33 In case of an error, ANSI-41 MSC-A rejects the redirection request. The IIF then returns a
34 GSM-Resume Call Handling Error message to GSM MSC-B, which then attempts to forward the
35 call to MSC-C using the forwarding information available.
36
37 n. Upon receiving the ANSI-41-Redirection Request (Acknowledgment) in step m., the IIF sends a
38 GSM-Resume Call Handling Acknowledgment message to GSM MSC-B.
39
40 o. The ANSI-41 MSC-A releases all circuit-associated resources specific to GSM MSC/VLR-B.
41
42 p. The ANSI-41 MSC-A starts a call setup procedure using the call forwarded-to number as
43 Subscriber B's address at MSC-C.
2-74
X.S0023
1 4.7.2.2 GSM Foreign Mode - Failure case
2 Scenario: ANSI-41 Subscriber A makes a call origination attempt at ANSI-41 MSC-A to ANSI-41
3 Subscriber B roaming and registered in a GSM network at MSC-B. Subscriber B has call forwarding
4 set to an address at MSC-C. Optimal Routing fails at IPLMN. Subscriber B is not IMSI detached.
5
ANSI-41 ANSI-41 GSM
(MSC-A) (B’s HLR) IIF (VLR/MSC-B) (MSC-C)
Call Origination
a a
LOCREQ
b b
ROUTEREQ
c c
Provide Roaming Number [GMSC#,CR#]
d d
Provide Roaming Number Ack [MSRN]
e e
Routereq [TLDN]
f f
Locreq [TLDN]
g g
Resume Call Handling [CR#,reason]
i i
j REDREQ [REDREASON]
j
TRANUMREQ [REDREASON]
k k
tranumreq
l l
redreq (reject)
m m
Resume Call Handling Error
n n
o Forward Call o
6
7
8 Figure 61: Optimal Routing with Late Call Forwarding (GSM Foreign Mode) Failure Case
9 a.-l.These steps are the same as the Success Case.
10
11 m. The redirection request at step j. is rejected.
12
13 n. The IIF sends a GSM-Resume Call Handling Error message to GSM MSC-B.
14
15 o. The GSM MSC-B forwards the incoming call to MSC-C.
2-75
X.S0023
1 4.8 Call Waiting

2 This section depicts the interactions between network entities in various situations related to GSM
3 and ANSI-41 foreign mode operation and Call Waiting (CW).
4 4.8.1 Call Waiting Activation

5 4.8.1.1 ANSI-41 Foreign Mode Successful Call Waiting Activation
6 This scenario describes a successful call waiting activation by a native GSM subscriber roaming in
7 an ANSI-41 network.
8
9 Figure 62: ANSI-41 Foreign Mode Call Waiting Activation
10 a. The subscriber requests activation of call waiting. The MS converts the user-entered MMI/menu
11 selections to feature codes. (e.g. *FC). The MS sends this feature code string to the Serving
12 MSC. During analysis of the digit string, the Serving MSC detects a feature code string.
13 b. The digit string is included in a FEATREQ and sent from the Serving MSC to the IIF emulating
14 the HLR associated with the MS.
2-76
X.S0023
1 c. The IIF determines the digit string pertains to the activation of call waiting and then sends an
2 Activate SS message to the HLR to request activation of call waiting. 5
3 d. The HLR returns an Activate SS Ack message to the IIF indicating a successful activation of call
4 waiting.
5 e. The IIF sends a featreq to the Serving MSC containing the feature request confirmation
6 indication.
7 f. When the featreq is received from the IIF, the Serving MSC provides treatment to the served
8 MS based on the information contained in the response. In this case, the treatment is to apply
9 feature confirmation.
10 g. The Serving MSC releases the call.
11 h. Because the request resulted in a change to the subscriber’s service profile (i.e., the call waiting
12 feature was activated), the HLR reports the change by sending an Insert Subscriber Data
13 message to the IIF emulating the Serving MSC/VLR.
14 i. The IIF returns an Insert Subscriber Data Ack message to the HLR.
15 j. The IIF sends a QUALDIR message to the Serving MSC/VLR.
16 k. The Serving MSC/VLR returns a qualdir to the IIF.
5 Most likely, the GSM 02.30 standardized MMI would be mapped to the equivalent GSM
functional message.
2-77
X.S0023
1 4.8.1.2 ANSI-41 Foreign Mode Unsuccessful Call Waiting Activation
2 The following scenario describes an unsuccessful call waiting activation by a native GSM subscriber
3 roaming in an ANSI-41 network.
5
6 Figure 63: ANSI-41 Foreign Mode Unsuccessful Call Waiting Activation
7 a. The subscriber requests activation of call waiting. The MS converts the user-entered MMI/menu
8 selections to feature codes. (e.g. *FC). The MS sends this feature code string to the Serving
9 MSC. During analysis of the digit string, the Serving MSC detects a feature code string.
10 b. The digit string is included in a FEATREQ and sent from the Serving MSC to the IIF emulating
11 the HLR associated with the MS.
12 c. The IIF determines the digit string pertains to the activation of call waiting and then sends an
13 Activate SS message to the HLR to request activation of call waiting. 6
14 d. The HLR returns an Activate SS Ack message to the IIF indicating an unsuccessful activation of
15 call waiting.
16 e. The IIF sends a featreq to the Serving MSC containing a Feature Result parameter set to
17 “Unsuccessful”. In addition, it may include an AnnouncementList code that corresponds to the
18 User error parameter included in the Activate SS Ack message sent by the GSM HLR.
20 MS based on the information contained in the response.
21 g. The Serving MSC sends a Release message to the MS.
22
functional message.
2-78
X.S0023
1 4.8.1.3 GSM Foreign Mode Feature Activation
2 This scenario describes a successful call waiting activation by a native ANSI-136 subscriber
3 roaming in a GSM network.
4
5 Figure 64: GSM Foreign Mode Call Waiting Activation
6 a. The subscriber requests activation of call waiting. The MS interprets the user-entered
7 MMI/menu selections. The MS sends a request for activation of call waiting (by issuing an
8 Activate SS operation).
9 b. The Serving GSM MSC sends an Activate SS message to the IIF emulating the HLR
10 associated with the subscriber. The message specifies the call waiting supplementary
11 service for the activation being requested.
12 c. The IIF converts the call waiting Activate SS message to a particular feature code (e.g.
13 *FC). The IIF includes this feature code (including *) in the Digits (Dialed) parameter of a
14 FEATREQ message and sends the message to the subscriber’s HLR.
15 d. The HLR returns a featreq message to the IIF indicating a successful call waiting activation.
16 e. The IIF returns an Activate SS Ack message back to the Serving GSM MSC. Any
17 parameters the HLR may have included that provide instructions for treatment towards the
18 user (such as AnnouncementList) shall be ignored by the IIF and not mapped into the
19 message sent to the Serving GSM MSC.
20 f. When the Activate SS Ack message is received from the IIF, the Serving GSM MSC sends
21 a message to the MS to indicate that the call waiting activation had been successful.
2-79
X.S0023
1 g. Because the request resulted in a change to the subscriber’s service profile (i.e., the call
2 waiting feature was activated), the HLR reports the change by sending a QUALDIR
3 message to the IIF emulating the Serving GSM MSC/VLR.
4 h. The IIF sends an Insert Subscriber Data message to the Serving GSM MSC/VLR.
5 i. The Serving GSM MSC/VLR returns an Insert Subscriber Data Ack to the IIF.
6 j. The IIF returns a qualdir message to the HLR.
7 Note that the GSM foreign mode unsuccessful call waiting activation case parallels the ANSI-41
8 foreign mode unsuccessful call waiting activation case shown in the previous section.
2-80
X.S0023
1 4.8.2 Call Waiting Deactivation

2 4.8.2.1 ANSI-41 Foreign Mode Call Waiting Deactivation
3 This scenario describes a successful call waiting deactivation by a native GSM subscriber roaming
4 in an ANSI-41 network.
6
7 Figure 65: ANSI-41 Foreign Mode Call Waiting Deactivation
8 a. The subscriber selects a menu entry in order to deactivate call waiting. The MS converts the
9 user-entered MMI/menu selections to feature codes. (e.g. *FC0). The MS sends this digit string
10 towards the network. The digit string is received by the Serving MSC. During analysis of the
11 digit string, the Serving MSC detects a feature code string.
12 b. The dialed digits are included in a FEATREQ and sent from the Serving MSC to the IIF
13 emulating the HLR associated with the MS.
2-81
X.S0023
1 c. The IIF determines the digit string pertains to the deactivation of call waiting and then sends a
2 Deactivate SS message to the HLR to request deactivation of call waiting. 7
3 d. The HLR returns a Deactivate SS Ack message to the IIF indicating a successful deactivation of
4 call waiting.
5 e. The IIF sends a featreq to the Serving MSC containing the feature request confirmation
6 indication.
8 MS based on the information contained in the response. In this case, the treatment is to apply
9 feature confirmation.
10 g. The Serving MSC releases the call.
11 h. Because the request resulted in a change to the subscriber’s service profile (i.e., the call waiting
12 feature was deactivated), the HLR reports the change by sending an Insert Subscriber Data
13 message to the IIF emulating the Serving MSC/VLR.
14 i. The IIF returns an Insert Subscriber Data Ack message to the HLR.
15 j. The IIF sends a QUALDIR message to the Serving MSC/VLR.
16 k. The Serving MSC/VLR returns a qualdir to the IIF.
functional message.
2-82
X.S0023
1 4.8.2.2 GSM Foreign Mode Feature Deactivation
2 This scenario describes a successful call waiting deactivation by a native ANSI-41subscriber

3 roaming in a GSM network.
4
5
6 Figure 66: GSM Foreign Mode Call Waiting Deactivation
7 a. The subscriber requests activation of call waiting. The MS associates the MMI/menu selection
8 provided by the subscriber with a request to deactivate call waiting. The MS sends a request for
9 deactivation of call waiting (by issuing a Deactivate SS operation).
10 b. The Serving GSM MSC sends a Deactivate SS message to the IIF emulating the HLR
11 associated with the subscriber. The message specifies the call waiting supplementary service
12 for the deactivation being requested.
13 c. The IIF converts the call waiting Deactivate SS message to a particular digit string (e.g. *FC0).
14 The IIF includes this digit string (including *) in the Digits (Dialed) parameter of a FEATREQ
15 message and sends the message to the subscriber’s HLR.
16 d. The HLR returns a featreq message to the IIF indicating a successful call waiting deactivation.
17 e. The IIF returns a Deactivate SS Ack message back to the Serving GSM MSC. Any parameters
18 the HLR may have included that provide instructions for treatment towards the user (such as
19 AnnouncementList) shall be ignored by the IIF and not mapped into the message sent to the
20 Serving GSM MSC.
21 f. When the Deactivate SS Ack message is received from the IIF, the Serving GSM MSC sends a
22 message to the MS to indicate that the call waiting deactivation had been successful.
2-83
X.S0023
1 g. Because the request resulted in a change to the subscriber’s service profile (i.e., the call waiting
2 feature was deactivated), the HLR reports the change by sending a QUALDIR message to the
3 IIF emulating the Serving GSM MSC/VLR.
4 h. The IIF sends an Insert Subscriber Data message to the Serving GSM MSC/VLR.
5 i. The Serving GSM MSC/VLR returns an Insert Subscriber Data Ack to the IIF.
6 j. The IIF returns a qualdir message to the HLR.
7
2-84
X.S0023
1 4.9 Calling Number / Line Identification Presentation/Restriction

2 4.9.1 Handling of calling number/ line identification presentation
3 4.9.1.1 GSM Foreign Mode
4 If CNIP / CLIP service is authorized and active, the calling party number is available and
5 presentation is allowed, the called party’s serving network shall provide the calling party number to
6 the called party during call alerting as in Figure 67 below.
MSC/
MSC HLR IIF MS
VLR
Incoming call to DN
a
LOCREQ
b
(Calling Party No)
ROUTREQ
c
(Calling Party No)
Provide Roaming No
d
(Calling Party No))
Prov Roaming No Ack
e
(MSRN)
Routreq (TLDN = MSRN)
f
Locreq (TLDN = MSRN)

g
Call Setup
h
(Calling Party No)
Alert
i
(Calling Party No,
PI, SI, Sub-address)
7
8
9 Figure 67: Calling number/ line identification presentation:
10 mobile station or fixed terminal to mobile station – GSM Foreign Mode
11 a. An incoming call for the called party is received at his/her home network.
12
13 b. The calling party number may be carried in the calling party number digits parameter as
14 specified in TIA/EIA-41-5-D [2].
15
16 c. The calling party number may be carried in the calling party number string parameter as
17 specified in TIA/EIA-41-5-D [2].
18
19 d. The calling party number may be carried in the additional signal information element as
21
22 e. The VLR returns a roaming number for routing purposes.
23
2-85
X.S0023
1 f. The IIF maps the MSRN it receives from the VLR into the TLDN field in the routreq.
2
3 g. The HLR returns a locreq to the MSC with the routing information it received from the IIF.
4
5 h. The trunk signaling between the MSC’s may transit a number of intermediate signaling networks
6 of various capabilities. As such, there is no guarantee that the calling party number can be
7 conveyed using the ISUP/TUP signaling capabilities.
8
9 i. The MSC delivers the calling party identification during the call setup operation with the MS.
10 The calling party subaddress is passed if it is received from the originating network. The Calling
11 Party No, Presentation Indicator (PI), and Screening Indicator (SI) shall be sent in accordance
12 with GSM 03.81 [34].
13
14 Note: Where a calling party number is delivered both via MAP signaling and ISUP/TUP signaling,
15 the number delivered via MAP signaling takes precedence.
16
17 Note: When an additional calling party number is also available for presentation purposes, the
18 additional calling party number (subject to CNIP/CLIR) shall be presented in preference to any
19 other calling party number.
20
21 4.9.1.1.1 Interrogation
22 The subscriber can request the status of the supplementary service when operating in GSM foreign
23 mode and be informed if the service is provided to him/her.
2-86
X.S0023
1 4.9.1.2 ANSI-41 Foreign Mode
3 presentation is allowed, the called party’s serving network shall provide the calling party number to
4 the called party during call alerting as in Figure 68 below.
HLR MSC/
GMSC IIF MS
VLR
Incoming call to DN
a
Send Routing Info

b
(Calling Party No)
Provide Roaming No
c
(Calling Party No)
ROUTREQ
d
(Calling Party No))
routreq
e
(TLDN)
Prov Roaming No Ack
f
(MSRN =TLDN)
SRI Ack g
(MSRN = TLDN)
Call Setup
h
(Calling Party No)
Alert
i
(Calling Party No)
6 Figure 68: Calling number/ line identification presentation:

7 mobile station or fixed terminal to mobile station – ANSI-41 Foreign Mode
8 a. An incoming call for the called party is received at his/her home network.
9
10 b. The calling party number may be carried in the additional signal information element as
12
13 c. The calling party number may be carried in the additional signal information element as
15
16 d. The calling party number may be carried in the calling party number string parameter as
17 specified in ANSI-41.5 [2].
18
19 e. The MSC returns a TLDN for routing purposes
20
21 f. The IIF maps the TLDN it receives from the MSC into the MSRN field in the Provide Roaming
22 No Ack.
23
24 g. The HLR returns an SRI Ack to the GMSC with the routing information it received from the IIF.
25
2-87
X.S0023
1 h. The trunk signaling between the MSC’s may transit a number of intermediate signaling networks
2 of various capabilities. As such, there is no guarantee that the calling party number can be
3 conveyed using the ISUP/TUP signaling capabilities.
4
5 i. The mobile station receives an incoming call alert, which contains the calling party identification
6 information.
7
8 Note: Where a calling party number is delivered both via MAP signaling and ISUP/TUP signaling,
9 the number delivered via MAP signaling takes precedence.
11 The subscriber cannot request the status of the supplementary service in ANSI-41 Foreign mode.
2-88
X.S0023
1 4.9.2 Handling of calling number/ line identification restriction

2 4.9.2.1 General
3 If the calling subscriber has calling number/line identification restriction authorized and active and it
4 is impossible to indicate to the terminating network (due to interworking) that the number shall not
5 be presented to the terminating party, the calling number/line identity shall not be delivered to the
6 terminating network.
8 If CNIR / CLIR service is authorized and active, the calling party number is available and
9 presentation is restricted, the called party’s serving network shall not present the calling party
10 number to the called party during call alerting. An indication that the calling party number is
11 restricted shall be delivered to the called party.
13 The subscriber can request the status of the CNIR /CLIR supplementary service and be informed if
14 the service is provided to him/her and which mode is provided, i.e. permanent or temporary and if
15 temporary, what the default value is (i.e. allowed or restricted).
22 The subscriber cannot request the status of the supplementary service.
2-89
X.S0023
1 4.10 Call Barring and Operator Determined Barring

2 This section describes the interoperability at the IIF to support ANSI-41 outgoing call restrictions,
3 GSM Operator Determined Barring (ODB), and GSM Call Barring Supplementary Services. The
4 scenarios included are illustrative and not exhaustive.
5 ODB is a GSM administrative feature. As described in associated Stage 1 documentation, direct

6 mapping of many GSM ODB or call barring options does not exist in ANSI-41mode. Likewise, many
7 ANSI-41 outgoing call restrictions do not directly map to equivalent GSM ODB or call barring
8 options.
9 4.10.1 Activation of Barring at VLR

10 These call flows apply only to Call Barring Supplementary Services, ANSI-41 call restrictions, or
11 ODB programs (e.g., Barring of Outgoing Calls) for which barring is performed at the VLR. Any
12 barring or call restrictions applied in the HLR shall result in the appropriate restrictions being
13 downloaded to the serving VLR/MSC via the IIF.
14 4.10.1.1 Activation of Call Restrictions while in GSM Foreign Mode
15 This scenario describes the successful activation of call restrictions for a native ANSI-41subscriber
16 roaming in a GSM network at a time when the subscriber is currently registered.
ANSI-41 GSM
HLR IIF VLR/
MSC
QUALDIR a

b
ISD Ack c
qualdir
d
17
18 Figure 69: Activation of Call Restriction - GSM Foreign Mode
19 a. Call restrictions are applied at the ANSI-41 HLR. The HLR sends an appropriate
20 QualificationDirective INVOKE message to the IIF emulating the VLR where the subscriber is
21 roaming.
22
23 b. The IIF forwards a corresponding Insert Subscriber Data message to the GSM VLR.
24
25 c. The VLR sends an Insert Subscriber Data acknowledgement to the IIF.
26
27 d. The IIF forwards a QualificationDirective RETURN RESULT message to the HLR.
28
2-90
X.S0023
1 4.10.1.2 Activation of Call Barring while in ANSI-41 Foreign Mode
2 This scenario describes the successful application of ODB or call barring for a native GSM
3 subscriber roaming in an ANSI-41 network.
ANSI-41
GSM
IIF VLR/
HLR
MSC

a
QUALDIR
b
qualdir c
ISD Ack
d
4
5 Figure 70: Activation of Call Barring – ANSI-41 Foreign Mode
6
7 a. ODB or call barring is applied at the GSM HLR. The HLR sends an appropriate Insert
8 Subscriber Data message to the IIF emulating the VLR where the subscriber is roaming.
9
10 b. The IIF forwards a corresponding QualificationDirective INVOKE message to the ANSI-41 VLR.
11
12 c. The VLR sends a QualificationDirective RETURN RESULT to the IIF.
13
14 d. The IIF forwards an Insert Subscriber Data acknowledgement message to the HLR.
2-91
X.S0023
1 4.10.2 Invocation of Barring of Incoming Calls

3 Barring of incoming calls is performed at the ANSI-41 HLR. There is no IIF involvement.
5 Barring of incoming calls is performed at the GSM HLR. There is no IIF involvement.
6 4.10.3 Invocation of Barring of Roaming

7 Barring of Roaming is performed at the HLR. The following subsections, however, illustrate the
8 signaling at the IIF when a barred subscriber attempts to roam into a GSM or ANSI-41 Foreign
9 network.
11 This scenario describes the successful barring of roaming for a native ANSI-41subscriber
12 attempting to roam into a GSM network.
GSM
IIF ANSI-41
MSC/
HLR
VLR
Update Location a
REGNOT
b
regnot c
UL Ack
d
13
14 Figure 71: Invocation of Barring of Roaming – GSM Foreign Mode
15
16 a. A native ANSI-41subscriber with barring of Roaming active, attempts to register in a GSM
17 network. The GSM VLR sends an Update Location message to the IIF emulating the
18 subscriber’s HLR.
19
20 b. The IIF issues a RegistrationNotification INVOKE to the HLR.
21
22 c. The HLR determines that roaming is denied in this case, returns a RegistrationNotification
23 RETURN RESULT with AuthorizationDenied set to Not Authorized for the MSC. Optionally,
24 a RegistrationCancellation message may be sent to the previous Serving MSC/VLR (if
25 registration was in an ANSI-41 network) or to the IIF (if registration was in a GSM network).
26
27 d. The IIF issues an Update Location acknowledgement with User Error set to Roaming Not
28 Allowed. The VLR denies the registration attempt.
2-92
X.S0023
2 This scenario describes the successful ODB barring of roaming for a native GSM subscriber
3 attempting to roam into an ANSI-41 network.
ANSI-41 GSM
MSC/ IIF HLR
VLR
REGNOT a
Update Location
b
UL Ack c
regnot
d
4
5 Figure 72: Invocation of Barring of Roaming – ANSI-41 Foreign Mode
6
7 a. A native GSM subscriber with ODB barring of Roaming active, attempts to register in an
8 ANSI-41 network. The ANSI-41 VLR sends an RegistrationNotification INVOKE to the IIF
9 emulating the subscriber’s HLR.
10
11 b. The IIF issues an Update Location message to the HLR.
12
13 c. The HLR determines that roaming is denied in this case, returns an Update Location
14 acknowledgement with User Error set to Roaming Not Allowed. Optionally, a Cancel Location
15 message may be sent to the previous Serving MSC/VLR (if registration was in a GSM network)
16 or to the IIF (if registration was in an ANSI-41 network).
17
18 d. The IIF issues a RegistrationNotification RETURN RESULT with AuthorizationDenied set to Not
19 Authorized for the MSC. The VLR denies the registration attempt.
2-93
X.S0023
1 4.10.4 Invocation of Barring of Supplementary Services Management

2 Barring of Supplementary Services Management is performed at the HLR. The following
3 subsections, however, illustrate the signaling at the IIF when a subscriber attempts to activate a
4 supplementary service in a GSM or ANSI-41 Foreign network, while Barring of Supplementary
5 Services Management is in effect.
7 This scenario describes the successful barring of supplementary service control for a native
8 ANSI-41subscriber in a GSM network.
GSM
MSC/ IIF ANSI-41
VLR HLR
Activate SS a
FEATREQ
b
featreq c
Activate SS Ack
d
9
10 Figure 73: Invocation of Barring of Supplementary Service Control – GSM Foreign Mode
11
12 a. A native ANSI-41subscriber attempts to activate a feature to which he is not authorized. The
13 MSC sends an Activate SS message to the IIF emulating the subscriber’s HLR.
14
15 b. The IIF issues a FeatureRequest INVOKE message to the HLR.
16
17 c. The HLR, determining that the subscriber is not authorized, sends a FeatureRequest RETURN
18 RESULT, with FeatureResult set to Unsuccessful to the IIF.
19
20 d. The IIF issues an Activate SS acknowledgement, with User Error set to SS Subscription
21 Violation to the VLR. The VLR denies the activation.
2-94
X.S0023
2 This scenario describes the successful ODB barring of supplementary services management for a
3 native GSM subscriber in an ANSI-41 network.
ANSI-41 GSM
MSC/ IIF HLR
VLR
FEATREQ a
Activate SS
b
Activate SS Ack c
featreq
d
4
5 Figure 74: Invocation of Barring of Supplementary Services Management – ANSI-41 Foreign
6 Mode
7 a. A native GSM subscriber with ODB barring of Supplementary Services Management active,
8 roaming in an ANSI-41 network, attempts to activate a supplementary service. The MSC sends
9 a FeatureRequest INVOKE to the IIF emulating the subscriber’s HLR.
10
11 b. The IIF issues an Activate SS message to the HLR.
12
13 c. The HLR, determining that ODB barring is in effect for this subscriber, sends an Activate SS
14 acknowledgement, with User Error set to SS Subscription Violation to the IIF.
15
16 d. The IIF issues a FeatureRequest RETURN RESULT, with FeatureResult set to Unsuccessful to
17 the VLR. The VLR denies the activation.
2-95
X.S0023
1 4.11 Short Message Service

2 This section illustrates the interactions between network entities in various situations related to GSM
3 and ANSI-41 foreign mode operation for Short Message Service.
4 4.11.1 Assumptions
5 The following assumptions are made in the message flows:
6 • The SMS-GMSC and SMS-IWMSC functions are combined in the SMSC.
7 • The user data received in the GSM SMS-DELIVER and GSM SMS-SUBMIT is tunneled from
8 the Short Message Entity (SME) to the Mobile Station (MS).
9 • When the MS wishes to originate a short message and is operating in foreign mode, it shall use
10 a teleservice server address which maps to the IIF. When the IIF receives this address it shall
11 be mapped to the corresponding message center.
12 • The MO SMS first goes to the originator’s Message Center (MC) and then to the recipient’s
13 Message Center.
14 Only foreign mode message flows are described. Native mode message flows are as defined for the
15 native mode technology except in 4.11.2 which addresses GHOST/WEMT-CMT interworking within
16 an ANSI-41 network. Note: CMT applies for CDMA or ANSI-136 subscribers, GHOST applies only
17 for ANSI-136 subscribers, and WEMT only for CDMA subscribers.
2-96
X.S0023
1 4.11.2 Mobile Station only Supports GHOST/WEMT

2 If the mobile station only supports GHOST (GSM Hosted SMS Teleservice) or WEMT, there shall
3 be a need for CMT (Cellular Messaging Transport) to GHOST/WEMT and GHOST/WEMT to CMT
4 conversion in the ANSI-41 network (i.e., in native mode), most probably in the Message Centers.
5 This is depicted in the next two diagrams.
6 4.11.2.1 Short Message from CMT Mobile Station to GHOST/WEMT Mobile Station
7 both in Native Mode
MS-A ANSI-41 MC-A MC-B ANSI-41 ANSI-41

MSC HLR MSC
SMD-REQ(CMT)
a
SMDPP(CMT) b
smdpp[ACK] c
SMD-ACK d
SMDPP(CMT)
e
smdpp[ACK]
f
SMSREQ g
smsreq h
SMDPP(GHOST/WEMT) i
(SMS delivered to MS
using GHOST/WEMT) j
smdpp [ACK] k
8
9 Figure 75: Short Message from a TDMA or CDMA CMT phone to a GHOST or WEMT mobile
10 station, both in native mode
11 Notes:
12 Message Center B (MC-B) is responsible for converting CMT to GHOST/WEMT.
13 MC-A and MC-B could be one and the same.

14
2-97
X.S0023
1 4.11.2.2 Short Message sent from GHOST/WEMT Mobile Station to CMT Mobile
2 Station, both in Native Mode
MS-A ANSI-41 MC-A MC-B ANSI-41 ANSI-41

MSC HLR MSC
SMD-REQ(GHOST/WEMT)
a
SMDPP(GHOST/WEMT) b
smdpp[ACK] c
SMD-ACK d
SMDPP(CMT)
e
smdpp[ACK]
f
SMSREQ g
smsreq h
SMDPP(CMT) i
(SMS delivered to MS
using CMT) j
smdpp [ACK] k
3
4 Figure 76: Short Message from a GHOST or WEMT mobile station to a TDMA CMT or CDMA
5 CMT Phone, both in native mode
6 Notes:
7 Message Center A (MC-A) is responsible for converting GHOST/WEMT to CMT. This is done so
8 that only the operators using GHOST/WEMT would need to have a modified Message Center. In
9 the event that MS-B also uses GHOST/WEMT and that MC-A is not the same as MC-B, then MC-B
10 would have to re-convert from CMT to GHOST/WEMT, unless there is some way for MC-A to know
11 that MS-B also uses GHOST/WEMT.
12 In the event that MC-A and MC-B are one and the same, and that MS-B also uses GHOST/WEMT,
13 then no conversion is needed.
14
2-98
X.S0023
1 4.11.3 Mobile Terminating SMS in GSM Foreign Mode

2 This section discusses the delivery of the short message, i.e. how to deliver it to the roaming
3 subscriber once the message has been delivered in the recipient’s Message Center.
4 On the ANSI-41 side, the short message may have been originated in CMT or GHOST/WEMT
5 format. So the IIF has to convert either CMT or GHOST/WEMT to GSM SMS.
6 4.11.3.1 Successful Mobile Terminating ANSI-41SMS (CMT) mapped to GSM SMS
ANSI-41 ANSI-41 GSM

MC HLR IIF MSC/ MS
VLR
SMS
Delivery
a
SMSREQUEST
b
smsrequest
c
SMDPP (CMT)
d
FORWARD SHORT MESSAGE
e
SMS Delivery
f
SMS Delivery Ack
g
Forward Short Message
h
smdpp [ACK]
i
7
8
9 Figure 77: Successful Mobile Terminating ANSI-41SMS (CMT) mapped to GSM SMS
10
11 a. The ANSI-41Message Center (MC) receives a short message for a specific subscriber. Note:
12 This step is shown for completeness only and is not repeated in subsequent call flows.
13
14 b. The Message Center sends an SMS Request message to the ANSI-41 HLR of the short
15 message recipient to request a routing address for delivering the short message to that
16 subscriber.
17
18 c. Since the subscriber has a current valid location stored in the HLR, the HLR returns it to the
19 MC in the SMS Request Return Result message.
20
21 d. The Message Center then sends a Short Message Delivery Point to Point message to the IIF,
22 which is seen as the current serving ANSI-41 MSC/VLR for that subscriber. Note that in this
23 case, the format used by the MC is the CMT format (Cellular Messaging Transport). Note that
24 alternatively, the ANSI-41MC could translate the original CMT SMS to GHOST/WEMT format
25 before sending it to the IIF if the IIF only supports the GHOST format. In this case the IIF would
26 convert TDMA GHOST or CDMA WEMT into GSM format (see Section 4.11.3.2) instead of
27 ANSI-41CMT into GSM format.
2-99
X.S0023
1 e. Upon reception of the Short Message Delivery Point to Point message from the ANSI-41MC,
2 the IIF originates a FORWARD SHORT MESSAGE to the serving GSM MSC/VLR after having
3 translated the short message into GSM format. The IIF is then acting as a GSM SMS-GMSC.
4
5 f. The serving GSM MSC/VLR sends the short message to the mobile station. Note: This step is
6 shown for completeness only and is not repeated in subsequent call flows.
7
8 g. The mobile station acknowledges the delivery of the short message. Note: This step is shown
9 for completeness only and is not repeated in subsequent call flows.
10
11 h. The serving GSM MSC/VLR sends the result of the Forward Short Message to the IIF.
12
13 i. The IIF sends the result of the Short Message Delivery Point to Point to the ANSI-41Message
14 Center.
2-100
X.S0023
1 4.11.3.2 Successful Mobile Terminating ANSI-41SMS (GHOST/WEMT) Mapped to GSM

2 SMS
ANSI-41 GSM
MC HLR IIF VMSC
SMSREQ
a
smsreq
b
SMDPP
c
d
e
smdpp [ACK]
f
3
4 Figure 78: Successful Mobile Terminating ANSI-41SMS (GHOST/WEMT) mapped to GSM SMS
5 a. The ANSI-41 MC sends a SMSRequest Invoke message to the HLR, including as arguments
6 the MIN (MSISDN) of the mobile station and SMS Notification Indicator.
7 b. The HLR determines if the message shall be forwarded to the MS and sends a response back
8 in a SMSRequest Return Result, with the SMS_Address set to the IIF address (point code or
9 E.164 address).
10 c. The MC formats a GHOST/WEMT teleservice and sends it to the IIF in an SMDPP message.
11 d. Upon receipt of the SMDPP message, the IIF builds a FORWARD SHORT MESSAGE,
12 stripping off the GHOST/WEMT teleservice and using the encapsulated GSM SMS transfer
13 PDU, and routes it to the VMSC.
14 e. The VMSC packages the GSM SMS RP-DATA into a CP-DATA message and delivers it across
15 the GSM air interface to the mobile station. The mobile station acknowledges receipt of the CP-
16 DATA and RP-DATA messages via CP-ACK and CP-ACK[RP-ACK], respectively. Upon
17 successful receipt of the RP-ACK, the VMSC shall send a positive acknowledgement Forward
18 Short Message back to the IIF.
19 f. The IIF maps the received Forward Short Message into a SMDPP Return Result and sends it to
20 the MC.
2-101
X.S0023
1 4.11.3.3 Unsuccessful Mobile Terminated Delivery (Failure at MSC)
2 The following scenario applies to short message delivery failure in either CMT or GHOST/WEMT
ANSI-41 GSM
MC HLR IIF VMSC
SMSREQ
a
smsreq
b
SMDPP
c
d
e
smdpp [NAK]
f
3 format.
4 Figure 79: Unsuccessful Mobile Terminated Delivery (Failure at MSC)

5
10 E.164 address).
11 c. The MC formats a GHOST/WEMT teleservice or a CMT short message and sends it to the IIF in
12 an SMDPP message.
15 PDU, and routes it to the VMSC. If the message received is in the CMT format, the IIF maps
16 this information into a short message in GSM format.
17 e. The VMSC packages the GSM SMS RP-DATA into a CP-DATA message and delivers it across
18 the GSM air interface to the mobile station. The mobile station negatively acknowledges either
19 the CP-DATA message or the RP-DATA message. The VMSC sends a negative
20 acknowledgement Forward Short Message (with appropriate cause value) back to the IIF.
22 the MC. In addition, the IIF sets one of the GSM SMS flags as defined in the GSM 03.40
23 specification [35] according to the error cause received from the VMSC; that is, the Mobile
24 Subscriber Not Reachable Flag (MNRF) shall be set if the error cause is “absent subscriber”,
25 and the Memory Capacity Exceeded Flag (MCEF) shall be set if the error cause is “memory
26 capacity exceeded”. Additionally, the IIF emulating the ANSI-41 MSC shall set and store the
2-102
X.S0023
1 SMS Delivery Pending flag with the MC parameters received in the SMDPP (for later delivery in
2 the SMSNOT) – note that this “SMS Delivery Pending” flag/data serves the same purpose as a
3 GSM HLR’s “Message Waiting Data” flag/data. [However, note that if an ANSI-41 REGCAN is
4 received from the ANSI-41 HLR before the SMS Delivery Pending Flag is cleared, then the
5 regcanc response shall contain the SMS_MessageWaitingIndicator, and all flags are cleared
6 (i.e., MNRF, MCEF, and SMS Delivery Pending Flag)].
7
2-103
X.S0023
1 4.11.3.4 Unsuccessful Mobile Terminated Delivery (Failure at IIF)
3 format.
4
ANSI-41 GSM
MC HLR IIF VMSC
SMSREQ
a
smsreq
b
SMDPP
c
smdpp [NAK]
d
5 Figure 80: Unsuccessful Mobile Terminated Delivery (Failure at IIF)

7 the MIN (MSISDN) or IMSI of the mobile station and SMS Notification Indicator.
10 E.164 address).
12 d. Upon receipt of the SMDPP message, the IIF examines the GSM 03.40 HLR flags
13 (MNRF/MCEF) and determines that the MS is unable to receive a Short Message. The IIF
14 indicates this fact in the SMDPP Return Result. It includes the cause for the failure in the
15 SMS_CauseCode parameter of the SMDPP Return Result. The IIF shall set & store the SMS
16 Delivery Pending Flag with the data received in the SMDPP message (for later delivery in the
17 SMSNOT).
2-104
X.S0023
1 4.11.3.5 Alerting for an ANSI-41Subscriber in GSM Foreign Mode
2 The following scenario applies to short messages originated in either CMT or GHOST/WEMT
3 format.
4
ANSI-41 GSM
MC HLR IIF VMSC
READY FOR SM
a
Ready fro SM
b
SMSNOT
c
smsnot
d
5 Figure 81: Alerting for an ANSI-41Subscriber in GSM Foreign Mode

6
7 a. The VMSC sends a READY FOR SM (MAP V2) to the IIF, including as arguments the IMSI and
8 Alert Reason. Note: The SMS notification can also be triggered when the VMSC sends a
9 NoteMSPresent (MAP V1) or an UpdateLocation.
10 b. If the IIF has GSM 03.40 flags set, then these flags shall be cleared according to the “alert
11 reason”; that is, if the “alert reason” is “memory available”, then both the MCEF and MNRF flags
12 are cleared, and if the “alert reason” is “MS present”, then the MNRF flag is cleared. If the
13 UpdateLocation is received, then the MNRF flag is cleared. The IIF sends a Ready for SM
14 response to the VMSC with no arguments.
15 c. If the IIF has the SMS Delivery Pending Flag set, and if the MCEF flag is not set, then the IIF
16 sends a SMSNOT to each of the subscriber’s MCs stored with the SMS Delivery Pending Flag.
17 The SMSNOT shall contain; the MIN (MSISDN) as mapped from the IMSI, ESN, and
18 SMS_Address containing the IIF address.
19 d. The MC sends a SMSNOT Return Result to the IIF, then the IIF clears the SMS Delivery
20 Pending Flag, then proceeds to send the mobile station a mobile terminated GHOST/WEMT
21 teleservice message according to 4.11.3.2.
22
2-105
X.S0023
1 4.11.4 Mobile Terminated SMS in ANSI-41 Foreign Mode

2 This section describes the message flows for delivering a CMT or GHOST/WEMT teleservice when
3 the mobile station is operating in ANSI-41 Foreign Mode. Since on the ANSI-41 side, the short
4 message may need to be in CMT or GHOST/WEMT format, the IIF has to convert the GSM SMS to
5 either CMT or GHOST/WEMT.
6 4.11.4.1 Successful GSM SMS mapped to ANSI-41(CMT) SMS
GSM ANSI-41
SMSC HLR IIF MSC
SMS
Delivery
a
SEND ROUTING INFO FOR SM

b
Send Routing Info For SM
c
FORWARD SHORT MESAGE
d
SMDPP (CMT) e
(SMS delivered to f
Mobile Station)
smdpp [CMT]
g
h
8 Figure 82: Successful GSM SMS mapped to ANSI-41(CMT) SMS

9 a. The GSM Short Message Service Center (SMSC) receives a short message for a specific
10 subscriber. Note: This step is shown for completeness only and is not repeated in subsequent
11 call flows.
12
13 b. The SMS-GMSC originates a Send Routing Info for Short Message to the GSM HLR of the
14 short message recipient to request a routing address for delivering the short message to that
15 subscriber.
16
17 c. Since the subscriber has a current valid location stored in the HLR, the HLR returns it to the
18 SMS-GMSC in the Send Routing Info for Short Message Result message.
19
20 d. The SMS-GMSC then sends a Forward Short Message to the IIF, seen as the serving GSM
21 MSC/VLR.
22
23 e. Upon reception of the Forward Short Message from the SMS-GMSC, the IIF originates a Short
24 Message Delivery Point to Point message to the serving ANSI-41 MSC/VLR after having
2-106
X.S0023
1 translated the short message into IS-41 CMT format. The IIF is then acting as an
2 ANSI-41Message Center.
3
4 f. The serving ANSI-41 MSC/VLR sends the short message to the mobile station and an
5 acknowledgement is sent back to the MSC/VLR.
6
7 g. The serving ANSI-41 MSC/VLR sends the result of the Short Message Delivery Point to Point
8 message to the IIF.
9
10 h. The IIF sends the result of the Forward Short Message to the GSM SMS-GMSC.
11
2-107
X.S0023
1 4.11.4.2 Successful GSM SMS mapped to ANSI-41(GHOST/WEMT) SMS
2 This method uses the tunneling concept. Instead of translating the GSM SMS to an ANSI-41CMT
3 SMS format, the IIF shall package the GSM SMS into a TDMA SMS with the teleservice GHOST
4 (GSM Hosted SMS Teleservice) or CDMA SMS with teleservice WEMT.
5
GSM ANSI-41
SMSC HLR IIF MSC

a

b
c
SMDPP (GHOST)
d
smdpp [ACK]
e
f
REPORT SM DELIVERY STATUS
g
Report SM Delivery Status
h
6 Figure 83: Successful GSM SMS mapped to ANSI-41(GHOST/WEMT) SMS

7
8 a. The SMSC receives a request to deliver a short message to a GSM subscriber. It sends to the
9 GSM HLR a SEND ROUTING INFO FOR SM, including as arguments the MSISDN, Priority,
10 and Service Centre address.
12 to the SMSC in a Send Routing Info for SM, including as arguments the IMSI of the MS and
13 Network Node Number of the IIF.
14 c. The SMSC originates a FORWARD SHORT MESSAGE to the address provided by the HLR
15 (i.e., IIF), including as arguments the IMSI, Service Centre Address, and GSM SMS-DELIVER
16 PDU (and optionally if more messages are to be sent).
2-108
X.S0023
1 Upon receipt of the FORWARD SHORT MESSAGE, the IIF shall build an ANSI-41 SMDPP ,
2 encapsulating the GSM SMS transfer PDU in the GHOST/WEMT teleservice. The IIF shall
3 route the SMDPP message to the serving MSC. The serving MSC maps the SMDPP
4 message into an R-DATA message and sends it to the mobile station over the TDMA or
5 CDMA air interface. The mobile station shall acknowledge receipt of the R-DATA message
6 and GHOST/WEMT teleservice by sending an R-DATA ACCEPT message to the MSC.
7
8 d. After receiving the R-DATA ACCEPT message, the serving MSC sends a positive
9 acknowledgement SMDPP Return Result to the IIF.
10 e. The IIF maps the received SMDPP Return Result to a Forward Short Message, and sends it to
11 the GSM SMSC.
12 f. The SMSC send a REPORT SM DELIVERY STATUS to the HLR, including as arguments the
13 MSISDN, SMSC Address, and Successful Transfer. The SMSC sends this message based on
14 the procedures described in GSM 03.40 [35] and GSM 09.02 [4].
15 g. The HLR shall set the appropriate flags as specified in the GSM specifications (GSM 09.02 and
16 03.40), then send a Report SM Delivery Status to the SMSC.
2-109
X.S0023
1 4.11.4.3 Unsuccessful GSM SMS mapped to ANSI-41SMS (Failure at MS)
2 The following scenario applies to short messages delivered in either CMT or GHOST/WEMT format.
GSM ANSI-41
SMSC HLR IIF MSC

a

b
c
SMDPP
d
smdpp [NAK]
e
f
g
h
3 Figure 84: Successful GSM SMS mapped to ANSI-41SMS (Failure at MS)

4
7 and Service Center address.
12 (i.e., IIF), including as arguments the IMSI, Service Center Address, and GSM SMS-DELIVER
14 d. Upon receipt of the FORWARD SHORT MESSAGE, the IIF builds an ANSI-41 SMDPP
15 message, encapsulating the GSM SMS transfer PDU in a GHOST/WEMT teleservice, and
16 routes it to the serving MSC. The IIF can also convert the message into ANSI-41CMT format.
17 The serving MSC converts the SMDPP message into an R-DATA message and sends it to the
18 mobile station over the TDMA or CDMA air interface. The mobile station returns an R-DATA
19 REJECT message to the MSC, indicating an error in the receipt of the message.
20 e. Upon receipt of the R-DATA REJECT, the serving MSC maps the ANSI-41R-Cause code to the
21 appropriate ANSI-41 SMS_CauseCode value, and sends a negative acknowledgement SMDPP
22 Return Result back to the IIF.
2-110
X.S0023
1 f. The IIF sets the SMS Delivery Pending Flag in the IIF and maps the received SMDPP Return
2 Result into a Forward Short Message and sends it to the SMSC, after mapping the
3 SMS_CauseCode to the appropriate GSM MAP error.
4 g. The SMSC sends a REPORT SM DELIVERY STATUS to the HLR, including as arguments the
5 MSISDN, SMSC Address, and Error Cause. The SMSC sends this message based on the
6 procedures described in GSM 03.40 [35] and GSM 09.02 [4].
7 h. The HLR shall set the appropriate flags as specified in the GSM specifications (GSM 09.02 and
2-111
X.S0023
1 4.11.4.4 Unsuccessful Delivery to GSM Subscriber (Postponed at MSC)
2 The following scenario applies to short messages delivered in either CMT or GHOST/WEMT format.
GSM ANSI-41
SMSC HLR IIF MSC

a

b
c
SMDPP
d
smdpp [NAK]
e
f
g
h
3
4 Figure 85: Unsuccessful Delivery to GSM Subscriber (Postponed at MSC)
14 d. Upon receipt of the FORWARD SHORT MESSAGE, the IIF builds an ANSI-41 SMDPP
16 routes it to the serving MSC. The IIF can also convert the message into ANSI-41CMT format.
17 The addressed MS is temporarily unavailable for short message delivery and notification was
18 requested.
19 e. The MSC responds with a negative acknowledgement SMS_CauseCode carried in the SMDPP
20 Return Result indicating delivery is postponed and returns it to the source of the corresponding
21 SMDPP (i.e., IIF). The MSC sets its SMS Delivery Pending Flag.
2-112
X.S0023
1 f. The IIF sets the SMS Delivery Pending Flag in the IIF and maps the received SMDPP Return
2 Result into a Forward Short Message and sends it to the SMSC, after mapping the
3 SMS_CauseCode to the appropriate GSM MAP error.
4 g. The SMSC sends a REPORT SM DELIVERY STATUS to the HLR, including as arguments the
5 MSISDN, SMSC Address, and Error Cause. The SMSC sends this message based on the
6 procedures described in GSM 03.40 [35] and GSM 09.02 [4].
7 h. The HLR shall set the appropriate flags as specified in the GSM specifications (GSM 09.02 and
2-113
X.S0023
1 4.11.4.5 Unsuccessful Delivery to GSM Subscriber (Failure at IIF)
GSM ANSI-41
SMSC HLR IIF MSC

a

b
c
d
e
f
3 Figure 86: Unsuccessful Delivery to GSM Subscriber (Failure at IIF)

13 d. Upon receipt of the FORWARD SHORT MESSAGE at the IIF, if the subscriber is known to be
14 unavailable or the SMS Waiting Indicator flag is set, then the IIF builds a Forward Short
15 Message and send it back to the SMSC.
16 e. The SMSC sends a REPORT SM DELIVERY STATUS to the HLR, including as arguments the
17 MSISDN, SMSC Address, and Error Cause.
18 f. The HLR shall set the appropriate flags as specified in the GSM specifications (GSM 09.02 and
19 03.40) and sends a Report SM Delivery Status to the SMSC. The SMSC sends this message
20 based on the procedures described in GSM 03.40 [35] and GSM 09.02 [4].
2-114
X.S0023
1 4.11.4.6 Alerting for a GSM Subscriber in ANSI-41 Foreign Mode
2 In the event that the delivery of the short message to the ANSI-41 network is not possible, the IIF
3 shall be notified by the serving ANSI-41 MSC/VLR when the subscriber is available again. This shall
4 be done by receiving a Registration Notification or an SMS Notification message. This is illustrated
5 in the following diagram. The following scenario applies to short messages delivered in either CMT
6 or GHOST/WEMT format.
7
GSM ANSI-41
SMSC HLR IIF MSC
SMSNOT or REGNOT
a
READY FOR SM
b
Ready for SM
c
smsnot or regnot
d
ALERT SERVICE CENTRE

e
alert service centre

f
8 Figure 87: Alerting for a GSM Subscriber in ANSI-41 Foreign Mode

9 a. The IIF receives either (1) an SMSNOT, or (2) a REGNOT when the ANSI-41 SMS Delivery
10 Pending Flag is set at the IIF or the SMS_Address parameter is present in the REGNOT.
11 b. The IIF alerts the GSM HLR by sending a READY FOR SM including as arguments the IMSI
12 and MS-Present.
13 c. The HLR shall send a Ready for SM to the IIF. If the SMS Waiting Indicator flag is set in the IIF,
14 then it is cleared.
15 d. The IIF returns a Return Result acknowledgement message.
16 e. The HLR originates an ALERT SERVICE CENTRE to the SMSC address stored in the HLR,
17 including as arguments the MSISDN, and SMSC Address.
18 f. The SMSC sends an Alert Service Centre to the HLR, then proceeds to send the mobile station
19 a mobile terminated GSM SMS message according to 4.11.4.2.
2-115
X.S0023
1
2 4.11.5 Message Flows for Mobile Originated SMS in GSM Foreign Mode
3 This section describes the message flows for originating a short message to the subscriber’s home
4 message center when the mobile station is operating in GSM Foreign Mode. The following
5 scenarios apply to short messages delivered to the MC in either CMT or GHOST/WEMT format.
6 4.11.5.1 Successful Mobile Originated Delivery
GSM ANSI-41
VMSC HLR IIF MC

a
SMDPP
b
smdpp [ACK]
c
d
7 Figure 88: Successful Mobile Originated Delivery

8 a. The VMSC originates a FORWARD SHORT MESSAGE to the address provided by the MS
9 (i.e., IIF), including as arguments the Service Centre Address, MSISDN and GSM SMS-
10 SUBMIT PDU.
11 b. Upon receipt of the FORWARD SHORT MESSAGE, the IIF builds an ANSI-41 SMDPP
13 routes it to the originator’s home MC. The IIF can also map the Forward Short Message into a
14 CMT short message.
15 c. The MC sends a positive acknowledgement SMDPP Return Result to the IIF.
16 d. The IIF maps the received SMDPP Return Result to a Forward Short Message, and sends it to
17 the VMSC.
18
2-116
X.S0023
1 4.11.5.2 Unsuccessful Mobile Originated (Failure at MC)
GSM ANSI-41
VMSC HLR IIF MC

a
SMDPP
b
smdpp [NAK]
c
d
2 Figure 89: Unsuccessful Mobile Originated (Failure at MC)

3
6 SUBMIT PDU.
8 message encapsulating the GSM SMS transfer PDU in a GHOST/WEMT teleservice, and
9 routes it to the MC. The IIF can also map the Forward Short Message into a CMT short
10 message.
11 c. The MC sends a negative acknowledgement SMDPP Return Result to the IIF.
12 d. The IIF maps the received SMDPP Return Result to a Forward Short Message with the
13 appropriate cause code value, and sends it to the VMSC.
14
2-117
X.S0023
1 4.11.5.3 Unsuccessful Mobile Originated (Failure at IIF)
GSM ANSI-41
VMSC HLR IIF MC

a

b
2
3 Figure 90: Unsuccessful Mobile Originated (Failure at IIF)
4
7 SUBMIT PDU.
8 b. Upon receipt of the FORWARD SHORT MESSAGE, the IIF builds a negative acknowledgement
9 Forward Short Message and sends it to the VMSC.
10
2-118
X.S0023
1 4.11.6 Message Flows for Mobile Originated SMS in ANSI-41 Foreign Mode
3 message center when the mobile station is operating in ANSI-41 Foreign Mode. The following
4 scenarios apply to short messages originated in either CMT or GHOST/WEMT format.
5 4.11.6.1 Successful Mobile Originated Delivery
ANSI-41 GSM
VMSC HLR IIF SMSC
SMDPP
a

b

c
smdpp [ACK]
d
6 Figure 91: Successful Mobile Originated Delivery – ANSI-41 Foreign Mode

7 a. The VMSC originates a SMDPP invoke to the address provided by the MS (i.e., IIF), including
8 as arguments the Teleservice Server Address, MIN (MSISDN), and GSM SMS-SUBMIT PDU
9 encapsulated in the GHOST/WEMT teleservice. The mobile originated message can also be in
10 the CMT format.
11 b. Upon receipt of the SMDPP invoke, the IIF builds a FORWARD SHORT MESSAGE, and routes
12 it to the SMSC.
13 c. The SMSC sends a positive acknowledgement Forward Short Message to the IIF.
14 d. The IIF maps the received Forward Short Message to a SMDPP Return Result and sends it to
15 the VMSC.
2-119
X.S0023
1 4.11.6.2 Unsuccessful Mobile Originated (Failure at SMSC)
ANSI-41 GSM
VMSC HLR IIF SMSC
SMDPP
a

b
c
smdpp [NAK]
d
2 Figure 92: Successful Mobile Originated (Failure at SMSC) – ANSI-41 Foreign Mode
3
5 as arguments the Teleservice Server Address, MIN (MSISDN) and GSM SMS-SUBMIT PDU
7 the CMT format.
8 b. Upon receipt of the SMDPP message, the IIF builds a FORWARD SHORT MESSAGE,
10 PDU, and routes it to the SMSC.
11 c. The SMSC sends a negative acknowledgement Forward Short Message to the IIF.
12 d. The IIF maps the received Forward Short Message into a SMDPP Return Result and sends it to
13 the VMSC.
2-120
X.S0023
ANSI-41 GSM
VMSC HLR IIF SMSC
SMDPP
a
smdpp [NAK]
b
3 Figure 93: Unsuccessful Mobile Originated (Failure at IIF) – ANSI-41 Foreign Mode
4
6 as arguments the Teleservice Server Address, MIN (MSISDN) and GSM SMS-SUBMIT PDU
8 the CMT format.
9 b. Upon receipt of the SMDPP message, the IIF builds a negative acknowledgement SMDPP
10 Return Result and sends it to the VMSC.
2-121
X.S0023
1 4.12 Message Waiting Notification

2 This contribution illustrates the interactions between network entities in various situations related to
3 GSM and ANSI-41 foreign mode operation and Message Waiting Notification.
4 4.12.1 GSM Foreign Mode

5 For a native ANSI-41subscriber roaming in a GSM environment, there can be two events that
6 trigger the IIF to send the Message Waiting Notification (MWN) using the GSM SMS to the Mobile
7 Station (MS). The first one is at registration (location update), if there is an indication in the ANSI-41
8 HLR that messages have been delivered to the subscriber’s voice mail box, the ANSI-41 HLR shall
9 indicate that in the Registration Notification Return Result message. This shall trigger the IIF to send
10 a GSM SMS with the MWN information. This is shown in Section 4.12.1.1 The second event is
11 when the HLR receives a Message Waiting Notification for a subscriber that is already registered. In
12 this case, the ANSI-41 HLR shall send a Qualification Directive message to the IIF which shall
13 translate it into a GSM SMS with MWN indication. This is shown in Section 4.12.1.2
2-122
X.S0023
1 4.12.1.1 Indicator in ANSI-41 Registration Notification Return Result mapped to GSM

2 SMS
4 ANSI-41
VMS HLR IIF GSM MS
5 MSC/VLR
Vmail
6
Delivery a
7 “Message Waiting
Notification”
8 b
9 Update Loc Req
c
10 UPDATE
11 LOCATION
d
12
REGNOT
13 e
regnot (MWNCOUNT,
14 MWNTYPE)
f
15
16 INSERT_SUB_DATA g
17
Insert_sub_data h
18
19 update location i
20
Update Loc Accept
21 j
FORW.SHORT
22 MESSAGE (MWN)
k
23
24 SMS Delivery (MWN) l
25
SMS Delivery Ack m
26 Forw.Short
27 Message
n
28
29 Figure 94: Indicator in ANSI-41 Registration Notification Return Result mapped to GSM SMS
30 a. The Voice Mail System (VMS) receives a voice mail for a specific subscriber.
31
32 b. The VMS send the “Message Waiting Notification” (MWN) to the ANSI-41 HLR of the voice mail
33 recipient. Note that the interface between the VMS and the ANSI-41 HLR is not standardized in
2-123
X.S0023
1 ANSI-41 [2]. Note also that at that point in time, the subscriber is not registered in any serving
2 system, so the HLR just keeps the information that a voice mail was received.
3
4 c. The Mobile Station accesses a serving system and originates an update location request.
5
6 d. The Update Location is sent from the serving GSM MSC/VLR to the IIF, seen as the GSM HLR
7 for that subscriber.
8
9 e. The IIF sends a Registration Notification to the ANSI-41 HLR of the subscriber.
10
11 f. The ANSI-41 HLR replies with the Registration Notification Return Result containing the
12 “Message Waiting Notification” information that consists of two parameters:
13 MessageWaitingNotificationCount (MWNCOUNT) and MessageWaitingNotificationType
14 (MWNTYPE). For a description of these parameters, see the ANSI-41 specifications, sections
15 6.5.2.78 and 6.5.2.79 [2].
16
17 At this point, the IIF sets the MWN flag. This is an indication that Message Waiting Notification
18 is to be delivered to the Mobile Station.
19
20 g. The IIF sends Insert Subscriber Data to the serving GSM MSC/VLR. Note that there could be
21 more than one Insert Subscriber Data message depending on the subscriber profile.
22
23 h. The serving GSM MSC/VLR returns the Insert Subscriber Data result. Note that there could be
24 more than one such result message, one matching every Insert Subscriber Data message.
25
26 i. The IIF completes the location update by sending the Update Location result message to the
27 serving GSM MSC/VLR.
28
29 j. The serving GSM MSC/VLR confirms the update location to the mobile station.
30
31 k. Since the REGNOT return result from event f contained the Message Waiting Notification
32 information, this triggers the IIF to originate an SMS with MWN information by sending Forward
33 Short Message to the serving GSM MSC/VLR. The IIF is then acting as a GSM SMS-GMSC.
34 The IIF is to encode the MWN information in the SMS with three methods, namely, UDH, DCS,
35 and CPHS. See to Volume 3 for the encoding details.
36
37 l. The serving GSM MSC/VLR sends the short message with the MWN information to the mobile
38 station.
39
40 m. The mobile station acknowledges the delivery of the short message.
41
42 n. The serving GSM MSC/VLR sends the result of the Forward Short Message to the IIF.
43
44 At this point, the IIF clears the MWN flag. The reception of the Forward Short Message Result
45 without error indicates that the MWN information was delivered successfully to the Mobile
46 Station.
2-124
X.S0023
1 4.12.1.2 ANSI-41 Qualification Directive mapped to GSM SMS
VMS ANSI-41 IIF GSM

MS
HLR MSC/VLR
2
3
4
Vmail
5 Delivery
a
7 Notification”
b
8 QUALDIR (MWNCOUNT,
MWNTYPE)
9 c
10 qualdir
d
11 FORW.SHORT
12 MESSAGE (MWN)
e
13
SMS Delivery (MWN)
14 f
15 SMS Delivery Ack

g
16 Forw.Short
Message
17 h
18 Figure 95: ANSI-41 Qualification Directive mapped to GSM SMS

20
23 ANSI-41 [2].
24
25 c. Since the subscriber has a current valid location stored in the HLR, the HLR initiates a
26 Qualification Directive message with the MWN information to the IIF acting as the serving
27 ANSI-41 MSC/VLR. The MWN information consists of two parameters:
29 (MWNTYPE). For a description of these parameters, see to the ANSI-41-D specifications,
30 sections 6.5.2.78 and 6.5.2.79 [2].
31
34
35 d. The IIF sends the result of the Qualification Directive message to the ANSI-41 HLR.
36
37 e. The IIF also originates an SMS with MWN information by sending a Forward Short Message to
38 the serving GSM MSC/VLR. The IIF is then acting as a GSM SMS-GMSC. The IIF is to encode
2-125
X.S0023
1 the MWN information in the SMS with three methods, namely, UDH, DCS, and CPHS. See to
2 Volume 3 for the encoding details.
3
4 f. The serving GSM MSC/VLR sends the short message with the MWN information to the mobile
5 station.
6
7 g. The mobile station acknowledges the delivery of the short message.
8
9 h. The serving GSM MSC/VLR sends the result of the Forward Short Message to the IIF.
10
13 Station.
2-126
X.S0023
1 4.12.1.3 Handling when GSM MSC/VLR only supports GSM Phase 1 (MAP V1)
2 After the IIF has received a Qualification Directive message with MWN information or received the
3 MWN information through a Registration Notification Return Result, a Forward Short Message with
4 MWN information needs to be sent to the serving GSM MSC/VLR. This was shown in Sections
5 4.12.1.1 and 4.12.1.2. However, it is possible that the serving GSM MSC/VLR does not support the
6 MAP V2 Application Context. In this case, the IIF shall receive an ABORT message and shall re-
7 send the Forward Short Message with MWN information using MAP V1 instead of MAP V2. This is
8 illustrated in the following diagram.
9
GSM
10 IIF MSC/VLR MS
11
12 MWN “Information”
a
13 FORW.SHORT
MSG (MWN) – V2
14 b
15 ABORT
cc
16 FORW.SHORT
MSG (MWN) – V1
17 d
18
SMS Delivery (MWN)
19 e
20 SMS Delivery Ack

f
Forw.Short
21
Message
22 g
23
24 Figure 96: Handling when GSM MSC/VLR only supports GSM Phase 1 (MAP V1)
25 a. The IIF receives Message Waiting Notification (MWN) information from a Qualification Directive
26 or a Registration Notification Return Result. This was described in Sections 4.12.1.1 and
27 4.12.1.2.
30
31 b. The IIF originates an SMS with MWN information by sending Forward Short Message using
32 MAP V2 to the serving GSM MSC/VLR. The IIF is then acting as a GSM SMS-GMSC. The IIF is
33 to encode the MWN information in the SMS with three methods, namely, UDH, DCS, and
34 CPHS.
35
36 c. Since the serving GSM MSC/VLR does not support the MAP V2 Application Context, it returns
37 an Abort message to the IIF.
38
39 d. The IIF then re-sends a Forward Short Message with MWN information to the serving GSM
40 MSC/VLR, but this time using MAP V1. In this case, the MWN information can be encoded with
41 only two encoding methods, namely, DCS and CPHS.
42
43 e. The serving GSM MSC/VLR sends the short message with the MWN information to the mobile
44 station.
2-127
X.S0023
1
2 f. The mobile station acknowledges the delivery of the short message.
3
4 g. The serving GSM MSC/VLR sends the result of the Forward Short Message to the IIF.
5
8 Station.
2-128
X.S0023
1 4.12.1.4 Handling at SMS delivery failure at the IIF
2 This section describes the case where the error occurs at the IIF, for example, an unrecognized
3 Mobile Identity Number (MIN).
5 ANSI-41
VMS IIF
HLR
6
7 Vmail Delivery
a
Notification”
b
9
QUALDIR (MWNCOUNT),
10 MWNTYPE)
cc
11
Qualdir Return Error
12
13 Figure 97: Handling at SMS delivery failure at the IIF

15
18 ANSI-41 [2].
19
24 (MWNTYPE). For a description of these parameters, see to the ANSI-41-D specifications,
25 sections 6.5.2.78 and 6.5.2.79 [2].
26
27 d. An error is encountered so that the IIF cannot process the Qualification Directive message and
28 sends a Return Error message to the ANSI-41 HLR with the proper error code as per ANSI-41
29 Specifications, Chapter 6, Section 4.32.2, Table 42 [2].
2-129
X.S0023
1 4.12.1.5 Handling at SMS delivery failure at the MSC/VLR or at the Mobile Station
2 The IIF is to keep a Message Waiting Notification (MWN) flag for each subscriber in its database. In
3 the event of a failure to deliver a short message with MWN to the mobile station, the IIF is to keep
4 the MWN flag set. Another Forward Short Message with MWN information shall be sent, triggered
5 by the reception of a subsequent GSM Update Location message, a Ready for Short Message, or a
6 Note MS Present message. This is illustrated in the following diagram.
8 GSM
IIF MSC/ MS
9 VLR
10 MWN “Information”
a
11
FORW.SHORT
12 MSG (MWN) – V2
b
13
SMS Delivery (MWN)
14 cc
15 SMS Delivery Error

d
16 Error, Abort,
17 Reject, timeout
e
18
Time elapsed f
19
UPDATE LOCATION
20
g
21 READY FOR SM
(AlertReason) -V2
22 h
23 NOTE MS PRES – V1
i
24
“Acknowledgement”
25 j
FORW.SHORT h
26 MSG (MWN) – V2
k
27
SMS Delivery (MWN)
28 l
29 SMS Delivery Ack
m
30 Forw.Short
Message
31 n
32 Figure 98: Handling at SMS delivery failure at the MSC/VLR or at the MS
2-130
X.S0023
3 4.12.1.2.
6
8 MAP V2 to the serving GSM MSC/VLR. The IIF is then acting as a GSM SMS-GMSC. The IIF is
9 to encode the MWN information in the SMS with three methods, namely, UDH, DCS, and
10 CPHS. See to Volume 3 for the encoding details.
11
12 c. The serving GSM MSC/VLR may attempt to deliver the short message or may immediately find
13 out that there is an error and reply (step e below) to the IIF.
14
15 d. The Mobile Station returns an error message to the SMS delivery.
16
17 e. The serving GSM MSC/VLR sends an Error, Abort or Reject message to the IIF, either resulting
18 from the reception of an error message from the MS or from an internal event such as an error
19 or a timeout. Note also, that a timeout may also occur in the IIF itself. Note that this may result
20 in the IIF setting the GSM 03.40 MNRF/MCEF flag depending on the error cause received (see
21 section 4.11.3.3 “Unsuccessful Mobile Terminated Delivery (Failure at MSC)”.
22
23 f. Time elapsed.
24
25 g. A new serving GSM MSC/VLR sends an Update Location message to the IIF acting as a GSM
26 HLR for that subscriber. Note that the normal Update Location sequence is not shown in this
27 diagram. Or it could be a
28
29 h. Ready for Short Message (MAP V2) or a
30
31 i. Note MS Present Message (MAP V1)
32
33 j. The IIF shall reply with the corresponding acknowledgement message. Note that in the case of
34 the Note MS Present message, there shall be no acknowledgement. Upon receipt of g, h, or i
35 above, the procedures in section 4.11.3.5 “Alerting for an ANSI-41Subscriber in GSM Foreign
36 Mode” apply (GSM 03.40 flags may be cleared and the SMSNOT may be sent to the MC if
37 appropriate).
38
39 k. Triggered by event g, h, or i above, the IIF originates a new Forward Short Message with MWN
40 information to the serving GSM MSC/VLR. The IIF is to encode the MWN information in the
41 SMS with three methods, namely, UDH, DCS, and CPHS. See to Volume 3 for the encoding
42 details.
43
44 l. The serving GSM MSC/VLR sends the short message with the MWN information to the mobile
45 station.
46
48
49 n. The serving GSM MSC/VLR sends the result of the Forward Short Message to the IIF.
52 Station.
2-131
X.S0023
1 4.12.2 ANSI-41 Foreign Mode

2 For the native GSM subscribers roaming in ANSI-41 networks, there are two implementation
3 options. The GSM SMS containing the Message Waiting Notification information is either converted
4 by the IIF to a ANSI-41 Qualification Directive with Message Waiting Notification information as
5 shown in Section 4.12.2.1, or converted to a GHOST/WEMT ANSI-41short message as shown in
6 Section 4.12.2.2.
7 4.12.2.1 GSM SMS mapped to ANSI-41 Qualification Directive
8
GSM GSM GSM ANSI-41
SC SMS- HLR IIF MSC
GMSC
Vmail
Delivery
a
FORW. MOBILE
TERM SM (MWN)
SEND ROUTING
b
INFO FOR SM (MWN)
Send Routing
c
Info for SM
d
FORW. SHORT
MESSAGE (MWN)
QUALDIR(MWNCOUNT, e
MWNTYPE)
f
(MWN delivered to
Mobile Station) g
Qualdir
h
Forw. Short Message (error: absent sub.)
Forw. Mobile
i
Term SM (error)
j
Report SM (error)
DeliveryStatus
k
9
10
11 Figure 99: GSM SMS mapped to ANSI-41 Qualification Directive

12 a. The GSM Service Center (SC) receives a voice mail for a specific subscriber.
13
14 b. The SC sends the Forward Mobile Terminating Short Message with Message Waiting
15 Notification (MWN) information to the GSM SMS-GMSC.
16
17 c. The GSM SMS-GMSC enquires about the subscriber location by sending the Send Routing
18 Information For Short Message to the HLR.
19
20 d. The HLR replies with the Send Routing Information For Short Message result. It is assumed that
21 the native GSM subscriber has already made a registration in the ANSI-41 MSC/VLR.
22
23 e. The GSM SMS-GMSC originates an SMS with MWN information by sending Forward Short
24 Message to IIF then acting as a serving GSM MSC/VLR. This requires GSM MAP phase 2 or
25 higher.
26
2-132
X.S0023
2 is to be delivered to the Mobile Station. If the GSM SMS-GMSC only supports GSM MAP phase
3 1 and delivers MWN via pure text SMS, then a pure text SMS shall be delivered to the IIF. The
4 IIF shall then translate it into a CMT or GHOST/WEMT ANSI-41 SMS. Note that this then
5 becomes a simple SMS mapping covered in Section 4.12.2.2.
6
7 f. Upon reception of the Forward Short Message with MWN information, the IIF shall initiate a
8 Qualification Directive message with MWN information to the serving ANSI-41 MSC/VLR. The
9 IIF is then acting as an ANSI-41 HLR. The MWN information consists of two parameters:
11 (MWNTYPE). For a description of these parameters, see to the ANSI-41-D specifications
12 sections 6.5.2.78 and 6.5.2.79 [2]. Alternatively, a GHOST/WEMT short message could be sent
13 instead of the Qualification Directive message (see Section 4.12.2.2) if the IIF has the possibility
14 to confirm that the Mobile Station is SMS-capable.
15
16 g. In this step, the MWN information shall be delivered to the mobile station.
17
18 h. The serving ANSI-41 MSC/VLR sends the Qualification Directive Return Result to the IIF. Note
19 that this result message does not guaranty that the MWN information was delivered
20 successfully to the Mobile Station, it just means that the MSC/VLR received the Qualification
21 Directive message, therefore the MWN flag shall not be cleared at this point by the IIF.
22
23 i. The IIF sends the result of the Forward Short Message to the GSM SMS-GMSC with error code
24 “absent subscriber” so that the home system assumes that the delivery failed in case the
25 subscriber goes back to the home system without having retrieved the mail messages. This
26 way, at the reception of the Update Location message, the HLR shall send an Alert-SC
27 message so that the MWN information (in a short message) is once again sent to the Mobile
28 Station.
29
30 j. The SMS-GMSC sends the result of the Forward Mobile Terminating Short Message to the
31 Service Center. Note that depending on the Service Center implementation, this may cause the
32 SMS to be re-sent periodically instead of waiting for the ALERTSC message indicating that the
33 subscriber is again available to receive short messages.
34
35 k. The SMS-GMSC reports the error to the HLR, which shall set the proper flags as per GSM
36 03.40 [35] so that an Alert-SC message is sent when necessary as explained in step i above.
2-133
X.S0023
1 4.12.2.2 GSM SMS mapped to ANSI-41 SMS using GHOST or WEMT Teleservice
2 This method uses the tunneling concept. Instead of translating the GSM SMS with Message Waiting
3 Notification information to an ANSI-41 Qualification Directive with MWN information, the IIF shall
4 package the GSM SMS into an ANSI-41SMS with the new teleservice GHOST (GSM Hosted SMS
5 Teleservice)/WEMT.
6 Event g only works with Mobile Stations (MS) capable of handling GHOST or WEMT. The MS shall
7 remove the ANSI-41part of the message (the envelope) and send the GSM SMS Packet Data Units
8 (PDU) to the GSM part of the mobile station to handle the GSM SMS, in this case, containing the
9 Message Waiting Notification information. Specifically, the ANSI-41 MSC shall convert the SMDPP
10 to an R-DATA message which has a HLPI (higher layer protocol identifier) that indicates
11 GHOST/WEMT. The payload of the R-DATA message is the GSM SMS which is effectively
12 identified as the target application whenever HLPI = GHOST/WEMT.
GSM GSM GSM ANSI-41

SC SMS- HLR IIF MSC
GMSC
Vmail
Delivery
a
FORW.
TERM SM
MOBILE b
(MWN) SEND
INFO FOR SM
ROUTING c
(MWN)
Send
Info for SM
Routing d
FORW. SHORT
MESSAGE e
(MWN)
SMDPP (MWN)
f
(SMS delivered
Mobile Station)
g
to
smdpp
(GHOST) h
Forw. Short Message
i
Forw. Mobile
Term SM
j
13
14
15 Figure 100: GSM SMS mapped to ANSI-41 using GHOST/WEMT Teleservice

17
20
21 c. The GSM SMS-GMSC inquires about the subscriber location by sending the Send Routing
23
2-134
X.S0023
1
3 Message to IIF then acting as a serving GSM MSC/VLR.
4
5 This requires GSM MAP phase 2 or higher. If the GSM SMS-GMSC only supports GSM MAP
6 phase 1 and delivers MWN via pure text SMS, then a pure text SMS shall be delivered to the
7 IIF. The IIF shall then translate it into a CMT or GHOST/WEMT ANSI-41 SMS. Note that this
8 then becomes a simple SMS mapping covered in Section 4.11.
9
11 Short Message Delivery Point to Point with Teleservice GHOST/WEMT to the serving ANSI-41
12 MSC/VLR. The IIF is then acting as an ANSI-41Message Center (MC). Inside of this
13 GHOST/WEMT short message is the GSM short message containing the MWN information.
14
15 g. In this step, the GHOST/WEMT Short Message containing the GSM short message containing
16 the MWN information shall be delivered to the mobile station.
17
18 h. The serving ANSI-41 MSC/VLR sends the Short Message Delivery Point to Point Return Result
19 to the IIF.
20
21 i. The IIF sends the result of the Forward Short Message to the GSM SMS-GMSC.
22
24 Service Center.
2-135
X.S0023
1 4.12.2.3 Clearing of MWN Information after Retrieval of Messages while in ANSI-41

2 Foreign Mode – QualDir Method
3 This section describes the case where the messages are retrieved while a GSM subscriber is still
4 roaming in ANSI-41 foreign mode.
5
GSM GSM GSM ANSI-41

SC SMS- HLR IIF MSC
GMSC
Vmail
Retrieval
a
FORW. MOBILE
TERM SM (mwn)
b
SEND ROUTING
INFO FOR SM (mwn)
c
Send Routing
Info for SM
d
FORW. SHORT
MESSAGE (mwn)
QUALDIR(MWNCOUNT, e
MWNTYPE)
f
(mwn delivered to
Mobile Station) g
Qualdir
h
Forw. Mobile
i
Term SM (error)
Report SM (error)
j
DeliveryStatus
k
6
7
8 Figure 101: Clearing of MWN Information after Retrieval of Messages while in ANSI-41
9 Foreign mode – Qualdir Method
10 a. The voice mail messages are retrieved from the GSM subscriber.
11
13 Notification (MWN) information set to “clear” to the GSM SMS-GMSC.
14
17
19 the native GSM subscriber has already made a registration in the ANSI-41 MSC/VLR. Another
20 requirement is that the Service Center sets the priority of this SMS to “high” to make sure that
21 the SMS is sent (Section 3.2.5 of GSM 03.40). This is necessary since the IIF had previously
22 responded with absent subscriber and the HLR had set some flags that could have prevented
23 the delivery of this new SMS.
24
25 e. The GSM SMS-GMSC originates an SMS with MWN information (set to “clear”) by sending
26 Forward Short Message to IIF then acting as a serving GSM MSC/VLR. This requires a GSM
27 phase 2 support or higher.
2-136
X.S0023
1
2 f. Upon reception of the Forward Short Message with MWN information (set to “clear”), the IIF
3 shall initiate a Qualification Directive message with MWN information (set to “clear”) to the
4 serving ANSI-41 MSC/VLR. The IIF is then acting as an ANSI-41 HLR. The MWN information
5 consists of two parameters: MessageWaitingNotificationCount (MWNCOUNT) and
6 MessageWaitingNotificationType (MWNTYPE). For a description of these parameters, see to
7 the ANSI-41-D specifications, sections 6.5.2.78 and 6.5.2.79 [2].
8
9 g. In this step, the MWN information (set to “clear”) shall be delivered to the mobile station.
10
12 that this result message does not guaranty that the MWN information (set to ”clear”) was
13 delivered successfully to the Mobile Station, it just means that the MSC/VLR received the
14 Qualification Directive message, so the MWN flag shall not be cleared at this point by the IIF.
15
18 subscriber goes back to the home system without having received the clearing notification from
19 the serving MSC. This way, at the reception of the Update Location message, the HLR shall
20 send an Alert-SC message so that the MWN information (in a short message) is once again
21 sent to the Mobile Station.
22
27
28 k. The SMS-GMSC reports the error to the HLR, which shall set the proper flags as per GSM
29 03.40 [35] so that an Alert-SC message is sent when necessary as explained in step i above.
2-137
X.S0023
1 4.12.2.4 Handling at SMS delivery failure at the IIF
GSM GSM GSM ANSI-41

SC SMS- HLR IIF MSC
GMSC
Vmail
Retrieval
a
FORW. MOBILE
TERM SM (mwn)
SEND ROUTING
b
INFO FOR SM (mwn)
Send Routing
c
Info for SM
FORW. SHORT
d
MESSAGE (mwn)
e
SMDPP (GHOST,WEMT)
f
smdpp error g
Forw. Short Message (error)
Forw. Mobile Term.
h
SM (error)
i
Report SM (error)
Delivery Status j
k
2
3
4 Figure 102: Handling at SMS delivery failure at the IIF

6
9
12
15
17 Message to IIF then acting as a serving GSM MSC/VLR.
18
19 f. Upon reception of the Forward Short Message with MWN information, the IIF encounters an
20 error and sends the result of the Forward Short Message to the GSM SMS-GMSC with the
21 proper error code as per GSM Specifications 09.02 [4].
22
23 g. The SMS-GMSC sends the result of the Forward Mobile Terminating Short Message to the
24 Service Center.
2-138
X.S0023
1
2 h. The SMS-GMSC reports the error to the HLR, which sets the proper flags as per GSM 03.40 [4]
3 so that an Alert-SC message is sent when necessary.
2-139
X.S0023
1 4.12.2.5 Handling at SMS delivery failure at the MSC/VLR – QualDir Method
GSM GSM GSM ANSI-41

SC SMS- HLR IIF MSC
GMSC
Vmail
Delivery
a
FORW. MOBILE
TERM SM (MWN)
b
SEND ROUTING
INFO FOR SM (MWN)
Send Routing
c
Info for SM
d
FORW. SHORT
MESSAGE (MWN)
QUALDIR(MWNCOUNT,
e
MWNTYPE)
f
Qualdir Return Error
g
Forw. Mobile
h
Term SM (error)
Report SM (error)
i
DeliveryStatus
j
3
4
5 Figure 103: Handling at SMS delivery failure at the MSC/VLR Qualdir Method
7
10
12 Information for Short Message to the HLR.
13
14 d. The HLR replies with the Send Routing Information for Short Message result. It is assumed that
16
18 Message to IIF then acting as a serving GSM MSC/VLR. This requires GSM phase 2 support or
19 higher.
22
23 f. The IIF shall also initiate a Qualification Directive message with MWN information to the serving
24 ANSI-41 MSC/VLR. The IIF is then acting as an ANSI-41 HLR. The MWN information consists
25 of two parameters: MessageWaitingNotificationCount (MWNCOUNT) and
26 MessageWaitingNotificationType (MWNTYPE). For a description of these parameters, see to
27 the ANSI-41-D specifications, sections 6.5.2.78 and 6.5.2.79 [2].
28
2-140
X.S0023
1 g. The serving ANSI-41 MSC/VLR encounters an error and sends the Qualification Directive
2 Return Error to the IIF, as per the ANSI-41 Specifications, Chapter 6, Section 4.32.2, Table 42.
3 h. The IIF sends the error result of the Forward Short Message to the GSM SMS-GMSC.
4
5 i. The SMS-GMSC sends the result of the Forward Mobile Terminating Short Message to the
6 Service Center.
7
8 j. The SMS-GMSC reports the error to the HLR which sets the proper flags as per GSM 03.40
9 [35] so that an Alert-SC message is sent when necessary.
10
2-141
X.S0023
1 4.12.2.6 Handling at SMS delivery failure at the MSC/VLR – GHOST/WEMT SMS

2 Method
GSM GSM GSM ANSI-41

SC SMS- HLR IIF MSC
GMSC
Vmail
Retrieval
a
FORW. MOBILE
TERM SM (mwn)
SEND ROUTING
b
INFO FOR SM (mwn)
Send Routing
c
Info for SM
FORW. SHORT
d
MESSAGE (mwn)
e
SMDPP (GHOST,WEMT)
f
smdpp error g
Forw. Mobile Term.
h
SM (error)
i
Report SM (error)
Delivery Status j
k
3
4
5 Figure 104: Handling at SMS delivery failure at the MSC/VLR – GHOST/WEMT SMS Method
7
10
12 Information for Short Message to the HLR.
13
14 d. The HLR replies with the Send Routing Information for Short Message result. It is assumed that
16
19 higher.
20
22 Short Message Delivery Point to Point with Teleservice GHOST/WEMT to the serving ANSI-41
23 MSC/VLR. The IIF is then acting as an ANSI-41Message Center (MC). Inside of this
24 GHOST/WEMT short message is the GSM short message containing the MWN information.
2-142
X.S0023
1
2 g. The serving ANSI-41 MSC/VLR encounters an error and sends the Short Message Delivery
3 Point to Point Return error to the IIF.
4
5 h. The IIF sends the result of the Forward Short Message to the GSM SMS-GMSC with the proper
6 error code. .
7
8 i. The SMS-GMSC sends the result of the Forward Mobile Terminating Short Message to the
9 Service Center.
10
11 j. The SMS-GMSC shall report the error to the HLR.
2-143
X.S0023
1 4.12.2.7 GSM SMS mapped to ANSI-41 Qualification Directive and to Registration

2 Notification Return Result
GSM GSM GSM ANSI-41 IIF ANSI-41

SC SMS- HLR MSC 2 MSC 1
GMSC
Vmail
Delivery
a
FORW. MOBILE
TERM SM (MWN)
b
SEND ROUTING
INFO FOR SM (MWN)
Send Routing
c
Info for SM
d
FORW. SHORT
QUALDIR
MESSAGE (MWN)
(MWNCOUNT, e
MWNTYPE)
f
(MWN delivered to
Mobile Station) g
h
Forw. Mobile
i
Term SM (error)
j
Report SM (error)
DeliveryStatus
k
Time elapsed
l
REGNOT
m
j
Regnot(MWNCOUNT,
MWNTYPE)
n
(MWN delivered to
Mobile Station) o
4
5
6 Figure 105: GSM SMS mapped to ANSI-41 Qualification Directive and to Registration
7 Notification Return Result
9
11 Notification (MWN) information to the GSM SMS-GMSC
12
15
18
2-144
X.S0023
3 higher.
5 is to be delivered to the Mobile Station. If the handset only supports GSM phase 1, then a pure
6 text SMS shall be delivered to the IIF. The IIF shall then translate it into a CMT or
7 GHOST/WEMT ANSI-41 SMS. Note that this then becomes a simple SMS mapping covered in
8 Section 4.11.
9
11 Qualification Directive message with MWN information to the serving ANSI-41 MSC/VLR. The
12 IIF is then acting as an ANSI-41 HLR. The MWN information consists of two parameters:
14 (MWNTYPE). For a description of these parameters, see to the ANSI-41 specifications, sections
15 6.5.2.78 and 6.5.2.79 [2]. Alternatively, a GHOST/WEMT short message could be sent instead
16 of the Qualification Directive message (see Section 4.12.2.2) if the IIF has the possibility to
17 confirm that the Mobile Station is SMS-capable.
18
19 g. In this step, the MWN information shall be delivered to the mobile station.
20
22 that this result message does not guaranty that the MWN information was delivered
23 successfully to the Mobile Station, it just means that the MSC/VLR received the Qualification
24 Directive message, therefore the MWN flag shall not be cleared at this point by the IIF.
25
28 subscriber goes back to the home system without having retrieved the mail messages. This
29 way, at the reception of the Update Location message, the HLR shall send an Alert-SC
30 message so that the MWN information (in a short message) is once again sent to the Mobile
31 Station.
32
37
38 k. The SMS-GMSC reports the error to the HLR, which sets the proper flags as per GSM 03.40
39 [35] so that an Alert-SC message is sent when necessary as explained in step i above.
40
41 l. Time elapses before the MS re-registers.
42
43 m. A Registration Notification is sent from the serving ANSI-41 MSC 2 to the IIF.
44
45 n. The IIF discovers that the MWN flag is still set. The IIF sends back the MWN in the Registration
46 Notification Return Result along with the other registration information (e.g. other Profile
47 parameters) to the serving ANSI-41 MSC/VLR. The IIF is then acting as an ANSI-41 HLR. The
48 MWN information consists of two parameters: MessageWaitingNotificationCount (MWNCOUNT)
49 and MessageWaitingNotificationType (MWNTYPE). For a description of these parameters, see
50 to the ANSI-41 specifications, sections 6.5.2.78 and 6.5.2.79 [2].
51
52 o. In this step, the MWN information shall be delivered to the mobile station. Since there is no
53 acknowledgement from the regnot Return Result, there is no guarantee that the MWN
2-145
X.S0023
1 information was delivered successfully to the Mobile Station. The MWN flag shall not be cleared
2 at this point by the IIF.
2-146
X.S0023
1 4.13 GPRS in GSM Foreign Mode

2 This section describes the support of GPRS service for ANSI-41subscribers roaming in a GSM
3 radio environment.
4 To support multiple network configuration requirements this standard defines several optional
5 capabilities that may be implemented. The scenarios in this section are not exhaustive.
6 The services offered are dependent on both the MS capabilities and the users GPRS subscription
7 data. The services to be provided are provisioned in the IIF by means outside the scope of this
8 standard. Provisioning in the IIF is required to support both voice and GPRS.
9 When an MS is capable of both GSM-CS and GPRS service, it may be attached to the GSM
10 network through either a GSM MSC (for GSM-CS service) or an SGSN (for GPRS service) or
11 through both. The attachments may be done in series, i.e. first one service and then another, or
12 simultaneously.
13 The IIF may implement a timer, GPRS_LU, to reduce the number of location updates in the
14 ANSI-41 network when an MS is capable of both MSC-CS and GPRS services. If the timer is
15 supported, then when a Location Update is received from the SGSN for an MS that is capable of
16 both GSM_CS and GPRS service, the IIF starts the timer and then performs the ‘Insert Subscriber
17 Data’ procedure to the SGSN. The IIF sends the REGNOT to the HLR only after the expiry of the
18 timer or the receipt of the Location Update from the GSM MSC.
19 When the timer is not started, either because :
20 - it is not supported; or
21 - the MS is provisioned for GPRS only service; or
22 - the MS is already CS attached; or
23 - the IIF does not support multiple MSCIDs;
24 then the IIF sends the REGNOT to the HLR and waits for a response before performing the ‘Insert
25 Subscriber Data’ procedure to the SGSN.
26 The IIF may support multiple MSCIDs to separately identify each GSM MSC and each SGSN when
27 an MS is attached for either or both services. When multiple MSCIDs are supported the IIF shall
28 notify the ANSI-41 HLR whenever the MS registers on a different SGSN, GSM MSC or both.
29 An IIF that does not support multiple MSCIDs shall always convey its own identity towards the
30 ANSI-41 HLR.
31 Subscriber Data Management procedures shall follow similar procedures as described in 4.4.2. In
32 the case of subscriber deletion, it shall also result in the deletion of any GPRS subscription data in
33 the IIF, for that subscriber. In this case, the IIF shall also send a Cancel Location Request to the
34 serving SGSN. The ANSI-41 HLR does not have the capability to request the modification of GPRS
35 subscription data in the IIF. Modification of GPRS subscriber data in the IIF shall be in accordance
36 with GSM 09.02 [4] via an OMC directly connected to the IIF.
2-147
X.S0023
1 4.13.1 Location Registration ScenariosIn each of the following scenarios, the following
2 interactions are not shown:
3  Interactions between SGSNs
4  Interactions between SGSNs and GGSNs
5 Existing procedures defined in GSM 03.60 [33], describing the actions between SGSNs or between
6 an SGSN and a GGSN for scenarios involving interaction between those functional elements also
7 apply.
8 Existing procedures and timers defined in GSM 03.60 [33], describing the actions between the
9 SGSN and the GSM HLR also apply between the SGSN and the IIF (emulating a GSM HLR).
10 The combined attach and location registration procedures described, require support of the optional
11 Gs interface as described in GSM 03.60[33].
12 It should be noted that certain scenarios may only be relevant to certain MS types. For a full
13 description of the various MS types see GSM 03.60 [33].
14 4.13.1.1 GPRS Attach (not currently registered)
15 If an MS requests GPRS service when currently not registered in the IIF, the MS performs a GPRS
16 attach request using its IMSI. The IIF acts like a GPRS HLR/AuC in this case. The subscriber's
17 ANSI-41 HLR has no knowledge of this request, but the IIF makes it aware of the attachment to an
18 SGSN via a REGNOT. If timer GPRS_LU is used then the message flow is as shown in Figure
19 106. If timer GPRS_LU is not used then the message flow is as shown in Figure 107.1
2-148
X.S0023
MS SGSN IIF HLR

GPRS Attach
Req. (IMSI)
a
Authentication Info
b
c
Authentication Req
d
AuthenticationRes e
Update GPRS Location Req (IMSI, SGSN Address)
f
Insert Sub Data

g
Insert Sub Data Ack

h
GPRS_LU
Update GPRS Location Ack
i
REGNOT
j
regnot
k
GPRS Attach Ack
l
1
2 Figure 106: GPRS Attach (Option1: with timer)
3 a. MS performs a GPRS Attach.
4 b. If the Serving GPRS Support Node (SGSN) does not have authentication information in order to
5 perform authentication i.e. authentication triplets, it requests authentication information from the
6 IIF. The IIF emulates a GSM HLR/AuC in this case supporting GPRS.
7 c. The IIF returns the necessary authentication information, if applicable.
8 d. SGSN initiates authentication towards the MS.
10 f. SGSN initiates a MAP GPRS location update towards the IIF. The Update GPRS Location
11 Request contains the IMSI.
12 g. The IIF validates whether the GPRS service request is authorized. Since GPRS service is
13 requested, and the subscriber is currently PS-deregistered, it initiates the GSM MAP Insert
14 Subscriber Data Procedure towards the SGSN after the subscriber has been successfully
15 authorized. This procedure is used to download GPRS subscriber data to the SGSN. Multiple
16 Insert Subscriber Data transactions may be necessary to complete the transfer of subscriber
17 data to the SGSN.
18 h. The SGSN acknowledges the ISD Operation(s).
2-149
X.S0023
1 i. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the IIF
2 returns an acknowledgement to the Update GPRS Location Request.
3 j. After the IIF’s GPRS_LU timer expires, the IIF shall send a registration notification (REGNOT)
4 to the ANSI-41 HLR. The REGNOT shall contain the MSID (MIN/IMSI), the ESN , the MSCID ,
5 etc. If SIM-based roaming is authorized, an initially provisioned, fixed ESN for this subscriber
6 shall be passed in the REGNOT to the subscriber’s HLR. The ANSI-41 HLR records the
7 address of the IIF as the serving ANSI-41 MSC. Although call delivery may not be possible,
8 SMS delivery is made possible by registering the IIF as the ANSI-41 MSC with the ANSI-41
9 HLR.
10 k. The ANSI-41 HLR sends an acknowledgment to the registration with a regnot. The IIF may
11 ignore the CS-related profile information, since the subscriber is only GPRS-attached (and not
12 GSM CS-attached). Only the provisioned SMS parameters in the regnot (profile) may be
13 mapped and sent to the SGSN in an Insert Subscriber Data message (e.g., as in the next
14 figure). (Alternatively, SMS parameters related to GPRS could be provisioned directly on the IIF
15 and sent to the SGSN in step g.)
16 If a negative regnot response is received from the ANSI-41 HLR, (then as a Network option) the
17 IIF may perform an initiated detach procedure as described in section 4.13.2.6.
18 l. The SGSN acknowledges the GPRS Attach Request.
MS SGSN IIF HLR
GPRS Attach Req

a
(IMSI)
Authentication Info
b
c
Authentication Req
d
Update GPRS Location Req
f
(IMSI, SGSN Address)
REGNOT g
Regnot ack
h
Insert Sub Data
i
Insert Sub Data Ack
j
Update GPRS Location Ack k
GPRS Attach Accept l

19
20 Figure 107: GPRS Attach (Option 2: without timer)
21
2-150
X.S0023
10 g. The REGNOT shall contain the MSID (MIN/IMSI), the ESN, the MSCID etc. If SIM-based
11 roaming is authorized, an initially provisioned, fixed ESN for this subscriber shall be passed in
12 the REGNOT to the subscriber’s HLR. The ANSI-41 HLR records the address of the IIF as the
13 serving ANSI-41 MSC. Although call delivery may not be possible, SMS delivery is made
14 possible by registering the IIF as the ANSI-41 MSC with the ANSI-41 HLR.
15 h. The ANSI-41 HLR sends an acknowledgment to the registration with a regnot. The IIF may
16 ignore the CS-related profile information, since the MS is only GPRS-attached (and not GSM
17 CS-attached). Only the provisioned SMS parameters in the regnot (profile) may be mapped
18 and sent to the SGSN in an Insert Subscriber Data message.
19 i. The IIF validates whether the GPRS service request is authorized. Since GPRS service is
20 requested, and the subscriber is currently PS-deregistered, it initiates the GSM MAP Insert
24 data to the SGSN.
25 j. The SGSN acknowledges the ISD Operation(s).
26 k. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the IIF
28 l. The SGSN acknowledges the GPRS Attach request.
2-151
X.S0023
1 GPRS Attach when currently registered in an ANSI-41 network
2 If an MS requests GPRS service when currently registered in an ANSI-41 network, the SGSN sends
3 an Update GPRS location update using its IMSI. The IIF acts like a GPRS HLR/AuC and an
4 ANSI-41 VLR in this case. To the subscriber's ANSI-41 HLR, the subscriber becomes registered on
5 the IIF acting as an ANSI-41 MSC. If timer GPRS_LU is used then the message flow is as shown in
6 Figure 108. If timer GPRS_LU is not used then the message flow is as shown in Figure 109.
MS SGSN PMSC/
MSC IIF HLR VLR
GPRS Attach Req
a
(IMSI)
c
Authentication Req
d
Update GPRS Location Req (IMSI)
f
Insert Sub Data
g
Insert Sub Data Ack GPRS_LU
h
Update gprs location ack
i
REGNOT
j
REGCANC
k
regcanc
l
Regnot ack
m
GPRS Attach Accept
n
o
7
8 Figure 108: GPRS Attach when currently registered in ANSI-41 (Option 1: with timer)
9
2-152
X.S0023
2 requested, and the MS is currently PS-deregistered, it initiates the GSM MAP Insert
6 data to the SGSN.
8 i. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the
9 IIF returns an acknowledgement to the Update GPRS Location Request.
10 j. After the IIF’s GPRS_LU timer expires, the IIF shall send a registration notification (REGNOT)
11 to the ANSI-41 HLR. The REGNOT shall contain the MSID (MIN/IMSI), the ESN, the MSCID,
16 HLR.
17 k. The ANSI-41 HLR updates its location information and deletes the previous VLR record by
18 sending a REGCANC to the previous MSC/VLR.
19 l. The VLR acknowledges the REGCANC.
20 m. The ANSI-41 HLR sends an acknowledgment to the registration with a regnot. The IIF may
22 CS-attached).
23 If a negative regnot response is received from the ANSI-41 HLR, (then as a Network option)
24 the IIF may perform an initiated detach procedure as described in section 4.13.2.6.
25 n. The SGSN acknowledges the GPRS Attach request.
2-153
X.S0023
MS SGSN IIF HLR MSC

/VLR
GPRS Req (IMSI)
ffRRReAttach a
Authentication Info
b
AuthenticatioInfoAck
c
n
Authentication Req
d
Authentication Res
e
Update GPRS Location Req (IMSI, SGSN Address)
f
REGNOT (MSID, ESN MSCID or MSCIN)
g
REGCAN h
regcan
GPRS_LU i
regnot
j
Insert Sub
Data k
Insert Sub Ack
Data l
Update GPRS Ack
Location m
GPRS Ack
n
1
2
3 Figure 109: GPRS Attach when currently registered in ANSI-41 (Option 2: without timer)
4
14 g. The REGNOT shall contain the MSID (MIN/IMSI), the ESN, the MSCID, etc. If SIM-based
15 roaming is authorized, an initially provisioned, fixed ESN for this subscriber shall be passed in
2-154
X.S0023
1 the REGNOT to the subscriber’s HLR. The ANSI-41 HLR records the address of the IIF as the
2 serving ANSI-41 MSC. Although call delivery may not be possible, SMS delivery is made
3 possible by registering the IIF as the ANSI-41 MSC with the ANSI-41 HLR.
4 h. The ANSI-41 HLR updates its location information and deletes the previous VLR record by
5 sending a REGCANC to the previous MSC/VLR.
6 i. The VLR acknowledges the REGCANC.
7 j. The ANSI-41 HLR sends an acknowledgment to the registration with a regnot.
8 k. The IIF validates whether the GPRS service request is authorized. Since GPRS service is
9 requested, and the MS is currently PS-deregistered, it initiates the GSM MAP Insert Subscriber
10 Data Procedure towards the SGSN after the subscriber has been successfully authorized. This
11 procedure is used to download GPRS subscriber data to the SGSN. Multiple Insert Subscriber
12 Data transactions may be necessary to complete the transfer of subscriber data to the SGSN.
13 l. The SGSN acknowledges the ISD Operation(s).
14 m. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the IIF
16 n. The SGSN acknowledges the GPRS Attach request.

17
2-155
X.S0023
1 4.13.1.3 Inter-SGSN routing area update
2 If an MS requests a GPRS routing area update while registered on a GPRS SGSN only. The
3 message flow is as shown in Figure 110 and 111, depending on whether the timer GPRS_LU is
4 supported on the IIF.
MS SGSN
IIF HLR Prev
SGSN
inter-SGSN Routing Area Update (IMSI)
a
c
Authentication Req
d
f
Cancel Location
g
Cancel Location Ack
h
GPRS_LU
Insert Sub Data i
Insert Sub Data Ack
j
k
REGNOT
l
REGCANC
m
regcanc
n
Regnot ack
o
inter-SGSN Routing Area Update Accept
p
GPRS NETWORK ANSI-41 GPRS NETWORK
5 Figure 110: Inter-SGSN routing area update (Option 1: with timer)
6 a. MS sends a Routing Area Update request.
14 Request contains the IMSI. The IIF starts the GPRS_LU timer.
2-156
X.S0023
1 g. The IIF (acting like a GPRS HLR) shall also send a Cancel Location to the previous SGSN.
2 h. The IIF shall receive a Cancel Location acknowledgement from the previous SGSN.
4 requested, it initiates the GSM MAP Insert Subscriber Data Procedure towards the SGSN after
5 the subscriber has been successfully authorized. This procedure is used to download GPRS
6 subscriber data to the SGSN. Multiple Insert Subscriber Data transactions may be necessary to
7 complete the transfer of subscriber data to the SGSN.
11 Note: Steps l,m,n & o are optional depending on whether the IIF supports multiple MSCIDs.
12 l. After the IIF’s GPRS_LU timer expires, the IIF shall send a registration notification (REGNOT)
13 to the ANSI-41 HLR. The REGNOT shall contain the MSID (MIN/IMSI), the ESN, the MSCID,
18 HLR.
19 m. The HLR updates its location information and deletes the previous VLR record by sending a
20 REGCANC to the previous MSC/VLR, which in this case is the IIF (if in step l, the IIF sent a
21 REGNOT with a different MSCID (IIF address corresponding to the current SGSN) than the
22 MSCID sent corresponding to the previous SGSN).
23 n. The IIF acknowledges the REGCANC.
24 o. The ANSI-41 HLR sends an acknowledgment to the registration with a regnot. The IIF may
26 CS-attached).
2-157
X.S0023
1 Related to Figure 110, if a negative regnot response is received from the ANSI-41 HLR, (then
2 as a Network option) the IIF may perform an initiated detach procedure as described in section
3 4.13.2.6.
4 p. The SGSN acknowledges the GPRS routing area update.
MS SGSN
IIF HLR Prev
SGSN
inter-SGSN Routing Area Update
a
(IMSI)
c
Authentication Req
d
f
Cancel Location
g
Cancel Location Ack
h
REGNOT i
REGCANC
j
regcanc
k
Regnot ack
l
Insert Sub Data
m
Insert Sub Data Ack
n
o
inter-SGSN Routing Area Update Accept
ANSI-41 p
GPRS NETWORK GPRS NETWORK
5 Figure 111: Inter-SGSN routing area update (Option 2: without timer)
6 a. MS sends a Routing Area Update request. .
7 b. If the Serving GPRS Support Node (SGSN) does not have authentication information in
8 order to perform authentication i.e. authentication triplets, it requests authentication
9 information from the IIF. The IIF emulates a GSM HLR/AuC in this case supporting GPRS.
15 g. The IIF sends a Cancel Location to the previous SGSN.
2-158
X.S0023
1 h. IIF shall receive an acknowledgement for the Cancel Location.
2 i. If the IIF implementation supports multiple MSCIDs, then it shall send a REGNOT to the
3 ANSI-41 HLR with the MSCID corresponding to the new SGSN. Then the IIF shall correlate
4 that MSCID with the GSM MSCID when receiving mobile terminated SMS messages (so
5 that the IIF can deliver them to the SGSN).
6 j. This is a continuation of the optional procedure started in item i. IIF receives REGCANC.
7 The IIF needs to keep both the current MSCID associated to the SGSN as well as the
8 current MSCID associated to the MSC. The IIF must also keep a record of the last MSCID
9 which was sent to the ANSI-41 HLR to know that is the one stored in the ANSI-41 HLR.
10 k. This is a continuation of the optional procedure started in item i. IIF sends regcanc
11 response.
12 l. This is a continuation of the optional procedure started in item i. IIF receives regnot
13 response.
14 m. The IIF validates whether the GPRS service request is authorized. Since GPRS service is
15 requested, it initiates the GSM MAP Insert Subscriber Data Procedure towards the SGSN
16 after the subscriber has been successfully authorized. This procedure is used to download
17 GPRS subscriber data to the SGSN. Multiple Insert Subscriber Data transactions may be
18 necessary to complete the transfer of subscriber data to the SGSN.
19 n. The SGSN acknowledges the ISD Operation(s).
20 o. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the
22 p. The SGSN acknowledges the Routing Area Update request.

23
2-159
X.S0023
1 4.13.1.4 GPRS- Attach when only GSM CS Attached
2 If an MS roams while registered in a GSM serving MSC, and the MS requests GPRS attach, the MS
3 performs a GPRS attach and the network responds as shown in Figure 112. Note that the GSM
4 MSC does not update the IIF (emulating the GSM HLR). The serving MSC remains constant.
MS SGSN PMSC/
MSC IIF HLR VLR
GPRS Attach Req
a
(IMSI)
c
Authentication Req
d
f
REGNOT
g
REGCANC
h
regcanc
i
Regnot ack
j
Insert Sub Data
k
Insert Sub Data Ack
l
m
BSSAP+-Location Update Req
n
BSSAP+-Location Update Accept
o
GPRS Attach Accept p
GSM NETWORK ANSI-41 GSM NETWORK
5
6 Figure 112: GPRS Attach when GSM CS Attached.
16 g. If the IIF implementation supports multiple MSCIDs, then it shall send a REGNOT to the
17 ANSI-41 HLR with the MSCID corresponding to the new SGSN.
2-160
X.S0023
1 h. This is a continuation of the optional procedure started in item g. IIF receives REGCANC.
2 i. This is a continuation of the optional procedure started in item g. IIF sends regcanc response.
3 j. This is a continuation of the optional procedure started in item g. IIF receives regnot response.]
10 m. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the IIF
12 n. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
13 The GSM MSC creates the association with the SGSN by storing the SGSN Number. The MSC
14 does not see a need to notify the IIF (emulating the GSM HLR, since there is no change to the
15 CS location update parameters).
16 o. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface by

17 sending the Accept message.
18 p. The SGSN acknowledges the GPRS Attach request from the MS.
19
2-161
X.S0023
1 4.13.1.5 Combined GSM and GPRS attach when not currently registered
2 If an MS requests a combined GSM and GPRS attach when not registered in the IIF, then the
3 SGSN first requests a GPRS location update to the IIF (acting as a GPRS HLR) and then a CS
4 location update through the GSM MSC as depicted in Figure 114.
MS SGSN
IIF HLR
MSC
Combined Attach Req (IMSI)

a
Authentication Req c
d
f
Insert Sub Data
g
Insert Sub Data Ack GPRS_LU
h
i
j
Update Location Req
k
REGNOT
l
Regnot ack
m
n
ISD ack
o
Update Location ack
p
BSSAP+-Location Update Accept q
Combined Attach Accept
r
5
6 Figure 113: Combined GPRS and GSM attach (Option 1: With timer).
7 a. MS performs a GPRS attach.
15 Request contains the IMSI. The IIF starts timer GPRS LU.
2-162
X.S0023
4 j. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
5 The GSM MSC creates the association with the SGSN by storing the SGSN Number.
6 k. The MSC determines that it needs to notify the IIF (emulating the GSM HLR), since there is a
7 change to the CS location update parameters. The MSC sends the Update Location operation
8 to the IIF (emulating the GSM HLR). The IIF stops timer GPRS LU.
9 l. The IIF shall send a Registration Notification (REGNOT) to the ANSI-41 HLR to indicate the
10 changed location (MSCID associated with the new GSM MSC).
13 validated dynamic ESN for this subscriber, but the HLR shall also accept this fixed ESN for this
14 subscriber.
15 m. The ANSI-41 HLR acknowledges the registration and sends back the subscriber’s information.
16 This information is for non-GPRS services.
17 n. The IIF sends MAP INSERT SUBSCRIBER DATA message(s) to the GSM MSC providing GSM
18 CS information based on the contents of the regnot (profile).
19 o. The GSM MSC acknowledges receipt of the Insert Subscriber Data information.
20 p. The IIF acknowledges the completion of the Update Location procedure and sends the Update
21 Location Acknowledgement to the GSM MSC.
22 q. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface to the
23 SGSN by sending the Accept message.
24 r. The SGSN acknowledges the combined GPRS and GSM Attach request from the MS.
25
26
2-163
X.S0023
SGSN IIF HLR

MS MSC

a
Authentication Req c
d
f
REGNOT
g
Regnot ack
h
Insert Sub Data
i
Insert Sub Data Ack
j
Update gprs location ack k

l
Update Location Req m
Insert Subscriber Data n
ISD ack
o
Update Location ack
p
BSSAP+-Location Update Accept q
Combined Attach Accept
r
1
2 Figure 114: Combined GPRS and GSM attach (Option 2: Without timer and without support
3 for multiple MSCIDs).
13 g. The IIF shall send a Registration Notification (REGNOT) to the ANSI-41 HLR to indicate the
14 changed location.
18 subscriber.
19 h. The ANSI-41 HLR acknowledges the registration and sends back the subscriber’s information in
20 the regnot response.
2-164
X.S0023
9 l. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
11 m. The MSC determines that it needs to notify the IIF (emulating the GSM HLR), since there is a
13 to the IIF (emulating the GSM HLR). The IIF does not send a REGNOT in this case, because it
14 does not support multiple MSCIDs.
15 n. The IIF sends MAP INSERT SUBSCRIBER DATA message(s) to the GSM MSC providing GSM
17 o. The GSM MSC acknowledges receipt of the Insert Subscriber Data information.
18 p. The IIF acknowledges the completion of the Update Location procedure and sends the Update
20 q. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface to the
22 r. The SGSN acknowledges the combined GPRS and GSM Attach request from the MS.
2-165
X.S0023
MS SGSN MSC IIF HLR

a
Authentication Info
b
c
Authentication Req
d
Authentication Res
e
f
REGNOT
g
Regnot ack
h
Insert Sub Data
i
Insert Sub Data Ack
j
k
l
Update Location Req
m
REGNOT
n
REGCANC
o
regcanc
p
regnot
q
Insert Sub Data
r
Insert Sub Data Ack
s
Update Location ack
t
u
GPRS Attach Accept/Routing Area Update Accept
v

1
2
3 Figure 115: Combined GPRS and GSM attach (Option 3: IIF supports multiple MSCIDs).
4
2-166
X.S0023
6 changed location (MSCID associated to the new GSM SGSN).
10 subscriber.
11 h. The ANSI-41 HLR acknowledges the registration and sends back the subscriber’s information in
12 a regnot response.
21 l. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
23 m. The MSC determines that it needs to notify the IIF (emulating the GSM HLR), since there is a
25 to the IIF (emulating the GSM HLR).
26 n. The IIF shall send a Registration Notification (REGNOT) to the ANSI-41 HLR to indicate the
27 changed location (MSCID associated to the new GSM MSC).
31 subscriber.
32 o. IIF receives a REGCANC. The IIF needs to keep both the current MSCID associated to the
33 SGSN as well as the current MSCID associated to the MSC. The IIF must also keep a record of
34 the last MSCID which was sent to the ANSI-41 HLR to know that is the one stored in the
35 ANSI-41 HLR.
36 p. IIF sends regcanc response.
37 q. The ANSI-41 HLR acknowledges the registration and sends back the subscriber’s information.
38 r. The IIF sends MAP INSERT SUBSCRIBER DATA message(s) to the GSM MSC providing GSM
40 s. The GSM MSC acknowledges receipt of the Insert Subscriber Data information.
2-167
X.S0023
1 t. The IIF acknowledges the completion of the Update Location procedure and sends the Update
3 u. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface to the
5 v. The SGSN acknowledges the combined GPRS and GSM Attach request from the MS.
2-168
X.S0023
1 4.13.1.6 Combined Inter-SGSN Routeing Area/Location Area Update
2 If an MS requests a combined routeing area update when previously registered on a different SGSN
3 and GSM MSC, then the SGSN first requests a GPRS location update to the IIF (acting as a GPRS
4 HLR) and then a CS location update.
Prev PMSC/
MS SGSN MSC IIF HLR
SGSN VLR
Inter-SGSN Routing Area Update (IMSI)

a
Authentication Info
b
c
Authentication Req
d
Authentication Res
e
f
Cancel Location
g
Cancel Location Ack
h
REGNOT
i
REGCANC
j
regcanc
k
regnot
l
Insert Sub Data
m
Insert Sub Data Ack
n
o
p
Update Location Req
q
Cancel Location
r
Cancel Location Ack
s
REGNOT
t
REGCANC
u
regcanc
v
regnot
w
Insert Sub Data
x
Insert Sub Data Ack
y
Update Location ack
z
aa
GPRS Attach Accept/Routing Area Update Accept ab
5 GSM NETWORK ANSI-41 NETWORK GSM NETWORK

6
7 Figure 116: Combined Inter-SGSN RA/LA update
2-169
X.S0023
1 a. MS sends a Routeing Area Update request
10 g. In the case of a combined attach when registered on a different MSC and SGSN, and in the
11 case of a combined inter-SGSN routing area update case when previously registered on a
12 different MSC and SGSN, the IIF (acting like a GPRS HLR) shall also send a Cancel Location to
13 the previous SGSN
16 ANSI-41 MSC with the MSCID corresponding to the new SGSN.
17 j. This is a continuation of the optional procedure started in item i. IIF receives REGCANC. The
18 IIF needs to keep both the current MSCID associated to the SGSN as well as the current
19 MSCID associated to the MSC. The IIF must also keep a record of the last MSCID which was
20 sent to the ANSI-41 HLR to know that is the one stored in the ANSI-41 HLR.
21 k. This is a continuation of the optional procedure started in item i. IIF sends regcanc response.
22 l. This is a continuation of the optional procedure started in item i. IIF receives regnot response.
29 o. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the IIF
31 p. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
33 q. The MSC determines that it needs to notify the IIF (emulating the GSM HLR), since there is a
34 change to the CS location update parameters, so the IIF sends the Update Location operation
35 to the IIF (emulating the GSM HLR).
36 r. The IIF sends a Cancel Location to the previous GSM MSC/VLR if a change in MSC has been
37 detected.
38 s. The IIF receives the Cancel Location acknowledgement.
39 t. If the IIF implementation supports multiple IIF MSCIDs, then it shall send a Registration
40 Notification (REGNOT) to the ANSI-41 HLR to indicate the changed location (MSCID
41 associated to the new GSM MSC).
2-170
X.S0023
4 subscriber.
5 u. This is a continuation of the optional procedure started in item t. The IIF receives a REGCANC
6 if the MSCID just sent in item (t) is a different one than stored in the ANSI-41 HLR. IIF receives
7 REGCANC. The IIF needs to keep both the current MSCID associated to the SGSN as well as
8 the current MSCID associated to the MSC. The IIF must also keep a record of the last MSCID
10 v. This is a continuation of the optional procedure started in item t. The IIF acknowledges the
11 regcanc.
12 w. This is a continuation of the optional procedure started in item t. The IIF receives the regnot
13 response with the subscriber’s information. This information is for non-GPRS services.
14 x. The IIF sends MAP INSERT SUBSCRIBER DATA message(s) to the GSM MSC providing GSM
16 y. The GSM MSC acknowledges receipt of the Insert Subscriber Data information.
17 z. The IIF acknowledges the completion of the Update Location procedure and sends the Update
19 aa. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface to the
21 bb. The SGSN acknowledges the GPRS Attach request from the MS.
22
2-171
X.S0023
1 4.13.1.7 Inter-SGSN routing area update when GSM CS and GPRS attached (GSM MSC
2 remains constant)
3 An MS request a GPRS routing area update while registered in a GSM serving MSC and GPRS
4 attached. In this case, the change of routing areas is within one Location area (and the MSC
5 remains constant) as shown in Figure 118. Note that the GSM MSC does not update the IIF
6 (emulating the GSM HLR).
Prev
MS SGSN MSC IIF HLR
SGSN
Inter-SGSN Routing Area Update (IMSI)

a
Authentication Info
b
c
Authentication Req
d
Authentication Res
e
f
Cancel Location
g
Cancel Location Ack
h
REGNOT
i
REGCANC
j
regcanc
k
regnot
l
Insert Sub Data
m
Insert Sub Data Ack
n
o
p
q
Routing Area Update Accept
r

7
8
9 Figure 117: Inter-SGSN routing area update when GSM CS and GPRS Attached
10 (MSC remains constant)
2-172
X.S0023
1
2 a. MS sends a Routing Area Update request.
11 g. The IIF (acting like a GPRS HLR) shall send a Cancel Location to the previous SGSN
14 ANSI-41 MSC with the MSCID corresponding to the new SGSN. The IIF shall correlate that
15 MSCID with the GSM MSCID when receiving mobile terminated SMS messages (so that the IIF
16 can deliver them to the MSC).
17 j. This is a continuation of the optional procedure started in item i. IIF receives REGCANC. The
18 IIF needs to keep both the current MSCID associated to the SGSN as well as the current
19 MSCID associated to the MSC. The IIF must also keep a record of the last MSCID which was
20 sent to the ANSI-41 HLR to know that is the one stored in the ANSI-41 HLR.
21 k. This is a continuation of the optional procedure started in item i. IIF sends regcanc response.
22 l. This is a continuation of the optional procedure started in item i. IIF receives regnot response.
24 requested, it initiates the GSM MAP Insert Subscriber Data Procedure towards the SGSN after
25 the subscriber has been successfully authorized. This procedure is used to download GPRS
26 subscriber data to the SGSN. Multiple Insert Subscriber Data transactions may be necessary to
27 complete the transfer of subscriber data to the SGSN.
29 o. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the IIF
31 p. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
32 q. The MSC determines that it does not need to notify the IIF (emulating the GSM HLR), since
33 there is no change to the CS location update parameters, so the IIF does not send the Update
34 Location operation to the IIF (emulating the GSM HLR). The GSM MSC acknowledges the
35 BSSAP+LocationUpdateRequest over the Gs interface to the SGSN by sending the Accept
36 message.
37 r. The SGSN acknowledges the Routing Area Update request from the MS.
2-173
X.S0023
1 4.13.1.8 Combined Attach When Currently Registered in an ANSI-41 MSC
2 This scenario describes the case where a mobile that is currently registered in an ANSI-41 MSC
3 performs a combined attach for both GPRS and non-GPRS services.
PMSC/
MS SGSN MSC IIF HLR
VLR
GPRS Attach Req (IMSI)

a
Authentication Info
b
c
Authentication Req
d
Authentication Res
e
f
Insert Sub Data
g
Insert Sub Data Ack
h
i
GPRS_LU
j
Update location Req
k
REGNOT
l
REGCANC
m
regcanc
n
regnot ack
o
Insert Sub Data
p
Insert Sub Data Ack
q
Update location ack
r
s
GPRS Attach Accept
t
GSM NETWORK ANSI-41 NETWORK ANSI-41 NETWORK
4
5
6 Figure 118: Combined Attach when registered on a ANSI-41 MSC (Option 1: With timer)
2-174
X.S0023
4 Request contains the IMSI. The IIF starts timer GPRS LU.
13 j. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
15 k. The MSC determines that it needs to notify the IIF (emulating the GSM HLR), since there is a
17 to the IIF (emulating the GSM HLR). The IIF stops timer GPRS LU.
18 l. The IIF shall send a Registration Notification (REGNOT) to the ANSI-41 HLR to indicate the
19 changed location (MSCID associated with the new GSM MSC).
23 subscriber.
24 m. The HLR updates its location information and deletes the previous VLR record by sending a
25 REGCANC to the previous MSC/VLR.
26 n. The VLR acknowledges the REGCANC.
27 o. The ANSI-41 HLR acknowledges the registration and sends back the subscriber’s information.
28 This information is for non-GPRS services
29 p. The IIF sends MAP INSERT SUBSCRIBER DATA message(s) to the GSM MSC providing GSM
31 q. The GSM MSC acknowledges receipt of the Insert Subscriber Data information.
32 r. The IIF acknowledges the completion of the Update Location procedure and sends the Update
34 s. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface to the
36 t. The SGSN acknowledges the combined GPRS and GSM attach request from the MS.
2-175
X.S0023
PMSC/
MS SGSN MSC IIF HLR
VLR
GPRS Attach Req (IMSI)

a
Authentication Info
b
c
Authentication Req
d
Authentication Res
e
f
REGNOT
g
REGCANC
h
regcanc
i
regnot ack
j
Insert Sub Data
k
Insert Sub Data Ack
l
m
n
Update location Req
o
REGNOT
p
REGCANC
q
regcanc
r
regnot
s
Insert Sub Data
t
Insert Sub Data Ack
u
Update location ack
v
w
GPRS Attach Accept
x
GSM NETWORK ANSI-41 NETWORK ANSI-41 NETWORK
1
2 Figure 119: Combined attach when registered on a ANSI-41 MSC (Option 2: without timer )
4 b. If the Serving GPRS Support Node (SGSN) does not have authentication information in
5 order to perform authentication i.e. authentication triplets, it requests authentication
6 information from the IIF. The IIF emulates a GSM HLR/AuC in this case supporting GPRS.
2-176
X.S0023
7 changed location.
12 h. ANSI-41 HLR sends a REGCANC to the ANSI-41 MSC on which the MS was previously
13 registered.
14 i. ANSI-41 MSC sends regcanc response.
15 j. The ANSI-41 HLR acknowledges the registration and sends back the subscriber’s
16 information in a regnot response.
18 requested, and the MS is currently PS-deregistered, it initiates the GSM MAP Insert
20 authorized. This procedure is used to download GPRS subscriber data to the SGSN.
21 Multiple Insert Subscriber Data transactions may be necessary to complete the transfer of
22 subscriber data to the SGSN.
26 n. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs

27 interface. The GSM MSC creates the association with the SGSN by storing the SGSN
28 Number (e.g. for later CS paging over the Gs interface upon a call delivery attempt).
29 o. The MSC determines that it needs to notify the IIF (emulating the GSM HLR), since there is
30 a change to the CS location update parameters. The MSC sends the Update Location
31 operation to the IIF (emulating the GSM HLR).
32 p. If the IIF implementation supports multiple MSCIDs, then it shall send a Registration
33 Notification (REGNOT) to the ANSI-41 HLR to indicate the changed location (MSCID
34 associated to the new GSM MSC).
39 q. This is a continuation of the optional procedure started in item p. The IIF receives a
40 REGCANC if the MSCID just sent in item (p) is a different one than stored in the ANSI-41
41 HLR. The IIF needs to keep both the current MSCID associated to the SGSN as well as the
42 current MSCID associated to the MSC. The IIF must also keep a record of the last MSCID
2-177
X.S0023
1 r. This is a continuation of the optional procedure started in item p. The IIF acknowledges the
2 regcanc.
3 s. This is a continuation of the optional procedure started in item p. The IIF receives the
4 regnot response with the subscriber’s information. This information is for non-GPRS
5 services.
6 t. The IIF sends MAP INSERT SUBSCRIBER DATA message(s) to the GSM MSC providing
7 GSM CS information based on the contents of the regnot (profile).
8 u. The GSM MSC acknowledges receipt of the Insert Subscriber Data information.
9 v. The IIF acknowledges the completion of the Update Location procedure and sends the
10 Update Location Acknowledgement to the GSM MSC.
11 w. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface to

12 the SGSN by sending the Accept message.
13 x. The SGSN acknowledges the combined GPRS and GSM attach request from the MS.
14 4.13.1.9 Authentication Failure at the IIF
15 In any of the scenarios shown previously in 4.13.1 (assuming authentication is performed),

16 authentication may fail at the IIF.
17 In the event that authentication fails at the IIF (emulating a GSM HLR), it shall send a response to
18 the SGSN indicating the reason for failure.
19 Note: The ANSI-41 HLR is not informed about a registration attempt if authentication fails at the IIF.
20 4.13.1.10 Registration Failure at the ANSI-41HLR
21 In any of the scenarios shown previously in 4.13.1 where the ANSI-41 HLR is informed about the
22 registration attempt (assuming authentication is successful or not performed), the registration
23 procedure may fail.
24 In the event that the ANSI-41 HLR denies the registration attempt, it shall send a regnot to the IIF
25 indicating the reason for failure. If the IIF determines that the MS is already registered in an SGSN,
26 it shall send a Cancel Location to the SGSN. Otherwise, the IIF sends an update GPRS location
27 response indicating the reason for failure.
2-178
X.S0023
1 4.13.2 Location Deregistration Scenarios

2
3 4.13.2.1 GSM CS (IMSI) Detach while GPRS and GSM CS Attached
4 A GPRS mobile attached for both GPRS and non-GPRS services can request a detach for circuit
5 services (IMSI detach). The IIF is not notified about the MS initiated detachment and hence the
6 ANSI-41 HLR is not informed.
7 4.13.2.2 GPRS Detach While Attached for Both GPRS and GSM CS Services
8 A GPRS mobile attached for both GPRS and non-GPRS services can request a GPRS detach. The
9 IIF is not notified about the MS initiated detachment and hence the ANSI-41 HLR is not informed.
10 4.13.2.3 GPRS Detach While Attached for GPRS Services Only
11 In GPRS, the GPRS HLR is not notified when a GPRS subscriber performs a GPRS detach. Hence,
12 the IIF (which is emulating the GPRS HLR) shall not be notified of the GPRS detach. In this case, a
13 GPRS subscriber performs a Detach request that is handled by the SGSN and GGSN to remove
14 MM and PDP contexts. There is no interworking with circuit services.
15 4.13.2.4 Combined GPRS Detach and GSM CS (IMSI) Detach
16 A GPRS mobile attached for both GPRS and non-GPRS services can request a combined detach
17 from GPRS and non-GPRS services. The IIF is not notified about the MS initiated detachment and
18 hence the ANSI-41 HLR is not informed.
2-179
X.S0023
1 4.13.2.5 GPRS Detach Followed By Purge
2 The IIF becomes involved in a detach procedure when the detach procedure is followed by a purge
3 MS procedure. The following scenario shows the case where a GAIT mobile is attached for
4 services to an SGSN-only. The mobile performs a GPRS detach. After accepting the detach
5 request, the SGSN is configured to initiate a purge MS procedure (after some pre-configured time
6 period). In a case when the MS is still GSM CS attached, the MS-Inactive is not sent by the IIF.
7 Likewise, if an MSC sends the PurgeMS operation to the IIF when the subscriber is still GPRS
8 attached, the IIF would not send the MS-Inactive to the ANSI-41 HLR.
ANSI-41/
MS SGSN GGSN IIF
HLR
Detach Request
a
Signaling with GGSN
b
Signaling with GGSN
c
Detach Accept
d
Purge MS
e
Purge MS Ack
f
MS INACTIVE
g
ms inactive
h
9
10
11 Figure 120: MS in GSM Foreign Mode Performing GPRS Detach Followed by Purge
12
13 a. The MS performs a Detach Request to detach from GPRS services. This MS was attached for
14 GPRS services only.
15 b. The SGSN exchanges signaling information with the GGSN to remove PDP contexts on the
16 GGSN for the subscriber.
17 c. See (b)
18 d. The SGSN accepts the detach from the MS and sends a Detach Accept.
19 e. The SGSN is configured to delete MM contexts as soon as the Detach Accept is sent. Hence,
20 the SGSN notifies the IIF (acting as a GPRS HLR) that it has deleted the MM context for the
21 MS.
22 f. The IIF acknowledges the Purge Operation and marks in its GPRS subscription data for the
23 subscriber that the GPRS data has been purged.
24 g. The IIF sends an MSINACTIVE to the ANSI-41 HLR to de-register the MS from the IIF (acting
25 as an ANSI-41 MSC).
26 h. The ANSI-41 HLR acknowledges the MSINACTIVE operation
2-180
X.S0023
1 4.13.2.6 IIF - Initiated Detach
2 The IIF initiated detach procedure is initiated by the IIF. The procedure results in the removal of a
3 subscribers PDP contexts at the SGSN.
MS SGSN GGSN IIF MSC/VLR
Cancel Location
a
Detach Request
b
Delete PDP Context Request
c
Delete PDP Context Response
d
GPRS Detach Indication
e
Detach Accept
f
Cancel Location Ack

g
5 Figure 121: IIF - Initiated Detach

6 a. The IIF requests deletion of a subscribers PDP contexts from the SGSN by sending a Cancel
7 Location (IMSI, Cancellation Type) to the SGSN with Cancellation Type set to Subscription
8 Withdraw.
9
10 b. The SGSN informs the MS that it has been detached by sending Detach Request (Detach
11 Type) to the MS. Detach Type shall indicate that the MS is not requested to make a new
12 attach and PDP context activation.
13
14 c. The active PDP contexts in the GGSNs are de-activated by the SGSN sending Delete PDP
15 Context Request messages to the GGSNs.
16
17 d. The GGSNs acknowledge the Delete Request
18
19 e. If the MS was both IMSI-attached and GPRS–attached the SGSN sends a GPRS Detach
20 Indication (IMSI) to the VLR.
21
22 f. The MS sends a Detach Accept to the SGSN any time after step b.
23
24 g. The SGSN confirms the deletion of the PDP contexts with a Cancel Location Ack (IMSI).
25
26 Note: In some cases the IIF may send an MS Inactive towards the ANSI-41 HLR (but not if CS
27 services are still to be offered).
2-181
X.S0023
1 4.13.3 SMS Scenarios

2 This section describes the scenarios for MS terminated and MS originated SMS while the mobile in
3 roaming in a GPRS network in GSM foreign mode.
4 4.13.3.1 SMS Scenarios for Mobile Terminated SMS while GPRS Attached
5 If the subscriber is both GSM CS attached as well as GPRS attached, then the IIF shall act like a
6 GSM SMS-SC.
7 The scenarios that follow only show the SMS delivery via GPRS.
8 4.13.3.1.1 Successful Mobile Terminated ANSI-41SMS (CMT) Mapped to GSM SMS
ANSI-41 ANSI-41 SGSN

MC HLR IIF MS
SMS
Delivery
a
SMSREQUEST
b
smsrequest
c
SMDPP (CMT)
d
e
SMS Delivery
f
SMS Delivery Ack
g
h
smdpp [ACK]
i
9
10 Figure 122: Successful Mobile Terminating ANSI-41SMS (CMT) mapped to GSM SMS
11
12 a. The ANSI-41Message Center (MC) receives a short message for a specific subscriber. Note:
13 This step is shown for completeness only and is not repeated in subsequent call flows.
14
15 b. The Message Center sends an SMS Request message to the ANSI-41 HLR of the short
16 message recipient to request a routing address for delivering the short message to that
17 subscriber.
18
19 c. Since the subscriber has a current valid location stored in the HLR, the HLR returns it to the MC
20 in the SMS Request Return Result message.
21
22 d. The Message Center then sends a Short Message Delivery Point to Point message to the IIF,
23 which is seen as the current serving ANSI-41 MSC/VLR for that subscriber. Note that in this
24 case, the format used by the MC is the CMT format (Cellular Messaging Transport). Note that
25 alternatively, the ANSI-41MC could translate the original CMT SMS to GHOST/WEMT format
26 before sending it to the IIF if the IIF only supports the GHOST/WEMT format. In this case the IIF
2-182
X.S0023
1 would convert ANSI-41GHOST/WEMT into GSM format (see Section 4.13.3.1.2) instead of
2 ANSI-41CMT into GSM format.
3
4 e. Upon reception of the Short Message Delivery Point to Point message from the ANSI-41MC,
5 the IIF originates a FORWARD SHORT MESSAGE to the SGSN after having translated the
6 short message into GSM format. The IIF is then acting as a GSM SMS-GMSC.
7
8 f. The SGSN sends the short message to the mobile station. Note: This step is shown for
9 completeness only and is not repeated in subsequent call flows.
10
11 g. The mobile station acknowledges the delivery of the short message. Note: This step is shown
12 for completeness only and is not repeated in subsequent call flows.
13
14 h. The SGSN sends the result of the Forward Short Message to the IIF.
15
16 i. The IIF sends the result of the Short Message Delivery Point to Point to the ANSI-41Message
17 Center.
2-183
X.S0023
1 4.13.3.1.2 Successful Mobile Terminating ANSI-41SMS (GHOST/WEMT) Mapped to GSM SMS
3
4
5 Figure 123: Successful Mobile Terminating ANSI-41SMS (GHOST/WEMT) mapped to GSM
6 SMS
7
12 E.164 address).
16 PDU, and routes it to the SGSN as a first choice. Alternatively, the IIF could send the FSM to
17 the GSM MSC (if the 03.40 MNRC flag is not set).
18 e. The SGSN packages the GSM SMS RP-DATA into a CP-DATA message and delivers it across
19 the GSM air interface to the mobile station. The mobile station acknowledges receipt of the CP-
20 DATA and RP-DATA messages via CP-ACK and CP-ACK[RP-ACK], respectively. Upon
21 successful receipt of the RP-ACK, the SGSN shall send a positive acknowledgement Forward
22 Short Message back to the IIF.
24 the MC.
2-184
X.S0023
1 4.13.3.1.3 Unsuccessful Mobile Terminated Delivery (Failure at SGSN)
3 format.
4
5 Figure 124: Unsuccessful Mobile Terminated Delivery (Failure at SGSN)
6
11 E.164 address).
12 c. The MC formats a GHOST/WEMT teleservice or a CMT short message and sends it to the IIF in
13 an SMDPP message.
16 PDU, and routes it to the SGSN. If the message received is in the CMT format, the IIF maps this
17 information into a short message in GSM format.
18 e. The SGSN packages the GSM SMS RP-DATA into a CP-DATA message and delivers it across
19 the GSM air interface to the mobile station. The mobile station negatively acknowledges either
20 the CP-DATA message or the RP-DATA message. The SGSN sends a negative
21 acknowledgement Forward Short Message (with appropriate cause value) back to the IIF.
23 the MC. In addition, the IIF sets one of the GSM SMS flags as defined in the GSM 03.40
24 specification [35] according to the error cause received from the SGSN; that is, the Mobile
25 Subscriber Not GPRS Reachable Flag (MNRG) shall be set if the error cause is “absent
26 subscriber”, and the Memory Capacity Exceeded Flag (MCEF) shall be set if the error cause is
27 “memory capacity exceeded”. Additionally, the IIF emulating the ANSI-41 MSC shall set and
2-185
X.S0023
1 store the SMS Delivery Pending flag with the MC parameters received in the SMDPP (for later
2 delivery in the SMSNOT) – note that this “SMS Delivery Pending” flag/data serves the same
3 purpose as a GSM HLR’s “Message Waiting Data” flag/data. [However, note that if an ANSI-41
4 REGCAN is received from the ANSI-41 HLR before the SMS Delivery Pending Flag is cleared,
5 then the regcanc response shall contain the SMS_MessageWaitingIndicator, and all flags are
6 cleared (i.e., MNRG, MNRF, MCEF, and SMS Delivery Pending Flag)].
2-186
X.S0023
1 4.13.3.1.4 Unsuccessful Mobile Terminated Delivery (Failure at IIF)
3 format.
4
ANSI-41 GSM
MC HLR IIF MSC
SMSREQ a
SMSREQ
b
SMDPP
c
smdpp [NAK]
d
5
6 Figure 125: Unsuccessful Mobile Terminated Delivery (Failure at IIF)
7
9 the MIN (MSISDN) or IMSI of the mobile station and SMS Notification Indicator.
12 E.164 address).
14 d. Upon receipt of the SMDPP message, the IIF examines the GSM 03.40 HLR flags (if “both
15 MNRC and MNRG” or ”MCEF” is set) and determines that the MS is unable to receive a Short
16 Message. The IIF indicates this fact in the SMDPP Return Result. It includes the cause for the
17 failure in the SMS_CauseCode parameter of the SMDPP Return Result. The IIF shall set &
18 store the SMS Delivery Pending Flag with the data received in the SMDPP message (for later
19 delivery in the SMSNOT). If the 03.40 flag is set to MNRG and if the flag is not set to MNRC,
20 then the SMDPP shall be delivered to the GSM MSC as described in GAIT phase 1. If 03.40
21 flag is set to MNRC and not MNRG nor MCEF, then SMS delivery is possible through the SGSN
22 as shown in section 4.13.3.1.
23
24
2-187
X.S0023
1 4.13.3.1.5 Alerting for an ANSI-41Subscriber for GPRS in GSM Foreign Mode
2 The following scenario applies to short messages originated in either CMT or GHOST/WEMT
3 format.
ANSI-41 GSM
SMSC HLR IIF MSC
READY FOR SM
a
SMSNOT
b
smsnot
c
ready for SM
d
5 Figure 126: Alerting for an ANSI-41Subscriber in GSM Foreign Mode

6 a. The SGSN sends a READY FOR SM to the IIF, including as arguments the IMSI, Alert Reason
7 Indicator and Alert Reason. Note: The SMS notification can also be triggered when the SGSN
8 sends an Update GPRS Location. This happens when an MS for whom messages are pending
9 re-attaches or performs an inter-SGSN routing area update, the SGSN sends an Update GPRS
10 Location message to the IIF.
11 b. If the IIF has the SMS Delivery Pending Flag set, and if the MCEF flag is not set, then the IIF
12 sends a SMSNOT to each of the subscriber’s MCs stored with the SMS Delivery Pending Flag.
13 The SMSNOT shall contain; the MIN (MSISDN) as mapped from the IMSI, ESN, and
14 SMS_Address containing the IIF address.
15 c. The MC sends a SMSNOT Return Result to the IIF, then the IIF clears the SMS Delivery
16 Pending Flag, then proceeds to send the mobile station a mobile terminated CMT or
17 GHOST/WEMT teleservice message.
18 d. If the IIF has GSM 03.40 flags set, then these flags shall be cleared according to the “alert
19 reason”; that is, if the “alert reason” is “memory available”, then both the MCEF and MNRG
20 flags are cleared, and if the “alert reason” is “MS present”, then the MNRG flag is cleared. If the
21 UpdateGPRSLocation is received, then the MNRG flag is cleared. The IIF sends a Ready for
22 SM response to the SGSN with no arguments.
23
2-188
X.S0023
1 4.13.4 Message Flows for Mobile Originated SMS when operating GPRS in
2 GSM Foreign Mode
4 message center when the mobile station is operating GPRS in GSM Foreign Mode. The following
5 scenarios apply to short messages delivered to the MC in either CMT or GHOST/WEMT format.
6 4.13.4.1 Successful Mobile Originated SMS to MC
GSM ANSI-41
SGSN HLR IIF MC

a
SMDPP b
smdpp [ACK] c

d
7
8 Figure 127: Successful Mobile Originated Delivery
9
10 a. The SGSN originates a FORWARD SHORT MESSAGE to the address provided by the MS (i.e.,
11 IIF), including as arguments the Service Center Address, MSISDN and GSM SMS-SUBMIT
12 PDU.
15 routes it to the originator’s home MC. The IIF can also map the Forward Short Message into a
16 CMT short message.
17 c. The MC sends a positive acknowledgement SMDPP Return Result to the IIF.
18 d. The IIF maps the received SMDPP Return Result to a Forward Short Message, and sends it to
19 the SGSN.
2-189
X.S0023
1 4.13.4.2 Unsuccessful Mobile Originated (Failure at MC)
GSM ANSI-41
SGSN HLR IIF MC

a
SMDPP b
smdpp [NAK] c

d
2
3 Figure 128: Unsuccessful Mobile Originated Delivery (Failure at MC)
4
6 IIF), including as arguments the Service Centre Address, MSISDN and GSM SMS-SUBMIT
7 PDU.
9 message encapsulating the GSM SMS transfer PDU in a GHOST/WEMT teleservice, and
10 routes it to the MC. The IIF can also map the Forward Short Message into a CMT short
11 message.
12 c. The MC sends a negative acknowledgement SMDPP Return Result to the IIF.
13 d. The IIF maps the received SMDPP Return Result to a Forward Short Message with the
14 appropriate cause code value, and sends it to the SGSN.
2-190
X.S0023
GSM ANSI-41
SGSN HLR IIIF MC

a

b
2
3 Figure 129: Unsuccessful Mobile Originated (Failure at IIF)
5 IIF), including as arguments the Service Centre Address, MSISDN and GSM SMS-SUBMIT
6 PDU.
7 b. Upon receipt of the FORWARD SHORT MESSAGE, the IIF builds a negative acknowledgement
8 Forward Short Message and sends it to the SGSN.
9
2-191
X.S0023
1 4.13.5 Message Waiting Notification while GPRS Attached in GSM Foreign

2 Mode
3 This section illustrates the interactions between network entities in various situations related to
4 mobile originations and GPRS in GSM foreign mode and Message Waiting Notification. For a native
5 ANSI-41subscriber roaming in a GSM environment, there can be two events that trigger the IIF to
6 send the Message Waiting Notification (MWN) using the GSM SMS to the Mobile Station (MS). The
7 first one is at registration (update GPRS location), if there is an indication in the ANSI-41 HLR that
8 messages have been delivered to the subscriber’s voice mail box, the ANSI-41 HLR shall indicate
9 that in the Registration Notification Return Result message. This shall trigger the IIF to send a GSM
10 SMS with the MWN information. This is shown in section 4.13.5.1. The second event is when the
11 HLR receives a Message Waiting Notification for a subscriber that is already registered. In this
12 case, the ANSI-41 HLR shall send a Qualification Directive message to the IIF which shall translate
13 it into a GSM SMS with MWN indication. This is shown in Section 4.13.5.2.
14 If the subscriber is both GSM CS attached as well as GPRS attached, then the IIF shall act like a
15 GSM SMS-SC.
16 The scenarios that follow only show the MWN SMS delivery via GPRS.
2-192
X.S0023
1 4.13.5.1 Indicator in ANSI-41 Registration Notification Return Result mapped

2 to GSM SMS
GSM
ANSI-41 ANSI-41
IIF SGSN MS
VMS HLR
Vmail
Delivery
a
“Message Waiting
Notification”
b
GPRS attach req
UPDATE GPRS c
LOCATION
d
REGNOT
regnot (MWNCOUNT,
e
MWNTYPE)
f
INSERT_SUB_DATA
g
Insert_sub_data
h
update gprs location
i
GPRS Accept
FORW. SHORT
j
MESSAGE (MWN)
k
SMS Delivery (MWN)
l
SMS Delivery Ack
m
Forw. Short
Message
n
3
4
5 Figure 130: Indicator in ANSI-41 Registration Notification Return Result mapped to GSM SMS
7
10 ANSI-41.D [2]. Note also that at that point in time, the subscriber is not registered in any serving
11 system, so the HLR just keeps the information that a voice mail was received.
12
13 c. The Mobile Station accesses a serving system and originates an update location request.
14
15 d. The Update Location is sent from the serving GSM MSC/VLR to the IIF, seen as the GSM HLR
16 for that subscriber.
17
18 e. The IIF sends a Registration Notification to the ANSI-41 HLR of the subscriber.
19
20 f. The ANSI-41 HLR replies with the Registration Notification Return Result containing the
21 “Message Waiting Notification” information that consists of two parameters:
2-193
X.S0023
1 (MWNTYPE). For a description of these parameters, refer to the ANSI-41.D specifications,

2 sections 6.5.2.78 and 6.5.2.79 [2].
3
4 At this point, the IIF sets the MWN flag. This is an indication that Message Waiting Notification is to
5 be delivered to the Mobile Station.
6
7 g. The IIF sends Insert Subscriber Data to the serving GSM SGSN. Note that there could be more
8 than one Insert Subscriber Data message depending on the subscriber profile.
9
10 h. The serving GSM SGSN returns the Insert Subscriber Data result. Note that there could be
11 more than one such result message, one matching every Insert Subscriber Data message.
12
13 i. The IIF completes the location update by sending the Update Location result message to the
14 serving GSM SGSN.
15
16 j. The serving GSM SGSN confirms the update location to the mobile station.
17
18 k. Since the REGNOT return result from event f contained the Message Waiting Notification
19 information, this triggers the IIF to originate an SMS with MWN information by sending Forward
20 Short Message to the serving GSM SGSN. The IIF is then acting as a GSM SMS-GMSC. The
21 IIF is to encode the MWN information in the SMS with three methods, namely, UDH, DCS, and
22 CPHS. Refer to Volume 3 for the encoding details.
23
24 l. The serving GSM SGSN sends the short message with the MWN information to the mobile
25 station.
26
28
29 n. The serving GSM SGSN sends the result of the Forward Short Message to the IIF.
30
32 without error indicates that the MWN information was delivered successfully to the Mobile Station.
33
2-194
X.S0023
1 4.13.5.2 ANSI-41 Qualification Directive mapped to GSM SMS
ANSI-41 GSM
VMS HLR IIF SGSN MS
Vmail
Delivery
a
“Message Waiting
Notification”
b
QUALDIR(MWNCOUNT,
MWNTYPE) c
qualdir d
FORW. SHORT
MESSAGE (MWN) e
SMS Delivery (MWN) f
SMS DeliveryAck g
Forw. Short
Message
h
2
3 Figure 131: ANSI-41 Qualification Directive mapped to GSM SMS
5
8 ANSI-41 [2].
9
14 (MWNTYPE). For a description of these parameters, refer to the ANSI-41-D specifications,
15 sections 6.5.2.78 and 6.5.2.79 [2].
16
19
20 d. The IIF sends the result of the Qualification Directive message to the ANSI-41 HLR.
21
22 e. The IIF also originates an SMS with MWN information by sending a Forward Short Message to
23 the serving GSM SGSN. The IIF is then acting as a GSM SMS-GMSC. The IIF is to encode the
24 MWN information in the SMS with three methods, namely, UDH, DCS, and CPHS. Refer to
25 Volume 3 for the encoding details.
26
27 f. The serving GSM SGSN sends the short message with the MWN information to the mobile
28 station.
29
30 g. The mobile station acknowledges the delivery of the short message.
31
32 h. The serving GSM SGSN sends the result of the Forward Short Message to the IIF.
33
2-195
X.S0023
2-196
X.S0023
1 4.13.5.3 Handling at SMS delivery failure at the SGSN or at the Mobile Station
2 The IIF is to keep a Message Waiting Notification (MWN) flag for each subscriber in its database. In
3 the event of a failure to deliver a short message with MWN to the mobile station, the IIF is to keep
4 the MWN flag set. Another Forward Short Message with MWN information shall be sent, triggered
5 by the reception of a subsequent GSM Update Location message, a Ready for Short Message, or a
6 Note MS Present message. This is illustrated in the following diagram.
GSM
IIF SGSN MS
MWN “Information”
a
FORW. SHORT
MSG (MWN) – V3 b
SMS Delivery (MWN)
c
SMS Delivery Error
d
Error, Abort,
Reject, timeout e
Time elapsed
f
UPDATE GPRS LOCATION
g
READY FOR SM
(AlertReason) – V3
h
“Acknowledgement”
i
FORW. SHORT
MSG (MWN) – V3 j
SMS Delivery (MWN)
k
SMS Delivery Ack
Forw. Short l
Message
m
8 Figure 132: Handling at SMS delivery failure at the SGSN or at the MS

11 4.13.5.2.
12
15
17 MAP V2 to the serving GSM SGSN. The IIF is then acting as a GSM SMS-GMSC. The IIF is to
18 encode the MWN information in the SMS with three methods, namely, UDH, DCS, and CPHS.
19 Refer to Volume 3 for the encoding details.
2-197
X.S0023
1
2 c. The serving GSM SGSN may attempt to deliver the short message or may immediately find out
3 that there is an error and reply (step e below) to the IIF.
4
5 d. The Mobile Station returns an error message to the SMS delivery.
6
7 e. The serving GSM SGSN sends an Error, Abort or Reject message to the IIF, either resulting
8 from the reception of an error message from the MS or from an internal event such as an error
9 or a timeout. Note also, that a timeout may also occur in the IIF itself. Note that this may result
10 in the IIF setting the GSM 03.40 MNRF/MNRG/MCEF flag depending on the error cause
11 received (see section 4.13.3.1.3 “Unsuccessful Mobile Terminated Delivery (Failure at SGSN)”.
12
13 f. Time elapsed.
14
15 g. A new serving GSM SGSN sends an Update GPRS Location message to the IIF acting as a
16 GSM HLR for that subscriber. Note that the normal Update Location sequence is not shown in
17 this diagram. Or it could be a
18
19 h. Ready for Short Message (MAP V3)
20
21
22 i. The IIF shall reply with the corresponding acknowledgement message. Upon receipt of g, h, or i
23 above, the procedures in section 4.13.3.1.5 “Alerting for an ANSI-41Subscriber for GPRS in
24 GSM Foreign Mode” apply (GSM 03.40 flags may be cleared and the SMSNOT may be sent to
25 the MC if appropriate).
26
27 j. Triggered by event g, h, or i above, the IIF originates a new Forward Short Message with MWN
28 information to the serving GSM SGSN. The IIF is to encode the MWN information in the SMS
29 with three methods, namely, UDH, DCS, and CPHS.
30
31 k. The serving GSM SGSN sends the short message with the MWN information to the mobile
32 station.
33
34 l. The mobile station acknowledges the delivery of the short message.
35
36 m. The serving GSM SGSN sends the result of the Forward Short Message to the IIF.
37
38
41
2-198
X.S0023
1 4.13.6. Call Delivery Scenarios

2 This section describes the scenarios for call delivery to an MS that is roaming in a GPRS network in
3 GSM foreign mode.
4 4.13.6.1 Call Delivery Scenarios in GSM Foreign Mode while GSM CS and GPRS Attached
6 4.13.6.1.1 Call Delivery to ANSI-41Subscriber Roaming on a GSM/GPRS Network
GSM ANSI-41
MS SGSN MSC IIF HLR O-MSC
Incoming call a
LOCREQ b
ROUTEREQ
c
PRN d
prn e
routereq
f
locreq
g
ISUP signaling / SS7
h
PAGING-REQ
i
Paging Procedure j
SUSPEND To BSS k
7 Figure 133: Call Delivery to ANSI-41Subscriber Roaming in GSM/GPRS Network

8
9 a. The originating ANSI-41 MSC receives an incoming call from the PSTN for a subscriber that is
10 roaming in a GSM/GPRS network. This MS is registered simultaneously with an SGSN and a
11 GSM MSC/VLR.
12 b. The O-MSC sends a LOCREQ to the ANSI-41 HLR
13 c. The ANSI-41 HLR knows the address of the IIF (acting as an ANSI-41 serving MSC) and sends
14 a ROUTEREQ to it
15 d. The call may be delivered if the IIF determines that the called MS is registered with on a GSM
16 MSC/VLR. As such, the IIF (acting as a GSM HLR) sends the serving GSM MSC/VLR a MAP
17 Provide Roaming Number (PRN).
18 e. The serving GSM MSC/VLR responds with a prn to the PRN operation providing a temporary
19 routing number.
2-199
X.S0023
1 f. The IIF forwards this number to the ANSI-41 HLR in the routereq.
2 g. The ANSI-41 HLR forwards a locreq to the O-MSC with the temporary routing number.
3 h. The O-MSC proceeds to contact the serving GSM MSC/VLR exchanging ISUP signaling for call
4 setup.
5 i. The serving GSM MSC/VLR realizes that the MS is actually attached to an SGSN. So the GSM
6 serving MSC/VLR sends a BSSAP+PAGING-REQUEST to the SGSN.
7 j. The SGSN executes a Paging procedure for circuit services.
8 k. The MS sends a SUSPEND REQ to the BSS that may be forwarded to the SGSN. At this point,
9 the MS can respond to the page via GSM cell sites to the serving GSM MSC/VLR.
2-200
X.S0023
1 4.13.6.1.2 Call Delivery to ANSI-41Subscriber Roaming in a GPRS Network (Unsuccessful)
2 The following scenario describes the case where a subscriber in GSM foreign mode is roaming in a
3 GPRS network. The MS is attached for GPRS-only services. The IIF has already registered itself
4 (as an ANSI-41 MSC) with the ANSI-41 HLR. Since the MS is attached for GPRS-only service,
5 incoming calls are not deliverable to the subscriber. This scenario attempts to describe what
6 happens in the case of an incoming call to an MS attached for GPRS services only.
GSM ANSI-41
MS SGSN IIF HLR MSC

Incoming call
a
LOCREQ b
ROUTEREQ c
routereq d
locreq e
FSM f
SMS Exchange g
fsm h
7
8 Figure 134: MS Notification of a “Missed” Call via SMS
9
10 a. The O-MSC receives an incoming call for the subscriber roaming in the GSM network
11 b. The O-MSC sends the HLR a LOCREQ
12 c. The HLR has the address of the IIF (acting as an ANSI-41 MSC) and sends a ROUTEREQ to
13 the IIF
14 d. The IIF recognizes that fact this is a GAIT subscriber roaming in a GSM network. The IIF, from
15 its dynamic data, sees that the subscriber is attached for GPRS-only services and hence,
16 cannot have call delivery. The IIF sends a routreq with the field “AccessDeniedReason” set to
17 “Unavailable” or “No Page Response”.
18 e. The HLR returns a locreq to the O-MSC. At this point, the calling party may receive secondary
19 treatment.
20 f. The IIF contains the functionality to act as an SMS-SC. In this case, the IIF has the calling party
21 DN available (from the ROUTEREQ message). The IIF proceeds to act as an SMS-SC and
2-201
X.S0023
1 sends an FSM to the SGSN requesting the SGSN to deliver an SMS message containing the
2 calling party’s DN to the MS.
3 g. The SGSN sends the MS the SMS message containing the DN of the calling party and the MS
4 acknowledges receipt of the SMS message.
5 h. The SGSN acknowledges the request and sends back an fsm.
2-202
X.S0023
1 4.13.6.2 Successful Network-Requested PDP Context Activation Procedure
2 The network requested PDP Context Activation procedure allows the GGSN to initiate the activation
3 of a PDP context when a data packet arrives for a particular PDP address and no PDP context has
4 been previously established.
MS SGSN IIF GGSN
PDP
PDU a
SRI for
b
GPRS
SRI for Ack
GPRS c
PDU Notification
Request d
PDU Notification
e
Response
Request PDP context
Activation f
Activate PDP context g
Request
SendAuth
Info h
SendAuth Ack
Info i
Create PDP Context j

Request
Create PDP Context k
Response
Activate PDP context l
Accept
6 Figure 135: Successful Network Requested PDP context Activation
8 a. When receiving a PDP PDU the GGSN follows the procedures described in GSM 03.60 [33]
9
10 b. The GGSN may send a Send Routeing Information for GPRS (IMSI) message to the IIF.
11
12 c. The IIF determines if the request can be served. If the request can be served it returns a
13 Send Routeing Information for GPRS Ack (IMSI, SGSN Address) to the GGSN. If the request
14 cannot be served it returns a Send Routeing Information for GPRS Ack (IMSI, MAP Error
15 Cause).
16
2-203
X.S0023
1 d. Steps d through l are provided for completeness and are outside the scope of this
2 specification.
3 Note: Certain security procedures as in step h) may be invoked.
4 4.13.6.3 Unsuccessful Network-Requested PDP Context Activation Procedure
5 If the PDP context requested by the GGSN cannot be established, the IIF in conjunction with the
6 SGSN and GGSN may perform the Protection and Mobile User Activity Procedures as described in
7 GSM 03.60 [33]. The IIF acting as a GPRS HLR shall follow the same procedures as the GSM
8 HLR.
9 4.13.7 Packet Domain Subscriber Data in the IIF

10 GPRS subscriber data shall be provisioned in the IIF (emulating a GPRS HLR) to support GPRS
11 service capability in GSM Foreign mode. The IIF shall store the same subscription information as
12 identified in GSM 03.60 [33].
13 It may be possible to provision an ANSI-41native subscriber with GPRS-only service (and no GSM
14 CS service)
2-204
X.S0023
1 Annex A (informative)
2 The following is an example of some of the timers defined in existing ANSI-41 and GSM
3 specifications.
4 As an example, the GSM timer controlling, the Update Location Request is defined to be in the
5 range 15s to 30s whereas the equivalent ANSI-41 timer controlling the REGNOT is defined to be a
6 default value of 12s.
LOCATION REGISTRATION PROCEDURES

GSM Timer Value ANSI-41 Timer Value
Operation Operation
Update 15s to 30s REGNOT 12s
Location
Request
Insert Sub 15s to 30s
Data
CALL DELIVERY PROCEDURES
Operation Operation
Provide 15s to 30s ROUTREQ 10s
Roaming
Number
SUBSCRIBER DATA MANAGEMENT PROCEDURES
Operation Operation
Cancel 15s to 30s REGCANC 6s
Location
Request
Delete Sub 15s to 30s QUALDIR 6s
Data
SUPPLEMENTARY SERVICE PROCEDURES
Operation Operation
REGISTER 15s to 30s FEATREQ 16s
SS
ERASE SS 15s to 30s
ACTIVATE SS 15s to 30s
DE-ACTIVATE 15s to 30s
SS
2-205
X.S0023
OPTIMAL ROUTING PROCEDURES

Operation Operation
Resume Call 15s to 30s REDREQ 22s
Handling
TRANUMREQ 16s
SHORT MESSAGE PROCEDURES
Operation Operation
Forward SM 1m to 10m SMDPP 6s
1
2 Notes: GSM timer values are defined as a range of values, whereas ANSI-41 defines a default timer
3 value.
2-206
X.S0023
1 Annex B - CDMA to GSM One-way Roaming Only

2 Optionally, IIF may support one way-roaming only from CDMA to GSM network. In this case, all the
3 flows below are applicable only in GSM Foreign Mode. ANSI-41 HLR/AC must be compliant with
4 TIA/EIA-868 [11]. All the changes are made on the assumption the new requirements for
5 UIM/handsets are working.
6 B.1 Successful Authentication on Initial Access in GSM System

7
8 This scenario illustrates the successful authentication of an MS on the initial MS access is a GSM
9 system
ANSI-41 GSM
HLR MSC/ MS
AC IIF VLR
Location area update (IMSI)
a
SEND_AUTH_INFO (IMSI)
b
AUTHREQ (MSCID, SYSCAP, MSID, ESN, SYSAC)
AUTHREQ (MSCID, SYSCAP, MSID, ESN, SYSAC) c
AUTHREQ (MSCID, d
ART SYSCAP, MSID,
ART ESN, SYSAC)
Authreq (SSD, ESN) e
Authreq (SSD, ESN)
f
SEND_AUTH_INFO ack (AuthenticationSetList)
g
authentication (RAND) h
ASRRT
authentication ack (SRES)
i
UPDATE LOCATION (IMSI) j

ASREPORT (MSCID, MSID, UCHALRPT)
k
l
ASRT
ASRRT ASRRT
asreport[]
m
asreport[]
n
REGNOT [MSCID, TRANSCAP, SYSCAP, MSID, ESN, SYSAC]
o
10
11 Figure 136 – Successful Authentication on Initial Access in GSM System
12
13 a) The MS determines that a new serving system has been entered. The MS registers at the new GSM
14 serving system and provides its IMSI.
15
16 b) The GSM serving system sends a SEND_AUTHENTICATION_INFO to the IIF.
2-207
X.S0023
1
2 c) The IIF sends an AUTHREQ to the HLR associated with the MS. The MSCID parameter identifies the
3 IIF. The SYSCAP parameter is set to indicate GSM system. The ESN parameter is set to a default
4 value. The SYSACCTYPE parameter is set to indicate GSM system access.
5
6 d) The HLR forwards the AUTHREQ to the AC.
7
8 e) The AC determines that the subscriber is roaming in a GSM system. The AC includes the SSD
9 parameter in the authreq sent to the HLR. The ESN parameter is set to the indicated MS’s ESN.
10
11 f) The HLR forwards the authreq to the IIF.
12
13 g) The IIF stores the received SSD and ESN. The IIF computes one or more groups of GSM triplets using
14 the subscriber’s SSD. The IIF sends a SEND_AUTHENTICATION_INFO ack to the GSM system and
15 includes the groups of triplets.
16
17 h) The GSM system issues a random challenge to the MS
18
19 i) The MS responds to the challenge with the computed response.
20
21 j) The GSM system compares the response received from the MS with the expected response. In this
22 scenario, the response is equal to the expected response. The GSM system sends a
23 UPDATE_LOCATION to the IIF. The IMSI is used to identify the MS.
24
25 k) The IIF sends an ASREPORT to the HLR associated with the MS. The UCHALRPT parameter is set
26 to indicate Unique Challenge successful.
27
28 l) The HLR forwards the ASREPORT to the AC.
29
30 m) The AC sends an asreport to the HLR.
31
32 n) The HLR forwards the asreport to the IIF.
33
34 o) The IIF sends a REGNOT to the HLR
35
36 p) The HLR sends a regnot to the IIF with the subscriber’s service profile
37
38 q) The IIF sends an INSERT_SUBSCRIBER_DATA to the GSM system.
39
40 r) The GSM systems sends an INSERT_SUBSCRIBER_DATA ack to the IIF.
41
42 s) The IIF sends an LOCATION_UPDATE ack to the GSM system.
43
44 t) The GSM system sends a location area update ack to the MS.
45
46
2-208
X.S0023
1 B. 2 Authentication Failure on Initial Access in GSM System

2 This scenario illustrates an authentication failure on the initial MS access is a GSM system.
3 The GSM system reports the authentication failure to the IIF.
ANSI-41 GSM
HLR MSC/ MS
AC IIF VLR
a
b
AUTHREQ (MSCID, d
ART SYSCAP, MSID,
ART ESN, SYSAC)
Authreq (SSD, ESN)
f
SEND_AUTH_INFO ack (AuthenticationSetList) g
authentication (RAND)
h
ASRRT
i
AUTHENTICATION FAILURE (IMSI) j

k
l
ASRRT ASRRT
asreport[DENACC]
m
asreport[DENACC]
n
AUTHENTICATION_FAILURE
o
location area update reject p
4
5 Figure 137 - Authentication Failure on Initial Access in GSM System
2-209
X.S0023
1 a-i. Same as Scenario 5.Y.1, Steps a-i.

2
4 scenario, the response does equal to the expected response. The GSM system sends an
5 AUTHENTICATION_FAILURE to the IIF. The subscriber’s IMSI is used to identify the MS.
6
7 k) The IIF sends an ASREPORT to the HLR associated with the MS. The UCHALRPT parameter is set
8 to indicate Unique Challenge failed.
9
10 l) The HLR forwards the ASREPORT to the AC.
11
12 m) The AC includes the DENACC parameter and sends an asreport to the HLR.
13
14 n) The HLR forwards the asreport to the IIF. The IIF removes the SSD, ESN and other information
15 stored for the MS.
16
17 o) The IIF sends an AUTHENTICATION_FAILURE ack to the GSM system.
18
19 p) The GSM system sends a location area update reject to the MS.
2-210
X.S0023
1 B.3 Authentication Failure on Initial Access in GSM System –

2 Authentication Failure Message Not Supported
3
4 This scenario illustrates an authentication failure on the initial MS access is a GSM system. The GSM
5 system doe not report the authentication failure to the IIF
ANSI-41 GSM
HLR MSC/ MS
AC IIF VLR
a
b
AUTHREQ (MSCID, d
ART SYSCAP, MSID,
ART ESN, SYSAC)
Authreq (SSD, ESN)
f
g
ASRRT timer
i
Location area update reject j
timer expiry k
l

m
ASRRT ASRRT
asreport[DENACC]
n
asreport[DENACC]
o
6
7
8 Figure 138 - Authentication Failure on Initial Access in GSM System – Authentication Failure Message
9 Not Supported
10
11 a-i. Same as Scenario 5.Y.1, Steps a-i.
12
14 scenario, the response does equal to the expected response. The GSM system compares the response
15 received from the MS with the expected response. In this scenario, the response does equal to the
16 expected response. The GSM system sends a location area update reject to the MS.
17
18 k) An IIF timer expires when no message for the MS is received from the GSM system.
19
20 l) The IIF sends an ASREPORT to the HLR associated with the MS. The UCHALRPT parameter is set
21 to indicate Unique Challenge failed.
2-211
X.S0023
1
2 m) The HLR forwards the ASREPORT to the AC.
3
4 n) The AC includes the DENACC parameter and sends an asreport to the HLR.
5
6 o) The HLR forwards the asreport to the IIF. The IIF removes the SSD, ESN and other information stored
7 for the MS.
8
2-212
X.S0023
1 B.4 GSM System Request for Additional Triplets

2 This scenario illustrates a GSM system requesting addition triplets after the MS is register in the serving GSM
3 system.
4
ANSI-41 GSM
HLR MSC/ MS
AC IIF VLR
SEND_AUTHENTICATION_INFO (IMSI)
a
b

5 Figure 139 - GSM System Request for Additional Triplets
d
6
7 a) The GSM system determines that additional triplets are required and sends a e
8 SEND_AUTHENTICATION_INFO
Authreq (SSD, ESN) to the IIF. The IMSI identifies the subscriber.
9 b) The IIF computes one or more groups of triplets and includes them in the response fto
10 the GSM system. (Note, the IIF may have pre-computed triplets for the MS that it g
11 sends to the GSM system).
12
ASRRT timer
i
Location area update reject j
timer expiry k
l

m
ASRRT ASRRT
asreport[DENACC]
n
asreport[DENACC]
o
2-213
X.S0023
1 N
Neettw
woorrkk IInntteerrw
woorrkkiinngg BBeettw
weeeenn G
GS SMMM MAAPP aanndd TTIIA
A--4411 M
MAAP
P;;
2 R
Reevviissiioonn B
B –– CCDDMMA A22000000 S
Suuppppoorrtt
3 V
Voolluum
mee 33 –– M
Meessssaaggee M
Maappppiinnggss
4 ((R
STTD
D--003388--A
AVVoolluum
mee 33))
5 Abstract
6 This volume contains the mappings between GSM MAP messages and TIA-41 MAP messages.
3-i
X.S0023
1 Contents
2 ABSTRACT.................................................................................................................................................... I
3 CONTENTS................................................................................................................................................... II
4 LIST OF TABLES ........................................................................................................................................IV
5 LIST OF FIGURES ......................................................................................................................................XI
6 FOREWORD ...............................................................................................................................................XII
7 1 INTRODUCTION ................................................................................................................................... 1
8 1.1 General..............................................................................................................................................................1
9 1.2 Purpose..............................................................................................................................................................1
10 1.3 Scope..................................................................................................................................................................1
11 4 MESSAGE MAPPINGS ........................................................................................................................ 2
12 4.1 Mobility Procedures ........................................................................................................................................2

13 4.1.1 Location Registration ................................................................................................................................2
14 4.1.2 Fault Recovery.........................................................................................................................................15
15 4.2 Call Handing Procedures..............................................................................................................................19

16 4.2.1 Automatic Call Delivery .........................................................................................................................19
17 4.2.2 Invocation of Conditional Call Forwarding in ANSI-41 Foreign Mode...............................................32
18 4.2.3 Optimal Routing after Late Call Forwarding .........................................................................................36
19 4.3 Supplementary Services Procedures ...........................................................................................................45

20 4.3.2 SS Registration and Erasure....................................................................................................................61
21 4.3.3 Retrieval of Forward-To Number ...........................................................................................................83
22 4.3.4 Calling Number / Line Identification Presentation/Restriction .............................................................87
23 4.4 O&M Procedures...........................................................................................................................................92

24 4.4.1 Detailed Procedures.................................................................................................................................92
25 4.4.2 Mapping of Messages, Parameters & Parameter Values .......................................................................93
26 4.4.3 Error Handling.......................................................................................................................................111
27 4.5 Short Message Procedures (ANSI-41 Network) ......................................................................................116

28 4.5.1 Short Message Service via CMT ..........................................................................................................116
29 4.5.2 Short Message Service via GHOST or WEMT ...................................................................................132
30 4.5.3 Message Waiting Notification ..............................................................................................................142
31 4.6 GPRS IN GSM FOREIGN MODE .............................................................................................151

32 4.6.1 Mobility Procedures ..............................................................................................................................151
33 4.6.2 Automatic Call Delivery .......................................................................................................................159
3-ii
X.S0023
1 4.6.3 Short Message Procedures for ANSI-41 subscriber.............................................................................162

2 4.6.4 Short Message Service via GHOST or WEMT ...................................................................................165
3 4.6.5 Message Waiting Notification ..............................................................................................................166
4 ANNEX A SHORT MESSAGE SERVICE PROCEDURES WITHIN AN ANSI-136 NETWORK..........168
5 A.1 CMT to GHOST Delivery...........................................................................................................................168

6 A.1.1 Detailed Procedures...............................................................................................................................168
7 A.1.2 Mapping of Messages, Parameters & Parameter Values .....................................................................169
8 A.1.3 Error Handling.......................................................................................................................................170
9 A.2 GHOST to CMT Delivery...........................................................................................................................170

11 A.2.2 Mapping of Messages, Parameters & Parameter Values .....................................................................172
12 A.2.3 Error Handling.......................................................................................................................................176
13 A.3 Callback Number.........................................................................................................................................177

15 A.3.2 Message Mapping, Parameters and Parameters Values.......................................................................178
16 A.3.3 Error Handling.......................................................................................................................................178
17 ANNEX B CAUSE CODE MAPPING AT NON-IIF NODES ...................................................................179
18 ANNEX C: CDMA TO GSM ONE-WAY ROAMING ONLY....................................................................181

19
3-iii
X.S0023
1 List of Tables
2
3 Table 1: Location Updating in GSM Foreign Mode Message Mapping............................................... 5
4 Table 2: Location Updating in ANSI-41 Foreign Mode Message Mapping ......................................... 5
5 Table 3: MS Purging Message Mapping............................................................................................... 6
6 Table 4: Location Cancellation Message Mapping............................................................................... 6
7 Table 5: UPDATE_LOCATION_REQUEST  REGNOT Parameter Mapping.................................. 7
8 Table 6: INSERT_SUBSCRIBER_DATA_REQUEST  regnot Parameter Mapping ....................... 8
9 Table 7: UPDATE LOCATION RESPONSE  regnot Parameter Mapping....................................... 9
10 Table 8: MS_PURGE_REQUEST  MS INACTIVE Parameter Mapping ......................................... 9
11 Table 9: CANCEL_LOCATION_REQUEST  REGCAN Parameter Mapping................................ 10
12 Table 10: UPDATE_LOCATION_RESPONSE to regnot Error Mapping .......................................... 14
13 Table 11: regnot return errors to UPDATE_LOCATION_RESPONSE Error Mapping..................... 15
14 Table 12 Fault Recovery Message Mapping ...................................................................................... 16
15 Table 13: GSM RESET  ANSI UNRELDIR Parameter Mapping ................................................... 17
16 Table 14: Automatic Call Delivery Message Mapping........................................................................ 21
17 Table 15: ROUTREQ  PROVIDE_ROAMING_NUMBER_REQUEST Parameter

18 Mapping ............................................................................................................................. 22
19 Table 16: Provide Roaming Number Response  Routreq Return Result Parameter
20 Mapping ............................................................................................................................. 24
21 Table 17: PROVIDE_ROAMING_NUMBER_RESPONSE to Routreq Return Error Mapping

22 (ANSI-41Foreign Mode) .................................................................................................... 24
23 Table 18: Routreq Return Error to Provide Roaming Number Response Error Mapping
24 (GSM Foreign mode) ........................................................................................................ 25
25 Table 19: Provide Roaming Number Request default parameter...................................................... 25
26 Table 20: RoutingRequest Return Result default parameters ........................................................... 26
27 Table 21: Routing Request Invoke default parameter........................................................................ 27
28 Table 22: PRN response User Error to routreq Return Error Mapping ............................................ 30
3-iv
X.S0023
1 Table 23: PRN Response Provider Error to routereq Return Error Mapping.................................... 31
2 Table 24: RoutingRequest Return Result to User Error in the PRN response Error Mapping......... 31
3 Table 25: Routing Request Return Error to PRN User Error Mapping.............................................. 31
4 Table 26: ROUTEREQ Return Result to Provide Roaming Number Response parameter
5 mapping (Option 1)............................................................................................................ 34
6 Table 27: ROUTREQ Return Result to Provide Roaming Number Response Parameter
7 Mapping (Option 2)............................................................................................................ 34
8 Table 28: Return Error to User Error in the PRN response Error Mapping....................................... 36
9 Table 29: Optimal Routing for Late Call Forwarding Message Mapping........................................... 38
10 Table 30: GSM Provide_Roaming_Number  ANSI-41 ROUTEREQ Parameter Mapping ........... 39
11 Table 31: Mapping of Parameter values ............................................................................................. 40
12 Table 32: Provide_Roaming_Number_Response  routereq Parameter Mapping ........................ 40
13 Table 33: Mapping of Parameter Values ............................................................................................ 41
14 Table 34: Resume_Call_Handling  REDREQ Parameter Mapping ............................................... 41
15 Table 35: Mapping of Parameters Values........................................................................................... 41
16 Table 36: Resume_Call_Handling_Response  redreq Parameter Mapping ................................. 41
17 Table 37: ANSI-41 Redirection_Reason to GSM Forwarding_Reason............................................. 42
18 Table 38: GSM Forwarding_Reason to ANSI-41 Redirection_Reason............................................. 42
19 Table 39: Provide_Roaming_Number to Routing_Request Error Mapping ...................................... 43
20 Table 40: Routing_Request to Provide_Roaming_Number Error Mapping ...................................... 43
21 Table 41: Resume_Call_Handling to Redirection_Request Error Mapping ...................................... 44
22 Table 42: Redirection_Request to Resume_Call_Handling Error Mapping ...................................... 44
23 Table 43: Supplementary Service Activation and Deactivation Message Mapping.......................... 47
24 Table 44: Activate/Deactivate SS Request  FEATREQ Parameter Mapping................................ 48
25 Table 45: Activate/Deactivate SS Response  Feature Request Return Result Parameter

26 Mapping ............................................................................................................................. 49
27 Table 46: Activate/Deactivate SS Response  Feature Request Return Error Mapping ............... 50
28 Table 47: Activate/Deactivate SS Request to FEATREQ Parameter Mapping ................................ 50
3-v
X.S0023
1 Table 48: FEATREQ default parameter.............................................................................................. 51
2 Table 49: Activate/Deactivate SS Response default parameter values............................................ 52
3 Table 50: Feature Request Invoke to Activate/Deactivate SS Request Parameter Mapping .......... 53
4 Table 51: Activate/Deactivate SS Request default parameter........................................................... 53
5 Table 52: FeatureRequest Return Result default parameter............................................................. 54
6 Table 53: FeatureRequest Return Result to User Error in the Activate/Deactivate SS

7 Response Error Mapping .................................................................................................. 57
8 Table 54: FeatureRequest Return Error to Activate/Deactivate SS Response Error

9 Mapping ............................................................................................................................. 57
10 Table 55: Activate/Deactivate SS Response User Error to FeatureRequest Return Result

11 Mapping ............................................................................................................................. 58
12 Table 56: Activate/Deactivate SS Response User Error to FeatureRequest Return Error

13 Mapping ............................................................................................................................. 59
14 Table 57: Activate/Deactivate SS Response Provider Error to Feature Request Return

15 Error Mapping.................................................................................................................... 60
16 Table 58: Supplementary Service Registration Message Mapping................................................... 63
17 Table 59: Register SS Request  FEATREQ parameter mapping .................................................. 64
18 Table 60: Register SS Response  Feature Request Return Result Parameter Mapping............. 65
19 Table 61: Register SS Response  Return Error Parameter Mapping............................................ 66
20 Table 62: Register SS Request to Feature Request Invoke parameter mapping............................. 66
21 Table 63: FEATREQ default parameter.............................................................................................. 67
22 Table 64: Register SS Response default parameter values .............................................................. 68
23 Table 65: FEATREQ to Register SS Request parameter mapping................................................... 69
24 Table 66: Register SS Request default parameter............................................................................. 69
26 Table 68: FeatureRequest Return Result to User Error in the Register SS Response
27 mapping ............................................................................................................................. 71
28 Table 69: Supplementary Service Erasure Message Mapping.......................................................... 74
29 Table 70: Erase SS Request  FEATREQ parameter mapping ...................................................... 75
30 Table 71: Erase SS Response  Feature Request Return Result parameter mapping ................. 76
3-vi
X.S0023
1 Table 72: Erase SS Response  Return Error parameter mapping ................................................ 77
2 Table 73: Erase SS Request to FEATREQ parameter mapping....................................................... 77
3 Table 74: Feature Request Invoke default parameter........................................................................ 78
4 Table 75: Erase SS Response default parameter values .................................................................. 79
5 Table 76: FEATREQ to Erase SS Request parameter mapping...................................................... 79
6 Table 77: Erase SS Request default parameter................................................................................. 80
8 Table 79: FeatureRequest Return Result to Register SS Response User Error .............................. 82
9 Table 80: Retrieval of Forward-to-Number in GSM Foreign Mode.................................................... 84
10 Table 81: TransferToNumberRequest Return Result to Insert Subscriber Data parameter

11 mapping ............................................................................................................................. 85
12 Table 82: TransferToNumberRequest Return Result to Insert Subscriber Data Request

13 value mapping ................................................................................................................... 86
14 Table 83: Routing Request  Provide Roaming Number Request (Network Provided
15 number) Parameter Mapping............................................................................................ 88
16 Table 84: Routing Request  Provide Roaming Number Request (User Provided number)
17 Parameter Mapping........................................................................................................... 89
18 Table 85: Routing Request  Provide Roaming Number Request (Two calling party
19 numbers) Parameter Mapping .......................................................................................... 90
20 Table 86: Routing Request  Provide Roaming Number Request(Caller Id Restricted)

21 Parameter Mapping........................................................................................................... 91
22 Table 87: Cancel_Location_Request  REGCAN (Subscriber Deletion) Mapping......................... 93
23 Table 88: Mapping of GSM MAP Messages  ANSI MAP Messages (Subscriber Data
24 Modification) ...................................................................................................................... 93
25 Table 89: Delete_Subscriber_Data  Qualdir Mapping (Subscriber Data Modification)................. 94
26 Table 90: CANCEL_LOCATION_REQUEST  REGCAN Parameter Mapping.............................. 94
27 Table 91: INSERT_SUBSCRIBER_DATA_REQUEST  QUALDIR Parameter Mapping ............. 95
28 Table 92: INSERT_SUBSCRIBER_DATA_REQUEST  profile ‘macro’ Mapping ......................... 96
29 Table 93: Forwarding Information List to Calling Features Indicator Parameter Mapping ............... 98
30 Table 94: Regional Subscription Data to Geographic Authorization Parameter Mapping.............. 100
3-vii
X.S0023
1 Table 95: Call Barring Information List to Origination Indicator Parameter Mapping ..................... 101
2 Table 96: SSData List to Calling Features Indicator Parameter Mapping....................................... 103
3 Table 97: Operator Determined Barring general data to Origination Indicator

4 Parameter Mapping......................................................................................................... 105
5 Table 98: Operator Determined Barring HPLMN data to Origination Indicator Parameter
6 Mapping ........................................................................................................................... 106
7 Table 99: Operator Determined Barring HPLMN data to Restriction digits Parameter
8 Mapping ........................................................................................................................... 106
9 Table 100: Call Barring Information List to SMS Origination Restrictions Parameter
10 Mapping ........................................................................................................................... 107
11 Table 101: Call Barring Information List to SMS Termination Restrictions Parameter
12 Mapping ........................................................................................................................... 108
13 Table 102: Call Barring Information List to Termination Restriction Code Parameter
14 Mapping ........................................................................................................................... 109
15 Table 103: SSData List to SMS Origination Restrictions Parameter Mapping ............................... 110
16 Table 104: SSData List to SMS Termination Restrictions Parameter Mapping.............................. 110
17 Table 105: ISD_RESPONSE and DSD_RESPONSE to Qualdir Return Error Mapping................ 115
18 Table 106: Qualdir Return Error to INSERT_SUBSCRIBER_DATA_RESPONSE and

19 DELETE_SUSBCRIBER_DATA_RESPONSE Error Mapping ..................................... 115
20 Table 107: Short Message Service in GSM Foreign Mode (for CMT) Message Mapping ............. 119
21 Table 108: Short Message Service in ANSI-41 Foreign Mode (for CMT) Message Mapping ...... 119
22 Table 109: SMDPP to MT_Forward Short Message Parameter Mapping for GSM Foreign
23 Mode ................................................................................................................................ 120
24 Table 110: MT_Forward Short Message to SMDPP Parameter Mapping for ANSI-41
25 Foreign Mode .................................................................................................................. 120
26 Table 111: SM-RP-UI in MT_FORWARD_SHORT_MESSAGE for MAP V2 Parameter

27 Values for GSM Foreign Mode ....................................................................................... 121

29 Encoding for GSM Foreign Mode ................................................................................... 122
30 Table 113: SMS_Bearer Data in Mobile Terminating SMDPP Parameter Encoding for
31 ANSI-41 Foreign Mode ................................................................................................... 123
32 Table 114: Forward_Short_Message to ANSI-41_SMDPP Parameter Mapping for MO SMS

33 in GSM Foreign Mode ..................................................................................................... 124
3-viii
X.S0023
1 Table 115: ANSI-41 SMDPP to GSM Forward_Short_Message Parameter Mapping for MO

2 SMS in ANSI-41 Foreign Mode ...................................................................................... 126
3 Table 116: Forward_Short_Message to SMS_CauseCode Values in SMDPP Return Result

4 Error Mapping.................................................................................................................. 130
5 Table 117: SMDPP to Forward_Short_Message Error Mapping..................................................... 131
6 Table 118: Short Message Service (for GHOST or WEMT) Message Mapping............................. 135
7 Table 119: Alerting for an ANSI-41 Subscriber in GSM Foreign Mode Parameter Mapping ......... 136
8 Table 120: Alerting for a GSM Subscriber in ANSI-41 Foreign Mode Parameter Mapping ........... 136
9 Table 121: SMDPP to Forward Short Message for Mobile Terminated GHOST/WEMT
10 Teleservice Parameter Mapping in GSM Foreign Mode ............................................... 137
11 Table 122: Forward Short Message to SMDPP for Mobile Terminated GHOST/WEMT
12 Teleservice Parameter Mapping in ANSI Foreign Mode ............................................... 138
13 Table 123: Forward Short Message to SMDPP for Mobile Originated GHOST/WEMT in
14 GSM Foreign Mode Parameter Mapping ....................................................................... 139
15 Table 124: SMDPP to Forward Short Message for Mobile Originated GHOST/WEMT
16 Teleservice Parameter Mapping in ANSI-41 Foreign Mode.......................................... 140
17 Table 125: HLPI for GHOST.............................................................................................................. 141
18 Table 126: Teleservice Server Address Mapping in IIF ................................................................... 142
19 Table 127: Message Waiting Notification in GSM Foreign Mode Message Mapping..................... 144
20 Table 128: Message Waiting Notification in ANSI-41 Foreign Mode Message Mapping ............... 145
21 Table 129: regnot to Forward Short Message for Message Waiting Notification Parameter
22 Mapping ........................................................................................................................... 145
23 Table 130: QUALDIR to Forward Short Message for Message Waiting Notification
25 Table 131: Forward Short Message to QUALDIR for Message Waiting Notification
27 Table 132: Forward Short Message to SMDPP for Message Waiting Notification Parameter
28 Mapping ........................................................................................................................... 146
29 Table 133: SM-RP-UI in Message FORWARD-SHORT-MESSAGE For MAP V2 Parameter

30 Encoding.......................................................................................................................... 147
31 Table 134: SM-RP-UI in Message FORWARD_SHORT-MESSAGE for MAP V1 Parameter

32 Encoding.......................................................................................................................... 149
3-ix
X.S0023
1 Table 135: qualdir return error to FORWARD_SHORT_MESSAGE response Error

2 Mapping ........................................................................................................................... 150
3 Table 136: SMSDPP to FORWARD_SHORT_MESSAGE response Error Mapping..................... 150
4 Table 137: Location Updating GPRS in GSM Foreign Mode Message Mapping ........................... 152
5 Table 138: MAP_UPDATE_GPRS_LOCATION_REQUEST  REGNOT Parameter

6 Mapping ........................................................................................................................... 153
7 Table 139: MAP_INSERT_SUBSCRIBER_DATA_REQUEST  regnot Parameter Mapping...... 154
8 Table 140: MAP_UPDATE GPRS LOCATION RESPONSE  regnot Parameter Mapping ......... 155
9 Table 141: MAP_INSERT_SUBSCRIBER_DATA_REQUEST  profile ‘macro’ Mapping............ 156
10 Table 142: ROUTREQ  MT_Forward Short Message Parameter Mapping................................ 160
11 Table 143: Alerting for an ANSI-41 Subscriber for GPRS in GSM Foreign Mode Parameter
12 Mapping ........................................................................................................................... 163
13 Table 144: ANSI-136-710 to GHOST Parameter Mapping.............................................................. 169
14 Table 145: TP Derived Values........................................................................................................... 170
15 Table 146: GHOST to ANSI-136-710 Parameter Mapping.............................................................. 172
16 Table 147: CMT Derived Values ....................................................................................................... 173
17 Table 148: SMS_CauseCode to TP-STATUS Mapping................................................................... 174
18 Table 149: SMS-STATUS-REPORT Derived Values....................................................................... 176
19 Table 150: RP-ERROR Cause to R-Cause for Mobile Station Response to Mobile
20 Terminated Transfer Attempt.......................................................................................... 179
21 Table 151: ANSI-41 SMS_CauseCode to ANSI-136 R-Cause Code Mapping .............................. 180
22 Table 152: ANSI-136 R-Cause Code to RP-ERROR Cause Mapping within the Mobile
23 Station.............................................................................................................................. 180
24 Table 153: UPDATE_LOCATION_REQUEST ->REGNOT Parameter Mapping ........................... 181
25
3-x
X.S0023
1 List of Figures
2
3 There are no figures in this volume.
3-xi
X.S0023
1 Foreword
2
6 standard is to achieve fully automatic, two-way interoperability between the heterogeneous
7 networks. Services supported by this standard are described along with the associated information
8 flows and message mappings. However, not all services and associated capabilities of ANSI-41
9 MAP and GSM MAP are supported by this standard. In general the attempt has been to focus on
10 the key subscriber services needed in the market.
11 The focus of this standard is on common GSM and ANSI-136/TIA-2000 TDMA and CDMA services
13 interoperability is Multi-mode mobile stations with an enhanced SIM card for roaming between
14 ANSI-41 and GSM networks.
16 MAP to achieve the described interworking and interoperability. However, due to differences
17 between the services and associated capabilities of the MAP protocols, complete and fully
18 transparent interoperability may not have been achieved for some services. Future releases of this
19 standard may require changes to ANSI-41 MAP, GSM MAP and the associated services to achieve
20 full transparency while roaming between the different networks.
21 Aspects of TIA/EIA-136 Revision C have been incorporated into this standard.
22 Revision A added the capability of getting GPRS services when roaming in GSM Foreign Mode.
23 Revision B added two way roaming between GSM and CDMA systems
3-xii
X.S0023
1 1 Introduction
2
3 1.1 General
4 When a subscriber to one network type (e.g., ANSI-41) roams to a network of another type
5 (e.g., GSM), interworking and interoperability functions are required to support roaming and
6 enable service. This standard describes an Interworking and Interoperability Function (IIF) to
7 support this cross-technology roaming between ANSI-41 and GSM networks. The IIF supports
8 a multi-mode mobile station with a removable Subscriber Identity Module (SIM). The standard
9 also defines the required network message mappings between ANSI-41 MAP and GSM MAP to
10 support the mobile terminal and associated services.
11 This standard includes the support of cross-technology roaming from an ANSI-41 based
12 network to a GPRS network. The GPRS network may be coupled with a GSM network. This
13 feature requires enhancement to the Interworking and Interoperability Function (IIF) which
14 supports a multi-mode mobile station and Subscriber Identity Module (SIM) with GPRS
15 functionality. GPRS foreign mode roaming requires a subscription in the GSM domain. There is
16 no interaction with the CDMA packet data network infrastructure defined.
17 Optionally, IIF may support one way-roaming only from CDMA to GSM network. In this case, all
18 the relevant mapping tables described are applicable only in GSM Foreign Mode and for this
19 scenario they apply as unidirectional only. (Annex C)
20 1.2 Purpose
21 The purpose of this standard is to define and describe the functions necessary for roaming
22 between ANSI-41 MAP and GSM MAP based networks in the support of roaming subscribers.
23 This includes a capability to allow a subscriber to an ANSI-41 based network (e.g., an ANSI-41
24 TDMA or CDMA native subscriber) with a mobile terminal supporting GPRS service to roam to
25 a GPRS network in GSM Foreign Mode.
26 1.3 Scope
27 The scope of this standard is the services, information flows, and message mappings which
29 ANSI-41 MAP [2] and GSM MAP [4] networks.
30 The scope of this volume is to describe the processing, messages and parameters for
31 GPRS/GSM and ANSI-41 network interoperability.
3-1
X.S0023
1 4 Message Mappings
2
3 The IIF shall perform the translation of messages, parameters and parameter values in
4 accordance with the tables included in this volume of the standard. The following notation is
5 used in accordance with the definitions given in GSM 09.02 [4] and ANSI-41 [2].
6 Within the following tables, the parameters are identified as either being:
7 M Mandatory,
8 C Conditional
9 O Service Provider Optional
10 U Service User Optional
11 The following notation is used in this standard to identify parameters as being syntactically
12 optional but semantically required to be sent by the IIF in order to support interoperability:
13 R Required.
14 Refer to GSM 09.02 [4] and ANSI-41 [2] for a description of the messages, parameters and
15 parameter values.
16 When the IIF receives either a GSM MAP message or an ANSI MAP message, it shall apply
17 the following rules regarding the handling of parameters within those messages:
18  The IIF shall populate mandatory parameters in messages sent by the IIF, regardless
19 of whether mapping of parameters is possible.
20  The IIF may populate optional parameters in messages sent by the IIF, regardless of
21 whether mapping of parameters is possible.
22 All parameters shall be populated in accordance with GSM 09.02 [4] and ANSI-41 [2].
23 Where there is no direct mapping for parameters, a hyphen (‘-‘) has been entered in the
24 corresponding table.
25
26 4.1 Mobility Procedures

27 Existing mobility procedures described in either GSM 09.02 [4] or ANSI-41 [2] are also directly
28 applicable to the IIF when it is emulating a GSM or ANSI-41 functional network element.
29 Enhancements/modifications to ANSI-41 [2] are also applicable.
30 4.1.1 Location Registration

31 The location registration procedure is used to update the location information held in the
32 network. This location information is used to route incoming calls and short messages to the
33 roaming subscriber.
34 The Location registration procedure is also used to cancel location information held in the
35 network.
3-2
X.S0023
1 4.1.1.1 Detailed Procedures

2
3 4.1.1.1.1 Location Updating

4
5 The IIF contains location information (vlr number) relating to the roaming subscriber. Therefore,
6 the IIF needs to be updated at each change in VLR. The IIF shall translate GSM MAP
7 messages to ANSI-41 MAP messages and vice versa, when the subscribers home HLR needs
8 updating. The subscriber’s home HLR needs to be updated only in the following cases:
9  When the subscriber’s MS registers in a GSM network, when previously registered in

10 an ANSI-41 network;
11  When the subscribers MS registers in an ANSI-41 network, when previously registered

12 in a GSM network;
13 Optionally, the subscriber’s home HLR may be updated in the following cases:
14  When the subscribers MS (accessing a GSM Network) registers in another VLR within
15 the same GSM network;
16  When the subscribers MS (accessing an ANSI-41 Network) registers in another VLR

17 within the same ANSI-41 network;
18 When the HLR is updated, the IIF conveys a unique identifier to the HLR identifying the serving
19 MSC/VLR.
20 If the IIF receives a GSM MAP _UPDATE_LOCATION_REQUEST, it shall compare the

21 received location information with any previously stored location information. If the received
22 and previously stored location information are different, the IIF shall determine if the location
23 updating is allowed and update the corresponding subscriber record accordingly and send a
24 GSM MAP _CANCEL_LOCATION_REQUEST to the old VLR. If there is no previously stored
25 location information in the IIF, the IIF shall determine if the location updating is allowed and
26 update the corresponding subscriber record accordingly. In either case, if the HLR is required
27 to be updated, then the IIF shall send an ANSI_MAP_REGNOT to the HLR and await a
28 response.
29 If the response indicates that the location updating procedure has been successful, then the IIF
30 shall update the corresponding subscriber record and send a GSM MAP
31 _INSERT_SUBSCRIBER_DATA_REQUEST to the serving VLR and await a response. If the
32 response indicates success, the IIF completes the location updating procedure by sending a
33 GSM MAP _UPDATE_LOCATION_RESPONSE to the serving VLR. The GSM MAP
34 _UPDATE_LOCATION_RESPONSE contains a unique identifier, identifying the HLR.
35 Otherwise, the IIF sends a GSM MAP _UPDATE_LOCATION_RESPONSE to the serving VLR
36 indicating the reason why the location updating procedure was not successful.
37 If the response indicates that the location updating procedure has been unsuccessful, then the
38 IIF shall not update the corresponding subscriber record and shall send a GSM MAP
39 _UPDATE_LOCATION_RESPONSE to the serving VLR indicating the reason for failure.
40 If the IIF receives an ANSI_MAP_REGNOT, it shall compare the received location information
41 with any previously stored location information. If the received and previously stored location
42 information is different, the IIF shall update the corresponding subscriber record and send an
43 ANSI_MAP_REGCAN to the old VLR. If there is no previously stored location information in
3-3
X.S0023
1 the IIF, the corresponding subscriber record is updated. In either case, if the HLR is required to
2 be updated, then the IIF shall send a GSM MAP _UPDATE_LOCATION_REQUEST to the HLR
3 and await a response.
4 If the response indicates that the location updating procedure has been successful, then the IIF
5 shall update the corresponding subscriber record and send an ANSI_MAP_regnot to the
6 serving VLR. The ANSI_MAP_regnot contains a unique identifier, identifying the HLR.
7 If the response indicates that the location updating procedure has been unsuccessful, then the
8 IIF shall not update the corresponding subscriber record and shall send an ANSI_MAP_regnot
9 to the serving VLR indicating the reason for failure.
10 If the IIF receives a GSM MAP _MS_PURGE_REQUEST, it shall check the contents of the
11 message for errors. If errors exist, the IIF shall send a GSM MAP _MS_PURGE_RESPONSE
12 indicating the reason for failure and the MS purged flag shall not be set. If no errors exist, the
13 IIF shall check if the received VLR number matches the stored VLR number.
14 If the received VLR number and the stored VLR number match, the IIF shall set the MS purged
15 flag and shall send both a GSM MAP _MS_PURGE_RESPONSE to the VLR (including the
16 Freeze TMSI parameter) and an ANSI_MAP_MS_INACTIVE to the HLR and awaits a response
17 from the HLR.
18 If the received VLR number and the stored VLR number do not match, the IIF sends a GSM
19 MAP _PURGE_MS_RESPONSE containing an empty result to indicate successful outcome
20 and the MS purged flag is not set.
21 When the IIF receives a response from the HLR, it shall follow the VLR procedures outlined in
22 ANSI-41 [2].
23 If the IIF receives an ANSI_MAP_MS_INACTIVE, it shall check the contents of the message for
24 errors. If errors exist, the IIF shall send an ANSI_MAP_ms_inactive indicating the reason for
25 failure and shall not set the MS state to inactive. If no errors exist, the IIF shall set the MS state
26 to inactive and follow the HLR procedures described in ANSI-41 [2]. If the state of the MS
27 remains inactive for a period of time (time controlled by operator), the IIF may send a GSM
28 MAP _MS_PURGE_REQUEST to the HLR.
29 4.1.1.1.2 Location Cancellation

30
31 If the IIF receives a GSM MAP _CANCEL_LOCATION_REQUEST as part of a location

32 cancellation procedure it shall check the contents of the message for errors. If errors exist, the
33 corresponding temporary subscriber data is not deleted and the IIF shall send a GSM MAP
34 _CANCEL_LOCATION_RESPONSE indicating the reason for failure to the HLR. If no errors
35 exist, the IIF shall delete the corresponding temporary subscriber data and send an
36 ANSI_MAP_REGCAN to the VLR and await a response.
37 If the response indicates that the location cancellation procedure has been successful, then the
38 IIF shall send a GSM MAP _CANCEL_LOCATION_RESPONSE to the HLR.
39 If the response indicates that the location cancellation procedure has been unsuccessful, then
40 the IIF shall send a GSM MAP _CANCEL_LOCATION_RESPONSE to the HLR indicating
41 successful deletion of subscriber data (i.e., ignore the error).
3-4
X.S0023
1 If the IIF receives an ANSI_MAP_REGCAN and the message can be processed, the IIF shall
2 delete the corresponding temporary subscriber data and send a GSM MAP
3 _CANCEL_LOCATION_REQUEST to the VLR and await a response.
4 If the response indicates that the location cancellation procedure has been successful, then the
5 IIF shall send an ANSI_MAP_regcan to the HLR.
6 If the response indicates that the location cancellation procedure has been unsuccessful, then
7 the IIF shall send an ANSI_MAP_regcan to the HLR indicating successful deletion of subscriber
8 data (i.e., ignore the error). The IIF may retry to sending the ANSI_MAP_REGCAN before
9 responding to the HLR.
10 If the IIF receives an ANSI_MAP_REGCAN and the message cannot be processed, the
11 corresponding temporary subscriber data shall not be deleted and the IIF shall send an
12 ANSI_MAP_regcan to the HLR indicating reason for failure.
13 4.1.1.2 Mapping of Messages, Parameters & Parameter Values

14
15 4.1.1.2.1 Mapping of Messages

16
17 Table 1 shows the mapping between GSM MAP messages and ANSI MAP messages related
18 to Location Registration.
19 Table 1: Location Updating in GSM Foreign Mode Message Mapping

GSM MAP Messages ANSI MAP Messages
UPDATE_LOCATION_REQUEST REGNOT
INSERT_SUBSCRIBER_DATA_REQUEST regnot
UPDATE_LOCATION_RESPONSE regnot1
20
21
1
22 This message can also contain error values if the location updating procedure is unsuccessful.
23 If the location updating procedure fails, the mapping is as shown in 4.1.1.3Table 2 shows the
24 mapping between GSM MAP messages and ANSI MAP messages related to Location
25 Registration in ANSI-41 Foreign Mode.
26 Table 2: Location Updating in ANSI-41 Foreign Mode Message Mapping

UPDATE_LOCATION_REQUEST REGNOT
UPDATE_LOCATION_RESPONSE regnot
27
3-5
X.S0023
1 Table 3 shows the mapping between GSM MAP messages and ANSI MAP messages (MS
2 Purging, regardless of mode of operation)
4 Table 3: MS Purging Message Mapping

MS_PURGE MS Inactive
5
8 to Location Cancellation.
9 Table 4: Location Cancellation Message Mapping

CANCEL_LOCATION_REQUEST REGCAN
CANCEL_LOCATION_RESPONSE regcan
10
3-6
X.S0023
1 4.1.1.2.2 Mapping of Parameters

2
3 Table 5 through Table 9 shows the mapping of parameters, which the IIF shall perform
4 regardless of the mode of operation (GSM Foreign Mode or ANSI-41 Foreign Mode).
5 Table 5: UPDATE_LOCATION_REQUEST  REGNOT Parameter Mapping

GSM MAP Status ANSI_MAP_REGNOT Status
_UPDATE_LOCATION_
REQUEST
IMSI M ElectronicSerialNumber M
MSID M
1 1
MSC Address M MSCID (Serving MSC) M
- QualificationInformationCode M
- SystemMyTypeCode M
- MSCIdentificationNumber O
VLR Number M -
- PC_SSN (Serving MSC or VLR) O
2
- SystemAccessType O
2
TerminalType O
2
- TransactionCapability O
LMSI U -
Supported CAMEL Phases C -
1
6 These parameters are used to convey a unique identifier from the IIF to the HLR,
7 identifying the serving MSC/VLR.
2
8 Parameters are included in ANSI specifications IS-41-C and later.
3-7
X.S0023
2 Table 6 shows the mapping of parameters for GSM MAP

3 _INSERT_SUBSCRIBER_DATA_REQUEST to regnot.
4 Table 6: INSERT_SUBSCRIBER_DATA_REQUEST  regnot Parameter Mapping

GSM MAP Status regnot Status
_INSERT_SUBSCRIBER_
DATA_REQUEST
- SystemMYTypeCode (VLR or M
HLR)
- AuthorizationDenied O
- Authorization Period O
- ControlChannelData O
- DeniedAuthorizationPeriod O
- Digits (Carrier) O
- Digits (Destination) O
- MSCID (HLR) O
1
- Profile “Macro” O
- ReceivedSignalQuality O
- SenderIdentificationNumber O
- SMS_MessageWaitingIndicator O
- SystemAccessData O
- MSID O
IMSI C -
5
1
6 This parameter is itself a macro containing a number of other parameters. The IIF shall
7 map the contents of the ‘Profile’ macro in the ANSI-41-D ‘regnot’ to the contents of the
8 GSM MAP _INSERT_SUBSCRIBER_DATA_REQUEST as shown in Table 92
3-8
X.S0023
1 Table 7: UPDATE LOCATION RESPONSE  regnot Parameter Mapping

_UPDATE_LOCATION_
RESPONSE
HLR)
1, 2 2
HLR number R MSCID (HLR) R
3
- MSID O
2
1
3 The presence of this parameter is mandatory in case of successful HLR updating.
2
4 These parameters are used to convey a unique identifier from the IIF to the serving
5 MSC/VLR, identifying the HLR.
3
6 This parameter is itself a macro containing a number of other parameters. As far as
7 mapping of parameters is concerned, the IIF shall map the contents of the ‘Profile’ macro in
8 the ANSI-41-D ‘regnot’ to the contents of the GSM MAP
9 _INSERT_SUBSCRIBER_DATA_REQUEST as shown in Table 92.
10 Table 8: MS_PURGE_REQUEST  MS INACTIVE Parameter Mapping

GSM MAP Status MS INACTIVE Status
_MS_PURGE_REQUEST
IMSI M MSID M
VLR Number C -
- ESN M
- CallHistoryCount O
- DeregistrationType O
- LocationAreaId O
- SMSMessageWaitingIndicator O
11
3-9
X.S0023
2 Table 9: CANCEL_LOCATION_REQUEST  REGCAN Parameter Mapping

GSM MAP Status ANSI_MAP_REGCAN Status
_CANCEL_LOCATION_
REQUEST
IMSI M ESN M
MSID M
LMSI C -
1
Cancellation Type C Cancellation Type O
SystemAccessData O
3
1
4 Cancellation Type is only used between the HLR and the SGSN for GPRS procedures.
5 Cancellation Type is not applicable between HLR and VLR.
6 4.1.1.3 Error Handling

7
8 Error handling defined in GSM 09.02 [4] and ANSI-41 [2] is directly applicable to the IIF, when
9 the IIF is emulating a GSM or ANSI-41 network functional element.
3-10
X.S0023
1 4.1.1.3.1 Location Updating

2
3 If the Location Updating procedure fails at an ANSI-41 HLR, the HLR shall respond by either
4 sending:
5
6 An ANSI_MAP_regnot in a TCAP RETURN RESULT indicating authorization denied
7 (AUTHDEN) to the IIF, with one of the following reasons as defined in ANSI-41 [2]:
8 Appropriate AUTHDEN Values in ANSI_MAP_regnot RETURN RESULT
AUTHDEN Value
Delinquent account.
Invalid serial number.
Stolen unit.
Duplicate unit.
Unassigned directory number.
Unspecified.
Multiple access.
Not Authorized for the MSC.
Missing authentication parameters.
TerminalType mismatch
10 The ANSI-MAP-regnot may optionally, indicate:
11 • The authorization period (DENAUTHPER) as defined in ANSI-41 [2]
12 • Access Info as defined in ANSI-41 [2]
3-11
X.S0023
1 Or, an ANSI_MAP_regnot in a TCAP RETURN ERROR one of the following error codes as
2 defined in ANSI-41 [2]:
3 Appropriate Error Codes in ANSI_MAP_regnot RETURN ERROR
Error Codes
MSID/HLRMismatch
ResourceShortage
OperationNotSupported
ParameterError
SystemFailure
UnrecognizedParameter
Value
MissingParameter
4 The IIF is therefore responsible for mapping any errors it receives from the HLR in the ANSI-
5 MAP-regnot to an equivalent error in the GSM-MAP-UPDATE-LOCATION RESPONSE towards
6 the serving GSM MSC/VLR.
8 The GSM-MAP-UPDATE-LOCATION RESPONSE may include one the following ‘user’ errors
9 as defined in GSM 09.02 [4]:
10 Appropriate User Errors
User Errors
unknown subscriber;
roaming not allowed;
system failure;
unexpected data
value.
11
3-12
X.S0023
1 The following ‘provider errors’ (protocol related errors) are also defined in GSM 09.02 [4]:
2 Appropriate Provider Errors
duplicated invoke Id;
not supported service;
mistyped parameter;
resource limitation;
initiating release (i.e., the peer has already

initiated release of the dialogue and the service
has to be released);
unexpected response from the peer;
service completion failure;
no response from the peer;
invalid response received.
4 If the Location Updating procedure fails at a GSM HLR, it returns a GSM MAP
5 _UPDATE_LOCATION_RESPONSE to the IIF, indicating a ‘user error’ as indicated above.
6 The IIF is therefore responsible for mapping any errors it receives into a corresponding error in
7 the ANSI_MAP_regnot towards the serving ANSI MSC/VLR. For further description of these
8 errors and when they are used, refer to either GSM 09.02 [4] or ANSI-41 [2].
3-13
X.S0023
1 The table below provides the mapping of both user errors and provider errors to the equivalent
2 value in either the AUTHDEN parameter in the ANSI_MAP_regnot RETURN RESULT or the
3 RETURN ERROR for ANSI-41 Foreign Mode.
4 Table 10: UPDATE_LOCATION_RESPONSE to regnot Error Mapping

UPDATE_LOCATION_RESPONSE regnot
(Errors)
Unknown subscriber SystemFailure
roaming not allowed Not Authorized for the MSC
system failure SystemFailure
unexpected data value SystemFailure
duplicated invoke Id SystemFailure
not supported service SystemFailure
mistyped parameter SystemFailure
resource limitation SystemFailure
initiating release SystemFailure
unexpected response from the peer SystemFailure
service completion failure SystemFailure
no response from the peer SystemFailure
invalid response received SystemFailure
5
3-14
X.S0023
1 Table 11 provides the mapping for GSM Foreign Mode.
2 Table 11: regnot return errors to UPDATE_LOCATION_RESPONSE Error Mapping

regnot UPDATE_LOCATION_RESPONSE
(Errors)
Delinquent account System failure
Invalid serial number System failure
Stolen unit System failure
Duplicate unit System failure
Unassigned directory number System failure
Unspecified System failure
Multiple access System failure
Not Authorized for the MSC Roaming not allowed
Missing authentication parameters System failure
TerminalType mismatch System failure
MSID/HLRMismatch Unknown subscriber
ResourceShortage System failure
OperationNotSupported System failure
ParameterError System failure
SystemFailure System failure
UnrecognizedParameterValue System failure
MissingParameter System failure
3
4 4.1.1.3.2 Location Cancellation

5 If the Location Cancellation procedure fails at the IIF, existing procedures described in GSM
6 09.02 [4] and ANSI-41 [2] apply.
7 4.1.2 Fault Recovery

8
9 After the fault of a location register, the fault recovery procedures ensure that subscriber data in
10 the VLR becomes consistent with the subscriber data stored in the IIF or that subscriber data in
11 the IIF becomes consistent with the subscriber data that are stored in the HLR for the MS
12 concerned and that the location information in the IIF and VLR or HLR and IIF reflect accurately
13 the current location of the MS.
14

16
17 If the IIF receives an ANSI_MAP_UNRELDIR, it shall send a RETURN RESULT and clear the
18 records of those MSs associated with the requesting HLR. The IIF shall then send a GSM MAP
3-15
X.S0023
1 _RESET towards the serving VLR containing a unique identity, identifying the ANSI-41 HLR.
2 When the MS concerned next establishes authenticated radio contact (including a mobile
3 originated call attempt), the IIF shall receive a GSM MAP _UPDATE_LOCATION_REQUEST
4 and shall follow the procedures outlined in
5 4.1.1 Location Registration.
6 If the IIF receives a GSM MAP _RESET, it shall derive all involved MSs of that HLR either from
7 the HLR Identity List (if present), or from the HLR number. The IIF shall then mark these MSs
8 with the indicator "Location Information Confirmed in HLR" set to "Not Confirmed". The IIF shall
9 then send an ANSI_MAP_UNRELDIR towards the serving VLR containing a unique identity,
10 identifying the GSM HLR. The status "Not Confirmed" of the indicator "Location Information
11 Confirmed in HLR" forces the IIF to invoke the GSM MAP _UPDATE_LOCATION service after
12 establishment of authenticated radio contact with the MS concerned.
13 If the IIF suffers a failure, while operating in GSM Foreign Mode, it shall send a GSM MAP
14 _RESET to the serving GSM VLR once it has returned to a stable state. The IIF shall not
15 receive a response. The IIF may also send an ANSI_MAP_BULKDEREG to the ANSI-41 HLR.
16 If the IIF suffers a failure, while operating in ANSI-41Foreign Mode, it shall send an
17 ANSI_MAP_UNRELDIR to the serving ANSI-41 VLR once it has returned to a stable state. The
18 IIF shall receive an indication of success or failure.
19 If the IIF receives an ANSI_MAP_BULKDEREG, it shall send a RETURN RESULT to the

20 requesting VLR and clear the location pointer of those MSs that were registered in the
21 requesting VLR. Otherwise, the IIF shall send a RETURN ERROR with an appropriate error
22 value to the requesting VLR.
23

25
26 The IIF shall perform the mapping of messages, parameters and parameter values related to
27 fault recovery in accordance with the tables presented in 4.1.2.2.

29
31 to fault recovery in either mode of operation (GSM Foreign mode or IS-41 Foreign mode)
32 Table 12 Fault Recovery Message Mapping

RESET UNRELDIR
33
3-16
X.S0023

2 Table 13 shows the mapping of parameters, which the IIF shall perform regardless of the mode
3 of operation (GSM Foreign Mode or ANSI-41Foreign Mode).
4 Table 13: GSM RESET  ANSI UNRELDIR Parameter Mapping

GSM MAP _RESET Status ANSI_MAP_UNRELDIR Status
HLR Id LIST U
HLR Number1 M MSCID (HLR) 1 R
5
1
6 These parameters are used to convey a unique identifier from the IIF to the serving VLR,
7 identifying the true HLR.

9
12 If the Fault Recovery procedure fails at an ANSI-41 VLR, the VLR shall respond by either
13 sending:
14 An ANSI_MAP_unreldir in a TCAP RETURN ERROR with one of the following error codes as
16
17 Appropriate Error Codes in ANSI_MAP_unreldir RETURN ERROR
18
Error Codes
ResourceShortage
SystemFailure
19
20 There are no error handling procedures defined in GSM 09.02 [4] covering the case where
21 Fault Recovery procedures fail at a GSM VLR i.e. the GSM MAP _RESET service is a non-
22 confirmed service. As such, the IIF shall not map ANSI-41 error values to equivalent GSM
23 error values.
3-17
X.S0023
1 If the Fault Recovery procedure fails at the IIF following the reception of an
2 ANSI_MAP_BULKDEREG, the IIF shall respond by sending an ANSI_MAP_bulkdereg in a
3 TCAP RETURN ERROR with one of the following error codes as defined in ANSI-41 [2]:
5 Appropriate Error Codes in ANSI_MAP_bulkdereg RETURN ERROR
Error Codes
ResourceShortage
SystemFailure
UnrecognizedParameterValue
3-18
X.S0023
1 4.2 Call Handing Procedures

2
3 Existing call handling procedures described in either GSM 09.02 [4] or ANSI-41 [2] are also
4 directly applicable to the Interworking and Interoperability Function (IIF) when it is emulating a
5 GSM or ANSI-41 functional network element.
7 4.2.1 Automatic Call Delivery

8

10
11 The Automatic Call Delivery procedure is invoked in the IIF, when a terminating call attempt
12 results in a request for routing information from the IIF.
13 The following procedures are applicable at the IIF for Automatic Call Delivery:
14 4.2.1.1.1 GSM Foreign Mode

15
16 If the IIF receives an ANSI MAP_RoutingRequest Invoke message from the ANSI-41 HLR, it
17 shall check if the terminating call can be placed to that subscriber. The IIF shall then deduce
18 the IMSI from the MSID for that subscriber and populate the corresponding field of the
19 MAP_PROVIDE_ROAMING_NUMBER message.
20 The IIF shall store the BillingID received in the ANSI MAP_RoutingRequest Invoke message to
21 later be able to populate the corresponding field in the ANSI MAP_RoutingRequest Return
22 Result message.
23 If the MobileDirectoryNumber field is present and in an international format in the

24 MAP_RoutingRequest Invoke message, the IIF shall populate the MSISDN field in the
25 MAP_PROVIDE_ROAMING_NUMBER message with it. If the MobileDirectoryNumber is in
26 National format, the IIF shall convert it to an International format before populating the MSISDN
27 field1.
28 The IIF shall then populate the MSC Number field in the
29 MAP_PROVIDE_ROAMING_NUMBER message with the serving MSC Number that had been
30 stored in the IIF at the time of the subscriber’s location registration.
31 The IIF shall then send the MAP_PROVIDE_ROAMING_NUMBER message to the GSM
32 MSC/VLR and wait for a response.
33 If the response indicates that the retrieval of routing information procedure has been
34 successful, the IIF shall deduce the MSRN from the MAP_PROVIDE_ROAMING_NUMBER
35 ack and populate the field Digits (Destination) in the MAP_RoutingRequest Return Result. The
1
As an alternative, the MSISDN may also be retrieved directly from the Subscriber profile,
pre-provisioned in the IIF.
3-19
X.S0023
1 IIF shall populate the BillingID field with the value of the BillingID received in the
2 RoutingRequest Invoke message.
3 The IIF shall then populate the MSCID (Serving) field with its own ID and forward it to the
4 ANSI-41 HLR.
5 If the response is unsuccessful, the IIF shall map any error code it receives to either an
6 AccessDeniedReason value in the MAP_RoutingRequest Return Result or to an Error Code in
7 a Return Error message.
8 For the cases of failure at the IIF on reception of the MAP_RoutingRequest Invoke message
9 (e.g. missing expected parameter, unknown subscriber), the procedures described in ANSI-41
10 [2] are also applicable to the IIF.
11 For the cases of failure at the IIF on reception of the PROVIDE_ROAMING_NUMBER

12 response, the procedures described in GSM 09.02 [4] for retrieval of routing information are
13 also applicable to the IIF.
14
15 4.2.1.1.2 ANSI-41 Foreign Mode

16 If the IIF receives a MAP_PROVIDE_ROAMING_NUMBER message from the GSM HLR, it
17 shall check if the terminating call can be placed to that subscriber.
18 If the IIF determines that the subscriber is Not Reachable, it shall send a
19 MAP_PROVIDE_ROAMING_NUMBER Response message with User Error field indicating
20 Absent Subscriber to the GSM HLR.
21 Otherwise, the IIF shall deduce the MSID and ESN from the IMSI and populate the
22 corresponding fields of the ANSI MAP_RoutingRequest Invoke.
23 The IIF shall create a billing ID for that transaction and populate the corresponding field of the
24 ANSI MAP_RoutingRequest Invoke.
25 The MSCID address field shall be set to the IIF address.
26 The IIF shall also assign a predefined value (vendor specific) to the SystemMyTypeCode field,
27 indicating the IIF vendor identity.
28 If the MSISDN field is present in the MAP_PROVIDE_ROAMING_NUMBER, the IIF shall

29 populate the MobileDirectoryNumber field in the RoutingRequest Invoke message with it1.
30 The IIF shall set the MSCIdentificationNumber and PC_SSN fields to its own ID.
31 The IIF shall then send the RoutingRequest Invoke message to the ANSI-41 MSC/VLR and
32 wait for a response.
33 If the response indicates that the retrieval of routing information procedure has been
34 successful, the IIF shall deduce the MSRN from the Digits (Destination) field of the
35 RoutingRequest Return Result and populate the MSRN field in the
36 MAP_PROVIDE_ROAMING_NUMBER ack. The MSRN shall have an E.164 format. Therefore,
37 if the TLDN is not in international format, the IIF shall add the country code digits associated
1
As an alternative, the MSISDN may also be retrieved directly from the Subscriber profile,
pre-provisioned in the IIF.
3-20
X.S0023
1 with the country of the serving system The IIF shall then forward the
2 MAP_PROVIDE_ROAMING_NUMBER ack to the GSM HLR.
3 If the response is unsuccessful, the IIF may receive a RoutingRequest Return Result with the
4 field AccessReasonDenied present, or a ReturnError message with an Error Code value. The
5 IIF shall map any Access Reason Denied or Error Code it receives to a User or Provider Error
6 in the MAP_PROVIDE_ROAMING_NUMBER return error.
7 For the cases of failure at the IIF on reception of the MAP_PROVIDE_ROAMING_NUMBER

8 request, (e.g. missing expected parameter, unidentified subscriber), the procedure described in
9 GSM 09.02 [4] for retrieval of routing information are applicable to the IIF.
10 For the cases of failure at the IIF on reception of the MAP_RoutingRequest Invoke message
11 return Result, the procedure described in ANSI-41 [2] for automatic call delivery is applicable to
12 the IIF.
13

15
16 4.2.1.2 presents the mapping of messages, parameters and parameter values that the IIF shall
17 perform. The mapping in the following tables is applicable to the generic Call delivery
18 scenarios. For mapping of parameters relevant to the Optimal Routing cases, refer to 4.2.3. For
19 mapping of parameters relevant to CLIP/CLIR refer to 4.3.4.
20

22
24 to Automatic Call Delivery regardless of the mode of operation (GSM Foreign Mode or ANSI-41
25 Foreign Mode)
26 Table 14: Automatic Call Delivery Message Mapping

GSM MAP Message ANSI-41 MAP Message
PROVIDE ROAMING NUMBER Routreq
REQUEST
PROVIDE ROAMING NUMBER routereq
REQUEST REPONSE
3-21
X.S0023

2 Table 15 and Table 16 show the mapping of parameters, which the IIF shall perform regardless
3 of the mode of operation (GSM Foreign Mode or ANSI-41 Foreign Mode).
4 Table 15: ROUTREQ  PROVIDE_ROAMING_NUMBER_REQUEST Parameter Mapping

ROUTREQ Status Provide Roaming Number Status
Request
BillingID (Originating) M -
ElectronicSerialNumber M -
MobileStationIDentity M IMSI M
MSCID (Originating MSC) M
SystemMyTypeCode (Originating M -
MSC)
AlertCode O -
CallingPartyNumberString1 O -
(Note 1)
CallingPartyNumberString2 O -
(Note 1)
CallingPartySubaddress O -
DestinationDigits O -
DMH_AccountCodeDigits O -
DMH_AlternateBillingDigits O -
DMH_BillingDigits O -
LegInformation O -
LocationAreaID O -
MobileDirectoryNumber R MSISDN R
(Note 2) (Note 3) (Note 4)
MSCIdentificationNumber R -
NoAnswerTime O -
OneTimeFeatureIndicator O -
PC_SSN (Originating MSC) R -
PilotBillingID O -
PilotNumber O -
RedirectingNumberString O -
RedirectingSubAddress O -
SenderIdentificationNumber O -
TerminationTreatment O -
5
3-22
X.S0023
1 Table 15: ROUTREQ  PROVIDE_ROAMING_NUMBER_REQUEST Parameter Mapping

2 (concluded)
ROUTREQ Status Provide Roaming Number Status

Request
TerminationTriggers O -
VoiceMailboxNumber O -
VoiceMailPIN O -
- MSC Number M
- LMSI U
- GMSC address R
(Note 5)
- GSM Bearer Capability C
- Network Signal Info C
- Suppression of C
Announcement
- Call Reference Number R
(Note 5)
- OR Interrogation C
- Alerting Pattern C
- CCBS Call C
CDMAService Option O GSM BearerServiceCode O (Note
6)
3
4 Note 1: For encoding of those parameters, refer to “4.3.4 Calling Number/Line Identification
5 Presentation/Restriction”.
6 Note 2: If present from the PRN request
7 Note 3: May also be directly retrieved from the subscriber profile pre-provisioned in the IIF.
8 Note 4: Only if the IIF requires it to be included in the call data record
9 Note 5: Only for Optimal Routing after late Call Forwarding
10 Note 6: Optional, if the network settings support data, a mapping may be performed as
11 described in Table 92
3-23
X.S0023
1 The following table shows the mapping of parameters between the Provide Roaming Number
2 Response and the Routing Request Return Result messages regardless of the mode of
3 operation (GSM Foreign Mode or ANSI-41 Foreign Mode).
4 Table 16: Provide Roaming Number Response  Routreq Return Result Parameter
5 Mapping
Provide Roaming Number ack Status Routreq Return Result Status
Roaming Number* M Digits (Destination) R
- MSCID (Serving) M
User Error* R R
(Note AccessDeniedReason (Note
1) 2)
- BillingID (Anchor) R
- ConditionallyDeniedReason O
- MSCIdentificationNumber R
- PC_SSN (Serving MSC) O
GSM Bearer Capability (Note 3) O CDMAServiceOption O
6
7 * These parameters are mutually exclusive
8 Note 1: If the request is unsuccessful.
9 Note 2: If User Error is present in Provide Roaming Number ack.
10 -Note 3: Optional, if the network settings support data, a mapping may be performed as
11 described in Table 92
12 Or
13 Table 17: PROVIDE_ROAMING_NUMBER_RESPONSE to Routreq Return Error Mapping

14 (ANSI-41Foreign Mode)
Provide Roaming Number ack Status RoutingRequest Return Status
Error
User Error C Error Code O
Provider Error C
15
16 For detailed mapping of User/Provider Error parameter value to the AccessDeniedReason

17 parameter, see Table 22 and Table 23.
18
3-24
X.S0023
1 Table 18: Routreq Return Error to Provide Roaming Number Response Error Mapping
2 (GSM Foreign mode)
Routing Request Return Error Status Provide Roaming Number Status
ack
Error Code O User Error C
3 4.2.1.2.2.1 Mapping of parameter values in GSM Foreign Mode

4 Default parameter value
5 Table 19 presents how the IIF shall populate the parameters of the Provide Roaming Number
6 message to be sent to the GSM VLR. These fields do not have an equivalent in the received
7 Routing Request Invoke message.
8 Table 19: Provide Roaming Number Request default parameter

Parameter Name Status Value
MSC Number M ISDN number of the serving MSC.
Stored in the IIF at the time of location
registration.
LMSI C Local Mobile Subscriber Identity. Shall
be present if the LMSI was sent to the
IIF at location updating
GSM Bearer Capability C Shall be absent
Network Signal Info C Shall be absent
Suppression of Announcement C CAMEL Specific Information Element
(IE)
Call Reference Number C Not required unless Optimal Routing
for LateCall Forwarding is supported
by the IIF.
GMSC address C Not required unless CAMEL or Optimal
Routing for Late Call Forwarding is
supported by the IIF (and if so, it shall
be set to the IIF address)
OR Interrogation C Not required to be sent by the IIF
(however may be received as a result
of Optimal Routing)
Alerting Pattern C CAMEL Specific Information Element
(IE)
CCBS Call C CCBS Specific IE
9
3-25
X.S0023
2 Table 20 presents how the IIF shall populate the parameters of the Routing Request Return
3 Result message to be sent to the ANSI-41 HLR. These fields cannot be mapped from the
4 received Provide Roaming Number response message.
5 Table 20: RoutingRequest Return Result default parameters

Parameter Name Status Default Value
MSCID (Serving) M Shall be set to the serving MSC
address
BillingID (Anchor) O When the IIF receives the Routing
Request Invoke message it shall
store the BillingID and use it to
populate this field.
AccessDeniedReason O See Table 24
ConditionallyDeniedReason O Shall be absent.
MSCIdentificationNumber O Shall be set to the serving MSC
address
PC_SSN (Serving MSC) O Shall be absent
CDMAServiceOption O If received in Invoke or from Profile
6
3-26
X.S0023
1 4.2.1.2.2.2 Mapping of parameter values in ANSI-41 Foreign Mode

3 Table 21 presents how the IIF shall populate the parameters of the Routing Request Invoke
4 message to be sent to the ANSI-41 VLR. These fields cannot be mapped from the received
5 Provide Roaming Number request message.
6 Table 21: Routing Request Invoke default parameter

ROUTEREQ Status Default Value
BillingID (Originating) M Shall be created by the IIF
ElectronicSerialNumber M Shall be deducted from the IMSI received
in the PRN request. For each subscriber
provisioned in the IIF, there must be a
table defining a correspondence between
IMSI on the one hand and MIN/ESN on
the other hand.
MSCID (Originating MSC) M Shall be set to the IIF address.
SystemMyTypeCode (IIF vendor Id)) M Assigned by the IIF
AlertCode O May be absent
CallingPartyNumberString1 O See Table 83 to Table 86
CallingPartyNumberString2 O See Table 83 to Table 86
CallingPartySubaddress O See Table 83 to Table 86
DestinationDigits O Shall be absent
DMH_AccountCodeDigits O Shall be absent
DMH_AlternateBillingDigits O Shall be absent
DMH_BillingDigits O Shall be absent
LegInformation O Shall be absent (not a multileg call)
LocationAreaID O Shall be absent
MSCIdentificationNumber O Shall be set to identify the IIF, as the
information may be required at a later
time by the ANSI VMSC to redirect the
call.
NoAnswerTime O Shall be absent
OneTimeFeatureIndicator O Shall be absent
PC_SSN (Originating MSC) O Shall be set to identify the IIF, as the
information may be required at a later
time by the ANSI VMSC to redirect the
call.
PilotBillingID O Shall be absent [multi leg call]
PilotNumber O Shall be absent [pilot directory number for
a multi-leg call]
7
3-27
X.S0023
1 Table 21: Routing Request Invoke default parameter (concluded)
ROUTEREQ Status Default Value

RedirectingNumberString O Shall be absent
RedirectingSubAddress O Shall be absent
SenderIdentificationNumber O Shall be absent
TerminationTreatment O Shall be absent or set to 1 (MS
Termination which is also the default
value)
TerminationTriggers O Shall be absent. Define the
treatment to apply (termination or
redirection)
VoiceMailboxNumber O Shall be absent
VoiceMailPIN O Shall be absent
CDMAServiceOption O From Profile or from Location
Request Invoke if received

3 The following tables present the appropriate GSM MSC/VLR negative response to a Provide
4 Roaming Number message as described in GSM 09.02 [4].
5 Appropriate User Error value:
User Error value
Absent Subscriber
No roaming Number available
Facility Not supported
System Failure
Data Missing
Unexpected Data Value
3-28
X.S0023
1 Appropriate Provider Error value:
Provider Error value
Duplicated Invoke ID
Not supported service
Mistyped parameter
Resource limitation
Initiating Release
Unexpected response from the peer
Service Completion Failure
No response from the peer
Invalid response received
3 The following tables present the appropriate ANSI-41 MSC/VLR negative response to a
4 Routing Request Invoke message as described in ANSI-41 [2].
6 Appropriate AccessDeniedReason parameter values in the RoutingRequest Return

7 Result:
AccessDeniedReason
Inactive
Busy
No page Response
Unavailable
3-29
X.S0023
1 Appropriate Error Code parameter value in the Return Error message:
Error Code value
UnrecognizedMIN
UnrecognizedESN
ResourceShortage
ParameterError (Note 1)
SystemFailure
MissingParameter
3 Note 1: The FaultyParameter field shall be present and populated with the appropriate Parameter
4 Identifier.

6
7 The IIF is responsible for the mapping of the User Error/Provider Error received in the Provide
8 Roaming Number response to the appropriate AccessDeniedReason in the RoutingRequest
9 Return Result message or Error Code in the Return Error.
10 The following tables present the preferred mapping.
11 Table 22: PRN response User Error to routreq Return Error Mapping
User Error value received in PRN AccessDeniedReason in routreq or Error
response Code in Return Error.
Absent Subscriber AccessDeniedReason to Unavailable
No roaming Number available Error Code to System Failure
Facility Not supported Error Code to System Failure
System Failure Error Code to System Failure
Data Missing Error Code to System Failure
Unexpected Data Value Error Code to System Failure
12
13
3-30
X.S0023
1 Table 23: PRN Response Provider Error to routereq Return Error Mapping
Provider Error value received in PRN Error Code value in Return Error
Confirm.
Duplicated Invoke ID System Failure
Not supported service System Failure
Mistyped parameter System Failure
Resource limitation System Failure
Initiating Release System Failure
Unexpected response from the peer System Failure
Service Completion Failure System Failure
No response from the peer System Failure
Invalid response received System Failure

3
4 The IIF is responsible for the mapping of the AccessDeniedReason received in the
5 RoutingRequest Return Result or Error Code received in the Return Error to the appropriate
6 User Error/Provider Error in the Provide Roaming Number response message.
7 The following tables present the preferred mapping.
8 Table 24: RoutingRequest Return Result to User Error in the PRN response Error
9 Mapping
AccessDeniedReason received in the User Error in the PRN response
RoutingRequest Return Result
Inactive Absent Subscriber
Busy Absent Subscriber
No page Response Absent Subscriber
Unavailable Absent Subscriber
10 Table 25: Routing Request Return Error to PRN User Error Mapping
Error Code value User Error in the PRN response
UnrecognizedMIN System Failure
UnrecognizedESN System Failure
ResourceShortage System Failure
OperationNotSupported System Failure
ParameterError System Failure
UnrecognizedParameterValue System Failure
SystemFailure System Failure
MissingParameter System Failure
3-31
X.S0023
1 4.2.2 Invocation of Conditional Call Forwarding in ANSI-41 Foreign Mode

2
3 Existing call forwarding procedures described in either GSM 09.02 [4] or ANSI-41 [2] are also
4 directly applicable to the IIF when it is emulating a GSM or ANSI-41 functional network element.
5 Enhancements and modifications to ANSI-41 [2] are also applicable.

7
8 4.2.2.1.1 Invocation of Call Forwarding before the call has been routed to the serving
9 MSC
10
11 The Call Forwarding procedure is invoked in the IIF when a terminating call attempt results in
12 an “unavailable” indication and the IIF is required to provide treatment for the “unavailable”
13 situation.
14 The following procedures are applicable at the IIF for Call Forwarding invocation:
15 If the IIF receives an ANSI_MAP_routreq indicating ‘access denied’, the IIF shall determine if
16 call forwarding is applicable for the call.
17 If call forwarding is applicable for the call, the IIF shall send a GSM MAP _PROVIDE
18 ROAMING_NUMBER_RESPONSE to the HLR.
19 The IIF shall process the forwarding request in one of the following two optional methods:
20 • Send the Forward_To_Number that corresponds to the access denied reason (stored
21 for the subscriber in the IIF). Refer to Table 26 or,
22 • Send a user error indicating “Absent Subscriber”. Refer to Table 27.
23 If call forwarding is not applicable for the call, the IIF shall follow the procedures outlined in
24 4.2.1 of this document
25 If the IIF receives an ANSI_MAP routreq Return Error or a Reject message, the IIF shall map
26 the Error Code it receives to a suitable User Error in the
27 MAP_PROVIDE_ROAMING_NUMBER RESPONSE as described in 4.2.1 of this document
28 For the cases of failure at the IIF on reception of the MAP_RoutingRequest Return Result, the
29 procedure described in ANSI-41 [2] for automatic call delivery is applicable to the IIF.
3-32
X.S0023
1 4.2.2.1.2 Invocation of Call Forwarding after the call has been routed to the serving
2 MSC
3
4 If the called party is either busy, not reachable or does not answer the call, the serving MSC
5 may redirect the call by sending REDREQ to the IIF, indicating the reason for failure.
6 If the IIF receives an ANSI_MAP_REDREQ, it shall determine if the message can be

7 processed:
8  If the message can be processed and optimal routing is supported, the IIF shall follow
9 the procedures outlined in 4.2.3 of this document for Optimal Routing for late call
10 forwarding.
11  If the message can be processed but optimal routing is not supported, the IIF shall
12 send an ANSI_MAP_redreq Reject message. On receipt of the Reject message, the
13 serving MSC may attempt to redirect the call by sending a TRANUMREQ message to
14 the IIF.
15  If the message cannot be processed, the IIF shall send an ANSI_MAP redreq Return
16 Reject message with the appropriate error code. On receipt of the Return Reject
17 message, the serving MSC may attempt to redirect the call by sending a TRANUMREQ
18 message to the IIF.
19  If the IIF receives an ANSI_MAP_TRANUMREQ, it shall determine if the message can

20 be processed.
21  If the message can be processed, the IIF shall send an ANSI_MAP_tranumreq

22 indicating the forwarded-to-number.
23 If the message cannot be processed, the IIF shall send an ANSI_MAP tranumreq indicating the
24 reason for failure.
25

27
28 4.2.2.2 presents the mapping of messages, parameters and parameter values that the IIF shall
29 perform.

31
32 These messages are the same as those in 4.2.1.2.1.
33
3-33
X.S0023

2
3 Table 26 represents how the IIF shall map the value of the parameter it has received to
4 populate the fields of the message it shall transmit.
5 Table 26: ROUTEREQ Return Result to Provide Roaming Number Response parameter
6 mapping (Option 1)
Routing Request Return Result Status Provide Roaming Number ack. Status
AccessDeniedReason = Busy, O Roaming Number C
Inactive, No Page Response or
Unavailable
7
9 Table 27: ROUTREQ Return Result to Provide Roaming Number Response Parameter
10 Mapping (Option 2)
Return Error Status Provide Roaming Number ack Status
AccessDeniedReason = Busy, O User Error = Absent Subscriber C
Inactive, No Page Response or
Unavailable
11
12 Default parameters value
13 N/A

15
16 The following table presents the appropriate GSM MSC/VLR negative response to a Provide
17 Roaming Number message as described in GSM 09.02 [4].
User Error value
Absent Subscriber
No roaming Number available
Facility Not supported
System Failure
Data Missing
19
3-34
X.S0023
Mistyped parameter
Resource limitation
Initiating Release
3 The following table presents the appropriate ANSI-41 MSC/VLR negative response to a
4 Routing Request Invoke message as described in in ANSI-41 [2].
5 Appropriate AccessDeniedReason parameter values in the RoutingRequest Return Result:
AccessDeniedReason
Inactive
Busy
No page Response
Unavailable
Error Code value
UnrecognizedESN
ResourceShortage
ParameterError*
UnrecognizedParameterValue*
SystemFailure
MissingParameter*
3-35
X.S0023
2 Table 28: Return Error to User Error in the PRN response Error Mapping
Error Code value User Error
3 4.2.3 Optimal Routing after Late Call Forwarding

4
5 An optimal routing for late call forwarding procedure covers the interoperability between
6 ANSI-41 and GSM MAP signaling to support Optimal Routing after Late Call Forwarding. This
7 signaling is based on ANSI-41 [2] and GSM 09.02 [4].
8 From GSM 03.79 [32], a Late Call Forwarding procedure is defined as Call Forwarding
9 performed after the call has been extended to the Visited PLMN (VPLMN) of the forwarding
10 subscriber. This forwarding is based on subscription of supplementary services like Conditional
11 Call Forwarding on Busy, Conditional Call Forwarding on No Reply, and Conditional Call
12 Forwarding on Not Reachable detected in the VPLMN of the forwarding subscriber. Note that
13 the Late Call Forwarding procedure may be invoked in the Interrogating PLMN (IPLMN) or in
14 the VPLMN of the forwarding subscriber.
15 The procedure is applicable when the Subscriber has appropriate forwarding service active;
16 and Optimal Routing is enabled.
17

19
20 Roaming may occur either from ANSI-41 to GSM network or vice versa. Since the solutions and
21 ultimate functionality provided to the roaming subscriber are not symmetrical, the Optimal
22 Routing for Late Call Forwarding procedure is different in both cases. 4.2.3.1 defines roaming
23 procedures when roaming from GSM to ANSI-41 network and roaming from ANSI-41 to GSM
24 network respectively.
25
3-36
X.S0023

2
3 When the IIF receives a GSM-Provide Roaming Number message, it stores GMSC Address,
4 Call Reference Number and OR Interrogation Indicator parameters if they are present. It then
5 sends an ANSI-41Routing Request message to the VLR and awaits a response.
6 If successful ANSI-41 Routing Request response is received from VLR, it converts Temporary
7 Location Directory Number (TLDN) in to Mobile Subscriber Roaming Number (MSRN) and send
8 this information to HLR in GSM-Provide Roaming Number Acknowledge message.
9 Otherwise, the IIF sends a GSM-Provide Roaming Number negative response to HLR and
10 discards GMSC Address, Call Reference Number and OR Interrogation Indicator parameter
11 information if present.
12 If the IIF receives ANSI-41 Redirection Request message, it shall check GMSC Address.
13 If GMSC Address is available, it shall map Redirection Reason parameter to Forwarding

14 Reason. The IIF sends this information in addition to the Call Reference Number and
15 Forwarding Number in GSM-Resume Call Handling message to originating MSC using GMSC
16 Address and await a response.
17 Otherwise, the IIF rejects the ANSI-41 Redirection Request.
18 If the IIF receives GSM-Resume Call Handling Acknowledge message, it sends response of
19 ANSI-41- Redirection Request message to the MSC. Otherwise, if negative response of GSM-
20 Resume Call Handling is received, the IIF shall send ANSI-41-Redreq Return Error with an
21 appropriate error code to the MSC.

23
24 When the IIF receives an ANSI-41-Routing Request message, it stores Originating MSC ID,
25 TERMTRMT if present. The IIF then generates a Call Reference Number and sends it as a
26 parameter in the a GSM-Provide Roaming Number message to the VLR along with the GMSC
27 address set to the IIF address and along with the GMSC address set to the IIF address awaits
28 a response.
29 If successful GSM-Provide Roaming Number Acknowledge is received from VLR, it converts

30 MSRN to TLDN and sends this information to HLR in ANSI-41-Routing Request response
31 message.
32 Otherwise, the IIF sends an ANSI-41- Routing Request negative response (routreq) to HLR and
33 discards information of Originating MSCID and TERMTRMT (if present).
34 If the IIF receives GSM-Resume Call Handling, it shall use its Call Reference Number
35 parameter to corelate and determine the ANSI-41 originating MSC, and the IIF shall map the
36 Forwarding Reason parameter to Redirection Reason. The IIF sends this information to the
37 originating MSC in the ANSI-41-Redirection Request message and awaits a response.
38 If the IIF receives ANSI-41-Redirection Request response message, it sends a GSM-Resume

39 Call Handling Acknowledge message to the MSC. Otherwise, if negative response is received
3-37
X.S0023
1 (in form of return error), the IIF shall send GSM-Resume Call Handling Return Error with an
2 appropriate error code to the MSC.
3 The IIF shall perform the translation of messages, parameters and parameter values related to
4 Optimal Routing Support for Late Call Forwarding procedure in accordance with the tables
5 presented here. Refer to GSM 03.18 [31] and GSM 03.79 [32] and ANSI-41 [2] for a description
6 of messages, parameters and parameter values.

8
10
11 Table 29 shows the translation between GSM MAP messages and ANSI-41 MAP messages
12 related to Optimal Routing Support for Late Call Forwarding procedure.
13 Table 29: Optimal Routing for Late Call Forwarding Message Mapping
GSM-Provide Roaming Number Request ROUTEREQ
GSM- Provide Roaming Number routereq
Acknowledge
GSM-Resume Call Handling REDREQ
GSM-Resume Call Handling Acknowledge redreq
14
3-38
X.S0023

2
3 The following tables show the mapping of parameters, which the IIF shall perform regardless of
4 the mode of operation.
5 Table 30: GSM Provide_Roaming_Number  ANSI-41 ROUTEREQ Parameter Mapping
GSM Provide_Roaming_Number Status ANSI-41-Route_Request Status

(ROUTEREQ)
IMSI M MSID M
ESN M
MSC Number M -
MSISDN (Note 1) R MDN R
LMSI O -
GSM Bearer Capability C -
ISDN BC C -
ISDN LLC C -
ISDN HLC C -
Alerting Pattern C -
GMSC Address (Note 2) R -
Call Reference Number R -
OR Interrogation Indicator C -
- Billing ID M
- System My Type Code M
- PC_SSN R
- LocationAreaID O
- TERMTRMT O
- TERMTRIG O
- LEGINFO O
- OTFI O
CNIinfoASCII:
- CallingPartyNumber-String 1 O
- CallingPartyNumber- String 2 O
- Redirecting Number O
- Calling Party Subaddress O
- Redirecting Subaddress O
3-39
X.S0023
2 Table 30: GSM Provide_Roaming_Number  ANSI-41 ROUTEREQ Parameter Mapping

3 (concluded)
GSM Provide_Roaming_Number Status ANSI-41-Route_Request Status

(ROUTEREQ)
DMHData:
- DMH AccountCodeDigits O
- DMH AlternateBillingDigits O
- DMH_BillingDigits O
- MobileDirectoryNumber O
- VMSPIN O
- VMBOX O
5 Note 1: Alternatively a provisioning number may be mapped to the MDN.
6 Note 2: The GMSC Address is used by the IIF to route information to the originating MSC.
7 Table 31: Mapping of Parameter values

IMSI MSID See Automatic Call Delivery
ESN See Automatic Call Delivery
MSISDN MDN See Automatic Call Delivery
Billing ID See Automatic Call Delivery
MSCID See Automatic Call Delivery
8
9 Table 32: Provide_Roaming_Number_Response  routereq Parameter Mapping

Provide_Roaming_Number_Res Status ANSI-41 Route_Request Status
ponse (routereq)
Roaming Number M TLDN [DGTSDEST] M
- MSCID M
- BILLID M
User Error C ACCDEN (Note 1) M
- PC_SSN R
10
11 Note 1: Used only with the negative response of ANSI-41-Routing Request message.
12
3-40
X.S0023
1 Table 33: Mapping of Parameter Values

Roaming Number TLDN See Automatic Call Delivery
MSCID See Automatic Call Delivery
BILLID See Automatic Call Delivery
User Error ACCDEN See Automatic Call Delivery
2
4 Table 34: Resume_Call_Handling  REDREQ Parameter Mapping

GSM Resume_Call_Handling Status ANSI-41 Redirection_Request Status
(REDREQ)
Call Reference Number M -
Basic Service group M -

IMSI M MSID M
ESN M
ForwardingData:
Forwarding Reason M REDREASON M
Forwarded-to-Number M -
Notification to Calling Party M -
Forwarded-to-Subaddress C -
CUG Interlock C -
CUG Outgoing Access C -
Originating CSI C -
- BILLID M
- LEGINFO O
5
6 Table 35: Mapping of Parameters Values

IMSI MSID See Automatic Call Delivery
MSN See Automatic Call Delivery
Forwarding REDREASON See below
Reason
BILLID See Automatic Call Delivery
7
8 Table 36: Resume_Call_Handling_Response  redreq Parameter Mapping

Resume_Call_Handling_Respon Status Redirection_Request (redreq) Status
se
- -
3-41
X.S0023
1 4.2.3.2.3 Mapping ANSI-41 Redirection_Reason and GSM Forwarding Reason for

4 Table 37: ANSI-41 Redirection_Reason to GSM Forwarding_Reason

Redirection_Reason Forwarding_Reason
Busy Call Forwarding Busy
No Answer Call Forwarding No Reply
No Page Response Call Forwarding Not Reachable
Call Accepted (Note1, Note2) -
Unavailable Call Forwarding Not Reachable
Unroutable Call Forwarding Not Reachable
Call Refused (Note2) -
5
6 Notes:
7 1. The "Call Accepted" redirection reason shall not be received from the terminating ANSI-41
8 MSC in ANSI-41-Redirection Request. Hence the mapping of this value may not be
9 applicable.
10 2. These Redirection Reasons do not map to any existing GSM Forwarding Reasons. As a
11 result, if the IIF receives an ANSI-41-Redirection Request message with one of these
12 Redirection Reasons, it shall reject the request. Hence the mapping of this value may not
13 be applicable.
14
15 4.2.3.2.4 Mapping Forwarding Reason to Redirection Reason for GSM Foreign Mode
16
17 Table 38: GSM Forwarding_Reason to ANSI-41 Redirection_Reason

Forwarding_Reason Redirectionion_Reason
Call Forwarding Busy Busy
Call Forwarding No Reply No Answer
Call Forwarding Not Reachable No Page Response OR Unavailable
18
3-42
X.S0023

3
4 Negative Response of GSM-Provide Roaming Number
5 The serving MSC determines that it is unable to provide a routing number and returns this
6 indication to the IIF via a GSM Provide Roaming Number RETURN ERROR component with an
7 error code.
8 Negative Response of GSM-Resume Call Handling
9 The Originating MSC determines that it is unable to redirect the call and returns this indication
10 to the IIF via a GSM Resume Call Handling RETURN ERROR component with an error code.
11 Negative Response of ANSI-41-Routing Request (ROUTEREQ)
12 If TERMTRMT (TerminationTreatment) indicates termination to an MS, the Serving MSC

13 consults its internal data structures to determine if the MS is already engaged in a call on this
14 MSC. If termination is to a voice mailbox, the Serving MSC verifies the VMS availability. Finding
15 the MS or VMS busy (or otherwise unable to receive calls), the Serving MSC returns an
16 appropriate indication to the IIF in the ANSI-41 Routing Request response message (routreq).
17 Parameters included are MSCID and ACCDEN. The IIF then forwards the response of ANSI-41
18 Routing Request message to the HLR.
19 Negative Response of ANSI-41-Redirection Request (REDREQ)
20 The Originating MSC determines that it is unable to redirect the call and returns this indication
21 to the Serving MSC via an ANSI-41-Redirection Request RETURN ERROR component with an
22 error code.
23 4.2.3.3.1 Error Code Mapping

24
25 Table 39: Provide_Roaming_Number to Routing_Request Error Mapping

Provide_Roaming_Number User and Routing_Request Error Codes
Provider Errors
OR not allowed (Note 1) -
26
27 Note 1: If 'OR not allowed' is returned, the IIF should retry the Provide_Roaming_Number
28 operation without the OR indication to allow for normal routing
29
30 For other error mappings see Automatic Call Delivery, Error Handling, GSM Foreign Mode.
31 Table 40: Routing_Request to Provide_Roaming_Number Error Mapping

Routing_Request Error Codes Provide_Roaming_Number User Errors
- -
32
3-43
X.S0023
1 For error mappings see Automatic Call Delivery, Error Handling, ANSI-41 Foreign Mode.
3 Table 41: Resume_Call_Handling to Redirection_Request Error Mapping

Resume_Call_Handling Redirection_Request
User and Provider Errors Error Codes
OR not allowed (Note 1) SystemFailure
Forwarding failed SystemFailure
Duplicated Invoke ID SystemFailure
Not Supported Service System Failure
Mistyped Parameter System Failure
Resource Limitation System Failure
Initiating Release SystemFailure
Unexpected Response From the Peer SystemFailure
Service Completion Failure SystemFailure
No Response from the Peer SystemFailure
Invalid Response Received SystemFailure
4
5 Note 1: This error should not occur. The process requires the GMSC support OR.
7 Table 42: Redirection_Request to Resume_Call_Handling Error Mapping

Redirection_Request Resume_Call_Handling
Error Codes User Errors
MissingParameter OR-NotAllowed
UnrecognizedParameterValue OR-NotAllowed
UnrecognizedMIN OR-NotAllowed
UnrecognizedESN OR-NotAllowed
MIN/HLRMismatch OR-NotAllowed
OperationSequenceProblem OR-NotAllowed
TrunkUnavailable OR-NotAllowed
SystemFailure OR-NotAllowed
FeatureInactive OR-NotAllowed
ParameterError OR-NotAllowed
OperationNotSupported OR-NotAllowed
ResourceShortage OR-NotAllowed
8
3-44
X.S0023
2 4.3 Supplementary Services Procedures

3
4 4.3.1 SS Activation and Deactivation

5
6 Because of the similarities in the procedures and signaling between the supplementary service
7 activation and deactivation cases, these are combined into one description. Furthermore, 4.3.1
8 makes use of terms such as "Activate/Deactivate" or
9 "MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS". In all cases in which such terms are used, for
10 activation cases the terms "Activate" or "MAP_ACTIVATE_SS" terms apply. For deactivation
11 cases, the terms "Deactivate" or "MAP_DEACTIVATE_SS" apply.
12

14
15 4.3.1.1 contains the procedures in the IIF for the case in which the subscriber requests either
16 an activation or deactivation of one of the following supplementary services while roaming in
17 foreign mode (i.e., while roaming in a network of a technology different from that of its home
18 network):
19
20 • Call Waiting (in both GSM and ANSI-41 foreign modes)
21 • Call Forwarding Unconditional (in both GSM and ANSI-41 foreign modes)
22 • Call Forwarding Busy (in both GSM and ANSI-41 foreign modes)
23 • Call Forwarding No Reply (in ANSI-41 foreign-mode only)
24 • Call Forwarding Not Reachable (in ANSI-41 foreign-mode only)
25 • Call Forwarding No Answer (in GSM foreign-mode only)
26

28
29 While in GSM Foreign Mode, the principal role of the IIF, with respect to supplementary service
30 activation and deactivation, is that of handling the GSM MAP_ACTIVATE_SS message (for
31 activation) or the GSM MAP_DEACTIVATE_SS message (for deactivation), as follows: If the
32 IIF receives an GSM MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS message from the GSM
33 serving system, it shall verify the correct format and content of the message as described in
34 GSM 09.02 [4].
35 For cases in which the received message contains a "Basic service" parameter, the IIF shall
36 also verify that the request for activation/deactivation applies to (at least) speech. If the
37 received request does not include "speech" as one of the services to which the request applies,
3-45
X.S0023
1 the IIF shall respond with either a GSM MAP_ACTIVATE_SS or GSM MAP_DEACTIVATE_SS
2 Response message that includes a "User error" parameter with a value of "Illegal SS
3 operation". Note that cases in which no "Basic service" parameter is included in the received
4 message are acceptable, since, by default, no "Basic service" parameter indicates that the
5 request applies to all services.
6 If the format and content of the message is correct, the IIF shall determine the location of the
7 subscriber’s HLR and send to it an ANSI-41 FeatureRequest INVOKE message populated as
8 described in Table 44 and Table 48. If a failure occurs at the IIF on reception of the GSM
9 MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS message (e.g. missing data), the procedures
10 described in GSM 09.02 [4] are applicable to the IIF.
11 If, in response to the ANSI-41 FeatureRequest INVOKE, the IIF receives an ANSI-41
12 FeatureRequest Return Result message with a FeatureResult parameter set to successful, the
13 IIF shall send a GSM MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS Response message back
14 towards the serving system populated as described in Table 45.
15 If, in response to the ANSI-41 FeatureRequest INVOKE, the IIF instead receives an ANSI-41
16 FeatureRequest Return Result message with a FeatureResult parameter set to unsuccessful,
17 the IIF shall send a GSM MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS Response message
18 back towards the serving system populated as described in Table 45 and Table 53.
20 FeatureRequest Return Error message, the IIF shall send a GSM MAP_ACTIVATE_SS/
21 MAP_DEACTIVATE_SS Response message back towards the serving system populated as
22 described in Table 54.
23 Note that successful supplementary service activation/deactivation cases in GSM foreign mode
24 may result in the subscriber's ANSI-41 HLR sending out an ANSI-41 QUALDIR message to the
25 serving system. For these cases, the IIF would need to map the message to a GSM MAP
26 Insert Subscriber Data message. The mapping of an ANSI-41 QUALDIR message to a GSM
27 MAP Insert Subscriber Data message is covered in the Subscriber Data Management.

29
30 While in ANSI-41 Foreign Mode, the principal role of the IIF, with respect to supplementary
31 service activation, is that of handling the ANSI-41 FeatureRequest INVOKE message, as
32 follows: If the IIF receives an ANSI-41 FeatureRequest INVOKE message from the ANSI-41
34 ANSI-41 [2].
35 If format and content of the message is correct, the IIF shall determine the location of the
36 subscriber’s HLR and send a GSM MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS Request
37 message populated as described in Table 44 and Table 50.
38 For cases in which the FeatureRequest INVOKE message includes a feature code
39 corresponding to Call Forwarding No Answer, and if the IIF is configured to do so, the IIF may
40 send two MAP_ACTIVATE_SS/ MAP_DEACTIVATE_SS messages, one indicating Call
41 Forwarding No Reply and the other indicating Call Forwarding Not Reachable. These messages
42 may be sent in parallel. The mapping in Table 44 and Table 50 would still be applicable.
43
3-46
X.S0023
1 For the cases of failure at the IIF on reception of the ANSI-41 FeatureRequest Return Result
2 message (e.g. parameter error, unrecognized subscriber), the procedures described in
3 ANSI-41 [2] are applicable to the IIF.
4 If, in response to the a GSM MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS message, the IIF

5 receives a GSM MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS Response message with neither
6 a User Error nor Provider Error parameter, the IIF shall send an ANSI-41 FeatureRequest
7 Return Result message back towards the serving system populated as described in Table 45.
8 For those cases in which two requests had been previously sent by the IIF, the IIF would wait
9 until receiving the responses to both requests before sending the FeatureRequest Return Result
10 message. For cases in which both responses indicate success, the mapping in Table 45 may be
11 applied to either of the responses (as an IIF implementation option). For cases in which one of
12 the responses indicates success and the other failure, the mapping in Table 45 applies to the
13 successful response.
14 If, in response to the GSM MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS message, the IIF

15 instead receives a GSM MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS Response message
16 with a User Error, the IIF shall send either an ANSI-41 FeatureRequest Return Result
17 populated as described in Table 55 or a Return Error populated as described in Table 56. If a
18 Provider Error parameter is included in the received GSM
19 MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS Response message, the IIF shall send an
20 ANSI-41 FeatureRequest Return Error message populated with an Error Code as shown in
21 Table 57.
22 For cases in which two requests had been previously sent by the IIF, and both responses
23 indicate failure, the mapping described in Table 55 or Table 56 may be applied to either of the
24 responses (as an IIF implementation option).
25 Note that successful supplementary service activation/deactivation cases in ANSI-41 foreign

26 mode may result in the subscriber's GSM HLR sending out a GSM MAP Insert Subscriber Data
27 message to the serving system. For these cases, the IIF would need to map the message to
28 an ANSI-41 QUALDIR message. The mapping of GSM MAP Insert Subscriber Data message
29 to an ANSI-41 QUALDIR message is covered in the Subscriber Data Management.

31

33 The following table shows the mapping of messages for the Activation and Deactivation of
34 Supplementary Services.
35 Table 43: Supplementary Service Activation and Deactivation Message Mapping

Activate SS Request FEATREQ
Deactivate SS Request FEATREQ
Activate SS Request Response featreq
Deactivate SS Request Response featreq
3-47
X.S0023
1 4.3.1.2.2 Mapping of parameters

2 The following tables show the mapping between the parameters in GSM MAP messages and
3 parameters in the corresponding ANSI-41 messages. The relationships between the
4 parameters shown in the tables are meant to be bi-directional.
5 Table 44: Activate/Deactivate SS Request  FEATREQ Parameter Mapping

Activate/Deactivate SS Request Status FEATREQ Status
SS-Code M Digits (Dialed) M
Basic services C -
- ElectronicSerialNumber M
- MSID (Either MIN or IMSI) M
- BillingID (Originating) O
- CallingPartyNumberString1 O
- CallingPartySubaddress O
- ConferenceCallingIndicator O
- MSCID (Serving) O
- OneTimeFeatureIndicator O
- PC_SSN O
3-48
X.S0023
1 Table 45: Activate/Deactivate SS Response  Feature Request Return Result Parameter

2 Mapping
Activate/Deactivate SS Status Feature Request Return Result Status
Response
Call forwarding information C -
Call barring information C -
SS-Data C -
- FeatureResult (Note1) M
User Error C Announcement List O
Provider Error O -
- ActionCode O
- Access Denied Reason O
- CarrierDigits O
- Digits (Dialed) O
- DMH_AccountCodeDigits O
- DMH_AlternateBillingDigits O
- DMH_RedirectionIndicator O
- GroupInformation O
- NoAnswerTime O
- PACAIndicator O
- PilotNumber O
- RedirectingNumberDigits O
- RedirectingNumberString O
- RedirectingSubaddress O
- RoutingDigits O
- TerminationList O
- TerminationTriggers O
3
4 Note 1: The FeatureResult parameter shall be mapped to “Unsuccessful” if a User Error or a

5 Provider Error is received in the ACTIVATE/DEACTIVATE SS RESPONSE. Or, a User Error
6 mapped to an appropriate value shall be returned if the FeatureResult parameter is set to
7 “Unsuccessful”. See Table 53
3-49
X.S0023
2 Table 46: Activate/Deactivate SS Response  Feature Request Return Error Mapping

Activate/Deactivate SS Status Return Error Status
Response
Call forwarding information C
Call barring information C
SS-Data C
Provider Error O
- Faulty Parameter O
3
4 4.3.1.2.2.1 Mapping of parameter values in GSM Foreign Mode

5
6 Activate/Deactivate SS Request to Feature Request Invoke mapping
8 This table represents how the IIF shall map the value of the parameter it has received to
10 Table 47: Activate/Deactivate SS Request to FEATREQ Parameter Mapping

This parameter shall consist of
an ANSI-41 feature code. The
IIF shall support a table mapping
GSM supplementary service
operations (e.g. CFB activation)
to ANSI-41 feature codes.
11
12 Note that no parameter in the FeatureRequest INVOKE message currently supports the
13 mapping from the GSM MAP parameter "Basic service". The "GSM Foreign Mode" part of
14 4.3.2 SS Registration and Erasure contains procedures pertaining to the handling of the "Basic
15 service" parameter, when included in the received GSM MAP message.
3-50
X.S0023
2 Default parameter values
3 This table presents how the IIF shall populate the parameters of the Feature Request Invoke
5 Activate/Deactivate SS request message.
6 Table 48: FEATREQ default parameter

FEATREQ Status Default Value
ElectronicSerialNumber M Shall be derived from IMSI information
previously received during GSM
MAP_OPEN procedures.
MSID (Either MIN or IMSI) M Shall be obtained from mapping from the
IMSI received previously (during GSM
MAP_OPEN procedures)
BillingID (Originating) O Not required to be included in message.
CallingPartyNumberString1 O Not required to be included in message.
CallingPartySubaddress O Not required to be included in message.
ConferenceCallingIndicator O Not required to be included in message.
MobileDirectoryNumber O May be optionally included in message
from IIF’s data.
MSCID (Serving) O May be included from IIF internal data. It is
recommended that it be set to the same
unique ID used during registration to
identify serving MSC.
MSCIdentificationNumber O May be included from IIF data.
OneTimeFeatureIndicator O Not required to be included in message.
PC_SSN O May be included from IIF data.
SenderIdentificationNumber O May be included from IIF data.
TransactionCapability O If included, it shall be populated based on
IIF’s MAP interworking capabilities.
7
8 Feature Request Return Result to Activate/Deactivate SS Response mapping
9 Mapping of parameter values
10 For the successful case (in which a FeatureRequest Return Result is received with the
11 FeatureResult parameter set to “successful”) there are no meaningful parameter mappings to
12 support. For those successful cases, the “Default parameter values” describes how the
13 corresponding GSM Activate/Deactivate SS Response message shall be populated. For the
14 unsuccessful cases, 4.3.1.3 Error Handling describes the appropriate mappings.
3-51
X.S0023
2 This table describes the population of the parameters in the Activate/Deactivate SS Response
3 message for successful activation/deactivation cases (i.e. when the received Feature Request
4 Return Result contains a FeatureResult parameter set to “successful”).
5 Table 49: Activate/Deactivate SS Response default parameter values

Activate/Deactivate SS Status Default Value
Response
Call forwarding information C Included for cases in which activation
request concerned one of the call
forwarding features, based on stored
information in IIF. SS-Code portion of
parameter equal to that in the
Activate/Deactivate SS request, and with
A-bit of SS-Status portion within this
parameter set to either “1” (for activation
case) or "0" (for deactivation case). Other
bits in field are set to reflect current status
of subscriber's profile.
Call barring information C Subscriber activation/deactivation of call
barring services not required to be
supported by IIF, thus population of this
parameter not required.
SS-Data C Included for cases in which activation
request concerned Call Waiting, based on
stored information in IIF. SS-Code portion
of parameter equal to Call Waiting, and
with A-bit of SS-Status portion within this
parameter set to either “1” (for activation
case) or "0" (for deactivation case). Other
bits in field are set to reflect current status
of subscriber's profile.
6
3-52
X.S0023
1 4.3.1.2.2.2 Mapping of parameter values in ANSI-41 Foreign Mode

2
3 Feature Request Invoke to Activate/Deactivate SS Request mapping
6 Table 50: Feature Request Invoke to Activate/Deactivate SS Request Parameter Mapping

FEATREQ Status Activate/Deactivate SS Request Status
Digits (Dialed) M SS-Code M
The IIF shall support a table
mapping ANSI-41 feature codes
to GSM supplementary service
operations.
7
9 Table 51 presents how the IIF shall populate the parameters of the Activate/Deactivate SS
10 Request message to be sent to the GSM HLR. These fields do not have an equivalent in the
11 received Feature Request Invoke message.
12 Table 51: Activate/Deactivate SS Request default parameter

Basic services C Not required to be included.
(Activation/deactivation operation shall
apply to all service groups when absent.)
13
14 GSM Activate/Deactivate SS Response to ANSI-41 Feature Request Return Result

15 mapping
17 For the successful case (in which there’s no User error or Provider Error in the received GSM
18 Activate/Deactivate SS Response message), there are no meaningful parameter mappings to
20 corresponding ANSI-41 FeatureRequest Return Result shall be populated. For the
21 unsuccessful cases, Table 46 describes the appropriate mappings.
3-53
X.S0023
3 Table 52 presents how the IIF shall populate the parameters of the Feature Request Return
4 Result message to be sent to the ANSI-41 VLR for successful activation cases. Note that the
5 population of the message may differ for non-activation cases.
6 Table 52: FeatureRequest Return Result default parameter

FeatureResult M Set to “successful”
AccessDeniedReason O Not required to be included.
ActionCode O Not required to be included.
AnnouncementList O Not required to be included.
CallingPartyNumberString1 O Not required to be included.
CallingPartySubaddress O Not required to be included.
CarrierDigits O Not required to be included.
ConferenceCallingIndicator O Not required to be included.
Digits (Dialed) O Not required to be included.
DMH_AccountCodeDigits O Not required to be included.
DMH_AlternateBillingDigits O Not required to be included.
DMH_BillingDigits O Not required to be included.
DMH_RedirectionIndicator O Not required to be included.
GroupInformation O Not required to be included.
MobileDirectoryNumber O Not required to be included.
NoAnswerTime O Not required to be included.
OneTimeFeatureIndicator O Not required to be included.
PACAIndicator O Not required to be included.
PilotNumber O Not required to be included.
RedirectingNumberDigits O Not required to be included.
RedirectingNumberString O Not required to be included.
RedirectingSubaddress O Not required to be included.
RoutingDigits O Not required to be included.
TerminationList O Not required to be included.
TerminationTriggers O Not required to be included.
7
3-54
X.S0023

2
3 The following table presents the appropriate GSM MSC/VLR negative response to an
4 Activate/Deactivate SS message as described in GSM 09.02 [4].
User Error value
System Failure
Data Missing
Bearer service not provisioned
Teleservice not provisioned
Call Barred
Illegal SS operation
SS error status
SS subscription violation
SS incompatibility (Activation case only)
Negative PW check
Number of PW Attempts Violation
Mistyped parameter
Resource limitation
Initiating Release
9
3-55
X.S0023
1 The following table presents the appropriate ANSI-41 MSC/VLR negative response to a
2 Feature Request Invoke message as described in ANSI-41 [2].
3 Appropriate AccessDeniedReason parameter values in the FeatureRequest Return Result

4 (Note, however, that none of these values are applicable to the feature activation scenarios):
AccessDeniedReason
Unassigned directory number
Inactive
Busy
No page Response
Unavailable
TerminationDenied
Error Code value
UnrecognizedMIN
UnrecognizedESN
MIN/HLRMismatch
OperationSequenceProblem
ResourceShortage
ParameterError
SystemFailure
3-56
X.S0023

3
4 For cases in which a FeatureRequest Return Result is received by the IIF with a FeatureResult
5 parameter set to “unsuccessful”, if the AnnouncementList parameter is also present, the IIF
6 may use the contents of the AnnouncementList in order to provide a better mapping to the User
7 Error in the Activate/Deactivate SS Response message, as shown in Table 53:
9 Table 53: FeatureRequest Return Result to User Error in the Activate/Deactivate SS

10 Response Error Mapping
FeatureRequest Return Result Activate/Deactivate SS Response
FeatureResult ="unsuccessful" User Error = "SS subscription violation"
AnnouncementList="UnauthorizedFeature Or
Code" User Error = “Illegal SS Operation”
FeatureResult ="unsuccessful" User Error="System Failure"
AnnouncementList not present
11
12 Table 54: FeatureRequest Return Error to Activate/Deactivate SS Response Error

13 Mapping
Error Code value User Error
UnrecognizedMIN System Failure
MIN/HLRMismatch System Failure
OperationSequenceProblem System Failure
14
3-57
X.S0023

3
4 The IIF is responsible for the translation of the User Error/Provider Error received in the
5 Activate/Deactivate SS Response to either the appropriate FeatureRequest Return Result
6 message (with FeatureResult set to “unsuccessful” and, if supported, the AnnouncementList
7 parameter) or Error Code in the FeatureRequest Return Error, as shown in the following two
8 tables (Table 55 and Table 56).
9 Table 55: Activate/Deactivate SS Response User Error to FeatureRequest Return Result

10 Mapping
Activate/Deactivate SS Response User FeatureRequest Return Result
Error
SS subscription violation FeatureResult="unsuccessful"
AnnouncementList =
“UnauthorizedFeatureCode” (if parameter
supported by serving system)
3-58
X.S0023
2 Table 56: Activate/Deactivate SS Response User Error to FeatureRequest Return Error

3 Mapping
Activate/Deactivate SS Response User FeatureRequest Return Error Error Code
Error
System Failure System Failure
Data Missing System Failure
Unexpected Data Value System Failure
Bearer service not provisioned Not applicable to SS
activation/deactivation requests sent by IIF
(If received, may be mapped to System
Failure)
Teleservice not provisioned Not applicable to SS
Failure)
Call Barred Not applicable to SS
Failure)
Illegal SS operation Not applicable to SS
Failure)
SS error status Not applicable to SS
Failure)
SS incompatibility Not applicable to SS
Failure)
Negative PW check Not applicable to SS
Failure)
Number of PW Attempts Violation Not applicable to SS
Failure)
4
3-59
X.S0023
2 Table 57: Activate/Deactivate SS Response Provider Error to Feature Request Return

3 Error Mapping
Provider Error value received in Feature Request Return Error
Activate/Deactivate SS Response Error Code
Duplicated Invoke ID System Failure
Not supported service System Failure
Mistyped parameter System Failure
Resource limitation System Failure
Initiating Release System Failure
Unexpected response from the peer System Failure
Service Completion Failure System Failure
No response from the peer System Failure
Invalid response received System Failure
4
3-60
X.S0023
2 4.3.2 SS Registration and Erasure

3
5
6 4.3.2.1.1 Detailed Procedures

7
8 4.3.2.1.1 contains the procedures in the IIF for the case in which the subscriber requests
9 registration of information in association with one of the following supplementary services while
10 roaming in foreign mode (i.e., while roaming in a network of a technology different from that of
11 its home network):
17
18 4.3.2.1.1.1 GSM Foreign Mode

19
21 registration is that of handling the GSM MAP_REGISTER_SS as follows: If the IIF receives an
22 GSM MAP_REGISTER_SS message from the GSM serving system, it shall verify the correct
23 format and content of the message as described in GSM 09.02 [4].
24
26 also verify that the request for registration applies to (at least) speech. If the received request
27 does not include "speech" as one of the services to which the request applies, the IIF shall
28 respond with either a GSM MAP_REGISTER_SS Response message that includes a "User
29 error" parameter with a value of "Illegal SS Operation". Note that cases in which no "Basic
30 service" parameter is included in the received message are acceptable, since, by default, no
31 "Basic service" parameter indicates that the request applies to all services.
32
35 described in Table 59, Table 62 and Table 63. If a failure occurs at the IIF on reception of the
36 GSM MAP_REGISTER_SS message (e.g. missing data), the procedures described in GSM
37 09.02 [4] are applicable to the IIF.
38
3-61
X.S0023
3 IIF shall send a GSM MAP_REGISTER_SS Response message back towards the serving
4 system populated as described in Table 60 and Table 64.
7 the IIF shall send a GSM MAP_REGISTER_SS Response message back towards the serving
8 system as described in 4.3.2.2.3 Error Handling.
10 FeatureRequest Return Error message, the IIF shall send a GSM MAP_REGISTER_SS
11 Response message back towards the serving system as described in 4.3.2.2.3 Error Handling.
12 Note that successful supplementary service registration cases in GSM foreign mode may result
13 in the subscriber's ANSI-41 HLR sending out an ANSI-41 QUALDIR message to the serving
14 system. For these cases, the IIF would need to map the message to a GSM MAP Insert
15 Subscriber Data message. The mapping of an ANSI-41 QUALDIR message to a GSM MAP
16 Insert Subscriber Data message is covered in the Subscriber Data Management.
17
18 4.3.2.1.1.2 ANSI-41 Foreign Mode

19
21 service registration, is that of handling the ANSI-41 FeatureRequest INVOKE message, as
22 follows: if the IIF receives an ANSI-41 FeatureRequest INVOKE message from the ANSI-41
24 ANSI-41 [2]. If format and content of the message is correct, the IIF shall determine the
25 location of the subscriber’s HLR and send a GSM MAP_REGISTER_SS Request message
26 populated as described in in Table 59, Table 66 and Table 67. For cases in which the
27 FeatureRequest INVOKE message includes a feature code corresponding to Call Forwarding
28 No Answer, and if the IIF is configured to do so, the IIF may send two MAP_REGISTER_SS
29 messages, one indicating Call Forwarding No Reply and the other indicating Call Forwarding
30 Not Reachable. These messages may be sent in parallel. The mapping in Table 59, Table 66
31 and Table 73 should still be applicable.
32
36 If, in response to the a GSM MAP_REGISTER_SS Request message, the IIF receives a GSM
37 MAP_REGISTER_SS Response message with neither a User Error nor Provider Error
38 parameter, the IIF shall send an ANSI-41 FeatureRequest Return Result message back towards
39 the serving system populated as described in Table 60 and Table 67. For those cases in which
40 two requests had been previously sent by the IIF, the IIF would wait until receiving the
41 responses to both requests before sending the FeatureRequest Return Result message. For
42 cases in which both responses indicate success, the mapping in Table 60 may be applied to
43 either of the responses (as an IIF implementation option). For cases in which one of the
44 responses indicates success and the other failure, the mapping in Table 60 applies to the
45 successful response.
3-62
X.S0023
1 If, in response to the GSM MAP_REGISTER_SS Request message, the IIF instead receives a
2 GSM MAP_REGISTER_SS Response message with a User Error, the IIF shall send either an
3 ANSI-41 FeatureRequest Return or a Return Error as described in 4.3.2.2.3 Error Handling.
4 If a Provider Error parameter is included in the received GSM MAP_REGISTER_SS Response
5 message, the IIF shall send an ANSI-41 FeatureRequest Return Error message populated with
6 an Error Code as described in 4.3.2.2.3 Error Handling. For cases in which two requests
7 had been previously sent by the IIF, and both responses indicate failure, the procedures
8 described may be applied to either of the responses (as an IIF implementation option).
9 Note that successful supplementary service registration cases in ANSI-41 foreign mode may
10 result in the subscriber's GSM HLR sending out a GSM MAP Insert Subscriber Data message
11 to the serving system. For these cases, the IIF would need to map the message to an ANSI-41
12 QUALDIR message. The mapping of GSM MAP Insert Subscriber Data message to an
13 ANSI-41 QUALDIR message is covered in the Subscriber Data Management.
14
15 4.3.2.1.2 Mapping of Messages, Parameters & Parameter Values

16
17 4.3.2.1.2 presents the mapping of messages, parameters and parameter values that the IIF
18 shall perform.
19
20 4.3.2.1.2.1 Mapping of Messages

21
22 Table 58 shows the mapping of messages for Supplementary Service Registration
23 Table 58: Supplementary Service Registration Message Mapping

REGISTER SS REQUEST FEATREQ
REGITER SS REQUEST RESPONSE featreq
24
3-63
X.S0023
1 4.3.2.1.2.2 Mapping of parameters

5 Table 59: Register SS Request  FEATREQ parameter mapping

REGISTER SS REQUEST Status FEATREQ Status
Forwarded-to number with C
subaddress
Basic services C -
No reply condition time C -
EMLPP default priority C -
- MSCID (Serving) O
- PC_SSN O
6
3-64
X.S0023
1 Table 60: Register SS Response  Feature Request Return Result Parameter Mapping
Register SS Response Status Feature Request Return Result Status
EMLPP default priority C -
Forwarding information C -
FeatureResult (Note 1) M
Provider Error O -
- ActionCode O
- CarrierDigits O
- Digits (Dialed) O
- NoAnswerTime O
- PACAIndicator O
- PilotNumber O
- RoutingDigits O
- TerminationList O
2
3 Note 1: The FeatureResult parameter shall be mapped to an error value if a User Error is
4 received in the REGISTER SS RESPONSE, or the User Error shall be mapped to an
5 appropriate value if an Unsuccessful value is received in Feature Result. See Table 68.
3-65
X.S0023
1 Table 61: Register SS Response  Return Error Parameter Mapping

Register SS Response Status Return Error Status
EMLPP default priority C
Forwarding information C
Provider Error O
2
3 4.3.2.1.2.2.1 Mapping of parameter values in GSM Foreign Mode

4
5 Register SS Request to Feature Request Invoke mapping

6
9 Table 62: Register SS Request to Feature Request Invoke parameter mapping

Register SS Request Status FEATREQ Status
SS-Code/ M Digits (Dialed) M
Forwarded-to number with C This parameter is made up of
subaddress digits that make up a feature
code, plus a forwarded-to
number. The IIF shall obtain the
feature code from a table
mapping GSM supplementary
service operations (e.g. CFB
registration) to ANSI-41 feature
codes. The forwarded-to number
component is obtained from the
"Forwarded-to number with
subadress" parameter. Note that
any included subaddress in that
parameter is ignored.
10
12 mapping from the GSM MAP parameter "Basic service". The "GSM Foreign Mode" of
3-66
X.S0023
2 Table 63 presents how the IIF shall populate the parameters of the Feature Request Invoke
3 message to be sent to the ANSI-41 HLR. These fields cannot be mapped from the received
4 Register SS request message.
5 Table 63: FEATREQ default parameter

6
ElectronicSerialNumber M Shall be derived from IMSI previously
obtained from GSM MAP_OPEN
information.
MSID (Either MIN or IMSI) M Shall be obtained from mapping from the
IMSI previously obtained from GSM
MAP_OPEN information.
MobileDirectoryNumber O May be optionally included in message
from IIF’s data.
unique ID used during registration to
identify serving MSC.
MSCIdentificationNumber O May be included from IIF data. Set to the
Serving MSC's address.
7
3-67
X.S0023
1 Feature Request Return Result to Register SS Response mapping
7 corresponding GSM Register SS Response message shall be populated. For the unsuccessful
8 cases, refer to 4.3.2.2.3 Error Handling.
11 Table 64 describes the population of the parameters in the Register SS Response message for
12 successful registration cases (i.e. when the received Feature Request Return Result contains a
13 FeatureResult parameter set to “successful”).
14 Table 64: Register SS Response default parameter values

Register SS Response Status Default Value
Call forwarding information C The forwarded-to number of the
"Forwarding feature" parameter within the
"Call forwarding information" parameter is
populated using the registered address.
The suggested values for other
parameters are as follows:
- SS-Code: The code of the call
forwarding supplementary service to which
the registration applies.
- Basic Service Group: not included;
- SS-Status: Based on current status of
feature;
- forwarded-to subaddress: not included;
- forwarding options: not included;
- no reply condition timer: May be included
only for Call Forwarding No Reply cases.
EMLPP default priority C Not applicable. May be ignored when
received.
15
3-68
X.S0023
1 4.3.2.1.2.2.2 Mapping of parameter values ANSI-41 Foreign Mode

2
3 Feature Request Invoke to Register SS Request mapping
6 Table 65: FEATREQ to Register SS Request parameter mapping

FEATREQ Status Register SS Request Status

operations (e.g. CFB
registration)
Digits (Dialed) M Forwarded-to number with M
subaddress
Populated from the forwarded-to
number portion of the Digits
(Dialed) parameter.
7
9 Table 66 presents how the IIF shall populate the parameters of the Register SS Request
10 message to be sent to the GSM HLR. These fields do not have an equivalent in the received
11 Feature Request Invoke message.
12 Table 66: Register SS Request default parameter

Basic services C Not required to be included. (Registration
operation shall apply to all service groups
when absent.)
No reply condition time C Not required to be included.
EMLPP default C Not required to be included.
13
3-69
X.S0023
2 GSM Register SS Response to ANSI-41 Feature Request Return Result mapping
5 For the successful case (in which there’s no User error or Provider Error in the received GSM
6 Register SS Response message), there are no meaningful parameter mappings to support.
7 For those successful cases, the “Default parameter values” describes how the corresponding
8 ANSI-41 FeatureRequest Return Result shall be populated. For the unsuccessful cases, refer
9 to 4.3.2.2.3 Error Handling.
10
12 Table 67 presents how the IIF shall populate the parameters of the Feature Request Return
13 Result message to be sent to the ANSI-41 VLR for successful supplementary service
14 registration cases. Note that the population of the message may differ for non-registration
15 cases.

17
3-70
X.S0023
2 Table 67: FeatureRequest Return Result default parameter (concluded)

3
4 4.3.2.1.3 Error Handling

5
6 The error handling procedures specified for supplementary service activation apply also for the
7 supplementary service registration case, with the following modification: the User Error values
8 "SS subscription violation", "Negative PW Check", and "Number of PW Attempts Violation",
9 although valid for the activation case, are not valid for the registration case. If any of those
10 values are received in the User Error parameter of a Register SS Response, they may be
11 mapped to "System Failure". Also, the IIF may not include any of those User Error values in
12 the Register SS Response messages it sends.
13 Table 68: FeatureRequest Return Result to User Error in the Register SS Response
14 mapping
FeatureRequest Return Result User Error in the Register SS Response
AnnouncementList="UnauthorizedFeature
Code"
15
3-71
X.S0023
1 4.3.2.2 Erasure
2

4
5 4.3.2.2.1 contains the procedures in the IIF for the case in which the subscriber requests
6 erasure (de-registration) of information in association with one of the following supplementary
7 services while roaming in foreign mode (i.e., while roaming in a network of a technology
8 different from that of its home network):
15
16 4.3.2.2.1.1 GSM Foreign Mode

17
19 erasure is that of handling the GSM MAP_ERASE_SS as follows: If the IIF receives an GSM
20 MAP_ERASE_SS message from the GSM serving system, it shall verify the correct format and
21 content of the message as described in GSM 09.02 [4].
22
24 also verify that the request for erasure applies to (at least) speech. If the received request does
25 not include "speech" as one of the services to which the request applies, the IIF shall respond
26 with either a GSM MAP_ERASE_SS Response message that includes a "User error"
27 parameter with a value of "Illegal SS Operation". Note that cases in which no "Basic service"
28 parameter is included in the received message are acceptable, since, by default, no "Basic
29 service" parameter indicates that the request applies to all services.
30
33 described in Table 70, Table 73 and Table 74. If a failure occurs at the IIF on reception of the
34 GSM MAP_ERASE_SS message (e.g. missing data), the procedures described in GSM 09.02
35 [4] are applicable to the IIF.
36
3-72
X.S0023
1 IIF shall send a GSM MAP_ERASE_SS Response message back towards the serving system
2 populated as described in Table 71 and Table 75.
6 the IIF shall send a GSM MAP_ERASE_SS Response message back towards the serving
7 system as described in Table 71 and Table 79.
9 FeatureRequest Return Error message, the IIF shall send a GSM MAP_ERASE_SS Response
10 message back towards the serving system as described in 4.3.2.2.3 Error Handling.
11 Note that successful supplementary service erasure cases in GSM foreign mode may result in
12 the subscriber's ANSI-41 HLR sending out an ANSI-41 QUALDIR message to the serving
13 system. For these cases, the IIF would need to map the message to a GSM MAP Insert
14 Subscriber Data message. The mapping of an ANSI-41 QUALDIR message to a GSM MAP
15 Insert Subscriber Data message is covered in the Subscriber Data Management.
16
17 4.3.2.2.1.2 ANSI-41 Foreign Mode

18
20 service erasure, is that of handling the ANSI-41 FeatureRequest INVOKE message, as follows:
21 If the IIF receives an ANSI-41 FeatureRequest INVOKE message from the ANSI-41 serving
22 system, it shall verify the correct format and content of the message as described in ANSI-41
23 [2]. If format and content of the message is correct, the IIF shall determine the location of the
24 subscriber’s HLR and send a GSM MAP_ERASE_SS Request message populated as described
25 in Table 70 and Table 77. For cases in which the FeatureRequest INVOKE message includes a
26 feature code corresponding to Call Forwarding No Answer, and if the IIF is configured to do so,
27 the IIF may send two MAP_ERASE_SS messages, one indicating Call Forwarding No Reply and
28 the other indicating Call Forwarding Not Reachable. These messages may be sent in parallel.
29 The mapping in Table 70,Table 75 and Table 77 would still be applicable.
33 If in response to the a GSM MAP_ERASE_SS Request message, the IIF receives a GSM
34 MAP_ERASE_SS Response message with neither a User Error nor Provider Error parameter,
35 the IIF shall send an ANSI-41 FeatureRequest Return Result message back towards the serving
36 system populated as described in Table 71. For those cases in which two requests had been
37 previously sent by the IIF, the IIF would wait until receiving the responses to both requests
38 before sending the FeatureRequest Return Result message. For cases in which both responses
39 indicate success, the mapping in Table 71 may be applied to either of the responses (as an IIF
40 implementation option). For cases in which one of the responses indicates success and the
41 other failure, the mapping in Table 71, Table 75 and Table 86 applies to the successful
42 response.
43 If, in response to the GSM MAP_ERASE_SS Request message, the IIF instead receives a
44 GSM MAP_ERASE_SS Response message with a User Error, the IIF shall send either an
45 ANSI-41 FeatureRequest Return Result or a Return Error as described in 4.3.2.2.3 Error
46 Handling If a Provider Error parameter is included in the received GSM MAP_ERASE_SS
3-73
X.S0023
1 Response message, the IIF shall send an ANSI-41 FeatureRequest Return Error message
2 populated with an Error Code. For cases in which two requests had been previously sent by the
3 IIF, and both responses indicate failure, the procedures described in 4.3.2.2.3 Error Handling
4 may be applied to either of the responses (as an IIF implementation option).
5 Note that successful supplementary service erasure cases in ANSI-41 foreign mode may result
6 in the subscriber's GSM HLR sending out a GSM MAP Insert Subscriber Data message to the
7 serving system. For these cases, the IIF would need to map the message to an ANSI-41
8 QUALDIR message. The mapping of GSM MAP Insert Subscriber Data message to an
9 ANSI-41 QUALDIR message is covered in the Subscriber Data Management.

11 4.3.2.2.2 presents the mapping of messages, parameters and parameter values that the IIF
12 shall perform.
13

15 Table 69 shows the mapping of messages for Supplementary Service Erasure.
16 Table 69: Supplementary Service Erasure Message Mapping

ERASE SS REQUEST FEATREQ
ERASE SS REQUEST RESPONSE featreq
17
3-74
X.S0023
1 4.3.2.2.2.2 Mapping of parameters

5 Table 70: Erase SS Request  FEATREQ parameter mapping

Erase SS Request Status FEATREQ Status
Basic services C -
- MSCID (Serving) O
- PC_SSN O
6
3-75
X.S0023
1 Table 71: Erase SS Response  Feature Request Return Result parameter mapping
Erase SS Response Status Feature Request Return Result Status
Forwarding information C -
- FeatureResult (Note1) M
Provider Error O -
- ActionCode O
- CarrierDigits O
- Digits (Dialed) O
- NoAnswerTime O
- PACAIndicator O
- PilotNumber O
- RoutingDigits O
- TerminationList O
2
3 Note 1: The FeatureResult parameter shall be mapped to an error value if a User Error is
4 received in the ERASE SS RESPONSE
5
3-76
X.S0023
2 Table 72: Erase SS Response  Return Error parameter mapping

Erase SS Response Status Return Error Status
Call forwarding information C -
Provider Error O
3
4 4.3.2.2.2.2.1 Mapping of parameter values in GSM Foreign Mode

5
6 Erase SS Request to Feature Request Invoke mapping
9 Table 73: Erase SS Request to FEATREQ parameter mapping

Erase SS Request Status FEATREQ Status
This parameter shall be made up
of digits that make up the feature
code string that corresponds to
erasure (de-registration) of the
information that pertains to the
supplementary service specified
in the SS-Code parameter. The
IIF shall obtain the feature code
from a table mapping GSM
supplementary service
operations (e.g. CFB erasure) to
ANSI-41 feature codes.
10
12 mapping from the GSM MAP parameter "Basic service". The "GSM Foreign Mode" part of
13
3-77
X.S0023
3 Table 74 presents how the IIF shall populate the parameters of the Feature Request Invoke
5 Erase SS request message.
6 Table 74: Feature Request Invoke default parameter

ElectronicSerialNumber M Shall be derived from IMSI previously
obtained from GSM MAP_OPEN information.
MSID (MIN or IMSI) M Shall be obtained from mapping from the IMSI
obtained previously from GSM MAP_OPEN
information.
MobileDirectoryNumber O May be optionally included in message from
IIF’s data.
unique ID used during registration to identify
serving MSC.
MSCIdentificationNumber O May be included from IIF data.
7
8 Feature Request Return Result to Erase SS Response mapping
11
15 corresponding GSM Erase SS Response message shall be populated. For the unsuccessful
16 cases, refer to 4.3.2.2.3 Error Handling
17
3-78
X.S0023
2 Table 75 describes the population of the parameters in the Erase SS Response message for
3 successful erasure cases (i.e. when the received Feature Request Return Result contains a
4 FeatureResult parameter set to “successful”).
5 Table 75: Erase SS Response default parameter values

Erase SS Response Status Default Value
Call forwarding C The suggested values for the fields in this parameter
information are as follows:
- SS-Code: The code of the call forwarding
supplementary service to which the registration
applies.
- Basic Service Group: not included;
- SS-Status: Based on current status of feature;
- forwarded-to number: not included;
- forwarded-to subaddress: not included;
- forwarding options: not included;
- no reply condition timer: May be included only for
Call Forwarding No Reply cases.
6
7 4.3.2.2.2.2.2 Mapping of parameter values in ANSI-41 Foreign Mode

8
9 Feature Request Invoke to Erase SS Request mapping
12 Table 76: FEATREQ to Erase SS Request parameter mapping

FEATREQ Status Erase SS Request Status
operations (e.g. CFB erasure)
13
3-79
X.S0023
2 This table presents how the IIF shall populate the parameters of the Erase SS Request
3 message to be sent to the GSM HLR. These fields do not have an equivalent in the received
4 Feature Request Invoke message.
5 Table 77: Erase SS Request default parameter

Basic services C Not required to be included. (Registration operation
shall apply to all service groups when absent.)
6
7 GSM Erase SS Response to ANSI-41 Feature Request Return Result mapping
9 For the successful case (in which there is no User error or Provider Error present in the
10 received GSM Erase SS Response message), there are no meaningful parameter mappings to
12 corresponding ANSI-41 FeatureRequest Return Result shall be populated. For the
13 unsuccessful cases, refer to 4.3.2.2.3 Error Handling.
3-80
X.S0023

2 This table presents how the IIF shall populate the parameters of the Feature Request Return
3 Result message to be sent to the ANSI-41 HLR for successful erasure cases. Note that the
4 population of the message may differ for non-erasure cases.

3-81
X.S0023

2
3 The error handling procedures specified for supplementary service activation apply also for the
4 supplementary service erasure case, with the following modification: the User Error values "SS
5 subscription violation", "SS incompatibility", "Negative PW Check", and "Number of PW
6 Attempts Violation", although valid for the activation case, are not valid for the erasure case. If
7 any of those values are received in the User Error parameter of a Register SS Response, they
8 may be mapped to "System Failure". Also, the IIF may not include any of those User Error
9 values in the Erase SS Response messages it sends.
10
11 Table 79: FeatureRequest Return Result to Register SS Response User Error

FeatureRequest Return Result User Error in the Erase SS Response
AnnouncementList="UnauthorizedFeature
Code"
12
3-82
X.S0023
1 4.3.3 Retrieval of Forward-To Number

2

4
5 The following procedures are applicable at the IIF for retrieval of forwarded-to-number, in GSM
6 foreign mode. These procedures are applicable for Call Forwarding Busy (CFB) and Call
7 Forwarding No Answer (CFNA), which will be referred to as Conditional Call Forwarding.
8 In GSM, the HLR provides the forwarded-to-number(s) to the serving MSC/VLR as part of the
9 profile update procedure, in the MAP_Insert_Subscriber_Data message (or, as part of the
10 response to a MAP_Interrogate_SS request). The ANSI-41 HLR, however, only provides this
11 information when the Call Forwarding feature is actually invoked. Therefore, in GSM foreign
12 mode, in order to the able to include the forwarded-to-number(s) in the
13 MAP_Insert_Subscriber_Data message to the serving system during profile updates, the IIF
14 has to, beforehand, explicitly request the ANSI-41 HLR for the forwarded-to-number(s). The IIF
15 makes this request to the ANSI-41 HLR via the TransferToNumberRequest Invoke message.
16 (Note that two separate TRANUMREQ messages may be needed: one for CFB and another for
17 CFNA. The two requests may be sent in parallel by the IIF). The IIF shall then store the
18 received forwarded-to numbers for subsequent use.
19 Specifically, before a MAP_Insert_Subscriber_Data message is sent by the IIF, the IIF shall
20 determine if it needs to query the ANSI-41 HLR for the CFB or CFNA forwarded-to number(s).
21 In general, the IIF needs to query the ANSI-41 HLR at least for the case in which the
22 CFB/CFNA feature is authorized and active for the subscriber, and the profile update procedure
23 is being performed immediately after an initial successful location update of the subscriber in
24 GSM foreign mode1. Other cases for initiating the query may be supported by the IIF as
25 follows:
26 a) After a recent successful forwarded-to number registration pertaining to either the CFB or
27 CFNA feature.
28 (Note, however, that a query after a forwarded-to number registration may not be
29 necessary if the IIF saves the forwarded-to number while processing the registration
30 messages.)
31 After a successful location update when either the CFB or CFNA feature is authorized, but not
32 necessarily active.
33 (This case differs from the mandatory case in that the CFB/CFNA feature need not be
34 active in order to initiate the query. Supporting this case would make it unnecessary for
35 the query to be performed after an activation of the CFB/CFNA feature)
36 b) After a recent successful activation of either the CFB or CFNA feature.

37 (Note that this case would only be needed if the IIF had not queried the ANSI-41 HLR
38 previously. In particular if the IIF, during the initial location update, does not perform the
39 query because the CFB/CFNA feature is not active.)
40 c) On a regular basis (e.g. timer-based)
1
Note that this refers only to the successful location update case. There's no need for the
IIF to perform this procedure for unsuccessful cases.
3-83
X.S0023
1 (Supporting this case would be useful for accounting for the possibility of a network
2 administrator-initiated change of the forwarded-to DN(s)).
3 The IIF shall populate the TransferToNumberRequest Invoke message in a manner compliant
4 with ANSI-41 [2]. The IIF shall then send the TransferToNumberRequest Invoke message to
5 the ANSI-41 HLR, start the Transfer-To-Number Request Timer, and wait for a response.
6 If the response indicates that the retrieval of forwarded-to-number procedure has been
7 successful, the IIF shall map the forwarded-to-number information (along with any other
8 subscriber profile information received in either the QualificationDirective Invoke or
9 RegistrationNotification RETURN RESULT) into a MAP_Insert_Subscriber_Data Request
10 message. As shown in Table 81 and Table 82, the Forwarded-to-Number field of the
11 TransferToNumberRequest RETURN RESULT shall be mapped from the Digits (Destination)
12 field in the MAP_Insert_Subscriber_Data message. In addition, if the registration deals with Call
13 Forwarding No Answer, the No Reply Condition Time parameter in the
14 MAP_Insert_Subscriber_Data message should be populated with the content of the
15 NoAnswerTime field in the TransferToNumberRequest RETURN RESULT message.
16 In case of a failure, the IIF may receive either a TransferToNumberRequest RETURN RESULT
17 with the field AccessDeniedReason present, or a Return Error or Reject message with an Error
18 Code value. For those cases in which a failure occurs, the IIF shall continue to use a
19 previously obtained forwarded-to number, if available. If no previously obtained forwarded-to
20 number is available at the IIF, the IIF shall not populate the corresponding information (i.e., the
21 Forwarded-to-Number field within the Forwarding Information List parameter) in the
22 MAP_Insert_Subscriber_Data Request message.

24
25 Note: the mapping of the QualificationDirective Invoke message to the

26 MAP_Insert_Subscriber_Data Request message is described in details in 4.4 O&M
27 Procedures. Therefore, 4.3.3.2 focuses on the mapping of TransferToNumberRequest return
28 result to the relevant MAP_Insert_Subscriber_Data field. Not all Insert Subscriber Data fields
29 are shown in the following tables.

31
32 The following table shows the mapping of messages for Retrieval of Forward-to-Number in
33 GSM Foreign Mode.
34 Table 80: Retrieval of Forward-to-Number in GSM Foreign Mode

ANSI MAP MESSAGE GSM MAP MESSAGE
Transfer to Number Request Return Result INSERT SUBSCRIBER DATA
35
3-84
X.S0023
1 4.3.3.2.2 Mapping of parameters

2 The following tables are only for GSM Foreign Mode.
4 Table 81: TransferToNumberRequest Return Result to Insert Subscriber Data parameter

5 mapping
TransferToNumberRequest Status Insert Subscriber Data Status
Return Result
Digits (Destination) M Forwarded-to-Number (within C
or TerminationList (see Note 1) O Forwarding Information List)
AccessDeniedReason O -
ActionCode O -
AnnouncementList O -
CallingPartyString1 O -
CallingPartyString2 O -
Digits (Carrier) O -
DMH_RedirectionIndicator (Set O -
to CFB or CFNA)
GroupInformation O -
MobileDirectoryNumber O -
NoAnswerTime O No Reply Condition time (within C
Forwarding Information List)
RedirectingNumberDigits O -
RedirectingSubaddress O -
CDMAServiceOption (Note 2) O -GSM BearerServiceCode or O
GSm TeleService
6
7 Note 1: When TerminationList parameter is present, the Digits (Destination) parameter is
8 ignored.
9 Note 2: Optional, if the network settings support data, a mapping may be performed as
3-85
X.S0023
1 TransferToNumberRequest Return Result to Insert Subscriber Data Request
2 Mapping of parameters value
5 Table 82: TransferToNumberRequest Return Result to Insert Subscriber Data Request

6 value mapping
TransferToNumberRequest Return Status Insert Subscriber Data Request Status
Result
Digits (Destination) or M Forwarding Information List C
DestinationDigits parameter within Forwarded-to-Number
TerminationList (See Note 1) (See Note 2)
This is the forwarded-to-number. E.164 format
Format is Type of Digits (1 octet),
Nature of Number (1 octet),
Numbering Plan (4 bits), Encoding
(4 bits), Number of Digits (1 octet),
and actual digits in BCD.
NoAnswerTime O Forwarding Information List C
No Reply Condition time
CDMAServiceOption (Note 3) O -GSM BearerServiceCode or O
GSM TeleService
7 Note 1: When TerminationList parameter is present, the Digits (Destination) parameter of the
8 TransferToNumberRequest RETURN RESULT is ignored.
9 Note 2: There may be up to three forwarded-to number parameters with the Insert Subscriber
10 Data Request message mapped from TransferToNumberRequest information: one for Call
11 Forwarding Busy, one for Call Forwarding No Reply (mapped from CFNA results), and another
12 for Call Forwarding Not Reachable (also mapped from CFNA results).
13 Note 3: Optional, if the network settings support data, a maping may be performed as
16 The other parameters in the TransferToNumberRequest Return Result message are not
17 mapped to any of the Insert Subscriber Data Request parameters.

19
20 No mapping between ANSI-41 and GSM MAP messages is required for cases in which the
21 forwarded-to number retrieval operation fails. Refer to 4.3.3.1 Detailed Procedures for a
22 description of the IIF procedures when the forwarded-to number retrieval operation fails.
23
3-86
X.S0023
1 4.3.4 Calling Number / Line Identification Presentation/Restriction

2 The calling number/line identification Presentation/Restriction procedure is used to determine
3 whether the calling party number should be presented to the called party.
4 4.3.4.1 Handling of calling number/ line identification presentation

7 presentation is allowed, the called party’s serving network shall provide the calling party
8 number to the called party during call alerting.
9 If the IIF receives a GSM MAP _PROVIDE_ROAMING_Request with the Calling Party Number
10 in the Additional Signal Info field correctly populated, the IIF shall send an ANSI_MAP
11 ROUTEREQ to the serving MSC/VLR with the Calling Party Number field correctly mapped.
12 If the IIF receives an ANSI_MAP ROUTREQ with the Calling Party Number field in the
13 Additional Signal Info field correctlty populated, the IIF shall send a GSM MAP
14 _PROVIDE_ROAMING_NUMBER_Request to the serving MSC/VLR with the Calling Party
15 Number field correctly mapped.

18 The mapping of messages is in accordance with 4.2.1, with the exception that GSM 09.02 [4] is
19 supported.
3-87
X.S0023
1 4.3.4.1.2.2 Mapping of Parameters

2 The following tables show the mapping of parameters specific to handling calling number/line
3 presentation/restrcition, which the IIF shall perform regardless of the mode of operation (GSM
4 Foreign Mode or ANSI-41 Foreign Mode). The mapping of other parameters not specific to
5 handling calling number/line presentation/restriction can be found in 4.2.1, with the exception
6 that GSM 09.02 [4] is supported.
7 Note: The tables are constructed in such a way that the parameter names appear first and any
8 information contained within those parameters are shown as indented text.
9 Table 83: Routing Request  Provide Roaming Number Request (Network Provided
10 number) Parameter Mapping
Routing Request Status Provide Roaming Number Status
CallingPartyNumberString1 O AdditionalSignalInfo:- C
(Network Provided No):- CallingPartyNumber:-
Type Of Digits:- Calling Party -

Number
Nature of Number:- National, Screening Indicator: Network

Presentation Allowed, Network Provided
Provided Presentation Indicator:
Presentation Allowed
Numbering Plan:- Telephony -

Numbering
Encoding:- IA5 -
Characters:- Digits Line Identity: E164 address of

Calling Party
3-88
X.S0023
1 Table 84: Routing Request  Provide Roaming Number Request (User Provided
2 number) Parameter Mapping
Route Request Status Provide Roaming Number Status
CallingPartyNumberString2 O AddititonalSignalInfo:- C
(User Provided No):- CallingPartyNumber:-

Number
Nature of Number:- Screening Indicator: User

National,Presentation Allowed, Provided, not screened
User Provided, not screened Presentation Indicator:

Numbering
Encoding:- IA5 -

Calling Party
3
3-89
X.S0023
1 Table 85: Routing Request  Provide Roaming Number Request (Two calling party
2 numbers) Parameter Mapping
Route Request Status Provide Roaming Number Status
CallingPartyNumberString1 O AdditionalSignalInfo:- C

Number

Presentation Allowed, Provided
Network Provided Presentation Indicator:

Numbering
Encoding:-IA5 -

Calling Party
CallingPartyNumberString2 O Generic Number:-
(User Provided No):-

Number
Nature of Number:- National, Screening Indicator: User

Presentation Allowed Provided, not screened
User Provided

Numbering
Encoding:- IA5 -

Calling Party
3
4 4.3.4.2 Handling of calling number/ line identification restriction

6 If the calling subscriber has calling number/line identification restriction authorized and active
7 and it is impossible to indicate to the terminating network (due to interworking) that the number
8 shall not be presented to the terminating party, the calling number/line identity shall not be
9 delivered to the terminating network.
3-90
X.S0023
3 4.3.4.2.2 Mapping of Messages, Parameters and Parameter Values

5 Messages for Calling number/line identification restriction is the same as 4.3.4.1.

7 The following table shows the mapping of parameters for calling name/line restriction, which the
8 IIF shall perform regardless of the mode of operation (ANSI-41 Foreign Mode or GSM Foreign
9 mode).
10 Table 86: Routing Request  Provide Roaming Number Request(Caller Id Restricted)

11 Parameter Mapping
Routing Request Status Provide Roaming Number Status
CallingPartyNumberString1 O AdditionallSignalInfo:- C

Number

Presentation Restricted, Provided,
Network Provided Presentation Indicator:
Presentation Restrcited

Numbering
Encoding:- IA5 -
Characters:-Digits Line Identity: E164 address of

Calling Party
13 For the cases of failure at the IIF on reception of an ANSI_ MAP_RoutingRequest return Result,
14 the procedures described in ANSI-41 [2] for automatic call delivery is applicable to the IIF.
15 For the cases of failure at the IIF on resception of a GSM MAP

16 _PROVIDE_ROAMING_NUMBER_Response, the procedures described in GSM 09.02 [4] are
17 applicable to the IIF.
18 If the IIF receives a GSM MAP _PROVIDE_ROAMING_NUMBER_Request indicating an error

19 code, the IIF shall map that error code it receives to a suitable error in the ANSI_MAP_routereq
20 as described in 4.2.1
21 If the IIF receives an ANSI_MAP_routreq indicating an error code, the IIF shall map that error
22 code it receives to a suitable error in the GSM MAP
23 _PROVIDE_ROAMING_NUMBER_Response as described in 4.2.1.
3-91
X.S0023
1 4.4 O&M Procedures

2 Existing operation and maintenance procedures described in either GSM 09.02 [4] or ANSI-41
3 [2] are also directly applicable to the IIF when it is emulating a GSM or ANSI-41 functional
4 network element. Enhancements/modifications to ANSI-41 [2] are also applicable.
5 4.4.1 Detailed Procedures

6 Subscriber data management procedures are used to either delete or modify, subscriber data
7 held in the network. These procedures are initiated by the OMC.
8 Subscriber data management procedures also cover ANSI-41 specific procedures, describing
9 the retrieval of subscriber data from network elements.
10 The IIF contains both permanent subscriber data (can only be changed by administration
11 means) and temporary subscriber data (may be changed as a result of normal operation of the
12 system) relating to the roaming subscriber.
13 4.4.1.1 Subscriber Deletion Procedure

14 If the IIF receives a GSM MAP _CANCEL_LOCATION_REQUEST, it shall follow the location
15 cancellation procedures outlined in this document for Location Registration (see 4.1.1).
16 If the IIF receives an ANSI_MAP_REGCAN, it shall follow the location cancellation procedures
17 outlined in this document for Location Registration (see 4.1.1).
18 4.4.1.2 Subscriber Data Modification Procedure (ANSI-41 Foreign Mode)

19 If the IIF receives either a GSM MAP _INSERT_SUBSCRIBER_DATA_REQUEST, or a GSM
20 MAP _DELETE_SUBSCRIBER_DATA_REQUEST, it shall follow the VLR procedures
21 described in GSM 09.02 [4].
22 As part of the subscriber data modification procedure, the IIF may send an
23 ANSI_MAP_QUALDIR to the serving ANSI-41 VLR and await a response.
24 If the response indicates success, the IIF shall modify the corresponding subscriber data and
25 send a GSM MAP _INSERT_SUBSCRIBER_DATA_RESPONSE to the GSM HLR.
26 If the response indicates failure, the received subscriber data is stored by IIF even if there is a
27 failure reported from the visited (foreign mode) system and the IIF shall send the reason for
28 failure in a GSM MAP _INSERT_SUBSCRIBER_DATA_RESPONSE to the GSM HLR.
29 4.4.1.3 Subscriber Data Modification Procedure (GSM Foreign Mode)

30 If the IIF receives an ANSI_MAP_QUALDIR, it shall follow the VLR procedures described in
31 ANSI-41 [2].
32 As part of the subscriber data modification procedure, the IIF may send either a GSM MAP
33 _INSERT_SUBSCRIBER_DATA_REQUEST or a GSM MAP
34 _DELETE_SUBSCRIBER_DATA_REQUEST to the serving GSM VLR and await a response.
35 If the response indicates success, the IIF shall modify the corresponding subscriber data and
36 send an ANSI_MAP_qualdir to the ANSI-41 HLR.
37 If the response indicates failure, the received subscriber data is stored by IIF even if there is a
38 failure reported from the visited (foreign mode) system and the IIF shall send the reason for
39 failure in the ANSI_MAP_qualdir to the ANSI-41 HLR.
3-92
X.S0023
1 4.4.1.4 Subscriber Data Retrieval

2 If the IIF receives an ANSI_MAP_QUALREQ, it shall follow the ANSI-41 HLR procedures
3 described in ANSI-41 [2]. The IIF is not required to retrieve subscriber data from the GSM
4 HLR.
5 4.4.2 Mapping of Messages, Parameters & Parameter Values

6 The IIF shall perform the translation of messages, parameters and parameter values related to
7 subscriber data management in accordance with the tables presented.
8 4.4.2.1 Mapping of Messages

9 Table 87 shows the mapping between GSM MAP messages and ANSI-41 MAP messages
10 related to Subscriber Deletion. Table 88 and Table 89, show the mapping between GSM MAP
11 messages and ANSI-41 MAP messages related to Subscriber Data Modification.
12 Table 87: Cancel_Location_Request  REGCAN (Subscriber Deletion) Mapping

CANCEL_LOCATION_REQUEST REGCAN
CANCEL_LOCATION_RESPONSE (Note 1) regcan return result
CANCEL_LOCATION_RESPONSE (Note 2) regcan Return Error
13
14 Note 1: In the successful case, the CANCEL_LOCATION_RESPONSE is an empty result i.e.

15 contains no parameters other than the invoke Id.
16 Note 2: This message can also contain error values if the subscriber deletion procedure is
17 unsuccessful. If the subscriber deletion procedure fails, the mapping is as shown. See 4.4.3
18 Error Handling for more information.
19
20 Table 88: Mapping of GSM MAP Messages  ANSI MAP Messages (Subscriber Data
21 Modification)
INSERT_SUBSCRIBER_DATA_REQUEST QUALDIR
INSERT_SUBSCRIBER_DATA_RESPONSE qualdir (Note 2)
INSERT_SUBSCRIBER_DATA_RESPONSE qualdir Return Error

(Note 1)
22
3-93
X.S0023
1 Table 89: Delete_Subscriber_Data  Qualdir Mapping (Subscriber Data Modification)

DELETE_SUBSCRIBER_DATA_REQUEST QUALDIR
DELETE_SUBSCRIBER_DATA_RESPONSE qualdir Return Result (Note 2)
DELETE_SUBSCRIBER_DATA_RESPONSE qualdir Return Error

(Note 1)
2
3 Note 1: These messages can also contain error values if the subscriber data modification
4 procedure is unsuccessful. If the subscriber data modification procedure fails, the mapping is
5 as shown. See 4.4.3 Error Hanlding for more information.
6 Note 2: The qualdir Return Result is an empty response i.e. contains no parameters other than
7 the Invoke Id.
8 4.4.2.2 Mapping of Parameters

9 The following tables show the mapping of parameters, which the IIF shall perform regardless of
10 the mode of operation (GSM Foreign Mode or ANSI-41 Foreign Mode).
11 Table 90: CANCEL_LOCATION_REQUEST  REGCAN Parameter Mapping

CANCEL_LOCATION_REQUEST Status REGCAN Status
IMSI M MSID M
LMSI C -
Cancellation Type C Cancellation Type O
ControlChannelData O
ReceivedSignalQuality O
SenderIdentifcationNumber O
SystemAccessData O
12
13 Note 1: Cancellation Type is only used between the HLR and the SGSN for GPRS procedures.
14 Cancellation Type is not applicable between HLR and VLR.
3-94
X.S0023
1 Table 91: INSERT_SUBSCRIBER_DATA_REQUEST  QUALDIR Parameter Mapping

INSERT_SUBSCRIBER_DATA_ Status QUALDIR Status
REQUEST
IMSI C ElectronicSerialNumber M
MSID M
QualificationInformationCode M
SystemMyTypeCode (HLR or M
VLR)
AuthorizationDenied O
AuthorizationPeriod O
DeniedAuthorizationPeriod O
Digits (Carrier) O
Digits (Destination) O
LocationAreaID O
1
Profile “Macro” O
2
1
5 the ANSI-41-D ‘QUALDIR Invoke’ to the contents of the GSM MAP
3-95
X.S0023
1 Table 92: INSERT_SUBSCRIBER_DATA_REQUEST  profile ‘macro’ Mapping

INSERT_SUBSCRIBER_DATA_ Status ‘profile’ macro Status
REQUEST
- AuthenticationCapability O
MSISDN C MobileDirectoryNumber O
Category C -
Subscriber Status C -
Bearer service List C -
Teleservice List C
Forwarding information List C CallingFeaturesIndicator1 O
- CarrierDigits O
Regional Subscription Data C -
- GeographicAuthorization O
- MessageWaitingNotificationCount O
- MessageWaitingNotificationType O
3 2
Call barring information List C OriginationIndicator O
VLR CAMEL Subscription Info4 C OriginationTriggers4 O
- PACAIndicator O
CUG information List C -
6
SS-Data List C CallingFeaturesIndicator1 O
EMLPP Subscription Data C -
Operator Determined Barring C OriginationIndicator2 O
General data
HPLMN data5
Operator Determined Barring C RestrictionDigits O
HPLMN data5
Roaming Restriction Due To C -
Unsupported Feature
- RoutingDigits O
3 7
Call barring information List C SMS_OriginationRestrictions O
Call barring information List3 C SMS_TerminationRestrictions8 O
- SPINIPIN O
- SPINITriggers O
3-96
X.S0023
1 Table 92: INSERT_SUBSCRIBER_DATA_REQUEST  profile ‘macro’ Mapping

2 (concluded)
INSERT_SUBSCRIBER_DATA_ Status ‘profile’ macro Status

REQUEST
Call barring information List3 C TerminationRestrictionCode O
4
VLR CAMEL Subscription Info C TerminationTriggers O
Voice Broadcast Data C
Voice Group Call Data C -
- PreferredLanguageIndicator O
6 7
SS-Data List SMS_OriginationRestrictions O
6 8
SS-Data List SMS_TerminationRestrictions O
-GSM BearerServiceCode or O CDMAServiceOptionList9 O
GSM TeleService
3
1
4 The CallingFeaturesIndicator parameter provides a status of several ANSI supplementary
5 services. This information may map into one or more GSM MAP parameters as shown in
6 Table 92.
2
7 The OriginationIndicator parameter defines the type of calls that a MS is allowed to make.
8 This information may map into one or more GSM MAP parameters as shown in Table 92.
3
9 The Call barring information List is a list of the call barring supplementary services that are
10 either active, quiescent or not active for individual or all teleservices. This information may
11 map into one or more ANSI MAP parameters as shown in Table 92.
4
12 If this information is received by the IIF it does have to be mapped.
5
13 Operator Determined Barring HPLMN data may map into one or more ANSI MAP
14 parameters as shown in Table 92.
6
15 The SS-Data List may map into one or more ANSI MAP parameters as shown in Table 92.
7
16 The SMS_OriginationRestrictions may map into one or more GSM MAP parameters as
17 shown in Table 92.
8
18 The SMS_TerminationRestrictions may map into one or more ANSI MAP parameters as
9
20 The CDMAServiceOptionList may map into one or more GSM MAP parameters (e.g., ADS
21 (9.6 kpps) to “CDA-9600 bps” BearerServiceCode; G3FAX to “FacsimileGroup3”
22 GSMTeleService; PacketDataService (PDS) to “dataPDS” BearerServiceCode).
3-97
X.S0023
1 Parameter Value Mapping
2 Table 93 through Table 104 shows the mapping of parameter values (more commonly referred
3 to as ASN.1 data types in GSM 09.02 [4] which the IIF shall perform based on the parameter
4 mapping shown in Table 92. If there is no direct mapping for parameter values, a ‘-‘ has been
5 entered in the corresponding table. The implication therefore, is that those services/features
6 and/or subscription options may not be available when roaming in either a GSM or ANSI-41
7 PLMN.
8 The ASN.1 data type encoding is specified in GSM 09.02 [4].
9 Table 93: Forwarding Information List to Calling Features Indicator Parameter Mapping
GSM_Forwarding Information List ANSI-41_Calling Features Indicator
SSCode FeatureActivityStatus
AllForwardingSS CFU + CFNA +CFB
CFU CFU
AllConditionalForwardingSS CFNA +CFB
CFB CFB
CFNRy CFNA1
CFNRc CFNA1
CD -
BasicService2 -
Refer to GSM 09.02 [4] for Basic Service

Codes
SSStatus FeatureActivityStatus
Q P R A3
0000 Not authorized

0 0 0 14 -
0 0 1 04 -
0 0 1 14 -
0100 Authorized but de-activated
0 1 0 14 -
0110 Authorized but de-activated
0111 Authorized and activated
1 0 0 04 -
1 0 0 14 -
1 0 1 04 -
1 0 1 14 -
1 1 0 04 -
1 1 0 14 -
1 1 1 04 -
3-98
X.S0023
1 Table 93: Forwarding Information List to Calling Features Indicator Parameter Mapping
2 (concluded)
GSM_Forwarding Information List ANSI-41_Calling Features Indicator
ForwardedToNumber -
E164 Address
ForwardedToSubaddress -
E164 Address
ForwardingOptions -
Notification to forwarding party
Notification to calling party
Forwarding reason
NoReplyConditionTime -
3
1
4 The ANSI-41 CFNA value maps to both GSM values CFNRc and CFNRy.
2
5 GSM allows call forwarding services to be operated on a per basic service group basis.
6 ANSI-41 on the other hand has no concept of basic service groups. Therefore, one or more
7 GSM basic services or basic service groups shall map to all basic services in ANSI-41.
3
8 The QPRA bits, refer to the Quiescent, Provisioned, Registered & Activation status of the
9 various call forwarding services e.g. QPRA = 0110 means that the status of that call
10 forwarding service is not quiescent, provisioned, registered, not active.
4
11 These combinations are not applicable to GSM Call Forwarding services.
3-99
X.S0023
1 Table 94: Regional Subscription Data to Geographic Authorization Parameter Mapping

GSM_Regional Subscription Data ANSI-41_Geographic Authorization
ZoneCode GeographicAuthorization
See GSM 09.02 [4] for definition of zone Authorized for all MarketIDs served by the
code1 VLR
Authorized for this MarketID only
Authorized for this MarketID and SwitchNo

only
Authorized for this locationAreaID within a

MarketID only
2
1
3 Based on the zone code, which identifies those regions or zones where a roaming is allowed,
4 these values may map to one or more values in the Geographic Authorization.
3-100
X.S0023
1 Table 95: Call Barring Information List to Origination Indicator Parameter Mapping
GSM_Call Barring Information List ANSI-41_Origination Indicator
SSCode Allowed Call Types
See Note (a) Prior Agreement
AllBarringSS1 Orignation denied
BarringOfOutgoingCalls1 Origination denied
BAOC1 Origination denied3
BOIC2 National long distance4
BOIC-exHC2 National long distance
BAOC Local calls only5
BAOC, BOIC, BOIC-exHC Selected leading digits of directory or of

international E.164 number6
BAOC,BOIC, BOIC-exHC Selected leading digits of directory number

or of international E.164 number and local
calls6
- International calls
- Single Directory number or international

E.164 number
BarringOfIncomingCalls -
BAIC -
BIC-Roam -
BAOC -
BasicService -
See GSM 09.02 [4] for Basic Service

codes
SSStatus -
QPRA
See GSM 09.02 [4] for SSStatus values

2
3-101
X.S0023
1 Note (a): If the origination indicator value received indicates ‘prior agreement’ this may map into
2 one or more GSM SS Codes depending on the agreement between roaming partners.
1,2
3 If the IIF receives any of these GSM SSCodes, they shall map to the same ANSI-41
4 allowed call type as shown in Table 95.
3
5 If the IIF receives the ANSI-41 allowed call type set to ‘origination denied’, this shall be
6 mapped as shown in Table 95.
4
7 If the IIF receives the ANSI-41 allowed call type set to ‘national long distance’, this shall be
8 mapped as shown in Table 95.
5
9 If the IIF receives the ANSI-41 allowed call type set to ‘local calls only’ this shall be mapped
10 as shown in Table 95.
6
11 If the IIF receives the ANSI-41 allowed call type as shown, this may be mapped to one or
12 more GSM SSCode values as shown in Table 95.
3-102
X.S0023
1 Table 96: SSData List to Calling Features Indicator Parameter Mapping

GSM_SSData List ANSI-41_Calling Features Indicator
SSCode FeatureActivityStatus
CW + CH CW
- CT
- VP
- CD
MPTY 3WC
Note (a) CNIROver
CLIR CNIR
CLIP CNIP2
CLIP CNIP1
- PCW
COLP -
COLR -
CNAP -
ECT -
CCBS-A -
CCBS-B -
AoCI -
AoCC -
UUS -
PLMNSpecific -
BasicService1 -

codes
2
3-103
X.S0023
2 Table 96: SSData List to Calling Features Indicator Parameter Mapping (concluded)
GSM_SSData List ANSI-41_Calling Features Indicator

SSStatus(need to map to SMSMo & MT FeatureActivityStatus
Restriction in ANSI)
QPRA
Not authorized
0000 -
0 0 0 12 -
0 0 1 02 -
0 0 1 12 Authorized but de-activated
0101 -
0 1 1 02 Authorized and activated
0111 -
1 0 0 02 -
1 0 0 12 -
1 0 1 02 -
1 0 1 12 -
1 1 0 02 -
1 1 0 12 -
1 1 1 02 -
1 1 1 12
CLIRestrictionOption3 Feature Activity Status
Permanent -
TemporaryDefaultRestricted Authorized and activated
TemporaryDefaultAllowed Authorized and deactivated
4
OverrideCategory Feature Activity Status
OverrideEnabled Authorized and activated
OverrideDisabled Authorized and deactivated
3
4 Note (a): There is no equivalent GSM SSCode value for CNIROver. The override restriction
5 capability in GSM is a subscription option whose value is reflected by the OverrideCategory
1
6 GSM allows supplementary services to be operated on a per basic service group basis.
7 ANSI-41 on the other hand has no concept of basic service groups. Therefore, one or
8 more GSM basic services or basic service groups shall map to all basic services in
9 ANSI-41.
2
10 These combinations are not applicable to the GSM supplementary services defined by their
11 SSCode in Table 96
3-104
X.S0023
3
1 The CLIRestriction option is equivalent to the ANSI-41 Feature Activity Status, CNIR. If the
2 CLIRestriction is temporary default restricted, this equates to the value ‘Authorized and
3 activated’ in the CNIR feature activity status. If the CLIRestriction is temporary default
4 allowed, this equates to the value ‘Authorized but deactivated’ in the CNIR feature activity
5 status. There is no equivalent in ANSI-41 to permanently restricted.
4
6 The GSM override category is equivalent to the ANSI-41 Feature Activity Status,
7 CNIROver. If the Override Category is enabled, this equates to the value ‘Authorized and
8 activated’ in the CNIROver feature activity status. If the Override Category is disabled, this
9 equates to the value ‘Authorized but deactivated’ in the CNIROver feature activity status.

11 Parameter Mapping
GSM_Operator determined barring (general) ANSI-41_Origination Indicator
ODB-General data Allowed Call Types
AllOG-callsBarred Origination denied
InternationalOGCalls Barred1 National long distance2
InternationalOGCallsNotToHPLMN- National long distance

CountryBarred1
InterzonalOGCallsBarred1 Selected leading digits of directory

number or of international E.164
number and local calls
InterzonalOGCallsNotToHPLMN- Selected leading digits of directory

CountryBarred1 number or of international E.164
InterzonalandInternationalOGCallsNotToHPL Selected leading digits of directory

MN-CountryBarred1 number or of international E.164
PremiumRateInformationOGCallsBarred1 Selected leading digits of directory

PremiumRateEntertainmentOGCallsBarred1 Selected leading digits of directory

12
3-105
X.S0023

2 Parameter Mapping (concluded)
GSM_Operator determined barring (general) ANSI-41_Origination Indicator

SSAccessBarred -
AllECTBarred -
ChargeableECTBarred -
InternationalECTBarred -
InterzonalECTBarred -
DoublyChargedECTBarred -
MultipleECTBarred
3
4 Note: The mapping shown in Table 97 applies in one direction only i.e. from GSM to ANSI-41.
5 The corresponding ANSI-41 values received by the IIF in “profile” macro parameter, it shall be
6 mapped according to Table 95.
1
7 If the IIF receives any of these GSM ODB general data, they shall map to the same ANSI-41
8 allowed call type as shown in Table 97.
10 Table 98: Operator Determined Barring HPLMN data to Origination Indicator Parameter
11 Mapping
GSM_Operator determined barring ANSI-41_Origination Indicator
(HPLMN)
ODB-HPLMN data Allowed Call Types
PLMN-SpecificBarringType1 -
12
13 Table 99: Operator Determined Barring HPLMN data to Restriction digits Parameter
14 Mapping
GSM_Operator determined barring ANSI-41_Restriction Digits
(HPLMN)
ODB-HPLMN data Type of Number
PLMN-SpecificBarringType1 -
3-106
X.S0023
2 Mapping
GSM_Call Barring Information List ANSI-41_SMS Origination Restrictions
SSCode Default
AllBarringSS -
BarringOfOutgoingCalls -
BAOC Block All
- Allow Specific
- Allow All
BOIC -
BOIC-exHC -
BAOC -
BAIC -
BIC-Roam -
- Direct
- Block Direct
- Allow Direct
- ForceMessageCenter
- Force Indirect
3
3-107
X.S0023
3 Mapping (concluded)
GSM_Call Barring Information List ANSI-41_SMS Origination Restrictions

BasicService -
codes
SSStatus -
QPRA
4
5 Table 101: Call Barring Information List to SMS Termination Restrictions Parameter
6 Mapping
GSM_Call Barring Information List ANSI-41_SMS Termination Restrictions
SSCode Default
AllBarringSS -
BAOC Block All
- Allow Specific
- Allow All
BOIC -
BOIC-exHC -
BAOC -
BAIC -
BIC-Roam -
- Reserve Charges
- Block Direct
- Allow Direct
BasicService
See GSM 09.02 [4] for Basic Service -
codes
SSStatus
QPRA -
7
3-108
X.S0023
1 Table 102: Call Barring Information List to Termination Restriction Code Parameter
2 Mapping
GSM_Call Barring Information List ANSI-41_Termination Restriction Code
SSCode Termination RC
AllBarringSS -
BAOC -
BOIC -
BOIC-exHC -
BAOC -
BAIC Termination denied
BIC-Roam -
- Unrestricted
BasicService -
codes
SSStatus -
QPRA
3
3-109
X.S0023
1 Table 103: SSData List to SMS Origination Restrictions Parameter Mapping

GSM_SSData List ANSI-41 SMS Origination Restrictions
SSCode -
See GSM 09.02 [4] for SS Codes
BasicService Default
See GSM 09.02 [4] for complete list of Block All1
Basic Services
SSStatus -
CLIRestrictionOption -
OverrideCategory -
2
1
3 In the case where the BasicService does not indicate that SMS is available, this shall be mapped to
4 ‘Block All’.
5 Table 104: SSData List to SMS Termination Restrictions Parameter Mapping

GSM_SSData List ANSI-41 SMS Termination Restrictions
SSCode -
See GSM 09.02 [4] for SS Codes
BasicService Default
See GSM 09.02 [4] for complete list of Block All1
Basic Services
SSStatus -
CLIRestrictionOption -
OverrideCategory -
1
6 In the case where the BasicService does not indicate that SMS is available, this shall be mapped to
7 ‘Block All’.
3-110
X.S0023
1 4.4.3 Error Handling

4 Subscriber Deletion
5 If the Subscriber Deletion procedure fails at an ANSI-41 VLR, the VLR shall respond by either
6 sending:
7
8 An ANSI_MAP_regcan in a TCAP RETURN RESULT indicating cancellation denied (CANDEN)
9 to the IIF, with one of the following reasons as defined in ANSI-41 [2]
10 Appropriate CANDEN Values in ANSI_MAP_regcan RETURN RESULT
CANDEN Value
Multiple access
Busy
11
12 The ANSI_MAP regcan may optionally indicate:
13 • CallHistoryCount
14 • ControlChannelData
15 • ReceivedSignalQuality
16 • SMS_MessageWaitingIndicator
17 • SystemAccessData
18 as defined in ANSI-41 [2]
19 Or, an ANSI_MAP regcan in a TCAP RETURN ERROR one of the following error codes as
21 Appropriate Error Codes in ANSI_MAP_regcan RETURN ERROR
Error Codes
UnrecognizedESN
OperationSequenceProblem
ResourceShortage
ParameterError
SystemFailure
22
23 The IIF is therefore responsible for mapping any errors it receives from the ANSI-41 VLR in the
24 ANSI_MAP regcan to an equivalent error in the GSM MAP
25 _CANCEL_LOCATION_RESPONSE towards the GSM HLR.
3-111
X.S0023
2 The GSM MAP _CANCEL_LOCATION_RESPONSE may include one the following ‘user’
3 errors as defined in GSM 09.02 [4]:
User Errors
unexpected data
value;
data missing;
6 The following ‘provider errors’ (protocol related errors) are also defined in GSM 09.02 [4]:
Provider Errors
mistyped parameter;
initiating release (i.e., the peer has

already initiated release of the dialogue
and the service has to be released);
9 If the Subscriber Deletion procedure fails at a GSM VLR, it returns a GSM MAP
10 _CANCEL_LOCATION_RESPONSE to the IIF, indicating an ‘user error’ as indicated above. The
11 IIF is therefore responsible for mapping any errors it receives into a corresponding error in the
12 ANSI_MAP regcan towards the ANSI-41 HLR. For further description of these errors and when
13 they are used, refer to either GSM 09.02 [4] or ANSI-41 [2].
14 The Location Registration provides the mapping of both user errors and provider errors in the
15 GSM MAP _CANCEL_LOCATION_RESPONSE to the equivalent value in either the CANDEN
16 parameter in the ANSI_MAP regcan RETURN RESULT or the RETURN ERROR.
17
3-112
X.S0023
1 Subscriber Data Modification
2 If the Subscriber Data Modification procedure fails at an ANSI-41 VLR, the VLR shall respond
3 by sending:-
4
5 An ANSI_MAP qualdir in a TCAP RETURN ERROR with one of the following reasons as
Provider Errors
mistyped parameter;
initiating release (i.e., the peer has

already initiated release of the dialogue
and the service has to be released);
9 The IIF is therefore responsible for mapping any errors it receives from the ANSI-41 VLR in the
10 ANSI_MAP qualdir to an equivalent error in the GSM MAP
11 _INSERT_SUBSCRIBER_DATA_RESPONSE or the GSM MAP
12 _DELETE_SUSBCRIBER_DATA_RESPONSE towards the GSM HLR.
13
14 The GSM MAP _INSERT_SUBSCRIBER_DATA_RESPONSE and the GSM

15 MAP_DELETE_SUBSCRIBER_DATA RESPONSE may include one the following ‘user’ errors
16 as defined in GSM 09.02 [4]:
User Errors
unidentified
subscriber;
data missing;
unexpected data
value.
18
3-113
X.S0023
1 The following ‘provider errors’ are also defined in GSM 09.02 [4]:
Provider Errors
mistyped parameter;
initiating release (i.e. the peer has

already initiated release of the
dialogue and the service has to be
released);
unexpected response from the

peer;
4 If the Subscriber Data Modification procedure fails at a GSM VLR, it returns either a GSM MAP
5 _INSERT_SUBSCRIBER_DATA_RESPONSE or a GSM MAP
6 _DELETE_SUBSCRIBER_DATA_RESPONSE to the IIF, indicating a ‘user error’ as indicated
7 above. The IIF is therefore responsible for mapping any errors it receives into a corresponding
8 error in the ANSI_MAP qualdir towards the ANSI-41 HLR. For further description of these
9 errors and when they are used, refer to either GSM 09.02 [4] or ANSI-41 [2].
10 Table 105 below provides the mapping of both user errors and provider errors in the GSM MAP
11 _INSERT_SUBSCRIBER_DATA_RESPONSE and GSM MAP
12 _DELETE_SUBSCRIBER_DATA_RESPONSE to the equivalent value in the ANSI_MAP
13 qualdir RETURN ERROR for ANSI-41 Foreign mode. Table 106 provides the mapping for GSM
14 Foreign mode.
3-114
X.S0023
1 Table 105: ISD_RESPONSE and DSD_RESPONSE to Qualdir Return Error Mapping

INSERT/DELETE_SUBSCRIBER_DATA_ Qualdir Return Error
RESPONSE (Errors)
Unidentified subscriber Unrecognized MSID
Data missing SystemFailure
Unexpected data value SystemFailure
Duplicated Invoke Id SystemFailure
Not supported service SystemFailure
Mistyped parameter SystemFailure
Resource limitation SystemFailure
Initiating release SystemFailure
Unexpected response from the peer SystemFailure
Service completion failure SystemFailure
No response from the peer SystemFailure
Invalid response received SystemFailure
2
3 Table 106: Qualdir Return Error to INSERT_SUBSCRIBER_DATA_RESPONSE and

4 DELETE_SUSBCRIBER_DATA_RESPONSE Error Mapping
Qualdir Return Error INSERT/DELETE_SUBSCRIBER_DATA_
RESPONSE (Errors)
Unrecognized MSID Unidentified subscriber
Unrecognized ESN Unexpected data value
ResourceShortage Unexpected data value
OperationNotSupported Unexpected data value
ParameterError Unexpected data value
SystemFailure Unexpected data value
UnrecognizedParameterValue Unexpected data value
Missing Parameter Data Missing
5
3-115
X.S0023
2 4.5 Short Message Procedures (ANSI-41 Network)

3
7 4.5.1 Short Message Service via CMT

8
9 The Short Message Service procedure is used to deliver short text messages to and from
10 mobile subscribers.
11

13
14 The following procedures are applicable at the IIF for Short Message Service. Mobile
15 Terminating SMS and Mobile Originated SMS using the CMT teleservice ID are described in
16 4.5.1.1.
17
18 4.5.1.1.1 Mobile Terminating SMS in GSM foreign mode

19
20 If the IIF receives an ANSI-41 Short Message Delivery Point to Point message from the home
21 Message Center, it shall check if the subscriber location is known and if the subscriber is active.
22 If both conditions are true, the IIF shall format and send a GSM_
23 MAP_FORWARD_SHORT_MESSAGE to the GSM MSC/VLR serving the mobile. Refer to
24 Table 109 for the mapping of parameters from ANSI_SMDPP to GSM MAP
25 _FORWARD_SHORT_MESSAGE.
26 If a successful response is received for the FSM, the IIF shall send a SMDPP Return Result
27 message to the home Message Center
28 If the subscriber’s location is not known, or if the subscriber is inactive or if the response to the
29 FSM indicates the short message was not delivered to the mobile, the IIF shall set the SMS
30 Delivery Pending flag for the subscriber. The IIF shall then send an SMDPP Return Result
31 message with an appropriate SMS_CauseCode value to the home MC. Refer to 4.5.1.3 Error
32 Handling for the values of SMS_CauseCode returned.
33 If errors are detected when the SMDPP is received, the message may be rejected if it cannot
34 be processed or if mandatory parameters are missing. Otherwise, the IIF shall send an SMDPP
35 Return Result message with the appropriate SMS_CauseCode value. Refer to 4.5.1.3 Error
36 Handling for the description of error conditions and corresponding SMS_CauseCode values.
3-116
X.S0023
1 If the response to FSM indicates a failure in the delivery of the short message, the IIF shall map
2 the cause value received to a corresponding SMS_CauseCode value in the SMDPP Return
3 Result, as described in Table 116.
4 If the response to FSM indicates that the receiving entity does not support MAP V2, the GSM
5 MAP_FORWARD_SHORT_MESSAGE is formatted in MAP V1 and sent again to the serving
6 MSC/VLR.
7 4.5.1.1.2 Alerting in GSM Foreign Mode

8
9 If the IIF receives a GSM MAP _READY_FOR-SHORT_MESSAGE (MAP V2) or a

10 GSM_UPDATE_LOCATION message, or a GSM MAP _NOTE_MS_PRESENT message (MAP
11 V1) and the Delivery pending flag is set for the subscriber, the IIF shall send an
12 ANSI_MAP_SMS_NOTIFICATION message to the home Message Center. The flag shall then
13 be cleared. The home MC shall re-send message SMDPP to deliver the short message to the
14 subscriber as described previously.
15 4.5.1.1.3 Mobile Terminating SMS in ANSI-41 Foreign Mode

16
17 If the IIF receives a GSM_FORWARD_SHORT_MESSAGE, it shall format and send an

18 ANSI_MAP Short Message Delivery Point to Point message to the serving TDMA MSC/VLR.
19 Refer to Table 110, Table 111 and Table 112 for the mapping of parameters from GSM MAP
20 _FORWARD_SHORT_MESSAGE to ANSI_SMDPP.
21 If the IIF receives a positive acknowledgment to the SMDPP message, it shall send a positive
22 acknowledgment to the Forward Short Message.
23 If the IIF receives a negative acknowledgment to the SMDPP message, it shall set the Mobile
24 Not Reachable flag for the subscriber and shall map the received SMS_CauseCode value into
25 a corresponding error code in the FSM Response message as described in Table 117.
26 If the IIF detects errors in the FORWARD_SHORT_MESSAGE, an error indication is sent in the
27 response message. This shall cause the GSM MSC/VLR to send an error indication to the GSM
28 HLR. Refer to 4.5.1.3 Error Handling for error detection on reception of FSM.
29 If a Return Error or Reject is received in response to the ANSI_MAP_SMSDPP INVOKE, the

30 error code is mapped into the corresponding Forward Short Message error code as described
31 in Table 117.
32 4.5.1.1.4 Alerting in ANSI--41 Foreign Mode

33
34 If the IIF receives an ANSI_MAP Registration Notification message or an ANSI_MAP SMS

35 Notification message, and the SMS Delivery Pending flag is set for a mobile subscriber, it shall
36 send a GSM MAP _READY_FOR-SHORT_MESSAGE (MAP V2) or a GSM MAP
37 _NOTE_MS_PRESENT message (MAP V1) to the GSM HLR. This shall cause the HLR to
38 send an indication to the GSM SMSC that shall trigger the re-sending of the Short message.
3-117
X.S0023
1 4.5.1.1.5 Mobile Originating SMS in GSM Foreign Mode

2
3 If the IIF receives a GSM_FORWARD_SHORT_MESSAGE for a mobile originated short

4 message, it shall format and send an ANSI_MAP_SMDPP message to the serving ANSI-41
5 Message Center. Refer to Table 114 for the mapping of parameters from GSM MAP
9 If the IIF receives a negative acknowledgment to the SMDPP message, it shall map the
10 received SMS_CauseCode value into a corresponding error code in the FSM Response
11 message as described in Table 117
13 response message. Refer to 4.5.1.3 for the handling of errors at the reception of FSM.
14 4.5.1.1.6 Mobile Originating SMS in ANSI-41 Foreign Mode

15
16 If the IIF receives an ANSI-SMDPP message from the Serving MSC, it shall format and send a
17 GSM MAP_FORWARD_SHORT_MESSAGE to the GSM Message Center of the subscriber.
18 Refer to Table 115 for the mapping of parameters from ANSI_SMDPP to GSM MAP
20 If a successful response is received for the FSM, the IIF shall send a SMDPP Return Result
21 message to the MSC/VLR.
23 be processed or if mandatory parameters are missing. Otherwise, the IIF shall send an SMDPP
26 If the response to FSM indicates that the receiving entity does not support MAP V2, the GSM
27 MAP_FORWARD_SHORT_MESSAGE is formatted in MAP V1 and sent again to the serving
28 MSC/VLR.
3-118
X.S0023

2

4
6 Short Message Service in accordance with the tables presented.
7 Table 107 shows the mapping between ANSI MAP messages and GSM MAP messages
8 related to Short Message Service in GSM Foreign Mode. Table 108 shows the mapping
9 between GSM MAP messages and ANSI MAP messages related to Short Message Service in
10 ANSI-41 Foreign Mode.
11 Table 107: Short Message Service in GSM Foreign Mode (for CMT) Message Mapping
ANSI MAP Messages GSM MAP Messages
SMDPP FORWARD_SHORT_MESSAGE
12
13 Table 108: Short Message Service in ANSI-41 Foreign Mode (for CMT) Message Mapping
FORWARD_SHORT_MESSAGE SMDPP
3-119
X.S0023

2 Table 109 through Table 115 show the mapping of parameters, which the IIF shall perform.
3 Table 109: SMDPP to MT_Forward Short Message Parameter Mapping for GSM Foreign
4 Mode
ANSI SMDPP Status GSM MT FSM Status
MSID O SM-RP-DA = IMSI M
Note 1
SMS_OriginalDestinationAddres O
s (= MSID) Note 1
SMS-Originating-Address (= MC O SM-RP-OA = IIF address in M
Address) international format. See 4.5.2.4
User Data Unit (in M SM-RP-UI M
SMS_Bearer_Data) See Table 111 and Table 112 for
details of encoding of this
parameter.
- More Messages to Send = no M

Note 2
5
6 Note 1: MSID and SMS_Original_Destination_Address should be the same.
7 Note 2: This parameter is only valid for MAP V2.
8 Table 110: MT_Forward Short Message to SMDPP Parameter Mapping for ANSI-41
9 Foreign Mode
GSM MT FSM Status ANSI SMDPP Status
SM-RP-DA= IMSI M MSID R
ESN O
SM-RP-UI M SMS Bearer Data M
See
Table 113 for encoding of this
parameter.
- SMS Teleservice Identifier set to M
value (= CMT)
SM-RP-OA (=SMS-SC Address) M SMSOriginating Address (= IIF R

Address) See 4.5.2.4
10
11 The IIF shall support the mapping of parameters in Forward Short Message in both MAP V1
12 and MAP V2. Encoding of parameter SM-RP-UI is different depending on the MAP version
13 being encoded in the message. The two following tables describe the coding for each version
14 of MAP.
3-120
X.S0023
2 Table 111 describes the setting of field values for parameter SM-RP-UI for MAP V2.
3 Table 111: SM-RP-UI in MT_FORWARD_SHORT_MESSAGE for MAP V2 Parameter Values

4 for GSM Foreign Mode
FIELD VALUE
Message Type Indicator Set to value “SMS-DELIVER”
More Messages to Send Set to value “No more messages are waiting for the MS
in this SC”
Reply Path Set to value “TP-Reply-Path is not set in this SMS-
DELIVER”
Status Report Indication Set to value “A status report is not requested”
Protocol Identifier Set to value “0”
Service Center Time Stamp Created by the IIF
User Data Length Number of characters
User Data If TDMA CMT, the IS-136 SMS message (parameter
User Data) converted to the GSM default alphabet,
unless it is sent as an 8-bit data. Truncate message
length if longer than 134 octets (152 characters).
IIf CDMA CMT, the IS-95 SMS message (parameter
User Data) converted to the GSM default alphabet,
unless it is sent as an 8-bit data. Truncate message
length if longer than 134 octets (152 characters) (only
MAP V2). Truncate message length if longer than 134
octets (152 characters) for MAP V2 (160 characters for
MAP V1).
Originating Address The address of the original SME. Use the value received
in parameter SMS Original Originating Address in
SMDPP.
Data Coding Scheme - Set bit numbers 7, 6, 5, 4 to data coding (value 1111).
Set bit number 3 to 0.
- Set bit 2 to value default alphabet if received

parameter Encoder Identifier has value “IRA” or “Latin-
1, otherwise set to value “8-bit”.
- Set bit numbers 1&0 to value “Class 0” if received
parameter Urgency Indicator has value “Very Urgent”,
otherwise set to value “Class 1”.
5
3-121
X.S0023
1 The following table describes the setting of field values for parameter SM-RP-UI for MAP V1.

3 Encoding for GSM Foreign Mode
FIELD VALUE
Message Type Indicator Set to value “SMS-DELIVER”
More Messages to Send Set to value “No more messages are waiting for the MS
in this SC”
Protocol Identifier Set to value “0”
Service Center Time Stamp Created by the IIF
User Data Length Number of characters
User Data
Originating Address The address of the original SME. Use the value received
in parameter SMS Original Originating Address in
SMDPP.
Data Coding Scheme Use the coding value “default alphabet”
3-122
X.S0023
1 Table 113: SMS_Bearer Data in Mobile Terminating SMDPP Parameter Encoding for
FIELD VALUE
Message type indicator (M) 000 “SMS Deliver”
Message Reference (M) created by IIF
Privacy Indicator (M) 000 “Not restricted”
Urgency Indicator (M) 11 “Very urgent” if class 0 coded in the TP-DCS received,
01 “Normal” otherwise.
Delivery ack request (M) Set to value “Delivery acknowledge prohibited”
Manual ack request (M) Set to value “Manual acknowledge prohibited”
Message Updating (M) 1 “new”
Validity (M) 000 “indefinite”
Display time (M) 01 “Default”
User Data Unit (M) Encoding Identifier: 00001 “IRA”
Length Modifier: 0
User Data Structure Type: 00
User Data: GSM User Data from SM-RP-UI translated to
the IS-136 IRA alphabet
If CDMA CMT:
Encoding Identifier: possible values are
unspecified, IS-91 EPM, 7-bit ASCII, and IA5
MSG_ENCODING: Set to 7-bit ASCII if received

message is in GSM default alphabet, otherwise set to
Octet, unspecified.
MST:omitted
NUM_FIELDS: Number of characters
CHARi: GSM SMS message. If encoding identifier

has value 7-bit ASCII (ANSI X3.4), translate GSM
SMS message to the 7-bit ASCII alphabet.
3-123
X.S0023

3 in GSM Foreign Mode
GSM Forward Short Message Status ANSI SMDPP Status
Note 1 ESN O
Note 1 MSID O
SMS Teleservice ID = CMT M
SMS_Originating Address (=IIF O
Address)
SM-RP-OA (A-MSISDN) M SMS_Original Originating R
Note 1 Address (= A-MSID)
SMS_Original O
DestinationAddress Sub
Address (not sent)
SM-RP-UI: TP-Destination M SMS_Original Destination R
address (B-MSISDN) Address
SMS_Original Originating O
Address Sub Address (not sent)
SMS_Charge Indicator (not sent) O
SMS_Message Count (not sent) O
SMS_Notification Indicator (not O
sent)
SM-RP-DA (IIF Address) M SMS_Destination Address (= MC R
address retrieved from mapping
in database) See 4.5.2.4
SM-RP-UI M SMS Bearer Data M
TP-Message-Type-Indicator TP-Message-Type-Indicator
TP-Reject-Duplicates (ignored)
TP-Validity-Period TP-Validity-Period
TP-Validity-Period-Format
TP-Reply-Path (ignored) TP-Delivery-Ack-Request
TP-User-Data-Header-Indicator (=prohibit)
(ignored)
TP-Status-Report-Request
(ignored)
TP-Message-Reference TP-Message-Reference
TP-Protocol-Identifier (ignored)
TP-Data-Coding-Scheme TP-Urgent-Indicator
TP-User-Data-Length TP-User-Data-Unit
4
3-124
X.S0023

2 in GSM Foreign Mode (concluded)
GSM Forward Short Message Status ANSI SMDPP Status

TP-User-Data
TP-Privacy_indicator (=not
restricted)
TP-Manual-Ack-Request
(=prohibit)
TP-Message-Updating (=do not
overwrite)
TP-Deferred-Delivery-Time (=not
set)
TP-Call-Back-Number (=not set)
TP-Call-Back-Number-
Presentation-Indicator (=not set)
TP-Call-Back-Number-Alpha-Tag
(=not set)
TP-Multilingual-Call-Back-
Number (=not set)
TP-Multilingual-Call-Back-
Number-Alpha (=not set)
TP-Multilingual-Destination-
Address (=not set)
4 Note 1: MSID and ESN are supplied based on MSISDN received in SM-RP-OA
3-125
X.S0023

2 SMS in ANSI-41 Foreign Mode
ANSI SMDPP Status GSM Forward Short Message Status
SMS Teleservice ID M -
ESN O -
MSID O -
SMS_Charge Indicator O -
SMS_Message Count O -
SMS_Notification Indicator O -
SMS_Destination Address (IIF O SM-RP-DA: SC Address M
Address) (retrieved from mapping in IIF
database) see 4.5.2.4
SMS_Original Destination O TP_Destination-Address within M
Address (B-MSISDN) SM-RP-UI
SMS_Original Destination Sub O -
Address
SMS_Originating Address O -
SMS_Original Originating O SM-RP-OA: A-MSISDN M
Address (A-MSID)
SMS_Original Originating Sub O -
Address
SMS Bearer Data M SM-RP-UI M
- TP-Message-Type- - TP-Message-Type-
Indicator Indicator
- - TP-Reject-Duplicates
=TRUE
- TP-Validity-Period - TP-Validity-Period
- - TP-Validity-Period-Format
- - TP-Reply-Path = NOT-
- SET
- TP-User-Data-Header-
Indicator=NO-HEADER
- TP-Message-Reference - TP-Status-Report-
- Request=NO
- TP-Message-Reference
- TP-User-Data-Unit - TP-Protocol-Identifier = 0
TP-Urgent-Indicator - TP-Data-Coding-Scheme
TP-User-Data-Length
- TP-Delivery-Ack-Request TP-User-Data
(ignored)
3
3-126
X.S0023
1
3 SMS in ANSI-41 Foreign Mode (concluded)
ANSI SMDPP Status GSM Forward Short Message Status
- TP-Privacy_Indicator \
(ignored)
- TP-Manual-Ack-Request
(ignored)
- TP-Message-Updating
(ignored)
- TP-Deferred-Delivery-
Time (ignored)
- TP-Call-Back-Number
(ignored)
- TP-Call-Back-Number-
Presentation-Indicator
(ignored)
- TP-Call-Back-Number-
Alpha-Tag (ignored)
- TP-Multilingual-Call-
Back-Number (ignored)
- TP-Multilingual-Call-
Back-Number-Alpha
(ignored)
TP-Multilingual-Destination-
Address (ignored)
- User Data
MSG_ENCODING: For
CDMA, possible values are
unspecified, IS-91 EPM, 7-bit
ASCII, and IA5.
MST:Message type IS-95
or IS-136 is used
NUM_FIELDS: Number
of characters. Messages
above GSM limit will be
truncated.
CHARi: IS-95 or IS-136
SMS message itself
3-127
X.S0023

3
4 Error handling at the reception of a Forward Short Message in the IIF
6 1. If a mandatory parameter is missing (MAP V2), a Forward Short Message Response

7 with the indication “Data Missing” is sent back to the SMS-GMSC.
8 2. If a mandatory parameter is missing (MAP V1), a Forward Short Message Response

9 with the indication “Mistyped Parameter” is sent back to the SMS-GMSC.
10 3. A Forward Short Message Response with the problem code “Mistyped Parameter” is
11 sent in the following cases:
12 • A parameter tag is not one of those associated with the operation.
13 • The received value is not a value of the type associated with the operation.
14 • Erroneous tag and length information.
15 • Exceeding of the defined size of an ASN.1 module.
16 4. If the SM-RP-DA parameter does not have an IMSI number, a Forward Short Message
17 Response with the indication “Unexpected Data Value” is sent back to the SMS-GMSC.
18 5. If the SM-RP-OA parameter does not have a SC, a Forward Short Message Response
19 with the indication “Unexpected Data Value” is sent back to the SMS-GMSC.
20 6. If the subscriber is not connected in the IIF or if the profile is not available, Forward
21 Short Message Response with the indication “Unidentified Subscriber” is sent back to
22 the SMS-GMSC.
23 7. If location is unknown or inactive, send back to the SMS-GMSC a Forward Short

24 Message Response message with the indication “Absent Subscriber”.
25 8. If the subscriber has an ANSI SMS termination restriction, a Forward Short Message
26 Response message with indication “Facility Not Supported” is sent back to the SMS-
27 GMSC.
28 9. If the short message contents could not be extracted from the SM-RP-UI parameter, send
29 back to the SMS-GMSC a Forward Short Message Response message with the
30 indication “System Failure”.
3-128
X.S0023
2 Error Handling at the Reception of ANSI-41 SMDPP
4 1. If the subscriber is not connected in the IIF then a SMDPP RR with cause code “SMS
5 Termination Denied” is returned.
6 If the ESN received does not match stored ESN then a SMDPP RR with cause code
7 “SMS Termination Denied” or “Address Translation Failure” is returned.
8 When the SMSNotification Indicator: “Notify when available” is not set, and the MS is
9 inactive or the subscriber’s location is unknown, a SMDPP RR with one of the following
10 cause codes is returned:
11
12 • “SMS Termination Denied”
13 • “Destination Out of Service”
14 • “No page response”
15 • “Destination no longer at this address”
16 When the SMSNotification Indicator: “Notify when available” is set, and the MS is
17 inactive or the subscribers location is unknown then a SMDPP RR with cause code
18 “SMS Delivery Postponed” is returned.
19 If the subscriber does not have SMS service then a SMDPP RR with cause code “SMS
20 Termination Denied” is returned.
21 2. If a SMDPP Invoke arrives at the IIF WITH A Teleservice ID that is not supported by the
22 IIF, then it shall return a SMDPP RR with cause code “Invalid Teleservice ID”.
23 3. If a mandatory parameter is missing or if the MSID parameter is missing, a SMDPP RR

24 with cause code “Missing mandatory parameter” is returned.
25 4. If the subscriber’s profile is not available, a SMDPP RR with cause code “Destination No
26 Longer at this Address” is returned.
27 5. If the GSM MSC/VLR is on a Barring List, a SMDPP RR with cause code “SMS Delivery
28 Postponed” “SMS Termination Denied” is returned.
29 6. If any other error is detected, a SMDPP RR with cause code “Network Failure” is returned.
30 Note: The IIF should not use “SMS Delivery Postponed” if the ANSI-41 MC indicates that it
31 doesn’t require notification, or the IIF doesn’t set the delivery pending flag.
32
3-129
X.S0023
1 Error Mapping from GSM FSM to ANSI SMDPP to support Mobile Terminating SMS in
2 GSM Foreign and Mobile Originating SMS in ANSI-41 Foreign Mode
3 Table 116: Forward_Short_Message to SMS_CauseCode Values in SMDPP Return Result

4 Error Mapping
GSM FORWARD_SHORT_MESSAGE ANSI SMDPP Return Result SMS-
RESPONSE CauseCode Value
Absent Subscriber SMS Delivery Postponed OR
No Page Response
Subscriber Busy for MT SMS SMS Delivery Postponed OR
Destination Busy
Memory Capacity exceeded Destination resource shortage
System Failure Other network problem OR Network failure
DataMissing Other general problem OR
Missing Mandatory Parameter
UnexpectedDataValue Encoding problem OR
Unexpected Parameter value
FacilityNotSupported SMS not supported
Unknown Subscriber Address translation failure
Illegal Subscriber Address translation failure OR
SMS termination denied
SM-DeliveryFailure Other radio interface problem OR
cause: Equipment Protocol Error No Acknowledgement
SM-DeliveryFailure Other terminal problem OR

cause: Equipment Not SM-Equipped No Acknowledgement
SM-DeliveryFailure cause: unknownSC Address translation failure

SM-DeliveryFailure cause: SC-Congestion Network resource shortage OR
No Acknowledgement
SM-DeliveryFailure cause: invalid SME- Address translation failure OR
Addr No Acknowledgement
SM-DeliveryFailure SMS origination denied OR
cause: subscriberNotSC-Subscriber No Acknowledgement
Absent Subscriber SM No acknowledgment OR
No page response
Encoding Error Network Failure
Unidentified Subscriber Address Vacant
Illegal Equipment Other General Problems

Any other error Network Failure
5
6 Note: Unidentified Subscriber and Illegal Equipment may be treated as Any Other Error and
7 may be mapped to Network failure.
3-130
X.S0023
2 Error Mapping from ANSI SMSDPP to GSM FSM to support Mobile Terminating SMS in
3 ANSI-41 Foreign Mode and Mobile Originated SMS in GSM Foreign Mode
4 Table 117: SMDPP to Forward_Short_Message Error Mapping

SMSDPP (Cause Code) FORWARD_SHORT_MESSAGE
Response
Destination Busy Subscriber Busy for MT-SMS
Address Vacant Absent Subscriber
No Page Response Absent Subscriber
No Acknowledgement Absent Subscriber
Destination Out of Service Absent Subscriber
Destination No Longer at this Address Absent Subscriber
SMS not supported FacilityNotSupported
Destination resource shortage SM-DeliveryFailure with cause

“MemoryCapacityExceeded”
Other radio interface problem SM-DeliveryFailure with cause
“equipmentProtocolError”
Unrecognized parameter value or SM-DeliveryFailure with cause
Encoding problem “equipmentProtocolError”
Radio interface incompatibility or Other SM-DeliveryFailure with cause
terminal problems “equipmentProtocolError”
SMS Delivery Postponed Absent Subscriber OR System Failure
Any other value System Failure
3-131
X.S0023
1 4.5.2 Short Message Service via GHOST or WEMT

2

4
5 SMS Alert Procedure
6 The SMS Alert procedure is used for alerting the SMSC when the mobile subscriber is active
7 and available for short messaging after a short message transfer has failed because the mobile
8 subscriber is not reachable or when the Mobile Station (MS) has indicated that it has no
9 memory capacity to accept a short message.
10 4.5.2.1.1 Alerting for an ANSI-41 Subscriber in GSM Foreign Mode

11
12 IIF Receiving a READY_FOR_SM
13 Upon receipt of a READY_FOR_SM message, the IIF shall store the originating Visited MSC
14 (VMSC) address in the subscriber’s profile and Invoke ID. It shall map the
15 GSM_READY_FOR_SM message to the ANSI_SMSNOT INVOKE message as described in
16 Table 119.
17 It shall populate the SMS_Address parameter with the IIF address. All other parameters are
18 ignored.
19 The ANSI_SMSNOT INVOKE is then transmitted to the subscriber’s SMSC with local
20 Transaction ID. Finally, the IIF shall return a READY_FOR_SM_ACK message with no
21 arguments to the originating VMSC.
22
23 IIF Receiving a SMSNOT RETURN RESULT
24 Upon receipt of a SMSNOT RR message, the IIF shall associate the SMSNOT Transaction ID
25 with the Invoke ID.
26 4.5.2.1.2 Alerting for a GSM Subscriber in ANSI-41 Foreign Mode

27
28 IIF Receiving a SMSNOT INVOKE
29 Upon receipt of a SMSNOT message, the IIF shall store the originating VMSC address and
30 Transaction ID. The IIF shall map the ANSI_SMSNOT message to the
31 GSM_READY_FOR_SM. The parameters shall be mapped as described in Table 120.
32 The GSM_READY_FOR_SM is transmitted to the subscriber’s HLR with local Invoke ID.
33 Finally, the IIF shall return a SMSNOT RR to the originating VMSC.
3-132
X.S0023
1 IIF Receiving a REGNOT INVOKE
2 Alternatively, the IIF may receive a REGNOT message indicating an update in location of the
3 MS. Upon receipt of the REGNOT message, the IIF shall determine if the SMS Delivery
4 Pending Flag is set. If the DPF is not set, the IIF follow normal procedures according to 4.1.1
5 Location Registration. If the DPF is set, the IIF shall store the originating VMSC address
6 and Transaction ID. The IIF shall create a GSM_READY_FOR_SM.
7 The content of the MSID is mapped to the equivalent IMSI and place in the IMSI parameter.
8 The Alert Reason parameter is populated with the value - MS Present. All other parameters
9 are ignored.
10 The GSM_READY_FOR_SM is transmitted to the subscriber’s HLR with local Invoke ID. .
11 Finally, the IIF shall return a REGNOT RR to the originating VMSC.
12 IIF Receiving a GSM_READY_FOR_SM_ACK
13 Upon receipt of a GSM_READY_FOR_SM_ACK message, the IIF shall associate the

14 GSM_READY_FOR_SM_ACK Invoke ID with Transaction ID.
15 4.5.2.1.3 SMS Delivery for an ANSI--41 Subscriber in GSM Foreign Mode

16
17 IIF Receiving SMSDeliveryPointToPoint INVOKE
18 Upon receipt of an SMSDeliveryPointToPoint INVOKE message, the IIF shall store the
19 originating MC address and transaction ID. It shall map the ANSI_SMDPP message into a
20 GSM_FSM message and populate the subscriber’s known VMSC into the DPC. The mapping
21 of parameters is described in Table 121.
22 The IIF transmits the GSM_FSM message with local Invoke ID.
23 IIF Receiving FORWARD_SHORT_MESSAGE_ACK
24 Upon receipt of the FORWARD_SHORT_MESSAGE_ACK message, the IIF shall associate the
25 Invoke ID with SMDPP transaction ID and map the GSM_FSM_ACK message into an
26 ANSI_SMDPP RETURN RESULT.
27 Next, it populates the stored originating SMSC address into the DPC and populates the
28 transaction ID.
29 If the User Error parameter is populated in the GSM_FSM_ACK, then map this value into the
30 SMS_CauseCode according to Table 116.
31 Finally, the ANSI_SMDPP RR is transmitted to the originating SMSC.
3-133
X.S0023
1 4.5.2.1.4 SMS Delivery for a GSM Subscriber in ANSI-41 Foreign Mode

2
3 IIF Receiving MT_FORWARD_SHORT_MESSAGE
4 Upon receipt of the MT_FORWARD_SHORT_MESSAGE message, the IIF shall store the
5 originating SMSC address and Invoke ID. It shall map the GSM_FSM message into an
6 ANSI_SMDPP INVOKE message and populate the subscriber’s known VMSC into the DPC.
7 The mapping of parameters is described in Table 122.
8 The IIF transmits the ANSI_SMDPP INVOKE message with local transaction ID
9 IIF Receiving SMDPP RETURN RESULT
10 Upon receipt of a SMSDeliveryPointToPoint RR message, the IIF shall associate the SMDPP
11 transaction ID with Invoke ID and map the ANSI_SMDPP RR to GSM_FSM_ACK.
12 Next, it populates the stored originating SMSC address and Invoke ID. If the SMS_CauseCode
13 parameter is populated in the ANSI_SMDPP RR message, then map value into User error
14 parameter according to Table 117.
15 Finally, transmit the GSM_FSM_ACK to the originating SMSC.
16 4.5.2.1.5 SMS Origination for an ANSI-41 Subscriber in GSM Foreign Mode

17
18 IIF Receiving MO_FORWARD_SHORT_MESSAGE
19 Upon receipt of a MO_FORWARD_SHORT_MESSAGE, the IIF shall store the address of the
20 originating VMSC and Invoke ID. It shall map the GSM_MO_FSM to ANSI_SMDPP INVOKE.
21 The address of the subscriber’s TSA (from the SM RP DA – Service Center Address) is
22 mapped according to 4.5.2.4 into the SMS_DestinationAddress. The mapping of parameters is
24 The IIF transmits the ANSI_SMDPP INVOKE message with local transaction ID.
25 IIF Receiving SMDPP RETURN RESULT
27 transaction ID with Invoke ID and map the ANSI_SMDPP RR to the GSM_FSM_ACK.
28 Next, it populates the stored originating SMSC address and Invoke ID. If SMS_CauseCode
31 Finally, transmit the GSM_FSM_ACK to the originating VMSC.
3-134
X.S0023
1 4.5.2.1.6 SMS Origination for a GSM Subscriber in ANSI-41 Foreign Mode

2
3 IIF Receiving SMSDeliveryPointToPoint INVOKE
4 Upon receipt of an SMSDeliveryPointToPoint INVOKE message, the IIF shall store the address
5 of the originating VMSC and Transaction ID and map the ANSI_SMDPP INVOKE to the
6 GSM_MO_FSM. The mapping of parameters is described in Table 124.
8 IIF Receiving FORWARD_SHORT_MESSAGE_ACK
10 Invoke ID with SMDPP transaction ID. The GSM_FSM_ACK message is mapped into an
12 Next, it populates the stored originating SMSC address and transaction ID. If the User Error
13 parameter is populated in GSM_FSM_ACK, then this value is mapped into the
14 SMS_CauseCode according to Table 116.
15 Finally, transmit the ANSI_SMDPP RR to the originating VMSC.

17
19 Short Message Service in accordance with the tables presented next.

21
22 Table 118: Short Message Service (for GHOST or WEMT) Message Mapping
SMSNOT READY_FOR_SM
SMDPP FORWARD_SHORT_MESSAGE
3-135
X.S0023

2
3 The mapping of the GSM MAP _READY_FOR_SM message to the ANSI_SMSNOT message
4 is per Table 119.
5 Table 119: Alerting for an ANSI-41 Subscriber in GSM Foreign Mode Parameter Mapping
GSM MAP _READY_FOR_SM Status ANSI_SMSNOT Status
IMSI M ESN M
MSID M
Alert Reason (MS present or M -
Memory Available)
SMS_Address (IIF Address) R
6
7 The mapping of the ANSI_SMSNOT message to the GSM MAP _READY_FOR_SM message
8 is per Table 120.
9 Table 120: Alerting for a GSM Subscriber in ANSI-41 Foreign Mode Parameter Mapping
ANSI_SMSNOT Status GSM MAP _READY_FOR_SM Status
ESN M IMSI R
MSID M
SMS_Address (Serving MSC) O -
Alert Reason (MS present) M
10
3-136
X.S0023
1 4.5.2.2.3 SMS Delivery for an ANSI-41 Subscriber in GSM Foreign Mode

2
3 When the IIF receives an SMDPP Invoke from an ANSI-41 SMSC for an ANSI-41 MS roaming
4 in a GSM network, it stores the Originating MC address, converts the SMDPP to a MAP_FSM,
5 replaces the Originating Address by the address of the IIF, and sends the message to the
6 serving GSM MSC. Upon receipt of the MAP_FSM_ACK from the serving MSC, the IIF
7 converts the message to an SMDPP Return Result, replaces the Originating Address with its
8 own address and replaces the Destination Address with the previously stored address of the
9 ANSI-41 SMSC. See Table 121.
10 Table 121: SMDPP to Forward Short Message for Mobile Terminated GHOST/WEMT
11 Teleservice Parameter Mapping in GSM Foreign Mode
SMDPP Status MT FSM Status
SMS Teleservice ID =GHOST or M -
WEMT
ESN O -
MSID (Note 1) O SM-RP-DA = IMSI M
SMS_OriginalDestinationAddres O
s (= MSID) (Note 1)
SMS_ChargeIndicator O -
SMS_DestinationAddress O -
SMS_MessageCount O -
SMS_NotificationIndicator O -
SMS_OriginalDestinationSub O -
Address
SMS_Original Originating O -
Address
Address Sub Address
SMS_Originating Address (= MC O SM-RP-OA (set to IIF address) M
Address) See 4.5.2.4
12
13 Note 1: MSID and SMS-Original-Destination Address should be the same
14
3-137
X.S0023
1 4.5.2.2.4 SMS Delivery for a GSM Subscriber in ANSI-41 Foreign Mode

2
3 When the IIF receives a MAP_FSM destined for an MS roaming in an ANSI-136/41 network, it
4 stores the originating Service Center address locally, and replaces the Service Center Address
5 in the outgoing SMDPP message by E.164 address of the IIF. Upon receipt of an SMDPP
6 Return Result from the serving ANSI-136/41 MSC, the IIF converts it to a MAP_FSM_ACK, and
7 places the previously stored Originating Service Center address in the Destination Address.
8 See Table 122.
9 Table 122: Forward Short Message to SMDPP for Mobile Terminated GHOST/WEMT
10 Teleservice Parameter Mapping in ANSI Foreign Mode
MT FSM Status SMDPP Status
SM-RP-DA = M MSID R
IMSI
SMS-Original_Destination- O
Address = MSID
SM-RP-OA = M SMS_Originating Address = IIF O
Service center address OA Address . See 4.5.2.4
SM-RP-UI M SMS_BearerData M
- SMS_Teleservice Identifier = M
GHOST or WEMT
More Messages to Send C - -
ESN (Not used)
SMS_Charge Indicator (Not
used)
SMS_Destination Address (Not
used)
SMS_Message Count (Not used)
SMS_Notification Indicator (Not
used)
SMS_Original Originating
Address (Not used)
SMS_OriginalDestinationAddres
s (Not used)
11
3-138
X.S0023
1 4.5.2.2.5 SMS Origination for an ANSI-41 Subscriber in GSM Foreign Mode

2
3 When the IIF receives a MAP_FSM originated from a MS roaming in a GSM network, it stores
4 the VMSC address locally and replaces the VMSC address in the outgoing SMDPP message
5 by the E.164 address of the IIF (placed in the SCCP Calling Party Address). Upon receipt of an
6 SMDPP Return Result from the MC, the IIF converts it to a MAP_FSM_ACK and places the
7 previously stored VMSC address in the SCCP Called Party Address. See Table 123.
8 Table 123: Forward Short Message to SMDPP for Mobile Originated GHOST/WEMT in
9 GSM Foreign Mode Parameter Mapping
GSM MO FSM Status ANSI SMDPP Status
SM-RP-DA = M SMS_DestinationAddress= MC R
Service Center Address DA = IIF Address. See 4.5.2.4
Address
SM-RP-OA = M SMS_OriginalOriginating Address R
A-MSISDN Note 1 =A-MSID
SM-RP-UI M SMS_BearerData M
- SMS_Teleservice Identifier = M
GHOST or WEMT (Set by IIF)
- SMS_Originating Address (Set to O
IIF address)
- Note 1 MSID O
- Note 1 ESN O
- SMS_Charge Indicator (Not used)
- SMS_Message Count (Not used)
- SMS_Notification Indicator (Not
used)
- SMS_OriginalDestinationAddress
(Not used)
SMS_Original Destination Sub

- Address (Not used)
- SMS_Original Originating
Address Sub Address (Not used)
10
11 Note 1: MSID and ESN are mapped from MSISDN received in SM-RP-OA
12
3-139
X.S0023
1 4.5.2.2.6 SMS Origination for a GSM Subscriber in ANSI-41 Foreign Mode

2
3 When the IIF receives a SMDPP Invoke originated from a MS roaming in an ANSI-41 network,
4 it stores the VMSC address locally and replaces the VMSC address in the outgoing MT FSM
5 message by the E.164 address of the IIF (placed in the SCCP Calling Party Address). It also
6 internally maps the TSAF from the SMS_Destination Address into the TSAH and places that
7 value in the RP-Destination Address per 4.5.2.4 Identification of the IIF SS7 Address for
8 Mobile Originated Services. Upon receipt of a MAP_FSM_ACK from the MC, the IIF converts it
9 to a SMDPP Return Result and places the previously stored VMSC address in the SCCP
10 Called Party Address. See Table 124.
11 Table 124: SMDPP to Forward Short Message for Mobile Originated GHOST/WEMT
12 Teleservice Parameter Mapping in ANSI-41 Foreign Mode
ANSI SMDPP Status GSM MO FSM Status
SMS Teleservice ID =GHOST or M -
WEMT
ESN O -
MSID O -
(Note 1)
SMS_Charge Indicator O -
SMS_Destination Address O SM-RP-DA: Service Center M
Address (retrieved from mapping
in IIF database). See 4.5.2.4
SMS_Message Count O -
SMS_Notification Indicator O -
SMS_Original Destination O -
Address
SMS_Original Destination Sub O -
Address
SMS_Original Originating O SM-RP-OA (A-MSISDN) M
Address
(A-MSID)
Address Sub Address
SMS_Originating Address O -
13 Note 1: If MSID is received it should be the same as the SMS_OriginalOriginating Address
14
3-140
X.S0023
1 GHOST shall use the HLPI shown below. TSAR may or may not be applied to the GHOST
2 teleservice.
3 Table 125: HLPI for GHOST

HLPI Subfield Coding
Teleservice Type Indicator Subfield
0 - Standardized Teleservice
Teleservice Segmentation and May or may not have TSAR sub-layer
Reassembly Subfield
0 - No TSAR
1 - TSAR is being used

Teleservice Protocol Identifier Subfield
000111
4
6 4.5.2.3.1 Error handling at the reception of a Forward Short Message in the IIF
7 Refer to 4.5.1.3 Error Handling
8 4.5.2.3.2 Error handling at the reception of a SMDPP message in the IIF

10 4.5.2.3.3 Cause Code Mapping at the IIF

11
12 At the IIF, the ANSI-41 SMS_CauseCode is mapped to a return error in the GSM
13 MAP_FSM_ACK message according to Table 117
14 The IIF is responsible for mapping GSM MAP_FSM_ACK Return Errors to ANSI-41
15 SMS_CauseCodes according to Table 116.
16
3-141
X.S0023
1 4.5.2.4 Identification of the IIF SS7 Address for Mobile Originated Services
2 The following SS7 address mapping scheme is defined in order to resolve the ambiguity that
3 occurs when a roaming subscriber attempts to invoke mobile originated teleservices.
4 Specifically, instead of using only a single Teleservice Server Address (TSA) as the SS7 SCCP
5 Called Party Address, a pair of E.164 addresses are defined for each Teleservice Server
6 Address Center (e.g., MC or SMSC). This pair of addresses (native and foreign mode TSAs) is
7 used to enable the routing of incoming messages to the IIF from the serving foreign network,
8 while messages that originate in a network that uses the same technology as the home network
9 bypass the IIF and are routed directly to the MC. The native mode address can be translated
10 using global title translation to the actual SS7 address (DPC and SSN) of the MC while the
11 foreign mode address is a virtual address that points (via global title translation) to the IIF.
12 There is a one-to-one mapping in the IIF between the home and foreign mode addresses for
13 each MC, as shown in Table 126. Note that there is a many-to-one relationship between the
14 virtual addresses and the actual IIF address.
15 While roaming in foreign mode, the mobile station uses the foreign mode address in order to
16 ensure that messages are first routed to the IIF. The IIF performs message translation, and
17 inserts the native mode address, i.e., an E.164 number that is translatable by the network to the
18 actual MC destination SS7 address.
19 Table 126: Teleservice Server Address Mapping in IIF

Home Technology Address Foreign Technology Address
TSAH1 ↔ TSAF1
TSAH2 ↔ TSAF2
TSAH3 ↔ TSAF3
20
21 4.5.3 Message Waiting Notification

22 The Message Waiting Notification procedure is used to notify a mobile subscriber of voice mail
23 messages added or removed in his voice mail system.

25 The following procedures are applicable at the IIF for Message Waiting Notification.
26 GSM Foreign Mode
27 Two events can trigger the sending of updated MWN information by the IIF to the serving GSM
28 MSC/VLR, when an ANSI-41 native subscriber is roaming in GSM Foreign Mode.
29 4.5.3.1.1 Registration Notification Return Result with MWN Information Received

30 When the ANSI-41 native subscriber registers in a GSM MSC/VLR, a GSM
31 MAP_UPDATE_LOCATION message is received at the IIF. This shall trigger an ANSI MAP
32 REGISTRATION_NOTIFICATION message to be sent by the IIF to the ANSI-41 home HLR.
33 If the IIF receives a Registration Notification Return Result message with MWNCOUNT and
34 MWNTYPE parameters set to valid values, it shall set the Message Waiting Notification flag
35 and it shall send a GSM MAP_INSERT_SUB_DATA message(s) to the GSM MSC/VLR from
36 which it had received a previous GSM MAP_UPDATE_LOCATION message.
3-142
X.S0023
1 The IIF shall also send an Update Location acknowledge message and send it to the GSM
2 MSC/VLR.
3 The IIF shall then format and send a GSM MAP_FORWARD_SHORT_MESSAGE. Refer to
4 Table 129 for the mapping of parameters from ANSI-regnot return result to GSM MAP
6 If a successful response is received for the FSM, the IIF shall clear the Message Waiting
7 Notification flag.
8 If the response to FSM indicates that the receiving node does not support MAP V2, the
9 GSM_FSM message shall be reformatted in MAP V1 and sent again.
10 If the response to FSM indicates an error condition, or if a time out occurs, the MWN
11 information is sent in a new GSM MAP _FORWARD_SHORT_MESSAGE when the IIF
12 receives a new GSM MAP _UPDATE_LOCATION, GSM MAP
13 _READY_FOR_SHORT_MESSAGE or GSM MAP _NOTE_MS_PRESENT message.
14 4.5.3.1.2 Qualification Directive Invoke Received

15 If the IIF receives a QUALDIR INVOKE message from the ANSI-41 HLR with MWNCOUNT and
16 MNWTYPE parameters set to valid values, it shall set the Message waiting Notification flag and
17 it shall send a GSM MAP FORWARD_SHORT_MESSAGE. Refer to Table 130 for the mapping
18 of parameters between ANSI-QUALDIR and GSM-_MAP_FORWARD_SHORT_MESSAGE.
19 If an error is detected in the QUALDIR INVOKE message, a Reject or Return Error message is
20 sent back to the sending node. No other processing is executed.
21 If a successful response is received for the FSM, the IF shall clear the Message Waiting
23 If the error in the response to FSM indicates that the receiving node does not support MAP V2,
24 the GSM_FSM message shall be reformatted in MAP V1 and sent again.
25 If an error is received in the response to FSM, or if a time out occurs, the MWN information is
26 sent in a new GSM MAP _FORWARD_SHORT_MESSAGE when the IIF receives a new GSM
27 MAP _UPDATE_LOCATION, GSM MAP _READY_FOR_SHORT_MESSAGE or GSM MAP
28 _NOTE_MS_PRESENT message.
30 Two methods of delivering Message Waiting Notification to a native GSM subscriber roaming in
31 ANSI-41 are supported.
32 4.5.3.1.3 GSM SMS Mapped to ANSI-41 Qualification Directive Invoke

33 If the IIF receives a GSM_FORWARD_SHORT_MESSAGE with MWN information, it shall set
34 the message waiting Notification flag and it shall format and send an ANSI_MAP_ QUALDIR
35 message to the serving ANSI-41 MSC/VLR. Refer to Table 131 for the mapping of parameters
36 from GSM MAP _FORWARD_SHORT_MESSAGE to ANSI_QUALDIR.
37 When the IIF receives a positive acknowledgment to the Qualification Directive message, it
38 shall send an acknowledgment to the Forward Short Message with an error indication of
39 “absent subscriber”. This shall ensure that the MWN information is delivered again from the
40 home system when the subscriber returns home.
3-143
X.S0023
1 If the MS registers in a different ANSI-41 MSC/VLR after some time, the MWN information is
2 delivered in the Registration Return Result message
5 Message Center.
6 If a Return Error or Reject is received in response to the ANSI_MAP Qualification Directive

7 INVOKE, the error code is mapped into the corresponding Forward Short Message error code
8 as described in Table 135.
9 4.5.3.1.4 GSM SMS Mapped to ANSI-41 SMS using GHOST or WEMT

10 If the IIF receives GSM MAP _FORWARD_SHORT_MESSAGE for a mobile that is GHOST or
11 WEMT capable, it shall send an ANSI_MAP Short Message Delivery Point to Point INVOKE
12 message. Refer to Table 132 for the mapping of parameters from GSM MAP
13 _FORWARD_SHORT_MESSAGE to ANSI-SMDPP.
14 When the Return Result for the SMDPP is received, the IIF sends back a positive
15 acknowledgement to the Forward Short Message.
18 Message Center.
19 If a Return Error or Reject is received in response to the ANSI_MAP Short Message Delivery
20 Point to Point INVOKE, the error code is mapped into the corresponding Forward Short
21 Message error code as described in Table 117.

24 message waiting notification in accordance with the tables presented. Within the following
25 tables, the parameters are identified as either being Mandatory (M), Conditional (C), Service
26 Provider Optional (O) or Service User Optional (U) in accordance with the definitions given in
27 GSM 09.02 [4] and ANSI-41 [2].
28 Table 127 shows the mapping between ANSI MAP messages and GSM MAP messages
29 related to Message Waiting Notification in GSM Foreign ModeTable 128 shows the mapping
30 between GSM MAP messages and ANSI MAP messages related to Message Waiting
31 Notification in ANSI-41 Foreign Mode.
32 Table 127: Message Waiting Notification in GSM Foreign Mode Message Mapping
regnot FORWARD_SHORT_MESSAGE
QUALDIR FORWARD_SHORT_MESASGE
33
3-144
X.S0023
1 Table 128: Message Waiting Notification in ANSI-41 Foreign Mode Message Mapping
FORWARD_SHORT_MESSAGE QUALDIR
FORWARD_SHORT_MESSAGE SMDPP
2
3 When the IIF receives either a GSM MAP message or an ANSI MAP message, it shall apply
4 the following rules regarding the handling of parameters within those messages:
5 The IIF shall populate mandatory parameters in messages sent by the IIF, regardless of
6 whether mapping of parameters is possible.
7 The IIF may populate optional parameters in messages sent by the IIF, regardless of whether
8 mapping of parameters is possible.
9 All parameters shall be populated in accordance with either GSM 09.02 [4] or ANSI-41 [2].
10
11 Table 129 through Table 134 show the mapping of parameters, which the IIF shall perform
12 regardless of the mode of operation (GSM Foreign Mode or ANSI-41 Foreign Mode). Where
13 there is no direct mapping for parameters, a ‘-‘ has been entered in the corresponding table.
14 Table 129: regnot to Forward Short Message for Message Waiting Notification Parameter
15 Mapping
ANSI-41 regnot Return Result Status GSM MT FSM Status
SM-RP-DA = IMSI M
SM-RP-OA = IIF address M
MWNCount (from Profile) O SM-RP-UI M
See Table 133 and Table 134 for
details of encoding of this
MWNType (from Profile) O parameter.
More Messages to Send = no M

Note 1
16
3-145
X.S0023
1 Table 130: QUALDIR to Forward Short Message for Message Waiting Notification
2 Parameter Mapping
ANSI-41 QUALDIR GSM MT FSM
MSID SM-RP-DA (M) = IMSI
SM-RP-OA (M) = IIF address
MWNCount (from Profile) SM-RP-UI (M)
MWNType (from Profile) See Table 133 and Table 134 for details of
encoding of this parameter.
_ More Messages to Send (M) = no
(Note 1)
3
4 Note 1: This parameter is only valid for MAP V2.
5 Table 131: Forward Short Message to QUALDIR for Message Waiting Notification
6 Parameter Mapping
GSM MT FSM Status ANSI QUALDIR Status
IMSI M MSID M
ESN M
_ QualificationInformationCode = M
Profile only
_ SystemMyTypeCode M
SM-RP-UI M MWNCount (in Profile) R

MWNType (in Profile) R
7
8 Table 132: Forward Short Message to SMDPP for Message Waiting Notification
9 Parameter Mapping
GSM MT FSM Status ANSI SMDPP Status
SM-RP-UI (M) M SMS_BearerData M
_ SMS_TeleserviceIdentifier = M
GHOST or WEMT
Originating Address M SMS-OriginalOriginatingAddress O
IMSI M ESN O
MSID R
10
3-146
X.S0023

2 Encoding
FIELD VALUE ENCODING
METHOD
Message Type Set to value “SMS-DELIVER” All
Indicator
More Messages to Set to value “No more messages are waiting All
Send for the MS in this SC”
Reply Path Set to value “TP-Reply-Path is not set in this All
SMS-DELIVER”
Status Report Set to value “A status report is not All
Indication requested”
Protocol Identifier Set to value “0” All
Service Center Time Created by the IIF All

Stamp
User Data Length Number of characters All
Originating Address Encoded as follows to support delivering of CPHS
MWN information for the CPHS encoding
method:
- First octet: Set value to 00000100

(address length).
- Second octet: Type of address. Bit 7 set to
value 1, bits 654 set to value 101
(alphanumeric) and bits 3210 set to value
0000 (numbering plan id).
- Third octet: First address value. Set bit
number 0 to value 1 to enable and value 1
to disable indication. Set bits 321 with value
000 (voice message waiting indicator). Set
bits 654 with value 001. Set bit 7 with value
0 for first indicator.
- Fourth octet: Second address value. Set
bits 76543210 with value 0.
3-147
X.S0023

3 Encoding (concluded)

METHOD
Data Coding Scheme - Set bit numbers 7654 to discard (value DCS
1100) message.
- Set bit number 3 to enable (1) or disable
indication (0).
- Set bit number 2 to 0.
- Set bit numbers 10 to Mail Message
Indication (value 00).
User Data Header parameter (one bit) indicating that the UD UD
Indicator
field contains a Header. Set to value “The
beginning of the TP-UD field contains a
Header in addition to the short message”.
User Data one space character using the default UD
alphabet
User Data Header - First octet: Length of the User Data UD
Header.
- Second octet: Information Element
Identifier (IEI) = Special SMS Message
- Third octet: Length of this IEI (value 2).
- Fourth octet: Bit 7 is Store(1)/Discard(0)
message. Bits 0-6 with value 0 (Voice
Message Waiting).
- Fifth octet: Number of messages waiting.
- Rest of octets: Beginning of short message
4
3-148
X.S0023
1 Table 134: SM-RP-UI in Message FORWARD_SHORT-MESSAGE for MAP V1 Parameter

2 Encoding
METHOD
Message Type Indicator Set to value “SMS-DELIVER” All
More Messages to Send Set to value “No more messages are All
waiting for the MS in this SC”
Protocol Identifier Set to value “0” All
Service Center Time Stamp Created by the IIF All

User Data Length Number of characters All
User Data one space character using the default All
alphabet
Originating Address Encoded as follows to support delivering CPHS
of MWN information for the CPHS
encoding method:
- First octet: Set value to 00000100

(address length).
- Second octet: Type of address. Bit 7
set to value 1, bits 654 set to value 101
(alphanumeric) and bits 3210 set to
value 0000 (numbering plan id).
- Third octet: First address value. Set bit
number 0 to value 1 to enable and value
0 to disable indication. Set bits 321 with
value 000 (voice message waiting
indicator). Set bits 654 with value 001.
Set bit 7 with value 0 for first indicator.
- Fourth octet: Second address value.
Set bits 76543210 with value 0.
Data Coding Scheme - Set bit numbers 7654 to discard (value DCS
1100) message.
- Set bit number 3 to enable (1) or
disable indication (0).
- Set bit number 2 to 0.
- Set bit numbers 10 to Mail Message
3-149
X.S0023
2 4.5.3.3.1 Error Handling at the Reception of a Forward Short Message

4 4.5.3.3.2 Error Mapping from ANSI QUALDIR to GSM FSM
5 Table 135: qualdir return error to FORWARD_SHORT_MESSAGE response Error

6 Mapping
QUALDIR (Errors) FORWARD_SHORT_MESSAGE
Unrecognized MSID SMS Delivery Failure
Unrecognized ESN SMS Delivery Failure
ResourceShortage SMS Delivery Failure
OperationNotSupported SMS Delivery Failure
ParameterError SMS Delivery Failure
SystemFailure SMS Delivery Failure
UnrecognizedParameterValue SMS Delivery Failure
MissingParameter SMS Delivery Failure
8 4.5.3.3.3 Error Mapping from ANSI SMSDPP to GSM FSM

9
10 Table 136: SMSDPP to FORWARD_SHORT_MESSAGE response Error Mapping

SMSDPP (Cause Code) FORWARD_SHORT_MESSAGE
Destination Busy Subscriber Busy for MT-SMS
Address Vacant Absent Subscriber
No Pager Response Absent Subscriber
No Acknowledgement Absent Subscriber
Destination Out of Service Absent Subscriber
Destination No Longer at this Address Absent Subscriber
SMS Delivery Postponed Absent Subscriber
Any other value System Failure
3-150
X.S0023
1 4.6 GPRS in GSM Foreign mode

2
3 The following text describes the procedures in the IIF for the case in which an ANSI-41
4 subscriber requests GPRS service while operating in GSM foreign mode.
5 Note: There is no GPRS service for GSM subscribers roaming in an ANSI-41 radio
6 environment.
7 4.6.1 Mobility Procedures

8
11 Enhancements and modifications to GSM 02.60 [30] and ANSI-41 [2] are also applicable.
12

14
15 The following text contains the procedures in the IIF for the case in which the ANSI-41
16 subscriber requests GPRS services while roaming in foreign mode (i.e., while roaming in a
17 GSM network).
18 4.6.1.1.1 GPRS Location Updating

19 The IIF contains location information (SGSN number) relating to the roaming subscriber.
20 Therefore, the IIF needs to be updated at each change in SGSN. The IIF shall translate GSM
21 MAP messages to ANSI-41 MAP messages and vice versa when the subscribers home
22 ANSI-41 HLR needs updating. The subscriber’s ANSI-41 HLR shall be updated in the following
23 cases:
24 • When the subscriber’s MS registers in an SGSN in a GSM network, when previously

25 registered in an ANSI-41 network;
26 • When the subscriber’s MS registers in an ANSI-41 network, when previously registered in

27 an SGSN in a GSM network;
28 The subscriber’s home HLR may be updated in the following cases:
29 • When the subscriber’s MS (accessing a GSM Network) registers in another SGSN within
30 the same GSM network. The IIF acts like a GPRS HLR/AuC in this case.
31 • When the subscriber’s MS (accessing a GSM network) registers in a SGSN when

32 previously registered in a GSM VLR within the same GSM network.
33 When the HLR is updated, the IIF conveys a unique identifier to the ANSI-41 HLR identifying
34 the SGSN/GSM VLR or IIF, depending on Multiple MSCIDs optional support.
35 If the IIF receives a GSM_ MAP_UPDATE_GPRS_LOCATION _REQUEST, it shall compare

36 the received routing area information with any previously stored routing area information. If the
37 received and previously stored routing area information are different, the IIF shall determine if
3-151
X.S0023
1 the location updating is allowed and update the corresponding subscriber record accordingly
2 and send a GSM MAP _CANCEL_LOCATION_REQUEST to the old SGSN. If there is no
3 previously SGSN stored routing area information in the IIF, the IIF shall determine if the location
4 updating is allowed and update the corresponding subscriber record accordingly.
5 If the IIF receives a GSM MAP _MS_PURGE_REQUEST, it shall check the contents of the
6 message for errors. If errors exist, the IIF shall send a GSM MAP _MS_PURGE_RESPONSE
7 indicating the reason for failure and the MS purged flag shall not be set. If no errors exist, the
8 IIF shall check if the received SGSN number matches the stored SGSN number.
9 If the received SGSN number and the stored SGSN number match, the IIF shall set the MS
10 purged flag and shall send both a GSM MAP _MS_PURGE_RESPONSE to the SGSN and an
11 ANSI_MAP_MS_INACTIVE to the ANSI-41 HLR and awaits a response from the HLR.
12 If the received SGSN number and the stored SGSN number do not match, the IIF sends a GSM
13 MAP _PURGE_MS_RESPONSE containing an empty result to indicate that the MS purged flag
14 is not set.
15 If the MS requests a combined GSM and GPRS attach, then the SGSN requests a GPRS
16 location update to the IIF (acting as a GPRS HLR) and then the GSM-MSC requests a CS
17 location update. CS location update and mobility procedures are described in 4.1 Mobility
18 Procedures.
20 The following tables present the mapping of presents the mapping of messages, parameters
21 and parameter values that the IIF shall perform.
23 Table 137 shows the mapping between GSM MAP messages and ANSI MAP messages
24 related to GPRS Location Registration when necessary.
25 Table 137: Location Updating GPRS in GSM Foreign Mode Message Mapping
MAP_UPDATE_GPRS_LOCATION_REQUEST REGNOT
1
MAP_INSERT_SUBSCRIBER_DATA_REQUEST regnot
MAP_UPDATE_GPRS_LOCATION_RESPONSE regnot2
26
1
27 This procedure is used to download GPRS subscriber data to the SGSN.
2
28 This message can also contain error values if the location updating procedure is
29 unsuccessful. If the location updating procedure fails, the mapping is as shown in 4.1.1.3.
30 Table 3 shows the mapping between GSM MAP messages and ANSI MAP messages for MS
31 Purge operation. Table 4 shows the mapping between GSM MAP messages and ANSI MAP
32 messages related to Location Cancellation.
33
3-152
X.S0023
4 parameters in the corresponding ANSI-41 messages when necessary.
5 Table 138: MAP_UPDATE_GPRS_LOCATION_REQUEST  REGNOT Parameter Mapping

_UPDATE_GPRS_LOCATION_
REQUEST
MSID M
1
SGSN address M MSCID (Serving MSC) M
SGSN Number M -
QualificationInformationCode M
2
2
- TerminalType O
- TransactionCapability2 O
6
1
7 This parameter is used to convey an identity from the IIF to the ANSI-41 HLR identifying either
8 the SGSN or the IIF. In the case where the IIF supports multiple MSCIDs this identity is a
9 unique identity associated with the SGSN. Otherwize, the identity shall be that of the IIF.
2
10 Parameters are included in IS-41-C and later.
3-153
X.S0023
2 Table 139 shows the mapping of parameters for GSM MAP

3 _INSERT_SUBSCRIBER_DATA_REQUEST to regnot when necessary.
4 Table 139: MAP_INSERT_SUBSCRIBER_DATA_REQUEST  regnot Parameter Mapping

_INSERT_SUBSCRIBER_DATA
_REQUEST
HLR)
- MSCID (HLR) O
1
- MSID O
IMSI C -
5
1
9 _INSERT_SUBSCRIBER_DATA_REQUEST as shown in Table 140:
3-154
X.S0023
1 Table 140: MAP_UPDATE GPRS LOCATION RESPONSE  regnot Parameter Mapping

GSM MAP _UPDATE_ Statu regnot Status
GPRS_LOCATION_RESPONSE s
HLR)
1, 2 2
HLR number R MSCID (HLR) R
- Profile “Macro”3 O
- MSID O
1
2 The presence of this parameter is mandatory in case of successful HLR updating.
2
3 These parameters are used to convey a unique identifier from the IIF to the serving
4 MSC/VLR, identifying the HLR.
3
3-155
X.S0023
1 As far as mapping of parameters is concerned, the IIF shall map the contents of the ‘Profile’
2 macro in the ANSI-41-D GSM MAP _INSERT_SUBSCRIBER_DATA_REQUEST as shown in
3 Table 141:
4 Table 141: MAP_INSERT_SUBSCRIBER_DATA_REQUEST  profile ‘macro’ Mapping

MAP_INSERT_SUBSCRIBER_D Status regnot Status
ATA_REQUEST
IMSI C MSID M
- AuthenticationCapability O
MSISDN C MobileDirectoryNumber O
Category C -
Subscriber Status C -
Bearer service List C -
Teleservice List C
Forwarding information List C CallingFeaturesIndicator1 O
- CarrierDigits O
Regional Subscription Data C -
- GeographicAuthorization O
- MessageWaitingNotificationCount O
- MessageWaitingNotificationType O
3 2
Call barring information List C OriginationIndicator O
4 4
VLR CAMEL Subscription Info C OriginationTriggers O
- PACAIndicator O
CUG information List C -
6
SS-Data List C CallingFeaturesIndicator1 O
EMLPP Subscription Data C -
General data
HPLMN data5
Operator Determined Barring C RestrictionDigits O
HPLMN data5
Roaming Restriction Due To C -
Unsupported Feature
- RoutingDigits O
3 7
Call barring information List C SMS_OriginationRestrictions O
3-156
X.S0023
1 Table 141: MAP_INSERT_SUBSCRIBER_DATA_REQUEST  macro profile Mapping

2 (concluded)
MAP_INSERT_SUBSCRIBER_D Status ‘profile’ macro Status

ATA_REQUEST
Call barring information List3 C SMS_TerminationRestrictions8 O
- SPINIPIN O
- SPINITriggers O
3
Call barring information List C TerminationRestrictionCode O
4
VLR CAMEL Subscription Info C TerminationTriggers O
Voice Broadcast Data C
Voice Group Call Data C -
- PreferredLanguageIndicator O
6 7
SS-Data List SMS_OriginationRestrictions O
8
SMS_TerminationRestrictions O
6
SS-Data List
North American Equal Access U -
preferred Carrier Id
Roaming Restricted In SGSN C -
Due To Unsupported Feature9
GPRS Subscription Data10 C -
11
Network access mode C -
3
1
4 The CallingFeaturesIndicator parameter provides a status of several ANSI supplementary
5 services. This information may map into one or more GSM MAP parameters as shown in
6 Table 92.
2
7 The OriginationIndicator parameter defines the type of calls that a MS is allowed to make.
8 This information may map into one or more GSM MAP parameters as shown in Table 92.
3
9 The Call barring information List is a list of the call barring supplementary services that are
10 either active, quiescent or not active for individual or all teleservices. This information may
11 map into one or more ANSI MAP parameters as shown in Table 92.
4
12 Camel/WIN interworking is out of the scope of this version of the standard.
5
13 Operator Determined Barring HPLMN data may map into one or more ANSI MAP
14 parameters as shown in Table 92.
6
15 The SS-Data List may map into one or more ANSI MAP parameters as shown in Table 92.
7
16 The SMS_OriginationRestrictions may map into one or more GSM MAP parameters as
8
18 The SMS_TerminationRestrictions may map into one or more ANSI MAP parameters as
9
20 The IIFmay decide to include this parameter in the request if certain services or features
21 are indicated as not supported by the SGSN. This parameter is used only by the SGSN.
3-157
X.S0023
10
1 This parameter contains a list of PDP-contexts a user has subscribed to. At GPRS location
2 updating the IIF shall include the complete GPRS Subscription Data. When there is a
3 change in GPRS subscriber data the IIF shall include only the new and/or modified PDP
4 contexts. When the SGSN receives GPRS Subscription Data it shall check if the received
5 data has to be considered as the entire GPRS subscription data. If so, it shall replace the
6 stored GPRS Subscription Data with the received data set, otherwise it shall replace the
7 data only for the modified PDP contexts (if any) and add the new PDP contexts (if any) to
8 the stored GPRS Subscription Data. If GPRS Subscription Data is omitted in the Insert
9 Subscriber Data operation the SGSN shall keep the previously stored GPRS Subscription
10 Data.If the SGSN detects that there is overlapping in the information received within a
11 dialogue, it shall send the error Unexpected Data Value. This parameter is used only by the
12 SGSN.
11
13 This parameter defines the access capabilities of a registered MS.
14 Error handling, Fault Recovery procedures and Error Code mapping are described in 4.1
15 Mobility Procedures.
3-158
X.S0023
1 4.6.2 Automatic Call Delivery

2 The Automatic Call Delivery procedure is invoked in the IIF, when a terminating call attempt
3 results in a request for routing information from the IIF.
4 The following procedures are applicable at the IIF for GPRS in GSM Foreign mode Automatic
5 Call Delivery:

7 If the IIF receives an ANSI MAP_RoutingRequest Invoke message from the ANSI-41 HLR, it
8 shall check if the terminating call can be placed to that subscriber. Call delivery to an MS that is
9 roaming in a GPRS network in GSM foreign mode shall be delivered only if the subscriber is
10 registered with a GSM serving MSC/VLR. As such, the IIF (acting as a GSM HLR) sends the
11 GSM serving MSC/VLR a MAP Provide Roaming Number (PRN) see 4.2.1 Call Delivery.
12 If the MS is attached for GPRS-only services, incoming calls are not deliverable to the
13 subscriber. Upon the reception of ROUTEREQ, the IIF determines if the MS is attached for
14 GPRS-only services and if so, the IIF shall not deliver the call. The IIF sends a routreq with the
15 field “AccessDeniedReason” set to “No Page Response” or “Unavailable”.
3-159
X.S0023

2 In this case, the IIF has the calling party DN available (from the ROUTEREQ message). Upon
3 the reception of a ROUTREQ, if the MS is only GPRS attached, the IIF proceeds to act as an
4 SMS-SC and sends an FSM to the SGSN requesting the SGSN to deliver an SMS message
5 containing the calling party’s DN to the MS. The mapping of parameters is shown in the
6 following table:
7 Table 142: ROUTREQ  MT_Forward Short Message Parameter Mapping

ROUTREQ Status MT_Forward Short Status
BillingID (Originating) M -
ElectronicSerialNumber M -
MobileStationIDentity M SM-RP-DA = IMSI M
- SM-RP-OA = IIF address in M

international format. See
4.5.2.4
- More Messages to Send = no M
SystemMyTypeCode (Originating M -
MSC)
AlertCode O -
CallingPartyNumberString1 O SM-RP-UI M
(Note 1)
CallingPartyNumberString2 O SM-RP-UI M
(Note 1)
DestinationDigits O -
LegInformation O -
LocationAreaID O -
MobileDirectoryNumber O MSISDN R
(Note 2)
MSCIdentificationNumber R -
NoAnswerTime O -
OneTimeFeatureIndicator O -
PC_SSN (Originating MSC) R -
PilotBillingID O -
PilotNumber O -
3-160
X.S0023
1 Table 142: ROUTREQ  MT_Forward Short Message Parameter Mapping (concluded)
ROUTREQ Status MT_Forward Short Status

RedirectingSubAddress O -
SenderIdentificationNumber O -
TerminationTreatment O -
VoiceMailboxNumber O -
VoiceMailPIN O -
- MSC Number M
- LMSI U
- GMSC address R
- GSM Bearer Capability C

- Network Signal Info C
- Suppression of C
Announcement
- Call Reference Number R
- OR Interrogation C
- Alerting Pattern C
- CCBS Call C
2
3 Note 1: For encoding of those parameters, refer to “4.3.4 Calling Number/Line Identification
4 Presentation/Restriction”.
5 Note 2: May also be directly retrieved from the subscriber profile pre-provisioned in the IIF.
6 4.6.2.1.1.1 Error Code Mapping
7 Appropriate errors for an MS attached to both GPRS and non-GPRS services are described in
8 4.2.1.3
9 Appropriate AccessDeniedReason parameter values in the RoutingRequest Return Result for

10 the case of a call delivery attempt to an MS attached for GPRS-only services:
AccessDeniedReason
Unavailable
No page Response
11
3-161
X.S0023
1 4.6.3 Short Message Procedures for ANSI-41 subscriber

2 The following describes the procedures for MS terminated and MS originated SMS while the
3 MS is roaming in a GPRS network in GSM foreign mode and is GPRS attached.
4 Existing mobility procedures described in either GSM 09.02 [4] and GSM 03.60 Error!
5 Reference source not found. or ANSI-41 [2] are also directly applicable to the IIF when it is
6 emulating a GPRS, GSM or ANSI-41 functional network element.
7 If the MS is both GSM CS attached as well as GPRS attached, then the IIF shall act as a GSM
8 SMS-SC.
9 4.6.3.1 Short Message Service via CMT

10 The Short Message Service procedure is used to deliver short text messages to and from
11 mobile subscribers.

13 The following procedures are applicable at the IIF for Short Message Service. Mobile
14 Terminating SMS and Mobile Originated SMS using the CMT teleservice ID are described.
15 4.6.3.1.1.1 Mobile Terminating SMS

16 If the IIF receives an ANSI-41 Short Message Delivery Point to Point message it shall check if
17 the MS location is known and if the subscriber is reachable. If both conditions are true, the IIF
18 shall format and send a GSM_ MAP_FORWARD_SHORT_MESSAGE (FSM) to the SGSN
19 serving the mobile. Refer to Table 109 for the mapping of parameters from ANSI_SMDPP to
20 GSM MAP _FORWARD_SHORT_MESSAGE.
21 If a successful response is received for the FSM, the IIF shall return SMDPP Return Result
22 message. If the MS's location is not known, or if the MS is not reachable or if the response to
23 the FSM indicates the short message was not delivered to the mobile, the IIF shall set the SMS
24 Delivery Pending flag for the subscriber. The IIF shall then return an SMDPP Return Result
25 message with an appropriate SMS_CauseCode value. Refer to 4.5.1.3 Error Handling for the
26 values of SMS_CauseCode returned.
28 be processed or if mandatory parameters are missing. Otherwise, the IIF shall return a SMDPP
31 If the response to FSM indicates a failure in the delivery of the short message, the IIF shall map
32 the cause value received to a corresponding SMS_CauseCode value in the SMDPP Return
33 Result, as described in Table 116.
34 4.6.3.1.1.2 Alerting for GPRS in GSM Foreign Mode in either CMT or GHOST/WEMT
35 format
36 The SMS Alert procedure is used for alerting the SGSN when the MS is available for short
37 messaging after a short message transfer has failed because the mobile subscriber is not
38 reachable or when the MS has indicated that it has no memory capacity to accept a short
39 message.
3-162
X.S0023
1 Upon receipt of a READY_FOR_SM message, the IIF shall store the originating SGSN address
2 and Invoke ID in the subscriber’s profile. It shall map the GSM_READY_FOR_SM message to
3 the ANSI_SMSNOT INVOKE message as described in Table 119.
4 It shall populate the SMS_Address parameter with the IIF address. All other parameters are
5 ignored.
6 The ANSI_SMSNOT INVOKE is then transmitted to the subscriber’s SGSN with local
7 Transaction ID. Finally, the IIF shall return a READY_FOR_SM_ACK message with no
8 arguments to the originating SGSN.
9 Upon receipt of a SMSNOT RR message, the IIF shall associate the SMSNOT Transaction ID
10 with the Invoke ID.
11 If the IIF receives a GSM MAP _READY_FOR-SHORT_MESSAGE and the Delivery pending
12 flag is set for the subscriber, the IIF shall send an ANSI_MAP_SMS_NOTIFICATION message
13 to the home Message Center. The IIF shall clear the MNRG flag if Alert Reason is set to MS
14 present or The Memory Capacity Exceeded Flag (MCEF) flag if Alert Reason is set to Memory
15 Available and the flags were previously set. If the Alert Reason indicates the mobile present for
16 non GPRS situation, or when the update location procedure has been successfully completed
17 or Supplementary Service Control request is received, the MS not reachable flag (MNR) is
18 cleared and the service centre alert procedure is initiated. If the memory capacity exceeded flag
19 is set, the MS not reachable flag is cleared and stored reason for absence for non GPRS are
20 cleared but the alert procedure is not started. If the Alert Reason indicates the mobile present
21 for GPRS situation, or when the Update GPRS location procedure has been successfully
22 completed, the MS not reachable for GPRS (MNRG) flag is cleared and the service centre alert
23 procedure is initiated. The mapping of parameters is described in Table 143.
24 The ANSI-41 MC shall re-send message SMDPP to deliver the short message to the subscriber.
25 Table 143: Alerting for an ANSI-41 Subscriber for GPRS in GSM Foreign Mode Parameter
26 Mapping
GSM MAP _READY_FOR_SM Status ANSI_SMSNOT Status
IMSI M ESN M
MSID M
Alert Reason M -
1
Alert Reason Indicator C
SMS_Address (IIF Address) R
1
27 This parameter indicates that the alert reason is sent to the HLR due to GPRS activity.
28
29 4.6.3.1.1.3 Mobile Originating SMS for GPRS in GSM Foreign Mode

30
31 If the IIF receives a GSM_FORWARD_SHORT_MESSAGE for a mobile originated short

32 message, it shall format and send an ANSI_MAP_SMDPP message to the home Message
33 Center. Refer to Table 114 for the mapping of parameters from GSM MAP
3-163
X.S0023
3 If the IIF receives a negative acknowledgment to the SMDPP message, it shall map the
4 received SMS_CauseCode value into a corresponding error code in the FSM Response
5 message as described in Table 117. Also the IIF shall set the Mobile Not Reachable for GPRS
6 (MNRG) GSM SMS flag.
8 response message. Refer to 4.5.1.3 for the handling of errors at the reception of FSM.

11 Short Message Service in accordance with the tables presented in 4.5.1.2.1.

13 Error handling is described in 4.5.1.3
3-164
X.S0023
1 4.6.4 Short Message Service via GHOST or WEMT

2
4 4.6.4.1.1 SMS Delivery for an ANSI-41 Subscriber for GPRS in GSM Foreign Mode
5 Upon receipt of an SMSDeliveryPointToPoint INVOKE message, the IIF shall store the
6 originating MC address and transaction ID. It shall map the ANSI_SMDPP message into a
7 GSM_FSM message and populate the subscriber’s known SGSN into the DPC. The IIF
8 transmits the GSM_FSM message with local Invoke ID.
9 The mapping of parameters is described in Table 121.
12 Invoke ID with SMDPP transaction ID and map the GSM_FSM_ACK message into an
14 Next, it populates the stored originating SGSN address into the DPC and populates the
15 transaction ID.
16 If the User Error parameter is populated in the GSM_FSM_ACK, then map this value into
17 the SMS_CauseCode according to Table 116.
18 Finally, the ANSI_SMDPP RR is transmitted to the originator.
19 4.6.4.1.2 SMS Origination

20 Upon receipt of a MO_FORWARD_SHORT_MESSAGE, the IIF shall store the address of the
21 originating SGSN and Invoke ID. It shall map the GSM_MO_FSM to ANSI_SMDPP INVOKE.
22 The address of the subscriber’s TSA (from the SM RP DA – Service Center Address) is
23 mapped according to 4.5.2.4 into the SMS_DestinationAddress. The IIF transmits the
24 ANSI_SMDPP INVOKE message with local transaction ID. The mapping of parameters is
27 transaction ID with Invoke ID and map the ANSI_SMDPP RR to the GSM_FSM_ACK.
28 Next, it populates the stored originating SGSN address and Invoke ID. If SMS_CauseCode
31 Finally, transmit the GSM_FSM_ACK to the originating SGSN.

34 Short Message Service in accordance with the tables presented in 4.5.2.2.

36 Error handling is described in 4.5.1.3
3-165
X.S0023
1 4.6.5 Message Waiting Notification

2 The Message Waiting Notification procedure is used to notify a mobile subscriber of voice mail
3 messages added or removed in his voice mail system. 4.6.5 shows only the changes needed to
4 support GPRS service for an ANSI-41 subscriber in GSM foreign mode.
5 If the subscriber is both GSM CS attached as well as GPRS attached, then the IIF shall act like
6 a GSM SMS-SC.
8 4.6.5.1.1 Registration Notification Return Result with MWN Information Received

9 When the IIF receives a Registration Notification Return Result message with MWNCOUNT
10 and MWNTYPE parameters set to valid values, it shall send a GSM SMS with the MWN
11 information.
12 The IIF shall then format and send a GSM MAP_FORWARD_SHORT_MESSAGE. Refer to
13 Table 129 for the mapping of parameters from ANSI-41 regnot return result to GSM MAP
17 If the response to FSM indicates an error condition, or if a time out occurs, the MWN
18 information is sent in a new GSM MAP _FORWARD_SHORT_MESSAGE when the IIF
19 receives a new GSM MAP _UPDATE_GPRS_LOCATION, GSM MAP
20 _READY_FOR_SHORT_MESSAGE or GSM MAP _NOTE_MS_PRESENT message.
21 When the IIF receives a QUALDIR INVOKE message from the ANSI-41 HLR with
22 MWNCOUNT and MNWTYPE parameters set to valid values, it shall set the Message waiting
23 Notification flag and the IIF shall send a GSM MAP FORWARD_SHORT_MESSAGE. Refer to
24 Table 130 for the mapping of parameters between ANSI-QUALDIR and GSM-
25 _MAP_FORWARD_SHORT_MESSAGE.
26 If an error is detected in the QUALDIR INVOKE message, a Reject or Return Error message is
27 sent back to the sending node. No other processing is executed.
30 If an error is received in the response to FSM, or if a time out occurs, the MWN information is
31 sent in a new GSM MAP _FORWARD_SHORT_MESSAGE when the IIF receives a new GSM
32 MAP _UPDATE_GPRS_LOCATION, GSM MAP _READY_FOR_SHORT_MESSAGE or GSM
33 MAP _NOTE_MS_PRESENT message.

36 message waiting notification in accordance with 4.5.3.2.

3-166
X.S0023
1 4.6.5.3.1 Error Mapping

2 Refer to 4.5.3.3.2 Error Mapping.
3-167
X.S0023
1 ANNEX A Short Message Service Procedures

2 within an ANSI-136 Network
3 (Normative)
4 GHOST may be used as the delivery teleservice from a short message entity to a mobile
5 station operating in ANSI-136 Native Mode through a SMSC, which is providing IIF functionality
6 at the GSM TP-layer. In this case, normal ANSI-41 procedures are used to deliver the GHOST
7 teleservice between ANSI-41 network elements and normal ANSI-136 procedures are used to
8 deliver the GHOST teleservice from the serving MSC to the mobile station. The SMSC is
9 responsible for identifying the MS as GHOST capable and for packaging the short message in
10 the proper format using the GHOST teleservice for delivery to the MS.
11 A.1 CMT to GHOST Delivery

12 If the short message entity is an MS originating a message using the Cellular Messaging
13 Teleservice (CMT) teleservice to the GHOST MS, then upon receipt of the CMT message the
14 SMSC proceeds as follows.
15 A.1.1 Detailed Procedures

16 After determining the incoming CMT message is destined for an MS that supports the GHOST
17 teleservice, (the method to perform this identification is internal to the SMSC and beyond the
18 scope of this standard) the SMSC shall determine the status and location of the targeted MS
19 using normal ANSI-41 procedures.
20 If the MS is unavailable or the location is unknown, the SMSC shall set an internal retry
21 schedule or wait for notification from HLR. Otherwise, it shall populate address delivery
22 information and optional parameters per normal ANSI-41 procedures. Next, it shall map the
23 contents of the SMS_BearerData per Error! Reference source not found. and populate the
24 SMS_TeleserviceIdentifier with the GHOST teleservice identifier. Finally, it shall transmit the
25 SMDPP INVOKE message to the serving MSC.
3-168
X.S0023
1 A.1.2 Mapping of Messages, Parameters & Parameter Values

2 When the SMSC receives the SMDPP Invoke message from a CMT capable MS, the SMSC
3 follows normal ANSI-41 procedures except it replaces the CMT value of 32513d with the
4 GHOST value. In addition, the following parameter mapping related to ANSI-136-710 shall be
5 performed as indicated inTable 144.
6 Table 144: ANSI-136-710 to GHOST Parameter Mapping.

SMDPP/CMT Parameter Status Handling
ANSI-136 Message Type M Only SMS_SUBMIT shall be relayed as
Indicator a GHOST message.
SMS_DELIVERY_ACK and
SMS_MANUAL_ACK shall be
discarded if the destination is a
GHOST MS.
ANSI-136 Message Reference M -
ANSI-136 Privacy Indicator M -
ANSI-136 Urgency Indicator M Not mapped. Handled by the SMSC.
ANSI-136 Delivery M Not mapped. See note 1.
Acknowledgement Request
ANSI-136 Manual M -
Acknowledgement Request
ANSI-136 Message Updating M Not mapped. Handled internally by the
MC.
ANSI-136 User Data Unit M Mapped to TP-Data-Coding-Scheme,
TP-User-Data and TP-User-Data-
Length.
The MC should support mapping of
user data as described in A.2.1
Detailed Procedures
ANSI-136 Validity Period O Not mapped. Handled internally by the
MC.
ANSI-136 Deferred Delivery Time O Not mapped. Handled internally by the
MC.
ANSI-136 Call Back Number O See A.3.1
ANSI-136 Call Back Number O -
Presentation
ANSI-136 Call Back Number O -
Alpha Tag
7
8 Note 1: In GSM, delivery acknowledgement indicates that the data is stored at the MS. In ANSI-
9 136, delivery acknowledgement is triggered by an action of the MS user (displaying the
10 message). Therefore this parameter is not mapped. It is a local decision for the operator as to
11 how to treat MO messages requesting these acknowledgements. The recommended procedure
12 for operators is for the MC to return a SMS DELIVERY ACK to the originator upon receipt of a
3-169
X.S0023
1 positive delivery confirmation from the terminating mobile. The procedures and format of the
2 SMS DELIVERY ACK message shall follow ANSI-136-710.
3 Table 145 describes where the parameters in the MT GHOST message are derived from:
4 Table 145: TP Derived Values

Parameter in MT GHOST Status Value/derivation
message
TP-Message-Type-Indicator M SMS-DELIVER
TP-More-Messages-To-Send M Set appropriately by the MC based on
the MC message store.
TP-Reply-Path M Set to “TP-Reply-Path parameter is not
set”
TP-User-Data-Header-Indicator O Set to “the TP-UD field contains only
the short message”
TP-Status-Report-Indicator O Set to “a status report will not be
returned to the SME”
TP-Originating-Address M Set to the
SMS_OriginalOriginatingAddress
TP-Protocol-Identifier M Set to 00000000
TP-Data-Coding-Scheme M Set based on information in the ANSI-
136 User Data Unit
Set bit number 3 per A.2.1
Detailed Procedures
Set bit numbers 1&0 to value “Class 1”.
TP-Service-Center-Timestamp M Set by the MC to the appropriate value
TP-User-Data-Length M Set based on information in the ANSI-
136 User Data Unit
TP-User-Data O Set based on information in the ANSI-
136 User Data Unit.
5
6 A.1.3 Error Handling

7 No additional error handling procedures beyond those in ANSI-41D are required.
8 A.2 GHOST to CMT Delivery

9 GHOST may be used to deliver teleservices from a mobile station operating in ANSI-136 Native
10 Mode to an MS-based short message entity, which only supports the CMT ID without the
11 involvement of an IIF.

13 The mobile station formulates a GSM SMS PDU and adds the GHOST header to the GSM
14 SMS PDU. If required, it adds the TSAR header to the GHOST teleservice. Next, it inserts the
3-170
X.S0023
1 GHOST teleservice into the Higher Layer Protocol Data Unit of the R-Data Unit and adds the
2 GHOST HLPI. An R-DATA message is formulated and sent to the ANSI-136 BMI.
3 The ANSI-136 MSC follows normal procedures and translates the R-DATA message to an
4 ANSI-41 SMDPP Invoke message and sends it to the originator’s home MC. The MC
5 destination address can be specified in the Teleservice Server Address. {Alternatively, MIN to
6 MC GTT or a routing table in the MSC may be used if the TSA is not present.} The MSC does
7 not open the Higher Layer Protocol Data Unit, but converts it directly to SMS_BearerData.
8 For the mobile station in ANSI-136 Native Mode, the Teleservice Server Address shall indicate
9 that the home Teleservice Server is the home Message Center. Upon receipt of the SMDPP
10 Invoke message, the SMSC responds with a SMDPP RR per normal ANSI-41 procedures.
11 The SMSC then identifies the destination address as an MS that supports CMT. (The method to
12 perform this identification is internal to the SMSC and beyond the scope of this standard.) It
13 then determines the status and location of the targeted MS using normal ANSI-41 procedures.
14 If the MS is unavailable or location is unknown, the SMSC shall set its internal retry schedule or
15 wait for notification from HLR
16 Otherwise, it shall populate the address delivery information and optional parameters per
17 normal ANSI-41 procedures. Next, it maps the contents of the SMS_BearerData per Error!
18 Reference source not found. and MT CMT message are derived from
19 Table 146 and populates the SMS_TeleserviceIdentifier with the CMT teleservice identifier.
20 Finally, the SMSC transmits the SMDPP Invoke message to the serving MSC.
21 Supported user data mappings
22 The following user data mappings should be supported:

23
IS-136 Encoding GSM TP-Data-Coding-Scheme

IRA/ITU.T50 GSM Default Alphabet. Mapping of the user data content should
be performed.
User Specific 8-bit data. No mapping of user data content needs to be
performed.
24
3-171
X.S0023
2 A.2.2 Mapping of Messages, Parameters & Parameter Values

3
4 When the SMSC receives the SMDPP Invoke message from a GHOST capable MS, the SMSC
5 follows normal ANSI-41 procedures except it replaces the GHOST value of {to be provided by
6 TR45.3} with the CMT value of 32513d. In addition, the following parameter mapping related to
7 ANSI-136-710 shall be performed as indicated in Table 146.
8 Table 146: GHOST to ANSI-136-710 Parameter Mapping

Parameter in MT GHOST message Value/derivation
TP-Message-Type-Indicator SMS-DELIVER
TP-More-Messages-To-Send Set appropriately by the MC based on the
MC message store.
TP-Reply-Path Set to “TP-Reply-Path parameter is not
set”
TP-User-Data-Header-Indicator Set to “the TP-UD field contains only the
short message”
TP-Status-Report-Indicator Set to “a status report will not be returned
to the SME”
TP-Originating-Address Set to the
SMS_OriginalOriginatingAddress
TP-Protocol-Identifier Set to 00000000
TP-Data-Coding-Scheme Set based on information in the ANSI-136
User Data Unit
Set bit number 3 per A.2.1 Detailed
Procedures
Set bit numbers 1&0 to value “Class 1”.
TP-Service-Center-Timestamp Set by the MC to the appropriate value
TP-User-Data-Length Set based on information in the ANSI-136
User Data Unit
TP-User-Data Set based on information in the ANSI-136
User Data Unit.
9
3-172
X.S0023
1 Table 147 describes where the parameters in the MT CMT message are derived from
2 Table 147: CMT Derived Values

SMDPP/GHOST Parameter Handling
TP-Message-Type-Indicator Only SMS-SUBMIT shall be relayed as a
CMT message. SMS-STATUS-REPORT
shall be discarded if the destination is a
CMT MS.
TP-Reject-Duplicates Not mapped. Handled internally by the
MC.
TP-Validity-Period-Format Not mapped. Handled internally by the
MC.
TP-Reply-Path Not mapped
TP-User-Data-Header-Indicator If the TP-UDHI indicates that the TP-UD
contains a header then the MC shall
interpret the header. The MC may,
depending on the values in the header,
discard the message, ignore the header or
process the header and modify the ANSI-
136 User Data Unit
TP-Status-Report-Request Not mapped. Handled internally by the
MC. See Table 149
TP-Message-Reference Mapped to ANSI-136 Message Reference
TP-Destination-Address Mapped to
SMS_OriginalDestinationAddress
TP-Protocol-Identifier Not mapped. Handled internally by the
MC.
TP-Data-Coding-Scheme Mapped to ANSI-136 User Data Unit
TP-Validity-Period Not mapped. Handled internally by the
MC.
TP-User-Data-Length Mapped to ANSI-136 User Data Unit
TP-User-Data Mapped to ANSI-136 User Data Unit
3
4 If the TP-Status-Report-Request is requested, then Table 149 provides mapping to identify the
5 status of a message being sent to a CMT mobile from a GHOST mobile. The SMS-STATUS-
6 REPORT is encapsulated in a new SMDPP message to the status requester. The derived
7 values for the SMS-STATUS-REPORT are contained in Table 149.
3-173
X.S0023
2 Table 148: SMS_CauseCode to TP-STATUS Mapping

SMS_CauseCode TP-STATUS
(ANSI-41) (GSM)
Short message
transaction
completed
None sent. Positive 0000000 Short message received by
ACK. the SME
Not mapped. 0000001 Short message forwarded by
(future item for SMPP the SC to the SME but the SC
interworking) is unable to confirm delivery
Not applicable. 0000010 Short message replaced by

the SC
Reserved values
0000011..0001111 Reserved
0010000..0011111 Values specific to each SC
Temporary error,
SC still trying to
transfer SM
0000 0010 Network resource 0100000 Congestion
shortage
0010 0100 SMS delivery 0100001 SME busy
postponed
Not mapped 0100010 No response from SME
0100 0010 Other radio interface 0100011 Service rejected
problems
Not mapped 0100100 Quality of service not
available
Not mapped 0100101 Error in SME
Not mapped 0100110..0101111 Reserved
Not mapped 0110000..0111111 Values specific to each SC
Permanent error,
SC is not making
any more transfer
attempts
0110 0000 Encoding problem 1000000 Remote procedure error
0010 0110 Destination no longer 1000001 Incompatible destination
at this address
3
3-174
X.S0023
2 Table 148: SMS_CauseCode to TP-STATUS Mapping (concluded)
SMS_CauseCode TP-STATUS
(ANSI-41) (GSM)
0010 0111 Other terminal 1000010 Connection rejected by SME
problem
Not mapped 1000011 Not obtainable
available
Not mapped 1000101 No interworking available
MC internal procedure 1000110 SM Validity Period Expired
MC internal procedure 1000111 SM Deleted by originating
SME
MC internal procedure 1001000 SM Deleted by SC
Administration
MC internal procedure 1001001 SM does not exist (The SM
may have previously existed
in the SC but the SC no
longer has knowledge of it or
the SM may never have
previously existed in the SC)
Temporary error,
SC is not making
any more transfer
attempts
0010 0011 Destination resource 1100000 Congestion
shortage
Not mapped 1100001 SME busy
Not mapped 1100010 No response from SME
0110 0100 SMS not supported 1100011 Service rejected
available
Not mapped 1100101 Error in SME
3
4 All other values mapped to Service Rejected (0110 0011).
3-175
X.S0023
2 Table 149: SMS-STATUS-REPORT Derived Values

Parameter in SMS-STATUS- Status Value/derivation
REPORT
TP-Message-Type-Indicator M Set to “SMS-STATUS-REPORT”
TP-User-Data-Header-Indication O Not used or Set to value = 0
TP-More-Messages-to-Send M Set to value = 1
TP-Status-Report-Qualifier M Set to value = 0
TP-Message-Reference M Set by the MC to the appropriate value
TP-Recipient-Address M Set by the MC to the appropriate value
TP-Service-Center-Time-Stamp M Set by the MC to the appropriate value
TP-Discharge-Time M Set by the MC to the appropriate value
TP-Status M Set per Table 148
TP-Parameter-Indicator O -
TP-Protocol-Identifier O -
TP-Data-Coding-Scheme O -
TP-User-Data-Length O -
TP-User-Data O -
3

6
3-176
X.S0023
2 A.3 Callback Number

3 The Callback service enables SMS subscribers to be able to return calls to callers automatically
4 in an easy-to-use manner. Callers may provide their callback number to the SMSC by various
5 methods, including:
6  DTMF entry through a voicemail system, etc.
7  Paging the SMS subscriber directly (e.g., numeric paging entry)
8  Automatically through the Original Origination Address
9  As part of the text body of a short message
10 The callback number can be dialed through a single button (e.g., pressing the SEND key) or a
11 simple key sequence (i.e., 3 or less keystrokes) of the MS. Using the capabilities of the MS,
12 the user may edit the callback number prior to originating the call.
13

15
16 A.3.1.1 CMT to GHOST

17
18 The CMT mobile shall follow existing procedures as described in ANSI-136-710 to transmit a
19 callback number. If the MO-SMS is routed through an IIF to get to the subscriber’s home
20 SMSC, callback number information is in the application layer of the message and thus is
21 passed transparently.
22 Upon receipt at the SMSC, if the message contains the Callback Number parameter, then the
23 SMSC shall extract the callback number from this parameter and place it at the end of the TP-
24 User-Data field preceded by the phrase “CALLBACK: <space>”. Carriers should limit the
25 message size they inform their subscribers that they are allowed to send to account for the
26 sending of the callback number.
27
28 A.3.1.2 External SME (SMPP to GHOST)

29
30 Upon receiving of a submitted short message for delivery, the SMSC shall determine if the
31 recipient’s mobile requires short message delivery via GHOST. This determination by the
32 SMSC is an internal process and is beyond the scope of this document. If the recipient’s
33 mobile uses CMT to receive short messages, then the SMSC shall delivery the message via
34 procedures as defined in ANSI-136-710. If the recipient’s mobile uses GHOST, then the SMSC
35 shall extract the callback number from the SMPP callback_num parameter and place it at the
36 end of the TP-User-Data field preceded by the phrase “CALLBACK: <space>”. Carriers should
37 limit the message size they inform their subscribers that they are allowed to send to account for
38 the sending of the callback number.
39
3-177
X.S0023
1 A.3.1.3 GHOST to CMT

2
3 Since there is no GSM equivalent to the ANSI-136 Callback Number parameter, two solutions
4 exist to provide equivalent feature functionality.
5 1. The SMSC shall parse each message looking for a callback number based upon
6 a set of rules to determine the Callback number. It shall then place this number in
7 the ANSI-136 Callback Number parameter.
8 2. The SMSC shall transparently map the TP-User-Data to the SMS_BearerData

9 per Table 122. The MS shall be capable of parsing the message and extracting
10 the callback number based upon the number appearing in the MS display screen.
11 The subscriber shall be able to press one button (e.g., SEND key) to callback the
12 number showing on the display screen.
13 Solution 2 above is the recommended procedure to provide a callback number under this
14 scenario.
15
16 A.3.2 Message Mapping, Parameters and Parameters Values

17
18 A.3.2.1 CMT to GHOST

19 Mapping for messages, parameters and parameter values shall be as according to
20 A.1.2 Mapping of Messages, Parameters & Parameter Values.
21 A.3.2.2 External SME

22 ANSI-41/136 mapping for messages, parameters and parameter values for a GHOST message
23 is not affected by the Callback Number procedures.
24 A.3.2.3 GHOST to CMT

25 Mapping for messages, parameters and parameter values shall be as according to
26 A.2.2 Mapping of Messages, Parameters & Parameter Values.

3-178
X.S0023
2 ANNEX B Cause Code Mapping at Non-IIF Nodes

3 (Informative)
4 This annex is informative and describes processing that does not affect the IIF.
5 A mobile station shall respond to a received GHOST teleservice after processing the relay
6 layer. If the relay layer generates a failure, then the mobile station shall map the resulting RP-
7 Cause value into its equivalent R-Cause code according to Table 150.
8 Table 150: RP-ERROR Cause to R-Cause for Mobile Station Response to Mobile
9 Terminated Transfer Attempt.
GSM RP-ERROR Cause ANSI-136 R-Cause
Memory capacity exceeded (22) Memory capacity exceeded (22)
Invalid short message transfer reference Invalid short message transfer reference
value (81) value (81)
Semantically incorrect message(95) Invalid message, unspecified (95)
Invalid mandatory information (96) Mandatory information element error (96)
Message type nonexistent or not Message type non-existent or not
implemented (97) implemented (97)
Message not compatible with short Message not compatible with the short
message protocol state (98) message transfer state (101)
Information element nonexistent or not Information element non-existent or not
implemented (99) implemented (99)
Protocol error, unspecified (111) Protocol error, unspecified (111)
Interworking, unspecified (127) Interworking, unspecified (127)
All other values Protocol error, unspecified (111)
10
11 At the ANSI-136 MSC, the R-Cause code returned by a mobile station is mapped into a
12 corresponding ANSI-41 SMS_CauseCode for inclusion in an SMDPP Return Result message.
13 At the ANSI-136 MSC, the ANSI-41 SMS_CauseCodes are mapped to ANSI-136 R-DATA
14 REJECT R-Cause codes according to Table 151. The mobile station in turn maps the R-Cause
15 codes to RP-ERROR Causes according to Table 152.
3-179
X.S0023
1 Table 151: ANSI-41 SMS_CauseCode to ANSI-136 R-Cause Code Mapping

ANSI-41 SMS_CauseCode ANSI-136 R-Cause
Network failure (3) Network out of order (38)
Other network problems (5) Network out of order (38)
SMS origination denied (97) Unidentified subscriber (28) or

Facility rejected (29)
SMS not supported (100) Requested facility not implemented (69)
Address translation failure (1) Destination out of service (27) or
Unknown subscriber (30)
Network resource shortage (2) Congestion (42)
2
3 Table 152: ANSI-136 R-Cause Code to RP-ERROR Cause Mapping within the Mobile
4 Station
ANSI-136 R-Cause RP-ERROR Cause
Destination out of service (27) Destination out of service (27)
Unidentified subscriber (28) Unidentified subscriber (28)
Facility rejected (29) Facility rejected (29)
Unknown subscriber (30) Unknown subscriber (30)

Network out of order (38) Network out of order (38)
Congestion (42) Congestion (42)
Requested facility not implemented ((69) Requested facility not implemented (69)
5
3-180
X.S0023
1 ANNEX C: CDMA to GSM One-way Roaming Only

2 (Informative)
3
4 Optionally, IIF may support one way-roaming only from CDMA to GSM networks.
5 In this case, all the mapping tables are applicable only in GSM Foreign Mode.
6 The IIF maps the ANSI-41 authentication parameters to the GSM triplets
7 All the changes are made on the assumption that the new requirements for UIM/handsets are
8 working. Table 152 shows the location updating mapping in the GSM foreign mode.
9
10 Table 153: UPDATE_LOCATION_REQUEST ->REGNOT Parameter Mapping

_UPDATE_LOCATION_
REQUEST
MSID M
1 1
MSC Address M MSCID (Serving MSC) M
- QualificationInformationCode M
VLR Number M -
2
2
TerminalType O
2
LMSI U -
Supported CAMEL Phases C -
- -SYSACCTYPE3 O
11
1
12 These parameters are used to convey a unique identifier from the IIF to the HLR,
13 identifying the serving MSC/VLR.
2
14 Parameters are included in ANSI specifications IS-41-C and later.
3
15 SYSACCTYPE parameter is required for the one-way CDMA to GSM roaming optional
16 scenario and in this case the parameter must be set by IIF to indicate GSM access type.
17
3-181

Network Inter Working Between GSM MAP and ANSI-41 CDMA

Uploaded by

Copyright:

Available Formats

Network Inter Working Between GSM MAP and ANSI-41 CDMA

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Network Inter Working Between GSM MAP and ANSI-41 CDMA

Uploaded by

Copyright:

Available Formats

3GPP2 X.

Version Date: July, 2004

Network Interworking Between GSM MAP and

3 Contents ................................................................................................................................................. iii

4 List of Tables ...........................................................................................................................................v

9 1.2 Purpose ....................................................................................................................... 1

10 1.3 Scope .......................................................................................................................... 1

12 3 Definitions and Acronyms ........................................................................................................ 4

14 3.2 Acronyms .................................................................................................................... 7

15 4 Overview of Internetwork Roaming ....................................................................................... 11

16 5 IIF Reference Model and Description .................................................................................... 12

17 5.1 Reference Model....................................................................................................... 12

18 5.2 Description ................................................................................................................ 12

19 5.2.1 Provisioned Subscriber Data ..................................................................... 13

20 5.3 Interworking for Network Interfaces ......................................................................... 15

21 5.3.1 HLR - VLR Interface................................................................................... 16

22 5.3.2 Originating / Gateway MSC - Serving MSC Interface ............................... 18

23 5.3.3 MC / SMS-SC - Serving MSC Interface .................................................... 19

24 5.3.4 HLR – SGSN Interface................................................................................ 20

1 5.4 IIF Implementation Alternatives................................................................................ 21

2 5.4.1 IIF Resides within a GSM Network Entity .................................................. 21

3 5.4.2 IIF Resides within ANSI-41 Network Entity................................................ 21

4 5.4.3 IIF Resides within External Network Element............................................ 22

1 3 Definitions and Acronyms

23 ANSI-136 Foreign Mode

26 ANSI-136 Native Mode

29 ANSI-136 Native Subscriber

33 ANSI-41 Foreign Mode

6 CDMA Foreign Mode

11 CDMA Native Mode

14 CDMA Native Subscriber

33 GPRS in GSM Foreign Mode

7 GSM Foreign Mode

12 GSM Native Mode

15 GSM Native Subscriber

19 Late Call Forwarding

28 Subscriber Identity Module

2 AC Authentication Center in ANSI TIA/EIA-41 based networks

3 ADN Abbreviated Dialing Numbers

4 AMPS Advanced Mobile Phone Service

5 ANSI American National Standards Institute

6 AuC Authentication Center in GSM networks

7 BAIC Barring of All Incoming Calls

8 BAOC Barring of All Outgoing Calls

9 BIC-Roam Barring of Incoming Calls while Roaming Outside HPLMN Country

10 BMI Base Station, Mobile Switching System, and Interworking Function

11 BOIC Barring of Outgoing International Calls

12 BOIC-exHC Baring of Outgoing International Calls Except to HPLMN Country

13 CDMA Code-Division Multiple Access

14 CFB Call Forwarding Busy

15 CFNA Call Forwarding No Answer

16 CFNRc Call Forwarding Not Reachable

17 CFNRy Call Forwarding No Reply

18 CFU Call Forwarding Unconditional

19 CPHS Common PCN Handset Specification

21 DCS Data Coding Scheme

22 EDGE Enhanced Data Rates Through Global Evolution

23 EIA Electronics Industries Association

24 ESN Electronic Serial Number

25 ETSI European Telecommunications Standards Institute