3GPP GSM Network Interworking N.S0028-0 v1.0

3GPP2 N.
S0028
Version 1.0.0
Version Date: April 2002
Network Interworking Between GSM MAP and

ANSI-41 MAP Rev. B
Revision: 0
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 secretariat@3gpp2.org. Requests to
reproduce individual Organizational Partner's documents should be directed
to that Organizational Partner. See www.3gpp2.org for more information.
N.S0028-0
Revision History
Revision Date
Rev. 0 Initial Publication April 2002
Note
This specification is an extract of TIA TR-46.3 J-STD-038-B.
(This page is intentionally left blank)

N.S0028-0
2 Abstract
3
4 This standard addresses the interworking and interoperability between ANSI-41 MAP[1] and GSM
5 MAP[4] based networks in the support of subscribers roaming between networks. The
6 interworking and interoperability functionality of the services, information flows, and message
7 mappings are specified.
8 This standard consists of four volumes:
9 Volume 0 - Overview and Interworking Reference Model
10 Volume 1 - Service Descriptions
11 Volume 2 - Information Flows
12 Volume 3 - Message Mappings
13
14 This is Volume 0 - an overview of the Interworking and Interoperability Function (IIF) and the
15 associated network reference model.
16
Version 1 i
N.S0028-0
2 Document Revision History

3
Revision Date Version Comment
0 March 2001 Post Ballot version with ballot comments

A May 2001 0 Version 0- Addition of GPRS in GSM Foreign Mode
A June 2001 1 Version 1 – Editorial Changes
B July 2001 3 Version 3: Addition of CDMA/GSM two way roaming
B March 2002 5 Version V&V: Addition of CDMA/GSM two way and
one roaming
4
5
Version 1 ii
N.S0028-0
2 Contents
3 Abstract........................................................................................................................................i
4 Document Revision History.......................................................................................................... ii
5 Contents..................................................................................................................................... iii
6 List of Tables.............................................................................................................................. vi
7 List of Figures............................................................................................................................ vii
8 Foreword...................................................................................................................................viii
9 1 Introduction.....................................................................................................................1
10 1.1 General ..............................................................................................................1
11 1.2 Purpose..............................................................................................................1
12 1.3 Scope.................................................................................................................1
13 1.4 Organization.......................................................................................................1
14 2 References .....................................................................................................................3
15 3 Definitions and Acronyms................................................................................................4
16 3.1 Definitions ..........................................................................................................4
17 3.2 Acronyms ...........................................................................................................6
18 4 Overview of Internetwork Roaming..................................................................................8
19 5 IIF Reference Model and Description...............................................................................9
20 5.1 Reference Model ................................................................................................9
21 5.2 Description .........................................................................................................9

22 5.2.1 Provisioned Subscriber Data ...............................................................10
23 5.3 Interworking for Network Interfaces...................................................................11

24 5.3.1 HLR - VLR Interface............................................................................12
25 5.3.2 Originating / Gateway MSC - Serving MSC Interface............................13
26 5.3.3 MC / SMS-SC - Serving MSC Interface ...............................................14
Version 1 iii
N.S0028-0
1 5.3.4 HLR – SGSN Interface.........................................................................16
2 5.4 IIF Implementation Alternatives.........................................................................16

3 5.4.1 IIF Resides within a GSM Network Entity..............................................17
4 5.4.2 IIF Resides within ANSI-41 Network Entity ...........................................17
5 5.4.3 IIF Resides within External Network Element........................................18
6 5.4.4 IIF Resides within Both ANSI-41 and GSM Network Entities.................18
7 Abstract........................................................................................................................................i
8 Document Revision History.......................................................................................................... ii
9 Contents..................................................................................................................................... iii
10 List of Tables...............................................................................................................................v
11 List of Figures............................................................................................................................. vi
12 Foreword................................................................................................................................... vii
13 1 Introduction.....................................................................................................................1
14 1.1 General ..............................................................................................................1
15 1.2 Purpose..............................................................................................................1
16 1.3 Scope.................................................................................................................1
17 1.4 Organization.......................................................................................................1
18 2 References .....................................................................................................................2
19 3 Definitions and Acronyms................................................................................................3
20 3.1 Definitions ..........................................................................................................3
21 3.2 Acronyms ...........................................................................................................4
22 4 Overview of Internetwork Roaming..................................................................................6
23 5 IIF Reference Model and Description...............................................................................7
24 5.1 Reference Model ................................................................................................7
25 5.2 Description .........................................................................................................7

26 5.2.1 Provisioned Subscriber Data .................................................................7
Version 1 iv
N.S0028-0
1 5.3 Interworking for Network Interfaces.....................................................................8

2 5.3.1 HLR - VLR Interface..............................................................................8
3 5.3.2 Originating / Gateway MSC - Serving MSC Interface............................10
4 5.3.3 MC / SMS-SC - Serving MSC Interface ...............................................10
5 5.4 IIF Implementation Alternatives.........................................................................12

6 5.4.1 IIF Resides within a GSM Network Entity..............................................12
7 5.4.2 IIF Resides within ANSI-41 Network Entity ...........................................12
8 5.4.3 IIF Resides within External Network Element........................................13
9 5.4.4 IIF Resides within Both ANSI-41 and GSM Network Entities.................13
10
11
Version 1 v
N.S0028-0
2 List of Tables
3
4 There are no tables in this volume.
5
Version 1 vi
N.S0028-0
2 List of Figures
3
4 Figure 1: IIF Reference Model ................................................................................................... 9
5 Figure 2: HLR - VLR Interface...................................................................................................12
6 Figure 3: Originating / Gateway MSC - Serving MSC Interface..................................................14
7 Figure 4: MC / SMS-SC - Serving MSC Interface ......................................................................15
8 Figure 5: HLR- SGSN Interface.................................................................................................16
9 Figure 6: IIF Resides within GSM Network Element ..................................................................17
10 Figure 7: IIF Resides within ANSI-41 Network Element .............................................................17
11 Figure 8: IIF Resides within External Network Element .............................................................18
12 Figure 9: IIF Resides within both ANSI-41 and GSM Network Elements ....................................18
13 Figure 1: IIF Reference Model ................................................................................................... 7
14 Figure 2: HLR - VLR Interface.................................................................................................... 9
15 Figure 3: Originating / Gateway MSC - Serving MSC Interface..................................................10
16 Figure 4: MC / SMS-SC - Serving MSC Interface ......................................................................11
17 Figure 5: IIF Resides within GSM Network Element ..................................................................12
18 Figure 6: IIF Resides within ANSI-41 Network Element .............................................................12
19 Figure 7: IIF Resides within External Network Element .............................................................13
20 Figure 8: IIF Resides within both ANSI-41 and GSM Network Elements....................................13
21
22
Version 1 vii
N.S0028-0
2 Foreword
3 This foreword is not part of this standard.
4 This standard addresses the interworking and interoperability between ANSI-41 MAP and GSM
5 based networks in the support of subscribers roaming between networks. The objective of the
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
8 information flows and message mappings. However, not all services and associated capabilities
9 of ANSI-41 MAP and GSM MAP are supported by this standard. In general the attempt has been
10 to focus on the key subscriber services needed in the market.
11 The focus of the first release of this standard was on common GSM and ANSI-136 TDMA
12 services and associated network signaling (i.e. ANSI-41 MAP and GSM MAP). A prerequisite for
13 this interoperability is multi-mode mobile stations with an enhanced SIM card for roaming
14 between ANSI-136, GSM, and AMPS networks.
15 The first release of the standard did not define or require changes to existing ANSI-41 MAP or
16 GSM MAP to achieve the described interworking and interoperability. However, due to
17 differences between the services and associated capabilities of the MAP protocols, complete and
18 fully transparent interoperability may not have been achieved for some services. Future releases
19 of this standard may require changes to ANSI-41 MAP, GSM MAP and the associated services to
20 achieve full transparency while roaming between the different networks.
21 Additional or alternate service descriptions, information flows, and message mappings may be
22 required to support other air interfaces supported by ANSI-41 MAP (e.g., IS-95, CDMA2000).
23 This may be accomplished in a future release of this standard.
24 Aspects of TIA/EIA-136 Revision C have been incorporated into the standard.
25 Revision A adds GPRS service capability in GSM Foreign Mode.
26 Revision BC adds two way roaming between GSM and IS-95 CDMA systems. A prerequisite for
27 this interoperability is multi-mode mobile stations with an enhanced SIM card for roaming
28 between IS-95 and GSM networks.
29 Information disclosed in this document is subject to the export jurisdiction of the US Department of
30 Commerce as specified in Export Administration Regulations (title 15 CFR parts 730 through 774
31 inclusive). The information contained herein may not be exported or re-exported to Cuba, Iran, Iraq, Libya,
32 North Korea, Sudan, or Syria. Contact the Telecommunications Industry Association, Arlington, VA or
33 http://ftp.tiaonline.org/tr-45/tr45ahag/public%20documents.
34
35
Version 1 viii
N.S0028-0
1
2
3
4
9
10
11
12
13
14
15
16 (This page is intentionally left blank)
Version 1 ix
N.S0028-0
2 1 Introduction
3 1.1 General
4 When a subscriber to one network type (e.g., ANSI-41) roams to a network of another type (e.g.,
5 GSM), interworking and interoperability functions are required to support roaming and enable
6 service. This standard describes an Interworking and Interoperability Function (IIF) to support this
7 cross-technology roaming between ANSI-41 and GSM networks. The IIF supports a multi-mode
8 mobile station with a removable Subscriber Identity Module (SIM). The standard also defines the
9 required network message mappings between ANSI-41 MAP and GSM MAP to support the
10 mobile terminal and associated services.
11 This standard includes the support of cross-technology roaming between an ANSI-41 based
12 network and 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.
16
17 1.2 Purpose
18 The purpose for this standard is to define and describe the functions necessary for roaming
19 between ANSI-41 MAP and GSM MAP based networks in the support of roaming subscribers.
20 This includes a capability to allow a subscriber to an ANSI-41 based network (e.g., a TDMA or
21 CDMAn ANSI-136 native subscriber) with a mobile terminal supporting GPRS service to roam to
22 a GPRS network in GSM Foreign Mode. GPRS support for IS-95 handsets is not addressed in
23 this release of the standard.
24 1.3 Scope
25 The scope of this standard are the services, information flows and message mappings which
26 require interworking and interoperability functional specifications to support roaming between
27 ANSI-41 MAP and GSM MAP networks.
28 The scope of this volume is to provide a description of interstandard roaming along with an
29 overview and network reference model for the Interworking and Interoperability Function (IIF).
30 1.4 Organization
31 This standard is divided into four separate volumes:
32 Volume 0 - Overview and Network Reference Model
36
37 Volume 0 is organized as follows:
38 1 Introduction - provides an overview, purpose, scope, and organization of this volume.
1
N.S0028-0
1 2 References - is a list of references used in the preparation of this volume of this Interim
2 Standard.
3 3 Definitions and Acronyms - defines words and acronyms that are used in this volume of this
4 Interim Standard.
5 4 Overview of Internetwork Roaming - provides an overview of interstandard roaming and
6 defines the terms used to describe it.
7 5 IIF Reference Model and Description - provides an architecture description of the
8 Interoperability and Interworking Function (IIF), an overview of its functionality,
9 and description of its relationship and interfaces to other network elements.
10
Version 1 2
N.S0028-0
2 2 References
3
4 [1] TIA/EIA-136: “TDMA Cellular/PCS--Radio Interface--Mobile Station-Base Station
5 Compatibility Standard,” March 2000, ANSI.
6
7 [2] TIA/EIA-41-D: “Cellular Radiotelecommunications Intersystem Operations,” December 1997,
8 ANSI.
9
10 [3] TIA/EIA-553: “Mobile Station – Land Station Compatibility Specification,” September 1989,
11 ANSI.
12 [4] GSM 09.02 Version 6.2.0 Release 1997 “Digital cellular telecommunication system (Phase
13 2+); Mobile Application Part (MAP) specification”, August 1998, ETSI.
14
15 [5] TIA/EIA/IS-129, “Interworking/Interoperability Between DCS 1900 and IS-41 Based MAPs for
16 1800 MHz Personal Communications Systems,” Phase 1, July 1996.
17 [6] TIA/EIA/IS-637”Short Message Services for Wideband Spread Spectrum Cellular Systems”
18 [7] TIA/EIA/IS 737A”IS-41 support for data services for digital terminals (TDMA and CDMA)”
19 [8] TIA/EIA/IS 735 “IS-41 support for IS-95-A (advanced CDMA)”
20 [9] TIA/EIA/TSB58-E A “Administration of Parameter Value Assignments for TIA/EIA Spread

21 Spectrum Standards” , January 2002
22
23 [10] TIA/EIA-95-B - Mobile Station-Base Station Compatibility Standard for Dual-Mode Spread
24 Spectrum Systems; Published October 1998.
25
26 [11] "TIA/EIA-IS-2000-A, cdma2000 Series, March 2000, plus addenda"Mobile Station-Base
27 Station Compatibility Standard for Dual-Mode Spread Spectrum Systems;
28 [12] TIA/EIA-868 – ANSI-41-D Network Based Enhancements to support one-way roaming to
29 GSM, Published TBD.
30 [12]"Enhanced Cryptographic Algorithms, Revision B," TR45AHAG, Published TBD
31
3
N.S0028-0
2 3 Definitions and Acronyms

3 3.1 Definitions
4 AMPS
5 Advanced Mobile Phone Service (AMPS) is the same as EIA/TIA-553[3], which is an analog air
6 interface protocol standard for mobile stations and their associated base stations. AMPS
7 networks use ANSI-41 for intersystem signaling.
8 ANSI-41
9 ANSI-41, as used in this document, refers to TIA/EIA-41[2] and the modifications and
10 enhancements as noted in IS-751 and IS-807. This is a network protocol standard to support
11 intersystem operation of cellular networks, such as ANSI-136 or CDMAIS-95 networks. Key
12 intersystem support defined by ANSI-41 includes automatic roaming, intersystem handoff, and
13 intersystem operation, administration, and maintenance. Among other things, ANSI-41 defines
14 the interfaces between MSCs, between the MSC/VLR and the HLR/AC, and between the MSC
15 and the Short Message Service Center (SMS-SC) or Teleservice Server (TS).
16 ANSI-136
17 ANSI-136, as used in this document, refers to TIA/EIA-136[1], which is a TDMA air interface
18 protocol standard for mobile stations and their associated base stations. ANSI-136 is a dual-
19 mode standard that includes digital (TDMA) operation at 800 MHz and 1900 MHz, and analog
20 (AMPS) operation at 800 MHz. ANSI-136 networks use ANSI-41 for intersystem signaling.
21 ANSI-136 Mode
22 ANSI-136 mode indicates the condition or state of a mobile station accessing an ANSI-136
23 network.
24 ANSI-136 Foreign Mode
25 ANSI-136 foreign mode indicates the condition or state of a GSM native subscriber accessing an
26 ANSI-136 network.
27 ANSI-136 Native Mode
28 ANSI-136 native mode indicates the condition or state of an ANSI-136 native subscriber
29 accessing an ANSI-136 network.
30 ANSI-136 Native Subscriber
31 ANSI-136 native subscriber indicates an end user whose primary or home subscription resides in
32 an ANSI-136 network. These subscribers include both home subscribers from the ANSI-136
33 network, as well as roamers from other ANSI-136 networks.
34
35 CDMA CDMA as used in this document, refers to TIA/EIA -95 [9] or TIA/EIA-2000 [10], which is a
36 CDMA
37 air interface protocol standard for mobile stations and their associated base stations. CDMA is a
38 dual-mode standard that includes digital (CDMA) operation and analog (AMPS) operation. CDMA
40 CDMA Mode
41 CDMA mode indicates the condition or state of a mobile station accessing an CDMA network.
42
Version 1 4
N.S0028-0
1 CDMA Foreign Mode

2 CDMA foreign mode indicates the condition or state of a GSM native subscriber accessing a
3 CDMA network.
4
5 CDMA Native Mode
6 CDMA native mode indicates the condition or state of an CDMA native subscriber accessing an
7 CDMA network.
8
9 CDMA Native Subscriber
10 CDMA native subscriber indicates an end user whose primary or home subscription resides in an
11 CDMA network. These subscribers include both home subscribers from the CDMA network, as
12 well as roamers from other CDMA networks.
13
14 GPRS in GSM Foreign Mode
15 GPRS in GSM Foreign Mode is a subset of GSM Foreign Mode and indicates the condition or
16 state of an ANSI-41136 native subscriber accessing a GPRS network; the GPRS network may be
17 coupled with a GSM network.
18
19 GSM
20 Global System for Mobile Communications (GSM) defines both air interface and network
21 intersystem protocol standards for mobile stations (MS), base station systems (BSS), and
22 network switching systems (NSS).
23 GSM Mode
24 GSM mode indicates the condition or state of a mobile station accessing a GSM network.
25 GSM Foreign Mode
26 GSM foreign mode indicates the condition or state of an ANSI-41136 or an IS-95 native
27 subscriber accessing a GSM network.
28 GSM Native Mode
29 GSM native mode indicates the condition or state of a GSM native subscriber accessing a GSM
30 network.
31 GSM Native Subscriber
32 GSM native subscriber indicates an end user whose primary or home subscription resides in a
33 GSM network. These subscribers include both home subscribers from the GSM network, as well
34 as roamers from other GSM networks.
35 Mobile Equipment
36 The radio transceiver, main processing unit, and man-machine interface necessary to access the
37 radio network.
38 Mobile Station
39 The mobile equipment and the SIM together make up the mobile station, which is the wireless
40 radiotelephone used by the subscriber.
41 Subscriber Identity Module (SIM)
42 A smart card that plugs into the mobile equipment and that contains the authentication
43 algorithms, and stores service-oriented subscription information.
5
N.S0028-0
1 3.2 Acronyms
2 AC Authentication Center in ANSI TIA/EIA-41 based networks
3 AuC Authentication Center in GSM networks
4 AMPS Advanced Mobile Phone Service
5 ANSI American National Standards Institute
6 CDMA Code-Division Multiple Access
7 EIA Electronics Industries Association
8 ESN Electronic Serial Number
9 ETSI European Telecommunications Standards Institute
10 GMSC Gateway Mobile Switching Center
11 GSM Global System for Mobile Communication
12 GGSN Gateway GPRS Serving Node
13 GPRS General Packet Radio Service
14 HLR Home Location Register
15 HPLMN Home Public Land Mobile Network
16 IIF Interworking and Interoperability Function
17 IMSI International Mobile Subscriber Identity
18 ITU International Telecommunications Union
19 MAP Mobile Application Part
20 MC ANSI-41136 Message Center (for SMS)
21 ME Mobile Equipment
22 MIN Mobile Identification Number
23 MS Mobile Station
24 MSC Mobile Switching Center
25 MSID Mobile Station Identity
26 MSISDN Mobile Subscriber ISDN Number
27 PDP Packet Data Protocol
Version 1 6
N.S0028-0
1 PLMN Public Land Mobile Network
2 SGSN Serving GPRS Support Node
3 SIM Subscriber Identity Module
4 SMS Short Message Service
5 SMS-GMSC GSM Short Message Service Gateway Mobile Switching Center
6 SMS-IWMSC GSM Short Message Service Interworking Mobile Switching Center
7 SMS-SC GSM Short Message Service Center
8 SS7 Signaling System 7
9 TDMA Time Division Multiple Access
10 TIA Telecommunications Industry Association
11 VLR Visited Location Register

12
7
N.S0028-0
2 4 Overview of Internetwork Roaming

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

3
4 5.1 Reference Model

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

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

45 This following describes the individual network interfaces for which interoperability is provided by
46 the IIF. For each particular interoperability function and interface interworking, the IIF
47 simultaneously emulates a network element using foreign protocol messaging and a
48 corresponding network element using native protocol messaging. For each particular messaging
49 operation, the IIF converts the operation from the foreign protocol to the native protocol, and vice
11
N.S0028-0
1 versa. The emulation functions in the IIF conform to existing ANSI-41 and GSM protocols when
2 communicating over the external interfaces.
3 The following figures depict the emulated network elements within the IIF using hashed lines. The
4 hashed lines connecting emulated network elements within the IIF represent internal, conversion
5 or mapping interfaces. All solid connecting lines depict standard ANSI-41 or GSM interfaces
6 based on existing protocol.
7 The arrow above each figure represents information exchange for the top half of the figure, while
8 the arrow below each figure represents information exchange for the bottom half of the figure.
9 5.3.1 HLR - VLR Interface

10 The IIF provides an interface between the subscriber's HLR and any VLR which uses a foreign
11 network signaling protocol. This interworking is provided over the interface reference "D" depicted
12 in the network reference model. Figure 2 below depicts the interworking and control interface
13 provided by the IIF in this case.
14
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
15
16 Figure 2: HLR - VLR Interface
17
18 5.3.1.1 ANSI-136 Foreign Mode Implementation for GSM Subscriber
19 When a GSM native subscriber operates in ANSI-136 foreign mode, the mobile station shall use
20 the ANSI-136 air interface. The interoperability gateway or IIF shall provide both ANSI-41 HLR
21 and GSM VLR emulation to allow the subscriber to automatically register and obtain service. To
22 the visited ANSI-41 network, the subscriber appears to register with the IIF, emulating an
23 ANSI-41 HLR. This emulated ANSI-41 HLR acts as a limited proxy for the actual GSM HLR, with
24 the true GSM HLR retaining ultimate control. At the same time, to the home GSM network, the
25 subscriber appears to register from the IIF, emulating a GSM VLR. The IIF links ANSI-41 MAP
26 operations and data to the equivalent GSM MAP operations and data, and vice versa, in order to
27 support interoperability.
Version 1 12
N.S0028-0
1 To support ANSI-136 foreign mode operation, an ANSI-136 Authentication Center (AC) can be
2 integrated into the IIF gateway or implemented as a separate network element.
3
4 5.3.1.2 GSM Foreign Mode Implementation for ANSI-136 Subscriber
5 Similarly, when an ANSI-136 native subscriber operates in GSM foreign mode, the mobile station
6 shall use the GSM air interface. The interoperability gateway or IIF shall provide both GSM HLR
7 and ANSI-41 VLR emulation to allow the subscriber to automatically register and obtain service.
8 To the visited GSM network, the subscriber appears to register with the IIF, emulating a GSM
9 HLR. This emulated GSM HLR acts as a limited proxy for the actual ANSI-41 HLR, with the true
10 ANSI-41 HLR retaining ultimate control. At the same time, to the home ANSI-136 network, the
11 subscriber appears to register from the IIF, emulating an ANSI-136 VLR. The IIF links GSM MAP
12 operations and data to the equivalent ANSI-41 MAP operations and data, and vice versa, in order
13 to support interoperability.
14 To support GSM foreign mode operation, a GSM Authentication Center (AuC) can be integrated
15 into the IIF gateway or implemented as a separate network element.
16 5.3.1.3 CDMAIS-95 Foreign Mode Implementation for GSM Subscriber
17 When a GSM native subscriber operates in IS-95 foreign mode, the mobile station shall use the
18 IS-95 CDMA air interface. The interoperability gateway or IIF shall provide both ANSI-41 HLR and
19 GSM VLR emulation to allow the subscriber to automatically register and obtain service. To the
20 visited ANSI-41 network, the subscriber appears to register with the IIF, emulating an ANSI-41
21 HLR. This emulated ANSI-41 HLR acts as a limited proxy for the actual GSM HLR, with the true
22 GSM HLR retaining ultimate control. At the same time, to the home GSM network, the subscriber
23 appears to register from the IIF, emulating a GSM VLR. The IIF links ANSI-41 MAP operations
24 and data to the equivalent GSM MAP operations and data, and vice versa, in order to support
25 interoperability.
26 To support IS-95 foreign mode operation, an IS-95 Authentication Center (AC) can be integrated
28
29 5.3.1.4 GSM Foreign Mode Implementation for IS-95CDMA Subscriber
30 Similarly, when an IS-95CDMA native subscriber operates in GSM foreign mode, the mobile
31 station shall use the GSM air interface. The interoperability gateway or IIF shall provide both
32 GSM HLR and ANSI-41 VLR emulation to allow the subscriber to automatically register and
33 obtain service. To the visited GSM network, the subscriber appears to register with the IIF,
34 emulating a GSM HLR. This emulated GSM HLR acts as a limited proxy for the actual ANSI-41
35 HLR, with the true ANSI-41 HLR retaining ultimate control. At the same time, to the home IS-
36 95CDMA network, the subscriber appears to register from the IIF, emulating an IS-95CDMA VLR.
37 The IIF links GSM MAP operations and data to the equivalent ANSI-41 MAP operations and data,
38 and vice versa, in order to support interoperability.
41
42
43 5.3.2 Originating / Gateway MSC - Serving MSC Interface

44 The IIF provides a MAP interface between the subscriber's originating or gateway MSC to a
45 serving MSC which uses a foreign network signaling protocol. This interworking is provided over
46 the interface reference "E" depicted in the network reference model. In this case, no ISUP or MF
13
N.S0028-0
1 signaling is supported over this interface. Figure 3 below depicts the interworking and control
2 interface provided by the IIF in this case.
3 This interface is key to supporting optimal routing for late call forwarding, where the serving MSC
4 wishes to signal back to the originating or gateway MSC in order to request forwarding of the call.
5 In order to support optimal routing for late call forwarding, the IIF provides originating or gateway
6 MSC emulation.
7
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
8
9 Figure 3: Originating / Gateway MSC - Serving MSC Interface
10
11 5.3.3 MC / SMS-SC - Serving MSC Interface

12 The IIF provides an interface from the subscriber's short message service message center (MC /
13 SMS-SC) to a serving MSC which uses a foreign network signaling protocol. This interworking is
14 provided over the interface references "Q" and "E" depicted in the network reference model. In
15 the case of ANSI-41 messaging, the MC has a direct "Q" interface to the serving MSC. In the
16 case of GSM messaging, the SMS-SC interfaces with the serving MSC via the SMS Interworking
17 MSC (SMS-IWMSC) or the SMS Gateway MSC (SMS-GMSC) over the "E" interface. Figure 4
18 below depicts the interworking and control interface provided by the IIF in this case.
19
20
Version 1 14
N.S0028-0

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
1
2 Figure 4: MC / SMS-SC - Serving MSC Interface
3
4 5.3.3.1 ANSI-41136 Foreign Mode Implementation for GSM Subscriber
5 For short message service (SMS) interoperability, the IIF shall provide ANSI-41 Message Center
6 (MC) emulation, acting as a limited proxy for the subscriber’s GSM Short Message Service
7 Center (SMS-SC). The IIF links GSM MAP operations and data to the equivalent ANSI-41 MAP
8 operations and data, and vice versa.
9
10 5.3.3.2 GSM Foreign Mode Implementation for ANSI-41136 Subscriber
11 For SMS interoperability, the IIF shall provide GSM SMS-SC emulation, as well as SMS-GMSC
12 or SMS-IWMSC emulation, acting as a limited proxy for the subscriber’s ANSI-41 MC. The IIF
13 links ANSI-41 MAP operations and data to the equivalent GSM MAP operations and data, and
14 vice versa. In some cases, the IIF may need to originate short messages in order to support
15 interoperability.
16
15
N.S0028-0
2 5.3.4 HLR – SGSN Interface

3
4 The IIF provides an interface between the subscriber's HLR and any SGSN which uses a foreign
5 network signaling protocol. This interworking is provided over the interface reference "Gr"
6 depicted in the network reference model. Figure 5 below depicts the interworking and control
7 interface provided by the IIF in this case.
8
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
9 Figure 5: HLR- SGSN Interface
10
11 5.3.4.1 GPRS in GSM Foreign Mode Implementation for ANSI-41136 Subscriber
12 When an ANSI-41136 native subscriber operates GPRS in GSM foreign mode, the mobile station
13 shall use the GSM air interface. The interoperability gateway or IIF shall provide both GSM HLR
14 and ANSI-41 VLR emulation to allow the subscriber to automatically register and obtain service.
15 To the visited GSM network, the subscriber appears to register with the IIF, emulating a GSM
16 HLR. This emulated GSM HLR acts as a limited proxy for the actual ANSI-41 HLR, with the true
17 ANSI-41 HLR retaining ultimate control. At the same time, to the home ANSI-41 network, the
18 subscriber appears to register from the IIF, emulating an ANSI-41 VLR. The IIF links GSM MAP
19 operations and data to the equivalent ANSI-41 MAP operations and data, and vice versa, in order
20 to support interoperability.
23
24 5.4 IIF Implementation Alternatives

25 There are four alternatives for the implementation of the IIF functional element with respect to the
26 network reference model and the network entities that are served. See “5 IIF Reference Model
27 and Description” for applicable interfaces.
Version 1 16
N.S0028-0
1 5.4.1 IIF Resides within a GSM Network Entity

2 The IIF may reside entirely inside an existing GSM network entity as a separate functional
3 element. Each of the interfaces can be supported with this implementation alternative.
T IA /E IA - 4 1 G SM
N e tw o rk N e tw o rk
E le m e n t E le m e n t
IIF
5 Figure 6: IIF Resides within GSM Network Element

6
7 5.4.2 IIF Resides within ANSI-41 Network Entity

8 The IIF may reside entirely inside an existing ANSI-41 network entity as a separate functional
T IA /E IA -4 1 GSM
N e tw o rk N e tw o rk
E le m e n t E le m e n t
IIF
10
11 Figure 7: IIF Resides within ANSI-41 Network Element

12
13
17
N.S0028-0
2 5.4.3 IIF Resides within External Network Element

3 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
6 Figure 8: IIF Resides within External Network Element
8 5.4.4 IIF Resides within Both ANSI-41 and GSM Network Entities
9 Finally, the IIF may reside within both existing ANSI-41 and GSM network entities at the same
10 time. In this case, each individual subscriber is likely to be served by one particular IIF, although
11 the use of multiple IIFs per subscriber is possible. Again, each of the interfaces can be supported
12 with this implementation alternative. While multiple IIFs can support one particular subscriber,
13 each network interworking function would be supported by one specific IIF implementation.
14
TIA/EIA-41 GSM
Network Network
Element Element
IIF IIF
15
16 Figure 9: IIF Resides within both ANSI-41 and GSM Network Elements
17
Version 1 18
N.S0028-0
1 Abstract
2 This standard addresses the interworking and interoperability between ANSI-41 MAP[3] and GSM
3 MAP[21] based networks in the support of subscribers roaming between networks. The interworking
4 and interoperability functionality of the services, information flows, and message mappings are
5 specified.
6 This standard consists of four Volumes:
11 This is Volume 1. Volume 1 is based on ANSI-664[1] and GSM stage 1’s (see GSM 02-series e.g.,
12 GSM 02.04, etc. in the References section). Some modifications (primarily simplifications) were made
13 for the purpose of specifying the degree of interoperability desired. ANSI-664 services and GSM
14 services do not necessarily align.
15
Ballot Version i
N.S0028-0

3
Revision Date Version Comments
0 March 2001 Initial Release J-STD-038

A April 12, 2001 0 Added Section 4.10 GPRS.
A May 23, 2001 1 Misc. editorial changes.

A June 26, 2001 2 New Foreword; Modifications to 4.10.2.4.
A August 01, 2001 3 Editorial changes.
A August 01, 2001 4 Editorial changes; Modifications to 4.10.2.8 SMS Impacts.

A August 14, 2001 5 Editorial changes; Modifications to 4.10 GPRS.
A August 15, 2001 6 Ballot Version; Modifications to 4.10 GPRS

one roaming
5
Ballot Version ii
N.S0028-0
Contents
Ballot Version iii

Abstract.............................................................................................................................................. i
Document Revision History................................................................................................................ ii

N.S0028-0
Contents........................................................................................................................................... iii
List of Tables.................................................................................................................................... vi
List of Figures.................................................................................................................................. vii
Foreword.........................................................................................................................................viii
1 Introduction .................................................................................................................................1
1.1 General 1
1.2 Purpose 1
1.3 Scope 1
1.4 Organization 2
2 References..................................................................................................................................3
3 Definitions and Acronyms............................................................................................................5
3.1 Definitions 5
3.2 Acronyms 8
4 Stage 1 Service Descriptions.....................................................................................................10
4.1 Authentication..................................................................................................................10
4.2 Call Forwarding................................................................................................................17
4.3 Optimal Routing for Late Call Forwarding .........................................................................48
4.4 Call Waiting (CW) ............................................................................................................53
4.5 Three-Way Calling (3WC) and Multi-Party (MPTY)..........................................................64
4.6 Calling Number / Line Identification Presentation..............................................................75
4.7 Call Barring (CB) and Operator Determined Barring (ODB) ..............................................81
4.8 Short Message Teleservice Support (ANSI-41 Networks).................................................89
4.9 Message Waiting Notification ...........................................................................................96
4.10 GPRS in GSM Foreign mode ......................................................................................... 102
Abstract.............................................................................................................................................. i
Document Revision History................................................................................................................ ii
Contents........................................................................................................................................... iii
List of Tables..................................................................................................................................... v
List of Figures................................................................................................................................... vi
Foreword......................................................................................................................................... vii
Ballot Version iv
1 Introduction .................................................................................................................................1
N.S0028-0
Ballot Version v
N.S0028-0
List of Tables
Table 1: CW Subscription Options ................................................................................................... 53
Table 2: 2-Way State for Call Waiting ............................................................................................. 56
Table 3: 2-Way Notification State for Call Waiting ........................................................................... 57
Table 4: 2-Way CW State for Call Waiting........................................................................................ 58
Table 5: ANSI-41 Foreign Mode Interoperability for Barring of Outgoing Calls .................................. 82
Table 6: GSM Foreign Mode Interoperability for Outgoing Call Restrictions...................................... 82
Table 7: Call Barring Activation Options........................................................................................... 83
Table 8: Call Barring Deactivation Options....................................................................................... 84
Table 1: CW Subscription Options ................................................................................................... 51
Table 2: 2-Way State for Call Waiting ............................................................................................. 54
Table 3: 2-Way Notification State for Call Waiting ........................................................................... 55
Table 4: 2-Way CW State for Call Waiting........................................................................................ 56
Table 5: ANSI-41 Foreign Mode Interoperability for Barring of Outgoing Calls .................................. 80
Table 6: GSM Foreign Mode Interoperability for Outgoing Call Restrictions ...................................... 80
Table 7: Call Barring Activation Options........................................................................................... 81
Table 8: Call Barring Deactivation Options....................................................................................... 82
Ballot Version vi
N.S0028-0
List of Figures
There are no figures in this volume.
Ballot Version vii

N.S0028-0
2 Foreword
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
12 and associated network signaling (i.e. ANSI-41 MAP and GSM MAP). A pre-requisite for this
13 interoperability is multi-mode mobile stations with an enhanced SIM card for roaming between ANSI-
14 136, GSM, and AMPS networks.
15 The first release of the standard did not define or require changes to existing ANSI-41 MAP or GSM
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.
22 required to support other air interfaces supported by ANSI-41 MAP (e.g., IS-95, cdmaOne and
23 cdma2000). This may be accomplished in a future release of this standard.
24 Aspects of TIA/EIA-136 Rev C have been incorporated into this standard.
25 Revision A adds the capability of getting GPRS services when roaming in GSM Foreign Mode.
26
27 Revision B adds roaming between GSM and CDMA systems
Ballot Version viii

N.S0028-0
1 1 Introduction
2
3 1.1 General
5 GSM), interworking and interoperability functions are required to support roaming and enable service.
6 This standard describes an Interworking and Interoperability Function (IIF) to support this cross-
7 technology roaming between ANSI-41 and GSM networks. The IIF supports a multi-mode mobile
8 station with a removable Subscriber Identity Module (SIM). The standard also defines the required
9 network message mappings between ANSI-41 MAP and GSM MAP to support the mobile terminal
10 and associated services.
11 This standard includes the support of cross-technology roaming from an ANSI-41 based network to a
12 GPRS network. The GPRS network may be coupled with a GSM network. This feature requires
13 enhancement to the Interworking and Interoperability Function (IIF) which supports a multi-mode
14 mobile station and Subscriber Identity Module (SIM) with GPRS functionality.
15
16 1.2 Purpose
17 The purpose for this standard is to define and describe the functions necessary for roaming between
18 ANSI-41 MAP and GSM MAP based networks in the support of roaming subscribers. This includes a
19 capability to allow a subscriber to an ANSI-41 based network (e.g., an ANSI-136 or CDMA native
20 subscriber) with a mobile terminal supporting GPRS service to roam to a GPRS network in GSM
21 Foreign Mode.
22
23 1.3 Scope
24 The scope of this standard are the services, information flows, and message mappings which require
25 interworking and interoperability functional specifications to support roaming between ANSI-41 MAP
26 and GSM MAP networks.
27 The scope of this volume is a high level (stage 1) description of the services and functionality required
28 to support GSM and ANSI-41 network interoperability. In particular, when in foreign mode (roaming in
29 non-native mode technology), subscribers are able to:
30 roam and register (with authentication);
31 originate and terminate calls;
32 have the following supplementary services operate:
33 - Call Forwarding,
34 - Call Waiting,
35 - Calling Number Identification Presentation - Line Identification Presentation,
36 - Call Barring, and
37 - GSM Multi-Party - ANSI-41 3-way Calling and Conference;
Ballot Version 1
N.S0028-0
1 have Short Message Service access and Message Waiting Notification;
2 have Late Call Forwarding optimally routed; and
3 have GPRS service in GSM Foreign Mode.
5 1.4 Organization
6 This standard is organized into the following volumes:
11 This volume 1 is organized according to the following:
12 2 References - a list of references.
13 3 Definitions and Acronyms - definions of words and acronyms.
14 4 Stage 1 Service Descriptions - descriptions of the interoperable network features.
15
Ballot Version 2
N.S0028-0
1 2 References
2
3 [1] TIA/EIA-664: “Cellular Features Description”, Telecommunications Industry Association;
4 February 2000, ANSI.
5 [2] TIA/EIA-136: “TDMA Cellular/PCS--Radio Interface--Mobile Station-Base Station Compatibility
6 Standard,” March 2000, ANSI.
7 [3] TIA/EIA-41-D: “Cellular Radiotelecommunications Intersystem Operations,” December 1997,
8 ANSI.
9 [4] TIA/EIA/IS-751, "TIA/EIA 41-D Modifications to Support IMSI, February 1998".
10 [5] TIA/EIA/IS-807, "TIA/EIA-41-D Enhancements for Internationalization".
11 [6] EIA/TIA-553: “Mobile Station – Land Station Compatibility Specification,” September 1989,
12 ANSI.
13 [7] “Common Cryptographic Algorithms, Revision C,” October 27, 1998, TR45AHAG.
14 [8] TIA/EIA-136-510 “Authentication, encryption of signaling information/user data and privacy”.
15 [9] GSM 02.04 version 6.1.1 Release 1997, “General on Supplementary Services”, (Phase 2+),
16 ETSI.
17 [10] GSM 02.09 version 6.1.0 Release 1997, “Digital cellular telecommunications system Security
18 Aspects”, (Phase 2+), ETSI.
19 [11] GSM 02.30 version 6.1.0 Release 1997, “Man-Machine Interface (MMI) of the Mobile Station”,
20 (Phase 2+), ETSI.
21 [12] GSM 02.41 version 6.0.0, Release 1997, "Operator Determined Barring (ODB)", (Phase 2+),
22 ETSI.
23 [13] GSM 02.79 version 6.0.0, Release 1997, “Support of Optimal Routeing (SOR) Service
24 Definition (Stage 1)”, (Phase 2+), ETSI.
25 [14] GSM 02.81 version 7.0.0 Release 1998, “Line Identification Supplementary Services – Stage 1“
27 [15] GSM 02.82 version 6.0.0 Release 1997, “Call Forwarding (CF) Supplementary Services - Stage
28 1” (Phase 2+), ETSI.
29 [16] GSM 02.83 version 6.0.0 Release 1997, “Call Waiting (CW) and Call Holding (HOLD)
30 Supplementary Services - Stage 1”, (Phase 2+), ETSI.
31 [17] GSM 02.84 version 6.0.0 Release 1997, “MultiParty (MPTY) Supplementary Services – Stage
32 1”, (Phase 2+), ETSI.
33 [18] GSM 02.85 version 6.0.0 Release 1997, “Closed User Group (CUG) Supplementary Services –
34 Stage 1 ”, (Phase 2+), ETSI.
35 [19] GSM 02.86 version 6.0.0 Release 1997, “Advice of Charge (AOC) Supplementary Services –
36 Stage 1”, (Phase 2+), ETSI.
37 [20] GSM 02.88 version 6.0.0 Release 1997, “Call Barring (CB) Supplementary Services – Stage 1”
Ballot Version 3
N.S0028-0
1 [21] GSM 09.02 version 6.2.0 Release 1997, “Digital cellular communication system (Phase2+);
2 Mobile Application Part (MAP) specification”, August 1998, ETSI
3 [22] GSM 02.60 version 6.3.1 Release 1997 “General Packet Radio Service (GPRS); Service
4 Description, Stage 1
7 [25] TIA/EIA/TSB58-E “Administration of Parameter Value Assignments for TIA/EIA Spread

11
12 [27] "TIA/EIA-IS-2000-A, cdma2000 Series, March 2000, plus addenda"Mobile Station-Base Station
13 Compatibility Standard for Dual-Mode Spread Spectrum Systems;
15 GSM, Published TBD. [12]"Enhanced Cryptographic Algorithms, Revision B," TR45AHAG, Published TBD
16
17
Ballot Version 4
N.S0028-0

2
3 3.1 Definitions
4 AMPS
5
6 Advanced Mobile Phone Service (AMPS) is the same as ANSI EIA/TIA-553[6], which as an analog air
7 interface protocol standard for mobile stations and their associated base stations. AMPS networks
8 use ANSI-41 for intersystem signaling.
9
10 ANSI-41
11
12 ANSI-41, as used in this document, refers to TIA/EIA-41[3] and the modifications and enhancements
13 as noted in IS-751[4] and IS-807[5]. This is a network protocol standard to support intersystem
14 operation of cellular networks, such as ANSI-136 or CDMA networks. Key intersystem support
15 defined by ANSI-41 includes automatic roaming, intersystem handoff, and intersystem operation,
16 administration, and maintenance. Among other things, ANSI-41 defines the interfaces between
17 MSCs, between the MSC/VLR and the HLR/AC, and between the MSC and the Short Message
18 Service Center (SMS-C) or Teleservice Server (TS).
19
20 ANSI-136
21
22 ANSI-136, as used in this document, refers to TIA/EIA-136[2], which is a TDMA air interface protocol
23 standard for mobile stations and their associated base stations. ANSI-136 is a dual-mode standard
24 that includes digital (TDMA) operation at 800 MHz and 1900 MHz, and analog (AMPS) operation at
25 800 MHz. ANSI-136 networks use ANSI-41 for intersystem signaling.
26
27 ANSI-136 Mode
28
29 ANSI-136 mode indicates the condition or state of a mobile station accessing an ANSI-136 network.
30
32
35
37
38 ANSI-136 native mode indicates the condition or state of an ANSI-136 native subscriber accessing an
40
42
43 ANSI-136 native subscriber indicates an end user whose primary or home subscription resides in an
44 ANSI-136 network. These subscribers include both home subscribers from the ANSI-136 network, as
45 well as roamers from other ANSI-136 networks.
46
48
50 ANSI-41 based network.
Ballot Version 5
N.S0028-0
1
2
3
4 GSM
5
6 Global System for Mobile Communications (GSM) defines both air interface and network intersystem
7 protocol standards for mobile stations (MS), base station systems (BSS), and network switching
8 systems (NSS).
9
10 GSM CS attached
11 GSM circuit-switched services attached means that the subscriber is attached to a GSM MSC. This is
12 also referred to as IMSI attached.
13 GSM CS detached
14 GSM circuit-switched services detached means that the subscriber is detached from a GSM MSC.
15 This is also referred to as IMSI detached.
16
17 GSM Foreign Mode
18
19 GSM foreign mode indicates the condition or state of an ANSI-136 ANSI-41 native subscriber
20 accessing a GSM network.
21
22
23 GPRS HLR
24 General Packet Radio Service Home Location Register is the HLR responsible for GPRS functions. It
25 interfaces with the SGSN and GGSN and Authentication Center.
26
27 GSM Mode
28
30
31 GSM Native Mode
32
34 network.
35
37
38 GSM native subscriber indicates an end user whose primary or home subscription resides in a GSM
39 network. These subscribers include both home subscribers from the GSM network, as well as
40 roamers from other GSM networks.
41
42 CDMA
43
44 CDMA as used in this document, refers to TIA/EIA -95 [9] or TIA/EIA-2000 [10], which is a CDMA
48 CDMA Mode
50
51
Ballot Version 6
N.S0028-0
1 CDMA Foreign Mode

2 CDMA foreign mode indicates the condition or state of a GSM native subscriber accessing a CDMA
3 network.
4
5 CDMA Native Mode
7 CDMA network.
8
13
15 GPRS in GSM Foreign Mode is a subset of GSM Foreign Mode and indicates the condition or state of
16 an ANSI-136 41 native subscriber accessing a GPRS network; the GPRS network may be coupled
17 with a GSM network.
18
19 Late Call Forwarding
20
21 Call Forwarding invoked after the call has been offered to the terminating VMSC (e.g., CFB,
22 CFNA/CFNRy, CFNRc) .
23
24 Mobile Equipment
25
26 The radio transceiver, main processing unit, and man-machine interface necessary to access the
27 radio network.
28 Mobile Station
29
32
33 Subscriber Identity Module
34
35 A smart card that plugs into the mobile equipment and that contains the authentication algorithms,
36 and stores service-oriented subscription information.
37
38
39
Ballot Version 7
N.S0028-0
1 3.2 Acronyms
2 AC Authentication Center in ANSI TIA/EIA-41 based networks
6 BAIC Barring of All Incoming Calls
7 BAOC Barring of All Outgoing Calls
8 BIC-Roam Barring of Incoming Calls while Roaming Outside HPLMN Country
9 BMI Base Station, Mobile Switching System, and Interworking Function
10 BOIC Barring of Outgoing International Calls
11 BOIC-exHC Baring of Outgoing International Calls Except to HPLMN Country
13 CFB Call Forwarding Busy
14 CFNA Call Forwarding No Answer
15 CFNRc Call Forwarding Not Reachable
16 CFNRy Call Forwarding No Reply
17 CS Circuit-Switched
18 EDGE Enhanced Data Rates Through Global Evolution
19 EIA Electronics Industry Association
22 FC Feature Code
23 FSM GSM Forward Short Message
24 GGSN Gateway GPRS Support Node
26 GSM Global System for Mobile Communications
Ballot Version 8
N.S0028-0
1 MC ANSI-41136 Message Center (for SMS)

3 MO Mobile Originated
4 MS Mobile Station
6 MT Mobile Terminated
7 MWN Message Waiting Notification
8 ODB Operator Determined Barring
9 OTA Over-the-Air Activation
10 PCS Personal Communications Service
11 PIN Personal Identification Number
14 SID System Identity
16 SMDPP ANSI-41 SMS message
18 SMS-C GSM Short Message Service Center
21 UWCC Universal Wireless Communications Consortium
22 VLR Visitor Location Register
23 VPLMN Visitor Public Land Mobile Network
24
Ballot Version 9
N.S0028-0
1 4 Stage 1 Service Descriptions

2 When in foreign mode (e.g., GSM or ANSI-136 ANSI-41 subscribers accessing respectively ANSI-
3 41136 or GSM 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 4.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 4.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-136. These events are dependent of the technology used and are different in GSM
21 and ANSI-136. The authentication procedure involves an authentication center on the network side
22 and an 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 4.1.1.1 Applicability to Telecommunications Services
35 Not identified.
36
Ballot Version 10
N.S0028-0
2 4.1.2 Normal Procedures With Successful Outcome

3 In ANSI-41136 native and foreign mode, the authentication procedure is done according to the
4 procedures defined in TIA/EIA-136-510 [8] for TDMA or according to TIA/EIA-95 for a CDMA..
5 In GSM native and foreign mode, the authentication procedure is done according to the procedures
6 defined in GSM 02.09 [10].
7 ANSI-136 Mode
8 The ANSI-136 authentication module is defined by the ANSI-136 directory. It holds the secret data
9 and internal values used during the authentication process.
10 The secret data used in the ANSI-136 authentication process is the shared secret data (SSD). The
11 internal values used within the ANSI-136 authentication process are the ESN, the MIN1 and the
12 MIN2.
13 CDMA Mode
14 The secret data used in the CDMA authentication process is the shared secret data (SSD). The
15 internal values used within the CDMA authentication process are the ESN, and the IMSI.
16 Authentication on IMSI is done in a CDMA mobile according to the IS-95 specification by extracting
17 10 digits from the IMSI. (IMSI_S).
18 ANSI-41 Mode
19 The ANSI-41 authentication module is defined by the air-interface specific directory in the mobile
20 station. The data used for authentication is as define by the Common Cryphtograpic Algorithm
21 (CAVE)add reference).
22
23
24 GSM Mode
25 The GSM authentication module is defined by the GSM directory in the SIM. The SIM card can
26 support multiple GSM subscriptions and each one has its own authentication module.
27 The secret data used in the GSM authentication process is the Ki. There is no internal data used in
28 the GSM authentication process.
29 4.1.2.1 Authorization (or Provision)

30 In GSM mode, the secret data (Ki) is stored in advance in the network’s Authentication Center (AuC)
31 as well as the SIM’s authentication module at the time of personalization of the SIM. This secret data
32 on the SIM cannot be modified after the issuance of the SIM.
33 In ANSI mode, the secret data (A-key) is stored in advance in the network’s Authentication Center
34 (AC) as well as the mobile’s station authentication module at the time of provisioning. This secret data
35 maybe overwritten with a new value via reprovisioning or over the air parameter administration
36 In ANSI-13641, the shared secret data (SSD) is generated from a root secret data (A-Key). This root
37 secret data is stored in advance in the authentication module and can be modified after issuance. The
38 generation of the secret data is done by the authentication center issuing an SSD UPDATE request
39 with the appropriate parameters.
Ballot Version 11
N.S0028-0
1 4.1.2.2 De-Authorization (or Withdrawal)

2 The de-authorization is done at the Authentication Center.
3 4.1.2.3 Registration
4 None identified.
5 4.1.2.4 De-Registration (or Erasure)

6 None identified.
7 4.1.2.5 Activation
8 Activation is performed by the operator or serving system.
9 4.1.2.6 De-Activation
10 De-activation is performed by the operator or serving system.
11 4.1.2.7 Invocation
12 The authentication function is invoked in the mobile station by selecting the appropriate directory
13 (GSM or ANSI-41136) on the authentication module and sending the appropriate command (RUN
14 AUTH ALGO or RUN CAVE)command, with the appropriate parameters (random value, option flag,
15 internal values). The authentication function is invoked in the network by the receipt of an
16 authentication message from the mobile station.
17 4.1.2.8 Normal Operation with Successful Outcome

18 If the Authentication Signature result calculated by the mobile station and sent to the BMI (Base
19 Station, Mobile Switching Center, Interworking Function) matches the result calculated by the BMI
20 then call processing and feature access is allowed by the BMI.
21 4.1.3 Exception Procedures or Unsuccessful Outcome

22 In the event that the mobile station cannot provide the correct Authentication Signature result to the
23 BMI then call processing and feature access is may be denied not allowed by the BMI.
25 None identified.
26 4.1.3.2 De-Registration / Erasure

27 None identified.
29 None identified.
31 None identified.
Ballot Version 12
N.S0028-0
1 None identified.
2 4.1.3.6 Exceptions While Roaming

3 None identified.
4 4.1.3.7 Exceptions During Intersystem Handoff

5 None identified.
6 4.1.4 Alternate Procedures

7 None identified.
8
9 4.1.5 Interactions With Other Features and Services

10
11 4.1.5.1 Advice of charge (AoC)

12 None identified.
13 4.1.5.2 Barring of All Outgoing Calls (BAOC)

14 None identified.
15 4.1.5.3 Barring of Outgoing International Calls (BOIC)

16 None identified.
17 4.1.5.4 Barring of Outgoing International Calls except those directed to the Home PLMN
18 (BOIC-exHC)
19 None identified.
20 4.1.5.5 Barring of All Incoming Calls (BAIC)

21 None identified.
22 4.1.5.6 Barring of Incoming Calls when Roaming Outside the Home PLMN (BIC-Roam)
23 None identified.
24 4.1.5.7 Call Delivery (CD)

25 If the Authentication Signature result at the mobile station does not match that of the BMI then Call
26 Delivery shall not be allowed.
27 4.1.5.8 Call Forwarding—Busy (CFB)

28 None identified.
29 4.1.5.9 Call Forwarding—Default (CFD)
Ballot Version 13
N.S0028-0
1 None identified.
2 4.1.5.10 Call Forwarding—No Answer / No Reply (CFNA / CFNRy)

3 None identified.
4 4.1.5.11 Call Forwarding—Not Reachable (CFNRc)

5 None identified.
6 4.1.5.12 Call Forwarding—Unconditional (CFU)

7 None identified.
8 4.1.5.13 Call Transfer (CT)

9 None identified.
10 4.1.5.14 Call Waiting / Call Hold (CW / HOLD)

11 None identified.
12 4.1.5.15 Calling Number / Line Identification Presentation (CNIP / CLIP)

13 None identified.
14 4.1.5.16 Calling Number / Line Identification Restriction (CNIR / CLIR)

15 None identified.
16 4.1.5.17 Calling Name Presentation (CNAP)

17 None identified.
18 4.1.5.18 Calling Name Restriction (CNAR)

19 None identified.
20 4.1.5.19 Closed User Group (CUG)

21 None identified.
22 4.1.5.20 Conference Calling / Multi Party Service (CC / MPTY)

23 A special challenge shall be made to the mobile station by the BMI in order to activate this feature. If
24 the Authentication Signature result at the mobile station does not match that of the BMI then this
25 feature shall not be allowed.
26 4.1.5.21 Do Not Disturb (DND)

27 None identified.
28 4.1.5.22 Emergency Services (Future)

29 None identified.
Ballot Version 14
N.S0028-0
1 4.1.5.23 Flexible Alerting (FA)

2 None identified.
3 4.1.5.24 Message Waiting Notification (MWN)

4 None identified.
5 4.1.5.25 Mobile Access Hunting (MAH)

6 None identified.
7 4.1.5.26 Password Call Acceptance (PCA)

8 None identified.
9 4.1.5.27 Preferred Language (PL)

10 None identified.
11 4.1.5.28 Priority Access and Channel Assignment (PACA)

12 None identified.
13 4.1.5.29 Remote Feature Control (RFC)

14 None identified.
15 4.1.5.30 Selective Call Acceptance (SCA)

16 None identified.
17 4.1.5.31 Subscriber PIN Access (SPINA)

18 The Authentication Feature shall take precedence over the SPINA feature.
19 4.1.5.32 Subscriber PIN Intercept (SPINI)

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

22 A special challenge shall be made to the mobile station by the BMI in order to activate this feature. If
23 the Authentication Signature result at the mobile station does not match that of the BMI then this
24 feature shall not be allowed.
25 4.1.5.34 Voice Message Retrieval (VMR)

26 If this feature requires the mobile station to originate a call from the mobile station and the
27 Authentication Signature result at the mobile station does not match that of the BMI then this feature
28 shall not be allowed.
29 4.1.5.35 Voice Privacy (VP)
Ballot Version 15
N.S0028-0
1 The Voice Privacy elements (e.g., for ANSI-41136 ,TDMA or CDMA) are derived from the same
2 secret A-Key as for the Authentication algorithm. If the HLR/AC for the mobile subscriber does not
3 have knowledge of this information it shall not be able to activate the Voice Privacy feature.
Ballot Version 16
N.S0028-0
1 4.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[15] 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[1] 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)
17
Ballot Version 17
N.S0028-0
1 4.2.2 Call Forwarding Unconditional (CFU)

2
3 4.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 4.2.2.1.1 Applicability to Telecommunications Services

8 CFU is applicable to voice telecommunication services.
9
10 4.2.2.2 Normal Procedures With Successful Outcome

11
12 4.2.2.2.1 Authorization (or Provision)

13 CFU may be generally available or may be provided after pre-arrangement with the service provider.
14 The authorization (provision) may have subscription options. These options are defined in either
15 GSM 02.82[15] (i.e., GSM native mode subscribers) or ANSI-664[1] (e.g., ANSI-41,TDMA136 or
16 CDMA native mode subscribers). Authorization or Provisioning may occur while operating in foreign
17 mode.
18 4.2.2.2.2 De-Authorization (or Withdrawal)

19 CFU may be withdrawn by the service provider, at the subscriber’s request or for administrative
20 reasons. De-authorization or withdrawal may occur while operating in foreign mode.
21 4.2.2.2.3 Registration
22 If the subscriber is authorized for Fixed Registration, the forward-to number shall be registered upon
23 authorization (provision). Mobile stations operating in foreign mode may attempt to perform
24 registration procedures normally supported in native mode.
25 The forward-to-number may be registered by the service provider upon authorization (provision) for
26 Variable Registration subscribers
27 GSM foreign mode: A forward-to-number may be registered by a Variable Registration authorized
28 subscriber specifying the CFU registration feature code and a forward-to number termination address
29 as in:
*
30 FC + termination address + SEND .
31 Alternatively, if the mobile station offers menu driven control of registration, the mobile station is
32 expected to generate the equivalent GSM functional signaling towards the network.
33 ANSI-41 foreign mode: Registration can take place with an appropriate control procedure by the
34 subscriber, per GSM 02.30[11]. In ANSI-41 foreign mode, if the equivalent GSM feature code (MMI)
35 is manually entered by the user, the mobile station is expected to issue the relevant ANSI-13641
36 feature code entry.
Ballot Version 18
N.S0028-0
2 expected to generate the equivalent ANSI-13641 feature code entry and resulting call origination
3 based on the menu driven entry.
4 If the registration is accepted, the system shall indicate success using either GSM or ANSI-13641
5 signaling techniques depending on the mode of operation.
6 4.2.2.2.4 De-Registration (or Erasure)

7 Mobile stations operating in foreign mode may attempt to perform De-Registration or Erasure
8 procedures normally supported in native mode.
9 A forward-to-number may be de-registered upon de-activation (at the home service provider option).
10 GSM foreign mode: If the de-registration is to be separate from de-activation, the de-registration
11 feature code must be distinct from the corresponding de-activation feature code.
12 GSM foreign mode: CFU may be de-registered by a Variable Registration authorized subscriber
13 specifying the CFU de-registration feature code, as in:
*
14 FC0 + SEND .
17 ANSI-41 foreign mode: The subscriber can specifically erase a previous registration with an
18 appropriate control procedure, per GSM 02.30[11]. In ANSI-41 foreign mode, if the equivalent GSM
19 feature code (MMI) is manually entered by the user, the mobile station is expected to issue the
20 necessary ANSI-13641 feature code to the network.
21 CFU shall be de-registered upon de-authorization or withdrawal.
22 4.2.2.2.5 Activation
23 Mobile stations operating in foreign mode may attempt to perform Activation procedures normally
24 supported in native mode.
25 If the subscriber is authorized for Permanent Activation, CFU shall be activated upon authorization
26 (provision).
27 CFU may be activated upon authorization or registration for Demand Activation authorized
28 subscribers. CFU may be activated upon registration for Variable Registration authorized subscribers.
29 GSM foreign mode: A previously registered forward-to-number may be activated by a Demand
30 Activation authorized subscriber specifying a CFU activation feature code, as in:
*
31 FC + SEND .
32 Alternatively, if the mobile station offers menu driven control of activation, the mobile station is
33 expected to generate the equivalent GSM functional signaling.
34 ANSI-41 foreign mode: The MS shall be allowed to activate CFU by a control procedure (e.g., using
35 the MMI command described in GSM 02.30[11]). In ANSI-41 foreign mode, if the equivalent GSM
38 If the activation is accepted, the system shall indicate success using either GSM or ANSI-13641
Ballot Version 19
N.S0028-0
1 The serving system may provide a courtesy call to the forward-to number shortly after this feature is
2 activated permitting the subscriber to verify the validity of the forward-to-number.
3 4.2.2.2.6 De-Activation
4 GSM foreign mode: CFU may be de-activated by a Demand Activation authorized subscriber
5 specifying the CFB de-activation feature code, as in:
*
6 FC0 + SEND .
7 Alternatively, if the mobile station offers menu driven control of de-activation, the mobile station is
9 ANSI-41 foreign mode: The user may deactivate CFU by means of an appropriate control procedure
10 (e.g., as described in GSM 02.30[11]). In ANSI-41 foreign mode, if the equivalent GSM feature code
11 (MMI) is manually entered by the user, the mobile station is expected to issue the necessary ANSI-
12 13641 feature code to the network.
13 If the de-activation is accepted, the system shall indicate success using either GSM or ANSI-13641
14 signaling techniques depending on the mode of operation. Registered information shall not be
15 erased.
16 CFU shall be de-activated upon de-authorization (withdrawal) or de-registration (erasure).
17 4.2.2.2.7 Invocation
18 The feature treatment is invoked unconditionally when there is an incoming call and CFU is active.

20 When CFU is active, incoming calls for the subscriber shall be forwarded unconditionally to the
21 forward-to number.
22 GSM Foreign Mode: When an incoming call is forwarded unconditionally the forward-to-party shall
23 receive a notification that the call has been forwarded. The calling party may also receive a
24 notification that the call has been forwarded.
25 ANSI-41 foreign mode: When an incoming call is forwarded unconditionally the served mobile
26 subscriber may receive a notification that the call has been forwarded.
27 4.2.2.3.1 Call Detail Record / Charging Requirements

28 For GSM and ANSI-41 based network interoperability, no new or special recording capabilities are
29 needed.
30
Ballot Version 20
N.S0028-0
2 4.2.2.4 Exception Procedures or Unsuccessful Outcome

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

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

30 None identified.
31 4.2.2.4.7 Exceptions During Intersystem Handoff

32 None identified.
33 4.2.2.5 Alternate Procedures
Ballot Version 21
N.S0028-0
1 None identified.
2 4.2.2.6 Interactions With Other Features and Services

3
4 4.2.2.6.1 Advice of charge (AoC)

5 See GSM 02.86[19].
6 4.2.2.6.2 Barring of All Outgoing Calls (BAOC)

7 None identified at this time..
8 4.2.2.6.3 Barring of Outgoing International Calls (BOIC)

9 None identified at this time..
10 4.2.2.6.4 Barring of Outgoing International Calls except those directed to the Home PLMN
11 (BOIC-exHC)
12 None identified at this time.
13 4.2.2.6.5 Barring of All Incoming Calls (BAIC)

15 4.2.2.6.6 Barring of Incoming Calls when Roaming Outside the Home PLMN (BIC-Roam)
17 4.2.2.6.7 Call Delivery (CD)

18 CFU takes precedence over CD. That is, calls arriving when CFU is active are forwarded
19 unconditionally and not given CD treatment.
20 4.2.2.6.8 Call Forwarding—Busy (CFB)

21 CFU takes precedence over CFB. That is, calls arriving when CFU is active shall be forwarded
22 unconditionally and not given CFB treatment
23 4.2.2.6.9 Call Forwarding—Default (CFD)

24 CFU takes precedence over CFD. That is, calls arriving when CFU is active shall be forwarded
25 unconditionally and not given CFD treatment.
26 4.2.2.6.10 Call Forwarding—No Answer / No Reply /Not Reachable (CFNA / CFNRy/CFNRc)

27 CFU takes precedence over CFNA/CFNRy/CFNRc. That is, an incoming call arriving for a subscriber
28 with both CFU and CFNA/CFNRy/CFNRc active shall be forwarded with CFU.
29 4.2.2.6.11 Call Transfer (CT)

30 None identified.
Ballot Version 22
N.S0028-0
1 4.2.2.6.12 Call Waiting / Call Hold (CW / HOLD)

2 CFU takes precedence over CW. That is, calls arriving when CFU is active shall be forwarded
3 unconditionally and not given CW treatment.
4 4.2.2.6.13 Calling Number / Line Identification Presentation (CNIP / CLIP)

5 When a call has been forwarded and the forward-to user has been provided with the CNIP / CLIP
6 supplementary service, the forward-to user shall receive the number of the original calling user, if this
7 calling user has not subscribed to or invoked the CNIR / CLIR supplementary service.
8 4.2.2.6.14 Calling Number / Line Identification Restriction (CNIR / CLIR)

9 If the calling number indicates presentation restricted, the calling number shall not be presented to
10 the called party or the forward-to-party.
11 If the called (redirecting) subscriber has CFU active and CNIR is either Permanently Restricted or the
12 default is Presentation Restricted, the redirecting number shall indicate presentation restricted to
13 prevent presentation to the forward-to-party or to the forward-to station.
14 4.2.2.6.15 Calling Name Presentation (CNAP)

15 When a call has been forwarded and the forward-to-party has been provided with the CNAP
16 supplementary service, the forward-to user shall receive the name of the original calling user, if this
17 calling user has not subscribed to or invoked the CNAR or CNIR / CLIR supplementary service.
18 4.2.2.6.16 Calling Name Restriction (CNAR)

19 If the calling name or number indicates presentation restricted, the calling name or number shall not
20 be presented to the called party or the forward-to-party.
21 If the called (redirecting) subscriber has CFU active and CNAR or CNIR is either Permanently
22 Restricted, or the default is Presentation Restricted, the redirecting name shall indicate presentation
23 restricted to prevent presentation to the forward-to-party.
24 4.2.2.6.17 Closed User Group (CUG)

25 See GSM 02.85[18].
26 4.2.2.6.18 Conference Calling / Multi Party Service (CC / MPTY)

27 None identified.
28 4.2.2.6.19 Do Not Disturb (DND)

30 4.2.2.6.20 Emergency Services (Future)

32 4.2.2.6.21 Flexible Alerting (FA)

34 4.2.2.6.22 Message Waiting Notification (MWN)
Ballot Version 23
N.S0028-0
1 None identified.
2 4.2.2.6.23 Mobile Access Hunting (MAH)

4 4.2.2.6.24 Password Call Acceptance (PCA)

6 4.2.2.6.25 Preferred Language (PL)

7 None identified.
8 4.2.2.6.26 Priority Access and Channel Assignment (PACA)

10 4.2.2.6.27 Remote Feature Control (RFC)

11 CFU Registration shall be allowed via RFC in ANSI-41136 mode, or via functional messaging in GSM
12 mode.
13 4.2.2.6.28 Selective Call Acceptance (SCA)

15 4.2.2.6.29 Subscriber PIN Access (SPINA)

17 4.2.2.6.30 Subscriber PIN Intercept (SPINI)

18 None identified.
19 4.2.2.6.31 Three-Way Calling / Multi Party Service (3WC / MPTY)

20 None identified.
21 4.2.2.6.32 Voice Message Retrieval (VMR)

22 None identified.
23 4.2.2.6.33 Voice Privacy (VP)

24 None identified.
25
Ballot Version 24
N.S0028-0
1 4.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[15] (i.e., GSM native mode subscribers) or ANSI-664[1] (e.g., ANSI-41,TDMA136 or
16 CDMA native mode subscribers). Authorization or Provisioning may occur while operating in foreign
17 mode.

19 CFB may be withdrawn at the subscriber’s request or for administrative reasons. De-authorization or
20 withdrawal may occur while operating in foreign mode.
23 authorization (provision).
24 The CFB forward-to number may be registered by the service provider upon authorization (provision)
25 for Variable Registration subscribers. Mobile stations operating in foreign mode may attempt to
26 perform registration procedures normally supported in native mode.
28 subscriber specifying the CFB registration feature code and a forward-to number termination address
29 as in:
*
30 FC + termination address + SEND .Alternatively, if the mobile station offers menu driven control
31 of registration, the mobile station is expected to generate the equivalent GSM functional signaling
32 towards the network.
33 ANSI-41 foreign mode: Registration may take place with an appropriate control procedure by the
34 subscriber, per GSM 02.30[11]. In ANSI-41 foreign mode, if the equivalent GSM mode feature code
35 (MMI) is manually entered by the user, the mobile station is expected to issue the relevant ANSI-
36 13641 feature code entry.
Ballot Version 25
N.S0028-0

9 Forward-to numbers may be de-registered upon de-activation (at the home service provider option).
12 GSM foreign mode: CFB may be de-registered by a Variable Registration authorized subscriber
13 specifying the CFB de-registration feature code, as in:
*
14 FC0 + SEND .
16 expected to generate the GSM functional signaling towards the network.
19 mode feature code is manually entered by the user, the mobile station is expected to issue the
21 CFB shall be de-registered upon de-authorization or withdrawal.
25 If the subscriber is authorized for Permanent Activation, CFB shall be activated upon authorization
26 (provision).
27 CFB may be activated upon registration for Demand Activation authorized subscribers. CFB may be
28 activated upon registration for Variable Registration authorized subscribers.
29 GSM foreign mode: A previously registered forward-to number may be activated by a Demand
30 Activation authorized subscriber specifying a CFB activation feature code, as in:
*
31 FC + SEND .
34 ANSI-41 foreign mode: The MS shall be allowed to activate CFB by for example using the MMI
35 command described in GSM 02.30[11]. In ANSI-41 foreign mode, if the equivalent GSM mode feature
36 code (MMI) is manually entered by the user, the mobile station is expected to issue the necessary
37 ANSI-13641 feature code to the network.
38 If the activation is accepted, the system shall indicate success with using either GSM or ANSI-13641
Ballot Version 26
N.S0028-0
2 activated permitting the subscriber to verify the validity of the forward-to number.
4 GSM foreign mode: CFB may be de-activated by a Demand Activation authorized subscriber
5 specifying the CFB de-activation feature code, as in:
*
6 FC0 + SEND .
9 ANSI-41 foreign mode: The user may deactivate CFB by means of an appropriate control procedure
10 (e.g., as described in GSM 02.30[11]). In ANSI-41 foreign mode, if the equivalent GSM mode feature
11 code (MMI) is manually entered by the user, the mobile station is expected to issue the necessary
12 ANSI-13641 feature code to the network.
13 If the de-activation is accepted, the system shall indicate success with using either GSM or ANSI-
14 13641 signaling techniques depending on the mode of operation. Registered information shall not be
15 erased.
16 CFB shall be de-activated upon de-authorization (withdrawal) or de-registration (erasure).
18 The feature treatment is invoked when there is an incoming call while the subscriber is considered to
19 be busy (i.e., in any state other than the idle state) and CFB is active.

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

31 needed.
32
Ballot Version 27
N.S0028-0

3
6 notification that call forwarding on mobile subscriber busy registration was not successful. Possible
7 causes are:

18 If the subscriber is not authorized for the request, or if a forward-to number is not properly registered,
24 If the forwarded call cannot be routed to the forward-to destination, then the call shall be given the
29 calling party.

31 None identified.

33 None identified.
34
Ballot Version 28
N.S0028-0

2 None identified.
3

5

7 See GSM 02.86[19].


13 (BOIC-exHC)


20 CD affects CFB. That is, if CD is inactive while the subscriber is roaming, the subscriber is considered
21 to be inaccessible. Even if the subscriber has CFB active, incoming calls shall be given the subscriber
22 inaccessible treatment.
23 If CD is active and registered for a roaming subscriber, or if the subscriber is at home, CFB works
24 normally.
25 If the call is delivered to the subscriber, the subscriber is busy, and the subscriber has CFB active,
26 the call shall be diverted to the CFB forward-to number.

28 Not applicable.

30 CFB takes precedence over CFD. That is, calls arriving to a busy subscriber with CFB and CFD
31 active shall be forwarded by CFB and not given CFD treatment.
32 4.2.3.6.10 Call Forwarding—No Answer / No Reply (CFNA / CFNRy)
Ballot Version 29
N.S0028-0
1 CFB is mutually exclusive with CFNA / CFNRy. That is, calls arriving to a busy subscriber with CFB
2 and CFNA / CFNRy active shall be forwarded by CFB and not given CFNA / CFNRy treatment.
3 4.2.3.6.11 Call Forwarding—Not Reachable (CFNRc)

4 CFB is mutually exclusive with CFNRc. That is, calls arriving to a busy subscriber with CFB and
5 CFNRc active shall be forwarded by CFB and not given CFNRc treatment.
6 4.2.3.6.12 Call Forwarding—Unconditional (CFU)

7 CFU takes precedence over CFB. That is, calls arriving when CFU is active shall be forwarded
8 unconditionally and not given CFB treatment.

10 None identified.

12 CW is invoked before CFB. If a call arrives for a busy subscriber able to receive a second call, the
13 called subscriber has both CW and CFB active, and no call is already waiting to be answered; the call
14 is presented to the subscriber with CW notification. If the CW call is not accepted, CFB is not invoked.
15 If a call arrives for a busy subscriber, the called subscriber has both CW and CFB active, and if the
16 called subscriber is unable to receive a second call or has a call waiting to be answered; the call shall
17 be forwarded immediately by CFB.


24 the called party, the called station, the forward-to party, or the forward-to station.
25 If the called (redirecting) subscriber has CFB invoked and either the CNIR mode is Permanently
26 Restricted or the CNIR Default is Presentation Restricted, the redirecting number shall indicate
27 presentation restricted to prevent presentation to the forward-to party or to the forward-to station.

29 When a call has been forwarded and the forward-to user has been provided with the CNAP

34 be presented to the called party, the called station, the forward-to party, or the forward-to station.
35 If the called (redirecting) subscriber has CFB invoked and either the CNAR or CNIR mode is
36 Permanently Restricted, or the CNAR or CNIR Default is Presentation Restricted, the redirecting
37 name shall indicate presentation restricted to prevent presentation to the forward-to party or to the
38 forward-to station.
Ballot Version 30
N.S0028-0

2 See GSM 02.85[18].

4 None identified.

7 4.2.3.6.22 Emergency Services



12 None identified.



18 None identified.


22 CFB Registration shall be allowed via RFC in ANSI-41136 mode, or via functional messaging in GSM
23 mode.



29 None identified.
Ballot Version 31
N.S0028-0

2 None identified.

4 None identified.

6 None identified.
Ballot Version 32
N.S0028-0
1 4.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[15] (i.e., GSM native mode subscribers) or ANSI-664[1] (e.g., ANSI-136
25 41, TDMA or CDMA native mode subscribers). Authorization or Provisioning may occur while
26 operating in 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.
37 subscriber specifying the CFNA registration feature code and a forward-to number termination
38 address as in:
Ballot Version 33
N.S0028-0
*
1 FC + termination address + SEND
4 ANSI-41 foreign mode: Registration can take place with an appropriate control procedure by the
5 subscriber, per GSM 02.30[11]. In ANSI-41 foreign mode, if the equivalent GSM feature code (MMI)
6 is manually entered by the user, the mobile station is expected to issue the relevant ANSI-13641
7 feature code entry.

19 GSM foreign mode: CFNA may be de-registered by a Variable Registration authorized subscriber
20 specifying the CFNA de-registration feature code, as in:
*
21 FC0 + SEND .
28 CFNA/CFNRy/CFNRc shall be de-registered upon de-authorization or withdrawal.
32 If the subscriber is authorized for Permanent Activation, CFNA shall be activated upon authorization
33 (provision).
34 CFNA may be activated upon authorization or registration for Demand Activation authorized
35 subscribers. CFNA may be activated upon registration for Variable Registration authorized
36 subscribers.
38 Activation authorized subscriber specifying a CFNA activation feature code, as in:
*
39 FC + SEND .
Ballot Version 34
N.S0028-0
3 ANSI-41 foreign mode: The MS shall be allowed to activate CFNRy/CFNRc by using an appropriate
4 control procedure (e.g. using the MMI command described in GSM 02.30[11]). In ANSI-41 foreign
5 mode, if the equivalent GSM feature code (MMI) is manually entered by the user, the mobile station is
6 expected to issue the necessary ANSI-13641 feature code to the network.
7 If the activation is accepted, the system shall indicate success using either GSM or ANSI-13641
12 GSM foreign mode: CFNA may be de-activated by a Demand Activation authorized subscriber
13 specifying the CFNA de-activation feature code, as in:
*
14 FC0 + SEND .
17 ANSI-41 foreign mode: The user may deactivate CFNRy/CFNRc by means of an appropriate control
18 procedure (e.g., as described in GSM 02.30[11]). In ANSI-41 foreign mode, if the equivalent GSM
21 If the de-activation is accepted, the system shall indicate success using either GSM or ANSI-13641
22 signaling techniques depending on the mode of operation. Registered information shall not be
23 erased.
24 CFNA/CFNRy/CFNRc shall be de-activated upon de-authorization (withdrawal) or de-registration
25 (erasure).
27 The feature treatment is invoked when there is an incoming call and either CFNA, CFNRy or CFNRc
28 is active and the necessary conditions have been met – see GSM 02.82[15] and ANSI-664[1].

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

39 needed.
Ballot Version 35
N.S0028-0

3
6 notification that registration of CFNA/CFNRy/CFNRc was not successful. Possible causes are:

28 calling party.

30 None identified.

32 None identified.
Ballot Version 36
N.S0028-0
1 None identified.

3

5 See GSM 02.86[19].


11 (BOIC-exHC)


18 CD affects CFNA. That is, if CD is inactive while the subscriber is roaming, the subscriber is
19 considered to be inaccessible. If the subscriber has CFNA active, incoming calls shall be diverted to
20 the CFNA forward-to number.
21 If CD is active and registered for a roaming subscriber, or if the subscriber is at home, CFNA works
22 normally.
23 If the call is presented to the subscriber, the call is not answered, and the subscriber has CFNA
24 active, the call shall be diverted to the CFNA forward-to number.

26 CFB is mutually exclusive with CFNA/CFNRy/CFNRc. That is, calls arriving to a busy subscriber with
27 CFB and CFNA/CFNRy/CFNRc active shall be forwarded by CFB and not given
28 CFNA/CFNRy/CFNRc treatment.

30 CFNA takes precedence over CFD. That is, an incoming call to an inaccessible or non-answering
31 subscriber with both CFNA and CFD active shall be forwarded using CFNA.
Ballot Version 37
N.S0028-0
1 None identified.
2
Ballot Version 38
N.S0028-0

3 CW is invoked before CFNA/CFNRy. If a call arrives for a busy subscriber able to receive a second
4 call, the called subscriber has both CW and CFNA/CFNRy active, and no call is waiting to be
5 answered; the call is presented to the subscriber with CW notification. If the call is not answered
6 within a period of time after applying the first CW notification, it shall be given no answer treatment.
7 CFNRc is invoked before CW.

11 calling party has not subscribed to or invoked the CNIR / CLIR supplementary service.

15 If the called (redirecting) subscriber has CFNA/CFNRy/CFNRc active and CNIR is either Permanently
16 Restricted or the default is Presentation Restricted, the redirecting number shall indicate presentation
17 restricted to prevent presentation to the forward-to-party or to the forward-to station.


25 If the called (redirecting) subscriber has CFNA/CFNRy/CFNRc active and CNAR or CNIR is either
26 Permanently Restricted, or the default is Presentation Restricted, the redirecting name shall indicate
27 presentation restricted to prevent presentation to the forward-to-party.

29 See GSM 02.85[18].

31 None identified.


Ballot Version 39
N.S0028-0


4 None identified.



10 None identified.


14 CFNA/CFNRy/CFNRc Registration shall be allowed via RFC in ANSI-13641 mode, or via functional
15 messaging in GSM mode.



21 None identified.

23 None identified.

25 None identified.

27 None identified.
28
Ballot Version 40
N.S0028-0
1 4.2.5 Call Forwarding Default

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

10 CFD is applicable to voice telecommunication services.

12

14 CFD may be generally available or may be provided after pre-arrangement with the service provider.
15 The authorization (provision) may have subscription options. These options are defined in
16 ANSI-664[1] (e.g., ANSI-136 41, TDMA or CDMA native mode subscribers). Authorization or
17 Provisioning may occur while operating in foreign mode.

19 CFD may be withdrawn by the service provider, at the subscriber’s request, or for administrative
20 reasons. De-authorization or withdrawal may occur while operating in foreign mode.
28 subscriber specifying the CFD registration feature code and a forward-to number termination address
29 as in:
*
30 FC + termination address + SEND .
33 If the registration is accepted, the system shall indicate success using either GSM signaling
34 techniques.

36 Mobile stations operating in foreign mode, may attempt to perform De-Registration or Erasure
Ballot Version 41
N.S0028-0
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-13641 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).
35
Ballot Version 42
N.S0028-0
3 The feature treatment is invoked when there is an incoming call, CFD is active and the necessary
4 conditions have been met – See ANSI-664[1].

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

13 needed.

15
18 notification that registration of CFD was not successful. Possible causes are:

34
Ballot Version 43
N.S0028-0
8 calling party.

10 None identified.

12 None identified.

14 None identified.

17 CD affects CFD. That is, if CD is inactive while the subscriber is roaming, the subscriber is
18 considered to be inaccessible. If the subscriber has CFD active, incoming calls shall be diverted to
19 the CFD forward-to number.

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.

24 None identified.

26 CW is invoked before CFD. If a call arrives for a busy subscriber able to receive a second call, the
27 called subscriber has both CW and CFD active, and no call is waiting to be answered; the call is
28 presented to the subscriber with CW notification. If the call is not answered within a period of time
29 after applying the first CW notification, it shall be given no answer treatment.

Ballot Version 44
N.S0028-0
3 If the called (redirecting) subscriber has CFD active and CNIR is either Permanently Restricted or the
4 default is Presentation Restricted, the redirecting number shall indicate presentation restricted to
5 prevent presentation to the forward-to-party or to the forward-to station.


13 If the called (redirecting) subscriber has CFD active and CNAR or CNIR is either Permanently
14 Restricted, or the default is Presentation Restricted, the redirecting name shall indicate presentation
15 restricted to prevent presentation to the forward-to-party.

17 See GSM 02.85[18].

19 None identified.




27 None identified.


Ballot Version 45
N.S0028-0
1 None identified.
2
Ballot Version 46
N.S0028-0


5 CFD Registration shall be allowed via RFC in ANSI-13641 mode, or via functional messaging in GSM
6 mode.



12 None identified.

14 None identified.

16 None identified.

18 None identified.
Ballot Version 47
N.S0028-0
1 4.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[13]. 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 4.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.
40 4.3.2.1 Call Detail Record
Ballot Version 48
N.S0028-0
2 needed.

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

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

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

17 None identified.
18 4.3.3.5 Exceptions during Intersystem Handoff

19 None identified.

21 None identified.
22 4.3.5 Interactions with Other Features and Services
23 4.3.5.1 Advice of Charge

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

27 None identified.

29 None identified.

31 BAIC takes precedence over Optimal Routing for Late Call Forwarding, and all incoming calls are
32 given denial treatment.
Ballot Version 49
N.S0028-0
1 Barring of Incoming Calls when Roaming Outside the Home PLMN Country (BIC-Roam)
2 No impact.
3 4.3.5.5 Call Forwarding Busy (CFB)

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

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

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

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

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

23 None identified.

25 None identified.

27 None identified.

29 None identified.

31 None identified.

33 None identified.
Ballot Version 50
N.S0028-0

2 None identified.

4 Same as CFU.
5 4.3.5.18 Emergency Services

6 None identified.
7 4.3.5.19 Law Enforcement or CALEA

8 None identified.

10 None identified.

12 None identified.

14 Applicable to ANSI-136 (ANSI-41 ) networks only. None identified.

16 None identified.

18 Applicable to ANSI-136 (ANSI-41) networks only. None identified.


22 Applicable to ANSI-136 (ANSI-41) networks only. Callers that are not able to provide the correct
23 password are given denial treatment. Calls that are allowed may be subjected to OR treatment.



29 None identified.
Ballot Version 51
N.S0028-0

2 None identified.
3 4.3.5.31 3-Way Calls or Conference Calls

4 None identified.
5
Ballot Version 52
N.S0028-0
1 4.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-13641 mode, this means that no further
12 calls are offered to the subscriber while a call is waiting. In GSM mode, another call can be offered to
13 the 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-13641 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-41136 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).
Ballot Version 53
N.S0028-0

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-13641 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
21 GSM native and foreign modes: This supplementary service shall be activated either collectively
22 for all applicable Basic Services or on a Basic Service group basis by the subscriber using a control
23 procedure, as specified in GSM 02.30[11], or by the service provider. The controlling subscriber shall
24 be informed by the network of the success or otherwise of her action.
26 In both GSM and ANSI-41 foreign modes, the subscriber shall be provided with menu selections by
27 the mobile station to allow him/or her to de-activate the call waiting feature. Menu selections shall
28 also be available to the subscriber while in native mode as well. In addition, the user may also be able
29 to de-activate call waiting (depending on individual service provider’s preference) through the use of
30 the keypad, as follows:
31 ANSI-13641 native and foreign mode:
32 CW shall be de-activated upon de-authorization.
33 CW Demand De-Activation:
34 CW may be de-activated by a Demand Activation authorized subscriber specifying a CW
35 de-activation feature code, as in:
*
36 FC0 + SEND .
Ballot Version 54
N.S0028-0
1 If the de-activation is accepted, the system shall indicate success with feature confirmation treatment.
2 Temporary Cancellation During a Call (ANSI-13641 Native Mode Only):
3 CW may be canceled during a single call by a Demand Cancellation authorized subscriber issuing a
4 flash request and then specifying a CCW feature code, as in:
*
5 FC0 + SEND .
6 If the cancellation is accepted, the system may indicate success with feature confirmation treatment
7 and then reconnect the call. At the completion of the call, CW shall resume the activation state prior
8 to using the cancel CW feature code.
9 Temporary Cancellation With a Call Setup Request (ANSI-13641 Native Mode Only):
10 CW may be canceled for a single call concurrently with a call request by a Demand Cancellation
11 authorized subscriber specifying a CCW feature code and a termination address, as in:
*
12 FC0 + # + termination address + SEND .
13 Alternatively:
*
14 FC + termination address + SEND
15 is possible, if a fixed length Temporary Cancellation feature code is distinct from the de-activation
16 feature code.
17 If the cancellation is accepted, the system may indicate success with feature confirmation treatment
18 and then the call is allowed to proceed toward the termination address. At the completion of the call,
19 CW shall resume the activation state prior to using the cancel CW feature code.
20 GSM native and foreign mode: The service shall be deactivated either collectively for all applicable
21 Basic Services or on a Basic Service group basis by the subscriber using a control procedure, as
22 specified in GSM 02.30[11], or by the service provider. The controlling subscriber shall be informed
23 by the network of the success or otherwise of her action.
25 CW is invoked when a incoming call attempt arrives for a subscriber who is already engaged in
26 conversation on a prior call, who does not have another call waiting, and who has CW active.
27 There are functions or actions which exist on GSM (in GSM 02.83[16]), but do not exist in ANSI-
28 13641, and vice versa (see charts below). In order to achieve a seamless user Interface when
29 roaming, it would be better to either provide the menu selections as it is in a GSM handset, or some
30 other mechanism that can achieve the same goal.
31 4.4.3 Normal Operation with Successful Outcome

32 Menu selections shall be provided by the mobile station, in both foreign and native modes, to allow
33 the subscriber to control the operation of calls involving call waiting. Because, in general, GSM
34 networks provide more capabilities related to call waiting operation, the menu-driven procedures may
35 be different for a given subscriber depending on whether the serving network is GSM or ANSI-13641.
36 In addition to the use of menu selections, a subscriber may use the keypad entries (shown in the
37 tables below) to control the operation of calls involving call waiting. Note that the subscriber would
38 need to use different set of keypad entries depending on whether the serving network is GSM or
39 ANSI-13641, and thus the use of the shown keypad entries to control the operation of the calls is not
40 encouraged. In general, the menu-driven approach would be preferred instead.
Ballot Version 55
N.S0028-0
1 The following tables describe the call party actions and system reactions for CW on GSM and ANSI-
2 13641.
3 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-13641 Called System Reaction

Action Party 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.
Ballot Version 56
N.S0028-0
1
2 The CW notification may be an audible Call Waiting Tone injected into the voice path, a message on
3 the alphanumeric display, or both.
4 Table 3: 2-Way Notification State for Call Waiting
State 2-way CW Condition The controlling subscriber is in a two-way

notification conversation with the other party and call
waiting notification is applied.

Action Party 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
the calling party. Go to the
SEND key . 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 subscriber for the calling
key.
END key. party. Go to the Alerting
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
the calling party. Go to the
SEND key .
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
the 2-way CW notification
SEND key .
state.
5
6
Ballot Version 57
N.S0028-0
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.

Action party 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 4.4.3.1 Call Detail Record / Charging Requirements

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

6
8 None identified.

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

26 None identified.

28 None identified.

30 None identified.

32
Ballot Version 59
N.S0028-0

2 None identified.

4 None identified.

6 None identified.
8 (BOIC-exHC)
9 None identified.

11 None identified.
13 None identified.

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

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

29 CW is invoked before CFD. If a call arrives for a busy subscriber able to receive a second call, the
30 called subscriber has both CW and CFD active, and no call is waiting to be answered; the call is
33 If a call arrives for a busy subscriber, the called subscriber has both CW and CFD active, and if the
35 be forwarded immediately by CFD.
Ballot Version 60
N.S0028-0

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.
Ballot Version 61
N.S0028-0
1 DND takes precedence over CW. That is, calls arriving for a subscriber with DND and CW active shall
2 be refused and not be given CW treatment.

4 None identified.

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

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

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

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

31 None identified.

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

36 None identified.
Ballot Version 62
N.S0028-0

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

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

7 None identified.

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

16 None identified.

18 None identified.
19
Ballot Version 63
N.S0028-0
1 4.5 Three-Way Calling (3WC) and Multi-Party (MPTY)

2

4 ANSI-13641 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-13641 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.
Ballot Version 64
N.S0028-0
2 ANSI-13641 Mode: 3WC is invoked when the appropriate flash request is sent and the feature is
3 authorized.
4 GSM Mode: Multi-Party service is invoked by the served mobile subscriber by use of a control
5 procedure, as defined in GSM 02.30[11].

7
8 4.5.3.1 ANSI-13641 Mode

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

21 Only the served mobile subscriber shall be able to add remote parties to the multi-party call as
22 specified in GSM 02.84[17].
23 4.5.3.2.1 Beginning the multi-party call

24 When the served mobile subscriber invokes multi-party, the network joins the active call and the call
25 on hold together into a multi-party call in which the served mobile subscriber and the remote parties
26 can all communicate with one another.
27 4.5.3.2.2 Managing an active multi-party call

28 During an active multi-party call, the served mobile subscriber shall be able to:
29
30 1. Add another remote party,
31 to which a private communication has been established, if the number of remote parties does not
32 then exceed the maximum number allowed, which results in an active multi-party call.
33 A MPTY invoke notification shall be sent towards all remote parties. A Retrieve notification
34 (according to GSM 02.83[16]) shall be sent towards all previously held remote parties.
35 2. Put the connection to multi-party call on hold:
36 (i.e., place her connection to the multi-party call on hold (and typically later retrieve it)). The served
37 mobile subscriber may make an enquiry call (e.g., to a potential new remote party) or process a
Ballot Version 66
N.S0028-0
1 Call Waiting request from this state. While the multi-party call is on hold the remaining remote
2 parties in the multi-party call can have communication with each other.
3 As a result of this scenario, the inquiry call or the accepted waiting call can be added to the multi-
4 party call or released. If the call is released by the served mobile subscriber or by the remote
5 party, the served mobile subscriber is in control of a held multi-party call.
6 A Hold notification (according to GSM 02.83[16]) shall be sent towards all remote parties.
7 3. Separate a remote party:
8 Explicitly choose one remote party to have a private communication with. This results in that
9 remote party being removed from the multi-party call which is placed on hold, and the conversation
10 between the served mobile subscriber and the designated remote party being a normal active call.
11 The remaining remote parties may have communication with each other in this state.
12 As a result of this scenario the private communication can be added again to the multi-party call or
13 released. If the private call is released by the served mobile subscriber or by the remote party, the
14 served mobile subscriber is in control of a held multi-party call.
15 A Hold notification (according to GSM 02.83[16]) shall be sent towards all remote parties, except
16 the designated remote party to which a private communication was established.
17 4. Terminate the entire multi-party call.
18 When the served mobile subscriber releases, this is interpreted as a request for termination of the
19 entire multi-party call even if there are calls on hold.
20 No further notification shall be sent.
21 5. Disconnect a remote party:
22 Explicitly release the remote parties on a one at a time basis. In the case when no remote parties
23 remain, the multi-party call is terminated.
24 The notification about the held multiparty call towards the served mobile subscriber is given by
25 the MS, not by the network.
26 4.5.3.2.3 Managing a held multi-party call

27 During a held multi-party call the served mobile subscriber shall be able to:
28 1. Retrieve the held multi-party call, which results in an active multi-party call.
29 2. Initiate a new call.
30 3. Process a Call Waiting request.
31 4. Disconnect the held multi-party call. All calls belonging to the multi-party call shall be released.
32 5. Disconnect a single remote party.
33 During a held multi-party call the served mobile subscriber shall NOT be able to: Retrieve a single
34 remote party.
35 4.5.3.2.4 Managing a single call and a MPTY

36 a) Single active call
37 If the served mobile subscriber is connected to a single active call (regardless whether it is a private
38 communication or a new initiated call) and has a MPTY on hold, she is able to:
Ballot Version 67
N.S0028-0
1 1. Disconnect the single active call.

2 2. Disconnect the held MPTY.
3 3. Disconnect both. All calls, even if they are on hold, shall be released.
4 4. Join the single active call and the held MPTY together.
5 This would result in an active MPTY, except if the number of remote parties exceeds the number
6 allowed.
7 A MPTY invoke notification shall be sent towards all remote parties.
8 A Retrieve notification (according to GSM 02.83[16]) shall be sent towards the previously held
9 remote party.
10 5. Alternate between both calls.
11
12 b) Active MPTY and held call
13 If the served mobile subscriber is connected to a active MPTY and has a single call on hold, she is
14 able to:
15 1. Disconnect the active MPTY.
16 2. Disconnect the single held call.
17 3. Disconnect both. All calls, even if they are on hold, shall be released.
18 4. Join the single held call and the active MPTY together.
19 This would result in an active MPTY, except if the number of remote parties exceeds the number
20 allowed.
21 A MPTY invoke notification shall be sent towards all remote parties. A Retrieve notification
22 (according to GSM 02.83[16]) shall be sent towards all previously held remote parties.
23 5. Alternate between both calls.
24 If the served mobile subscriber is connected to an active Multi Party call and has a single call on
25 hold, a request for establishing a private communication shall be rejected by the network. (Because
26 this would lead to an active call and two calls on hold, which is not supported according to the GSM
27 Call Hold Supplementary Service).
28 An indication shall be given to the served mobile subscriber with the reason for failure.
29 4.5.3.2.5 Remote parties in a Multi-Party Call

30 Any of the remote parties shall be able to:
31 1. Put her connection to the multi-party call on hold (and typically later retrieve it). The requirements
32 of the Call Hold service then apply;
33 2. Release from the multi-party call.
34 If a remote party releases and no remote party then remains, the requirements of the normal call
35 release procedures then apply.
Ballot Version 68
N.S0028-0

3 needed.
5 GSM mode
6 The controlling subscriber may interrogate the network by the use of a control procedure, as specified
7 in GSM 02.30[11]. The network shall respond with an appropriate indication telling the subscriber
8 whether the service is supported in this network and, if so, provide a list of all Basic Service groups to
9 which the Call waiting supplementary service is active.

11
13 None identified.

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

20 None identified.

22 None identified.

24 ANSI-13641 Mode
25 An alternative procedures has been identified for 3WC. This procedure builds upon the normal 3WC
26 procedures.
27 The controlling subscriber is alerting the other party, or the controlling subscriber is in a two-way
28 conversation with the other party:
29 If the controlling subscriber enters a termination address + SEND , the system puts the other party
30 on hold. Atempts to establish a connection to the termination address.
31 If the controlling subscriber enters a termination address + SEND , if the other party is alerting, the
32 controlling subscriber is not authorized for the request, resources are not available, or the
33 termination address was not acceptable; the system applies denial treatment. Reconnects the
34 controlling subscriber and the second party.
35 If the controlling subscriber enters *FC + # + termination address + SEND , the system acts upon
36 the feature code. The system applies feature confirmation treatment. Puts the other party on
37 hold. Attempts to establish a connection to the termination address.
Ballot Version 70
N.S0028-0
1 If the controlling subscriber enters *FC + # + termination address + SEND , the system acts upon
2 the feature code. If the other party is alerting, the controlling subscriber is not authorized for the
3 request, resources are not available, or the termination address was not acceptable; the system
4 applies for denial treatment. Reconnects the controlling subscriber and the second party.
5
6 GSM Mode
7 None identified.
8

10

12 None identified.

14 None identified.

16 None identified.
18 (BOIC-exHC)
19 None identified.

21 None identified.
23 None identified.

25 None identified.

27 None identified.

29 None identified.
Ballot Version 71
N.S0028-0
1 None identified.

3 None identified.

5 None identified.

7 ANSI-13641 Mode
8 CT takes precedence over 3WC. When the controlling subscriber disconnects on an active three-way
9 call, and also has CT active, then the disconnect shall be used to transfer the call and the two non-
10 controlling parties remain connected.
11 To avoid a call transfer, the controlling subscriber may force a three-way call to disconnect by
12 sending a flash request to drop the last party added and then disconnecting the remaining party.
13 3WC takes precedence over CT for the interpretation of flash requests. If the controlling subscriber
14 presses SEND in the Holding 2-way state (and both CT and 3WC are active), the result is a
15 conference request rather than a CT drop party request. If the controlling subscriber presses SEND
16 while in the 3-way state, the last party is requested to be dropped.

18 ANSI-13641 Mode
19 3WC and CW are mutually exclusive. A call incoming to a controlling subscriber setting up or
20 engaged in a three-way call shall be given busy treatment, even if the called subscriber has CW
21 active.
22 A flash request from a subscriber authorized for 3WC, while CW alerting is being applied, shall be
23 used to respond to the CW call. If the controlling subscriber still desires a three-way call, it must first
24 dispose of the CW call before requesting a three-way call.
25 GSM Mode
26 A user who is active on a multi-party call, either as the served mobile subscriber or as remote party,
27 may receive an indication of a waiting call, provided that the maximum number of calls at the mobile
28 equipment is not exceeded.
29 After the multi-party call has been put on hold by this user, the waiting call may be accepted by the
30 user.
31 Any party involved in an active multi-party call may place the connection to the multi-party call on hold
32 and later retrieve it.

34 None identified.

36 ANSI-13641 Mode
Ballot Version 72
N.S0028-0
1 If the 3WC controlling subscriber activates the Temporary CNIR Mode during the setup of a 3WC leg,
2 then the Temporary CNIR activation applies only to that call leg.
3 If the 3WC controlling subscriber de-activates the Temporary CNIR Mode during the setup of a 3WC
4 leg, then the Temporary CNIR de-activation applies only to that call leg.

6 None identified.

8 None identified.

10 None identified.
11 See GSM 02.85[18], Section 1.6.84.1.

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

29 Remote parties in an existing multi-party call who have subscribed to connected line number
30 identification presentation shall not receive a new remote party’s number whenever a served mobile
31 subscriber adds a new remote party to the multi-party call.

33 None identified.
Ballot Version 73
N.S0028-0
1 None identified.

3 None identified.

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

7 None identified.

9 None identified.

11 None identified.

13 None identified.

15 None identified.

17 None identified.

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

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

25 Not applicable.

27 None identified.

29 None identified.
30
Ballot Version 74
N.S0028-0
2 4.6 Calling Number / Line Identification Presentation

3

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

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

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

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

31 CNIP / CLIP may be withdrawn at the subscriber’s request or for administrative reasons.
Ballot Version 75
N.S0028-0
1 CNIP / CLIP has no registration.

3 CNIP / CLIP has no de-registration (or erasure).
5 CNIP / CLIP shall be activated upon authorization (or provision).
7 CNIP / CLIP shall be de-activated upon de-authorization (or withdrawal).
9 The network automatically invokes CNIP / CLIP upon incoming call set-up when calling number
10 identification is available and presentation is not restricted.

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

25 needed.
27 GSM mode only: The subscriber can request the status of the CLIP supplementary service.
28

30
32 None identified.
Ballot Version 76
N.S0028-0
1 None identified.
3 None identified.
5 None identified.
7 In some situations with insufficient signaling capability, if the calling party number identification is not
8 available, the called party / subscriber shall receive an indication that calling number identity is not
9 available. This indication may include an alphanumeric display indicatingnumber not available.
10 For an international call with calling party number identification not available, the called party /
11 subscriber shall receive an indication that calling number identity is not available. This indication may
12 include an alphanumeric display indicating number not available.

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

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

20 None identified.
21

23

25 None identified.

27 None identified.

29 None identified.
31 (BOIC-exHC)
32 None identified.
Ballot Version 77
N.S0028-0

2 When BAIC is active, the subscriber shall receive no calling party identification or display.
4 When BIC-Roam is active and invoked, the subscriber shall receive no calling party identification or
5 display.

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

9 None identified.

11 None identified.

13 None identified.

15 None identified.

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

21 None identified.

23 If the called subscriber has CNIP / CLIP active, the calling party identification shall be presented to
24 the subscriber with the call waiting notification.

26 Not applicable.

28 CNIR / CLIR takes precedence over CNIP / CLIP.

30 Authorization and activation of CNAP may be linked to the authorization and activation of CNIP /
31 CLIP.
Ballot Version 78
N.S0028-0

2 Authorization and activation of CNAR may be linked to the authorization and activation of CNIR /
3 CLIR.

5 None identified.

7 None identified.

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

12 None identified.

14 None identified.

16 None identified.

18 None identified.
19 4.6.7.25 Over the Air Activation (OTA)

20 None identified.

22 None identified.

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

26 None identified.

28 None identified.
Ballot Version 79
N.S0028-0
1 None identified.

3 None identified.

5 None identified.

7 None identified.

9 None identified.

11 None identified.
12
Ballot Version 80
N.S0028-0
1 4.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[12]. Call Barring Supplementary Services in GSM is
35 documented in GSM 02.88[20].
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[3]. 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.
Ballot Version 81
N.S0028-0
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 4.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 4.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.
Ballot Version 82
N.S0028-0
1 4.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 4.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 4.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
26
Ballot Version 83
N.S0028-0
1 4.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 4.7.3.1 Call Detail Record

18 needed.
19

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

26 None identified.
Ballot Version 84
N.S0028-0

2 None identified.
3

5
6 4.7.5.1 Advice of Charge (AoC) or Prepaid Charging (PPC)

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

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

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

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

29 Call Barring (CB)/ODB takes precedence over CFB. If an incoming call arrives for a subscriber with
30 both CB/ODB and CFB active, the call is screened by the CB/ODB program first. If CB and ODB
31 accepts the call, an attempt is made to deliver or terminate the call to the subscriber. If the subscriber
32 is busy, then CFB is invoked.
33 If CFB is in contravention of a Call Barring / Operator Determined Barring Category, when the latter is
34 activated, then the activation shall result in making CFB quiescent. If the subscriber attempts to
35 activate a new CFB program in contravention of a Call Barring / Operator Determined Barring
36 Category, then the activation shall be denied, and the subscriber informed of the denial.
37 4.7.5.6 ANSI-13641 Call Forwarding—Default (CFD)
Ballot Version 85
N.S0028-0
1 CB/ODB takes precedence over CFD. If an incoming call arrives for a subscriber with CB/ODB and
2 CFD active, the call is screened by CB/ODB first. If CB and ODB accepts the call, an attempt is made
3 to deliver or terminate the call to the subscriber. If the subscriber does not or cannot answer the call,
4 then CFD is invoked.
5 If CFD is in contravention of a Call Barring / Operator Determined Barring Category, when the latter is
6 activated, then the activation shall result in making CFD quiescent. If the subscriber attempts to
7 activate a new CFD program in contravention of a Call Barring / Operator Determined Barring
9 Call Forwarding—No Answer (ANSI-13641 CFNA = GSM CF No Reply (CFNRy) and GSM CF Not
10 Reachable (CFNRc))
11 CB/ODB takes precedence over CFNA. If an incoming call arrives for a subscriber with CB/ODB and
12 CFNA active, the call is screened by CB/ODB first. If CB and ODB accepts the call, an attempt is
13 made to deliver or terminate the call to the subscriber. If the subscriber does not or cannot answer the
14 call, then CFNA is invoked.
15 If CFNA is in contravention of a Call Barring / Operator Determined Barring Category, when the latter
16 is activated, then the activation shall result in making CFNA quiescent. If the subscriber attempts to
17 activate a new CFNA program in contravention of a Call Barring / Operator Determined Barring

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

32 If the subscriber attempts to invoke a call transfer in contravention of a Call Barring / Operator
33 Determined Barring category, then the invocation shall be denied, and the subscriber informed of the
34 denial.
35 4.7.5.9 Call Waiting (CW) or Call Hold (CH)

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

39 None identified.
40 4.7.5.11 Calling Number/Line Identification Restriction (CNIR/CLIR)

41 If the calling number indicatespresentation restricted, the calling number shall not be presented to the
42 called party, the called station, the diversion party, or the diversion station.
Ballot Version 86
N.S0028-0

2 See GSM 02.85[18].
3 If a call is barred due to both Call Barring / Operator Determined Barring and CUG restrictions, then
4 the message or notification returned towards the caller shall be the same as if the barring was due
5 solely to Call Barring / Operator Determined Barring.

7 None identified.

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

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

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

23 None identified.

25 Interaction between MAH and CB/ODB is beyond the scope of this Standard. The following describes
26 a possible implementation:
27 CB/ODB of the MAH Pilot Directory Number takes precedence over MAH. That is, calls to the MAH
28 Pilot Directory Number with CB/ODB active are given CB/ODB treatment first. If CB/ODB screening
29 fails, the call is refused. If CB/ODB screening passes, the call is given MAH treatment.
30 4.7.5.19 Password Call Acceptance (BIC)

31 Not applicable.

33 None identified.
Ballot Version 87
N.S0028-0
1 None identified.

3 TBD.

5 None identified

7 None identified.
8 4.7.5.25 Three-Way Calling (3WC)

9 None identified.

11 None identified.

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

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.
33
Ballot Version 90
N.S0028-0
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-13641 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 4.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.
Ballot Version 91
N.S0028-0
3 4.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
Ballot Version 92
N.S0028-0

2 None Identified

4

6 None Identified

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

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

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

20 None Identified

22 None Identified

24 None Identified

26 None Identified

28 None Identified
Ballot Version 93
N.S0028-0
1 None Identified

3 None Identified

5 None Identified

7 None Identified

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
Ballot Version 94
N.S0028-0
1 None Identified

3 None Identified

5 None Identified

7 None Identified

9 None Identified

11 None Identified

13 None Identified

15 None Identified

17 None Identified

19 None Identified
Ballot Version 95
N.S0028-0
1 4.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 4.9.1.2 GSM and ANSI-13641 interoperability Feature Mapping

21 The definition of which feature capabilities are mapped between GSM and ANSI-13641 modes is
22 described below.
23 4.9.1.2.1 ANSI-41 foreign mode Capabilities (GSM --> ANSI-13641 Feature 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 4.9.1.2.2 GSM Foreign Mode Capabilities (ANSI-13641 --> 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-13641 mode. Only MS
35 display indication is provided in GSM mode.
Ballot Version 96
N.S0028-0
1 Authorization on demand by the subscriber, as described in ANSI-664[1], shall be optionally

2 supported in ANSI-13641 native mode only.

4 MWN is withdrawn by the service provider.
6 MWN is registered upon authorization.

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

28 Alert pip tone shall be applied when the MS powers up and a voice message remains unretrieved in
29 the VMS. The alert pip tone shall also be applied when the first voice message is left on a VMS and
30 the MS is available and not engaged in a call or service request.
31 Pip tone notification shall be inserted into the voice channel when the subscriber originates a call or
32 answers an incoming call and a voice message is awaiting retrieval.
33 The MS display message waiting indication shall be provided to an MS as long as there is an
34 unretrieved voice message in the VMS. The MS display indication (including message waiting
35 indication and message waiting count) is removed from the MS after the last voice message has been
36 retrieved from the VMS.
Ballot Version 97
N.S0028-0
2 needed.
4 Not applicable

6
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

26 None identified.

28 None identified.
Ballot Version 98
N.S0028-0

2 None identified.
4 (BOIC-exHC)
5 None identified.

7 None identified.
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 No pip tone notification shall be provided if call waiting has been deactivated.

27 None identified.

29 None identified.
Ballot Version 99
N.S0028-0

2 None identified.

4 None identified.

6 None identified.

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

10 MWN MS indication, count, and pip tone takes precedence over DND. MWN indication and pip tone
11 may still be applied while DND is active.
12 DND takes precedence over MWN alert pip tone. That is, while DND is active, alerting shall not be
13 applied.

15 None identified.

17 None identified.

19 Not applicable.

21 None identified.
22 4.9.6.26 Over the Air Activation (OTA)

23 None identified.

25 None identified.

27 None identified.

29 None identified.
Ballot Version 100

N.S0028-0

2 None identified.

4 None identified.

6 None identified.

8 None identified.

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

12 None identified.

14 None identified.
15
Ballot Version 101

N.S0028-0
1 4.10 GPRS in GSM Foreign mode

2 GPRS in GSM Foreign mode applies to the case where an ANSI-41 based subscriber (e.g., an ANSI-
3 41, TDMA or CDMA136 native subscriber) has registered on a GPRS network [22].
4 GPRS in GSM Foreign Mode allows a subscriber to an ANSI-41 based network (e.g., an ANSI-41,
5 TDMA or CDMA136 native subscriber) to obtain GPRS service (i.e., register for service) in GSM
6 Foreign Mode. There is no impact on ANSI-41 Foreign Mode. There is no communication between a
7 GSM SGSN and an ANSI-41 MSC and a mobile can not operate simultaneously on GPRS and ANSI-
8 41 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 applicable to telecommunications services and can be a bearer for SMS teleservices.

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

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

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

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

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

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

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

33 GPRS has the following impacts on SMS:
Ballot Version 103

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

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

37 None identified.
38 4.10.3.2 GPRS Detach

39 None identified.
Ballot Version 104

N.S0028-0
1 None identified.

3 None identified.

5 None identified.

7

9 None identified
10 4.10.5.2 Authentication
11 GSM authentication procedures are required to be supported by the IIF in the GPRS home network.
12 For GPRS in GSM Foreign Mode the authentication procedure is done according to the procedures
13 defined in GSM 02.09[21].

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

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

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

28 ODB_BAIC may be provisioned in the IIF, emulating a GPRS HLR, and it applies for GPRS and
29 Mobile Terminated SMS deliveries thru the GPRS network.
31 None identified.
Ballot Version 105

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

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.
1 The MSC and SGSN are both GSM.
Ballot Version 106

N.S0028-0
1 None identified.

3 None identified.

5 None identified.

7 None identified.
8 4.10.5.24 Emergency Services (Future)

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.
Ballot Version 107

N.S0028-0
1 None identified.

3 None Identified.

5 None identified.

7 None identified.
8
Ballot Version 108

N.S0028
1 Abstract
2 This standard addresses the interworking and interoperability between ANSI-41 MAP and GSM MAP
3 based networks in the support of subscribers roaming between networks. The interworking and
4 interoperability functionality of the services, information flows, and message mappings are specified.
5 This standard consists of four volumes:
6 Volume 0- Overview and Interworking Reference Model
7 Volume 1- Service Descriptions
8 Volume 2- Information Flows
9 Volume 3- Message Mappings
10 This is Volume 2 – Information Flows
11
Post Ballot Version i

N.S0028

Revision Date Version Comment
0 December 2000 Ballot Version
0 March 2001 Inclusion of agreed Ballot Comments
A April 2001 0 Rev A – Inclusion of GPRS
A May 2001 1 New sections added (4.13.1.9 & 4.13.1.10) dealing with
authentication failure and registration failure. Alignment
of section 4.13 with previous agreed ballot comments.
A June 2001 2 Editorial changes
A 1st August 2001 3 Editorial changes
A 14th August 4 Various technical & editorial changes incorporated

2001 during August 7th Conference call
A 15th August 5 Ballot Version - Technical changes to 4.13 GPRS

2001
A 26th November 6 Incorporation of agreed ballot comments from both TIA

2001 and T1.

one roaming
Post Ballot Version ii

N.S0028
1 Contents
2Abstract ..............................................................................................................................................i
3Document Revision History................................................................................................................ ii
4List of Tables ...................................................................................................................................xiii
5List of Figures ................................................................................................................................. xiv
6Foreword .......................................................................................................................................xxiii
71 Introduction ...........................................................................................................................1
8 1.1 General........................................................................................................................1
9 1.2 Purpose .......................................................................................................................1
10 1.3 Scope ..........................................................................................................................1
11 1.4 Organization ................................................................................................................1
122 References............................................................................................................................3
133 Definitions and Acronyms......................................................................................................5

14 3.1 Definitions....................................................................................................................5
15 3.2 Acronyms ....................................................................................................................9
164 Stage 2 Information Flows...................................................................................................12

17 4.1 Location Registration .................................................................................................12
18 4.1.1 Location Registration in GSM Foreign Mode .....................................................12
19 4.1.1.1 MS registers in a GSM network when previously registered in an ANSI-41
20 network 12
21 4.1.1.2 MS location updates in a different MSC/VLR.....................................................14
22 4.1.1.3 IMSI Detach .....................................................................................................15
23 4.1.1.4 IMSI Attach.......................................................................................................16
24 4.1.2 Location Registration in ANSI-41 Foreign Mode................................................17
25 4.1.2.1 MS registers in an ANSI-41 network when previously registered in a GSM
26 network 17
28 4.1.2.3 MS Powers Off .................................................................................................20
29 4.1.2.4 MS Powers On .................................................................................................20
30 4.1.3 Location Registration in Native Mode................................................................20
32 network 20
34 network 22
35 4.2 Fault Recovery Procedures........................................................................................24
36 4.2.1 Fault Recovery Procedures in GSM Foreign Mode............................................24
37 4.2.1.1 Recovery from Failure at the ANSI-41 HLR.......................................................24
38 4.2.1.2 Recovery from Failure at the IIF........................................................................25
39 4.2.1.3 Recovery from Failure at the serving GSM VLR ................................................26
40 4.2.2 Fault Recovery Procedures in ANSI-41 Foreign Mode ......................................27
Post Ballot Version iii

N.S0028
1 4.2.2.1 Recovery from Failure at the GSM HLR............................................................27

3 4.2.2.3 Recovery from Data Failure at the ANSI-41 VLR...............................................28
4 4.3 Authentication............................................................................................................29
5 4.3.1 ANSI-41 Foreign Mode Authentication Activation ..............................................29
6 4.3.1.1 Receiving AUTHREQ Message ........................................................................29
7 4.3.1.2 Receiving AFREPORT Message ......................................................................31
8 4.3.1.3 Receiving ASREPORT Message ......................................................................33
9 4.3.1.4 Receiving BSCHALL Message .........................................................................35
10 4.3.1.5 Receiving AUTHDIR Message..........................................................................37
11 4.3.1.6 Receiving COUNTREQ Message .....................................................................39
12 4.3.2 GSM Foreign Mode Authentication Activation ...................................................41
13 4.3.2.1 Authentication Related Messages.....................................................................41
14 4.4 Subscriber Data Management....................................................................................43
15 4.4.1 Subscriber Data Management Procedures in ANSI-41 Foreign Mode................43
16 4.4.1.1 Subscriber Deletion ..........................................................................................43
17 4.4.1.2 Subscriber Data Modification ............................................................................44
18 4.4.2 Subscriber Data Management Procedures in GSM Foreign Mode.....................47
20 4.4.2.2 Modifying Subscriber Data................................................................................48
21 4.5 Automatic Call Delivery ..............................................................................................49
22 4.5.1 Automatic Call Delivery Activation/Deactivation.................................................49
23 4.5.2 Automatic Call Delivery Invocation....................................................................49
24 4.5.2.1 Call Delivery to ANSI-41 Subscriber Roaming in GSM Network ........................49
25 4.5.2.2 Delivery to an ANSI-41 Subscriber Roaming in a GSM Network –
26 Unsuccessful Case...........................................................................................50
27 4.5.2.3 Call Delivery to a GSM Subscriber Roaming in ANSI-41 Network –
28 Successful Case...............................................................................................51
31 4.6 Call Forwarding..........................................................................................................53
32 4.6.1 Call forwarding scenarios for ANSI-41 foreign mode .........................................53
33 4.6.1.1 Call forwarding unconditional (CFU)..................................................................53
34 4.6.1.2 Call forwarding busy (CFB)...............................................................................61
35 4.6.1.3 Call forwarding no reply (CFNRy) .....................................................................66
36 4.6.1.4 Call forwarding not reachable (CFNRc).............................................................69
37 4.6.2 Call forwarding scenarios for GSM foreign mode ..............................................73
40 4.6.2.3 Call forwarding no answer (CFNA)....................................................................86
41 4.7 Optimal Routing for Late Call Forwarding ...................................................................88
42 4.7.1 ANSI-41 Foreign Mode .....................................................................................88
43 4.7.1.1 ANSI-41 Foreign Mode - Success condition ......................................................88
44 4.7.1.2 ANSI-41 Foreign Mode - Failure condition ........................................................91
45 4.7.2 GSM Foreign Mode ..........................................................................................92
46 4.7.2.1 GSM Foreign Mode - Success Case.................................................................92
47 4.7.2.2 GSM Foreign Mode - Failure case ....................................................................94
Post Ballot Version iv

N.S0028
1 4.8 Call Waiting ...............................................................................................................95

2 4.8.1 Call Waiting Activation ......................................................................................95
3 4.8.1.1 ANSI-41 Foreign Mode Successful Call Waiting Activation................................95
4 4.8.1.2 ANSI-41 Foreign Mode Unsuccessful Call Waiting Activation ............................96
5 4.8.1.3 GSM Foreign Mode Feature Activation .............................................................98
6 4.8.2 Call Waiting Deactivation ..................................................................................99
7 4.8.2.1 ANSI-41 Foreign Mode Call Waiting Deactivation .............................................99
8 4.8.2.2 GSM Foreign Mode Feature Deactivation .......................................................101
9 4.9 Calling Number / Line Identification Presentation/Restriction ....................................104
10 4.9.1 Handling of calling number/ line identification presentation..............................104
11 4.9.1.1 GSM Foreign Mode ........................................................................................104
12 4.9.1.2 ANSI-41 Foreign Mode ...................................................................................106
13 4.9.2 Handling of calling number/ line identification restriction..................................107
14 4.9.2.1 General 107
15 4.9.2.2 GSM Foreign Mode ........................................................................................107
17 4.10 Call Barring and Operator Determined Barring .........................................................108
18 4.10.1 Activation of Barring at VLR............................................................................108
19 4.10.1.1 Activation of Call Restrictions while in GSM Foreign Mode ............................108
20 4.10.1.2 Activation of Call Barring while in ANSI-41 Foreign Mode ..............................109
21 4.10.2 Invocation of Barring of Incoming Calls ...........................................................109
22 4.10.2.1 GSM Foreign Mode.......................................................................................109
23 4.10.2.2 ANSI-41 Foreign Mode .................................................................................109
24 4.10.3 Invocation of Barring of Roaming ....................................................................109
25 4.10.3.1 GSM Foreign Mode.......................................................................................109
27 4.10.4 Invocation of Barring of Supplementary Services Management .......................111
28 4.10.4.1 GSM Foreign Mode.......................................................................................111
30 4.11 Short Message Service ............................................................................................114
31 4.11.1 Assumptions...................................................................................................114
32 4.11.2 Mobile Station only Supports GHOST/WEMT .................................................115
33 4.11.2.1 Short Message from CMT Mobile Station to GHOST/WEMT Mobile Station
34 both in Native Mode........................................................................................115
35 4.11.2.2 Short Message sent from GHOST/WEMT Mobile Station to CMT Mobile
36 Station, both in Native Mode...........................................................................116
37 4.11.3 Mobile Terminating SMS in GSM Foreign Mode..............................................117
38 4.11.3.1 Successful Mobile Terminating ANSI-41 SMS (CMT) mapped to GSM SMS..117
39 4.11.3.2 Successful Mobile Terminating ANSI-41 SMS (GHOST/WEMT) Mapped to
40 GSM SMS ......................................................................................................119
41 4.11.3.3 Unsuccessful Mobile Terminated Delivery (Failure at MSC)...........................121
42 4.11.3.4 Unsuccessful Mobile Terminated Delivery (Failure at IIF) ..............................123
43 4.11.3.5 Alerting for an ANSI-41 Subscriber in GSM Foreign Mode.............................124
44 4.11.4 Mobile Terminated SMS in ANSI-41 Foreign Mode .........................................124
45 4.11.4.1 Successful GSM SMS mapped to ANSI-41 (CMT) SMS ................................125
46 4.11.4.2 Successful GSM SMS mapped to ANSI-41 (GHOST/WEMT) SMS................127
47 4.11.4.3 Unsuccessful GSM SMS mapped to ANSI-41 SMS (Failure at MS) ...............128
Post Ballot Version v

N.S0028
1 4.11.4.4 Unsuccessful Delivery to GSM Subscriber (Postponed at MSC) ....................129

2 4.11.4.5 Unsuccessful Delivery to GSM Subscriber (Failure at IIF)..............................132
3 4.11.4.6 Alerting for a GSM Subscriber in ANSI-41 Foreign Mode...............................132
4 4.11.5 Message Flows for Mobile Originated SMS in GSM Foreign Mode..................134
5 4.11.5.1 Successful Mobile Originated Delivery ..........................................................134
6 4.11.5.2 Unsuccessful Mobile Originated (Failure at MC) ............................................135
7 4.11.5.3 Unsuccessful Mobile Originated (Failure at IIF) .............................................136
8 4.11.6 Message Flows for Mobile Originated SMS in ANSI-41 Foreign Mode.............136
10 4.11.6.2 Unsuccessful Mobile Originated (Failure at SMSC) .......................................138
12 4.12 Message Waiting Notification ...................................................................................140
13 4.12.1 GSM Foreign Mode ........................................................................................140
14 4.12.1.1 Indicator in ANSI-41 Registration Notification Return Result mapped to GSM
15 SMS 141
16 4.12.1.2 ANSI-41 Qualification Directive mapped to GSM SMS...................................143
17 4.12.1.3 Handling when GSM MSC/VLR only supports GSM Phase 1 (MAP V1).........144
18 4.12.1.4 Handling at SMS delivery failure at the IIF.....................................................145
19 4.12.1.5 Handling at SMS delivery failure at the MSC/VLR or at the Mobile Station.....147
20 4.12.2 ANSI-41 Foreign Mode ...................................................................................148
21 4.12.2.1 GSM SMS mapped to ANSI-41 Qualification Directive...................................149
22 4.12.2.2 GSM SMS mapped to ANSI-41 SMS using GHOST or WEMT Teleservice....151
23 4.12.2.3 Clearing of MWN Information after Retrieval of Messages while in ANSI-41
24 Foreign Mode – QualDir Method.....................................................................154
26 4.12.2.5 Handling at SMS delivery failure at the MSC/VLR – QualDir Method .............158
27 4.12.2.6 Handling at SMS delivery failure at the MSC/VLR – GHOST/WEMT SMS
28 Method 159
29 4.12.2.7 GSM SMS mapped to ANSI-41 Qualification Directive and to Registration
30 Notification Return Result ...............................................................................162
31 4.13 GPRS in GSM Foreign Mode ...................................................................................166
32 4.13.1 Location Registration Scenarios......................................................................166
33 4.13.1.1 GPRS Attach (not currently registered)..........................................................167
34 4.13.1.2 GPRS Attach when currently registered in an ANSI-41 network.....................171
35 4.13.1.3 Inter-SGSN routing area update....................................................................175
36 4.13.1.4 GPRS- Attach when only GSM CS Attached ................................................179
37 4.13.1.5 Combined GSM and GPRS attach when not currently registered...................181
38 4.13.1.6 Combined Inter-SGSN Routeing Area/Location Area Update.........................189
39 4.13.1.7 Inter-SGSN routing area update when GSM CS and GPRS attached (GSM
40 MSC remains constant) ..................................................................................193
41 4.13.1.8 Combined Attach When Currently Registered in an ANSI-41 MSC ................196
42 4.13.1.9 Authentication Failure at the IIF.....................................................................205
43 4.13.1.10 Registration Failure at the ANSI-41HLR .....................................................205
44 4.13.2 Location Deregistration Scenarios ..................................................................205
45 4.13.2.1 GSM CS (IMSI) Detach while GPRS and GSM CS Attached .........................205
46 4.13.2.2 GPRS Detach While Attached for Both GPRS and GSM CS Services ...........205
47 4.13.2.3 GPRS Detach While Attached for GPRS Services Only.................................205
48 4.13.2.4 Combined GPRS Detach and GSM CS (IMSI) Detach...................................205
Post Ballot Version vi

N.S0028
1 4.13.2.5 GPRS Detach Followed By Purge .................................................................206

2 4.13.2.6 IIF - Initiated Detach.....................................................................................208
3 4.13.3 SMS Scenarios...............................................................................................209
4 4.13.3.1 SMS Scenarios for Mobile Terminated SMS while GPRS Attached ...............209
5 4.13.3.1.1 Successful Mobile Terminated ANSI-41 SMS (CMT) Mapped to GSM SMS 209
6 4.13.3.1.2 Successful Mobile Terminating ANSI-41 SMS (GHOST/WEMT) Mapped to
7 GSM SMS ......................................................................................................211
8 4.13.3.1.3 Unsuccessful Mobile Terminated Delivery (Failure at SGSN) ......................212
9 4.13.3.1.4 Unsuccessful Mobile Terminated Delivery (Failure at IIF) ............................213
10 4.13.3.1.5 Alerting for an ANSI-41 Subscriber for GPRS in GSM Foreign Mode...........214
11 4.13.4 Message Flows for Mobile Originated SMS when operating GPRS in GSM Foreign
12 Mode .................................................................................................215
13 4.13.4.1 Successful Mobile Originated SMS to MC......................................................215
14 4.13.4.2 Unsuccessful Mobile Originated (Failure at MC).............................................216
15 4.13.4.3 Unsuccessful Mobile Originated (Failure at IIF)..............................................217
16 4.13.5 Message Waiting Notification while GPRS Attached in GSM Foreign Mode ....218
17 4.13.5.1 Indicator in ANSI-41 Registration Notification Return Result mapped to GSM SMS219
18 4.13.5.2 ANSI-41 Qualification Directive mapped to GSM SMS ...................................221
19 4.13.5.3 Handling at SMS delivery failure at the SGSN or at the Mobile Station ...........222
20 4.13.6. Call Delivery Scenarios..................................................................................224
21 4.13.6.1 Call Delivery Scenarios in GSM Foreign Mode while GSM CS and GPRS
22 Attached.........................................................................................................224
23 4.13.6.1.1 Call Delivery to ANSI-41 Subscriber Roaming on a GSM/GPRS Network...224
24 4.13.6.1.2 Call Delivery to ANSI-41 Subscriber Roaming in a GPRS Network
25 (Unsuccessful)................................................................................................226
26 4.13.6.2 Successful Network-Requested PDP Context Activation Procedure ..............228
27 4.13.6.3 Unsuccessful Network-Requested PDP Context Activation Procedure...........229
28 4.13.7 Packet Domain Subscriber Data in the IIF......................................................229
29Annex A (informative) ....................................................................................................................230
30 Abstract .........................................................................................................................................i
31 Document Revision History ........................................................................................................... ii
32 Contents ...................................................................................................................................... iii
33 List of Tables ..............................................................................................................................viii
34 List of Figures .............................................................................................................................. ix
35 Foreword ................................................................................................................................... xiv
36 1 Introduction ...........................................................................................................................1
37 1.1 General........................................................................................................................1
38 1.2 Purpose .......................................................................................................................1
39 1.3 Scope ..........................................................................................................................1
40 1.4 Organization ................................................................................................................1
Post Ballot Version vii

N.S0028
1 2 References............................................................................................................................2
2 3 Definitions and Acronyms......................................................................................................3

3 3.1 Definitions....................................................................................................................3
4 3.2 Acronyms ....................................................................................................................6
5 4 Stage 2 Information Flows.....................................................................................................9

6 4.1 Location Registration ...................................................................................................9
7 4.1.1 Location Registration in GSM Foreign Mode .......................................................9
9 network 9
11 4.1.1.3 IMSI Detach .....................................................................................................12
12 4.1.1.4 IMSI Attach.......................................................................................................13
13 4.1.2 Location Registration in ANSI-41 Foreign Mode................................................14
15 network 14
17 4.1.2.3 MS Powers Off .................................................................................................17
18 4.1.2.4 MS Powers On .................................................................................................17
19 4.1.3 Location Registration in Native Mode................................................................17
21 network 17
23 network 19
24 4.2 Fault Recovery Procedures........................................................................................21
25 4.2.1 Fault Recovery Procedures in GSM Foreign Mode............................................21
26 4.2.1.1 Recovery from Failure at the ANSI-41 HLR.......................................................21
28 4.2.1.3 Recovery from Failure at the serving GSM VLR ................................................23
29 4.2.2 Fault Recovery Procedures in ANSI-41 Foreign Mode ......................................24
30 4.2.2.1 Recovery from Failure at the GSM HLR............................................................24
32 4.2.2.3 Recovery from Data Failure at the ANSI-41 VLR...............................................25
33 4.3 Authentication............................................................................................................26
34 4.3.1 ANSI-41 Foreign Mode Authentication Activation ..............................................26
35 4.3.1.1 Receiving AUTHREQ Message ........................................................................26
36 4.3.1.2 Receiving AFREPORT Message ......................................................................28
37 4.3.1.3 Receiving ASREPORT Message ......................................................................30
38 4.3.1.4 Receiving BSCHALL Message .........................................................................32
39 4.3.1.5 Receiving AUTHDIR Message..........................................................................34
40 4.3.1.6 Receiving COUNTREQ Message .....................................................................36
41 4.3.2 GSM Foreign Mode Authentication Activation ...................................................38
42 4.3.2.1 Authentication Related Messages.....................................................................38
43 4.4 Subscriber Data Management....................................................................................40
44 4.4.1 Subscriber Data Management Procedures in ANSI-41 Foreign Mode................40
46 4.4.1.2 Subscriber Data Modification ............................................................................41
Post Ballot Version viii

N.S0028
1 4.4.2 Subscriber Data Management Procedures in GSM Foreign Mode.....................44

3 4.4.2.2 Modifying Subscriber Data................................................................................45
4 4.5 Automatic Call Delivery ..............................................................................................46
5 4.5.1 Automatic Call Delivery Activation/Deactivation.................................................46
6 4.5.2 Automatic Call Delivery Invocation....................................................................46
7 4.5.2.1 Call Delivery to ANSI-136 Subscriber Roaming in GSM Network.......................46
8 4.5.2.2 Delivery to an ANSI-136 Subscriber Roaming in a GSM Network –
11 Successful Case...............................................................................................48
14 4.6 Call Forwarding..........................................................................................................50
15 4.6.1 Call forwarding scenarios for ANSI-41 foreign mode .........................................50
18 4.6.1.3 Call forwarding no reply (CFNRy) .....................................................................63
19 4.6.1.4 Call forwarding not reachable (CFNRc).............................................................66
20 4.6.2 Call forwarding scenarios for GSM foreign mode ..............................................70
23 4.6.2.3 Call forwarding no answer (CFNA)....................................................................83
24 4.7 Optimal Routing for Late Call Forwarding ...................................................................85
25 4.7.1 ANSI-41 Foreign Mode .....................................................................................85
26 4.7.1.1 ANSI-41 Foreign Mode - Success condition ......................................................85
27 4.7.1.2 ANSI-41 Foreign Mode - Failure condition ........................................................88
28 4.7.2 GSM Foreign Mode ..........................................................................................89
29 4.7.2.1 GSM Foreign Mode - Success Case.................................................................89
30 4.7.2.2 GSM Foreign Mode - Failure case ....................................................................91
31 4.8 Call Waiting ...............................................................................................................92
32 4.8.1 Call Waiting Activation ......................................................................................92
33 4.8.1.1 ANSI-41 Foreign Mode Successful Call Waiting Activation................................92
34 4.8.1.2 ANSI-41 Foreign Mode Unsuccessful Call Waiting Activation ............................93
35 4.8.1.3 GSM Foreign Mode Feature Activation .............................................................95
36 4.8.2 Call Waiting Deactivation ..................................................................................96
37 4.8.2.1 ANSI-41 Foreign Mode Call Waiting Deactivation .............................................96
38 4.8.2.2 GSM Foreign Mode Feature Deactivation .........................................................98
39 4.9 Calling Number / Line Identification Presentation/Restriction ....................................101
40 4.9.1 Handling of calling number/ line identification presentation..............................101
41 4.9.1.1 GSM Foreign Mode ........................................................................................101
43 4.9.2 Handling of calling number/ line identification restriction..................................104
44 4.9.2.1 General 104
45 4.9.2.2 GSM Foreign Mode ........................................................................................104
47 4.10 Call Barring and Operator Determined Barring .........................................................105
Post Ballot Version ix

N.S0028
1 4.10.1 Activation of Barring at VLR............................................................................105

2 4.10.1.1 Activation of Call Restrictions while in GSM Foreign Mode ............................105
3 4.10.1.2 Activation of Call Barring while in ANSI-41 Foreign Mode ..............................106
4 4.10.2 Invocation of Barring of Incoming Calls ...........................................................106
5 4.10.2.1 GSM Foreign Mode.......................................................................................106
7 4.10.3 Invocation of Barring of Roaming ....................................................................106
8 4.10.3.1 GSM Foreign Mode.......................................................................................106
10 4.10.4 Invocation of Barring of Supplementary Services Management .......................108
11 4.10.4.1 GSM Foreign Mode.......................................................................................108
13 4.11 Short Message Service ............................................................................................111
14 4.11.1 Assumptions...................................................................................................111
15 4.11.2 Mobile Station only Supports GHOST .............................................................112
16 4.11.2.1 Short Message from CMT Mobile Station to GHOST Mobile Station both in
17 Native Mode ...................................................................................................112
18 4.11.2.2 Short Message sent from GHOST Mobile Station to CMT Mobile Station,
19 both in Native Mode........................................................................................113
20 4.11.3 Mobile Terminating SMS in GSM Foreign Mode..............................................114
21 4.11.3.1 Successful Mobile Terminating ANSI-136 SMS (CMT) mapped to GSM
22 SMS 114
23 4.11.3.2 Successful Mobile Terminating ANSI-136 SMS (GHOST) Mapped to GSM
24 SMS 115
25 4.11.3.3 Unsuccessful Mobile Terminated Delivery (Failure at MSC)...........................116
26 4.11.3.4 Unsuccessful Mobile Terminated Delivery (Failure at IIF) ..............................118
27 4.11.3.5 Alerting for an ANSI-136 Subscriber in GSM Foreign Mode...........................119
28 4.11.4 Mobile Terminated SMS in ANSI-41 Foreign Mode .........................................119
29 4.11.4.1 Successful GSM SMS mapped to ANSI-136 (CMT) SMS ..............................120
30 4.11.4.2 Successful GSM SMS mapped to ANSI-136 (GHOST) SMS .........................122
31 4.11.4.3 Unsuccessful GSM SMS mapped to ANSI-136 SMS (Failure at MS) .............123
32 4.11.4.4 Unsuccessful Delivery to GSM Subscriber (Postponed at MSC) ....................124
33 4.11.4.5 Unsuccessful Delivery to GSM Subscriber (Failure at IIF)..............................126
34 4.11.4.6 Alerting for a GSM Subscriber in ANSI-41 Foreign Mode...............................127
35 4.11.5 Message Flows for Mobile Originated SMS in GSM Foreign Mode..................128
37 4.11.5.2 Unsuccessful Mobile Originated (Failure at MC) ............................................129
39 4.11.6 Message Flows for Mobile Originated SMS in ANSI-41 Foreign Mode.............130
41 4.11.6.2 Unsuccessful Mobile Originated (Failure at SMSC) .......................................132
43 4.12 Message Waiting Notification ...................................................................................134
44 4.12.1 GSM Foreign Mode ........................................................................................134
45 4.12.1.1 Indicator in ANSI-41 Registration Notification Return Result mapped to GSM
46 SMS 135
47 4.12.1.2 ANSI-41 Qualification Directive mapped to GSM SMS...................................137
48 4.12.1.3 Handling when GSM MSC/VLR only supports GSM Phase 1 (MAP V1).........138
Post Ballot Version x

N.S0028

2 4.12.1.5 Handling at SMS delivery failure at the MSC/VLR or at the Mobile Station.....141
3 4.12.2 ANSI-41 Foreign Mode ...................................................................................142
4 4.12.2.1 GSM SMS mapped to ANSI-41 Qualification Directive...................................143
5 4.12.2.2 GSM SMS mapped to TDMA SMS using GHOST Teleservice.......................144
6 4.12.2.3 Clearing of MWN Information after Retrieval of Messages while in ANSI-41
7 Foreign Mode – QualDir Method.....................................................................146
9 4.12.2.5 Handling at SMS delivery failure at the MSC/VLR – QualDir Method .............149
10 4.12.2.6 Handling at SMS delivery failure at the MSC/VLR – GHOST SMS Method ....150
11 4.12.2.7 GSM SMS mapped to ANSI-41 Qualification Directive and to Registration
12 Notification Return Result ...............................................................................152
13 4.13 GPRS in GSM Foreign Mode ...................................................................................154
14 4.13.1 Location Registration Scenarios......................................................................154
15 4.13.1.1 GPRS Attach (not currently registered)..........................................................155
16 4.13.1.2 GPRS Attach when currently registered in an ANSI-41 network.....................159
17 4.13.1.3 Inter-SGSN routing area update....................................................................163
18 4.13.1.4 GPRS- Attach when only GSM CS Attached ................................................167
19 4.13.1.5 Combined GSM and GPRS attach when not currently registered...................169
20 4.13.1.6 Combined Inter-SGSN Routeing Area/Location Area Update.........................177
21 4.13.1.7 Inter-SGSN routing area update when GSM CS and GPRS attached (GSM
22 MSC remains constant) ..................................................................................181
23 4.13.1.8 Combined Attach When Currently Registered in an ANSI-41 MSC ................184
24 4.13.1.9 Authentication Failure at the IIF.....................................................................193
25 4.13.1.10 Registration Failure at the ANSI-41HLR .....................................................193
26 4.13.2 Location Deregistration Scenarios ..................................................................193
27 4.13.2.1 GSM CS (IMSI) Detach while GPRS and GSM CS Attached .........................193
28 4.13.2.2 GPRS Detach While Attached for Both GPRS and GSM CS Services ...........193
29 4.13.2.3 GPRS Detach While Attached for GPRS Services Only.................................193
30 4.13.2.4 Combined GPRS Detach and GSM CS (IMSI) Detach...................................193
31 4.13.2.5 GPRS Detach Followed By Purge .................................................................194
32 4.13.2.6 IIF - Initiated Detach.....................................................................................196
33 4.13.3 SMS Scenarios...............................................................................................197
34 4.13.3.1 SMS Scenarios for Mobile Terminated SMS while GPRS Attached ...............197
35 4.13.3.1.1 Successful Mobile Terminated ANSI-136 SMS (CMT) Mapped to GSM
36 SMS ...............................................................................................................197
37 4.13.3.1.2 Successful Mobile Terminating ANSI-136 SMS (GHOST) Mapped to GSM
38 SMS ...............................................................................................................199
39 4.13.3.1.3 Unsuccessful Mobile Terminated Delivery (Failure at SGSN) ......................200
40 4.13.3.1.4 Unsuccessful Mobile Terminated Delivery (Failure at IIF) ............................201
41 4.13.3.1.5 Alerting for an ANSI-136 Subscriber for GPRS in GSM Foreign Mode.........202
42 4.13.4 Message Flows for Mobile Originated SMS when operating GPRS in GSM Foreign
43 Mode .................................................................................................203
44 4.13.4.1 Successful Mobile Originated SMS to MC......................................................203
45 4.13.4.2 Unsuccessful Mobile Originated (Failure at MC).............................................204
46 4.13.4.3 Unsuccessful Mobile Originated (Failure at IIF)..............................................205
47 4.13.5 Message Waiting Notification while GPRS Attached in GSM Foreign Mode ....206
48 4.13.5.1 Indicator in ANSI-41 Registration Notification Return Result mapped to GSM SMS207
Post Ballot Version xi

N.S0028
1 4.13.5.2 ANSI-41 Qualification Directive mapped to GSM SMS ...................................209

2 4.13.5.3 Handling at SMS delivery failure at the SGSN or at the Mobile Station ...........210
3 4.13.6. Call Delivery Scenarios..................................................................................212
4 4.13.6.1 Call Delivery Scenarios in GSM Foreign Mode while GSM CS and GPRS
5 Attached.........................................................................................................212
6 4.13.6.1.1 Call Delivery to ANSI-136 Subscriber Roaming on a GSM/GPRS Network.212
7 4.13.6.1.2 Call Delivery to ANSI-136 Subscriber Roaming in a GPRS Network
8 (Unsuccessful)................................................................................................214
9 4.13.6.2 Successful Network-Requested PDP Context Activation Procedure ..............216
10 4.13.6.3 Unsuccessful Network-Requested PDP Context Activation Procedure...........217
11 4.13.7 Packet Domain Subscriber Data in the IIF......................................................217
12 Annex A (informative) ..............................................................................................................218

13
14
15
Post Ballot Version xii

N.S0028
1 List of Tables
2 There are no tables in this volume.
3
Post Ballot Version xiii

N.S0028
1 List of Figures
2 Figure 1: Registration on a GSM Network – GSM Foreign Mode ...................................................12
3 Figure 2: Registration in a different MSC/VLR – GSM Foreign Mode .............................................14
4 Figure 3: Registration on an ANSI-41 network – ANSI-41 Foreign Mode .......................................17
5 Figure 4: Registration in a different MSC/VLR – ANSI-41 Foreign Mode........................................19
6 Figure 5: Registration in an ANSI-41 Network (Native Mode).........................................................21
7 Figure 6: Registration in a GSM Network (Native Mode)................................................................22
8 Figure 7: Failure at the ANSI-41 HLR (GSM Foreign Mode) ..........................................................24
9 Figure 8: IIF Failure (GSM Foreign Mode).....................................................................................25
10 Figure 9: Terminating Call Flow following a GSM VLR Failure .......................................................26
11 Figure 10: Failure at a GSM HLR (ANSI-41 Foreign Mode) ...........................................................27
12 Figure 11: AUTHREQ - Successful Case ......................................................................................29
13 Figure 12: AUTHREQ - Unsuccessful Case ..................................................................................30
14 Figure 13: AFREPORT - Successful Case ....................................................................................31
15 Figure 14: AFREPORT - Unsuccessful Case ................................................................................32
16 Figure 15: ASREPORT - Successful Case ....................................................................................33
17 Figure 16: ASREPORT - Unsuccessful Case ................................................................................34
18 Figure 17: BSCHALL - Successful Case .......................................................................................35
19 Figure 18: BSCHALL - Unsuccessful Case ...................................................................................36
20 Figure 19: AUTHDIR - Successful Case........................................................................................37
21 Figure 20: AUTHDIR - Unsuccessful Case....................................................................................38
22 Figure 21: COUNTREQ - Successful Case ...................................................................................39
23 Figure 22: COUNTREQ - Unsuccessful Case ...............................................................................40
24 Figure 23: SEND_AUTH_INFO.....................................................................................................41
25 Figure 24: SEND_PARAMETER with Request for Authentication Set............................................42
26 Figure 25: Subscriber Deletion – ANSI-41 Foreign Mode ..............................................................43
27 Figure 26: Insert Subscriber Data Procedure.................................................................................44
28 Figure 27: Delete Subscriber Data Procedure ...............................................................................45
29 Figure 28: Cancel Location Procedure ..........................................................................................46
30 Figure 29: Subscriber Deletion- GSM Foreign Mode .....................................................................47
31 Figure 30: Subscriber Data Modification........................................................................................48
32 Figure 31: Call Delivery to ANSI-41 Subscriber Roaming in a GSM Network .................................49
Post Ballot Version xiv

N.S0028
1 Figure 32: Unsuccessful Call Delivery to an ANSI-41 Subscriber Roaming in a GSM Network.......50
2 Figure 33: Call Delivery to GSM Subscriber Roaming in an ANSI-41 Network ...............................51
3 Figure 34: Unsuccessful Call Delivery to GSM Subscriber Roaming in an ANSI-41 Network..........52
4 Figure 35: CFU registration...........................................................................................................53
5 Figure 36: CFU deregistration (erasure)........................................................................................55
6 Figure 37: CFU activation .............................................................................................................57
7 Figure 38: CFU deactivation .........................................................................................................59
8 Figure 39: CFU invocation ............................................................................................................60
9 Figure 40: CFB invocation (Scenario 1a, “CFB#=MSRN method”).................................................62
10 Figure 41: CFB invocation (Scenario 1b, “AbsentSubscriber method”)...........................................63
11 Figure 42: CFB invocation (Scenario 2, without OR)......................................................................64
12 Figure 43: CFNRy invocation (Scenario 1, without OR) .................................................................67
13 Figure 44: CFNRc invocation (Scenario 1) ....................................................................................70
14 Figure 45: CFNRc invocation (Scenario 2, without OR) .................................................................71
16 Figure 47: CFU deregistration (erasure)........................................................................................74
20 Figure 51: Obtaining forward-to numbers ......................................................................................78
21 Figure 52: CFB registration ...........................................................................................................79
22 Figure 53: CFB deregistration (erasure) ........................................................................................81
23 Figure 54: CFB activation..............................................................................................................82
24 Figure 55: CFB deactivation..........................................................................................................83
25 Figure 57: CFNA invocation (Scenario 1, without OR) ...................................................................87
26 Figure 58: Optimal Routing with Late Call Forwarding (ANSI-41 Foreign Mode) Success Case .....88
27 Figure 59: Optimal Routing with Late Call Forwarding (ANSI-41 Foreign Mode) Failure Case........91
28 Figure 60: Optimal Routing with Late Call Forwarding (GSM Foreign Mode) Success Case ..........92
29 Figure 61: Optimal Routing with Late Call Forwarding (GSM Foreign Mode) Failure Case.............94
30 Figure 62: ANSI-41 Foreign Mode Call Waiting Activation .............................................................95
31 Figure 63: ANSI-41 Foreign Mode Unsuccessful Call Waiting Activation .......................................97
32 Figure 64: GSM Foreign Mode Call Waiting Activation ..................................................................98
33 Figure 65: ANSI-41 Foreign Mode Call Waiting Deactivation .......................................................100
Post Ballot Version xv

N.S0028
1 Figure 66: GSM Foreign Mode Call Waiting Deactivation ............................................................102

2 Figure 67: Calling number/ line identification presentation: mobile station or fixed terminal to
3 mobile station – GSM Foreign Mode .....................................................................104
5 mobile station – ANSI-41 Foreign Mode ................................................................106
6 Figure 69: Activation of Call Restriction - GSM Foreign Mode......................................................108
7 Figure 70: Activation of Call Barring – ANSI-41 Foreign Mode.....................................................109
8 Figure 71: Invocation of Barring of Roaming – GSM Foreign Mode ............................................110
9 Figure 72: Invocation of Barring of Roaming – ANSI-41 Foreign Mode ........................................111
10 Figure 73: Invocation of Barring of Supplementary Service Control – GSM Foreign Mode ...........112
11 Figure 74: Invocation of Barring of Supplementary Services Management – ANSI-41 Foreign
12 Mode ....................................................................................................................113
13 Figure 75: Short Message from a TDMA or CDMA CMT phone to a GHOST or WEMT mobile
14 station, both in native mode ..................................................................................115
15 Figure 76: Short Message from a GHOST or WEMT mobile station to a TDMA CMT or CDMA
16 CMT Phone, both in native mode ..........................................................................116
17 Figure 77: Successful Mobile Terminating ANSI-41 SMS (CMT) mapped to GSM SMS...............118
18 Figure 78: Successful Mobile Terminating ANSI-41 SMS (GHOST/WEMT) mapped to GSM
19 SMS .....................................................................................................................120
20 Figure 79: Unsuccessful Mobile Terminated Delivery (Failure at MSC)........................................121
21 Figure 80: Unsuccessful Mobile Terminated Delivery (Failure at IIF)............................................123
22 Figure 81: Alerting for an ANSI-41 Subscriber in GSM Foreign Mode ..........................................124
23 Figure 82: Successful GSM SMS mapped to ANSI-41 (CMT) SMS .............................................125
24 Figure 83: Successful GSM SMS mapped to ANSI-41 (GHOST/WEMT) SMS.............................127
25 Figure 84: Successful GSM SMS mapped to ANSI-41 SMS (Failure at MS) ................................128
26 Figure 85: Unsuccessful Delivery to GSM Subscriber (Postponed at MSC) .................................130
27 Figure 86: Unsuccessful Delivery to GSM Subscriber (Failure at IIF)...........................................132
28 Figure 87: Alerting for a GSM Subscriber in ANSI-41 Foreign Mode............................................133
29 Figure 88: Successful Mobile Originated Delivery........................................................................134
30 Figure 89: Unsuccessful Mobile Originated (Failure at MC) .........................................................135
31 Figure 90: Unsuccessful Mobile Originated (Failure at IIF)...........................................................136
32 Figure 91: Successful Mobile Originated Delivery – ANSI-41 Foreign Mode ................................137
33 Figure 92: Successful Mobile Originated (Failure at SMSC) – ANSI-41 Foreign Mode .................138
34 Figure 93: Unsuccessful Mobile Originated (Failure at IIF) – ANSI-41 Foreign Mode ...................139
35 Figure 94: Indicator in ANSI-41 Registration Notification Return Result mapped to GSM SMS.....141
Post Ballot Version xvi

N.S0028
1 Figure 95: ANSI-41 Qualification Directive mapped to GSM SMS...............................................143

2 Figure 96: Handling when GSM MSC/VLR only supports GSM Phase 1 (MAP V1)......................144
3 Figure 97: Handling at SMS delivery failure at the IIF .................................................................145
4 Figure 98: Handling at SMS delivery failure at the MSC/VLR or at the MS..................................147
5 Figure 99: GSM SMS mapped to ANSI-41 Qualification Directive................................................150
6 Figure 100: GSM SMS mapped to ANSI-41 using GHOST/WEMT Teleservice ...........................153
7 Figure 101: Clearing of MWN Information after Retrieval of Messages while in ANSI-41
8 Foreign mode – Qualdir Method............................................................................155
9 Figure 102: Handling at SMS delivery failure at the IIF ................................................................157
10 Figure 103: Handling at SMS delivery failure at the MSC/VLR Qualdir Method ............................158
11 Figure 104: Handling at SMS delivery failure at the MSC/VLR – GHOST/WEMT SMS Method....160
12 Figure 105: GSM SMS mapped to ANSI-41 Qualification Directive and to Registration
13 Notification Return Result .....................................................................................164
14 Figure 106: GPRS Attach (Option1: with timer) ...........................................................................167
15 Figure 107: GPRS Attach (Option 2: without timer)......................................................................169
16 Figure 108: GPRS Attach when currently registered in ANSI-41 (Option 1: with timer).................171
17 Figure 109: GPRS Attach when currently registered in ANSI-41 (Option 2: without timer)............173
18 Figure 112: GPRS Attach when GSM CS Attached. ....................................................................179
19 Figure 113: Combined GPRS and GSM attach (Option 1: With timer)..........................................181
20 Figure 114: Combined GPRS and GSM attach (Option 2: Without timer and without support
21 for multiple MSCIDs).............................................................................................183
22 Figure 115: Combined GPRS and GSM attach (Option 3: IIF supports multiple MSCIDs). ...........186
23 Figure 116: Combined Inter-SGSN RA/LA update.......................................................................190
24 Figure: 117: Inter-SGSN routing area update when GSM CS and GPRS Attached (MSC
25 remains constant) .................................................................................................194
26 Figure 118: Combined Attach when registered on a ANSI-41 MSC (Option 1: With timer) ...........198
27 Figure 119: Combined attach when registered on a ANSI-41 MSC (Option 2: without timer ).......201
29 Figure 120: MS in GSM Foreign Mode Performing GPRS Detach Followed by Purge..................206
30 Figure 121: IIF - Initiated Detach.................................................................................................208
31 Figure 122: Successful Mobile Terminating ANSI-41 SMS (CMT) mapped to GSM SMS............209
32 Figure 123: Successful Mobile Terminating ANSI-41 SMS (GHOST/WEMT) mapped to GSM
33 SMS .....................................................................................................................211
34 Figure 124: Unsuccessful Mobile Terminated Delivery (Failure at SGSN)....................................212
35 Figure 125: Unsuccessful Mobile Terminated Delivery (Failure at IIF)..........................................213
Post Ballot Version xvii

N.S0028
1 Figure 126: Alerting for an ANSI-41 Subscriber in GSM Foreign Mode ........................................214
2 Figure 127: Successful Mobile Originated Delivery.....................................................................215
3 Figure 128: Unsuccessful Mobile Originated Delivery (Failure at MC)..........................................216
4 Figure 129: Unsuccessful Mobile Originated (Failure at IIF).........................................................217
5 Figure 130: Indicator in ANSI-41 Registration Notification Return Result mapped to GSM
6 SMS ....................................................................................................................219
7 Figure 131: ANSI-41 Qualification Directive mapped to GSM SMS..............................................221
8 Figure 132: Handling at SMS delivery failure at the SGSN or at the MS ......................................222
9 Figure 133: Call Delivery to ANSI-41 Subscriber Roaming in GSM/GPRS Network .....................224
10 Figure 134: MS Notification of a “Missed” Call via SMS ...............................................................226
11 Figure 1: Registration on a GSM Network – GSM Foreign Mode .....................................................9
12 Figure 2: Registration in a different MSC/VLR – GSM Foreign Mode .............................................11
13 Figure 3: Registration on an ANSI-41 network – ANSI-41 Foreign Mode .......................................14
14 Figure 4: Registration in a different MSC/VLR – ANSI-41 Foreign Mode........................................16
15 Figure 5: Registration in an ANSI-41 Network (Native Mode).........................................................18
16 Figure 6: Registration in a GSM Network (Native Mode)................................................................19
17 Figure 7: Failure at the ANSI-41 HLR (GSM Foreign Mode) ..........................................................21
18 Figure 8: IIF Failure (GSM Foreign Mode).....................................................................................22
19 Figure 9: Terminating Call Flow following a GSM VLR Failure .......................................................23
20 Figure 10: Failure at a GSM HLR (ANSI-41 Foreign Mode) ...........................................................24
21 Figure 11: AUTHREQ - Successful Case ......................................................................................26
22 Figure 12: AUTHREQ - Unsuccessful Case ..................................................................................27
23 Figure 13: AFREPORT - Successful Case ....................................................................................28
24 Figure 14: AFREPORT - Unsuccessful Case ................................................................................29
25 Figure 15: ASREPORT - Successful Case ....................................................................................30
26 Figure 16: ASREPORT - Unsuccessful Case ................................................................................31
27 Figure 17: BSCHALL - Successful Case .......................................................................................32
28 Figure 18: BSCHALL - Unsuccessful Case ...................................................................................33
29 Figure 19: AUTHDIR - Successful Case........................................................................................34
30 Figure 20: AUTHDIR - Unsuccessful Case....................................................................................35
31 Figure 21: COUNTREQ - Successful Case ...................................................................................36
32 Figure 22: COUNTREQ - Unsuccessful Case ...............................................................................37
33 Figure 23: SEND_AUTH_INFO.....................................................................................................38
Post Ballot Version xviii

N.S0028
1 Figure 24: SEND_PARAMETER with Request for Authentication Set............................................39

2 Figure 25: Subscriber Deletion – ANSI-41 Foreign Mode ..............................................................40
3 Figure 26: Insert Subscriber Data Procedure.................................................................................41
4 Figure 27: Delete Subscriber Data Procedure ...............................................................................42
5 Figure 28: Cancel Location Procedure ..........................................................................................43
6 Figure 29: Subscriber Deletion- GSM Foreign Mode .....................................................................44
7 Figure 30: Subscriber Data Modification........................................................................................45
8 Figure 31: Call Delivery to ANSI-41 Subscriber Roaming in a GSM Network .................................46
9 Figure 32: Unsuccessful Call Delivery to an ANSI-136 Subscriber Roaming in a GSM
10 Network ..................................................................................................................47
11 Figure 33: Call Delivery to GSM Subscriber Roaming in an ANSI-41 Network ...............................48
12 Figure 34: Unsuccessful Call Delivery to GSM Subscriber Roaming in an ANSI-41 Network..........49
14 Figure 36: CFU deregistration (erasure) ........................................................................................52
18 Figure 40: CFB invocation (Scenario 1a, “CFB#=MSRN method”).................................................59
19 Figure 41: CFB invocation (Scenario 1b, “AbsentSubscriber method”)...........................................60
20 Figure 42: CFB invocation (Scenario 2, without OR)......................................................................61
21 Figure 43: CFNRy invocation (Scenario 1, without OR) .................................................................64
22 Figure 44: CFNRc invocation (Scenario 1) ....................................................................................67
23 Figure 45: CFNRc invocation (Scenario 2, without OR) .................................................................68
25 Figure 47: CFU deregistration (erasure) ........................................................................................71
29 Figure 51: Obtaining forward-to numbers ......................................................................................75
30 Figure 52: CFB registration ...........................................................................................................76
31 Figure 53: CFB deregistration (erasure) ........................................................................................78
32 Figure 54: CFB activation..............................................................................................................79
33 Figure 55: CFB deactivation..........................................................................................................80
Post Ballot Version xix

N.S0028
1 Figure 57: CFNA invocation (Scenario 1, without OR) ...................................................................84

2 Figure 58: Optimal Routing with Late Call Forwarding (ANSI-41 Foreign Mode) Success Case .....85
3 Figure 59: Optimal Routing with Late Call Forwarding (ANSI-41 Foreign Mode) Failure Case........88
4 Figure 60: Optimal Routing with Late Call Forwarding (GSM Foreign Mode) Success Case ..........89
5 Figure 61: Optimal Routing with Late Call Forwarding (GSM Foreign Mode) Failure Case.............91
6 Figure 62: ANSI-41 Foreign Mode Call Waiting Activation .............................................................92
7 Figure 63: ANSI-41 Foreign Mode Unsuccessful Call Waiting Activation .......................................94
8 Figure 64: GSM Foreign Mode Call Waiting Activation ..................................................................95
9 Figure 65: ANSI-41 Foreign Mode Call Waiting Deactivation .........................................................97
10 Figure 66: GSM Foreign Mode Call Waiting Deactivation ..............................................................99
12 mobile station – GSM Foreign Mode .....................................................................101
14 mobile station – ANSI-41 Foreign Mode ................................................................103
15 Figure 69: Activation of Call Restriction - GSM Foreign Mode......................................................105
16 Figure 70: Activation of Call Barring – ANSI-41 Foreign Mode.....................................................106
17 Figure 71: Invocation of Barring of Roaming – GSM Foreign Mode ............................................107
18 Figure 72: Invocation of Barring of Roaming – ANSI-41 Foreign Mode ........................................108
19 Figure 73: Invocation of Barring of Supplementary Service Control – GSM Foreign Mode ...........109
21 Mode ....................................................................................................................110
22 Figure 75: Short Message from a TDMA CMT phone to a GHOST mobile station, both in
23 native mode..........................................................................................................112
24 Figure 76: Short Message from a GHOST mobile station to a TDMA CMT Phone, both in
25 native mode..........................................................................................................113
26 Figure 77: Successful Mobile Terminating ANSI-136 SMS (CMT) mapped to GSM SMS.............114
27 Figure 78: Successful Mobile Terminating ANSI-136 SMS (GHOST) mapped to GSM SMS........115
28 Figure 79: Unsuccessful Mobile Terminated Delivery (Failure at MSC)........................................116
29 Figure 80: Unsuccessful Mobile Terminated Delivery (Failure at IIF)............................................118
30 Figure 81: Alerting for an ANSI-136 Subscriber in GSM Foreign Mode ........................................119
31 Figure 82: Successful GSM SMS mapped to ANSI-136 (CMT) SMS ...........................................120
32 Figure 83: Successful GSM SMS mapped to ANSI-136 (GHOST) SMS ......................................122
33 Figure 84: Successful GSM SMS mapped to ANSI-136 SMS (Failure at MS) ..............................123
34 Figure 85: Unsuccessful Delivery to GSM Subscriber (Postponed at MSC) .................................125
35 Figure 86: Unsuccessful Delivery to GSM Subscriber (Failure at IIF)...........................................126
Post Ballot Version xx

N.S0028
1 Figure 87: Alerting for a GSM Subscriber in ANSI-41 Foreign Mode............................................127

2 Figure 88: Successful Mobile Originated Delivery........................................................................128
3 Figure 89: Unsuccessful Mobile Originated (Failure at MC) .........................................................129
4 Figure 90: Unsuccessful Mobile Originated (Failure at IIF)...........................................................130
5 Figure 91: Successful Mobile Originated Delivery – ANSI-41 Foreign Mode ................................131
6 Figure 92: Successful Mobile Originated (Failure at SMSC) – ANSI-41 Foreign Mode .................132
7 Figure 93: Unsuccessful Mobile Originated (Failure at IIF) – ANSI-41 Foreign Mode ...................133
8 Figure 94: Indicator in ANSI-41 Registration Notification Return Result mapped to GSM SMS.....135
9 Figure 95: ANSI-41 Qualification Directive mapped to GSM SMS...............................................137
10 Figure 96: Handling when GSM MSC/VLR only supports GSM Phase 1 (MAP V1)......................138
11 Figure 97: Handling at SMS delivery failure at the IIF .................................................................139
12 Figure 98: Handling at SMS delivery failure at the MSC/VLR or at the MS..................................141
13 Figure 99: GSM SMS mapped to ANSI-41 Qualification Directive................................................143
14 Figure 100: GSM SMS mapped to TDMA using GHOST Teleservice ..........................................145
15 Figure 101: Clearing of MWN Information after Retrieval of Messages while in ANSI-41
16 Foreign mode – Qualdir Method............................................................................146
17 Figure 102: Handling at SMS delivery failure at the IIF ................................................................148
18 Figure 103: Handling at SMS delivery failure at the MSC/VLR Qualdir Method ............................149
19 Figure 104: Handling at SMS delivery failure at the MSC/VLR – GHOST SMS Method ...............150
21 Notification Return Result .....................................................................................152
22 Figure 106: GPRS Attach (Option1: with timer) ...........................................................................155
23 Figure 107: GPRS Attach (Option 2: without timer)......................................................................157
24 Figure 108: GPRS Attach when currently registered in ANSI-41 (Option 1: with timer).................159
25 Figure 109: GPRS Attach when currently registered in ANSI-41 (Option 2: without timer)............161
26 Figure 112: GPRS Attach when GSM CS Attached. ....................................................................167
27 Figure 113: Combined GPRS and GSM attach (Option 1: With timer)..........................................169
28 Figure 114: Combined GPRS and GSM attach (Option 2: Without timer and without support
29 for multiple MSCIDs).............................................................................................171
30 Figure 115: Combined GPRS and GSM attach (Option 3: IIF supports multiple MSCIDs). ...........174
31 Figure 116: Combined Inter-SGSN RA/LA update.......................................................................178
32 Figure: 117: Inter-SGSN routing area update when GSM CS and GPRS Attached (MSC
33 remains constant) .................................................................................................182
34 Figure 118: Combined Attach when registered on a ANSI-41 MSC (Option 1: With timer) ...........186
Post Ballot Version xxi

N.S0028
1 Figure 120: MS in GSM Foreign Mode Performing GPRS Detach Followed by Purge..................194
2 Figure 121: IIF - Initiated Detach.................................................................................................196
3 Figure 122: Successful Mobile Terminating ANSI-136 SMS (CMT) mapped to GSM SMS..........197
4 Figure 123: Successful Mobile Terminating ANSI-136 SMS (GHOST) mapped to GSM SMS ......199
5 Figure 124: Unsuccessful Mobile Terminated Delivery (Failure at SGSN)....................................200
6 Figure 125: Unsuccessful Mobile Terminated Delivery (Failure at IIF)..........................................201
7 Figure 126: Alerting for an ANSI-136 Subscriber in GSM Foreign Mode ......................................202
8 Figure 127: Successful Mobile Originated Delivery.....................................................................203
9 Figure 128: Unsuccessful Mobile Originated Delivery (Failure at MC)..........................................204
10 Figure 129: Unsuccessful Mobile Originated (Failure at IIF).........................................................205
11 Figure 130: Indicator in ANSI-41 Registration Notification Return Result mapped to GSM
12 SMS ....................................................................................................................207
13 Figure 131: ANSI-41 Qualification Directive mapped to GSM SMS..............................................209
14 Figure 132: Handling at SMS delivery failure at the SGSN or at the MS ......................................210
15 Figure 133: Call Delivery to ANSI-136 Subscriber Roaming in GSM/GPRS Network ...................212
16 Figure 134: MS Notification of a “Missed” Call via SMS ...............................................................214
17
18
Post Ballot Version xxii

N.S0028
1 Foreword
3 This standard addresses the interworking and interoperability between TIA/EIA IS41 MAP and GSM
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
13 ANSI-136, GSM, and AMPS networks.
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.
21 required to support other air interfaces supported by ANSI-41 MAP (e.g., IS-95, CDMA2000). This
22 may be accomplished in future release of this standard.
23 Existing ANSI-41 and GSM standard specifications cover the use and value of timers controlling the
24 various operations. Therefore, these timers are not part of this standard. However, care should be
25 taken when allocating actual timer values in order to support interoperability between ANSI-41 MAP
26 and GSM MAP.
27 Aspects of TIA/EIA-136 Rev C have been incorporated into this standard.
28 Revision A adds GPRS service capability in GSM Foreign Mode.
29
30 Revision B adds two way roaming between GSM and CDMA systems
31 Information disclosed in this document is subject to the export jurisdiction of the US Department of Commerce
32 as specified in Export Administration Regulations (title 15 CFR parts 730 through 774 inclusive). The
33 information contained herein may not be exported or re-exported to Cuba, Iran, Iraq, Libya, North Korea,
34 Sudan, or Syria. Contact the Telecommunications Industry Association, Arlington, VA or
35 http://ftp.tiaonline.org/tr-45/tr45ahag/public%20documents.
Post Ballot Version xxiii

N.S0028
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 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 Optionally, IIF may support one way-roaming only from CDMA to GSM network. In this case since no
15 data is provisioned at IIF level, IIF must generate the GSM triplets using as input the authentication
16 parameters returned by ANSI-41 HLR/AC. and ANSI-41 HLR/AC must be compliant with PN-4925 (to
17 be published as TIA/EIA-868 [28]. All the changes are made on the assumption the new requirements
18 for UIM/handsets are working. (Annex B)
19 1.2 Purpose
20 The purpose for this standard is to define and describe the functions necessary for roaming between
21 ANSI-41 MAP [1] and GSM MAP [6] 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-136 41,
23 TDMA or CDMA native subscriber) with a mobile terminal supporting GPRS service to roam to a
24 GPRS network in GSM Foreign Mode.
25 1.3 Scope
26 The scope of this standard are the services, information flows and message mappings which require
27 interworking and interoperability functional specifications to support roaming between ANSI-41 MAP
28 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.
31 1.4 Organization
33 Volume 0 – Overview and Interworking Reference Model
34 Volume 1 – Service Descriptions
35 Volume 2 – Information Flows
36 Volume 3 – Message Mappings
37 This volume is organized according to the following:
38 2 References - a list of references specific to this volume of the Standard.
Post Ballot Version 1

N.S0028
1 3 Definitions and Acronyms - defines words and acronyms that are specific to this volume.
2 4 Information flows - Message Flows and functionality of the interoperable network features.
3

N.S0028
1 2 References
2 [1] TIA/EIA IS-41-D: “Cellular Radiotelecommunications Intersystem Operations,” December
3 1997, ANSI.
4 [2] TIA/EIA/IS-751: “TIA/EIA-41-D Modifications to support IMSI”, PN-3892 version 7.
5 [3] TIA/EIA/IS-807: “TIA/EIA-41-D Enhancements for Internationalization”
6 [4] TS 100 901 v 6.1.0 (1998-07); “Digital cellular telecommunications system (Phase 2+);
7 Technical realization of the Short Message Service (SMS); Point-to-Point (PP),” (GSM 03.40
8 version 6.1.0 Release 1997)
9 [5] TS 100 542 v 7.0.1 (1999-07); "Digital cellular telecommunications system (Phase 2+); Line
10 identification supplementary services;Stage2 (GSM 03.81 version 7.0.1 Release 1998).
11 [6] TS 100 974 v 6.2.0 (1998-11): “Digital cellular telecommunication system (Phase 2+); Mobile
12 Application Part (MAP) specification,” (GSM 09.02 version 6.2.0 Release 1997).
13 [7] TS 100 974 v 7.1.0 (1999-08): “Digital cellular telecommunication system (Phase 2+); Mobile
14 Application Part (MAP) specification,” (GSM 09.02 version 7.1.0 Release 1998).
15 [8] TS 101 629 v 6.0.0 (1999-04): "Digital cellular telecommunication system (Phase 2+);
16 Support of Optimal Routeing (SOR); Service definition (Stage 1)". (GSM 02.79 v 6.0.0
17 Release 1997)
18 [9] TS 101 045 v 6.2.0 (1999-11): "Digital cellular telecommunication system (Phase 2+);
19 Support of Optimal Routeing (SOR); Technical realisation" (GSM 03.79 v 6.2.0 Release
20 1997).
21 [10] Draft ETSI EN 301 344: “Digital cellular telecommunication system (Phase 2+); General
22 Packet Radio Service; Service description (Stage 2)" (GSM 03.60 v 6.8.0 Release 1997).

29
30 [15] "TIA/EIA-IS-2000-A, cdma2000 Series, March 2000, plus addenda"Mobile Station-Base Station
31 Compatibility Standard for Dual-Mode Spread Spectrum Systems;
33 GSM, Published TBD. [12]"Enhanced Cryptographic Algorithms, Revision B," TR45AHAG, Published TBD
34
35

N.S0028

N.S0028

2 3.1 Definitions
3 AMPS
4 Advanced Mobile Phone Service (AMPS) is the same as EIA/TIA-553, which as an analog air
5 interface protocol standard for mobile stations and their associated base stations. AMPS networks
6 use ANSI-41 for intersystem signaling.
7 ANSI-41
8 ANSI-41 is the same as TIA/EIA IS-41 with the modifications and enhancements contained in IS751
9 [2] and IS 807 [3] . ANSI-41 is the North American version of ITU defined MAP. Key intersystem
10 support defined by ANSI-41 includes automatic roaming, intersystem handoff, and intersystem
11 operation, administration, and maintenance. Among other things, ANSI-41 defines the interfaces
12 between MSCs, between the MSC/VLR and the HLR/AC, and between the MSC and the Short
13 Message Service Center (SMS-C) or Teleservice Server (TS).
14 ANSI-136
15 ANSI-136 is the same as TIA/EIA-136, which is a TDMA air interface protocol standard for mobile
16 stations and their associated base stations. ANSI-136 is a dual-mode standard that includes digital
17 (TDMA) operation at 800 MHz and 1900 MHz, and analog (AMPS) operation at 800 MHz. ANSI-136
19 ANSI-136 Mode
20 ANSI-136 mode indicates the condition or state of a mobile station accessing an ANSI-136 network.
25 ANSI-136 native mode indicates the condition or state of an ANSI-136 native subscriber accessing an
28 ANSI-136 native subscriber indicates an end user whose primary or home subscription resides in an
29 ANSI-136 network. These subscribers include both home subscribers from the ANSI-136 network, as
30 well as roamers from other ANSI-136 networks.
34 ANSI-41 Subscriber
35 ANSI-41 subscriber indicates an end user whose primary or home subscription resides in an ANSI-41
36 based network. These subscribers include both home subscribers from ANSI-41 based networks as
37 well as roamers from other ANSI-41 based networks.
38 CDMA

N.S0028
1 CDMA as used in this document, refers to TIA/EIA -95 [9] or TIA/EIA-2000 [10], which is a CDMA
5 B.1.1.1.1.1 CDMA Mode
7
8 CDMA Foreign Mode
9 CDMA foreign mode indicates the condition or state of a GSM native subscriber accessing a CDMA
10 network.
11
12 CDMA Native Mode
14 CDMA network.
15
18 CDMA network. These subscribers include both home subscribers from the CDMA network, as well
19 as roamers from other CDMA networks.
20
21 Class A mobile
22 Class A mobile station is a GSM mobile that can operate in Class A mode: both GSM circuit-switched
23 and GPRS packet services simultaneously.
24
25 Class B mobile
26 Class B mobile station is a GAIT or GSM mobile that operates in Class B mode: can operate
27 alternatively GSM circuit-switched or GPRS packet services (1 type service at a time). The mobile
28 can be attached to GSM and GPRS networks simultaneously in this case. The subscriber cannot be
29 simultaneously attached to an ANSI-41 MSC.
30
31 Class C mobile
32 Class C mobile station is a GSM mobile that can only operate in Class C mode: GSM circuit-switched
33 only or GPRS packet services only. The mobile is attached to only one network at a time.
34
35 GSM
36 Global System for Mobile Communications (GSM) defines both air interface and network intersystem
37 protocol standards for mobile stations (MS), base station systems (BSS), and network switching
38 systems (NSS).
39 GSM CS attached
40 GSM circuit-switched services attached means that the subscriber is attached to a GSM MSC. This is
41 also referred to as IMSI attached
42 GSM CS detached
43 GSM circuit-switched services detached means that the subscriber is detached from a GSM MSC.
44 This is also referred to as IMSI detached.
45
46 GSM Mode

N.S0028
1 GSM Foreign Mode

2 GSM foreign mode indicates the condition or state of an ANSI-136 41 native subscriber accessing a
3 GSM network.
4 GPRS HLR
5 General Packet Radio Service Home Location Register is the HLR responsible for GPRS functions. It
6 interfaces with the SGSN and GGSN and Authentication Center.
7
9 GPRS in GSM Foreign Mode is a subset of GSM Foreign Mode and indicates the condition or state of
10 an ANSI-136 41 native subscriber accessing a GPRS network; the GPRS network may be coupled
11 with a GSM network.
12
13 GSM Native Mode
15 network.
16

N.S0028

2 GSM native subscriber indicates an end user whose primary or home subscription resides in a GSM
3 network. These subscribers include both home subscribers from the GSM network, as well as
4 roamers from other GSM networks.
5 Mobile Station
9 A smart card that plugs into the mobile equipment and that contains the authentication algorithms,
10 and stores service-oriented subscription information.
11
12

N.S0028
1 3.2 Acronyms
2 AC Authentication Center in TIA/EIA-41 based networks
3 ADN Abbreviated Dialing Numbers
11 BOIC-exHC Baring of Outgoing International Calls Except to HPLMN Country
17 CFU Call Forwarding Unconditional
18 CPHS Common PCN Handset Specification
19 DCS Data Coding Scheme
23 EUI ESN Usage Indicator
24 FC Feature Code
25 FDN Fixed Dialing Numbers
26 FSM Forward Short Message
28 GHOST GSM Hosted SMS Teleservice
32 HLPI Higher Layer Protocol Indicator

N.S0028

4 IMEI International Mobile Equipment Identifier
6 Interim OAA Interim Over-the-Air Activation
7 IRDB Intelligent Roaming Database
10 MC ANSI-136 41 Message Center (for SMS)
11 MDN Mobile Directory Number
15 MS Mobile Station
17 MSCIN MSC Identification Number
20 MSRN Mobile Station Routing Number
23 NAM Numeric Assignment Module
24 NSDB Network Selection Database
26 OTA Over-the-Air Activation
27 PCS Personal Communications Service
28 PDU Packet Data Unit
31 PRN Provide Roaming Number
32 PSAP Public Safety Access Point

N.S0028
1 SESN SIM Electronic Serial Number

5 SMDPP Short Message Delivery Point-to-Point
8 SOC System Operator Code
11 TP-FCS TP Failure Cause
13 TLDN Temporary Location Directory Number
14 TMSI Temporary Mobile Station Identity
15 TS Teleservice Server
16 TSAR Teleservice Segmentation and Reassembly
17 UWCC Universal Wireless Communications Consortium
18 UDH Universal Data Header
21 WAP Wireless Application Protocol
22 WEMT Wireless Enhanced Messaging Teleservices
23
24

N.S0028
1 4 Stage 2 Information Flows

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

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

MS IIF
VLR VLR
Update Location Req
(IMSI) a
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
10 Figure 1: Registration on a GSM Network – GSM Foreign Mode
11

N.S0028
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 authentication
4 i.e. authentication triplets, it requests authentication information from the IIF. The IIF emulates
5 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 VLR
13 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 shall
16 be passed in the REGNOT to the subscriber’s HLR. This ESN may not match the currently
17 validated dynamic ESN for this subscriber, but the HLR shall also accept this fixed ESN for
18 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 Procedure
24 towards the serving VLR. This procedure is used to download subscriber data to the serving
25 VLR. Multiple Insert Subscriber Data transactions may be necessary to complete the transfer
26 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.
30

N.S0028
1 B.1.1.3 4.1.1.2 MS location updates in a different MSC/VLR
2 When an ANSI-136 41 subscriber roams within a GSM PLMN and registers in a different MSC/VLR
3 area, 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
4
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 sends
7 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

N.S0028
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
15 validated dynamic ESN for this subscriber, but the HLR shall also accept this fixed ESN for this
16 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. This
21 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
27 m. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the IIF
28 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 [6]. The IIF however, is not informed.
33 B.1.1.4 4.1.1.3 IMSI Detach
34 If a 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 [6]. Neither the IIF or the home
36 HLR is informed.
37 Terminating calls intended for this ANSI-136 41 subscriber, shall therefore be treated in the home
38 HLR 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 this
41 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 [1]. (Terminating calls intended for this ANSI-136 41
43 subscriber, shall therefore be treated in the home HLR as if that subscriber was not available).
44

N.S0028
1 B.1.1.5 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 record)
3 while operating in GSM Foreign mode and the IMSI Attach procedure is supported, it shall perform an
4 IMSI Attach as described in GSM 09.02 [6]. 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 an
7 IMSI Attach as described in GSM 09.02 [6]. The IIF shall be informed as shown in Section 4.1.1.2.
8 (however the IIF shall not send a Cancel Location to the MSC/VLR as it is the same MSC/VLR).
9 If an MS powers on and registers on a different MSC/VLR, while operating in GSM Foreign mode and
10 the IMSI Attach procedure is supported, it shall perform an IMSI Attach as described in GSM 09.02
11 [6]. The IIF shall be informed as shown in Section 4.1.1.2.
12

N.S0028
1 4.1.2 Location Registration in ANSI-41 Foreign Mode

2 B.1.1.6 4.1.2.1 MS registers in an ANSI-41 network when previously registered in a
3 GSM network
4 When a GSM subscriber registers in an ANSI-41 network, when previously registered in a GSM
5 network, the MS performs a location update using an IMSI or MIN as shown in Figure 3. The IIF
6 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
8 Figure 3: Registration on an ANSI-41 network – ANSI-41 Foreign Mode
9
10 a. Upon MS power up, if global authentication is active, the MS first sends an Authentication
11 message to the network. The MS then sends a Registration message (which includes the IMSI
12 or MIN) to the network.
13
14 b. If global authentication is active upon registration, the serving VLR initiates an AUTHREQ
15 towards the IIF. The IIF emulates an ANSI-41 HLR/AC in this case.
16
17 The reported ESN for this subscriber shall be dynamic to support SIM-based roaming. The IIF
18 shall authenticate the subscriber using this reported ESN.
19

N.S0028
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 in
4 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 procedure
16 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.
24

N.S0028
1 B.1.1.7 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
4
5 Figure 4: Registration in a different MSC/VLR – ANSI-41 Foreign Mode
6
7 a. MS powers up and registers in a new MSC/VLR in the same ANSI-41 network. If global
8 authentication is active, the MS sends an Authentication message to the network. The MS also
9 sends a Registration message (which includes the IMSI / MIN) to the network.
10
11 b. If global authentication is active upon registration, the serving VLR initiates an AUTHREQ
12 towards the IIF. The IIF emulates an ANSI-41 HLR/AC in this case.
13
14 The reported ESN for this subscriber shall be dynamic to support SIM-based roaming. The IIF
16
17 c. The IIF acknowledges the authentication request. If authentication is successful, the IIF shall
18 store the reported ESN as the currently validated dynamic ESN for this subscriber.
19

N.S0028
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 B.1.1.8 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. If
23 the MS remains inactive for an extended period of time (determined by operator), the IIF may delete
24 the subscriber record associated with that MS and send an MS Purge to the HLR.
25 B.1.1.9 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.
28 4.1.3 Location Registration in Native Mode

29 B.1.1.10 4.1.3.1 MS registers in an ANSI-41 network when previously registered in a
30 GSM network
31 When an ANSI subscriber registers in an ANSI-41 network (Native Mode), when previously registered
32 in a GSM Network (Foreign Mode), the MS performs a location update and the temporary subscriber
33 data in the IIF is deleted as shown in figure 5.

N.S0028
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
1 Figure 5: Registration in an ANSI-41 Network (Native Mode)

2
3 a. MS powers up and registers in a new MSC/VLR in an ANSI-41 network.
4 If global authentication is active upon registration, the serving VLR initiates an AUTHREQ
5 towards the ANSI-41 HLR.
6 The reported ESN for this subscriber shall be dynamic to support SIM-based roaming. The HLR
8
9 c. The HLR acknowledges the authentication request. If authentication is successful, the HLR shall
10 store the reported ESN as the currently validated dynamic ESN for this subscriber.
11
12 d. The serving VLR sends a REGNOT to the HLR.
13
14 e. The HLR sends a REGCANC to the IIF.
15
16 f. The IIF deletes the temporary subscriber data and sends a Cancel Location to the previous VLR
17 in the GSM network.
18
19 g. The previous VLR deletes the relevant subscriber data and acknowledges the request.
20
21 h. The IIF acknowledges the REGCANC.
22
23 i. HLR updates the new serving VLR.
24
25 j. The VLR acknowledges the update towards the MS.

N.S0028
1 B.1.1.11 4.1.3.2 MS registers in a GSM network when previously registered in an ANSI-

2 41 network
3 When a GSM subscriber registers in a GSM network (Native Mode), when previously registered in an
4 ANSI-41 Network (Foreign Mode), the MS performs a location update and the temporary subscriber
5 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
6 Figure 6: Registration in a GSM Network (Native Mode)

7
8 a. MS powers up and registers in a new MSC/VLR in a GSM network.
9
10 b. The serving VLR sends an Update Location Request to the HLR.
11
12 c. The HLR sends a Cancel Location to the IIF.
13
14 d. The IIF deletes the temporary subscriber data and sends a REGCANC to the previous VLR in the
15 ANSI-41 network.
16
17 e. The Previous VLR deletes the relevant subscriber data and acknowledges the request.
18
19 f. The IIF acknowledges the Cancel Location Request.
20

N.S0028
1 g. HLR updates the new serving VLR.

2
3 h. The VLR acknowledges the update.
4
5 i. The HLR acknowledges the Update Location Request.
6
7 j. The VLR acknowledges the Update Location Request towards the MS.
8

N.S0028
1 4.2 Fault Recovery Procedures

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

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

19
20 a. HLR returns to stable state following a failure and sends an UNRELDIR towards the IIF.
21
22 b. The IIF acknowledges the request and removes all the temporary subscriber data of all the MSs
23 associated with that HLR from its memory.
24
25 c. The IIF may reload its data from a non-volatile backup (optional) and shall send a RESET
26 towards each of the serving VLRs. The RESET message contains a unique identity, identifying
27 the ANSI-41 HLR that failed and that is connected to the IIF.
28
29 When the MS next establishes authenticated radio contact (including a mobile originated call
30 attempt), the VLR initiates location updating towards the IIF (See 4.1.1).

N.S0028
1 B.1.1.13 4.2.1.2 Recovery from Failure at the IIF
2 If the IIF suffers a failure, it shall follow the recovery procedure described in GSM 09.02 [6] section
3 19.3.2 (i.e. IIF is acting like a GSM HLR). As part of the recovery procedure, the IIF shall send all the
4 serving GSM VLRs a RESET message for each associated ANSI-41 HLR as shown in step a) in
5 Figure 8. The message shall contain a unique identifier for the ANSI-41 HLR. In addition, the IIF shall
6 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
7 Figure 8: IIF Failure (GSM Foreign Mode)

8 a. The IIF sends a RESET towards each of the affected VLRs, containing a unique identity,
9 identifying the ANSI-41 HLRs connected to the IIF.
10
11 b. The IIF sends a BULKDEREG towards all the affected ANSI-41 HLRs. On reception of the
12 BULKDEREG the HLR(s) follow(s) the procedures as described in ANSI-41.6D [1].
13
14 c. The ANSI-41 HLR(s) responds with a bulkdereg.
15
17 attempt), the VLR initiates location updating towards the IIF (See 4.1.1).
18
19
20

N.S0028
1 B.1.1.14 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 [6] 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 request
14 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.
19

N.S0028
1 4.2.2 Fault Recovery Procedures in ANSI-41 Foreign Mode

2 B.1.1.15 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 [6]
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 [6] 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 [6] 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 [1] and ANSI-41.6 [1] and acknowledges
19 the UNRELDIR.
20
22 attempt), the VLR initiates location updating towards the IIF (See 4.1.2.1).
23
24

N.S0028
1 B.1.1.16 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 [1] (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 B.1.1.17 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 [1].
12 As part of the recovery procedure, when an MS next establishes authenticated radio contact, the VLR
13 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.
18

N.S0028
1 4.3 Authentication
2 4.3.1 ANSI-41 Foreign Mode Authentication Activation
3 B.1.1.18 4.3.1.1 Receiving AUTHREQ Message
4 B.1.1.18.1 4.3.1.1.1 Successful AUTHREQ Response Received from ANSI-41 AC
ANSI-41
Serving
System
ANSI-41
MSC/VLR IIF
AC
AUTHREQ
a
AUTHREQ
b
authreq
c
authreq
d
6
7 Figure 11: AUTHREQ - Successful Case
8 a,b,c,d The IIF is emulating an ANSI-41 HLR. For successful processing, see to ANSI-41 [1].

N.S0028
1 B.1.1.18.2 4.3.1.1.2 AUTHREQ Failure Reported by IIF
ANSI-41
Serving
System
ANSI-41
MSC/VLR IIF
AC
AUTHREQ
a
AUTHREQ
b
authreq
c
(error handling)
authreq
d
(error handling)
3
4 Figure 12: AUTHREQ - Unsuccessful Case
5
6 a,b,c,d The IIF is emulating an ANSI-41 HLR. For error handling see to ANSI-41 [1].

N.S0028
1 B.1.1.19 4.3.1.2 Receiving AFREPORT Message
2 B.1.1.19.1 4.3.1.2.1 Successful AFREPORT Response Received from ANSI-41 AC
ANSI-41
Serving
System
ANSI-41
MSC/VLR IIF
AC
AFREPORT
a
AFREPORT
b
afreport
c
afreport
d
4
5 Figure 13: AFREPORT - Successful Case
6
8
9

N.S0028
1 B.1.1.19.2 4.3.1.2.2 AFREPORT failure reported by IIF
ANSI-41
Serving
System
ANSI-41
MSC/VLR IIF
AC
AFREPORT
a
AFREPORT
b
afreport
c
(error handling)
afreport
d
(error handling)
3
4 Figure 14: AFREPORT - Unsuccessful Case
5
6 a,b,c,d The IIF is emulating an ANSI-41 HLR. For error handling see to ANSI-41.D [1].

N.S0028
1 B.1.1.20 4.3.1.3 Receiving ASREPORT Message
2 B.1.1.20.1 4.3.1.3.1 Successful ASREPORT Response Received from ANSI-41 AC
ANSI-41
Serving
System
ANSI-41
MSC/VLR IIF
AC
ASREPORT
a
ASREPORT
b
asreport
c
asreport
d
4
5 Figure 15: ASREPORT - Successful Case
6

N.S0028
1 B.1.1.20.2 4.3.1.3.2 ASREPORT Failure Reported by IIF
ANSI-41
Serving
System
ANSI-41
MSC/VLR IIF
AC
ASREPORT
a
ASREPORT
b
asreport
c
(error handling)
asreport
d
(error handling)
3
4 Figure 16: ASREPORT - Unsuccessful Case
5

N.S0028
1 B.1.1.21 4.3.1.4 Receiving BSCHALL Message
2 B.1.1.21.1 4.3.1.4.1 Successful BSCHALL Response Received from ANSI-41 AC
ANSI-41
Serving
System
ANSI-41
MSC/VLR IIF
AC
BSCHALL
a
BSCHALL
b
bschall
c
bschall
d
4
5 Figure 17: BSCHALL - Successful Case
6

N.S0028
1 B.1.1.21.2 4.3.1.4.2 BSCHALL Failure Reported by IIF
ANSI-41
Serving
System
ANSI-41
MSC/VLR IIF
AC
BSCHALL
a
BSCHALL
b
bschall
c
(error handling)
bschall
d
(error handling)
3
4 Figure 18: BSCHALL - Unsuccessful Case
5

N.S0028
1 B.1.1.22 4.3.1.5 Receiving AUTHDIR Message
2 B.1.1.22.1 4.3.1.5.1 Successful AUTHDIR Response Received from Serving System
ANSI-41
Serving
System
ANSI-41
MSC/VLR IIF
AC
AUTHDIR
a
AUTHDIR
b
authdir
c
authdir
d
4
5 Figure 19: AUTHDIR - Successful Case
6

N.S0028
1 B.1.1.22.2 4.3.1.5.2 AUTHDIR failure Received from Serving System
ANSI-41
Serving
System
ANSI-41
MSC/VLR IIF
AC
AUTHDIR
a
AUTHDIR
b
authdir
c
(error handling)
authdir
d
(error handling)
3
4 Figure 20: AUTHDIR - Unsuccessful Case
5

N.S0028
1 B.1.1.23 4.3.1.6 Receiving COUNTREQ Message
2 B.1.1.23.1 4.3.1.6.1 Successful COUNTREQ Response Received from Serving System
ANSI-41
Serving
System
ANSI-41
MSC/VLR IIF
AC
COUNTREQ
a
COUNTREQ
b
countreq
c
countreq
d
4
5 Figure 21: COUNTREQ - Successful Case
6

N.S0028
1 B.1.1.23.2 4.3.1.6.2 COUNTREQ Failure Received from Serving System
2
ANSI-41
Serving
System
ANSI-41
MSC/VLR IIF
AC
COUNTREQ
a
COUNTREQ
b
countreq
c
(error handling)
countreq
d
(error handling)
3
4 Figure 22: COUNTREQ - Unsuccessful Case
5

N.S0028
1 B.1.2 4.3.2 GSM Foreign Mode Authentication Activation

2 B.1.2.1 4.3.2.1 Authentication Related Messages
3 B.1.2.1.1 4.3.2.1.1 Receiving SEND_AUTHENTICATION_INFO (Version 2 MAP)

4
GSM
Serving
System
GSM
IIF MSC/VLR
AuC
SEND_AUTH_INFO
a
SEND_AUTH_INFO
b
send_auth_info
c
send_auth_info
d
5
6 Figure 23: SEND_AUTH_INFO
7
8 a,b,c,d The IIF is emulating a GSM HLR. For successful processing, see to GSM 09.02 [6].

N.S0028
1 B.1.2.1.2 4.3.2.1.2 Receiving SEND_PARAMETER (Version 1 MAP)
GSM
Serving
System
GSM
IIF MSC/VLR
AuC
SEND_PARAMETER
a
SEND_PARAMETER
b
send_parameter
c
send_parameter
d
3
4 Figure 24: SEND_PARAMETER with Request for Authentication Set
5
6 a,b,c,d The IIF is emulating a GSM HLR. For successful processing, see to GSM 09.02 [6].

N.S0028
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 [6]. 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 subscriber
6 data in the IIF is addressed. The procedures are (1) Subscriber Deletion and (2) Subscriber Data
7 Modification.
8 B.1.2.2 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.

N.S0028
1 e. The IIF acknowledges the cancel location request.
2 f. The HLR acknowledges the delete subscriber request.

3
4 B.1.2.3 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 the
8 IIF. These procedures are described in more detail in GSM 09.02 [6].
9 B.1.2.3.1 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-136 41 subscriber profile modification. In this case, no QualDir operation shall
19 be initiated.
20 d. The serving MSC/VLR modifies the subscriber data and acknowledges the QUALDIR

N.S0028
1 e. The IIF acknowledges the Insert Subscriber Data Request.
2 f. The HLR acknowledges the request to modify subscriber data.

3
4 B.1.2.3.2 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
7
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 mapped
14 to an associated ANSI-136 41 subscriber 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 QUALDIR.
17 e. The IIF acknowledges the Delete Subscriber Data Request.

N.S0028
1 B.1.2.3.3 4.4.1.2.3 Cancel Location Procedure
2 If roaming modifications are required, which require the subscriber to be removed from the VLR data,
3 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
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.

14

N.S0028
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-136 41 subscribers HLR, the IIF and the serving VLR when the subscriber is
4 operating in GSM Foreign Mode. For these procedures, only modification to temporary subscriber
5 data in the IIF is addressed.
6 B.1.2.4 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.
MSC/ HLR OMC

IIF
VLR
Sub Data Delete
REGCANC
b
Cancel Location
Cancel Location Ack
regc anc
e
Sub Data Delete Ack

f
NSI-41 NETWO RK
GSM NETWORK
10 Figure 29: Subscriber Deletion- GSM Foreign Mode

11 a. OMC initiates a request to delete a subscriber
12 b. The HLR deletes the subscriber data from the HLR and sends a REGCANC to the IIF.
13 c. The IIF deletes the temporary subscriber data from the IIF and sends a Cancel Location to the
14 serving VLR.
15 d. The VLR acknowledges the cancel location
16 e. The IIF acknowledges the REGCANC
17 f. The HLR acknowledges the request to delete subscriber data.
18

N.S0028
1 B.1.2.5 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
QUALDIR
b
Insert Sub Data
Insert Sub Data Ack
qualdir
e
Sub Dat a Change Ack

f
NSI-41 NETWO RK
GSM NETWORK
5 Figure 30: Subscriber Data Modification

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

N.S0028
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-136 41 subscriber 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 B.1.2.6 4.5.2.1 Call Delivery to ANSI-136 41 Subscriber Roaming in GSM Network
Serving System
MSC/ GSM
VLR IIF MSC/
HLR
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 an
23 MSRN.

N.S0028
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 is
3 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 indication
7 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).
11 B.1.2.7 4.5.2.2 Delivery to an ANSI-136 41 Subscriber Roaming in a GSM Network –

12 Unsuccessful Case
13 In the following scenario, call delivery to an ANSI-136 41 subscriber roaming in a GSM network fails
14 during the processing of the Provide Roaming Number message (e.g., no roaming number is
15 available, absent subscriber).
Serving System
MSC/ GSM
VLR IIF MSC/
HLR
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
16
17 Figure 32: Unsuccessful Call Delivery to an ANSI-136 41 Subscriber Roaming in a GSM
18 Network
20 Originating ANSI-41 MSC from the PSTN destined to a subscriber to the ANSI-41 network.
21 b. The Originating ANSI-41 MSC sends a LOCREQ message to the ANSI-41 HLR associated with
22 the called subscriber; this association is made through the dialed MS address digits.
23 c. The ANSI-41 HLR sends a ROUTREQ message to the IIF emulating the VLR where the MS is
24 registered. If necessary, mapping from IMSI to MIN is done beforehand by the IIF.
25 d. The IIF forwards a Provide Roaming Number message to the GSM VLR/MSC where the MS is
26 registered.
27 e. The GSM VLR/MSC determines that either no roaming numbers are available or subscriber is not
28 reachable and it replies with a PRN Return Error message.

N.S0028
1 f. The IIF sends a RoutingRequest RETURN ERROR message.

2 g. The ANSI-41 HLR sends a LocationRequest RETURN ERROR message.
3 B.1.2.8 4.5.2.3 Call Delivery to a GSM Subscriber Roaming in ANSI-41 Network –

4 Successful Case
Serving System
GSM GSM
MSC/ IIF MSC/
HLR VLR
Incoming Call VLR
From PSTN
a
Send Routing Info
b
Provide Roaming No. c
ROUTREQ
d
routreq
e
PRN Ack f
SRI Ack
g
Call setup
h
5
6 Figure 33: Call Delivery to GSM Subscriber Roaming in an ANSI-41 Network
8 Originating MSC from the PSTN destined to a subscriber to the GSM network.
9 b. The Gateway GSM MSC sends a Send Routing Information message to the GSM HLR
10 associated with the called subscriber; this association is made through the dialed MS address
11 digits.
12 c. The GSM HLR sends a Provide Roaming Number message to the IIF emulating the VLR where
13 the MS is registered. If necessary, mapping from IMSI to MIN is done beforehand by the IIF.
14 d. The IIF forwards a ROUTREQ message to the VLR/MSC where the MS is registered.
15 e. The serving VLR/ MSC returns a routreq message that includes a TLDN to the IIF.
16 f. The IIF returns a Provide Roaming Number Ack message that includes an MSRN (set to the
17 received TLDN) to the GSM HLR. If the TLDN is not received in international format, the IIF shall
18 first convert the TLDN to international format (by prepending the country code associated with the
19 serving system) before setting the MSRN equal to it.
20 g. When the Provide Roaming Number Ack is received by the GSM HLR, it returns a Send Routing
21 Information Ack message to the Gateway GSM MSC.
22 h. Upon receiving the Send Routing Information Ack message, the Gateway GSM MSC sets up a
23 voice path to the Serving MSC (using a protocol such as SS7 ISUP).

N.S0028
1 B.1.2.9 4.5.2.4 Call Delivery to a GSM Subscriber Roaming in ANSI-41 Network –

2 Unsuccessful Case
3 In the following scenario, call delivery to a GSM subscriber roaming in an ANSI-41 network fails
4 because the user is either ‘not reachable’ as determined by the IIF or does not answer a page sent by
5 the serving system during the processing of the RouteRequest message, and call forwarding is not
6 active for the subscriber.
Serving System
GSM GSM
MSC/ IIF MSC/
HLR VLR
Incoming Call VLR
From PSTN
a
Send Routing Info
b
Provide Roaming No. c
ROUTREQ
d
routreq[ACCDEN]
e
PRN Ret Error f

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

N.S0028
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 B.1.2.10 4.6.1.1 Call forwarding unconditional (CFU)
6 The following scenarios illustrate the call forwarding unconditional (CFU) information flows applicable
7 to ANSI-41 foreign mode operation.
8 B.1.2.10.1 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-136
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

N.S0028
1 a. The ANSI-41 serving system receives dialed digits from the subscriber’s mobile station (MS). The
2 serving system detects a “*” character as the first dialed digit. This indicates that the dialed digits
3 are a feature code string.1
4
5 b. The serving system sends a FEATREQ message to the IIF, including the digits received from the
6 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 is
24 too large for a single ISD message, then multiple ISD exchanges may be executed between the
25 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 change
30 in the value of the subscriber’s ANSI-41 profile, the IIF includes the revised ANSI-41 profile data
31 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
35 B.1.2.10.2 4.6.1.1.2 CFU deregistration (erasure)
36 This scenario illustrates the CFU deregistration information flows applicable to ANSI-41 foreign mode
37 operation.
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).

N.S0028
GSM ANSI-136
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
1
2 Figure 36: CFU deregistration (erasure)
5 are a feature code string.
6
8 subscriber.
9
10 c. The IIF parses the received digit string. In this case, the subscriber has requested to erase a call
11 forwarding number. The IIF sends an ERASE_SS message to the GSM HLR.
12
13 d. The HLR processes the request and returns an erase_ss message to the IIF, indicating operation
14 success.
15
16
18 request.
19
21
23 message to the IIF, containing the new or modified profile data (e.g., the new ss-status value).
24
25

N.S0028
4
6
10
12

N.S0028
1
2 B.1.2.10.3 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-136
IIF
HLR VMSC MS
2
GSM ANSI-41
feature code digits

a
FEATREQ [digits]
b
ACT_SS
c
act_ss
d
featreq [success]
e
f
ISD
g
isd
h
[TCAP End]
i
QUALDIR
j
qualdir
k
5
6 Figure 37: CFU activation
10
12 subscriber.
13
14 c. The IIF parses the received digit string. In this case, the subscriber has requested to activate call
15 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
24

N.S0028
3
7
9
13
15
16

N.S0028
1 B.1.2.10.4 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-136
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 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

N.S0028
3
7
9
13
15
16 B.1.2.10.5 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 B.1.2.10.6 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-136
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 HLR
29 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.
32

N.S0028
1 B.1.2.11 4.6.1.2 Call forwarding busy (CFB)

2
3 The following scenarios illustrate the call forwarding busy (CFB) information flows applicable to ANSI-
4 41 foreign mode operation.
5 B.1.2.11.1 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 B.1.2.11.2 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 B.1.2.11.3 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 operation,
13 since they are the same as those for CFU.
14 B.1.2.11.4 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 B.1.2.11.5 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.
20 B.1.2.11.6 4.6.1.2.6 CFB invocation
21 The following scenarios illustrate the CFB invocation information flows applicable to ANSI-41 foreign
22 mode operation.
23 B.1.2.11.6.1 4.6.1.2.6.1 CFB invocation (Scenario 1a, “CFB#=MSRN method”)
24 In this scenario, the busy condition is detected by the ANSI-41 serving system when the
25 RoutingRequest Invoke message is received, and the IIF returns the CFB forward-to number (i.e., as
26 the MSRN) to the GSM HLR in the ProvideRoamingNumber Return Result message.

N.S0028
GSM GSM ANSI-136

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
1
2 Figure 40: CFB invocation (Scenario 1a, “CFB#=MSRN method”)
3 a. The GSM GMSC receives an incoming call for the subscriber.
4
6
7 c. The HLR sends a PRN message to the current GSM serving system; i.e., the IIF.
8
9 d. The IIF sends a ROUTREQ message to the ANSI-41 serving system.
10
11 e. The serving system determines that the subscriber is busy.
12
13 f. Therefore, the serving system returns a routreq message, containing the AccessDeniedReason
14 parameter set to the value Busy.
15
16 The IIF determines that CFB is active for the subscriber. The IIF sends the subscriber’s CFB
17 forward-to number as the MSRN in the prn message.
18
19 g. NOTE: From the GSM HLR and GMSC’s perspectives, the call is routed to a MSRN; they are not
20 aware that the call is being forwarded. Therefore, there may be billing issues associated with this
21 handling. Another drawback is that it is not possible to provide the GSM notification of forwarding
22 to the calling party functionality. It is also critical that the GMSC have controls built in to limit the
23 potential for call looping (e.g., if two dual-mode roaming subscribers have forwarded their calls to
24 each other).
25
26 h. The GSM HLR returns an sri message containing the CFB forward-to number as the MSRN to
27 the GMSC.
28
29 i. The GMSC establishes a call to the CFB forward-to number.
30
31

N.S0028
1 B.1.2.11.6.2 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-136
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
23

N.S0028
1 B.1.2.11.6.3 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-136
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

N.S0028
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 TLDN
7 into international format for use as the MSRN by adding country code digit(s) associated with the
8 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, the
15 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 condition.
19
20 k. Since the IIF is not able to redirect the call (i.e., optimal routing is not possible), it rejects the
21 redirection request.
22
23 l. If the serving system is able to redirect the call, it sends a TRANUMREQ message to the IIF,
24 requesting the CFB forward-to number. Note that not all ANSI-41 systems have implemented this
25 redirection capability. Without this capability, the call shall fail, possibly with a tone or
26 announcement to the calling party.
27
28 m. The IIF determines that CFB is active for the subscriber. Therefore, the IIF responds with a
29 tranumreq message including the subscriber’s CFB forward-to number.
30
31 n. The serving system forwards the call to the CFB forward-to number.
32 B.1.2.11.6.4 4.6.1.2.6.4 CFB invocation (Scenario 2, with OR)
33 In this scenario, the busy condition is detected by the ANSI-41 serving system after the
35 and optimal routing is invoked.
36 This scenario is covered in Section 4.7.1.
37

N.S0028
1 B.1.2.12 4.6.1.3 Call forwarding no reply (CFNRy)
2 The following scenarios illustrate the call forwarding no reply (CFNRy) information flows applicable to
3 ANSI-41 foreign mode operation.
4 B.1.2.12.1 4.6.1.3.1 CFNRy registration
5 See 4.6.1.1.1 for the CFNRy registration information flows applicable to ANSI-41 foreign mode
3
7 B.1.2.12.2 4.6.1.3.2 CFNRy deregistration (erasure)
8 See 4.6.1.1.2 for the CFNRy deregistration information flows applicable to ANSI-41 foreign mode
9 operation, since they are the same as those for CFU.3
10 B.1.2.12.3 4.6.1.3.3 CFNRy activation
11 See 4.6.1.1.3 for the CFNRy activation information flows applicable to ANSI-41 foreign mode
12 operation, since they are the same as those for CFU. 3
13 B.1.2.12.4 4.6.1.3.4 CFNRy deactivation
14 See 4.6.1.1.4 for the CFNRy deactivation information flows applicable to ANSI-41 foreign mode
15 operation, since they are the same as those for CFU. 3
16 B.1.2.12.5 4.6.1.3.5 CFNRy invocation
17 The following scenarios illustrate the CFNRy invocation information flows applicable to ANSI-41
18 foreign mode operation.
19
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).

N.S0028
1 B.1.2.12.5.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 to
3 complete the call to the TLDN, and optimal routing is not invoked.
GSM GSM ANSI-136
IIF
GMSC HLR VMSC
2
GSM ANSI-41
incoming call
a
SRI
b
PRN
c
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 no
13 answer condition.
14
16 redirection request
17

N.S0028
1 l. If the serving system is able to redirect the call, it sends a TRANUMREQ message to the IIF,
2 requesting the CFNA (i.e., GSM CFNRy) forward-to number. Note that not all ANSI-41 systems
3 have implemented this redirection capability. Without this capability, the call shall fail, possibly
4 with a tone or announcement to the calling party.
5
6 m. The IIF determines that CFNRy is active for the subscriber. Therefore, the IIF responds with a
7 tranumreq message including the subscriber’s CFNRy forward-to number.
8
9 n. The serving system forwards the call to the CFNRy forward-to number.
10 B.1.2.12.5.2 4.6.1.3.5.2. CFNRy invocation (Scenario 1, with OR)
11 In this scenario, the no reply condition is detected by the ANSI-41 serving system while attempting to
12 complete the call to the TLDN, and optimal routing is invoked.
13 This scenario is addressed in Section 4.7.1.
14

N.S0028
1 B.1.2.13 4.6.1.4 Call forwarding not reachable (CFNRc)
2 The following scenarios illustrate the call forwarding not reachable (CFNRc) information flows
3 applicable to ANSI-41 foreign mode operation.
4 B.1.2.13.1 4.6.1.4.1 CFNRc registration
5 See 4.6.1.1.1 for the CFNRc registration information flows applicable to ANSI-41 foreign mode
6 operation.4
7 B.1.2.13.2 4.6.1.4.2 CFNRc deregistration (erasure)
8 See 4.6.1.1.2 for the CFNRc deregistration information flows applicable to ANSI-41 foreign mode
4
10 B.1.2.13.3 4.6.1.4.3 CFNRc activation
11 See 4.6.1.1.3 for the CFNRc activation information flows applicable to ANSI-41 foreign mode
4
13 B.1.2.13.4 4.6.1.4.4 CFNRc deactivation
14 See 4.6.1.1.4 for the CFNRc deactivation information flows applicable to ANSI-41 foreign mode
4
16 B.1.2.13.5 4.6.1.4.5 CFNRc invocation
17 The following scenarios illustrate the CFNRc invocation information flows applicable to ANSI-41
19
20
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.

N.S0028
1 B.1.2.13.5.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.
GSM GSM ANSI-136
Gateway Home Serving
IIF
GMSC HLR VMSC
2
GSM ANSI-41
incoming call
a
SRI
b
PRN
c
ROUTREQ
d
No response
to paging e
routreq [No response]
f
prn_RE
[AbsentSubscriber]
g
sri [CFNRc #]
h
forward call to CFNRc#

i
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 subscriber
13 error, otherwise, the IIF sends a ROUTREQ message to the ANSI-41 serving system.
14
15 e. The serving system determines that the subscriber is no reachable (e.g., does not respond to
16 paging).
17
18 f. Therefore, the serving system returns a routreq message, containing the AccessDeniedReason
19 parameter set to the value No Page Response.
20
21 g. The IIF determines that CFNRc is active for the subscriber. The IIF sends the AbsentSubscriber
22 error code in a ProvideRoamingNumber Return Error message.
23
24 h. The GSM HLR returns a sri message, directing the GMSC to forward the call to the CFNRc
26
27 i. The GMSC forwards the call to the CFB forward-to number.
28

N.S0028
1 B.1.2.13.5.2 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.
GSM GSM ANSI-136
IIF
GMSC HLR VMSC
2
GSM ANSI-41
incoming call
a
SRI
b
PRN
c
d
routreq [TLDN]
e
prn [MSRN]
f
sri [MSRN]
g
setup call to MSRN

h
No response
to paging i
REDREQ [No Page Response, BillingID1]
j
redreq [reject]
k
TRANUMREQ [No Page Response]
l
tranumreq [CFNRc #]
m
forward call to CFNRc #

n
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
17 redirection request.
18

N.S0028
1 If the serving system is able to redirect the call, it sends a TRANUMREQ message to the IIF,
2 requesting the forward-to number appropriate for the no page response condition. Note that not
3 all ANSI-41 systems have implemented this redirection capability. Without this capability, the call
4 shall fail, possibly with a tone or announcement to the calling party.
5
6 l. The IIF determines that CFNRc is active for the subscriber. Therefore, the IIF responds with a
7 tranumreq message including the subscriber’s CFNRc forward-to number.
8
9 m. The serving system forwards the call to the CFNRc forward-to number.
10 B.1.2.13.5.3 4.6.1.4.5.3 CFNRc invocation (Scenario 2, with OR)
11 In this scenario, the not reachable condition is detected by the ANSI-41 serving system after the
13 and optimal routing is invoked.
15

N.S0028
1 B.1.3 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 ANSI-136
3 41 native subscriber roaming in a GSM network; i.e., GSM foreign mode.
4 B.1.3.1 4.6.2.1 Call forwarding unconditional (CFU)
5 The following scenarios illustrate the call forwarding unconditional (CFU) information flows applicable
6 to GSM foreign mode operation.
7 B.1.3.1.1 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 station
14 (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

N.S0028
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 B.1.3.1.2 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 digit
16 message.
17
19 success.
20
21 e. The IIF sends an erase_ss message to the serving system, indicating a successful feature control
22 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 service.
27

N.S0028
1 B.1.3.1.3 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 information
10 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.
23 B.1.3.1.4 4.6.2.1.4 CFU deactivation
24
25 This scenario illustrates the CFU deactivation information flows applicable to GSM foreign mode
26 operation.
27

N.S0028
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
1
2 Figure 49: CFU deactivation
3
4 a. The GSM serving system receives an A_DEACT_SS message from the subscriber’s mobile
5 station (MS), indicating that the subscriber wishes to deactivate the CFU service.
6
7 b. The serving system sends a DEACT_SS message to the IIF, constructed based on the
8 information received in the A_DEACT_SS message.
9
10 c. The IIF translates the information received in the DEACT_SS message into a corresponding digit
12 message.
13
15 success.
16
17 e. The IIF sends a deact_ss message to the serving system, indicating a successful feature control
18 request.
19
20 f. The serving system sends a deactivation response message to the subscriber.
21

N.S0028
1 B.1.3.1.5 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.
15

N.S0028
1 B.1.3.2 4.6.2.2 Call forwarding busy (CFB)
2 The following scenarios illustrate the call forwarding busy (CFB) information flows applicable to GSM
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 time—
7 the IIF shall use the ANSI-41 TransferToNumberRequest operation to obtain the CFB forward-to
8 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 correspond
27 with the numbers previously provided to the GSM serving system, then the IIF sends the modified
28 information to the GSM serving system using the InsertSubscriberData operation. The CFNA
29 forward-to number shall be populated as both the CFNRc and CFNRy forward-to numbers.

N.S0028
1 B.1.3.2.1 4.6.2.2.1 CFB registration
2 This scenario illustrates the CFB registration information flows applicable to GSM foreign mode
3 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
4
5 Figure 52: CFB registration
6 a. The GSM serving system receives an A_REG_SS message from the subscriber’s mobile station
7 (MS), indicating that the subscriber wishes to change his call forwarding number.
8
9 b. The serving system sends a REG_SS message to the IIF, constructed based on the information
10 received in the A_REG_SS message.
11
12 c. The IIF translates the information received in the REG_SS message into a corresponding digit
14 message.
15
17 success.
18
19 e. The IIF sends a reg_ss message to the serving system, indicating a successful feature control
20 request.
21

N.S0028
1 f. The serving system sends a registration response message to the subscriber.

2
3 g-h. If the subscriber’s ANSI-41 profile changes as a result of the operation (e.g., the service was
4 previously authorized, but not activated), the HLR sends a QUALDIR message to the IIF,
5 containing the new profile information.
6
7 i. If the IIF determines that the subscriber’s call forwarding number may have changed, it sends a
8 TRANUMREQ message to the HLR to request the new number.
9
10 j. The HLR responds with the subscriber’s call forwarding number in the tranumreq message.
11
12 k-m. If the subscriber’s GSM profile has changed as a result of these operations, then the IIF sends
13 the modified profile information to the serving system via an InsertSubscriberData message
14 exchange.
15
16 Note: The process of registering the call forwarding number may also result in activation of the
17 service. This is based on HLR (i.e., carrier) determined policy.
18

N.S0028
1 B.1.3.2.2 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 digit
15 message.
16
18 success.
19
20 e. The IIF sends an erase_ss message to the serving system, indicating a successful feature control
21 request.
22
23 f. The serving system sends a deregistration response message to the subscriber.
24

N.S0028
2 previously authorized and activated), the HLR sends a QUALDIR message to the IIF, containing
3 the new profile information.
4
5 i-k. If the subscriber’s GSM profile has changed as a result of these operations, then the IIF sends
7 exchange.
8
9 Note: The process of deregistering the call forwarding service also results in deactivation of the
10 service.
11
12 B.1.3.2.3 4.6.2.2.3 CFB activation
13 This scenario illustrates the CFB activation information flows applicable to GSM foreign mode
14 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
15
16 Figure 54: CFB activation
17
18 a. The GSM serving system receives an A_ACT_SS message from the subscriber’s mobile station
19 (MS), indicating that the subscriber wishes to activate the call forward service.
20
21 b. The serving system sends an ACT_SS message to the IIF, constructed based on the information
22 received in the A_ACT_SS message.
23

N.S0028
1 c. The IIF translates the information received in the ACT_SS message into a corresponding digit
3 message.
4
6 success.
7
8 e. The IIF sends an act_ss message to the serving system, indicating a successful feature control
9 request.
10
11 f. The serving system sends an activation response message to the subscriber.
12
14 previously authorized but not active), the HLR sends a QUALDIR message to the IIF, containing
15 the new profile information.
16
19 exchange.
20 B.1.3.2.4 4.6.2.2.4 CFB deactivation
21 This scenario illustrates the CFB deactivation information flows applicable to GSM foreign mode
22 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
23
24 Figure 55: CFB deactivation

N.S0028
1
2 a. The GSM serving system receives an A_DEACT_SS message from the subscriber’s mobile
3 station (MS), indicating that the subscriber wishes to deactivate the call forward service.
4
5 b. The serving system sends a DEACT_SS message to the IIF, constructed based on the
6 information received in the A_DEACT_SS message.
7
8 c. The IIF translates the information received in the DEACT_SS message into a corresponding digit
10 message.
11
13 success.
14
15 e. The IIF sends a deact_ss message to the serving system, indicating a successful feature control
16 request.
17
18 f. The serving system sends a deactivation response message to the subscriber.
19
21 previously authorized and active), the HLR sends a QUALDIR message to the IIF, containing the
22 new profile information.
23
26 exchange.
27 B.1.3.2.5 4.6.2.2.5 CFB invocation
28 The following scenarios illustrate the CFB invocation information flows applicable to GSM foreign
29 mode operation.
30

N.S0028
1 B.1.3.2.5.1 4.6.2.2.5.1 CFB invocation (without OR)
2 In this scenario, the busy condition is detected by the GSM serving system while attempting to
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
4
5 Figure 56: CFB invocation (without OR)
6 a. The ANSI-41 originating MSC (OMSC) receives an incoming call for the subscriber.
7
8 b. The OMSC sends a LOCREQ message to the HLR.
9
10 c. The HLR sends a ROUTREQ message to the current serving system; i.e., the IIF.
11
12 d. The IIF sends a PRN message to the GSM serving system.
13
14 e. The serving system returns a prn message, containing a routing number (called a mobile station
15 roaming number, or MSRN, in GSM) to the IIF.
16
17 f. The IIF responds to the HLR with a routreq message including the TLDN that it derives from the
18 MSRN. Note that the TLDN is typically in international format.
19
20 g. The HLR returns a locreq message containing the TLDN to the OMSC.
21
22 h. The OMSC establishes a call to the TLDN.
23
24 i-j. The serving system determines that the subscriber is busy and forwards the call to the CFB
26

N.S0028
1 B.1.3.2.5.2 4.6.2.2.5.2 CFB invocation (with OR)
2 In this scenario, the busy condition is detected by the GSM serving system while attempting to
5 B.1.3.3 4.6.2.3 Call forwarding no answer (CFNA)
6 The following scenarios illustrate the call forwarding no answer (CFNA) information flows applicable
7 to GSM foreign mode operation.
8 Since the ANSI-41 HLR does not provide the CFNA forward-to number to the serving system until the
9 feature is actually invoked—versus the GSM method, whereby the HLR provides the forward-to
10 number(s) to the serving system as part of the subscriber’s profile information at registration time—
11 the IIF shall use the ANSI-41 TransferToNumberRequest operation to obtain the CFNA forward-to
12 number. This is illustrated in Figure 51 and described in Section 4.6.2.2.
13 Note that ANSI-41, unlike GSM, does not distinguish the “not reachable” condition from the “no reply”
14 condition. Therefore, if ANSI-41 CFNA is activated, then both of the GSM CFNRy and CFNRc
15 services shall be considered activated.
16 B.1.3.3.1 4.6.2.3.1 CFNA registration
17 See 4.6.2.2.1 for the CFNA registration information flows applicable to GSM foreign mode operation,
18 since they are the same as those for CFB. Both CFNRy and CFNRc shall be registered in the IIF and
19 GSM VLR.
20 B.1.3.3.2 4.6.2.3.2 CFNA deregistration (erasure)
21 See 4.6.2.2.2 for the CFNA deregistration information flows applicable to GSM foreign mode
22 operation, since they are the same as those for CFB. Both CFNRy and CFNRc shall be deregistered
23 in the IIF and GSM VLR.
24 B.1.3.3.3 4.6.2.3.3 CFNA activation
25 See 4.6.2.2.3 for the CFNA activation information flows applicable to GSM foreign mode operation,
26 since they are the same as those for CFB. Both CFNRy and CFNRc shall be activated in the IIF and
27 GSM VLR.
28 B.1.3.3.4 4.6.2.3.4 CFNA deactivation
29 See 4.6.2.2.4 for the CFNA deactivation information flows applicable to GSM foreign mode operation,
30 since they are the same as those for CFB. Both CFNRy and CFNRc shall be deactivated in the IIF
31 and GSM VLR.
32 B.1.3.3.5 4.6.2.3.5 CFNA invocation
33 The following scenarios illustrate the CFNA invocation information flows applicable to GSM foreign
34 mode operation.
35 B.1.3.3.5.1 4.6.2.3.5.1 CFNA invocation (Scenario 1, without OR)
36 In this scenario, the no reply condition is detected by the GSM serving system while attempting to

N.S0028
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
1
2 Figure 57: CFNA invocation (Scenario 1, without OR)
4
5 i-j. The serving system determines that the subscriber does not answer the alert and forwards the
6 call to the CFNRy forward-to number.
7
8 B.1.3.3.5.2 4.6.2.3.5.2 CFNA invocation (Scenario 1, with OR)
9 In this scenario, the no reply condition is detected by the GSM serving system while attempting to
11
13

N.S0028
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 [1] and GSM 9.02 [6].
4 From GSM 02.79 [8] and GSM 03.79 [9], Late Call Forwarding is Call Forwarding performed after the
5 call has been extended to the Visited PLMN (VPLMN) of the forwarding subscriber (i.e., Conditional
6 Call Forwarding on Busy, Conditional Call Forwarding on No Reply, and Conditional Call Forwarding
7 on Not Reachable detected in the VPLMN of the forwarding subscriber). Late Call Forwarding may be
8 invoked in the Interrogating PLMN (IPLMN) or in the VPLMN of the forwarding subscriber.
9 Assumptions:
10 1) The Subscriber has forwarding enabled.
11 2) Optimal Routing is enabled.
12 The following scenarios address the case where the forwarding attempt is done by the IPLMN.
13 4.7.1 ANSI-41 Foreign Mode
14 B.1.3.4 4.7.1.1 ANSI-41 Foreign Mode - Success condition
15 Scenario: GSM Subscriber A makes a call origination attempt at GMSC-A to a GSM Subscriber B
16 who is roaming and registered in an ANSI-41 network at MSC-B. Subscriber B has call forwarding set
17 to an address at MSC-C.
18
GSM GSM ANSI-41

(GMSC-A) (B’s HLR) IIF (MSC-B/VLR) (MSC-C)
Call Origination
a a
Send Routing Info
b b
[ORphase, Provide Roaming Number
c c
GMSC#,CR#, ROUTEREQ [billing ID]
[GMSC#,CR#,
d ORinterrog(Opt.)] d
ORinterrog(Opt.)]
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
19
20 Figure 58: Optimal Routing with Late Call Forwarding (ANSI-41 Foreign Mode) Success Case
21

N.S0028
1 a. GSM GMSC-A receives a call origination stimulus from Subscriber A.

2
3 b. If GMSC-A recognizes subscriber B's address as belonging to a GSM PLMN, it checks the
4 identity of HPLMN-B and shall follow the following procedures:
5
6 (i) If GMSC-A is in the same PLMN as the HLR-B, GMSC-A sends a request for routing
7 information to Subscriber B's HLR. This GSM-SRI request contains:
8
9 - an indication of the phase of optimal routing supported by the GMSC-A;
10
11 - the E-164 address of GMSC-A;
12
13 - the Call Reference Number.
14
15 (ii) If GMSC-A is in a different PLMN from HLR-B, it sends a request for routing information to
16 Subscriber B's HLR. This GSM-SRI request contains all parameters as in item (i) above as well
17 as an indication that it is an optimal routing inquiry (OR interrogation indicator).
18
19
20 c. Subscriber B's GSM HLR determines that Subscriber B is roaming at MSC-B and sends a GSM-
21 Provide Roaming Number message, which also contains the GMSC address, the Call Reference
22 Number and the OR interrogation indicator if it was received in the GSM-SRI to an IIF acting on
23 behalf of MSC-B to get a roaming number. The E-164 address of GMSC-A shall be provided in
24 the message, as specified in GSM 03.79.
25
26 d. The IIF relays this request to the ANSI-41 MSC/VLR-B by sending an ANSI-41-Routing Request
27 message. The originating address in this message is provided as a routing address back to the
28 IIF.
29
30 e. The ANSI-41 MSC/VLR-B acknowledges the ANSI-41-Routing Request message with the
31 Temporary Local Directory Number (TLDN).
32
33 f. Upon receipt of the ANSI-41-Routing Request message, the IIF sends an MSRN to Subscriber
34 B's GSM HLR in the GSM-Provide Roaming Number Acknowledgment message.
35
36 g. Subscriber B's GSM HLR relays this information to GMSC-A using the GSM-Send Routing
37 Information Acknowledgment message. This message includes MSRN and optionally a
38 ForwardedInterrogationRequired (FIR) parameter, which indicates whether the GMSC-A shall
39 interrogate the HLR for routing information for late call forwarding.
40
41 h. GMSC-A starts a call setup procedure using the MSRN (TLDN) as Subscriber B's called address
42 at ANSI-41 MSC/VLR-B).
43
44 i. The incoming call at ANSI-41 MSC/VLR-B can not be terminated because of reasons such as No
45 Answer, No Page Response, or Unavailable. An ANSI-41-Redirection Request message with a
46 RedirectionReason parameter is then sent to the IIF based on the originating address received in
47 the ANSI-41-Route Request message at step d.
48
49 j. The IIF sends GSM-Resume Call Handling message to GMSC-A based on the GMSC-A address
50 received in the GSM-Provide Roaming Number. Note that the GSM-Resume Call Handling
51 includes the same Call Reference Number received in the GSM-Provide Roaming Number, the
52 cause for termination failure (forwarding reason) and the forwarding number at MSC-C plus all
53 necessary parameters required for call forwarding.
54
55 k. If the ForwardedInterrogationRequired parameter was received from Subscriber B's GSM HLR in
56 the GSM-Send Routing Information Acknowledgement message at step g, , GMSC-A sends a

N.S0028
1 GSM-Send Routing Information message to Subscriber B's GSM HLR requesting it to send a call
2 forwarding information.
3
4 Otherwise, it is assumed that all forwarding information is ready available at GMSC-A and an
5 acknowledgment of the GSM-Resume Call Handling message is sent to the IIF (step m).
6
7 l. If a corresponding forwarded-to number is available at subscriber B's GSM HLR, GMSC-A
8 receives a GSM-Send Routing Information Acknowledge message with the necessary forwarding
9 information.
10
11 In case of an error, a GSM-Send Routing Information Error message is sent to GMSC-A and
12 GMSC-A uses the forwarding information from step j.
13
14 m. GMSC-A sends an acknowledgment of the GSM-Resume Call Handling message.
15
16 n. Upon receipt of GSM-Resume Call Handling Acknowledgment message, the IIF acknowledges
17 the ANSI-41-Redirection Request message.
18
19 In case of an error, the IIF rejects the redirection request and the ANSI-MSC-B initiates a call
20 forwarding procedure extend the call to MSC-C. See Section 6.2.
21
22 o. If step n is successful, GMSC-A releases all circuit-associated resources specific to ANSI-41
23 MSC/VLR-B.
24
25 p. GMSC-A starts a call setup procedure using the call forwarded-to number as Subscriber B’s
26 address at ANSI-41 MSC-C.
27
28

N.S0028
1 B.1.3.5 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 Figure 59: Optimal Routing with Late Call Forwarding (ANSI-41 Foreign Mode) Failure Case
7 a.-l.These steps are the same as the success case.
8
9 m. If GMSC-A determines that it cannot forward the call via an optimal route, it returns a Resume
10 Call Handling error to the IIF.
11
12 n. The redirection request at step i. is rejected.
13
14 o. The ANSI-41 MSC/VLR-B sends an ANSI-41 TransferToNumberRequest message to the IIF with
15 the RedirectionReason parameter.
16
17 p. The IIF returns the ANSI-41 TransferToNumberResponse message to the ANSI-41 MSC/VLR-B
18 with the forward-to number in the TerminationList parameter along with an indication of the
19 reason (DMH_RedirectionIndicator) for extending the incoming call.
20
21 q. The ANSI-41 MSC/VLR-B forwards the incoming call to MSC-C.
22

N.S0028
1 4.7.2 GSM Foreign Mode

2 B.1.3.6 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
ROUTEREQ
c 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
REDREQ [REDREASON]
j 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 Figure 60: Optimal Routing with Late Call Forwarding (GSM Foreign Mode) Success Case
8 a. ANSI-41 MSC-A receives a call origination stimulus from Subscriber A.
9
10 b. The ANSI-41 MSC-A sends an ANSI-41-Location Request message for routing information to
11 Subscriber B's ANSI-41 HLR with the MSCID address of the originating MSC (ANSI-41 MSC-A).
12
13 c. Subscriber B's ANSI-41 HLR determines that Subscriber B is roaming at MSC-B and sends a
14 ANSI-41-Routing Request message number with the MSCID address of the ANSI-41 MSC-A
15 received in step b. to an IIF acting on behalf of MSC-B to get a roaming number.
16
17 d. The IIF relays this request to GSM MSC/VLR-B by sending a GSM-Provide Roaming Number
18 message. The IIF generates two parameters: the Call Reference number (for the VLR/MSC-B to
19 use in the GSM-RCH) and the GMSC address set to the IIF address, to indicate that the IIF is
20 capable of supporting optimal routing for late call forwarding.
21
22 e. GSM MSC/VLR-B acknowledges the GSM - Provide Roaming Number message with the Mobile
23 Subscriber Roaming Number (MSRN).
24
25 f. Upon receipt of this message, the IIF sends the TLDN to Subscriber B's ANSI-41 HLR in the
26 ANSI-41-Routing Request message.

N.S0028
1
2 g. Subscriber B's ANSI-41 HLR relays this information to ANSI-41 MSC-A via the ANSI-41-Location
3 Request (Acknowledgment) message.
4
5 h. ANSI-41 MSC starts a call setup procedure using TLDN (MSRN) as Subscriber B's called
6 address at GSM MSC/VLR-B. The incoming call can not be terminated at GSM MSC/VLR-B
7 because of reasons such as Busy, Not Reachable, or No Reply.
8
9 i. Since the GMSC address and the Call Reference Number parameters were present in the
10 GSM-Provide Roaming Number message the GSM MSC-B sends a GSM-Resume Call Handling
11 message to the IIF with the received Call Reference number and all necessary information
12 required for call forwarding.
13
14 If optimal routing is not supported the call is forwarded by GSM MSC-B using the forwarding
15 information available.
16
17 j. When optimal routing is supported and the IIF receives the GSM-Resume Call Handling
18 message, the IIF sends an ANSI-41-Redirecion Request message with the Redirection Reason to
19 the ANSI-41 MSC-A supporting subscriber A's call origination attempt.
20
21 k. The ANSI-41 MSC-A passes this Redirection Reason to the Subscriber B's ANSI-41 HLR in the
22 ANSI-41-Transfer To Number message to get call forwarding number information.
23
24 l. Based on the Redirection Reason, the ANSI-41 HLR returns the corresponding forwarded-to
25 number to ANSI-41 MSC/VLR-A.
26
27 m. If ANSI-41 MSC-A received forwarded-to number from ANSI-41 HLR, it sends
28 ANSI-41-Redirection Request (Acknowledgment) message to the IIF.
29
30 In case of an error, ANSI-41 MSC-A rejects the redirection request. The IIF then returns a
31 GSM-Resume Call Handling Error message to GSM MSC-B, which then attempts to forward the
32 call to MSC-C using the forwarding information available.
33
34 n. Upon receiving the ANSI-41-Redirection Request (Acknowledgment) in step m., the IIF sends a
35 GSM-Resume Call Handling Acknowledgment message to GSM MSC-B.
36
37 o. The ANSI-41 MSC-A releases all circuit-associated resources specific to GSM MSC/VLR-B.
38
39 p. The ANSI-41 MSC-A starts a call setup procedure using the call forwarded-to number as
40 Subscriber B's address at MSC-C.
41

N.S0028
1 B.1.3.7 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 NumberAck [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 Figure 61: Optimal Routing with Late Call Forwarding (GSM Foreign Mode) Failure Case
8 a.-l.These steps are the same as the Success Case.
9
10 m. The redirection request at step j. is rejected.
11
12 n. The IIF sends a GSM-Resume Call Handling Error message to GSM MSC-B.
13
14 o. The GSM MSC-B forwards the incoming call to MSC-C.
15

N.S0028
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 B.1.3.8 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 an
7 ANSI-41 network.
Serving System
MS MSC/ GSM
IIF
VLR HLR
*FC [SEND]
a
FEATREQ [DGTSDIAL]
b
ActivateSS
c
ActivateSS Ack
d
featreq [FEATRESULT, ANNLIST]
e
f
call release
g

h
ISD Ack
i
QUALDIR
j
qualdir k
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 the
14 HLR associated with the MS.

N.S0028
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 MS
8 based on the information contained in the response. In this case, the treatment is to apply feature
9 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.
17 B.1.3.9 4.8.1.2 ANSI-41 Foreign Mode Unsuccessful Call Waiting Activation
18 The following scenario describes an unsuccessful call waiting activation by a native GSM subscriber
19 roaming in an ANSI-41 network.
20
5 Most likely, the GSM 02.30 standardized MMI would be mapped to the equivalent GSM
functional message.

N.S0028
Serving System
MS MSC/ GSM
IIF
VLR HLR
*FC [SEND]
a
FEATREQ [DGTSDIAL]
b
ActivateSS
c
ActivateSS Ack [User error]

d
e
f
call release
g
1
2 Figure 63: ANSI-41 Foreign Mode Unsuccessful Call Waiting Activation
3 a. The subscriber requests activation of call waiting. The MS converts the user-entered MMI/menu
4 selections to feature codes. (e.g. *FC). The MS sends this feature code string to the Serving
5 MSC. During analysis of the digit string, the Serving MSC detects a feature code string.
6 b. The digit string is included in a FEATREQ and sent from the Serving MSC to the IIF emulating the
7 HLR associated with the MS.
8 c. The IIF determines the digit string pertains to the activation of call waiting and then sends an
9 Activate SS message to the HLR to request activation of call waiting. 6
10 d. The HLR returns an Activate SS Ack message to the IIF indicating an unsuccessful activation of
11 call waiting.
12 e. The IIF sends a featreq to the Serving MSC containing a Feature Result parameter set to
13 “Unsuccessful”. In addition, it may include an AnnouncementList code that corresponds to the
14 User error parameter included in the Activate SS Ack message sent by the GSM HLR.
16 based on the information contained in the response.
17 g. The Serving MSC sends a Release message to the MS.
18
19
functional message.

N.S0028
1 B.1.3.10 4.8.1.3 GSM Foreign Mode Feature Activation
2 This scenario describes a successful call waiting activation by a native ANSI-136 41 subscriber
3 roaming in a GSM network.
GSM
MS MSC/
IIF HLR
VLR
Activate SS
a
Activate SS
b
FEATREQ [DGTSDIAL]
c
d
Activate SS Ack
e
Activate SS Ack
f
QUALDIR g
h
ISD Ack i
qualdir
j
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 service
11 for the activation being requested.
12 c. The IIF converts the call waiting Activate SS message to a particular feature code (e.g. *FC).
13 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 parameters
17 the HLR may have included that provide instructions for treatment towards the user (such as
18 AnnouncementList) shall be ignored by the IIF and not mapped into the message sent to the
19 Serving GSM MSC.
20 f. When the Activate SS Ack message is received from the IIF, the Serving GSM MSC sends a
21 message to the MS to indicate that the call waiting activation had been successful.

N.S0028
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 message
3 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.
9 4.8.2 Call Waiting Deactivation
10 B.1.3.11 4.8.2.1 ANSI-41 Foreign Mode Call Waiting Deactivation
11 This scenario describes a successful call waiting deactivation by a native GSM subscriber roaming in
12 an ANSI-41 network.
13

N.S0028
ANSI-136 Serving System
MS MSC/ GSM
IIF
VLR HLR
*FC0 [SEND]
a
FEATREQ [DGTSDIAL]
b
DeactivateSS
c
DeactivateSS Ack
d
e
f
call release
g

h
ISD Ack
i
QUALDIR
j
qualdir k
1
2 Figure 65: ANSI-41 Foreign Mode Call Waiting Deactivation
3 a. The subscriber selects a menu entry in order to deactivate call waiting. The MS converts the
4 user-entered MMI/menu selections to feature codes. (e.g. *FC0). The MS sends this digit string
5 towards the network. The digit string is received by the Serving MSC. During analysis of the digit
6 string, the Serving MSC detects a feature code string.
7 b. The dialed digits are included in a FEATREQ and sent from the Serving MSC to the IIF emulating
8 the HLR associated with the MS.
9 c. The IIF determines the digit string pertains to the deactivation of call waiting and then sends a
10 Deactivate SS message to the HLR to request deactivation of call waiting. 7
11 d. The HLR returns a Deactivate SS Ack message to the IIF indicating a successful deactivation of
12 call waiting.
functional message.

N.S0028
1 e. The IIF sends a featreq to the Serving MSC containing the feature request confirmation
2 indication.
4 based on the information contained in the response. In this case, the treatment is to apply feature
5 confirmation.
6 g. The Serving MSC releases the call.
7 h. Because the request resulted in a change to the subscriber’s service profile (i.e., the call waiting
8 feature was deactivated), the HLR reports the change by sending an Insert Subscriber Data
9 message to the IIF emulating the Serving MSC/VLR.
10 i. The IIF returns an Insert Subscriber Data Ack message to the HLR.
11 j. The IIF sends a QUALDIR message to the Serving MSC/VLR.
12 k. The Serving MSC/VLR returns a qualdir to the IIF.
13 B.1.3.12 4.8.2.2 GSM Foreign Mode Feature Deactivation
14 This scenario describes a successful call waiting deactivation by a native ANSI-136 41 subscriber
15 roaming in a GSM network.
16

N.S0028
GSM Serving System
MS GSM
MSC/ IIF HLR
VLR
Deactivate SS
a
Deactivate SS
b
FEATREQ [DGTSDIAL]
c
d
Deactivate SS Ack
e
Deactivate SS Ack
f
QUALDIR g
h
ISD Ack i
qualdir
j
1
2 Figure 66: GSM Foreign Mode Call Waiting Deactivation
3 a. The subscriber requests activation of call waiting. The MS associates the MMI/menu selection
4 provided by the subscriber with a request to deactivate call waiting. The MS sends a request for
5 deactivation of call waiting (by issuing a Deactivate SS operation).
6 b. The Serving GSM MSC sends a Deactivate SS message to the IIF emulating the HLR associated
7 with the subscriber. The message specifies the call waiting supplementary service for the
8 deactivation being requested.
9 c. The IIF converts the call waiting Deactivate SS message to a particular digit string (e.g. *FC0).
10 The IIF includes this digit string (including *) in the Digits (Dialed) parameter of a FEATREQ
11 message and sends the message to the subscriber’s HLR.
12 d. The HLR returns a featreq message to the IIF indicating a successful call waiting deactivation.
13 e. The IIF returns a Deactivate SS Ack message back to the Serving GSM MSC. Any parameters
14 the HLR may have included that provide instructions for treatment towards the user (such as
15 AnnouncementList) shall be ignored by the IIF and not mapped into the message sent to the
16 Serving GSM MSC.

N.S0028
1 f. When the Deactivate SS Ack message is received from the IIF, the Serving GSM MSC sends a
2 message to the MS to indicate that the call waiting deactivation had been successful.
3 g. Because the request resulted in a change to the subscriber’s service profile (i.e., the call waiting
4 feature was deactivated), the HLR reports the change by sending a QUALDIR message to the IIF
5 emulating the Serving GSM MSC/VLR.
6 h. The IIF sends an Insert Subscriber Data message to the Serving GSM MSC/VLR.
7 i. The Serving GSM MSC/VLR returns an Insert Subscriber Data Ack to the IIF.
8 j. The IIF returns a qualdir message to the HLR.
9
10

N.S0028
1 4.9 Calling Number / Line Identification Presentation/Restriction

2 4.9.1 Handling of calling number/ line identification presentation
3 B.1.3.13 4.9.1.1 GSM Foreign Mode
4 If CNIP / CLIP service is authorized and active, the calling party number is available and presentation
5 is allowed, the called party’s serving network shall provide the calling party number to the called party
6 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 specified
14 in TIA/EIA-41-5-D [1].
15
16 c. The calling party number may be carried in the calling party number string parameter as specified
17 in TIA/EIA-41-5-D [1].
18
19 d. The calling party number may be carried in the additional signal information element as specified
20 in GSM 09.02 [7].
21
22 e. The VLR returns a roaming number for routing purposes.
23
24 f. The IIF maps the MSRN it receives from the VLR into the TLDN field in the routreq.

N.S0028
1
2 g. The HLR returns a locreq to the MSC with the routing information it received from the IIF.
3
4 h. The trunk signaling between the MSC’s may transit a number of intermediate signaling networks
5 of various capabilities. As such, there is no guarantee that the calling party number can be
6 conveyed using the ISUP/TUP signaling capabilities.
7
8 i. The MSC delivers the calling party identification during the call setup operation with the MS. The
9 calling party subaddress is passed if it is received from the originating network. The Calling Party
10 No, Presentation Indicator (PI), and Screening Indicator (SI) shall be sent in accordance with
11 GSM 03.81 [5].
12
13 Note: Where a calling party number is delivered both via MAP signaling and ISUP/TUP signaling, the
14 number delivered via MAP signaling takes precedence.
15
16 Note: When an additional calling party number is also available for presentation purposes, the
17 additional calling party number (subject to CNIP/CLIR) shall be presented in preference to any
18 other calling party number.
19
20 B.1.3.13.1 4.9.1.1.1 Interrogation
21 The subscriber can request the status of the supplementary service when operating in GSM foreign
22 mode and be informed if the service is provided to him/her.
23

N.S0028
1 B.1.3.14 4.9.1.2 ANSI-41 Foreign Mode
2 If CNIP / CLIP service is authorized and active, the calling party number is available and presentation
3 is allowed, the called party’s serving network shall provide the calling party number to the called party
4 during call alerting as in Figure 68 below.
5
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 specified
11 in GSM 09.02 [7].
12
13 c. The calling party number may be carried in the additional signal information element as specified
14 in GSM 09.02 [7].
15
16 d. The calling party number may be carried in the calling party number string parameter as specified
17 in ANSI-41.5 [1].
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 No
22 Ack.
23
24 g. The HLR returns an SRI Ack to the GMSC with the routing information it received from the IIF.
25

N.S0028
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.
10 B.1.3.14.1 4.9.1.2.1 Interrogation
11 The subscriber cannot request the status of the supplementary service in ANSI-41 Foreign mode.
12 4.9.2 Handling of calling number/ line identification restriction
13 B.1.3.15 4.9.2.1 General
14 If the calling subscriber has calling number/line identification restriction authorized and active and it is
15 impossible to indicate to the terminating network (due to interworking) that the number shall not be
16 presented to the terminating party, the calling number/line identity shall not be delivered to the
17 terminating network.
19 If CNIR / CLIR service is authorized and active, the calling party number is available and presentation
20 is restricted, the called party’s serving network shall not present the calling party number to the called
21 party during call alerting. An indication that the calling party number is restricted shall be delivered to
22 the called party.
23 B.1.3.16.1 4.9.2.2.1 Interrogation
24 The subscriber can request the status of the CNIR /CLIR supplementary service and be informed if
25 the service is provided to him/her and which mode is provided, i.e. permanent or temporary and if
26 temporary, what the default value is (i.e. allowed or restricted).
28 If CNIR / CLIR service is authorized and active, the calling party number is available and presentation
29 is restricted, the called party’s serving network shall not present the calling party number to the called
30 party during call alerting. An indication that the calling party number is restricted shall be delivered to
31 the called party.
32 B.1.3.17.1 4.9.2.3.1 Interrogation
33 The subscriber cannot request the status of the supplementary service.
34

N.S0028
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-136 41 mode. Likewise,
7 many 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 ODB
11 programs (e.g., Barring of Outgoing Calls) for which barring is performed at the VLR. Any barring or
12 call restrictions applied in the HLR shall result in the appropriate restrictions being downloaded to the
13 serving VLR/MSC via the IIF.
14 B.1.3.18 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-136 41
16 subscriber roaming in a GSM network at a time when the subscriber is currently registered.
VLR/
HLR IIF 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
29

N.S0028
1 B.1.3.19 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 subscriber
3 roaming in an ANSI-41 network.
VLR/
HLR IIF 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 Subscriber
8 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.
15 4.10.2 Invocation of Barring of Incoming Calls
17 Barring of incoming calls is performed at the ANSI-41 HLR. There is no IIF involvement.
19 Barring of incoming calls is performed at the GSM HLR. There is no IIF involvement.
20 4.10.3 Invocation of Barring of Roaming
21 Barring of Roaming is performed at the HLR. The following subsections, however, illustrate the
22 signaling at the IIF when a barred subscriber attempts to roam into a GSM or ANSI-41 Foreign
23 network.
25 This scenario describes the successful barring of roaming for a native ANSI-136 41 subscriber
26 attempting to roam into a GSM network.

N.S0028
MSC/
VLR IIF HLR
Update Location
a
REGNOT
b
regnot
c
UL Ack
d
1
2 Figure 71: Invocation of Barring of Roaming – GSM Foreign Mode
3
4 a. A native ANSI-136 41 subscriber with barring of Roaming active, attempts to register in a
5 GSM network. The GSM VLR sends an Update Location message to the IIF emulating the
6 subscriber’s HLR.
7
8 b. The IIF issues a RegistrationNotification INVOKE to the HLR.
9
10 c. The HLR determines that roaming is denied in this case, returns a RegistrationNotification
11 RETURN RESULT with AuthorizationDenied set to Not Authorized for the MSC. Optionally, a
12 RegistrationCancellation message may be sent to the previous Serving MSC/VLR (if
13 registration was in an ANSI-41 network) or to the IIF (if registration was in a GSM network).
14
15 d. The IIF issues an Update Location acknowledgement with User Error set to Roaming Not
16 Allowed. The VLR denies the registration attempt.
17

N.S0028
2 This scenario describes the successful ODB barring of roaming for a native GSM subscriber
3 attempting to roam into an ANSI-41 network.
MSC/ HLR
IIF
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 ANSI-41
8 network. The ANSI-41 VLR sends an RegistrationNotification INVOKE to the IIF emulating the
9 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) or
16 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.
20 4.10.4 Invocation of Barring of Supplementary Services Management
21 Barring of Supplementary Services Management is performed at the HLR. The following subsections,
22 however, illustrate the signaling at the IIF when a subscriber attempts to activate a supplementary
23 service in a GSM or ANSI-41 Foreign network, while Barring of Supplementary Services Management
24 is in effect.
26 This scenario describes the successful barring of supplementary service control for a native
27 ANSI-136 41 subscriber in a GSM network.

N.S0028
MSC/
VLR IIF HLR
Activate SS
a
FEATREQ
b
featreq
c
Activate SS Ack
d
1
2 Figure 73: Invocation of Barring of Supplementary Service Control – GSM Foreign Mode
3
4 a. A native ANSI-136 41 subscriber attempts to activate a feature to which he is not authorized. The
5 MSC sends an Activate SS message to the IIF emulating the subscriber’s HLR.
6
7 b. The IIF issues a FeatureRequest INVOKE message to the HLR.
8
9 c. The HLR, determining that the subscriber is not authorized, sends a FeatureRequest RETURN
10 RESULT, with FeatureResult set to Unsuccessful to the IIF.
11
12 d. The IIF issues an Activate SS acknowledgement, with User Error set to SS Subscription Violation
13 to the VLR. The VLR denies the activation.
14

N.S0028
2 This scenario describes the successful ODB barring of supplementary services management for a
3 native GSM subscriber in an ANSI-41 network.
MSC/
VLR IIF HLR
FEATREQ a
Activate SS
b
Activate SS Ack c
featreq
d
4
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 a
9 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.
18

N.S0028
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 the
8 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 a
10 teleservice server address which maps to the IIF. When the IIF receives this address it shall be
11 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 subscriber, GHOST applies only for
17 ANSI-136 subscriber and WEMT only for CDMA subscribers.
18
19

N.S0028
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 be
3 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. This
5 is depicted in the next two diagrams.
6 B.1.3.26 4.11.2.1 Short Message from CMT Mobile Station to GHOST/WEMT Mobile
7 Station both in Native Mode
MS-A TDMA MC-A MC-B TDMA TDMA

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

N.S0028
1 B.1.3.27 4.11.2.2 Short Message sent from GHOST/WEMT Mobile Station to CMT Mobile
2 Station, both in Native Mode
MS-A TDMA MC-A MC-B TDMA TDMA

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

N.S0028
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 TDMA 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 B.1.3.28 4.11.3.1 Successful Mobile Terminating ANSI-136 41 SMS (CMT) mapped to

7 GSM SMS

N.S0028
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
1
TDMA TDMA GSM
MC HLR IIF MSC/ MS
VLR
SMS
Delivery
a
SMSREQUEST
b
smsrequest
c
SMDPP (CMT)
d
e
SMS Delivery
f
SMS Delivery Ack
g
h
smdpp [ACK]
i
2
3 Figure 77: Successful Mobile Terminating ANSI-136 41 SMS (CMT) mapped to GSM SMS
4
5 a. The ANSI-136 41 Message Center (MC) receives a short message for a specific subscriber.
6 Note: This step is shown for completeness only and is not repeated in subsequent call flows.
7
8 b. The Message Center sends an SMS Request message to the ANSI-41 HLR of the short
9 message recipient to request a routing address for delivering the short message to that
10 subscriber.
11

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

27 Mapped to GSM SMS
28
29

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

N.S0028
1 B.1.3.30 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 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 routes it to the VMSC. If the message received is in the CMT format, the IIF maps this information
16 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 [4] 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”, and
25 the Memory Capacity Exceeded Flag (MCEF) shall be set if the error cause is “memory capacity
26 exceeded”. Additionally, the IIF emulating the ANSI-41 MSC shall set and store the SMS
27 Delivery Pending flag with the MC parameters received in the SMDPP (for later delivery in the

N.S0028
1 SMSNOT) – note that this “SMS Delivery Pending” flag/data serves the same purpose as a GSM
2 HLR’s “Message Waiting Data” flag/data. [However, note that if an ANSI-41 REGCAN is received
3 from the ANSI-41 HLR before the SMS Delivery Pending Flag is cleared, then the regcanc
4 response shall contain the SMS_MessageWaitingIndicator, and all flags are cleared (i.e., MNRF,
5 MCEF, and SMS Delivery Pending Flag)].
6
7

N.S0028
1 B.1.3.31 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 MIN (MSISDN) or IMSI of the mobile station and SMS Notification Indicator.
10 address).
12 d. Upon receipt of the SMDPP message, the IIF examines the GSM 03.40 HLR flags (MNRF/MCEF)
13 and determines that the MS is unable to receive a Short Message. The IIF indicates this fact in
14 the SMDPP Return Result. It includes the cause for the failure in the SMS_CauseCode
15 parameter of the SMDPP Return Result. The IIF shall set & store the SMS Delivery Pending Flag
16 with the data received in the SMDPP message (for later delivery in the SMSNOT).
17

N.S0028
1 B.1.3.32 4.11.3.5 Alerting for an ANSI-136 41 Subscriber in GSM Foreign Mode
2 The following scenario applies to short messages originated in either CMT or GHOST/WEMT format.
ANSI-41 GSM
MC HLR IIF VMSC
READY FOR SM
a
Ready fro SM
b
SMSNOT
c
smsnot
d
3
4 Figure 81: Alerting for an ANSI-136 41 Subscriber in GSM Foreign Mode
5
6 a. The VMSC sends a READY FOR SM (MAP V2) to the IIF, including as arguments the IMSI and
7 Alert Reason. Note: The SMS notification can also be triggered when the VMSC sends a
8 NoteMSPresent (MAP V1) or an UpdateLocation.
9 b. If the IIF has GSM 03.40 flags set, then these flags shall be cleared according to the “alert
10 reason”; that is, if the “alert reason” is “memory available”, then both the MCEF and MNRF flags
11 are cleared, and if the “alert reason” is “MS present”, then the MNRF flag is cleared. If the
12 UpdateLocation is received, then the MNRF flag is cleared. The IIF sends a Ready for SM
13 response to the VMSC with no arguments.
14 c. If the IIF has the SMS Delivery Pending Flag set, and if the MCEF flag is not set, then the IIF
15 sends a SMSNOT to each of the subscriber’s MCs stored with the SMS Delivery Pending Flag.
16 The SMSNOT shall contain; the MIN (MSISDN) as mapped from the IMSI, ESN, and
17 SMS_Address containing the IIF address.
18 d. The MC sends a SMSNOT Return Result to the IIF, then the IIF clears the SMS Delivery Pending
19 Flag, then proceeds to send the mobile station a mobile terminated GHOST/WEMT teleservice
20 message according to 4.11.3.2.
21
22 4.11.4 Mobile Terminated SMS in ANSI-41 Foreign Mode
23 This section describes the message flows for delivering a CMT or GHOST/WEMT teleservice when
24 the mobile station is operating in ANSI-41 Foreign Mode. Since on the TDMA ANSI-41 side, the short
25 message may need to be in CMT or GHOST/WEMT format, the IIF has to convert the GSM SMS to
26 either CMT or GHOST/WEMT.
27

N.S0028
1 B.1.3.33 4.11.4.1 Successful GSM SMS mapped to ANSI-136 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
3 Figure 82: Successful GSM SMS mapped to ANSI-136 41 (CMT) SMS

4 a. The GSM Short Message Service Center (SMSC) receives a short message for a specific
5 subscriber. Note: This step is shown for completeness only and is not repeated in subsequent
6 call flows.
7
8 b. The SMS-GMSC originates a Send Routing Info for Short Message to the GSM HLR of the short
9 message recipient to request a routing address for delivering the short message to that
10 subscriber.
11
12 c. Since the subscriber has a current valid location stored in the HLR, the HLR returns it to the
13 SMS-GMSC in the Send Routing Info for Short Message Result message.
14
15 d. The SMS-GMSC then sends a Forward Short Message to the IIF, seen as the serving GSM
16 MSC/VLR.
17
18 e. Upon reception of the Forward Short Message from the SMS-GMSC, the IIF originates a Short
19 Message Delivery Point to Point message to the serving ANSI-41 MSC/VLR after having
20 translated the short message into IS-136 41 CMT format. The IIF is then acting as an ANSI-136
21 41 Message Center.
22
23 f. The serving ANSI-41 MSC/VLR sends the short message to the mobile station and an
24 acknowledgement is sent back to the MSC/VLR.
25

N.S0028
1 g. The serving ANSI-41 MSC/VLR sends the result of the Short Message Delivery Point to Point
2 message to the IIF.
3
4 h. The IIF sends the result of the Forward Short Message to the GSM SMS-GMSC.
5
6

N.S0028
1 B.1.3.34 4.11.4.2 Successful GSM SMS mapped to ANSI-136 41 (GHOST/WEMT) SMS
2 This method uses the tunneling concept. Instead of translating the GSM SMS to an ANSI-136 41
3 CMT SMS format, the IIF shall package the GSM SMS into an ANSI-136TDMA SMS with the
4 teleservice GHOST (GSM Hosted SMS Teleservice) or CDMA SMS with teleservice WEMT..
5
6
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
7 Figure 83: Successful GSM SMS mapped to ANSI-136 41 (GHOST/WEMT) SMS

8
9 a. The SMSC receives a request to deliver a short message to a GSM subscriber. It sends to the
10 GSM HLR a SEND ROUTING INFO FOR SM, including as arguments the MSISDN, Priority, and
11 Service Centre address.
12 b. The HLR determines if the message shall be forwarded to the MS and sends a response back to
13 the SMSC in a Send Routing Info for SM, including as arguments the IMSI of the MS and
14 Network Node Number of the IIF.
15 c. The SMSC originates a FORWARD SHORT MESSAGE to the address provided by the HLR (i.e.,
16 IIF), including as arguments the IMSI, Service Centre Address, and GSM SMS-DELIVER PDU
17 (and optionally if more messages are to be sent).
18 Upon receipt of the FORWARD SHORT MESSAGE, the IIF shall build an ANSI-41 SMDPP ,
19 encapsulating the GSM SMS transfer PDU in the GHOST/WEMT teleservice. The IIF shall route
20 the SMDPP message to the serving MSC. The serving MSC maps the SMDPP message into an
21 R-DATA message and sends it to the mobile station over the TDMA or CDMAANSI-136 air

N.S0028
1 interface. The mobile station shall acknowledge receipt of the R-DATA message and
2 GHOST/WEMT teleservice by sending an R-DATA ACCEPT message to the MSC.
3
4 d. After receiving the R-DATA ACCEPT message, the serving MSC sends a positive
5 acknowledgement SMDPP Return Result to the IIF.
6 e. The IIF maps the received SMDPP Return Result to a Forward Short Message, and sends it to
7 the GSM SMSC.
8 f. The SMSC send a REPORT SM DELIVERY STATUS to the HLR, including as arguments the
9 MSISDN, SMSC Address, and Successful Transfer. The SMSC sends this message based on
10 the procedures described in GSM 03.40 [4] and GSM 09.02 [6].
11 g. The HLR shall set the appropriate flags as specified in the GSM specifications (GSM 09.02 and
12 03.40), then send a Report SM Delivery Status to the SMSC.
13 B.1.3.35 4.11.4.3 Unsuccessful GSM SMS mapped to ANSI-136 41 SMS (Failure at MS)
14 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
15 Figure 84: Successful GSM SMS mapped to ANSI-136 41 SMS (Failure at MS)
16
19 Service Center address.

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

N.S0028
GSM ANSI-41
SMSC HLR IIF MSC

a

b
c
SMDPP
d
smdpp [NAK]
e
f
g
h
1 Figure 85: Unsuccessful Delivery to GSM Subscriber (Postponed at MSC)

11 d. Upon receipt of the FORWARD SHORT MESSAGE, the IIF builds an ANSI-41 SMDPP message,
13 serving MSC. The IIF can also convert the message into ANSI-136 41 CMT format. The
14 addressed MS is temporarily unavailable for short message delivery and notification was
15 requested.
16 e. The MSC responds with a negative acknowledgement SMS_CauseCode carried in the SMDPP
17 Return Result indicating delivery is postponed and returns it to the source of the corresponding
18 SMDPP (i.e., IIF). The MSC sets its SMS Delivery Pending Flag.
19 f. The IIF sets the SMS Delivery Pending Flag in the IIF and maps the received SMDPP Return
20 Result into a Forward Short Message and sends it to the SMSC, after mapping the
21 SMS_CauseCode to the appropriate GSM MAP error.
22 g. The SMSC sends a REPORT SM DELIVERY STATUS to the HLR, including as arguments the
23 MSISDN, SMSC Address, and Error Cause. The SMSC sends this message based on the
24 procedures described in GSM 03.40 [4] and GSM 09.02 [6].

N.S0028
1 h. The HLR shall set the appropriate flags as specified in the GSM specifications (GSM 09.02 and
3

N.S0028
1 B.1.3.37 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)

8 the SMSC in a Send Routing Info for SM, including as arguments the IMSI of the MS and Network
9 Node Number of the 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 Message
15 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 [4] and GSM 09.02 [6].
21 B.1.3.38 4.11.4.6 Alerting for a GSM Subscriber in ANSI-41 Foreign Mode
22 In the event that the delivery of the short message to the ANSI-41 network is not possible, the IIF
23 shall be notified by the serving ANSI-41 MSC/VLR when the subscriber is available again. This shall
24 be done by receiving a Registration Notification or an SMS Notification message. This is illustrated in

N.S0028
1 the following diagram. The following scenario applies to short messages delivered in either CMT or
2 GHOST/WEMT format.
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
3
4 Figure 87: Alerting for a GSM Subscriber in ANSI-41 Foreign Mode
5 a. The IIF receives either (1) an SMSNOT, or (2) a REGNOT when the ANSI-41 SMS Delivery
6 Pending Flag is set at the IIF or the SMS_Address parameter is present in the REGNOT.
7 b. The IIF alerts the GSM HLR by sending a READY FOR SM including as arguments the IMSI and
8 MS-Present.
9 c. The HLR shall send a Ready for SM to the IIF. If the SMS Waiting Indicator flag is set in the IIF,
10 then it is cleared.
11 d. The IIF returns a Return Result acknowledgement message.
12 e. The HLR originates an ALERT SERVICE CENTRE to the SMSC address stored in the HLR,
13 including as arguments the MSISDN, and SMSC Address.
14 f. The SMSC sends an Alert Service Centre to the HLR, then proceeds to send the mobile station a
15 mobile terminated GSM SMS message according to 4.11.4.2.
16

N.S0028
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 scenarios
5 apply to short messages delivered to the MC in either CMT or GHOST/WEMT format.
6 B.1.3.39 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 (i.e.,
9 IIF), including as arguments the Service Centre Address, MSISDN and GSM SMS-SUBMIT PDU.
10 b. Upon receipt of the FORWARD SHORT MESSAGE, the IIF builds an ANSI-41 SMDPP message,
12 originator’s home MC. The IIF can also map the Forward Short Message into a CMT short
13 message.
14 c. The MC sends a positive acknowledgement SMDPP Return Result to the IIF.
15 d. The IIF maps the received SMDPP Return Result to a Forward Short Message, and sends it to
16 the VMSC.
17
18

N.S0028
1 B.1.3.40 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 b. Upon receipt of the FORWARD SHORT MESSAGE, the IIF builds an ANSI-41 SMDPP message
8 MC. The IIF can also map the Forward Short Message into a CMT short message.
9 c. The MC sends a negative acknowledgement SMDPP Return Result to the IIF.
10 d. The IIF maps the received SMDPP Return Result to a Forward Short Message with the
11 appropriate cause code value, and sends it to the VMSC.
12
13

N.S0028
1 B.1.3.41 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 b. Upon receipt of the FORWARD SHORT MESSAGE, the IIF builds a negative acknowledgement
8 Forward Short Message and sends it to the VMSC.
9
10 4.11.6 Message Flows for Mobile Originated SMS in ANSI-41 Foreign Mode
12 message center when the mobile station is operating in ANSI-41 Foreign Mode. The following
13 scenarios apply to short messages originated in either CMT or GHOST/WEMT format.
14

N.S0028
1 B.1.3.42 4.11.6.1 Successful Mobile Originated Delivery
ANSI-41 GSM
VMSC HLR IIF SMSC
SMDPP
a

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

3 a. The VMSC originates a SMDPP invoke to the address provided by the MS (i.e., IIF), including as
4 arguments the Teleservice Server Address, MIN (MSISDN), and GSM SMS-SUBMIT PDU
5 encapsulated in the GHOST/WEMT teleservice. The mobile originated message can also be in
6 the CMT format.
7 b. Upon receipt of the SMDPP invoke, the IIF builds a FORWARD SHORT MESSAGE, and routes it
8 to the SMSC.
9 c. The SMSC sends a positive acknowledgement Forward Short Message to the IIF.
10 d. The IIF maps the received Forward Short Message to a SMDPP Return Result and sends it to the
11 VMSC.
12

N.S0028
1 B.1.3.43 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 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, stripping
9 off the GHOST GHOST/WEMT teleservice and using the encapsulated GSM SMS transfer PDU,
10 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.
14

N.S0028
1 B.1.3.44 4.11.6.3 Unsuccessful Mobile Originated (Failure at IIF)
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 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.
11

N.S0028
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-136 41 subscriber 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 when
11 the 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 it
13 into a GSM SMS with MWN indication. This is shown in Section 4.12.1.2
14

N.S0028
1 B.1.3.45 4.12.1.1 Indicator in ANSI-41 Registration Notification Return Result mapped to

2 GSM SMS
3
4 ANSI- GSM MS
VMS IIF
41 MSC/VLR
5
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)
15 f
①
16 INSERT_SUB_DATA
g
17
Insert_sub_data
18 h
19 update location
i
20
21 Update Loc Accept
FORW.SHORT j
22 MESSAGE (MWN)
23 k
24 SMS Delivery (MWN)

l
25
SMS Delivery Ack
26 m
Forw.Short
27 Message
28 n
②
29
30 Figure 94: Indicator in ANSI-41 Registration Notification Return Result mapped to GSM SMS
31 a. The Voice Mail System (VMS) receives a voice mail for a specific subscriber.
32
33 b. The VMS send the “Message Waiting Notification” (MWN) to the ANSI-41 HLR of the voice mail
34 recipient. Note that the interface between the VMS and the ANSI-41 HLR is not standardized in
35 ANSI-41 [1]. Note also that at that point in time, the subscriber is not registered in any serving
36 system, so the HLR just keeps the information that a voice mail was received.
37
38 c. The Mobile Station accesses a serving system and originates an update location request.
39

N.S0028
1 d. The Update Location is sent from the serving GSM MSC/VLR to the IIF, seen as the GSM HLR
2 for that subscriber.
3
4 e. The IIF sends a Registration Notification to the ANSI-41 HLR of the subscriber.
5
6 f. The ANSI-41 HLR replies with the Registration Notification Return Result containing the
7 “Message Waiting Notification” information that consists of two parameters:
8 MessageWaitingNotificationCount (MWNCOUNT) and MessageWaitingNotificationType
9 (MWNTYPE). For a description of these parameters, see the ANSI-41 specifications, sections
10 6.5.2.78 and 6.5.2.79 [1].
11
12 ➀At this point, the IIF sets the MWN flag. This is an indication that Message Waiting Notification
13 is to be delivered to the Mobile Station.
14
15 g. The IIF sends Insert Subscriber Data to the serving GSM MSC/VLR. Note that there could be
16 more than one Insert Subscriber Data message depending on the subscriber profile.
17
18 h. The serving GSM MSC/VLR returns the Insert Subscriber Data result. Note that there could be
19 more than one such result message, one matching every Insert Subscriber Data message.
20
21 i. The IIF completes the location update by sending the Update Location result message to the
22 serving GSM MSC/VLR.
23
24 j. The serving GSM MSC/VLR confirms the update location to the mobile station.
25
26 k. Since the REGNOT return result from event f contained the Message Waiting Notification
27 information, this triggers the IIF to originate an SMS with MWN information by sending Forward
28 Short Message to the serving GSM MSC/VLR. The IIF is then acting as a GSM SMS-GMSC. The
29 IIF is to encode the MWN information in the SMS with three methods, namely, UDH, DCS, and
30 CPHS. See to Volume 3 for the encoding details.
31
32 l. The serving GSM MSC/VLR sends the short message with the MWN information to the mobile
33 station.
34
35 m. The mobile station acknowledges the delivery of the short message.
36
37 n. The serving GSM MSC/VLR sends the result of the Forward Short Message to the IIF.
38
39 ➁At this point, the IIF clears the MWN flag. The reception of the Forward Short Message Result
40 without error indicates that the MWN information was delivered successfully to the Mobile Station.
41

N.S0028
1 B.1.3.46 4.12.1.2 ANSI-41 Qualification Directive mapped to GSM SMS
2
3 ANSI-41
4 VMS ANSI- GSM
IIF MS
41 MSC/VLR
5
Vmail
6 Delivery
a
8 Notification”
b
9 QUALDIR (MWNCOUNT,
MWNTYPE)
10 c
qualdir ①
11
d
12 FORW.SHORT
13 MESSAGE (MWN)
e
14
SMS Delivery (MWN) f
15
16 SMS Delivery Ack g
17 Forw.Short
Message
18 h
19 ②
20
21 Figure 95: ANSI-41 Qualification Directive mapped to GSM SMS
23
26 ANSI-41 [1].
27
28 c. Since the subscriber has a current valid location stored in the HLR, the HLR initiates a
29 Qualification Directive message with the MWN information to the IIF acting as the serving ANSI-
30 41 MSC/VLR. The MWN information consists of two parameters:
32 (MWNTYPE). For a description of these parameters, see to the ANSI-41-D specifications,
33 sections 6.5.2.78 and 6.5.2.79 [1].
34
35 ① At this point, the IIF sets the MWN flag. This is an indication that Message Waiting Notification
37
38 d. The IIF sends the result of the Qualification Directive message to the ANSI-41 HLR.
39
40 e. The IIF also originates an SMS with MWN information by sending a Forward Short Message to
41 the serving GSM MSC/VLR. The IIF is then acting as a GSM SMS-GMSC. The IIF is to encode
42 the MWN information in the SMS with three methods, namely, UDH, DCS, and CPHS. See to
43 Volume 3 for the encoding details.
44

N.S0028
1 f. The serving GSM MSC/VLR sends the short message with the MWN information to the mobile
2 station.
3
4 g. The mobile station acknowledges the delivery of the short message.
5
6 h. The serving GSM MSC/VLR sends the result of the Forward Short Message to the IIF.
7
10 B.1.3.47 4.12.1.3 Handling when GSM MSC/VLR only supports GSM Phase 1 (MAP V1)
11 After the IIF has received a Qualification Directive message with MWN information or received the
12 MWN information through a Registration Notification Return Result, a Forward Short Message with
13 MWN information needs to be sent to the serving GSM MSC/VLR. This was shown in Sections
14 4.12.1.1 and 4.12.1.2. However, it is possible that the serving GSM MSC/VLR does not support the
15 MAP V2 Application Context. In this case, the IIF shall receive an ABORT message and shall re-send
16 the Forward Short Message with MWN information using MAP V1 instead of MAP V2. This is
17 illustrated in the following diagram.
18
GSM
19 IIF MSC/ MS
20 VLR
21 MWN “Information”
a
22 ① FORW.SHORT
MSG (MWN) – V2
23 b
24 ABORT
cc
25 FORW.SHORT
MSG (MWN) – V1
26 d
27
SMS Delivery (MWN)
28 e
29 SMS Delivery Ack

f
30 Forw.Short
Message
31 g
32 ②
33
34
35
36 Figure 96: Handling when GSM MSC/VLR only supports GSM Phase 1 (MAP V1)
37 a. The IIF receives Message Waiting Notification (MWN) information from a Qualification Directive
38 or a Registration Notification Return Result. This was described in Sections 4.12.1.1 and
39 4.12.1.2.
42

N.S0028
1 b. The IIF originates an SMS with MWN information by sending Forward Short Message using MAP
2 V2 to the serving GSM MSC/VLR. The IIF is then acting as a GSM SMS-GMSC. The IIF is to
3 encode the MWN information in the SMS with three methods, namely, UDH, DCS, and CPHS.
4
5 c. Since the serving GSM MSC/VLR does not support the MAP V2 Application Context, it returns an
6 Abort message to the IIF.
7
8 d. The IIF then re-sends a Forward Short Message with MWN information to the serving GSM
9 MSC/VLR, but this time using MAP V1. In this case, the MWN information can be encoded with
10 only two encoding methods, namely, DCS and CPHS.
11
12 e. The serving GSM MSC/VLR sends the short message with the MWN information to the mobile
13 station.
14
15 f. The mobile station acknowledges the delivery of the short message.
16
17 g. The serving GSM MSC/VLR sends the result of the Forward Short Message to the IIF.
18
21 B.1.3.48 4.12.1.4 Handling at SMS delivery failure at the IIF
22 This section describes the case where the error occurs at the IIF, for example, an unrecognized
23 Mobile Identity Number (MIN).
24
25 ANSI-
VMS IIF
41
26
27 Vmail Delivery
a
Notification”
29 b
QUALDIR (MWNCOUNT),
30 MWNTYPE) cc
31
Qualdir Return Error
32
33
34 Figure 97: Handling at SMS delivery failure at the IIF
36
39 ANSI-41 [1].
40
45 (MWNTYPE). For a description of these parameters, see to the ANSI-41-D specifications,
46 sections 6.5.2.78 and 6.5.2.79 [1].

N.S0028
1
2 d. An error is encountered so that the IIF cannot process the Qualification Directive message and
3 sends a Return Error message to the ANSI-41 HLR with the proper error code as per ANSI-41
4 Specifications, Chapter 6, Section 4.32.2, Table 42 [1].
5

N.S0028
1 B.1.3.49 4.12.1.5 Handling at SMS delivery failure at the MSC/VLR or at the Mobile
2 Station
3 The IIF is to keep a Message Waiting Notification (MWN) flag for each subscriber in its database. In
4 the event of a failure to deliver a short message with MWN to the mobile station, the IIF is to keep the
5 MWN flag set. Another Forward Short Message with MWN information shall be sent, triggered by the
6 reception of a subsequent GSM Update Location message, a Ready for Short Message, or a Note
7 MS Present message. This is illustrated in the following diagram.
8
9 GSM
IIF MSC/ MS
10 VLR
11 MWN “Information”
a
12
① FORW.SHORT
13 MSG (MWN) – V2
b
14
SMS Delivery (MWN)
15 cc
16 SMS Delivery Error

d
17
Error, Abort,
18 Reject, timeout
e
19
Time elapsed f
20
21 UPDATE LOCATION
g
22 READY FOR SM
(AlertReason) -V2
23 h
24 NOTE MS PRES – V1
i
25
“Acknowledgement”
26 j
FORW.SHORT
27 MSG (MWN) – V2
k
28
SMS Delivery (MWN)
29 l
30 SMS Delivery Ack
m
31 Forw.Short
Message
32 n
33 ②
34
35 Figure 98: Handling at SMS delivery failure at the MSC/VLR or at the MS
38 4.12.1.2.

N.S0028
3
5 V2 to the serving GSM MSC/VLR. The IIF is then acting as a GSM SMS-GMSC. The IIF is to
6 encode the MWN information in the SMS with three methods, namely, UDH, DCS, and CPHS.
7 See to Volume 3 for the encoding details.
8
9 c. The serving GSM MSC/VLR may attempt to deliver the short message or may immediately find
10 out that there is an error and reply (step e below) to the IIF.
11
12 d. The Mobile Station returns an error message to the SMS delivery.
13
14 e. The serving GSM MSC/VLR sends an Error, Abort or Reject message to the IIF, either resulting
15 from the reception of an error message from the MS or from an internal event such as an error or
16 a timeout. Note also, that a timeout may also occur in the IIF itself. Note that this may result in
17 the IIF setting the GSM 03.40 MNRF/MCEF flag depending on the error cause received (see
18 section 4.11.3.3 “Unsuccessful Mobile Terminated Delivery (Failure at MSC)”.
19
20 f. Time elapsed.
21
22 g. A new serving GSM MSC/VLR sends an Update Location message to the IIF acting as a GSM
23 HLR for that subscriber. Note that the normal Update Location sequence is not shown in this
24 diagram. Or it could be a
25
26 h. Ready for Short Message (MAP V2) or a
27
28 i. Note MS Present Message (MAP V1)
29
30 j. The IIF shall reply with the corresponding acknowledgement message. Note that in the case of
31 the Note MS Present message, there shall be no acknowledgement. Upon receipt of g, h, or i
32 above, the procedures in section 4.11.3.5 “Alerting for an ANSI-136 41 Subscriber in GSM
33 Foreign Mode” apply (GSM 03.40 flags may be cleared and the SMSNOT may be sent to the MC
34 if appropriate).
35
36 k. Triggered by event g, h, or i above, the IIF originates a new Forward Short Message with MWN
37 information to the serving GSM MSC/VLR. The IIF is to encode the MWN information in the SMS
38 with three methods, namely, UDH, DCS, and CPHS. See to Volume 3 for the encoding details.
39
40 l. The serving GSM MSC/VLR sends the short message with the MWN information to the mobile
41 station.
42
44
45 n. The serving GSM MSC/VLR sends the result of the Forward Short Message to the IIF.
48 4.12.2 ANSI-41 Foreign Mode
49 For the native GSM subscribers roaming in ANSI-41 networks, there are two implementation options.
50 The GSM SMS containing the Message Waiting Notification information is either converted by the IIF
51 to a ANSI-41 Qualification Directive with Message Waiting Notification information as shown in
52 Section 4.12.2.1, or converted to a GHOST or WEMT ANSI-136 41 short message as shown in
53 Section 4.12.2.2.
54

N.S0028
1 B.1.3.50 4.12.2.1 GSM SMS mapped to ANSI-41 Qualification Directive

2
3

N.S0028
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)
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. Short Message (error: absent sub.)
Forw. Mobile
i
Term SM (error)
j
Report SM (error)
DeliveryStatus
k
1
GSM GSM GSM TDMA
SC SMS- HLR IIF MSC
GMSC
Vmail
Delivery
a
FORW. MOBILE
TERM SM (MWN)
b
SEND ROUTING
INFO FOR SM (MWN)
c
Send Routing
Info for SM
d
FORW. SHORT
MESSAGE (MWN) e
QUALDIR(MWNCOUNT,
① MWNTYPE)
f
(MWN delivered to
Mobile Station) g
Qualdir
h
i
Forw. Mobile
Term SM (error)
j
Report SM (error)
DeliveryStatus
k
2
3 Figure 99: GSM SMS mapped to ANSI-41 Qualification Directive
4 a. The GSM Service Center (SC) receives a voice mail for a specific subscriber.
5

N.S0028
1 b. The SC sends the Forward Mobile Terminating Short Message with Message Waiting Notification
2 (MWN) information to the GSM SMS-GMSC.
3
4 c. The GSM SMS-GMSC enquires about the subscriber location by sending the Send Routing
5 Information For Short Message to the HLR.
6
7 d. The HLR replies with the Send Routing Information For Short Message result. It is assumed that
8 the native GSM subscriber has already made a registration in the ANSI-41 MSC/VLR.
9
10 e. The GSM SMS-GMSC originates an SMS with MWN information by sending Forward Short
11 Message to IIF then acting as a serving GSM MSC/VLR. This requires GSM MAP phase 2 or
12 higher.
13
15 is to be delivered to the Mobile Station. If the GSM SMS-GMSC only supports GSM MAP phase 1
16 and delivers MWN via pure text SMS, then a pure text SMS shall be delivered to the IIF. The IIF
17 shall then translate it into a CMT or GHOST/WEMT IS-136 SMS. Note that this then becomes a
18 simple SMS mapping covered in Section 4.12.2.2.
19
20 f. Upon reception of the Forward Short Message with MWN information, the IIF shall initiate a
21 Qualification Directive message with MWN information to the serving ANSI-41 MSC/VLR. The IIF
22 is then acting as an ANSI-41 HLR. The MWN information consists of two parameters:
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 [1]. Alternatively, a GHOST/WEMT short message could be sent
26 instead of the Qualification Directive message (see Section 4.12.2.2) if the IIF has the possibility
27 to confirm that the Mobile Station is SMS-capable.
28
29 g. In this step, the MWN information shall be delivered to the mobile station.
30
31 h. The serving ANSI-41 MSC/VLR sends the Qualification Directive Return Result to the IIF. Note
32 that this result message does not guaranty that the MWN information was delivered successfully
33 to the Mobile Station, it just means that the MSC/VLR received the Qualification Directive
34 message, therefore the MWN flag shall not be cleared at this point by the IIF.
35
36 i. The IIF sends the result of the Forward Short Message to the GSM SMS-GMSC with error code
37 “absent subscriber” so that the home system assumes that the delivery failed in case the
38 subscriber goes back to the home system without having retrieved the mail messages. This way,
39 at the reception of the Update Location message, the HLR shall send an Alert-SC message so
40 that the MWN information (in a short message) is once again sent to the Mobile Station.
41
42 j. The SMS-GMSC sends the result of the Forward Mobile Terminating Short Message to the
43 Service Center. Note that depending on the Service Center implementation, this may cause the
44 SMS to be re-sent periodically instead of waiting for the ALERTSC message indicating that the
45 subscriber is again available to receive short messages.
46
47 k. The SMS-GMSC reports the error to the HLR, which shall set the proper flags as per GSM 03.40
48 [4] so that an Alert-SC message is sent when necessary as explained in step i above.
49 B.1.3.51 4.12.2.2 GSM SMS mapped to TDMA ANSI-41 SMS using GHOST or WEMT
50 Teleservice
51 This method uses the tunneling concept. Instead of translating the GSM SMS with Message Waiting
52 Notification information to an ANSI-41 Qualification Directive with MWN information, the IIF shall
53 package the GSM SMS into an ANSI-136 41 SMS with the new teleservice GHOST (GSM Hosted
54 SMS Teleservice) or WEMT.

N.S0028
1 Event g only works with Mobile Stations (MS) capable of handling GHOST or WEMT. The MS shall
2 remove the ANSI-136 41 part of the message (the envelope) and send the GSM SMS Packet Data
3 Units (PDU) to the GSM part of the mobile station to handle the GSM SMS, in this case, containing
4 the Message Waiting Notification information. Specifically, the ANSI-41 MSC shall convert the
5 SMDPP to an R-DATA message which has a HLPI (higher layer protocol identifier) that indicates
6 GHOST/WEMT. The payload of the R-DATA message is the GSM SMS which is effectively identified
7 as the target application whenever HLPI = GHOST/WEMT.

N.S0028
GSM GSM GSM ANSI-41

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

N.S0028
2
5
6 c. The GSM SMS-GMSC inquires about the subscriber location by sending the Send Routing
8
11
13 Message to IIF then acting as a serving GSM MSC/VLR.
14
15 This requires GSM MAP phase 2 or higher. If the GSM SMS-GMSC only supports GSM MAP
16 phase 1 and delivers MWN via pure text SMS, then a pure text SMS shall be delivered to the IIF.
17 The IIF shall then translate it into a CMT or GHOST/WEMT IS-136ANSI-41 SMS. Note that this
18 then becomes a simple SMS mapping covered in Section 4.11.
19
20 f. Upon reception of the Forward Short Message with MWN information, the IIF shall initiate a Short
21 Message Delivery Point to Point with Teleservice GHOST/WEMT to the serving ANSI-41
22 MSC/VLR. The IIF is then acting as an ANSI-136 41 Message Center (MC). Inside of this
23 GHOST/WEMT short message is the GSM short message containing the MWN information.
24
25 g. In this step, the GHOST/WEMT Short Message containing the GSM short message containing
26 the MWN information shall be delivered to the mobile station.
27
28 h. The serving ANSI-41 MSC/VLR sends the Short Message Delivery Point to Point Return Result
29 to the IIF.
30
31 i. The IIF sends the result of the Forward Short Message to the GSM SMS-GMSC.
32
34 Service Center.
35 B.1.3.52 4.12.2.3 Clearing of MWN Information after Retrieval of Messages while in ANSI-
36 41 Foreign Mode – QualDir Method
37 This section describes the case where the messages are retrieved while a GSM subscriber is still
38 roaming in ANSI-41 foreign mode.
39

N.S0028
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
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
1
GSM GSM GSM TDMA
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) e
QUALDIR(MWNCOUNT,
MWNTYPE)
f
(mwn delivered to
Mobile Station) g
Qualdir
h
i
Forw. Mobile
Term SM (error)
j
Report SM (error)
DeliveryStatus k
2
3 Figure 101: Clearing of MWN Information after Retrieval of Messages while in ANSI-41 Foreign
4 mode – Qualdir Method
5 a. The voice mail messages are retrieved from the GSM subscriber.

N.S0028
1
3 (MWN) information set to “clear” to the GSM SMS-GMSC.
4
7
9 the native GSM subscriber has already made a registration in the ANSI-41 MSC/VLR. Another
10 requirement is that the Service Center sets the priority of this SMS to “high” to make sure that the
11 SMS is sent (Section 3.2.5 of GSM 03.40). This is necessary since the IIF had previously
12 responded with absent subscriber and the HLR had set some flags that could have prevented the
13 delivery of this new SMS.
14
15 e. The GSM SMS-GMSC originates an SMS with MWN information (set to “clear”) by sending
16 Forward Short Message to IIF then acting as a serving GSM MSC/VLR. This requires a GSM
17 phase 2 support or higher.
18
19 f. Upon reception of the Forward Short Message with MWN information (set to “clear”), the IIF shall
20 initiate a Qualification Directive message with MWN information (set to “clear”) to the serving
21 ANSI-41 MSC/VLR. The IIF is then acting as an ANSI-41 HLR. The MWN information consists of
22 two parameters: MessageWaitingNotificationCount (MWNCOUNT) and
23 MessageWaitingNotificationType (MWNTYPE). For a description of these parameters, see to the
24 ANSI-41-D specifications, sections 6.5.2.78 and 6.5.2.79 [1].
25
26 g. In this step, the MWN information (set to “clear”) shall be delivered to the mobile station.
27
29 that this result message does not guaranty that the MWN information (set to ”clear”) was
30 delivered successfully to the Mobile Station, it just means that the MSC/VLR received the
31 Qualification Directive message, so the MWN flag shall not be cleared at this point by the IIF.
32
35 subscriber goes back to the home system without having received the clearing notification from
36 the serving MSC. This way, at the reception of the Update Location message, the HLR shall send
37 an Alert-SC message so that the MWN information (in a short message) is once again sent to the
38 Mobile Station.
39
44
45 k. The SMS-GMSC reports the error to the HLR, which shall set the proper flags as per GSM 03.40
46 [4] so that an Alert-SC message is sent when necessary as explained in step i above.
47

N.S0028
1 B.1.3.53 4.12.2.4 Handling at SMS delivery failure at the IIF
GSM GSM GSM

SC SMS- HLR IIF
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)
e
Forw. Short Message (error)
f
Forw. Mobile
Term SM (error) g
Report SM (error)
DeliveryStatus
h
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 error
20 and sends the result of the Forward Short Message to the GSM SMS-GMSC with the proper error
21 code as per GSM Specifications 09.02 [6].
22
23 g. The SMS-GMSC sends the result of the Forward Mobile Terminating Short Message to the
24 Service Center.
25
26 h. The SMS-GMSC reports the error to the HLR, which sets the proper flags as per GSM 03.40 [4]
27 so that an Alert-SC message is sent when necessary.
28

N.S0028
1 B.1.3.54 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)
c
Send Routing
Info for SM
d
FORW. SHORT
MESSAGE (MWN)
QUALDIR(MWNCOUNT,
e
① MWNTYPE)
f
g
h
Forw. Mobile
Term SM (error)
Report SM (error)
i
DeliveryStatus
j
3
GSM GSM GSM TDMA
SC SMS- HLR IIF MSC
GMSC
Vmail
Delivery
a
FORW. MOBILE
TERM SM (MWN)
b
SEND ROUTING
INFO FOR SM (MWN)
c
Send Routing
Info for SM
d
FORW. SHORT
MESSAGE (MWN) e
QUALDIR(MWNCOUNT,
① MWNTYPE)
f
g
h
Forw. Mobile
Term SM (error)
i
Report SM (error)
DeliveryStatus
j
4
5 Figure 103: Handling at SMS delivery failure at the MSC/VLR Qualdir Method
7

N.S0028
3
5 Information for Short Message to the HLR.
6
7 d. The HLR replies with the Send Routing Information for Short Message result. It is assumed that
9
11 Message to IIF then acting as a serving GSM MSC/VLR. This requires GSM phase 2 support or
12 higher.
13 ①At this point, the IIF sets the MWN flag. This is an indication that Message Waiting Notification
15
16 f. The IIF shall also initiate a Qualification Directive message with MWN information to the serving
17 ANSI-41 MSC/VLR. The IIF is then acting as an ANSI-41 HLR. The MWN information consists of
18 two parameters: MessageWaitingNotificationCount (MWNCOUNT) and
19 MessageWaitingNotificationType (MWNTYPE). For a description of these parameters, see to the
20 ANSI-41-D specifications, sections 6.5.2.78 and 6.5.2.79 [1].
21
22 g. The serving ANSI-41 MSC/VLR encounters an error and sends the Qualification Directive Return
23 Error to the IIF, as per the ANSI-41 Specifications, Chapter 6, Section 4.32.2, Table 42.
24 h. The IIF sends the error result of the Forward Short Message to the GSM SMS-GMSC.
25
26 i. The SMS-GMSC sends the result of the Forward Mobile Terminating Short Message to the
27 Service Center.
28
29 j. The SMS-GMSC reports the error to the HLR which sets the proper flags as per GSM 03.40 [4]
30 so that an Alert-SC message is sent when necessary.
31
32 B.1.3.55 4.12.2.6 Handling at SMS delivery failure at the MSC/VLR – GHOST/WEMT SMS
33 Method
34

N.S0028
GSM GSM GSM TDMA

SC SMS- HLR IIF MSC
GMSC
Vmail
Delivery
a
FORW. MOBILE
TERM SM (MWN)
b
SEND ROUTING
INFO FOR SM (MWN)
c
Send Routing
Info for SM
d
FORW. SHORT
MESSAGE (MWN) e
SMDPP (GHOST, MWN)
f
smdpp (error)
g
h
Forw. Mobile
Term SM (error)
i
Report SM (error)
DeliveryStatus j
1
2 Figure 104: Handling at SMS delivery failure at the MSC/VLR – GHOST/WEMT SMS Method
4
7
9 Information for Short Message to the HLR.
10
11 d. The HLR replies with the Send Routing Information for Short Message result. It is assumed that
13
16 higher.
17
18 f. Upon reception of the Forward Short Message with MWN information, the IIF shall initiate a Short
19 Message Delivery Point to Point with Teleservice GHOST/WEMT to the serving ANSI-41
20 MSC/VLR. The IIF is then acting as an ANSI-136 41 Message Center (MC). Inside of this GHOST
21 or WEMT short message is the GSM short message containing the MWN information.
22
23 g. The serving ANSI-41 MSC/VLR encounters an error and sends the Short Message Delivery Point
24 to Point Return error to the IIF.
25
26 h. The IIF sends the result of the Forward Short Message to the GSM SMS-GMSC with the proper
27 error code. .
28
29 i. The SMS-GMSC sends the result of the Forward Mobile Terminating Short Message to the
30 Service Center.

N.S0028
1
2 j. The SMS-GMSC shall report the error to the HLR.
3

N.S0028
1 B.1.3.56 4.12.2.7 GSM SMS mapped to ANSI-41 Qualification Directive and to

2 Registration Notification Return Result

N.S0028
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
MESSAGE (MWN) QUALDIR
(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
1

N.S0028
GSM GSM GSM TDMA IIF TDMA

SC SMS- HLR MSC 2 MSC 1
GMSC
Vmail
Delivery
a
FORW. MOBILE
TERM SM (MWN)
b
SEND ROUTING
INFO FOR SM (MWN)
c
Send Routing
Info for SM
d
FORW. SHORT
QUALDIR
MESSAGE (MWN) e
(MWNCOUNT,
MWNTYPE)
① f
(MWN delivered to
Mobile Station) g
h
i
Forw. Mobile
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
1
3 Notification Return Result
5
7 (MWN) information to the GSM SMS-GMSC
8
11
14
17 higher.
18 ①At this point, the IIF sets the MWN flag. This is an indication that Message Waiting Notification
19 is to be delivered to the Mobile Station. If the handset only supports GSM phase 1, then a pure
20 text SMS shall be delivered to the IIF. The IIF shall then translate it into a CMT or GHOST/WEMT
21 IS-136ANSI-41 SMS. Note that this then becomes a simple SMS mapping covered in Section
22 4.11.

N.S0028
1
2 f. Upon reception of the Forward Short Message with MWN information, the IIF shall initiate a
3 Qualification Directive message with MWN information to the serving ANSI-41 MSC/VLR. The IIF
4 is then acting as an ANSI-41 HLR. The MWN information consists of two parameters:
6 (MWNTYPE). For a description of these parameters, see to the ANSI-41 specifications, sections
7 6.5.2.78 and 6.5.2.79 [1]. Alternatively, a GHOST/WEMT short message could be sent instead of
8 the Qualification Directive message (see Section 4.12.2.2) if the IIF has the possibility to confirm
9 that the Mobile Station is SMS-capable.
10
11 g. In this step, the MWN information shall be delivered to the mobile station.
12
14 that this result message does not guaranty that the MWN information was delivered successfully
15 to the Mobile Station, it just means that the MSC/VLR received the Qualification Directive
16 message, therefore the MWN flag shall not be cleared at this point by the IIF.
17
20 subscriber goes back to the home system without having retrieved the mail messages. This way,
21 at the reception of the Update Location message, the HLR shall send an Alert-SC message so
22 that the MWN information (in a short message) is once again sent to the Mobile Station.
23
28
29 k. The SMS-GMSC reports the error to the HLR, which sets the proper flags as per GSM 03.40 [4]
30 so that an Alert-SC message is sent when necessary as explained in step i above.
31
32 l. Time elapses before the MS re-registers.
33
34 m. A Registration Notification is sent from the serving ANSI-41 MSC 2 to the IIF.
35
36 n. The IIF discovers that the MWN flag is still set. The IIF sends back the MWN in the Registration
37 Notification Return Result along with the other registration information (e.g. other Profile
38 parameters) to the serving ANSI-41 MSC/VLR. The IIF is then acting as an ANSI-41 HLR. The
39 MWN information consists of two parameters: MessageWaitingNotificationCount (MWNCOUNT)
40 and MessageWaitingNotificationType (MWNTYPE). For a description of these parameters, see to
41 the ANSI-41 specifications, sections 6.5.2.78 and 6.5.2.79 [1].
42
43 o. In this step, the MWN information shall be delivered to the mobile station. Since there is no
44 acknowledgement from the regnot Return Result, there is no guarantee that the MWN information
45 was delivered successfully to the Mobile Station. The MWN flag shall not be cleared at this point
46 by the IIF.
47

N.S0028
1 4.13 GPRS in GSM Foreign Mode

2 This section describes the support of GPRS service for ANSI-136 41 subscribers 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 network
10 through either a GSM MSC (for GSM-CS service) or an SGSN (for GPRS service) or through both.
11 The attachments may be done in series, i.e. first one service and then another, or simultaneously.
12 The IIF may implement a timer, GPRS_LU, to reduce the number of location updates in the ANSI-41
13 network when an MS is capable of both MSC-CS and GPRS services. If the timer is supported, then
14 when a Location Update is received from the SGSN for an MS that is capable of both GSM_CS and
15 GPRS service, the IIF starts the timer and then performs the ‘Insert Subscriber Data’ procedure to the
16 SGSN. The IIF sends the REGNOT to the HLR only after the expiry of the timer or the receipt of the
17 Location Update from the GSM MSC.
18 When the timer is not started, either because :
19 - it is not supported; or
20 - the MS is provisioned for GPRS only service; or
21 - the MS is already CS attached; or
22 - the IIF does not support multiple MSCIDs;
23 then the IIF sends the REGNOT to the HLR and waits for a response before performing the ‘Insert
24 Subscriber Data’ procedure to the SGSN.
25 The IIF may support multiple MSCIDs to separately identify each GSM MSC and each SGSN when
26 an MS is attached for either or both services. When multiple MSCIDs are supported the IIF shall
27 notify the ANSI-41 HLR whenever the MS registers on a different SGSN, GSM MSC or both.
28 An IIF that does not support multiple MSCIDs shall always convey its own identity towards the ANSI-
29 41 HLR.
30 Subscriber Data Management procedures shall follow similar procedures as described in 4.4.2. In
31 the case of subscriber deletion, it shall also result in the deletion of any GPRS subscription data in the
32 IIF, for that subscriber. In this case, the IIF shall also send a Cancel Location Request to the serving
33 SGSN. The ANSI-41 HLR does not have the capability to request the modification of GPRS
34 subscription data in the IIF. Modification of GPRS subscriber data in the IIF shall be in accordance
35 with GSM 09.02 [6] via an OMC directly connected to the IIF.
36 4.13.1 Location Registration ScenariosIn each of the following scenarios, the following
37 interactions are not shown :-
38 Interactions between SGSNs
39 Interactions between SGSNs and GGSNs
40 Existing procedures defined in GSM 03.60 [10], describing the actions between SGSNs or between
41 an SGSN and a GGSN for scenarios involving interaction between those functional elements also
42 apply.

N.S0028
1 Existing procedures and timers defined in GSM 03.60 [10], describing the actions between the SGSN
2 and the GSM HLR also apply between the SGSN and the IIF (emulating a GSM HLR).
3 The combined attach and location registration procedures described, require support of the optional
4 Gs interface as described in GSM 03.60[10].
5 It should be noted that certain scenarios may only be relevant to certain MS types. For a full
6 description of the various MS types see GSM 03.60 [10].
7 4.13.1.1 GPRS Attach (not currently registered)
8 If an MS requests GPRS service when currently not registered in the IIF, the MS performs a GPRS
9 attach request using its IMSI. The IIF acts like a GPRS HLR/AuC in this case. The subscriber's
10 ANSI-41 HLR has no knowledge of this request, but the IIF makes it aware of the attachment to an
11 SGSN via a REGNOT. If timer GPRS_LU is used then the message flow is as shown in Figure 106.
12 If timer GPRS_LU is not used then the message flow is as shown in Figure 107.
MS SGSN IIF HLR
GPRS Attach Req

(IMSI) a
Authentication Info
b
c
Authentication Req
d
Update GPRS Location Req
f
(IMSI, SGSN Address)
Insert Sub Data g
Insert Sub Data Ack

h
Update GPRS Location Ack i

GPRS_LU
REGNOT
j
regnot
k
GPRS Attach Ack
ANSI-41 NETWORK l
GSM NETWORK
13 Figure 106: GPRS Attach (Option1: with timer)
14 a. MS performs a GPRS Attach. .
15 b. If the Serving GPRS Support Node (SGSN) does not have authentication information in order to
16 perform authentication i.e. authentication triplets, it requests authentication information from the
17 IIF. The IIF emulates a GSM HLR/AuC in this case supporting GPRS.

N.S0028
1 c. The IIF returns the necessary authentication information, if applicable.

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

N.S0028
MS SGSN IIF HLR
GPRS Attach Req

(IMSI) a
Authentication Info
b
c
Authentication Req
d
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
1 Figure 107: GPRS Attach (Option 2: without timer)

2
3 a. MS performs a GPRS Attach.
12 g. The REGNOT shall contain the MSID (MIN/IMSI), the ESN, the MSCID etc. If SIM-based roaming
13 is authorized, an initially provisioned, fixed ESN for this subscriber shall be passed in the
14 REGNOT to the subscriber’s HLR. The ANSI-41 HLR records the address of the IIF as the
15 serving ANSI-41 MSC. Although call delivery may not be possible, SMS delivery is made
17 h. The ANSI-41 HLR sends an acknowledgment to the registration with a regnot. The IIF may
18 ignore the CS-related profile information, since the MS is only GPRS-attached (and not GSM CS-
19 attached). Only the provisioned SMS parameters in the regnot (profile) may be mapped and sent
20 to the SGSN in an Insert Subscriber Data message.

N.S0028
1 i. The IIF validates whether the GPRS service request is authorized. Since GPRS service is
2 requested, and the subscriber is currently PS-deregistered, it initiates the GSM MAP Insert
5 Insert Subscriber Data transactions may be necessary to complete the transfer of subscriber data
6 to the SGSN.
7 j. The SGSN acknowledges the ISD Operation(s).
8 k. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the IIF
10 l. The SGSN acknowledges the GPRS Attach request.
11

N.S0028
1 4.13.1.2 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 ANSI-41
4 VLR in this case. To the subscriber's ANSI-41 HLR, the subscriber becomes registered on the IIF
5 acting as an ANSI-41 MSC. If timer GPRS_LU is used then the message flow is as shown in Figure
6 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 Figure 108: GPRS Attach when currently registered in ANSI-41 (Option 1: with timer)
8

N.S0028
2 requested, and the MS is currently PS-deregistered, it initiates the GSM MAP Insert Subscriber
3 Data Procedure towards the SGSN after the subscriber has been successfully authorized. This
4 procedure is used to download GPRS subscriber data to the SGSN. Multiple Insert Subscriber
5 Data transactions may be necessary to complete the transfer of subscriber data to the SGSN.
9 j. After the IIF’s GPRS_LU timer expires, the IIF shall send a registration notification (REGNOT)
10 to the ANSI-41 HLR. The REGNOT shall contain the MSID (MIN/IMSI), the ESN, the MSCID,
11 etc. If SIM-based roaming is authorized, an initially provisioned, fixed ESN for this subscriber
12 shall be passed in the REGNOT to the subscriber’s HLR. The ANSI-41 HLR records the
13 address of the IIF as the serving ANSI-41 MSC. Although call delivery may not be possible,
14 SMS delivery is made possible by registering the IIF as the ANSI-41 MSC with the ANSI-41
15 HLR.
16 k. The ANSI-41 HLR updates its location information and deletes the previous VLR record by
17 sending a REGCANC to the previous MSC/VLR.
18 l. The VLR acknowledges the REGCANC.
19 m. The ANSI-41 HLR sends an acknowledgment to the registration with a regnot. The IIF may
20 ignore the CS-related profile information, since the MS is only GPRS-attached (and not GSM
21 CS-attached).
22 If a negative regnot response is received from the ANSI-41 HLR, (then as a Network option) the
23 IIF may perform an initiated detach procedure as described in section 4.13.2.6.
24 n. The SGSN acknowledges the GPRS Attach request.
25

N.S0028
SGSN HLR MSC/

MS IIF
VLR
GPRS Attach Req
(IMSI) a
Authentication Info
b
c
Authentication Req
d
f
(IMSI, SGSN
Address) REGNOT
g
(MSID, ESNF,
MSCID or MSCIN) REGCAN h
regcan
i
regnot j
Insert Sub Data

k
Insert Sub Data Ack

l
Update GPRS Location Ack

m
GPRS Attach Ack

n
1 Figure 109: GPRS Attach when currently registered in ANSI-41 (Option 2: without timer)
2
3 a. MS performs a GPRS Attach. .
12 g. The REGNOT shall contain the MSID (MIN/IMSI), the ESN, the MSCID, etc. If SIM-based
13 roaming is authorized, an initially provisioned, fixed ESN for this subscriber shall be passed in the
14 REGNOT to the subscriber’s HLR. The ANSI-41 HLR records the address of the IIF as the

N.S0028
1 serving ANSI-41 MSC. Although call delivery may not be possible, SMS delivery is made
3 h. The ANSI-41 HLR updates its location information and deletes the previous VLR record by
4 sending a REGCANC to the previous MSC/VLR.
5 i. The VLR acknowledges the REGCANC.
6 j. The ANSI-41 HLR sends an acknowledgment to the registration with a regnot.
7 k. The IIF validates whether the GPRS service request is authorized. Since GPRS service is
12 l. The SGSN acknowledges the ISD Operation(s).
15 n. The SGSN acknowledges the GPRS Attach request.
16
17

N.S0028
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
a
(IMSI)
c
Authentication Req
d
f
Cancel Location
g
Cancel Location Ack
h
Insert Sub Data
i
Insert Sub Data Ack
j
Update gprs location ack GPRS_LU
k
REGNOT
l
REGCANC
m
regcanc
n
Regnot ack
o
inter-SGSN Routing Area Update Accept
p
ANSI-41
GPRS NETWORK 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.
15 g. The IIF (acting like a GPRS HLR) shall also send a Cancel Location to the previous SGSN.

N.S0028
1 h. The IIF shall receive a Cancel Location acknowledgement from the previous SGSN.
3 requested, it initiates the GSM MAP Insert Subscriber Data Procedure towards the SGSN after
4 the subscriber has been successfully authorized. This procedure is used to download GPRS
5 subscriber data to the SGSN. Multiple Insert Subscriber Data transactions may be necessary to
6 complete the transfer of subscriber data to the SGSN.
10 Note: Steps l,m,n & o are optional depending on whether the IIF supports multiple MSCIDs.
11 l. After the IIF’s GPRS_LU timer expires, the IIF shall send a registration notification (REGNOT) to
12 the ANSI-41 HLR. The REGNOT shall contain the MSID (MIN/IMSI), the ESN, the MSCID, etc. If
13 SIM-based roaming is authorized, an initially provisioned, fixed ESN for this subscriber shall be
14 passed in the REGNOT to the subscriber’s HLR. The ANSI-41 HLR records the address of the IIF
15 as the serving ANSI-41 MSC. Although call delivery may not be possible, SMS delivery is made
17 m. The HLR updates its location information and deletes the previous VLR record by sending a
18 REGCANC to the previous MSC/VLR, which in this case is the IIF (if in step l, the IIF sent a
19 REGNOT with a different MSCID (IIF address corresponding to the current SGSN) than the
20 MSCID sent corresponding to the previous SGSN).
21 n. The IIF acknowledges the REGCANC.
22 o. The ANSI-41 HLR sends an acknowledgment to the registration with a regnot. The IIF may
23 ignore the CS-related profile information, since the MS is only GPRS-attached (and not GSM CS-
24 attached).
25

N.S0028
1 Related to Figure 110, if a negative regnot response is received from the ANSI-41 HLR, (then as
2 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
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 order
8 to perform authentication i.e. authentication triplets, it requests authentication information
9 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.
16 h. IIF shall receive an acknowledgement for the Cancel Location.

N.S0028
1 i. If the IIF implementation supports multiple MSCIDs, then it shall send a REGNOT to the
2 ANSI-41 HLR with the MSCID corresponding to the new SGSN. Then the IIF shall correlate
3 that MSCID with the GSM MSCID when receiving mobile terminated SMS messages (so that
4 the IIF can deliver them to the SGSN).
5 j. This is a continuation of the optional procedure started in item i. IIF receives REGCANC. The
6 IIF needs to keep both the current MSCID associated to the SGSN as well as the current
7 MSCID associated to the MSC. The IIF must also keep a record of the last MSCID which
8 was sent to the ANSI-41 HLR to know that is the one stored in the ANSI-41 HLR.
9 k. This is a continuation of the optional procedure started in item i. IIF sends regcanc response.
10 l. This is a continuation of the optional procedure started in item i. IIF receives regnot
11 response.
12 m. The IIF validates whether the GPRS service request is authorized. Since GPRS service is
13 requested, it initiates the GSM MAP Insert Subscriber Data Procedure towards the SGSN
14 after the subscriber has been successfully authorized. This procedure is used to download
15 GPRS subscriber data to the SGSN. Multiple Insert Subscriber Data transactions may be
16 necessary to complete the transfer of subscriber data to the SGSN.
17 n. The SGSN acknowledges the ISD Operation(s).
18 o. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the
19 IIF returns an acknowledgement to the Update GPRS Location Request.
20 p. The SGSN acknowledges the Routing Area Update request.
21
22

N.S0028
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 MSC
4 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 Figure 112: GPRS Attach when GSM CS Attached.


N.S0028
1 g. If the IIF implementation supports multiple MSCIDs, then it shall send a REGNOT to the ANSI-41
2 HLR with the MSCID corresponding to the new SGSN.
3 h. This is a continuation of the optional procedure started in item g. IIF receives REGCANC.
4 i. This is a continuation of the optional procedure started in item g. IIF sends regcanc response.
5 j. This is a continuation of the optional procedure started in item g. IIF receives regnot response.]
14 n. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
15 The GSM MSC creates the association with the SGSN by storing the SGSN Number. The MSC
16 does not see a need to notify the IIF (emulating the GSM HLR, since there is no change to the
17 CS location update parameters).
18 o. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface by
19 sending the Accept message.
20 p. The SGSN acknowledges the GPRS Attach request from the MS.
21
22

N.S0028
1
2 4.13.1.5 Combined GSM and GPRS attach when not currently registered
3 If an MS requests a combined GSM and GPRS attach when not registered in the IIF, then the SGSN
4 first requests a GPRS location update to the IIF (acting as a GPRS HLR) and then a CS location
5 update through the GSM MSC as depicted in Figure 114.
MS SGSN IIF
MSC HLR
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
6
7 Figure 113: Combined GPRS and GSM attach (Option 1: With timer).
8 a. MS performs a GPRS attach.
16 Request contains the IMSI. The IIF starts timer GPRS LU.

N.S0028
7 j. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
8 The GSM MSC creates the association with the SGSN by storing the SGSN Number.
9 k. The MSC determines that it needs to notify the IIF (emulating the GSM HLR), since there is a
10 change to the CS location update parameters. The MSC sends the Update Location operation to
11 the IIF (emulating the GSM HLR). The IIF stops timer GPRS LU.
12 l. The IIF shall send a Registration Notification (REGNOT) to the ANSI-41 HLR to indicate the
13 changed location (MSCID associated with the new GSM MSC).
15 passed in the REGNOT to the subscriber’s HLR. This ESN may not match the currently validated
16 dynamic ESN for this subscriber, but the HLR shall also accept this fixed ESN for this subscriber.
17 m. The ANSI-41 HLR acknowledges the registration and sends back the subscriber’s information.
18 This information is for non-GPRS services.
19 n. The IIF sends MAP INSERT SUBSCRIBER DATA message(s) to the GSM MSC providing GSM
20 CS information based on the contents of the regnot (profile).
21 o. The GSM MSC acknowledges receipt of the Insert Subscriber Data information.
22 p. The IIF acknowledges the completion of the Update Location procedure and sends the Update
23 Location Acknowledgement to the GSM MSC.
24 q. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface to the
25 SGSN by sending the Accept message.
26 r. The SGSN acknowledges the combined GPRS and GSM Attach request from the MS.
27
28

N.S0028
MS SGSN IIF
MSC HLR
Combined Attach Req
(IMSI)
a
d
f
REGNOT
g
Regnot ack
h
Insert Sub Data
i
Insert Sub Data Ack
j
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 Figure 114: Combined GPRS and GSM attach (Option 2: Without timer and without support for
2 multiple MSCIDs).
3

N.S0028

10 g. The IIF shall send a Registration Notification (REGNOT) to the ANSI-41 HLR to indicate the
11 changed location.
15 h. The ANSI-41 HLR acknowledges the registration and sends back the subscriber’s information in
16 the regnot response.
25 l. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
27 m. The MSC determines that it needs to notify the IIF (emulating the GSM HLR), since there is a
29 the IIF (emulating the GSM HLR). The IIF does not send a REGNOT in this case, because it does
30 not support multiple MSCIDs.
31 n. The IIF sends MAP INSERT SUBSCRIBER DATA message(s) to the GSM MSC providing GSM
33 o. The GSM MSC acknowledges receipt of the Insert Subscriber Data information.
34 p. The IIF acknowledges the completion of the Update Location procedure and sends the Update
36 q. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface to the
38 r. The SGSN acknowledges the combined GPRS and GSM Attach request from the MS.
39
40

N.S0028
MS SGSN IIF
MSC HLR
Combined Attach Req
(IMSI)
a
d
f
REGNOT
g
Regnot ack
h
Insert Sub Data
i
Insert Sub Data Ack
j
k

1

N.S0028
MS
SGSN MSC IIF HLR

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
GPRS Attach Accept/ u
Routing Area Update
Accept v
1 Figure 115: Combined GPRS and GSM attach (Option 3: IIF supports multiple MSCIDs).
2
3

N.S0028

11 changed location (MSCID associated to the new GSM SGSN).
15 h. The ANSI-41 HLR acknowledges the registration and sends back the subscriber’s information in
16 a regnot response.
25 l. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
27 m. The MSC determines that it needs to notify the IIF (emulating the GSM HLR), since there is a
29 the IIF (emulating the GSM HLR).
30 n. The IIF shall send a Registration Notification (REGNOT) to the ANSI-41 HLR to indicate the
31 changed location (MSCID associated to the new GSM MSC).
35 o. IIF receives a REGCANC. The IIF needs to keep both the current MSCID associated to the
36 SGSN as well as the current MSCID associated to the MSC. The IIF must also keep a record of
37 the last MSCID which was sent to the ANSI-41 HLR to know that is the one stored in the ANSI-41
38 HLR.
39 p. IIF sends regcanc response.
40 q. The ANSI-41 HLR acknowledges the registration and sends back the subscriber’s information.
41 r. The IIF sends MAP INSERT SUBSCRIBER DATA message(s) to the GSM MSC providing GSM

N.S0028
1 s. The GSM MSC acknowledges receipt of the Insert Subscriber Data information.
2 t. The IIF acknowledges the completion of the Update Location procedure and sends the Update
4 u. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface to the
6 v. The SGSN acknowledges the combined GPRS and GSM Attach request from the MS.
7

N.S0028
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.
5
MS SGSN PMSC/
MSC IIF HLR Prev VLR
SGSN
a
(IMSI)
c
Authentication Req
d
f
Cancel Location
g
Cancel Location Ack
h
REGNOT i
REGCANC
j
regcanck
k
Regnot ack
l
Insert Sub Data
m
Insert Sub Data Ack
n
o
ANSI-41
GSM NETWORK GSM NETWORK

N.S0028
MS SGSN PMSC/
MSC IIF HLR Prev VLR
SGSN
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
GPRS Attach Accept/ aa
Routing Area Update
Accept bb
ANSI-41
1
2 Figure 116: Combined Inter-SGSN RA/LA update
3 a. MS sends a Routeing Area Update request
12 g. In the case of a combined attach when registered on a different MSC and SGSN, and in the case
13 of a combined inter-SGSN routing area update case when previously registered on a different
14 MSC and SGSN, the IIF (acting like a GPRS HLR) shall also send a Cancel Location to the
15 previous SGSN

N.S0028
1 i. If the IIF implementation supports multiple MSCIDs, then it shall send a REGNOT to the ANSI-41
2 MSC with the MSCID corresponding to the new SGSN.
3 j. This is a continuation of the optional procedure started in item i. IIF receives REGCANC. The IIF
4 needs to keep both the current MSCID associated to the SGSN as well as the current MSCID
5 associated to the MSC. The IIF must also keep a record of the last MSCID which was sent to the
6 ANSI-41 HLR to know that is the one stored in the ANSI-41 HLR.
8 l. This is a continuation of the optional procedure started in item i. IIF receives regnot response.
15 o. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the IIF
17 p. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
19 q. The MSC determines that it needs to notify the IIF (emulating the GSM HLR), since there is a
20 change to the CS location update parameters, so the IIF sends the Update Location operation to
21 the IIF (emulating the GSM HLR).
22 r. The IIF sends a Cancel Location to the previous GSM MSC/VLR if a change in MSC has been
23 detected.
24 s. The IIF receives the Cancel Location acknowledgement.
25 t. If the IIF implementation supports multiple IIF MSCIDs, then it shall send a Registration
26 Notification (REGNOT) to the ANSI-41 HLR to indicate the changed location (MSCID associated
27 to the new GSM MSC).
31 u. This is a continuation of the optional procedure started in item t. The IIF receives a REGCANC if
32 the MSCID just sent in item (t) is a different one than stored in the ANSI-41 HLR. IIF receives
33 REGCANC. The IIF needs to keep both the current MSCID associated to the SGSN as well as
34 the current MSCID associated to the MSC. The IIF must also keep a record of the last MSCID
35 which was sent to the ANSI-41 HLR to know that is the one stored in the ANSI-41 HLR.
36 v. This is a continuation of the optional procedure started in item t. The IIF acknowledges the
37 regcanc.
38 w. This is a continuation of the optional procedure started in item t. The IIF receives the regnot
39 response with the subscriber’s information. This information is for non-GPRS services.
40 x. The IIF sends MAP INSERT SUBSCRIBER DATA message(s) to the GSM MSC providing GSM
42 y. The GSM MSC acknowledges receipt of the Insert Subscriber Data information.

N.S0028
1 z. The IIF acknowledges the completion of the Update Location procedure and sends the Update
3 aa. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface to the
5 bb. The SGSN acknowledges the GPRS Attach request from the MS.
6
7
8

N.S0028
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 remains
5 constant) as shown in Figure 118. Note that the GSM MSC does not update the IIF (emulating the
6 GSM HLR).
7

N.S0028
MS SGSN
MSC IIF HLR Prev
SGSN
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
ANSI-41
MS SGSN
MSC IIF HLR Prev
SGSN
p
q
Routing Area Update
Accept
r
GSM NETWORK ANSI-41
GSM NETWORK
2 Figure: 117: Inter-SGSN routing area update when GSM CS and GPRS Attached (MSC remains
3 constant)

N.S0028
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
13 i. If the IIF implementation supports multiple MSCIDs, then it shall send a REGNOT to the ANSI-41
14 MSC with the MSCID corresponding to the new SGSN. The IIF shall correlate that MSCID with
15 the GSM MSCID when receiving mobile terminated SMS messages (so that the IIF can deliver
16 them to the MSC).
17 j. This is a continuation of the optional procedure started in item i. IIF receives REGCANC. The IIF
18 needs to keep both the current MSCID associated to the SGSN as well as the current MSCID
19 associated to the MSC. The IIF must also keep a record of the last MSCID which was sent to the
20 ANSI-41 HLR to know that is the one stored in the ANSI-41 HLR.
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 there
33 is no change to the CS location update parameters, so the IIF does not send the Update Location
34 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.
38

N.S0028
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.
4

N.S0028
MS SGSN PMSC/
MSC IIF HLR VLR
GPRS Attach Req
(IMSI)
a
c
Authentication Req
d
f
Insert Sub Data GPRS_LU
g
Insert Sub Data Ack h
i
j
Update Location Req
k
REGNOT
l
REGCANC
m
regcanc
n
GSM NETWORK ANSI-41 ANSI-41

N.S0028
MS SGSN IIF HLR

MSC
Regnot ack
o
Insert Sub Data p
Insert Sub Data Ack
q
Update Locationack
r
BSSAP+-Location Update Accept s
GPRS Attach Accept
t

1
2 Figure 118: Combined Attach when registered on a ANSI-41 MSC (Option 1: With timer)
3
4

N.S0028
1
10 Request contains the IMSI. The IIF starts timer GPRS LU.
19 j. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
21 k. The MSC determines that it needs to notify the IIF (emulating the GSM HLR), since there is a
23 the IIF (emulating the GSM HLR). The IIF stops timer GPRS LU.
24 l. The IIF shall send a Registration Notification (REGNOT) to the ANSI-41 HLR to indicate the
25 changed location (MSCID associated with the new GSM MSC).
29 m. The HLR updates its location information and deletes the previous VLR record by sending a
30 REGCANC to the previous MSC/VLR.
31 n. The VLR acknowledges the REGCANC.
32 o. The ANSI-41 HLR acknowledges the registration and sends back the subscriber’s information.
33 This information is for non-GPRS services
34 p. The IIF sends MAP INSERT SUBSCRIBER DATA message(s) to the GSM MSC providing GSM
36 q. The GSM MSC acknowledges receipt of the Insert Subscriber Data information.
37 r. The IIF acknowledges the completion of the Update Location procedure and sends the Update
39 s. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface to the
41 t. The SGSN acknowledges the combined GPRS and GSM attach request from the MS.

N.S0028

N.S0028
MS SGSN PMSC/
MSC IIF HLR VLR
GPRS Attach Req (IMSI)
a
c
Authentication Req
d
f
REGNOT
g
REGCANC
h
regcanc
i
Regnot ack
j
Insert Sub Data
k
Insert Sub Data Ack
l
m

N.S0028
MS PMSC/
SGSN MSC IIF HLR VLR

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
1 Figure 119: Combined attach when registered on a ANSI-41 MSC (Option 2: without timer )
2

N.S0028

3 b. If the Serving GPRS Support Node (SGSN) does not have authentication information in order
4 to perform authentication i.e. authentication triplets, it requests authentication information
5 from the IIF. The IIF emulates a GSM HLR/AuC in this case supporting GPRS.
12 changed location.
16 this subscriber.
17 h. ANSI-41 HLR sends a REGCANC to the ANSI-41 MSC on which the MS was previously
18 registered.
19 i. ANSI-41 MSC sends regcanc response.
20 j. The ANSI-41 HLR acknowledges the registration and sends back the subscriber’s information
21 in a regnot response.
23 requested, and the MS is currently PS-deregistered, it initiates the GSM MAP Insert
26 Insert Subscriber Data transactions may be necessary to complete the transfer of subscriber
27 data to the SGSN.
29 m. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the
30 IIF returns an acknowledgement to the Update GPRS Location Request.
31 n. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
32 The GSM MSC creates the association with the SGSN by storing the SGSN Number (e.g. for
33 later CS paging over the Gs interface upon a call delivery attempt).
34 o. The MSC determines that it needs to notify the IIF (emulating the GSM HLR), since there is a
35 change to the CS location update parameters. The MSC sends the Update Location
36 operation to the IIF (emulating the GSM HLR).
37 p. If the IIF implementation supports multiple MSCIDs, then it shall send a Registration
38 Notification (REGNOT) to the ANSI-41 HLR to indicate the changed location (MSCID
39 associated to the new GSM MSC).

N.S0028
2 this subscriber.
3 q. This is a continuation of the optional procedure started in item p. The IIF receives a
4 REGCANC if the MSCID just sent in item (p) is a different one than stored in the ANSI-41
5 HLR. The IIF needs to keep both the current MSCID associated to the SGSN as well as the
6 current MSCID associated to the MSC. The IIF must also keep a record of the last MSCID
7 which was sent to the ANSI-41 HLR to know that is the one stored in the ANSI-41 HLR.
8 r. This is a continuation of the optional procedure started in item p. The IIF acknowledges the
9 regcanc.
10 s. This is a continuation of the optional procedure started in item p. The IIF receives the regnot
11 response with the subscriber’s information. This information is for non-GPRS services.
12 t. The IIF sends MAP INSERT SUBSCRIBER DATA message(s) to the GSM MSC providing
13 GSM CS information based on the contents of the regnot (profile).
14 u. The GSM MSC acknowledges receipt of the Insert Subscriber Data information.
15 v. The IIF acknowledges the completion of the Update Location procedure and sends the
16 Update Location Acknowledgement to the GSM MSC.
17 w. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface to
18 the SGSN by sending the Accept message.
19 x. The SGSN acknowledges the combined GPRS and GSM attach request from the MS.
20

N.S0028
1 4.13.1.9 Authentication Failure at the IIF
2 In any of the scenarios shown previously in 4.13.1 (assuming authentication is performed),

3 authentication may fail at the IIF.
4 In the event that authentication fails at the IIF (emulating a GSM HLR), it shall send a response to the
5 SGSN indicating the reason for failure.
6 Note: The ANSI-41 HLR is not informed about a registration attempt if authentication fails at the IIF.
7 4.13.1.10 Registration Failure at the ANSI-41HLR
8 In any of the scenarios shown previously in 4.13.1 where the ANSI-41 HLR is informed about the
9 registration attempt (assuming authentication is successful or not performed), the registration
10 procedure may fail.
11 In the event that the ANSI-41 HLR denies the registration attempt, it shall send a regnot to the IIF
12 indicating the reason for failure. If the IIF determines that the MS is already registered in an SGSN, it
13 shall send a Cancel Location to the SGSN. Otherwise, the IIF sends an update GPRS location
14 response indicating the reason for failure.
15 4.13.2 Location Deregistration Scenarios

16
17 4.13.2.1 GSM CS (IMSI) Detach while GPRS and GSM CS Attached
18 A GPRS mobile attached for both GPRS and non-GPRS services can request a detach for circuit
19 services (IMSI detach). The IIF is not notified about the MS initiated detachment and hence the ANSI-
20 41 HLR is not informed.
21 4.13.2.2 GPRS Detach While Attached for Both GPRS and GSM CS Services
22 A GPRS mobile attached for both GPRS and non-GPRS services can request a GPRS detach. The
23 IIF is not notified about the MS initiated detachment and hence the ANSI-41 HLR is not informed.
24 4.13.2.3 GPRS Detach While Attached for GPRS Services Only
25 In GPRS, the GPRS HLR is not notified when a GPRS subscriber performs a GPRS detach. Hence,
26 the IIF (which is emulating the GPRS HLR) shall not be notified of the GPRS detach. In this case, a
27 GPRS subscriber performs a Detach request that is handled by the SGSN and GGSN to remove MM
28 and PDP contexts. There is no interworking with circuit services.
29 4.13.2.4 Combined GPRS Detach and GSM CS (IMSI) Detach
30 A GPRS mobile attached for both GPRS and non-GPRS services can request a combined detach
31 from GPRS and non-GPRS services. The IIF is not notified about the MS initiated detachment and
32 hence the ANSI-41 HLR is not informed.
33
34

N.S0028
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 services
4 to an SGSN-only. The mobile performs a GPRS detach. After accepting the detach request, the
5 SGSN is configured to initiate a purge MS procedure (after some pre-configured time period). In a
6 case when the MS is still GSM CS attached, the MS-Inactive is not sent by the IIF. Likewise, if an
7 MSC sends the PurgeMS operation to the IIF when the subscriber is still GPRS attached, the IIF
8 would not send the MS-Inactive to the ANSI-41 HLR.
SGSN ANSI-41
MS IIF
HLR
Detach Request
a
b
Signaling
with GGSN
c
Detach Accept d
Purge MS e
Purge MS Ack f
MSINACTIVE g
msinactive h
9
10 Figure 120: MS in GSM Foreign Mode Performing GPRS Detach Followed by Purge
11
12 a. The MS performs a Detach Request to detach from GPRS services. This MS was attached for
13 GPRS services only.
14 b. The SGSN exchanges signaling information with the GGSN to remove PDP contexts on the
15 GGSN for the subscriber.
16 c. See (b)
17 d. The SGSN accepts the detach from the MS and sends a Detach Accept.
18 e. The SGSN is configured to delete MM contexts as soon as the Detach Accept is sent. Hence,
19 the SGSN notifies the IIF (acting as a GPRS HLR) that it has deleted the MM context for the MS.

N.S0028
1 f. The IIF acknowledges the Purge Operation and marks in its GPRS subscription data for the
2 subscriber that the GPRS data has been purged.
3 g. The IIF sends an MSINACTIVE to the ANSI-41 HLR to de-register the MS from the IIF (acting as
4 an ANSI-41 MSC).
5 h. The ANSI-41 HLR acknowledges the MSINACTIVE operation
6

N.S0028
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.
4
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 1
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 attach
12 and PDP context activation.
13 1
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 1
17 d. The GGSNs acknowledge the Delete Request
18 1
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 1
22 f. The MS sends a Detach Accept to the SGSN any time after step b.
23 1
24 g. The SGSN confirms the deletion of the PDP contexts with a Cancel Location Ack (IMSI).
25 1

N.S0028
1 1Note: In some cases the IIF may send an MS Inactive towards the ANSI-41 HLR (but not if CS
2 services are still to be offered).
3
4 4.13.3 SMS Scenarios
5 This section describes the scenarios for MS terminated and MS originated SMS while the mobile in
6 roaming in a GPRS network in GSM foreign mode.
7 4.13.3.1 SMS Scenarios for Mobile Terminated SMS while GPRS Attached
8 a.If the subscriber is both GSM CS attached as well as GPRS attached, then the IIF shall act like a
9 GSM SMS-SC.
10 The scenarios that follow only show the SMS delivery via GPRS.
11 4.13.3.1.1 Successful Mobile Terminated ANSI-136 41 SMS (CMT) Mapped to GSM SMS
TDMA TDMA 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
12
13 Figure 122: Successful Mobile Terminating ANSI-136 41 SMS (CMT) mapped to GSM SMS
14
15 a. The ANSI-136 41 Message Center (MC) receives a short message for a specific subscriber.
16 Note: This step is shown for completeness only and is not repeated in subsequent call flows.
17
18 b. The Message Center sends an SMS Request message to the ANSI-41 HLR of the short message
19 recipient to request a routing address for delivering the short message to that subscriber.
20
21 c. Since the subscriber has a current valid location stored in the HLR, the HLR returns it to the MC
22 in the SMS Request Return Result message.
23
24 d. The Message Center then sends a Short Message Delivery Point to Point message to the IIF,
25 which is seen as the current serving ANSI-41 MSC/VLR for that subscriber. Note that in this case,

N.S0028
1 the format used by the MC is the CMT format (Cellular Messaging Transport). Note that
2 alternatively, the ANSI-136 41 MC could translate the original CMT SMS to GHOST/WEMT
3 format before sending it to the IIF if the IIF only supports the GHOST/WEMT format. In this case
4 the IIF would convert ANSI-136 41 GHOST/WEMT into GSM format (see Section 4.13.3.1.2)
5 instead of ANSI-136 41 CMT into GSM format.
6
7 e. Upon reception of the Short Message Delivery Point to Point message from the ANSI-136 41 MC,
8 the IIF originates a FORWARD SHORT MESSAGE to the SGSN after having translated the short
9 message into GSM format. The IIF is then acting as a GSM SMS-GMSC.
10
11 f. The SGSN sends the short message to the mobile station. Note: This step is shown for
12 completeness only and is not repeated in subsequent call flows.
13
14 g. The mobile station acknowledges the delivery of the short message. Note: This step is shown for
15 completeness only and is not repeated in subsequent call flows.
16
17 h. The SGSN sends the result of the Forward Short Message to the IIF.
18
19 i. The IIF sends the result of the Short Message Delivery Point to Point to the ANSI-136 41
20 Message Center.
21
22
23

N.S0028
1
2 4.13.3.1.2 Successful Mobile Terminating ANSI-136 41 SMS (GHOST/WEMT) Mapped to GSM
ANSI-41 GSM
MC HLR IIF SGSN
SMSREQ
a
smsreq
b
SMDPP
c
d
e
smdpp [ACK]
f
3 SMS
4
5 Figure 123: Successful Mobile Terminating ANSI-136 41 SMS (GHOST/WEMT) mapped to GSM
6 SMS
7
12 address).
16 routes it to the SGSN as a first choice. Alternatively, the IIF could send the FSM to the GSM MSC
17 (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.

N.S0028
1 4.13.3.1.3 Unsuccessful Mobile Terminated Delivery (Failure at SGSN)
ANSI-41 GSM
MC HLR IIF SGSN
SMSREQ
a
smsreq
b
SMDPP
c
d
e
smdpp [NAK]
f
3 format.
4
5 Figure 124: Unsuccessful Mobile Terminated Delivery (Failure at SGSN)
6
11 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 routes it to the SGSN. If the message received is in the CMT format, the IIF maps this information
17 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 [4] 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

N.S0028
1 subscriber”, and the Memory Capacity Exceeded Flag (MCEF) shall be set if the error cause is
2 “memory capacity exceeded”. Additionally, the IIF emulating the ANSI-41 MSC shall set and
3 store the SMS Delivery Pending flag with the MC parameters received in the SMDPP (for later
4 delivery in the SMSNOT) – note that this “SMS Delivery Pending” flag/data serves the same
5 purpose as a GSM HLR’s “Message Waiting Data” flag/data. [However, note that if an ANSI-41
6 REGCAN is received from the ANSI-41 HLR before the SMS Delivery Pending Flag is cleared,
7 then the regcanc response shall contain the SMS_MessageWaitingIndicator, and all flags are
8 cleared (i.e., MNRG, MNRF, MCEF, and SMS Delivery Pending Flag)].
9 4.13.3.1.4 Unsuccessful Mobile Terminated Delivery (Failure at IIF)
11 format.
12
ANSI-41 GSM
MC HLR IIF SGSN
SMSREQ
a
smsreq
b
SMDPP
c
smdpp [NAK]
d
13
14 Figure 125: Unsuccessful Mobile Terminated Delivery (Failure at IIF)
15
17 MIN (MSISDN) or IMSI of the mobile station and SMS Notification Indicator.
20 address).
22 d. Upon receipt of the SMDPP message, the IIF examines the GSM 03.40 HLR flags (if “both MNRC
23 and MNRG” or ”MCEF” is set) and determines that the MS is unable to receive a Short Message.
24 The IIF indicates this fact in the SMDPP Return Result. It includes the cause for the failure in the
25 SMS_CauseCode parameter of the SMDPP Return Result. The IIF shall set & store the SMS
26 Delivery Pending Flag with the data received in the SMDPP message (for later delivery in the
27 SMSNOT). If the 03.40 flag is set to MNRG and if the flag is not set to MNRC, then the SMDPP
28 shall be delivered to the GSM MSC as described in GAIT phase 1. If 03.40 flag is set to MNRC
29 and not MNRG nor MCEF, then SMS delivery is possible through the SGSN as shown in section
30 4.13.3.1.
31

N.S0028
1
2 4.13.3.1.5 Alerting for an ANSI-136 41 Subscriber for GPRS in GSM Foreign Mode
3 The following scenario applies to short messages originated in either CMT or GHOST/WEMT format.
ANSI-41 GSM
SMSC HLR IIF MSC
READY FOR SM
a
SMSNOT
b
smsnot
c
ready for SM
d
4
5 Figure 126: Alerting for an ANSI-136 41 Subscriber 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 Pending
16 Flag, then proceeds to send the mobile station a mobile terminated CMT or GHOST/WEMT
17 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 flags
20 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 SM
22 response to the SGSN with no arguments.
23
24

N.S0028
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 PDU.
12 b. Upon receipt of the FORWARD SHORT MESSAGE, the IIF builds an ANSI-41 SMDPP message,
14 originator’s home MC. The IIF can also map the Forward Short Message into a CMT short
15 message.
16 c. The MC sends a positive acknowledgement SMDPP Return Result to the IIF.
17 d. The IIF maps the received SMDPP Return Result to a Forward Short Message, and sends it to
18 the SGSN.
19

N.S0028
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
3 Figure 128: Unsuccessful Mobile Originated Delivery (Failure at MC)

4
7 b. Upon receipt of the FORWARD SHORT MESSAGE, the IIF builds an ANSI-41 SMDPP message
9 MC. The IIF can also map the Forward Short Message into a CMT short message.
10 c. The MC sends a negative acknowledgement SMDPP Return Result to the IIF.
11 d. The IIF maps the received SMDPP Return Result to a Forward Short Message with the
12 appropriate cause code value, and sends it to the SGSN.
13

N.S0028
1 4.13.4.3 Unsuccessful Mobile Originated (Failure at IIF)
GSM ANSI-41
SGSN HLR IIF MC

a

b
2
3 Figure 129: Unsuccessful Mobile Originated (Failure at IIF)
4
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
10

N.S0028
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 mobile
4 originations and GPRS in GSM foreign mode and Message Waiting Notification. For a native ANSI-
5 136 ANSI-41 subscriber roaming in a GSM environment, there can be two events that trigger the IIF
6 to send the Message Waiting Notification (MWN) using the GSM SMS to the Mobile Station (MS).
7 The first one is at registration (update GPRS location), if there is an indication in the ANSI-41 HLR
8 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.13.5.1. The second event is when
11 the 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 it
13 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.
17

N.S0028
1 4.13.5.1 Indicator in ANSI-41 Registration Notification Return Result mapped to

2 GSM SMS
TDMA TDMA GSM n

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

N.S0028
1
2 ➀At this point, the IIF sets the MWN flag. This is an indication that Message Waiting Notification is to
3 be delivered to the Mobile Station.
4
5 g. The IIF sends Insert Subscriber Data to the serving GSM SGSN. Note that there could be more
6 than one Insert Subscriber Data message depending on the subscriber profile.
7
8 h. The serving GSM SGSN returns the Insert Subscriber Data result. Note that there could be more
9 than one such result message, one matching every Insert Subscriber Data message.
10
11 i. The IIF completes the location update by sending the Update Location result message to the
12 serving GSM SGSN.
13
14 j. The serving GSM SGSN confirms the update location to the mobile station.
15
16 k. Since the REGNOT return result from event f contained the Message Waiting Notification
17 information, this triggers the IIF to originate an SMS with MWN information by sending Forward
18 Short Message to the serving GSM SGSN. The IIF is then acting as a GSM SMS-GMSC. The IIF
19 is to encode the MWN information in the SMS with three methods, namely, UDH, DCS, and
20 CPHS. Refer to Volume 3 for the encoding details.
21
22 l. The serving GSM SGSN sends the short message with the MWN information to the mobile
23 station.
24
26
27 n. The serving GSM SGSN sends the result of the Forward Short Message to the IIF.
28
31
32

N.S0028
1
2 4.13.5.2 ANSI-41 Qualification Directive mapped to GSM SMS
.............................................................
TDMA TDMA 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
②
3 Figure 131: ANSI-41 Qualification Directive mapped to GSM SMS

5
8 ANSI-41 [1].
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 [1].
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
26

N.S0028
1 f. The serving GSM SGSN sends the short message with the MWN information to the mobile
2 station.
3
4 g. The mobile station acknowledges the delivery of the short message.
5
6 h. The serving GSM SGSN sends the result of the Forward Short Message to the IIF.
7
10 4.13.5.3 Handling at SMS delivery failure at the SGSN or at the Mobile Station
11 The IIF is to keep a Message Waiting Notification (MWN) flag for each subscriber in its database. In
12 the event of a failure to deliver a short message with MWN to the mobile station, the IIF is to keep the
13 MWN flag set. Another Forward Short Message with MWN information shall be sent, triggered by the
14 reception of a subsequent GSM Update Location message, a Ready for Short Message, or a Note
15 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
②
n
16
17 Figure 132: Handling at SMS delivery failure at the SGSN or at the MS

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

N.S0028
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
5
6 4.13.6.1.1 Call Delivery to ANSI-136 41 Subscriber Roaming on a GSM/GPRS Network
GSM ANSI
SGSN IIF HLR

MS MSC O-MSC
a
Incoming call
LOCREQ
b
ROUTEREQ c
PRN d
prn e
routereq f
locreq g
ISUP signaling / SS7 h

PAGING-REQ
i
Paging Procedure j
To
SUSPEND BSS k
7 Figure 133: Call Delivery to ANSI-136 41 Subscriber 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 a
14 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).

N.S0028
1 e. The serving GSM MSC/VLR responds with a prn to the PRN operation providing a temporary
2 routing number.
3 f. The IIF forwards this number to the ANSI-41 HLR in the routereq.
4 g. The ANSI-41 HLR forwards a locreq to the O-MSC with the temporary routing number.
5 h. The O-MSC proceeds to contact the serving GSM MSC/VLR exchanging ISUP signaling for call
6 setup.
7 i. The serving GSM MSC/VLR realizes that the MS is actually attached to an SGSN. So the GSM
8 serving MSC/VLR sends a BSSAP+PAGING-REQUEST to the SGSN.
9 j. The SGSN executes a Paging procedure for circuit services.
10 k. The MS sends a SUSPEND REQ to the BSS that may be forwarded to the SGSN. At this point,
11 the MS can respond to the page via GSM cell sites to the serving GSM MSC/VLR.
12

N.S0028
1 4.13.6.1.2 Call Delivery to ANSI-136 41 Subscriber Roaming in a GPRS Network

2 (Unsuccessful)
3 The following scenario describes the case where a subscriber in GSM foreign mode is roaming in a
4 GPRS network. The MS is attached for GPRS-only services. The IIF has already registered itself (as
5 an ANSI-41 MSC) with the ANSI-41 HLR. Since the MS is attached for GPRS-only service, incoming
6 calls are not deliverable to the subscriber. This scenario attempts to describe what happens in the
7 case of an incoming call to an MS attached for GPRS services only.
GSM ANSI
MS SGSN IIF HLR MSC
Incoming call
a
LOCREQ b
ROUTEREQ c
routereq d
locreq e
FSM f
SMS Exchange
g
fsm
h
8
9 Figure 134: MS Notification of a “Missed” Call via SMS
10
11 a. The O-MSC receives an incoming call for the subscriber roaming in the GSM network
12 b. The O-MSC sends the HLR a LOCREQ
13 c. The HLR has the address of the IIF (acting as an ANSI-41 MSC) and sends a ROUTEREQ to the
14 IIF
15 d. The IIF recognizes that fact this is a GAIT subscriber roaming in a GSM network. The IIF, from
16 its dynamic data, sees that the subscriber is attached for GPRS-only services and hence, cannot
17 have call delivery. The IIF sends a routreq with the field “AccessDeniedReason” set to
18 “Unavailable” or “No Page Response”.
19 e. The HLR returns a locreq to the O-MSC. At this point, the calling party may receive secondary
20 treatment.

N.S0028
1 f. The IIF contains the functionality to act as an SMS-SC. In this case, the IIF has the calling party
2 DN available (from the ROUTEREQ message). The IIF proceeds to act as an SMS-SC and
3 sends an FSM to the SGSN requesting the SGSN to deliver an SMS message containing the
4 calling party’s DN to the MS.
5 g. The SGSN sends the MS the SMS message containing the DN of the calling party and the MS
6 acknowledges receipt of the SMS message.
7 h. The SGSN acknowledges the request and sends back an fsm.
8

N.S0028
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.
5
MS SGSN IIF GGSN
PDP PDU
a
SRI for GPRS
b
SRI for GPRS Ack
c
PDU Notification Request
d
PDU Notification Response
e
Request PDP context Activation
f
Activate PDP context Request
g
Send Auth Info
h
Send Auth Info Ack
i
Create PDP Context Request j
Create PDP Context Response

k
Activate PDP context Accept
l
6 1Figure 135: Successful Network Requested PDP context Activation

7 1
8 a. When receiving a PDP PDU the GGSN follows the procedures described in GSM 03.60 [10]
9 1
10 b. The GGSN may send a Send Routeing Information for GPRS (IMSI) message to the IIF.
11 1
12 c. The IIF determines if the request can be served. If the request can be served it returns a Send
13 Routeing Information for GPRS Ack (IMSI, SGSN Address) to the GGSN. If the request cannot
14 be served it returns a Send Routeing Information for GPRS Ack (IMSI, MAP Error Cause).
15
16 d. Steps d through l are provided for completeness and are outside the scope of this specification.
17 Note: Certain security procedures as in step h) may be invoked.

N.S0028
1 4.13.6.3 Unsuccessful Network-Requested PDP Context Activation Procedure
2 If the PDP context requested by the GGSN cannot be established, the IIF in conjunction with the
3 SGSN and GGSN may perform the Protection and Mobile User Activity Procedures as described in
4 GSM 03.60 [10]. The IIF acting as a GPRS HLR shall follow the same procedures as the GSM HLR.
5 4.13.7 Packet Domain Subscriber Data in the IIF

6 GPRS subscriber data shall be provisioned in the IIF (emulating a GPRS HLR) to support GPRS
7 service capability in GSM Foreign mode. The IIF shall store the same subscription information as
8 identified in GSM 03.60 [10].
9 It may be possible to provision an ANSI-136 41 native subscriber with GPRS-only service (and no
10 GSM CS service)
11

N.S0028
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 range
5 15s to 30s whereas the equivalent ANSI-41 timer controlling the REGNOT is defined to be a default
6 value of 12s.
7

N.S0028
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 SS 15s to 30s FEATREQ 16s
ERASE SS 15s to 30s
ACTIVATE SS 15s to 30s
DE-ACTIVATE 15s to 30s
SS
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.

N.S0028
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 [16]. All the changes are made on the assumption the new requirements for
5 UIM/handsets are working.

N.S0028
1 B.1 - Successful Authentication on Initial Access in

2 GSM System
3
4 This scenario illustrates the successful authentication of an MS on the initial MS access is a GSM
5 system
ANSI-41 GSM
HLR MSC/ MSC/
AC IIF VLR VLR
Location area update (IMSI)
a
SEND_AUTH_INFO (IMSI)
b
AUTHREQ (MSCID, SYSCAP, MSID, ESN, SYSAC)
c
d
ART ART
Authreq (SSD, ESN) e
Authreq (SSD, ESN)
SEND_AUTH_INFO ack (AuthenticationSetList) g

authentication (RAND)
h
ASRRT
authentication ack (SRES)
i
UPDATE LOCATION (IMSI) j

ASREPORT (MSCID, MSID, UCHALRPT)
k
l
ASRRT
ASRT ASRRT
asreport[]
m
asreport[]
REGNOT [MSCID, TRANSCAP, SYSCAP, MSID, ESN, SYSAC]

o
6
7 Figure 136 – Successful Authentication on Initial Access in GSM System
8
9 a) The MS determines that a new serving system has been entered. The MS registers at the new GSM
10 serving system and provides its IMSI.
11
12 b) The GSM serving system sends a SEND_AUTHENTICATION_INFO to the IIF.
13
14 c) The IIF sends an AUTHREQ to the HLR associated with the MS. The MSCID parameter identifies the
15 IIF. The SYSCAP parameter is set to indicate GSM system. The ESN parameter is set to a default
16 value. The SYSACCTYPE parameter is set to indicate GSM system access.

N.S0028
1
2 d) The HLR forwards the AUTHREQ to the AC.
3
4 e) The AC determines that the subscriber is roaming in a GSM system. The AC includes the SSD
5 parameter in the authreq sent to the HLR. The ESN parameter is set to the indicated MS’s ESN.
6
7 f) The HLR forwards the authreq to the IIF.
8
9 g) The IIF stores the received SSD and ESN. The IIF computes one or more groups of GSM triplets using
10 the subscriber’s SSD. The IIF sends a SEND_AUTHENTICATION_INFO ack to the GSM system and
11 includes the groups of triplets.
12
13 h) The GSM system issues a random challenge to the MS
14
15 i) The MS responds to the challenge with the computed response.
16
17 j) The GSM system compares the response received from the MS with the expected response. In this
18 scenario, the response is equal to the expected response. The GSM system sends a
19 UPDATE_LOCATION to the IIF. The IMSI is used to identify the MS.
20
21 k) The IIF sends an ASREPORT to the HLR associated with the MS. The UCHALRPT parameter is set
22 to indicate Unique Challenge successful.
23
24 l) The HLR forwards the ASREPORT to the AC.
25
26 m) The AC sends an asreport to the HLR.
27
28 n) The HLR forwards the asreport to the IIF.
29
30 o) The IIF sends a REGNOT to the HLR
31
32 p) The HLR sends a regnot to the IIF with the subscriber’s service profile
33
34 q) The IIF sends an INSERT_SUBSCRIBER_DATA to the GSM system.
35
36 r) The GSM systems sends an INSERT_SUBSCRIBER_DATA ack to the IIF.
37
38 s) The IIF sends an LOCATION_UPDATE ack to the GSM system.
39
40 t) The GSM system sends a location area update ack to the MS.
41

N.S0028
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.
4
ANSI-41 GSM
HLR MSC/ MSC/
AC IIF VLR VLR
a
b
c
d
ART ART
Authreq (SSD, ESN)

h
ASRRT
i
UPDATE LOCATION (IMSI) j

k
l
ASRRT ASRRT
asreport[DENACC]
m
asreport[DENACC]
AUTHENTICATION_FAILURE
o
5
6 Figure 137 - Authentication Failure on Initial Access in GSM System

N.S0028
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.

N.S0028
1 B.3 Authentication Failure on Initial Access

2 in GSM System – Authentication Failure
3 Message Not Supported
4
5 This scenario illustrates an authentication failure on the initial MS access is a GSM system. The GSM
6 system doe not report the authentication failure to the IIF
ANSI-41 GSM
HLR MSC/ MSC/
AC IIF VLR VLR
a
b
c
d
ART ART
Authreq (SSD, ESN)

h
ASRRT timer
i
Location area update reject j
timer expiry k
l

m
ASRRT ASRRT
asreport[DENACC]
asreport[DENACC]
o
7
8 Figure 138 - Authentication Failure on Initial Access in GSM System – Authentication
9 Failure Message 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

N.S0028
1 l) The IIF sends an ASREPORT to the HLR associated with the MS. The UCHALRPT parameter is set
2 to indicate Unique Challenge failed.
3
4 m) The HLR forwards the ASREPORT to the AC.
5
6 n) The AC includes the DENACC parameter and sends an asreport to the HLR.
7
8 o) The HLR forwards the asreport to the IIF. The IIF removes the SSD, ESN and other information stored
9 for the MS.
10
11

N.S0028
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/ MSC/
AC IIF VLR VLR
SEND_AUTHENTICATION_INFO (IMSI)
a
SEND_AUTH_INFO ack (AuthenticationSetList)
b
5 Figure 139 - GSM System Request for Additional Triplets

6
7 a) The GSM system determines that additional triplets are required and sends a
8 SEND_AUTHENTICATION_INFO 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 to
10 the GSM system. (Note, the IIF may have pre-computed triplets for the MS that it
11 sends to the GSM system).

N.S0028
1 Abstract
2
4 based networks in the support of subscribers roaming between networks. The interworking and
5 interoperability functionality of the services, information flows, and message mappings are
6 specified. This standard consists of four Volumes:
7
12
13 This is Volume 3.
14
i
N.S0028

Revision Date Version Comments
0 March 2001 Initial Release J-STD-038
A May 23, 2001 draft GPRS text added: section 4.6.

A July 9, 2001 0 Misc. editorial changes.
A August 1, 2001 1 Review changes.

A August 14, 2001 1 Review changes.
A August 15, 2001 2 Editorial changes. Ballot version.
A November 27, 3 Incorporation of agreed ballot comments
2001

one roaming
3
4
5
6
ii
N.S0028
2 Contents
3
4 ABSTRACT .......................................................................................................................................I
5 DOCUMENT REVISION HISTORY....................................................................................................II
6 CONTENTS .....................................................................................................................................III
7 LIST OF TABLES .......................................................................................................................... VII
8 LIST OF FIGURES........................................................................................................................ XXI
9 FOREWORD................................................................................................................................ XXII
10 1 INTRODUCTION ........................................................................................................................1
11 1.1 General............................................................................................................................................... 1
12 1.2 Purpose............................................................................................................................................... 1
13 1.3 Scope .................................................................................................................................................. 1
14 1.4 Organization ...................................................................................................................................... 1
15 2 REFERENCES...........................................................................................................................3
16 3 DEFINITIONS AND ACRONYMS...............................................................................................4
17 3.1 Definitions .......................................................................................................................................... 4
18 3.2 Acronyms ........................................................................................................................................... 6
19 4 MESSAGE MAPPINGS............................................................................................................10
20 4.1 Mobility Procedures......................................................................................................................... 10

21 4.1.1 Location Registration ................................................................................................................. 10
22 4.1.2 Fault Recovery ........................................................................................................................... 23
23 4.2 Call Handing Procedures................................................................................................................. 26

24 4.2.1 Automatic Call Delivery............................................................................................................. 26
25 4.2.2 Invocation of Conditional Call Forwarding in ANSI-41 Foreign Mode ........................................ 40
26 4.2.3 Optimal Routing after Late Call Forwarding ............................................................................... 44
27 4.3 Supplementary Services Procedures................................................................................................ 53
iii
N.S0028
1 4.3.1 SS Activation and Deactivation................................................................................................... 53

2 4.3.2 SS Registration and Erasure........................................................................................................ 70
3 4.3.3 Retrieval of Forward-To Number................................................................................................ 94
4 4.3.4 Calling Number / Line Identification Presentation/Restriction ..................................................... 98
5 4.4 O&M Procedures........................................................................................................................... 105

6 4.4.1 Detailed Procedures.................................................................................................................. 105
7 4.4.2 Mapping of Messages, Parameters & Parameter Values............................................................. 106
8 4.4.3 Error Handling ......................................................................................................................... 126
9 4.5 Short Message Procedures (ANSI-41 Network) ............................................................................ 131

10 4.5.1 Short Message Service via CMT............................................................................................... 131
11 4.5.2 Short Message Service via GHOST or WEMT.......................................................................... 150
12 4.5.3 Message Waiting Notification................................................................................................... 161
13 4.6 GPRS IN GSM FOREIGN MODE........................................................................................ 170

14 4.6.1 Mobility Procedures ................................................................................................................. 170
15 4.6.2 Automatic Call Delivery........................................................................................................... 177
16 4.6.3 Short Message Procedures for ANSI-41 subscriber ................................................................... 180
17 4.6.4 Short Message Service via GHOST or WEMT.......................................................................... 183
18 4.6.5 Message Waiting Notification................................................................................................... 184
19 ANNEX A SHORT MESSAGE SERVICE PROCEDURES WITHIN AN ANSI-136 NETWORK ...... 186
20 A.1 CMT to GHOST Delivery.............................................................................................................. 186

21 A.1.1 Detailed Procedures.................................................................................................................. 186
22 A.1.2 Mapping of Messages, Parameters & Parameter Values............................................................. 186
23 A.1.3 Error Handling ......................................................................................................................... 188
24 A.2 GHOST to CMT Delivery.............................................................................................................. 188

26 A.2.2 Mapping of Messages, Parameters & Parameter Values............................................................. 190
27 A.2.3 Error Handling ......................................................................................................................... 194
28 A.3 Callback Number ........................................................................................................................... 195

30 A.3.2 Message Mapping, Parameters and Parameters Values .............................................................. 196
31 A.3.3 Error Handling ......................................................................................................................... 196
32 ANNEX B CAUSE CODE MAPPING AT NON-IIF NODES............................................................ 197
33 ANNEX C: CDMA TO GSM ONE-WAY ROAMING ONLY............................................................. 198
34 ABSTRACT .......................................................................................................................................I
35 DOCUMENT REVISION HISTORY....................................................................................................II
36 CONTENTS .....................................................................................................................................III
37 LIST OF TABLES ............................................................................................................................ V
iv
N.S0028
1 LIST OF FIGURES......................................................................................................................... XII
2 FOREWORD................................................................................................................................. XIII
3 1 INTRODUCTION ........................................................................................................................1
4 1.1 General ..................................................................................................................................1
5 1.2 Purpose .................................................................................................................................1
6 1.3 Scope.....................................................................................................................................1
7 1.4 Organization..........................................................................................................................1
8 2 REFERENCES...........................................................................................................................3
9 3 DEFINITIONS AND ACRONYMS...............................................................................................4
10 3.1 Definitions .............................................................................................................................4
11 3.2 Acronyms ..............................................................................................................................6
12 4 MESSAGE MAPPINGS..............................................................................................................9
13 4.1 Mobility Procedures..............................................................................................................9

14 4.1.1 Location Registration........................................................................................................9
15 4.1.2 Fault Recovery...............................................................................................................22
16 4.2 Call Handing Procedures....................................................................................................25

17 4.2.1 Automatic Call Delivery ..................................................................................................25
18 4.2.2 Invocation of Conditional Call Forwarding in ANSI-41 Foreign Mode...............................38
19 4.2.3 Optimal Routing after Late Call Forwarding ....................................................................42
20 4.3 Supplementary Services Procedures.................................................................................51

21 4.3.1 SS Activation and Deactivation.......................................................................................51
22 4.3.2 SS Registration and Erasure ..........................................................................................68
23 4.3.3 Retrieval of Forward-To Number ....................................................................................92
24 4.3.4 Calling Number / Line Identification Presentation/Restriction...........................................96
25 4.4 O&M Procedures ............................................................................................................... 103

26 4.4.1 Detailed Procedures..................................................................................................... 103
27 4.4.2 Mapping of Messages, Parameters & Parameter Values .............................................. 104
28 4.4.3 Error Handling.............................................................................................................. 123
29 4.5 Short Message Procedures (ANSI-136 Network) ............................................................. 128

30 4.5.1 Short Message Service via CMT .................................................................................. 128
31 4.5.2 Short Message Service via GHOST.............................................................................. 145
32 4.5.3 Message Waiting Notification ....................................................................................... 156
33 4.6 GPRS IN GSM FOREIGN MODE........................................................................................ 165

34 4.6.1 Mobility Procedures...................................................................................................... 165
v
N.S0028
1 4.6.2 Automatic Call Delivery ................................................................................................ 172

2 4.6.3 Short Message Procedures for ANSI-136 subscriber .................................................... 175
3 4.6.4 Short Message Service via GHOST.............................................................................. 178
4 4.6.5 Message Waiting Notification ....................................................................................... 179
5 ANNEX A SHORT MESSAGE SERVICE PROCEDURES WITHIN AN ANSI-136 NETWORK ...... 181
6 A.1 CMT to GHOST Delivery.................................................................................................... 181

7 A.1.1 Detailed Procedures..................................................................................................... 181
8 A.1.2 Mapping of Messages, Parameters & Parameter Values .............................................. 181
9 A.1.3 Error Handling.............................................................................................................. 183
10 A.2 GHOST to CMT Delivery....................................................................................................183

12 A.2.2 Mapping of Messages, Parameters & Parameter Values .............................................. 185
13 A.2.3 Error Handling.............................................................................................................. 189
14 A.3 Callback Number............................................................................................................... 190

16 A.3.2 Message Mapping, Parameters and Parameters Values............................................... 191
17 A.3.3 Error Handling.............................................................................................................. 191
18 ANNEX B CAUSE CODE MAPPING AT NON-IIF NODES............................................................ 192

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

19 Mapping ...................................................................................................................29
20 Table 16: Provide Roaming Number Response ↔ Routreq Return Result Parameter
21 Mapping ...................................................................................................................31
22 Table 17: PROVIDE_ROAMING_NUMBER_RESPONSE to Routreq Return Error Mapping

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

26 Mapping ...................................................................................................................58
27 Table 46: Activate/Deactivate SS Response ↔ Feature Request Return Error Mapping.............59
28 Table 47: Activate/Deactivate SS Request to FEATREQ Parameter Mapping ............................59
29 Table 48: FEATREQ default parameter......................................................................................60
viii
N.S0028
1 Table 49: Activate/Deactivate SS Response default parameter values .......................................61
2 Table 50: Feature Request Invoke to Activate/Deactivate SS Request Parameter Mapping........62
3 Table 51: Activate/Deactivate SS Request default parameter.....................................................62
4 Table 52: FeatureRequest Return Result default parameter.......................................................63
5 Table 53: FeatureRequest Return Result to User Error in the Activate/Deactivate SS

6 Response Error Mapping..........................................................................................66
7 Table 54: FeatureRequest Return Error to Activate/Deactivate SS Response Error

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

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

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

14 Error Mapping ..........................................................................................................69
15 Table 58: Supplementary Service Registration Message Mapping .............................................72
16 Table 59: Register SS Request ↔ FEATREQ parameter mapping.............................................73
17 Table 60: Register SS Response ↔ Feature Request Return Result Parameter Mapping ..........74
18 Table 61: Register SS Response ↔ Return Error Parameter Mapping .......................................75
19 Table 62: Register SS Request to Feature Request Invoke parameter mapping.........................76
21 Table 64: Register SS Response default parameter values........................................................78
22 Table 65: FEATREQ to Register SS Request parameter mapping .............................................79
23 Table 66: Register SS Request default parameter......................................................................79
25 Table 68: FeatureRequest Return Result to User Error in the Register SS Response
26 mapping ...................................................................................................................82
27 Table 69: Supplementary Service Erasure Message Mapping....................................................85
28 Table 70: Erase SS Request ↔ FEATREQ parameter mapping.................................................85
29 Table 71: Erase SS Response ↔ Feature Request Return Result parameter mapping ..............86
30 Table 72: Erase SS Response ↔ Return Error parameter mapping ...........................................87
31 Table 73: Erase SS Request to FEATREQ parameter mapping .................................................88
ix
N.S0028
1 Table 74: Feature Request Invoke default parameter.................................................................89
2 Table 75: Erase SS Response default parameter values............................................................90
3 Table 76: FEATREQ to Erase SS Request parameter mapping ................................................91
4 Table 77: Erase SS Request default parameter .........................................................................91
6 Table 79: FeatureRequest Return Result to Register SS Response User Error ..........................93
7 Table 80: Retrieval of Forward-to-Number in GSM Foreign Mode ..............................................95
8 Table 81: TransferToNumberRequest Return Result to Insert Subscriber Data parameter

9 mapping ...................................................................................................................96
10 Table 82: TransferToNumberRequest Return Result to Insert Subscriber Data Request

11 value mapping..........................................................................................................97
12 Table 83: Routing Request ↔ Provide Roaming Number Request (Network Provided
13 number) Parmater Mapping......................................................................................99
14 Table 84: Routing Request ↔ Provide Roaming Number Request (User Provided number)
15 Parameter Mapping................................................................................................100
16 Table 85: Routing Request ↔ Provide Roaming Number Request (Two calling party
17 numbers) Parameter Mapping ................................................................................101
18 Table 86: Routing Request ↔ Provide Roaming Number Request(Caller Id Restricted)

20 Table 87: Cancel_Location_Request ↔ REGCAN (Subscriber Deletion) Mapping ...................107
21 Table 88: Mapping of GSM MAP Messages ↔ ANSI MAP Messages (Subscriber Data
22 Modification)...........................................................................................................107
23 Table 89: Delete_Subscriber_Data ↔ Qualdir Mapping (Subscriber Data Modification)............107
24 Table 90: CANCEL_LOCATION_REQUEST ↔ REGCANC Parameter Mapping .....................108
25 Table 91: INSERT_SUBSCRIBER_DATA_REQUEST ↔ QUALDIR Parameter Mapping.........108
26 Table 92: INSERT_SUBSCRIBER_DATA_REQUEST ↔ profile ‘macro’ Mapping....................109
27 Table 93: Forwarding Information List to Calling Features Indicator Parameter Mapping ..........112
28 Table 94: Regional Subscription Data to Geographic Authorization Parameter Mapping...........114
29 Table 95: Call Barring Information List to Origination Indicator Parameter Mapping ..................114
30 Table 96: SSData List to Calling Features Indicator Parameter Mapping ..................................117
31 Table 97: Operator Determined Barring general data to Origination Indicator

x
N.S0028
1 Table 98: Operator Determined Barring HPLMN data to Origination Indicator Parameter
2 Mapping .................................................................................................................121
3 Table 99: Operator Determined Barring HPLMN data to Restriction digits Parameter
4 Mapping .................................................................................................................121
5 Table 100: Call Barring Information List to SMS Origination Restrictions Parameter
6 Mapping .................................................................................................................122
7 Table 101: Call Barring Information List to SMS Termination Restrictions Parameter
8 Mapping .................................................................................................................123
9 Table 102: Call Barring Information List to Termination Restriction Code Parameter
10 Mapping .................................................................................................................124
11 Table 103: SSData List to SMS Origination Restrictions Parameter Mapping ...........................125
12 Table 104: SSData List to SMS Termination Restrictions Parameter Mapping..........................125
13 Table 105: ISD_RESPONSE and DSD_RESPONSE to Qualdir Return Error Mapping.............130
14 Table 106: Qualdir Return Error to INSERT_SUBSCRIBER_DATA_RESPONSE and

15 DELETE_SUSBCRIBER_DATA_RESPONSE Error Mapping .................................130
16 If the response to FSM indicates a failure in the delivery of the short message, the IIF shall
17 map the cause value received to a corresponding SMS_CauseCode value in
18 the SMDPP Return Result, as described in.............................................................132
19 Table 107: Short Message Service in GSM Foreign Mode (for CMT) Message Mapping ..........134
20 Table 108: Short Message Service in ANSI-41 Foreign Mode (for CMT) Message Mapping ....134
21 Table 109: SMDPP to MT_Forward Short Message Parameter Mapping for GSM Foreign
22 Mode......................................................................................................................135
23 Table 110: MT_Forward Short Message to SMDPP Parameter Mapping for ANSI-41
24 Foreign Mode.........................................................................................................136
25 Table 111: SM-RP-UI in MT_FORWARD_SHORT_MESSAGE for MAP V2 Parameter

26 Values for GSM Foreign Mode ...............................................................................136

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

32 in GSM Foreign Mode ............................................................................................140
33 Table 115: ANSI-41 SMDPP to GSM Forward_Short_Message Parameter Mapping for MO

34 SMS in ANSI-41 Foreign Mode...............................................................................141
35 Table 116: Forward_Short_Message to SMS_CauseCode Values in SMDPP Return Result

36 Error Mapping ........................................................................................................147
xi
N.S0028
1 Table 117: SMDPP to Forward_Short_Message Error Mapping ...............................................149
2 If the User Error parameter is populated in the GSM_FSM_ACK, then map this value into
3 the SMS_CauseCode according to.........................................................................151
4 Next, it populates the stored originating SMSC address and transaction ID. If the User
5 Error parameter is populated in GSM_FSM_ACK, then this value is mapped into
7 Table 118: Short Message Service (for GHOST or WEMT) Message Mapping.........................153
8 Table 119: Alerting for an ANSI-41 Subscriber in GSM Foreign Mode Parameter Mapping.......154
9 Table 120: Alerting for a GSM Subscriber in ANSI-41 Foreign Mode Parameter Mapping ........155
10 Table 121: SMDPP to Forward Short Message for Mobile Terminated

11 GHOST/WEMTTeleservice Parameter Mapping in GSM Foreign Mode ..................155
12 Table 122: Forward Short Message to SMDPP for Mobile Terminated GHOST/WEMT
13 Teleservice Parameter Mapping in ANSI Foreign Mode ..........................................156
14 Table 123: Forward Short Message to SMDPP for Mobile Originated GHOST/WEMT in
15 GSM Foreign Mode Parameter Mapping.................................................................157
16 Table 124: SMDPP to Forward Short Message for Mobile Originated GHOST/WEMT
17 Teleservice Parameter Mapping in ANSI-41 Foreign Mode .....................................158
18 Table 125: HLPI for GHOST ....................................................................................................158
19 The IIF is responsible for mapping GSM MAP_FSM_ACK Return Errors to ANSI-41
20 SMS_CauseCodes according to.............................................................................159
21 Table 126: Teleservice Server Address Mapping in IIF.............................................................160
22 Table 127: Message Waiting Notification in GSM Foreign Mode Message Mapping .................163
23 Table 128: Message Waiting Notification in ANSI-41 Foreign Mode Message Mapping ............163
24 Table 129: Regnot to Forward Short Message for Message Waiting Notification Parameter
25 Mapping .................................................................................................................164
26 Table 130: QUALDIR to Forward Short Message for Message Waiting Notification
28 Table 131: Forward Short Message to QUALDIR for Message Waiting Notification
30 Table 132: Forward Short Message to SMDPP for Message Waiting Notification Parameter
31 Mapping .................................................................................................................165
32 Table 133: SM-RP-UI in Message FORWARD-SHORT-MESSAGE For MAP V2 Parameter

33 Encoding................................................................................................................166
34 Table 134: SM-RP-UI in Message FORWARD_SHORT-MESSAGE for MAP V1 Parameter

35 Encoding................................................................................................................168
xii
N.S0028
1 Table 135: qualdir return error to FORWARD_SHORT_MESSAGE response Error

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

6 Mapping .................................................................................................................172
7 Table 139: MAP_INSERT_SUBSCRIBER_DATA_REQUEST → regnot Parameter Mapping ...173
8 Table 140: MAP_UPDATE GPRS LOCATION RESPONSE → regnot Parameter Mapping.......174
9 Table 141: MAP_INSERT_SUBSCRIBER_DATA_REQUEST → profile ‘macro’ Mapping.........175
10 Table 141 A: ROUTREQ → MT_Forward Short Message Parameter Mapping ........................178
14 Table 142: Alerting for an ANSI-41 Subscriber for GPRS in GSM Foreign Mode Parameter
15 Mapping .................................................................................................................182
18 Table 143: ANSI-136-710 to GHOST Parameter Mapping........................................................187
19 Table 144: TP Derived Values .................................................................................................188
20 Table 145: GHOST to ANSI-136-710 Parameter Mapping........................................................190
21 Table 146: CMT Derived Values ..............................................................................................191
22 Table 147: SMS_CauseCode to TP-STATUS Mapping ............................................................192
23 Table 148: SMS-STATUS-REPORT Derived Values................................................................194
24 Table 149: RP-ERROR Cause to R-Cause for Mobile Station Response to Mobile
25 Terminated Transfer Attempt. .................................................................................197
26 Table 150: ANSI-41 SMS_CauseCode to ANSI-136 R-Cause Code Mapping ..........................198
27 Table 151: ANSI-136 R-Cause Code to RP-ERROR Cause Mapping within the Mobile
28 Station ...................................................................................................................198
29 Table 152: UPDATE_LOCATION_REQUEST ->REGNOT Parameter Mapping .......................199
30 Table 1: Location Updating in GSM Foreign Mode Message Mapping........................................12
31 Table 2: Location Updating in ANSI-41 Foreign Mode Message Mapping...................................13
32 Table 3: MS Purging Message Mapping.....................................................................................13
xiii
N.S0028
1 Table 4: Location Cancellation Message Mapping......................................................................13
2 Table 5: UPDATE_LOCATION_REQUEST ↔ REGNOT Parameter Mapping............................13
3 Table 6: INSERT_SUBSCRIBER_DATA_REQUEST ↔ regnot Parameter Mapping ..................15
4 Table 7: UPDATE LOCATION RESPONSE ↔ regnot Parameter Mapping ................................16
5 Table 8: MS_PURGE_REQUEST ↔ MS INACTIVE Parameter Mapping...................................16
6 Table 9: CANCEL_LOCATION_REQUEST ↔ REGCANC Parameter Mapping .........................17
7 Table 10: UPDATE_LOCATION_RESPONSE to regnot Error Mapping .....................................20
8 Table 11: regnot return errors to UPDATE_LOCATION_RESPONSE Error Mapping .................21
9 Table 12 Fault Recovery Message Mapping ..............................................................................23
10 Table 13: GSM RESET ↔ ANSI UNRELDIR Parameter Mapping ..............................................23
11 Table 14: Automatic Call Delivery Message Mapping.................................................................27
12 Table 15: ROUTREQ ↔ PROVIDE_ROAMING_NUMBER_REQUEST Parameter

13 Mapping ...................................................................................................................28
15 Mapping ...................................................................................................................30

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

18 Mapping ...................................................................................................................56
19 Table 46: Activate/Deactivate SS Response ↔ Feature Request Return Error Mapping.............57
20 Table 47: Activate/Deactivate SS Request to FEATREQ Parameter Mapping ............................57
22 Table 49: Activate/Deactivate SS Response default parameter values .......................................59
23 Table 50: Feature Request Invoke to Activate/Deactivate SS Request Parameter Mapping........60
24 Table 51: Activate/Deactivate SS Request default parameter.....................................................60

27 Response Error Mapping..........................................................................................64

29 Mapping ...................................................................................................................64
xv
N.S0028

2 Mapping ...................................................................................................................65

4 Mapping ...................................................................................................................66

6 Error Mapping ..........................................................................................................67
7 Table 58: Supplementary Service Registration Message Mapping .............................................70
8 Table 59: Register SS Request ↔ FEATREQ parameter mapping.............................................71
9 Table 60: Register SS Response ↔ Feature Request Return Result Parameter Mapping ..........72
10 Table 61: Register SS Response ↔ Return Error Parameter Mapping .......................................73
11 Table 62: Register SS Request to Feature Request Invoke parameter mapping.........................74
13 Table 64: Register SS Response default parameter values........................................................76
14 Table 65: FEATREQ to Register SS Request parameter mapping .............................................77
15 Table 66: Register SS Request default parameter......................................................................77
18 mapping ...................................................................................................................80
19 Table 69: Supplementary Service Erasure Message Mapping....................................................83
20 Table 70: Erase SS Request ↔ FEATREQ parameter mapping.................................................83
21 Table 71: Erase SS Response ↔ Feature Request Return Result parameter mapping ..............84
22 Table 72: Erase SS Response ↔ Return Error parameter mapping ...........................................85
23 Table 73: Erase SS Request to FEATREQ parameter mapping .................................................86
24 Table 74: Feature Request Invoke default parameter.................................................................87
25 Table 75: Erase SS Response default parameter values............................................................88
26 Table 76: FEATREQ to Erase SS Request parameter mapping ................................................89
27 Table 77: Erase SS Request default parameter .........................................................................89
29 Table 79: FeatureRequest Return Result to Register SS Response User Error ..........................91
30 Table 80: Retrieval of Forward-to-Number in GSM Foreign Mode ..............................................93
xvi
N.S0028

2 mapping ...................................................................................................................94

4 value mapping..........................................................................................................95
6 number) Parmater Mapping......................................................................................97
7 Table 84: Routing Request ↔ Provide Roaming Number Request (User Provided number)
8 Parameter Mapping..................................................................................................98
10 numbers) Parameter Mapping ..................................................................................99

13 Table 87: Cancel_Location_Request ↔ REGCAN (Subscriber Deletion) Mapping ...................105
15 Modification)...........................................................................................................105
16 Table 89: Delete_Subscriber_Data ↔ Qualdir Mapping (Subscriber Data Modification)............105
17 Table 90: CANCEL_LOCATION_REQUEST ↔ REGCANC Parameter Mapping .....................106
18 Table 91: INSERT_SUBSCRIBER_DATA_REQUEST ↔ QUALDIR Parameter Mapping.........106
19 Table 92: INSERT_SUBSCRIBER_DATA_REQUEST ↔ profile ‘macro’ Mapping....................107
20 Table 93: Forwarding Information List to Calling Features Indicator Parameter Mapping ..........109
21 Table 94: Regional Subscription Data to Geographic Authorization Parameter Mapping...........111
22 Table 95: Call Barring Information List to Origination Indicator Parameter Mapping ..................111
23 Table 96: SSData List to Calling Features Indicator Parameter Mapping ..................................114

27 Mapping .................................................................................................................118
29 Mapping .................................................................................................................118
31 Mapping .................................................................................................................119
33 Mapping .................................................................................................................120
xvii
N.S0028
2 Mapping .................................................................................................................121
3 Table 103: SSData List to SMS Origination Restrictions Parameter Mapping ...........................122
4 Table 104: SSData List to SMS Termination Restrictions Parameter Mapping..........................122
5 Table 105: ISD_RESPONSE and DSD_RESPONSE to Qualdir Return Error Mapping.............127

7 DELETE_SUSBCRIBER_DATA_RESPONSE Error Mapping .................................127
11 Table 107: Short Message Service in GSM Foreign Mode (for CMT) Message Mapping ..........131
12 Table 108: Short Message Service in ANSI-136 Foreign Mode (for CMT) Message
13 Mapping .................................................................................................................131
15 Mode......................................................................................................................132
17 Foreign Mode.........................................................................................................133

19 Values for GSM Foreign Mode ...............................................................................133

21 Encoding for GSM Foreign Mode............................................................................134
23 ANSI-41 Foreign Mode...........................................................................................135

25 in GSM Foreign Mode ............................................................................................136

27 SMS in ANSI-41 Foreign Mode...............................................................................137

29 Error Mapping ........................................................................................................142
30 Table 117: SMDPP to Forward_Short_Message Error Mapping ...............................................144
34 Error parameter is populated in GSM_FSM_ACK, then this value is mapped into
36 Table 118: Short Message Service (for GHOST) Message Mapping ........................................148
xviii
N.S0028
1 Table 119: Alerting for an ANSI-136 Subscriber in GSM Foreign Mode Parameter Mapping.....149
2 Table 120: Alerting for a GSM Subscriber in ANSI-136 Foreign Mode Parameter Mapping.......150
3 Table 121: SMDPP to Forward Short Message for Mobile Terminated GHOST Teleservice
4 Parameter Mapping in GSM Foreign Mode.............................................................150
5 Table 122: Forward Short Message to SMDPP for Mobile Terminated GHOST Teleservice
6 Parameter Mapping in ANSI Foreign Mode.............................................................151
7 Table 123: Forward Short Message to SMDPP for Mobile Originated GHOST in GSM
8 Foreign Mode Parameter Mapping .........................................................................152
9 Table 124: SMDPP to Forward Short Message for Mobile Originated GHOST Teleservice
10 Parameter Mapping in ANSI-41 Foreign Mode........................................................153
11 Table 125: HLPI for GHOST ....................................................................................................153
13 SMS_CauseCodes according to.............................................................................154
14 Table 126: Teleservice Server Address Mapping in IIF.............................................................154
15 Table 127: Message Waiting Notification in GSM Foreign Mode Message Mapping .................158
16 Table 128: Message Waiting Notification in ANSI-136 Foreign Mode Message Mapping ..........158
17 Table 129: Regnot to Forward Short Message for Message Waiting Notification Parameter
18 Mapping .................................................................................................................159
23 Table 132: Forward Short Message to SMDPP for Message Waiting Notification Parameter
24 Mapping .................................................................................................................160

26 Encoding................................................................................................................161

28 Encoding................................................................................................................163

30 Mapping .................................................................................................................164
31 Table 136: SMSDPP to FORWARD_SHORT_MESSAGE response Error Mapping .................164
32 Table 137: Location Updating GPRS in GSM Foreign Mode Message Mapping .......................166
33 Table 138: MAP_UPDATE_GPRS_LOCATION_REQUEST → REGNOT Parameter

34 Mapping .................................................................................................................167
xix
N.S0028
1 Table 139: MAP_INSERT_SUBSCRIBER_DATA_REQUEST → regnot Parameter Mapping ...168
2 Table 140: MAP_UPDATE GPRS LOCATION RESPONSE → regnot Parameter Mapping.......169
3 Table 141: MAP_INSERT_SUBSCRIBER_DATA_REQUEST → profile ‘macro’ Mapping.........170
4 Table 141 A: ROUTREQ → MT_Forward Short Message Parameter Mapping ........................173
5 Table 142: Alerting for an ANSI-136 Subscriber for GPRS in GSM Foreign Mode
7 Table 143: ANSI-136-710 to GHOST Parameter Mapping........................................................182
8 Table 144: TP Derived Values .................................................................................................183
9 Table 145: GHOST to ANSI-136-710 Parameter Mapping........................................................185
10 Table 146: CMT Derived Values ..............................................................................................186
11 Table 147: SMS_CauseCode to TP-STATUS Mapping ............................................................187
12 Table 148: SMS-STATUS-REPORT Derived Values................................................................189
14 Terminated Transfer Attempt. .................................................................................192
15 Table 150: ANSI-41 SMS_CauseCode to ANSI-136 R-Cause Code Mapping ..........................193
17 Station ...................................................................................................................193
18
19
xx
N.S0028
2 List of Figures
3
4 There are no figures in this volume.
xxi
N.S0028
2 Foreword
3
7 standard is to achieve fully automatic, two-way interoperability between the heterogeneous
8 networks. Services supported by this standard are described along with the associated information
9 flows and message mappings. However, not all services and associated capabilities of ANSI-41
10 MAP and GSM MAP are supported by this standard. In general the attempt has been to focus on
11 the key subscriber services needed in the market.
12 The focus of this the first release of this standard is on common GSM and ANSI-136 TDMA
13 services and associated network signaling (i.e. ANSI-41 MAP and GSM MAP). A pre-requisite for
14 this interoperability is Multi-mode mobile stations with an enhanced SIM card for roaming between
15 ANSI-136, GSM, and AMPS networks.
17 MAP to achieve the described interworking and interoperability. However, due to differences
18 between the services and associated capabilities of the MAP protocols, complete and fully
19 transparent interoperability may not have been achieved for some services. Future releases of this
20 standard may require changes to ANSI-41 MAP, GSM MAP and the associated services to achieve
21 full transparency while roaming between the different networks.
23 required to support other air interfaces supported by ANSI-41 MAP (e.g., IS-95, cdmaOne, and
24 cdma2000). This may be accomplished in future release of this standard.
25 Aspects of TIA/EIA-136 Revision C have been incorporated into this standard.
26 Revision A adds the capability of getting GPRS services when roaming in GSM Foreign Mode.
27 Revision B adds two way roaming between GSM and CDMA systems
28 Information disclosed in this document is subject to the export jurisdiction of the US Department of
29 Commerce as specified in Export Administration Regulations (title 15 CFR parts 730 through 774 inclusive).
30 The information contained herein may not be exported or re-exported to Cuba, Iran, Iraq, Libya, North Korea,
31 Sudan, or Syria. Contact the Telecommunications Industry Association, Arlington, VA or
32 http://ftp.tiaonline.org/tr-45/tr45ahag/public%20documents
33
34
35
36
37
38
39
40
xxii
N.S0028
1
2
3
4
5
6
7 (This page intentionally left blank.)
xxiii
N.S0028
1 1 Introduction
2
3 1.1 General
4
5 When a subscriber to one network type (e.g., ANSI-41) roams to a network of another type
6 (e.g., GSM), interworking and interoperability functions are required to support roaming and
7 enable service. This standard describes an Interworking and Interoperability Function (IIF) to
8 support this cross-technology roaming between ANSI-41 and GSM networks. The IIF supports
9 a multi-mode mobile station with a removable Subscriber Identity Module (SIM). The standard
10 also defines the required network message mappings between ANSI-41 MAP and GSM MAP to
11 support the mobile terminal and associated services.
12 This standard includes the support of cross-technology roaming from an ANSI-41 based
13 network to a GPRS network. The GPRS network may be coupled with a GSM network. This
14 feature requires enhancement to the Interworking and Interoperability Function (IIF) which
15 supports a multi-mode mobile station and Subscriber Identity Module (SIM) with GPRS
16 functionality.
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 applied as unidirectional only. (Annex C)
20
21 1.2 Purpose
22
23 The purpose for this standard is to define and describe the functions necessary for roaming
24 between ANSI-41 MAP and GSM MAP based networks in the support of roaming subscribers.
25 This includes a capability to allow a subscriber to an ANSI-41 based network (e.g., an ANSI-
26 136 41, TDMA or CDMA native subscriber) with a mobile terminal supporting GPRS service to
27 roam to a GPRS network in GSM Foreign Mode.
28 1.3 Scope
29
30 The scope of this standard are the services, information flows, and message mappings which
31 require interworking and interoperability functional specifications to support roaming between
32 ANSI-41 MAP [6] and GSM MAP [3] networks.
33 The scope of this volume is to describe the processing, messages and parameters for
34 GPRS/GSM and ANSI-41 network interoperability.
35 1.4 Organization
36
1
N.S0028

4 Volume 3 - Message Flows
5
6 This volume is organized according to the following:
7 2 References - is a list of references specific to this volume of the standard.
8 3 Definitions and Acronyms - defines words and acronyms that are used in this volume of
9 the standard.
10 4 Message Mappings - describes the stage 3 processing required to map messages
11 between ANSI-41 and GSM MAP.
12 Annex A Short Message Service Procedures within an ANSI-136 Network - contains a
13 description of mapping CMT to GHOST mapping for Short Messages.
14 Annex B Cause Code Mapping at non-IIF nodes - contains a description of cause code
15 mappings at non-IIF nodes.
16 Annex C One-way roaming from CDMA to GSM - contains a descriptio
17 Of the optional one-way roaming procedures, mappings
18
2
N.S0028
2 2 References
3
4 [1] GSM 03.18 Version 6.2.0 Release 1997 “ Digital cellular communication system (Phase
5 2+); Basic call handling; Technical realisation”, November 1998, ETSI.
6 [2] GSM 03.79 version 6.2.0 release 1997, “Digital cellular telecommunications system
7 (Phase 2+); Support of Optimal Routeing (SOR) Technical Realisation”.
8 [3] GSM 09.02 Version 6.2.0 Release 1997 “ Digital cellular communication system (Phase
9 2+); Mobile Application Part (MAP) specification”, August 1998, ETSI;
10 [4] GSM 02.60 version 6.3.1 Release 1997 “General Packet Radio Service (GPRS); Service
11 Description, Stage 1”
12 [5] GSM 03.60 version 6.8.0 Release 1997 “General Packet Radio Service (GPRS); Stage
13 2”
14
15 [6] TIA/EIA-41-D: “Cellular Radiotelecommunications Intersystem Operations,” December

16 1997, ANSI.
17 [7] TIA/EIA/IS-751: “TIA/EIA-41-D Modifications to support IMSI”, February 1998

18 [8]TIA/EIA/IS-807: “TIA/EIA-41-D Enhancements for Internationalization”, August 1999
25
26 [11] "TIA/EIA-IS-2000-A, cdma2000 Series, March 2000, plus addenda"Mobile Station-Base
27 Station Compatibility Standard for Dual-Mode Spread Spectrum Systems;
29 GSM, Published TBD. [12]"Enhanced Cryptographic Algorithms, Revision B," TR45AHAG, Published
30 TBD
31
32
33
3
N.S0028

3
4 3.1 Definitions
5
6 AMPS
7
8 Advanced Mobile Phone Service (AMPS) is the same as ANSI EIA/TIA-553, which is an analog
9 air interface protocol standard for mobile stations and their associated base stations. AMPS
11
12 ANSI-41
13
14 ANSI-41 is the same as ANSI TIA/EIA-41, which is a network protocol standard to support
15 intersystem operation of cellular networks, such as ANSI-136 networks. ANSI-41 is the North
16 American version of ITU defined MAP. Key intersystem support defined by ANSI-41 includes
17 automatic roaming, intersystem handoff, and intersystem operation, administration, and
18 maintenance. Among other things, ANSI-41 defines the interfaces between MSCs, between the
19 MSC/VLR and the HLR/AC, and between the MSC and the Short Message Service Center
20 (SMS-C) or Teleservice Server (TS).
21
22 ANSI-136
23
24 ANSI-136 is the same as ANSI TIA/EIA-136, which is a TDMA air interface protocol standard
25 for mobile stations and their associated base stations. ANSI-136 is a dual-mode standard that
26 includes digital (TDMA) operation at 800 MHz and 1900 MHz, and analog (AMPS) operation at
27 800 MHz. ANSI-136 networks use ANSI-41 for intersystem signaling.
28
29 ANSI-136 Mode
30
31 ANSI-136 mode indicates the condition or state of a mobile station accessing an ANSI-136
32 network.
33
35
36 ANSI-136 foreign mode indicates the condition or state of a GSM native subscriber accessing
37 an ANSI-136 network.
38
40
41 ANSI-136 native mode indicates the condition or state of an ANSI-136 native subscriber
42 accessing an ANSI-136 network.
43
45
46 ANSI-136 native subscriber indicates an end user whose primary or home subscription resides
47 in an ANSI-136 network. These subscribers include both home subscribers from the ANSI-136
48 network, as well as roamers from other ANSI-136 networks.
49
50
4
N.S0028

4 CDMA
5 CDMA as used in this document, refers to TIA/EIA -95 [9] or TIA/EIA-2000 [10], which is a
6 CDMA air interface protocol standard for mobile stations and their associated base stations.
7 CDMA is a dual-mode standard that includes digital (CDMA) operation and analog (AMPS)
8 operation. CDMA networks use ANSI-41 for intersystem signaling.
9 CDMA Mode
11
12 CDMA Foreign Mode
13 CDMA foreign mode indicates the condition or state of a GSM native subscriber accessing a
14 CDMA network.
15
16 CDMA Native Mode
18 CDMA network.
19
21 CDMA native subscriber indicates an end user whose primary or home subscription resides in
22 an
25 Class A mobile
26 Class A mobile station is a GSM mobile that can operate in Class A mode: both GSM circuit-
27 switched and GPRS packet services simultaneously.
28 Class B mobile
29 Class B mobile station is a GSM mobile that operates in Class B mode: it can operate
30 alternatively in GSM circuit-switched or in GPRS packet services (1 type service at a time). The
31 mobile can be attached to GSM and GPRS networks simultaneously in this case. The
32 subscriber cannot be simultaneously attached to a TDMA ANSI-41 MSC.
33 Class C mobile
34 Class C mobile station is a GSM mobile that can only operate in Class C mode: GSM circuit-
35 switched only or GPRS packet services only. The mobile is attached to only one network at a
36 time.
37 GPRS HLR
38 General Packet Radio Service Home Location Register is the HLR responsible for GPRS
39 functions. It interfaces with the SGSN and GGSN and Authentication Center.
41 GPRS in GSM Foreign Mode is a subset of GSM Foreign Mode and indicates the condition or
42 state of an ANSI-136 41native subscriber accessing a GPRS network; the GPRS network may
43 be coupled with a GSM network.
44 GSM
45
5
N.S0028
1 Global System for Mobile Communications (GSM) defines both air interface and network
2 intersystem protocol standards for mobile stations (MS), base station systems (BSS), and
3 network switching systems (NSS).
4
5 GSM CS attached
6 GSM circuit-switched services attached means that the subscriber is attached to a GSM MSC.
7 This is also referred to as IMSI attached.
8 GSM CS detached
9 GSM circuit-switched services detached means that the subscriber is detached from a GSM
10 MSC. This is also referred to as IMSI detached.
11
12 GSM Mode
13
15
16 GSM Foreign Mode
17
18 GSM foreign mode indicates the condition or state of an ANSI-136 41 native subscriber
19 accessing a GSM network.
20
21 GSM Native Mode
22
24 network.
25
27
28 GSM native subscriber indicates an end user whose primary or home subscription resides in a
29 GSM network. These subscribers include both home subscribers from the GSM network, as
30 well as roamers from other GSM networks.
31
32 Mobile Station
33
36
38 A smart card that plugs into the mobile equipment and that contains the authentication
39 algorithms, and stores service-oriented subscription information.
40
41 3.2 Acronyms
42
43 AC Authentication center
6
N.S0028

2 BMI Base Station, Mobile Switching System, and Interworking Function
4 BOIC-exHC Barring of Outgoing International Calls Except to HPLMN Country
10 CFU Call Forwarding Unconditional
11 CPHS Common PCN Handset Specification
12 CS Circuit-Switched
13 DCS Data Coding Scheme
14 EDGE Enhanced Data Rates Through Global Evolution
18 FC Feature Code
19 FSM Forward Short Message
21 GHOST GSM Hosted SMS Teleservice
25 HLPI Higher Layer Protocol Indicator
32 MC ANSI-136 41 Message Center (for SMS)
7
N.S0028
1 MDN Mobile Directory Number

5 MS Mobile Station
7 MSCID MSC Identification Number
10 MSRN Mobile Station Routing Number
14 OR Optimal Routing
15 PCS Personal Communication Service
16 PDU Packet Data Unit
20 PRN Provide Roaming Number
21 SC Service Center
24 SMDPP Short Message Delivery Point-to-Point
25 SME Short Message Entity
31 TLDN Temporary Location Directory Number
32 TSAR Teleservice Segmentation and Reassembly
8
N.S0028
1 UDH Universal Data Header

4 WEMT Wireless Enhanced Messaging Teleservices
5
6
9
N.S0028
2 4 Message Mappings
3
4 The IIF shall perform the translation of messages, parameters and parameter values in
5 accordance with the tables included in this volume of the standard. The following notation is
6 used in accordance with the definitions given in GSM 09.02 [3] and ANSI-41 [6], [7], 0.
7 Within the following tables, the parameters are identified as either being:
8 M Mandatory,
9 C Conditional
10 O Service Provider Optional
11 U Service User Optional
12 The following notation is used in this standard to identify parameters as being syntactically
13 optional but semantically required to be sent by the IIF in order to support interoperability:
14 R Required.
15 Refer to GSM 09.02 [3] and ANSI-41 [6], [7], 0 for a description of the messages, parameters
16 and parameter values.
17 When the IIF receives either a GSM MAP message or an ANSI MAP message, it shall apply
18 the following rules regarding the handling of parameters within those messages:
19 The IIF shall populate mandatory parameters in messages sent by the IIF, regardless
20 of whether mapping of parameters is possible.
21 The IIF may populate optional parameters in messages sent by the IIF, regardless of
22 whether mapping of parameters is possible.
23 All parameters shall be populated in accordance with GSM 09.02 [3] or ANSI-41 [6], [7], 0.
24 Where there is no direct mapping for parameters, a hyphen (‘-‘) has been entered in the
25 corresponding table.
26
27 4.1 Mobility Procedures

28
29 Existing mobility procedures described in either GSM 09.02 [3] or ANSI-41 [6] are also directly
30 applicable to the IIF when it is emulating a GSM or ANSI-41 functional network element.
31 Enhancements/modifications to ANSI-41 [7], 0 are also applicable.
32 4.1.1 Location Registration

33
34 The location registration procedure is used to update the location information held in the
35 network. This location information is used to route incoming calls and short messages to the
36 roaming subscriber.
10
N.S0028
1 The Location registration procedure is also used to cancel location information held in the
2 network.
3 4.1.1.1 Detailed Procedures

4
5 4.1.1.1.1 Location Updating

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

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

11
12 4.1.1.2.1 Mapping of Messages

13
14 Table 1 shows the mapping between GSM MAP messages and ANSI MAP messages related
15 to Location Registration.
16 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
17
18
1
19 This message can also contain error values if the location updating procedure is unsuccessful.
20 If the location updating procedure fails, the mapping is as shown in 4.1.1.3.
13
N.S0028
2 to Location Registration in ANSI-41 Foreign Mode.
3 Table 2: Location Updating in ANSI-41 Foreign Mode Message Mapping

UPDATE_LOCATION_REQUEST REGNOT
UPDATE_LOCATION_RESPONSE Regnot
4
5 Table 3 shows the mapping between GSM MAP messages and ANSI MAP messages (MS
6 Purging, regardless of mode of operation)
7
8 Table 3: MS Purging Message Mapping

MS_PURGE MS Inactive
9
10
12 to Location Cancellation.
13 Table 4: Location Cancellation Message Mapping

CANCEL_LOCATION_REQUEST REGCANC
CANCEL_LOCATION_RESPONSE regcanc
14
15 4.1.1.2.2 Mapping of Parameters

16
17 Table 5 through Table 9 shows the mapping of parameters, which the IIF shall perform
18 regardless of the mode of operation (GSM Foreign Mode or ANSI-41 Foreign Mode).
19 Table 5: UPDATE_LOCATION_REQUEST ↔ REGNOT Parameter Mapping

GSM MAP Status ANSI_MAP_REGNOT Status
_UPDATE_LOCATION_REQUE
ST
IMSI M ElectronicSerialNumber M
MSID M
1 1
MSC Address M MSCID (Serving MSC) M
- QualificationInformationCode M
- SystemMyTypeCode M
- MSCIdentificationNumber O
14
N.S0028
1
2 Table 5: UPDATE_LOCATION_REQUEST ↔ REGNOT Parameter Mapping (concluded)

ST
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 -
3
1
4 These parameters are used to convey a unique identifier from the IIF to the HLR, identifying
5 the serving MSC/VLR.
2
6 Parameters are included in ANSI specifications IS-41-C and later.
7
15
N.S0028
1
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
6
1
7 This parameter is itself a macro containing a number of other parameters. As far as mapping
8 of parameters is concerned, the IIF shall map the contents of the ‘Profile’ macro in the ANSI-41-
9 D ‘regnot’ to the contents of the GSM MAP _INSERT_SUBSCRIBER_DATA_REQUEST as
10 shown in Table 92
11
16
N.S0028
1 Table 7: UPDATE LOCATION RESPONSE ↔ regnot Parameter Mapping

_UPDATE_LOCATION_RESPO
NSE
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 MSC/VLR,
5 identifying the HLR.
3
9 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
12
17
N.S0028
1 Table 9: CANCEL_LOCATION_REQUEST ↔ REGCANC Parameter Mapping

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

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

10
11 If the Location Updating procedure fails at an ANSI-41 HLR, the HLR shall respond by either
12 sending:
13 An ANSI_MAP_regnot in a TCAP RETURN RESULT indicating authorization denied
14 (AUTHDEN) to the IIF, with one of the following reasons as defined in ANSI-41 [6]:
15 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.
18
N.S0028
TerminalType mismatch
1
2 The ANSI-MAP-regnot may optionally, indicate:
3 • The authorization period (DENAUTHPER) as defined in ANSI-41 [6]

4 • Access Info as defined in ANSI-41 [6]
5 Or, an ANSI_MAP_regnot in a TCAP RETURN ERROR one of the following error codes as
6 defined in ANSI-41 [6]:
7 Appropriate Error Codes in ANSI_MAP_regnot RETURN ERROR
Error Codes
MSID/HLRMismatch
ResourceShortage
OperationNotSupported
ParameterError
SystemFailure
8
9
19
N.S0028
1
2 Appropriate Error Codes in ANSI_MAP_regnot RETURN ERROR (concluded)
3
Error Codes
UnrecognizedParameterValue
MissingParameter
4
5 The IIF is therefore responsible for mapping any errors it receives from the HLR in the ANSI-
6 MAP-regnot to an equivalent error in the GSM-MAP-UPDATE-LOCATION RESPONSE towards
7 the serving GSM MSC/VLR.
8
9 The GSM-MAP-UPDATE-LOCATION RESPONSE may include one the following ‘user’ errors
10 as defined in GSM 09.02 [3]:
11 Appropriate User Errors
User Errors
unknown subscriber;
roaming not allowed;
system failure;
unexpected data
value.
12
13 The following ‘provider errors’ (protocol related errors) are also defined in GSM 09.02 [3]:
14 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.
15
20
N.S0028
1 If the Location Updating procedure fails at a GSM HLR, it returns a GSM MAP
2 _UPDATE_LOCATION_RESPONSE to the IIF, indicating a ‘user error’ as indicated above.
3 The IIF is therefore responsible for mapping any errors it receives into a corresponding error in
4 the ANSI_MAP_regnot towards the serving ANSI MSC/VLR. For further description of these
5 errors and when they are used, refer to either GSM 09.02 [3] or ANSI-41 [6].
6 Table below provides the mapping of both user errors and provider errors to the equivalent
7 value in either the AUTHDEN parameter in the ANSI_MAP_regnot RETURN RESULT or the
8 RETURN ERROR for ANSI-41 Foreign Mode.
9 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
10
11
12 Table 11 provides the mapping for GSM Foreign Mode.
13
21
N.S0028
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
6 If the Location Cancellation procedure fails at the IIF, existing procedures described in GSM
7 09.02 [3] and ANSI-41 [6] apply.
8
22
N.S0028
2 4.1.2 Fault Recovery

3
4 After the fault of a location register, the fault recovery procedures ensure that subscriber data in
5 the VLR becomes consistent with the subscriber data stored in the IIF or that subscriber data in
6 the IIF becomes consistent with the subscriber data that are stored in the HLR for the MS
7 concerned and that the location information in the IIF and VLR or HLR and IIF reflect accurately
8 the current location of the MS.
9

11
12 If the IIF receives an ANSI_MAP_UNRELDIR, it shall send a RETURN RESULT and clear the
13 records of those MSs associated with the requesting HLR. The IIF shall then send a GSM MAP
14 _RESET towards the serving VLR containing a unique identity, identifying the ANSI-41 HLR.
15 When the MS concerned next establishes authenticated radio contact (including a mobile
16 originated call attempt), the IIF shall receive a GSM MAP _UPDATE_LOCATION_REQUEST
17 and shall follow the procedures outlined in
18 4.1.1 Location Registration.
19 If the IIF receives a GSM MAP _RESET, it shall derive all involved MSs of that HLR either from
20 the HLR Identity List (if present), or from the HLR number. The IIF shall then mark these MSs
21 with the indicator "Location Information Confirmed in HLR" set to "Not Confirmed". The IIF shall
22 then send an ANSI_MAP_UNRELDIR towards the serving VLR containing a unique identity,
23 identifying the GSM HLR. The status "Not Confirmed" of the indicator "Location Information
24 Confirmed in HLR" forces the IIF to invoke the GSM MAP _UPDATE_LOCATION service after
25 establishment of authenticated radio contact with the MS concerned.
26 If the IIF suffers a failure, while operating in GSM Foreign Mode, it shall send a GSM MAP
27 _RESET to the serving GSM VLR once it has returned to a stable state. The IIF shall not
28 receive a response. The IIF may also send an ANSI_MAP_BULKDEREG to the ANSI-41 HLR.
29 If the IIF suffers a failure, while operating in ANSI-41Foreign Mode, it shall send an
30 ANSI_MAP_UNRELDIR to the serving ANSI-41 VLR once it has returned to a stable state. The
31 IIF shall receive an indication of success or failure.
32 If the IIF receives an ANSI_MAP_BULKDEREG, it shall send a RETURN RESULT to the
33 requesting VLR and clear the location pointer of those MSs that were registered in the
34 requesting VLR. Otherwise, the IIF shall send a RETURN ERROR with an appropriate error
35 value to the requesting VLR.
36

38
39 The IIF shall perform the mapping of messages, parameters and parameter values related to
40 fault recovery in accordance with the tables presented in 4.1.2.2.
41
23
N.S0028

3
5 to fault recovery in either mode of operation (GSM Foreign mode or IS-136 41 Foreign mode)
6 Table 12 Fault Recovery Message Mapping

RESET UNRELDIR
7

9
10 Table 13 shows the mapping of parameters, which the IIF shall perform regardless of the mode
11 of operation (GSM Foreign Mode or ANSI-41Foreign Mode).
12 Table 13: GSM RESET ↔ ANSI UNRELDIR Parameter Mapping

GSM MAP _RESET Status ANSI_MAP_UNRELDIR Status
HLR Id LIST U
1
HLR Number M MSCID (HLR) 1 R
13
1
14 These parameters are used to convey a unique identifier from the IIF to the serving VLR,
15 identifying the true HLR.
16
24
N.S0028

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

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

9

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

16
17 If the IIF receives an ANSI MAP_RoutingRequest Invoke message from the ANSI-41 HLR, it
18 shall check if the terminating call can be placed to that subscriber. The IIF shall then deduce
19 the IMSI from the MSID for that subscriber and populate the corresponding field of the
20 MAP_PROVIDE_ROAMING_NUMBER message.
21 The IIF shall store the BillingID received in the ANSI MAP_RoutingRequest Invoke message to
22 later be able to populate the corresponding field in the ANSI MAP_RoutingRequest Return
23 Result message.
24 If the MobileDirectoryNumber field is present and in an international format in the
25 MAP_RoutingRequest Invoke message, the IIF shall populate the MSISDN field in the
26 MAP_PROVIDE_ROAMING_NUMBER message with it. If the MobileDirectoryNumber is in
27 National format, the IIF shall convert it to an International format before populating the MSISDN
1
28 field .
29 The IIF shall then populate the MSC Number field in the
30 MAP_PROVIDE_ROAMING_NUMBER message with the serving MSC Number that had been
31 stored in the IIF at the time of the subscriber’s location registration.
32 The IIF shall then send the MAP_PROVIDE_ROAMING_NUMBER message to the GSM
33 MSC/VLR and wait for a response.
34 If the response indicates that the retrieval of routing information procedure has been
35 successful, the IIF shall deduce the MSRN from the MAP_PROVIDE_ROAMING_NUMBER
36 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.
26
N.S0028
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 ANSI-
4 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 [6] 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 [3] for retrieval of routing information are
13 also applicable to the IIF.
14
15 4.2.1.1.2 ANSI-41 Foreign Mode

16
17 If the IIF receives a MAP_PROVIDE_ROAMING_NUMBER message from the GSM HLR, it
18 shall check if the terminating call can be placed to that subscriber.
19 If the IIF determines that the subscriber is Not Reachable, it shall send a
20 MAP_PROVIDE_ROAMING_NUMBER Response message with User Error field indicating
21 Absent Subscriber to the GSM HLR.
22 Otherwise, the IIF shall deduce the MSID and ESN from the IMSI and populate the
23 corresponding fields of the ANSI MAP_RoutingRequest Invoke.
24 The IIF shall create a billing ID for that transaction and populate the corresponding field of the
25 ANSI MAP_RoutingRequest Invoke.
26 The MSCID address field shall be set to the IIF address.
27 The IIF shall also assign a predefined value (vendor specific) to the SystemMyTypeCode field,
28 indicating the IIF vendor identity.
29 If the MSISDN field is present in the MAP_PROVIDE_ROAMING_NUMBER, the IIF shall
1
30 populate the MobileDirectoryNumber field in the RoutingRequest Invoke message with it .
31 The IIF shall set the MSCIdentificationNumber and PC_SSN fields to its own ID.
32 The IIF shall then send the RoutingRequest Invoke message to the ANSI-41 MSC/VLR and
33 wait for a response.
34 If the response indicates that the retrieval of routing information procedure has been
35 successful, the IIF shall deduce the MSRN from the Digits (Destination) field of the
36 RoutingRequest Return Result and populate the MSRN field in the
37 MAP_PROVIDE_ROAMING_NUMBER ack. The MSRN shall have an E.164 format. Therefore,
38 if the TLDN is not in international format, the IIF shall add the country code digits associated
39 with the country of the serving system The IIF shall then forward the
40 MAP_PROVIDE_ROAMING_NUMBER ack to the GSM HLR.
1
As an alternative, the MSISDN may also be retrieved directly from the Subscriber profile,
pre-provisioned in the IIF.
27
N.S0028
1 If the response is unsuccessful, the IIF may receive a RoutingRequest Return Result with the
2 field AccessReasonDenied present, or a ReturnError message with an Error Code value. The
3 IIF shall map any Access Reason Denied or Error Code it receives to a User or Provider Error
4 in the MAP_PROVIDE_ROAMING_NUMBER return error.
5 For the cases of failure at the IIF on reception of the MAP_PROVIDE_ROAMING_NUMBER
6 request, (e.g. missing expected parameter, unidentified subscriber), the procedure described in
7 GSM 09.02 [3] for retrieval of routing information are applicable to the IIF.
8 For the cases of failure at the IIF on reception of the MAP_RoutingRequest Invoke message
9 return Result, the procedure described in ANSI-41 [6] for automatic call delivery is applicable to
10 the IIF.
11

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

20
22 to Automatic Call Delivery regardless of the mode of operation (GSM Foreign Mode or ANSI-41
23 Foreign Mode)
24 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
25
28
N.S0028

3
4 Table 15 and Table 16 show the mapping of parameters, which the IIF shall perform regardless
5 of the mode of operation (GSM Foreign Mode or ANSI-41 Foreign Mode).
6 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 -
7
29
N.S0028
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
CDMAServiceOption O -GSM BearerServiceCode or O (Note 6)
GSM TeleService
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
12
30
N.S0028
1
2 The following table shows the mapping of parameters between the Provide Roaming Number
3 Response and the Routing Request Return Result messages regardless of the mode of
4 operation (GSM Foreign Mode or ANSI-41 Foreign Mode).
6 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 BearerServiceCode or GSM O CDMAServiceOption O
TeleService (Note 3)
7
8 * These parameters are mutually exclusive
9 Note 1: If the request is unsuccessful.
10 Note 2: If User Error is present in Provide Roaming Number ack.
13
14 Or

16 (ANSI-41Foreign Mode)
Provide Roaming Number ack Status RoutingRequest Return Status
Error
User Error C Error Code O
Provider Error C
17
18 For detailed mapping of User/Provider Error parameter value to the AccessDeniedReason
19 parameter, see Table 22 and Table 23.
20
31
N.S0028
2 (GSM Foreign mode)
Routing Request Return Error Status Provide Roaming Number Status
ack
Error Code O User Error C
32
N.S0028
2 4.2.1.2.2.1 Mapping of parameter values in GSM Foreign Mode

3
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
10
33
N.S0028
1
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 request 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
7
34
N.S0028
2 4.2.1.2.2.2 Mapping of parameter values in ANSI-41 Foreign Mode

3
5 Table 21 presents how the IIF shall populate the parameters of the Routing Request Invoke
6 message to be sent to the ANSI-41 VLR. These fields cannot be mapped from the received
7 Provide Roaming Number request message.
8 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]
9
35
N.S0028
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
2

4
5 The following tables present the appropriate GSM MSC/VLR negative response to a Provide
6 Roaming Number message as described in GSM 09.02 [3].
7 Appropriate User Error value:
User Error value
Absent Subscriber
No roaming Number available
Facility Not supported
System Failure
Data Missing
Unexpected Data Value
8
9 Appropriate Provider Error value:
Provider Error value
Duplicated Invoke ID
Not supported service

Mistyped parameter
Resource limitation
Initiating Release
36
N.S0028
1
2
3 Appropriate Provider Error value (concluded):
Unexpected response from the peer

Service Completion Failure
No response from the peer

Invalid response received
4
5 The following tables present the appropriate ANSI-41 MSC/VLR negative response to a
6 Routing Request Invoke message as described in ANSI-41 [6].
7
8 Appropriate AccessDeniedReason parameter values in the RoutingRequest Return
9 Result:
AccessDeniedReason
Inactive
Busy
No page Response
Unavailable
10
11 Appropriate Error Code parameter value in the Return Error message:
Error Code value
UnrecognizedMIN
UnrecognizedESN
ResourceShortage
ParameterError (Note 1)
SystemFailure
MissingParameter
12
13 Note 1: The FaultyParameter field shall be present and populated with the appropriate Parameter
14 Identifier.
15
37
N.S0028

3
4 The IIF is responsible for the mapping of the User Error/Provider Error received in the Provide
5 Roaming Number response to the appropriate AccessDeniedReason in the RoutingRequest
6 Return Result message or Error Code in the Return Error.
7 The following tables present the preferred mapping.
8 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
9
10
11 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
12
13
38
N.S0028

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
11 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
12
13
39
N.S0028
2 4.2.2 Invocation of Conditional Call Forwarding in ANSI-41 Foreign Mode

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

9
10 4.2.2.1.1 Invocation of Call Forwarding before the call has been routed to the serving
11 MSC
12
13 The Call Forwarding procedure is invoked in the IIF when a terminating call attempt results in
14 an “unavailable” indication and the IIF is required to provide treatment for the “unavailable”
15 situation.
16 The following procedures are applicable at the IIF for Call Forwarding invocation:
17 If the IIF receives an ANSI_MAP_routreq indicating ‘access denied’, the IIF shall determine if
18 call forwarding is applicable for the call.
19 If call forwarding is applicable for the call, the IIF shall send a GSM MAP _PROVIDE
20 ROAMING_NUMBER_RESPONSE to the HLR.
21 The IIF shall process the forwarding request in one of the following two optional methods:
22 • Send the Forward_To_Number that corresponds to the access denied reason (stored
23 for the subscriber in the IIF). Refer to Table 26 or,
24 • Send a user error indicating “Absent Subscriber”. Refer to Table 27.

25 If call forwarding is not applicable for the call, the IIF shall follow the procedures outlined in
26 4.2.1 of this document
27 If the IIF receives an ANSI_MAP routreq Return Error or a Reject message, the IIF shall map
28 the Error Code it receives to a suitable User Error in the
29 MAP_PROVIDE_ROAMING_NUMBER RESPONSE as described in 4.2.1 of this document
30 For the cases of failure at the IIF on reception of the MAP_RoutingRequest Return Result, the
31 procedure described in ANSI-41 [6] for automatic call delivery is applicable to the IIF.
32
33 4.2.2.1.2 Invocation of Call Forwarding after the call has been routed to the serving
34 MSC
35
36 If the called party is either busy, not reachable or does not answer the call, the serving MSC
37 may redirect the call by sending REDREQ to the IIF, indicating the reason for failure.
38 If the IIF receives an ANSI_MAP_REDREQ, it shall determine if the message can be
39 processed:
40
N.S0028
1 If the message can be processed and optimal routing is supported, the IIF shall
2 follow the procedures outlined in 4.2.3 of this document for Optimal Routing for
3 late call forwarding.
4 If the message can be processed but optimal routing is not supported, the IIF
5 shall send an ANSI_MAP_redreq Reject message. On receipt of the Reject
6 message, the serving MSC may attempt to redirect the call by sending a
7 TRANUMREQ message to the IIF.
8 If the message cannot be processed, the IIF shall send an ANSI_MAP redreq
9 Return Reject message with the appropriate error code. On receipt of the Return
10 Reject message, the serving MSC may attempt to redirect the call by sending a
11 TRANUMREQ message to the IIF.
12 If the IIF receives an ANSI_MAP_TRANUMREQ, it shall determine if the
13 message can be processed.
14 If the message can be processed, the IIF shall send an ANSI_MAP_tranumreq
15 indicating the forwarded-to-number.
16 If the message cannot be processed, the IIF shall send an ANSI_MAP tranumreq indicating the
17 reason for failure.
18

20
21 4.2.2.2 presents the mapping of messages, parameters and parameter values that the IIF shall
22 perform.

24
25 These messages are the same as those in 4.2.1.2.1.
26

28
29 Table 26 represents how the IIF shall map the value of the parameter it has received to
30 populate the fields of the message it shall transmit.
32 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
33
34
41
N.S0028
2 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
3
4 Default parameters value
5 N/A

7
8 The following table presents the appropriate GSM MSC/VLR negative response to a Provide
9 Roaming Number message as described in GSM 09.02 [3].
User Error value
Absent Subscriber
No roaming Number available

Facility Not supported
System Failure
Data Missing
11
Mistyped parameter
Resource limitation
Initiating Release

13
42
N.S0028
1 The following table presents the appropriate ANSI-41 MSC/VLR negative response to a
2 Routing Request Invoke message as described in in ANSI-41 [6].
3 Appropriate AccessDeniedReason parameter values in the RoutingRequest Return Result:
4
AccessDeniedReason
Inactive
Busy
No page Response
Unavailable
5
7
Error Code value
UnrecognizedESN
ResourceShortage
ParameterError*
UnrecognizedParameterValue*
SystemFailure
MissingParameter*
8
9 Table 28: Return Error to User Error in the PRN response Error Mapping
Error Code value User Error


10
11
43
N.S0028
1 4.2.3 Optimal Routing after Late Call Forwarding

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

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

25
26 When the IIF receives a GSM-Provide Roaming Number message, it stores GMSC Address,
27 Call Reference Number and OR Interrogation Indicator parameters if they are present. It then
28 sends an ANSI-41Routing Request message to the VLR and awaits a response.
29 If successful ANSI-41 Routing Request response is received from VLR, it converts Temporary
30 Location Directory Number (TLDN) in to Mobile Subscriber Roaming Number (MSRN) and send
31 this information to HLR in GSM-Provide Roaming Number Acknowledge message.
32 Otherwise, the IIF sends a GSM-Provide Roaming Number negative response to HLR and
33 discards GMSC Address, Call Reference Number and OR Interrogation Indicator parameter
34 information if present.
35 If the IIF receives ANSI-41 Redirection Request message, it shall check GMSC Address.
36 If GMSC Address is available, it shall map Redirection Reason parameter to Forwarding

37 Reason. The IIF sends this information in addition to the Call Reference Number and
38 Forwarding Number in GSM-Resume Call Handling message to originating MSC using GMSC
39 Address and await a response.
44
N.S0028
1 Otherwise, the IIF rejects the ANSI-41 Redirection Request.

2 If the IIF receives GSM-Resume Call Handling Acknowledge message, it sends response of
3 ANSI-41- Redirection Request message to the MSC. Otherwise, if negative response of GSM-
4 Resume Call Handling is received, the IIF shall send ANSI-41-Redreq Return Error with an
5 appropriate error code to the MSC.
6

8
9 When the IIF receives an ANSI-41-Routing Request message, it stores Originating MSC ID,
10 TERMTRMT if present. The IIF then generates a Call Reference Number and sends it as a
11 parameter in the a GSM-Provide Roaming Number message to the VLR along with the GMSC
12 address set to the IIF address and along with the GMSC address set to the IIF address awaits
13 a response.
14 If successful GSM-Provide Roaming Number Acknowledge is received from VLR, it converts
15 MSRN to TLDN and sends this information to HLR in ANSI-41-Routing Request response
16 message.
17 Otherwise, the IIF sends an ANSI-41- Routing Request negative response (routreq) to HLR and
18 discards information of Originating MSCID and TERMTRMT (if present).
19 If the IIF receives GSM-Resume Call Handling, it shall use its Call Reference Number
20 parameter to corelate and determine the ANSI-41 originating MSC, and the IIF shall map the
21 Forwarding Reason parameter to Redirection Reason. The IIF sends this information to the
22 originating MSC in the ANSI-41-Redirection Request message and awaits a response.
23 If the IIF receives ANSI-41-Redirection Request response message, it sends a GSM-Resume
24 Call Handling Acknowledge message to the MSC. Otherwise, if negative response is received
25 (in form of return error), the IIF shall send GSM-Resume Call Handling Return Error with an
26 appropriate error code to the MSC.
27 The IIF shall perform the translation of messages, parameters and parameter values related to
28 Optimal Routing Support for Late Call Forwarding procedure in accordance with the tables
29 presented here. Refer to GSM 3.18 [1] and GSM 3.79 [2] and ANSI -41 [6] for a description of
30 messages, parameters and parameter values.
31
45
N.S0028

3
5
6 Table 29 shows the translation between GSM MAP messages and ANSI-41 MAP messages
7 related to Optimal Routing Support for Late Call Forwarding procedure.
8 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
9

11
12 The following tables show the mapping of parameters, which the IIF shall perform regardless of
13 the mode of operation.
14
46
N.S0028
2 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
DMHData:
- DMH AccountCodeDigits O
- DMH AlternateBillingDigits O
3
4
47
N.S0028
1
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)
- DMH_BillingDigits O
- MobileDirectoryNumber O
- VMSPIN O
- VMBOX O
4
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
13 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
14
48
N.S0028
2 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
3
4 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
5
6 Table 36: Resume_Call_Handling_Response ↔ redreq Parameter Mapping

Resume_Call_Handling_Respon Status Redirection_Request (redreq) Status
se
- -
7
8
49
N.S0028
2 4.2.3.2.3 Mapping ANSI-41 Redirection_Reason and GSM Forwarding Reason for

5 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) -
6
7 Notes:
8 1. The "Call Accepted" redirection reason shall not be received from the terminating ANSI-41
9 MSC in ANSI-41-Redirection Request. Hence the mapping of this value may not be
10 applicable.
11 2. These Redirection Reasons do not map to any existing GSM Forwarding Reasons. As a
12 result, if the IIF receives an ANSI-41-Redirection Request message with one of these
13 Redirection Reasons, it shall reject the request. Hence the mapping of this value may not
14 be applicable.
15
16 4.2.3.2.4 Mapping Forwarding Reason to Redirection Reason for GSM Foreign Mode
17
18 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
19
20
50
N.S0028

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
33 For error mappings see Automatic Call Delivery, Error Handling, ANSI-136 41 Foreign Mode.
51
N.S0028
2 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
3
4 Note 1: This error should not occur. The process requires the GMSC support OR.
5
6 Table 42: Redirection_Request to Resume_Call_Handling Error Mapping

Redirection_Request Resume_Call_Handling
Error Codes User Errors
MissingParameter OR-NotAllowedForwardingFailed
UnrecognizedParameterValue OR-NotAllowedForwardingFailed
UnrecognizedMIN OR-NotAllowedForwardingFailed
UnrecognizedESN OR-NotAllowedForwardingFailed
MIN/HLRMismatch OR-NotAllowedForwardingFailed
OperationSequenceProblem OR-NotAllowedForwardingFailed
TrunkUnavailable OR-NotAllowedForwardingFailed
SystemFailure OR-NotAllowedForwardingFailed
FeatureInactive OR-NotAllowedForwardingFailed
ParameterError OR-NotAllowedForwardingFailed
OperationNotSupported OR-NotAllowedForwardingFailed
ResourceShortage OR-NotAllowedForwardingFailed
7
8
52
N.S0028
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-136 41 foreign modes)
21 • Call Forwarding Unconditional (in both GSM and ANSI-136 41 foreign modes)
22 • Call Forwarding Busy (in both GSM and ANSI-136 41 foreign modes)
23 • Call Forwarding No Reply (in ANSI-136 41 foreign-mode only)
24 • Call Forwarding Not Reachable (in ANSI-136 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 [3].
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,
38 the IIF shall respond with either a GSM MAP_ACTIVATE_SS or GSM MAP_DEACTIVATE_SS
39 Response message that includes a "User error" parameter with a value of "Illegal SS
53
N.S0028
1 operation". Note that cases in which no "Basic service" parameter is included in the received
2 message are acceptable, since, by default, no "Basic service" parameter indicates that the
3 request applies to all services.
4
5 If the format and content of the message is correct, the IIF shall determine the location of the
6 subscriber’s HLR and send to it an ANSI-41 FeatureRequest INVOKE message populated as
7 described in Table 44 and Table 48. If a failure occurs at the IIF on reception of the GSM
8 MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS message (e.g. missing data), the procedures
9 described in GSM 09.02 [3] are applicable to the IIF.
10 If, in response to the ANSI-41 FeatureRequest INVOKE, the IIF receives an ANSI-41
11 FeatureRequest Return Result message with a FeatureResult parameter set to successful, the
12 IIF shall send a GSM MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS Response message back
13 towards the serving system populated as described in Table 45.
14 If, in response to the ANSI-41 FeatureRequest INVOKE, the IIF instead receives an ANSI-41
15 FeatureRequest Return Result message with a FeatureResult parameter set to unsuccessful,
16 the IIF shall send a GSM MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS Response message
17 back towards the serving system populated as described in Table 45 and Table 53.
19 FeatureRequest Return Error message, the IIF shall send a GSM MAP_ACTIVATE_SS/
20 MAP_DEACTIVATE_SS Response message back towards the serving system populated as
21 described in Table 54.
22 Note that successful supplementary service activation/deactivation cases in GSM foreign mode
23 may result in the subscriber's ANSI-41 HLR sending out an ANSI-41 QUALDIR message to the
24 serving system. For these cases, the IIF would need to map the message to a GSM MAP
25 Insert Subscriber Data message. The mapping of an ANSI-41 QUALDIR message to a GSM
26 MAP Insert Subscriber Data message is covered in the Subscriber Data Management.
27
28 4.3.1.1.2 ANSI-136 41 Foreign Mode

29
30 While in ANSI-136 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 [6].
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 inTable 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
44 For the cases of failure at the IIF on reception of the ANSI-41 FeatureRequest Return Result
45 message (e.g. parameter error, unrecognized subscriber), the procedures described in ANSI-41
46 [6] are applicable to the IIF.
54
N.S0028
1 If, in response to the a GSM MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS message, the IIF

2 receives a GSM MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS Response message with neither
3 a User Error nor Provider Error parameter, the IIF shall send an ANSI-41 FeatureRequest
4 Return Result message back towards the serving system populated as described in Table 45.
5 For those cases in which two requests had been previously sent by the IIF, the IIF would wait
6 until receiving the responses to both requests before sending the FeatureRequest Return Result
7 message. For cases in which both responses indicate success, the mapping in Table 45 may be
8 applied to either of the responses (as an IIF implementation option). For cases in which one of
9 the responses indicates success and the other failure, the mapping in Table 45 applies to the
10 successful response.
11 If, in response to the GSM MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS message, the IIF
12 instead receives a GSM MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS Response message
13 with a User Error, the IIF shall send either an ANSI-41 FeatureRequest Return Result
14 populated as described in Table 55 or a Return Error populated as described in Table 56. If a
15 Provider Error parameter is included in the received GSM
16 MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS Response message, the IIF shall send an ANSI-
17 41 FeatureRequest Return Error message populated with an Error Code as shown in Table 57.
18 For cases in which two requests had been previously sent by the IIF, and both responses
19 indicate failure, the mapping described in Table 55 or Table 56 may be applied to either of the
20 responses (as an IIF implementation option).
21 Note that successful supplementary service activation/deactivation cases in ANSI-136 41
22 foreign mode may result in the subscriber's GSM HLR sending out a GSM MAP Insert
23 Subscriber Data message to the serving system. For these cases, the IIF would need to map
24 the message to an ANSI-41 QUALDIR message. The mapping of GSM MAP Insert Subscriber
25 Data message to an ANSI-41 QUALDIR message is covered in the Subscriber Data
26 Management.
27
55
N.S0028

3

5
6 The following table shows the mapping of messages for the Activation and Deactivation of
7 Supplementary Services.
8 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
9
10
11 4.3.1.2.2 Mapping of parameters

12
13 The following tables show the mapping between the parameters in GSM MAP messages and
14 parameters in the corresponding ANSI-41 messages. The relationships between the
15 parameters shown in the tables are meant to be bi-directional.
16 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
17
18
56
N.S0028
1
2 Table 44: Activate/Deactivate SS Request ↔ FEATREQ Parameter Mapping (concluded)

- PC_SSN O
3
4
57
N.S0028

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
8
58
N.S0028
1 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
2
3 4.3.1.2.2.1 Mapping of parameter values in GSM Foreign Mode

4
5 Activate/Deactivate SS Request to Feature Request Invoke mapping
6
7 This table represents how the IIF shall map the value of the parameter it has received to
9 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.
10
11 Note that no parameter in the FeatureRequest INVOKE message currently supports the
12 mapping from the GSM MAP parameter "Basic service". The "GSM Foreign Mode" part of
13 4.3.2 SS Registration and Erasure contains procedures pertaining to the handling of the "Basic
14 service" parameter, when included in the received GSM MAP message.
15
59
N.S0028
1
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
9 Feature Request Return Result to Activate/Deactivate SS Response mapping
10
11 Mapping of parameter values
12
13 For the successful case (in which a FeatureRequest Return Result is received with the
14 FeatureResult parameter set to “successful”) there are no meaningful parameter mappings to
15 support. For those successful cases, the “Default parameter values” describes how the
16 corresponding GSM Activate/Deactivate SS Response message shall be populated. For the
17 unsuccessful cases, 4.3.1.3 Error Handling describes the appropriate mappings.
60
N.S0028
1
3
4 This table describes the population of the parameters in the Activate/Deactivate SS Response
5 message for successful activation/deactivation cases (i.e. when the received Feature Request
6 Return Result contains a FeatureResult parameter set to “successful”).
7 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.
8
9
61
N.S0028
2 4.3.1.2.2.2 Mapping of parameter values in ANSI-136 41 Foreign Mode

3
4 Feature Request Invoke to Activate/Deactivate SS Request mapping
5
8
9 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.
10
12
13 Table 51 presents how the IIF shall populate the parameters of the Activate/Deactivate SS
14 Request message to be sent to the GSM HLR. These fields do not have an equivalent in the
15 received Feature Request Invoke message.
16 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.)
17
18 GSM Activate/Deactivate SS Response to ANSI-41 Feature Request Return Result
19 mapping
20
22 For the successful case (in which there’s no User error or Provider Error in the received GSM
23 Activate/Deactivate SS Response message), there are no meaningful parameter mappings to
25 corresponding ANSI-41 FeatureRequest Return Result shall be populated. For the
26 unsuccessful cases, Table 46 describes the appropriate mappings.
27
62
N.S0028
1
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
8
63
N.S0028

3
4 The following table presents the appropriate GSM MSC/VLR negative response to an
5 Activate/Deactivate SS message as described in GSM 09.02 [3].
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
7
9
Mistyped parameter
Resource limitation
Initiating Release
10
64
N.S0028
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 [6].
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):
5
AccessDeniedReason
Unassigned directory number

Inactive
Busy
No page Response
Unavailable
TerminationDenied
6
7
Error Code value
UnrecognizedMIN
UnrecognizedESN
MIN/HLRMismatch
OperationSequenceProblem
ResourceShortage
ParameterError
SystemFailure
9
10
65
N.S0028

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

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

13 Mapping
Error Code value User Error
UnrecognizedMIN System Failure
MIN/HLRMismatch System Failure
OperationSequenceProblem System Failure
14
15
66
N.S0028
2 4.3.1.3.2 ANSI-136 41 Foreign Mode

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

10 Mapping
Activate/Deactivate SS Response User FeatureRequest Return Result
Error
SS subscription violation FeatureResult="unsuccessful"
AnnouncementList =
“UnauthorizedFeatureCode” (if parameter
supported by serving system)
11
12
67
N.S0028

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
5
68
N.S0028

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
5
69
N.S0028
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 [3].
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 [3] are applicable to the IIF.
38
70
N.S0028
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-136 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 [6]. 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.
46 If, in response to the GSM MAP_REGISTER_SS Request message, the IIF instead receives a
47 GSM MAP_REGISTER_SS Response message with a User Error, the IIF shall send either an
48 ANSI-41 FeatureRequest Return or a Return Error as described in 4.3.2.2.3 Error Handling.
71
N.S0028
1 If a Provider Error parameter is included in the received GSM MAP_REGISTER_SS Response

2 message, the IIF shall send an ANSI-41 FeatureRequest Return Error message populated with
3 an Error Code as described in 4.3.2.2.3 Error Handling. For cases in which two requests
4 had been previously sent by the IIF, and both responses indicate failure, the procedures
5 described may be applied to either of the responses (as an IIF implementation option).
6 Note that successful supplementary service registration cases in ANSI-136 41 foreign mode
7 may result in the subscriber's GSM HLR sending out a GSM MAP Insert Subscriber Data
8 message to the serving system. For these cases, the IIF would need to map the message to
9 an ANSI-41 QUALDIR message. The mapping of GSM MAP Insert Subscriber Data message
10 to an ANSI-41 QUALDIR message is covered in the Subscriber Data Management.
11
12 4.3.2.1.2 Mapping of Messages, Parameters & Parameter Values

13
14 4.3.2.1.2 presents the mapping of messages, parameters and parameter values that the IIF
15 shall perform.
16
17 4.3.2.1.2.1 Mapping of Messages

18
19 Table 58 shows the mapping of messages for Supplementary Service Registration
20 Table 58: Supplementary Service Registration Message Mapping

REGISTER SS REQUEST FEATREQ
REGITER SS REQUEST RESPONSE featreq
21
72
N.S0028
2 4.3.2.1.2.2 Mapping of parameters

3
7 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
8
9
10
73
N.S0028
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.
6
7
8
74
N.S0028
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
5
75
N.S0028
2 4.3.2.1.2.2.1 Mapping of parameter values in GSM Foreign Mode

3
4 Register SS Request to Feature Request Invoke mapping
5
8 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.
9
11 mapping from the GSM MAP parameter "Basic service". The "GSM Foreign Mode" of
14
76
N.S0028
1
3
4 Table 63 presents how the IIF shall populate the parameters of the Feature Request Invoke
5 message to be sent to the ANSI-41 HLR. These fields cannot be mapped from the received
6 Register SS request message.
7 Table 63: FEATREQ default parameter

8
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.
9
10
11 Feature Request Return Result to Register SS Response mapping
12
14
77
N.S0028
2 corresponding GSM Register SS Response message shall be populated. For the unsuccessful
3 cases, refer to 4.3.2.2.3 Error Handling.
4
6
7 Table 64 describes the population of the parameters in the Register SS Response message for
8 successful registration cases (i.e. when the received Feature Request Return Result contains a
9 FeatureResult parameter set to “successful”).
10
11 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.
12
13
78
N.S0028
2 4.3.2.1.2.2.2 Mapping of parameter values ANSI-136 41 Foreign Mode

3
4 Feature Request Invoke to Register SS Request mapping
5
8 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.
9
11 Table 66 presents how the IIF shall populate the parameters of the Register SS Request
12 message to be sent to the GSM HLR. These fields do not have an equivalent in the received
13 Feature Request Invoke message.
14 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.
15
16
79
N.S0028
1
2 GSM Register SS Response to ANSI-41 Feature Request Return Result mapping
3
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
18
80
N.S0028
1
2 Table 67: FeatureRequest Return Result default parameter (concluded)

3
4
81
N.S0028
2 4.3.2.1.3 Error Handling

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

17
18 4.3.2.2.1 contains the procedures in the IIF for the case in which the subscriber requests
19 erasure (de-registration) of information in association with one of the following supplementary
20 services while roaming in foreign mode (i.e., while roaming in a network of a technology
21 different from that of its home network):
22

28
29 4.3.2.2.1.1 GSM Foreign Mode

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

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

34
35 4.3.2.2.2 presents the mapping of messages, parameters and parameter values that the IIF
36 shall perform.
37

39
40
84
N.S0028
1
2 Table 69 shows the mapping of messages for Supplementary Service Erasure.
3 Table 69: Supplementary Service Erasure Message Mapping

ERASE SS REQUEST FEATREQ
ERASE SS REQUEST RESPONSE featreq
5 4.3.2.2.2.2 Mapping of parameters

6
10 Table 70: Erase SS Request ↔ FEATREQ parameter mapping

Erase SS Request Status FEATREQ Status
Basic services C -
- MSCID (Serving) O
- PC_SSN O
11
12
13
85
N.S0028
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
6
86
N.S0028
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
5
6
87
N.S0028
2 4.3.2.2.2.2.1 Mapping of parameter values in GSM Foreign Mode

3
4 Erase SS Request to Feature Request Invoke mapping
5
8 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.
9
11 mapping from the GSM MAP parameter "Basic service". The "GSM Foreign Mode" part of
14
88
N.S0028
1
3
4 Table 74 presents how the IIF shall populate the parameters of the Feature Request Invoke
6 Erase SS request message.
7 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.
8
9
89
N.S0028
1
2 Feature Request Return Result to Erase SS Response mapping
3
5
9 corresponding GSM Erase SS Response message shall be populated. For the unsuccessful
10 cases, refer to 4.3.2.2.3 Error Handling
11
13
14 Table 75 describes the population of the parameters in the Erase SS Response message for
15 successful erasure cases (i.e. when the received Feature Request Return Result contains a
16 FeatureResult parameter set to “successful”).
17 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.
18
19
90
N.S0028
2 4.3.2.2.2.2.2 Mapping of parameter values in ANSI-136 41 Foreign Mode

3
4 Feature Request Invoke to Erase SS Request mapping
5
8 Table 76: FEATREQ to Erase SS Request parameter mapping

FEATREQ Status Erase SS Request Status
operations (e.g. CFB erasure)
9
10
12
13 This table presents how the IIF shall populate the parameters of the Erase SS Request
14 message to be sent to the GSM HLR. These fields do not have an equivalent in the received
15 Feature Request Invoke message.
16 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.)
17
18
91
N.S0028
1
2 GSM Erase SS Response to ANSI-41 Feature Request Return Result mapping
3
5
6 For the successful case (in which there is no User error or Provider Error present in the
7 received GSM Erase SS Response message), there are no meaningful parameter mappings to
9 corresponding ANSI-41 FeatureRequest Return Result shall be populated. For the
10 unsuccessful cases, refer to 4.3.2.2.3 Error Handling.
11
13
14 This table presents how the IIF shall populate the parameters of the Feature Request Return
15 Result message to be sent to the ANSI-41 HLR for successful erasure cases. Note that the
16 population of the message may differ for non-erasure cases.
17

19
20
92
N.S0028
1
2 Table 78: FeatureRequest Return Result default parameter (concluded)

3

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

FeatureRequest Return Result User Error in the Erase SS Response
AnnouncementList="UnauthorizedFeature
Code"
15
16
17
93
N.S0028
2 4.3.3 Retrieval of Forward-To Number

3

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

3
4 The following tables are only for GSM Foreign Mode.
5

7 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 GSM O
TeleService
8
9 Note 1: When TerminationList parameter is present, the Digits (Destination) parameter is
10 ignored.
13
96
N.S0028
1
2 TransferToNumberRequest Return Result to Insert Subscriber Data Request
3
4 Mapping of parameters value
7

9 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 GSM O
TeleService
10
11
12 Note 1: When TerminationList parameter is present, the Digits (Destination) parameter of the
13 TransferToNumberRequest RETURN RESULT is ignored.
14 Note 2: There may be up to three forwarded-to number parameters with the Insert Subscriber
15 Data Request message mapped from TransferToNumberRequest information: one for Call
16 Forwarding Busy, one for Call Forwarding No Reply (mapped from CFNA results), and another
17 for Call Forwarding Not Reachable (also mapped from CFNA results).
18 Note 3: Optional, if the network settings support data, a mapping may be performed as
20
22
23 The other parameters in the TransferToNumberRequest Return Result message are not
24 mapped to any of the Insert Subscriber Data Request parameters.
25
97
N.S0028

3
4 No mapping between ANSI-41 and GSM MAP messages is required for cases in which the
5 forwarded-to number retrieval operation fails. Refer to 4.3.3.1 Detailed Procedures for a
6 description of the IIF procedures when the forwarded-to number retrieval operation fails.
7
8 4.3.4 Calling Number / Line Identification Presentation/Restriction

9
10 The calling number/line identification Presentation/Restriction procedure is used to determine
11 whether the calling party number should be presented to the called party.
12
13 4.3.4.1 Handling of calling number/ line identification presentation

14

16
17 If CNIP / CLIP service is authorized and active, the calling party number is available and
18 presentation is allowed, the called party’s serving network shall provide the calling party
19 number to the called party during call alerting.
20 If the IIF receives a GSM MAP _PROVIDE_ROAMING_Request with the Calling Party Number
21 in the Additional Signal Info field correctly populated, the IIF shall send an
22 ANSI_MAP_ROUTEREQ to the serving MSC/VLR with the Calling Party Number field correctly
23 mapped.
24 If the IIF receives an ANSI_MAP_ROUTREQ with the Calling Party Number field in the
25 Additional Signal Info field correctlty populated, the IIF shall send a GSM MAP
26 _PROVIDE_ROAMING_NUMBER_Request to the serving MSC/VLR with the Calling Party
27 Number field correctly mapped.
28

30

32
33 The mapping of messages is in accordance with 4.2.1, with the exception that GSM 09.02 [3] is
34 supported.
35
98
N.S0028
2 4.3.4.1.2.2 Mapping of Parameters

3
4 The following tables show the mapping of parameters specific to handling calling number/line
5 presentation/restrcition, which the IIF shall perform regardless of the mode of operation (GSM
6 Foreign Mode or ANSI-136 41 Foreign Mode). The mapping of other parameters not specific to
7 handling calling number/line presentation/restriction can be found in 4.2.1, with the exception
8 that GSM 09.02 [3] is supported.
9
10 Note: The tables are constructed in such a way that the parameter names appear first and any
11 information contained within those parameters are shown as indented text.
12
14 number) Parmater 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,

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

Numbering -
Encoding:- IA5
-
Characters:- Digits
Line Identity: E164 address of
Calling Party
15
16
99
N.S0028
2 Table 84: Routing Request ↔ Provide Roaming Number Request (User Provided
3 number) Parameter Mapping
Route Request Status Provide Roaming Number Status
CallingPartyNumberString2 O AddititonalSignalInfo:- C
(User Provided No):- CallingPartyNumber:-

Number
Nature of Number:-
National,Presentation Allowed, Screening Indicator: User
Provided, not screened
User Provided, not screened
Numbering
-
Encoding:- IA5
-
Characters:- Digits

Calling Party
4
5
6
100
N.S0028
2 numbers) Parameter Mapping
Route Request Status Provide Roaming Number Status
CallingPartyNumberString1 O AdditionalSignalInfo:- C

Number

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

Numbering
Encoding:-IA5
-
Characters:- Digits
Calling Party
CallingPartyNumberString2 O Generic Number:-

(User Provided No):-

Number

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

Numbering -
Encoding:- IA5
-
Characters:- Digits
Calling Party
3
101
N.S0028
1 4.3.4.2 Handling of calling number/ line identification restriction

2

4
5 If the calling subscriber has calling number/line identification restriction authorized and active
6 and it is impossible to indicate to the terminating network (due to interworking) that the number
7 shall not be presented to the terminating party, the calling number/line identity shall not be
8 delivered to the terminating network.
9 If CNIR / CLIR service is authorized and active, the calling party number is available and
10 presentation is restricted, the called party’s serving network shall not present the calling party
11 number to the called party during call alerting. An indication that the calling party number is
12 restricted shall be delivered to the called party.
13
14 4.3.4.2.2 Mapping of Messages, Parameters and Parameter Values

15

17
18 Messages for Calling number/line identification restriction is the same as 4.3.4.1.
19

21
22 The following table shows the mapping of parameters for calling name/line restriction, which the
23 IIF shall perform regardless of the mode of operation (ANSI-41 Foreign Mode or GSM Foreign
24 mode).
25
102
N.S0028

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

Number

Presentation Restricted, Screening Indicator: Network
Provided,
Network Provided
Presentation Restrcited
Numbering Plan:- Telephony -

Numbering
Encoding:- IA5
-
Characters:-Digits
Calling Party
103
N.S0028

3
4 For the cases of failure at the IIF on reception of an ANSI_ MAP_RoutingRequest return Result,
5 the procedures described in ANSI-41 [6] for automatic call delivery is applicable to the IIF.
6 For the cases of failure at the IIF on resception of a GSM MAP
7 _PROVIDE_ROAMING_NUMBER_Response, the procedures described in GSM 09.02 [3] are
8 applicable to the IIF.
9
10 If the IIF receives a GSM MAP _PROVIDE_ROAMING_NUMBER_Request indicating an error
11 code, the IIF shall map that error code it receives to a suitable error in the ANSI_MAP_routereq
12 as described in 4.2.1
13
14 If the IIF receives an ANSI_MAP_routreq indicating an error code, the IIF shall map that error
15 code it receives to a suitable error in the GSM MAP
16 _PROVIDE_ROAMING_NUMBER_Response as described in 4.2.1.
17
18
104
N.S0028
2 4.4 O&M Procedures

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

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

21
22 If the IIF receives a GSM MAP _CANCEL_LOCATION_REQUEST, it shall follow the location
23 cancellation procedures outlined in this document for Location Registration (see 4.1.1).
24 If the IIF receives an ANSI_MAP_REGCANC, it shall follow the location cancellation
25 procedures outlined in this document for Location Registration (see 4.1.1).
26
27 4.4.1.2 Subscriber Data Modification Procedure (ANSI-136 41 Foreign Mode)

28
29 If the IIF receives either a GSM MAP _INSERT_SUBSCRIBER_DATA_REQUEST, or a GSM
30 MAP _DELETE_SUBSCRIBER_DATA_REQUEST, it shall follow the VLR procedures
31 described in GSM 09.02 [3].
32 As part of the subscriber data modification procedure, the IIF may send an
33 ANSI_MAP_QUALDIR to the serving ANSI-41 VLR and await a response.
34 If the response indicates success, the IIF shall modify the corresponding subscriber data and
35 send a GSM MAP _INSERT_SUBSCRIBER_DATA_RESPONSE to the GSM HLR.
36
105
N.S0028
1 If the response indicates failure, the received subscriber data is stored by IIF even if there is a
2 failure reported from the visited (foreign mode) system and the IIF shall send the reason for
3 failure in a GSM MAP _INSERT_SUBSCRIBER_DATA_RESPONSE to the GSM HLR.
4
5 4.4.1.3 Subscriber Data Modification Procedure (GSM Foreign Mode)

6
7 If the IIF receives an ANSI_MAP_QUALDIR, it shall follow the VLR procedures described in
8 ANSI-41 [6].
9 As part of the subscriber data modification procedure, the IIF may send either a GSM MAP
10 _INSERT_SUBSCRIBER_DATA_REQUEST or a GSM MAP
11 _DELETE_SUBSCRIBER_DATA_REQUEST to the serving GSM VLR and await a response.
12 If the response indicates success, the IIF shall modify the corresponding subscriber data and
13 send an ANSI_MAP_qualdir to the ANSI-41 HLR.
14 If the response indicates failure, the received subscriber data is stored by IIF even if there is a
15 failure reported from the visited (foreign mode) system and the IIF shall send the reason for
16 failure in the ANSI_MAP_qualdir to the ANSI-41 HLR.
17 4.4.1.4 Subscriber Data Retrieval

18
19 If the IIF receives an ANSI_MAP_QUALREQ, it shall follow the ANSI-41 HLR procedures
20 described in ANSI-41 [6]. The IIF is not required to retrieve subscriber data from the GSM
21 HLR.
22
23 4.4.2 Mapping of Messages, Parameters & Parameter Values

24
25 The IIF shall perform the translation of messages, parameters and parameter values related to
26 subscriber data management in accordance with the tables presented.
27
28 4.4.2.1 Mapping of Messages

29
30 Table 87 shows the mapping between GSM MAP messages and ANSI-41 MAP messages
31 related to Subscriber Deletion. Table 88 and Table 89, show the mapping between GSM MAP
32 messages and ANSI-41 MAP messages related to Subscriber Data Modification.
33
106
N.S0028
2 Table 87: Cancel_Location_Request ↔ REGCAN (Subscriber Deletion) Mapping

CANCEL_LOCATION_REQUEST REGCANC
CANCEL_LOCATION_RESPONSE (Note 1) regcanc return result
CANCEL_LOCATION_RESPONSE (Note 2) regcanc Return Error
3
4 Note 1: In the successful case, the CANCEL_LOCATION_RESPONSE is an empty result i.e.
5 contains no parameters other than the invoke Id.
6 Note 2: This message can also contain error values if the subscriber deletion procedure is
7 unsuccessful. If the subscriber deletion procedure fails, the mapping is as shown. See 4.4.3
8 Error Handling for more information.
9
11 Modification)
INSERT_SUBSCRIBER_DATA_REQUEST QUALDIR
INSERT_SUBSCRIBER_DATA_RESPONSE qualdir (Note 2)
INSERT_SUBSCRIBER_DATA_RESPONSE qualdir Return Error

(Note 1)
12
13 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)
14
15 Note 1: These messages can also contain error values if the subscriber data modification
16 procedure is unsuccessful. If the subscriber data modification procedure fails, the mapping is
17 as shown. See 4.4.3 Error Hanlding for more information.
18 Note 2: The qualdir Return Result is an empty response i.e. contains no parameters other than
19 the Invoke Id.
20
107
N.S0028
2 4.4.2.2 Mapping of Parameters

3
4 The following tables show the mapping of parameters, which the IIF shall perform regardless of
5 the mode of operation (GSM Foreign Mode or ANSI-41 Foreign Mode).
6 Table 90: CANCEL_LOCATION_REQUEST ↔ REGCANC Parameter Mapping

CANCEL_LOCATION_REQUEST Status REGCANC Status
IMSI M MSID M
LMSI C -
Cancellation Type C Cancellation Type O
ControlChannelData O
ReceivedSignalQuality O
SenderIdentifcationNumber O
SystemAccessData O
7
8 Note 1: Cancellation Type is only used between the HLR and the SGSN for GPRS procedures.
9 Cancellation Type is not applicable between HLR and VLR.
10 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
11
1
14 D ‘QUALDIR Invoke’ to the contents of the GSM MAP
15 _INSERT_SUBSCRIBER_DATA_REQUEST as shown in Table 92.
16
108
N.S0028
2 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
1
Forwarding information List C CallingFeaturesIndicator 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 -
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
3 8
Call barring information List C SMS_TerminationRestrictions O
- SPINIPIN O
- SPINITriggers O
3
4
109
N.S0028
1
2 Table 92: INSERT_SUBSCRIBER_DATA_REQUEST ↔ profile ‘macro’ Mapping
3 (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
8
SMS_TerminationRestrictions O
6
SS-Data List
-GSM BearerServiceCode or GSM O CDMAServiceOptionList9 O
TeleService
4
1
5 The CallingFeaturesIndicator parameter provides a status of several ANSI supplementary
6 services. This information may map into one or more GSM MAP parameters as shown in Table
7 92.
2
8 The OriginationIndicator parameter defines the type of calls that a MS is allowed to make.
9 This information may map into one or more GSM MAP parameters as shown in Table 92.
3
10 The Call barring information List is a list of the call barring supplementary services that are
11 either active, quiescent or not active for individual or all teleservices. This information may map
12 into one or more ANSI MAP parameters as shown in Table 92.
4
13 If this information is received by the IIF it does have to be mapped.
5
14 Operator Determined Barring HPLMN data may map into one or more ANSI MAP parameters
15 as shown in Table 92.
6
16 The SS-Data List may map into one or more ANSI MAP parameters as shown in Table 92.
7
17 The SMS_OriginationRestrictions may map into one or more GSM MAP parameters as shown
18 in Table 92.
8
19 The SMS_TerminationRestrictions may map into one or more ANSI MAP parameters as
9
21 The CDMAServiceOptionList may map into one or more GSM MAP parameters (e.g.:
22 ADS (9.6kbps) to “CDA-9600 bps” BearerServiceCode;
23 G3FAX to “FacsimileGroup3” GSMTeleService;
24 Packet Data Service (PDS) to “dataPDS” BearerServiceCode).
25
26 Parameter Value Mapping
27 Table 93 through Table 104 shows the mapping of parameter values (more commonly referred
28 to as ASN.1 data types in GSM09.02 [3] which the IIF shall perform based on the parameter
29 mapping shown in Table 92. If there is no direct mapping for parameter values, a ‘-‘ has been
30 entered in the corresponding table. The implication therefore, is that those services/features
110
N.S0028
1 and/or subscription options may not be available when roaming in either a GSM or ANSI-41
2 PLMN.
3
4 The ASN.1 data type encoding is specified in GSM09.02 [3].
5
111
N.S0028
1 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[1] for Basic Service

Codes
SSStatus FeatureActivityStatus
Q P R A3
0000 Not authorized

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

GSM_Regional Subscription Data ANSI-41_Geographic Authorization
ZoneCode GeographicAuthorization
See GSM 09.02 [1] 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
3
1
4 Based on the zone code, which identifies those regions or zones where a roaming is allowed,
5 these values may map to one or more values in the Geographic Authorization.
6 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

7
8
114
N.S0028
1
2 Table 95: Call Barring Information List to Origination Indicator Parameter Mapping
3 (concluded)
GSM_Call Barring Information List ANSI-41_Origination Indicator

or of international E.164 number6
Selected leading digits of directory number

BAOC,BOIC, BOIC-exHC or of international E.164 number and local
6
calls
International calls
-
Single Directory number or international
E.164 number
-
BarringOfIncomingCalls -
BAIC -
BIC-Roam -
BAOC
BasicService -
See GSM 09.02[1] for Basic Service codes
SSStatus -
QPRA
See GSM 09.02[1] for SSStatus values

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

UUS -
PLMNSpecific -
1
BasicService -
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
3
CLIRestrictionOption 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
118
N.S0028
1
2 Note (a): There is no equivalent GSM SSCode value for CNIROver. The override restriction
3 capability in GSM is a subscription option whose value is reflected by the OverrideCategory
4
1
5 GSM allows supplementary services to be operated on a per basic service group basis. ANSI-
6 41 on the other hand has no concept of basic service groups. Therefore, one or more GSM
7 basic services or basic service groups shall map to all basic services in ANSI-41.
2
8 These combinations are not applicable to the GSM supplementary services defined by their
9 SSCode in Table 96
3
10 The CLIRestriction option is equivalent to the ANSI-41 Feature Activity Status, CNIR. If the
11 CLIRestriction is temporary default restricted, this equates to the value ‘Authorized and
12 activated’ in the CNIR feature activity status. If the CLIRestriction is temporary default allowed,
13 this equates to the value ‘Authorized but deactivated’ in the CNIR feature activity status. There
14 is no equivalent in ANSI-41 to permanently restricted.
4
15 The GSM override category is equivalent to the ANSI-41 Feature Activity Status, CNIROver.
16 If the Override Category is enabled, this equates to the value ‘Authorized and activated’ in the
17 CNIROver feature activity status. If the Override Category is disabled, this equates to the value
18 ‘Authorized but deactivated’ in the CNIROver feature activity status.

20 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
21
22
119
N.S0028
1
3 Parameter Mapping (concluded)
GSM_Operator determined barring (general) ANSI-41_Origination Indicator

Selected leading digits of directory
InterzonalandInternationalOGCallsNotToHPL number or of international E.164
MN-CountryBarred1 number and local calls
PremiumRateInformationOGCallsBarred1 Selected leading digits of directory

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

PremiumRateEntertainmentOGCallsBarred1 number or of international E.164
SSAccessBarred
-
AllECTBarred
-
ChargeableECTBarred
-
InternationalECTBarred
-
InterzonalECTBarred
-
DoublyChargedECTBarred
-
MultipleECTBarred
4
5 Note: The mapping shown in Table 97 applies in one direction only i.e. from GSM to ANSI-41.
6 The corresponding ANSI-41 values received by the IIF in “profile” macro parameter, it shall be
7 mapped according to Table 95.
8
1
9 If the IIF receives any of these GSM ODB general data, they shall map to the same ANSI-41
10 allowed call type as shown in Table 97.
11
120
N.S0028
3 Mapping
GSM_Operator determined barring ANSI-41_Origination Indicator
(HPLMN)
ODB-HPLMN data Allowed Call Types
PLMN-SpecificBarringType1 -
6 Mapping
GSM_Operator determined barring ANSI-41_Restriction Digits
(HPLMN)
ODB-HPLMN data Type of Number
PLMN-SpecificBarringType1 -
7
8
121
N.S0028
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
4
122
N.S0028
1
3 Mapping (concluded)
GSM_Call Barring Information List ANSI-41_SMS Origination Restrictions

BasicService -
SSStatus -
QPRA
4
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[1] for Basic Service codes -
SSStatus
QPRA -
7
8
123
N.S0028
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 -
SSStatus -
QPRA
3
4
124
N.S0028
1 Table 103: SSData List to SMS Origination Restrictions Parameter Mapping

GSM_SSData List ANSI-41 SMS Origination Restrictions
SSCode -
See GSM 09.02 [1] for SS Codes
BasicService Default
See GSM 09.02 [1] 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 [1] for SS Codes
BasicService Default
See GSM 09.02 [1] for complete list of Block All1
Basic Services
SSStatus -
CLIRestrictionOption -
OverrideCategory -
6
1
7 In the case where the BasicService does not indicate that SMS is available, this shall be mapped to
8 ‘Block All’.
9
125
N.S0028
2 4.4.3 Error Handling

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

mistyped parameter;
initiating release (i.e., the peer has
already initiated release of the dialogue
and the service has to be released);

11
12 If the Subscriber Deletion procedure fails at a GSM VLR, it returns a GSM MAP
13 _CANCEL_LOCATION_RESPONSE to the IIF, indicating an ‘user error’ as indicated above. The
14 IIF is therefore responsible for mapping any errors it receives into a corresponding error in the
15 ANSI_MAP regcanc towards the ANSI-41 HLR. For further description of these errors and when
16 they are used, refer to either GSM 09.02 [3] or ANSI-41 [6].
17 The « Location Registration » provides the mapping of both user errors and provider errors in
18 the GSM MAP _CANCEL_LOCATION_RESPONSE to the equivalent value in either the
19 CANDEN parameter in the ANSI_MAP regcanc RETURN RESULT or the RETURN ERROR.
20
21
127
N.S0028
1
2 Subscriber Data Modification
3 If the Subscriber Data Modification procedure fails at an ANSI-41 VLR, the VLR shall respond
4 by sending:-
5
6 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
10 The IIF is therefore responsible for mapping any errors it receives from the ANSI-41 VLR in the
11 ANSI_MAP qualdir to an equivalent error in the GSM MAP
12 _INSERT_SUBSCRIBER_DATA_RESPONSE or the GSM MAP
13 _DELETE_SUSBCRIBER_DATA_RESPONSE towards the GSM HLR.
14
15 The GSM MAP _INSERT_SUBSCRIBER_DATA_RESPONSE and the GSM
16 MAP_DELETE_SUBSCRIBER_DATA RESPONSE may include one the following ‘user’ errors
17 as defined in GSM 09.02 [3]:
User Errors
unidentified
subscriber;
data missing;
unexpected data
value.
19
128
N.S0028
1 The following ‘provider errors’ are also defined in GSM 09.02 [3]:
2
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
5 If the Subscriber Data Modification procedure fails at a GSM VLR, it returns either a GSM MAP
6 _INSERT_SUBSCRIBER_DATA_RESPONSE or a GSM MAP
7 _DELETE_SUBSCRIBER_DATA_RESPONSE to the IIF, indicating a ‘user error’ as indicated
8 above. The IIF is therefore responsible for mapping any errors it receives into a corresponding
9 error in the ANSI_MAP qualdir towards the ANSI-41 HLR. For further description of these
10 errors and when they are used, refer to either GSM 09.02 [3] or ANSI-41 [6].
11 Table 105 below provides the mapping of both user errors and provider errors in the GSM MAP
12 _INSERT_SUBSCRIBER_DATA_RESPONSE and GSM MAP
13 _DELETE_SUBSCRIBER_DATA_RESPONSE to the equivalent value in the ANSI_MAP
14 qualdir RETURN ERROR for ANSI-41 Foreign mode. Table 106 provides the mapping for GSM
15 Foreign mode.
16
129
N.S0028
2 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
3

5 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
6
7
8
130
N.S0028
2 4.5 Short Message Procedures (ANSI-136 41 Network)

3
6
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.
131
N.S0028
1 If the response to FSM indicates a failure in the delivery of the short message, the IIF
2 shall map the cause value received to a corresponding SMS_CauseCode value in the
3 SMDPP Return Result, as described in
6
7 Table 116.
8
9 If the response to FSM indicates that the receiving entity does not support MAP V2, the GSM
10 MAP_FORWARD_SHORT_MESSAGE is formatted in MAP V1 and sent again to the serving
11 MSC/VLR.
12
13 4.5.1.1.2 Alerting in GSM Foreign Mode

14
15 If the IIF receives a GSM MAP _READY_FOR-SHORT_MESSAGE (MAP V2) or a
16 GSM_UPDATE_LOCATION message, or a GSM MAP _NOTE_MS_PRESENT message (MAP
17 V1) and the Delivery pending flag is set for the subscriber, the IIF shall send an
18 ANSI_MAP_SMS_NOTIFICATION message to the home Message Center. The flag shall then
19 be cleared. The home MC shall re-send message SMDPP to deliver the short message to the
20 subscriber as described previously.
21
22 4.5.1.1.3 Mobile Terminating SMS in ANSI-136 41 Foreign Mode

23
24 If the IIF receives a GSM_FORWARD_SHORT_MESSAGE, it shall format and send an
25 ANSI_MAP Short Message Delivery Point to Point message to the serving TDMA ANSI-41
26 MSC/VLR. Refer to Table 110, Table 111 and Table 112 for the mapping of parameters from
27 GSM MAP _FORWARD_SHORT_MESSAGE to ANSI_SMDPP.
28 If the IIF receives a positive acknowledgment to the SMDPP message, it shall send a positive
29 acknowledgment to the Forward Short Message.
30 If the IIF receives a negative acknowledgment to the SMDPP message, it shall set the Mobile
31 Not Reachable flag for the subscriber and shall map the received SMS_CauseCode value into
32 a corresponding error code in the FSM Response message as described in Table 117.
33 If the IIF detects errors in the FORWARD_SHORT_MESSAGE, an error indication is sent in the
34 response message. This shall cause the GSM MSC/VLR to send an error indication to the GSM
35 HLR. Refer to 4.5.1.3 Error Handling for error detection on reception of FSM.
36 If a Return Error or Reject is received in response to the ANSI_MAP_SMSDPP INVOKE, the
37 error code is mapped into the corresponding Forward Short Message error code as described
38 in Table 117.
39
132
N.S0028
1 4.5.1.1.4 Alerting in ANSI-136 41 Foreign Mode

2
3 If the IIF receives an ANSI_MAP Registration Notification message or an ANSI_MAP SMS
4 Notification message, and the SMS Delivery Pending flag is set for a mobile subscriber, it shall
5 send a GSM MAP _READY_FOR-SHORT_MESSAGE (MAP V2) or a GSM MAP
6 _NOTE_MS_PRESENT message (MAP V1) to the GSM HLR. This shall cause the HLR to
7 send an indication to the GSM SMSC that shall trigger the re-sending of the Short message.
8
9 4.5.1.1.5 Mobile Originating SMS in GSM Foreign Mode

10
11 If the IIF receives a GSM_FORWARD_SHORT_MESSAGE for a mobile originated short
12 message, it shall format and send an ANSI_MAP_SMDPP message to the serving TDMA
13 ANSI-41 Message Center. Refer to Table 114 for the mapping of parameters from GSM MAP
14 _FORWARD_SHORT_MESSAGE to ANSI_SMDPP.
17 If the IIF receives a negative acknowledgment to the SMDPP message, it shall map the
18 received SMS_CauseCode value into a corresponding error code in the FSM Response
19 message as described in Table 117
21 response message. Refer to 4.5.1.3 for the handling of errors at the reception of FSM.
22
23 4.5.1.1.6 Mobile Originating SMS in ANSI-136 41 Foreign Mode

24
25 If the IIF receives an ANSI-SMDPP message from the Serving MSC, it shall format and send a
26 GSM MAP_FORWARD_SHORT_MESSAGE to the GSM Message Center of the subscriber.
27 Refer to Table 115 for the mapping of parameters from ANSI_SMDPP to GSM MAP
29 If a successful response is received for the FSM, the IIF shall send a SMDPP Return Result
30 message to the MSC/VLR.
32 be processed or if mandatory parameters are missing. Otherwise, the IIF shall send an SMDPP
35 If the response to FSM indicates that the receiving entity does not support MAP V2, the GSM
36 MAP_FORWARD_SHORT_MESSAGE is formatted in MAP V1 and sent again to the serving
37 MSC/VLR.
38
133
N.S0028

3

5
7 Short Message Service in accordance with the tables presented.
8 Table 107 shows the mapping between ANSI MAP messages and GSM MAP messages
9 related to Short Message Service in GSM Foreign Mode. Table 108 shows the mapping
10 between GSM MAP messages and ANSI MAP messages related to Short Message Service in
11 ANSI-136 41 Foreign Mode.
12 Table 107: Short Message Service in GSM Foreign Mode (for CMT) Message Mapping
ANSI MAP Messages GSM MAP Messages
SMDPP FORWARD_SHORT_MESSAGE
13
14 Table 108: Short Message Service in ANSI-136 41 Foreign Mode (for CMT) Message
15 Mapping
FORWARD_SHORT_MESSAGE SMDPP
16
17
134
N.S0028

3
4 Table 109 through Table 115 show the mapping of parameters, which the IIF shall perform.
6 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
7
8 Note 1: MSID and SMS_Original_Destination_Address should be the same.
9 Note 2: This parameter is only valid for MAP V2.
10
135
N.S0028
3 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
4
5 The IIF shall support the mapping of parameters in Forward Short Message in both MAP V1
6 and MAP V2. Encoding of parameter SM-RP-UI is different depending on the MAP version
7 being encoded in the message. The two following tables describe the coding for each version
8 of MAP.
9
10 Table 111describes the setting of field values for parameter SM-RP-UI for MAP V2.
11 Table 111: SM-RP-UI in MT_FORWARD_SHORT_MESSAGE for MAP V2 Parameter Values

12 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 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).
If 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
136
N.S0028
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.
1
2
137
N.S0028
1
2 Table 111: SM-RP-UI in MT_FORWARD_SHORT_MESSAGE for MAP V2 Parameter Values
3 for GSM Foreign Mode (concluded)
FIELD VALUE
Data Coding Scheme - Set bit numbers 7654 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”.
4
5 The following table describes the setting of field values for parameter SM-RP-UI for MAP V1.

7 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”
8
9
138
N.S0028
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.
4
5
139
N.S0028

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
DestinationOriginating Address
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
5
140
N.S0028
1
3 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
5 Note 1: MSID and ESN are supplied based on MSISDN received in SM-RP-OA
6

8 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 -
9
10
141
N.S0028
1
3 SMS in ANSI-41 Foreign Mode (continued)

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-Status-Report-
Request=NO
- TP-Message-Reference
- TP-Message-Reference
-
- TP-Protocol-Identifier = 0
- TP-Data-Coding-Scheme
- TP-User-Data-Unit
TP-User-Data-Length
TP-Urgent-Indicator
TP-User-Data
- TP-Delivery-Ack-Request
(ignored)
4
5
142
N.S0028
1
3 SMS in ANSI-41 Foreign Mode (concluded)

- 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-Destination-Address =
- TP-Multilingual-Call- SMS-Original-Destination
Back-Number (ignored) Address.
- 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
143
N.S0028
144
N.S0028

3
4 Error handling at the reception of a Forward Short Message in the IIF
5
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”.
31
145
N.S0028
1
2 Error Handling at the Reception of ANSI-41 SMDPP
3
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
33 Error Mapping from GSM FSM to ANSI SMDPP to support Mobile Terminating SMS in
34 GSM Foreign and Mobile Originating SMS in ANSI-41 Foreign Mode
146
N.S0028

6 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
7
8
147
N.S0028
1
3 Error Mapping (concluded)
GSM FORWARD_SHORT_MESSAGE ANSI SMDPP Return Result SMS-

RESPONSE CauseCode 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 No
cause: Equipment Protocol Error Acknowledgement
SM-DeliveryFailure Other terminal problem OR No

cause: Equipment Not SM-Equipped 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 No
Addr Acknowledgement
SM-DeliveryFailure SMS origination denied OR No
cause: subscriberNotSC-Subscriber 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
4
5 Note: Unidentified Subscriber and Illegal Equipment may be treated as Any Other Error and
6 may be mapped to Network failure.
7
148
N.S0028
1
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
149
N.S0028
2 4.5.2 Short Message Service via GHOST or WEMT

3

5
6 SMS Alert Procedure
7 The SMS Alert procedure is used for alerting the SMSC when the mobile subscriber is active
8 and available for short messaging after a short message transfer has failed because the mobile
9 subscriber is not reachable or when the Mobile Station (MS) has indicated that it has no
10 memory capacity to accept a short message.
11
12 4.5.2.1.1 Alerting for an ANSI-136 41 Subscriber in GSM Foreign Mode

13
14 IIF Receiving a READY_FOR_SM
15 Upon receipt of a READY_FOR_SM message, the IIF shall store the originating Visited MSC
16 (VMSC) address in the subscriber’s profile and Invoke ID. It shall map the
17 GSM_READY_FOR_SM message to the ANSI_SMSNOT INVOKE message as described in
18 Table 119.
19 It shall populate the SMS_Address parameter with the IIF address. All other parameters are
20 ignored.
21 The ANSI_SMSNOT INVOKE is then transmitted to the subscriber’s SMSC with local
22 Transaction ID. Finally, the IIF shall return a READY_FOR_SM_ACK message with no
23 arguments to the originating VMSC.
24
25 IIF Receiving a SMSNOT RETURN RESULT
26 Upon receipt of a SMSNOT RR message, the IIF shall associate the SMSNOT Transaction ID
27 with the Invoke ID.
28
29 4.5.2.1.2 Alerting for a GSM Subscriber in ANSI-136 41 Foreign Mode

30
31 IIF Receiving a SMSNOT INVOKE
32 Upon receipt of a SMSNOT message, the IIF shall store the originating VMSC address and
33 Transaction ID. The IIF shall map the ANSI_SMSNOT message to the
34 GSM_READY_FOR_SM. The parameters shall be mapped as described in Table 120.
35 The GSM_READY_FOR_SM is transmitted to the subscriber’s HLR with local Invoke ID.
36 Finally, the IIF shall return a SMSNOT RR to the originating VMSC.
37
150
N.S0028
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
13 IIF Receiving a GSM_READY_FOR_SM_ACK
14 Upon receipt of a GSM_READY_FOR_SM_ACK message, the IIF shall associate the

15 GSM_READY_FOR_SM_ACK Invoke ID with Transaction ID.
16
17 Short Message Service for GHOST
18 4.5.2.1.3 SMS Delivery for an ANSI-136 41 Subscriber in GSM Foreign Mode

19
20 IIF Receiving SMSDeliveryPointToPoint INVOKE
21 Upon receipt of an SMSDeliveryPointToPoint INVOKE message, the IIF shall store the
22 originating MC address and transaction ID. It shall map the ANSI_SMDPP message into a
23 GSM_FSM message and populate the subscriber’s known VMSC into the DPC. The mapping
24 of parameters is described in Table 121.
25 The IIF transmits the GSM_FSM message with local Invoke ID.
26
27 IIF Receiving FORWARD_SHORT_MESSAGE_ACK
28 Upon receipt of the FORWARD_SHORT_MESSAGE_ACK message, the IIF shall associate the
29 Invoke ID with SMDPP transaction ID and map the GSM_FSM_ACK message into an
30 ANSI_SMDPP RETURN RESULT.
31 Next, it populates the stored originating SMSC address into the DPC and populates the
32 transaction ID.
34 the SMS_CauseCode according to
35
36
37
38 Table 116.
151
N.S0028
1 Finally, the ANSI_SMDPP RR is transmitted to the originating SMSC.

2
3 4.5.2.1.4 SMS Delivery for a GSM Subscriber in ANSI-136 41 Foreign Mode

4
5 IIF Receiving MT_FORWARD_SHORT_MESSAGE
6 Upon receipt of the MT_FORWARD_SHORT_MESSAGE message, the IIF shall store the
7 originating SMSC address and Invoke ID. It shall map the GSM_FSM message into an
8 ANSI_SMDPP INVOKE message and populate the subscriber’s known VMSC into the DPC.
9 The mapping of parameters is described in Table 122.
10 The IIF transmits the ANSI_SMDPP INVOKE message with local transaction ID
11
12 IIF Receiving SMDPP RETURN RESULT
13 Upon receipt of a SMSDeliveryPointToPoint RR message, the IIF shall associate the SMDPP
14 transaction ID with Invoke ID and map the ANSI_SMDPP RR to GSM_FSM_ACK.
15 Next, it populates the stored originating SMSC address and Invoke ID. If the SMS_CauseCode
16 parameter is populated in the ANSI_SMDPP RR message, then map value into User error
17 parameter according to Table 117.
18 Finally, transmit the GSM_FSM_ACK to the originating SMSC.
19
20 4.5.2.1.5 SMS Origination for an ANSI-136 41 Subscriber in GSM Foreign Mode

21
22 IIF Receiving MO_FORWARD_SHORT_MESSAGE
23 Upon receipt of a MO_FORWARD_SHORT_MESSAGE, the IIF shall store the address of the
24 originating VMSC and Invoke ID. It shall map the GSM_MO_FSM to ANSI_SMDPP INVOKE.
25 The address of the subscriber’s TSA (from the SM RP DA – Service Center Address) is
26 mapped according to 4.5.2.4 into the SMS_DestinationAddress. The mapping of parameters is
28 The IIF transmits the ANSI_SMDPP INVOKE message with local transaction ID.
29 IIF Receiving SMDPP RETURN RESULT
31 transaction ID with Invoke ID and map the ANSI_SMDPP RR to the GSM_FSM_ACK.
32 Next, it populates the stored originating SMSC address and Invoke ID. If SMS_CauseCode
35 Finally, transmit the GSM_FSM_ACK to the originating VMSC.
36
37 4.5.2.1.6 SMS Origination for a GSM Subscriber in ANSI-136 41 Foreign Mode

38
152
N.S0028
1 IIF Receiving SMSDeliveryPointToPoint INVOKE
2 Upon receipt of an SMSDeliveryPointToPoint INVOKE message, the IIF shall store the address
3 of the originating VMSC and Transaction ID and map the ANSI_SMDPP INVOKE to the
4 GSM_MO_FSM. The mapping of parameters is described in Table 124.
6
7 IIF Receiving FORWARD_SHORT_MESSAGE_ACK
9 Invoke ID with SMDPP transaction ID. The GSM_FSM_ACK message is mapped into an
12 Error parameter is populated in GSM_FSM_ACK, then this value is mapped into the
13 SMS_CauseCode according to
14
15
16
17 Table 116.
18 Finally, transmit the ANSI_SMDPP RR to the originating VMSC.
19

21
23 Short Message Service in accordance with the tables presented next.
24

26
27 Table 118: Short Message Service (for GHOST or WEMT) Message Mapping
SMSNOT READY_FOR_SM
28

30
153
N.S0028
1 The mapping of the GSM MAP _READY_FOR_SM message to the ANSI_SMSNOT message
2 is per Table 119.
3 Table 119: Alerting for an ANSI-136 41 Subscriber in GSM Foreign Mode Parameter
4 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
5
6
154
N.S0028
1 The mapping of the ANSI_SMSNOT message to the GSM MAP _READY_FOR_SM message
2 is per Table 120.
3 Table 120: Alerting for a GSM Subscriber in ANSI-136 41 Foreign Mode Parameter
4 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
5
6 4.5.2.2.3 SMS Delivery for an ANSI-136 41 Subscriber in GSM Foreign Mode

7
8 When the IIF receives an SMDPP Invoke from an ANSI-136/41 SMSC for an ANSI-136/41 MS
9 roaming in a GSM network, it stores the Originating MC address, converts the SMDPP to a
10 MAP_FSM, replaces the Originating Address by the address of the IIF, and sends the message
11 to the serving GSM MSC. Upon receipt of the MAP_FSM_ACK from the serving MSC, the IIF
12 converts the message to an SMDPP Return Result, replaces the Originating Address with its
13 own address and replaces the Destination Address with the previously stored address of the
14 ANSI-136/41 SMSC. See Table 121.
15 Table 121: SMDPP to Forward Short Message for Mobile Terminated GHOST/WEMT
16 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
17
155
N.S0028
1 Note 1: MSID and SMS-Original-Destination Address should be the same
3 4.5.2.2.4 SMS Delivery for a GSM Subscriber in ANSI-136 41 Foreign Mode

4
5 When the IIF receives a MAP_FSM destined for an MS roaming in an ANSI-136/41 network, it
6 stores the originating Service Center address locally, and replaces the Service Center Address
7 in the outgoing SMDPP message by E.164 address of the IIF. Upon receipt of an SMDPP
8 Return Result from the serving ANSI-136/41 MSC, the IIF converts it to a MAP_FSM_ACK, and
9 places the previously stored Originating Service Center address in the Destination Address.
10 See Table 122.
11 Table 122: Forward Short Message to SMDPP for Mobile Terminated GHOST/WEMT
12 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)
SMS_Original Destination Sub
Address (Not used)
13
14
15 4.5.2.2.5 SMS Origination for an ANSI-136 41 Subscriber in GSM Foreign Mode

16
156
N.S0028
1 When the IIF receives a MAP_FSM originated from a MS roaming in a GSM network, it stores
2 the VMSC address locally and replaces the VMSC address in the outgoing SMDPP message
3 by the E.164 address of the IIF (placed in the SCCP Calling Party Address). Upon receipt of an
4 SMDPP Return Result from the MC, the IIF converts it to a MAP_FSM_ACK and places the
5 previously stored VMSC address in the SCCP Called Party Address. See Table 123.
6 Table 123: Forward Short Message to SMDPP for Mobile Originated GHOST/WEMT in
7 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)
8
9 Note 1: MSID and ESN are mapped from MSISDN received in SM-RP-OA
10
11 4.5.2.2.6 SMS Origination for a GSM Subscriber in ANSI-136 41 Foreign Mode

12
13 When the IIF receives a SMDPP Invoke originated from a MS roaming in an ANSI-136 41
14 network, it stores the VMSC address locally and replaces the VMSC address in the outgoing
15 MT FSM message by the E.164 address of the IIF (placed in the SCCP Calling Party Address).
16 It also internally maps the TSAF from the SMS_Destination Address into the TSAH and places
17 that value in the RP-Destination Address per 4.5.2.4 Identification of the IIF SS7 Address for
18 Mobile Originated Services. Upon receipt of a MAP_FSM_ACK from the MC, the IIF converts it
157
N.S0028
1 to a SMDPP Return Result and places the previously stored VMSC address in the SCCP
2 Called Party Address. See Table 124.
3 Table 124: SMDPP to Forward Short Message for Mobile Originated GHOST/WEMT
4 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 -
5 Note 1: If MSID is received it should be the same as the SMS_OriginalOriginating Address
6
7 GHOST shall use the HLPI shown below. TSAR may or may not be applied to the GHOST
8 teleservice.
9 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
10
158
N.S0028

2
3 4.5.2.3.1 Error handling at the reception of a Forward Short Message in the IIF
4
5 Refer to 4.5.1.3 Error Handling
6 4.5.2.3.2 Error handling at the reception of a SMDPP message in the IIF

7
9 4.5.2.3.3 Cause Code Mapping at the IIF

10
11 At the IIF, the ANSI-41 SMS_CauseCode is mapped to a return error in the GSM
12 MAP_FSM_ACK message according to Table 117
14 SMS_CauseCodes according to
15
16
17
18 Table 116.
19
20 4.5.2.4 Identification of the IIF SS7 Address for Mobile Originated Services
21
22 The following SS7 address mapping scheme is defined in order to resolve the ambiguity that
23 occurs when a roaming subscriber attempts to invoke mobile originated teleservices.
24 Specifically, instead of using only a single Teleservice Server Address (TSA) as the SS7 SCCP
25 Called Party Address, a pair of E.164 addresses are defined for each Teleservice Server
26 Address Center (e.g., MC or SMSC). This pair of addresses (native and foreign mode TSAs) is
27 used to enable the routing of incoming messages to the IIF from the serving foreign network,
28 while messages that originate in a network that uses the same technology as the home network
29 bypass the IIF and are routed directly to the MC. The native mode address can be translated
30 using global title translation to the actual SS7 address (DPC and SSN) of the MC while the
31 foreign mode address is a virtual address that points (via global title translation) to the IIF.
32 There is a one-to-one mapping in the IIF between the home and foreign mode addresses for
33 each MC, as shown in Table 126. Note that there is a many-to-one relationship between the
34 virtual addresses and the actual IIF address.
35 While roaming in foreign mode, the mobile station uses the foreign mode address in order to
36 ensure that messages are first routed to the IIF. The IIF performs message translation, and
37 inserts the native mode address, i.e., an E.164 number that is translatable by the network to the
38 actual MC destination SS7 address.
159
N.S0028
1 Table 126: Teleservice Server Address Mapping in IIF

Home Technology Address Foreign Technology Address
TSAH1 ↔ TSAF1
TSAH2 ↔ TSAF2
TSAH3 ↔ TSAF3
2
3
160
N.S0028
2 4.5.3 Message Waiting Notification

3
4 The Message Waiting Notification procedure is used to notify a mobile subscriber of voice mail
5 messages added or removed in his voice mail system.
6

8 The following procedures are applicable at the IIF for Message Waiting Notification.
9
10 GSM Foreign Mode
11 Two events can trigger the sending of updated MWN information by the IIF to the serving GSM
12 MSC/VLR, when an ANSI-136 41 native subscriber is roaming in GSM Foreign Mode.
13
14 4.5.3.1.1 Registration Notification Return Result with MWN Information Received

15
16 When the ANSI-136 41 native subscriber registers in a GSM MSC/VLR, a GSM
17 MAP_UPDATE_LOCATION message is received at the IIF. This shall trigger an ANSI MAP
18 REGISTRATION_NOTIFICATION message to be sent by the IIF to the TDMA ANSI-41 home
19 HLR.
20 If the IIF receives a Registration Notification Return Result message with MWNCOUNT and
21 MWNTYPE parameters set to valid values, it shall set the Message Waiting Notification flag
22 and it shall send a GSM MAP_INSERT_SUB_DATA message(s) to the GSM MSC/VLR from
23 which it had received a previous GSM MAP_UPDATE_LOCATION message.
24 The IIF shall also send an Update Location acknowledge message and send it to the GSM
25 MSC/VLR.
26 The IIF shall then format and send a GSM MAP_FORWARD_SHORT_MESSAGE. Refer to
27 Table 129 for the mapping of parameters from ANSI-Regnot return result to GSM MAP
29 If a successful response is received for the FSM, the IIF shall clear the Message Waiting
30 Notification flag.
31 If the response to FSM indicates that the receiving node does not support MAP V2, the
32 GSM_FSM message shall be reformatted in MAP V1 and sent again.
33 If the response to FSM indicates an error condition, or if a time out occurs, the MWN
34 information is sent in a new GSM MAP _FORWARD_SHORT_MESSAGE when the IIF
35 receives a new GSM MAP _UPDATE_LOCATION, GSM MAP
36 _READY_FOR_SHORT_MESSAGE or GSM MAP _NOTE_MS_PRESENT message.
37
38 4.5.3.1.2 Qualification Directive Invoke Received

39
161
N.S0028
1 If the IIF receives a QUALDIR INVOKE message from the TDMA ANSI-41 HLR with
2 MWNCOUNT and MNWTYPE parameters set to valid values, it shall set the Message waiting
3 Notification flag and it shall send a GSM MAP FORWARD_SHORT_MESSAGE. Refer to Table
4 130 for the mapping of parameters between ANSI-QUALDIR and GSM-
5 _MAP_FORWARD_SHORT_MESSAGE.
6 If an error is detected in the QUALDIR INVOKE message, a Reject or Return Error message is
7 sent back to the sending node. No other processing is executed.
8 If a successful response is received for the FSM, the IF shall clear the Message Waiting
10 If the error in the response to FSM indicates that the receiving node does not support MAP V2,
11 the GSM_FSM message shall be reformatted in MAP V1 and sent again.
12 If an error is received in the response to FSM, or if a time out occurs, the MWN information is
13 sent in a new GSM MAP _FORWARD_SHORT_MESSAGE when the IIF receives a new GSM
14 MAP _UPDATE_LOCATION, GSM MAP _READY_FOR_SHORT_MESSAGE or GSM MAP
15 _NOTE_MS_PRESENT message.
16
17 ANSI-136 41 Foreign Mode
18 Two methods of delivering Message Waiting Notification to a native GSM subscriber roaming in
19 ANSI-136 41 are supported.
20
21 4.5.3.1.3 GSM SMS Mapped to ANSI-41 Qualification Directive Invoke

22
23 If the IIF receives a GSM_FORWARD_SHORT_MESSAGE with MWN information, it shall set
24 the message waiting Notification flag and it shall format and send an ANSI_MAP_ QUALDIR
25 message to the serving ANSI-41 MSC/VLR. Refer to Table 131 for the mapping of parameters
26 from GSM MAP _FORWARD_SHORT_MESSAGE to ANSI_QUALDIR.
27 When the IIF receives a positive acknowledgment to the Qualification Directive message, it
28 shall send an acknowledgment to the Forward Short Message with an error indication of
29 “absent subscriber”. This shall ensure that the MWN information is delivered again from the
30 home system when the subscriber returns home.
31 If the MS registers in a different ANSI-41 MSC/VLR after some time, the MWN information is
32 delivered in the Registration Return Result message
35 Message Center.
36 If a Return Error or Reject is received in response to the ANSI_MAP Qualification Directive
37 INVOKE, the error code is mapped into the corresponding Forward Short Message error code
38 as described in Table 135.
39
162
N.S0028
2 4.5.3.1.4 GSM SMS Mapped to TDMAANSI-41 SMS using GHOST or WEMT

3
4 If the IIF receives GSM MAP _FORWARD_SHORT_MESSAGE for a mobile that is GHOST or
5 WEMT capable, it shall send an ANSI_MAP Short Message Delivery Point to Point INVOKE
6 message. Refer to Table 132 for the mapping of parameters from GSM MAP
7 _FORWARD_SHORT_MESSAGE to ANSI-SMDPP.
8 When the Return Result for the SMDPP is received, the IIF sends back a positive
9 acknowledgement to the Forward Short Message.
10
13 Message Center.
14 If a Return Error or Reject is received in response to the ANSI_MAP Short Message Delivery
15 Point to Point INVOKE, the error code is mapped into the corresponding Forward Short
16 Message error code as described in Table 117.
17

19
21 message waiting notification in accordance with the tables presented. Within the following
22 tables, the parameters are identified as either being Mandatory (M), Conditional (C), Service
23 Provider Optional (O) or Service User Optional (U) in accordance with the definitions given in
24 GSM 09.02 [3] and ANSI-41 [6], [7], 0.
25 Table 127 shows the mapping between ANSI MAP messages and GSM MAP messages
26 related to Message Waiting Notification in GSM Foreign ModeTable 128 shows the mapping
27 between GSM MAP messages and ANSI MAP messages related to Message Waiting
28 Notification in ANSI-136 41 Foreign Mode.
29 Table 127: Message Waiting Notification in GSM Foreign Mode Message Mapping
Regnot FORWARD_SHORT_MESSAGE
QUALDIR FORWARD_SHORT_MESASGE
30
31 Table 128: Message Waiting Notification in ANSI-136 41 Foreign Mode Message Mapping
FORWARD_SHORT_MESSAGE QUALDIR
FORWARD_SHORT_MESSAGE SMDPP
32
163
N.S0028
1 When the IIF receives either a GSM MAP message or an ANSI MAP message, it shall apply
2 the following rules regarding the handling of parameters within those messages:
3 The IIF shall populate mandatory parameters in messages sent by the IIF, regardless of
4 whether mapping of parameters is possible.
5 The IIF may populate optional parameters in messages sent by the IIF, regardless of whether
6 mapping of parameters is possible.
7 All parameters shall be populated in accordance with either GSM 09.02 [3] or ANSI-41 [6], [7],
8 0.
9
10 Table 129 through Table 134 show the mapping of parameters, which the IIF shall perform
11 regardless of the mode of operation (GSM Foreign Mode or ANSI-136 41 Foreign Mode).
12 Where there is no direct mapping for parameters, a ‘-‘ has been entered in the corresponding
13 table.
14 Table 129: Regnot to Forward Short Message for Message Waiting Notification
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
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)
19
20 Note 1: This parameter is only valid for MAP V2.
21
164
N.S0028
3 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
4
5 Table 132: Forward Short Message to SMDPP for Message Waiting Notification
6 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
7
8
165
N.S0028

3 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.
4
5
166
N.S0028
1
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
5
167
N.S0028

3 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
4
5
168
N.S0028

3
4 4.5.3.3.1 Error Handling at the Reception of a Forward Short Message

5
7 4.5.3.3.2 Error Mapping from ANSI QUALDIR to GSM FSM

8

10 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
11
12 4.5.3.3.3 Error Mapping from ANSI SMSDPP to GSM FSM

13
14 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
15
16
169
N.S0028
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-136 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-136 41 radio
6 environment.
7 4.6.1 Mobility Procedures

8
11 Enhancements and modifications to GSM 02.60 [4] and ANSI-41 [7], 0 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
20 The IIF contains location information (SGSN number) relating to the roaming subscriber.
21 Therefore, the IIF needs to be updated at each change in SGSN. The IIF shall translate GSM
22 MAP messages to ANSI-41 MAP messages and vice versa when the subscribers home ANSI-
23 41 HLR needs updating. The subscriber’s ANSI-41 HLR shall be updated in the following
24 cases:
25 • When the subscriber’s MS registers in an SGSN in a GSM network, when previously

26 registered in an ANSI-41 network;
27 • When the subscriber’s MS registers in an ANSI-41 network, when previously registered in

28 an SGSN in a GSM network;
29 The subscriber’s home HLR may be updated in the following cases:
30 • When the subscriber’s MS (accessing a GSM Network) registers in another SGSN within
31 the same GSM network. The IIF acts like a GPRS HLR/AuC in this case.
32 • When the subscriber’s MS (accessing a GSM network) registers in a SGSN when

33 previously registered in a GSM VLR within the same GSM network.
34 When the HLR is updated, the IIF conveys a unique identifier to the ANSI-41 HLR identifying
35 the SGSN/GSM VLR or IIF, depending on Multiple MSCIDs optional support.
36 If the IIF receives a GSM_ MAP_UPDATE_GPRS_LOCATION _REQUEST, it shall compare
37 the received routing area information with any previously stored routing area information. If the
38 received and previously stored routing area information are different, the IIF shall determine if
39 the location updating is allowed and update the corresponding subscriber record accordingly
170
N.S0028
1 and send a GSM MAP _CANCEL_LOCATION_REQUEST to the old SGSN. If there is no

2 previously SGSN stored routing area information in the IIF, the IIF shall determine if the location
3 updating is allowed and update the corresponding subscriber record accordingly.
4 If the IIF receives a GSM MAP _MS_PURGE_REQUEST, it shall check the contents of the
5 message for errors. If errors exist, the IIF shall send a GSM MAP _MS_PURGE_RESPONSE
6 indicating the reason for failure and the MS purged flag shall not be set. If no errors exist, the
7 IIF shall check if the received SGSN number matches the stored SGSN number.
8 If the received SGSN number and the stored SGSN number match, the IIF shall set the MS
9 purged flag and shall send both a GSM MAP _MS_PURGE_RESPONSE to the SGSN and an
10 ANSI_MAP_MS_INACTIVE to the ANSI-41 HLR and awaits a response from the HLR.
11 If the received SGSN number and the stored SGSN number do not match, the IIF sends a GSM
12 MAP _PURGE_MS_RESPONSE containing an empty result to indicate that the MS purged flag
13 is not set.
14 If the MS requests a combined GSM and GPRS attach, then the SGSN requests a GPRS
15 location update to the IIF (acting as a GPRS HLR) and then the GSM-MSC requests a CS
16 location update. CS location update and mobility procedures are described in 4.1 Mobility
17 Procedures.
18
20
21 The following tables present the mapping of presents the mapping of messages, parameters
22 and parameter values that the IIF shall perform.
23
25
26 Table 137 shows the mapping between GSM MAP messages and ANSI MAP messages
27 related to GPRS Location Registration when necessary.
28 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
29
1
30 This procedure is used to download GPRS subscriber data to the SGSN.
2
31 This message can also contain error values if the location updating procedure is unsuccessful.
32 If the location updating procedure fails, the mapping is as shown in 4.1.1.3.
33 Table 3 shows the mapping between GSM MAP messages and ANSI MAP messages for MS
34 Purge operation. Table 4 shows the mapping between GSM MAP messages and ANSI MAP
35 messages related to Location Cancellation.
36
171
N.S0028

2
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
2
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 ANSI-41-C and later.
11
172
N.S0028
1
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
6
1
10 shown in Table 140:
11
173
N.S0028
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
3
- 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 MSC/VLR,
4 identifying the HLR.
3
9
10 As far as mapping of parameters is concerned, the IIF shall map the contents of the ‘Profile’
11 macro in the ANSI-41-D GSM MAP _INSERT_SUBSCRIBER_DATA_REQUEST as shown in
12 Table 141:
13
174
N.S0028
2 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
5
HPLMN data
Roaming Restriction Due To C -
Unsupported Feature
- RoutingDigits O
3 7
Call barring information List C SMS_OriginationRestrictions O
3 8
Call barring information List C SMS_TerminationRestrictions O
- SPINIPIN O
- SPINITriggers O
175
N.S0028
1
2
3 Table 141: MAP_INSERT_SUBSCRIBER_DATA_REQUEST → macro profile Mapping
4 (concluded)
MAP_INSERT_SUBSCRIBER_D Status ‘profile’ macro Status

ATA_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
8
SMS_TerminationRestrictions O
6
SS-Data List
North American Equal Access U -
preferred Carrier Id
Roaming Restricted In SGSN C -
9
Due To Unsupported Feature
GPRS Subscription Data10 C -
11
Network access mode C -
5
1
6 The CallingFeaturesIndicator parameter provides a status of several ANSI supplementary
7 services. This information may map into one or more GSM MAP parameters as shown in Table
8 92.
2
9 The OriginationIndicator parameter defines the type of calls that a MS is allowed to make.
10 This information may map into one or more GSM MAP parameters as shown in Table 92.
3
11 The Call barring information List is a list of the call barring supplementary services that are
12 either active, quiescent or not active for individual or all teleservices. This information may map
13 into one or more ANSI MAP parameters as shown in Table 92.
4
14 Camel/WIN interworking is out of the scope of this version of the standard.
5
15 Operator Determined Barring HPLMN data may map into one or more ANSI MAP parameters
16 as shown in Table 92.
6
17 The SS-Data List may map into one or more ANSI MAP parameters as shown in Table 92.
7
18 The SMS_OriginationRestrictions may map into one or more GSM MAP parameters as shown
19 in Table 92.
8
20 The SMS_TerminationRestrictions may map into one or more ANSI MAP parameters as
9
22 The IIFmay decide to include this parameter in the request if certain services or features are
23 indicated as not supported by the SGSN. This parameter is used only by the SGSN.
10
24 This parameter contains a list of PDP-contexts a user has subscribed to. At GPRS location
25 updating the IIF shall include the complete GPRS Subscription Data. When there is a change in
176
N.S0028
1 GPRS subscriber data the IIF shall include only the new and/or modified PDP contexts. When
2 the SGSN receives GPRS Subscription Data it shall check if the received data has to be
3 considered as the entire GPRS subscription data. If so, it shall replace the stored GPRS
4 Subscription Data with the received data set, otherwise it shall replace the data only for the
5 modified PDP contexts (if any) and add the new PDP contexts (if any) to the stored GPRS
6 Subscription Data. If GPRS Subscription Data is omitted in the Insert Subscriber Data operation
7 the SGSN shall keep the previously stored GPRS Subscription Data.If the SGSN detects that
8 there is overlapping in the information received within a dialogue, it shall send the error
9 Unexpected Data Value. This parameter is used only by the SGSN.
11
10 This parameter defines the access capabilities of a registered MS.
11 Error handling, Fault Recovery procedures and Error Code mapping are described in 4.1
12 Mobility Procedures.
13 4.6.2 Automatic Call Delivery

14
15 The Automatic Call Delivery procedure is invoked in the IIF, when a terminating call attempt
16 results in a request for routing information from the IIF.
17 The following procedures are applicable at the IIF for GPRS in GSM Foreign mode Automatic
18 Call Delivery:
19

21
22 If the IIF receives an ANSI MAP_RoutingRequest Invoke message from the ANSI-41 HLR, it
23 shall check if the terminating call can be placed to that subscriber. Call delivery to an MS that is
24 roaming in a GPRS network in GSM foreign mode shall be delivered only if the subscriber is
25 registered with a GSM serving MSC/VLR. As such, the IIF (acting as a GSM HLR) sends the
26 GSM serving MSC/VLR a MAP Provide Roaming Number (PRN) see 4.2.1 Call Delivery.
27
28 If the MS is attached for GPRS-only services, incoming calls are not deliverable to the
29 subscriber. Upon the reception of ROUTEREQ, the IIF determines if the MS is attached for
30 GPRS-only services and if so, the IIF shall not deliver the call. The IIF sends a routreq with the
31 field “AccessDeniedReason” set to “No Page Response” or “Unavailable”.

33
34 In this case, the IIF has the calling party DN available (from the ROUTEREQ message). Upon
35 the reception of a ROUTREQ, if the MS is only GPRS attached, the IIF proceeds to act as an
36 SMS-SC and sends an FSM to the SGSN requesting the SGSN to deliver an SMS message
37 containing the calling party’s DN to the MS. The mapping of parameters is shown in the
38 following table:
39
40
177
N.S0028
1 Table 141 A: 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 -
2
3
4
5
6
178
N.S0028
1 Table 141 A : 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
7 4.6.2.1.1.1 Error Code Mapping
8
9 Appropriate errors for an MS attached to both GPRS and non-GPRS services are described in
10 4.2.1.3
11
12 Appropriate AccessDeniedReason parameter values in the RoutingRequest Return Result for
13 the case of a call delivery attempt to an MS attached for GPRS-only services:
14
AccessDeniedReason
Unavailable
No page Response
15
179
N.S0028
1 4.6.3 Short Message Procedures for ANSI-136 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 [3] and GSM 03.60 [5] or ANSI-41
5 [6], [7], 0 are also directly applicable to the IIF when it is emulating a GPRS, GSM or ANSI-41
6 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
11 The Short Message Service procedure is used to deliver short text messages to and from
12 mobile subscribers.

14
15 The following procedures are applicable at the IIF for Short Message Service. Mobile
16 Terminating SMS and Mobile Originated SMS using the CMT teleservice ID are described.
17
18 4.6.3.1.1.1 Mobile Terminating SMS

19
20 If the IIF receives an ANSI-41 Short Message Delivery Point to Point message it shall check if
21 the MS location is known and if the subscriber is reachable. If both conditions are true, the IIF
22 shall format and send a GSM_ MAP_FORWARD_SHORT_MESSAGE (FSM) to the SGSN
23 serving the mobile. Refer to Table 109 for the mapping of parameters from ANSI_SMDPP to
24 GSM MAP _FORWARD_SHORT_MESSAGE.
25 If a successful response is received for the FSM, the IIF shall return SMDPP Return Result
26 message. If the MS's location is not known, or if the MS is not reachable or if the response to
27 the FSM indicates the short message was not delivered to the mobile, the IIF shall set the SMS
28 Delivery Pending flag for the subscriber. The IIF shall then return an SMDPP Return Result
29 message with an appropriate SMS_CauseCode value. Refer to 4.5.1.3 Error Handling for the
30 values of SMS_CauseCode returned.
32 be processed or if mandatory parameters are missing. Otherwise, the IIF shall return a SMDPP
180
N.S0028
1 If the response to FSM indicates a failure in the delivery of the short message, the IIF
2 shall map the cause value received to a corresponding SMS_CauseCode value in the
3 SMDPP Return Result, as described in
6
7 Table 116.
8
9 4.6.3.1.1.2 Alerting for GPRS in GSM Foreign Mode in either CMT or GHOST/WEMT
10 format
11
12 The SMS Alert procedure is used for alerting the SGSN when the MS is available for short
13 messaging after a short message transfer has failed because the mobile subscriber is not
14 reachable or when the MS has indicated that it has no memory capacity to accept a short
15 message.
16 Upon receipt of a READY_FOR_SM message, the IIF shall store the originating SGSN address
17 and Invoke ID in the subscriber’s profile. It shall map the GSM_READY_FOR_SM message to
18 the ANSI_SMSNOT INVOKE message as described in Table 119.
19 It shall populate the SMS_Address parameter with the IIF address. All other parameters are
20 ignored.
21 The ANSI_SMSNOT INVOKE is then transmitted to the subscriber’s SGSN with local
22 Transaction ID. Finally, the IIF shall return a READY_FOR_SM_ACK message with no
23 arguments to the originating SGSN.
24 Upon receipt of a SMSNOT RR message, the IIF shall associate the SMSNOT Transaction ID
25 with the Invoke ID.
26 If the IIF receives a GSM MAP _READY_FOR-SHORT_MESSAGE and the Delivery pending
27 flag is set for the subscriber, the IIF shall send an ANSI_MAP_SMS_NOTIFICATION message
28 to the home Message Center. The IIF shall clear the MNRG flag if Alert Reason is set to MS
29 present or The Memory Capacity Exceeded Flag (MCEF) flag if Alert Reason is set to Memory
30 Available and the flags were previously set. If the Alert Reason indicates the mobile present for
31 non GPRS situation, or when the update location procedure has been successfully completed
32 or Supplementary Service Control request is received, the MS not reachable flag (MNR) is
33 cleared and the service centre alert procedure is initiated. If the memory capacity exceeded flag
34 is set, the MS not reachable flag is cleared and stored reason for absence for non GPRS are
35 cleared but the alert procedure is not started. If the Alert Reason indicates the mobile present
36 for GPRS situation, or when the Update GPRS location procedure has been successfully
37 completed, the MS not reachable for GPRS (MNRG) flag is cleared and the service centre alert
38 procedure is initiated. The mapping of parameters is described in Table 142.
39 The ANSI-41 MC shall re-send message SMDPP to deliver the short message to the subscriber.
40
181
N.S0028
2 Table 142: Alerting for an ANSI-136 41 Subscriber for GPRS in GSM Foreign Mode
3 Parameter 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
4 This parameter indicates that the alert reason is sent to the HLR due to GPRS activity.
5
6 4.6.3.1.1.3 Mobile Originating SMS for GPRS in GSM Foreign Mode

7
8 If the IIF receives a GSM_FORWARD_SHORT_MESSAGE for a mobile originated short
9 message, it shall format and send an ANSI_MAP_SMDPP message to the home Message
10 Center. Refer to Table 114 for the mapping of parameters from GSM MAP
11 _FORWARD_SHORT_MESSAGE to ANSI_SMDPP.
14 If the IIF receives a negative acknowledgment to the SMDPP message, it shall map the
15 received SMS_CauseCode value into a corresponding error code in the FSM Response
16 message as described in Table 117. Also the IIF shall set the Mobile Not Reachable for GPRS
17 (MNRG) GSM SMS flag.
19 response message. Refer to 4.5.1.3 for the handling of errors at the reception of FSM.
20
182
N.S0028

3
5 Short Message Service in accordance with the tables presented in 4.5.1.2.1.

7
8 Error handling is described in 4.5.1.3
9 4.6.4 Short Message Service via GHOST or WEMT

10

12
13 4.6.4.1.1 SMS Delivery for an ANSI-136 41 Subscriber for GPRS in GSM Foreign
14 Mode
15
16 Upon receipt of an SMSDeliveryPointToPoint INVOKE message, the IIF shall store the
17 originating MC address and transaction ID. It shall map the ANSI_SMDPP message into a
18 GSM_FSM message and populate the subscriber’s known SGSN into the DPC. The IIF
19 transmits the GSM_FSM message with local Invoke ID.
20 The mapping of parameters is described in Table 121.
23 Invoke ID with SMDPP transaction ID and map the GSM_FSM_ACK message into an
25 Next, it populates the stored originating SGSN address into the DPC and populates the
26 transaction ID.
28 the SMS_CauseCode according to
29
30
31
32 Table 116.
33 Finally, the ANSI_SMDPP RR is transmitted to the originator.
183
N.S0028
1 4.6.4.1.2 SMS Origination
2
3 Upon receipt of a MO_FORWARD_SHORT_MESSAGE, the IIF shall store the address of the
4 originating SGSN and Invoke ID. It shall map the GSM_MO_FSM to ANSI_SMDPP INVOKE.
5 The address of the subscriber’s TSA (from the SM RP DA – Service Center Address) is
6 mapped according to 4.5.2.4 into the SMS_DestinationAddress. The IIF transmits the
7 ANSI_SMDPP INVOKE message with local transaction ID. The mapping of parameters is
10 transaction ID with Invoke ID and map the ANSI_SMDPP RR to the GSM_FSM_ACK.
11 Next, it populates the stored originating SGSN address and Invoke ID. If SMS_CauseCode
14 Finally, transmit the GSM_FSM_ACK to the originating SGSN.

16
18 Short Message Service in accordance with the tables presented in 4.5.2.2.
19

21
22 Error handling is described in 4.5.1.3
23 4.6.5 Message Waiting Notification

24
25 The Message Waiting Notification procedure is used to notify a mobile subscriber of voice mail
26 messages added or removed in his voice mail system. 4.6.5 shows only the changes needed to
27 support GPRS service for an ANSI-136 41 subscriber in GSM foreign mode.
28 If the subscriber is both GSM CS attached as well as GPRS attached, then the IIF shall act
29 like a GSM SMS-SC.
31 4.6.5.1.1 Registration Notification Return Result with MWN Information Received

32
33 When the IIF receives a Registration Notification Return Result message with MWNCOUNT
34 and MWNTYPE parameters set to valid values, it shall send a GSM SMS with the MWN
35 information.
36 The IIF shall then format and send a GSM MAP_FORWARD_SHORT_MESSAGE. Refer to
37 Table 129 for the mapping of parameters from ANSI-41 regnot return result to GSM MAP
184
N.S0028
3 If the response to FSM indicates an error condition, or if a time out occurs, the MWN
4 information is sent in a new GSM MAP _FORWARD_SHORT_MESSAGE when the IIF
5 receives a new GSM MAP _UPDATE_GPRS_LOCATION, GSM MAP
6 _READY_FOR_SHORT_MESSAGE or GSM MAP _NOTE_MS_PRESENT message.
7 When the IIF receives a QUALDIR INVOKE message from the ANSI-41 HLR with
8 MWNCOUNT and MNWTYPE parameters set to valid values, it shall set the Message waiting
9 Notification flag and the IIF shall send a GSM MAP FORWARD_SHORT_MESSAGE. Refer to
10 Table 130 for the mapping of parameters between ANSI-QUALDIR and GSM-
11 _MAP_FORWARD_SHORT_MESSAGE.
12 If an error is detected in the QUALDIR INVOKE message, a Reject or Return Error message is
13 sent back to the sending node. No other processing is executed.
16 If an error is received in the response to FSM, or if a time out occurs, the MWN information is
17 sent in a new GSM MAP _FORWARD_SHORT_MESSAGE when the IIF receives a new GSM
18 MAP _UPDATE_GPRS_LOCATION, GSM MAP _READY_FOR_SHORT_MESSAGE or GSM
19 MAP _NOTE_MS_PRESENT message.

21
23 message waiting notification in accordance with 4.5.3.2.

25
27
28 4.6.5.3.1 Error Mapping

29
30 Refer to 4.5.3.3.2 Error Mapping.
31
32
33
34
185
N.S0028
1
2
3 ANNEX A Short Message Service Procedures

4 within an ANSI-136 Network
5 (Normative)
6
7 GHOST may be used as the delivery teleservice from a short message entity to a mobile
8 station operating in ANSI-136 Native Mode through a SMSC, which is providing IIF functionality
9 at the GSM TP-layer. In this case, normal ANSI-41 procedures are used to deliver the GHOST
10 teleservice between ANSI-41 network elements and normal ANSI-136 procedures are used to
11 deliver the GHOST teleservice from the serving MSC to the mobile station. The SMSC is
12 responsible for identifying the MS as GHOST capable and for packaging the short message in
13 the proper format using the GHOST teleservice for delivery to the MS.
14
15 A.1 CMT to GHOST Delivery

16
17 If the short message entity is an MS originating a message using the Cellular Messaging
18 Teleservice (CMT) teleservice to the GHOST MS, then upon receipt of the CMT message the
19 SMSC proceeds as follows.
20
21 A.1.1 Detailed Procedures

22
23 After determining the incoming CMT message is destined for an MS that supports the GHOST
24 teleservice, (the method to perform this identification is internal to the SMSC and beyond the
25 scope of this standard) the SMSC shall determine the status and location of the targeted MS
26 using normal ANSI-41 procedures.
27 If the MS is unavailable or the location is unknown, the SMSC shall set an internal retry
28 schedule or wait for notification from HLR. Otherwise, it shall populate address delivery
29 information and optional parameters per normal ANSI-41 procedures. Next, it shall map the
30 contents of the SMS_BearerData per Table 143 and populate the SMS_TeleserviceIdentifier
31 with the GHOST teleservice identifier. Finally, it shall transmit the SMDPP INVOKE message
32 to the serving MSC.
33
34 A.1.2 Mapping of Messages, Parameters & Parameter Values

35
36 When the SMSC receives the SMDPP Invoke message from a CMT capable MS, the SMSC
37 follows normal ANSI-41 procedures except it replaces the CMT value of 32513d with the
186
N.S0028
1 GHOST value. In addition, the following parameter mapping related to ANSI-136-710 shall be
2 performed as indicated in Table 143.
3
4
5 Table 143: 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
6
7 Note 1: In GSM, delivery acknowledgement indicates that the data is stored at the MS. In ANSI-
8 136, delivery acknowledgement is triggered by an action of the MS user (displaying the
9 message). Therefore this parameter is not mapped. It is a local decision for the operator as to
10 how to treat MO messages requesting these acknowledgements. The recommended procedure
11 for operators is for the MC to return a SMS DELIVERY ACK to the originator upon receipt of a
12 positive delivery confirmation from the terminating mobile. The procedures and format of the
13 SMS DELIVERY ACK message shall follow ANSI-136-710.
187
N.S0028
2 Table 144 describes where the parameters in the MT GHOST message are derived from:
3 Table 144: 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.
4
5
6 A.1.3 Error Handling

7
8 No additional error handling procedures beyond those in ANSI-41D are required.
9
10 A.2 GHOST to CMT Delivery

11
12 GHOST may be used to deliver teleservices from a mobile station operating in ANSI-136 Native
13 Mode to an MS-based short message entity, which only supports the CMT ID without the
14 involvement of an IIF.
188
N.S0028

3
4 The mobile station formulates a GSM SMS PDU and adds the GHOST header to the GSM
5 SMS PDU. If required, it adds the TSAR header to the GHOST teleservice. Next, it inserts the
6 GHOST teleservice into the Higher Layer Protocol Data Unit of the R-Data Unit and adds the
7 GHOST HLPI. An R-DATA message is formulated and sent to the ANSI-136 BMI.
8 The ANSI-136 MSC follows normal procedures and translates the R-DATA message to an
9 ANSI-41 SMDPP Invoke message and sends it to the originator’s home MC. The MC
10 destination address can be specified in the Teleservice Server Address. {Alternatively, MIN to
11 MC GTT or a routing table in the MSC may be used if the TSA is not present.} The MSC does
12 not open the Higher Layer Protocol Data Unit, but converts it directly to SMS_BearerData.
13 For the mobile station in ANSI-136 Native Mode, the Teleservice Server Address shall indicate
14 that the home Teleservice Server is the home Message Center. Upon receipt of the SMDPP
15 Invoke message, the SMSC responds with a SMDPP RR per normal ANSI-41 procedures.
16 The SMSC then identifies the destination address as an MS that supports CMT. (The method to
17 perform this identification is internal to the SMSC and beyond the scope of this standard.) It
18 then determines the status and location of the targeted MS using normal ANSI-41 procedures.
19 If the MS is unavailable or location is unknown, the SMSC shall set its internal retry schedule or
20 wait for notification from HLR
21 Otherwise, it shall populate the address delivery information and optional parameters per
22 normal ANSI-41 procedures. Next, it maps the contents of the SMS_BearerData per Table 145
23 and MT CMT message are derived from
24 Table 146 and populates the SMS_TeleserviceIdentifier with the CMT teleservice identifier.
25 Finally, the SMSC transmits the SMDPP Invoke message to the serving MSC.
26
27 Supported user data mappings
28
29 The following user data mappings should be supported:
30
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.
31
32
189
N.S0028
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 145.
8 Table 145: 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
10
190
N.S0028
1
2 Table 146 describes where the parameters in the MT CMT message are derived from
3 Table 146: 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 148
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
4
5 If the TP-Status-Report-Request is requested, then Table 148 provides mapping to identify the
6 status of a message being sent to a CMT mobile from a GHOST mobile. The SMS-STATUS-
7 REPORT is encapsulated in a new SMDPP message to the status requester. The derived
8 values for the SMS-STATUS-REPORT are contained in Table 148.
9
191
N.S0028
2 Table 147: 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
4
192
N.S0028
1
2 Table 147: 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).
5
193
N.S0028
2 Table 148: 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 147
TP-Parameter-Indicator O -
TP-Protocol-Identifier O -
TP-Data-Coding-Scheme O -
TP-User-Data-Length O -
TP-User-Data O -
3
4

6
8
9
194
N.S0028
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
195
N.S0028
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
20 Mapping for messages, parameters and parameter values shall be as according to §A.1.2
21 Mapping of Messages, Parameters & Parameter Values.
22
23 A.3.2.2 External SME

24
25 ANSI-41/136 mapping for messages, parameters and parameter values for a GHOST message
26 is not affected by the Callback Number procedures.
27
28 A.3.2.3 GHOST to CMT

29
30 Mapping for messages, parameters and parameter values shall be as according to §A.2.2
31 Mapping of Messages, Parameters & Parameter Values.
32

34
36
196
N.S0028
2 ANNEX B Cause Code Mapping at Non-IIF Nodes

3 (Informative)
4
5 This annex is informative and describes processing that does not affect the IIF.
6
7 A mobile station shall respond to a received GHOST teleservice after processing the relay
8 layer. If the relay layer generates a failure, then the mobile station shall map the resulting RP-
9 Cause value into its equivalent R-Cause code according to Table 149.
11 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)
12
13 At the ANSI-136 MSC, the R-Cause code returned by a mobile station is mapped into a
14 corresponding ANSI-41 SMS_CauseCode for inclusion in an SMDPP Return Result message.
15 At the ANSI-136 MSC, the ANSI-41 SMS_CauseCodes are mapped to ANSI-136 R-DATA
16 REJECT R-Cause codes according to Table 150. The mobile station in turn maps the R-Cause
17 codes to RP-ERROR Causes according to Table 151.
18
197
N.S0028
2 Table 150: 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)
3
5 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)
6
7 ANNEX C: CDMA to GSM One-way Roaming Only

8 (Informative)
9
10
11 Optionally, IIF may support one way-roaming only from CDMA to GSM networks.
12 In this case, all the mapping tables are applicable only in GSM Foreign Mode.
13 The IIF maps the ANSI-41 authentication parameters to the GSM triplets
14 All the changes are made on the assumption that the new requirements for UIM/handsets are
15 working. Table 152 shows the location updating mapping in the GSM foreign mode.
198
N.S0028
1 Table 152: UPDATE_LOCATION_REQUEST ->REGNOT Parameter Mapping

ST
MSID M
1 1
MSC Address M MSCID (Serving MSC) M
- QualificationInformationCode M
2
3 Table 152: UPDATE_LOCATION_REQUEST ↔ REGNOT Parameter Mapping (concluded)

ST
VLR Number M -
2
2
TerminalType O
2
LMSI U -
Supported CAMEL Phases C -
- -SYSACCTYPE3 O
4
1
5 These parameters are used to convey a unique identifier from the IIF to the HLR, identifying
6 the serving MSC/VLR.
2
7 Parameters are included in ANSI specifications IS-41-C and later.
3
8 SYSACCTYPE parameter is required for the one-way CDMA to GSM roaming optional
9 scenario and in this case the parameter must be set by IIF to indicate GSM access type.
10
11
199
N.S0028
1
2
200

3GPP GSM Network Interworking N.S0028-0 v1.0

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

3GPP GSM Network Interworking N.S0028-0 v1.0

Transféré par

Droits d'auteur :

Formats disponibles

3GPP2 N.

Version Date: April 2002

Network Interworking Between GSM MAP and

Rev. 0 Initial Publication April 2002

This specification is an extract of TIA TR-46.3 J-STD-038-B.

(This page is intentionally left blank)

2 Document Revision History

Revision Date Version Comment

0 March 2001 Post Ballot version with ballot comments

4 Document Revision History.......................................................................................................... ii

7 List of Figures............................................................................................................................ vii

10 1.1 General ..............................................................................................................1

15 3 Definitions and Acronyms................................................................................................4

16 3.1 Definitions ..........................................................................................................4

17 3.2 Acronyms ...........................................................................................................6

18 4 Overview of Internetwork Roaming..................................................................................8

19 5 IIF Reference Model and Description...............................................................................9

20 5.1 Reference Model ................................................................................................9

21 5.2 Description .........................................................................................................9

23 5.3 Interworking for Network Interfaces...................................................................11

1 5.3.4 HLR – SGSN Interface.........................................................................16

2 5.4 IIF Implementation Alternatives.........................................................................16

8 Document Revision History.......................................................................................................... ii

14 1.1 General ..............................................................................................................1

19 3 Definitions and Acronyms................................................................................................3

20 3.1 Definitions ..........................................................................................................3

21 3.2 Acronyms ...........................................................................................................4

22 4 Overview of Internetwork Roaming..................................................................................6

23 5 IIF Reference Model and Description...............................................................................7

24 5.1 Reference Model ................................................................................................7

25 5.2 Description .........................................................................................................7

1 5.3 Interworking for Network Interfaces.....................................................................8

5 5.4 IIF Implementation Alternatives.........................................................................12

19 [8] TIA/EIA/IS 735 “IS-41 support for IS-95-A (advanced CDMA)”

20 [9] TIA/EIA/TSB58-E A “Administration of Parameter Value Assignments for TIA/EIA Spread

2 3 Definitions and Acronyms

1 CDMA Foreign Mode

2 AC Authentication Center in ANSI TIA/EIA-41 based networks

3 AuC Authentication Center in GSM networks

4 AMPS Advanced Mobile Phone Service

5 ANSI American National Standards Institute

6 CDMA Code-Division Multiple Access

7 EIA Electronics Industries Association

8 ESN Electronic Serial Number

9 ETSI European Telecommunications Standards Institute

10 GMSC Gateway Mobile Switching Center

11 GSM Global System for Mobile Communication

12 GGSN Gateway GPRS Serving Node

13 GPRS General Packet Radio Service

14 HLR Home Location Register

15 HPLMN Home Public Land Mobile Network

16 IIF Interworking and Interoperability Function

17 IMSI International Mobile Subscriber Identity

18 ITU International Telecommunications Union

19 MAP Mobile Application Part

20 MC ANSI-41136 Message Center (for SMS)

22 MIN Mobile Identification Number

24 MSC Mobile Switching Center

25 MSID Mobile Station Identity

26 MSISDN Mobile Subscriber ISDN Number

27 PDP Packet Data Protocol

1 PLMN Public Land Mobile Network